[ansible-project] How do you add an EC2 instance created with ec2 module to ~/.ssh/known_hosts

[Tim Stewart]

Let's say I have this ec2 task (taken from the documentation 
) in a file 
named site.yml:

# Basic provisioning example
- ec2:
  key_name: mykey
  instance_type: t2.micro
  image: ami-123456
  wait: yes
  group: webserver
  count: 3
  vpc_subnet_id: subnet-29e63245
  assign_public_ip: yes

Assuming I register the ec2 module result into a variable named 
ec2_instances, what would I do to add that single ec2 instance to my 
~/.ssh/known_hosts file so that I can easily ssh into the new instance?

I've looked at the known_hosts 
 
module and its example is:

- name: tell the host about our servers it might want to ssh to
  known_hosts:
  path: /etc/ssh/ssh_known_hosts
  name: foo.com.invalid
  key: "{{ lookup('file', 'pubkeys/foo.com.invalid') }}"

Every property makes sense to me except for the key property.  Regarding 
the lookup plugin, I don't have any file containing public keys for my new 
instance (that I know of).  What should I provide for the key property?

The documentation for the key property is:

The SSH public host key, as a string (required if state=present, optional 
> when state=absent, in which case all keys for the host are removed). The 
> key must be in the right format for ssh (see sshd(8), section 
> "SSH_KNOWN_HOSTS FILE FORMAT")


I have looked into the sshd(8) manual entry 
 and here are 
the relevant paragraphs (emphasis mine):


Each line in these files contains the following fields: markers (optional), 
hostnames, keytype, base64-encoded key, comment. The fields are separated 
by spaces.

The *keytype* and base64-encoded *key* are taken directly from the host 
key; they can be obtained, for example, from /etc/ssh/ssh_host_rsa_key.pub. 
The optional comment field continues to the end of the line, and is not 
used.


How do I get the key I need to add to the file?  This sounds like a common 
task so before I put forth potentially unnecessary effort to build my own 
solution, I thought I'd check to see if I was just missing something.

Thanks! 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/8613a235-3942-49c7-92dd-b47eae6f6642%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: How to properyly set up target groups for an application load balancer (ALB)?

[Tim Stewart]

BTW, the ec2_instances variable in my solution is the registered result of 
the ec2 task run with 'with_items'.

