I forgot to add, the inventory module only gives the instance-ids, not the actual facts about those instances. If the instance isn't running, I don't want to have to start it up, log in, and use ec2_facts (which only works for a single instance) to get this information. That's very, very slow compared to directly gathering the ec2_instance_facts information without having to actually log into the instances individually.
-scott On Mar 8, 2014, at 6:37 PM, Scott Anderson <[email protected]> wrote: > On Mar 8, 2014, at 6:27 PM, Michael DeHaan <[email protected]> wrote: > >> This feels like it belongs in the inventory plugin, so it is automatic, can >> you expand on thoughts? > > Yes, I wrote this precisely because the inventory plugin didn't suit my > needs. The inventory module only works for existing instances. > > I create a maintenance instance on the fly for burning AMIs. I need to check > to see if the instance exists; if not, I create it using a base AMI in a > particular VPC, then configure the instance with whatever roles I need (web, > monitoring, syslog, etc) by passing the newly created host IP to add_host. > Finally, I burn an AMI from the instance and shut it down. > > Regards, > -scott -- 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/4AE1381D-A2F8-4AD9-A694-BC038AFD890B%40gmail.com. For more options, visit https://groups.google.com/d/optout.
