Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/stromweld/chef_automate_ha
Development repository for the automate_ha Chef Cookbook
https://github.com/stromweld/chef_automate_ha
chef chef-cookbook chef-resource managed-by-terraform
Last synced: 9 days ago
JSON representation
Development repository for the automate_ha Chef Cookbook
- Host: GitHub
- URL: https://github.com/stromweld/chef_automate_ha
- Owner: Stromweld
- License: apache-2.0
- Created: 2022-11-28T17:21:19.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2023-10-26T20:19:21.000Z (about 1 year ago)
- Last Synced: 2024-10-11T16:01:14.724Z (2 months ago)
- Topics: chef, chef-cookbook, chef-resource, managed-by-terraform
- Language: Ruby
- Homepage:
- Size: 28.3 KB
- Stars: 0
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# automate_ha
This Cookbook will install and configure Chef Automate HA Feature on all your on-prem nodes
Use of this cookbook for installing Chef Automate means you agree to the license terms found at
## Requirements
- Please see for server hardware requirements
- Latest chef-workstation installed
- For test-kitchen testing locally you'll need about 48GB of local ram for the VM's themselves
- When using test-kitchen run the `start_kitchen_test.sh` in a bash window to automate the creation of the machines, gathering of the IP's, and writing out kitchen_nodes.json with the IP's for the config.toml file generation
- For test-kitchen to run in AWS use `saml2aws login` and `export KITCHEN_LOCAL_YAML="kitchen.ec2.yml"` before the `start_kitchen_test.sh` script
- kitchen.ec2.yml is configured to use a subnet and security group pre-built in us-west-2 for aws account 'chef-success-aws'
### Platforms
- Linux
## Attributes
### default attributes
| Attribute | Default | Type | Comment |
|---------------------------------------------------|-----------------------------|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| \['automate_ha']\['accept_license'] | true | Boolean | Consents to the license agreement at |
| \['automate_ha']\['version'] | 'latest' | String | Version of Automate to install. HA requires version 4.3.x or newer |
| \['automate_ha']\['username'] | 'chef' | String | Username for SSH access to nodes in cluster |
| \['automate_ha']\['ssh_key'] | See attribute file | String | SSH private key used for access to nodes, this should be replaced by one preferably from a secrets manager, this one is ok for testing with test-kitchen locally |
| \['automate_ha']\['ssh_authorize_key'] | See attribute file | String | SSH public key added to the user's authorized_keys file for ssh key based access to nodes |
| \['automate_ha']\['dns_configured'] | false | boolean | Specifies if /etc/hosts needs to be modified if automate and chef dns entries aren't configured and resolvable locally |
| \['automate_ha']\['automate_dns_entry'] | 'chef-automate.example.com' | String | Url used to resolve connection to the automate frontends |
| \['automate_ha']\['infra-server_dns_entry'] | 'chef-server.example.com' | String | Url used to resolve connection to the chef infra server frontends |
| \['automate_ha']\['instance_ips'] | See attribute file | Hash | Key value pairs defining all IP's of nodes in the cluster |
| \['automate_ha']\['initial_config_toml_template'] | See attribute file | Hash | Hash of values used to generate the config.toml file for initial deployment of Automate HA across all nodes in the cluster, not to be used for patch config changes |
| \['automate_ha']\['patch_config_toml_template'] | nil | Hash | Hash of values used to generate a patch_config.toml file for modifying cluster configuration after initial deployment |
## Recipes
### default recipe
Used on all nodes to:
- Create the user for ssh access
- Add ssh public key to users authorized_keys file for ssh access
- Ensures user has full sudo access without password
- Add /etc/hosts file entries for automate and infra server urls if DNS is not configured
- Sets SElinux policy to permissive
### bastion
Should only run on the bastion host to:
- Create ssh private key in chef cache directory for ssh access to all nodes
- Download, extract and link the chef-automate binary to the OS default bin folder
- Downloads the automate.aib file for deployment in the chef cache directory
- Sets sysctl settings needed for automate deployment
- Generates config.toml file in chef cache directory for initial deployment
- Executes command for inital Automate HA deployment for all servers
## Usage
1. Set attributes and runlist via wrapper cookbook, policy files, role or environment files.
1. Build cluster servers with runlist `automate_ha::default`
1. Build bastion server with runlist `["automate_ha::default", "automate_ha::bastion"]`
## Test-kitchen Usage
1. In terminal run script `start_kitchen_test.sh`
1. To use a different platform found in the kitchen.yml file add the platform as parameter `start_kitchen_test.sh centos-7`
1. To specify alternate virtualization platform for vagrant like parallels set environment variable `VAGRANT_DEFAULT_PROVIDER` to the name of the provider desired
1. To use another kitchen file setup set `KITCHEN_LOCAL_YAML` to point to another kitchen file that overrides values in the default kitchen.yml file
1. After all servers are up and converged run normal `kitchen` commands as needed