Skype will shut down soon. I wanted an open source alternative so I tried Galene (https://galene.org/) multiple times to call my dad and it works very well.

For now, I spawn a disposable instance on OVHcloud using OpenTofu and the OpenStack provider. Then I configure the software using Ansible. The code is available here https://git.riou.xyz/jriou/galene-cloud.

Tomorrow, I would like to only host a TURN server on my VPS and self-host galene on my homelab.

Soon I might have a clue about #opentofu (those scary Terrahawks kept me off #Terraform).

Now I just need to hope #Azure will stop having resource availability issues in CentralUS or EastUS.

It'd be "such a shame" if we had to move back to AWS.

New shitpost from our Developer Experience team: "Tell me terraform no longer segfaults without telling me it no longer segfaults"

Happy Friday (deploy) everyone!

A versatile version manager for #OpenTofu, #Terraform, Terragrunt and Atmos, written in Go.
#golang

https://github.com/tofuutils/tenv

Whew...the muscle memory to type "tofu" instead of "terraform" is *really* strong. I made the switch fully a couple of months back, finally updating all my IAC repos to use #OpenTofu instead of #Terraform. I took the opportunity to centralize on a single reusable release pipeline instead of each having their own, which I honestly should have done in the first place but that's showbiz baby.

It's just like how when I switched to using "main" as my primary repository name, it took time to rework that muscle memory but eventually that became natural for me and typing in anything else when branching and merging felt strange.

So while maybe DevOps and SRE shouldn't be seen as a reflection of real life, in this case I think there's a lesson to be gleaned. Sometimes breaking a habit is hard. Sometimes it's more than just a habit and you're trying to change something fundamental about yourself or your work environment and that's even harder and maybe even impossible for some. But striving towards that goal is still important. Maybe it'll take you a year to make a change feel natural. Maybe it'll taken ten. Maybe it'll never feel 100% authentic and natural. That time is going to elapse either way. You can choose to stay right where you are right now or you can refactor and work towards something else and see how far you get.

Might as well right? Tech debt, emotional debt, it all comes due at some point and if you don't start now then it'll keep accruing and you'll still be sitting here 1 or 5 or 20 years from now thinking maybe you should fix something.

This is a post about #devops but I only got a few sentences into this before I realized I really wanted to write about life and about change and about doing something different.

So maybe what I do to pay the bills is more rooted in real life than I thought.

Discovered there is a way to move state if you need to rename a resource in OpenTofu/Terraform:

tofu state mv google_compute_subnetwork.current-region google_compute_subnetwork.current_region

do folks have opinions on which #OpenTofu / #Terraform provider to use for #Proxmox?

Anyone using terraform/opentofu for their homelab setups? Either on infra level or for CM?

I've made it a project for this year to get everything managed via gitops. I'm taking it step by step and as such I haven't locked down manual write access so that I can tinker with stuff and troubleshoot as needed.

I'm finding that I need a good way to spot state drift so that I get notified if I forget to correct things afterwards. I think this is going to be less frustrating than fighting against enforced state while I get my bearings.

I guess I could use a cron or a timer unit. Unless someone has any recommendations? I would like to manage all the TF using fluxcd eventually but I think it's too early to start enforcing desired state right now. I'm open to suggestions...?

howdy, folks - it's been a bit since our last #hachyderm infra check in.

stuff in motion:

- ditching #terraform cloud & tf for #opentofu and #atlantis. we are just about to import our dev environment and put it through its paces.
- bringing #postgresql under ansible management. the team has been doing awesome work, and we've started to spin up dev nodes using the new playbooks. soon: production!
- moving #DNS zones away from AWS route 53. we chose bunny DNS as our provider and have been doing basic tests in dev. we'll likely prep our records for production this week with a plan for a cutover in one of the coming weekends.

and if you filled out our volunteer form and haven't heard from me in a bit - you're still on the list. we'll onboard a new batch of folks in the next couple of weeks.

I must admit, writing in OpenTofu / Terraform is the first time in a while that I’m actually having fun with code. It is just genuinely enjoyable. It’s been a long time since I’ve had this much fun tinkering with code.
#OpenTofu #Terraform #IaC #DevOps

My employer is continuing to pursue increased sales to the US government, so for ethical reasons I'm fully on the job market now.

I am an experienced #devOps engineer, having worked exclusively with #AWS. I have extensive experience in #terraform and #openTofu with significant #Ansible work as well. I've used the full alphabet soup of AWS services: VPC, EC2, S3, ACM, KMS, IAM, RDS, Route53, SNS, SES, SQS, WAF, and many more. I also am familiar with the various monitoring, alerting, and on-call platforms, most notably CloudWatch, DataDog, and Pager Duty. I also have management and project management experience, leading teams and projects at the application and architectural levels.

I do not, unfortunately, have experience with K8s or EKS, so any potential position would need to accept a ramp-up time if those are part of the infrastructure ecosystem. I am a fast learner, and I have a solid engineering expertise to build off of.

My primary need is a fully #remote position for family reasons. As my profile states, I am based in the Twin Cities area in US Central time. I am fully authorized to work in the US without employer support.

I'm happy to answer any other questions folks may have, and I can provide my resume upon request. Thanks in advance for boosts and such!

Just released my very first #Terraform provider: https://registry.terraform.io/providers/svalabs/uyuni

It can be used to manage #Uyuni or #SUSE Manager. Currently it only supports creating users, but additional features will follow in the feature. The provider might also be available for #OpenTofu soon, too: https://github.com/opentofu/registry/issues/1481

It took me two days from never haven written Golang to a working provider MVP.

I'll share my learnings in the #CfgMgmtCamp 2025 talk: https://cfp.cfgmgmtcamp.org/ghent2025/talk/N8GY3W/

Checking out Homepage as a #selfhosted landing page. Looks excellent so far! Seems to work well with the small stack I’ve given it so far, and it allows me to define everything in dynamic yaml from my #opentofu infrastructure: https://github.com/perry-mitchell/homelab-infra/blob/main/applications/k3s/app_homepage.tf

https://github.com/gethomepage/homepage

this morning in #hachyderm infrastructure, we're renaming our tailnet so it isn't a name made up of random characters! this *miiiight* break things temporarily.

also, one of our recent joiners wrote a set of ADRs and design docs about moving our infrastructure management from #terraform (boo BSL license!) to #opentofu and #atlantis.

to science!

@icedquinn@blob.cat @shortstories@merovingian.club @vriska@lizards.live @frogzone@wizard.casa

Well, I'm having a fine #Thanksgiving I guess. I've got no-one to see and nowhere to go. I'll have some store-bought pumpkin pie later.

I'm working on a #terraform #opentofu build script (abstracted into a gnu make makefile). I intend for this to be the boilerplate code that I use to bootstrap up servers and containers for... anything. Anything I want, in the future. Chatbots, video streaming apps, wordpress educational quiz sites, anything I can dream up.

I should have started on this long time ago. Journey of a thousand miles, eh?

How do you handle your secrets?  #IaC #devops #ansible #terraform #opentofu #vault #openbao #bitwarden #devsecops

Still looking for alternative options to move my #gandi domains somewhere else. Paint point is the `.ch` domain compatibility as it's not often available. Whish to have #terraform / #opentofu support and #privacy over the records information (without extra $$$ for the latter).

People asked me what I thought of #Pulumi and so here it is:

I've spent 3 days trying to get Pulumi up and working. The installation under Nix complains that it's out of date and plugins don't match the main version.

The importer doesn't work at all for me. Either I get an error that it can't find the resource (despite it being correct and working with OpenTofu) or it complains about installation issues.

Pulumi is so much nicer to use in user friendliness and using Python instead of HDL is really nice, but if I can't get the thing to install right, and it can't do basic functions right, I can't rely on it.

IaC tools need to be something you can rely on without question. Pulumi isn't that, at least not right now.

Anybody using #OpenTOFU encrypted state? Any feedback?
What did you start storing in the state that you did not store previously?