[Openstack] To add a "project manager" role

[SpringWind Lee]

Hello，everyone!
I’d like to add a “project manager” role, which has the privilege to
CRUD project users and images in the project he owns.
In the keystone, lots of the authenticate is implemented by the
is_admin() function, so is it appropriate to add a is_pm()?
Do you have any good suggestions?

___
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] Being pedantic about pedanticism: HACKING styleguide

[Andy Smith]

On Thu, Mar 22, 2012 at 4:26 PM, Maru Newby  wrote:

> Hi Jay,
>
> On 2012-03-22, at 2:13 PM, Jay Pipes wrote:
>
>
> Object Imports
> ==
>
> In addition, the following DOES NOT appear in Glance's section on imports:
>
> - Do not import objects, only modules
>
> Nowhere in PEP8 does it mention anything about not importing objects. In
> fact, PEP8
>
> says this:
>
>
The rule is there because it makes it obvious where you are using objects
from (and they aren't in the current namespace), prevents that "where is
this defined -scan around the file- oh, it is being imported from this
other thing, let's go look there" pattern, instead you see very obviously
that it isn't defined in the file and usually has a unique enough name
already that you know exactly where to look.

It is something pulled from the google style guide.

>
> I'm pretty sure the reason for this rule has nothing to do with PEP8, and
> is instead intended to avoid circular imports.  I don't see the utility in
> applying the rule to 3rd party modules, since circular imports wouldn't be
> an issue, but I do consider it a best practice for project code.
>
> Cheers,
>
>
> Maru
>
> ___
> 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] Enabling remote participation at Folsom Design Summit

[hitesh wadekar]

Hello,

As we are located in India, Its very hard for us to come folosom design
summit, but we don;t want to miss this opportunity if you are going to
provide us as a online conference.

Many big firms from US use to take a call from us on webex, but that will
be good for 2 to 3 hrs. and I am expecting our design summit will be going
 through a day.

Can we get some free calling bridge number from big firm along with webex?
so that, we can easily connect that conference bridge whenever required,
also it will be easy to ask questions, suggestions etc..(Summit moderator
can take this initiative...)

Looking forward some solutions for this, so that we won't miss this
opportunity  !!!

Deepak, What is your openion on this?

Thanks,
Hitesh Wadekar

On Fri, Mar 23, 2012 at 4:38 AM, Stefano Maffulli wrote:

> On Wed, 2012-03-21 at 15:47 -0700, Debo Dutta (dedutta) wrote:
> > SW side: Another option would be to run webex meetings or even google
> > hangout!
>
> On the software side we have *plenty* of options. Webex, Justin.tv,
> ustream, g+, the great system that powered live streaming from pycon
> http://streamti.me/ ... lots of options, free as in freedom and free as
> in beer. Software is not a problem.
>
> Hardware is the first thing we need to procure before this project takes
> off.
>
> I started talking with a hardware company in the bay area, friendly to
> Linux. Hopefully we'll be able to pull it off. I'd love to have
> alternatives though, should this deal not close.
>
> Thanks,
> stef
>
>
>
>
> ___
> 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] Caching strategies in Nova ...

[Mark Washenberger]

This is precisely my concern.

It must be brought up that with Rackspace Cloud Servers, nearly
all client codes routinely submit requests with a query parameter 
"cache-busting=" just to get around problems with
cache invalidation. And woe to the client that does not.

I get the feeling that once trust like this is lost, a project has
a hard time regaining it. I'm not saying that we can avoid
inconsistency entirely. Rather, I believe we will have to embrace
some eventual-consistency models to enable the performance and
scale we will ultimately attain. But I just get the feeling that
generic caches are really only appropriate for write-once or at
least write-rarely data. So personally I would rule out external
caches entirely and try to be very judicious in selecting internal
caches as well.

"Joshua Harlow"  said:

> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> Just from experience.
> 
> They do a great job. But the killer thing about caching is how u do the cache
> invalidation.
> 
> Just caching stuff is easy-peasy, making sure it is invalidated on all 
> servers in
> all conditions, not so easy...
> 
> On 3/22/12 4:26 PM, "Sandy Walsh"  wrote:
> 
> We're doing tests to find out where the bottlenecks are, caching is the
> most obvious solution, but there may be others. Tools like memcache do a
> really good job of sharing memory across servers so we don't have to
> reinvent the wheel or hit the db at all.
> 
> In addition to looking into caching technologies/approaches we're gluing
> together some tools for finding those bottlenecks. Our first step will
> be finding them, then squashing them ... however.
> 
> -S
> 
> On 03/22/2012 06:25 PM, Mark Washenberger wrote:
>> What problems are caching strategies supposed to solve?
>>
>> On the nova compute side, it seems like streamlining db access and
>> api-view tables would solve any performance problems caching would
>> address, while keeping the stale data management problem small.
>>
> 
> ___
> 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] Caching strategies in Nova ...

[Mark Washenberger]

Working on this independently, I created a branch with some simple
performance logging around the nova-api, and individually around 
glance, nova.db, and nova.rpc calls. (Sorry, I only have a local
copy and its on a different computer right now, and probably needs
a rebase. I will rebase and publish it on GitHub tomorrow.) 

With this logging, I could get some simple profiling that I found
very useful. Here is a GH project with the analysis code as well
as some nova-api logs I was using as input. 

https://github.com/markwash/nova-perflog

With these tools, you can get a wall-time profile for individual
requests. For example, looking at one server create request (and
you can run this directly from the checkout as the logs are saved
there):

markw@poledra:perflogs$ cat nova-api.vanilla.1.5.10.log | python 
profile-request.py req-3cc0fe84-e736-4441-a8d6-ef605558f37f
keycountavg
nova.api.openstack.wsgi.POST   1  0.657
nova.db.api.instance_update1  0.191
nova.image.show1  0.179
nova.db.api.instance_add_security_group1  0.082
nova.rpc.cast  1  0.059
nova.db.api.instance_get_all_by_filters1  0.034
nova.db.api.security_group_get_by_name 2  0.029
nova.db.api.instance_create1  0.011
nova.db.api.quota_get_all_by_project   3  0.003
nova.db.api.instance_data_get_for_project  1  0.003

key  count  total
nova.api.openstack.wsgi  1  0.657
nova.db.api 10  0.388
nova.image   1  0.179
nova.rpc 1  0.059

All times are in seconds. The nova.rpc time is probably high
since this was the first call since server restart, so the
connection handshake is probably included. This is also probably
1.5 months stale.

The conclusion I reached from this profiling is that we just plain
overuse the db (and we might do the same in glance). For example,
whenever we do updates, we actually re-retrieve the item from the
database, update its dictionary, and save it. This is double the
cost it needs to be. We also handle updates for data across tables
inefficiently, where they could be handled in single database round
trip.

In particular, in the case of server listings, extensions are just
rough on performance. Most extensions hit the database again
at least once. This isn't really so bad, but it clearly is an area
where we should improve, since these are the most frequent api
queries.

I just see a ton of specific performance problems that are easier
to address one by one, rather than diving into a general (albeit
obvious) solution such as caching.


"Sandy Walsh"  said:

> We're doing tests to find out where the bottlenecks are, caching is the
> most obvious solution, but there may be others. Tools like memcache do a
> really good job of sharing memory across servers so we don't have to
> reinvent the wheel or hit the db at all.
> 
> In addition to looking into caching technologies/approaches we're gluing
> together some tools for finding those bottlenecks. Our first step will
> be finding them, then squashing them ... however.
> 
> -S
> 
> On 03/22/2012 06:25 PM, Mark Washenberger wrote:
>> What problems are caching strategies supposed to solve?
>>
>> On the nova compute side, it seems like streamlining db access and
>> api-view tables would solve any performance problems caching would
>> address, while keeping the stale data management problem small.
>>
> 
> ___
> 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] Caching strategies in Nova ...

[Joshua Harlow]

Just from experience.

They do a great job. But the killer thing about caching is how u do the cache 
invalidation.

Just caching stuff is easy-peasy, making sure it is invalidated on all servers 
in all conditions, not so easy...

On 3/22/12 4:26 PM, "Sandy Walsh"  wrote:

We're doing tests to find out where the bottlenecks are, caching is the
most obvious solution, but there may be others. Tools like memcache do a
really good job of sharing memory across servers so we don't have to
reinvent the wheel or hit the db at all.

In addition to looking into caching technologies/approaches we're gluing
together some tools for finding those bottlenecks. Our first step will
be finding them, then squashing them ... however.

-S

On 03/22/2012 06:25 PM, Mark Washenberger wrote:
> What problems are caching strategies supposed to solve?
>
> On the nova compute side, it seems like streamlining db access and
> api-view tables would solve any performance problems caching would
> address, while keeping the stale data management problem small.
>

___
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] Caching strategies in Nova ...

[Sandy Walsh]

We're doing tests to find out where the bottlenecks are, caching is the
most obvious solution, but there may be others. Tools like memcache do a
really good job of sharing memory across servers so we don't have to
reinvent the wheel or hit the db at all.

In addition to looking into caching technologies/approaches we're gluing
together some tools for finding those bottlenecks. Our first step will
be finding them, then squashing them ... however.

-S

On 03/22/2012 06:25 PM, Mark Washenberger wrote:
> What problems are caching strategies supposed to solve?
> 
> On the nova compute side, it seems like streamlining db access and
> api-view tables would solve any performance problems caching would
> address, while keeping the stale data management problem small.
> 

___
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] Being pedantic about pedanticism: HACKING styleguide

[Maru Newby]

Hi Jay,

On 2012-03-22, at 2:13 PM, Jay Pipes wrote:
> 
> Object Imports
> ==
> 
> In addition, the following DOES NOT appear in Glance's section on imports:
> 
> - Do not import objects, only modules
> 
> Nowhere in PEP8 does it mention anything about not importing objects. In 
> fact, PEP8 says this:

I'm pretty sure the reason for this rule has nothing to do with PEP8, and is 
instead intended to avoid circular imports.  I don't see the utility in 
applying the rule to 3rd party modules, since circular imports wouldn't be an 
issue, but I do consider it a best practice for project code.

Cheers,


Maru___
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] Enabling remote participation at Folsom Design Summit

[Stefano Maffulli]

On Wed, 2012-03-21 at 15:47 -0700, Debo Dutta (dedutta) wrote:
> SW side: Another option would be to run webex meetings or even google
> hangout!  

On the software side we have *plenty* of options. Webex, Justin.tv,
ustream, g+, the great system that powered live streaming from pycon
http://streamti.me/ ... lots of options, free as in freedom and free as
in beer. Software is not a problem.

Hardware is the first thing we need to procure before this project takes
off.

I started talking with a hardware company in the bay area, friendly to
Linux. Hopefully we'll be able to pull it off. I'd love to have
alternatives though, should this deal not close. 

Thanks,
stef




___
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 client broken??

[Dolph Mathews]

For anyone following along, this is now being tracked in
https://bugs.launchpad.net/keystone/+bug/962600

On Thu, Mar 22, 2012 at 5:21 PM, Joshua Harlow wrote:

>  I’m still confused.
>
> Is there a bug in the keystone client that is causing these attributes to
> not exist?
>
> I am assuming yes, since devstack.org is doing the same calls.
>
> https://github.com/openstack-dev/devstack/blob/master/eucarc#L22
>
> Which should blow up in the same place.
>
> Thx for the explanation though.
>
>
> On 3/22/12 3:16 PM, "Jesse Andrews"  wrote:
>
> With *all* services, if you know the endpoint you can query them
> directly with the auth mechanism (either token or ec2 access/secret).
>
> OpenStack has an identity service (keystone) that returns a catalog of
> services (for discovery)
>
> You don't need to look at the catalog if you know the endpoints.
>
> Just set the AWS endpoint how you would normally.
>
> That said: horizon can build a eucarc that has an access/secret & ec2
> endpoint for you.  It does so by doing the same thing devstack does:
>
>   * looks in the catalog for the ec2 endpoint, and writes it the file
>   * requests an access/secret for a user from keystone.
>
> If you have all that, you can skip ahead to go :) and use your tools.
>
> The assumption is a user of an openstack cloud would need to determine
> those things, and we expose them in keystone (discovery and
> tokens/access/secrets)
>
> Jesse
>
> On Thu, Mar 22, 2012 at 1:39 PM, Joshua Harlow 
> wrote:
> > I’m confused.
> >
> > So this means ec2 won’t work because it can’t have a service catalog?
> >
> > All of those variables should of been set:
> >
> > export OS_AUTH_URL=http://172.21.102.236:5000/v2.0
> > export OS_PASSWORD=ac31bec851146d3c7f00
> > export OS_TENANT_NAME=demo
> > export OS_USERNAME=demo
> >
> >
> > On 3/22/12 1:39 PM, "Dolph Mathews"  wrote:
> >
> > Accidentally hit send...
> >
> > Anyway... which does not necessarily correspond to a normal user with a
> > service catalog.
> >
> > The error message should explain this and direct you to use an
> OS_USERNAME,
> > OS_PASSWORD, OS_TENANT_* and OS_AUTH_URL instead (which can have a
> service
> > catalog).
> >
> > -Dolph Mathews
> >
> > On Mar 22, 2012, at 1:42 PM, Joshua Harlow 
> wrote:
> >
> > Keystone client broken?? Hi all,
> >
> >
> > When trying to use eucarc
> > (https://github.com/openstack-dev/devstack/blob/master/eucarc) or the
> > devstackPY copy called euca.sh (
> > https://github.com/yahoo/Openstack-DevstackPy/blob/master/euca.sh )
> >
> > I am getting the following:
> >
> > ++ keystone catalog --service ec2
> > ++ awk '/ publicURL / { print $4 }'
> > 'Client' object has no attribute 'service_catalog'
> > + export EC2_URL=
> > + EC2_URL=
> > ++ keystone ec2-credentials-create
> > 'Client' object has no attribute 'auth_tenant_id'
> > + CREDS=
> > ++ echo ''
> > ++ awk '/ access / { print $4 }'
> > + export EC2_ACCESS_KEY=
> > + EC2_ACCESS_KEY=
> > ++ echo ''
> > ++ awk '/ secret / { print $4 }'
> > + export EC2_SECRET_KEY=
> > + EC2_SECRET_KEY=
> > + NOVA_KEY_DIR=
> > ++ keystone catalog --service s3
> > ++ awk '/ publicURL / { print $4 }'
> > 'Client' object has no attribute 'service_catalog'
> >
> > Has there been some changes that are causing this??
> >
> > Seems like maybe the keystone client is not working anymore?
> >
> > -Josh
> >
> > ___
> > 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] Keystone client broken??

[Joshua Harlow]

I'm still confused.

Is there a bug in the keystone client that is causing these attributes to not 
exist?

I am assuming yes, since devstack.org is doing the same calls.

https://github.com/openstack-dev/devstack/blob/master/eucarc#L22

Which should blow up in the same place.

Thx for the explanation though.

On 3/22/12 3:16 PM, "Jesse Andrews"  wrote:

With *all* services, if you know the endpoint you can query them
directly with the auth mechanism (either token or ec2 access/secret).

OpenStack has an identity service (keystone) that returns a catalog of
services (for discovery)

You don't need to look at the catalog if you know the endpoints.

Just set the AWS endpoint how you would normally.

That said: horizon can build a eucarc that has an access/secret & ec2
endpoint for you.  It does so by doing the same thing devstack does:

  * looks in the catalog for the ec2 endpoint, and writes it the file
  * requests an access/secret for a user from keystone.

If you have all that, you can skip ahead to go :) and use your tools.

The assumption is a user of an openstack cloud would need to determine
those things, and we expose them in keystone (discovery and
tokens/access/secrets)

Jesse

