[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: OpenStack Debian 7 Image



On 27 October 2013 17:32, Thomas Goirand <zigo@debian.org> wrote:
On 10/26/2013 06:07 AM, Tyler Wilson wrote:
> Hey All,
>
> I've tried researching into creating a qcow2 Debian Openstack image but
> diddnt get very far; Is there a recently-updated guide on how this is
> completed or possibly a Debian-maintained cloud image? I've attempted
> using cloud-init (after adding from experimental)

You don't need the experimental version of cloud-init. This one contains
only an addition for Google cloud. If you are using Wheezy, then you can
use the version I uploaded to backports directly (don't use the one from
Sid).

> however it doesn't
> seem to work with growpart to resize /dev/vda1

It does work for me on OpenStack... Though here, it should be
/dev/xvda1, and not /dev/vda1, and I don't think that it is possible to
grow a partition in the AWS thing: you have access to a partition, not
to a full hard drive. So the only thing that should be done is
resize2fs, and that's it.

> and doesn't pull EC2
> metadata from 169.254.169.254 and instead uses the DHCP gateway.

It did work for me (again, on OpenStack, but that's the same EC2
protocol and same IP address). Are you sure that you have configured
cloud-init correctly? (you can try to dpkg-reconfigure cloud-init to
make sure of that)

Thomas Goirand (zigo)


--
To UNSUBSCRIBE, email to debian-cloud-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 526D4023.6070509@debian.org" target="_blank">http://lists.debian.org/526D4023.6070509@debian.org


> [..] and I don't think that it is possible to grow a partition in the AWS thing: you have access to a partition, not to a full hard drive.
For EBS that is not true. It's a block device and you can partition it if you like, the xvda1 is a hack really.
It's a leftover from instance-backed AMI times where the ephemeral storage was presented as xvda1 xvda2... to the system (though they are not partitions).
(Actually, in the WIP branch of my bootstrapper I have fixed this for EBS instances, the HDD is now attached as /dev/sda instead of /dev/sda1)

Reply to: