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

[keystone] Keystone Team Update - Week of 17 June 2019
by Colleen Murphy 21 Jun '19

21 Jun '19

# Keystone Team Update - Week of 17 June 2019 ## News ### Next steps for oslo.limit In order to make progress on having a usable interface for oslo.limit, we discussed[1][2] simplifying the current implementation. Lance has some patches[3] that remove the ideas of claims and context managers, which sacrifices the risk of race conditions and performance penalties in favor of simplicity for the time being. [1] http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-06-18-1… [2] http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-k… [3] https://review.opendev.org/665708 ## Open Specs Train specs: https://bit.ly/2uZ2tRl Ongoing specs: https://bit.ly/2OyDLTh Train specs need to be merged by July 26. Please help review these specs and be mindful of feedback. ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 20 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 44 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ## Bugs This week we opened 6 new bugs and closed 5. Bugs opened (6) Bug #1833085 (keystone:High) opened by Sebastian Riese https://bugs.launchpad.net/keystone/+bug/1833085 Bug #1833739 (keystone:High) opened by David Orman https://bugs.launchpad.net/keystone/+bug/1833739 Bug #1833311 (keystone:Undecided) opened by Michael Carpenter https://bugs.launchpad.net/keystone/+bug/1833311 Bug #1833340 (keystone:Undecided) opened by cnaik https://bugs.launchpad.net/keystone/+bug/1833340 Bug #1833554 (keystone:Undecided) opened by Chason Chan https://bugs.launchpad.net/keystone/+bug/1833554 Bug #1833207 (keystoneauth:Undecided) opened by Jagatjot Singh https://bugs.launchpad.net/keystoneauth/+bug/1833207 Bugs closed (2) Bug #1832005 (keystone:Undecided) https://bugs.launchpad.net/keystone/+bug/1832005 Bug #1833340 (keystone:Undecided) https://bugs.launchpad.net/keystone/+bug/1833340 Bugs fixed (3) Bug #1750676 (keystone:High) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1750676 Bug #1818844 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1818844 Bug #1649735 (keystonemiddleware:Medium) fixed by Colleen Murphy https://bugs.launchpad.net/keystonemiddleware/+bug/1649735 ## Milestone Outlook https://releases.openstack.org/train/schedule.html Milestone 2 is in 5 weeks. Train specs need to be merged by then. Feature proposal freeze is in 8 weeks. ## Shout-outs Shout out to Nathan Oyler, whose first patch to OpenStack[4] fixed a major omission in our audit notifications. Thanks, Nathan! [4] https://review.opendev.org/664618 ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

[goal][python3] Train unit tests weekly update (goal-12)
by Corey Bryant 21 Jun '19

21 Jun '19

This is the goal-12 weekly update for the "Update Python 3 test runtimes for Train" goal [1]. There are 12 weeks remaining for completion of Train community goals [2]. == What's the Goal? == To ensure (in the Train cycle) that all official OpenStack repositories with Python 3 unit tests are exclusively using the 'openstack-python3-train-jobs' Zuul template or one of its variants (e.g. 'openstack-python3-train-jobs-neutron') to run unit tests, and that tests are passing. This will ensure that all official projects are running py36 and py37 unit tests in Train. For complete details please see [1]. == Ongoing Work == I've submitted patch automation scripts for review: https://review.opendev.org/#/c/666934 And I've started submitting patches that were generated using the above scripts. Open patches needing reviews: https://review.openstack.org/#/q/topic:python3-train+is:open Failing patches: https://review.openstack.org/#/q/topic:python3-train+status:open+(+label:Ve… Some notes on 2 issues I came across this week: 1) Some projects that have a valid reason to keep old tox.ini py3 environments or setup.cfg classifiers. For example, the OpenStack Charms project is a deployment project that still supports deployments on xenial, and keeping the py35 environment in tox.ini makes sense. In scenarios like this I plan to continue with the Zuul switch to openstack-python3-train-jobs without removing py35 tox.ini or Python 3.5 classifier from setup.cfg. 2) Some projects are missing Zuul config. Not to pick on any projects in particular but as an example there are projects that I'd expect to have .zuul.yaml or equivalent, such as python-adjutant, however it doesn't. In scenarios like this I plan to skip the project entirely. == Completed Work == Merged patches: https://review.openstack.org/#/q/topic:python3-train+is:merged == How can you help? == Please take a look at the failing patches and help fix any failing unit tests for your project(s). Python 3.7 unit tests will be self-testing in Zuul. If you're interested in helping submit patches, please let me know. == Reference Material == [1] Goal description: https://governance.openstack.org/tc/goals /train/python3-updates.html [2] Train release schedule: https://releases.openstack.org/train/schedule.html (see R-5 for "Train Community Goals Completed") Storyboard: https://storyboard.openstack.org/#!/story/2005924 Porting to Python 3.7: https://docs.python.org/3/whatsnew/3.7.html#porting-to-python-3-7 Python Update Process: https://opendev.org/openstack/governance/src/branch/master/resolutions/2018… Train runtimes: https://opendev.org/openstack/governance/src/branch/master/reference/runtim… Thanks, Corey

1 0

[ThirdParty][CI] : CI-watch is not updating with latest patchset
by Sharma, Virendra Sharma 21 Jun '19

21 Jun '19

Hi Team, >From last few days unable to see latest patch set entry in CI-WATCH (http://ciwatch.mmedvede.net/project?project=cinder&time=7+days) However third party CI running on latest patch set and reporting its vote to Gerrit accordingly. Currently it is visible for last 7 days but soon it will also go off, if it won't reflect updated one. Please help me to understand if any update regarding this or else provide way to get it resolved from my end. Regards, Virendra

2 1

[openstack-operators][neutron][olso.db] connection pool configuration
by Arnaud Morin 21 Jun '19

21 Jun '19

Hey all, I am wondering what configuration the operators in this mailing list are using in [oslo.db] section. For example, the max_pool_size default value is 5, which seems very low to me (our deployment is having more than 1000 neutron agents). So, is there any recommendation somewhere for those settings? Thanks for any tip. -- Arnaud Morin

1 0

[placement] update 19-24
by Chris Dent 21 Jun '19

21 Jun '19

HTML: https://anticdent.org/placement-update-19-24.html Here's a 19-24 pupdate. Last week I said there wouldn't be one this week. I was wrong. There won't be one next week. I'm taking the week off to reset (I hope). I've tried to make sure that there's nothing floating about in Placement land that is blocking on me. # Most Important The [spec for nested magic](https://review.opendev.org/662191) is close. What it needs now is review from people outside the regulars to make sure it doesn't suffer from tunnel vision. The features discussed form the foundation for Placement being able to service queries for real world uses of nested providers. Placement can already model nested providers but asking for the right one has needed some work. # Editorial I read an article this morning which touches on the importance of considering [cognitive load in software design](https://techbeacon.com/app-dev-testing/forget-monoliths-vs-microser…. It's fully of glittering generalities, but it reminds me of some of the reasons why it was important to keep a solid boundary between Nova and Placement and why, now that Placement is extracted, the complexity of this nested magic is something we need to measure against the cognitive load it will induce in the people who come after us as developers and users. # What's Changed * Support for mappings in allocation candidates has merged as [microversion 1.34](https://docs.openstack.org/placement/latest/placement-api-microversio…. * Gibi made it so [OSProfiler](https://docs.openstack.org/osprofiler/latest/) works with placement again. # 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. 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 23 (3) stories in [the placement group](https://storyboard.openstack.org/#!/project_group/placement). 0 (0) are [untagged](https://storyboard.openstack.org/#!/worklist/580). 4 (1) are [bugs](https://storyboard.openstack.org/#!/worklist/574). 5 (-1) are [cleanups](https://storyboard.openstack.org/#!/worklist/575). 11 (0) are [rfes](https://storyboard.openstack.org/#!/worklist/594). 3 (1) 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 (0). * Placement related nova [in progress bugs](https://goo.gl/vzGGDQ) on launchpad: 5 (-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. * <https://review.opendev.org/666542> Add support for multiple member_of. # 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). Code related to this: * <https://review.opendev.org/663009> PoC: resourceless request, including some code from <https://review.opendev.org/657510> WIP: Allow RequestGroups without resources * <https://review.opendev.org/#/q/topic:story/2005575-33753> Support for the new root_required query parameter. Introduces the useful concepts of required wide params and a request wide search context. ## 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. * <https://review.opendev.org/#/q/topic:story/2005443> Add a nested-perfload job, using gabbi to create the trees. Unsurprisingly, nested topologies are slower than non; having this job will help us track that. # Other Placement Miscellaneous changes can be found in [the usual place](https://review.opendev.org/#/q/project:openstack/placement+status:op…. There are five [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/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/634551> libvirt: report pmem namespaces resources by provider tree * <https://review.opendev.org/660852> Nova: Remove PlacementAPIConnectFailure handling from AggregateAPI * <https://review.opendev.org/#/q/topic:bp/support-move-ops-with-qos-ports> Nova: support move ops with qos ports * <https://review.opendev.org/665168> TripleO: Enable Request Filter for Image Types * <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 * <https://review.opendev.org/657796> Nova: Defaults missing group_policy to 'none' * <https://review.opendev.org/666202> Blazar: Create placement client for each request * <https://review.opendev.org/666298> OSA: Fix aio_distro_metal jobs for openSUSE # End Go outside. Reflect a bit. Then do. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent

1 0

[Security SIG] Weekly Newsletter June 13th & June 20th
by Gage Hugo 20 Jun '19

20 Jun '19

So I wrote the newsletter for last week, but forgot to send out the actual email, so this week will have double the content! #Week of: 20 June 2019 - Security SIG Meeting Info: http://eavesdrop.openstack.org/#Security_SIG_meeting - Weekly on Thursday at 1500 UTC in #openstack-meeting - Agenda: https://etherpad.openstack.org/p/security-agenda - https://security.openstack.org/ - https://wiki.openstack.org/wiki/Security-SIG #Meeting Notes - Summary: http://eavesdrop.openstack.org/meetings/security/2019/security.2019-06-20-1… - This week we discussed cleaning up the security.openstack.org page - Overall there are many outdated sections, we came up with a current rough plan that is outlined in the security-agenda notes for this week's meeting - Retiring Syntribos - On the topic of cleaning up the security.openstack.org page, one section is security tools, which currently lists bandit and syntribos. - Looking at the Syntribos repo, it seems like lately there's only been changes related to doc fixes and overall zuul updates, with a couple actual updates to the project. - If there's anyone still with interest in updating/using Syntribos, please reach out to us. ## News - [nova] TPM thread: http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007258.html # VMT Reports - A full list of publicly marked security issues can be found here: https://bugs.launchpad.net/ossa/ - No new public security bugs this week ======================================================================================================== #Week of: 13 June 2019 - Security SIG Meeting Info: http://eavesdrop.openstack.org/#Security_SIG_meeting - Weekly on Thursday at 1500 UTC in #openstack-meeting - Agenda: https://etherpad.openstack.org/p/security-agenda - https://security.openstack.org/ - https://wiki.openstack.org/wiki/Security-SIG #Meeting Notes - Summary: http://eavesdrop.openstack.org/meetings/security/2019/security.2019-06-13-1… - This week we finalized the details and settings for the [openstack-security] mailing list. The list will be used to provide purely automated notifications about security-related changes and bug reports within OpenStack. Anyone looking to reach out to the security SIG can either use the [openstack-discuss] mailing list or use the #openstack-security channel on freenode IRC. ## News - Storyboard: The security team autoassignment feature landed - If a new story is marked as "security" upon creation, it will automatically become private, however it can be edited to become public after it is created. # VMT Reports - A full list of publicly marked security issues can be found here: https://bugs.launchpad.net/ossa/ - No new public security bugs this week

1 0

[nova]Bug #1829696: qemu-kvm process takes 100% CPU usage when running redhat/centos 7.6 guest OS
by 钱熙 20 Jun '19

20 Jun '19

Hi there, I am struggling with qemu-kvm 100% CPU usage problem. When running redhat or centos 7.6 guest os on vm, the cpu usage is very low on vm(almost 100% idle when no tasks run), but on the host, qemu-kvm reports 100% cpu busy usage. https://bugs.launchpad.net/nova/+bug/1829696 I opened the bug above, however it did not find some interest. After searching some related bugs report, I suspect that it is due to the clock settings in vm's domain xml. My settings are as follows: <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> And details about the bug, please see https://bugs.launchpad.net/nova/+bug/1829696 It shows that only the version 7.6 of redhat or centos affected by this bug behavior. In my cluster, it is OK for versions from redhat or centos 6.8 to 7.5. Any clue or suggestion? ------------------ Thanks a lot! Best regards QianXi

2 1

[nova] API updates week 19-25
by Ghanshyam Mann 20 Jun '19

20 Jun '19

Hi All, Please find the Nova API updates of this week. API Related BP : ============ Code Ready for Review: ------------------------------ 1. Support adding description while locking an instance: - Topic: https://review.opendev.org/#/q/topic:bp/add-locked-reason+(status:open+OR+s… - Weekly Progress: OSC patch has been updated by tssurya. mriedem is +1. 2. Add host and hypervisor_hostname flag to create server - Topic: https://review.opendev.org/#/q/topic:bp/add-host-and-hypervisor-hostname-fl… - Weekly Progress: patch is updated with review comment. ready for re-review. 3. Specifying az when restore shelved server - Spec: https://review.opendev.org/#/q/topic:bp/support-specifying-az-when-restore-… - Weekly Progress: Spec is merged and code is up for review. 4. Nova API cleanup - Spec: https://review.openstack.org/#/c/603969/ - Weekly Progress: working on code, seems like a lot of tests changes. Should be able to push code by next report. 5. Detach and attach boot volumes: - Topic: https://review.openstack.org/#/q/topic:bp/detach-boot-volume+(status:open+O… - Weekly Progress: No Progress Spec Ready for Review: ----------------------------- 1. Nova API policy improvement - Spec: https://review.openstack.org/#/c/547850/ - PoC: https://review.openstack.org/#/q/topic:bp/policy-default-refresh+(status:op… - Weekly Progress: Under review and updates. 2. Support for changing deleted_on_termination after boot -Spec: https://review.openstack.org/#/c/580336/ - Weekly Progress: No update this week. 3. Support delete_on_termination in volume attach api -Spec: https://review.openstack.org/#/c/612949/ - Weekly Progress: No updates this week. 4. Add API ref guideline for body text - ~8 api-ref are left to fix. Previously approved Spec needs to be re-proposed for Train: --------------------------------------------------------------------------- 1. Servers Ips non-unique network names : - https://blueprints.launchpad.net/nova/+spec/servers-ips-non-unique-network-… - https://review.openstack.org/#/q/topic:bp/servers-ips-non-unique-network-na… 2. Volume multiattach enhancements: - https://blueprints.launchpad.net/nova/+spec/volume-multiattach-enhancements - https://review.openstack.org/#/q/topic:bp/volume-multiattach-enhancements+(… Bugs: ==== No progress report in this week. NOTE- There might be some bug which is not tagged as 'api' or 'api-ref', those are not in the above list. Tag such bugs so that we can keep our eyes. -gmann

1 0

[sigs][publiccloud][publiccloud-wg][publiccloud-sig][billing] Cancellation todays meeting for the Public Cloud SIG
by Tobias Rydberg 20 Jun '19

20 Jun '19

Hi all, Unfortunate I need to cancel today meeting for the Public Cloud SIG since I can't manage to make it. Feel free to use the time if you will to continue our ongoing discussions regarding the billing initiative. I'm happy to schedule a meeting next week at the same time, please respond to this email or drop a message in the channel if that i suitable for you. I also want to bring the new User Survey to attention to you all if you have missed that and haven't taken it. Please also spread the word to fellow colleagues, customers and what not. URL to survey: https://www.openstack.org/user-survey/survey-2019/ Cheers, Tobias -- Tobias Rydberg Senior Developer Twitter & IRC: tobberydberg www.citynetwork.eu | www.citycloud.com INNOVATION THROUGH OPEN IT INFRASTRUCTURE ISO 9001, 14001, 27001, 27015 & 27018 CERTIFIED

1 0

[placement][docs][packaging] rpm- and deb- related placement install docs
by Chris Dent 20 Jun '19

20 Jun '19

The placement install docs [1] have the following warning plastered on top: These installation documents are a work in progress. Some of the distribution packages mentioned are not yet available so the instructions will not work. It is likely that packages are now available, but the docs have not been updated to reflect that, nor have the docs been verified against those packages. None of the regular and active contributors to placement are involved with distro-related packaging. In addition they are all already fully booked. Are there members of the community who are involved with the distros, and who can update and verify these docs? If not, we will likely need to remove the distro related install documents before the end of the Train release and solely maintain the install-from-pypi docs [2] (which are up to date). This is because the existing docs are now misleading, and thus potentially dangerous and extra-work-inducing, as suggested by a recent bug [3]. If you are interested in helping out, please follow up. If you're unable to help out, but know people involved with packaging who should know about this concern, please let them know. Thanks for your help. [1] https://docs.openstack.org/placement/latest/install/index.htmlk [2] https://docs.openstack.org/placement/latest/install/from-pypi.html [3] https://storyboard.openstack.org/#!/story/2005910 -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent

4 3