[openstack-dev] [publiccloud-wg] Reminder weekly meeting Public Cloud WG

Hi everyone, Time for a new meeting for PCWG - today (27th) 1400 UTC in #openstack-publiccloud! Agenda found at https://etherpad.openstack.org/p/publiccloud-wg We will again have a short brief from the PTG for those of you that missed that last week. Also, time to start planning for the upco

Re: [openstack-dev] [mistral] Extend created(updated)_at by started(finished)_at to clarify the duration of the task

Hi Oleg, I looked at the blueprint. Looks good to me, I understand the motivation behind. The fact that we use created_at and updated_at now to see the duration of the task is often confusing, I agree. So this would be a good addition and it is backward compatible. The only subtle thing is that

Re: [openstack-dev] [keystone] Domain-namespaced user attributes in SAML assertions from Keystone IdPs

> From : Colleen Murphy > To : > Date : Tue, 25 Sep 2018 18:33:30 +0900 > Subject : Re: [openstack-dev] [keystone] Domain-namespaced user attributes in > SAML assertions from Keystone IdPs > Forwarded message > > On Mon, Sep 24, 2018, at 8:40 PM, John Dennis wrote: >

Re: [openstack-dev] [neutron] subnet pool can not delete prefixes

On 09/26/2018 10:11 PM, wenran xiao wrote: Relation bug: https://bugs.launchpad.net/neutron/+bug/1792901 Any suggestion is welcome! Removing a prefix from a subnetpool is not supported, there was an inadvertent change to the client that made it seem possible. We are in the process of reverti

Re: [openstack-dev] [heat][senlin] Action Required. Idea to propose for a forum for autoscaling features integration

Hi, Due to many reasons, I cannot join you on this event, but I do like to leave some comments here for references. On Tue, Sep 18, 2018 at 11:27:29AM +0800, Rico Lin wrote: > *TL;DR* > *How about a forum in Berlin for discussing autoscaling integration (as a > long-term goal) in OpenStack?* Fir

[openstack-dev] [neutron] subnet pool can not delete prefixes

Relation bug: https://bugs.launchpad.net/neutron/+bug/1792901 Any suggestion is welcome! Cheers, -wenran __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?su

Re: [openstack-dev] [nova] Stein PTG summary

On 9/26/2018 5:30 PM, Sylvain Bauza wrote: So, during this day, we also discussed about NUMA affinity and we said that we could possibly use nested resource providers for NUMA cells in Stein, but given we don't have yet a specific Placement API query, NUMA affinity should still be using the NUM

[openstack-dev] Last day for TC voting

We are coming down to the last hours for voting in the TC election. Voting ends Sep 27, 2018 23:45 UTC. Search your gerrit preferred email address [0] for the following subject: Poll: Stein TC Election That is your ballot and links you to the voting application. Please vote. If you have vote

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

On 09/26/2018 04:33 PM, Dean Troyer wrote: On Wed, Sep 26, 2018 at 3:44 PM, Matt Riedemann wrote: I started documenting the compute API gaps in OSC last release [1]. It's a big gap and needs a lot of work, even for existing CLIs (the cold/live migration CLIs in OSC are a mess, and you can't eve

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

Oh, very definitely +1000 -- Rochelle Grober Rochelle Grober M: +1-6508889722(preferred) E: rochelle.gro...@huawei.com 2012实验室-硅谷研究所技术规划及合作部 2012 Laboratories-Silicon Valley Technology Planning & Cooperation,Sili

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

On 09/26/2018 04:12 PM, Dean Troyer wrote: On Wed, Sep 26, 2018 at 3:01 PM, Doug Hellmann wrote: Would it be useful to have the SDK work in OSC as a prerequisite to the goal work? I would hate to have folks have to write a bunch of things twice. I don't think this is necessary, once we have t

Re: [openstack-dev] [nova] Stein PTG summary

Thanks for the recap email, Mel. Just a question inline for all the people that were in the room by Wednesday. Le jeu. 27 sept. 2018 à 00:10, melanie witt a écrit : > Hello everybody, > > I've written up a high level summary of the discussions we had at the > PTG -- please feel free to reply to

Re: [openstack-dev] [goal][python3] week 7 update

Doug Hellmann writes: > == Things We Learned This Week == > > When we updated the tox.ini settings for jobs like pep8 and release > notes early in the Rocky session we only touched some of the official > repositories. I'll be working on making a list of the ones we missed so > we can update them

[openstack-dev] [nova] Stein PTG summary

