Currently there are places within the Ansible playbook, plays and tasks that require the use of hard coding IP addresses for different servers, clients, and services. This should be enhanced and made dynamic in some way to make the environment more portable for users to download and use as a "playground".
An example of one of these definitions can be found within the webapp_settings.ini file in the playbooks/roles/webapp/templates/webapp directory. This is the same for the chexnet_client.py module as well...eventually being able to define these are arguments into the container instantiation might be the best place for control.
Currently there are places within the Ansible playbook, plays and tasks that require the use of hard coding IP addresses for different servers, clients, and services. This should be enhanced and made dynamic in some way to make the environment more portable for users to download and use as a "playground".
An example of one of these definitions can be found within the webapp_settings.ini file in the
playbooks/roles/webapp/templates/webappdirectory. This is the same for thechexnet_client.pymodule as well...eventually being able to define these are arguments into the container instantiation might be the best place for control.