February 2020 - openstack-discuss

[neutron][ironic][nova][routed_network] what's normal workflow when ironic host added to nova from neutron?
by 양유석 11 Feb '20

11 Feb '20

Hi stacker, I'm trying to use ironic routed network from stein. I do not sure how the normal workflow works in nova/neutron/ironic side for routed network, so I sent this mail to get more information. >From what I understand for ironic routed network, what I did - Enable segment plugin in Neutron - Add ironic 'node' - Add ironic port with physical network - network-baremetal plugin reports neutron from all ironic nodes. - It sent 'physical_network' and 'ironic node uuid' to Neutron - It make 'segmenthostmapping' entry with ('node uuid', 'segment_id') - Add segment for the subnet. At last step, I encountered the strange. In detail, - Neutron subnet update callback call nova inventory registration - Neutron ask placement to create resource provider for segment - Neutron ask nova to create aggregate for segment - Neutron request placement to associate nova aggregate to resource provider. - (Bug?) Neutron add hosts came from 'segmenthostmapping' to nova aggregate Since 'segmenthostmapping' has 'ironic node uuid' for host, nova deny to register the host to aggregate emitting the exception like below Returning 404 to user: Compute host 27004f76-2606-4e4a-980e-a385a01f04de could not be found. __call__ What's strange for me is why neutron ask 'ironic node uuid' for host when nova aggregate only look for host from HostMapping which came from 'host' in compute_nodes. I could not find the code related to how 'ironic node uuid' can be registered in nova aggregate. Please someone who knows what's going on shed light on me. Thanks.

2 4

[tripleo] rework of triple squads and the tripleo mtg.
by Wesley Hayutin 11 Feb '20

11 Feb '20

Greetings, As mentioned at the previous tripleo meeting [1], we're going to revisit the current tripleo squads and the expectations for those squads at the tripleo meeting. Currently we have the following squads.. 1. upgrades 2. edge 3. integration 4. validations 5. networking 6. transformation 7. ci A reasonable update could include the following.. 1. validations 2. transformation 3. mistral-to-ansible 4. CI 5. Ceph / Integration?? maybe just Ceph? 6. others?? The squads should reflect major current efforts by the TripleO team IMHO. For the meetings, I would propose we use this time and space to give context to current reviews in progress and solicit feedback. It's also a good time and space to discuss any upstream blockers for those reviews. Let's give this one week for comments etc.. Next week we'll update the etherpad list and squads. The etherpad list will be a decent way to communicate which reviews need attention. Thanks all!!! [1] http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-01-07-14.…

7 7

[infra][neutron] Removing networking-calico from OpenStack governance
by Neil Jerram 11 Feb '20

11 Feb '20

Hi all, networking-calico is the code that integrates Project Calico [1] with Neutron. It has been an OpenStack project for several years, but we, i.e. its developers [2], would like now to remove it from OpenStack governance and instead manage it like the other Project Calico projects under https://github.com/projectcalico/. In case anyone has any concerns about this, please let me know very soon! Please could infra folk confirm that https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project is the correct procedure for winding up the OpenStack side of this transition? Many thanks, Neil [1] https://www.projectcalico.org/ [2] That means mostly me, with some help from my colleagues here at Tigera. We do have some other contributors but I will take care that they are also on board with this change.

3 6

UC Elections Reminder
by Amy Marrich 11 Feb '20

11 Feb '20

Hey All! Just a reminder that the nomination period for the upcoming User Committee elections is open. See the original email below! Thanks, Amy (spotz) The nomination period for the February User Committee elections is now open. Any individual member of the Foundation who is an Active User Contributor (AUC) can propose their candidacy (except the two sitting UC members elected in the previous election). Self-nomination is common; no third party nomination is required. Nominations can be made by sending an email to the user-committee(a)lists.openstack.org mailing-list[0], with the subject: “UC candidacy” by February 16, 23:59 UTC aa voting will begin on February 17. The email can include a description of the candidate platform. The candidacy is then confirmed by one of the election officials, after verification of the electorate status of the candidate. Criteria for AUC status can be found at https://superuser.openstack.org/articles/auc-community/. If you are still not sure of your status and would like to verify in advance please email myself(amy(a)demarco.com) and Rain Leander(rleander(a)redhat.com) as we are serving as the Election Officials. Thanks, Amy Marrich (spotz) 0 - Please make sure you are subscribed to this list before sending in your nomination.

