[ansible-project] Re: IP whitelisting challenge

Thanks Jon, I appreciate hearing how you handled this. Apologies that my issue was not limited by Ansible. On Monday, July 13, 2015 at 2:39:34 PM UTC-4, Jon Hadfield wrote: I had a similar issue, the difference being that I'm using only private addresses within the VPC subnets. As Brian

[ansible-project] IP whitelisting challenge

We have used Ansible to automate all of our deployments to EC2 (via the EC2 packages included with Ansible) and custom roles for our own services. Our production instances run in a vpc within public subnets. In order to do an integration with a partner, we've been asked to provide a range

[ansible-project] EC2 Inventory Script - boto profiles (ansible 1.8)

I've been struggling to get the inventory script to pick up my boto profile (I have multiple aws account creds to manage). What is the correct filter to use in the ec2.ini to specify the profile that should be used? Also, how does the presence of both ~/.boto and ~/.aws/credentials files

Re: [ansible-project] EC2 script cache across inventories

Thanks, that worked great! On Wed, Mar 25, 2015 at 3:17 PM, Brian Coca bc...@ansible.com wrote: I would update the ec2.ini to use different cache directories. cache_path = ~/.ansible/tmp/ec2_prod -- Brian Coca -- You received this message because you are subscribed to a topic in the

[ansible-project] Re: EC2 module not filtering tags from different vpc

, February 9, 2015 at 11:49:30 PM UTC-5, Gary Malouf wrote: We are experimenting with a staging and production environment each in their own vpc. It has been a struggle to use the EC2 module with this setup because despite applying instance filters to ec2. ini, the 'count' tags used in the ec2

[ansible-project] ec2.py filtering issue

I'm attempting to separate my staging and production server via two different vpcs. I'm using a filter as follows in each of ec2.ini files to separate instances running in the staging vpc from those in the production one. instance_filters = vpc-id=vpc-someid This works well for filtering out

[ansible-project] EC2 module not filtering tags from different vpc

We are experimenting with a staging and production environment each in their own vpc. It has been a struggle to use the EC2 module with this setup because despite applying instance filters to ec2. ini, the 'count' tags used in the ec2 module for provisioning count instances across vpcs if

[ansible-project] Rolling upgrade of AWS instances of particular tag

For managing our web servers, I have two playbooks: webservers-provision and webservers-update. As one may guess, provision handles bootstrapping instances while update deals with in-place updates of our software. I have a desire to do a rolling upgrade of all of our servers from one EC2

[ansible-project] Conditionally upgrade container (specific version)

I'm trying to achieve the following behavior via the Ansible-Docker module 1. Check if currently deployed container image is of desired version; if so, exit else proceed 2. Pull updated image 3. Stop/remove currently deployed container image 4. Start new container image I know

[ansible-project] Configuring IAM permissions/roles via module

Are there any roles/module for configuring IAM users, roles, permissions, etc? -- You received this message because you are subscribed to the Google Groups Ansible Project group. To unsubscribe from this group and stop receiving emails from it, send an email to

[ansible-project] Task/role separation when provisioning with Docker

I want to get an idea what the recommended way of organizing your files would be around doing the following: 1. Provision N EC2 instances of a specific size with appropriate AMI (CentOS + Docker) 2. Create container on each instance running Image A 3. Create container on each

[ansible-project] Deploying Ansible in EC2 and managing playbook access via IAM roles

I am setting up a fresh EC2 deployment for a client and am hoping to do the following: 1. Set up a management host for the cluster and deploy Ansible to it along with the client's playbooks 2. Allow users to successfully execute playbooks based on whether their IAM user has been

[ansible-project] Provisioning a NAT via ec2_vpc

Is setting up a NAT supported (but undocumented) or do we need to manually launch instances(s) via the normal ec2 module to act as a NAT for private sub-domains? -- You received this message because you are subscribed to the Google Groups Ansible Project group. To unsubscribe from this group

[ansible-project] Where do you run Ansible from for managing an EC2 cluster?

In the past, we ran Ansible on our bastion aka jump host. I've seen many postings online that people actually install Ansible locally and manage it completely from there. What are the pros and cons of going with that setup over having Ansible installed on an instance? -- You received this

Re: [ansible-project] Where do you run Ansible from for managing an EC2 cluster?

systems. An example is setting quorum size based on number of nodes in the inventory. Overall it's been a cool setup. If the con is a show stopper, then check out ansible tower. On Dec 31, 2014 10:04 PM, Gary Malouf malou...@gmail.com javascript: wrote: In the past, we ran Ansible on our

[ansible-project] Figuring out EC2 Support 'IAM Role Per Service'

We have a setup around creating one IAM role per application. Both within and outside of VPC, can this be managed via the Ansible EC2 modules or is there some additional scripting necessary on my end? -- You received this message because you are subscribed to the Google Groups Ansible

[ansible-project] Re: Ideal permissions setup?

://www.ansible.com/tower Пʼятниця, 8 серпня 2014 р. 08:44:24 UTC+3 користувач Gary Malouf написав: Today, we have a setup where all of our playbooks, roles, etc are owned and run by root on our 'management instance'. Some important key files are protected/encrypted in the root home directory

[ansible-project] Trouble updating alternatives on CentOS via shell/command modules

I tried using the debian-specific update-alternatives module but this did not work. Very simply, I have a command that when executed from the command line on the server itself works fine but via a task in our playbook says it succeeded but in reality has no effect. Very simply, I am trying to

[ansible-project] Bumping the version of a library and deleting older versions

I have a jar file named something like myjar -1.1.0-assembly.jar. When our team does a release, a new jar named something like myjar -1.2.0-assembly.jar is created and needs to be deployed to the world. Additionally, any jars matching the myjar -[VERSION]-assembly.jar pattern need to be