Hello everybody, I've written up a high level summary of the discussions we had at the PTG -- please feel free to reply to this thread to fill in anything I've missed. We used our PTG etherpad: https://etherpad.openstack.org/p/nova-ptg-stein as an agenda and each topic we discussed was fill

Re: [openstack-dev] Ryu integration with Openstack

Hi, Thanks for your reply. Is there a way to access the code that is running in the app to see what is the logic implemented in the app? Regards, Niket On Wed, Sep 26, 2018 at 10:31 PM Slawomir Kaplonski wrote: > Hi, > > > Wiadomość napisana przez Niket Agrawal w dniu > 26.09.2018, o godz. 18

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

On Wed, Sep 26, 2018 at 3:44 PM, Matt Riedemann wrote: > I started documenting the compute API gaps in OSC last release [1]. It's a > big gap and needs a lot of work, even for existing CLIs (the cold/live > migration CLIs in OSC are a mess, and you can't even boot from volume where > nova creates

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

On Wed, Sep 26, 2018 at 3:01 PM, Doug Hellmann wrote: > Would it be useful to have the SDK work in OSC as a prerequisite to the > goal work? I would hate to have folks have to write a bunch of things > twice. I don't think this is necessary, once we have the auth and service discovery/version neg

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

On 9/26/2018 3:01 PM, Doug Hellmann wrote: Monty Taylor writes: On 09/26/2018 01:55 PM, Tim Bell wrote: Doug, Thanks for raising this. I'd like to highlight the goal "Finish moving legacy python-*client CLIs to python-openstackclient" from the etherpad and propose this for a T/U series goa

Re: [openstack-dev] Ryu integration with Openstack

Hi, > Wiadomość napisana przez Niket Agrawal w dniu > 26.09.2018, o godz. 18:11: > > Hello, > > I have a question regarding the Ryu integration in Openstack. By default, the > openvswitch bridges (br-int, br-tun and br-ex) are registered to a controller > running on 127.0.0.1 and port 6633.

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

On 26/09/18 18:55 +, Tim Bell wrote: Doug, Thanks for raising this. I'd like to highlight the goal "Finish moving legacy python-*client CLIs to python-openstackclient" from the etherpad and propose this for a T/U series goal. To give it some context and the motivation: At CERN, we have

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

Monty Taylor writes: > On 09/26/2018 01:55 PM, Tim Bell wrote: >> >> Doug, >> >> Thanks for raising this. I'd like to highlight the goal "Finish moving >> legacy python-*client CLIs to python-openstackclient" from the etherpad and >> propose this for a T/U series goal. >> >> To give it some

Re: [openstack-dev] [Heat] Bug in documentation?

On 26/09/18 12:02 PM, Postlbauer, Juan wrote: Hi everyone: I see that heat doc https://docs.openstack.org/heat/rocky/template_guide/openstack.html#OS::Nova::Flavor states that *ram¶ * Memory in

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

On 09/26/2018 01:55 PM, Tim Bell wrote: Doug, Thanks for raising this. I'd like to highlight the goal "Finish moving legacy python-*client CLIs to python-openstackclient" from the etherpad and propose this for a T/U series goal. To give it some context and the motivation: At CERN, we have m

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

+1 Yes please! -- Mathieu On Wed, Sep 26, 2018 at 2:56 PM Tim Bell wrote: > > > Doug, > > Thanks for raising this. I'd like to highlight the goal "Finish moving legacy > python-*client CLIs to python-openstackclient" from the etherpad and propose > this for a T/U series goal. > > To give it so

Re: [openstack-dev] [storyboard] Prioritization?

On Wed, Sep 26, 2018 at 9:50 AM Ben Nemec wrote: > > > On 9/25/18 3:29 AM, Thierry Carrez wrote: > > Doug Hellmann wrote: > >> I think we need to reconsider that position if it's going to block > >> adoption. I think Ben's case is an excellent second example of where > >> having a field to hold s

Re: [openstack-dev] [storyboard][oslo] Fewer stories than bugs?

So I 100% messed up that migration. Looking back at my terminal history I migrated 'stevedore' instead of 'python-stevedore'. I migrated the correct project now and all should be well. Some napkin math says that the number oslo bugs in lp minus oslo-incubator (it was concluded we didn't need to mi

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

+1 -Original Message- From: Tim Bell [mailto:tim.b...@cern.ch] Sent: Wednesday, September 26, 2018 1:56 PM To: OpenStack Development Mailing List (not for usage questions); openstack-operators; openstack-sigs Subject: Re: [Openstack-sigs] [openstack-dev] [goals][tc][ptl][uc] starting go

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

+1 :) From: Tim Bell [tim.b...@cern.ch] Sent: Wednesday, September 26, 2018 11:55 AM To: OpenStack Development Mailing List (not for usage questions); openstack-operators; openstack-sigs Subject: Re: [Openstack-sigs] [openstack-dev] [goals][tc][ptl][uc] sta

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