On Thu, Mar 22, 2012 at 1:39 PM, Joshua Harlow  wrote:
> I'm confused.
>
> So this means ec2 won't work because it can't have a service catalog?
>
> All of those variables should of been set:
>
> export OS_AUTH_URL=http://172.21.102.236:5000/v2.0
> export OS_PASSWORD=ac31bec851146d3c7f00
> export OS_TENANT_NAME=demo
> export OS_USERNAME=demo
>
>
> On 3/22/12 1:39 PM, "Dolph Mathews"  wrote:
>
> Accidentally hit send...
>
> Anyway... which does not necessarily correspond to a normal user with a
> service catalog.
>
> The error message should explain this and direct you to use an OS_USERNAME,
> OS_PASSWORD, OS_TENANT_* and OS_AUTH_URL instead (which can have a service
> catalog).
>
> -Dolph Mathews
>
> On Mar 22, 2012, at 1:42 PM, Joshua Harlow  wrote:
>
> Keystone client broken?? Hi all,
>
>
> When trying to use eucarc
> (https://github.com/openstack-dev/devstack/blob/master/eucarc) or the
> devstackPY copy called euca.sh (
> https://github.com/yahoo/Openstack-DevstackPy/blob/master/euca.sh )
>
> I am getting the following:
>
> ++ keystone catalog --service ec2
> ++ awk '/ publicURL / { print $4 }'
> 'Client' object has no attribute 'service_catalog'
> + export EC2_URL=
> + EC2_URL=
> ++ keystone ec2-credentials-create
> 'Client' object has no attribute 'auth_tenant_id'
> + CREDS=
> ++ echo ''
> ++ awk '/ access / { print $4 }'
> + export EC2_ACCESS_KEY=
> + EC2_ACCESS_KEY=
> ++ echo ''
> ++ awk '/ secret / { print $4 }'
> + export EC2_SECRET_KEY=
> + EC2_SECRET_KEY=
> + NOVA_KEY_DIR=
> ++ keystone catalog --service s3
> ++ awk '/ publicURL / { print $4 }'
> 'Client' object has no attribute 'service_catalog'
>
> Has there been some changes that are causing this??
>
> Seems like maybe the keystone client is not working anymore?
>
> -Josh
>
> ___
> 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] Keystone client broken??

[Jesse Andrews]

With *all* services, if you know the endpoint you can query them
directly with the auth mechanism (either token or ec2 access/secret).

OpenStack has an identity service (keystone) that returns a catalog of
services (for discovery)

You don't need to look at the catalog if you know the endpoints.

Just set the AWS endpoint how you would normally.

That said: horizon can build a eucarc that has an access/secret & ec2
endpoint for you.  It does so by doing the same thing devstack does:

  * looks in the catalog for the ec2 endpoint, and writes it the file
  * requests an access/secret for a user from keystone.

If you have all that, you can skip ahead to go :) and use your tools.

The assumption is a user of an openstack cloud would need to determine
those things, and we expose them in keystone (discovery and
tokens/access/secrets)

Jesse

On Thu, Mar 22, 2012 at 1:39 PM, Joshua Harlow  wrote:
> I’m confused.
>
> So this means ec2 won’t work because it can’t have a service catalog?
>
> All of those variables should of been set:
>
> export OS_AUTH_URL=http://172.21.102.236:5000/v2.0
> export OS_PASSWORD=ac31bec851146d3c7f00
> export OS_TENANT_NAME=demo
> export OS_USERNAME=demo
>
>
> On 3/22/12 1:39 PM, "Dolph Mathews"  wrote:
>
> Accidentally hit send...
>
> Anyway... which does not necessarily correspond to a normal user with a
> service catalog.
>
> The error message should explain this and direct you to use an OS_USERNAME,
> OS_PASSWORD, OS_TENANT_* and OS_AUTH_URL instead (which can have a service
> catalog).
>
> -Dolph Mathews
>
> On Mar 22, 2012, at 1:42 PM, Joshua Harlow  wrote:
>
> Keystone client broken?? Hi all,
>
>
> When trying to use eucarc
> (https://github.com/openstack-dev/devstack/blob/master/eucarc) or the
> devstackPY copy called euca.sh (
> https://github.com/yahoo/Openstack-DevstackPy/blob/master/euca.sh )
>
> I am getting the following:
>
> ++ keystone catalog --service ec2
> ++ awk '/ publicURL / { print $4 }'
> 'Client' object has no attribute 'service_catalog'
> + export EC2_URL=
> + EC2_URL=
> ++ keystone ec2-credentials-create
> 'Client' object has no attribute 'auth_tenant_id'
> + CREDS=
> ++ echo ''
> ++ awk '/ access / { print $4 }'
> + export EC2_ACCESS_KEY=
> + EC2_ACCESS_KEY=
> ++ echo ''
> ++ awk '/ secret / { print $4 }'
> + export EC2_SECRET_KEY=
> + EC2_SECRET_KEY=
> + NOVA_KEY_DIR=
> ++ keystone catalog --service s3
> ++ awk '/ publicURL / { print $4 }'
> 'Client' object has no attribute 'service_catalog'
>
> Has there been some changes that are causing this??
>
> Seems like maybe the keystone client is not working anymore?
>
> -Josh
>
> ___
> 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] boot from volume use cases

[Josh Durgin]

At the last couple volumes meetings, there was some discussion of the
desired behaviors of nova's boot from volume functionality. There were
a few use cases discussed, but there are probably plenty we didn't
think of, so it would be useful to get input from a larger audience.

What use cases for boot from volume are people interested in, and
which should nova support?

Here are a few use cases:

  1) I use an existing instance to manually create a bootable volume
 containing an OS there is no image for (and I cannot create an
 image). I boot the new OS from the volume I created.

  2) I create a bunch of new instances that have no ephemeral disks,
 but are all based on the same image. The data from the image is
 copied to a new volume for each new instance.

  3) I have an instance that has no ephemeral disks, and stores
 everything in a volume. I take periodic snapshots of the
 volume. Later, my original instance becomes corrupted, and I want
 to restore from the last known good snapshot I took. I boot a new
 instance from a new volume created by cloning from the last
 good snapshot.


___
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] Being pedantic about pedanticism: HACKING styleguide

[Andy Smith]

Oh, and we should include the file in each project with a link to whatever
the base one is.

That said, I don't intend to change the style of my project just because
the common one changes, and it shouldn't be a wiki because that makes it
too easy to change.

On Thu, Mar 22, 2012 at 3:01 PM, Andy Smith  wrote:

>
>
> On Thu, Mar 22, 2012 at 9:22 AM, Andrew Bogott wrote:
>
>>Just now I set out to merge a recent style guide change from
>> python-novaclient into the hacking docs of other OpenStack projects.  My
>> patch didn't apply, though, because each project has subtly diverging
>> HACKING files.
>>
>>Rather than contribute to this divergence, I've now read and compared
>> the style guides from Nova, Glance, Keystone, python-keystoneclient, and
>> python-novaclient.  From these diffs I've created a file (attached) that
>> encompasses the total of all guidelines from all projects.  Remarkably,
>> this merge produced only minor disagreements, described below under the
>> heading FLAMEBAIT.
>>
>>I propose that this unified style guide be copied into each of the
>> above projects, with a mandate to maintain consistency henceforth.  Any
>> objections?
>>
>> -Andrew
>>
>>
>> FLAMEBAIT (docstring format):
>>
>> The only explicit contradiction I came across is regarding docstring
>> formatting.  Glance says this:
>>
>> **DO NOT** leave an extra newline before the closing triple-double-quote.
>>
>> Nova, this:
>>
>>  A docstring ends with an empty line before the closing quotations.
>>
>> I propose that we just pick one or the other, or remove both
>> prescriptions.
>>
>
> I'm fine with moving forward to not having the trailing newline, it was
> for an emacs feature that has since become smarter (and who cares about
> emacs anyway). It is mentioned as the preferred way in PEP8, so it runs
> into some disagreements from time to time. Most of the code in the projects
> has been written with the older rule (yes on trailing newline) but I
> haven't been blocking new code from not using it.
>
>
>>
>> FLAMEBAIT (filename):
>>
>> Some projects have a HACKING file, and some have a HACKING.rst file.
>>  Doesn't .rst generally indicate a REST API definition?  I propose that the
>> file be called HACKING.
>>
>
> HACKING.rst makes github format it correctly, let's move everything to rst.
>
>
>>
>>
>> ___
>> 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] Being pedantic about pedanticism: HACKING styleguide

[Andy Smith]

On Thu, Mar 22, 2012 at 9:22 AM, Andrew Bogott wrote:

>Just now I set out to merge a recent style guide change from
> python-novaclient into the hacking docs of other OpenStack projects.  My
> patch didn't apply, though, because each project has subtly diverging
> HACKING files.
>
>Rather than contribute to this divergence, I've now read and compared
> the style guides from Nova, Glance, Keystone, python-keystoneclient, and
> python-novaclient.  From these diffs I've created a file (attached) that
> encompasses the total of all guidelines from all projects.  Remarkably,
> this merge produced only minor disagreements, described below under the
> heading FLAMEBAIT.
>
>I propose that this unified style guide be copied into each of the
> above projects, with a mandate to maintain consistency henceforth.  Any
> objections?
>
> -Andrew
>
>
> FLAMEBAIT (docstring format):
>
> The only explicit contradiction I came across is regarding docstring
> formatting.  Glance says this:
>
> **DO NOT** leave an extra newline before the closing triple-double-quote.
>
> Nova, this:
>
>  A docstring ends with an empty line before the closing quotations.
>
> I propose that we just pick one or the other, or remove both prescriptions.
>

I'm fine with moving forward to not having the trailing newline, it was for
an emacs feature that has since become smarter (and who cares about emacs
anyway). It is mentioned as the preferred way in PEP8, so it runs into some
disagreements from time to time. Most of the code in the projects has been
written with the older rule (yes on trailing newline) but I haven't been
blocking new code from not using it.


>
> FLAMEBAIT (filename):
>
> Some projects have a HACKING file, and some have a HACKING.rst file.
>  Doesn't .rst generally indicate a REST API definition?  I propose that the
> file be called HACKING.
>

HACKING.rst makes github format it correctly, let's move everything to rst.


>
>
> ___
> 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] Being pedantic about pedanticism: HACKING styleguide

[Doug Hellmann]

On Thu, Mar 22, 2012 at 4:22 PM, Jay Pipes  wrote:

> On 03/22/2012 01:47 PM, Doug Hellmann wrote:
>
>> Why are those sorts of instructions replicated in each project in the
>> first place? Shouldn't they be in the wiki?
>>
>
> :) Have you ever tried to get a dozen OpenStack contributors to agree on,
> well, anything?
>

Point taken. I was thrown off by the op's comments about merging them,
which made me think there was already consensus. :-)


>
> The reason it's duplicated in so many places is that the contributors in
> the various projects didn't agree with some of the style rules used in
> Nova...
>
> Best,
> -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

[Openstack] Warning to new Essex users

[David Kranz]

If you are trying out Essex on a single node, beware of bug 
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/959426



 nova services start before mysql on boot



 -David
___
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] Caching strategies in Nova ...

[Mark Washenberger]

What problems are caching strategies supposed to solve?

On the nova compute side, it seems like streamlining db access and
api-view tables would solve any performance problems caching would
address, while keeping the stale data management problem small.

"Sandy Walsh"  said:

> o/
> 
> Vek and myself are looking into caching strategies in and around Nova.
> 
> There are essentially two approaches: in-process and external (proxy).
> The in-process schemes sit in with the python code while the external
> ones basically proxy the the HTTP requests.
> 
> There are some obvious pro's and con's to each approach. The external is
> easier for operations to manage, but in-process allows us greater
> control over the caching (for things like caching db calls and not just
> HTTP calls). But, in-memory also means more code, more memory usage on
> the servers, monolithic services, limited to python based solutions,
> etc. In-process also gives us access to tools like Tach
> https://github.com/ohthree/tach for profiling performance.
> 
> I see Jesse recently landed a branch that touches on the in-process
> approach:
> https://github.com/openstack/nova/commit/1bcf5f5431d3c9620596f5329d7654872235c7ee#nova/common/memorycache.py
> 
> I don't know if people think putting caching code inside nova is a good
> or bad idea. If we do continue down this road, it would be nice to make
> it a little more modular/plug-in-based (YAPI .. yet another plug-in).
> Perhaps a hybrid solution is required?
> 
> We're looking at tools like memcache, beaker, varnish, etc.
> 
> Has anyone already started down this road already? Any insights to
> share? Opinions? (summit talk?)
> 
> What are Glance, Swift, Keystone (lite?) doing?
> 
> -S
> 
> ___
> 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] Being pedantic about pedanticism: HACKING styleguide

[Jay Pipes]

(in a thundering voice)

Release the Kraken!

On 03/22/2012 12:22 PM, Andrew Bogott wrote:

Just now I set out to merge a recent style guide change from
python-novaclient into the hacking docs of other OpenStack projects. My
patch didn't apply, though, because each project has subtly diverging
HACKING files.

Rather than contribute to this divergence, I've now read and compared
the style guides from Nova, Glance, Keystone, python-keystoneclient, and
python-novaclient. From these diffs I've created a file (attached) that
encompasses the total of all guidelines from all projects. Remarkably,
this merge produced only minor disagreements, described below under the
heading FLAMEBAIT.


You missed a couple things :) See below.


I propose that this unified style guide be copied into each of the above
projects, with a mandate to maintain consistency henceforth. Any
objections?


Yes. See below.


-Andrew

FLAMEBAIT (docstring format):

The only explicit contradiction I came across is regarding docstring
formatting. Glance says this:

**DO NOT** leave an extra newline before the closing triple-double-quote.


Yes, and there's a reason. The extra newline was an anachronism from 
Emacs of Old and is pointless -- it does nothing to improve readability.



Nova, this:

A docstring ends with an empty line before the closing quotations.

I propose that we just pick one or the other, or remove both prescriptions.


Well, you know which one I'm partial to. :)


FLAMEBAIT (filename):

Some projects have a HACKING file, and some have a HACKING.rst file.
Doesn't .rst generally indicate a REST API definition? I propose that
the file be called HACKING.


I changed the Glance HACKING to HACKING.rst when I saw a couple of the 
other projects do so... I could go either way.


Here are some of the other things you missed that are important differences:

Docstrings
==

Glance's HACKING section on docstrings includes these:

