Re: [Openstack] openstack instance does not make use of all of disk space of flavor

[Ritesh]

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  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 partition
> 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.
> 
> 
> 
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@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@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] openstack instance does not make use of all of disk space of flavor

[Ritesh]

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  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  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.
>> 
>> 
>> 
>> 
>> ___
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@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@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Fwd: Making the Hong Kong Summit as inclusive as possible

[David Mortman]

On Thu, Sep 12, 2013 at 4:26 PM, David Mortman wrote:

>  Agreed. There should be at least a small group, especially for events, so
> that one person doesn't get hammered but also so there's a committee to
> make judgement calls etc. Love the idea of some training too.
>

Given the closeness of the summit (only 2 months away), it's seems like a
good idea to put together the initial group of folks who can be the onsite
committee to help address any issues that hopefully won't arise. While I'll
continue to participate in this effort, unfortunately, I won't be attending
the summit myself so I can't help onsite. I will however like  nominate
both Anne Gentle and George Reese be initial members of the committee.
Anyone else interested? A group of three is probably plenty.

thanks
-David
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Fwd: Making the Hong Kong Summit as inclusive as possible

[Annapoornima Koppad]

Hi All,

I am still in the learning process. Any inputs here, I am trying to
understand them. So I would have loved to help, but right now, I am also
not attending the summit this time. I would like to be involved in
understanding how our thought process is going to evolve in this process.

Regards,
Annapoornima


On Sun, Sep 15, 2013 at 4:29 PM, David Mortman wrote:

> On Thu, Sep 12, 2013 at 4:26 PM, David Mortman wrote:
>
>>  Agreed. There should be at least a small group, especially for events,
>> so that one person doesn't get hammered but also so there's a committee to
>> make judgement calls etc. Love the idea of some training too.
>>
>
> Given the closeness of the summit (only 2 months away), it's seems like a
> good idea to put together the initial group of folks who can be the onsite
> committee to help address any issues that hopefully won't arise. While I'll
> continue to participate in this effort, unfortunately, I won't be attending
> the summit myself so I can't help onsite. I will however like  nominate
> both Anne Gentle and George Reese be initial members of the committee.
> Anyone else interested? A group of three is probably plenty.
>
> thanks
> -David
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@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@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] openstack meta-data

[Tim Bell]

I don’t think there is a formal exit inside OpenStack to do this.  You may have 
to make a small patch to Nova.

It would be an interesting feature to define a plug-in architecture for this 
which would have several other uses.

Tim

> -Original Message-
> From: Francesco Ceccarelli [mailto:cecca...@fnal.gov]
> Sent: 14 September 2013 20:40
> To: Tim Bell
> Cc: openstack@lists.openstack.org
> Subject: Re: [Openstack] openstack meta-data
> 
> Hello,
> thanks for the help! I hadn't seen the command in the documentation, this can 
> be helpful.
> BTW my problem is to update metadata every time a machine is launched.
> For example let's talk about the hostname. Every time I launch a machine, I 
> would like to have well-configured metadata, with the
> parameter public-hostname already set to a customized value. I don't want the 
> instance name as public-hostname.
> 
> I hope I was clear and thanks again for the help, Francesco
> 
> 
> 
> On Sat, 2013-09-14 at 07:18 +, Tim Bell wrote:
> > You can update the metadata associated with an instance using the 'nova 
> > meta' command. However, this only updates the metadata
> (i.e.
> > key value pairs) rather than the other attributes.
> >
> > Changing the server name would not alter the hostname of the VM, it would 
> > only alter the description in Nova.
> >
> > Can you explain a little more what you would like to be doing ?
> >
> > Tim
> >
> > > -Original Message-
> > > From: Francesco Ceccarelli [mailto:cecca...@fnal.gov]
> > > Sent: 14 September 2013 00:11
> > > To: openstack@lists.openstack.org
> > > Subject: [Openstack] openstack meta-data
> > >
> > > Is it possible to update instance meta-data, for example to set the 
> > > public hostname?
> > >
> > > Thanks in advance,
> > > Francesco
> > >
> > >
> > > ___
> > > Mailing list: 
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > > Post to : openstack@lists.openstack.org
> > > Unsubscribe :
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 



smime.p7s
Description: S/MIME cryptographic signature
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [Neutron] Bug #1225614 opened

