All Projects → Artemmkin → Infrastructure As Code Tutorial

Artemmkin / Infrastructure As Code Tutorial

Licence: apache-2.0
Infrastructure As Code Tutorial. Covers Packer, Terraform, Ansible, Vagrant, Docker, Docker Compose, Kubernetes

Projects that are alternatives of or similar to Infrastructure As Code Tutorial

Tads Boilerplate
Terraform + Ansible + Docker Swarm boilerplate = DevOps on 🔥🔥🔥 | Infrastructure as Code
Stars: ✭ 424 (-78.3%)
Mutual labels:  ansible, terraform, infrastructure-as-code, vagrant
Detectionlab
Automate the creation of a lab environment complete with security tooling and logging best practices
Stars: ✭ 3,237 (+65.66%)
Mutual labels:  ansible, terraform, packer, vagrant
Ansible Windows Docker Springboot
Example project showing how to provision, deploy, run & orchestrate Spring Boot apps with Docker Windows Containers on Docker Windows native using Packer, Powershell, Vagrant & Ansible
Stars: ✭ 58 (-97.03%)
Mutual labels:  ansible, packer, docker-compose, vagrant
Packer Windoze
Packer templates to create Windows vagrant box images
Stars: ✭ 117 (-94.01%)
Mutual labels:  ansible, packer, vagrant
Toc
A Table of Contents of all Gruntwork Code
Stars: ✭ 111 (-94.32%)
Mutual labels:  terraform, infrastructure-as-code, packer
Cloud Portal
Self service web portal for different Cloud platforms like Azure, AWS and VMWare vSphere.
Stars: ✭ 60 (-96.93%)
Mutual labels:  ansible, terraform, docker-compose
Packer Centos 7
This build has been moved - see README.md
Stars: ✭ 223 (-88.59%)
Mutual labels:  ansible, packer, vagrant
Hybrid multicloud overlay
MutiCloud_Overlay demonstrates a use case of overlay over one or more clouds such as AWS, Azure, GCP, OCI, Alibaba and a vSphere private infrastructure in Hub and spoke topology, point to point topology and in a Single cloud. Overlay protocols IPv6 and IPv4 are independent of underlying infrastructure. This solution can be integrated with encryption and additional security features.
Stars: ✭ 127 (-93.5%)
Mutual labels:  ansible, terraform, packer
Rubel
Rubel is a cms built with Laravel and React.
Stars: ✭ 70 (-96.42%)
Mutual labels:  ansible, docker-compose, vagrant
Packer Ubuntu 1404
DEPRECATED - Packer Example - Ubuntu 14.04 Vagrant Box using Ansible provisioner
Stars: ✭ 81 (-95.85%)
Mutual labels:  ansible, packer, vagrant
My Cheat Sheets
A place to keep all my cheat sheets for the complete development of ASIC/FPGA hardware or a software app/service.
Stars: ✭ 94 (-95.19%)
Mutual labels:  terraform, packer, vagrant
Packer Boxes
Jeff Geerling's Packer build configurations for Vagrant boxes.
Stars: ✭ 495 (-74.67%)
Mutual labels:  ansible, packer, vagrant
Learning Tools
A collection of tools and files for learning new technologies
Stars: ✭ 1,287 (-34.14%)
Mutual labels:  ansible, terraform, vagrant
Beetbox
Pre-provisioned L*MP stack
Stars: ✭ 94 (-95.19%)
Mutual labels:  ansible, packer, vagrant
Multi Env Deploy
Complete example of deploying complex web apps to AWS using Terraform, Ansible, and Packer
Stars: ✭ 132 (-93.24%)
Mutual labels:  ansible, terraform, packer
Packer Centos 6
This build has been moved - see README.md
Stars: ✭ 78 (-96.01%)
Mutual labels:  ansible, packer, vagrant
Terrible
An Ansible playbook that apply the principle of the Infrastructure as Code on a QEMU/KVM environment.
Stars: ✭ 161 (-91.76%)
Mutual labels:  ansible, terraform, infrastructure-as-code
Packer Templates
Scripts and Templates used for generating Vagrant images
Stars: ✭ 219 (-88.79%)
Mutual labels:  ansible, packer, vagrant
Kubernetes The Ansible Way
Bootstrap Kubernetes the Ansible way on Everything (here: Vagrant). Inspired by Kelsey Hightower´s kubernetes-the-hard-way, but refactored to Infrastructure-as-Code.
Stars: ✭ 82 (-95.8%)
Mutual labels:  ansible, infrastructure-as-code, vagrant
Packer Ubuntu 1804
This build has been moved - see README.md
Stars: ✭ 101 (-94.83%)
Mutual labels:  ansible, packer, vagrant

Infrastructure As Code Tutorial

license Tweet

This tutorial is intended to show what the Infrastructure as Code (IaC) is, why we need it, and how it can help you manage your infrastructure more efficiently.

It is practice-based, meaning I don't give much theory on what Infrastructure as Code is in the beginning of the tutorial, but instead let you feel it through the practice first. At the end of the tutorial, I summarize some of the key points about Infrastructure as Code based on what you learn through the labs.

This tutorial is not meant to give a complete guide on how to use a specific tool like Ansible or Terraform, instead it focuses on how these tools work in general and what problems they solve.

The tutorial was inspired by Kubernetes the Hard Way tutorial. I used it as an example to structure this one.

See my presentation at DevOpsDays Silicon Valley in which I talk more in depth about the tutorial.

Need your help!

This tutorial was created in 2018 and wasn't being kept up to date. Therefore, some of the instructions may not work due to updated APIs, obsolete repositories, etc. I apologize for that, but I currently don't have time to update this tutorial. So if you find that something is broken and you find a fix, please submit a PR.

When submitting a PR, make sure you include a description for it, i.e. what's broken and a test plan for the fix.

Also, note that some of things need to be updated in several different repositories at the same time. Main repositories used in this tutorial:

Target Audience

The target audience for this tutorial is anyone who loves or/and works in IT.

Tools Covered

  • Packer
  • Terraform
  • Ansible
  • Vagrant
  • Docker
  • Docker Compose
  • Kubernetes

Results of completing the tutorial

By the end of this tutorial, you'll make your own repository looking like this one.

NOTE: you can use this example repository in case you get stuck in some of the labs.

Labs

This tutorial assumes you have access to the Google Cloud Platform. While GCP is used for basic infrastructure requirements the lessons learned in this tutorial can be applied to other platforms.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].