June 2019 - openstack-discuss - lists.openstack.org

[nova] 'pre-commit' integration
by Stephen Finucane 15 Jun '19

15 Jun '19

This is a heads up that I've proposed a patch to integrate [1] to add support for the 'pre-commit' tool [2] in nova. As noted in that change, this provides a faster, most automated alternative to the 'fast8' tox target we currently use for validating recently changed code. While this is opt-in, I'm also proposing deprecating the 'fast8' behavior since I don't think it's necessary with pre-commit support. As a result, it would be good if anyone that has an opinion on the matter took a look at the change. Have a good weekend, Stephen [1] https://review.opendev.org/665518 [2] https://pre-commit.com/

1 0

Are most grenade plugin projects doing upgrades wrong?
by Matt Riedemann 14 Jun '19

14 Jun '19

While fixing how the watcher grenade plugin is cloning the watcher repo for the base (old) side [1] to hard-code from stable/rocky to stable/stien, I noticed that several other projects with grenade plugins aren't actually setting a stable branch when cloning the plugin for the old side [2]. So I tried removing the stable/stein branch from the base plugin clone in watcher [3] and grenade cloned from master for the base (old) side [4]. Taking designate as an example, I see the same thing happening for it's grenade run [5]. Is there something I'm missing here or are most of the openstack projects running grenade via plugin actually just upgrading from master to master rather than n-1 to master? [1] https://review.opendev.org/#/c/664610/1/devstack/upgrade/settings [2] http://codesearch.openstack.org/?q=base%20enable_plugin&i=nope&files=&repos= [3] https://review.opendev.org/#/c/664610/2/devstack/upgrade/settings [4] http://logs.openstack.org/10/664610/2/check/watcher-grenade/ad2e068/logs/gr… [5] http://logs.openstack.org/47/662647/6/check/designate-grenade-pdns4/0b8968f… -- Thanks, Matt

3 2

[placement] update 19-23
by Chris Dent 14 Jun '19

14 Jun '19

