Re: [openstack-dev] [Fuel] Doc team working with bugs

2014-09-09 Thread Mike Scherbakov
+1 for tags On Tue, Sep 9, 2014 at 12:05 AM, Anne Gentle a...@openstack.org wrote: On Mon, Sep 8, 2014 at 9:04 AM, Jay Pipes jaypi...@gmail.com wrote: On 09/08/2014 03:46 AM, Dmitry Mescheryakov wrote: Hello Fuelers, On the previous meeting a topic was raised on how Fuel doc team should

Re: [openstack-dev] memory usage in devstack-gate (the oom-killer strikes again)

2014-09-09 Thread Chmouel Boudjnah
On Tue, Sep 9, 2014 at 12:24 AM, Joe Gordon joe.gord...@gmail.com wrote: 1) Should we explicitly set the number of workers that services use in devstack? Why have so many workers in a small all-in-one environment? What is the right balance here? This is what we do for Swift, without

Re: [openstack-dev] China blocking access to OpenStack git review push

2014-09-09 Thread Baohua Yang
There're several ways to overcome the problem. Other than https, using the socks proxy is also possible. $ sudo aptitude install connect-proxy ##for windows, just install the git $ cat ~/.ssh/config Host review.openstack.org ProxyCommand connect -S *PROXY_IP*:*PORT* %h %p IdentityFile

[openstack-dev] [Glance] Please, help testing Glance and keeping glance_store updated

2014-09-09 Thread Flavio Percoco
Greetings, Yesterday, the switch-over to glance_store[0] landed. I'm really happy about this since it'll, I believe, help us to clean up the code in glance and have a better abstraction for the storage code. These are just 2 of a set of really important benefits. Anyway... I'd like to give a

[openstack-dev] [Cinder] [Devstack] - Create Volume is called in an infinite loop

2014-09-09 Thread Amit Das
Hi All, I have been running tempest tests on my cinder driver for about a month now. However, since last week i see the create volume logic was attempted thrice by the scheduler after a failure during volume creation. However, i would like the scheduler not to attempt after a failure in volume

[openstack-dev] [All] Maintenance mode in OpenStack during patching/upgrades

2014-09-09 Thread Mike Scherbakov
Hi all, please see below original email below from Dmitry. I've modified the subject to bring larger audience to the issue. I'd like to split the issue into two parts: 1. Maintenance mode for OpenStack controllers in HA mode (HA-ed Keystone, Glance, etc.) 2. Maintenance mode for

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

2014-09-09 Thread Daniel P. Berrange
On Mon, Sep 08, 2014 at 05:20:54PM -0700, Stefano Maffulli wrote: On 09/05/2014 07:07 PM, James Bottomley wrote: Actually, I don't think this analysis is accurate. Some people are simply interested in small aspects of a project. It's the scratch your own itch part of open source. The

Re: [openstack-dev] [neutron][policy] Group-based Policy next steps

2014-09-09 Thread Sumit Naiksatam
On Sat, Sep 6, 2014 at 9:54 AM, Prasad Vellanki prasad.vella...@oneconvergence.com wrote: Good discussion. Based on this I think we should get started on the stackforge right away. Sumit - It would be great if you get started on the StackForge soon. We have a few changes that needs to be

Re: [openstack-dev] Kilo Cycle Goals Exercise

2014-09-09 Thread Michael Still
I haven't had a chance to read other people's posts, so I am sure there is duplication here. What would I have all of OpenStack working on if I was ruler of the universe? Let's see... 1. Fixing our flakey gate: we're all annoyed by our code failing tests with transient errors, but most people

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

2014-09-09 Thread Mike Scherbakov
+1 to DmitryB, I think in this particular time and case we should open stable/5.1. But not to call it HCF [1]. Though I think we should retrospect our approaches here. 1. Sometimes we can squash 30 bugs a day, and formally reach HCF. Though the day after we will get 30 New bugs from QA. We

Re: [openstack-dev] about Distributed OpenStack Cluster

2014-09-09 Thread Vo Hoang, Tri
Hi Jesse Pretorius, if you read my whole mail carefully, it’s about the current development of OpenStack Cascading [1] and future development of OpenStack for distributed cluster. And I don’t see it fits to Ops at all. Many thanks. Kind Regards, Tri Hoang Vo From: Jesse Pretorius

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

