Re: [Openstack] Making Nova HA summit notes

[Mike Scherbakov]

Hi,
Thank you for the work on making nova components HA.

Did you have a chance to move further in this topic?
I especially interested in making nova-network HA and looking for possible
active-active implementations,
so the downtime of the service would me minimal.

Thank you,

On Tue, May 3, 2011 at 1:22 PM, Edward Konetzko
wrote:

> I have attached the slides and Tushar Patil doc on making nova-network ha
> along with the etherpad notes on the bottom.
>
>
> I hope to follow this email up later on in the week with plans for a full
> reference document based on Cacti.  Thanks for everyone’s participation at
> the Summit.
>
> Thanks
> Edward Konetzko
>
> Etherpad notes
>
>
> This Etherpad is for the
> Discussion on Design & Software Considerations for Making Nova HA/Fault
> Tolerant
> Please put ideas or comments in the appropriate sections
>
>
> Database
> - Does zones alleviate the need for HAing the DB?
>
>
>
> RabbitMQ
> For comparison http://wiki.secondlife.com/**wiki/Message_Queue_Evaluation_
> **Notes 
> - Need to update managers to create persistant queues and messages
> - XMPP an alternate?
> Talk to RabbitMQ devs about
> - Long term can we use Burrow?
>
>
> Nova-Network
> NTT Data documentation mailed to openstack list for their heartbeat POC
> tests
> Are there issues running multiple network nodes and assigning the same IP
> to mutlple instances?
> How about VRRP protocol?
>   --> we (NTT) are planning to evaluate VRRP using keepalived or some other
> software. Does anyone knows suitable software?
>
>
> Nova-scheduler
> Vish said you can run more then one
> - Yeah with zones and how the scheduler is structured now, it can
>
>
> Nova-api
> Possibliy to run this behind real web server, apache, nginx
>
>
> Nova-volume
>
> Nova-Objectstore
>
> Nova-Compute
>
>
> Other ideas
> Services should use dns srv records or something to automate service
> discovery, this would make running large infrastructures and ipv6
> configureation alot easier.
> - zeroconf?  -<-- like the idea but anyone can announce anything in
> zeroconf it has no idea of a master for security.
> Agreed
> Look at vrrp and keepalived
>
>
> Take aways
> Start Discussion with Rabbitmq
> Message Bus needs more investigation
> Discussion on how do we make messages have delievery
> Give feed back to end user, fail or pass just dont leave state in pending
> forever
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Mike Scherbakov
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] about vlan and switch

[Thor Wolpert]

That was a great explanation, thanks!

There is also a limit of 12 bits in the 802.1Q protocol, effectively setting
the max to 4096 vlans

I so look forward to having that kind of problem :)!

On Wed, Jul 20, 2011 at 9:26 PM, Jeff Kramer  wrote:

> As I understand it, you can setup the tags in the switch first if you
> want, but you don't need to.  You will create VLAN tags in the Nova
> database as you create networks with 'nova-manage network create ...',
> and those will be assigned to users on a first-come first-serve basis.
>  When a user creates their first node nova assigns them an unused
> network which has a unique VLAN tag.  This tag is passed to
> nova-compute when your instance is started, and it feeds that VLAN tag
> into KVM which uses it for all network traffic in a way that's
> transparent to the guest OS.  When the guest talks to the network it
> uses that VLAN tag, which the nova-network node is also listening on.
>
> As long as your switch supports host-tagged VLANs (802.1Q), you don't
> have to create the tags in the switch before you use them.  You could
> setup all your VLANs before, someone else may have more experience
> with that.
>
> One wrinkle is that many switches have a set number of tagged VLANs
> they can support, for instance the HP V1810-24G switch that I'm using
> supports 64 tagged VLANs, which means my Nova cluster can only have 64
> different networks (or 64 different users).  The next model up
> supports 256, etc.  I assume that if you go over this number your
> network traffic will start dropping and weird things will happen.
>
> Your switch's management IPs should probably be in an address space
> that doesn't conflict with what you're assigning with nova.  If you're
> using 10.x.x.x for Nova you could put the switch on 192.168.x.x.  You
> probably shouldn't be touching the switch from a Nova guest, since the
> time you'll want to be fiddling with it will be when your Nova cluster
> is crashing or otherwise broken.
>
>
> On Wed, Jul 20, 2011 at 10:43 PM, tianyi wang  wrote:
> > Hi, all
> >
> >
> > If use VLAN mode, it's need setting VLAN in switch's NOS first?
> > And then the setting VLAN in nova controller node?
> >
> > Now, the switch's IP is 192.168.0.234 and the gateway ip address is
> > 192.168.0.1 ( in switch web management interface), should I change the
> > switch  IP and gateway to 10.0.0.x ?
> >
> > In VLAN mode, what's the relationship tween the controller node's VLAN
> > management and switch's NOS VLAN management?
> >
> > thanks
> >
> >
> > alex
> >
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
> >
>
>
>
> --
> Jeff Kramer
> jeffkra...@gmail.com
> http://www.jeffkramer.org/
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] about vlan and switch

[Jeff Kramer]

As I understand it, you can setup the tags in the switch first if you
want, but you don't need to.  You will create VLAN tags in the Nova
database as you create networks with 'nova-manage network create ...',
and those will be assigned to users on a first-come first-serve basis.
 When a user creates their first node nova assigns them an unused
network which has a unique VLAN tag.  This tag is passed to
nova-compute when your instance is started, and it feeds that VLAN tag
into KVM which uses it for all network traffic in a way that's
transparent to the guest OS.  When the guest talks to the network it
uses that VLAN tag, which the nova-network node is also listening on.

As long as your switch supports host-tagged VLANs (802.1Q), you don't
have to create the tags in the switch before you use them.  You could
setup all your VLANs before, someone else may have more experience
with that.

One wrinkle is that many switches have a set number of tagged VLANs
they can support, for instance the HP V1810-24G switch that I'm using
supports 64 tagged VLANs, which means my Nova cluster can only have 64
different networks (or 64 different users).  The next model up
supports 256, etc.  I assume that if you go over this number your
network traffic will start dropping and weird things will happen.

Your switch's management IPs should probably be in an address space
that doesn't conflict with what you're assigning with nova.  If you're
using 10.x.x.x for Nova you could put the switch on 192.168.x.x.  You
probably shouldn't be touching the switch from a Nova guest, since the
time you'll want to be fiddling with it will be when your Nova cluster
is crashing or otherwise broken.


On Wed, Jul 20, 2011 at 10:43 PM, tianyi wang  wrote:
> Hi, all
>
>
>     If use VLAN mode, it's need setting VLAN in switch's NOS first?
> And then the setting VLAN in nova controller node?
>
> Now, the switch's IP is 192.168.0.234 and the gateway ip address is
> 192.168.0.1 ( in switch web management interface), should I change the
> switch  IP and gateway to 10.0.0.x ?
>
> In VLAN mode, what's the relationship tween the controller node's VLAN
> management and switch's NOS VLAN management?
>
> thanks
>
>
> alex
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Jeff Kramer
jeffkra...@gmail.com
http://www.jeffkramer.org/

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Thinking about Backups/Snapshots in Nova Volume

[Thorsten von Eicken]

+1

