Bureaucrats, cc_docs_admin, cc_staff
2,879
edits
Terraform: Difference between revisions
Jump to navigation
Jump to search
Remove top-level section. Relocate source citation
m (Rdickson moved page Using Terraform to Terraform) |
(Remove top-level section. Relocate source citation) |
||
| Line 1: | Line 1: | ||
{{draft}} | {{draft}} | ||
Terraform is seeing growing use within the Compute Canada Federation. Its infrastructure-as-code allows its users to maintain OpenStack resources as a collection of definitions which can be easily updated using favourite text editors, shared among members of a group, and stored in version control. | Terraform is seeing growing use within the Compute Canada Federation. Its infrastructure-as-code allows its users to maintain OpenStack resources as a collection of definitions which can be easily updated using favourite text editors, shared among members of a group, and stored in version control. | ||
| Line 680: | Line 676: | ||
# Use the name for the first Terraform run, and then get the ID from the output or state file, and finally, switch your configuration to use the ID instead. This should not attempt to recreate the VM, but check before you agree to <code>terraform apply</code>. | # Use the name for the first Terraform run, and then get the ID from the output or state file, and finally, switch your configuration to use the ID instead. This should not attempt to recreate the VM, but check before you agree to <code>terraform apply</code>. | ||
# Switch to using the OpenStack CLI. (Recommended.) | # Switch to using the OpenStack CLI. (Recommended.) | ||
== Notes == | |||
This material is adapted from a posting which appeared on [https://acme.c3.ca the ACME group blog] (login required). The original is [https://acme.c3.ca/blog/getting-started-with-terraform/ here]. | |||