- Update on the Touchpoint workaround
- Linkdump Week 44 / 2020
- Linkdump Week 42 / 2020
- Linkdump Week 41 / 2020
- Elasticsearch index creation problem
- Linkdump Week 40 / 2020
- Selfhost Shaarli
- Touchpoint in HCL Connections 6.5CR1
- Some updates (some delayed) on Engage 2020, Connections, my job and documentation as code
- Asciidoctor open links in new window
In the first two parts of this little devops series, I showed build templates with Packer and deploying virtual-machines with Terraform. Now we want to install some more packages on our new servers. tl;dr I started using Ansible for deployments some years ago. For example I showed deploying IBM Connections at Social Connections 12 in Vienna. For more details on the functionality, have a look at the post How Ansible Works Ansible uses plain ssh and doesn’t need any additional server or client component. You can run Ansible as a separate task in your deployment pipeline, or add it as post-provisioning task to Terraform.
My last article showed how to build a server template with Packer. Now we want to use this template to create some servers on VMware vSphere. DNS will be registered manually and all IP addresses will be defined as fixed in the config files. This code is tested with Terraform 0.12. tl;dr Terraform provides a good way to implement immutable server life cycle. Immutable means that servers aren’t changed, they get destroyed/deleted and created again when you change something. Immutable servers have a big advantage that configuration drift will not take place.