On Tue, Nov 18, 2014 at 6:25 PM, Matthew Morgan <[email protected]> wrote: > While I agree, that does sound like an idea, the problem with it is that I > need both, the private IP and public IP. The public IP is used on each node > for broadcast_address, the private IP is used on each node for > listen_address. In addition, each node needs a variable passed to it: > cassandra_seeds > Cassandra_seeds is a list of public IPs in the form of <ip1>,<ip2>,<ip3>. > > While it would be trivial to change the vpc_destination_variable to > ip_address, then i wouldn't be able to use the private IPs everywhere I need > them. > > Perhaps if I used two copies of the EC2 dynamic inventory script? is that > even possible? > It is possible by specifying a directory as your inventory and then placing both inventory scripts into the directory.
However, I was thinking that you could modify the script to return both the public and the private IP in separate fields. Is that not possible? The script should be able to even build up the cassandra_seeds variable for you and return it in, for instance, a group variable for the hosts that need to have the seed set so that you don't have to do as much work with jinja filters to build up the variable inside of your playbook. -Toshio "ec2 newbie" Kuratomi -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAG9juEoYXUpgjgKRS6b0%3DawE%3D2rNOY2bNYR%2BwsksZC8cG7byaQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
