Re: [openstack-dev] [stacktach] [oslo] stachtach - kombu - pika ??

2015-03-12 Thread gordon chung
We're going to be adding support for consuming from and writing to Kafka as well and will likely use a kafka-specific library for that too. is the plan to add this support to oslo.messaging? i believe there is interest from the oslo.messaging team in supporting Kafka and in addition to adding

Re: [openstack-dev] Avoiding regression in project governance

2015-03-12 Thread Thierry Carrez
Ed Leafe wrote: [...] So what is production-ready? And how would you trust any such designation? I think that it should be the responsibility of groups outside of OpenStack development to make that call. We discussed that particular point at the Ops Summit: how to describe and objectively

[openstack-dev] [Murano] PTL Candidacy

2015-03-12 Thread Serg Melikyan
Hi folks, I'd like to announce my candidacy as PTL for Murano [1]. I was handling PTL responsibilities in this release cycle so far, after Ruslan Kamaldinov (who was handling them in Juno cycle) hand over them to me on OpenStack Summit in Paris. I am working on Murano since it's kick-off two

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

2015-03-12 Thread Livnat Peer
Congratulations, well deserved ! On 03/11/2015 07:54 PM, Kyle Mestery wrote: On Wed, Mar 4, 2015 at 1:42 PM, Kyle Mestery mest...@mestery.com mailto:mest...@mestery.com wrote: I'd like to propose that we add Ihar Hrachyshka to the Neutron core reviewer team. Ihar has been doing a

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

2015-03-12 Thread Kevin Benton
The biggest disconnect in the model seems to be that Neutron assumes you want self service networking. Most of these deploys don't. Or even more importantly, they live in an organization where that is never going to be an option. Neutron provider networks is close, except it doesn't provide for

Re: [openstack-dev] [api][neutron] Best API for generating subnets from pool

2015-03-12 Thread Tidwell, Ryan
I agree with dropping support for the wildcards. It can always be revisited at later. I agree that being locked into backward compatibility with a design that we really haven't thought through is a good thing to avoid. Most importantly (to me anyway) is that this will help in getting subnet

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

2015-03-12 Thread Sean Dague
On 03/10/2015 08:52 PM, Joe Gordon wrote: On Tue, Mar 10, 2015 at 5:09 PM, Alan Pevec ape...@gmail.com mailto:ape...@gmail.com wrote: The wheel has been removed from PyPI and anyone installing testtools 1.7.0 now will install from source which works fine. On

[openstack-dev] [stacktach] [oslo] stachtach - kombu - pika ??

2015-03-12 Thread Joshua Harlow
Hi all, I saw the following on https://etherpad.openstack.org/p/PHL-ops-rabbit-queue and was wondering if there was more explanation of why? The StackTach team is switching from Kombu to Pika (at the recommendation of core rabbitmq devs). Hopefully oslo-messaging will do the same. I'm

Re: [openstack-dev] Avoiding regression in project governance

2015-03-12 Thread Kyle Mestery
On Tue, Mar 10, 2015 at 11:46 AM, Doug Hellmann d...@doughellmann.com wrote: On Tue, Mar 10, 2015, at 12:29 PM, Russell Bryant wrote: The TC is in the middle of implementing a fairly significant change in project governance. You can find an overview from Thierry on the OpenStack blog

Re: [openstack-dev] [nova][heat] Autoscaling parameters blueprint

2015-03-12 Thread ELISHA, Moshe (Moshe)
I am familiar of the removal policies. Thanks! Our use case for parameters on scale out is as follows: Every server has a unique index that identifies it. The first server has an index of 1, the second has an index of 2, etc. The index of each server must exist prior to the configuration phase

[openstack-dev] [nova] readout from Philly Operators Meetup

2015-03-12 Thread Sean Dague
The last couple of days I was at the Operators Meetup acting as Nova rep for the meeting. All the sessions were quite nicely recorded to etherpads here - https://etherpad.openstack.org/p/PHL-ops-meetup There was both a specific Nova session - https://etherpad.openstack.org/p/PHL-ops-nova-feedback

Re: [openstack-dev] [neutron][lbaas] v2 vendor drivers

2015-03-12 Thread Kyle Mestery
On Tue, Mar 10, 2015 at 12:08 PM, Doug Wiegley doug...@parksidesoftware.com wrote: Hi all, LBaaS v2 is going out in Kilo, and we have quite a few vendor drivers ready to merge, but most are waiting for the tempest tests/job to be done before they can satisfy their third-party CI

Re: [openstack-dev] Avoiding regression in project governance

2015-03-12 Thread Russell Bryant
On 03/10/2015 12:47 PM, Doug Hellmann wrote: On Tue, Mar 10, 2015, at 12:46 PM, Doug Hellmann wrote: I think we made it pretty clear that we would be taking approvals slowly, and that we might not approve any new projects before the summit, precisely for the reasons you state here. I have