Doug, Thanks for raising this. I'd like to highlight the goal "Finish moving legacy python-*client CLIs to python-openstackclient" from the etherpad and propose this for a T/U series goal. To give it some context and the motivation: At CERN, we have more than 3000 users of the OpenStack cloud

Re: [openstack-dev] [storyboard][oslo] Fewer stories than bugs?

Ben Nemec writes: > Okay, I found a few bugs that are in launchpad but not storyboard: > > https://bugs.launchpad.net/python-stevedore/+bug/1784823 > https://bugs.launchpad.net/pbr/+bug/1777625 > https://bugs.launchpad.net/taskflow/+bug/1756520 > https://bugs.launchpad.net/pbr/+bug/1742809 > > Th

Re: [openstack-dev] [ptl][release] Proposed changes for cycle-with-milestones deliverables

Jeremy Stanley writes: > On 2018-09-26 09:22:30 -0500 (-0500), Sean McGinnis wrote: > [...] >> It tests the release automation machinery to identify problems >> before the RC and final release crunch time. > [...] > > More to the point, it helped spot changes to projects which made it > impossibl

Re: [openstack-dev] [cinder][glance][ironic][keystone][neutron][nova][edge] PTG summary on edge discussions

For those who may be following along and are not familiar with what we mean by federated auto-provisioning [0]. [0] https://docs.openstack.org/keystone/latest/advanced-topics/federation/federated_identity.html#auto-provisioning On Wed, Sep 26, 2018 at 9:06 AM Morgan Fainberg wrote: > This discu

Re: [openstack-dev] [cinder][glance][ironic][keystone][neutron][nova][edge] PTG summary on edge discussions

Hey Colleen, >This sounds like it is based on the customizations done at Oath, which to my recollection did not use the actual federation implementation in keystone due to its reliance on Athenz (I think?) as an identity manager. Something similar can be accomplished in standard keystone with the

Re: [openstack-dev] [storyboard][oslo] Fewer stories than bugs?

Okay, I found a few bugs that are in launchpad but not storyboard: https://bugs.launchpad.net/python-stevedore/+bug/1784823 https://bugs.launchpad.net/pbr/+bug/1777625 https://bugs.launchpad.net/taskflow/+bug/1756520 https://bugs.launchpad.net/pbr/+bug/1742809 The latter three are all in an inco

Re: [openstack-dev] [storyboard] Prioritization?

On 9/25/18 3:29 AM, Thierry Carrez wrote: Doug Hellmann wrote: I think we need to reconsider that position if it's going to block adoption. I think Ben's case is an excellent second example of where having a field to hold some sort of priority value would be useful. Absence of priorities was

[openstack-dev] Ryu integration with Openstack

Hello, I have a question regarding the Ryu integration in Openstack. By default, the openvswitch bridges (br-int, br-tun and br-ex) are registered to a controller running on 127.0.0.1 and port 6633. The output of ovs-vsctl get-manager is ptcp:127.0.0.1:6640. This is noticed on the nova compute nod

[openstack-dev] [tripleo] OVB 1.0 and Upcoming Changes