1 0

Nominating Maysa De Macedo Souza for kuryr-kubernetes core
by mdulko＠redhat.com 11 Feb '20

11 Feb '20

Hi, I'd like to nominate Maysa to be core reviewer in Kuryr-Kubernetes project. Maysa shown numerous examples of diligent and valuable work in terms of code contribution (e.g. in network policy support), project maintenance and reviews [1]. Please express support or objections by replying to this email. Assuming that there will be no pushback, I'll proceed with granting Maysa core powers by the end of this week. Thanks, Michał [1] https://www.stackalytics.com/?module=kuryr-kubernetes&release=ussuri

3 3

[oslo] PTG Attendance
by Ben Nemec 11 Feb '20

11 Feb '20

Hi, As discussed in the meeting this morning, we need to decide if we want to request a room at the Vancouver PTG. Since I'm not expecting to be there this time someone else would need to organize it. I realize travel plans are not finalized for most people, but if you expect to be there and would like to have formal Oslo discussions please let me know ASAP. Thanks. -Ben

1 0

[neutron] Bug deputy report Feb 3-10
by Nate Johnston 11 Feb '20

11 Feb '20

Nate bug deputy notes - 2020-02-03 to 2020-02-10 ------------------------------------------------ It was a very quiet week - almost half of these were filed today, this report was looking very short as recently as yesterday. Thanks to amotoki for the next shift as bug deputy. Untriaged: - "Neutron try to register invalid host to nova aggregate for ironic routed network" * URL: https://bugs.launchpad.net/bugs/1862611 * Version: stable/stein * lajoskatona responded to the bug but I was not able to reproduce it; I don't have an ironic setup to verify the bug report. Critical: - "Neutron incorrectly selects subnet" * URL: https://bugs.launchpad.net/bugs/1862374 * Marked Incomplete by haleyb but there is still a significant chance there is a real issue here, it might just be in the SDK as opposed to neutron. Waiting for reported to respond. High: - "Fullstack tests failing due to "hang" neutron-server process" (slaweq) * URL: https://bugs.launchpad.net/bugs/1862178 * Unassigned - "Fullstack tests failing due to problem with connection to the fake placement service" * URL: https://bugs.launchpad.net/bugs/1862177 * Assigned: lajoskatona * Fix proposed: https://review.opendev.org/706500 - "Sometimes VMs can't get IP when spawned concurrently" * URL: https://bugs.launchpad.net/bugs/1862315 * Version: stable/stein * Assigned: obondarev - "[OVN] Reduce the number of tables watched by MetadataProxyHandler" * URL: https://bugs.launchpad.net/bugs/1862648 * Assigned: lucasgomes Medium: - "[OVN] functional test test_virtual_port_delete_parents is unstable" * URL: https://bugs.launchpad.net/bugs/1862618 * Assigned: sapana45 Invalid: - "placement in neutron_lib could not process keystone exceptions" * URL: https://bugs.launchpad.net/bugs/1862565 * Marked as duplicate of https://bugs.launchpad.net/neutron/+bug/1828543 (lajoskatona) RFE: - "Add RBAC for subnet pools" * URL: https://bugs.launchpad.net/bugs/1862032 * Cross-project with the nova team, nova has a patch up for their part. Last week's report by tidwellr: http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012332…

1 0

Re: [Release-job-failures] release-post job for openstack/releases for ref refs/heads/master failed
by Sean McGinnis 11 Feb '20

11 Feb '20

On 2/10/20 9:08 AM, zuul(a)openstack.org wrote: > Build failed. > > - tag-releases https://zuul.opendev.org/t/openstack/build/8796e6c046a84688b3dd9dc756f4a15d : FAILURE in 6m 13s > - publish-tox-docs-static https://zuul.opendev.org/t/openstack/build/None : SKIPPED > > _______________________________________________ > Release-job-failures mailing list > Release-job-failures(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures This failure was actually on the removal of a deliverable file for something that is no longer active. This can be safely ignored. Sean