On 7/20/2011 2:27 PM, Chuck Thier wrote:
> Yeah, I think you are illustrating how this generates much confusion :)
>
> To try to be more specific, the base functionality should be:
>
> 1. Create a point in time backup of a volume
> 2. Create a new volume from a backup (I guess it seems reasonable to
> call this a clone)
>
> This emulates the behavior of what EC2/EBS provide with volume
> snapshots.  In this scenario, a "restore" is create a new volume from
> the backup, and delete the old volume.
>
> In the Storage world, much more can generally be done with snapshots.
> For example in most storage system snapshots are treated just like a
> normal volume and can be mounted directly.  A snapshot is often used
> when creating a backup to ensure that you have a consistent point in
> time backup, which I think most of the confusion comes from.
>
> What we finally call it doesn't matter as much to me, as long as we
> paint a consistent story that isn't confusing, and that we get it in
> the Openstack API.
>
> --
> Chuck
>
> On Wed, Jul 20, 2011 at 3:33 PM, Vishvananda Ishaya
>  wrote:
>> In rereading this i'm noticing that you are actually suggesting alternative 
>> usage:
>>
>> backup/clone
>>
>> snapshot/restore
>>
>> Correct?
>>
>> It seems like backup and snapshot are kind of interchangable.  This is quite 
>> confusing, perhaps we should refer to them as:
>>
>> partial-snapshot
>>
>> whole-snapshot
>>
>> or something along those lines that conveys that one is a differencing image 
>> and one is a copy of the entire object?
>>
>> On Jul 20, 2011, at 12:01 PM, Chuck Thier wrote:
>>
>>> At the last developers summit, it was noted by many, that the idea of
>>> a volume snaphsot in the cloud is highly overloaded.  EBS uses the
>>> notion of snapshots for making point in time backups of a volume that
>>> can be used to create a new volume from.  These are not true snapshots
>>> though from a storage world view.  Because of this I would like to
>>> make the following proposal:
>>>
>>> Add a backup API to the Openstack API for Nova Volume.  This is to
>>> provide EBS style snapshot functionality in the Openstack API.  I'm
>>> proposing to name it backup instead of snapshot as that seems to
>>> better describe what is happening.  It also allows room for other
>>> storage backends to expose real snapshot capabilities down the road.
>>>
>>> In the case of Lunr, we would be making backups of volumes to swift
>>> (possibly abstracted through glance in the future).
>>>
>>> I have started a blueprint and spec at:
>>>
>>> https://blueprints.launchpad.net/nova/+spec/backups-api
>>> http://etherpad.openstack.org/volume-backup
>>>
>>> Please feel free to comment and contribute.
>>>
>>> --
>>> Chuck
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] about vlan and switch

[tianyi wang]

Hi, all


 If use VLAN mode, it's need setting VLAN in switch's NOS first?
And then the setting VLAN in nova controller node?

Now, the switch's IP is 192.168.0.234 and the gateway ip address is
192.168.0.1 ( in switch web management interface), should I change the
switch  IP and gateway to 10.0.0.x ?

In VLAN mode, what's the relationship tween the controller node's VLAN
management and switch's NOS VLAN management?

thanks


alex

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [Keystone] usage of PUT and POST in APIs

[Mellquist, Peter]

Looking through the latest Keystone code and developer guide I have noticed 
some differences in the usage of PUT and POST CRUD operations. 

Resource Creation  admin.py   Developer Guide Says   

Tenant PUT or POSTPUT in table 5.2.4 OR POST in section 
5.4.1 ?
Tenant Group   PUT or POSTNA
Users  PUT or POSTPUT in table 5.2.2 
Global Group   PUT or POSTNA
Role Ref   POST   POST in table 5.2.6 and section 5.6.4
Endpoints  POST   POST in table 5.2.5 and section 5.5.4


Questions:
Is there any reason why Tenants and Users allow PUT and POST for creation while 
Roles and Endpoints only allow POST?

Would it be possible to go only with POSTs in the above areas?

The developer guide does not match the current code in the above areas, these 
may just be typos at this stage but it would be good to clarify what the real 
APIs should be.


Peter.




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Keystone] Question from mgius on IRC about update_user API call

[Yogi Srikrishnan]

Even if we remove this restriction you still need to fetch and examine disabled 
users only by fetching every user with a get_users call. Do you think whether 
we need a shorthand operation just to get the disabled users.I am fine with 
removing these checks.
Yogeshwar Srikrishnan
Rackspace

From: Mark Gius [m...@markgius.com]
Sent: Wednesday, July 20, 2011 4:12 PM
To: Yogi Srikrishnan
Cc: Jay Pipes; openstack@lists.launchpad.net
Subject: Re: [Openstack] [Keystone] Question from mgius on IRC about 
update_user API call

Would you be opposed to removing the check for disabled in get_user, and 
possibly update_user as well?  As it stands now, you can only fetch and examine 
disabled users by fetching every user with get_users.

Is there some reason that a disabled user should not be fetched or updated?

Mark

On Wed, Jul 20, 2011 at 1:01 PM, Yogi Srikrishnan 
mailto:yogesh.srikrish...@rackspace.com>> 
wrote:
Right now the code to update doesn't allow the operation if the user is 
disabled as there is a separate call to enable/disable user ie 
/users/userId/enabled .That call should allow the enabling/disabling of user 
independent of his current status.
Regards
Yogeshwar Srikrishnan
Rackspace


From: 
openstack-bounces+yogesh.srikrishnan=rackspace.com@lists.launchpad.net
 
[openstack-bounces+yogesh.srikrishnan=rackspace.com@lists.launchpad.net]
 on behalf of Jay Pipes [jaypi...@gmail.com]
Sent: Wednesday, July 20, 2011 1:54 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] [Keystone] Question from mgius on IRC about update_user
API call

Keystone devs,

mgius had a question on IRC:

 I have a question about Keystone
 I'm looking to add support to the dashboard so that users can
be enabled or disabled from the dashboard
 but it looks like in update_user if the target user is
disabled a 403 is always thrown
 was that intentional?

-jay

___
Mailing list: https://launchpad.net/~openstack
Post to : 
openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is 
prohibited.
If you receive this transmission in error, please notify us immediately by 
e-mail
at ab...@rackspace.com, and delete the original 
message.
Your cooperation is appreciated.


___
Mailing list: https://launchpad.net/~openstack
Post to : 
openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp



Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace. 
Any dissemination, distribution or copying of the enclosed material is 
prohibited.
If you receive this transmission in error, please notify us immediately by 
e-mail
at ab...@rackspace.com, and delete the original message. 
Your cooperation is appreciated.

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Keystone] Question from mgius on IRC about update_user API call

[Mark Gius]

It looks like my previous email didn't go through because I hadn't
registered this email address with launchpad.  Sending again.

Would you be opposed to removing the check for disabled in get_user, and
possibly update_user as well?  As it stands now, you can only fetch and
examine disabled users by fetching every user with get_users.

Is there some reason that a disabled user should not be fetched or updated?

Mark

On Wed, Jul 20, 2011 at 2:12 PM, Mark Gius  wrote:

> Would you be opposed to removing the check for disabled in get_user, and
> possibly update_user as well?  As it stands now, you can only fetch and
> examine disabled users by fetching every user with get_users.
>
> Is there some reason that a disabled user should not be fetched or updated?
>
> Mark
>
>
> On Wed, Jul 20, 2011 at 1:01 PM, Yogi Srikrishnan <
> yogesh.srikrish...@rackspace.com> wrote:
>
>> Right now the code to update doesn't allow the operation if the user is
>> disabled as there is a separate call to enable/disable user ie
>> /users/userId/enabled .That call should allow the enabling/disabling of user
>> independent of his current status.
>> Regards
>> Yogeshwar Srikrishnan
>> Rackspace
>>
>> 
>> From: openstack-bounces+yogesh.srikrishnan=rackspace.com@
>> lists.launchpad.net [openstack-bounces+yogesh.srikrishnan=rackspace.com@
>> lists.launchpad.net] on behalf of Jay Pipes [jaypi...@gmail.com]
>> Sent: Wednesday, July 20, 2011 1:54 PM
>> To: openstack@lists.launchpad.net
>> Subject: [Openstack] [Keystone] Question from mgius on IRC about
>> update_userAPI call
>>
>> Keystone devs,
>>
>> mgius had a question on IRC:
>>
>>  I have a question about Keystone
>>  I'm looking to add support to the dashboard so that users can
>> be enabled or disabled from the dashboard
>>  but it looks like in update_user if the target user is
>> disabled a 403 is always thrown
>>  was that intentional?
>>
>> -jay
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> Confidentiality Notice: This e-mail message (including any attached or
>> embedded documents) is intended for the exclusive and confidential use of
>> the
>> individual or entity to which this message is addressed, and unless
>> otherwise
>> expressly indicated, is confidential and privileged information of
>> Rackspace.
>> Any dissemination, distribution or copying of the enclosed material is
>> prohibited.
>> If you receive this transmission in error, please notify us immediately by
>> e-mail
>> at ab...@rackspace.com, and delete the original message.
>> Your cooperation is appreciated.
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Thinking about Backups/Snapshots in Nova Volume

[Chuck Thier]

Yeah, I think you are illustrating how this generates much confusion :)

To try to be more specific, the base functionality should be:

1. Create a point in time backup of a volume
2. Create a new volume from a backup (I guess it seems reasonable to
call this a clone)

This emulates the behavior of what EC2/EBS provide with volume
snapshots.  In this scenario, a "restore" is create a new volume from
the backup, and delete the old volume.

In the Storage world, much more can generally be done with snapshots.
For example in most storage system snapshots are treated just like a
normal volume and can be mounted directly.  A snapshot is often used
when creating a backup to ensure that you have a consistent point in
time backup, which I think most of the confusion comes from.