On Thursday, March 29, 2018 at 2:28:50 PM UTC-6, Tim Stewart wrote:
>
> Here is the solution that I came up with through a good deal of trial and 
> error:
>
> vars:
>
> # The list of service names we will be deploying.
> services:
>   - name: microservice-1
> port: 8080
>   - name: microservice-2
> port: 8080
>   - name: microservice-3
> port: 8080
>  :
>  :
>   - name: microservice-8
> port: 8080
>
> tasks:
>
> # some tasks omitted
>
> - name: Create Target Groups
>   elb_target_group:
> region: "{{ region }}"
> name: "{{ item.name }}-tg"
> protocol: http
> port: 80
> vpc_id: "{{ vpc_id }}"
> health_check_path: /health
> health_check_interval: 60
> successful_response_codes: "200"
> targets: "{{ ec2_instances | json_query(query) | map('combine', 
> {'Port': item.port}) | list }}"
> tags:
>   service: "{{ item.name }}"
> state: present
>   register: target_groups
>   with_items: "{{ services }}"
>   vars:
> query: 
> "results[].tagged_instances[?tags.service=='{{item.name}}'][].{Id: 
> id}"
>
>
> On Wednesday, March 28, 2018 at 4:50:01 PM UTC-6, Tim Stewart wrote:
>>
>> Hi,
>>
>> *Background:*
>>
>> We are developing a system using a Microservices approach and deploying 
>> it with Ansible 2.5.0.
>>
>> I'm writing a site.yml playbook that will provision two Ubuntu 16.04 
>> servers for each of eight different microservices.  We're provisioning two 
>> of each microservice for HA and we may increase that number in the future.  
>> For example, here are the microservice instances I want to create grouped 
>> by subnet (note this is not YAML):
>>
>> SubNet-a:
>> MicroService-1-a
>> MicroService-2-a
>> :
>> :
>> MicroService-8-a
>>
>> SubNet-b:
>> MicroService-1-b
>> MicroService-2-b
>> :
>> :
>> MicroService-8-b
>>
>> Now I want to create a Target Group for each kind of microservice (e.g. 
>> one for MicroService-1, one for Microservice-2, etc.).  For example, here 
>> are the target groups and their targets:
>>
>> MicroService-1-TargetGroup:
>>MicroService-1-a
>>MicroService-1-b
>>
>> MicroService-2-TargetGroup:
>>MicroService-2-a
>>MicroService-2-b
>>
>> :
>> :
>>
>> MicroService-8-TargetGroup:
>>MicroService-8-a
>>MicroService-8-b
>>
>> I then want to set up my ALB (using the elb_application_lb module) so 
>> that it has a *listener* with eight *rules* that route requests to the 
>> various Target groups based on a *path_pattern* condition.
>>
>> Here is an example *elb_target_group* with hard-coded targets (based on 
>> Ansible's documentation on elb_target_groups):
>>
>> - elb_target_group:
>> name: Microservice-1
>> protocol: http
>> port: 81
>> vpc_id: vpc-01234567
>> health_check_path: /
>> successful_response_codes: "200"
>> targets:*  - Id: i-01234567
>> Port: 80
>>   - Id: i-98765432
>> Port: 80*
>> state: present
>> wait_timeout: 200
>> wait: True
>>
>>
>> But since my site.yml playbook creates the EC2 instances, I won't have 
>> access to the *instance_id*s referred to in the *Id* parameter above.
>>
>> What is a good way of specifying the *targets* property of the 
>> *elb_target_group* (above) such that it only includes all of the EC2 
>> instances of a particular kind of microservice?
>>
>> For example:
>>
>> - elb_target_group:
>> name: *Microservice-1*
>> protocol: http
>> port: 81
>> vpc_id: vpc-01234567
>> health_check_path: /
>> successful_response_codes: "200,250-260"
>> targets:  - Id: *< **Microservice-1-a's instance_id >*
>> Port: 80
>>   - Id:* < **Microservice-2-a's instance_id >*
>> Port: 80
>> state: present
>> wait_timeout: 200
>> wait: True
>>
>>
>> Thanks!
>>
>>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/d8b3aa27-555a-4a2d-99ca-6cbbbee7f27e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: How to properyly set up target groups for an application load balancer (ALB)?

[Tim Stewart]

Here is the solution that I came up with through a good deal of trial and 
error:

vars:

# The list of service names we will be deploying.
services:
  - name: microservice-1
port: 8080
  - name: microservice-2
port: 8080
  - name: microservice-3
port: 8080
 :
 :
  - name: microservice-8
port: 8080

tasks:

# some tasks omitted

- name: Create Target Groups
  elb_target_group:
region: "{{ region }}"
name: "{{ item.name }}-tg"
protocol: http
port: 80
vpc_id: "{{ vpc_id }}"
health_check_path: /health
health_check_interval: 60
successful_response_codes: "200"
targets: "{{ ec2_instances | json_query(query) | map('combine', 
{'Port': item.port}) | list }}"
tags:
  service: "{{ item.name }}"
state: present
  register: target_groups
  with_items: "{{ services }}"
  vars:
query: 
"results[].tagged_instances[?tags.service=='{{item.name}}'][].{Id: id}"