Re: [openstack-dev] [Ironic] proposing rameshg87 to ironic-core

2015-03-12 Thread David Shrewsbury
+1 On Mar 9, 2015, at 6:03 PM, Devananda van der Veen devananda@gmail.com wrote: Hi all, I'd like to propose adding Ramakrishnan (rameshg87) to ironic-core. He's been consistently providing good code reviews, and been in the top five active reviewers for the last 90 days and top

Re: [openstack-dev] [nova][heat] Autoscaling parameters blueprint

2015-03-12 Thread Pavlo Shchelokovskyy
Hi, as you have a separate monitoring solution (not Ceilometer), it seems you can use ResourceGroup instead of AutoscalingGroup and issue heatclient/rest calls to do a stack-update with desired size of the group when needed. The group members will be numbered, and as already said you can also

Re: [openstack-dev] [Neutron][IPAM] Uniqueness of subnets within a tenant

2015-03-12 Thread Carl Baldwin
On Tue, Mar 10, 2015 at 12:06 PM, Ryan Moats rmo...@us.ibm.com wrote: While I'd personally like to see this be restricted (Carl's position), I know of at least one existence proof where management applications are doing precisely what Gabriel is suggesting - reusing the same address range to

Re: [openstack-dev] [Openstack] [Horizon][Keystone] Failed to set up keystone v3 api for horizon

2015-03-12 Thread Trelohan Christophe
Hello, Does user_id replaced in cloud_admin rule is id of cloud_admin user ? I don't think you can log in with cloud_admin user in horizon, it seems that without project created for an user, you can't log in in horizon. I'm also interested in this, I also followed the mentioned article, but

Re: [openstack-dev] [Horizon][Keystone] Failed to set up keystone v3 api for horizon

2015-03-12 Thread Lin Hua Cheng
Hi, The 'cloud_admin' policy file requires domain-scoped to work to work. Horizon does not currently support domain scope token yet. So yes, it is a gap in horizon at the moment. There are on-going patches to address this in horizon: - https://review.openstack.org/#/c/141153/ -

Re: [openstack-dev] [neutron] Prefix delegation using dibbler client

2015-03-12 Thread John Davidge (jodavidg)
I am pleased to say that we are now in a good position with this patch. The necessary DHCPv6 client changes have been made available in the latest release of Dibbler (1.0.1) and we’re getting some much appreciated assistance from Ihar and Thomas in having this new version packaged for wide

Re: [openstack-dev] Avoiding regression in project governance

2015-03-12 Thread Georgy Okrokvertskhov
Some clarification about Murano: 3. *Maybe*. Not sure about the scope, it is fairly broad and there may be some open ended corners, such as some references to billing. On the other hand an application catalog sounds really useful and like a measured progression for OpenStack as a whole. Murano

[openstack-dev] [cinder] cinder is broken until someone fixes the forking code

2015-03-12 Thread Mike Bayer
Hello Cinder - I’d like to note that for issue https://bugs.launchpad.net/oslo.db/+bug/1417018, no solution that actually solves the problem for Cinder is scheduled to be committed anywhere. The patch I proposed for oslo.db is on hold, and the patch proposed for oslo.incubator in the service code

Re: [openstack-dev] Deprecation warnings considered harmful?

2015-03-12 Thread Boris Bobrov
On Thursday 12 March 2015 12:24:57 Duncan Thomas wrote: ubuntu@devstack-multiattach:~/devstack$ cinder-manage db sync /usr/local/lib/python2.7/dist-packages/oslo_db/_i18n.py:19: DeprecationWarning: The oslo namespace package is deprecated. Please use oslo_i18n instead. from oslo import i18n

[openstack-dev] [Kolla] PTL Candidacy

2015-03-12 Thread Steven Dake (stdake)
I am running for PTL for the Kolla project. I have been executing in an unofficial PTL capacity for the project for the Kilo cycle, but I feel it is important for our community to have an elected PTL and have asked Angus Salkeld, who has no outcome in the election, to officiate the election

Re: [openstack-dev] [devstack] pip wheel' requires the 'wheel' package

2015-03-12 Thread Donald Stufft
Is it using an old version of setuptools? Like 0.6.28. On Mar 11, 2015, at 11:28 AM, Timothy Swanson (tiswanso) tiswa...@cisco.com wrote: I don’t have any solution just chiming in that I see the same error with devstack pulled from master on a new ubuntu trusty VM created last night.

[openstack-dev] [nova] Enabling VM post-copy live migration

