openSUSE admin

pjessen wrote:

Shawn wrote:

What are the chances of finding some resources within the openSUSE Server
infrastructure for running @opensuse.org instances of things like Mastodon or
kbin, or whatever other federated services, for openSUSE members?

Presuming the hardware resources needed are "within reason", that is the easy part.

Ok, I'm running down some provisioning guidelines today, so I can give you a better idea of what potentially would be needed.

If it's a matter of somebody being willing to actually admin the things, I
personally don't have an issue doing the setup and being one of the folks,
I've already got experience setting up synapse, mastodon (and soon kbin)
through containers.

Yes, it is mostly a question of someone volunteering to do it. "it" being everything - setup, maintenance, troubleshooting, saltifying, upgrades etc etc.
Usually including the underlying system, (Leap 15.5, in exceptional cases Tumbleweed), but other people will also be able to help if necessary.

I mean, I'd prefer to be using microOS as the actual OS, but Leap or Tumbleweed would certainly work.

I haven't a clue how many actual openSUSE members there are, or how many would use them,

Currently about 700 members. As for the services proposed, I don't know either of them 😄

Ok, excellent, that gives me some numbers to figure out reasonable resource numbers.

sfalken wrote:

pjessen wrote:

Shawn wrote:

What are the chances of finding some resources within the openSUSE Server
infrastructure for running @opensuse.org instances of things like Mastodon or
kbin, or whatever other federated services, for openSUSE members?

Presuming the hardware resources needed are "within reason", that is the easy part.

Ok, I'm running down some provisioning guidelines today, so I can give you a better idea of what potentially would be needed.

Just some rough ballpark figures - 2-4 cpus, 4-6-8Gb RAM, 20-50-100Gb disk ? Adding vcpus and RAM is generally possible, as is extending the filesystem.

Yes, it is mostly a question of someone volunteering to do it. "it" being everything - setup, maintenance, troubleshooting, saltifying, upgrades etc etc.
Usually including the underlying system, (Leap 15.5, in exceptional cases Tumbleweed), but other people will also be able to help if necessary.

I mean, I'd prefer to be using microOS as the actual OS, but Leap or Tumbleweed would certainly work.

Unless there is something that means Tumbleweed is required, it'll be Leap 15.5.

When you're ready, @crameleon will no doubt be able to get a machine set up. Next we'll need to get you set up on the VPN, @cboltz
For DNS and email stuff, you can talk to me, although I'll be away for the next two weeks.

pjessen wrote:

sfalken wrote:

pjessen wrote:

Shawn wrote:

What are the chances of finding some resources within the openSUSE Server
infrastructure for running @opensuse.org instances of things like Mastodon or
kbin, or whatever other federated services, for openSUSE members?

Presuming the hardware resources needed are "within reason", that is the easy part.

Ok, I'm running down some provisioning guidelines today, so I can give you a better idea of what potentially would be needed.

Just some rough ballpark figures - 2-4 cpus, 4-6-8Gb RAM, 20-50-100Gb disk ? Adding vcpus and RAM is generally possible, as is extending the filesystem.

Yes, it is mostly a question of someone volunteering to do it. "it" being everything - setup, maintenance, troubleshooting, saltifying, upgrades etc etc.
Usually including the underlying system, (Leap 15.5, in exceptional cases Tumbleweed), but other people will also be able to help if necessary.

I mean, I'd prefer to be using microOS as the actual OS, but Leap or Tumbleweed would certainly work.

Unless there is something that means Tumbleweed is required, it'll be Leap 15.5.

When you're ready, @crameleon will no doubt be able to get a machine set up. Next we'll need to get you set up on the VPN, @cboltz
For DNS and email stuff, you can talk to me, although I'll be away for the next two weeks.

No rush. I'm still gathering information and whatnot.

crameleon wrote:

As we need to move services from Nuremberg to Prague this year it would make sense to wait for the infrastructure there so you don't have to migrate it shortly after setting it up.
We manage a big part of our infrastructure using SaltStack (https://code.opensuse.org/heroes/salt) - bonus points if you would deploy and manage your machines using Salt as well, but it's not a hard requirement. I suggest you read the policy (https://en.opensuse.org/openSUSE:Infrastructure_policy), it's outdated for the most part (especially the SUSE-IT related bits) but still gives a general idea of what's expected from someone maintaining a machine. Generally others in the team are already happy if it uses packages and comes back up after a reboot. ;-)
You can join our Heroes meeting every first Thursday of the month and #opensuse-admin to stay in touch.

Apart from this, Per already said it all. Let me know once you have your details.

Excellent, thanks, I'll read up. Like I said, this isn't something that has to happen tomorrow, if it makes sense to wait until things have settled down after the move, that certainly doesn't bother me in the least, it gives me more opportunity to make sure I know what I'm doing with my personal instances, and not going to cause a headache for the Heroes team in general.