[Evgeny Fedoruk]

Hi,
As a result of review comment 
(https://review.openstack.org/#/c/46071/5/neutron/tests/unit/test_db_plugin.py)
on unit testing for Change Ied831402
Bug #1225614 was opened and assigned to me.
Change proposed and needs a review

Evgeny
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Call for participation and conferences : Capitole du libre (23rd/24th November Toulouse, France)

[Christophe Sauthier]

An conference called "Capitole du Libre" 
(http://2013.capitoledulibre.org/) is happening on the 23rd and 24th of 
November in Toulouse, France, and will host a dedicated track for 
OpenStack.


During "Capitole du Libre" we try to address many goals : to promote 
some (open) technologies, but also allow some communities to 
meet/gather. It is mainly in the latter aspect that I writing this email 
since at Capitole du Libre, there'll be a dedicated track for Openstack. 
It is clearly a chance for the Openstack France community to gather, 
which is a good thing since we are working hard to organize ourselves. 
But it will be a great chance for us to host some other Openstackers...



This track will separated in 2 parts :
- conferences on saturday
- workshops on the sunday.


This email is mainly a call for conferences and workshops. Ideally we 
would be able to cover many aspect (technicals or not) around OpenStack. 
So far we have decided or not to have a french only event : it means 
that if you want to submit some talks in English you can, and regarding 
the number we'll be able to have we can have a track in English... The 
deadline for submitting is Septembre 29th...


Finally, I'd like to add that Toulouse is a really really nice city, 
with a very nice weather (well we always can be unlucky...) so spending 
at least the weekend there is quite nice :)


Thanks for your feedback and participation ! Feels free to contact me 
if you want any other information, or if you want to sponsor the event 
;)


Cheers,

   Christophe

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Fwd: Making the Hong Kong Summit as inclusive as possible

[Joshua McKenty]

David, while I think having an onsite group able to field complaints and 
address incidents is critical, we need to make sure that such a group has the 
ability to address any complaints. So I'd suggest we pass this directly to the 
foundation staff, and make sure that the event coordination team is coached 
appropriately. Having community members act as ombudsperson is both complicated 
from a legal standpoint, and potentially inappropriate.

Lauren, can you make sure the on-site events team is briefed on the proposed 
code-of-conduct, and is ready to respond to any complaints that might arise?

--

Joshua McKenty
Chief Technology Officer
Piston Cloud Computing, Inc.
+1 (650) 242-5683
+1 (650) 283-6846
http://www.pistoncloud.com

"Oh, Westley, we'll never survive!"
"Nonsense. You're only saying that because no one ever has."

On Sep 15, 2013, at 3:59 AM, David Mortman  wrote:

> On Thu, Sep 12, 2013 at 4:26 PM, David Mortman  wrote:
>  Agreed. There should be at least a small group, especially for events, so 
> that one person doesn't get hammered but also so there's a committee to make 
> judgement calls etc. Love the idea of some training too.
> 
> Given the closeness of the summit (only 2 months away), it's seems like a 
> good idea to put together the initial group of folks who can be the onsite 
> committee to help address any issues that hopefully won't arise. While I'll 
> continue to participate in this effort, unfortunately, I won't be attending 
> the summit myself so I can't help onsite. I will however like  nominate both 
> Anne Gentle and George Reese be initial members of the committee. Anyone else 
> interested? A group of three is probably plenty.
> 
> thanks
> -David
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@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@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] openstack instance does not make use of all of disk space of flavor

[laclasse]

@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 Ub​untu 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 
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  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  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  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.
> >>
> >>
> >> 
> >> 
> >> ___
> >> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> >> Post to : openstack@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@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@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Fwd: Making the Hong Kong Summit as inclusive as possible

[David Mortman]

Joshua,

I'll leave it up to the event staff to determine how they want to handle it
in this on-site case. Certainly someone needs to be empowered or the
exercise is pointless. For the community as a whole, does the Board of
Directors have the authority to create an ombuds office?

-DM


On Sun, Sep 15, 2013 at 12:44 PM, Joshua McKenty wrote:

