Re: [openstack-dev] [ci][infra][tripleo] Multi-staged check pipelines for Zuul v3 proposal

The proposed undercloud installation jobs dependency [0] worked, see the jobs start time [1], [2] confirms that. The resulting delay for the full pipeline is an ~80 minutes, as it was expected. So PTAL folks, I propose to try it out in real gating and see how the tripleo zuul queue gets

Re: [openstack-dev] [tripleo] Status of Standalone installer (aka All-In-One)

On 05/06/2018 02:26, Emilien Macchi wrote: [...] > I hope this update was useful, feel free to give feedback or ask any > questions, [...] I'm no prophet here, but I see a bright future for this approach. I can imagine how useful this can be on the testing and much more the learning side. Thanks

[openstack-dev] [openstack-ansible][releases][governance] Change in OSA roles tagging

Hello, *TL:DR;* If you are an openstack-ansible user, consuming our roles directly, with tags, without using openstack-ansible plays or integrated repo, then things will change for you. Start using git shas instead of tags. All other openstack-ansible users should not see a difference, even if

[openstack-dev] [watcher] Nominating suzhengwei as Watcher core

Hi Watchers, I’d like to nominate suzhengwei for Watcher Core team. suzhengwei makes great contribution to the Watcher project including code reviews and implementations. Please vote +1/-1. Best Regards, Alex __

Re: [openstack-dev] [tripleo][puppet] Hello all, puppet modules

We are using them for one of our deployments and are working on moving our other one to use the same modules :) Best regards On 06/04/2018 11:06 PM, Arnaud Morin wrote: > Hey, > > OVH is also using them as well as some custom ansible playbooks to manage the > deployment. But as for red had,

Re: [openstack-dev] [neutron][stable] Stepping down from core

Hi Ihar, Thanks for everything what You did for OpenStack and Neutron especially. I remember that You were one of first people which I met in OpenStack community. Thanks for all Your help then and during all time when we worked together :) Good luck in Your new project :) > Wiadomość napisana

Re: [openstack-dev] [tc] Organizational diversity tag

Sorry if I missed/repeat something already said in this thread... When I am looking at diversity, I generally like to know: 1) what's going on "right now", and 2) what happened in the cycle x. I think these 2 are different problems to solve. And tags are, IMO, best applied to the second case.

Re: [openstack-dev] [tc] summary of joint leadership meeting from 20 May

On Tue, Jun 05, 2018 at 11:21:16AM +0200, Thierry Carrez wrote: > Jay Pipes wrote: > > On 06/04/2018 05:02 PM, Doug Hellmann wrote: > >> [...]> > > Personally, I've very much enjoyed the separate PTGs because I've actually > > been able to get work done at them; something that was much harder when

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

On Mon, 2018-06-04 at 10:49 -0700, Nadathur, Sundar wrote: > Hi, > > Cyborg needs to create RCs and traits for accelerators. The > original plan was to do that with nested RPs. To avoid rushing > the > Nova developers, I had proposed that Cyborg could start by > applying >

Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

Hi, Sorry for re-using the ancient ML thread. Looking at recent xstatic-* repo reviews, I am a bit afraid that xstatic-cores do not have a common understanding on the principle of xstatic packages. I hope all xstatic-cores re-read "Packing Software" in the horizon contributor docs [1], especially

Re: [openstack-dev] [TC] Stein Goal Selection

On Mon, Jun 04, 2018 at 06:44:15PM -0500, Matt Riedemann wrote: > On 6/4/2018 5:13 PM, Sean McGinnis wrote: > > Yes, exactly what I meant by the NOOP. I'm not sure what Cinder would > > check here. We don't have to see if placement has been set up or if cell0 > > has been configured. Maybe once we

Re: [openstack-dev] [tc] summary of joint leadership meeting from 20 May

Jay Pipes wrote: > On 06/04/2018 05:02 PM, Doug Hellmann wrote: >> [...]> > Personally, I've very much enjoyed the separate PTGs because I've actually > been able to get work done at them; something that was much harder when the > design summits were part of the overall conference. Right, the

Re: [openstack-dev] [heat][neutron] Extraroute support

