Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Background

  • “The idea behind infrastructure as code (IAC) is that we write and execute code to define, deploy, and update our infrastructure. This represents an important shift in mindset where we treat all aspects of operations as software—even those aspects that represent hardware (e.g., setting up physical servers). In fact, a key insight of DevOps is that we can manage almost everything in code, including servers, databases, networks, log files, application configuration, documentation, automated tests, deployment processes, and so on.”

Project Structure and Organization

Possible Sub-pages/topics:

  • Directory Structure

  • Naming Conventions

  • Repository Layout

Infrastructure Provisioning

Possible Sub-pages/topics:

  • Explanation of IaC Language (Terraform and Ansible terminologies)

  • Creating Infrastructure Resources

  • Resource Dependencies and Order(?)

Configuration Management

Possible Sub-pages/topics:

  • Managing Configuration Files

  • Secrets Management

  • Parameterization and Variables

Setting Up IaC Environment

Possible Sub-pages/topics:

  • Pre-requisite Requirements

  • Installation and Configuration

  • Environment Variables

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.