2014-09-09 Thread Igor Marnat
Mike, just to clarify - do we want consider this as an exception, which is not going to be repeated next release? If not, we might want to consider updating the statement It is the time when master opens for next release changes, including features. in [1]. If I got you correct, we are going to

Re: [openstack-dev] [NFV] NFV Meetings

2014-09-09 Thread MENDELSOHN, ITAI (ITAI)
Hi, Was looking at the wrong channel last week…. Looked at the minutes. Tnx for raising the topic. Let’s discuss this week. Tnx! I On 9/8/14, 5:49 PM, Steve Gordon sgor...@redhat.com wrote: - Original Message - From: ITAI MENDELSOHN (ITAI) itai.mendels...@alcatel-lucent.com To:

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

2014-09-09 Thread Mike Scherbakov
Currently I think we should take it as an exception, and discuss two points which I brought up. Obviously, if we open stable/5.1, then we are opening master for new features. We will modify HCF definition once we settle on final decision. Thanks, On Tue, Sep 9, 2014 at 1:02 PM, Igor Marnat

[openstack-dev] [Fuel] master access control - future work

2014-09-09 Thread Lukasz Oles
Dear Fuelers, I have some ideas and questions to share regarding Fuel Master access control. During 5,1 cycle we made some non optimal decision which we have to fix. The following blueprint describes required changes:

Re: [openstack-dev] [Heat] Request for python-heatclient project to adopt heat-translator

2014-09-09 Thread Steven Hardy
Hi Sahdev, On Tue, Sep 02, 2014 at 11:52:30AM -0400, Sahdev P Zala wrote: Hello guys, As you know, the heat-translator project was started early this year with an aim to create a tool to translate non-Heat templates to HOT. It is a StackForge project licensed under Apache 2.

Re: [openstack-dev] [Fuel] SSL in Fuel

2014-09-09 Thread Guillaume Thouvenin
I think that the management of certificates should be discussed in the ca-deployment blueprint [3] We had some discussions and it seems that one idea is to use a docker container as the root authority. By doing this we should be able to sign certificate from Nailgun and distribute the certificate

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

2014-09-09 Thread Aleksandra Fedorova
As I understand your proposal, we need to split our HCF milestone into two check points: Branching Point and HCF itself. Branching point should happen somewhere in between SCF and HCF. And though It may coincide with HCF, it needs its own list of requirements. This will give us the possibility to

[openstack-dev] [sahara] summit session brainstorming

2014-09-09 Thread Sergey Lukjanov
Hi sahara folks, I'd like to start brainstorming ideas for the upcoming summit design sessions earlier than previous times to have more time to discuss topics and prioritize / filter / prepare them. Here is an etherpad to start the brainstorming:

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

2014-09-09 Thread Matthew Booth
On 09/09/14 01:20, Stefano Maffulli wrote: From conversations with PTLs and core reviewers I get the impression that lots of drivers contributions come with bad code. These require a lot of time and reviewers energy to be cleaned up, causing burn out and bad feelings on all sides. What if we

[openstack-dev] [ceilometer]How to collect the real-time data

2014-09-09 Thread lijian
Hi folks, We know the ceilometer collect the data through poster periodically. But how to collect the real-time data? whether plan to implement it or not Thanks! Jian Li ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org

Re: [openstack-dev] [ceilometer]How to collect the real-time data

2014-09-09 Thread Dina Belova
Jian, hello What do you actually mean by 'real-time data'? Here in Ceilometer we're having 'events' feature, for instance - so services like Nova, Cinder, etc. are notifying Ceilometer about recent changes like 'VM was created', 'IP was assigned', etc. - this data is more than recent one. May

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-09 Thread Gary Kotton
On 9/8/14, 7:23 PM, Sylvain Bauza sba...@redhat.com wrote: Le 08/09/2014 18:06, Steven Dake a écrit : On 09/05/2014 06:10 AM, Sylvain Bauza wrote: Le 05/09/2014 12:48, Sean Dague a écrit : On 09/05/2014 03:02 AM, Sylvain Bauza wrote: Le 05/09/2014 01:22, Michael Still a écrit : On Thu,

[openstack-dev] [Designate][Horizon][Tempest][DevStack] Supporting code for incubated projects

