Open Stack

Understood, in this case, I would recommend you use Ubuntu 12.04 LTS images
for your testing.
Hope this helps.


On Mon, Sep 16, 2013 at 2:07 AM, sam lee <lixq2000 at gmail.com> wrote:

> @laclasse, @Ritesh, thanks for the help. I will try right now.
>
> @laclasse, I am quite a newbe for openstack, and ubuntu 11.10 is just for
> test.
>
>
> 2013/9/16 laclasse <laclasse at gmail.com>
>
>>  @sam lee, if I understand properly
>> you are talking about a custom Ubuntu image you created? IIRC all Ubuntu
>> provided default images for OpenStack/AWS after 10.04 LTS have this package
>> installed (or was it starting at 12.04 LTS? Scott Moser the maintainer of
>> the packahe might know more).
>>
>>
>> Also, from your side, I would strongly reconsider and question why you
>> are deploying 11.10 Ubuntu, it is not an LTS release (Long Term Support) an
>> it is already End of Life (a.k.a not supported anymore, see here:
>> https://wiki.ubuntu.com/Releases
>> )
>> ;
>>  you will not get
>> any
>> updated software not mentioning potential security issues.
>>
>> A quick tip, the Ubuntu releases numbers have a meaning: 11 -> Year of
>> release, 10 -> Month of release. So Ubuntu 11.10 was released in October
>> 2011, nearly 2 years ago, in the Linux word, it is legacy and the
>> equivalent of deploying an old Windows release. If an ISV or an specific
>> application forces you to do deploy this version, you should simply push
>> back or give further details on the use case to see if the community can
>> help you further.
>>
>> The exact package you need installed in the instance is called "
>> cloud-initramfs-growroot
>> ", here is its description from the '
>> apt-cache show cloud-initramfs-growroot
>> ' command:
>>
>> Package: cloud-initramfs-growroot
>> Priority: extra
>> Section: universe/admin
>> Installed-Size: 48
>> Maintainer: Scott Moser <smoser at ubuntu.com>
>> Architecture: all
>> Source: cloud-initramfs-tools
>> Version: 0.19ubuntu1
>> Depends: cloud-utils (>= 0.21ubuntu1), initramfs-tools, util-linux (>=
>> 2.17.2)
>> Filename:
>> pool/universe/c/cloud-initramfs-tools/cloud-initramfs-growroot_0.19ubuntu1_all.deb
>> Size: 5692
>> MD5sum: 98035f2475531eec3b3179aeaa56a1d5
>> SHA1: 61a69b041ac8b54153ac6d1c4f9995b5f69b0a65
>> SHA256: 4ca1ec553c6a28a6942a13ea6f2c6db9e175449781a009c008191c19684b0d12
>> Description-en: automatically resize the root partition on first boot
>>  This package adds functionality to an initramfs built by initramfs-tools.
>>  When installed, the initramfs will repartition a disk to make the
>>  root volume consume all space that follows it.
>>   .
>>  You most likely do not want this package unless you know what you are
>>  doing.  It is primarily interesting in a virtualized environment when
>>  a disk can provisioned with a size larger than its original size.
>>  In this case, with this package installed, you can automatically use
>>  the new space without requiring a reboot to re-read the partition table.
>> Homepage: http://launchpad.net/cloud-initramfs-tools
>> Description-md5: 2a0d4bed7bada9873cf69d658abe0c23
>> Bugs: https://bugs.launchpad.net/ubuntu/+filebug
>> Origin: Ubuntu
>>
>>
>> Hope this helps.
>>
>>
>>
>>
>>
>> On Sun, Sep 15, 2013 at 8:09 AM, Ritesh <riteshnanda09 at gmail.com> wrote:
>>
>>> Hello sorry the spell check made package name changed its initramfs grow
>>> root deb package.
>>>
>>> Sent from my iPad
>>>
>>> On 15-Sep-2013, at 12:32 PM, Ritesh <riteshnanda09 at gmail.com> wrote:
>>>
>>> > Hello Sam,
>>> >
>>> > You need to install intramuscular-grow root deb available in Ubuntu ,
>>> which grow your root partition as space available.
>>> >
>>> > Cheers
>>> > Rite an
>>> >
>>> > Sent from my iPad
>>> >
>>> > On 15-Sep-2013, at 9:30 AM, sam lee <lixq2000 at gmail.com> wrote:
>>> >
>>> >> I have created a new instance with Ubuntu 11.10 with 80G disk space,
>>> but when I log into the instance and execute "df -h" the space show as
>>> attached dfh.png. and the output of "fdisk -l" as fdisk.png.
>>> >>
>>> >> I want vda taking all of the space and  do two steps as below:
>>> >>
>>> >> 1. fdisk /dev/vda, and create a extended partit
>>> >> 2. mkfs.ext4 /dev/vda1. ==> It will report "/dev/vda is is use"
>>> >>
>>> >> Is this right? If not, what is the correct way to taking all of the
>>> space?
>>> >>
>>> >> Thanks in advance.
>>> >>
>>> >>
>>> >> <dfh.png>
>>> >> <fdisk.png>
>>> >> _______________________________________________
>>> >> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> >> Post to     : openstack at lists.openstack.org
>>> >> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>> _______________________________________________
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to     : openstack at lists.openstack.org
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130916/cb4b2acf/attachment.html>