1 0

[neutron] 11.02.2020 team meeting cancelled
by Slawek Kaplonski 10 Feb '20

10 Feb '20

Hi, I will not be able to chair our tomorrow’s team meeting. So lets cancel it and see You all on Monday 17.02.2020. — Slawek Kaplonski Senior software engineer Red Hat

1 0

[largescale-sig] Next meeting: Feb 12, 9utc
by Thierry Carrez 10 Feb '20

10 Feb '20

Hi everyone, The Large Scale SIG will have a meeting this week on Wednesday, Feb 12 at 9 UTC[1] in #openstack-meeting on IRC: [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200212T09 As always, the agenda for our meeting is available at: https://etherpad.openstack.org/p/large-scale-sig-meeting Feel free to add topics to it. We'll start with a show-and-tell by Stig (oneswig), followed by a status update on the various TODOs we had from last meeting, in particular: - Reviewing oslo.metrics draft at https://review.opendev.org/#/c/704733/ and comment so that we can iterate on it - Reading page on golden signals at https://landing.google.com/sre/sre-book/chapters/monitoring-distributed-sys… Talk to you all on Wednesday, -- Thierry Carrez

1 0

[heat][tacker] After Stack is Created, will it change nested stack Id?
by Patil, Tushar 10 Feb '20

10 Feb '20

Hi All, In tacker project, we are using heat API to create stack. Consider a case where we want to add OS::Heat::AutoScalingGroup in which there are two servers and the desired capacity is set to 2. So internally heat will create two nested stacks and add following resources to it:- child stack1 VDU1 - OS::Nova::Server CP1 - OS::Neutron::Port VDU2 - OS::Nova::Server CP2- OS::Neutron::Port child stack2 VDU1 - OS::Nova::Server CP1 - OS::Neutron::Port VDU2 - OS::Nova::Server CP2- OS::Neutron::Port Now, as part of tacker heal API, we want to heal VDU1 from child stack2. To do this, we will mark the status of the resources from "child stack2" as unhealthy and then update "child stack2" stack. Since VDU1 resource is present in the two nested stacks, I want to keep the nested stack id information in tacker so that after the stack is updated, I can pull physical resource id of the resources from the nested child stack directly. My question is after the stack is created for the first time, will it ever change the nested child stack id? Thank you. Regards, tpatil Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.

2 2

[goals][Drop Python 2.7 Support] Week R-14 Update (1 week left to complete)
by Ghanshyam Mann 10 Feb '20

10 Feb '20

Hello Everyone, Below is the progress on "Drop Python 2.7 Support" at end of R-14 week. Schedule: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html#sc… Highlights: ======== * 1 week left to finish the work. * This week was very dramatic and full of failure as expected or more than that :). ** With that, I am expecting more issues to occur, dropping py2 from every repo asap is suggested so that we can stabilize the things well before m-3. * Do not worry about the gate failure, it is better to break it now and fix so that we can smoothly release Ussuri. * Oslo dropped the py2, which caused multiple failures on 1. tempest testing on stable branches 2. projects still running py2 jobs on the master. ** we did not opt to cap the oslo lib for <py3.6 and decided to fix the issue instead. **1. Tempest testing is fixed and stable branches gate is green now. **2. TripleO was one project that failed for this and py2 jobs are dropped now. If any project facing the same issue and waiting for some general fix, need to drop py2 job asap. * Bugs & Issues: ** Stable/ocata|pike|queens|rocky gate is up now. u-c issue on pinned Tempest is resolved now[1] *** http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012462… ** Nova stable branches are still falling for the u-c reason on nova-live-migration. Fixes are up[2] * * Tempest tox 'all-plugin' usage issue[3] *** designate stable branches fixes are up. If any project job faces the same issue, you can apply the same fix.[4] ** neutron-vpass in-tree plugin issue *** slaweq, amotoki and I are discussing the best possible fix. NOTE: I know few py2.7 drop patches are failing on few projects, I will continue debugging those. Help from the failing project will be greatly appreciated to meet the deadline. Project wise status and need reviews: ============================ Phase-1 status: The OpenStack services have not merged the py2 drop patches: NOTE: This was supposed to be completed by milestone-1 (Dec 13th, 19). * Adjutant * Masakari * Qinling Phase-2 status: This is ongoing work and I think most of the repo have patches up to review. Try to review them on priority. If any query and I missed to respond on review, feel free to ping me in irc. * Open review: https://review.opendev.org/#/q/topic:drop-py27-support+status:open How you can help: ============== - Review the patches. Push the patches if I missed any repo. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012463… [2] https://review.opendev.org/#/q/I8190f93e0a754fa59ed848a3a230d1ef63a06abc [3] https://bugs.launchpad.net/tempest/+bug/1862240 [4] https://review.opendev.org/#/q/topic:bug/1862240+(status:open+OR+status:mer… -gmann