2014-09-09 Thread Mac Innes, Kiall
Hi all, While requesting a openstack/designate-dashboard project from the TC/ Infra - The topic of why Designate panels, as an incubated project, can't be merged into openstack/horizon was raised. In the openstack/governance review[1], Russell asked: Hm, I think we should discuss this with

Re: [openstack-dev] [All] Maintenance mode in OpenStack during patching/upgrades

2014-09-09 Thread Sergii Golovatiuk
Hi Fuelers, 1. Sometimes fuel has non reversible changes. Here are a couple of samples A new version needs to change/adjust Pacemaker primitives. Such changes affect all controllers in cluster. A old API can be deprecated or new API can be introduced. Until we all components configured to use new

Re: [openstack-dev] [ceilometer]How to collect the real-time data

2014-09-09 Thread lijian
Hello Dina, 'real-time data' like the utilization of vcpu, mem, storage for a instance that collected by the poster. I realy want to collect the meters by demand, and do not store the data to the database I know the ceilometer event can not cover the above meters so, I think we can enhance the

[openstack-dev] [Cinder] Request for J3 FFE - add reset-state function for backups

2014-09-09 Thread yunling
Hi Cinder Folks,I would like to request a FFE for add reset-state function for backups[1][2].The spec of add reset-state function for backups has been reviewed and merged[2]. These code changes have been well tested and are not very complex[3]. I would appreciate any consideration for an

[openstack-dev] [neutron] List of BPs with an FFE

2014-09-09 Thread Kyle Mestery
The list of BPs for Neutron with an FFE are now targeted in the RC1 page here [1]. Please focus on reviewing these, we have a short window to merge this. I believe the window closes on Friday this week (9-12-2014), but I'll verify with Thierry in my 1:1 with him today. We'll also spend a good

Re: [openstack-dev] [qa][all][Heat] Packaging of functional tests

2014-09-09 Thread Zane Bitter
On 04/09/14 10:45, Jay Pipes wrote: On 08/29/2014 05:15 PM, Zane Bitter wrote: On 29/08/14 14:27, Jay Pipes wrote: On 08/26/2014 10:14 AM, Zane Bitter wrote: Steve Baker has started the process of moving Heat tests out of the Tempest repository and into the Heat repository, and we're looking

[openstack-dev] [oslo] Juno RC1 and beyond

2014-09-09 Thread Doug Hellmann
With some help from Thierry, we finally have our launchpad projects cleaned up and configured so we can use them correctly for tracking. I have reviewed our etherpad [1] and updated all of the bugs referenced in the RC1 section so they are now listed on

[openstack-dev] [sahara] FFEs list

2014-09-09 Thread Sergey Lukjanov
Hi sahara folks, here is a list of approved Feature Freeze Exceptions: * https://blueprints.launchpad.net/sahara/+spec/cluster-persist-sahara-configuration * https://blueprints.launchpad.net/sahara/+spec/edp-swift-trust-authentication *

Re: [openstack-dev] [Designate][Horizon][Tempest][DevStack] Supporting code for incubated projects

2014-09-09 Thread Thierry Carrez
Mac Innes, Kiall wrote: While requesting a openstack/designate-dashboard project from the TC/Infra – The topic of why Designate panels, as an incubated project, can’t be merged into openstack/horizon was raised. In the openstack/governance review[1], Russell asked: Hm, I think we

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

2014-09-09 Thread James Bottomley
On Mon, 2014-09-08 at 17:20 -0700, Stefano Maffulli wrote: On 09/05/2014 07:07 PM, James Bottomley wrote: Actually, I don't think this analysis is accurate. Some people are simply interested in small aspects of a project. It's the scratch your own itch part of open source. The thing

Re: [openstack-dev] [Designate][Horizon][Tempest][DevStack] Supporting code for incubated projects

2014-09-09 Thread Akihiro Motoki
On Tue, Sep 9, 2014 at 10:23 PM, Thierry Carrez thie...@openstack.org wrote: Mac Innes, Kiall wrote: While requesting a openstack/designate-dashboard project from the TC/Infra – The topic of why Designate panels, as an incubated project, can’t be merged into openstack/horizon was raised. In

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

2014-09-09 Thread Mike Scherbakov
Thanks Alexandra. We land a few patches a day currently, so I think we can open stable branch. If we see no serious objections in next 12 hours, let's do it. We would need to immediately notify everyone in mailing list - that for every patch for 5.1, it should go first to master, and then to

