just-a-bunch-of-nodes config whilst originally intended for the deployment of instances, is perhaps better described as "N un-configured RHEL machines all exposed to the internet".
It is worth noting, despite its name, that no application is actually deployed.
It makes an ideal base infrastructure to build on and can easily be extended via it’s env_vars.yml
to less or more machines and also to different operating system images.
This environment is used to deploy any number of RHEL nodes for generic use. It is also used as an example for new contributors to Agnostic D as an example
The ./default_vars.yml file contains all the variables you need to define to control the deployment of your environment.
This includes the ability to:
-
Change the number of machines deployed
-
Changed the operating system image (e.g. Ansible AMI or similar)
-
Change the tags carried by any instances
-
Change the base packages installed
-
Change/set the
ansible_user
andremote_user
These can be over-ridden at ansible-playbook
runtime via -e
options or perhaps more compactly by overriding vars in your own var file and invoking via -e @my_env_vars.yml
For further information on customizing images consult the Creating a Config Guide
To get started on OpenStack, please read First OSP Env warlkthrough, it uses this config.
You can deploy this config by running the following command from the ansible
directory. You will have to provide credentials and adjust settings to your own
environment.
You can run the playbook with the following arguments, from the ansible
directory, to overwrite the default variable values:
cp configs/just-a-bunch-of-nodes/sample_vars_osp.yml \
configs/just-a-bunch-of-nodes/my_vars.yml
ansible-playbook main.yml \
-e @configs/just-a-bunch-of-nodes/my_vars.yml \
-e @~/secret.yml