On Wednesday, March 28, 2018 at 4:50:01 PM UTC-6, Tim Stewart wrote:
>
> Hi,
>
> *Background:*
>
> We are developing a system using a Microservices approach and deploying it 
> with Ansible 2.5.0.
>
> I'm writing a site.yml playbook that will provision two Ubuntu 16.04 
> servers for each of eight different microservices.  We're provisioning two 
> of each microservice for HA and we may increase that number in the future.  
> For example, here are the microservice instances I want to create grouped 
> by subnet (note this is not YAML):
>
> SubNet-a:
> MicroService-1-a
> MicroService-2-a
> :
> :
> MicroService-8-a
>
> SubNet-b:
> MicroService-1-b
> MicroService-2-b
> :
> :
> MicroService-8-b
>
> Now I want to create a Target Group for each kind of microservice (e.g. 
> one for MicroService-1, one for Microservice-2, etc.).  For example, here 
> are the target groups and their targets:
>
> MicroService-1-TargetGroup:
>MicroService-1-a
>MicroService-1-b
>
> MicroService-2-TargetGroup:
>MicroService-2-a
>MicroService-2-b
>
> :
> :
>
> MicroService-8-TargetGroup:
>MicroService-8-a
>MicroService-8-b
>
> I then want to set up my ALB (using the elb_application_lb module) so that 
> it has a *listener* with eight *rules* that route requests to the various 
> Target groups based on a *path_pattern* condition.
>
> Here is an example *elb_target_group* with hard-coded targets (based on 
> Ansible's documentation on elb_target_groups):
>
> - elb_target_group:
> name: Microservice-1
> protocol: http
> port: 81
> vpc_id: vpc-01234567
> health_check_path: /
> successful_response_codes: "200"
> targets:*  - Id: i-01234567
> Port: 80
>   - Id: i-98765432
> Port: 80*
> state: present
> wait_timeout: 200
> wait: True
>
>
> But since my site.yml playbook creates the EC2 instances, I won't have 
> access to the *instance_id*s referred to in the *Id* parameter above.
>
> What is a good way of specifying the *targets* property of the 
> *elb_target_group* (above) such that it only includes all of the EC2 
> instances of a particular kind of microservice?
>
> For example:
>
> - elb_target_group:
> name: *Microservice-1*
> protocol: http
> port: 81
> vpc_id: vpc-01234567
> health_check_path: /
> successful_response_codes: "200,250-260"
> targets:  - Id: *< **Microservice-1-a's instance_id >*
> Port: 80
>   - Id:* < **Microservice-2-a's instance_id >*
> Port: 80
> state: present
> wait_timeout: 200
> wait: True
>
>
> Thanks!
>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/bcbdb5bc-e45c-408b-ad43-9fa52a3334b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: How to properyly set up target groups for an application load balancer (ALB)?

[Tim Stewart]

One more thing.   The reason I did not provide any of my ansible files is 
that I would rather find the right way of doing this and have to go and 
change all my Ansible files than have someone try to come up with a 
solution that works with the potentially bad approach I've started from.  
Thanks!

On Wednesday, March 28, 2018 at 4:50:01 PM UTC-6, Tim Stewart wrote:
>
> Hi,
>
> *Background:*
>
> We are developing a system using a Microservices approach and deploying it 
> with Ansible 2.5.0.
>
> I'm writing a site.yml playbook that will provision two Ubuntu 16.04 
> servers for each of eight different microservices.  We're provisioning two 
> of each microservice for HA and we may increase that number in the future.  
> For example, here are the microservice instances I want to create grouped 
> by subnet (note this is not YAML):
>
> SubNet-a:
> MicroService-1-a
> MicroService-2-a
> :
> :
> MicroService-8-a
>
> SubNet-b:
> MicroService-1-b
> MicroService-2-b
> :
> :
> MicroService-8-b
>
> Now I want to create a Target Group for each kind of microservice (e.g. 
> one for MicroService-1, one for Microservice-2, etc.).  For example, here 
> are the target groups and their targets:
>
> MicroService-1-TargetGroup:
>MicroService-1-a
>MicroService-1-b
>
> MicroService-2-TargetGroup:
>MicroService-2-a
>MicroService-2-b
>
> :
> :
>
> MicroService-8-TargetGroup:
>MicroService-8-a
>MicroService-8-b
>
> I then want to set up my ALB (using the elb_application_lb module) so that 
> it has a *listener* with eight *rules* that route requests to the various 
> Target groups based on a *path_pattern* condition.
>
> Here is an example *elb_target_group* with hard-coded targets (based on 
> Ansible's documentation on elb_target_groups):
>
> - elb_target_group:
> name: Microservice-1
> protocol: http
> port: 81
> vpc_id: vpc-01234567
> health_check_path: /
> successful_response_codes: "200"
> targets:*  - Id: i-01234567
> Port: 80
>   - Id: i-98765432
> Port: 80*
> state: present
> wait_timeout: 200
> wait: True
>
>
> But since my site.yml playbook creates the EC2 instances, I won't have 
> access to the *instance_id*s referred to in the *Id* parameter above.
>
> What is a good way of specifying the *targets* property of the 
> *elb_target_group* (above) such that it only includes all of the EC2 
> instances of a particular kind of microservice?
>
> For example:
>
> - elb_target_group:
> name: *Microservice-1*
> protocol: http
> port: 81
> vpc_id: vpc-01234567
> health_check_path: /
> successful_response_codes: "200,250-260"
> targets:  - Id: *< **Microservice-1-a's instance_id >*
> Port: 80
>   - Id:* < **Microservice-2-a's instance_id >*
> Port: 80
> state: present
> wait_timeout: 200
> wait: True
>
>
> Thanks!
>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/f594e81e-861c-4422-853c-b866e6fee784%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] How to properyly set up target groups for an application load balancer (ALB)?

[Tim Stewart]

Hi,

*Background:*

We are developing a system using a Microservices approach and deploying it 
with Ansible 2.5.0.

I'm writing a site.yml playbook that will provision two Ubuntu 16.04 
servers for each of eight different microservices.  We're provisioning two 
of each microservice for HA and we may increase that number in the future.  
For example, here are the microservice instances I want to create grouped 
by subnet (note this is not YAML):

SubNet-a:
MicroService-1-a
MicroService-2-a
:
:
MicroService-8-a

SubNet-b:
MicroService-1-b
MicroService-2-b
:
:
MicroService-8-b

Now I want to create a Target Group for each kind of microservice (e.g. one 
for MicroService-1, one for Microservice-2, etc.).  For example, here are 
the target groups and their targets:

MicroService-1-TargetGroup:
   MicroService-1-a
   MicroService-1-b
   
MicroService-2-TargetGroup:
   MicroService-2-a
   MicroService-2-b

:
:

MicroService-8-TargetGroup:
   MicroService-8-a
   MicroService-8-b

I then want to set up my ALB (using the elb_application_lb module) so that 
it has a *listener* with eight *rules* that route requests to the various 
Target groups based on a *path_pattern* condition.

Here is an example *elb_target_group* with hard-coded targets (based on 
Ansible's documentation on elb_target_groups):

- elb_target_group:
name: Microservice-1
protocol: http
port: 81
vpc_id: vpc-01234567
health_check_path: /
successful_response_codes: "200"
targets:*  - Id: i-01234567
Port: 80
  - Id: i-98765432
Port: 80*
state: present
wait_timeout: 200
wait: True


But since my site.yml playbook creates the EC2 instances, I won't have 
access to the *instance_id*s referred to in the *Id* parameter above.

What is a good way of specifying the *targets* property of the 
*elb_target_group* (above) such that it only includes all of the EC2 
instances of a particular kind of microservice?

For example:

- elb_target_group:
name: *Microservice-1*
protocol: http
port: 81
vpc_id: vpc-01234567
health_check_path: /
successful_response_codes: "200,250-260"
targets:  - Id: *< **Microservice-1-a's instance_id >*
Port: 80
  - Id:* < **Microservice-2-a's instance_id >*
Port: 80
state: present
wait_timeout: 200
wait: True


Thanks!

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/4e9d9b34-f63f-43ac-a205-ae2aadafcebb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: I would like 'vagrant provision' to save my ansible_python_interpreter setting in the inventory file

[Tim Stewart]

Giles,
Thanks for your helpful answer!  As I was drifting off to sleep, I 
realized my question might have been a better fit for the Vagrant group.

 Have a great day!


On Monday, March 19, 2018 at 12:47:17 AM UTC-6, Gilles Cornu wrote:
>
> Hi Tim,
>
> You can do this with the host_vars 
> <https://www.vagrantup.com/docs/provisioning/ansible_common.html#host_vars> 
> provisioner 
> option.
>
> Best,
> Gilles
>
> PS: This question should better be asked in the vagrant mailing list 
> <https://groups.google.com/forum/#!forum/vagrant-up> ;-)
>
> Le dimanche 18 mars 2018 05:53:05 UTC+1, Tim Stewart a écrit :
>>
>> Ansible Version:
>>
>> $ ansible --version
>> ansible 2.4.3.0
>>   config file = /home/tim/AnsibleFun/ansible.cfg
>>   configured module search path = [u'/home/tim/.ansible/plugins/modules', 
>> u'/usr/share/ansible/plugins/modules']
>>   ansible python module location = 
>> /usr/lib/python2.7/dist-packages/ansible
>>   executable location = /usr/bin/ansible
>>   python version = 2.7.12 (default, Dec  4 2017, 14:50:18) [GCC 5.4.0 
>> 20160609]
>>
>>
>> Vagrant Version:
>>
>> $ vagrant --version
>> Vagrant 2.0.3
>>
>>
>>
>> Ubuntu Version:
>> $ lsb_release -a
>> No LSB modules are available.
>> Distributor ID: Ubuntu
>> Description: Ubuntu 16.04.4 LTS
>> Release: 16.04
>> Codename: xenial
>>
>>
>> Here is ./ansible.cfg:
>>
>> [defaults]
>> inventory = 
>> .vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory 
>> nocows = 1
>>
>>
>> [privilege_escalation]
>> # These are required to enable ansible to escalate privileges for 
>> installing
>> # software.
>> become = True
>> become_method = sudo
>> become_user = root
>>
>>
>>
>>
>> Here is my Vagrantfile:
>>
>> Vagrant.configure("2") do |config|
>>
>>   config.vm.define "traffic" do |traffic|
>> traffic.vm.box = "ubuntu/xenial64"
>>
>> # Perform ansible provisioning
>> config.vm.provision "ansible" do |ansible|
>>
>>   # Specify the playbook to use
>>   ansible.playbook = "playbooks/traffic_playbook.yml"
>>
>>   # Specify Ansible compatibility mode
>>   ansible.compatibility_mode = "2.0"
>>
>>   ansible.extra_vars = { ansible_python_interpreter: 
>> "/usr/bin/python3" }
>> end
>>   end
>> end
>>
>> When I run vagrant provision, an inventory file is created containing:
>>
>> # Generated by Vagrant
>>
>> traffic ansible_host=127.0.0.1 ansible_port= ansible_user='vagrant' 
>> ansible_ssh_private_key_file='/home/tim/AnsibleFun/.vagrant/machines/traffic/virtualbox/private_key'
>>
>>
>>
>> When I run the ad-hoc command: ansible all -m ping 
>>
>> I get:
>>
>> traffic | FAILED! => {
>> "changed": false, 
>> "module_stderr": "Shared connection to 127.0.0.1 closed.\r\n", 
>> "module_stdout": "/bin/sh: 1: /usr/bin/python: not found\r\n", 
>> "msg": "MODULE FAILURE", 
>> "rc": 0
>> }
>>
>> Now if I add an ansible_python_interpreter setting to my inventory file, 
>> the ad hoc command succeeds:
>>
>> traffic | SUCCESS => {
>> "changed": false, 
>> "ping": "pong"
>> }
>>
>>
>> But when I run: vagrant provision again,  the ansible_python_interpreter 
>> setting is removed from my inventory file loses and my ad hoc commands 
>> start failing again with the /usr/bin/python not found error.
>>
>> Is there some Vagrantfile syntax I can use to persist the 
>> ansible_python_interpreter setting in my inventory file?
>>
>> Thanks!
>>
>>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/cd1b27e2-ed08-43d0-a33b-51fdb2f7441b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] I would like 'vagrant provision' to save my ansible_python_interpreter setting in the inventory file

[Tim Stewart]

Ansible Version:

$ ansible --version
ansible 2.4.3.0
  config file = /home/tim/AnsibleFun/ansible.cfg
  configured module search path = [u'/home/tim/.ansible/plugins/modules', 
u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.12 (default, Dec  4 2017, 14:50:18) [GCC 5.4.0 
20160609]


Vagrant Version:

$ vagrant --version
Vagrant 2.0.3



Ubuntu Version:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial


Here is ./ansible.cfg:

[defaults]
inventory = 
.vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory 
nocows = 1


[privilege_escalation]
# These are required to enable ansible to escalate privileges for installing
# software.
become = True
become_method = sudo
become_user = root




Here is my Vagrantfile:

Vagrant.configure("2") do |config|

  config.vm.define "traffic" do |traffic|
traffic.vm.box = "ubuntu/xenial64"

# Perform ansible provisioning
config.vm.provision "ansible" do |ansible|

  # Specify the playbook to use
  ansible.playbook = "playbooks/traffic_playbook.yml"

  # Specify Ansible compatibility mode
  ansible.compatibility_mode = "2.0"

  ansible.extra_vars = { ansible_python_interpreter: "/usr/bin/python3" 
}
end
  end
end

When I run vagrant provision, an inventory file is created containing:

# Generated by Vagrant

traffic ansible_host=127.0.0.1 ansible_port= ansible_user='vagrant' 
ansible_ssh_private_key_file='/home/tim/AnsibleFun/.vagrant/machines/traffic/virtualbox/private_key'



When I run the ad-hoc command: ansible all -m ping 

I get:

traffic | FAILED! => {
"changed": false, 
"module_stderr": "Shared connection to 127.0.0.1 closed.\r\n", 
"module_stdout": "/bin/sh: 1: /usr/bin/python: not found\r\n", 
"msg": "MODULE FAILURE", 
"rc": 0
}

Now if I add an ansible_python_interpreter setting to my inventory file, 
the ad hoc command succeeds:

traffic | SUCCESS => {
"changed": false, 
"ping": "pong"
}


But when I run: vagrant provision again,  the ansible_python_interpreter 
setting is removed from my inventory file loses and my ad hoc commands 
start failing again with the /usr/bin/python not found error.

Is there some Vagrantfile syntax I can use to persist the 
ansible_python_interpreter setting in my inventory file?

Thanks!

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/ebfa3b42-2367-4bdd-a17a-8e83791a7bbf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.