Re: [openstack-dev] how to provide tests environments for python things that require C extensions

2014-09-09 Thread Doug Hellmann
On Sep 8, 2014, at 8:18 PM, James E. Blair cor...@inaugust.com wrote: Sean Dague s...@dague.net writes: The crux of the issue is that zookeeper python modules are C extensions. So you have to either install from packages (which we don't do in unit tests) or install from pip, which means

[openstack-dev] Hyper-V meeting today.

2014-09-09 Thread Peter Pouliot
Hi everyone, Due to an overload of critical work in the CI we will be postponing this weeks hyper-v meeting. We will resume with the regular schedule next week. p Peter J. Pouliot CISSP Sr. SDET OpenStack Microsoft New England Research Development Center 1 Memorial Drive Cambridge, MA 02142

Re: [openstack-dev] how to provide tests environments for python things that require C extensions

2014-09-09 Thread Sean Dague
On 09/09/2014 10:41 AM, Doug Hellmann wrote: On Sep 8, 2014, at 8:18 PM, James E. Blair cor...@inaugust.com wrote: Sean Dague s...@dague.net writes: The crux of the issue is that zookeeper python modules are C extensions. So you have to either install from packages (which we don't do in

Re: [openstack-dev] memory usage in devstack-gate (the oom-killer strikes again)

2014-09-09 Thread Mike Bayer
yes. guppy seems to have some nicer string formatting for this dump as well, but i was unable to figure out how to get this string format to write to a file, it seems like the tool is very geared towards interactive console use. We should pick a nice memory formatter we like, there’s a bunch

[openstack-dev] [oslo] deferring incomplete juno specs

2014-09-09 Thread Doug Hellmann
We haven’t talked about the process for deferring incomplete specs. I submitted a review [1] to simply remove them from juno, with the understanding that their author (or a new owner) can resubmit them for kilo. Please look it over and vote on the review. If we need to have a process

[openstack-dev] [FUEL] Re: SSL in Fuel.

2014-09-09 Thread Stanislaw Bogatkin
I think that if we have 3 blueprints that realises some SSL stuff around themselves then we can discuss it here. My vision about SSL in Fuel split into 3 parts: A) We need to implement [1] blueprint, cause it is only one way to generate certificates. How i see that: 1.0 We sync puppet-openssl

Re: [openstack-dev] [Designate][Horizon][Tempest][DevStack] Supporting code for incubated projects

2014-09-09 Thread Mac Innes, Kiall
-Original Message- From: Sean Dague [mailto:s...@dague.net] Sent: 09 September 2014 15:13 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Designate][Horizon][Tempest][DevStack] Supporting code for incubated projects On 09/09/2014 07:58 AM, Mac Innes, Kiall

Re: [openstack-dev] [Glance][Nova][All] requests 2.4.0 breaks glanceclient

2014-09-09 Thread Ian Cordasco
On 9/3/14, 3:59 PM, Ian Cordasco ian.corda...@rackspace.com wrote: On 9/3/14, 2:20 PM, Sean Dague s...@dague.net wrote: On 09/03/2014 03:12 PM, Gregory Haynes wrote: Excerpts from Kuvaja, Erno's message of 2014-09-03 12:30:08 +: Hi All, While investigating glanceclient gating issues we

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