> David, while I think having an onsite group able to field complaints and
> address incidents is critical, we need to make sure that such a group has
> the ability to address any complaints. So I'd suggest we pass this directly
> to the foundation staff, and make sure that the event coordination team is
> coached appropriately. Having community members act as ombudsperson is both
> complicated from a legal standpoint, and potentially inappropriate.
>
> Lauren, can you make sure the on-site events team is briefed on the
> proposed code-of-conduct, and is ready to respond to any complaints that
> might arise?
>
> --
>
> Joshua McKenty
> Chief Technology Officer
> Piston Cloud Computing, Inc.
> +1 (650) 242-5683
> +1 (650) 283-6846
> http://www.pistoncloud.com
>
> "Oh, Westley, we'll never survive!"
> "Nonsense. You're only saying that because no one ever has."
>
> On Sep 15, 2013, at 3:59 AM, David Mortman  wrote:
>
> On Thu, Sep 12, 2013 at 4:26 PM, David Mortman wrote:
>
>>  Agreed. There should be at least a small group, especially for events,
>> so that one person doesn't get hammered but also so there's a committee to
>> make judgement calls etc. Love the idea of some training too.
>>
>
> Given the closeness of the summit (only 2 months away), it's seems like a
> good idea to put together the initial group of folks who can be the onsite
> committee to help address any issues that hopefully won't arise. While I'll
> continue to participate in this effort, unfortunately, I won't be attending
> the summit myself so I can't help onsite. I will however like  nominate
> both Anne Gentle and George Reese be initial members of the committee.
> Anyone else interested? A group of three is probably plenty.
>
> thanks
> -David
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@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@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Nova Client CLI Tool: Configure nova client CLI tool to consume image APIs from Glance service

[laclasse]

There is some overlap, maybe due to certain public cloud services that have
decided to expose the glance API through nova, rather than exposing the
glance api end point directly. Not entirely sure of  your end goal, but if
this is a private/custom install of OpenStack and you have the glance
service end point exposed, maybe you could use the 'python-glanceclient'
instead to speak the glance API directly?
Hope this helps.


On Sun, Sep 15, 2013 at 7:29 AM, GROSZ, Maty (Maty) <
maty.gr...@alcatel-lucent.com> wrote:

>  I f I understand you correctly – is there a duplication? Should not all
> the API you mentioned be pointed to Glance already?
>
> Why having these APIs under Nova if you have Glance?
>
> ** **
>
> *From:* Iccha Sethi [mailto:iccha.se...@rackspace.com]
> *Sent:* Thursday, September 12, 2013 20:31
> *To:* GROSZ, Maty (Maty)
> *Cc:* openstack@lists.openstack.org
> *Subject:* RE: [Openstack] Nova Client CLI Tool: Configure nova client
> CLI tool to consume image APIs from Glance service
>
> ** **
>
> Hey,
>
>  
>
> if you look at the readme :https://github.com/openstack/python-novaclient*
> ***
>
>  
>
> there are image calls you can make from nova cli
>
>  
>
> eg:
>
> image-create Create a new image by taking a snapshot of a running server.
> image-delete Delete an image. image-list Print a list of available images
> to boot from. image-meta Set or Delete metadata on an image. image-show
> Show details about the given image.
>
> Thanks,
>
> Iccha
>
>  
>
> -Original Message-
> From: "GROSZ, Maty (Maty)" 
> Sent: Thursday, September 12, 2013 4:43am
> To: "openstack@lists.openstack.org" 
> Subject: [Openstack] Nova Client CLI Tool: Configure nova client CLI tool
> to consume image APIs from Glance service
>
> Hey,
>
> I am trying to find out how do I configure nova client CLI  tool to
> consume image APIs from Glance service instead of nova v2.0.
>
> Someone can help?
>
> Thanks,
>
> Maty.
>
> [image: logo]
>
> *Maty Grosz*
>
> Alcatel-Lucent
>
> APIs Functional Owner, R&D
>
> CLOUDBAND BUSINESS UNIT
>
> 16 Atir Yeda St. Kfar-Saba 44643, ISRAEL
>
> T: +972 (0) 9 7933078
>
> F: +972 (0) 9 7933700
>
> *maty.gr...@alcatel-lucent.com * 
>
>  
>
>  
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@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@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] openstack meta-data

[laclasse]