Thanks for the answer. On 2018-06-01 18:04, Kevin Benton wrote: The neutron API now supports compare and swap updates with an If-Match header so the race condition can be avoided. https://bugs.launchpad.net/neutron/+bug/1703234 On Fri, Jun 1, 2018, 04:57 Rabi Mishra

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

To summarize: cyborg could model things nested-wise, but there would be no way to schedule them yet. Couple of clarifications inline. On 06/05/2018 08:29 AM, Jay Pipes wrote: > On 06/05/2018 08:50 AM, Stephen Finucane wrote: >> I thought nested resource providers were already supported by >>

Re: [openstack-dev] Unsubscribe

Hey Henry, see footer on every message for how to unsubscribe. On 06/05/2018 09:09 AM, Henry Nash wrote: __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [tripleo][tripleoclient] No more global sudo for "stack" on the undercloud

Hello guys! I'm currently working on python-tripleoclient in order to squash the dreadful "NOPASSWD:ALL" allowed to the "stack" user. The start was an issue with the rights on some files being wrong (owner by root instead of stack, in stack home). After some digging and poking, it appears the

[openstack-dev] [all][sdk] Integrating OpenStack and k8s with a service broker

I've been doing some investigation into the Service Catalog in Kubernetes and how we can get OpenStack resources to show up in the catalog for use by applications running in Kubernetes. (The Big 3 public clouds already support this.) The short answer is via an implementation of something

Re: [openstack-dev] [tc] StarlingX project status update

Hi everyone: This email is just to provide an update to the initial email regarding the state of StarlingX. The team has proposed a set of repositories to be imported[1] which are completely new projects (not forks of OpenStack or any other open source software). Importing those projects will

Re: [openstack-dev] [tc] Organizational diversity tag

Excerpts from Doug Hellmann's message of 2018-06-02 15:08:28 -0400: > Excerpts from Jeremy Stanley's message of 2018-06-02 18:51:47 +: > > On 2018-06-02 13:23:24 -0400 (-0400), Doug Hellmann wrote: > > [...] > > > It feels like we would be saying that we don't trust 2 core reviewers > > > from

[openstack-dev] [horizon][plugins][heat][searchlight][murano][sahara][watcher] Use default Django test runner instead of nose

Hi team, In Horizon, we're going to get rid of unsupported Nose and use Django Test Runner instead of it [1]. Nose has some issues and limitations which blocks us in our testing improvement efforts. Nose has different test discovery mechanism than Django does. So, there was a chance to break

Re: [openstack-dev] [tc] summary of joint leadership meeting from 20 May

Excerpts from Jay Pipes's message of 2018-06-04 18:47:22 -0400: > On 06/04/2018 05:02 PM, Doug Hellmann wrote: > > The most significant point of interest to the contributor > > community from this section of the meeting was the apparently > > overwhelming interest from companies employing

[openstack-dev] Unsubscribe

> On 5 Jun 2018, at 14:56, Eric Fried wrote: > > To summarize: cyborg could model things nested-wise, but there would be > no way to schedule them yet. > > Couple of clarifications inline. > > On 06/05/2018 08:29 AM, Jay Pipes wrote: >> On 06/05/2018 08:50 AM, Stephen Finucane wrote: >>> I

Re: [openstack-dev] Forum Recap - Stein Release Goals

Excerpts from Matt Riedemann's message of 2018-06-04 18:46:15 -0500: > On 6/4/2018 4:20 PM, Doug Hellmann wrote: > > See my comments on the other part of the thread, but I think this is too > > optimistic until we add a couple of people to the review team on OSC. > > > > Others from the OSC team

Re: [openstack-dev] [TC] Stein Goal Selection

Excerpts from Sean McGinnis's message of 2018-06-05 07:26:27 -0500: > On Mon, Jun 04, 2018 at 06:44:15PM -0500, Matt Riedemann wrote: > > On 6/4/2018 5:13 PM, Sean McGinnis wrote: > > > Yes, exactly what I meant by the NOOP. I'm not sure what Cinder would > > > check here. We don't have to see if