2014-09-09 Thread Dmitry Borodaenko
+1 on adding flow based criteria for HCF and Branching Point. Tracking down how many bugs was reported in LP on a given day is a bit tricky, so I think in both cases it would be easier to rely on flow of commits (which after Soft Code Freeze becomes a direct indicator of how many bugs are fixed

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

2014-09-09 Thread Roman Vyalov
All OSCI action items for prepare HCF check list has been done On Tue, Sep 9, 2014 at 6:27 PM, Mike Scherbakov mscherba...@mirantis.com wrote: Thanks Alexandra. We land a few patches a day currently, so I think we can open stable branch. If we see no serious objections in next 12 hours,

Re: [openstack-dev] [neutron] [nova] non-deterministic gate failures due to unclosed eventlet Timeouts

2014-09-09 Thread Kevin L. Mitchell
On Mon, 2014-09-08 at 17:25 -0400, Jay Pipes wrote: Thanks, that might be what's causing this timeout/gate failure in the nova unit tests. [1] [1] https://bugs.launchpad.net/nova/+bug/1357578 Indeed, there are a couple places where eventlet.timeout.Timeout() seems to be used in the

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

2014-09-09 Thread Mike Scherbakov
What we need to achieve that is have 2 build series based on Fuel master: one with Icehouse packages, and one with Juno, and, as Mike proposed, keep our manifests backwards compatible with Icehouse. Exactly. Our Fuel CI can do 4 builds against puppet modules: 2 voting, with Icehouse packages; 2

Re: [openstack-dev] [Heat] Request for python-heatclient project to adopt heat-translator

2014-09-09 Thread Sahdev P Zala
Hi Angus, please see my reply in-line. Thanks! Regards, Sahdev From: Angus Salkeld asalk...@mirantis.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 09/09/2014 12:25 AM Subject:Re: [openstack-dev] [Heat] Request

Re: [openstack-dev] how to provide tests environments for python things that require C extensions

2014-09-09 Thread Doug Hellmann
On Sep 9, 2014, at 10:51 AM, Sean Dague s...@dague.net wrote: On 09/09/2014 10:41 AM, Doug Hellmann wrote: On Sep 8, 2014, at 8:18 PM, James E. Blair cor...@inaugust.com wrote: Sean Dague s...@dague.net writes: The crux of the issue is that zookeeper python modules are C extensions.

Re: [openstack-dev] [Heat] convergence flow diagrams

2014-09-09 Thread Tyagi, Ishant
Thanks Angus for your comments. Your design is almost same as this one. I also agree that only engine should have DB access will DB rpc api’s. I will update the diagrams with this change. Regarding the worker communicating with the observer, flow would be like this: · Engine tells

Re: [openstack-dev] [Heat] Request for python-heatclient project to adopt heat-translator

2014-09-09 Thread Sahdev P Zala
Hi Steve, sure. Please see my reply in-line. Thanks! Regards, Sahdev From: Steven Hardy sha...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 09/09/2014 05:55 AM Subject:Re: [openstack-dev] [Heat]

[openstack-dev] [TripleO] Propose adding StevenK to core reviewers

2014-09-09 Thread Gregory Haynes
Hello everyone! I have been working on a meta-review of StevenK's reviews and I would like to propose him as a new member of our core team. As I'm sure many have noticed, he has been above our stats requirements for several months now. More importantly, he has been reviewing a wide breadth of

Re: [openstack-dev] [Designate][Horizon][Tempest][DevStack] Supporting code for incubated projects

2014-09-09 Thread Sean Dague
On 09/09/2014 12:23 PM, Mac Innes, Kiall wrote: -Original Message- From: Sean Dague [mailto:s...@dague.net] Sent: 09 September 2014 15:13 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Designate][Horizon][Tempest][DevStack] Supporting code for incubated projects

Re: [openstack-dev] [neutron][policy] Group-based Policy next steps

2014-09-09 Thread Jay Pipes
On 09/04/2014 12:07 AM, Sumit Naiksatam wrote: Hi, There's been a lot of lively discussion on GBP a few weeks back and we wanted to drive forward the discussion on this a bit more. As you might imagine, we're excited to move this forward so more people can try it out. Here are the options: *

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

2014-09-09 Thread Monty Taylor
On 09/04/2014 01:30 AM, Clint Byrum wrote: Excerpts from Flavio Percoco's message of 2014-09-04 00:08:47 -0700: Greetings, Last Tuesday the TC held the first graduation review for Zaqar. During the meeting some concerns arose. I've listed those concerns below with some comments hoping that it

[openstack-dev] [solum] pep8 - splitting expressions