2015-03-12 Thread Luis Tomas
Hi, As part of an European (FP7) project, named ORBIT (http://www.orbitproject.eu/), I'm working on including the possibility of live-migrating VMs in OpenStack in a post-copy mode. This way of live-migrating VMs basically moves the computation right away to the destination and then the VM

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

2015-03-12 Thread Sean Dague
On 03/11/2015 02:48 PM, Joe Gordon wrote: Out of sync Quotas -- https://etherpad.openstack.org/p/PHL-ops-nova-feedback L63 The quotas code is quite racey (this is kind of a known if you look at the bug tracker). It was actually marked as a top soft spot

Re: [openstack-dev] Deprecation warnings considered harmful?

2015-03-12 Thread John Griffith
On Thu, Mar 12, 2015 at 3:41 AM, Boris Bobrov bbob...@mirantis.com wrote: On Thursday 12 March 2015 12:24:57 Duncan Thomas wrote: ubuntu@devstack-multiattach:~/devstack$ cinder-manage db sync /usr/local/lib/python2.7/dist-packages/oslo_db/_i18n.py:19: DeprecationWarning: The oslo namespace

Re: [openstack-dev] Deprecation warnings considered harmful?

2015-03-12 Thread Duncan Thomas
So, assuming that all of the oslo depreciations aren't going to be fixed before release, we want every user out there to file a bug, for something we know about at release time? This seems to be a very broken model... On 12 March 2015 at 11:41, Boris Bobrov bbob...@mirantis.com wrote: On

Re: [openstack-dev] Deprecation warnings considered harmful?

2015-03-12 Thread Boris Bobrov
On Thursday 12 March 2015 12:59:10 Duncan Thomas wrote: So, assuming that all of the oslo depreciations aren't going to be fixed before release What makes you think that? In my opinion it's just one component's problem. These particular deprecation warnings are a result of still on-going

Re: [openstack-dev] [stable] Icehouse 2014.1.4 freeze exceptions

2015-03-12 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 12:21 PM, Alan Pevec wrote: Hi, next Icehouse stable point release 2014.1.4 has been slipping last few weeks due to various gate issues, see Recently closed section in https://etherpad.openstack.org/p/stable-tracker for details.

Re: [openstack-dev] [nova] need input on possible API change for bug #1420848

2015-03-12 Thread Chen CH Ji
FYI :) you may take a look at doc/source/devref/api_plugins.rst which was merged recently you can take a look at http://lists.openstack.org/pipermail/openstack-dev/2015-March/058493.html and its follow up discussion Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen

[openstack-dev] Fwd: [Neutron] IDSaaS: Request for features

2015-03-12 Thread Mario Tejedor González
I am copying this email from the openstack general list as I have not got any responses from there yet. If any of you has a user profile besides being a developer I would be very interested in your opinion. Hello, I am a MSc student. I am developing an IDSaaS openstack-plugin for my project and I

Re: [openstack-dev] [neutron] VXLAN with single-NIC compute nodes: Avoiding the MTU pitfalls

2015-03-12 Thread Fredy Neeser
On 11.03.2015 19:31, Ian Wells wrote: On 11 March 2015 at 04:27, Fredy Neeser fredy.nee...@solnet.ch mailto:fredy.nee...@solnet.ch wrote: 7: br-ex.1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN group default link/ether e0:3f:49:b4:7c:a7 brd

Re: [openstack-dev] [Openstack] [Horizon][Keystone] Failed to set up keystone v3 api for horizon

2015-03-12 Thread Lei Zhang
I created project for the user admin(6433222efd78459bb70ad9adbcfac418). The token horizon is past is a project scope token. So it can not passed the cloud_admin rule. I changed the rule to the admin_id is a little trick, and it works. On Thu, Mar 12, 2015 at 5:16 PM, Trelohan Christophe

Re: [openstack-dev] [neutron] Generic question about synchronizing neutron agent on compute node with DB

2015-03-12 Thread Leo Y
What does it mean under if that notification is lost, the agent will eventually resynchronize? Is it proven/guaranteed? By what means? Can you, please the process with more details? Or point me to resources that describe it. Thank you On Mon, Mar 9, 2015 at 2:11 AM, Kevin Benton

Re: [openstack-dev] [Horizon][Keystone] Failed to set up keystone v3 api for horizon

2015-03-12 Thread Lei Zhang
Hi Lin, This two PS is what I wanted. Thx a lot. btw, is it possible that these PS finished in Kilo? On Thu, Mar 12, 2015 at 5:41 PM, Lin Hua Cheng os.lch...@gmail.com wrote: Hi, The 'cloud_admin' policy file requires domain-scoped to work to work. Horizon does not currently support

Re: [openstack-dev] [Glance] Nitpicking in code reviews

2015-03-12 Thread Daniel P. Berrange
On Thu, Mar 12, 2015 at 09:07:30AM -0500, Flavio Percoco wrote: On 11/03/15 15:06 -1000, John Bresnahan wrote: FWIW I agree with #3 and #4 but not #1 and #2. Spelling is an easy enough thing to get right and speaks to the quality standard to which the product is held even in commit messages

