This is kind of in a broken state at the moment, but its the same concept as what you are describing (actually if you revert to a previous commit, it should work)
https://github.com/bodepd/puppet-ec2 On Mon, Sep 12, 2011 at 12:58 PM, Nan Liu <[email protected]> wrote: > On Sun, Sep 11, 2011 at 8:09 PM, Rob Terhaar <[email protected]> wrote: > > Hi All, > > > > I'd like to declaratively manage EC2 servers using Puppet. I'm aware > > of the new cloud-pack, however it's only useful for provisioning, not > > for managing an over-all consistent EC2 account state. Essentially, > > I'd like to use Puppet like an auditing tool for an EC2. Management of > > cloud services can become quite unwieldy when you have hundreds of EC2 > > instances starting and stopping in various phases of development. > > I did testing a while back, and I thought part of the process > installed the puppet agent on the ec2 node. It configured the > appropriate puppet master and took care of the certificates as well. > > > I've began working on a prototype, based on code from Brice Figureau's > > network-device code and from some borrowed bits from the cloud-pack > > code. However using network-device seems less than ideal because it > > does not collect facts from nodes. > > You can collect facts from network devices, but seems really odd to > write it as a network-device to ssh into the EC2 instance to gather > facts. Wouldn't it make sense to run the puppet agent on the EC2 nodes > after they are started from cloud-pack? You get all the facts, and you > can manage the system via puppet. > > > Is network-device an appropriate place to configure generic > > 'agent-less' nodes? What does the future hold for network-device? > > Seems like you are looking for a resource that simply start/stops EC2 > instances. So if you don't need a transport (ssh/telnet/xml wsdl) to > connect to the EC2 instance, I don't see a need to write it as a > network device. You can simply implement a resource that queries the > the list of instances through the command ec2-describe-instances, and > invokes ec2-run-instances, ec2-stop-instances based on ensure => > present, absent. I think libvirt provider is much closer to what you > are trying to implement rather than a network device. > > Thanks, > > Nan > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-dev?hl=en. > > -- "Join us for PuppetConf <http://bit.ly/puppetconfsig>, September 22nd and 23rd in Portland, OR." <http://bit.ly/puppetconfsig> -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
