Hi Ken, Were those 200GB populated with 50GB+ of data?
Yes it can be mounted with the same options on the command line fine. Also if the EBS vol is already mounted it still hangs when it gets to it (remount thingy). iostat shows high I/O on the volume when this happens, so I thought it was due to puppet trying to back it up - but file ( backup => false } or changing it to a mkdir -p on the directory it gets mounted on made no difference. I thought it could be related to EBS volumes created from snapshots (i.e. the EBS vol isn't populated fully yet) but it doesn't appear to. I agree re the community CentOS images, we also rolled our own AMI to keep in sync with our bare metal repo. It doesn't hang on most of our EBS mounts, but I know we have a few in live where we have to kill puppet and finish the catalogue manually. I couldn't think of any other way to try and narrow it down to provide any more info. Matt On 21 April 2010 18:09, Ken <k...@bob.sh> wrote: > I didn't seen this myself Matt. I was using 200g EBS volumes. Can you > see the mount command in action while its blocking and try to > replicate manually it with all command line options etc. > > I found the provided and community Centos images where a bit poor - > and rolled my own from scratch because I wanted to use EBS volumes. I > also wanted it to be 'clean' without someone else's customisations as > well :-). > > ken. > > On Apr 21, 3:42 pm, Matt <mattmora...@gmail.com> wrote: > > Having the ebs vol id as a parameter in the node manifest works for us > > > > $ebsvol = "xxx" > > > > Then use the Mount type with that variable in your manifest file. > > > > We've observed an issue when mounting EBS volumes in EC2 on our CentOS 5 > AMI > > though - puppetd seems to hang when executing the mount command. Occurs > if > > I use the puppet Mount type, or just call mount via exec/bash script. > > > > Seems related to the amount of data on the EBS vols (40GB+) > > > > Running in debug provides no extra info - running 0.25.4 > > > > Thanks, > > > > Matt > > > > On 21 April 2010 13:44, Phillip B Oldham <phillip.old...@gmail.com> > wrote: > > > > > > > > > > > > > Thanks for the reply. I think the mounting part should be straight > > > forward. > > > > > 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". > > > > > On Apr 21, 1:07 pm, Ken <k...@bob.sh> wrote: > > > > > Is it possible, using puppet, to configure an EC2 instance so that > > > > > when it boots it attaches & mounts an EBS volume? If so, what steps > > > > > would one take to achieve this? > > > > > > The mounting should normally be done by your os - ie. put the entry > > > > in /etc/fstab. > > > > > > However - puppet can manage the /etc/fstab file with the 'mount' > > > > resource if you wanted: > > > > > >http://docs.puppetlabs.com/references/stable/type.html#mount > > > > > > But - I'm guessing your problem is that you don't want to re-create > > > > your EBS/AMI image every time you change /etc/fstab right? > > > > > > If you didn't want to save the entry in fstab and do the whole > > > > 'snapshot' image thing (to persist your /etc/fstab entry in your EBS/ > > > > AMI image) you could have puppet always start at bootup and let > puppet > > > > do the mounting. > > > > > > Puppet will mount the file-system at any time quite happily in this > > > > regard. Just need to make sure that your ensure line is 'mounted'. > For > > > > example: > > > > > > mount {"/mnt/point": > > > > device => "/dev/sdc1", > > > > ensure => "mounted", > > > > ... > > > > > > } > > > > > > Just make sure you getting your ordering right - as most people would > > > > be used to mounts appearing quite early in any boot sequence ... if > > > > you manage your service starts in puppet as well, you can let puppet > > > > do the ordering for you. > > > > > > ken. > > > > > > -- > > > > 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<puppet-users%2bunsubscr...@googlegroups.com> > <puppet-users%2bunsubscr...@google groups.com> > > > . > > > > For more options, visit this group athttp:// > > > groups.google.com/group/puppet-users?hl=en. > > > > > -- > > > 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<puppet-users%2bunsubscr...@googlegroups.com> > <puppet-users%2bunsubscr...@google groups.com> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/puppet-users?hl=en. > > > > -- > > 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<puppet-users%2bunsubscr...@googlegroups.com> > . > > For more options, visit this group athttp:// > groups.google.com/group/puppet-users?hl=en. > > -- > 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<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- 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.