What we finally call it doesn't matter as much to me, as long as we
paint a consistent story that isn't confusing, and that we get it in
the Openstack API.

--
Chuck

On Wed, Jul 20, 2011 at 3:33 PM, Vishvananda Ishaya
 wrote:
> In rereading this i'm noticing that you are actually suggesting alternative 
> usage:
>
> backup/clone
>
> snapshot/restore
>
> Correct?
>
> It seems like backup and snapshot are kind of interchangable.  This is quite 
> confusing, perhaps we should refer to them as:
>
> partial-snapshot
>
> whole-snapshot
>
> or something along those lines that conveys that one is a differencing image 
> and one is a copy of the entire object?
>
> On Jul 20, 2011, at 12:01 PM, Chuck Thier wrote:
>
>> At the last developers summit, it was noted by many, that the idea of
>> a volume snaphsot in the cloud is highly overloaded.  EBS uses the
>> notion of snapshots for making point in time backups of a volume that
>> can be used to create a new volume from.  These are not true snapshots
>> though from a storage world view.  Because of this I would like to
>> make the following proposal:
>>
>> Add a backup API to the Openstack API for Nova Volume.  This is to
>> provide EBS style snapshot functionality in the Openstack API.  I'm
>> proposing to name it backup instead of snapshot as that seems to
>> better describe what is happening.  It also allows room for other
>> storage backends to expose real snapshot capabilities down the road.
>>
>> In the case of Lunr, we would be making backups of volumes to swift
>> (possibly abstracted through glance in the future).
>>
>> I have started a blueprint and spec at:
>>
>> https://blueprints.launchpad.net/nova/+spec/backups-api
>> http://etherpad.openstack.org/volume-backup
>>
>> Please feel free to comment and contribute.
>>
>> --
>> Chuck
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] FW: [Netstack] Official Python version for Quantum

[Joseph Heck]

Openstack currently supports back through Python 2.6 and includes Python 2.7 - 
as far as I know, we're not aiming to support any Python 3.x versions as yet.

-joe

On Jul 20, 2011, at 1:04 PM, Debo Dutta (dedutta) wrote:
> Some of us were discussing about the official stand on what version of python 
> one should use for Diablo. The web page says 2.6.x. If folks are going to 
> test on ubuntu 11.04 etc, then I guess things need to run on 2.7.x 
> …..Clarification would be very useful.
>  
> Debo
>  
> From: Dan Wendlandt [mailto:d...@nicira.com] 
> Sent: Wednesday, July 20, 2011 1:02 PM
> To: Debo Dutta (dedutta)
> Cc: Edgar Magana (eperdomo); netst...@lists.launchpad.net
> Subject: Re: [Netstack] Official Python version for Quantum
>  
>  
> 
> On Wed, Jul 20, 2011 at 11:51 AM, Debo Dutta (dedutta)  
> wrote:
> Hi Dan
>  
> Maybe we should talk to the Openstack list too …. We know OS works fine on 
> Ubuntu 11.04 with 2.7.2 and that dev env page was written in Jan 2011 before 
> 11.04 came out. Maybe that will get updated soon!
>  
> Definitely, I'd encourage you to contact the main list.  A clarification on 
> this point would be useful.  I use 11.04 fairly frequently as well and agree 
> that I haven't seen any problems.  
>  
> dan
>  
>  
> Debo
>  
> From: netstack-bounces+dedutta=cisco@lists.launchpad.net 
> [mailto:netstack-bounces+dedutta=cisco@lists.launchpad.net] On Behalf Of 
> Dan Wendlandt
> Sent: Wednesday, July 20, 2011 10:56 AM
> To: Edgar Magana (eperdomo)
> Cc: netst...@lists.launchpad.net
> Subject: Re: [Netstack] Official Python version for Quantum
>  
> Hi Edgar,
>  
> That's a good question.  I think this is a case where we would invoke the 
> "what is the larger openstack policy?" principle.  
>  
> My understanding is that Nova assumes python 2.6.x 
> (http://wiki.openstack.org/PythonDevelopmentEnvironment), though in practice 
> I suspect a general rule would be to avoid using anything that will break in 
> python 2.7 or python 3.x if there is a reasonable alternative (hence, it 
> often works on newer versions).   
>  
> RHEL can generally be a pain with OpenStack, though I know there are people 
> working on improving the experience.  I'd probably direct this conversation 
> to the OpenStack community as a whole if you have further question or 
> specific points you'd like to bring up.  Thanks,
>  
> Dan
>  
>  
> On Wed, Jul 20, 2011 at 10:46 AM, Edgar Magana (eperdomo) 
>  wrote:
> Hello Folks,
>  
> I would like to know if we have defined an official version of Python to be 
> used on all Quantum development. Is it 2.6 or 2.7?
> Is there any place on the Quantum blueprints where we have defined the 
> supported versions of all the libraries that we are using for our development?
>  
> Thanks,
>  
> Edgar
>  
> 
> --
> Mailing list: https://launchpad.net/~netstack
> Post to : netst...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~netstack
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
> -- 
> ~~~
> Dan Wendlandt 
> Nicira Networks, Inc. 
> www.nicira.com | www.openvswitch.org
> Sr. Product Manager 
> cell: 650-906-2650
> ~~~
> 
> 
> 
> 
> -- 
> ~~~
> Dan Wendlandt 
> Nicira Networks, Inc. 
> www.nicira.com | www.openvswitch.org
> Sr. Product Manager 
> cell: 650-906-2650
> ~~~
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Thinking about Backups/Snapshots in Nova Volume

[Vishvananda Ishaya]

In rereading this i'm noticing that you are actually suggesting alternative 
usage:

backup/clone

snapshot/restore

Correct?

It seems like backup and snapshot are kind of interchangable.  This is quite 
confusing, perhaps we should refer to them as:

partial-snapshot

whole-snapshot

or something along those lines that conveys that one is a differencing image 
and one is a copy of the entire object?

On Jul 20, 2011, at 12:01 PM, Chuck Thier wrote:

> At the last developers summit, it was noted by many, that the idea of
> a volume snaphsot in the cloud is highly overloaded.  EBS uses the
> notion of snapshots for making point in time backups of a volume that
> can be used to create a new volume from.  These are not true snapshots
> though from a storage world view.  Because of this I would like to
> make the following proposal:
> 
> Add a backup API to the Openstack API for Nova Volume.  This is to
> provide EBS style snapshot functionality in the Openstack API.  I'm
> proposing to name it backup instead of snapshot as that seems to
> better describe what is happening.  It also allows room for other
> storage backends to expose real snapshot capabilities down the road.
> 
> In the case of Lunr, we would be making backups of volumes to swift
> (possibly abstracted through glance in the future).
> 
> I have started a blueprint and spec at:
> 
> https://blueprints.launchpad.net/nova/+spec/backups-api
> http://etherpad.openstack.org/volume-backup
> 
> Please feel free to comment and contribute.
> 
> --
> Chuck
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] FW: [Netstack] Official Python version for Quantum

[Debo Dutta (dedutta)]

Hi 

 

Some of us were discussing about the official stand on what version of
python one should use for Diablo. The web page says 2.6.x. If folks are
going to test on ubuntu 11.04 etc, then I guess things need to run on
2.7.x .Clarification would be very useful. 

 

Debo

 

From: Dan Wendlandt [mailto:d...@nicira.com] 
Sent: Wednesday, July 20, 2011 1:02 PM
To: Debo Dutta (dedutta)
Cc: Edgar Magana (eperdomo); netst...@lists.launchpad.net
Subject: Re: [Netstack] Official Python version for Quantum

 

 

On Wed, Jul 20, 2011 at 11:51 AM, Debo Dutta (dedutta)
 wrote:

Hi Dan 

 

Maybe we should talk to the Openstack list too  We know OS works
fine on Ubuntu 11.04 with 2.7.2 and that dev env page was written in Jan
2011 before 11.04 came out. Maybe that will get updated soon!

 

Definitely, I'd encourage you to contact the main list.  A clarification
on this point would be useful.  I use 11.04 fairly frequently as well
and agree that I haven't seen any problems.  

 

dan

 

 

Debo 

 

From: netstack-bounces+dedutta=cisco@lists.launchpad.net
[mailto:netstack-bounces+dedutta 
=cisco@lists.launchpad.net] On Behalf Of Dan Wendlandt
Sent: Wednesday, July 20, 2011 10:56 AM
To: Edgar Magana (eperdomo)
Cc: netst...@lists.launchpad.net
Subject: Re: [Netstack] Official Python version for Quantum

 

