One For All: Using Terraform to manage OpenStack and Kubernetes resources

Posted on Tue 07 May 2019 in talk-submissions • 2 min read

This is a workshop I proposed1 for OpenInfra Days Nordics, via a non-anonymized CfP process using PaperCall.

Title

One For All: Using Terraform to manage OpenStack and Kubernetes resources

Elevator Pitch

You have 300 characters to sell your talk. This is known as the “elevator pitch”. Make it as exciting and enticing as possible.

A hands-on introduction to Terraform in an OpenStack and Kubernetes context. Get the basics (of Terraform), then spin up a Kubernetes cluster in an OpenStack public cloud (with Terraform), and manage resources on it (with Terraform).

Talk Format

Workshop (>60 minutes)

Audience Level

Intermediate

Description

This field supports Markdown. The description will be seen by reviewers during the CFP process and may eventually be seen by the attendees of the event.

You should make the description of your talk as compelling and exciting as possible. Remember, you’re selling both the organizers of the events to select your talk, as well as trying to convince attendees your talk is the one they should see.

If you are interested in deployment automation for arbitrarily complex containerized microservice applications, this is for you!

In this workshop, you will

You’ll walk away with a solid understanding of Terraform’s capabilities, enabling you to make an informed decision of whether Terraform is a suitable deployment automation facility for your organization’s needs.

Prior Terraform knowledge is not required.

Notes

This field supports Markdown. Notes will only be seen by reviewers during the CFP process. This is where you should explain things such as technical requirements, why you’re the best person to speak on this subject, etc…

There are no technical requirements other than internet connectivity, and a web browser (preferably on a laptop, though a reasonably-sized tablet with a modern browser should work as well).

Tags

Tag your talk to make it easier for event organizers to be able to find. Examples are “ruby, javascript, rails”.

Terraform, OpenStack, Kubernetes, Magnum


  1. If you’re curious why this is here, please read this