Public example deployment of Netpalm
- Packer and Terraform both expect an AWS CLI Profile named
netpalm-public - Packer and Terraform both expect the AWS Account to be
100784628684in order to find the AMIs in subsequent steps.
PS C:\projects\netpalm-public\packer\ansible-base> packer version
Packer v1.6.5
PS C:\projects\netpalm-public\packer\ansible-base> tf13 version
Terraform v0.13.5
- Packer & Ansible
- Packer builds a base AMI that includes ansible. Ansible is required for future steps and takes forever to install.
-
packer build template.json```
-
- Packer builds actual actual AMI that will be used to run Netpalm. This includes ansible roles to install Docker, etc.
-
packer build template.json``` - Any special user config has to happen here
- Also this is where we mandate
-
- Packer builds a base AMI that includes ansible. Ansible is required for future steps and takes forever to install.
- Terraform
- Terraform creates an instance based on the AMI from step 1.2, also creates and configures any necessary:
- Security Groups
- Subnets
- VPCs
- etc.
- Terraform creates an instance based on the AMI from step 1.2, also creates and configures any necessary:
- Fix formatting on this, probaly
- get tbot &
wgkeys added to 'accepted keys' for the default user actually deploy netpalmsecure the netpalm deployment(only permits API DOCS access for now)make netpalm reachable by editing security group