HTML: https://anticdent.org/placement-update-19-23.html 19-23. I'll be travelling the end of next week so there will be no 19-24. # Most Important We keep having interesting and helpful, but not yet fully conclusive, discussions related to the [spec for nested magic](https://review.opendev.org/662191). The discussion on the spec links back to a few different IRC discussions. Part of the reason this drags on so much is that we're trying to find a model that is internally consistent in placement and generally applicable while satisfying the NUMA requirements from Nova, while not requiring either Placement or Nova to bend over backwards to get things right, and while not imposing additional complexity on simple requests. (And probably a few other whiles...) If you have thoughts on these sorts of things, join that review. In the meantime there are plenty of other things to review (below). # What's Changed * A blocker migration for incomplete consumers has been added, and the inline migrations that would guard against the incompleteness have been removed. * CORS configuration and use in Placement has been modernized and corrected. You can now, if you want, talk to Placement from JavaScript in your browser. (This was a bug I found while working on a [visualisation toy](https://github.com/cdent/placeview) with a friend.) * Result sets for certain nested provider requests could return different results in Python versions 2 and 3. This has [been fixed](https://review.opendev.org/663137). * That ^ work was the result of working on implementing [mappings in allocations](https://docs.openstack.org/placement/latest/specs/train/approv… which has [merged today as microversion 1.34](https://docs.openstack.org/placement/latest/placement-api-microversio… # Specs/Features * <https://review.opendev.org/654799> Support Consumer Types. This has some open questions that need to be addressed, but we're still go on the general idea. * <https://review.opendev.org/662191> Spec for nested magic 1. The easier parts of nested magic: same_subtree, resourceless request groups, verbose suffixes (already merged as 1.33). See "Most Important" above. Some non-placement specs are listed in the Other section below. # Stories/Bugs (Numbers in () are the change since the last pupdate.) There are 20 (0) stories in [the placement group](https://storyboard.openstack.org/#!/project_group/placement). 0 (0) are [untagged](https://storyboard.openstack.org/#!/worklist/580). 3 (0) are [bugs](https://storyboard.openstack.org/#!/worklist/574). 6 (2) are [cleanups](https://storyboard.openstack.org/#!/worklist/575). 11 (0) are [rfes](https://storyboard.openstack.org/#!/worklist/594). 2 (0) are [docs](https://storyboard.openstack.org/#!/worklist/637). If you're interested in helping out with placement, those stories are good places to look. * Placement related nova [bugs not yet in progress](https://goo.gl/TgiPXb) on launchpad: 16 (1). * Placement related nova [in progress bugs](https://goo.gl/vzGGDQ) on launchpad: 6 (-1). [1832814: Placement API appears to have issues when compute host replaced](https://bugs.launchpad.net/nova/+bug/1832814) is an interesting bug. In a switch from RDO to OSA, resource providers are being duplicated because of a change in node name. # osc-placement osc-placement is currently behind by 11 microversions. There are no changes that have had attention in less than 4 weeks. There are 4 other changes. # Main Themes ## Nested Magic The overview of the features encapsulated by the term "nested magic" are in a [story](https://storyboard.openstack.org/#!/story/2005575) and [spec](https://review.opendev.org/662191). There is some in progress code, mostly WIPs to expose issues and think about how things ought to work: * <https://review.opendev.org/663009> PoC: resourceless request, including some code from <https://review.opendev.org/657510> WIP: Allow RequestGroups without resources ## Consumer Types Adding a type to consumers will allow them to be grouped for various purposes, including quota accounting. A [spec](https://review.opendev.org/654799) has started. There are some questions about request and response details that need to be resolved, but the overall concept is sound. ## Cleanup We continue to do cleanup work to lay in reasonable foundations for the nested work above. As a nice bonus, we keep eking out additional performance gains too. There are two new stories about some minor performance degradations: * <https://storyboard.openstack.org/#!/story/2005888> GET /allocations/{non existent consumer} slower than expected * <https://storyboard.openstack.org/#!/story/2005889> Allocation mappings have introduced a slight performance reduction Gibi discovered that osprofiler wasn't working with placement and then fixed it: * <https://review.opendev.org/663945> Add support for osprofiler in wsgi Thanks to Ed Leafe for his report on the [state of graph database work](http://lists.openstack.org/pipermail/openstack-discuss/2019-June/0070…. # Other Placement Miscellaneous changes can be found in [the usual place](https://review.opendev.org/#/q/project:openstack/placement+status:op…. There are three [os-traits changes](https://review.opendev.org/#/q/project:openstack/os-traits+status:… being discussed. And one [os-resource-classes change](https://review.opendev.org/#/q/project:openstack/os-resource-classe…. # Other Service Users New discoveries are added to the end. Merged stuff is removed. Anything that has had no activity in 4 weeks has been removed. * <https://review.openstack.org/601596> Nova: spec: support virtual persistent memory * <https://review.openstack.org/#/q/topic:bug/1819923> Nova: nova-manage: heal port allocations * <https://review.openstack.org/650188> nova-spec: Allow compute nodes to use DISK_GB from shared storage RP * <https://review.opendev.org/659233> Cyborg: Placement report * <https://review.opendev.org/657801> rpm-packaging: placement service * <https://review.opendev.org/657016> Delete resource providers for all nodes when deleting compute service * <https://review.opendev.org/654066> nova test and fix for: Drop source node allocations if finish_resize fails * <https://review.opendev.org/656885> nova: WIP: Hey let's support routed networks y'all! * <https://review.opendev.org/662371> starlingx: Add placement chart patch to openstack-helm * <https://review.opendev.org/662229> helm: WIP: add placement chart * <https://review.opendev.org/662164> kolla-ansible: Add a explanatory note for "placement_api_port" * <https://review.opendev.org/656023> Nova: Use OpenStack SDK for placement * <https://review.opendev.org/612497> Nova: Spec: Provider config YAML file * <https://review.opendev.org/623558> Nova: single pass instance info fetch in host manager * <https://review.opendev.org/663478> docs: Add Placement service to Minimal deployment for Stein * <https://review.opendev.org/663270> devstack: Add setting of placement microversion on tempest conf * <https://review.opendev.org/634551> libvirt: report pmem namespaces resources by provider tree * <https://review.opendev.org/660852> Nova: Remove PlacementAPIConnectFailure handling from AggregateAPI * <https://review.opendev.org/661237> Nova: Validate requested host/node during servers create * <https://review.opendev.org/#/q/topic:bp/support-move-ops-with-qos-ports> Nova: support move ops with qos ports * <https://review.opendev.org/664631> Kolla-ansible: Fix placement log perms in config.json * <https://review.opendev.org/665168> TripleO: Enable Request Filter for Image Types * <https://review.opendev.org/663979> Neutron: Force segments to use placement 1.1 * <https://review.opendev.org/664689> Nova: get_ksa_adapter: nix by-service-type confgrp hack * <https://review.opendev.org/664862> OSA: Add nova placement to placement migration # End If you, like me, use this collection of information to drive what to do early in the next week, you might like [placement-reviewme](https://github.com/cdent/placement-reviewme) which brute force loads all the links from the HTML version of this in tabs in your browser. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent

1 0

[requirements][kuryr][flame] openshift dificulties
by Matthew Thode 14 Jun '19

14 Jun '19

Openshift upstream is giving us difficulty as they are capping the version of urllib3 and kubernetes we are using. -urllib3===1.25.3 +urllib3===1.24.3 -kubernetes===9.0.0 +kubernetes===8.0.1 I've opened an issue with them but not had much luck there (and their prefered solution just pushes the can down the road). https://github.com/openshift/openshift-restclient-python/issues/289 What I'd us to do is move off of openshift as our usage doesn't seem too much. openstack/kuryr-tempest-plugin uses it for one import (and just one function with that import). I'm not sure exactly what you are doing with it but would it be too much to ask to move to something else? x/flame has it in it's constraints but I don't see any actual usage, so perhaps it's a false flag. Please let me know what you think -- Matthew Thode

3 7

[charms] Proposing Sahid Orentino Ferdjaoui to the Charms core team
by Chris MacNaughton 14 Jun '19

14 Jun '19

Hello all, I would like to propose Sahid Orentino Ferdjaoui as a member of the Charms core team. Chris MacNaughton

5 4

Retiring TripleO-UI - no longer supported
by Jason Rist 13 Jun '19

13 Jun '19

Hi everyone - I’m writing the list to announce that we are retiring TripleO-UI and it will no longer be supported. It’s already deprecated in Zuul and removed from requirements, so I’ve submitted a patch to remove all code. https://review.opendev.org/661113 Thanks, Jason Jason Rist Red Hat <https://www.redhat.com/> jrist / knowncitizen <https://www.redhat.com/>`

3 7

[nova] Help wanted with bug triage!
by Eric Fried 13 Jun '19

13 Jun '19