Re: [openstack-dev] [tc] summary of joint leadership meeting from 20 May

On 6/5/2018 7:31 AM, Sean McGinnis wrote: On Tue, Jun 05, 2018 at 11:21:16AM +0200, Thierry Carrez wrote: Jay Pipes wrote: On 06/04/2018 05:02 PM, Doug Hellmann wrote: [...]> Personally, I've very much enjoyed the separate PTGs because I've actually been able to get work done at them;

Re: [openstack-dev] [tc] summary of joint leadership meeting from 20 May

On 05/06/18 16:22, Jay S Bryant wrote: > > > On 6/5/2018 7:31 AM, Sean McGinnis wrote: >> On Tue, Jun 05, 2018 at 11:21:16AM +0200, Thierry Carrez wrote: >>> Jay Pipes wrote: On 06/04/2018 05:02 PM, Doug Hellmann wrote: > [...]> Personally, I've very much enjoyed the separate PTGs

Re: [openstack-dev] [heat][ci][infra] telemetry test broken on oslo.messaging stable/queens

Excerpts from Ken Giusti's message of 2018-06-05 10:47:17 -0400: > Hi, > > The telemetry integration test for oslo.messaging has started failing > on the stable/queens branch [0]. > > A quick review of the logs points to a change in heat-tempest-plugin > that is incompatible with the version of

Re: [openstack-dev] [tc] Organizational diversity tag

That might not be a good idea. That may just push the problem underground as people are afraid to speak up publicly. Perhaps an anonymous poll kind of thing, so that it can be counted publicly but doesn't cause people to fear retaliation? Thanks, Kevin

Re: [openstack-dev] [horizon][plugins][heat][searchlight][murano][sahara][watcher] Use default Django test runner instead of nose

Excerpts from Ivan Kolodyazhny's message of 2018-06-05 16:32:22 +0300: > Hi team, > > In Horizon, we're going to get rid of unsupported Nose and use Django Test > Runner instead of it [1]. Nose has some issues and limitations which blocks > us in our testing improvement efforts. > > Nose has

[openstack-dev] [heat][ci][infra] telemetry test broken on oslo.messaging stable/queens

Hi, The telemetry integration test for oslo.messaging has started failing on the stable/queens branch [0]. A quick review of the logs points to a change in heat-tempest-plugin that is incompatible with the version of gabbi from queens upper constraints (1.40.0) [1][2]. The job definition [3]

Re: [openstack-dev] [tripleo][tripleoclient] No more global sudo for "stack" on the undercloud

On Tue, Jun 5, 2018 at 3:44 PM, Cédric Jeanneret wrote: > Hello guys! > > I'm currently working on python-tripleoclient in order to squash the > dreadful "NOPASSWD:ALL" allowed to the "stack" user. > > The start was an issue with the rights on some files being wrong (owner > by root instead of

Re: [openstack-dev] [tc] StarlingX project status update

Excerpts from Graham Hayes's message of 2018-06-05 16:42:45 +0100: > > On 30/05/18 21:23, Mohammed Naser wrote: > > Hi everyone: > > > > Over the past week in the summit, there was a lot of discussion > > regarding StarlingX > > and members of the technical commitee had a few productive

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

On 06/05/2018 08:50 AM, Stephen Finucane wrote: I thought nested resource providers were already supported by placement? To the best of my knowledge, what is /not/ supported is virt drivers using these to report NUMA topologies but I doubt that affects you. The placement guys will need to

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

Alex- Allocations for an instance are pulled down by the compute manager and passed into the virt driver's spawn method since [1]. An allocation comprises a consumer, provider, resource class, and amount. Once we can schedule to trees, the allocations pulled down by the compute manager

Re: [openstack-dev] [tc] StarlingX project status update

On 30/05/18 21:23, Mohammed Naser wrote: > Hi everyone: > > Over the past week in the summit, there was a lot of discussion > regarding StarlingX > and members of the technical commitee had a few productive discussions > regarding > the best approach to deal with a proposed new pilot project

Re: [openstack-dev] [tc] StarlingX project status update