2014-09-09 Thread Gilbert Pilz
I have a question with regards to splitting expressions in order to conform to the pep8 line-length restriction. I have the following bit of code: res = amodel.Assemblies(uri=common.ASSEM_URI_STR % pecan.request.host_url,

[openstack-dev] [zaqar] Juno Performance Testing (Round 2)

2014-09-09 Thread Kurt Griffiths
Hi folks, In this second round of performance testing, I benchmarked the new Redis driver. I used the same setup and tests as in Round 1 to make it easier to compare the two drivers. I did not test Redis in master-slave mode, but that likely would not make a significant difference in the results

Re: [openstack-dev] [glance] HTTPS client breaks nova

2014-09-09 Thread Rob Crittenden
Flavio Percoco wrote: On 07/23/2014 06:05 PM, Rob Crittenden wrote: Rob Crittenden wrote: It looks like the switch to requests in python-glanceclient (https://review.openstack.org/#/c/78269/) has broken nova when SSL is enabled. I think it is related to the custom object that the

Re: [openstack-dev] [Infra] Meeting Tuesday September 9th at 19:00 UTC

2014-09-09 Thread Elizabeth K. Joseph
On Mon, Sep 8, 2014 at 10:34 AM, Elizabeth K. Joseph l...@princessleia.com wrote: The OpenStack Infrastructure (Infra) team is hosting our weekly meeting on Tuesday September 9th, at 19:00 UTC in #openstack-meeting Meeting minutes and log available here: Minutes:

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

2014-09-09 Thread Aleksandra Fedorova
Our Fuel CI can do 4 builds against puppet modules: 2 voting, with Icehouse packages; 2 non-voting, with Juno packages. Then, I'd suggest to create ISO with 2 releases (Icehouse, Juno) actually before Juno becomes stable. We will be able to run 2 sets of BVTs (against Icehouse and Juno), and it

[openstack-dev] global-reqs on tooz pulls in worrisome transitive dep

2014-09-09 Thread Matt Riedemann
It took me a while to untangle this so prepare for links. :) I noticed this change [1] today for global-requirements to require tooz [2] for a ceilometer blueprint [3]. The sad part is that tooz requires pymemcache [4] which is, from what I can tell, a memcached client that is not the same

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

2014-09-09 Thread Mike Scherbakov
Aleksandra, you've got us exactly right. Fuel CI for OSTF can wait a bit longer, but 4 fuel-library tests should happen right after we create stable/5.1. Also, for Fuel CI for OSTF - I don't think it's actually necessary to support 5.0 envs. Your questions: 1. Create jobs for both Icehouse

Re: [openstack-dev] [solum] pep8 - splitting expressions

2014-09-09 Thread Jay Pipes
On 09/09/2014 03:05 PM, Gilbert Pilz wrote: I have a question with regards to splitting expressions in order to conform to the pep8 line-length restriction. I have the following bit of code: res = amodel.Assemblies(uri=common.ASSEM_URI_STR %

Re: [openstack-dev] [Designate][Horizon][Tempest][DevStack] Supporting code for incubated projects

2014-09-09 Thread Lyle, David
Adding support for incubated projects in Horizon is blocked mainly for dependency issues. The way Horizon utilizes the python-*clients we force a requirement on distros to now include that version of the client even though it is not officially part of OpenStack's integrated release. Additionally,

Re: [openstack-dev] [All] Maintenance mode in OpenStack during patching/upgrades

2014-09-09 Thread Mike Scherbakov
Sergii, Clint, to rephrase what you are saying - there are might be situations when our OpenStack API will not be responding, as simply services would be down for upgrade. Do we want to support it somehow? For example, if we know that Nova is going to be down, can we respond with HTTP 503 with

[openstack-dev] [release] client release deadline - Sept 18th

2014-09-09 Thread Sean Dague
As we try to stabilize OpenStack Juno, many server projects need to get out final client releases that expose new features of their servers. While this seems like not a big deal, each of these clients releases ends up having possibly destabilizing impacts on the OpenStack whole (as the clients do

[openstack-dev] On an API proxy from baremetal to ironic

2014-09-09 Thread Michael Still
Hi. One of the last things blocking Ironic from graduating is deciding whether or not we need a Nova API proxy for the old baremetal extension to new fangled Ironic API. The TC has asked that we discuss whether we think this functionality is actually necessary. It should be noted that we're

Re: [openstack-dev] global-reqs on tooz pulls in worrisome transitive dep

2014-09-09 Thread Solly Ross
For the future == IMHO, we shouldn't be pulling in duplicate dependencies when we can control it. Since tooz is part of stackforge, it's somewhat part of OpenStack. We should strive to make all OpenStack projects use one memcached client. That being said, a quick Google search

Re: [openstack-dev] On an API proxy from baremetal to ironic

2014-09-09 Thread Solly Ross
With my admittedly limited knowledge of the whole Ironic process, the question seems to me to be: If we don't implement a proxy, which people are going to have a serious problem? Do we have an data on which users/operators are making use of the baremetal API in any extensive fashion? If

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

2014-09-09 Thread Dmitry Borodaenko
A clarification on 2: we are going to keep fuel_5.1_* jobs around for the benefict 5.1.x maintenance releases, that should take care of Icehouse testing for us, so I don't think we should keep Icehouse jobs in 6.0/master after Juno is stabilized. What we should do instead is drop Icehouse jobs and

Re: [openstack-dev] [Designate][Horizon][Tempest][DevStack] Supporting code for incubated projects

2014-09-09 Thread Gabriel Hurley
I would also like to add that incubated != integrated. There's no telling how long a project may stay in incubation or how many changes it may undergo before it's deemed ready (see David's reasoning around client changes during RC's). While the Horizon team has always made every effort to work

Re: [openstack-dev] On an API proxy from baremetal to ironic

2014-09-09 Thread Michael Still
On Wed, Sep 10, 2014 at 7:43 AM, Solly Ross sr...@redhat.com wrote: With my admittedly limited knowledge of the whole Ironic process, the question seems to me to be: If we don't implement a proxy, which people are going to have a serious problem? Do we have an data on which users/operators

Re: [openstack-dev] On an API proxy from baremetal to ironic

2014-09-09 Thread Ben Nemec
On 09/09/2014 04:24 PM, Michael Still wrote: Hi. One of the last things blocking Ironic from graduating is deciding whether or not we need a Nova API proxy for the old baremetal extension to new fangled Ironic API. The TC has asked that we discuss whether we think this functionality is

[openstack-dev] [Nova] Current state of play for nova FFEs

2014-09-09 Thread Michael Still
Hi. So feature freeze seems to be going quite well to me. We've already landed 10 things which had requested exceptions. However, there are still six things in flight, so I would like to remind people to keep focussing on those please. The deadline for these patches to be approved is Friday

Re: [openstack-dev] [neutron][policy] Group-based Policy next steps

2014-09-09 Thread Kevin Benton
Hi Jay, The main component that won't work without direct integration is enforcing policy on calls directly to Neutron and calls between the plugins inside of Neutron. However, that's only one component of GBP. All of the declarative abstractions, rendering of policy, etc can be experimented with

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

2014-09-09 Thread Samuel Merritt
On 9/9/14, 12:03 PM, Monty Taylor wrote: On 09/04/2014 01:30 AM, Clint Byrum wrote: Excerpts from Flavio Percoco's message of 2014-09-04 00:08:47 -0700: Greetings, Last Tuesday the TC held the first graduation review for Zaqar. During the meeting some concerns arose. I've listed those

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

2014-09-09 Thread Devananda van der Veen
On Tue, Sep 9, 2014 at 4:12 PM, Samuel Merritt s...@swiftstack.com wrote: On 9/9/14, 12:03 PM, Monty Taylor wrote: [snip] So which is it? Because it sounds like to me it's a thing that actually does NOT need to diverge in technology in any way, but that I've been told that it needs to diverge

Re: [openstack-dev] [neutron][policy] Group-based Policy next steps

2014-09-09 Thread Jay Pipes
On 09/09/2014 06:57 PM, Kevin Benton wrote: Hi Jay, The main component that won't work without direct integration is enforcing policy on calls directly to Neutron and calls between the plugins inside of Neutron. However, that's only one component of GBP. All of the declarative abstractions,

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

2014-09-09 Thread Clint Byrum
Excerpts from Samuel Merritt's message of 2014-09-09 16:12:09 -0700: On 9/9/14, 12:03 PM, Monty Taylor wrote: On 09/04/2014 01:30 AM, Clint Byrum wrote: Excerpts from Flavio Percoco's message of 2014-09-04 00:08:47 -0700: Greetings, Last Tuesday the TC held the first graduation review

Re: [openstack-dev] [tripleo] Puppet elements support

2014-09-09 Thread Emilien Macchi
So this is the patch to move the repo on Stackforge: https://review.openstack.org/#/c/120285 Of course, I copy/paste Gerrit permissions from tripleo-image-elements project, so people core in tripleo-image-elements will obviously be core on tripleo-puppet-elements. Emilien Macchi On 09/08/2014

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

2014-09-09 Thread Devananda van der Veen
On Thu, Sep 4, 2014 at 1:44 PM, Kurt Griffiths kurt.griffi...@rackspace.com wrote: [snip] Does a Qpid/Rabbit/Kafka provisioning service make sense? Probably. Would such a service totally overlap in terms of use-cases with Zaqar? Community feedback suggests otherwise. Will there be some other

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

2014-09-09 Thread Clint Byrum
Excerpts from Devananda van der Veen's message of 2014-09-09 16:47:27 -0700: On Tue, Sep 9, 2014 at 4:12 PM, Samuel Merritt s...@swiftstack.com wrote: On 9/9/14, 12:03 PM, Monty Taylor wrote: [snip] So which is it? Because it sounds like to me it's a thing that actually does NOT need to

Re: [openstack-dev] Kilo Cycle Goals Exercise

2014-09-09 Thread Joe Gordon
On Wed, Sep 3, 2014 at 8:37 AM, Joe Gordon joe.gord...@gmail.com wrote: As you all know, there has recently been several very active discussions around how to improve assorted aspects of our development process. One idea that was brought up is to come up with a list of cycle goals/project

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

2014-09-09 Thread Stefano Maffulli
On 09/09/2014 06:55 AM, James Bottomley wrote: CLAs are a well known and documented barrier to casual contributions I'm not convinced about this statement, at all. And since I think it's secondary to what we're discussing, I'll leave it as is and go on. I've done both ... I do prefer the patch

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

2014-09-09 Thread Adam Lawson
*should OpenStack include, in the integrated release, a messaging-as-a-service component* Assuming this is truly a question that represents where we are and not exploratory of what we might want to address, I would say the answer is a resounding no, as queuing is within the scope of what

Re: [openstack-dev] Kilo Cycle Goals Exercise

2014-09-09 Thread Adam Lawson
Deleting unnecessary code, introducing a stabilization cycle and/or making definite steps towards a unified SDK are definitely my votes. *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 101 International: +1

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

2014-09-09 Thread Boris Pavlovic
Devananda, While that is de rigueur today, it's actually at the core of the current problem space. Blessing a project by integrating it is not a scalable long-term solution. We don't have a model to integrate 1 project for the same space // of the same type, or to bless the stability of a

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

2014-09-09 Thread Devananda van der Veen
On Tue, Sep 9, 2014 at 5:31 PM, Boris Pavlovic bo...@pavlovic.me wrote: Devananda, While that is de rigueur today, it's actually at the core of the current problem space. Blessing a project by integrating it is not a scalable long-term solution. We don't have a model to integrate 1 project

Re: [openstack-dev] [Heat] convergence flow diagrams

2014-09-09 Thread Angus Salkeld
On Wed, Sep 10, 2014 at 4:12 AM, Tyagi, Ishant ishant.ty...@hp.com wrote: Thanks Angus for your comments. Your design is almost same as this one. I also agree that only engine should have DB access will DB rpc api’s. I will update the diagrams with this change. Regarding the worker

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

2014-09-09 Thread Samuel Merritt
On 9/9/14, 4:47 PM, Devananda van der Veen wrote: On Tue, Sep 9, 2014 at 4:12 PM, Samuel Merritt s...@swiftstack.com wrote: On 9/9/14, 12:03 PM, Monty Taylor wrote: [snip] So which is it? Because it sounds like to me it's a thing that actually does NOT need to diverge in technology in any

Re: [openstack-dev] [neutron][policy] Group-based Policy next steps

2014-09-09 Thread Baohua Yang
Agree. It's necessary for neutron to have GBP, and we can certainly utilize stackforge to help improve it. On Fri, Sep 5, 2014 at 11:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: I can only see the use of a separate project for Group Policy as a tactical and temporary solution. In my

Re: [openstack-dev] On an API proxy from baremetal to ironic

2014-09-09 Thread Russell Bryant
On 09/09/2014 05:24 PM, Michael Still wrote: Hi. One of the last things blocking Ironic from graduating is deciding whether or not we need a Nova API proxy for the old baremetal extension to new fangled Ironic API. The TC has asked that we discuss whether we think this functionality is

[openstack-dev] [all] i need some help on this bug Bug #1365892

2014-09-09 Thread Li Tianqing
Hello, I use backdoor of eventlet to enable gc.DEBUG_LEAK, and after wait a few minutes, i can sure that there will some objects that can not be collected by gc.collect in gc.garbage. Those looks like this (catched in ceilometer-collector) ['_context_auth_token', 'auth_token',