Folks- Nova's queue of untriaged bugs [1] has been creeping slowly upward lately. We could really use some focused effort to get this back under control. We're not even (necessarily) talking about *fixing* bugs - though that's great too. We're talking about triaging [2]. If every nova contributor (you don't need to be a core) triaged just one bug a day, it wouldn't take long for things to be back in manageable territory. Thanks in advance. efried [1] https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New [2] https://wiki.openstack.org/wiki/Nova/BugTriage

1 0

Re: [tc] Recap for Technical Committee Meeting 6 June 2019 @ 1400 UTC
by Alexandra Settle 13 Jun '19

13 Jun '19

Hi Alan, Thanks for your response :) I hope you don't mind, I'm replying back to you and the openstack-discuss list so the other TC members also working on the Help Most Wanted text can review your thoughts. In the etherpad, you can just start writing and it will give you an individual colour assigned to your user. If you feel like we won't see/know who you are, just put your initials next to your comments :) Thanks so much for offering to help. I've transferred over your thoughts below into the etherpad for now. Thanks, Alex On 13/06/2019 00:14, Alan Clark wrote: > Hey Alexandra, > > As I mentioned during the TC meeting I would love to help with the "Help Most Wanted" text. > > I took a look at the etherpad for the documentation role [1] > > I would like to offer a couple suggested changes. I wasn't sure where to post them, so am pinging you directly. > > My first comment is around the audience. Who is most likely to fit and fill this role. I think the audience we are after for this posting are those that take the OpenStack documentation to develop for re-use and distribution. Those are the most likely persons to convince to take a higher contribution and leadership role. Which is what this posting targets. > > The opening description section conveys the documentation teams pain and struggles. I think a more effective opening would be to convey the business and personal benefits the audience gains from contributing. They have to sell this to their boss. Boss wants to solve their pain not the documentation teams. If we agree that the most likely audience to contribute in this posted role, then their benefits are more complete documentation with less effort. Being able to leverage and re-use the community contributed text means much less text that the audience person has to write. Helping the community effort helps steer the contributed text to fill the needs and gaps that you find of most need. The first paragraph starts in the right direction but I suggest replacing the second paragraph with these ideas. I’m sure you can elaborate these ideas better than me. > > My second thought is that this posting should convey that it’s easy to do and get started. In fact you could turn it into an FAQ style. The First timers page is full of great material and a good page to point to: https://docs.openstack.org/doc-contrib-guide/quickstart/first-timers.html > Address the question of how easy it is to get started, that they use the tools they commonly use and here’s where to get their questions and concerns answered. > > Thanks, > AlanClark > > [1] https://etherpad.openstack.org/p/2019-upstream-investment-opportunities-ref… > > > > > >> -----Original Message----- >> From: Alexandra Settle [mailto:a.settle@outlook.com] >> Sent: Thursday, June 06, 2019 9:51 AM >> To: openstack-discuss(a)lists.openstack.org >> Subject: [tc] Recap for Technical Committee Meeting 6 June 2019 @ 1400 UTC >> >> Hello all, >> >> Thanks to those who joined the TC meeting today and running through it with me >> at the speed of light. Gif game was impeccably strong and that's primarily what I >> like about this community. >> >> For a recap of the meeting, please see the eavesdrop [0] for full detailed logs and >> action items. All items in the agenda [1] were covered and no major concerns >> raised. >> >> Next meeting will be on the 8th of July 2019. >> >> Cheers, >> >> Alex >> >> [0] http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-06-06-14.00.txt >> >> [1] >> http://lists.openstack.org/pipermail/openstack-discuss/2019-June/006877.html >> >> >

1 0

[openstack-helm] custom container images for helm
by Robson Ramos Barreto 13 Jun '19

13 Jun '19

Hi all I saw in the docker hub that there is just until rocky ubuntu xenial version. I'd like to know how can I create my own images centos-based from new versions like Stein to be used with the helm charts, if is there any specific customization to works with helm or, for example, if can I use the kolla images. Thank you Regards

2 3

[edge] China Mobile Edge platform evaluation presentation next Tuesday on the Edge WG call
by Ildiko Vancsa 13 Jun '19

13 Jun '19

Hi, I attended a presentation today from Qihui Zhao about China Mobile’s experience on evaluation different edge deployment models with various software components. As many of the evaluated components are part of OpenStack and/or StarlingX I invited her for next week’s Edge Computing Group call (Tuesday, June 18) to share their findings with the working group and everyone who is interested. For agenda and call details please visit this wiki: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings Please let me know if you have any questions. Thanks and Best Regards, Ildikó

1 0