1 0

openstack-dpdk installation
by mesut aygün 10 Feb '20

10 Feb '20

Hey, I am working over dpdk installation with openstack ocata release. How can I use the neutron-openvswitch-agent-dpdk or anything else instead of neutron-openvswitch-agent? Which can I choose the correct packages with os dpdk versions? I couldn't use the devstack versions!! Best regards

2 3

[nova] nova stable pike|queens|rocky is still failing on Tempest u-c: Do not recheck
by Ghanshyam Mann 10 Feb '20

10 Feb '20

After fixing the stable/pike|queens|rocky integrated jobs[1], on using the stable u-c for pinned Tempest run, nova-live-migration fail on these stable branch on nova. I have proposed the fixes[2], wait for recheck till those are merged. [1] https://review.opendev.org/#/q/topic:fix-stable-gate+status:merged [2] https://review.opendev.org/#/q/topic:fix-stable-gate+status:open+projects:o… -gmann

1 0

[qa][stable][tempest-plugins]: Tempest & plugins py2 jobs failure for stable branches (1860033: the EOLing python2 drama)
by Ghanshyam Mann 09 Feb '20

09 Feb '20

Hello Everyone, This is regarding bug: https://bugs.launchpad.net/tempest/+bug/1860033. Using Radosław's fancy statement of 'EOLing python2 drama' in subject :). neutron tempest plugin job on stable/rocky started failing as neutron-lib dropped the py2. neutron-lib 2.0.0 is py3 only and so does u-c on the master has been updated to 2.0.0. All tempest and its plugin uses the master u-c for stable branch testing which is the valid way because of master Tempest & plugin is being used to test the stable branches which need u-c from master itself. These failed jobs also used master u-c[1] which is trying to install the latest neutron-lib and failing. This is not just neutron tempest plugin issue but for all Tempest plugins jobs. Any lib used by Tempest or plugins can drop the py2 now and leads to this failure. Its just neutron-lib raised the flag first before I plan to hack on Tempest & plugins jobs for py2 drop from master and kepe testing py2 on stable bracnhes. We have two way to fix this: 1. Separate out the testing of python2 jobs with python2 supported version of Tempest plugins and with respective u-c. For example, test all python2 job with tempest plugin train version (or any latest version if any which support py2) and use u-c from stable/train. This will cap the Tempest & plugins with respective u-c for stable branches testing. 2. Second option is to install the tempest and plugins in py3 env on py2 jobs also. This should be an easy and preferred way. I am trying this first[2] and testing[3]. [1] https://zuul.opendev.org/t/openstack/build/fb8a928ed3614e09a9a3cf4637f2f6c2… [2] https://review.opendev.org/#/c/703011/ [3] https://review.opendev.org/#/c/703012/ -gmanne

5 17

[all] Gate status: Stable/ocata|pike|queens|rocky is broken: Avoid recheck
by Ghanshyam Mann 09 Feb '20

09 Feb '20

Hello Everyone, Stable/ocata, pike, queens, rocky gate is broken now due to Temepst dependency require >=py3.6. I summarized the situation in ML[1]. Do not recheck on failed patches of those branches until the job is explicitly disabling Tempest. Fixes are in progress, I will update the status here once fixes are merged. [1]http://lists.openstack.org/pipermail/openstack-discuss/2020-February/0123… -gmann

1 1

Regarding OpenStack
by HARISH KUMAR Ivaturi 09 Feb '20

