On 22 April 2010 08:12, Phillip B Oldham <phillip.old...@gmail.com> wrote:
> On Apr 21, 6:06 pm, Ken <k...@bob.sh> wrote: > > > My main problem is defining in puppet the name of the EBS volume to > > > attach, and having the puppet client on the EC2 instance actually > > > *attach* the volume after it has "spun-up". > > > > Is this because you want to be able to convert the EBS id to a /dev/ > > sdX device? So the EBS volume id is what you reference in your > > configuration ...? > > Not exactly. I'm working with an OpenSolaris instance. What I'm hoping > puppet can do is, when the instance starts up, issue the ec2 commands > to attach a specified EBS volume to itself then keep checking whether > the drive is available before issuing the ZFS commands to "import" the > newly-attached drive. Would this be possible? If so, which sections of > the documentation should I be focussing on? > > I don't know much about solaris, but you could use the Exec type to issue the EC2 commands to attach the EBS volume to say /dev/sdx, then use the Mount type or another Exec to mount/import the ZFS system. If you look at using EC2 facters http://projects.puppetlabs.com/projects/puppet/wiki/Amazon_Ec2_Patterns then your instance will even know it's own instance id etc. I personally prefer to set-up the instances externally with some other tool, saves having AWS credentials on the EC2 instance. Matt -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
