After giving up on Ansible Container for now, I’m going to take another swing at FutureGateway orchestration, this time putting Ansible on the outside of the containers.
The previous strategy was to express all of the services as containers in a topology similar to Docker-Compose first, and then configure each of the containers with a special Ansible conductor container. This proved just too much for me to grasp at the present time - there’s a dissonance between my way of thinking and the “right” way to do things with Ansible Container.
Also, I’m running out of Soundgarden to keep me going…
Sooo, I’m going to try do things the “older-school” way, by writing a playbook which will apply roles to containers, usig the docker connection, and avoiding Ansible Container entirely.
Start this post
Start the playbook in the fgSetup/ansible directory
had to get the docker-py pip re-installed
It’s time to switch to a little Nirvana. Dead old rockers are all that is going to get me through this day…
It’s not clear how to get a docker container started - do I use the docker_container module or the docker-py inventory ? Probably the module, since the dynamic inventory only shows things which have already been created.
Ok, I can create the containers quite nicely but now I need to refresh the inventory so that we can apply roles to host groups…
We don’t need an actual user on the db host now, we can change user: to mysql_user: