Re: [openstack-dev] Nova list with all-tenants flag

2013-06-17 Thread Ben Nemec
Is there ever a situation where you would use tenant_id and not want all_tenants=1? If there is then I can maybe see leaving it, but if tenant_id implies all_tenants=1 then IMHO it's rather poor to force the user to remember to set it. To be honest, as someone fairly new to OpenStack I found

Re: [openstack-dev] Nova list with all-tenants flag

2013-06-17 Thread Jay Pipes
On 06/17/2013 02:30 PM, Ben Nemec wrote: Is there ever a situation where you would use tenant_id and not want all_tenants=1? If there is then I can maybe see leaving it, but if tenant_id implies all_tenants=1 then IMHO it's rather poor to force the user to remember to set it. To be honest, as

Re: [openstack-dev] Compute node stats sent to the scheduler

2013-06-17 Thread Chris Behrens
On Jun 17, 2013, at 7:49 AM, Russell Bryant rbry...@redhat.com wrote: On 06/16/2013 11:25 PM, Dugger, Donald D wrote: Looking into the scheduler a bit there's an issue of duplicated effort that is a little puzzling. The database table `compute_nodes' is being updated periodically with

[openstack-dev] [Horizon] Second MultipleChoiceList is not showing values...

2013-06-17 Thread Paul Michali
Need some guidance here… Under Launch Instance, Networking tab, we have a custom Horizon version that also has a Policy Profile Checkbox field, in addition to the Network MultipleChoiceList field. Now, we'd like to be able to select a policy for each network selected. The initial thought was

Re: [openstack-dev] Puppet manifests for Grizzly

2013-06-17 Thread Giulio Fidente
On 06/17/2013 06:53 PM, Edgar Magaña Perdomo wrote: Hi Developers, Does anyone has a good collection of puppet manfests for installing openstack grizzly not in a production environment but all in one server is what I am looking for. Anything that I can make use of for some testing. if you're

Re: [openstack-dev] Compute node stats sent to the scheduler

2013-06-17 Thread Brian Elliott
On Jun 17, 2013, at 3:50 PM, Chris Behrens cbehr...@codestud.com wrote: On Jun 17, 2013, at 7:49 AM, Russell Bryant rbry...@redhat.com wrote: On 06/16/2013 11:25 PM, Dugger, Donald D wrote: Looking into the scheduler a bit there's an issue of duplicated effort that is a little puzzling.

Re: [openstack-dev] multiple message backends

2013-06-17 Thread Mark McLoughlin
Hi Paul On Mon, 2013-06-17 at 15:18 -0600, Paul Mathews wrote: Mark, As mentioned at the summit, we've been looking into migrating from qpid to zmq. We have gone through the process of migrating nodes from one set of controllers to another, but that brought about it's own set of

Re: [openstack-dev] [keystone] Inherited domain roles: Options for Havana and beyond

2013-06-17 Thread Henry Nash
Hi So I am also convinced by option a)it is just the time frame. I would be happy to commit to completing this for Havana m3 - but we all agreed that any significant api-changing modifications would be in and stable by m2and that feels like a much taller order. e.g. we need to: -

[openstack-dev] The future of run_tests.sh

2013-06-17 Thread Joe Gordon
Hi All, A patch to move the run_tests.sh script into oslo-incubator ( https://review.openstack.org/#/c/32736/), has brought up the bigger question of what is the future of './run_tests.sh.' This seems like a topic that directly affects all developers, so it sounded like it should be brought to

[openstack-dev] [Quantum] Tested python-quantumclient alpha tarball

2013-06-17 Thread Baldwin, Carl (HPCS Quantum)
I learned from today's quantum meeting on #openstack-meeting that a new alpha tarball for python-quantumclient is available. I'm happy to report that I was able to easily install a working copy with the following commands: $ wget

Re: [openstack-dev] [Swift] code changes feedback

2013-06-17 Thread James E. Blair
Pecoraro, Alex alex.pecor...@emc.com writes: Is there, by chance, a way to submit a patch file to gerrit via a web interface? Just wondering because I'm having a heck of time submitting my changes. My desktop computer seems to be blocked by the corporate firewall and when I try on my laptop

[openstack-dev] tags to deleted branches

2013-06-17 Thread Pádraig Brady
I notice on some projects like nova and quantum (I presume with milestone proposed commits) that the 2013.2.b1 tag was created on the now removed milestone-proposed branch. Therefore `git describe` and `git log --decorate` etc. on master, ignore the latest tag. I was wondering if it would be

Re: [openstack-dev] tags to deleted branches

2013-06-17 Thread Monty Taylor
On 06/18/2013 12:09 AM, Pádraig Brady wrote: I notice on some projects like nova and quantum (I presume with milestone proposed commits) that the 2013.2.b1 tag was created on the now removed milestone-proposed branch. Therefore `git describe` and `git log --decorate` etc. on master,

Re: [openstack-dev] [Tempest] - how to debug

2013-06-17 Thread Gareth
Great thanks, Sean! I'm now working on this. On Fri, Jun 14, 2013 at 7:39 PM, Davanum Srinivas dava...@gmail.com wrote: Just for comparison wsgi http header default is 8192 https://github.com/eventlet/eventlet/blob/master/eventlet/wsgi.py#L19 -- dims On Fri, Jun 14, 2013 at 7:27 AM,