Re: [openstack-dev] [mistral] September PTG in Denver

Hi Dougal, Very likely, I will join over the phone. Thanks, Andras From: Renat Akhmerov Sent: Tuesday, April 24, 2018 2:46:36 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [mistral]

Re: [openstack-dev] Changes to keystone-stable-maint members

> > > >Additions > >=== > >Lance Bragstad > > > >Lance is the PTL and also highly aware (and does reviews for stable > >keystone when I ask, so we have a second pair of eyes on them) of the > >differences/stable policy. > > > >This will bring us to a solid 2 contributors for Keystone that are

[openstack-dev] [cyborg]Weekly Team Meeting 2018.04.25

Hi Team, Team meeting starting UTC1400 as usual at #openstack-cyborg, initial agenda as follows: 1. KubeCon preparation for resource mgmt wg discussion 2. subteam meeting arrangement for more agile meeting time/logistic 3. Rocky critical spec update 4. open patches/bug review -- Zhipeng

Re: [openstack-dev] [openstack-infra] [neutron] Change of control over network-onos (was: How to take over a project?)

Thank you, Jeremy I did not think that it takes so long. :-) Sangho > On 24 Apr 2018, at 11:39 PM, Jeremy Stanley wrote: > > On 2018-04-20 01:01:33 +0900 (+0900), Sangho Shin wrote: >> Dear Neutron-Release team, >> >> I wonder if any of you can add me to the

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

I think many projects are now beginning to develop the sub-team structure (e.g Nova, Ironic and Cyborg) and that might be part of the answer here. Having a sub-team structure and also have volunteer as sub team leads could also help people that are not good at code review to contribute

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

On 24/04/18 12:04, Fox, Kevin M wrote: Yeah, I agree k8s seems to have hit on a good model where interests are separately grouped from the code bases. This has allowed architecture to not to be too heavily influenced by the logical groups interest. I'll go ahead and propose it again since its

Re: [openstack-dev] [Heat][TripleO] - Getting attributes of openstack resources not created by the stack for TripleO NetworkConfig.

On 19/04/18 08:59, Harald Jensås wrote: The problem is getting there using heat ... The real answer is to make everything explicit - create a Subnet resource and a Port resource and don't allow Neutron/Nova to make any decisions for you that would have the effect of hiding data that you

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

On Tue, Apr 24, 2018 at 3:51 PM, Fox, Kevin M wrote: > I support 12 factor. But 12 factor only works if you can commit to always > deploying on top of 12 factor tools. If OpenStack committed to only ever > deploying api services on k8s then my answer might be different. but

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

I support 12 factor. But 12 factor only works if you can commit to always deploying on top of 12 factor tools. If OpenStack committed to only ever deploying api services on k8s then my answer might be different. but so far has been unable to do that. Barring that, I think simplifying the

Re: [openstack-dev] [Heat][TripleO] - Getting attributes of openstack resources not created by the stack for TripleO NetworkConfig.

On 23/04/18 14:09, Dan Sneddon wrote: Yes, the port is currently created as part of the Ironic server resource. We would have more flexibility if this were a separate Neutron port, but we need to be able to support upgrades. This would require the ability in Heat to detach the implicit port

Re: [openstack-dev] Changes to keystone-stable-maint members

On 4/24/2018 12:58 PM, Morgan Fainberg wrote: Hi, I am proposing making some changes to the Keystone Stable Maint team. A lot of this is cleanup for contributors that have moved on from OpenStack. For the most part, I've been the only one responsible for Keystone Stable Maint reviews, and I'm

[openstack-dev] Changes to keystone-stable-maint members

Hi, I am proposing making some changes to the Keystone Stable Maint team. A lot of this is cleanup for contributors that have moved on from OpenStack. For the most part, I've been the only one responsible for Keystone Stable Maint reviews, and I'm not comfortable being this bottleneck Removals

Re: [openstack-dev] [All][Election] Rocky TC Election Voting Begins!

On 2018-04-24 00:03:55 + (+), Kendall Nelson wrote: > The poll for the TC Election is now open and will remain open until Apr 30, > 2018 23:45 UTC. > > We are selecting 7 TC members, please rank all candidates in > your order of preference. [...] Please note that the poll was configured

Re: [openstack-dev] [nova] Notification update week 17

On 4/23/2018 8:07 AM, Balázs Gibizer wrote: Add versioned notifications for removing a member from a server group - The specless bp https://blueprints.launchpad.net/nova/+spec/add-server-group-remove-member-notifications is

Re: [openstack-dev] [openstack-ansible] Proposing Mohammed Naser as core reviewer

