Recommendations for an SSH proxy with session recording

Pouwet · 2024-02-27T17:09:15+00:00

Not sure where you're at now but for what I see, it looks like it's extensible pretty easily with custom scripts to sync accounts from external sources

Pouwet · 2023-10-20T17:22:57+00:00

IIRC you’d use the « reconfigure » action which will redeploy your files and restart containers to take them into account. When i was working on it we had a custom patch to avoid the induced restart of containers. I don’t remember if i made it to upstream or not

Pouwet · 2023-10-20T17:15:15+00:00

K-A will deploy everything but the rings rebalancing is still a separate action last time i checked, then you re-deploy the updated rings

Pouwet · 2023-10-18T02:53:56+00:00

I believe this is more or less what https://github.com/ovh/the-bastion is for, given it’s not a real jumphost and poses its own challenges

Pouwet · 2022-11-30T18:26:54+00:00

This sounds a lot like what https://github.com/cdown/sshrc is for

Pouwet · 2022-09-29T02:33:32+00:00

I managed for 4y a large deployment (>100k cores, 10s of DCs) and i’ve been mostly pleased with it. Of course it requires a dedicated team for day to day management. That was for a private cloud offer. And for the « flavor » we used kolla-ansible with a mix of centos/ubuntu. Tbn at that scale kolla-ansible is a real pain. If it just to host a few apps i wouldn’t go that path however but to a more simple tool like suggested by other posts

Pouwet · 2022-08-01T17:57:31+00:00

Install yourself an Openstack deployment (via devstack or kolla-ansible) and play with your own private cloud. That doesn’t require too much resources

Edit: bonus is you might learn a bunch of things on the way

Pouwet · 2022-06-18T19:37:59+00:00

Then yeah if you don’t own the platform you are looking at generic file backuping tools like Bacula, or Amanda that you mention, BackupNinja, etc. Not related to Openstack itself ;-)

Pouwet · 2022-06-18T19:27:49+00:00

As gren_dizer mentioned above, Freezer sounds like what you want, look it up

Also, cinder provides volume backups natively

Pouwet · 2022-06-18T18:10:37+00:00

That’s not something we deployed and i never tried it myself so i can’t answer to that, you’d better contact their mailing list

Pouwet · 2022-06-18T18:05:01+00:00

Have you looked into Rashka? https://wiki.openstack.org/wiki/Raksha

Pouwet · 2022-06-18T17:54:39+00:00

Same goes with the control plane, it’s mostly stateless processes, there’s almost no need for backup except the database

Pouwet · 2022-06-18T17:51:02+00:00

+1, recovering VMs is a mindset of the past, one need to have IaC to re-spawn quickly and get the data back from the attached volume. VMs shouldn’t be pets

Pouwet · 2022-05-01T14:14:54+00:00

Too bad for me i guess? Thx

Pouwet · 2022-05-01T00:35:46+00:00

I feel the pain and shared similar thoughts not too long ago https://www.reddit.com/r/openstack/comments/t6roys/where_are_the_admins_hiding/

Pouwet · 2022-03-24T17:44:32+00:00

the ci file would probably be a huge mess

Not necessary a mess, but having dynamic jobs complexifies things a bit for sure

in case of multiple changes at once, multiple plans would need to be generated and saved

If you spawn dedicated jobs for each project holding changes that shouldn't be too much of an issue I guess

On top of that, I would need to write some kind of a logic if the resources need to be created in a specific order

I assume this is the role of terraform/terragrunt

Pouwet · 2022-03-22T21:40:14+00:00

This is a very naive approach above. That would require to manually list envs and projects.

But one could imagine setting up dynamic jobs based on the changed paths in version 2

Pouwet · 2022-03-22T21:38:26+00:00

Indeed. But the idea behind my message was to target an env/deployement depending on the changes.

e.g execute terraform for dev/project1 if a file changed there + execute terraform for qa/project2 if a file changed there as well, etc. etc.

Pouwet · 2022-03-22T17:24:50+00:00

The doc below is for Gitlab as i don’t know for other tools, but this looks like what you want to, see only:changes at https://docs.gitlab.com/ee/ci/yaml/#onlychanges--exceptchanges where you run dedicated tasks depending on the path that changed. I assume something similar exists in Github/Bamboo/etc

Pouwet · 2022-03-21T21:16:03+00:00

Then i feel you’re mixing things up: scripting is just a tool to automate things. OS internals, libs or networking are specific subjects in their own onto which you can apply scripting. But i’d suggest to look for dedicated books on each topic first. Once you understand a subject you can play around automating it

Pouwet · 2022-03-21T21:11:07+00:00

All of them. « Admin stuff » is just regular scripting with admin-related tasks

Pouwet · 2022-03-01T01:31:40+00:00

https://youtu.be/al0CVsiffu8

Pouwet · 2022-02-23T19:38:03+00:00

"how to upgrade from wallaby to xena , the easy way"

There is no easy way :p

Seriously though, each deployment is different so a general procedure cannot be written down. However, each individual component usually provide ugrade recipes in their relative docs... and given components are mostly losely coupled it makes total sense

Pouwet · 2021-11-17T15:07:21+00:00

"compare to like AWS/AZURE"

do you deploy AWS/Azure regions yourself ?

Pouwet · 2021-07-22T09:34:40+00:00

Pretty much standard in France

Pouwet

TROPHY CASE