Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/nishkarshraj/hashicorp-packer
Learning Infrastructure Build Automation with HashiCorp Packer and automating with GitHub Actions
https://github.com/nishkarshraj/hashicorp-packer
automation aws aws-ec2 devops github-actions hashicorp iaas infrastructure-as-code packer
Last synced: 17 days ago
JSON representation
Learning Infrastructure Build Automation with HashiCorp Packer and automating with GitHub Actions
- Host: GitHub
- URL: https://github.com/nishkarshraj/hashicorp-packer
- Owner: NishkarshRaj
- License: mit
- Created: 2020-05-11T01:41:37.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2023-12-15T05:36:39.000Z (about 1 year ago)
- Last Synced: 2024-11-10T02:15:48.483Z (2 months ago)
- Topics: automation, aws, aws-ec2, devops, github-actions, hashicorp, iaas, infrastructure-as-code, packer
- Language: Dockerfile
- Homepage:
- Size: 1.4 MB
- Stars: 3
- Watchers: 3
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: Readme.md
- License: LICENSE
Awesome Lists containing this project
README
# HashiCorp Packer - Infrastructure Build Tool
## Why use Packer?
Configuration Management and Infrastructure-as-a-Service is trending because of the surge of remote deployments of services and their access over network to the consumers via Cloud or containers techniques.
The biggest problem to infrastructure or pre-baked images is that they are written by development team and thus operations team are not too flexible to make changes to them due to **high learning curve**. Furthermore, it is difficult to **automate** infrastructure using pre-baked images.
* Create identical machine images for multiple platforms from a single source configuration. Packer automates the creation of any type of machine image.
* **Multi-provider portability:** Packer creates identical images which can be deployed on public cloud (AWS,GCP,Azure etc), private cloud (OpenStack etc.) or local desktop machines (Virtual Box, VWWare)
* Fast: Entire infrastructure is configured and provisioned in seconds
## What are the alternatives to Packer?
Configuration Management tools like Chef and Puppet are the alternatives but Packer is becoming more popular because:
1. Easy to learn and use
2. Automate IaaS
3. Compatible with other tools and frameworks like Chef and Puppet
## Key Features of Packer
* **Fast infrastructure deployment** - provision infrastructure and configures its dependencies within seconds.
* **Multi-Provider Portability** - identical images for all platforms
* **Improved Stability** - configure dependency on image creation rather than configuration of infrastructure
* **Greater Testability** - Easy to smoke test one machine and that guarentees it will work everywhere due to high portability.
## Some Use-cases of Packer
* **Continuous Delivery** - Lightweight, Portable, CMD driven. Can be used to create portable image to be configured by Ansible, Chef.
* **Dev-Prod Parity** - Tries to reduce the differences between the various environments in software development lifecycle.
* **Appliance-Demo creation** - Very suitable for alpha and beta testing as user environment can be replicated very easily.
## Installation of Packer in Linux machines
* Install Golang on your machine
```
$ apt install golang-go
```
* Check version of golang for verifying successful installation
```
$ go version
```
* Clone packer in your `GOPATH`
```
$ mkdir -p $(go env GOPATH)/src/github.com/hashicorp && cd $_
$ git clone https://github.com/hashicorp/packer.git
$ cd packer
```
* Extract and install binaries using Make utility
```
$ make dev
```
* Verify successful Packer installation
```
$ packer --version
```
## Direct installation of Packer for Debian based systems
```
$ apt-get upgrade && apt-get update
$ apt install packer
$ packer --version
```
## Launching an AWS EC2 instance using Packer
* Create a json script - `example.json`
```
{
"variables": {
"aws_access_key": "",
"aws_secret_key": ""
},
"builders": [
{
"type": "amazon-ebs",
"access_key": "{{user `aws_access_key`}}",
"secret_key": "{{user `aws_secret_key`}}",
"region": "us-east-1",
"source_ami_filter": {
"filters": {
"virtualization-type": "hvm",
"name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*",
"root-device-type": "ebs"
},
"owners": ["099720109477"],
"most_recent": true
},
"instance_type": "t2.micro",
"ssh_username": "ubuntu",
"ami_name": "packer-example {{timestamp}}"
}
]
}
```
* Validate the Packer Script
```
$ packer validate example.json
```
* Create IAM User and generate tokens to be passed as variables to the script file
```
$ export AWS_ACCESS_KEY_ID=AKIAYNZB56UH67JQO5XJ
$ export AWS_SECRET_ACCESS_KEY=fwQqvr7Fad60aSG/ekKjeNi5nYEC5RXUNEsmUYJl
```
* Build the Packer script
```
$ packer build example.json
```
# Automation HashiCorp Packer using GitHub Actions
* Create a Dockefile in **action-a/** folder to specify Packer installation
* Write the main configuration file of GitHub Actions that executes the above created Dockerfile
* Check for the current installation of Packer in GitHub Actions UI
* Pass the AWS IAM Credentials as encrypted secrets to GitHub workflow
* Modify the Dockerfile to build the packer for AWS example.json file
```
RUN ADD example.json /example.json
RUN packer build example.json
```
**Note:** You might get a build error stating there is no default VPC is the user you have authenticated has no direct VPC attached
* Go to AWS - VPC services and create a default VPC.
* Re-run the GitHub Actions workflow
* The workflow ran successfully and gives the AMI of the provisioned AWS EC2 instance.
* Visit AWS - EC2 services to see the snapshot in execution