Hi Edgar,

 

That's a good question.  I think this is a case where we would
invoke the "what is the larger openstack policy?" principle.  

 

My understanding is that Nova assumes python 2.6.x
(http://wiki.openstack.org/PythonDevelopmentEnvironment), though in
practice I suspect a general rule would be to avoid using anything that
will break in python 2.7 or python 3.x if there is a reasonable
alternative (hence, it often works on newer versions).   

 

RHEL can generally be a pain with OpenStack, though I know there
are people working on improving the experience.  I'd probably direct
this conversation to the OpenStack community as a whole if you have
further question or specific points you'd like to bring up.  Thanks,

 

Dan

 

 

On Wed, Jul 20, 2011 at 10:46 AM, Edgar Magana (eperdomo)
 wrote:

Hello Folks,

 

I would like to know if we have defined an official version of
Python to be used on all Quantum development. Is it 2.6 or 2.7?

Is there any place on the Quantum blueprints where we have
defined the supported versions of all the libraries that we are using
for our development?

 

Thanks,

 

Edgar

 


--
Mailing list: https://launchpad.net/~netstack
Post to : netst...@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help   : https://help.launchpad.net/ListHelp




-- 
~~~
Dan Wendlandt 
Nicira Networks, Inc. 
www.nicira.com | www.openvswitch.org
Sr. Product Manager 
cell: 650-906-2650
~~~




-- 
~~~
Dan Wendlandt 
Nicira Networks, Inc. 
www.nicira.com | www.openvswitch.org
Sr. Product Manager 
cell: 650-906-2650
~~~

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Thinking about Backups/Snapshots in Nova Volume

[Vishvananda Ishaya]

Can we clarify this a bit?

I see there are two functionalities:

backup / restore

this allows you to do an in place backup of an object, restore brings back the 
state in place

(internally the backup can be local or remote, but for effeciency would 
probably be something like a difference image)

snapshot / clone

this allows you to take the object and save its state.  You can't restore the 
object in place, but you can create a new object that is a clone of the old 
object.

Does this functionality line up with with what you are suggesting?

i think in general there should be a way to turn a backup into a snapshot as 
well, so you could create a new object from a backup

Vish

On Jul 20, 2011, at 12:01 PM, Chuck Thier wrote:

> At the last developers summit, it was noted by many, that the idea of
> a volume snaphsot in the cloud is highly overloaded.  EBS uses the
> notion of snapshots for making point in time backups of a volume that
> can be used to create a new volume from.  These are not true snapshots
> though from a storage world view.  Because of this I would like to
> make the following proposal:
> 
> Add a backup API to the Openstack API for Nova Volume.  This is to
> provide EBS style snapshot functionality in the Openstack API.  I'm
> proposing to name it backup instead of snapshot as that seems to
> better describe what is happening.  It also allows room for other
> storage backends to expose real snapshot capabilities down the road.
> 
> In the case of Lunr, we would be making backups of volumes to swift
> (possibly abstracted through glance in the future).
> 
> I have started a blueprint and spec at:
> 
> https://blueprints.launchpad.net/nova/+spec/backups-api
> http://etherpad.openstack.org/volume-backup
> 
> Please feel free to comment and contribute.
> 
> --
> Chuck
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Keystone] Question from mgius on IRC about update_user API call

[Yogi Srikrishnan]

Right now the code to update doesn't allow the operation if the user is 
disabled as there is a separate call to enable/disable user ie 
/users/userId/enabled .That call should allow the enabling/disabling of user 
independent of his current status. 
Regards
Yogeshwar Srikrishnan
Rackspace


From: openstack-bounces+yogesh.srikrishnan=rackspace@lists.launchpad.net 
[openstack-bounces+yogesh.srikrishnan=rackspace@lists.launchpad.net] on 
behalf of Jay Pipes [jaypi...@gmail.com]
Sent: Wednesday, July 20, 2011 1:54 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] [Keystone] Question from mgius on IRC about update_user
API call

Keystone devs,

mgius had a question on IRC:

 I have a question about Keystone
 I'm looking to add support to the dashboard so that users can
be enabled or disabled from the dashboard
 but it looks like in update_user if the target user is
disabled a 403 is always thrown
 was that intentional?

-jay

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace. 
Any dissemination, distribution or copying of the enclosed material is 
prohibited.
If you receive this transmission in error, please notify us immediately by 
e-mail
at ab...@rackspace.com, and delete the original message. 
Your cooperation is appreciated.


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [Keystone] Question from mgius on IRC about update_user API call

[Jay Pipes]

Keystone devs,

mgius had a question on IRC:

 I have a question about Keystone
 I'm looking to add support to the dashboard so that users can
be enabled or disabled from the dashboard
 but it looks like in update_user if the target user is
disabled a 403 is always thrown
 was that intentional?

-jay

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Thinking about Backups/Snapshots in Nova Volume

[Chuck Thier]

At the last developers summit, it was noted by many, that the idea of
a volume snaphsot in the cloud is highly overloaded.  EBS uses the
notion of snapshots for making point in time backups of a volume that
can be used to create a new volume from.  These are not true snapshots
though from a storage world view.  Because of this I would like to
make the following proposal:

Add a backup API to the Openstack API for Nova Volume.  This is to
provide EBS style snapshot functionality in the Openstack API.  I'm
proposing to name it backup instead of snapshot as that seems to
better describe what is happening.  It also allows room for other
storage backends to expose real snapshot capabilities down the road.

In the case of Lunr, we would be making backups of volumes to swift
(possibly abstracted through glance in the future).

I have started a blueprint and spec at:

https://blueprints.launchpad.net/nova/+spec/backups-api
http://etherpad.openstack.org/volume-backup

Please feel free to comment and contribute.

--
Chuck

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Request for review on merge proposal

[Jay Pipes]

Doh! Sorry, Rohit!

On Wed, Jul 20, 2011 at 2:04 PM, Rohit Karajgi
 wrote:
> The correct branch URL is:
>
> https://code.launchpad.net/~rohitkarajgi/nova/libvirt_unittests/+merge/68144
>
> Thanks,
> Rohit
>
> -Original Message-
> From: openstack-bounces+rohit.karajgi=vertex.co...@lists.launchpad.net 
> [mailto:openstack-bounces+rohit.karajgi=vertex.co...@lists.launchpad.net] On 
> Behalf Of Jay Pipes
> Sent: Wednesday, July 20, 2011 8:39 PM
> To: openstack@lists.launchpad.net
> Subject: [Openstack] Request for review on merge proposal
>
> Hi Nova-core, all,
>
> Rohit has asked for a review on his merge proposal. Please feel free to 
> oblige him.
>
> https://code.launchpad.net/~tpatil/nova/add-options-network-create-os-apis/+merge/68292
>
> Thanks,
> jay
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Request for review on merge proposal

[Rohit Karajgi]

The correct branch URL is: 

https://code.launchpad.net/~rohitkarajgi/nova/libvirt_unittests/+merge/68144

Thanks,
Rohit

-Original Message-
From: openstack-bounces+rohit.karajgi=vertex.co...@lists.launchpad.net 
[mailto:openstack-bounces+rohit.karajgi=vertex.co...@lists.launchpad.net] On 
Behalf Of Jay Pipes
Sent: Wednesday, July 20, 2011 8:39 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] Request for review on merge proposal

Hi Nova-core, all,

Rohit has asked for a review on his merge proposal. Please feel free to oblige 
him.

https://code.launchpad.net/~tpatil/nova/add-options-network-create-os-apis/+merge/68292

Thanks,
jay

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Host filter Instance Type Filter with virt layer Libvirt

[edouard1.thuleau]

Hi Lorin,

Thanks to point me the branch. I messed it. So you set the memory in Mb and 
disk in Kb.

I have questions:

1)  The method 'update_status' in class HostState doesn't return anything, 
so why method 'update_host_status' in class 'LibvirtConnection'  return it ?

2)  I made this change on my testing infrastructure. I set a parent zone 
without compute workers, a child zone with compute worker. When the parent zone 
ask child to return weights list of compute hosts, the child reserved (the 
method '_schedule' in class 'ZoneAwareScheduler' calls 'consume_resources' on 
each asked hosts) the resources for the instance while it doesn't know if it 
will be selected. Do you meet that problem ?
Édouard.