I agree with Graham +1 Remo > On Jun 5, 2018, at 8:42 AM, Graham Hayes wrote: > > > > On 30/05/18 21:23, Mohammed Naser wrote: >> Hi everyone: >> >> Over the past week in the summit, there was a lot of discussion >> regarding StarlingX >> and members of the technical commitee had a few

Re: [openstack-dev] [horizon][plugins][heat][searchlight][murano][sahara][watcher] Use default Django test runner instead of nose

This is an important step to drop nose and nosehtmloutput :) We plan to switch the test runner and then re-enable integration tests (with selenium) for cross project testing. In addition, we horizon team are trying to minimize gate breakage in horizon plugins for recent changes (this and django

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

Maybe I missed something. Is there anyway the nova-compute can know the resources are allocated from which child resource provider? For example, the host has two PFs. The request is asking one VF, then the nova-compute needs to know the VF is allocated from which PF (resource provider). As my

[openstack-dev] [FEMDC] meetings suspended until further notice

Dear all, Following the exchanges we had during the Vancouver summit, in particular the non-sense to maintain/animate two groups targeting similar challenges (ie., the FEMDC SIG [1] and the new Edge Computing Working group [2]), FEMDC meetings are suspended until further notice. If you are

[openstack-dev] [tc] proposing changes to the project-team-guide-core review team

The review team [1] for the project-team-guide repository (managed by the TC) hasn't been updated for a while. I would like to propose removing a few reviewers who are no longer active, and adding one new reviewer. My understanding is that Kyle Mestery and Nikhil Komawar have both moved on from

Re: [openstack-dev] [tc] Organizational diversity tag

Excerpts from Fox, Kevin M's message of 2018-06-05 16:09:24 +: > That might not be a good idea. That may just push the problem underground as > people are afraid to speak up publicly. > > Perhaps an anonymous poll kind of thing, so that it can be counted publicly > but doesn't cause people

Re: [openstack-dev] [tc] proposing changes to the project-team-guide-core review team

Doug Hellmann wrote: > The review team [1] for the project-team-guide repository (managed > by the TC) hasn't been updated for a while. I would like to propose > removing a few reviewers who are no longer active, and adding one > new reviewer. > > My understanding is that Kyle Mestery and Nikhil

Re: [openstack-dev] [all][sdk] Integrating OpenStack and k8s with a service broker

I will be happy to check it out. Remo > On Jun 5, 2018, at 9:19 AM, Zane Bitter wrote: > > I've been doing some investigation into the Service Catalog in Kubernetes and > how we can get OpenStack resources to show up in the catalog for use by > applications running in Kubernetes. (The Big 3

Re: [openstack-dev] [tripleo] Status of Standalone installer (aka All-In-One)

On Tue, Jun 5, 2018 at 3:31 AM Raoul Scarazzini wrote: > On 05/06/2018 02:26, Emilien Macchi wrote: > [...] > > I hope this update was useful, feel free to give feedback or ask any > > questions, > [...] > > I'm no prophet here, but I see a bright future for this approach. I can > imagine how

Re: [openstack-dev] [tc] proposing changes to the project-team-guide-core review team

On 06/05/2018 11:14 AM, Doug Hellmann wrote: [snip] My understanding is that Kyle Mestery and Nikhil Komawar have both moved on from OpenStack to other projects, so I propose that we remove them from the core team. Chris Dent has been active with reviews lately and has expressed willingness

[openstack-dev] [all][sdk] Integrating OpenStack and k8s with a service broker

Hi Zane, > Would you be interested in working on a new project to implement this > integration? Reply to this thread and let's collect a list of volunteers > to form the initial core review team. Yes, I would also like to join. That's exactly what I am looking at in my company as part of K8 over

Re: [openstack-dev] [heat][ci][infra] telemetry test broken on oslo.messaging stable/queens

On Tue, Jun 05, 2018 at 10:47:17AM -0400, Ken Giusti wrote: > Hi, > > The telemetry integration test for oslo.messaging has started failing > on the stable/queens branch [0]. > > A quick review of the logs points to a change in heat-tempest-plugin > that is incompatible with the version of gabbi

[openstack-dev] [tripleo] The Weekly Owl - 23th Edition

Welcome to the twenty third edition of a weekly update in TripleO world! The goal is to provide a short reading (less than 5 minutes) to learn what's new this week. Any contributions and feedback are welcome. Link to the previous version:

Re: [openstack-dev] [all][python3][tc][infra] Python 3.6

On 2018-06-05 15:55:49 -0400 (-0400), Zane Bitter wrote: [...] > AIUI we're planning to switch the test nodes to Bionic, since it's > the latest LTS release, so I'd assume that means that when we talk > about running docs jobs, pep8 with Python3 (under the > python3-first project-wide goal) that

Re: [openstack-dev] [all][python3][tc][infra] Python 3.6

On 05/06/18 16:38, Doug Hellmann wrote: Excerpts from Zane Bitter's message of 2018-06-05 15:55:49 -0400: We've talked a bit about migrating to Python 3, but (unless I missed it) not a lot about which version of Python 3. Currently all projects that support Python 3 are gating against 3.5.

Re: [openstack-dev] [tripleo] Status of Standalone installer (aka All-In-One)

On Mon, Jun 4, 2018 at 8:26 PM, Emilien Macchi wrote: > TL;DR: we made nice progress and you can checkout this demo: > https://asciinema.org/a/185533 > > We started the discussion back in Dublin during the last PTG. The idea of > Standalone (aka All-In-One, but can be mistaken with all-in-one

[openstack-dev] [all][python3][tc][infra] Python 3.6

We've talked a bit about migrating to Python 3, but (unless I missed it) not a lot about which version of Python 3. Currently all projects that support Python 3 are gating against 3.5. However, Ubuntu Artful and Fedora 26 already ship Python 3.6 by default. (And Bionic and F28 have been

Re: [openstack-dev] [all][python3][tc][infra] Python 3.6

Excerpts from Zane Bitter's message of 2018-06-05 15:55:49 -0400: > We've talked a bit about migrating to Python 3, but (unless I missed it) > not a lot about which version of Python 3. Currently all projects that > support Python 3 are gating against 3.5. However, Ubuntu Artful and > Fedora 26

Re: [openstack-dev] [keystone] Signing off

Henry, I'm really sad to see you go, you were a terrific mentor when I first joined the community - I remember all the thorough reviews and nice discussions ranging from topics on how to model the root domain for the reseller usecase to how to improve the role assignments API. :) Thanks for

Re: [openstack-dev] [tripleo][tripleoclient] No more global sudo for "stack" on the undercloud

> > > > In regards to your suggested positions within python code such as the > > client, its worth looking at oslo.privsep [1] where a decorator can be > > used for when needing to setuid. > > hmm yep, have to understand how to use it - its doc is.. well. kind of > sparse. Would be good to get

Re: [openstack-dev] [neutron][stable] Stepping down from core

On Mon, Jun 04, 2018 at 01:31:11PM -0700, Ihar Hrachyshka wrote: > Hi neutrinos and all, > > As some of you've already noticed, the last several months I was > scaling down my involvement in Neutron and, more generally, OpenStack. > I am at a point where I feel confident my disappearance won't

Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

Hi, akihiro and other guys, I understand why minified is considered to be non-free, but I was confused about the statement "At the very least, a non-minified version should be present next to the minified version" [1] in the documentation. Actually in existing xstatic repo, I observed several

Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

2018年6月6日(水) 11:54 Xinni Ge : > Hi, akihiro and other guys, > > I understand why minified is considered to be non-free, but I was confused > about the statement > "At the very least, a non-minified version should be present next to the > minified version" [1] > in the documentation. > > Actually

[openstack-dev] [kuryr][kuryr-kubernetes] Propose to support Kubernetes Network Custom Resource Definition De-facto Standard Version 1

Hi Kuryr-kubernetes team, I'm thinking to propose a new BP to support Kubernetes Network Custom Resource Definition De-facto Standard Version 1 [1], which was drafted by network plumbing working group of kubernetes-sig-network. I'll call it NPWG spec below. The purpose of NPWG spec is trying to

Re: [openstack-dev] [tripleo][tripleoclient] No more global sudo for "stack" on the undercloud

On 06/05/2018 06:08 PM, Luke Hinds wrote: > > > On Tue, Jun 5, 2018 at 3:44 PM, Cédric Jeanneret > wrote: > > Hello guys! > > I'm currently working on python-tripleoclient in order to squash the > dreadful "NOPASSWD:ALL" allowed to the "stack" user. >

Re: [openstack-dev] [tripleo][tripleoclient] No more global sudo for "stack" on the undercloud

On 06/06/2018 06:37 AM, Mike Carden wrote: > > > In regards to your suggested positions within python code such as the > > client, its worth looking at oslo.privsep [1] where a decorator can be > > used for when needing to setuid. > > hmm yep, have to understand how to use it -

Re: [openstack-dev] [all][python3][tc][infra] Python 3.6

On 06/05/2018 02:55 PM, Zane Bitter wrote: [snip] The list of breaking changes in 3.6 is quite short (although not zero), so I wouldn't expect too many roadblocks: https://docs.python.org/3/whatsnew/3.6.html#porting-to-python-3-6 I think we can split the problem into two parts: * How can we

[openstack-dev] [qa][ptg] Mark your availability for Denver PTG, 2018

Hi All, As you all might know that next PTG is in Denver [1] and we will plan the QA space in PTG. Please let me know if you are planning to attend the QA sessions (Not necessary to be full time in QA area). This is to get the rough number of attendees in QA. I know it might be little early

Re: [openstack-dev] [all][sdk] Integrating OpenStack and k8s with a service broker

Hi Zane, please count me in :-) Cheers, Lingxian Kong On Wed, Jun 6, 2018 at 4:52 AM, Remo Mattei wrote: > I will be happy to check it out. > > Remo > > > On Jun 5, 2018, at 9:19 AM, Zane Bitter wrote: > > I've been doing some investigation into the Service Catalog in Kubernetes > and how we