Re: [openstack-dev] [oslo] oslo.concurrency runtime dependency on fixtures/testtools

2015-03-12 Thread Brant Knudson
On Thu, Mar 12, 2015 at 7:20 AM, Davanum Srinivas dava...@gmail.com wrote: Alan, We are debating this on: https://review.openstack.org/#/c/157135/ Please hop on :) -- dims On Thu, Mar 12, 2015 at 5:28 AM, Alan Pevec ape...@gmail.com wrote: Hi, hijacking this thread to point out

Re: [openstack-dev] [nova][neutron][nfv] is there any reason neutron.allow_duplicate_networks should not be True by default?

2015-03-12 Thread Matt Riedemann
On 3/11/2015 7:23 PM, Ian Wells wrote: On 11 March 2015 at 10:56, Matt Riedemann mrie...@linux.vnet.ibm.com mailto:mrie...@linux.vnet.ibm.com wrote: While looking at some other problems yesterday [1][2] I stumbled across this feature change in Juno [3] which adds a config option

Re: [openstack-dev] [Glance] Nitpicking in code reviews

2015-03-12 Thread Flavio Percoco
On 11/03/15 15:06 -1000, John Bresnahan wrote: FWIW I agree with #3 and #4 but not #1 and #2. Spelling is an easy enough thing to get right and speaks to the quality standard to which the product is held even in commit messages and comments (consider the 'broken window theory'). Of course

Re: [openstack-dev] [nova] need input on possible API change for bug #1420848

2015-03-12 Thread Christopher Yeoh
FWIW I think we need to consider that the API is completely froxen for the V2 API (so this freeze does not apply to v2.1 microversions) except under very serious circumstances and only very high priority bug fixes and only apply this to a suitable microversion bump. We really want to get rid of

Re: [openstack-dev] [nova] need input on possible API change for bug #1420848

2015-03-12 Thread Christopher Yeoh
On Thu, Mar 12, 2015 at 11:19 PM, Christopher Yeoh cbky...@gmail.com wrote: On Wed, 11 Mar 2015 09:32:11 -0600 Chris Friesen chris.frie...@windriver.com wrote: Hi, I'm working on bug #1420848 which addresses the issue that doing a service-disable followed by a service-enable against

[openstack-dev] [nova] proper way to extend index() and add a new property?

2015-03-12 Thread Chris Friesen
I'm looking for some technical advice on API extensions. I want to add a new field to the output of the nova service-list command, which currently maps to ServiceController.index(). For the v2 API this seems straightforward, I can add a new extension and in the existing function I can call

Re: [openstack-dev] [neutron] Generic question about synchronizing neutron agent on compute node with DB

2015-03-12 Thread Assaf Muller
- Original Message - However, I briefly looked through the L2 agent code and didn't see a periodic task to resync the port information to protect from a neutron server that failed to send a notification because it crashed or lost its amqp connection. The L3 agent has a period

Re: [openstack-dev] A question on static routes on Neutron router

2015-03-12 Thread Kevin Benton
Yes, the extra routes extension allows IP addresses from any of the networks connected to the router. I see in the code that send_redirects is set to 0 so it will not generate ICMP redirect messages in the case you mentioned. I don't see anything obviously preventing the forwarding to a next hop

Re: [openstack-dev] A question on static routes on Neutron router

2015-03-12 Thread Maria Napierala
Yes, the extra routes extension allows IP addresses from any of the networks connected to the router. I see in the code that send_redirects is set to 0 so it will not generate ICMP redirect messages in the case you mentioned. I don't see anything obviously preventing the forwarding to a

Re: [openstack-dev] [neutron] Generic question about synchronizing neutron agent on compute node with DB

2015-03-12 Thread Kevin Benton
If there are any errors on the agent connecting to the message bus or retrieving messages, an exception will be thrown in the main rpc_loop, which will be caught and a sync flag will be set to true, which will trigger the sync on the next loop. However, I briefly looked through the L2 agent code

Re: [openstack-dev] [neutron] Generic question about synchronizing neutron agent on compute node with DB

2015-03-12 Thread Kevin Benton
Yeah, I was making a bad assumption for the l2 and l3. Sorry about that. It sounds like we don't have any protection against servers failing to send notifications. On Mar 12, 2015 7:41 PM, Assaf Muller amul...@redhat.com wrote: - Original Message - However, I briefly looked through

Re: [openstack-dev] [neutron] Generic question about synchronizing neutron agent on compute node with DB

2015-03-12 Thread YAMAMOTO Takashi
However, I briefly looked through the L2 agent code and didn't see a periodic task to resync the port information to protect from a neutron server that failed to send a notification because it crashed or lost its amqp connection. The L3 agent has a period sync routers task that helps in this

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