De : Lorin Hochstein [mailto:lo...@isi.edu]
Envoyé : mercredi 20 juillet 2011 17:44
À : THULEAU Edouard NRS
Cc : openstack@lists.launchpad.net
Objet : Re: [Openstack] Host filter Instance Type Filter with virt layer Libvirt

Edouard:

There's another branch that has this code added to the libvirt layer, which has 
already been proposed for merge. I need to make some minor fixes, but once I 
do, I think it will be approved for merge.

Here's the merge proposal: 
https://code.launchpad.net/~usc-isi/nova/extra_specs_sched/+merge/65980

Lorin
--
Lorin Hochstein, Computer Scientist
USC Information Sciences Institute
703.812.3710
http://www.east.isi.edu/~lorin

On Jul 20, 2011, at 11:15 AM, 
mailto:edouard1.thul...@orange-ftgroup.com>>
 wrote:


Hi,

I try to add code to the Libvirt layer to enable the Instance Type Filter 
needed by the zone aware scheduler.
I looked the code of fake virt layer which implement that. The table 
'host_status' in class 'FakeConnection' contains all capabilities of the host:

self.host_status = {
  'host_name-description': 'Fake Host',
  'host_hostname': 'fake-mini',
  'host_memory_total': 80,
  'host_memory_overhead': 1000,
  'host_memory_free': 79,
  'host_memory_free_computed': 79,
  'host_other_config': {},
  'host_ip_address': '192.168.1.109',
  'host_cpu_info': {},
  'disk_available': 5000,
  'disk_total': 6000,
  'disk_used': 1000,
  'host_uuid': 'cedb9b39-9388-41df-8891-c5c9a0c0fe5f',
 'host_name_label': 'fake-mini'
}

Nothing explain what corresponding each elements of this table and what unit 
use. I suppose, the unit is bytes for disk and memory.
And in the code of the host filtering in the scheduler 
(nova/scheduler/host_filter.py method class 'InstanceTypeFilter' method 
'host_filtrer'), the scheduler compares the host capabilities with specified 
resources of the instance to determined which host can support it. But 
specified resources of the instance is in Mbytes for memory and Gbytes for the 
disk. Is it normal ?

Édouard.



IMPORTANT.Les informations contenues dans ce message electronique y compris les 
fichiers attaches sont strictement confidentielles

et peuvent etre protegees par la loi.

Ce message electronique est destine exclusivement au(x) destinataire(s) 
mentionne(s) ci-dessus.

Si vous avez recu ce message par erreur ou s il ne vous est pas destine, 
veuillez immediatement le signaler  a l expediteur et effacer ce message

et tous les fichiers eventuellement attaches.

Toute lecture, exploitation ou transmission des informations contenues dans ce 
message est interdite.

Tout message electronique est susceptible d alteration.

A ce titre, le Groupe France Telecom decline toute responsabilite notamment s 
il a ete altere, deforme ou falsifie.

De meme, il appartient au destinataire de s assurer de l absence de tout virus.



IMPORTANT.This e-mail message and any attachments are strictly confidential and 
may be protected by law. This message is

intended only for the named recipient(s) above.

If you have received this message in error, or are not the named recipient(s), 
please immediately notify the sender and delete this e-mail message.

Any unauthorized view, usage or disclosure ofthis message is prohibited.

Since e-mail messages may not be reliable, France Telecom Group shall not be 
liable for any message if modified, changed or falsified.

Additionally the recipient should ensure they are actually virus free.


___
Mailing list: https://launchpad.net/~openstack
Post to : 
openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp



IMPORTANT.Les informations contenues dans ce message electronique y compris les 
fichiers attaches sont strictement confidentielles
et peuvent etre protegees

Re: [Openstack] Host filter Instance Type Filter with virt layer Libvirt

[Lorin Hochstein]

Edouard:

There's another branch that has this code added to the libvirt layer, which has 
already been proposed for merge. I need to make some minor fixes, but once I 
do, I think it will be approved for merge.

Here's the merge proposal: 
https://code.launchpad.net/~usc-isi/nova/extra_specs_sched/+merge/65980

Lorin
--
Lorin Hochstein, Computer Scientist
USC Information Sciences Institute
703.812.3710
http://www.east.isi.edu/~lorin

On Jul 20, 2011, at 11:15 AM,  wrote:

> Hi,
>  
> I try to add code to the Libvirt layer to enable the Instance Type Filter 
> needed by the zone aware scheduler.
> I looked the code of fake virt layer which implement that. The table 
> ‘host_status’ in class ‘FakeConnection’ contains all capabilities of the host:
>  
> self.host_status = {
>   'host_name-description': 'Fake Host',
>   'host_hostname': 'fake-mini',
>   'host_memory_total': 80,
>   'host_memory_overhead': 1000,
>   'host_memory_free': 79,
>   'host_memory_free_computed': 79,
>   'host_other_config': {},
>   'host_ip_address': '192.168.1.109',
>   'host_cpu_info': {},
>   'disk_available': 5000,
>   'disk_total': 6000,
>   'disk_used': 1000,
>   'host_uuid': 'cedb9b39-9388-41df-8891-c5c9a0c0fe5f',
>  'host_name_label': 'fake-mini'
> }
>  
> Nothing explain what corresponding each elements of this table and what unit 
> use. I suppose, the unit is bytes for disk and memory.
> And in the code of the host filtering in the scheduler 
> (nova/scheduler/host_filter.py method class ‘InstanceTypeFilter’ method 
> ‘host_filtrer’), the scheduler compares the host capabilities with specified 
> resources of the instance to determined which host can support it. But 
> specified resources of the instance is in Mbytes for memory and Gbytes for 
> the disk. Is it normal ?
>  
> Édouard.
> 
> IMPORTANT.Les informations contenues dans ce message electronique y compris 
> les fichiers attaches sont strictement confidentielles
> et peuvent etre protegees par la loi.
> Ce message electronique est destine exclusivement au(x) destinataire(s) 
> mentionne(s) ci-dessus.
> Si vous avez recu ce message par erreur ou s il ne vous est pas destine, 
> veuillez immediatement le signaler  a l expediteur et effacer ce message 
> et tous les fichiers eventuellement attaches.
> Toute lecture, exploitation ou transmission des informations contenues dans 
> ce message est interdite.
> Tout message electronique est susceptible d alteration.
> A ce titre, le Groupe France Telecom decline toute responsabilite notamment s 
> il a ete altere, deforme ou falsifie.
> De meme, il appartient au destinataire de s assurer de l absence de tout 
> virus.
> 
> IMPORTANT.This e-mail message and any attachments are strictly confidential 
> and may be protected by law. This message is
> intended only for the named recipient(s) above.
> If you have received this message in error, or are not the named 
> recipient(s), please immediately notify the sender and delete this e-mail 
> message.
> Any unauthorized view, usage or disclosure ofthis message is prohibited.
> Since e-mail messages may not be reliable, France Telecom Group shall not be 
> liable for any message if modified, changed or falsified.
> Additionally the recipient should ensure they are actually virus free.
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Host filter Instance Type Filter with virt layer Libvirt

[edouard1.thuleau]

Hi,

I try to add code to the Libvirt layer to enable the Instance Type Filter 
needed by the zone aware scheduler.
I looked the code of fake virt layer which implement that. The table 
'host_status' in class 'FakeConnection' contains all capabilities of the host:

self.host_status = {
  'host_name-description': 'Fake Host',
  'host_hostname': 'fake-mini',
  'host_memory_total': 80,
  'host_memory_overhead': 1000,
  'host_memory_free': 79,
  'host_memory_free_computed': 79,
  'host_other_config': {},
  'host_ip_address': '192.168.1.109',
  'host_cpu_info': {},
  'disk_available': 5000,
  'disk_total': 6000,
  'disk_used': 1000,
  'host_uuid': 'cedb9b39-9388-41df-8891-c5c9a0c0fe5f',
 'host_name_label': 'fake-mini'
}

Nothing explain what corresponding each elements of this table and what unit 
use. I suppose, the unit is bytes for disk and memory.
And in the code of the host filtering in the scheduler 
(nova/scheduler/host_filter.py method class 'InstanceTypeFilter' method 
'host_filtrer'), the scheduler compares the host capabilities with specified 
resources of the instance to determined which host can support it. But 
specified resources of the instance is in Mbytes for memory and Gbytes for the 
disk. Is it normal ?

Édouard.


