thr0w3345

It really depends on your cloud; I recently worked with an openstack setup where I needed to create some 6 resources per compute instance, with ~200 instances that’s a whole lot of resource blocks to manage — hiding al that in a module abd passing in a dict of machines to create was imo the right choice..

Considering that the ps5 can play all PS4 games it seems highly likely.

Check out pocket earth, the UI is a bit clumsy but it’s clearly a labour of love by the author and has served me well in such scenarios..

Redhat acquired it, then ibm acequired redhat and then game over.

I really enjoyed salvation by peter f Hamilton lately if you’re into sci-fi :)

Gah, the exact same thing started happening for me with teams this week and it’s been driving me crazy.

I guess I’ll have to rm it, all its junk in ~/Library and see if it gtfo’s and starts behaving again..

Total bollocks.

I mean really there isn’t a more polite way to sum up this nonsense. To anyone going straight to comments, do yourself a favour and skip it.

If you think that’s bad, wait til you see what the iptables-save output is like on an istio-proxy sidecar ;)

Sorry to say, but this was the completely wrong approach and I’m amazed the business let you do it.

Some poor bastard is going to have to undo all your mess down the road, I hope you buy them a beer if they ever track you down. I mean, at what point do you make the call that writing your own in-house copy of _DOCKER_ is a smart move? Let alone Jenkins.. The ‘magic’ abilities you describe this platform as having are utterly standard features and are yours as soon as you install e.g gitlab...

Of course, you actually have to spend some time and learn them and how to use them properly, but that time is VASTLY less than learning how to implement them badly and minuscule compared to the amount of time it’s going to take to migrate off your in-house pile..

I highly recommend you look at leofs instead — it’s been absolutely rock solid for us.

You can use http basic since forever with git....

The agent approach is mostly ok, it tends however to suffer when you have more than a few hundred machines (I’ve found, anyway) that your ansible code rots a bit. Say for that one server, you know the one, the weird etl thing bi uses, was run once and during a prod problem you suddenly have to start fixing the ansible code to rebuild it.

With an agent, it’s applying all the time and this doesn’t happen.

We actually moved to salt from ansible and we’re happy..

The problem we have with ansible is not yaml related but the push based approach, even with awx/tower as soon as you’re running hundreds of machines of a given group it gets painful.

We are actually seriously considering a shift to salt atm...

But that would only allow them to sign new certs, CA’s don’t get the private keys only the public part to sign... Or did I misunderstand you?

The “visionary” plan which should be enough for a family is only like €20/month

I don’t get this at all.

It’s unlistenable. Dreadful. Who considers this music and why? What’s the point of it?

What am I missing?

Check out burp suite.

Fellow Invernesian here — you still local or escaped for different pastures?