OpenTofu becomes the real deal
-
I felt completely lost. What is Terraform?
Terraform is a tool that codifies cloud APIs into declarative configuration files to automate infrastructure provisioning and management
Not exactly sure what that means, but that may help someone!
It's useful for configuring a turbo encabulator.
-
I felt completely lost. What is Terraform?
Terraform is a tool that codifies cloud APIs into declarative configuration files to automate infrastructure provisioning and management
Not exactly sure what that means, but that may help someone!
Imagine a tool that gives you a language in which you can describe the hardware resources you want from a cloud provider. Say you want multiple different classes of servers with different sets of firewall rules. Something like Terraform allows you to put that into a text-based form, make changes to it, re-run the tool and expect resources to be created, changed and destroyed to match what you wrote down.
-
I felt completely lost. What is Terraform?
Terraform is a tool that codifies cloud APIs into declarative configuration files to automate infrastructure provisioning and management
Not exactly sure what that means, but that may help someone!
It's just a way of defining configurations
-
I felt completely lost. What is Terraform?
Terraform is a tool that codifies cloud APIs into declarative configuration files to automate infrastructure provisioning and management
Not exactly sure what that means, but that may help someone!
Its for easily deploying virtual machines. You can specify the VM specs, give it an install disk and some instructions, and it will churn out a VM for you.
Honestly, it's not great in my experience, nothing about it is common or portable, so if you change your VM host, it might all fall apart.
-
I felt completely lost. What is Terraform?
Terraform is a tool that codifies cloud APIs into declarative configuration files to automate infrastructure provisioning and management
Not exactly sure what that means, but that may help someone!
Infrastructure configuration that is automatically applied to the cloud infrastructure. Like starting and stopping new instances and services, changing connections between them, etc. (I assume anyway.)
-
Based on the name I thought this was gonna be some platform to make homemade tofu more accessible to people and I was thinking “it’s really not all that hard to make, that’s kind of silly”
going after big nasoya
-
OpenTofu’s Slack workspace
Bro... why do opensource projects love proprietary collaboration platforms so much?
-
Its for easily deploying virtual machines. You can specify the VM specs, give it an install disk and some instructions, and it will churn out a VM for you.
Honestly, it's not great in my experience, nothing about it is common or portable, so if you change your VM host, it might all fall apart.
-
OpenTofu’s Slack workspace
Bro... why do opensource projects love proprietary collaboration platforms so much?
-
OpenTofu’s Slack workspace
Bro... why do opensource projects love proprietary collaboration platforms so much?
Plus, I don't find slack super competitive in terms of features & usability.
I remember having a much better experience with mattermost.
-
I don’t get it. Why go through the trouble and stay in a license that still allows Hashicorp / IBM to benefit from community contributions?
-
It's just a way of defining configurations
Like an .ini file.
-
Based on the name I thought this was gonna be some platform to make homemade tofu more accessible to people and I was thinking “it’s really not all that hard to make, that’s kind of silly”
going after big nasoya
It’s traditional in open source to have really terrible names.
-
Its for easily deploying virtual machines. You can specify the VM specs, give it an install disk and some instructions, and it will churn out a VM for you.
Honestly, it's not great in my experience, nothing about it is common or portable, so if you change your VM host, it might all fall apart.
nothing about it is common or portable, so if you change your VM host, it might all fall apart.
Disclaimer, I'm pretty much elbow deep into terraform daily and have written/contributed to a few providers.
A lot of this is highly dependent upon the providers (the thing that allows the Terraform engine to interface with APIs for AWS, Proxmox, vSphere, etc. The Telmate Proxmox provider in particular is/was quite awful with not realizing a provisioned VM had moved to a new host.
Also, the default/tutorial code tends to be not very flexible. The game changer for me was using the built-in functions for decoding yaml from a config file (like
yamldecode(file(config.yml))in a locals block. You can then specify your desired infrastructure with yaml and (if you write your Terraform code correctly) you can blowout hundreds of VMs, policies, firewall rules, dns records etc with a single manifest. I've also used thelocal_fileresource with a Terraform file template to dynamically create an Ansible inventory file based on what's deployed. -
I don’t get it. Why go through the trouble and stay in a license that still allows Hashicorp / IBM to benefit from community contributions?
stay in a license that still allows Hashicorp / IBM to benefit from community contributions?
I don't see how this is the case. As Hashicorp explains, they switched from the open-source Mozilla Public License 2.0 (MPL) to the proprietary Business Source License (BSL) in order to apply restrictions upon users of Terraform:
Organizations providing competitive offerings to HashiCorp will no longer be permitted to use the community edition products free of charge under our BSL license.
The terms of the MPL and BSL are incompatible, insofar that Hashicorp cannot unilaterally relicense MPL code from OpenTofu into BSL code in Terraform. But Hashicorp could still use/incorporate OpenTofu MPL code into Terraform, provided that they honor the rest of the obligations of the MPL.
This is exactly the same situation as what Hashicorp was obliged to do before the licensing kerfuffle, so it cuts against Hashicorp's objective: why continue developing legacy Terraform if OpenTofu is going to provide continuity? Perhaps they only intend to develop new, exclusive features that build upon the common legacy code, but users would now retain an option to reject those pricy add-ons and just stick with the free, open-source functionality from OpenTofu.
It seems to me less about giving the finger to Hashicorp and more about giving users a choice in the matter. Without OpenTofu, the userbase are forced into the BSL terms of Terraform, where Hashicorp could unilaterally prohibit any production use by yet another license change. That's no way to live or work, with such a threat hanging overhead. OpenTofu lifts that threat by providing competition, and so maybe does kinda throw the finger at Hashicorp anyway.
-
OpenTofu’s Slack workspace
Bro... why do opensource projects love proprietary collaboration platforms so much?
OpenTofu is mostly getting users from the corporate world. My work is on Slack and we're moving to OT. The lowest-friction for me as an OT-when-at-work user is to add another Slack. (I'd personally rather that they used an open platform. But it's easy for me to see why they didn't.)
-
OpenTofu is mostly getting users from the corporate world. My work is on Slack and we're moving to OT. The lowest-friction for me as an OT-when-at-work user is to add another Slack. (I'd personally rather that they used an open platform. But it's easy for me to see why they didn't.)
What is a good open platform for the tech business? My corp want to go full Teams, which sucks even more than Slack. At least most tooling has a Slack integration of some sort.
-
What is a good open platform for the tech business? My corp want to go full Teams, which sucks even more than Slack. At least most tooling has a Slack integration of some sort.
Is https://huly.io/ any good?
https://elest.io/open-source/huly offers managed-hosting, but their "if you want REAL support, that is $50/mo extra subscription" thing is something to consider..
There's got to be something that they're offering, there ( I'm probably going to be using hosted-Lemmy for my publishing-platform, soon, so these questions are oblique to mine )
_ /\ _
-
I don't know. I might say "Matrix" and run a private server? But that's a bunch of IT work. It's attractive to use a SaaS because you don't have to do any long-term planning or hiring; just pay Slack a crazy amount of money and it all works.
Corps also like a commercial paid service because they get a contract with an SLA (even if it's rare to actually get anything from these SLAs).