IMPORTANT.Les informations contenues dans ce message electronique y compris les 
fichiers attaches sont strictement confidentielles
et peuvent etre protegees par la loi.
Ce message electronique est destine exclusivement au(x) destinataire(s) 
mentionne(s) ci-dessus.
Si vous avez recu ce message par erreur ou s il ne vous est pas destine, 
veuillez immediatement le signaler  a l expediteur et effacer ce message 
et tous les fichiers eventuellement attaches.
Toute lecture, exploitation ou transmission des informations contenues dans ce 
message est interdite.
Tout message electronique est susceptible d alteration.
A ce titre, le Groupe France Telecom decline toute responsabilite notamment s 
il a ete altere, deforme ou falsifie.
De meme, il appartient au destinataire de s assurer de l absence de tout virus.

IMPORTANT.This e-mail message and any attachments are strictly confidential and 
may be protected by law. This message is
intended only for the named recipient(s) above.
If you have received this message in error, or are not the named recipient(s), 
please immediately notify the sender and delete this e-mail message.
Any unauthorized view, usage or disclosure ofthis message is prohibited.
Since e-mail messages may not be reliable, France Telecom Group shall not be 
liable for any message if modified, changed or falsified.
Additionally the recipient should ensure they are actually virus free.


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Request for review on merge proposal

[Jay Pipes]

Hi Nova-core, all,

Rohit has asked for a review on his merge proposal. Please feel free
to oblige him.

https://code.launchpad.net/~tpatil/nova/add-options-network-create-os-apis/+merge/68292

Thanks,
jay

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Host filter - Instance Type Filter with virt layer Libvirt

[Doude]

Hi,



I try to add code to the Libvirt layer to enable the Instance Type Filter
needed by the zone aware scheduler.

I looked the code of fake virt layer which implement that. The table
‘host_status’ in class ‘FakeConnection’ contains all capabilities of the
host:



self.host_status = {

  'host_name-description': 'Fake Host',

  'host_hostname': 'fake-mini',

  'host_memory_total': 80,

  'host_memory_overhead': 1000,

  'host_memory_free': 79,

  'host_memory_free_computed': 79,

  'host_other_config': {},

  'host_ip_address': '192.168.1.109',

  'host_cpu_info': {},

  'disk_available': 5000,

  'disk_total': 6000,

  'disk_used': 1000,

  'host_uuid': 'cedb9b39-9388-41df-8891-c5c9a0c0fe5f',

  'host_name_label': 'fake-mini'

}



Nothing explain what corresponding each elements of this table and what unit
use. I suppose, the unit is bytes for disk and memory.

And in the code of the host filtering in the scheduler
(nova/scheduler/host_filter.py method class ‘InstanceTypeFilter’ method
‘host_filtrer’), the scheduler compares the host capabilities with specified
resources of the instance to determined which host can support it. But
specified resources of the instance is in Mbytes for memory and Gbytes for
the disk. Is it normal ?



Doude.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Index out of range during nova-manage

[Anne Gentle]

Yes, the trunk docs show "nova-manage network create private cidr/nn" but you 
can use any word in place of private to name the network. 
Hope that gets you there.
Anne Gentle
Content Stacker
a...@openstack.org


On Jul 20, 2011, at 9:19 AM, Jay Pipes  wrote:

> FYI, the command signature was missing a network name after create...
> 
> -jay
> 
> 2011/7/20 Shehjar Tikoo :
>> Thanks. It still runs into the Index out of range error. Are there any
>> configurables we could look at to debug further?
>> 
>> -Shehjar
>> 
>> Diego Parrilla Santamaría wrote:
>>> 
>>> it seems fixed range and network size they don't match.
>>> 
>>> It seems you are running a small environment. Try with this parameters:
>>> 
>>> /usr/bin/nova-manage network create 10.0.0.0/ 8 1 255
>>> 
>>> and
>>> 
>>> --fixed_range=10.0.0.0/ 8
>>> --network_size=64
>>> 
>>> Diego
>>> 
>>> On Wed, Jul 20, 2011 at 3:00 PM, Shehjar Tikoo >> > wrote:
>>> 
>>>Hi all, I am running into a "Command failed, please check log for
>>>more info" error on running the following command:
>>> 
>>>/usr/bin/nova-manage network create 10.0.0.0/24 
>>>1 255
>>> 
>>>/var/log/nova/nova-manage.log contains the output at
>>>http://pastebin.com/HP85LKQE
>>> 
>>>The nova.conf contains;
>>>--dhcpbridge_flagfile=/etc/__nova/nova.conf
>>>--dhcpbridge=/usr/bin/nova-__dhcpbridge
>>>--logdir=/var/log/nova
>>>--state_path=/var/lib/nova
>>>--lock_path=/var/lock/nova
>>>--verbose
>>>--s3_host=192.168.1.154
>>>--rabbit_host=192.168.1.154
>>>--cc_host=192.168.1.154
>>>--ec2_url=http://192.168.1.__154:8773/services/Cloud
>>>
>>>--fixed_range=10.0.0.0/12 
>>>--network_size=8
>>>--FAKE_subdomain=ec2
>>>--routing_source_ip=192.168.1.__154
>>>--verbose
>>>--sql_connection=mysql://root:__gluster123@192.168.1.154/nova
>>>
>>>--network_manager=nova.__network.manager.FlatManager
>>> 
>>> 
>>>I am simply following the instructions in Section 3.5.2 in the
>>>Cactus compute admin guide. Appreciate any help here. Thanks.
>>>-Shehjar
>>> 
>>>_
>>>Mailing list: https://launchpad.net/~__openstack
>>>
>>>Post to : openstack@lists.launchpad.net
>>>
>>>Unsubscribe : https://launchpad.net/~__openstack
>>>
>>>More help   : https://help.launchpad.net/__ListHelp
>>>
>>> 
>>> 
>> 
>> 
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>> 
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Index out of range during nova-manage

[Shehjar Tikoo]

Yes, Got it, thanks to Jay.

Anne Gentle wrote:

Yes, the trunk docs show "nova-manage network create private cidr/nn"
but you can use any word in place of private to name the network. Hope
that gets you there. Anne Gentle Content Stacker a...@openstack.org


On Jul 20, 2011, at 9:19 AM, Jay Pipes  wrote:


FYI, the command signature was missing a network name after create...

-jay

2011/7/20 Shehjar Tikoo :

Thanks. It still runs into the Index out of range error. Are there
any configurables we could look at to debug further?

-Shehjar

Diego Parrilla Santamaría wrote:

it seems fixed range and network size they don't match.

It seems you are running a small environment. Try with this
parameters:

/usr/bin/nova-manage network create 10.0.0.0/
8 1 255

and

--fixed_range=10.0.0.0/ 8 --network_size=64

Diego

On Wed, Jul 20, 2011 at 3:00 PM, Shehjar Tikoo
mailto:shehj...@gluster.com>> wrote:

Hi all, I am running into a "Command failed, please check log for 
more info" error on running the following command:


/usr/bin/nova-manage network create 10.0.0.0/24
 1 255

/var/log/nova/nova-manage.log contains the output at 
http://pastebin.com/HP85LKQE


The nova.conf contains; 
--dhcpbridge_flagfile=/etc/__nova/nova.conf 
--dhcpbridge=/usr/bin/nova-__dhcpbridge --logdir=/var/log/nova 
--state_path=/var/lib/nova --lock_path=/var/lock/nova --verbose 
--s3_host=192.168.1.154 --rabbit_host=192.168.1.154 
--cc_host=192.168.1.154 
--ec2_url=http://192.168.1.__154:8773/services/Cloud 
 
--fixed_range=10.0.0.0/12  --network_size=8 
--FAKE_subdomain=ec2 --routing_source_ip=192.168.1.__154 --verbose
 --sql_connection=mysql://root:__gluster123@192.168.1.154/nova 
 
--network_manager=nova.__network.manager.FlatManager



I am simply following the instructions in Section 3.5.2 in the 
Cactus compute admin guide. Appreciate any help here. Thanks. 
-Shehjar


_ Mailing list:
https://launchpad.net/~__openstack 
 Post to :
openstack@lists.launchpad.net 
 Unsubscribe :
https://launchpad.net/~__openstack 
 More help   :
https://help.launchpad.net/__ListHelp 






___ Mailing list:
https://launchpad.net/~openstack Post to :
openstack@lists.launchpad.net Unsubscribe :
https://launchpad.net/~openstack More help   :
https://help.launchpad.net/ListHelp


___ Mailing list:
https://launchpad.net/~openstack Post to :
openstack@lists.launchpad.net Unsubscribe :
https://launchpad.net/~openstack More help   :
https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Index out of range during nova-manage