Docstrings should ONLY use triple-double-quotes (``"""``)

Single-line docstrings should NEVER have extraneous whitespace
between enclosing triple-double-quotes.

**INCORRECT** ::

  """ There is some whitespace between the enclosing quotes :( """

**CORRECT** ::

  """There is no whitespace between the enclosing quotes :)"""

Nova's HACKING section on docstrings also states that a docstring's 
one-line summary should end in a period, and that multi-line docstrings 
should always have a one-line summary, less than 80 characters, also 
ending in a period.


Glance's section on docstrings doesn't have this, as I believe that the 
rule on periods stretches the level of pedantry to new levels.


Object Imports
==

In addition, the following DOES NOT appear in Glance's section on imports:

- Do not import objects, only modules

Nowhere in PEP8 does it mention anything about not importing objects. In 
fact, PEP8 says this:



Imports should usually be on separate lines, e.g.:

Yes: import os
 import sys

No:  import sys, os

It's okay to say this though:

from subprocess import Popen, PIPE


In fact, many successful projects, including Django make use of 
importing objects instead of modules, so I don't see the need for that rule.


Best,
-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

Re: [Openstack] Keystone client broken??

[Joshua Harlow]

I'm confused.

So this means ec2 won't work because it can't have a service catalog?

All of those variables should of been set:

export OS_AUTH_URL=http://172.21.102.236:5000/v2.0
export OS_PASSWORD=ac31bec851146d3c7f00
export OS_TENANT_NAME=demo
export OS_USERNAME=demo

On 3/22/12 1:39 PM, "Dolph Mathews"  wrote:

Accidentally hit send...

Anyway... which does not necessarily correspond to a normal user with a service 
catalog.

The error message should explain this and direct you to use an OS_USERNAME, 
OS_PASSWORD, OS_TENANT_* and OS_AUTH_URL instead (which can have a service 
catalog).

-Dolph Mathews

On Mar 22, 2012, at 1:42 PM, Joshua Harlow  wrote:

Keystone client broken?? Hi all,

When trying to use eucarc 
(https://github.com/openstack-dev/devstack/blob/master/eucarc) or the 
devstackPY copy called euca.sh ( 
https://github.com/yahoo/Openstack-DevstackPy/blob/master/euca.sh )

I am getting the following:

++ keystone catalog --service ec2
++ awk '/ publicURL / { print $4 }'
'Client' object has no attribute 'service_catalog'
+ export EC2_URL=
+ EC2_URL=
++ keystone ec2-credentials-create
'Client' object has no attribute 'auth_tenant_id'
+ CREDS=
++ echo ''
++ awk '/ access / { print $4 }'
+ export EC2_ACCESS_KEY=
+ EC2_ACCESS_KEY=
++ echo ''
++ awk '/ secret / { print $4 }'
+ export EC2_SECRET_KEY=
+ EC2_SECRET_KEY=
+ NOVA_KEY_DIR=
++ keystone catalog --service s3
++ awk '/ publicURL / { print $4 }'
'Client' object has no attribute 'service_catalog'

Has there been some changes that are causing this??

Seems like maybe the keystone client is not working anymore?

-Josh

___
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 client broken??

[Dolph Mathews]

Accidentally hit send...

Anyway... which does not necessarily correspond to a normal user with a service 
catalog.

The error message should explain this and direct you to use an OS_USERNAME, 
OS_PASSWORD, OS_TENANT_* and OS_AUTH_URL instead (which can have a service 
catalog).

-Dolph Mathews

On Mar 22, 2012, at 1:42 PM, Joshua Harlow  wrote:

> Hi all,
> 
> When trying to use eucarc 
> (https://github.com/openstack-dev/devstack/blob/master/eucarc) or the 
> devstackPY copy called euca.sh ( 
> https://github.com/yahoo/Openstack-DevstackPy/blob/master/euca.sh )
> 
> I am getting the following:
> 
> ++ keystone catalog --service ec2
> ++ awk '/ publicURL / { print $4 }'
> 'Client' object has no attribute 'service_catalog'
> + export EC2_URL=
> + EC2_URL=
> ++ keystone ec2-credentials-create
> 'Client' object has no attribute 'auth_tenant_id'
> + CREDS=
> ++ echo ''
> ++ awk '/ access / { print $4 }'
> + export EC2_ACCESS_KEY=
> + EC2_ACCESS_KEY=
> ++ echo ''
> ++ awk '/ secret / { print $4 }'
> + export EC2_SECRET_KEY=
> + EC2_SECRET_KEY=
> + NOVA_KEY_DIR=
> ++ keystone catalog --service s3
> ++ awk '/ publicURL / { print $4 }'
> 'Client' object has no attribute 'service_catalog'
> 
> Has there been some changes that are causing this??
> 
> Seems like maybe the keystone client is not working anymore?
> 
> -Josh
> 
> ___
> 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 client broken??

[Dolph Mathews]

I'm not sure if there's an open bug on this or not (definitely should be), but 
you're attempting to perform operations using a SERVICE_TOKEN and 
SERVICE_ENDPOINT (
that require

-Dolph Mathews

On Mar 22, 2012, at 1:42 PM, Joshua Harlow  wrote:

> Hi all,
> 
> When trying to use eucarc 
> (https://github.com/openstack-dev/devstack/blob/master/eucarc) or the 
> devstackPY copy called euca.sh ( 
> https://github.com/yahoo/Openstack-DevstackPy/blob/master/euca.sh )
> 
> I am getting the following:
> 
> ++ keystone catalog --service ec2
> ++ awk '/ publicURL / { print $4 }'
> 'Client' object has no attribute 'service_catalog'
> + export EC2_URL=
> + EC2_URL=
> ++ keystone ec2-credentials-create
> 'Client' object has no attribute 'auth_tenant_id'
> + CREDS=
> ++ echo ''
> ++ awk '/ access / { print $4 }'
> + export EC2_ACCESS_KEY=
> + EC2_ACCESS_KEY=
> ++ echo ''
> ++ awk '/ secret / { print $4 }'
> + export EC2_SECRET_KEY=
> + EC2_SECRET_KEY=
> + NOVA_KEY_DIR=
> ++ keystone catalog --service s3
> ++ awk '/ publicURL / { print $4 }'
> 'Client' object has no attribute 'service_catalog'
> 
> Has there been some changes that are causing this??
> 
> Seems like maybe the keystone client is not working anymore?
> 
> -Josh
> 
> ___
> 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] Being pedantic about pedanticism: HACKING styleguide

[Jay Pipes]

On 03/22/2012 01:47 PM, Doug Hellmann wrote:

Why are those sorts of instructions replicated in each project in the
first place? Shouldn't they be in the wiki?


:) Have you ever tried to get a dozen OpenStack contributors to agree 
on, well, anything?


The reason it's duplicated in so many places is that the contributors in 
the various projects didn't agree with some of the style rules used in 
Nova...


Best,
-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

Re: [Openstack] Devstack +XCP/XenServer Kernel Panic

[Ewan Mellor]

6.0.0 will work fine.  6.0.2 will be back in the next few hours, too.  (It was 
withdrawn because of a severe bug in the handling of fragmented IPv6 packets 
inside Windows VMs.  That's been fixed now.)

A completely vanilla install would be fine (preferable, even).  Then pick one 
of the guides that John referenced earlier, and you should be good to go.  The 
only thing to do at install time is to make sure you select "ext" local storage 
rather than LVHD.  It might also be known as "XenDesktop-optimized" or 
"Intellicache" depending on where you're looking.  We realized the other day 
that we forgot to document that step and I don't know if John's done it yet.

Cheers,

Ewan.

From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net 
[mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] On Behalf 
Of Kieran Evans
Sent: Thursday, March 22, 2012 2:49 AM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Devstack +XCP/XenServer Kernel Panic

In hindsight, that makes sense (though I swear I disabled root-squashing). I've 
been having other issues now, so quick question;

Most guides referer/specify XenServer 6.0.2, should 6.0 work (due to 6.0.2 
being temporarily unavailable?).

I'm going to try now with XenServer 6.0 and build remotely.

Another quick question:

Should this all work on a completely vanilla install of XenServer or XCP or is 
there any prep-work not mentioned anywhere, or any steps a complete Xen newb 
may miss?

/Kieran

On 21 Mar 2012, at 20:11, Ewan Mellor wrote:


I've never seen that kernel panic before.  If you're building on an NFS share 
though, that often screws up the permissions.  You could have root-squashing 
turned on, and then every file that's supposed to be owned by root is owned by 
an unprivileged user instead.  It wouldn't surprise me that this freaks out the 
init process.

I'd try building somewhere else and see if that helps.  Or see whether you've 
got root-squashing or some other permission-modifying option turned on.

Cheers,

Ewan.

From: 
openstack-bounces+ewan.mellor=citrix@lists.launchpad.net
 
[mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net]
 On Behalf Of Kieran Evans
Sent: Saturday, March 17, 2012 9:38 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] Devstack +XCP/XenServer Kernel Panic

Hi all,

I'm not sure if this is the right place for this (and if not, can anyone point 
out where).

I've used the devstack scripts to try to set up Openstack on both XenServer 6.0 
and XCP 1.5 using the following guides:

http://wiki.xen.org/wiki/XCP_DevStack
https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md

Wether on XenServer or XCP, I always seem to hit the same issue. When the 
ALLINONE VM is fired up, it shuts down after a few seconds with a kernel panic 
( as seen here: http://imgur.com/i85fC). The same issue occurs with the 
domU_multi scripts too.

A note, in case it may affect the build scripts somehow, For external storage, 
rather than using a different machine, or external USB, I've mounted /root to 
an NFS share before running prepare_dom0.sh.

We've currently got a Diablo Openstack installation up and running using 
StackOps, but I'm currently trying out essex on some spare machines (both to 
get to know it, and an attempt to see if running with Xen is of any advantage 
to us).

Thanks

/Kieran


___
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] Being pedantic about pedanticism: HACKING styleguide

[Paul McMillan]

On 03/22/2012 10:47 AM, Doug Hellmann wrote:

Why are those sorts of instructions replicated in each project in the
first place? Shouldn't they be in the wiki?


Because nobody reads wikis. Especially not developers who are in a hurry 
to make a small fix. At least this way, we can yell at them and say "You 
saw the HACKING file, and you didn't read it."



___
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] Horizon

[Anthony Young]

I made a very simple horizon example plugin, maybe you will find this
useful:

https://github.com/cloudbuilders/simple_horizon_plugin

On Thu, Mar 22, 2012 at 5:16 AM, Hallvard Westman <
hallvard.west...@gmail.com> wrote:

> I would like an answer to this question :
> http://osdir.com/ml/openstack-cloud-computing/2012-02/msg00092.html
> ___
> 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] Being pedantic about pedanticism: HACKING styleguide

[Kevin L. Mitchell]

On Thu, 2012-03-22 at 13:47 -0400, Doug Hellmann wrote:
> Why are those sorts of instructions replicated in each project in the
> first place? Shouldn't they be in the wiki?

Well, you're both right and wrong.  Right in that they should be in a
wiki somewhere.  Wrong in that they should *also* be in the project in a
prominent place—someone just getting started is likely to start with
exactly one project, and it would be best to have the HACKING
instructions where they can find them in that project.

Besides, copying bits is cheap, right?  :)
-- 
Kevin L. Mitchell 


___
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] Horizon-Keystone servicecatalog exception "volume"

[Gabriel Hurley]

First, to answer your question, take a look at what's in DevStack's keystone 
templates:

https://github.com/openstack-dev/devstack/blob/master/files/default_catalog.templates

That's for an Essex Keystone install, but I think you can figure out how to 
generalize it back to your setup.

That said, fixing that endpoint will fix a few issues for you, but the current 
Horizon master (Essex) on github isn't fully-compatible with a Diablo stack 
behind it. It'll *mostly* work, but many commands will fail due to changes to 
the various APIs (Keystone and Nova have both diverged from Diablo over the 
Essex timeframe).

I recommend you use the stable/diablo release of Horizon if you want to run 
Horizon with a Diablo stack.

All the best,


-  Gabriel

From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net 
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On 
Behalf Of Vijay
Sent: Thursday, March 22, 2012 10:25 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] Horizon-Keystone servicecatalog exception "volume"

Hello,
I have installed diablo nova/openstack, keystone 2011-3 and horizon from git.
I am able to login to dashboard. However, when I go to "Instances and Volumes", 
I am getting the following error:
ServiceCatalogException

Exception Value:


Invalid service catalog service: volume

ServiceCatalogException

Exception Value:


Invalid service catalog service: volume


ServiceCatalogException

Exception Value:


Invalid service catalog service: volume

ServiceCatalogException: Invalid service catalog service: volume

In keystone, I have added only three end points, nova, glance and keystone.

What is the endpoint template for volume that I need to add?

Thanks for any leads,
-Vijay


___
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] Being pedantic about pedanticism: HACKING styleguide

[Johannes Erdfelt]

On Thu, Mar 22, 2012, Kevin L. Mitchell  wrote:
> On Thu, 2012-03-22 at 11:22 -0500, Andrew Bogott wrote:
> > Nova, this:
> > 
> >A docstring ends with an empty line before the closing quotations. 
> 
> Huh?  I thought I removed that...

You did:

https://github.com/openstack/nova/commit/35e98d55db2a82e23e9610e3638eb43be78b9d53#HACKING.rst

JE


___
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] [SWIFT] "Skipping as it is not mounted"

[Pete Zaitcev]

On Thu, 22 Mar 2012 17:56:01 +
Leander Bessa  wrote:

> I've tried mounting it directly but it still didn't work. The only thing
> that got it running was disabling the mount_check.

You don't happen to sub-partition like SAIO does?

This works for me (2 volumes on 1 node for a moment):

[root@kvm-rei swift]# head -7 account-server/1.conf
[DEFAULT]
#devices = /srv/node
#mount_check = false
bind_port = 6012
user = swift
log_facility = LOG_LOCAL0

[root@kvm-rei swift]# grep vd /proc/mounts 
/dev/vda2 / ext4 rw,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/vda1 /boot ext4 rw,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered 
0 0
/dev/vdb /srv/node/vdb xfs 
rw,seclabel,noatime,nodiratime,attr2,delaylog,noquota 0 0
/dev/vdc /srv/node/vdc xfs 
rw,seclabel,noatime,nodiratime,attr2,delaylog,noquota 0 0
[root@kvm-rei swift]# 

-- Pete

___
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 client broken??

[Joshua Harlow]

Hi all,

When trying to use eucarc 
(https://github.com/openstack-dev/devstack/blob/master/eucarc) or the 
devstackPY copy called euca.sh ( 
https://github.com/yahoo/Openstack-DevstackPy/blob/master/euca.sh )

I am getting the following:

++ keystone catalog --service ec2
++ awk '/ publicURL / { print $4 }'
'Client' object has no attribute 'service_catalog'
+ export EC2_URL=
+ EC2_URL=
++ keystone ec2-credentials-create
'Client' object has no attribute 'auth_tenant_id'
+ CREDS=
++ echo ''
++ awk '/ access / { print $4 }'
+ export EC2_ACCESS_KEY=
+ EC2_ACCESS_KEY=
++ echo ''
++ awk '/ secret / { print $4 }'
+ export EC2_SECRET_KEY=
+ EC2_SECRET_KEY=
+ NOVA_KEY_DIR=
++ keystone catalog --service s3
++ awk '/ publicURL / { print $4 }'
'Client' object has no attribute 'service_catalog'

Has there been some changes that are causing this??

Seems like maybe the keystone client is not working anymore?

-Josh

___
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] Being pedantic about pedanticism: HACKING styleguide

[Ewan Mellor]

.rst is ReStructured Text.  It's the markup language being used.

Cheers,

Ewan.

> -Original Message-
> From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net
> [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net]
> On Behalf Of Andrew Bogott
> Sent: Thursday, March 22, 2012 9:22 AM
> To: openstack@lists.launchpad.net
> Subject: [Openstack] Being pedantic about pedanticism: HACKING
> styleguide
> 
>  Just now I set out to merge a recent style guide change from
> python-novaclient into the hacking docs of other OpenStack projects.
> My patch didn't apply, though, because each project has subtly
> diverging HACKING files.
> 
>  Rather than contribute to this divergence, I've now read and
> compared the style guides from Nova, Glance, Keystone, python-
> keystoneclient, and python-novaclient.  From these diffs I've created a
> file (attached) that encompasses the total of all guidelines from all
> projects.  Remarkably, this merge produced only minor disagreements,
> described below under the heading FLAMEBAIT.
> 
>  I propose that this unified style guide be copied into each of the
> above projects, with a mandate to maintain consistency henceforth.  Any
> objections?
> 
> -Andrew
> 
> 
> FLAMEBAIT (docstring format):
> 
> The only explicit contradiction I came across is regarding docstring
> formatting.  Glance says this:
> 
> **DO NOT** leave an extra newline before the closing triple-double-
> quote.
> 
> Nova, this:
> 
>A docstring ends with an empty line before the closing quotations.
> 
> I propose that we just pick one or the other, or remove both
> prescriptions.
> 
> FLAMEBAIT (filename):
> 
> Some projects have a HACKING file, and some have a HACKING.rst file.
> Doesn't .rst generally indicate a REST API definition?  I propose that
> the file be called HACKING.


___
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] [SWIFT] "Skipping as it is not mounted"

[Leander Bessa]

I've tried mounting it directly but it still didn't work. The only thing
that got it running was disabling the mount_check.

Thx.

On Thu, Mar 22, 2012 at 5:48 PM, Pete Zaitcev  wrote:

> On Thu, 22 Mar 2012 14:09:52 +
> Leander Bessa  wrote:
>
> > I'm installing swift on ubuntu 11.10 on a physical machine with and the
> > partition mounted on /mnt/disk. I have a symbolic link on /srv/node/disk
> > pointing to /mnt/disk and /srv/node belongs to swift:swift. The disk is
> > mounted, but i keep getting the same error message.
>
> Perhaps the symbolic link confuses the check (done with os.path.ismount()).
> Either mount to /srv/node/disk or slap "mount_check = false" into
> the *.conf files.
>
> -- Pete
>
___
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] [SWIFT] "Skipping as it is not mounted"

[Pete Zaitcev]

On Thu, 22 Mar 2012 14:09:52 +
Leander Bessa  wrote:

> I'm installing swift on ubuntu 11.10 on a physical machine with and the
> partition mounted on /mnt/disk. I have a symbolic link on /srv/node/disk
> pointing to /mnt/disk and /srv/node belongs to swift:swift. The disk is
> mounted, but i keep getting the same error message.

Perhaps the symbolic link confuses the check (done with os.path.ismount()).
Either mount to /srv/node/disk or slap "mount_check = false" into
the *.conf files.

-- Pete

___
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] Being pedantic about pedanticism: HACKING styleguide

[Doug Hellmann]

Why are those sorts of instructions replicated in each project in the first
place? Shouldn't they be in the wiki?

On Thu, Mar 22, 2012 at 12:22 PM, Andrew Bogott wrote:

>Just now I set out to merge a recent style guide change from
> python-novaclient into the hacking docs of other OpenStack projects.  My
> patch didn't apply, though, because each project has subtly diverging
> HACKING files.
>
>Rather than contribute to this divergence, I've now read and compared
> the style guides from Nova, Glance, Keystone, python-keystoneclient, and
> python-novaclient.  From these diffs I've created a file (attached) that
> encompasses the total of all guidelines from all projects.  Remarkably,
> this merge produced only minor disagreements, described below under the
> heading FLAMEBAIT.
>
>I propose that this unified style guide be copied into each of the
> above projects, with a mandate to maintain consistency henceforth.  Any
> objections?
>
> -Andrew
>
>
> FLAMEBAIT (docstring format):
>
> The only explicit contradiction I came across is regarding docstring
> formatting.  Glance says this:
>
> **DO NOT** leave an extra newline before the closing triple-double-quote.
>
> Nova, this:
>
>  A docstring ends with an empty line before the closing quotations.
>
> I propose that we just pick one or the other, or remove both prescriptions.
>
> FLAMEBAIT (filename):
>
> Some projects have a HACKING file, and some have a HACKING.rst file.
>  Doesn't .rst generally indicate a REST API definition?  I propose that the
> file be called HACKING.
>
>
> ___
> 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] Network Connectivity issue

[Diego Parrilla Santamaría]

Hi Nicolas, thanks for using our distro!

Just to summarize:
- Single node
- Management network: 192.168.163.0/25 = 192.168.163.1 to 192.168.163.126.
Let's assume gateway = 192.168.163.1
- Service Network: 192.168.163.128/25 = 192.168.163.129 to 192.168.163.254.
gateway should be = 192.168.163.129

If you wan to ping from the service network to a host in the management
network (and it's not the single node) you need a route to that network. Or
you can configure your system to use the Management Network as the public
network. Then you will reach your hosts.

If you are using FlatDHCP, may be you can configure the smart installer to
use as the service network a subset (not a subnet) of the management
network. It's a dirty hack (I prefer to split networks always) we did in
the past...

For example if you want to setup a little lab in your lapto with the distro
you can use this settings:
- Single node
- Management network: 192.168.10.0/24 (this is my network, use yours)
- Service Network: 10.0.0.0/24
- Public Network (floating range): 192.168.10.64/28 (and of course I don't
have any host in this subnet)

With this configuration floating IPs will reach hosts in the management
network.

Cheers!
Diego


-- 
Diego Parrilla
*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* 
**



On Thu, Mar 22, 2012 at 3:47 PM, Nicolas Odermatt wrote:

> Hello guys, I am dealing with a strange phenomenon my StackOps environment.
>
> The thing is like this:
> I am running a single-node stackops deployment in a little /25 network.
> The installation and the few configurations I had to do afterwards went
> just fine, no problems so far. I was also able to upload an image to glance
> and to start an instance using euca2ools. I authorized the necessary port
> for ssh, allowed icmp and then connected to the instance with ssh.
> Afterwards I checked the instance's connection to the internet, which was
> up and running. Now to my so called "strange phenomenon": Although I am
> able to ping my stackops-node, public ip adresses (e.g 8.8.8.8) and in
> spite the fact that name resolving works as well, I can't ping a Client
> machine in my local area network. My stackops-node has the ip-address
> 192.168.163.20/25, the instance has the ip-address(192.168.163.130/25)
> and the client has the ip-address 192.168.163.5/25.
>
> I can't think of an approach to this problem, as I have enabled ssh and
> icmp and the connection between Client and stackops-node exists.
> Is it possible that I might have forgott to add a certain rule?
>
> Thanks for your ideas!
>
> Best regards.
> Nicolas
> --
> Freundliche Grüsse,
> Nicolas Odermatt
>
>
>
> ___
> 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] Being pedantic about pedanticism: HACKING styleguide

[Johannes Erdfelt]

On Thu, Mar 22, 2012, Andrew Bogott  wrote:
> I propose that this unified style guide be copied into each of
> the above projects, with a mandate to maintain consistency
> henceforth.  Any objections?

I recently saw a suggestion to put it into openstack-common, but I don't
remember who made it (sorry!).

> FLAMEBAIT (docstring format):
> 
> The only explicit contradiction I came across is regarding docstring
> formatting.  Glance says this:
> 
> **DO NOT** leave an extra newline before the closing triple-double-quote.
> 
> Nova, this:
> 
>   A docstring ends with an empty line before the closing quotations.
> 
> I propose that we just pick one or the other, or remove both prescriptions.

I prefer the glance version, which is also how nova has been developed.

PEP8 says otherwise, but it's an emacs anachronism which I understand
isn't relevant anymore.

> FLAMEBAIT (filename):
> 
> Some projects have a HACKING file, and some have a HACKING.rst file.
> Doesn't .rst generally indicate a REST API definition?  I propose
> that the file be called HACKING.

.rst means it's formatted in reStructuredText.

JE


___
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] nova-manage quota --headroom

[Eoghan Glynn]

> Kevin Mitchell wrote:
> I recently got the quota classes stuff merged into master (after the RC
> branch for Essex was cut, of course).  After I had completed that work,
> I started thinking about quotas in general, and I think there's a better
> way to organize how we do quotas in the first place.  One potential side
> effect I see of that possible work would be to address this
> particular feature.
> 
> My idea here is not really very well fleshed out or architected yet, and
> I have other things I'm focusing on right now (caching), but perhaps I
> should mention them on the list, in order to get a discussion going…and
> perhaps a summit discussion of the topic would be in order?

Yep, that's a good idea. Let me know if you'd be interested in collaborating
on a summit session.

I'll have a detailed look at your recent work on quota classes before
responding to your quota infrastructure thoughts below ... but on a first
look, definitely sounds sane.

Cheers,
Eoghan

> The basic thought I had here was to create a "quota manager" or
> "quota
> plugin" infrastructure, instead of a bunch of fixed functions in
> quota.py that we use to test certain specific quotas.  Having it as a
> plugin that you specify in configuration means you can easily
> substitute
> out the default implementation, if necessary—maybe you want quotas to
> be
> enforced across several cells instead of just one, for instance.
>  Then,
> checking a quota would be a matter of simply calling a method on the
> quota plugin class.
> 
> The side effect is that, in order to properly impose quotas in a
> flexible architecture, you would need to keep the quota plugin
> up-to-date on the current numbers of whatever resource is being
> limited
> anyway—in the example above, of having one quota applied across a
> number
> of cells, you don't want to have to ask each cell how many instances
> the
> user currently has.  That makes implementation of your headroom
> concept
> pretty trivial, and I could see it implemented by attaching a little
> more data to the /limits endpoint's returned data.
> 
> (The current quota code has to count how many instances there are
> each
> time it checks the quota; I think other parts that use quotas may do
> the
> counting themselves and just ask quota.py what the upper limit is.)
> --
> Kevin L. Mitchell 
> 
> 
> ___
> 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] Horizon-Keystone servicecatalog exception "volume"

[Vijay]

Hello,
I have installed diablo nova/openstack, keystone 2011-3 and horizon from git.
I am able to login to dashboard. However, when I go to "Instances and Volumes", 
I am getting the following error:




ServiceCatalogException

Exception Value:
Invalid service catalog service: volume




ServiceCatalogException

Exception Value:
Invalid service catalog service: volume
 




ServiceCatalogException

Exception Value:
Invalid service catalog service: volumeServiceCatalogException: Invalid service 
catalog service: volume
 
In keystone, I have added only three end points, nova, glance and keystone.
 
What is the endpoint template for volume that I need to add?
 
Thanks for any leads,
-Vijay___
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] Being pedantic about pedanticism: HACKING styleguide

[Kevin L. Mitchell]

On Thu, 2012-03-22 at 11:22 -0500, Andrew Bogott wrote:
> Nova, this:
> 
>A docstring ends with an empty line before the closing quotations. 

Huh?  I thought I removed that...
-- 
Kevin L. Mitchell 


___
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] nova-manage quota --headroom

[Eoghan Glynn]

Thanks Jay for the feedback and background info, comments inline ...

> > Eoghan Glynn wrote:
> > So the question is whether there's already a means to acheive this
> > in one fell swoop?
>
> Jay Pipes wrote: 
> Well, Horizon, in the launch instance modal dialog does show similar
> information. See attached screenshot. That dialog uses a call to the
> contrib/simple_usage extension of the compute API

Lovely, that's exactly the type of representation I had in mind
(but wearing my old-school CLI-oriented hat).

> Jay Pipes wrote: 
> Basically, you could take any of these approaches:
> 
> a) Modify the simple_usage extension to return information about the
> quotas along with the usage information
> 
> b) Make a new extension to the API that marries the usage with the
> quota
> 
> c) Make a new novaclient call that exposes the married information

A new extension that combines the quota with a report on current usage 
levels (i.e. options b+c) seems neatest to me.

Cheers,
Eoghan

___
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] MySQL connection gone away handling in OpenStack projects

[Vishvananda Ishaya]

This looks like a much better solution than MySQLPingListener.  It would be 
good to get this into common / nova, especially if we can verify that it works 
with postgres as well.

Vish

On Mar 22, 2012, at 7:48 AM, Unmesh Gurjar wrote:

> Hi,
>  
> The current handling of the ‘SQL server has gone away’ is different across 
> OpenStack projects (eg. Nova uses MySQLPingListener, whereas Glance retries 
> the db operation to recover connection).
> I am curious to know if the fix implemented in 
> https://review.openstack.org/5552 will be used across all projects (through 
> openstack-common) ?
>  
> Thanks & Regards,
> Unmesh G.
> ___
> 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] Caching strategies in Nova ...

[Jesse Andrews]

Agree that there are pros and cons to caching at different layers.

As for plugins, in most places where we support memcache we revert to
an in-memory cache if it isn't configured.

The work that was done during essex was to make the metadata service
use either an external cache or internal cache.  When an cloud-init
based image boots it makes dozens of calls to get data, which results
in dozens of RPC calls to nova-network to map IP to instance and then
to the DB to load data.

-

Background info: The in-process cache I commited is actually the code
previously known as the "fake" memcache, moved from nova/tests to
nova/common.  The reason for the move is two-fold: 1) the code was
already in use as an in-memory cache in other locations in the code 2)
nova/tests isn't included in most (all?) packagings.

Also Josh Harlow has been researching better alternatives for
in-memory caches for python (rather than re-inventing the wheel -
which I started here: https://github.com/cloudbuilders/millicache ...)

--

So ya, I think a summit proposal would be good.

Jesse

On Thu, Mar 22, 2012 at 8:06 AM, Sandy Walsh  wrote:
> o/
>
> Vek and myself are looking into caching strategies in and around Nova.
>
> There are essentially two approaches: in-process and external (proxy).
> The in-process schemes sit in with the python code while the external
> ones basically proxy the the HTTP requests.
>
> There are some obvious pro's and con's to each approach. The external is
> easier for operations to manage, but in-process allows us greater
> control over the caching (for things like caching db calls and not just
> HTTP calls). But, in-memory also means more code, more memory usage on
> the servers, monolithic services, limited to python based solutions,
> etc. In-process also gives us access to tools like Tach
> https://github.com/ohthree/tach for profiling performance.
>
> I see Jesse recently landed a branch that touches on the in-process
> approach:
> https://github.com/openstack/nova/commit/1bcf5f5431d3c9620596f5329d7654872235c7ee#nova/common/memorycache.py
>
> I don't know if people think putting caching code inside nova is a good
> or bad idea. If we do continue down this road, it would be nice to make
> it a little more modular/plug-in-based (YAPI .. yet another plug-in).
> Perhaps a hybrid solution is required?
>
> We're looking at tools like memcache, beaker, varnish, etc.
>
> Has anyone already started down this road already? Any insights to
> share? Opinions? (summit talk?)
>
> What are Glance, Swift, Keystone (lite?) doing?
>
> -S
>
> ___
> 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] horizon and keystone no route matched error

[jay_s_b]

Removing trailing slash in local_settings.py in horizon worked. Thank you all 
for the help.
-jay



From: Gabriel Hurley 
To: Dolph Mathews  
Cc: jay_s_b ; "openstack@lists.launchpad.net" 
 
Sent: Wednesday, March 21, 2012 5:34 PM
Subject: RE: [Openstack] horizon and keystone no route matched error


It’s not a trailing slash on the URL sent to keystone. It’s a trailing slash in 
the Horizon setting which leads to a double-slash in the URL sent to keystone.
 
-  Gabriel
 
From:anti...@gmail.com [mailto:anti...@gmail.com] On Behalf Of Dolph Mathews
Sent: Wednesday, March 21, 2012 5:26 PM
To: Gabriel Hurley
Cc: jay_s_b; openstack@lists.launchpad.net
Subject: Re: [Openstack] horizon and keystone no route matched error
 
Wasn't this fixed in keystoneclient (properly handling an unexpected trailing 
slash)?
 
-Dolph
On Wed, Mar 21, 2012 at 6:56 PM, Gabriel Hurley  
wrote:
It looks like you’ve got an extra slash in your URL. That probably means you’ve 
got a trailing slash on your OPENSTACK_KEYSTONE_URL setting. As per the example 
settings file it should look like this:
 
OPENSTACK_KEYSTONE_URL = "http://%25s:5000/v2.0"; % OPENSTACK_HOST
 
e.g.
 
OPENSTACK_KEYSTONE_URL = http://127.0.0.1:5000/v2.0
 
Hopefully that helps.
 
-  Gabriel
 
 
From:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net 
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On 
Behalf Of jay_s_b
Sent: Wednesday, March 21, 2012 4:28 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] horizon and keystone no route matched error
 
Hello,
I have installed horizon dash board from git and integrating with nova. When I 
login to dashboard, I am getting error. Error: please try logging again.
In dashboard log, I see  the following error:
Request returned failure status.
In keystone log, I see 
2012-03-21 15:37:02    DEBUG [routes.middleware] No route matched for POST 
//tokens
2012-03-21 15:37:02    DEBUG [eventlet.wsgi.server] 16.213.0.39 - - 
[21/Mar/2012 15:37:02] "POST /v2.0//tokens HTTP/1.1" 404 228 
0.000782"routes.middleware
 
Any clue regarding this is appreciated.
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] Caching strategies in Nova ...

[Vishvananda Ishaya]

On Mar 22, 2012, at 8:06 AM, Sandy Walsh wrote:

> o/
> 
> Vek and myself are looking into caching strategies in and around Nova.
> 
> There are essentially two approaches: in-process and external (proxy).
> The in-process schemes sit in with the python code while the external
> ones basically proxy the the HTTP requests.

We may need http caches as well in some cases, but we already use memcached in 
a few places, so I think we need internal caching as well.

> 
> There are some obvious pro's and con's to each approach. The external is
> easier for operations to manage, but in-process allows us greater
> control over the caching (for things like caching db calls and not just
> HTTP calls). But, in-memory also means more code, more memory usage on
> the servers, monolithic services, limited to python based solutions,
> etc. In-process also gives us access to tools like Tach
> https://github.com/ohthree/tach for profiling performance.
> 
> I see Jesse recently landed a branch that touches on the in-process
> approach:
> https://github.com/openstack/nova/commit/1bcf5f5431d3c9620596f5329d7654872235c7ee#nova/common/memorycache.py
> 
> I don't know if people think putting caching code inside nova is a good
> or bad idea. If we do continue down this road, it would be nice to make
> it a little more modular/plug-in-based (YAPI .. yet another plug-in).
> Perhaps a hybrid solution is required?

openstack-common is where jesse was planning on putting memorycache

> 
> We're looking at tools like memcache, beaker, varnish, etc.
> 

I kind of like keeping our caching simple, just talking to something that is 
replicating the python-memcached api so that we can change out an in memory 
cache or actual memcached or db cache or etc...


This has a bit of promise:

http://code.google.com/p/python-cache/

Vish

___
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] nova-billing with Horizon

[Lucian Thomaz]

It's weird, I just tried follow these steps but it haven't worked to me. I did 
the configurations in settings.py instead of local_settings.py , because in the 
local_settings.py I did not found INSTALLED_APPS and HORIZON_CONFIG.

Thank you by the help and tell me if there are anything else that should I try.
Lucian Thomaz


CC: thin...@gmail.com; openstack@lists.launchpad.net
From: andy...@gmail.com
Subject: Re: [Openstack] nova-billing with Horizon
Date: Thu, 22 Mar 2012 22:27:55 +0800
To: luciantho...@hotmail.com



That's probably all it needs, at least that's the way I tried it last time.
On 2012/3/22, at 下午10:19, Lucian Thomaz  wrote:





I'm trying to do that with diablo, but it isn't working.

I ran setup.py , next I added  'horizon_billing' to INSTALLED_APPS and I added 
'biling' to 'dashboards' key in HORIZON_CONFIG, after that I restarted Apache 
and tried acess the dashboard in the browser. It's all the steps that I need to 
do?

Lucian Thomaz 




From: andy...@gmail.com
Date: Thu, 22 Mar 2012 22:06:02 +0800
Subject: Re: [Openstack] [openstack] nova-billing with Horizon
To: luciantho...@hotmail.com
CC: thin...@gmail.com; openstack@lists.launchpad.net

I have tried running the billing last week, but they haven't update to latest 
horizon at essex, you might want to try them with diablo branch of horizon

On Thu, Mar 22, 2012 at 9:35 PM, Lucian Thomaz  wrote:






Mike, I just tried running setup.py now and it worked nice, and after that I 
tried to restart the apache, but it gives me the same error:

[Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237]   File 
"/usr/lib/pymodules/python2.7/django/utils/importlib.py", line 35, in 
import_module


[Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237] __import__(name)
[Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237] 
TemplateSyntaxError: Caught ImportError while rendering: No module named 
horizon_billing



You know what should I inspect?


Lucian Thomaz




Date: Wed, 21 Mar 2012 14:41:39 -0700
From: thin...@gmail.com
To: luciantho...@hotmail.com


Subject: Re: [Openstack] [openstack] nova-billing with Horizon


You need to make sure either system wide or in your virtual env 
that horizon_billing is installed by running setup.py in horizon_billing.


-- 
Mike Perez
DreamHost.com

 
On Wednesday, March 21, 2012 at 10:55 AM, Lucian Thomaz wrote:





Mike, this help me to understand a little more, but when I tried add 
'horizon_billing' to INSTALLED_APPS tuple and restart apache, the log of apache 
returns the following error: TemplateSyntaxError: Caught ImportError while 
rendering: No module named horizon_billing


Do you know anything about that?


Lucian Thomaz




Date: Wed, 21 Mar 2012 10:23:25 -0700
From: thin...@gmail.com
To: luciantho...@hotmail.com


Subject: Re: [Openstack] [openstack] nova-billing with Horizon


Whoops, from THEIR latest repo, instead of linking to mine. ;)

https://github.com/openstack/horizon/blob/master/openstack_dashboard/settings.py#L51



-- 
Mike Perez
DreamHost.com

  
On Wednesday, March 21, 2012 at 10:22 AM, Mike Perez wrote:

It appears to be in there with latest in the horizon repo:
https://github.com/Thingee/horizon/blob/master/openstack_dashboard/settings.py#L51



-- 
Mike Perez
DreamHost.com

   
On Wednesday, March 21, 2012 at 10:19 AM, Lucian Thomaz wrote:




Thank you by the answer Mike, but my settings.py don't have the HORIZON_CONFIG 
in it. Can I simply add it? How should it looks like?




Lucian Thomaz



Date: Wed, 21 Mar 2012 09:53:35 -0700
From: thin...@gmail.com
To: luciantho...@hotmail.com


CC: openstack@lists.launchpad.net
Subject: Re: [Openstack] [openstack] nova-billing with Horizon



horizon/openstack_dashboard/settings.py


-- 
Mike Perez
DreamHost.com


On Wednesday, March 21, 2012 at 7:07 AM, Lucian Thomaz wrote:




I'm trying use nova-billing with Horizon following the github page 
https://github.com/griddynamics/horizon-billing , but I can't find 
INSTALLED_APPS and HORIZON_CONFIG in local_settings.py . Anyone can help with 
that?



Lucian Thomaz


  
___Mailing list: 
https://launchpad.net/~openstackPost to : openstack@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstackMore help   : 
https://help.launchpad.net/ListHelp









  

   
   
   

Re: [Openstack] nova-manage quota --headroom

[Vishvananda Ishaya]

Seems like this would be much more useful as part of the quotas extension.  
This feature is small enough for a bug I think.

Vish

On Mar 22, 2012, at 6:36 AM, Eoghan Glynn wrote:

> 
> Folks,
> 
> One thing that's been on my wishlist since hitting a bunch of
> quota exceeded issues when first running Tempest and also on
> the Fedora17 openstack test day.
> 
> It's ability to easily see the remaining headroom for each
> per-project quota, e.g.
> 
> $ nova-manage quota --headroom --project=admin
> ...
> instances:10  (of which 1 remaining)
> floating_ips: 10  (of which 8 remaining)
> ...
> 
> This would give an immediate indication of an impending resource
> starvation issue - "shoot, I'll have to clean out some of those
> old instances before spinning up two more, else increase the quota".
> 
> It would only really be useful for quotas that represent a
> threshold on overall resource usage that may grow or shrink over
> time, as opposed to some fixed limit (think, max instances versus
> max injected files per instance).
> 
> So the question is whether there's already a means to acheive this
> in one fell swoop? 
> 
> And if not, would it be best tracked with a small-scale nova blueprint,
> or as an enhancement request expressed in a launchpad bug?
> 
> Cheers,
> Eoghan
> 
> ___
> 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] Being pedantic about pedanticism: HACKING styleguide

[Andrew Bogott]

Just now I set out to merge a recent style guide change from 
python-novaclient into the hacking docs of other OpenStack projects.  My 
patch didn't apply, though, because each project has subtly diverging 
HACKING files.


Rather than contribute to this divergence, I've now read and 
compared the style guides from Nova, Glance, Keystone, 
python-keystoneclient, and python-novaclient.  From these diffs I've 
created a file (attached) that encompasses the total of all guidelines 
from all projects.  Remarkably, this merge produced only minor 
disagreements, described below under the heading FLAMEBAIT.


I propose that this unified style guide be copied into each of the 
above projects, with a mandate to maintain consistency henceforth.  Any 
objections?


-Andrew


FLAMEBAIT (docstring format):

The only explicit contradiction I came across is regarding docstring 
formatting.  Glance says this:


**DO NOT** leave an extra newline before the closing triple-double-quote.

Nova, this:

  A docstring ends with an empty line before the closing quotations.

I propose that we just pick one or the other, or remove both prescriptions.

FLAMEBAIT (filename):

Some projects have a HACKING file, and some have a HACKING.rst file.  
Doesn't .rst generally indicate a REST API definition?  I propose that 
the file be called HACKING.


OpenStack Style Commandments
===

- Step 1: Read http://www.python.org/dev/peps/pep-0008/
- Step 2: Read http://www.python.org/dev/peps/pep-0008/ again
- Step 3: Read on


General
---
- Put two newlines between top-level code (funcs, classes, etc)
- Put one newline between methods in classes and anywhere else
- Do not write "except:", use "except Exception:" at the very least
- Include your name with TODOs as in "#TODO(termie)"
- When defining global constants, define them before functions and classes
- Do not shadow a built-in or reserved word. Example::

def list():
return [1, 2, 3]

mylist = list() # BAD, shadows `list` built-in

class Foo(object):
def list(self):
return [1, 2, 3]

mylist = Foo().list() # OKAY, does not shadow built-in


TODO vs FIXME
-

- TODO(name): implies that something should be done (cleanup, refactoring,
  etc), but is expected to be functional.
- FIXME(name): implies that the method/function/etc shouldn't be used until
  that code is resolved and bug fixed.

Imports
---
- Do not import objects, only modules
- Do not import more than one module per line
- Do not make relative imports
- Order your imports by the full module path
- Organize your imports according to the following template

Example::

  # vim: tabstop=4 shiftwidth=4 softtabstop=4
  {{stdlib imports in human alphabetical order}}
  \n
  {{third-party lib imports in human alphabetical order}}
  \n
  {{project imports in human alphabetical order}}
  \n
  \n
  {{begin your code}}


Human Alphabetical Order Examples
-
Example::

  import httplib
  import logging
  import random
  import StringIO
  import time
  import unittest

  import eventlet
  import webob.exc

  import nova.api.ec2
  from nova.api import openstack
  from nova.auth import users
  import nova.flags
  from nova.endpoint import cloud
  from nova import test


Docstrings
--
Example::

  """A one line docstring looks like this and ends in a period."""


  """A multiline docstring has a one-line summary, less than 80 characters.

  Then a new paragraph after a newline that explains in more detail any
  general information about the function, class or method. Example usages
  are also great to have here if it is a complex class for function.

  When writing the docstring for a class, an extra line should be placed
  after the closing quotations. For more in-depth explanations for these
  decisions see http://www.python.org/dev/peps/pep-0257/

  A docstring ends with an empty line before the closing quotations.

  Describe parameters and return values, using the Sphinx format; the
  appropriate syntax is as follows.

  :param foo: the foo parameter
  :param bar: the bar parameter
  :type bar: parameter type for 'bar'
  :returns: return_type -- description of the return value
  :returns: description of the return value
  :raises: AttributeError, KeyError

  """


Dictionaries/Lists
--
If a dictionary (dict) or list object is longer than 80 characters, its items
should be split with newlines. Embedded iterables should have their items
indented. Additionally, the last item in the dictionary should have a trailing
comma. This increases readability and simplifies future diffs.

Example::

  my_dictionary = {
  "image": {
  "name": "Just a Snapshot",
  "size": 2749573,
  "properties": {
   "user_id": 12,
   "arch": "x86_64",
  },
  "things": [
  "thing_one",
  "thing_two",
  ],
  "status": "ACTIV

Re: [Openstack] Network Connectivity issue

[Kieron]

On Thu, Mar 22, 2012 at 10:47 AM, Nicolas Odermatt wrote:

> Hello guys, I am dealing with a strange phenomenon my StackOps environment.
>
> The thing is like this:
> I am running a single-node stackops deployment in a little /25 network.
> The installation and the few configurations I had to do afterwards went
> just fine, no problems so far. I was also able to upload an image to glance
> and to start an instance using euca2ools. I authorized the necessary port
> for ssh, allowed icmp and then connected to the instance with ssh.
> Afterwards I checked the instance's connection to the internet, which was
> up and running. Now to my so called "strange phenomenon": Although I am
> able to ping my stackops-node, public ip adresses (e.g 8.8.8.8) and in
> spite the fact that name resolving works as well, I can't ping a Client
> machine in my local area network. My stackops-node has the ip-address
> 192.168.163.20/25, the instance has the ip-address(192.168.163.130/25)
> and the client has the ip-address 192.168.163.5/25.
>
> Does your client (192.168.163.5) have a route to the 
> 192.168.163.128/25network via 192.168.163.20?
___
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] Enabling remote participation at Folsom Design Summit

[Doug Hellmann]

The PSF has had fairly good luck with Ustream for our members' meetings.
They are 1-way, though, so questions or comments from remote participants
have to be relayed by someone in the room (we used IRC).

On Thu, Mar 22, 2012 at 1:44 AM, Marton Kiss  wrote:

> Ustream broadcast as an alternative option?
>
> Marton Kiss, CTO
> Xemeti
> On Mar 21, 2012 11:54 PM, "Debo Dutta (dedutta)" 
> wrote:
>
>> SW side: Another option would be to run webex meetings or even google
>> hangout!
>>
>> debo
>>
>> -Original Message-
>> From: openstack-bounces+dedutta=cisco@lists.launchpad.net
>> [mailto:openstack-bounces+dedutta=cisco@lists.launchpad.net] On
>> Behalf Of Stefano Maffulli
>> Sent: Wednesday, March 21, 2012 3:35 PM
>> To: openstack@lists.launchpad.net
>> Subject: Re: [Openstack] Enabling remote participation at Folsom Design
>> Summit
>>
>> I'm still loooking for *hardware* to make this happen.
>>
>> Lets try to make this more sexy and see where to cook hackers are: what
>> if we buy a few beaglebone boards ($89 each) and spend a weekend hacking
>> a streaming server on them?
>>
>> The boards are cheap enough and should have enough power to acquire
>> audio, convert it to mp4/h264 using their hardware and send the stream
>> over to a public icecast server. As with many other things, the software
>> is already out there, it needs hammering, put it together, testing and
>> praying it works at the summit.
>>
>> Any volunteer?
>>
>> Or any other option? Cheap desktops would work too: I wouldn't refuse
>> Dell or HP to ship 6 of their smallest machines either :)
>>
>> let me know, please.
>> Cheers,
>> stef
>>
>>
>> On Tue, 2012-03-06 at 13:47 -0800, Stefano Maffulli wrote:
>> > Hello folks,
>> >
>> > since the next design summit is sold out and many people are still
>> > interested in participating, I believe we should really make remote
>> > participation possible.
>> >
>> > Imitating Ubuntu Developer Summit, I think the ideal situation is to
>> > have in each room:
>> >
>> >  - 1 omnidirectional microphone to capture discussions and questions
>> >  - 1 streaming client hooked to a public icecast streaming server
>> >  - 1 IRC channel per room
>> >  - 1 projector showing the content of the IRC channel
>> >  - 1 projector available for collaborative note taking via etherpad
>> >
>> > And for plenary session:
>> >
>> >  - full audio/video service
>> >  - IRC channel, not shown but monitored in case there are interesting
>> > questions
>> >
>> > We'll also need dedicated bandwidth from the Hyatt hotel, networking,
>> > firewalling and the whole shabang. Anything else?
>> >
>> > I will start investigating what Rackspace can provide but this is a
>> big
>> > task and I would like to make this a shared effort.
>> >
>> > If you have experience with this, and want to help me get the
>> equipment,
>> > software, services needed to enable remote participation to the Design
>> > Summit please email me.
>> >
>> > Thanks,
>> > stef
>> >
>> >
>> > [1] http://uds.ubuntu.com/community/remote-participation/
>> >
>> >
>> > ___
>> > 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
>
>
___
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] nova-manage quota --headroom

[Kevin L. Mitchell]

On Thu, 2012-03-22 at 09:36 -0400, Eoghan Glynn wrote:
> It's ability to easily see the remaining headroom for each
> per-project quota, e.g.
> 
>  $ nova-manage quota --headroom --project=admin
>  ...
>  instances:10  (of which 1 remaining)
>  floating_ips: 10  (of which 8 remaining)
>  ...

I recently got the quota classes stuff merged into master (after the RC
branch for Essex was cut, of course).  After I had completed that work,
I started thinking about quotas in general, and I think there's a better
way to organize how we do quotas in the first place.  One potential side
effect I see of that possible work would be to address this particular
feature.

My idea here is not really very well fleshed out or architected yet, and
I have other things I'm focusing on right now (caching), but perhaps I
should mention them on the list, in order to get a discussion going…and
perhaps a summit discussion of the topic would be in order?

The basic thought I had here was to create a "quota manager" or "quota
plugin" infrastructure, instead of a bunch of fixed functions in
quota.py that we use to test certain specific quotas.  Having it as a
plugin that you specify in configuration means you can easily substitute
out the default implementation, if necessary—maybe you want quotas to be
enforced across several cells instead of just one, for instance.  Then,
checking a quota would be a matter of simply calling a method on the
quota plugin class.

The side effect is that, in order to properly impose quotas in a
flexible architecture, you would need to keep the quota plugin
up-to-date on the current numbers of whatever resource is being limited
anyway—in the example above, of having one quota applied across a number
of cells, you don't want to have to ask each cell how many instances the
user currently has.  That makes implementation of your headroom concept
pretty trivial, and I could see it implemented by attaching a little
more data to the /limits endpoint's returned data.

(The current quota code has to count how many instances there are each
time it checks the quota; I think other parts that use quotas may do the
counting themselves and just ask quota.py what the upper limit is.)
-- 
Kevin L. Mitchell 


___
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] Devstack +XCP/XenServer Kernel Panic

[Kieran Evans]

No worries, as I mentioned previously, my main "production" Openstack install 
is Diablo/Ubuntu/KVM, I'm just looking into XenServer as a potential future 
route. 

I'll keep an eye out for any news on the pack.

I'm sure you have what you need already, but if you want a user with some 
servers to test installing the pack, I'm happy to help!

/Kieran

On 22 Mar 2012, at 14:59, John Garbutt wrote:

> Afraid I haven’t finished producing the supplemental packs yet (might be a 
> few weeks till I get around to finishing that stuff off). I was aiming to 
> allow the supplemental packs to work in both cases, if I can.
>  
> Cheers,
> John
>  
> From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net 
> [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On 
> Behalf OfKieran Evans
> Sent: 22 March 2012 1:36
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Devstack +XCP/XenServer Kernel Panic
>  
> Thanks for the help/advice all. I did have root squashing disabled, but 
> something else must've been playing up. I did the build on another machine 
> and it's working now. At least, the ALLINONE vm booted and prepare_guest.sh 
> is running, so fingers crossed!
>  
> On one of the wiki pages, it says that an Openstack supplemental pack is in 
> the works, would it be safe to assume this would be a production oriented 
> pack, rather than the devstack style dev oriented setup?
>  
> /Kieran
>  
> On 22 Mar 2012, at 11:31, John Garbutt wrote:
> 
> 
> 6.0.0 should work fine.
>  
> I must have gained some weak mind reading powers, and I just wrote a few more 
> wiki pages.
>  
> Here is the best place to start:
> http://wiki.openstack.org/XenServer
>  
> I actually just added this wiki page (still a work in progress really):
> http://wiki.openstack.org/XenServer/PostInstall
>  
> Hope that helps,
> John
>  
> From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net 
> [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On 
> Behalf OfKieran Evans
> Sent: 22 March 2012 9:49
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Devstack +XCP/XenServer Kernel Panic
>  
> In hindsight, that makes sense (though I swear I disabled root-squashing). 
> I've been having other issues now, so quick question;
>  
> Most guides referer/specify XenServer 6.0.2, should 6.0 work (due to 6.0.2 
> being temporarily unavailable?). 
>  
> I'm going to try now with XenServer 6.0 and build remotely. 
>  
> Another quick question:
>  
> Should this all work on a completely vanilla install of XenServer or XCP or 
> is there any prep-work not mentioned anywhere, or any steps a complete Xen 
> newb may miss?
>  
> /Kieran
>  
> On 21 Mar 2012, at 20:11, Ewan Mellor wrote:
> 
> 
> 
> I’ve never seen that kernel panic before.  If you’re building on an NFS share 
> though, that often screws up the permissions.  You could have root-squashing 
> turned on, and then every file that’s supposed to be owned by root is owned 
> by an unprivileged user instead.  It wouldn’t surprise me that this freaks 
> out the init process.
>  
> I’d try building somewhere else and see if that helps.  Or see whether you’ve 
> got root-squashing or some other permission-modifying option turned on.
>  
> Cheers,
>  
> Ewan.
>  
> From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net 
> [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] On 
> Behalf Of Kieran Evans
> Sent: Saturday, March 17, 2012 9:38 AM
> To: openstack@lists.launchpad.net
> Subject: [Openstack] Devstack +XCP/XenServer Kernel Panic
>  
> Hi all,
>  
> I'm not sure if this is the right place for this (and if not, can anyone 
> point out where).
>  
> I've used the devstack scripts to try to set up Openstack on both XenServer 
> 6.0 and XCP 1.5 using the following guides:
>  
> http://wiki.xen.org/wiki/XCP_DevStack
> https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md
>  
> Wether on XenServer or XCP, I always seem to hit the same issue. When the 
> ALLINONE VM is fired up, it shuts down after a few seconds with a kernel 
> panic ( as seen here: http://imgur.com/i85fC). The same issue occurs with the 
> domU_multi scripts too.
>  
> A note, in case it may affect the build scripts somehow, For external 
> storage, rather than using a different machine, or external USB, I've mounted 
> /root to an NFS share before running prepare_dom0.sh.
>  
> We've currently got a Diablo Openstack installation up and running using 
> StackOps, but I'm currently trying out essex on some spare machines (both to 
> get to know it, and an attempt to see if running with Xen is of any advantage 
> to us).
>  
> Thanks
>  
> /Kieran
>  

___
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] Caching strategies in Nova ...

[Sandy Walsh]

o/

Vek and myself are looking into caching strategies in and around Nova.

There are essentially two approaches: in-process and external (proxy).
The in-process schemes sit in with the python code while the external
ones basically proxy the the HTTP requests.

There are some obvious pro's and con's to each approach. The external is
easier for operations to manage, but in-process allows us greater
control over the caching (for things like caching db calls and not just
HTTP calls). But, in-memory also means more code, more memory usage on
the servers, monolithic services, limited to python based solutions,
etc. In-process also gives us access to tools like Tach
https://github.com/ohthree/tach for profiling performance.

I see Jesse recently landed a branch that touches on the in-process
approach:
https://github.com/openstack/nova/commit/1bcf5f5431d3c9620596f5329d7654872235c7ee#nova/common/memorycache.py

I don't know if people think putting caching code inside nova is a good
or bad idea. If we do continue down this road, it would be nice to make
it a little more modular/plug-in-based (YAPI .. yet another plug-in).
Perhaps a hybrid solution is required?

We're looking at tools like memcache, beaker, varnish, etc.

Has anyone already started down this road already? Any insights to
share? Opinions? (summit talk?)

What are Glance, Swift, Keystone (lite?) doing?

-S

___
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] Devstack +XCP/XenServer Kernel Panic

[John Garbutt]

Afraid I haven't finished producing the supplemental packs yet (might be a few 
weeks till I get around to finishing that stuff off). I was aiming to allow the 
supplemental packs to work in both cases, if I can.

Cheers,
John

From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net 
[mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On 
Behalf Of Kieran Evans
Sent: 22 March 2012 1:36
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Devstack +XCP/XenServer Kernel Panic

Thanks for the help/advice all. I did have root squashing disabled, but 
something else must've been playing up. I did the build on another machine and 
it's working now. At least, the ALLINONE vm booted and prepare_guest.sh is 
running, so fingers crossed!

On one of the wiki pages, it says that an Openstack supplemental pack is in the 
works, would it be safe to assume this would be a production oriented pack, 
rather than the devstack style dev oriented setup?

/Kieran

On 22 Mar 2012, at 11:31, John Garbutt wrote:


6.0.0 should work fine.

I must have gained some weak mind reading powers, and I just wrote a few more 
wiki pages.

Here is the best place to start:
http://wiki.openstack.org/XenServer

I actually just added this wiki page (still a work in progress really):
http://wiki.openstack.org/XenServer/PostInstall

Hope that helps,
John

From: 
openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net
 
[mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net]
 On Behalf OfKieran Evans
Sent: 22 March 2012 9:49
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Devstack +XCP/XenServer Kernel Panic

In hindsight, that makes sense (though I swear I disabled root-squashing). I've 
been having other issues now, so quick question;

Most guides referer/specify XenServer 6.0.2, should 6.0 work (due to 6.0.2 
being temporarily unavailable?).

I'm going to try now with XenServer 6.0 and build remotely.

Another quick question:

Should this all work on a completely vanilla install of XenServer or XCP or is 
there any prep-work not mentioned anywhere, or any steps a complete Xen newb 
may miss?

/Kieran

On 21 Mar 2012, at 20:11, Ewan Mellor wrote:



I've never seen that kernel panic before.  If you're building on an NFS share 
though, that often screws up the permissions.  You could have root-squashing 
turned on, and then every file that's supposed to be owned by root is owned by 
an unprivileged user instead.  It wouldn't surprise me that this freaks out the 
init process.

I'd try building somewhere else and see if that helps.  Or see whether you've 
got root-squashing or some other permission-modifying option turned on.

Cheers,

Ewan.

From: 
openstack-bounces+ewan.mellor=citrix@lists.launchpad.net
 
[mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net]
 On Behalf Of Kieran Evans
Sent: Saturday, March 17, 2012 9:38 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] Devstack +XCP/XenServer Kernel Panic

Hi all,

I'm not sure if this is the right place for this (and if not, can anyone point 
out where).

I've used the devstack scripts to try to set up Openstack on both XenServer 6.0 
and XCP 1.5 using the following guides:

http://wiki.xen.org/wiki/XCP_DevStack
https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md

Wether on XenServer or XCP, I always seem to hit the same issue. When the 
ALLINONE VM is fired up, it shuts down after a few seconds with a kernel panic 
( as seen here: http://imgur.com/i85fC). The same issue occurs with the 
domU_multi scripts too.

A note, in case it may affect the build scripts somehow, For external storage, 
rather than using a different machine, or external USB, I've mounted /root to 
an NFS share before running prepare_dom0.sh.

We've currently got a Diablo Openstack installation up and running using 
StackOps, but I'm currently trying out essex on some spare machines (both to 
get to know it, and an attempt to see if running with Xen is of any advantage 
to us).

Thanks

/Kieran


___
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] Network Connectivity issue

[Nicolas Odermatt]

Hello guys, I am dealing with a strange phenomenon my StackOps environment.

The thing is like this:
I am running a single-node stackops deployment in a little /25 network. The
installation and the few configurations I had to do afterwards went just
fine, no problems so far. I was also able to upload an image to glance and
to start an instance using euca2ools. I authorized the necessary port for
ssh, allowed icmp and then connected to the instance with ssh. Afterwards I
checked the instance's connection to the internet, which was up and
running. Now to my so called "strange phenomenon": Although I am able to
ping my stackops-node, public ip adresses (e.g 8.8.8.8) and in spite the
fact that name resolving works as well, I can't ping a Client machine in my
local area network. My stackops-node has the ip-address 192.168.163.20/25,
the instance has the ip-address(192.168.163.130/25) and the client has the
ip-address 192.168.163.5/25.

I can't think of an approach to this problem, as I have enabled ssh and
icmp and the connection between Client and stackops-node exists.
Is it possible that I might have forgott to add a certain rule?

Thanks for your ideas!

Best regards.
Nicolas
-- 
Freundliche Grüsse,
Nicolas Odermatt
___
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] MySQL connection gone away handling in OpenStack projects

[Unmesh Gurjar]

Hi,

The current handling of the 'SQL server has gone away' is different across 
OpenStack projects (eg. Nova uses MySQLPingListener, whereas Glance retries the 
db operation to recover connection).
I am curious to know if the fix implemented in 
https://review.openstack.org/5552 will be used across all projects (through 
openstack-common) ?

Thanks & Regards,
Unmesh G.
___
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] nova-billing with Horizon

[Andy Chong]

That's probably all it needs, at least that's the way I tried it last time.

On 2012/3/22, at 下午10:19, Lucian Thomaz  wrote:

> I'm trying to do that with diablo, but it isn't working.
> 
> I ran setup.py , next I added 'horizon_billing' to INSTALLED_APPS and I added 
> 'biling' to 'dashboards' key in HORIZON_CONFIG, after that I restarted Apache 
> and tried acess the dashboard in the browser. It's all the steps that I need 
> to do?
> 
> Lucian Thomaz 
> 
> 
> From: andy...@gmail.com
> Date: Thu, 22 Mar 2012 22:06:02 +0800
> Subject: Re: [Openstack] [openstack] nova-billing with Horizon
> To: luciantho...@hotmail.com
> CC: thin...@gmail.com; openstack@lists.launchpad.net
> 
> I have tried running the billing last week, but they haven't update to latest 
> horizon at essex, 
> you might want to try them with diablo branch of horizon
> 
> On Thu, Mar 22, 2012 at 9:35 PM, Lucian Thomaz  
> wrote:
> Mike, I just tried running setup.py now and it worked nice, and after that I 
> tried to restart the apache, but it gives me the same error:
> 
> [Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237]   File 
> "/usr/lib/pymodules/python2.7/django/utils/importlib.py", line 35, in 
> import_module
> [Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237] 
> __import__(name)
> [Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237] 
> TemplateSyntaxError: Caught ImportError while rendering: No module named 
> horizon_billing
> 
> You know what should I inspect?
> 
> 
> Lucian Thomaz
> 
> 
> Date: Wed, 21 Mar 2012 14:41:39 -0700
> From: thin...@gmail.com
> To: luciantho...@hotmail.com
> Subject: Re: [Openstack] [openstack] nova-billing with Horizon
> 
> You need to make sure either system wide or in your virtual env that 
> horizon_billing is installed by running setup.py in horizon_billing.
> 
> -- 
> Mike Perez
> DreamHost.com
> 
> On Wednesday, March 21, 2012 at 10:55 AM, Lucian Thomaz wrote:
> 
> Mike, this help me to understand a little more, but when I tried add 
> 'horizon_billing' to INSTALLED_APPS tuple and restart apache, the log of 
> apache returns the following error: TemplateSyntaxError: Caught ImportError 
> while rendering: No module named horizon_billing
> 
> Do you know anything about that?
> 
> 
> Lucian Thomaz
> 
> 
> 
> Date: Wed, 21 Mar 2012 10:23:25 -0700
> From: thin...@gmail.com
> To: luciantho...@hotmail.com
> Subject: Re: [Openstack] [openstack] nova-billing with Horizon
> 
> Whoops, from THEIR latest repo, instead of linking to mine. ;)
> 
> https://github.com/openstack/horizon/blob/master/openstack_dashboard/settings.py#L51
> 
> -- 
> Mike Perez
> DreamHost.com
> 
> On Wednesday, March 21, 2012 at 10:22 AM, Mike Perez wrote:
> 
> It appears to be in there with latest in the horizon repo:
> 
> https://github.com/Thingee/horizon/blob/master/openstack_dashboard/settings.py#L51
> 
> -- 
> Mike Perez
> DreamHost.com
> 
> On Wednesday, March 21, 2012 at 10:19 AM, Lucian Thomaz wrote:
> 
> Thank you by the answer Mike, but my settings.py don't have the 
> HORIZON_CONFIG in it. Can I simply add it? How should it looks like?
> 
> 
> Lucian Thomaz
> 
> 
> Date: Wed, 21 Mar 2012 09:53:35 -0700
> From: thin...@gmail.com
> To: luciantho...@hotmail.com
> CC: openstack@lists.launchpad.net
> Subject: Re: [Openstack] [openstack] nova-billing with Horizon
> 
> 
> horizon/openstack_dashboard/settings.py
> 
> -- 
> Mike Perez
> DreamHost.com
> 
> On Wednesday, March 21, 2012 at 7:07 AM, Lucian Thomaz wrote:
> 
> I'm trying use nova-billing with Horizon following the github page 
> https://github.com/griddynamics/horizon-billing , but I can't find 
> INSTALLED_APPS and HORIZON_CONFIG in local_settings.py . Anyone can help with 
> that?
> 
> Lucian Thomaz
> ___
> 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] nova-billing with Horizon

[Lucian Thomaz]

I'm trying to do that with diablo, but it isn't working.

I ran setup.py , next I added  'horizon_billing' to INSTALLED_APPS and I added 
'biling' to 'dashboards' key in HORIZON_CONFIG, after that I restarted Apache 
and tried acess the dashboard in the browser. It's all the steps that I need to 
do?

Lucian Thomaz 




From: andy...@gmail.com
Date: Thu, 22 Mar 2012 22:06:02 +0800
Subject: Re: [Openstack] [openstack] nova-billing with Horizon
To: luciantho...@hotmail.com
CC: thin...@gmail.com; openstack@lists.launchpad.net

I have tried running the billing last week, but they haven't update to latest 
horizon at essex, you might want to try them with diablo branch of horizon

On Thu, Mar 22, 2012 at 9:35 PM, Lucian Thomaz  wrote:






Mike, I just tried running setup.py now and it worked nice, and after that I 
tried to restart the apache, but it gives me the same error:

[Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237]   File 
"/usr/lib/pymodules/python2.7/django/utils/importlib.py", line 35, in 
import_module


[Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237] __import__(name)
[Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237] 
TemplateSyntaxError: Caught ImportError while rendering: No module named 
horizon_billing



You know what should I inspect?


Lucian Thomaz




Date: Wed, 21 Mar 2012 14:41:39 -0700
From: thin...@gmail.com
To: luciantho...@hotmail.com


Subject: Re: [Openstack] [openstack] nova-billing with Horizon


You need to make sure either system wide or in your virtual env 
that horizon_billing is installed by running setup.py in horizon_billing.


-- 
Mike Perez
DreamHost.com

 
On Wednesday, March 21, 2012 at 10:55 AM, Lucian Thomaz wrote:





Mike, this help me to understand a little more, but when I tried add 
'horizon_billing' to INSTALLED_APPS tuple and restart apache, the log of apache 
returns the following error: TemplateSyntaxError: Caught ImportError while 
rendering: No module named horizon_billing


Do you know anything about that?


Lucian Thomaz




Date: Wed, 21 Mar 2012 10:23:25 -0700
From: thin...@gmail.com
To: luciantho...@hotmail.com


Subject: Re: [Openstack] [openstack] nova-billing with Horizon


Whoops, from THEIR latest repo, instead of linking to mine. ;)

https://github.com/openstack/horizon/blob/master/openstack_dashboard/settings.py#L51



-- 
Mike Perez
DreamHost.com

  
On Wednesday, March 21, 2012 at 10:22 AM, Mike Perez wrote:

It appears to be in there with latest in the horizon repo:
https://github.com/Thingee/horizon/blob/master/openstack_dashboard/settings.py#L51



-- 
Mike Perez
DreamHost.com

   
On Wednesday, March 21, 2012 at 10:19 AM, Lucian Thomaz wrote:




Thank you by the answer Mike, but my settings.py don't have the HORIZON_CONFIG 
in it. Can I simply add it? How should it looks like?




Lucian Thomaz



Date: Wed, 21 Mar 2012 09:53:35 -0700
From: thin...@gmail.com
To: luciantho...@hotmail.com


CC: openstack@lists.launchpad.net
Subject: Re: [Openstack] [openstack] nova-billing with Horizon



horizon/openstack_dashboard/settings.py


-- 
Mike Perez
DreamHost.com


On Wednesday, March 21, 2012 at 7:07 AM, Lucian Thomaz wrote:




I'm trying use nova-billing with Horizon following the github page 
https://github.com/griddynamics/horizon-billing , but I can't find 
INSTALLED_APPS and HORIZON_CONFIG in local_settings.py . Anyone can help with 
that?



Lucian Thomaz


  
___Mailing list: 
https://launchpad.net/~openstackPost to : openstack@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstackMore help   : 
https://help.launchpad.net/ListHelp









  

   
   
   
   





  
  
  
  



  

 
 
 
 

 



  

___

Mailing list: https://launchpad.net/~openstack

Post to : openstack@lists.launchpad.net

Unsubscribe : https://lau

[Openstack] [SWIFT] "Skipping as it is not mounted"

[Leander Bessa]

Hello,

I'm trying out an install script similar to the model of SAIO. I keep
running into the error message in the logs: "Skipping disk as it is not
mounted".

I'm installing swift on ubuntu 11.10 on a physical machine with and the
partition mounted on /mnt/disk. I have a symbolic link on /srv/node/disk
pointing to /mnt/disk and /srv/node belongs to swift:swift. The disk is
mounted, but i keep getting the same error message.

What am i missing?

Regards,

Leander
___
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] nova-billing with Horizon

[Andy Chong]

I have tried running the billing last week, but they haven't update to
latest horizon at essex,
you might want to try them with diablo branch of horizon

On Thu, Mar 22, 2012 at 9:35 PM, Lucian Thomaz wrote:

>  Mike, I just tried running setup.py now and it worked nice, and after
> that I tried to restart the apache, but it gives me the same error:
>
> [Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237]   File
> "/usr/lib/pymodules/python2.7/django/utils/importlib.py", line 35, in
> import_module
> [Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237]
> __import__(name)
> [Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237]
> TemplateSyntaxError: Caught ImportError while rendering: No module named
> horizon_billing
>
> You know what should I inspect?
>
>
> *Lucian Thomaz
> *
>
>
> --
> Date: Wed, 21 Mar 2012 14:41:39 -0700
> From: thin...@gmail.com
> To: luciantho...@hotmail.com
> Subject: Re: [Openstack] [openstack] nova-billing with Horizon
>
> You need to make sure either system wide or in your virtual env that
> horizon_billing is installed by running setup.py in horizon_billing.
>
> --
> Mike Perez
> DreamHost.com
>
> On Wednesday, March 21, 2012 at 10:55 AM, Lucian Thomaz wrote:
>
>  Mike, this help me to understand a little more, but when I tried add
> 'horizon_billing' to INSTALLED_APPS tuple and restart apache, the log of
> apache returns the following error: TemplateSyntaxError: Caught
> ImportError while rendering: No module named horizon_billing
>
> Do you know anything about that?
>
>
> *Lucian Thomaz*
>
>
>
> --
> Date: Wed, 21 Mar 2012 10:23:25 -0700
> From: thin...@gmail.com
> To: luciantho...@hotmail.com
> Subject: Re: [Openstack] [openstack] nova-billing with Horizon
>
> Whoops, from THEIR latest repo, instead of linking to mine. ;)
>
>
> https://github.com/openstack/horizon/blob/master/openstack_dashboard/settings.py#L51
>
> --
> Mike Perez
> DreamHost.com
>
> On Wednesday, March 21, 2012 at 10:22 AM, Mike Perez wrote:
>
>  It appears to be in there with latest in the horizon repo:
>
>
> https://github.com/Thingee/horizon/blob/master/openstack_dashboard/settings.py#L51
>
> --
> Mike Perez
> DreamHost.com
>
> On Wednesday, March 21, 2012 at 10:19 AM, Lucian Thomaz wrote:
>
>  Thank you by the answer Mike, but my settings.py don't have the
> HORIZON_CONFIG in it. Can I simply add it? How should it looks like?
>
>
> *Lucian Thomaz*
>
>
> --
> Date: Wed, 21 Mar 2012 09:53:35 -0700
> From: thin...@gmail.com
> To: luciantho...@hotmail.com
> CC: openstack@lists.launchpad.net
> Subject: Re: [Openstack] [openstack] nova-billing with Horizon
>
>
>  horizon/openstack_dashboard/settings.py
>
> --
> Mike Perez
> DreamHost.com
>
> On Wednesday, March 21, 2012 at 7:07 AM, Lucian Thomaz wrote:
>
>  I'm trying use nova-billing with Horizon following the github page
> https://github.com/griddynamics/horizon-billing , but I can't find
> INSTALLED_APPS and HORIZON_CONFIG in local_settings.py . Anyone can help
> with that?
>
> *Lucian Thomaz
> *
>  ___
> 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] nova-manage quota --headroom

[Eoghan Glynn]

Folks,

One thing that's been on my wishlist since hitting a bunch of
quota exceeded issues when first running Tempest and also on
the Fedora17 openstack test day.

It's ability to easily see the remaining headroom for each
per-project quota, e.g.

 $ nova-manage quota --headroom --project=admin
 ...
 instances:10  (of which 1 remaining)
 floating_ips: 10  (of which 8 remaining)
 ...

This would give an immediate indication of an impending resource
starvation issue - "shoot, I'll have to clean out some of those
old instances before spinning up two more, else increase the quota".

It would only really be useful for quotas that represent a
threshold on overall resource usage that may grow or shrink over
time, as opposed to some fixed limit (think, max instances versus
max injected files per instance).

So the question is whether there's already a means to acheive this
in one fell swoop? 

And if not, would it be best tracked with a small-scale nova blueprint,
or as an enhancement request expressed in a launchpad bug?

Cheers,
Eoghan

___
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] Devstack +XCP/XenServer Kernel Panic

[Kieran Evans]

Thanks for the help/advice all. I did have root squashing disabled, but 
something else must've been playing up. I did the build on another machine and 
it's working now. At least, the ALLINONE vm booted and prepare_guest.sh is 
running, so fingers crossed!

On one of the wiki pages, it says that an Openstack supplemental pack is in the 
works, would it be safe to assume this would be a production oriented pack, 
rather than the devstack style dev oriented setup?

/Kieran

On 22 Mar 2012, at 11:31, John Garbutt wrote:

> 6.0.0 should work fine.
>  
> I must have gained some weak mind reading powers, and I just wrote a few more 
> wiki pages.
>  
> Here is the best place to start:
> http://wiki.openstack.org/XenServer
>  
> I actually just added this wiki page (still a work in progress really):
> http://wiki.openstack.org/XenServer/PostInstall
>  
> Hope that helps,
> John
>  
> From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net 
> [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On 
> Behalf OfKieran Evans
> Sent: 22 March 2012 9:49
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Devstack +XCP/XenServer Kernel Panic
>  
> In hindsight, that makes sense (though I swear I disabled root-squashing). 
> I've been having other issues now, so quick question;
>  
> Most guides referer/specify XenServer 6.0.2, should 6.0 work (due to 6.0.2 
> being temporarily unavailable?). 
>  
> I'm going to try now with XenServer 6.0 and build remotely. 
>  
> Another quick question:
>  
> Should this all work on a completely vanilla install of XenServer or XCP or 
> is there any prep-work not mentioned anywhere, or any steps a complete Xen 
> newb may miss?
>  
> /Kieran
>  
> On 21 Mar 2012, at 20:11, Ewan Mellor wrote:
> 
> 
> I’ve never seen that kernel panic before.  If you’re building on an NFS share 
> though, that often screws up the permissions.  You could have root-squashing 
> turned on, and then every file that’s supposed to be owned by root is owned 
> by an unprivileged user instead.  It wouldn’t surprise me that this freaks 
> out the init process.
>  
> I’d try building somewhere else and see if that helps.  Or see whether you’ve 
> got root-squashing or some other permission-modifying option turned on.
>  
> Cheers,
>  
> Ewan.
>  
> From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net 
> [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] On 
> Behalf Of Kieran Evans
> Sent: Saturday, March 17, 2012 9:38 AM
> To: openstack@lists.launchpad.net
> Subject: [Openstack] Devstack +XCP/XenServer Kernel Panic
>  
> Hi all,
>  
> I'm not sure if this is the right place for this (and if not, can anyone 
> point out where).
>  
> I've used the devstack scripts to try to set up Openstack on both XenServer 
> 6.0 and XCP 1.5 using the following guides:
>  
> http://wiki.xen.org/wiki/XCP_DevStack
> https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md
>  
> Wether on XenServer or XCP, I always seem to hit the same issue. When the 
> ALLINONE VM is fired up, it shuts down after a few seconds with a kernel 
> panic ( as seen here: http://imgur.com/i85fC). The same issue occurs with the 
> domU_multi scripts too.
>  
> A note, in case it may affect the build scripts somehow, For external 
> storage, rather than using a different machine, or external USB, I've mounted 
> /root to an NFS share before running prepare_dom0.sh.
>  
> We've currently got a Diablo Openstack installation up and running using 
> StackOps, but I'm currently trying out essex on some spare machines (both to 
> get to know it, and an attempt to see if running with Xen is of any advantage 
> to us).
>  
> Thanks
>  
> /Kieran
>  

___
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] nova-billing with Horizon

[Lucian Thomaz]

Mike, I just tried running setup.py now and it worked nice, and after that I 
tried to restart the apache, but it gives me the same error:

[Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237]   File 
"/usr/lib/pymodules/python2.7/django/utils/importlib.py", line 35, in 
import_module
[Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237] __import__(name)
[Thu Mar 22 10:28:07 2012] [error] [client 192.168.100.237] 
TemplateSyntaxError: Caught ImportError while rendering: No module named 
horizon_billing

You know what should I inspect?

Lucian Thomaz




Date: Wed, 21 Mar 2012 14:41:39 -0700
From: thin...@gmail.com
To: luciantho...@hotmail.com
Subject: Re: [Openstack] [openstack] nova-billing with Horizon


You need to make sure either system wide or in your virtual env 
that horizon_billing is installed by running setup.py in horizon_billing.


-- 
Mike Perez
DreamHost.com

 
On Wednesday, March 21, 2012 at 10:55 AM, Lucian Thomaz wrote:





Mike, this help me to understand a little more, but when I tried add 
'horizon_billing' to INSTALLED_APPS tuple and restart apache, the log of apache 
returns the following error: TemplateSyntaxError: Caught ImportError while 
rendering: No module named horizon_billing
Do you know anything about that?


Lucian Thomaz


Date: Wed, 21 Mar 2012 10:23:25 -0700
From: thin...@gmail.com
To: luciantho...@hotmail.com
Subject: Re: [Openstack] [openstack] nova-billing with Horizon


Whoops, from THEIR latest repo, instead of linking to mine. ;)

https://github.com/openstack/horizon/blob/master/openstack_dashboard/settings.py#L51

-- 
Mike Perez
DreamHost.com

  
On Wednesday, March 21, 2012 at 10:22 AM, Mike Perez wrote:

It appears to be in there with latest in the horizon repo:
https://github.com/Thingee/horizon/blob/master/openstack_dashboard/settings.py#L51

-- 
Mike Perez
DreamHost.com

   
On Wednesday, March 21, 2012 at 10:19 AM, Lucian Thomaz wrote:




Thank you by the answer Mike, but my settings.py don't have the HORIZON_CONFIG 
in it. Can I simply add it? How should it looks like?


Lucian Thomaz



Date: Wed, 21 Mar 2012 09:53:35 -0700
From: thin...@gmail.com
To: luciantho...@hotmail.com
CC: openstack@lists.launchpad.net
Subject: Re: [Openstack] [openstack] nova-billing with Horizon



horizon/openstack_dashboard/settings.py


-- 
Mike Perez
DreamHost.com


On Wednesday, March 21, 2012 at 7:07 AM, Lucian Thomaz wrote:




I'm trying use nova-billing with Horizon following the github page 
https://github.com/griddynamics/horizon-billing , but I can't find 
INSTALLED_APPS and HORIZON_CONFIG in local_settings.py . Anyone can help with 
that?

Lucian Thomaz


  
___Mailing list: 
https://launchpad.net/~openstackPost to : 
openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore 
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] Can't delete instances with "error" status.

[Guilherme Birk]

Gabe, responding to your question "Do you know how to reliably reproduce an 
instance in ERROR state that cannot be deleted?":
In my case, I'm updating the status of the VM to "error" directly on the 
database. This is just for testing. But even when my VM is running and working 
fine, when I update it to "error" in the database I can't delete it.

> From: gabe.westm...@rackspace.com
> To: cp16...@gmail.com
> Date: Thu, 22 Mar 2012 06:49:15 +
> CC: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Can't delete instances with "error" status.
> 
> There are definitely lots of cases where deleting an instance in error state 
> works fine, and I’d like to know about the cases where it doesn’t.  They do 
> count against quota as well, so that’s a problem!
> 
> I can see value in keeping an instance around �C if the operations team has 
> configured it to do so.  However, it seems like the end user has asked for it 
> to be deleted and to them it should appear to be deleted.  Johannes had an 
> idea a while ago to allow the operations team to specify a project ID that 
> deleted servers that match certain criteria should be moved to.  If the 
> delete finishes up fine, then its no problem, the delete is done, the 
> customer is happy and the ops account is empty.  If it fails for some reason, 
> there is manual cleanup to be done, but that should be on the operator of the 
> deployment, not the user.  I think its critical for anything like this to be 
> configurable, as public clouds and private clouds have different privacy and 
> retention concerns, I would guess.
> 
> Do we have cases where we can reliably reproduce this issue?  If its 
> happening every time on some deployments there is a very serious problem!
> 
> Gabe
> 
> 
> From: Craig Vyvial [mailto:cp16...@gmail.com] 
> Sent: Thursday, March 22, 2012 2:20 AM
> To: Gabe Westmaas
> Cc: Yong Sheng Gong; Openstack Mail List
> Subject: Re: [Openstack] Can't delete instances with "error" status.
> 
> My understanding is that you would not always want a user to delete an 
> instance in an error state. So an operations person can figure out what went 
> wrong. I think the instances that are in error state do not count against the 
> quota but i agree that they clutter up the API calls to list servers. 
> 
> I have noticed this with my team and written code around this case to force 
> the instance into an 'active' state before sending nova the delete call if 
> the instance was in an 'error' or 'suspended' state.
> 
> -Craig
> 
> On Thu, Mar 22, 2012 at 1:02 AM, Gabe Westmaas  
> wrote:
> Instances in deleted status can normally be deleted, but there is definitely 
> a bug to file here somewhere �C possibly more than one.  A common reason I 
> have seen is that the node the instance lives on is no longer operating 
> correctly, so the compute manager never gets the delete request, so it 
> doesn’t finish.  If we can narrow the cases where this happens, we can file 
> bugs and decide how to resolve them �C although there may be some additional 
> work beyond just a developer picking up the bug and working on it to decide 
> what should happen!
>  
> Do you know how to reliably reproduce an instance in ERROR state that cannot 
> be deleted?
>  
> Gabe
>  
> From: openstack-bounces+gabe.westmaas=rackspace@lists.launchpad.net 
> [mailto:openstack-bounces+gabe.westmaas=rackspace@lists.launchpad.net] On 
> Behalf Of Yong Sheng Gong
> Sent: Thursday, March 22, 2012 12:58 AM
> 
> To: Openstack Mail List
> Subject: Re: [Openstack] Can't delete instances with "error" status.
>  
> why not allow "nova delete" and "euca-terminate " to delete the instance with 
> "error" status?
> 
> Yong Sheng Gong
>  
> -openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -
> To: Guilherme Birk , Openstack Mail List 
> 
> From: Mandar Vaze 
> Sent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.net
> Date: 03/22/2012 12:26PM
> Subject: Re: [Openstack] Can't delete instances with "error" status.
> I agree user shouldn’t have to update DB. 
> There needs to be some periodic cleanup task that “fixes” the 
> vm_state/task_state for “stuck” instances.
>  
> -Mandar
>  
> From: openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net 
> [mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net] On 
> Behalf Of Guilherme Birk
> Sent: Wednesday, March 21, 2012 6:05 PM
> To: Openstack Mail List
> Subject: Re: [Openstack] Can't delete instances with "error" status.
>  
> This is the only option? I've already done that, but it's kind "strange" I 
> update the database row everytime the script identifies a VM with error.
> 
> Date: Wed, 21 Mar 2012 09:39:03 +0800
> Subject: Re: [Openstack] Can't delete instances with "error" status.
> From: mwjpi...@gmail.com
> To: guib...@hotmail.com
> update "instances" table in "nova" db, set the vm_status of  the instance 
> which you want to delete "activ

Re: [Openstack] Keystone credentials

[Dolph Mathews]

keystoneclient ($ keystone) is actually the new way to perform these types
of operations instead of keystone-manage ($ keystone-manage)

You'll first need to let keystoneclient authenticate with your keystone
server as an admin, see:
http://keystone.openstack.org/configuration.html#adding-users-tenants-and-roles-with-python-keystoneclient

And then try:

$ keystone --help
$ keystone --help | grep ec2
$ keystone help ec2-credentials-create

-Dolph

On Thu, Mar 22, 2012 at 8:00 AM, Nicolas Odermatt wrote:

> Hey guys, I have a question regarding Keystone
>
> When I create a new keystone user, which I want to use for API-Calls (EC2)
> I have to insert a data row into the credentials table of the keystone
> database.
> My question is: How can I do this using keystone-manage? It's more of a
> cosmetic thing, but I'd like to do it in a "clean" way.
>
> Thanks for your writing!
>
> Best wishes,
> Nicolas
>
> --
> Freundliche Grüsse,
> Nicolas Odermatt
>
>
>
> ___
> 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] Keystone credentials

[Nicolas Odermatt]

Hey guys, I have a question regarding Keystone

When I create a new keystone user, which I want to use for API-Calls (EC2)
I have to insert a data row into the credentials table of the keystone
database.
My question is: How can I do this using keystone-manage? It's more of a
cosmetic thing, but I'd like to do it in a "clean" way.

Thanks for your writing!

Best wishes,
Nicolas

-- 
Freundliche Grüsse,
Nicolas Odermatt
___
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] Horizon

[Hallvard Westman]

I would like an answer to this question : 
http://osdir.com/ml/openstack-cloud-computing/2012-02/msg00092.html
___
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] Devstack +XCP/XenServer Kernel Panic

[John Garbutt]

6.0.0 should work fine.

I must have gained some weak mind reading powers, and I just wrote a few more 
wiki pages.

Here is the best place to start:
http://wiki.openstack.org/XenServer

I actually just added this wiki page (still a work in progress really):
http://wiki.openstack.org/XenServer/PostInstall

Hope that helps,
John

From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net 
[mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On 
Behalf Of Kieran Evans
Sent: 22 March 2012 9:49
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Devstack +XCP/XenServer Kernel Panic

In hindsight, that makes sense (though I swear I disabled root-squashing). I've 
been having other issues now, so quick question;

Most guides referer/specify XenServer 6.0.2, should 6.0 work (due to 6.0.2 
being temporarily unavailable?).

I'm going to try now with XenServer 6.0 and build remotely.

Another quick question:

Should this all work on a completely vanilla install of XenServer or XCP or is 
there any prep-work not mentioned anywhere, or any steps a complete Xen newb 
may miss?

/Kieran

On 21 Mar 2012, at 20:11, Ewan Mellor wrote:


I've never seen that kernel panic before.  If you're building on an NFS share 
though, that often screws up the permissions.  You could have root-squashing 
turned on, and then every file that's supposed to be owned by root is owned by 
an unprivileged user instead.  It wouldn't surprise me that this freaks out the 
init process.

I'd try building somewhere else and see if that helps.  Or see whether you've 
got root-squashing or some other permission-modifying option turned on.

Cheers,

Ewan.

From: 
openstack-bounces+ewan.mellor=citrix@lists.launchpad.net
 
[mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net]
 On Behalf Of Kieran Evans
Sent: Saturday, March 17, 2012 9:38 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] Devstack +XCP/XenServer Kernel Panic

Hi all,

I'm not sure if this is the right place for this (and if not, can anyone point 
out where).

I've used the devstack scripts to try to set up Openstack on both XenServer 6.0 
and XCP 1.5 using the following guides:

http://wiki.xen.org/wiki/XCP_DevStack
https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md

Wether on XenServer or XCP, I always seem to hit the same issue. When the 
ALLINONE VM is fired up, it shuts down after a few seconds with a kernel panic 
( as seen here: http://imgur.com/i85fC). The same issue occurs with the 
domU_multi scripts too.

A note, in case it may affect the build scripts somehow, For external storage, 
rather than using a different machine, or external USB, I've mounted /root to 
an NFS share before running prepare_dom0.sh.

We've currently got a Diablo Openstack installation up and running using 
StackOps, but I'm currently trying out essex on some spare machines (both to 
get to know it, and an attempt to see if running with Xen is of any advantage 
to us).

Thanks

/Kieran


___
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] Devstack +XCP/XenServer Kernel Panic

[Kieran Evans]

In hindsight, that makes sense (though I swear I disabled root-squashing). I've 
been having other issues now, so quick question;

Most guides referer/specify XenServer 6.0.2, should 6.0 work (due to 6.0.2 
being temporarily unavailable?). 

I'm going to try now with XenServer 6.0 and build remotely. 

Another quick question:

Should this all work on a completely vanilla install of XenServer or XCP or is 
there any prep-work not mentioned anywhere, or any steps a complete Xen newb 
may miss?

/Kieran

On 21 Mar 2012, at 20:11, Ewan Mellor wrote:

> I’ve never seen that kernel panic before.  If you’re building on an NFS share 
> though, that often screws up the permissions.  You could have root-squashing 
> turned on, and then every file that’s supposed to be owned by root is owned 
> by an unprivileged user instead.  It wouldn’t surprise me that this freaks 
> out the init process.
>  
> I’d try building somewhere else and see if that helps.  Or see whether you’ve 
> got root-squashing or some other permission-modifying option turned on.
>  
> Cheers,
>  
> Ewan.
>  
> From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net 
> [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] On 
> Behalf Of Kieran Evans
> Sent: Saturday, March 17, 2012 9:38 AM
> To: openstack@lists.launchpad.net
> Subject: [Openstack] Devstack +XCP/XenServer Kernel Panic
>  
> Hi all,
>  
> I'm not sure if this is the right place for this (and if not, can anyone 
> point out where).
>  
> I've used the devstack scripts to try to set up Openstack on both XenServer 
> 6.0 and XCP 1.5 using the following guides:
>  
> http://wiki.xen.org/wiki/XCP_DevStack
> https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md
>  
> Wether on XenServer or XCP, I always seem to hit the same issue. When the 
> ALLINONE VM is fired up, it shuts down after a few seconds with a kernel 
> panic ( as seen here: http://imgur.com/i85fC). The same issue occurs with the 
> domU_multi scripts too.
>  
> A note, in case it may affect the build scripts somehow, For external 
> storage, rather than using a different machine, or external USB, I've mounted 
> /root to an NFS share before running prepare_dom0.sh.
>  
> We've currently got a Diablo Openstack installation up and running using 
> StackOps, but I'm currently trying out essex on some spare machines (both to 
> get to know it, and an attempt to see if running with Xen is of any advantage 
> to us).
>  
> Thanks
>  
> /Kieran
>  

___
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] Swift 1.4.8 released

[Thierry Carrez]

Swift 1.4.8 has been released today. You can download it from:
https://launchpad.net/swift/essex/1.4.8

You can find the full changelog at:
https://github.com/openstack/swift/blob/1.4.8/CHANGELOG

Unless a critical regression is found in this release, Swift 1.4.8 will
be included in the common OpenStack 2012.1 "Essex" release coming up on
April 5.

Cheers,

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack

___
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] Thanks - OpenStack Essex RC1 on Ubuntu 12.04

[Kevin Jackson]

Dear all,
You might know me from such emails as "Agggh, I can't get this thing to
work and its close to RC status!" and such bugs as "Why is this only
affecting me?" so I thought I'd share my gratitude to everyone that has
come out to help make life a lot less stressful for me.
Over the course of just a week I've gone from despair and frustration to
almost wanting to shout from the rooftops the achievements that have been
made in OpenStack and my own deployments and testing.
Whilst many of you might still be on that rocky road, I can assure you that
there is light at the end of the tunnel.  And it's quite bright too.

Much of my frustration has come from a number of things:

1) Waiting for Ubuntu packagers and developers to keep pace with the
changes in OpenStack - a challenge that I feel only in the end product.
2) Configuration issues and changes in syntax which seem to be only known
to some key people - Google often sends people down some strange routes of
mis-information!
3) Bugs.

This is a fast-paced project with high expectations...  Very high
expectations.  Thankfully, the army of people working behind the scenes are
approachable and accessible and have literally worked their asses off and
gone out of their way on several occasions to work with me on ensuring that
what they see in their labs and on their networks is similar to what I have
running now.

I am one person of many that is an end-user of OpenStack that wants to see
it succeed as much as the next guy.  I am also one guy in an enterprise
that defines strategy and makes choices - explaining broken things and
answering tough questions to my own powers that be.  My journey began at
the end of the Bexar release, through a working Cactus setup, to
fundamental changes in Diablo, and equally scary and often confusing
late-game changes in Essex.  I am confident that with the help of the
community, and with the ease of installation that is now expected in
today's fast paced world that choosing and sticking with OpenStack was and
is the right thing to do.  Don't get me wrong, had there not been this late
surge in changes, development, packaging and help I'd be sitting here with
my coffee trying to understand what went wrong and where to go next - but
I'm not.  I'm sitting here now planning the next implementation phases in
the projects that had a cloud environment as a fundamental requirement -
these projects were going to succeed whether it was OpenStack or not.

I just want to send my gratitude to everyone and anyone that has made this
happen - from the people cracking the whips high up in the backing
organisations, to those on the front-line who tap away at the keyboard that
end-users take for granted.  I hope, over the course of my journey with
OpenStack, that I end up meeting with the great people that have helped
make this happen - just be sure you're wearing a name badge with your irc
handle, or twitter username on!

Cheers,

Kev
-- 
Kevin Jackson
@itarchitectkev
___
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] Can't delete instances with "error" status.

[Gabe Westmaas]

There are definitely lots of cases where deleting an instance in error state 
works fine, and I’d like to know about the cases where it doesn’t.  They do 
count against quota as well, so that’s a problem!

I can see value in keeping an instance around – if the operations team has 
configured it to do so.  However, it seems like the end user has asked for it 
to be deleted and to them it should appear to be deleted.  Johannes had an idea 
a while ago to allow the operations team to specify a project ID that deleted 
servers that match certain criteria should be moved to.  If the delete finishes 
up fine, then its no problem, the delete is done, the customer is happy and the 
ops account is empty.  If it fails for some reason, there is manual cleanup to 
be done, but that should be on the operator of the deployment, not the user.  I 
think its critical for anything like this to be configurable, as public clouds 
and private clouds have different privacy and retention concerns, I would guess.

Do we have cases where we can reliably reproduce this issue?  If its happening 
every time on some deployments there is a very serious problem!

Gabe


From: Craig Vyvial [mailto:cp16...@gmail.com] 
Sent: Thursday, March 22, 2012 2:20 AM
To: Gabe Westmaas
Cc: Yong Sheng Gong; Openstack Mail List
Subject: Re: [Openstack] Can't delete instances with "error" status.

My understanding is that you would not always want a user to delete an instance 
in an error state. So an operations person can figure out what went wrong. I 
think the instances that are in error state do not count against the quota but 
i agree that they clutter up the API calls to list servers. 

I have noticed this with my team and written code around this case to force the 
instance into an 'active' state before sending nova the delete call if the 
instance was in an 'error' or 'suspended' state.

-Craig

On Thu, Mar 22, 2012 at 1:02 AM, Gabe Westmaas  
wrote:
Instances in deleted status can normally be deleted, but there is definitely a 
bug to file here somewhere – possibly more than one.  A common reason I have 
seen is that the node the instance lives on is no longer operating correctly, 
so the compute manager never gets the delete request, so it doesn’t finish.  If 
we can narrow the cases where this happens, we can file bugs and decide how to 
resolve them – although there may be some additional work beyond just a 
developer picking up the bug and working on it to decide what should happen!
 
Do you know how to reliably reproduce an instance in ERROR state that cannot be 
deleted?
 
Gabe
 
From: openstack-bounces+gabe.westmaas=rackspace@lists.launchpad.net 
[mailto:openstack-bounces+gabe.westmaas=rackspace@lists.launchpad.net] On 
Behalf Of Yong Sheng Gong
Sent: Thursday, March 22, 2012 12:58 AM

To: Openstack Mail List
Subject: Re: [Openstack] Can't delete instances with "error" status.
 
why not allow "nova delete" and "euca-terminate " to delete the instance with 
"error" status?

Yong Sheng Gong
 
-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -
To: Guilherme Birk , Openstack Mail List 

From: Mandar Vaze 
Sent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.net
Date: 03/22/2012 12:26PM
Subject: Re: [Openstack] Can't delete instances with "error" status.
I agree user shouldn’t have to update DB. 
There needs to be some periodic cleanup task that “fixes” the 
vm_state/task_state for “stuck” instances.
 
-Mandar
 
From: openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net 
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net] On 
Behalf Of Guilherme Birk
Sent: Wednesday, March 21, 2012 6:05 PM
To: Openstack Mail List
Subject: Re: [Openstack] Can't delete instances with "error" status.
 
This is the only option? I've already done that, but it's kind "strange" I 
update the database row everytime the script identifies a VM with error.

Date: Wed, 21 Mar 2012 09:39:03 +0800
Subject: Re: [Openstack] Can't delete instances with "error" status.
From: mwjpi...@gmail.com
To: guib...@hotmail.com
update "instances" table in "nova" db, set the vm_status of  the instance which 
you want to delete "active" and set the task_status=NULL. 
After that, try to use euca-terminate 
 
On Wed, Mar 21, 2012 at 1:24 AM, Guilherme Birk  wrote:
I'm attempting to make a python script that controls all my virtual machines. 
Sometimes, when the script identifies that exists an instance with status of 
"error", he creates a new instance and tries to delete the old one with curl 
commands, but I'm not getting any response and the VM isn't deleted. When I 
execute euca-terminate instance  I got nothing too. How I should delete 
instances with error status ? I didn't found any way using nova-manage too. 

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