On Wed, Jan 8, 2014 at 10:38 AM, Thomas Goirand <[email protected]> wrote: > > On 01/08/2014 04:55 PM, Juerg Haefliger wrote: > > Hi Thomas, > > > >> > >> Hi, > >> > >> I have uploaded an up-to-date Wheezy image using the > >> build-openstack-images package currently available in Wheezy. Here's the > >> IDs: > >> > >> region-a.geo-1: > >> 4f3a6b69-dd27-4ad1-8307-def66c436f8c > >> > >> region-b.geo-1: > >> 9c86049c-06cf-4f96-ba46-1eba57cc65ff > >> > >> These images have the public flag, so they are available for everyone. > >> They are up-to-date regarding security updates. > > > > Very cool! Thanks for doing this. > > > > I noticed that /dev/vdb doesn't get mounted automatically. > > Is there by default a /dev/vdb in the HP cloud? Why this? The fstab that > I create doesn't have any reference to vdb at all...
The vdb entry is added by cloud-init. Cloud-init pulls the the relevant information from the metadata service: $ debian@juergh-b0e61e83:~$ curl 169.254.169.254/2009-04-04/meta-data/block-device-mapping/ephemeral0 /dev/vdb > > This is due > > to the 'nobootwait' mount option in /etc/fstab which Debian doesn't > > understand (it's an Ubuntu extension). You need to add the following > > line to /etc/cloud/cloud.cfg: > > mount_default_fields: [~, ~, 'auto', 'defaults,nofail', '0', '2'] > > Will that be enough, even without "fixing" the fstab? Yes. It's all cloud-init magic. ...Juerg > > Also, you should set some additional image properties using 'glance > > image-update <image ID> --property <key>=<val>': > > - architecture=x86_64 (I'm actually surprised that the image boots > > without this. The scheduler uses this property to find a node that > > supports the image's architecture. I guess there's a sane default...) > > > > And the following are required if you want users of the management > > console (manage.hpcloud.com <http://manage.hpcloud.com>) to be able to > > use the image: > > - com.hp__1__bootable_volume=true > > - com.hp__1__image_lifecycle=active > > - com.hp__1__image_type=disk > > - com.hp__1__os_distro=debian > > Will do that (after you explain me this vdb stuff...). > > > You might also want to consider to protect the image (glance > > image-update <ID> --is-protected=true) so that it can't be deleted > > accidentally. Although I trust you not to do that :-) > > > > Best > > ...Juerg > > Ok, will probably add the flag then. thanks! > > Thomas >
