hello without vagrant, using command line, etc. can you actually mount those devices ?
from my understanding aws will create the devices, but won't partition/format/mount them.. rite? On Wed, Jul 16, 2014 at 9:56 PM, San <[email protected]> wrote: > Thanks Alvaro for the script. > I already have similar sort of things but that doesn't actually sync with > the whole idea/concept of automated provisioning . I was wondering if > Vagrant has already cracked that. In stead of using script, surely I can do > in puppet using mount{} type but again, another problem is in AWS, the > devices get different names than the originally given. So, after the > installation, this is what happens on the node: > > root@p192-index-004:~# lsblk >> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >> xvda 202:0 0 30G 0 disk >> └─xvda1 202:1 0 30G 0 part / >> xvdb 202:16 0 30G 0 disk >> xvdf 202:80 0 100G 0 disk >> > > > So I need figure out the corresponding AWS device name, create the > file-system, stick that to the /etc/fstab and issue mount [-a] command to > mount the new volume, which involves running a number of external commands > from Puppet. Perhaps I can run that as user-data script but again, I > create nodes dynamically from a JSON config file and not sure if the > user-data (when not in-line) can get the value from the JSON. Best! > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" 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/d/optout. > -- You received this message because you are subscribed to the Google Groups "Vagrant" 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/d/optout.