Re: [openstack-dev] [all][python3][tc][infra] Python 3.6

On Tue, Jun 05, 2018 at 04:48:00PM -0400, Zane Bitter wrote: > On 05/06/18 16:38, Doug Hellmann wrote: > > Excerpts from Zane Bitter's message of 2018-06-05 15:55:49 -0400: > > > We've talked a bit about migrating to Python 3, but (unless I missed it) > > > not a lot about which version of Python

Re: [openstack-dev] [tripleo] [barbican] [tc] key store in base services

On 2018-05-31 13:00:47 + (+), Jeremy Stanley wrote: > On 2018-05-31 10:33:51 +0200 (+0200), Thierry Carrez wrote: > > Ade Lee wrote: > > > [...] > > > So it seems that the two blockers above have been resolved. So is it > > > time to ad a castellan compatible secret store to the base

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

2018-06-05 22:53 GMT+08:00 Eric Fried : > Alex- > > Allocations for an instance are pulled down by the compute manager > and > passed into the virt driver's spawn method since [1]. An allocation > comprises a consumer, provider, resource class, and amount. Once we can > schedule to

Re: [openstack-dev] [horizon][plugins][heat][searchlight][murano][sahara][watcher] Use default Django test runner instead of nose

Thanks Ivan, will check your patch soon. Regards, Kaz(Heat) 2018-06-05 22:59 GMT+09:00 Akihiro Motoki : > This is an important step to drop nose and nosehtmloutput :) > We plan to switch the test runner and then re-enable integration tests > (with selenium) for cross project testing. > > In

Re: [openstack-dev] [tripleo][tripleoclient] No more global sudo for "stack" on the undercloud

> > > \o/ - care to add the links on the doc? Would be really helpful for > others I guess :). > Doc? What doc? -- MC __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [tripleo][tripleoclient] No more global sudo for "stack" on the undercloud

On 06/06/2018 06:59 AM, Mike Carden wrote: > > \o/ - care to add the links on the doc? Would be really helpful for > others I guess :). > > > Doc? What doc? This one: https://docs.openstack.org/oslo.privsep/latest/index.html I just created https://review.openstack.org/#/c/572670/