(this is a reprint of a blog post I just made. I'm sending it here explicitly too because most (maybe all) of the major users are here. See also http://blog.nemebean.com/content/ovb-10-and-upcoming-changes) The time has come to declare a 1.0 version for OVB. There are a couple of reasons for t

[openstack-dev] [Heat] Bug in documentation?

Hi everyone: I see that heat doc https://docs.openstack.org/heat/rocky/template_guide/openstack.html#OS::Nova ::Flavor states that ram ¶ Memory in MB for the flavor. disk

[openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

It's time to start thinking about community-wide goals for the T series. We use community-wide goals to achieve visible common changes, push for basic levels of consistency and user experience, and efficiently improve certain areas where technical debt payments have become too high - across all Op

[openstack-dev] [goal][python3] week 7 update

This is week 7 of the "Run under Python 3 by default" goal (https://governance.openstack.org/tc/goals/stein/python3-first.html). == Things We Learned This Week == When we updated the tox.ini settings for jobs like pep8 and release notes early in the Rocky session we only touched some of the offi

Re: [openstack-dev] [storyboard] why use different "bug" tags per project?

On 26/09/18 09:45 -0500, Ben Nemec wrote: On 9/26/18 8:20 AM, Jeremy Stanley wrote: On 2018-09-26 00:50:16 -0600 (-0600), Chris Friesen wrote: At the PTG, it was suggested that each project should tag their bugs with "-bug" to avoid tags being "leaked" across projects, or something like that.

[openstack-dev] [nova] review runways for Stein are open

Just wanted to remind everyone that review runways for Stein are OPEN. Please feel free to add your approved, ready-for-review blueprints to the queue: https://etherpad.openstack.org/p/nova-runways-stein Cheers, -melanie

Re: [openstack-dev] [docs] Nominating Ian Y. Choi for openstack-doc-core

On Sat, 22 Sep 2018 23:32:06 +0900 "Ian Y. Choi" wrote: > Thanks a lot all for such nomination & agreement! > > I would like to do my best after I become doc-core as like what I > current do, > although I still need the help from so many kind, energetic, and > enthusiastic OpenStack contributo

Re: [openstack-dev] [cinder][glance][ironic][keystone][neutron][nova][edge] PTG summary on edge discussions

hi, thanks for sharing this! At TripleO we're looking at implementing in Stein deployment of at least 1 regional DC and N edge zones. More comments below. On 9/25/18 11:21 AM, Ildiko Vancsa wrote: > Hi, > > Hereby I would like to give you a short summary on the discussions that happened at the P

Re: [openstack-dev] [storyboard] why use different "bug" tags per project?

On 9/26/18 8:20 AM, Jeremy Stanley wrote: On 2018-09-26 00:50:16 -0600 (-0600), Chris Friesen wrote: At the PTG, it was suggested that each project should tag their bugs with "-bug" to avoid tags being "leaked" across projects, or something like that. Could someone elaborate on why this was r

Re: [openstack-dev] [taas] rocky

Thanks Takashi On Wed, Sep 26, 2018 at 4:57 AM Takashi Yamamoto wrote: > hi, > > it seems we forgot to create rocky branch. > i'll make a release and the branch sooner or later, unless someone > beat me to do so. > > __ > Op

Re: [openstack-dev] [ptl][release] Proposed changes for cycle-with-milestones deliverables

On 2018-09-26 09:22:30 -0500 (-0500), Sean McGinnis wrote: [...] > It tests the release automation machinery to identify problems > before the RC and final release crunch time. [...] More to the point, it helped spot changes to projects which made it impossible to generate and publish their releas

[openstack-dev] [ptl][release] Proposed changes for cycle-with-milestones deliverables

During the Stein PTG in Denver, the release management team talked about ways we can make things simpler and reduce the "paper pushing" work that all teams need to do right now. One topic that came up was the usefulness of pushing tags around milestones during the cycle. There were a couple of nee

Re: [openstack-dev] [cinder][glance][ironic][keystone][neutron][nova][edge] PTG summary on edge discussions

This discussion was also not about user assigned IDs, but predictable IDs with the auto provisioning. We still want it to be something keystone controls (locally). It might be hash domain ID and value from assertion ( similar.to the LDAP user ID generator). As long as within an environment, the IDs

Re: [openstack-dev] [horizon] Horizon gates are broken

Hi all, Patch [1] is merged and our gates are un-blocked now. I went throw review list and post 'recheck' where it was needed. We need to cherry-pick this fix to stable releases too. I'll do it asap Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Mon, Sep 24, 2018 at 11:18 AM Ivan Kolody

Re: [openstack-dev] [storyboard] why use different "bug" tags per project?

On 2018-09-26 00:50:16 -0600 (-0600), Chris Friesen wrote: > At the PTG, it was suggested that each project should tag their bugs with > "-bug" to avoid tags being "leaked" across projects, or something > like that. > > Could someone elaborate on why this was recommended? It seems to me that > it

Re: [openstack-dev] [kolla] ceph osd deploy fails

Hi, what version of rocky are you using. Maybe was in the middle of a backport which temporally broke ceph. Could you try latest stable/rocky branch? It is now working properly. Regards On Wed, Sep 26, 2018, 2:32 PM Florian Engelmann < florian.engelm...@everyware.ch> wrote: > Hi, > > I tried t

Re: [openstack-dev] [storyboard] Prioritization?

On Wed, Sep 26, 2018 at 8:17 AM Adam Coldrick wrote: > On Tue, 2018-09-25 at 18:40 +, CARVER, PAUL wrote: > [...] > > There is certainly room for additional means of juggling and > > discussing/negotiating priorities in the stages before work really gets > > under way, but if it doesn't event

[openstack-dev] [kolla] ceph osd deploy fails

Hi, I tried to deploy Rocky in a multinode setup but ceph-osd fails with: failed: [xxx-poc2] (item=[0, {u'fs_uuid': u'', u'bs_wal_label': u'', u'external_journal': False, u'bs_blk_label': u'', u'bs_db_partition_num': u'', u'journal_device': u'', u'journal': u'', u'partition': u'/dev/

Re: [openstack-dev] [kolla] Proposing Chason Chan (chason) as kolla-ansible core

+1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [storyboard] Prioritization?

On Tue, 2018-09-25 at 18:40 +, CARVER, PAUL wrote: [...] > There is certainly room for additional means of juggling and > discussing/negotiating priorities in the stages before work really gets > under way, but if it doesn't eventually become clear > > 1) who's doing the work > 2) when are the

Re: [openstack-dev] [cinder][glance][ironic][keystone][neutron][nova][edge] PTG summary on edge discussions

On 09/26/2018 05:10 AM, Colleen Murphy wrote: Thanks for the summary, Ildiko. I have some questions inline. On Tue, Sep 25, 2018, at 11:23 AM, Ildiko Vancsa wrote: We agreed to prefer federation for Keystone and came up with two work items to cover missing functionality: * Keystone to trus

Re: [openstack-dev] RFC: Next minimum libvirt / QEMU versions for 'T' release

On Mon, Sep 24, 2018, at 3:22 PM, Kashyap Chamarthy wrote: > Hey folks, > > Before we bump the agreed upon[1] minimum versions for libvirt and QEMU > for 'Stein', we need to do the tedious work of picking the NEXT_MIN_* > versions for the 'T' (which is still in the naming phase) release, which > w

[openstack-dev] [mistral] Extend created(updated)_at by started(finished)_at to clarify the duration of the task

Hi everyone! Please take a look to the blueprint that i've just created https://blueprints.launchpad.net/mistral/+spec/mistral-add-started-finished-at I'd like to implement this feature, also I want to update CloudFlow when this will be done. Please let me know in the blueprint if I can start impl

Re: [openstack-dev] [kolla] Proposing Chason Chan (chason) as kolla-ansible core

+1 On Tue, Sep 25, 2018 at 9:17 PM Eduardo Gonzalez wrote: > Hi, > > I would like to propose Chason Chan to the kolla-ansible core team. > > Chason is been working on addition of Vitrage roles, rework VpnaaS > service, maintaining > documentation as well as fixing many bugs. > > Voting will be o

[openstack-dev] [all] Sphinx 'doctrees' bug recently resolved

FYI, Sphinx 1.8.0 contained a minor issue (introduced by yours truly) which resulted in an incorrect default doctree directory [1]. This would manifest itself in a 'docs/source/.doctree' directory being created and would only affects projects that call 'sphinx-build' from tox without specifying the

[openstack-dev] [taas] rocky

hi, it seems we forgot to create rocky branch. i'll make a release and the branch sooner or later, unless someone beat me to do so. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-re

Re: [openstack-dev] [storyboard] Prioritization?

On Tue, 2018-09-25 at 13:41 -0400, Doug Hellmann wrote: > Adam Coldrick writes: > > For tasks I am less concerned in that aspect since cross-project > > support > > isn't hurt, but remain of the opinion that a global field is the wrong > > approach since it means that only one person (or group of

Re: [openstack-dev] [cinder][glance][ironic][keystone][neutron][nova][edge] PTG summary on edge discussions

Thanks for the summary, Ildiko. I have some questions inline. On Tue, Sep 25, 2018, at 11:23 AM, Ildiko Vancsa wrote: > > We agreed to prefer federation for Keystone and came up with two work > items to cover missing functionality: > > * Keystone to trust a token from an ID Provider master a

Re: [openstack-dev] [kolla] Proposing Chason Chan (chason) as kolla-ansible core

+1 good job On Wed, Sep 26, 2018 at 9:30 AM zhubingbing wrote: > +1 > > > > > > At 2018-09-25 23:47:10, Eduardo Gonzalez wrote: > > Hi, > > I would like to propose Chason Chan to the kolla-ansible core team. > > Chason is been working on addition of Vitrage roles, rework VpnaaS > service, maint

[openstack-dev] [cyborg]zero tolerance policy on padding activities

Hi all, I want to emphasize the zero tolerance policy in cyborg project regarding padding activities. If you look at the gerrit record [0] you would probably got the idea: out of the 15 abandoned patches, only the ones from jiapei and shaohe were actually meant to do real fixing. We have #opensta

[openstack-dev] [watcher] weekly meeting

Greetings, We’ll have meeting today at 8:00 UTC on #openstack-meeting-3 channel. Best Regards, Alex __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?