![]() ![]() In theory, you could work with a callback to tower for the second part, but then you need to set up a way for the client to reach the server through the nat instance. configuration: here we get the sandbox vpc ec2 instances and select a specific tagname we gave during provisioning.provision & install: ‘tower-via-local’ which is located in our VPC.We need to split these up as both playbooks need a different inventory to work with: The second one deploys the war and edits a file. ![]() The first one sets up a node and installs tomcat. I won’t detail the tower configuration of the project/inventory/job/… here in detail as it’s quite straightforward. Prox圜ommand ssh -i -o StrictHostKe圜hecking=no nc %h %p This allows ansible to use the ssh configuration stored on the tower server. Ssh_args = -o ControlMaster=auto -o ControlPersist=16m -F /opt/ansible/ssh/ In the root of our project we need an ansible.cfg file containing: To allow our tower to connect through the nat host we need some extra config. (and in our case an S3 read-only IAM policy as our version of ansible doesn’t support policy creation yet).a nat host so ansible tower can manage servers from our vpc in the remote vpc.While this is a very simple exercise, it does touch on some interesting topics about ansible and aws. To start learning about ansible and AWS, I created a small setup that does the following: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |