Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 9:32 AM, Steve Martinelli wrote: > > So I don't know the intricacies of the baremetal APIs, but hopefully I can > shed some light on best practices. > > Do try to reuse the existing actions >

[openstack-dev] [neutron][upgrade] new 'all things upgrade' subteam

Hi all, I want to announce that there is an informal group of folks who plan to work on upgrade story for Neutron during Mitaka: getting grenade partial aka sideways up; extending grenade resource migration checks; adopting oslo.versionedobjects for more resources; providing guidance to

Re: [openstack-dev] Learning to Debug the Gate

On 11/9/2015 3:54 PM, Anita Kuno wrote: On 11/05/2015 07:45 PM, Anita Kuno wrote: On 11/03/2015 05:30 PM, Anita Kuno wrote: On 11/02/2015 12:39 PM, Anita Kuno wrote: On 10/29/2015 10:42 PM, Anita Kuno wrote: On 10/29/2015 08:27 AM, Anita Kuno wrote: On 10/28/2015 12:14 AM, Matt Riedemann

[openstack-dev] [nova] live migration management approach

All I inherited the task of producing an upstream spec for querying and aborting ongoing migrations from a co-worker and submitted a new spec https://review.openstack.org/#/c/228828//. A related spec for pausing an instance being migrated to enable the migration to complete is also proposed

[openstack-dev] [Fuel][Fuel-QA][Fuel-TechDebt] Code Quality: Do Not Hardcode - Fix Things Instead

Folks I wanted to raise awareness about one of the things I captured while doing reviews recently - we are sacrificing quality to bugfixing and feature development velocity, essentially moving from one heap to another - from bugs/features to 'tech-debt' bugs. I understand that we all have

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 9:32 AM, Brad P. Crochet wrote: > In this case, the noun is actually 'baremetal provision state'. The > 'action' is the states themselves. It doesn't fit exactly, but seems > to at least be somewhat natural. resource == provision state (add baremetal if

Re: [openstack-dev] [Neutron] Reminder: Team meeting on Monday at 2100 UTC

Dear Vikram, Our deepest condolences for you and your family. Do not even think about work these days. Edgar From: Vikram Choudhary > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [Fuel] Master node upgrade

Evgeniy I am not sure you addressed me, but, anyway, - yes, we will have a situation with old containers on new host node. This will be identical to old host node from database migration point of view. On Tue, Nov 10, 2015 at 7:38 PM, Evgeniy L wrote: > Hi Vladimir, > > Just

[openstack-dev] [Ironic] Do we need to have a mid-cycle?

Hi, In the last Ironic meeting [1] we started a discussion about whether we need to have a mid-cycle meeting for the Mitaka cycle or not. Some ideas about the format of the midcycle were presented in that conversation and this email is just a follow up on that conversation. The ideas presented

Re: [openstack-dev] [OpenStack-Infra] Configure gerrit to have two reviewers giving +2

On 2015-11-10 07:02:49 + (+), GROSZ, Maty (Maty) wrote: > How do I configure gerrit to have two reviewers giving +2 for a change? By telling everyone who has approval control on your project to only approve changes with more than one +2 vote (or phrased differently: we don't have

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On Mon, Nov 9, 2015 at 7:44 AM, Dmitry Tantsur wrote: > Hi OOO'ers, hopefully the subject caught your attentions :) > > Currently, tripleoclient exposes several commands in "openstack baremetal" > and "openstack baremetal introspection" namespaces belonging to ironic and >

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On 11/10/2015 03:32 PM, Steve Martinelli wrote: So I don't know the intricacies of the baremetal APIs, but hopefully I can shed some light on best practices. Do try to reuse the existing actions (http://docs.openstack.org/developer/python-openstackclient/commands.html#actions) Do use "create",

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 05:26 AM, John Trowbridge wrote: > > > On 11/09/2015 07:44 AM, Dmitry Tantsur wrote: >> Hi OOO'ers, hopefully the subject caught your attentions :) >> >> Currently, tripleoclient exposes several commands in "openstack >> baremetal" and "openstack baremetal introspection" namespaces

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 9:46 AM, Dmitry Tantsur wrote: > inspect, manage, provide, active and abort are all provisioning verbs > used in ironic API. they usually represent some complex operations on a > node. Inspection is not related to showing, it's about fetching

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 10:14 AM, Brad P. Crochet wrote: > There was some discussion on one of the patches about changing to > 'baremetal node'. I was a little concerned by that since the original > 'baremetal' commands have landed, but I think since they landed > post-Liberty,

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 4:09 AM, Dmitry Tantsur wrote: > Hi all! > > I'd like to seek consensus (or at least some opinions) on patch > https://review.openstack.org/#/c/206119/ > It proposed the following command: > I think it's time to actually just write up a spec on this.

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On 11/10/2015 05:14 PM, Dean Troyer wrote: On Tue, Nov 10, 2015 at 9:46 AM, Dmitry Tantsur > wrote: inspect, manage, provide, active and abort are all provisioning verbs used in ironic API. they usually represent some complex

Re: [openstack-dev] [Fuel] Master node upgrade

Hi Vladimir, Just to make sure that we are on the same page. We'll have to use upgrade script anyway, since you will need to run database migration and register new releases. Thanks, On Monday, 9 November 2015, Vladimir Kozhukalov wrote: > Looks like most people

Re: [openstack-dev] [Fuel][Fuel-QA][Fuel-TechDebt] Code Quality: Do Not Hardcode - Fix Things Instead

I think that it is excellent thought. +1 On Tue, Nov 10, 2015 at 6:52 PM, Vladimir Kuklin wrote: > Folks > > I wanted to raise awareness about one of the things I captured while doing > reviews recently - we are sacrificing quality to bugfixing and feature > development

Re: [openstack-dev] [oslo] Graduate cliutils.py into oslo.utils

Excerpts from Davanum Srinivas (dims)'s message of 2015-11-10 08:01:50 -0500: > Julien, > > That's exactly what i want as well. We should just let whoever has > copies to do whatever they want with them and drop our oversight of > it. Since they are mature and haven't been touched for a while, i

[openstack-dev] [Group-based-policy]

Dear sirs, I'm a student trying to testing Group Based Policy functionalities. I have some questions about it, because from the documentation is not clear to me what role assume opendaylight in the plug-in. I can use gbp only with openstack or is mandatory to use it with opendaylight? And next, if

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On Tue, Nov 10, 2015 at 9:03 AM, Brad P. Crochet wrote: > Actually, the 'baremetal' namespace is exactly what it should be, > based on other OSC clients. For instance, Neutron uses 'network', Nova > uses 'server', etc. The idea is that the client should use the service > type,

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 11:14 AM, Dean Troyer wrote: > On Tue, Nov 10, 2015 at 9:46 AM, Dmitry Tantsur wrote: >> >> inspect, manage, provide, active and abort are all provisioning verbs >> used in ironic API. they usually represent some complex operations

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 11/10/2015 5:41 AM, Alan Pevec wrote: The Stable Branch Policy, lets not put it in any repo. Doing that would give indication that we expect changes into it and I'd prefer that policy mostly staying stable as well. What indication did it give when it was in wiki? :) It actually already

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 10:43 AM, Ben Nemec wrote: > On 11/10/2015 05:26 AM, John Trowbridge wrote: >> >> >> On 11/09/2015 07:44 AM, Dmitry Tantsur wrote: >>> Hi OOO'ers, hopefully the subject caught your attentions :) >>> >>> Currently, tripleoclient exposes several commands in "openstack >>> baremetal"

Re: [openstack-dev] [Fuel] shotgun code freeze

+1 to Dmitry, thanks for pushing this activity Vladimir. On Friday, 6 November 2015, Dmitry Pyzhov wrote: > Great job! We are much closer to removal of fuel-web repo. > > On Tue, Oct 27, 2015 at 7:35 PM, Vladimir Kozhukalov < > vkozhuka...@mirantis.com >

Re: [openstack-dev] [fuel] Using upstream packages & modules

Hey Vladimir, On Tue, Nov 10, 2015 at 5:56 AM, Vladimir Kuklin wrote: > Alex > > That's great to hear that. But be aware - making all of the components work > exactly the way they work within MOS is actually identical to upstreaming > MOS. We are using some components of

Re: [openstack-dev] How to change the email address for openstack Id ?

On 2015-11-10 16:23:29 +0800 (+0800), lichen.hangzhou wrote: > Anyone know how to change the email address for openstack id ? > > I have already changed the "Preferred Email" at > https://review.openstack.org/#/settings/contact, and it should > worked, the new email already showed on >

Re: [openstack-dev] [keystone] [Mistral] Autoprovisioning, per-user projects, and Federation

> On 09 Nov 2015, at 20:43, Adam Young wrote: > > On 11/06/2015 06:28 PM, Tim Hinrichs wrote: >> Congress allows users to write a policy that executes an action under >> certain conditions. >> >> The conditions can be based on any data Congress has access to, which >>

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/10/2015 04:37 PM, Giulio Fidente wrote: On 11/10/2015 04:16 PM, Dmitry Tantsur wrote: On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote: Hi all, At the last IRC meeting it was agreed that the new TripleO REST API should forgo the Tuskar name, and simply be called... the TripleO API. There's

Re: [openstack-dev] [TripleO] Proposing Ian Wienand as core reviewer on diskimage-builder

On Tue, Nov 03, 2015 at 03:25:27PM +, Gregory Haynes wrote: > Hello everyone, > > I would like to propose adding Ian Wienand as a core reviewer on the > diskimage-builder project. Ian has been making a significant number of > contributions for some time to the project, and has been a great

Re: [openstack-dev] [oslo] Graduate apiclient library

On Tue, Nov 10, 2015 at 9:57 AM, Adam Young wrote: > +2. keystoneauth is designed to be the library explicitly for this. Do > not duplicate auth behavior anywhere else in the supported client libraries. > To expand on this point a bit, if you are considering re-working the

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/10/2015 10:08 AM, Tzu-Mainn Chen wrote: > Hi all, > > At the last IRC meeting it was agreed that the new TripleO REST API > should forgo the Tuskar name, and simply be called... the TripleO > API. There's one more point of discussion: where should the API > live? There are two

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 6:19 AM, Sam Betts (sambetts) wrote: > So you would end up with a set of commands that look like this: > > Openstack baremetal [node/driver/chassis] list > Openstack baremetal port list [—node uuid] <— replicate node-port-list > > Openstack baremetal

Re: [openstack-dev] [keystone] [Mistral] Autoprovisioning, per-user projects, and Federation

> On 09 Nov 2015, at 21:57, Tim Hinrichs wrote: > > Congress happens to have the capability to run a script/API call under > arbitrary conditions on the state of other OpenStack projects, which sounded > like what you wanted. Or did I misread your original question? > >

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On Tue, Nov 10, 2015 at 7:42 AM, Lennart Regebro wrote: > I'm not so sure about the idea that we can't "hijack" other projects > namespaces. If only ironic is allowed to use the prefix "baremetal", > then the prefix should not have been "baremetal" in the first place, > it

Re: [openstack-dev] [oslo] Graduate cliutils.py into oslo.utils

+1000 Doug. On Tue, Nov 10, 2015 at 9:49 AM, Doug Hellmann wrote: > Excerpts from Julien Danjou's message of 2015-11-10 14:18:43 +0100: >> On Tue, Nov 10 2015, Davanum Srinivas wrote: >> >> > Julien, >> > >> > That's exactly what i want as well. We should just let whoever

Re: [openstack-dev] [heat][keystone] How to handle request for global admin in policy.json?

On 11/10/2015 05:08 AM, Henry Nash wrote: Steve, Currently, your best option is to use something similar to the policy.v3cloudsample.json, where you basically “bless” a project (or domain) as being the “cloud admin project/domain”. Having a role on that gives you super-powers. The only

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/10/2015 04:47 PM, Dmitry Tantsur wrote: On 11/10/2015 04:37 PM, Giulio Fidente wrote: On 11/10/2015 04:16 PM, Dmitry Tantsur wrote: On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote: Hi all, At the last IRC meeting it was agreed that the new TripleO REST API should forgo the Tuskar name,

Re: [openstack-dev] [Group-based-policy]

Hi Ernesto, Let me answer the first question for you. You can use GBP without OpenDaylight. OpenDaylight has a separate Group-based Policy project, which might make you wonder if you need it to run OpenStack GBP. Don’t worry, you can deploy OpenStack GBP right away without OpenDaylight. Best

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

On 11/10/2015 05:12 AM, Thierry Carrez wrote: > Kevin Carter wrote: >>> I believe Clint already linked to >>> https://aphyr.com/posts/309-knossos-redis-and-linearizability or >>> similar - but 'known for general ease of use and reliability' is uhm, >>> a bold claim. Its worth comparing that (and

Re: [openstack-dev] [oslo] Graduate cliutils.py into oslo.utils

Excerpts from Julien Danjou's message of 2015-11-10 14:18:43 +0100: > On Tue, Nov 10 2015, Davanum Srinivas wrote: > > > Julien, > > > > That's exactly what i want as well. We should just let whoever has > > copies to do whatever they want with them and drop our oversight of > > it. Since they

Re: [openstack-dev] [oslo] XxxOpt classes "kept for backward-compatibility" in oslo.config

Le 10/11/2015 15:33, Davanum Srinivas a écrit : +1 Victor. Ok thanks for the confirmation. The comment disturbed me a lot :-D Here is a simple change to remove the comment: https://review.openstack.org/243630 Victor __

[openstack-dev] [tripleo] Location of TripleO REST API

Hi all, At the last IRC meeting it was agreed that the new TripleO REST API should forgo the Tuskar name, and simply be called... the TripleO API. There's one more point of discussion: where should the API live? There are two possibilities: a) Put it in tripleo-common, where the business logic

Re: [openstack-dev] [keystone] [Mistral] Autoprovisioning, per-user projects, and Federation

Renat Akhmerov @ Mirantis Inc. > On 06 Nov 2015, at 00:09, Clint Byrum wrote: > > Excerpts from Doug Hellmann's message of 2015-11-05 09:51:41 -0800: >> Excerpts from Adam Young's message of 2015-11-05 12:34:12 -0500: >>> Can people help me work through the right set of

Re: [openstack-dev] [Zaqar] OpenStack Tokyo Summit Summary

On 11/06/2015 01:36 PM, Doug Hellmann wrote: Excerpts from Fei Long Wang's message of 2015-11-07 01:31:09 +1300: Greetings, Firstly, thank you for everyone joined Zaqar sessions at Tokyo summit. We definitely made some great progress for those working sessions. Here are the high level summary

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 4:09 AM, Dmitry Tantsur wrote: > Hi all! > > I'd like to seek consensus (or at least some opinions) on patch > https://review.openstack.org/#/c/206119/ > It proposed the following command: > > openstack baremetal provision state --provide UUID > >

Re: [openstack-dev] [keystone] [Mistral] Autoprovisioning, per-user projects, and Federation

> On 06 Nov 2015, at 03:41, Doug Hellmann wrote: > > Excerpts from Adam Young's message of 2015-11-05 15:14:03 -0500: >> On 11/05/2015 01:09 PM, Clint Byrum wrote: >>> Excerpts from Doug Hellmann's message of 2015-11-05 09:51:41 -0800: Excerpts from Adam Young's

Re: [openstack-dev] [oslo] Graduate apiclient library

On 11/10/2015 06:45 AM, Victor Stinner wrote: Hi, Le 10/11/2015 07:29, Kekane, Abhishek a écrit : We have done extensive analysis to figure out the differences of usages of different oslo-incubator/openstack/common/apiclient modules used in the respective Openstack python client libraries and

Re: [openstack-dev] [Zaqar] OpenStack Tokyo Summit Summary

for reference, Julien is currently signed up for that task[1]. if this is a high priority requirement, we might want to see if another resource can pick it up, we can help out to explain how it should all be done :) cheers, [1] https://etherpad.openstack.org/p/mitaka-telemetry-todos On

