MrPoopyButthole

joined 2 years ago
MODERATOR OF
[–] MrPoopyButthole@lemmy.dbzer0.com 4 points 8 months ago (4 children)

You would be surprised. When I am tolerant for a high dose I can vape 6 or 7 times a day which equates to around 3g of strong weed. And that would be every day. About 90g per month.

Yes I have a problem.

[–] MrPoopyButthole@lemmy.dbzer0.com 36 points 8 months ago (2 children)

I couldn't be bothered to DL anything anymore so I just browse the mega list whenever my fav one bows out.

https://rentry.co/megathread-movies-and-tv

[–] MrPoopyButthole@lemmy.dbzer0.com 4 points 8 months ago (1 children)

Well I don't wear underwear at all already 😀

GDPR ownership of your data and the ability to have your data erased

Kubernetes is extremely expensive on cloud so we run our own in house

Our problems with VMs on Azure were:

  • The Azure Linux Agent incrementing versions and breaking stuff.
  • The availability zone becoming over utilized and our non reserved VM clusters fail to start up.
  • Changes to Azure automation runbooks breaking scripts and schedules. (unrelated to the stuff they warned about)
  • Azure invisible proxy terminating ssh sessions as inactive while doing long running tasks and having to use the awful serial console.
[–] MrPoopyButthole@lemmy.dbzer0.com 1 points 9 months ago (3 children)

We take a cloud agnostic approach to systems development so we have flexibility. Our team is quite small and we use Manageengine for patching servers and Atera for patching users systems. We only use a few cloud native services like AWS event bridge, load balancers, S3, Lambda, Azure DNS, Azure storage, Azure App service. But if needed we could pull any one of those and move to an open source solution without too much fuss. The red tape comes from exec level and their appetite for risk. For some reason they think cloud is more stable than our own servers. But we had to move VMs off Azure because of instability!

[–] MrPoopyButthole@lemmy.dbzer0.com 1 points 9 months ago (5 children)

Yeah we were hit hard by the cost projections. It really sucks. But HCI stack from MS remains even more expensive. We have decided to bring as much as we can in house and only put the workloads that have strict contractual uptime agreements on our VMware or HCI stack. The rest of the stuff goes on KVM or bare metal to save costs.

view more: ‹ prev next ›