2015-03-12 Thread Zhi Yan Liu
I'd prefer 1400UTC. zhiyan On Mon, Mar 9, 2015 at 4:07 AM, Nikhil Komawar nikhil.koma...@rackspace.com wrote: Hi all, Currently, we've alternating time for Glance meetings. Now, with the Daylight savings being implemented in some parts of the world, we're thinking of moving the meeting

Re: [openstack-dev] [oslo] oslo.concurrency runtime dependency on fixtures/testtools

2015-03-12 Thread Ben Nemec
On 03/12/2015 09:18 AM, Brant Knudson wrote: On Thu, Mar 12, 2015 at 7:20 AM, Davanum Srinivas dava...@gmail.com wrote: Alan, We are debating this on: https://review.openstack.org/#/c/157135/ Please hop on :) -- dims On Thu, Mar 12, 2015 at 5:28 AM, Alan Pevec ape...@gmail.com wrote:

[openstack-dev] [all] oslo.config 1.9.3 release

2015-03-12 Thread Doug Hellmann
The Oslo team is content to announce the release of: oslo.config 1.9.3: Oslo Configuration API For more details, please see the git log history below and: http://launchpad.net/oslo.config/+milestone/1.9.3 Please report issues through launchpad: http://bugs.launchpad.net/oslo.config

[openstack-dev] [all] oslo.db 1.7.0 release

2015-03-12 Thread Doug Hellmann
The Oslo team is content to announce the release of: oslo.db 1.7.0: oslo.db library For more details, please see the git log history below and: http://launchpad.net/oslo.db/+milestone/1.7.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.db Notable changes

Re: [openstack-dev] [nova] Enabling VM post-copy live migration

2015-03-12 Thread John Garbutt
On 12 March 2015 at 12:26, Luis Tomas l...@cs.umu.se wrote: On 03/12/2015 12:34 PM, John Garbutt wrote: On 12 March 2015 at 08:41, Luis Tomas l...@cs.umu.se wrote: Hi, As part of an European (FP7) project, named ORBIT (http://www.orbitproject.eu/), I'm working on including the possibility

Re: [openstack-dev] [devstack] pip wheel' requires the 'wheel' package

2015-03-12 Thread Timothy Swanson (tiswanso)
Hi guys, I got to this again today and realized that I had copied a local.conf w/ OFFLINE=True”. Removing that resolved the issue w/ the run of stack.sh. Hope that helps! —Tim On Mar 11, 2015, at 12:41 PM, Donald Stufft don...@stufft.iomailto:don...@stufft.io wrote: Is it using an old

[openstack-dev] [QA][Keystone] Test plan template

2015-03-12 Thread Adam Young
I posted a test plan temoplate for review. WHile my template is specific to Keystone, I think that it will benefit from a wider review. I did not see a comparable document elsewhere. There are the qa specs, but those look more like feature proposals for QA infrastructure than for test

Re: [openstack-dev] [stable] Icehouse 2014.1.4 freeze exceptions

2015-03-12 Thread Tristan Cacqueray
On 03/12/2015 07:33 AM, Ihar Hrachyshka wrote: For OSSA patch, there seems to be some concerns and issues with the patch that was developed under embargo. It seems it will take more time than expected to merge it in master. It may mean we will actually miss the backport for 2014.1.4. The

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

2015-03-12 Thread Okuma, Wayne
My vote is for 1500. -Original Message- From: Hemanth Makkapati [mailto:hemanth.makkap...@rackspace.com] Sent: Thursday, March 12, 2015 8:32 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

[openstack-dev] FW: [nova] readout from Philly Operators Meetup

2015-03-12 Thread Tim Bell
I completely agree with you - Sean and Joe. Since the argument was brought up I just wanted to point out that this quota service thing is a bit of a unicorn at the moment, and it should not distract from fixing and improving quota maangement enforcement logic in the various openstack

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

2015-03-12 Thread Hemanth Makkapati
+1 to consistent time. Both 1400 and 1500 work me. -Hemanth From: Ian Cordasco ian.corda...@rackspace.com Sent: Wednesday, March 11, 2015 10:25 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Glance]

Re: [openstack-dev] [Ironic] proposing rameshg87 to ironic-core