Re: [openstack-dev] Learning to Debug the Gate

There is also a neutron issue which is causing a 35% failure rate in neutron jobs - http://tinyurl.com/ne3ex4v That one still needs resolution. On 11/10/2015 10:54 AM, Davanum Srinivas wrote: > Took about 35 mins or so :) > > -- Dims > > On Tue, Nov 10, 2015 at 10:45 AM, Matt Riedemann >

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

On 11/10/2015 10:28 AM, Renat Akhmerov wrote: On 09 Nov 2015, at 20:43, Adam Young wrote: On 11/06/2015 06:28 PM, Tim Hinrichs wrote: Congress allows users to write a policy that executes an action under certain conditions. The conditions can be based on any data

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

On 11/10/2015 05:21 PM, Brad P. Crochet wrote: On Tue, Nov 10, 2015 at 4:09 AM, Dmitry Tantsur wrote: Hi all! I'd like to seek consensus (or at least some opinions) on patch https://review.openstack.org/#/c/206119/ It proposed the following command: I think it's time

Re: [openstack-dev] [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On 11/9/2015 10:15 PM, Matthew Treinish wrote: On Mon, Nov 09, 2015 at 05:05:36PM +1100, Tony Breeds wrote: On Fri, Nov 06, 2015 at 10:12:21AM -0800, Clint Byrum wrote: The argument in the original post, I think, is that we should not stand in the way of the vendors continuing to

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 05:18 PM, Ben Nemec wrote: +1 to moving anything we can into Ironic itself. I do want to note that if we rename anything, we can't just rip and replace. We have users of the current commands, and we need to deprecate those to give people a chance to move to the new ones.

[openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

Hi, while we continue discussion about the future of stable branches in general and stable/juno in particular, I'd like to execute the current plan which was[1] 2014.2.4 (eol) early November, 2015. release manager: apevec Iff there's enough folks interested (I'm not) in keep Juno alive longer,

Re: [openstack-dev] [keystone] [Mistral] Autoprovisioning, per-user projects, and Federation

> On 10 Nov 2015, at 21:29, Renat Akhmerov wrote: > > >> On 09 Nov 2015, at 21:57, Tim Hinrichs wrote: >> >> Congress happens to have the capability to run a script/API call under >> arbitrary conditions on the state of other OpenStack projects, which

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On Tue, Nov 10, 2015 at 8:42 AM, Lennart Regebro wrote: > These changes are fine to me. > > I'm not so sure about the idea that we can't "hijack" other projects > namespaces. If only ironic is allowed to use the prefix "baremetal", > then the prefix should not have been

Re: [openstack-dev] [TripleO] Proposing Ian Wienand as core reviewer on diskimage-builder

On Tue, 2015-11-03 at 15:25 +, Gregory Haynes wrote: > Hello everyone, > > I would like to propose adding Ian Wienand as a core reviewer on the > diskimage-builder project. Ian has been making a significant number > of > contributions for some time to the project, and has been a great help >

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote: Hi all, At the last IRC meeting it was agreed that the new TripleO REST API should forgo the Tuskar name, and simply be called... the TripleO API. There's one more point of discussion: where should the API live? There are two possibilities: a)

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

+1 to moving anything we can into Ironic itself. I do want to note that if we rename anything, we can't just rip and replace. We have users of the current commands, and we need to deprecate those to give people a chance to move to the new ones. A few more thoughts inline. On 11/09/2015 06:44

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/10/2015 04:16 PM, Dmitry Tantsur wrote: On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote: Hi all, At the last IRC meeting it was agreed that the new TripleO REST API should forgo the Tuskar name, and simply be called... the TripleO API. There's one more point of discussion: where should the

[openstack-dev] [Infra] grafana.openstack.org now online

Greetings, If you are not aware, we now have a Grafana service running[1] under OpenStack Infra. What is Grafana? "The leading graph and dashboard builder for visualizing time series metrics"[2]. The cool thing about our Grafana service, like Jenkins, all of our dashboards are managed via our

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/10/2015 10:37 AM, Giulio Fidente wrote: > On 11/10/2015 04:16 PM, Dmitry Tantsur wrote: >> On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote: >>> Hi all, >>> >>> At the last IRC meeting it was agreed that the new TripleO REST API >>> should forgo the Tuskar name, and simply be called... the

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 10:53 AM, Dean Troyer wrote: > On Tue, Nov 10, 2015 at 9:32 AM, Brad P. Crochet wrote: >> >> In this case, the noun is actually 'baremetal provision state'. The >> 'action' is the states themselves. It doesn't fit exactly, but seems >>

Re: [openstack-dev] [tacker] Proposing Sripriya Seetharam to Tacker core

+1 On Mon, Nov 9, 2015 at 6:22 PM, Sridhar Ramaswamy wrote: > I'd like to propose Sripriya Seetharam to join the Tacker core team. > Sripriya > ramped up quickly in early Liberty cycle and had become an expert in the > Tacker > code base. Her major contributions include

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Thierry Carrez wrote: Hi everyone, A few cycles ago we set up the Release Cycle Management team which was a bit of a frankenteam of the things I happened to be leading: release management, stable branch maintenance and vulnerability management. While you could argue

[openstack-dev] [neutron] [gate] 35% failure rate for neutron tempest jobs

The neutron tempest jobs are now at a 35% failure rate: http://tinyurl.com/ne3ex4v (note, 35% is basically the worst possible fail rate, because it's just passing enough to land patches that cause that kind of fail on two test runs check/gate with a coin flip). The failure is currently seen here

[openstack-dev] [searchlight] Searching admin-only fields

An issue discovered at the end of the Liberty cycle [1] meant that while still present in results (for admins) we had to disable searching of admin-only fields (TL;DR – a non-admin can fish for results to discover values for admin-only fields by searching e.g. "hostId": "a*"). We'd like to fix

Re: [openstack-dev] Can we get some sanity in the Neutron logs please?

On 11/10/2015 12:51 PM, Armando M. wrote: On 10 November 2015 at 10:33, Matt Riedemann > wrote: Let me qualify by saying I'm not a Neutron person. We know that gate-tempest-dsvm-neutron-full is failing hard as of

Re: [openstack-dev] [neutron] [gate] 35% failure rate for neutron tempest jobs

On 11/10/2015 01:37 PM, Armando M. wrote: > > > On 10 November 2015 at 09:49, Sean Dague > wrote: > > The neutron tempest jobs are now at a 35% failure rate: > http://tinyurl.com/ne3ex4v (note, 35% is basically the worst possible > fail rate,

Re: [openstack-dev] [fuel] Using upstream packages & modules

Alex Thanks for your very detailed answer - it clarified things a bit. So, if you would allow me to rephrase it - you are actually conducting a research on what is the actual gap between our downstream/fork and upstream UCA/puppet-openstack. This seems to be a very promising initiative. Are you

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Bartolomiej, Adam, Stanislaw is correct. And this is going to be ported to master. The goal currently is to reach an agreement on the implementation so that there's going to be a some kinf of compatibility during upgrades. Stanislaw, Do I understand correctly that you propose using something like

[openstack-dev] [all] devstack-gate jobs that will break at Mitaka-1

Here is the weekly list of jobs that will no longer work at Mitaka-1 when we remove extras.d support in devstack (and the number of runs in the last 48 hours): gate-congress-dsvm-api 652 gate-murano-congress-devstack-dsvm 284 gate-cue-integration-dsvm-rabbitmq 176

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 11:18 AM, Dmitry Tantsur wrote: > On 11/10/2015 06:08 PM, Ben Nemec wrote: >> On 11/10/2015 10:28 AM, John Trowbridge wrote: >>> >>> >>> On 11/10/2015 10:43 AM, Ben Nemec wrote: On 11/10/2015 05:26 AM, John Trowbridge wrote: > > > On 11/09/2015 07:44 AM, Dmitry

Re: [openstack-dev] [OpenStack-Infra] Report from Gerrit User Summit

On Tue, Nov 10, 2015 at 4:53 AM Sean Dague wrote: <...> Is there any update on label:Code-Review<=-1,group:nova-core ? The group > search support is documented, but as far as I can tell doesn't work > except under very specific ldap configs. >

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 10:28 AM, John Trowbridge wrote: > > > On 11/10/2015 10:43 AM, Ben Nemec wrote: >> On 11/10/2015 05:26 AM, John Trowbridge wrote: >>> >>> >>> On 11/09/2015 07:44 AM, Dmitry Tantsur wrote: Hi OOO'ers, hopefully the subject caught your attentions :) Currently,

Re: [openstack-dev] [release][stackalytics] possibly breaking bug closing statistics?

Doug, You are right, there should not be any changes in the stats. Bugs are mapped to release only by date, target milestone is not taken into account. For resolved bugs metric Stackalytics uses 'date_fix_commited' field, for filed bugs metric - 'date_created'. Thanks, Ilya 2015-11-10 0:53

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 06:08 PM, Ben Nemec wrote: On 11/10/2015 10:28 AM, John Trowbridge wrote: On 11/10/2015 10:43 AM, Ben Nemec wrote: On 11/10/2015 05:26 AM, John Trowbridge wrote: On 11/09/2015 07:44 AM, Dmitry Tantsur wrote: Hi OOO'ers, hopefully the subject caught your attentions :)

[openstack-dev] [HA] weekly High Availability meetings on IRC start next Monday

Hi all, After some discussion in Tokyo by stakeholders in OpenStack High Availability, I'm pleased to announce that from next Monday we're starting a series of weekly meetings on IRC. Details are here: https://wiki.openstack.org/wiki/Meetings/HATeamMeeting

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 09/11/15 07:44, Dmitry Tantsur wrote: As we already have "openstack undercloud" and "openstack overcloud" prefixes for TripleO, I suggest we move these commands under "openstack overcloud nodes" namespace. So we end up with: overcloud nodes import overcloud nodes configure ready state

[openstack-dev] [oslo.messaging] State wrapping in the MessageHandlingServer

My patch to MessageHandlingServer is currently being reverted because it broke Nova tests: https://review.openstack.org/#/c/235347/ Specifically it causes a number of tests to take a very long time to execute, which ultimately results in the total build time limit being exceeded. This is very

Re: [openstack-dev] [neutron] [gate] 35% failure rate for neutron tempest jobs

On 10 November 2015 at 09:49, Sean Dague wrote: > The neutron tempest jobs are now at a 35% failure rate: > http://tinyurl.com/ne3ex4v (note, 35% is basically the worst possible > fail rate, because it's just passing enough to land patches that cause > that kind of fail on two

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

On 11/10/2015 05:45 PM, Lucas Alvares Gomes wrote: Hi, In the last Ironic meeting [1] we started a discussion about whether we need to have a mid-cycle meeting for the Mitaka cycle or not. Some ideas about the format of the midcycle were presented in that conversation and this email is just a

Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other projects' OSC namespaces

On 11/10/2015 10:40 AM, Dmitry Tantsur wrote: > On 11/10/2015 05:18 PM, Ben Nemec wrote: >> +1 to moving anything we can into Ironic itself. >> >> I do want to note that if we rename anything, we can't just rip and >> replace. We have users of the current commands, and we need to >> deprecate

[openstack-dev] Cross-Project Meeting SKIPPED, Tue Nov 10th, 21:00 UTC

Hi all! As discussed in the previous cross-project meeting [1], we will be skipping meetings if there is no agenda items to discuss. There are no items to discuss this time around, but someone can still call for a meeting by adding an agenda item for November 17th [2]. To keep up with the

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On Tue, Nov 10, 2015 at 10:13:09AM +0100, Thierry Carrez wrote: > Matthew Treinish wrote: > > [...] > > The discussion here is about the cross project effort around stable > > branches, > > which by design is a more limited scope now. Right now the cross project > > effort > > around stable

Re: [openstack-dev] Can we get some sanity in the Neutron logs please?

On 11/10/2015 1:10 PM, Matt Riedemann wrote: On 11/10/2015 12:51 PM, Armando M. wrote: On 10 November 2015 at 10:33, Matt Riedemann > wrote: Let me qualify by saying I'm not a Neutron person. We know that

Re: [openstack-dev] [OpenStack-Infra] Report from Gerrit User Summit

Thanks for the report Jim. I got excited about polygerrit and deployed it sortof... pointing at review-dev.o.o in case anyone wants to kick the tires. http://polygerrit.nibalizer.com/q/status:open After the gerrit upgrade next week we can point it at review.o.o. I think it would be good for

[openstack-dev] Can we get some sanity in the Neutron logs please?

Let me qualify by saying I'm not a Neutron person. We know that gate-tempest-dsvm-neutron-full is failing hard as of the last 24 hours [1]. An error that's been showing up in tempest runs with neutron a lot is: "AssertionError: 0 == 0 : No IPv4 addresses found in: []" So checking logstash

Re: [openstack-dev] [oslo.messaging] State wrapping in the MessageHandlingServer

Matthew Booth wrote: My patch to MessageHandlingServer is currently being reverted because it broke Nova tests: https://review.openstack.org/#/c/235347/ Specifically it causes a number of tests to take a very long time to execute, which ultimately results in the total build time limit being

Re: [openstack-dev] [tacker] Proposing Sripriya Seetharam to Tacker core

+1 From: Sridhar Ramaswamy [mailto:sric...@gmail.com] Sent: Monday, November 09, 2015 6:22 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [tacker] Proposing Sripriya Seetharam to Tacker core I'd like to propose Sripriya Seetharam to join the Tacker

Re: [openstack-dev] [nova] Proposal to add Alex Xu to nova-core

On Nov 6, 2015, at 7:32, John Garbutt wrote: > Hi, > > I propose we add Alex Xu[1] to nova-core. > > Over the last few cycles he has consistently been doing great work, > including some quality reviews, particularly around the API. > > Please respond with comments, +1s,

Re: [openstack-dev] [nova] Proposal to add Sylvain Bauza to nova-core

On Nov 6, 2015, at 7:32, John Garbutt wrote: > Hi, > > I propose we add Sylvain Bauza[1] to nova-core. > > Over the last few cycles he has consistently been doing great work, > including some quality reviews, particularly around the Scheduler. > > Please respond with

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

Sean Dague wrote: On 11/10/2015 05:12 AM, Thierry Carrez wrote: Kevin Carter wrote: I believe Clint already linked to https://aphyr.com/posts/309-knossos-redis-and-linearizability or similar - but 'known for general ease of use and reliability' is uhm, a bold claim. Its worth comparing that

Re: [openstack-dev] Can we get some sanity in the Neutron logs please?

On 10 November 2015 at 10:33, Matt Riedemann wrote: > Let me qualify by saying I'm not a Neutron person. > > We know that gate-tempest-dsvm-neutron-full is failing hard as of the last > 24 hours [1]. > > An error that's been showing up in tempest runs with neutron a

Re: [openstack-dev] Regarding Designate Issues

On 10/11/15 11:02, Sharma Swati6 wrote: > Hi All, > > I am trying to install Designate using Devstack-Kilo but facing the > following issues while starting its services- > > 1. WARNING keystone.common.wsgi [-] Could not find service: dns > 2. WARNING keystone.common.wsgi [-] Could not find

Re: [openstack-dev] [Group-based-policy]

On Tue, Nov 10, 2015 at 8:41 AM, Duarte Cardoso, Igor < igor.duarte.card...@intel.com> wrote: > Hi Ernesto, > > > > Let me answer the first question for you. > > > > You can use GBP without OpenDaylight. > > > > OpenDaylight has a separate Group-based Policy project, which might make > you wonder

[openstack-dev] [Manila] Design summit notes

I wasn't going to write a wrap-up email this time around since so many people were able to attend in person, but enough people missed it that I changed my mind and decided to write down my own impressions of the sessions. Wednesday working session: Migration Improvements

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Stanislaw, I've been experimenting with 'capsh' on the 6.1 master node and it doesn't seem to preserve any capabilities when setting SECURE_NOROOT bit, even if explicitely told to do so (via either --keep=1 or "SECURE_KEEP_CAPS" bit). On Tue, Nov 10, 2015 at 11:20 AM, Dmitry Nikishov

  1   2   3   >