This is not exactly Amazon cloud, but thanks for the hints. The way I use this is usually behind NAT, so I checkout Ansible with playbook and run them locally. -- anatoly t.
On Fri, Dec 6, 2013 at 6:34 PM, Eric Palmer <[email protected]> wrote: > can you associate it with a ip or even a host name in route53. When you > start up the instance you can use an aws cli script to associate the > instance dns name with a standard name and use that. Or create an elastic ip > and use aws cli to associate the elastic ip with the ec2 dns name. > > eric > > > On Fri, Dec 6, 2013 at 10:23 AM, anatoly techtonik <[email protected]> > wrote: >> >> >> On Thursday, December 5, 2013 3:10:17 PM UTC+3, Eric Palmer wrote: >>> >>> Just trying to find out of others use ansible for my edge case. I get >>> that most people orchestrate many servers with ansible. >>> >>> I use ansible to build one-off provisioning scripts. I am not a system >>> admin type and more of a developer. I find ansible very valuable (like it >>> has changed my professional life) for capturing my incremental learning of >>> provisioning steps, and when I'm done I can build test, staging, and prod >>> servers for various applications. >>> >>> Michael and team, thanks for Ansible! >> >> >> +1 >> >> I am trying to get Ansible manage my workstation (which is random node in >> the cloud), and I am currently struggling to avoid typing inventory file >> every time. > > > > > -- > Eric Palmer -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