2015-03-12 Thread Devananda van der Veen
Without further ado, and since everyone (even though some haven't replied here) has +1'd this, and since we could really use ramesh's +2's in the run up to Kilo-3 and feature freeze, even without the customary waiting/voting period being completely satisfied (after all, when we all agree, why wait

[openstack-dev] [all] oslo.policy 0.3.1 release

2015-03-12 Thread Doug Hellmann
The Oslo team is content to announce the release of: oslo.policy 0.3.1: RBAC policy enforcement library for OpenStack For more details, please see the git log history below and: http://launchpad.net/oslo.policy/+milestone/0.3.1 Please report issues through launchpad:

[openstack-dev] [all] oslo.concurrency 1.8.0 release

2015-03-12 Thread Doug Hellmann
The Oslo team is content to announce the release of: oslo.concurrency 1.8.0: oslo.concurrency library For more details, please see the git log history below and: http://launchpad.net/oslo.concurrency/+milestone/1.8.0 Please report issues through launchpad:

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

2015-03-12 Thread Clint Byrum
Excerpts from Sean Dague's message of 2015-03-11 05:59:10 -0700: = Additional Interesting Bits = Rabbit -- There was a whole session on Rabbit - https://etherpad.openstack.org/p/PHL-ops-rabbit-queue Rabbit is a top

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

2015-03-12 Thread Sean Dague
On 03/12/2015 12:47 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-03-11 05:59:10 -0700: = Additional Interesting Bits = Rabbit -- There was a whole session on Rabbit -

Re: [openstack-dev] Deprecation warnings considered harmful?

2015-03-12 Thread John Griffith
On Thu, Mar 12, 2015 at 10:48 AM, Doug Hellmann d...@doughellmann.com wrote: On Thu, Mar 12, 2015, at 05:24 AM, Duncan Thomas wrote: ubuntu@devstack-multiattach:~/devstack$ cinder-manage db sync /usr/local/lib/python2.7/dist-packages/oslo_db/_i18n.py:19: DeprecationWarning: The oslo

Re: [openstack-dev] FW: [nova] readout from Philly Operators Meetup

2015-03-12 Thread Sajeesh Cimson Sasi
Hi Salvatore, We had a short discussion on Hierarchical quota management in nova somewhere in December. The spec was approved ,but the code couldn't make it to Kilo. I am trying to get it merged in Liberty. Implementation is over. Only test cases are pending. I have

Re: [openstack-dev] Deprecation warnings considered harmful?

2015-03-12 Thread Doug Hellmann
On Thu, Mar 12, 2015, at 05:24 AM, Duncan Thomas wrote: ubuntu@devstack-multiattach:~/devstack$ cinder-manage db sync /usr/local/lib/python2.7/dist-packages/oslo_db/_i18n.py:19: DeprecationWarning: The oslo namespace package is deprecated. Please use oslo_i18n instead. from oslo import

Re: [openstack-dev] [nova] proper way to extend index() and add a new property?

2015-03-12 Thread Chris Friesen
On 03/12/2015 08:47 AM, Chris Friesen wrote: I'm looking for some technical advice on API extensions. I want to add a new field to the output of the nova service-list command, which currently maps to ServiceController.index(). For the v2 API this seems straightforward, I can add a new

Re: [openstack-dev] [Horizon][Keystone] Failed to set up keystone v3 api for horizon

2015-03-12 Thread Ali, Haneef
Horizon needs to support domain scoped token for this to work. I don’t think it is yet there. https://review.openstack.org/#/c/148082/39 https://review.openstack.org/#/c/141153/ Thanks Haneef From: Lei Zhang [mailto:zhang.lei@gmail.com] Sent: Wednesday, March 11, 2015 7:33 PM To:

[openstack-dev] [Glance] Experimental API

2015-03-12 Thread Sampath, Lakshmi
We had a discussion with API WG today about what it means to be an EXPERIMENTAL API and here's the takeway from that discussion. - API's can be experimental, but mark it clearly in the docs as such - Experimental means a breaking change may be introduced - Use /x1/ instead of /v1/ in the

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

2015-03-12 Thread Clint Byrum
Excerpts from Doug Hellmann's message of 2015-03-12 10:04:57 -0700: On Thu, Mar 12, 2015, at 12:47 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-03-11 05:59:10 -0700: = Additional Interesting Bits =

Re: [openstack-dev] [neutron] [metadata] metadata service when NOT using name space

2015-03-12 Thread Wanjing Xu
Assaf Thanks for replying. I have been playing around metadata service to make sure our product is not breaking it. If namespace is really needed if we want metadata service, then we need to know about it and document it in our product. Thanks and Regards! Wanjing Date: Wed, 11 Mar 2015

[openstack-dev] [openstack-operators][rally] What's new in Rally v0.0.2

2015-03-12 Thread Boris Pavlovic
Hi stackers, For those who doesn't know Rally team started making releases. There are 3 major reasons why we started doing releases: * A lot of people started using Rally in their CI/CD. Usually they don't like to depend on something that is from master. And would like to have smooth

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

2015-03-12 Thread Doug Hellmann
On Thu, Mar 12, 2015, at 12:47 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-03-11 05:59:10 -0700: = Additional Interesting Bits = Rabbit -- There was a whole session on Rabbit -

Re: [openstack-dev] Deprecation warnings considered harmful?

2015-03-12 Thread Joshua Harlow
Also note that the following is supposed to be true (or should be?): From: https://docs.python.org/2/library/warnings.html#warning-categories DeprecationWarning: Base category for warnings about deprecated features (ignored by default). Changed in version 2.7: DeprecationWarning is ignored

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

2015-03-12 Thread Clint Byrum
Excerpts from Sean Dague's message of 2015-03-12 09:59:35 -0700: On 03/12/2015 12:47 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-03-11 05:59:10 -0700: = Additional Interesting Bits = Rabbit --

Re: [openstack-dev] [Glance] Nitpicking in code reviews

2015-03-12 Thread Jim Rollenhagen
On Thu, Mar 12, 2015 at 09:07:30AM -0500, Flavio Percoco wrote: On 11/03/15 15:06 -1000, John Bresnahan wrote: FWIW I agree with #3 and #4 but not #1 and #2. Spelling is an easy enough thing to get right and speaks to the quality standard to which the product is held even in commit messages

[openstack-dev] [nova] is it possible to microversion a static class method?

2015-03-12 Thread Chris Friesen
Hi, I'm having an issue with microversions. The api_version() code has a comment saying This decorator MUST appear first (the outermost decorator) on an API method for it to work correctly I tried making a microversioned static class method like this: @wsgi.Controller.api_version(2.4)

Re: [openstack-dev] [nova] is it possible to microversion a static class method?

2015-03-12 Thread Sean Dague
On 03/12/2015 02:03 PM, Chris Friesen wrote: Hi, I'm having an issue with microversions. The api_version() code has a comment saying This decorator MUST appear first (the outermost decorator) on an API method for it to work correctly I tried making a microversioned static class method

[openstack-dev] [Glance] Reviews.

2015-03-12 Thread Nikhil Komawar
Hi all (and specifically Glance cores reviewers), We are approaching a Feature Freeze and there are reviews pending on multiple features [1]. I think as Good Samaritans and members of Glance community, we'd focus our reviews on the code that is expecting our attention in due time. So, let's

Re: [openstack-dev] [Glance] Experimental API

2015-03-12 Thread Alexander Tivelkov
Thanks Lakshmi, that's useful. So, we want to release Artifacts API in Kilo as experimental. We do need some early adopters to begin working with it (the initial interest was from Heat and Murano projects, and the OVA/OVF initiative for Images as well) in the next cycle and provide some feedback

Re: [openstack-dev] [nova] need input on possible API change for bug #1420848

2015-03-12 Thread Chris Friesen
So I've been playing with microversions and noticed that the information about req.ver_obj.matches(start_version, end_version) in the spec doesn't actually match what's in the codebase. 1) The code has req.api_version_request instead of req.ver_obj 2) The spec says that end_version is

Re: [openstack-dev] [all] Do we need release announcements for all the things?

2015-03-12 Thread Boris Pavlovic
Clint, Personally I am quite interested in new releases of python clients and oslo stuff, but I believe that oslo releases announcement should be merged to single email with rate limit 1 email per week. It will be much simpler at least for me to track stuff. Best regards, Boris Pavlovic On

Re: [openstack-dev] [all] Do we need release announcements for all the things?

2015-03-12 Thread Gregory Haynes
Excerpts from Clint Byrum's message of 2015-03-12 20:22:04 +: I spend a not-insignificant amount of time deciding which threads to read and which to fully ignore each day, so extra threads mean extra work, even with a streamlined workflow of single-key-press-per-thread. So I'm wondering

Re: [openstack-dev] Deprecation warnings considered harmful?

2015-03-12 Thread Robert Collins
On 13 March 2015 at 08:09, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/12/2015 11:38 AM, Boris Bobrov wrote: On Thursday 12 March 2015 12:59:10 Duncan Thomas wrote: So, assuming that all of the oslo depreciations aren't going to be fixed

Re: [openstack-dev] [Horizon] [swift] dependency on non-standardized, private APIs

2015-03-12 Thread Jay Pipes
On 03/12/2015 05:09 PM, John Dickinson wrote: On Mar 12, 2015, at 12:48 PM, Jay Pipes jaypi...@gmail.com wrote: On 03/12/2015 03:08 PM, John Dickinson wrote: I'd like a little more info here. Is Horizon relying on the X-Timestamp header for reads (GET/HEAD)? If so, I think that's somewhat

Re: [openstack-dev] [Horizon] [swift] dependency on non-standardized, private APIs

2015-03-12 Thread John Dickinson
On Mar 12, 2015, at 12:48 PM, Jay Pipes jaypi...@gmail.com wrote: On 03/12/2015 03:08 PM, John Dickinson wrote: I'd like a little more info here. Is Horizon relying on the X-Timestamp header for reads (GET/HEAD)? If so, I think that's somewhat odd, but not hugely problematic. Swift has

Re: [openstack-dev] Deprecation warnings considered harmful?

2015-03-12 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/12/2015 09:35 PM, Robert Collins wrote: On 13 March 2015 at 08:09, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/12/2015 11:38 AM, Boris Bobrov wrote: On Thursday 12 March 2015 12:59:10

Re: [openstack-dev] [all] Do we need release announcements for all the things?

2015-03-12 Thread Jeremy Stanley
On 2015-03-12 13:22:04 -0700 (-0700), Clint Byrum wrote: [...] So I'm wondering what people are getting from these announcements being on the discussion list. [...] The main thing I get from them is that they're being recorded to a (theoretically) immutable archive indexed by a lot of other

Re: [openstack-dev] [nova] is it possible to microversion a static class method?

2015-03-12 Thread Chen CH Ji
Know it's a little bit tricky but from doc/source/devref/api_microversions.rst, can we make _version_specific_func static function thought it's not required or we can explicitly suggest not to do so... 91 @api_version(2.1, 2.4) 92 def _version_specific_func(self, req, arg1): 93

Re: [openstack-dev] [Glance] Nitpicking in code reviews

2015-03-12 Thread Ian Cordasco
On 3/12/15, 09:26, Daniel P. Berrange berra...@redhat.com wrote: On Thu, Mar 12, 2015 at 09:07:30AM -0500, Flavio Percoco wrote: On 11/03/15 15:06 -1000, John Bresnahan wrote: FWIW I agree with #3 and #4 but not #1 and #2. Spelling is an easy enough thing to get right and speaks to the

Re: [openstack-dev] [Glance] Nitpicking in code reviews

2015-03-12 Thread Nikhil Komawar
+2A :P (Daniel and Ian) Thanks, -Nikhil From: Ian Cordasco ian.corda...@rackspace.com Sent: Thursday, March 12, 2015 10:59 AM To: Daniel P. Berrange; OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Glance]

Re: [openstack-dev] Deprecation warnings considered harmful?

2015-03-12 Thread Jay S. Bryant
Duncan, If you see any of these coming out of Cinder (not oslo) please get a bug to me. I think I have them all removed but need to know if I have missed anything. Thanks! Jay On 03/12/2015 04:24 AM, Duncan Thomas wrote: ubuntu@devstack-multiattach:~/devstack$ cinder-manage db sync

[openstack-dev] [all] Do we need release announcements for all the things?

2015-03-12 Thread Clint Byrum
I spend a not-insignificant amount of time deciding which threads to read and which to fully ignore each day, so extra threads mean extra work, even with a streamlined workflow of single-key-press-per-thread. So I'm wondering what people are getting from these announcements being on the

Re: [openstack-dev] [Horizon] [swift] dependency on non-standardized, private APIs

2015-03-12 Thread Jay Pipes
On 03/12/2015 03:08 PM, John Dickinson wrote: I'd like a little more info here. Is Horizon relying on the X-Timestamp header for reads (GET/HEAD)? If so, I think that's somewhat odd, but not hugely problematic. Swift has been returning an X-Timestamp header since patch b20264c9d3196 (which

[openstack-dev] [puppet] Re-schedule Puppet OpenStack meeting

2015-03-12 Thread Emilien Macchi
Hi everyone, Since OPS midcycle discussions, it seems we need to reschedule the meeting again. Here is the poll to do it: https://doodle.com/wuhsuafq5tibzugg Next meeting stays on Monday and we'll close this on Thursday of next week. Thanks, -- Emilien Macchi signature.asc Description:

Re: [openstack-dev] [Horizon][Keystone] Failed to set up keystone v3 api for horizon

2015-03-12 Thread Doug Fish
I'm sure additional feedback on those patches would be welcome and helpful toward getting them merged in Kilo On Mar 12, 2015, at 9:14 AM, Lei Zhang zhang.lei@gmail.com wrote: Hi Lin, This two PS is what I wanted. Thx a lot. btw, is it possible that these PS finished in Kilo? On

Re: [openstack-dev] [Glance] Experimental API

2015-03-12 Thread Jay Pipes
On 03/12/2015 01:19 PM, Sampath, Lakshmi wrote: We had a discussion with API WG today about what it means to be an EXPERIMENTAL API and here's the takeway from that discussion. All experimental means with regards to an API is we reserve the right to completely abandon this or change it in

Re: [openstack-dev] [Glance] Experimental API

2015-03-12 Thread Dean Troyer
On Thu, Mar 12, 2015 at 1:42 PM, Brian Rosmaita brian.rosma...@rackspace.com wrote: I don't know how elaborate we want to get here, but Everett Toews had an interesting suggestion in the openstack-api channel. It would go something like this: (1) User gets /x1/search endpoint from service

  1   2   >