Agreed, unique FQDNs on every instances is still a big issue for common
workloads, hopefully solved by DNS services coming to OpenStack soon... I
fully agree that the instance name and the FQDN of the instances should be
2 separate things, and even better, I think instances by default should try
a reverse lookup first when they get on the network, and if available,
collect a hostname, set it locally and display it in an additional column
in the DB/tables/webUI, and allows OpenStack services clients to use either
instance ID, name or hostname.

What the OP is trying to do is also feasible by installing a bind service
somewhere on the same subnet (bind9 minimum) and using the $GENERATE
directive in your zone file, see here on how to write your zone file using
that directive:
http://www.oit.uci.edu/dcslib/bind/bind-9.2.1/Bv9ARM.ch06.html#AEN4097

FWIW, AWS EC2 has a simple iterator that composes a unique hostname to any
instance by parsing the public IP address, replacing '.' (dots) with '-'
(to make it viable in a long hostname) and adding prefix/suffix to compose
the hostname (compute zones and domain) with added dots for example: "
ec2-54-211-89-105.compute-1.amazonaws.com" is an instance with IP
54.211.89.105 ... it a simple and useful solution. You can check it
yourself:

$ host 54.211.89.105
105.89.211.54.in-addr.arpa domain name pointer
ec2-54-211-89-105.compute-1.amazonaws.com.

Not having a unique FQDN on cloud instances can break many apps, and DNS
services in IaaS should not be taken for granted (failure may happen), so
IMHO, the best approach should be:
- boot instance, get on the network, do a reverse look up on IP to see if a
DNS server answers with a FQDN , collect it and set it
- if the look up fails, then resort to the iterator running and still end
up with an unique hostname per instance.

It seems a lot of public services hide this issue by allowing to launch
only one instance at the time, but AFAIK, if you launch several instances
at once using the nova CLI, you will end up with ALL instances having the
same hostname (which is the instance name you have given to nova CLI) ...
which breaks so many things it is not funny ... and is generally not a good
idea or best practices either.

If this functionality lands (very soon we hope), it will obviously also
allows users to deal with hostnames directly rather than IP address, which
in 2013, could give an archaic and old fashioned unfinished impression to
users.

Cheers, sorry for the mini-rant but I would think this is one of the most
urgent issues to address to see real automation and large scale apps.




On Sun, Sep 15, 2013 at 12:39 PM, Tim Bell  wrote:

>
> I don’t think there is a formal exit inside OpenStack to do this.  You may
> have to make a small patch to Nova.
>
> It would be an interesting feature to define a plug-in architecture for
> this which would have several other uses.
>
> Tim
>
> > -Original Message-
> > From: Francesco Ceccarelli [mailto:cecca...@fnal.gov]
> > Sent: 14 September 2013 20:40
> > To: Tim Bell
> > Cc: openstack@lists.openstack.org
> > Subject: Re: [Openstack] openstack meta-data
> >
> > Hello,
> > thanks for the help! I hadn't seen the command in the documentation,
> this can be helpful.
> > BTW my problem is to update metadata every time a machine is launched.
> > For example let's talk about the hostname. Every time I launch a
> machine, I would like to have well-configured metadata, with the
> > parameter public-hostname already set to a customized value. I don't
> want the instance name as public-hostname.
> >
> > I hope I was clear and thanks again for the help, Francesco
> >
> >
> >
> > On Sat, 2013-09-14 at 07:18 +, Tim Bell wrote:
> > > You can update the metadata associated with an instance using the
> 'nova meta' command. However, this only updates the metadata
> > (i.e.
> > > key value pairs) rather than the other attributes.
> > >
> > > Changing the server name would not alter the hostname of the VM, it
> would only alter the description in Nova.
> > >
> > > Can you explain a little more what you would like to be doing ?
> > >
> > > Tim
> > >
> > > > -Original Message-
> > > > From: Francesco Ceccarelli [mailto:cecca...@fnal.gov]
> > > > Sent: 14 September 2013 00:11
> > > > To: openstack@lists.openstack.org
> > > > Subject: [Openstack] openstack meta-data
> > > >
> > > > Is it possible to update instance meta-data, for example to set the
> public hostname?
> > > >
> > > > Thanks in advance,
> > > > Francesco
> > > >
> > > >
> > > > ___
> > > > Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > > > Post to : openstack@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@lists.opens

Re: [Openstack] openstack instance does not make use of all of disk space of flavor

[sam lee]

@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 