[Jay Pipes]

FYI, the command signature was missing a network name after create...

-jay

2011/7/20 Shehjar Tikoo :
> Thanks. It still runs into the Index out of range error. Are there any
> configurables we could look at to debug further?
>
> -Shehjar
>
> Diego Parrilla Santamaría wrote:
>>
>> it seems fixed range and network size they don't match.
>>
>> It seems you are running a small environment. Try with this parameters:
>>
>> /usr/bin/nova-manage network create 10.0.0.0/ 8 1 255
>>
>> and
>>
>> --fixed_range=10.0.0.0/ 8
>> --network_size=64
>>
>> Diego
>>
>> On Wed, Jul 20, 2011 at 3:00 PM, Shehjar Tikoo > > wrote:
>>
>>    Hi all, I am running into a "Command failed, please check log for
>>    more info" error on running the following command:
>>
>>    /usr/bin/nova-manage network create 10.0.0.0/24 
>>    1 255
>>
>>    /var/log/nova/nova-manage.log contains the output at
>>    http://pastebin.com/HP85LKQE
>>
>>    The nova.conf contains;
>>    --dhcpbridge_flagfile=/etc/__nova/nova.conf
>>    --dhcpbridge=/usr/bin/nova-__dhcpbridge
>>    --logdir=/var/log/nova
>>    --state_path=/var/lib/nova
>>    --lock_path=/var/lock/nova
>>    --verbose
>>    --s3_host=192.168.1.154
>>    --rabbit_host=192.168.1.154
>>    --cc_host=192.168.1.154
>>    --ec2_url=http://192.168.1.__154:8773/services/Cloud
>>    
>>    --fixed_range=10.0.0.0/12 
>>    --network_size=8
>>    --FAKE_subdomain=ec2
>>    --routing_source_ip=192.168.1.__154
>>    --verbose
>>    --sql_connection=mysql://root:__gluster123@192.168.1.154/nova
>>    
>>    --network_manager=nova.__network.manager.FlatManager
>>
>>
>>    I am simply following the instructions in Section 3.5.2 in the
>>    Cactus compute admin guide. Appreciate any help here. Thanks.
>>    -Shehjar
>>
>>    _
>>    Mailing list: https://launchpad.net/~__openstack
>>    
>>    Post to     : openstack@lists.launchpad.net
>>    
>>    Unsubscribe : https://launchpad.net/~__openstack
>>    
>>    More help   : https://help.launchpad.net/__ListHelp
>>    
>>
>>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Index out of range during nova-manage

[Diego Parrilla Santamaría]

mmm give our distro a try: http://www.stackops.org

But I copied the parameters from Cactus-based running system.

Cheers
Diego

2011/7/20 Shehjar Tikoo 

> Thanks. It still runs into the Index out of range error. Are there any
> configurables we could look at to debug further?
>
> -Shehjar
>
> Diego Parrilla Santamaría wrote:
>
>> it seems fixed range and network size they don't match.
>>
>> It seems you are running a small environment. Try with this parameters:
>>
>> /usr/bin/nova-manage network create 10.0.0.0/ 8 1 255
>>
>> and
>>
>> --fixed_range=10.0.0.0/ 8
>> --network_size=64
>>
>> Diego
>>
>>
>> On Wed, Jul 20, 2011 at 3:00 PM, Shehjar Tikoo > shehj...@gluster.com>> wrote:
>>
>>Hi all, I am running into a "Command failed, please check log for
>>more info" error on running the following command:
>>
>>/usr/bin/nova-manage network create 10.0.0.0/24 
>>
>>1 255
>>
>>/var/log/nova/nova-manage.log contains the output at
>>http://pastebin.com/HP85LKQE
>>
>>The nova.conf contains;
>>--dhcpbridge_flagfile=/etc/__**nova/nova.conf
>>--dhcpbridge=/usr/bin/nova-__**dhcpbridge
>>--logdir=/var/log/nova
>>--state_path=/var/lib/nova
>>--lock_path=/var/lock/nova
>>--verbose
>>--s3_host=192.168.1.154
>>--rabbit_host=192.168.1.154
>>--cc_host=192.168.1.154
>>--ec2_url=http://192.168.1.__**154:8773/services/Cloud
>>
>> 
>> >
>>--fixed_range=10.0.0.0/12 
>>
>>--network_size=8
>>--FAKE_subdomain=ec2
>>--routing_source_ip=192.168.1.**__154
>>--verbose
>>
>> --sql_connection=mysql://root:**__gluster123@192.168.1.154/**nova
>>
>> 
>> >
>>
>>--network_manager=nova.__**network.manager.FlatManager
>>
>>
>>I am simply following the instructions in Section 3.5.2 in the
>>Cactus compute admin guide. Appreciate any help here. Thanks.
>>-Shehjar
>>
>>__**___
>>Mailing list: 
>> https://launchpad.net/~__**openstack
>>
>> >
>>Post to : openstack@lists.launchpad.net
>>> >
>>
>>Unsubscribe : 
>> https://launchpad.net/~__**openstack
>>
>> >
>>More help   : 
>> https://help.launchpad.net/__**ListHelp
>>
>> 
>> >
>>
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Openstack-operators] FLAG --start_guests_on_host_boot=true

[Diego Parrilla Santamaría]

We are testing this flag for the 0.3 version of the Stackops Distro. Our
goal is to restart the VMs in a different compute-node if a server fails
automatically.


On Wed, Jul 20, 2011 at 1:08 AM, Vishvananda Ishaya
wrote:

> Hmm, this flag needs to be set when the instance is created, so it will
> only work for new instances.
>
> I'm not sure if this flag was in cactus or not.
>
> As a workaround, you can manually turn on autostart for the domains using
> virsh on the compute host
> virsh autostart instance-0001 (for example)
>
> Vish
>
> On Jul 15, 2011, at 7:13 AM, Leandro Reox wrote:
>
> HI all,
>
> Cant find any reference about this flag on the openstack docs 
> --start_guests_on_host_boot=true,
> is really available ? If so, even if i setted up on hthe compute nova.conf,
> doesnt restart instances at node reboot Using Cactus by now Any clues ?
> Regards ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Openstack-operators mailing list
> openstack-operat...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Openstack-operators] FLAG --start_guests_on_host_boot=true

[Leandro Reox]

Diego,

Thats the "rescue" option from Diablo, you can use this instead if youre
planing to do it with cactus :
https://github.com/Mirantis/openstack-utils/blob/master/nova-compute

Regards

2011/7/20 Diego Parrilla Santamaría 

> We are testing this flag for the 0.3 version of the Stackops Distro. Our
> goal is to restart the VMs in a different compute-node if a server fails
> automatically.
>
>
> On Wed, Jul 20, 2011 at 1:08 AM, Vishvananda Ishaya  > wrote:
>
>> Hmm, this flag needs to be set when the instance is created, so it will
>> only work for new instances.
>>
>> I'm not sure if this flag was in cactus or not.
>>
>> As a workaround, you can manually turn on autostart for the domains using
>> virsh on the compute host
>> virsh autostart instance-0001 (for example)
>>
>> Vish
>>
>> On Jul 15, 2011, at 7:13 AM, Leandro Reox wrote:
>>
>> HI all,
>>
>> Cant find any reference about this flag on the openstack docs 
>> --start_guests_on_host_boot=true,
>> is really available ? If so, even if i setted up on hthe compute nova.conf,
>> doesnt restart instances at node reboot Using Cactus by now Any clues ?
>> Regards ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> ___
>> Openstack-operators mailing list
>> openstack-operat...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Index out of range during nova-manage

[Shehjar Tikoo]

Thanks. It still runs into the Index out of range error. Are there any 
configurables we could look at to debug further?


-Shehjar

Diego Parrilla Santamaría wrote:

it seems fixed range and network size they don't match.

It seems you are running a small environment. Try with this parameters:

/usr/bin/nova-manage network create 10.0.0.0/ 8 1 255

and

--fixed_range=10.0.0.0/ 8
--network_size=64

Diego

On Wed, Jul 20, 2011 at 3:00 PM, Shehjar Tikoo > wrote:


Hi all, I am running into a "Command failed, please check log for
more info" error on running the following command:

/usr/bin/nova-manage network create 10.0.0.0/24 
1 255

/var/log/nova/nova-manage.log contains the output at
http://pastebin.com/HP85LKQE