09 Feb '20

Hi I am Harish Kumar, Master Student at BTH, Karlskrona, Sweden. I have started my Master thesis at BTH and my thesis topic is Performance evaluation of OpenStack with HTTP/3. My solutions will take some time (few months) and i would like to request you that could you add me as a contributor to your github repository , so after completing my thesis i could push my codes in that repository. You can contact me for further details. Thanks and Regards Harish Kumar

2 1

[cinder][nova] volume-local-cache meeting day/time set
by Brian Rosmaita 09 Feb '20

09 Feb '20

I picked the day/time with the most votes (9/10, sorry Rajat), but as gibi pointed out in the other thread, it may not have been obvious what you actually voted for. The good news is that the selected day is late in the week, so if you look at this time and say WTF?, let me know and we can scramble to try to find another day/time (though hopefully not--we're trying to find a time that works stretching from Minneapolis to Shanghai). Meeting time: 13:30-14:00 UTC Thursday 13 February 2020 Location: https://bluejeans.com/3228528973 Topic: volume-local-cache specs: cinder: https://review.opendev.org/#/c/684556/ nova: https://review.opendev.org/#/c/689070/ Etherpad: https://etherpad.openstack.org/p/volume-local-cache The meeting will be recorded. Feel free to leave comments on the etherpad if you can't make it but want something addressed. cheers, brian

2 1

[cinder][nova] volume-local-cache proposal cross-project meeting
by Brian Rosmaita 09 Feb '20

09 Feb '20

Liang Fang's volume-local-cache spec has gotten stuck because the Cinder team doesn't want to approve something that won't get approved on the Nova side and vice-versa. We discussed the spec at this week's Cinder meeting and there's sufficient interest to continue with it. In order to keep things moving along, we'd like to have a cross-project video conference next week instead of waiting for the PTG. I think we can get everything covered in a half-hour. I've put together a doodle poll to find a reasonable day and time: https://doodle.com/poll/w8ttitucgyqwe5yc Please take the poll before 17:00 UTC on Saturday 8 February. I'll send out an announcement shortly after that letting you know what time's been selected. I'll send out connection info once the meeting's been set. The meeting will be recorded and interested parties who can't make it can always leave notes on the discussion etherpad. Info: - cinder spec: https://review.opendev.org/#/c/684556/ - nova spec: https://review.opendev.org/#/c/689070/ - etherpad: https://etherpad.openstack.org/p/volume-local-cache cheers, brian

2 2

[Queens][neutron] multiple networks with same vlan id
by Ignazio Cassano 09 Feb '20

09 Feb '20

Hello, I trying to create multiple networks with the same vlan id and different address but it is impossibile because neutron returns vlan id is already present. I tried with success on vcenter and it works. On openstack I can create more subnets with different adresses under the same vlan id, but instances receive static routes from dhcp for all subnets. Any workaround ? I am also trying with segments but they do not seem to fit my case. Regards Ignazio

4 5

[quuens] neutron vxlan to vxlan
by Ignazio Cassano 09 Feb '20

09 Feb '20

Hello, I have an openstack installation and a vcenter installation with nsxv. Vcenter is not under openstack Any solution for vxlan to vxlan communication between them? Regards Ignazio

2 2

Re: [Release-job-failures] Release of openstack/mox3 for ref refs/tags/1.0.0 failed
by Sean McGinnis 07 Feb '20

07 Feb '20

On Fri, Feb 07, 2020 at 01:16:38PM +0000, zuul(a)openstack.org wrote: > Build failed. > > - release-openstack-python https://zuul.opendev.org/t/openstack/build/720dc1833f464e2db76b90d1c8437883 : SUCCESS in 3m 48s > - announce-release https://zuul.opendev.org/t/openstack/build/d85b18ed6e2a47f98e96c1ad168ae98a : FAILURE in 4m 00s > - propose-update-constraints https://zuul.opendev.org/t/openstack/build/c2abc022840846c7a87b5804580492ee : SUCCESS in 3m 51s > > _______________________________________________ > Release-job-failures mailing list > Release-job-failures(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures There was a temporary SMTP failure in sending the release announcement for mox3. All other release activities were successful, so I think this error can safely be ignored. Sean

1 0

[all] Nominations for the "W" release name
by Sean McGinnis 07 Feb '20

07 Feb '20

Hello all, We get to be a little proactive this time around and get the release name chosen for the "W" release. Time to start thinking of good names again! Process Changes --------------- There are a couple of changes to be aware of with our naming process. In the past, we had always based our naming criteria on something geographically local to the Summit location. With the event changes to no longer have two large Summit-type events per year, we have tweaked our process to open things up and make it hopefully a little easier to pick a good name that the community likes. There are a couple of significant changes. First, names can now be proposed for anything that starts with the appropriate letter. It is no longer tied to a specific geographic region. Second, in order to simplify the process, the electorate for the poll will be the OpenStack Technical Committee. Full details of the release naming process can be found here: https://governance.openstack.org/tc/reference/release-naming.html Name Selection -------------- With that, the nomination period for the "W" release name is now open. Please add suitable names to: https://wiki.openstack.org/wiki/Release_Naming/W_Proposals We will accept nominations until February 7, 202 at 23:59:59 UTC. We will then have a brief period for any necessary discussions and to get the poll set up, with the TC electorate voting starting by February 17, 2020 and going no longer than February 23, 2020. Based on past timing with trademark and copyright reviews, we will likely have an official release name by mid to late March. Happy naming! Sean

2 2

[Neutron][segments]
by Ignazio Cassano 07 Feb '20

07 Feb '20

Hello, I am reading about openstack neutron routed provider networks. If I understood well, using segments I can create more subnets within the same provider net vlan id. Correct? In documentation seems I must use different physical network for each segment. I am using only one physical network ...in other words I created an openvswitch with a bridge (br-ex) with an interface on which I receive all my vlans (trunk). Why must I use different physical net? Sorry, but my net skill is poor. Ignazio

2 2

[keystone] Keystone Team Update - Week of 3 February 2020
by Vishakha Agarwal 07 Feb '20

07 Feb '20

# Keystone Team Update - Week of 3 February 2020 ## News ### User Support and Bug Duty Every week the duty is being rotated between the members. The person-in-charge for bug duty for current and upcoming week can be seen on the etherpad [1] [1] https://etherpad.openstack.org/p/keystone-l1-duty ## Open Specs Ussuri specs: https://bit.ly/2XDdpkU Ongoing specs: https://bit.ly/2OyDLTh ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 13 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 27 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ### Priority Reviews * Ussuri Roadmap Stories - Groups in keystone SAML assertion https://tree.taiga.io/project/keystone-ussuri-roadmap/us/33 https://review.opendev.org/#/c/588211/ Add openstack_groups to assertion - Add support for modifying resource options to CLI tool https://tree.taiga.io/project/keystone-ussuri-roadmap/us/53 https://review.opendev.org/#/c/697444/ Adding options to user cli * Special Requests https://review.opendev.org/#/c/705887/ Drop py3.5 from tempest plugins ## Bugs This week we opened 2 new bugs and closed 3. Bugs opened (2) Bug #1861695 (keystoneauth:Undecided): Programming error choosing an endpoint. - Opened by Raphaël Droz https://bugs.launchpad.net/keystoneauth/+bug/1861695 Bug #1862035 (keystoneauth:Undecided): Make possible to pass TCP_USER_TIMEOUT in keystoneauth1 session - Opened by Anton Kurbatov https://bugs.launchpad.net/keystoneauth/+bug/1862035 Bugs closed (3) Bug #1756190 (python-keystoneclient:Undecided) https://bugs.launchpad.net/python-keystoneclient/+bug/1756190 Bug #1853839 (python-keystoneclient:Undecided) https://bugs.launchpad.net/python-keystoneclient/+bug/1853839 Bug #1856286 (python-keystoneclient:Undecided) https://bugs.launchpad.net/python-keystoneclient/+bug/1856286 ## Milestone Outlook https://releases.openstack.org/ussuri/schedule.html Next week is spec freeze. One month from now is feature proposal freeze, by which point all code for new features should be proposed and ready for review - no WIPs. This will give us 4 weeks to review. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0