On 4/24/18, 4:08 PM, "Jean-Philippe Evrard" wrote: >I’d like to propose Mohammed Naser [1] as a core reviewer for > OpenStack-Ansible. A happy +2 from me. ( Rackspace Limited is a company registered in England & Wales (company

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

On 04/24/2018 12:04 PM, Fox, Kevin M wrote: Could the major components, nova-api, neutron-server, glance-apiserver, etc be built in a way to have 1 process for all of them, and combine the upgrade steps such that there is also, one db-sync for the entire constellation? So, basically the

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

Yeah, I agree k8s seems to have hit on a good model where interests are separately grouped from the code bases. This has allowed architecture to not to be too heavily influenced by the logical groups interest. I'll go ahead and propose it again since its been a little while. In order to start

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

Note: this is the eighteenth edition of a weekly update of what happens in TripleO. The goal is to provide a short reading (less than 5 minutes) to learn where we are and what we're doing. Any contributions and feedback are welcome. Link to the previous version:

Re: [openstack-dev] [designate] Meeting Times - change to office hours?

I prefer 14:00 to 22:00 UTC, although depending on the time of year I may have some flexibility on that. On 04/24/2018 01:37 AM, Erik Olof Gunnar Andersson wrote: I can do anytime ranging from 16:00 UTC to 03:00 UTC, Mon-Fri, maybe up to 07:00 UTC assuming that it's once bi-weekly.

Re: [openstack-dev] [openstack-ansible] Proposing Mohammed Naser as core reviewer

+2 from me. Marc Gariépy On 2018-04-24 11:05 AM, Jean-Philippe Evrard wrote: Hi everyone, I’d like to propose Mohammed Naser [1] as a core reviewer for OpenStack-Ansible. He has been working actively on fixing the telemetry stack, and is now willing to step up to improve the CentOS platform

[openstack-dev] [barbican] Hangout Barbican team

Hi Barbican team, In order to be easy for reviewing some patch sets in Barbican, we propose that it should have a hangout meeting on 10pm EDT - Monday 30 April. So i would like to send an email to notify everyone that feel free to join with us by leaving your email. Cheers, Nam?

Re: [openstack-dev] [openstack-ansible] Proposing Mohammed Naser as core reviewer

+2 from me! Amy (spotz) On Tue, Apr 24, 2018 at 10:05 AM, Jean-Philippe Evrard < jean-phili...@evrard.me> wrote: > Hi everyone, > > I’d like to propose Mohammed Naser [1] as a core reviewer for > OpenStack-Ansible. > > He has been working actively on fixing the telemetry stack, and is now >

Re: [openstack-dev] [tc] campaign question: How "active" should the TC be?

On Mon, Apr 23, 2018 at 10:12:49PM +, Jeremy Stanley wrote: > On 2018-04-23 16:56:28 -0500 (-0500), Sean McGinnis wrote: > [...] > > I think Howard had an excellent idea of the TC coming up with > > themes for each cycle. I think that could be used to create a good > > cadence or focus to make

[openstack-dev] [FEMDC] Wed. 25 Apr - FEMDC IRC Meeting 15:00 UTC

Dear all, Here is a gentle reminder for the FEMDC meeting tomorrow at 15:00 UTC. A draft of the agenda is available at line 466 and you are very welcome to add any item: https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2018 Best regards, Dimitri

[openstack-dev] [openstack-ansible] Proposing Mohammed Naser as core reviewer

Hi everyone, I’d like to propose Mohammed Naser [1] as a core reviewer for OpenStack-Ansible. He has been working actively on fixing the telemetry stack, and is now willing to step up to improve the CentOS platform which is now in a very degraded state. I feel that it’s important that he’s able

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

Alex- On 04/24/2018 09:21 AM, Alex Xu wrote: > > > 2018-04-24 20:53 GMT+08:00 Eric Fried >: > > > The problem isn't just checking the traits in the nested resource > > provider. We also need to ensure the trait in the exactly same child

Re: [openstack-dev] [kolla][vote]Retire kolla-kubernetes project

+1 As we don't have active core team in Kolla-kubernetes since months, unfortunately going for sunset is reasonable. Though happy to help in running OpenStack on kubernetes. --- Thanks Surya On Wed, Apr 18, 2018 at 7:21 AM, Jeffrey Zhang wrote: > Since many of the

Re: [openstack-dev] [tc] campaign question related to new projects

On 2018-04-24 09:59:57 -0400 (-0400), Zane Bitter wrote: [...] > the PTG has limited attendance from operators [...] I have high hopes that will not be the case for the next PTG. -- Jeremy Stanley signature.asc Description: PGP signature

Re: [openstack-dev] [openstack-infra] [neutron] Change of control over network-onos (was: How to take over a project?)

On 2018-04-20 01:01:33 +0900 (+0900), Sangho Shin wrote: > Dear Neutron-Release team, > > I wonder if any of you can add me to the network-onos-release member. > It seems that Vikram is busy. :-) [...] I've adjusted the subject line here in hopes the thread might better catch their attention. --

Re: [openstack-dev] [tripleo] Proposing Marius Cornea core on upgrade bits

Thanks everyone for your trust and support. On Mon, Apr 23, 2018 at 5:35 PM, Emilien Macchi wrote: > Thanks everyone for your positive feedback. > I've updated Gerrit! > > Welcome Marius and thanks again for your hard work! > > On Mon, Apr 23, 2018 at 4:55 AM, James Slagle

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

2018-04-24 20:53 GMT+08:00 Eric Fried : > > The problem isn't just checking the traits in the nested resource > > provider. We also need to ensure the trait in the exactly same child > > resource provider. > > No, we can't get "granular" with image traits. We accepted this as

Re: [openstack-dev] [tc] campaign question related to new projects

On 24/04/18 05:55, Thierry Carrez wrote: Zane Bitter wrote: [...] I would love to see us have a conversation as a community to figure out what we all, collectively, think that list should look like and document it. Ideally new projects shouldn't have to wait until they've applied to join

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

Sorry folks for the late reply, I'll try to also weigh in the Gerrit change. On Tue, Apr 24, 2018 at 2:55 PM, Jay Pipes wrote: > On 04/23/2018 05:51 PM, Arvind N wrote: > >> Thanks for the detailed options Matt/eric/jay. >> >> Just few of my thoughts, >> >> For #1, we can

[openstack-dev] [OSSN-0083] Keystone policy rule "identity:get_identity_providers" was ignored

Keystone policy rule "identity:get_identity_providers" was ignored --- ### Summary ### A policy rule in Keystone did not behave as intended leading to a less secure configuration than would be expected. ### Affected Services / Software ### OpenStack Identity Service (Keystone) versions through

Re: [openstack-dev] [mistral] September PTG in Denver

Dougal, Most likely, I’ll go. Thanks Renat Akhmerov @Nokia 24 апр. 2018 г., 17:05 +0700, Dougal Matthews , писал: > > > > On 23 April 2018 at 20:58, Sean McGinnis wrote: > > > On Mon, Apr 23, 2018 at 07:32:40PM +, Kendall Nelson wrote: > > > > Hey

Re: [openstack-dev] [neutron] Bug deputy report

oops, i forgot to add the critical one. Critical https://bugs.launchpad.net/neutron/+bug/1765008 Tempest API tests failing for stable/queens branch On Tue, Apr 24, 2018 at 9:11 PM, Takashi Yamamoto wrote: > hi, > > here's a summary of this week. > > RFEs for drivers team:

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

On 04/23/2018 05:51 PM, Arvind N wrote: Thanks for the detailed options Matt/eric/jay. Just few of my thoughts, For #1, we can make the explanation very clear that we rejected the request because the original traits specified in the original image and the new traits specified in the new

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

> The problem isn't just checking the traits in the nested resource > provider. We also need to ensure the trait in the exactly same child > resource provider. No, we can't get "granular" with image traits. We accepted this as a limitation for the spawn aspect of this spec [1], for all the same

Re: [openstack-dev] [os-upstream-institute] Prep call for Vancouver today - Minutes

Hi All, I would like to thank all of you who were able to join to our planning call yesterday for the Vancouver training. For meeting minutes please visit the following etherpad: https://etherpad.openstack.org/p/OUI-AIO-guide-planning We also recorded the call, so those of you who couldn’t

[openstack-dev] [tc] [all] TC Report 18-17

HTML: https://anticdent.org/tc-report-18-17.html The main TC-related activity over the past week has been the [elections](https://governance.openstack.org/election/) currently in progress. A quiet campaigning period burst into late activity with a series of four questions posted in email by

[openstack-dev] [neutron] Bug deputy report

hi, here's a summary of this week. RFEs for drivers team: https://bugs.launchpad.net/neutron/+bug/1766380 [RFE] Create host-routes for routed networks (segments) https://bugs.launchpad.net/neutron/+bug/1764738 routed provider networks limit to one host Medium:

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

Thierry, please see below: On Tue, Apr 24, 2018 at 6:24 AM, Thierry Carrez wrote: > Fox, Kevin M wrote: >> OpenStack has created artificial walls between the various Projects. It >> shows up, for example, as holes in usability at a user level or extra >> difficulty for

Re: [openstack-dev] [tc] campaign question: How can we make contributing to OpenStack easier?

Fox, Kevin M wrote: > OpenStack has created artificial walls between the various Projects. It shows > up, for example, as holes in usability at a user level or extra difficulty > for operators juggling around so many projects. Users and for the most part, > Operators don't really care about

Re: [openstack-dev] [tc] campaign question: How "active" should the TC be?

Zane Bitter wrote: > [...]> I definitely don't want to get rid of office hours, and I think the > reasons for dropping the meeting (encouraging geographically diverse > participation) are still valid. I'd like to see the TC come up with a > program of work for the term after each Summit, and

Re: [openstack-dev] [mistral] September PTG in Denver

On 23 April 2018 at 20:58, Sean McGinnis wrote: > On Mon, Apr 23, 2018 at 07:32:40PM +, Kendall Nelson wrote: > > Hey Dougal, > > > > I think I had said May 2nd in my initial email asking about attendance. > If > > you can get an answer out of your team by then I would

Re: [openstack-dev] [tc] campaign question related to new projects

Zane Bitter wrote: > [...] > I would love to see us have a conversation as a community to figure out > what we all, collectively, think that list should look like and document > it. Ideally new projects shouldn't have to wait until they've applied to > join OpenStack to get a sense of whether we

Re: [openstack-dev] [tc] campaign question: How should we handle projects with overlapping feature sets?

Rico Lin wrote: > I think we have a start now with providing a decent map to show services > in OpenStack and fill in with projects. What we should have and will be > nice is to ask projects to search through the map (with a brief > introduction of services) when they're registering. To prevent >

Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

Doug Hellmann wrote: > Excerpts from Graham Hayes's message of 2018-04-23 15:36:32 +0100: >> I think as an add on to this, would to ask the board to talk to members >> and see what contributions they have made to the technical side of >> OpenStack. >> >> This should not just be Number of commits /

Re: [openstack-dev] [neutron] Gate-failure bugs spring cleaning

On 21/04/2018 14:16, Slawomir Kaplonski wrote: > Hi Neutrinos, > > There is time for some spring cleaning now so I went through list of Neutron > bugs with „gate-failure” tag https://tinyurl.com/y826rccx > I mark some of them as incomplete if there was not hits of same errors in > last 30

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

On Tue, Apr 24, 2018 at 9:08 AM, Alex Xu wrote: 2018-04-24 5:51 GMT+08:00 Arvind N : Thanks for the detailed options Matt/eric/jay. Just few of my thoughts, For #1, we can make the explanation very clear that we rejected the request because the

Re: [openstack-dev] [openstack-infra] How to take over a project?

Dear Neutron-Release team members, Can any of you handle the issue below? Thank you so much for your help in advance. Sangho > On 20 Apr 2018, at 10:01 AM, Sangho Shin wrote: > > Dear Neutron-Release team, > > I wonder if any of you can add me to the

Re: [openstack-dev] [Vitrage] Vitrage graph error

Hello Ifat, I have not checked the alarm yet. (I think it does not work.) However, i confirmed that the entity graph and the topology do not work. Additionally, the CLI does not seem to work either. I'll check it out with you. : ) Thank you. Best Regards, Minwook.

[openstack-dev] [publiccloud-wg]KubeCon EU Public Cloud Meetup ?

Hi, I'm wondering for people who will attend KubeCon EU is there any interest for a public cloud meetup ? We could discuss many items listed in the ptg summary I just sent out via the meetup :) -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei Technologies

Re: [openstack-dev] [Vitrage] Vitrage graph error

Hi Minwook, Is the problem only in the Entity Graph? Do the Alarms view and the Topology view work? And what about the CLI? I’ll check it and get back to you. Thanks, Ifat From: MinWookKim Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

2018-04-24 5:51 GMT+08:00 Arvind N : > Thanks for the detailed options Matt/eric/jay. > > Just few of my thoughts, > > For #1, we can make the explanation very clear that we rejected the > request because the original traits specified in the original image and the > new

Re: [openstack-dev] [designate] Meeting Times - change to office hours?

I can do anytime ranging from 16:00 UTC to 03:00 UTC, Mon-Fri, maybe up to 07:00 UTC assuming that it's once bi-weekly. From: Jens Harbott Sent: Monday, April 23, 2018 10:49:25 PM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [all][ptl][release][masakari][murano][qinling][searchlight][zaqar] reminder for rocky-1 milestone deadline

Hi Doug and ALL, Thank you for the reminder. This was my mistake and really ​s orry for any inconvenience this may have caused. This will not happen again.​​ ​Patches are up to review for following projects.​ > masakari-monitors ​> ​ masakari --- Regards, Sampath On Sat, Apr 21, 2018 at 3:04