The nova.conf contains;
--dhcpbridge_flagfile=/etc/__nova/nova.conf
--dhcpbridge=/usr/bin/nova-__dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--verbose
--s3_host=192.168.1.154
--rabbit_host=192.168.1.154
--cc_host=192.168.1.154
--ec2_url=http://192.168.1.__154:8773/services/Cloud

--fixed_range=10.0.0.0/12 
--network_size=8
--FAKE_subdomain=ec2
--routing_source_ip=192.168.1.__154
--verbose
--sql_connection=mysql://root:__gluster123@192.168.1.154/nova

--network_manager=nova.__network.manager.FlatManager


I am simply following the instructions in Section 3.5.2 in the
Cactus compute admin guide. Appreciate any help here. Thanks.
-Shehjar

_
Mailing list: https://launchpad.net/~__openstack

Post to : openstack@lists.launchpad.net

Unsubscribe : https://launchpad.net/~__openstack

More help   : https://help.launchpad.net/__ListHelp






___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Openstack-operators] FLAG --start_guests_on_host_boot=true

[Diego Parrilla Santamaría]

Yes, 0.3 will be based in Diablo.

2011/7/20 Leandro Reox 

> Diego,
>
> Thats the "rescue" option from Diablo, you can use this instead if youre
> planing to do it with cactus :
> https://github.com/Mirantis/openstack-utils/blob/master/nova-compute
>
> Regards
>
>
> 2011/7/20 Diego Parrilla Santamaría 
>
>> We are testing this flag for the 0.3 version of the Stackops Distro. Our
>> goal is to restart the VMs in a different compute-node if a server fails
>> automatically.
>>
>>
>> On Wed, Jul 20, 2011 at 1:08 AM, Vishvananda Ishaya <
>> vishvana...@gmail.com> wrote:
>>
>>> Hmm, this flag needs to be set when the instance is created, so it will
>>> only work for new instances.
>>>
>>> I'm not sure if this flag was in cactus or not.
>>>
>>> As a workaround, you can manually turn on autostart for the domains using
>>> virsh on the compute host
>>> virsh autostart instance-0001 (for example)
>>>
>>> Vish
>>>
>>> On Jul 15, 2011, at 7:13 AM, Leandro Reox wrote:
>>>
>>> HI all,
>>>
>>> Cant find any reference about this flag on the openstack docs 
>>> --start_guests_on_host_boot=true,
>>> is really available ? If so, even if i setted up on hthe compute nova.conf,
>>> doesnt restart instances at node reboot Using Cactus by now Any clues ?
>>> Regards ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>>> ___
>>> Openstack-operators mailing list
>>> openstack-operat...@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Index out of range during nova-manage

[Diego Parrilla Santamaría]

it seems fixed range and network size they don't match.

It seems you are running a small environment. Try with this parameters:

/usr/bin/nova-manage network create 10.0.0.0/ 8 1 255

and

--fixed_range=10.0.0.0/ 8
--network_size=64

Diego

On Wed, Jul 20, 2011 at 3:00 PM, Shehjar Tikoo  wrote:

> Hi all, I am running into a "Command failed, please check log for more
> info" error on running the following command:
>
> /usr/bin/nova-manage network create 10.0.0.0/24 1 255
>
> /var/log/nova/nova-manage.log contains the output at
> http://pastebin.com/HP85LKQE
>
> The nova.conf contains;
> --dhcpbridge_flagfile=/etc/**nova/nova.conf
> --dhcpbridge=/usr/bin/nova-**dhcpbridge
> --logdir=/var/log/nova
> --state_path=/var/lib/nova
> --lock_path=/var/lock/nova
> --verbose
> --s3_host=192.168.1.154
> --rabbit_host=192.168.1.154
> --cc_host=192.168.1.154
> --ec2_url=http://192.168.1.**154:8773/services/Cloud
> --fixed_range=10.0.0.0/12
> --network_size=8
> --FAKE_subdomain=ec2
> --routing_source_ip=192.168.1.**154
> --verbose
> --sql_connection=mysql://root:**gluster123@192.168.1.154/nova
> --network_manager=nova.**network.manager.FlatManager
>
>
> I am simply following the instructions in Section 3.5.2 in the Cactus
> compute admin guide. Appreciate any help here. Thanks.
> -Shehjar
>
> __**_
> Mailing list: 
> https://launchpad.net/~**openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : 
> https://launchpad.net/~**openstack
> More help   : 
> https://help.launchpad.net/**ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] FLAG --start_guests_on_host_boot=true

[Leandro Reox]

Vish,

I tried that out, and you were right, instances created after adding the
flag, autoreboots themselves like charm !

Best regards

On Wed, Jul 20, 2011 at 9:31 AM, Leandro Reox wrote:

> Virsh,
>
> I was trying with my already spawned instances, thats good to know ! Ill
> try that in a few minutes
>
> Best Regards
>
>
> On Tue, Jul 19, 2011 at 8:08 PM, Vishvananda Ishaya  > wrote:
>
>> Hmm, this flag needs to be set when the instance is created, so it will
>> only work for new instances.
>>
>> I'm not sure if this flag was in cactus or not.
>>
>> As a workaround, you can manually turn on autostart for the domains using
>> virsh on the compute host
>> virsh autostart instance-0001 (for example)
>>
>> Vish
>>
>> On Jul 15, 2011, at 7:13 AM, Leandro Reox wrote:
>>
>> HI all,
>>
>> Cant find any reference about this flag on the openstack docs 
>> --start_guests_on_host_boot=true,
>> is really available ? If so, even if i setted up on hthe compute nova.conf,
>> doesnt restart instances at node reboot Using Cactus by now Any clues ?
>> Regards ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Index out of range during nova-manage

[Shehjar Tikoo]

Hi all, I am running into a "Command failed, please check log for more 
info" error on running the following command:


/usr/bin/nova-manage network create 10.0.0.0/24 1 255

/var/log/nova/nova-manage.log contains the output at 
http://pastebin.com/HP85LKQE


The nova.conf contains;
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--verbose
--s3_host=192.168.1.154
--rabbit_host=192.168.1.154
--cc_host=192.168.1.154
--ec2_url=http://192.168.1.154:8773/services/Cloud
--fixed_range=10.0.0.0/12
--network_size=8
--FAKE_subdomain=ec2
--routing_source_ip=192.168.1.154
--verbose
--sql_connection=mysql://root:gluster123@192.168.1.154/nova
--network_manager=nova.network.manager.FlatManager


I am simply following the instructions in Section 3.5.2 in the Cactus 
compute admin guide. Appreciate any help here. Thanks.

-Shehjar

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] FLAG --start_guests_on_host_boot=true

[Leandro Reox]

Virsh,

I was trying with my already spawned instances, thats good to know ! Ill try
that in a few minutes

Best Regards

On Tue, Jul 19, 2011 at 8:08 PM, Vishvananda Ishaya
wrote:

> Hmm, this flag needs to be set when the instance is created, so it will
> only work for new instances.
>
> I'm not sure if this flag was in cactus or not.
>
> As a workaround, you can manually turn on autostart for the domains using
> virsh on the compute host
> virsh autostart instance-0001 (for example)
>
> Vish
>
> On Jul 15, 2011, at 7:13 AM, Leandro Reox wrote:
>
> HI all,
>
> Cant find any reference about this flag on the openstack docs 
> --start_guests_on_host_boot=true,
> is really available ? If so, even if i setted up on hthe compute nova.conf,
> doesnt restart instances at node reboot Using Cactus by now Any clues ?
> Regards ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Single server install script errors out on ubuntu 10.4+

[Shehjar Tikoo]

Ok, looks like the machine was reconfiged by someone else. This is fixed. 
Thanks


Shehjar Tikoo wrote:

Hi all,

On running:

./nova.sh install

The installation errors out giving the following errors:
http://pastebin.com/SK0YhDst

I am following the instructions at:
http://wiki.openstack.org/NovaInstall/DevInstallScript

using the script:
https://raw.github.com/cloudbuilders/deploy.sh/master/nova.sh

Any pointers to how this can be fixed?

Thanks

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Single server install script errors out on ubuntu 10.4+

[Shehjar Tikoo]

Hi all,

On running:

./nova.sh install

The installation errors out giving the following errors:
http://pastebin.com/SK0YhDst

I am following the instructions at:
http://wiki.openstack.org/NovaInstall/DevInstallScript

using the script:
https://raw.github.com/cloudbuilders/deploy.sh/master/nova.sh

Any pointers to how this can be fixed?

Thanks

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp