Where do Terraform and OpenTofu go from here?
(2024/05/24)
- Reference: 1716548467
- News link: https://www.theregister.co.uk/2024/05/24/opinion_column_terraform/
- Source link:
Opinion Oracle is dropping Terraform for OpenTofu, and IBM's CEO is talking up open source. What does all this mean for both programs? Here's what I see happening.
The Terraform tale has been… interesting. And, with [1]Oracle quietly dumping Terraform for OpenTofu and [2]IBM CEO Arvind Krishna saying real open source matters for enterprises, it's only going to get more interesting.
First, though, in case you haven't been following this drama, here's a quick summarization of what's going on with the Infrastructure as Code (IaC) programs.
[3]
[4]Terraform , the brainchild of Mitchell Hashimoto, the founder of [5]HashiCorp , was first introduced in July 2014. It was a revolutionary concept. The program provided an open source, cloud-agnostic way to describe and manage cloud infrastructure using a declarative configuration language: [6]HashiCorp Configuration Language (HCL) . Initially, it supported only AWS and DigitalOcean, but its impressive growth took to essentially all the cloud providers.
[7]
[8]
With its open source model, Terraform quickly became both a business and a technical success. Alas, for open source fans, that wasn't good enough for HashiCorp owners. [9]HashiCorp dumped the Mozilla Public License (MPL) for the semi-proprietary Business Source License (BSL) 1.1.
The open source developers and users were not amused. They immediately forked the code from the last MPL-licensed version of Terraform (1.5.6) to create OpenTF. This quickly became [10]OpenTofu to avoid trademark fights.
[11]
OpenTofu, somewhat silly name and all, retained all of Terraform's features and functionalities. It also introduced improvements and enhancements, such as end-to-end encryption, in its first release, [12]OpenTofu 1.7 .
OpenTofu quickly gained traction and support from The Linux Foundation, former HashiCorp customers, and programmers. This rapid growth and endorsement underscored OpenTofu's potential and competitive edge. However, Terraform was not amused and [13]accused OpenTofu of code misappropriation , setting the stage for a legal battle.
Then came a twist to the story. Hashicorp's new management had been hoping for a buyout — indeed, that's why it changed the license — and it got one, a huge one. IBM bought the company out for big bucks — $6.4 billion, to be exact.
[14]
That's the end of the fight. The notion that IBM would pursue OpenTofu in the courts is laughable.
But, what will IBM do next? Will they return Terraform to open source? While Krishna was talking primarily about [15]IBM's Granite Large Language Models (LLM) , he told [16]VentureBeat that the Apache license is a real open source license, unlike the host of faux-pen source licenses, such as BSL, that HashiCorp and other vendors use in place of open source.
Krishna said, "They're using the term open just for marketing purposes. … If you want people to contribute, it has to be clearly open source; it cannot actually just be open-source marketing."
Exactly so! Indeed, HashiCorp abandoned the Apache license for a faux-source license, and their open source developers abandoned the project. So, once IBM has the Terraform reins in its hands, will it return the program to Apache? If we can believe Krishna, it appears they will.
Besides, there's another reason for IBM to make this move. OpenTofu is grabbing former Terraform customers. The big fish that leaped into OpenTofu's boat, which caught my eye, was Oracle.
In an otherwise dull point release, Oracle announced that its Oracle E-Business Suite (EBS) Cloud Manager had "switched from using the Terraform infrastructure as code tool to OpenTofu. Note that this does not impact Cloud Manager functionality."
For those of you who aren't in the high-end IT space, EBS is a major money-maker for Oracle. It's an integrated set of business applications for automating Customer Relationship Management (CRM), Enterprise Resource Planning (ERP), and Supply Chain Management (SCM). According to 6Sense, a business-to-business marketing and analyst company, [17]EBS has 43.95 percent of the ERP market, coming in second to SAP Ariba Sourcing.
In other words, Oracle is betting serious coin that OpenTofu is already a drop-in-place replacement for Terraform. Oracle CEO Larry Ellison wouldn't be doing this if he wasn't sure OpenTofu was prime-time ready.
[18]Did IBM make a $6.4B blunder by buying HashiCorp?
[19]Linux Foundation is leading fight against fauxpen source
[20]How HashiCorp's license shakeup seeded a new open source rebel
[21]Redis tightens its license terms, pleasing basically no one
So, as I see it, if [22]IBM wants to make sure it gets its money's worth out of HashiCorp, it must re-open source Terraform and make peace with OpenTofu.
And it just so happens that this would be fine with the OpenTofu crew. As OpenTofu co-maintainer Sebastian Stadil recently told [23]TheNewStack , "OpenTofu is absolutely open to 'remerging' (unforking?) with a sufficiently open sourced Terraform, and always has been. Nobody likes split communities. Nobody likes fragmentation of efforts. So we would welcome Terraform."
With any luck, after the IBM-Hashicorp deal is completed at year's end, I hope to see the two projects rejoin together. Everyone will be better for it. ®
Get our [24]Tech Resources
[1] https://blogs.oracle.com/ebsandoraclecloud/post/ebs-cloud-manager-24111-now-available
[2] https://venturebeat.com/ai/ibm-ceo-praises-real-open-source-for-enterprise-gen-ai-as-new-efforts-emerge-at-think-2024/
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZlC5qvRDlZcGfHvZCotS7QAAAA4&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://www.terraform.io/
[5] https://www.hashicorp.com/
[6] https://github.com/hashicorp/hcl
[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZlC5qvRDlZcGfHvZCotS7QAAAA4&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZlC5qvRDlZcGfHvZCotS7QAAAA4&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[9] https://www.theregister.com/2023/08/11/hashicorp_bsl_licence/
[10] https://opentofu.org/
[11] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZlC5qvRDlZcGfHvZCotS7QAAAA4&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[12] https://opentofu.org/blog/opentofu-1-7-0/
[13] https://devops.com/hashicorp-versus-opentofu-gets-ugly/
[14] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZlC5qvRDlZcGfHvZCotS7QAAAA4&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[15] https://www.zdnet.com/article/ibm-open-sources-its-granite-ai-models-and-they-mean-business/
[16] https://venturebeat.com/
[17] https://6sense.com/tech/enterprise-resource-planning-(erp)/oracle-ebs-market-share
[18] https://www.theregister.com/2024/05/10/opinion_column_ibm_hashicorp/
[19] https://www.theregister.com/2024/04/12/linux_foundation_opinion/
[20] https://www.theregister.com/2024/04/04/opentofu_on_forking_terraform/
[21] https://www.theregister.com/2024/03/22/redis_changes_license/
[22] https://www.theregister.com/2024/05/10/opinion_column_ibm_hashicorp/
[23] https://thenewstack.io/opentofu-amiable-to-a-terraform-reconciliation/
[24] https://whitepapers.theregister.com/
The Terraform tale has been… interesting. And, with [1]Oracle quietly dumping Terraform for OpenTofu and [2]IBM CEO Arvind Krishna saying real open source matters for enterprises, it's only going to get more interesting.
First, though, in case you haven't been following this drama, here's a quick summarization of what's going on with the Infrastructure as Code (IaC) programs.
[3]
[4]Terraform , the brainchild of Mitchell Hashimoto, the founder of [5]HashiCorp , was first introduced in July 2014. It was a revolutionary concept. The program provided an open source, cloud-agnostic way to describe and manage cloud infrastructure using a declarative configuration language: [6]HashiCorp Configuration Language (HCL) . Initially, it supported only AWS and DigitalOcean, but its impressive growth took to essentially all the cloud providers.
[7]
[8]
With its open source model, Terraform quickly became both a business and a technical success. Alas, for open source fans, that wasn't good enough for HashiCorp owners. [9]HashiCorp dumped the Mozilla Public License (MPL) for the semi-proprietary Business Source License (BSL) 1.1.
The open source developers and users were not amused. They immediately forked the code from the last MPL-licensed version of Terraform (1.5.6) to create OpenTF. This quickly became [10]OpenTofu to avoid trademark fights.
[11]
OpenTofu, somewhat silly name and all, retained all of Terraform's features and functionalities. It also introduced improvements and enhancements, such as end-to-end encryption, in its first release, [12]OpenTofu 1.7 .
OpenTofu quickly gained traction and support from The Linux Foundation, former HashiCorp customers, and programmers. This rapid growth and endorsement underscored OpenTofu's potential and competitive edge. However, Terraform was not amused and [13]accused OpenTofu of code misappropriation , setting the stage for a legal battle.
Then came a twist to the story. Hashicorp's new management had been hoping for a buyout — indeed, that's why it changed the license — and it got one, a huge one. IBM bought the company out for big bucks — $6.4 billion, to be exact.
[14]
That's the end of the fight. The notion that IBM would pursue OpenTofu in the courts is laughable.
But, what will IBM do next? Will they return Terraform to open source? While Krishna was talking primarily about [15]IBM's Granite Large Language Models (LLM) , he told [16]VentureBeat that the Apache license is a real open source license, unlike the host of faux-pen source licenses, such as BSL, that HashiCorp and other vendors use in place of open source.
Krishna said, "They're using the term open just for marketing purposes. … If you want people to contribute, it has to be clearly open source; it cannot actually just be open-source marketing."
Exactly so! Indeed, HashiCorp abandoned the Apache license for a faux-source license, and their open source developers abandoned the project. So, once IBM has the Terraform reins in its hands, will it return the program to Apache? If we can believe Krishna, it appears they will.
Besides, there's another reason for IBM to make this move. OpenTofu is grabbing former Terraform customers. The big fish that leaped into OpenTofu's boat, which caught my eye, was Oracle.
In an otherwise dull point release, Oracle announced that its Oracle E-Business Suite (EBS) Cloud Manager had "switched from using the Terraform infrastructure as code tool to OpenTofu. Note that this does not impact Cloud Manager functionality."
For those of you who aren't in the high-end IT space, EBS is a major money-maker for Oracle. It's an integrated set of business applications for automating Customer Relationship Management (CRM), Enterprise Resource Planning (ERP), and Supply Chain Management (SCM). According to 6Sense, a business-to-business marketing and analyst company, [17]EBS has 43.95 percent of the ERP market, coming in second to SAP Ariba Sourcing.
In other words, Oracle is betting serious coin that OpenTofu is already a drop-in-place replacement for Terraform. Oracle CEO Larry Ellison wouldn't be doing this if he wasn't sure OpenTofu was prime-time ready.
[18]Did IBM make a $6.4B blunder by buying HashiCorp?
[19]Linux Foundation is leading fight against fauxpen source
[20]How HashiCorp's license shakeup seeded a new open source rebel
[21]Redis tightens its license terms, pleasing basically no one
So, as I see it, if [22]IBM wants to make sure it gets its money's worth out of HashiCorp, it must re-open source Terraform and make peace with OpenTofu.
And it just so happens that this would be fine with the OpenTofu crew. As OpenTofu co-maintainer Sebastian Stadil recently told [23]TheNewStack , "OpenTofu is absolutely open to 'remerging' (unforking?) with a sufficiently open sourced Terraform, and always has been. Nobody likes split communities. Nobody likes fragmentation of efforts. So we would welcome Terraform."
With any luck, after the IBM-Hashicorp deal is completed at year's end, I hope to see the two projects rejoin together. Everyone will be better for it. ®
Get our [24]Tech Resources
[1] https://blogs.oracle.com/ebsandoraclecloud/post/ebs-cloud-manager-24111-now-available
[2] https://venturebeat.com/ai/ibm-ceo-praises-real-open-source-for-enterprise-gen-ai-as-new-efforts-emerge-at-think-2024/
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZlC5qvRDlZcGfHvZCotS7QAAAA4&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://www.terraform.io/
[5] https://www.hashicorp.com/
[6] https://github.com/hashicorp/hcl
[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZlC5qvRDlZcGfHvZCotS7QAAAA4&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZlC5qvRDlZcGfHvZCotS7QAAAA4&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[9] https://www.theregister.com/2023/08/11/hashicorp_bsl_licence/
[10] https://opentofu.org/
[11] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZlC5qvRDlZcGfHvZCotS7QAAAA4&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[12] https://opentofu.org/blog/opentofu-1-7-0/
[13] https://devops.com/hashicorp-versus-opentofu-gets-ugly/
[14] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZlC5qvRDlZcGfHvZCotS7QAAAA4&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[15] https://www.zdnet.com/article/ibm-open-sources-its-granite-ai-models-and-they-mean-business/
[16] https://venturebeat.com/
[17] https://6sense.com/tech/enterprise-resource-planning-(erp)/oracle-ebs-market-share
[18] https://www.theregister.com/2024/05/10/opinion_column_ibm_hashicorp/
[19] https://www.theregister.com/2024/04/12/linux_foundation_opinion/
[20] https://www.theregister.com/2024/04/04/opentofu_on_forking_terraform/
[21] https://www.theregister.com/2024/03/22/redis_changes_license/
[22] https://www.theregister.com/2024/05/10/opinion_column_ibm_hashicorp/
[23] https://thenewstack.io/opentofu-amiable-to-a-terraform-reconciliation/
[24] https://whitepapers.theregister.com/
For what it's worth...
beardman
Terraform has _never_ been cloud agnostic. You should still know which cloud and which resource you're writing Terraform/OpenTofu code for.
Re: For what it's worth...
Michael Hoffmann
Amen! The arguments I've had on that topic.... good gods.
Funnily enough, you can use Pulumi with its lowest-common-denominator CrossCode and have that be truly agnostic - but you only get a fairly small set of cloud resources. Then use the version that produces Terraform. About the closest you'll get.
Re: For what it's worth...
notiggy
It is cloud agnostic in the sense that you can use one tool (and perhaps more importantly one language) to control more than one cloud service.
It isn't agnostic in the sense that you can write one resource block that will do something on more than one cloud. I'm fairly certain that wouldn't even be a good idea. You'd either have so much bloat for each resource (to cover each cloud's differences) or you'd have a seriously limited tool by design (to only capture each cloud's similarities).
I've seen shops write modules that created resources in different clouds. It worked but they weren't pretty.
We shall see.
nematoad
Everyone will be better for it.
Yes, I suppose they might, but those best off will be the people who cashed in on the Terraform sale.
We will have to see, but IBM?
I'm not sure that I would describe them as a safe pair of hands.
Look at what they have done with CentOS.
Re: We shall see.
Michael Hoffmann
Indeed. So, OpenTofu would be to CentOS as Terraform is to RHEL.
And when they feel like it, they pull out the rug.
here's a quick summarization ...
Anonymous Coward
Is that related to
here's a quick summary ...
IBM Death Spiral.....
I'm aware of smaller shops migrating this way after the IBM takeover, but nobody would notice.
This is a big name, and somebody at IBM should notice. If they don't, they could well be see the market move rapidly!