> @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 
> 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  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  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  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.
>> >>
>> >>
>> >> 
>> >> 
>> >> ___
>> >> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> >> Post to : openstack@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@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@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] openstack instance does not make use of all of disk space of flavor

[laclasse]

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  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 
>
>>  @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 
>> 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  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  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  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.
>>> >>
>>> >>
>>> >> 
>>> >> 
>>> >> ___
>>> >> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> >> Post to : openstack@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@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@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi

Re: [Openstack] openstack instance does not make use of all of disk space of flavor

[Craig Tracey]

Sam,

You might find cloud-init (https://launchpad.net/cloud-init) useful. It is
a tool (project also run by Scott Moser) to perform all kinds of instance
bootstrapping upon being launched, rebooted, etc across various operating
systems as well as cloud providers.  Specific to your case, cloud-init
supports growing any number of partitions. Here is an example of the
configuration:
https://github.com/number5/cloud-init/blob/master/doc/examples/cloud-config-growpart.txt

And more info on using cloud-init itself:
http://cloudinit.readthedocs.org/en/latest/

Hope this helps,
Craig




On Sun, Sep 15, 2013 at 9:07 PM, sam lee  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 
>
>> @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 
>> 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  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  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  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.
>>> >>
>>> >>
>>> >> 
>>> >> 
>>> >> ___
>>> >> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> >> Post to : openstack@lists.openstack.org
>>> >> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>> __

Re: [Openstack] Rebalancing issue

[Morten Møller Riis]

This is an example. It's the same for objects/containers/accounts (I recently 
lower the weight of the first two to 0 in preparation of replacing them).

$ swift-ring-builder account.builder
account.builder, build version 56
262144 partitions, 3 replicas, 7 zones, 15 devices, 306.67 balance
The minimum number of hours before a partition can be reassigned is 1
Devices:id  zone  ip address  port  name weight partitions balance 
meta
 0 1 10.44.1.101  6002   md2   0.00  00.00
 1 2 10.44.1.102  6002   md2   0.00  00.00
 2 3 10.44.1.103  6002   md2  25.00  26431  306.67
 5 4 10.44.1.104  6002  sda1 150.00  58928   51.11
 6 4 10.44.1.104  6002  sdb1 150.00  58928   51.11
 7 5 10.44.1.105  6002  sda1 150.00  58928   51.11
 8 5 10.44.1.105  6002  sdb1 150.00  58929   51.11
 9 6 10.44.1.106  6002  sdc1 300.00  65536  -15.97
10 6 10.44.1.106  6002  sdd1 300.00  65536  -15.97
11 6 10.44.1.106  6002  sde1 300.00  65536  -15.97
12 6 10.44.1.106  6002  sdf1 300.00  65536  -15.97
13 7 10.44.1.107  6002  sda1 300.00  65536  -15.97
14 7 10.44.1.107  6002  sdb1 300.00  65536  -15.97
15 7 10.44.1.107  6002  sdc1 300.00  65536  -15.97
16 7 10.44.1.107  6002  sdd1 300.00  65536  -15.97
$ swift-ring-builder account.builder rebalance
Cowardly refusing to save rebalance as it did not change at least 1%.
$




Mvh / Best regards
Morten Møller Riis
Gigahost ApS
m...@gigahost.dk




On Sep 14, 2013, at 2:03 AM, Clay Gerrard  wrote:

> Those two statements do seem in contrast - run `swift-ring-builer 
> account.builder` and check what is the current balance?Can you paste the 
> output?  Maybe you have an unbalanced region/zone/server and it's just can't 
> do any better than it is?
> 
> -Clay
> 
> 
> On Thu, Sep 12, 2013 at 11:53 PM, Morten Møller Riis  wrote:
> When adjusting weights and rebalancing I get the message:
> 
> NOTE: Balance of 306.68 indicates you should push this
>   ring, wait at least 1 hours, and rebalance/repush.
> 
> However, waiting a couple of hours and running swift-ring-builder 
> account.builder rebalance, it says that it has nothing to rebalance.
> 
> Cowardly refusing to save rebalance as it did not change at least 1%.
> 
> 
> What am I getting wrong here?
> 
> 
> Mvh / Best regards
> Morten Møller Riis
> Gigahost ApS
> m...@gigahost.dk
> 
> 
> 
> 
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@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@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack