- openstack-discuss - lists.openstack.org

[heat][election][ptl] Heat PTL candidacy for Ussuri cycle
by Rico Lin 02 Sep '19

02 Sep '19

Dear Heat members, I would like to announce my candidacy as the Heat project team leader for Ussuri cycle. We have been suffered from a lack of people to help on review. So if you're reading this, please join us, and help with review and features. One of our current strategies is to make a worklist to target for each release and try to make those items finish on time. Also, another strategy is to get better integration with other projects or even cross communities. We have been triggered some discussion with SIGs and other projects to try to figgering where we can keep this integration moving. Appears we still got a lot of jobs to do. My plan for the next cycle will keep those two strategies, and extend from there if we got time. Please consider my candidacy. Thank you. Rico Lin (ricolin) -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[openstack-dev] [neutron] Cancelling Neutron weekly meeting on September 2nd
by Miguel Lavalle 01 Sep '19

01 Sep '19

Hi Neutrinos, September 2nd is a holiday in the USA, so we will cancel our weekly meeting. We will resume on Tuesday 10th Best regards

1 0

[nova] Status of the bp support-move-ops-with-qos-ports
by Balázs Gibizer 31 Aug '19

31 Aug '19

Hi, As feature freeze is closing in I try to raise awareness of the implementation status of the support-move-ops-with-qos-ports<https://review.opendev.org/#/q/status:open+project:openstack/nova+branch:ma…> bp [1]. The original goal of the bp was to support every move operations (cold migrate, resize, live-migrate, evacuate, unshelve). Today I have ready and tested (unit + functional) patches proposed for cold migrate and resize [2]. I don't think every move operations will be ready and merged in Train but I still hope that there is a chance for cold migrate and resize to land. Sure I will continue working on supporting the operations that miss the Train in the U release. One possible complication in the current patch series is that it proposes the necessary RPC changes for _every_ move operations [3]. This might not be what we want to merge in Train if only cold migrate and resize support fill fit. So I see two possible way forwards: a) Others also feel that cold migrate and resize will fit into Train, and then I will quickly change [3] to only modify those RPCs. b) We agree to postpone the whole series to U. Then I will not spend too much time on reworking [3] in the Train timeframe. A connected topic: I proposed patches [4] to add cold migrate and resize tempest coverage to the nova-grenade-multinode (renamed from nova-grenade-live-migrate) job as Matt pointed out in [3] that we don't have such coverage and that my original change in [3] would have broken a mixed-compute-version deployment. Any feedback is appreciated. Cheers, gibi [1] https://specs.openstack.org/openstack/nova-specs/specs/train/approved/suppo… [2] https://review.opendev.org/#/q/topic:bp/support-move-ops-with-qos-ports [3] https://review.opendev.org/#/c/655721 [4] https://review.opendev.org/#/c/679210

4 5

[neutron][qa] Databases used on CI jobs
by Slawek Kaplonski 31 Aug '19

31 Aug '19

Hi, Recently in Neutron we merged patch [1] which caused error in Kolla-ansible [2]. It seems that issue happens on mariadb 10.1 which is used in broken Kolla-ansible job so I started checking what database is used on Neutron’s jobs as we didn’t found any issue with this patch. And it seems that in all scenario/api jobs we have installed mysql 5.7 - see [3] for example. And the question is - should we maybe switch somehow to Mariadb instead of Mysql? Should it be done globally or maybe it’s only “issue” in Neutron’s CI jobs? Or maybe we should have jobs with both Mariadb and Mysql databases? [1] https://review.opendev.org/#/c/677221 [2] https://bugs.launchpad.net/kolla-ansible/+bug/1841907 [3] https://2f275f27875ae066d2b6-00a9605a715176e6bd23401c23e881d7.ssl.cf2.rackc… — Slawek Kaplonski Senior software engineer Red Hat

4 6

[qa][ptl][election] Quality Assurance PTL Candidacy for Ussuri
by Ghanshyam Mann 31 Aug '19

31 Aug '19

Hi Everyone, I would like to announce my candidacy for Quality Assurance PTL role for Ussuri cycle. It was a great experience while serving QA PTL for the last three cycles. With very few active contributions, I am proud on the team to keep the QA tooling up and maintained. Making sure no gate break and keep the OpenStack stability as a priority. In Train Cycle, we concentrate on a few key things like improving the gate stability which was tried with breaking the integrate-gate project template into project-specific template[1]. Migrating all the OpenStack CI/CD from Xenial to Bionic etc. We have few more planned work still pending for Train like keystone's system scope testing, making sanity job voting, documenting the QA process etc but I think we will be able to make it in Train as we still have around a month to release Train. Along with daily QA activities, my priority for QA in the next cycle will be: - Release Patrole stable version and find out the way to make it faster so that it can test the API policy on project gate also. - New ideas for more tooling or tests project to focus on OpenStack or Common communities. - Finish the grenade job to zuulv3 which is not yet merged. - Stability of Tempest plugins. There are many tempest plugins which are not so stable. We will plan audit activities for all plugins. I know using Tempest service registry and setting service_availabilty properly is the key things to do on the Plugins side. - Finish the JSON strict validation for volume services. Zhufl has lot of patches to review on this. This will be on priority to finish in the next cycle. - Guiding and motivating more contributors to QA projects. Thanks for reading and consideration my candidacy for Ussuri cycle. [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007568.html -gmann

1 0

[all][tc] Hear ye! Hear ye! Our Newest Release Name - OpenStack Ussuri
by Rico Lin 31 Aug '19

31 Aug '19

Dear all OpenStackers It's my honor to announce OpenStack U release name "*Ussuri" *(naming after Ussuri River). Ussuri has been selected as top one option from community poll and also been lawyer-approved, so it's official. Thanks again for all who join the U release naming processes. -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

6 5

[security] Weekly Newsletter - 29 Aug 2019
by Gage Hugo 31 Aug '19

31 Aug '19

Last two weeks had no meeting activity, however this week we had plenty, so here's the summary. Hope everyone has a great weekend! #Date: 29 Aug 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-08-29-1… - OSSA-2019-004 was released this week, more details here: https://security.openstack.org/ossa/OSSA-2019-004.html - The VMT is currently in the process of updating the requirements for a project to obtain the "vulnerability:managed tag, there is a current change in progress here:https://review.opendev.org/#/c/678426/ - The main goal is to reduce the barrier of entry by not explicitly requiring an audit being performed on the project (but still recommending it), as well as clarifications on other guidelines - The security docs are continuing to see updates: https://review.opendev.org/#/q/project:openstack/security-doc - Shoutout to nickthetait for taking on this work, and to those reviewing it as well! - We discussed the default policy file discrepencies in Cinder/Nova in the Queens release, it appears that several projects have different file defaults for policy. - This is causing issues when a policy file works fine in one release, but after upgrading, the file is no longer automatically detected. - One path forward is to open a security docs bug to track these and look for a way to resolve this. #VMT Reports - A full list of publicly marked security issues can be found here: https://bugs.launchpad.net/ossa/ - OSSA-2019-004 was released this week, more details here: https://security.openstack.org/ossa/OSSA-2019-004.html

1 0

[cinder] PTL candidacy
by Brian Rosmaita 30 Aug '19

30 Aug '19

Hello everyone, I would like to announce my candidacy for Cinder PTL for the 'U' cycle. The Cinder project is in a good state right now due to Jay Bryant's leadership and a strong community of developers interested in keeping Cinder stable and relevant. The project has matured (which is a good thing): a look at the cinder-specs repository shows an interest in adding some features, but there's also a large focus on enhancing existing features and introducing improvements to make the software more reliable. And the project's relevance has been continued by the introduction of the cinderlib library that makes Cinder backend drivers usable for applications beyond OpenStack, for example, by the Ember CSI plugin for containers. The Cinder project also faces some challenges. Like all the major OpenStack projects, over the past several cycles it has been showing a decline in the number of contributors and in the diversity of their affiliations. Further, we had a big scare this cycle when it looked like about half of the backend drivers would have to be marked unsupported due to vendors not updating their third-party CI systems to Python 3. (As we approach milestone 3, happily, the situation is looking better.) Much as I'd like to say that as Cinder PTL, my scintillating personality will reverse this trend, the reality is that the days of companies renting out an entire museum in San Diego or Paris to entertain OpenStack contributors are well behind us. (Plus, I don't have a scintillating personality.) The positive way to look at this is that our community has contracted to a hard core of sufficient density as the effluvium is ejected, and we've reached a kind of steady state. Thus I think the main task I would need to undertake as PTL is to focus on nurturing the community we have. This isn't to say that we won't continue to do onboarding and outreach (we will), it's just that the days when an OpenStack project could design features and people would just show up and work on them are in the past. So we need to make sure that the current Cinder community--both developers working on the main project and developers working on vendor drivers--feel well-connected and valued. (This isn't to say they don't feel that way now; my point is that this is important to maintain.) Concrete steps toward this goal are continuing Jay's good work in keeping the Cinder community well-informed of the discussions at weekly meetings, Forum sessions, the PTG, and midcycle, and taking advantage of video meeting software so we can have more (virtual) face-to-face meetings. All this is sounds reasonable enough, but why me? I'm a fairly new member of the Cinder community. I've been a Cinder core contributor since April and have been helping with stable maintenance and releases. I've had some experience as an OpenStack PTL (Glance PTL for O, P, and Q), so I know what I'm getting into. I'm an active participant in the Cinder community, and if you'll have me as PTL, I promise to do my best not to break anything. Thank you for your consideration, Brian Rosmaita (rosmaita)

1 0

[neutron][graphql] Is the graphql branch still being used?
by Miguel Lavalle 30 Aug '19

30 Aug '19

Dear Stackers, Some time ago we created a feature branch in the Neutron repo for a PoC with graphql: https://opendev.org/openstack/neutron/src/branch/feature/graphql Is this PoC still going on? Is the branch still needed? The branch has been inactive since January and we are finding that patches against this branch don't pass zuul tests: https://review.opendev.org/#/c/678144/. If the branch is still being used, the team working on it should fix it so tests pass. If it is not used, let's remove it. If I don't hear back from anyone having interest in maintaining this branch by September 6th, I will go ahead and remove it. Thanks an regards Miguel

5 5

[tc] monthly meeting
by Mohammed Naser 30 Aug '19

30 Aug '19

Hi everyone, Here's the planning for the next TC meeting which will happen on Thursday, September 5th at 1400 UTC. If you’d like to add a topic of discussion, please feel free to do so. We will be cutting off the agenda on Wednesday the 4th so any subject added afterward won’t appear in the plan. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0

[goal][python3] Train unit tests weekly update (goal-2)
by Corey Bryant 30 Aug '19

30 Aug '19

This is the goal-2 weekly update for the "Update Python 3 test runtimes for Train" goal [1]. There are 2 weeks remaining for completion of Train community goals [2]. == How can you help? == If your project has failing tests please take a look and help fix. Python 3.7 unit tests will be self-testing in Zuul. Failing patches: https://review.openstack.org/#/q/topic:python3-train +status:open+(+label:Verified-1+OR+label:Verified-2+) If your project has patches with successful tests please help get them merged. Open patches needing reviews: https://review.openstack.org/#/q/topic:python3 -train+is:open Patch automation scripts needing review: https://review.opendev.org/#/c/666934 == Ongoing Work == Thank you to all who have contributed their time and fixes to enable patches to land. We're down to 9 projects with failing tests and 13 projects with successful tests. == Completed Work == All patches have been submitted to all applicable projects for this goal. Merged patches: https://review.openstack.org/#/q/topic:python3-train +is:merged == 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]. == 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… train.rst Thanks, Corey

1 0

[election][ptl][swift] Tim Burke's candidacy for Swift PTL
by tim＠swiftstack.com 30 Aug '19

30 Aug '19

I would be honored to continue serving you as Swift PTL. This past cycle, we have laid the foundation for Swift's continued success: we support running Swift on Python 3. This has been long overdue, and a long time coming. While we first began to the process four years ago, momentum has only really picked up for it in the last year and a half. As of last week, all unit tests and functional tests now run under py3. It has been such a joy to see this project finally coming to a close. We certainly benefited greatly by having four and a half years with an exceptionally stable base to build upon, but now we have ensured Swift's future deployability, maintainability, and longevity. John Dickinson's long-time goal that Swift be used everywhere, every day, by everyone could only hope to be fleeting without this community- driven effort. Speaking of, I'm so happy to see that the transition to storing Zuul logs in Swift [1] has gone so smoothly. A half-dozen or so clusters suddenly started ingesting millions more PUTs every day, and yet Clark Boylan says he "[hasn't] heard complaints from the swift clouds" -- I can think of few better compliments on the quality of our software. :-) With many millions of objects getting created every day and a median object size in the tens of kilobytes, this emphasizes another years- long project: OVH's work to optimize small-file workloads. Our next focus should be to integrate their (already running in production!) improvements back into master and disseminate their knowledge of how to hack on, debug, deploy, monitor, and troubleshoot in a brave new world. I look forward to organizing this effort in Ussuri. Tim Burke [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008516.h…

1 0

Metadata service caching old nameservers?
by Grant Morley 30 Aug '19

30 Aug '19

Hi All, We have a bit of a weird issue with resolv.conf for instances. We have changed our subnets in neutron to use googles nameservers which is fine. However it seems that when instances are launched they are still getting the old nameserver settings as well as the new ones. If I look at the metadata networking service it returns the old nameservers as well as the new ones below: curl -i http://169.254.169.254/openstack/2017-02-22/network_data.json HTTP/1.1 200 OK Content-Type: text/plain; charset=UTF-8 Content-Length: 753 Date: Thu, 29 Aug 2019 09:40:03 GMT {"services": [{"type": "dns", "address": "178.18.121.70"}, {"type": "dns", "address": "178.18.121.78"}, {"type": "dns", "address": "8.8.8.8"}, {"type": "dns", "address": "8.8.4.4"}] In our neutron dhcp-agent.ini file we have the correct dnsmasq nameservers set: dnsmasq_dns_servers = 8.8.8.8, 8.8.4.4 Are there any database tables I can change or clear up to ensure the old nameservers no longer get set? I can't seem to find any reference in our config any more of the old nameservers, so I assume one of the services is still setting them but I can't figure out what is. Any help will be much appreciated. Many thanks, -- Grant Morley Cloud Lead, Civo Ltd www.civo.com <https://www.civo.com/>| Signup for an account! <https://www.civo.com/signup>

2 3

[openstack-dev][magnum] Using Fedora Atomic 29 for k8s cluster
by Feilong Wang 30 Aug '19

30 Aug '19

Hi all, At this moment, Magnum is still using Fedora Atomic 27 as the default image in devstack. But you can definitely use Fedora Atomic 29 and it works fine. But you may run into a performance issue when booting Fedora Atomic 29 if your compute host doesn't have enough entropy. There are two steps you need for that case: 1. Adding property hw_rng_model='virtio' to Fedora Atomic 29 image 2. Adding property hw_rng:allowed='True' to flavor, and we also need hw_rng:rate_bytes=4096 and hw_rng:rate_period=1 to get a reasonable rate limit to avoid the VM drain the hypervisor. We are working on a patch for Magnum devstack to support FA29 out of box. Meanwhile, we're starting to test Fedora CoreOS 30. Please popup in #openstack-containers channel if you have any question. Cheers. -- Cheers & Best regards, Feilong Wang (王飞龙) -------------------------------------------------------------------------- Head of R&D Catalyst Cloud - Cloud Native New Zealand Tel: +64-48032246 Email: flwang(a)catalyst.net.nz Level 6, Catalyst House, 150 Willis Street, Wellington --------------------------------------------------------------------------

6 12

[neutron][ptl][elections] Non candidacy for U cycle
by Miguel Lavalle 30 Aug '19

30 Aug '19

Dear Neutron team, It has been an honor to be your PTL for the past four cycles. I have really enjoyed the ride and am thankful for all the support and hard work that you all have provided over these past two years. As I said in my last self-nomination ( http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003714.ht…) I am of the opinion that it is healthy to transfer periodically the baton to a new leader with fresh ideas and energy. One of the focus areas of my PTL tenure has been to keep the team strong by actively helping community members to become contributors and core reviewers. As a consequence, I know for a fact that we have a deep bench of potential new PTLs ready to step up to the plate. As for me, I am not going anywhere. I am very lucky that my management at Verizon Media supports my continued active involvement with the community at large and the Neutron family of projects in particular. So I look forward to help the team in the upcoming U cycle and beyond. Thank you soooo much! Miguel

9 8

Issue in cloudkitty
by Jyoti Dahiwele 30 Aug '19

30 Aug '19

Dear Team, Plz help in following issue. While collecting gnocchi aggregates I ran into 400 response from gnocchi due to lack of metrics at that particular point of time. I am unable to fill the metrics with zero values. The cloudkitty rated_data_frames table in the database shows __NO_DATA__ . Here below are the logs *cloudkitty-processor.log* *2019-01-11 17:06:56.334 7207 WARNING cloudkitty.orchestrator [-] [5793054cd0fe4a018e959eb9081442a8] Error while collecting metric volume.size: {u'cause': u'Metrics not found', u'detail': [u'volume.size']} (HTTP 400). Retrying on next collection cycle.: BadRequest: {u'cause': u'Metrics not found', u'detail': [u'volume.size']} (HTTP 400)* *2019-01-11 17:07:00.356 7207 WARNING cloudkitty.orchestrator [-] [2eea218eea984dd68f1378ea21c64b83] Error while collecting metric volume.size: {u'cause': u'Metrics not found', u'detail': [u'volume.size']} (HTTP 400). Retrying on next collection cycle.: BadRequest: {u'cause': u'Metrics not found', u'detail': [u'volume.size']} (HTTP 400)* *gnocchi-api.log* *10.20.0.100 - - [11/Jan/2019:17:07:04 +0000] "POST /v1/aggregates?details=False&groupby=id&groupby=project_id&start=2019-01-01T00%3A00%3A00&stop=2019-01-01T01%3A00%3A00 HTTP/1.1" 400 280 "-" "cloudkitty-processor keystoneauth1/3.11.2 python-requests/2.21.0 CPython/2.7.15rc1"* *10.20.0.100 - - [11/Jan/2019:17:07:08 +0000] "POST /v1/aggregates?details=False&groupby=id&groupby=project_id&start=2019-01-01T00%3A00%3A00&stop=2019-01-01T01%3A00%3A00 HTTP/1.1" 400 280 "-" "cloudkitty-processor keystoneauth1/3.11.2 python-requests/2.21.0 CPython/2.7.15rc1"* *Also, the price while launching the instance is not getting updated on the fly.* *Below are the processor logs of cloudkitty:-* *2019-08-30 11:20:18.571 23130 ERROR oslo_messaging.rpc.server AttributeError: 'list' object has no attribute 'start'* 2019-08-30 11:20:18.571 23130 ERROR oslo_messaging.rpc.server 2019-08-30 11:20:18.887 23136 DEBUG cloudkitty.orchestrator [-] Received quote from RPC. quote /usr/lib/python2.7/site-packages/cloudkitty/orchestrator.py:11 1 2019-08-30 11:20:18.977 23136 DEBUG oslo_db.api [-] Loading backend 'sqlalchemy' from 'cloudkitty.rating.hash.db.sqlalchemy.api' _load_backend /usr/lib/pytho n2.7/site-packages/oslo_db/api.py:261 2019-08-30 11:20:19.131 23136 DEBUG oslo_db.api [-] Loading backend 'sqlalchemy' from 'cloudkitty.db.sqlalchemy.api' _load_backend /usr/lib/python2.7/site-pa ckages/oslo_db/api.py:261 2019-08-30 11:20:19.153 23136 DEBUG oslo_db.api [-] Loading backend 'sqlalchemy' from 'cloudkitty.rating.pyscripts.db.sqlalchemy.api' _load_backend /usr/lib/ python2.7/site-packages/oslo_db/api.py:261 2019-08-30 11:20:19.167 23136 ERROR oslo_messaging.rpc.server [-] Exception during message handling: AttributeError: 'list' object has no attribute 'start' 2019-08-30 11:20:19.167 23136 ERROR oslo_messaging.rpc.server Traceback (most recent call last):

1 0

[election][barbican][ptl] U Cycle Candidacy
by Douglas Mendizábal 30 Aug '19

30 Aug '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I would like to announce my candidacy to continue to serve as Barbican PTL for the U cycle. My goals for this next cycle is to continue to improve the usability of the client libraries, especially getting feature parity between python-barbicanclient and openstacksdk.key_manager to support the Image Encryption cross-project effort. Thank you, Douglas Mendizábal -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEwcapj5oGTj2zd3XogB6WFOq/OrcFAl1pJhAACgkQgB6WFOq/ OreypA/+JweQuiTuM4TgcmngHdFWBWZeL2VQ9a6OgyfxwSBXV7QP859wbmLsc6UP bOZkRCNNq2/GLkx6fvQ8/4Q7NzoB5ZL3OSAJVkbo3Gdm8/eXiq+FHiy6JqX+2EjD 3GT8FUHDxI22zxsFnn9ILUGkreyJ2vxYFlIDhhRVrpJu40NCm8cm2FmVuFDmWbgk 3T73+Sch2GAkSuiB/ntlHlvzCd2yFX+8dLjtjeyRHL+uhA9Kx8Y75FMKF4bzlFl0 7WLc9fcQl7TSu3HlW0wFrC+EIIe9SJTvJF2f0UyuKstJLP1DdYyGNW+Qdv1Kcdwv 71jt8ZhjyD7OZ+WQ3kaYFcF33i2sTSpKWHZNISf3uB3dw1UL+tsu9x9xlcy+hfu3 AExE6kCmXinVNYf5i99MxNBbiqrnXJd5jSfLehHPj6dopUED253hqEu2ugO65aBM Nv1gORQPuO6iPq6l6YtHFj453OxBwFAvtTmPAKbd3S2N1USlik3x393t6y7ykhta X+EyC+Tci0cwX3JV1qkDSJvC1oPb0F8ynykrT3HrkCaDSqQ5xrScmMbXrlyHiB3J E99xzTKePz+xp7wY7hTFrSWdjFRJBlhgEgPzkxNCqblVkDkx3CvSdMfs3K75h0Og t4tckF82J5j+LeXn2W8nk6ZHGkKaFlC2cSWjCk5YWjBhridhVGs= =pfrQ -----END PGP SIGNATURE-----

1 0

kayobe 6.0.0.0rc2 (stein)
by no-reply＠openstack.org 30 Aug '19

30 Aug '19

Hello everyone, A new release candidate for kayobe for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/kayobe/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://opendev.org/openstack/kayobe/log/?h=stable/stein Release notes for kayobe can be found at: https://docs.openstack.org/releasenotes/kayobe/

1 0

[ops][glance] How to remove images stuck in 'deleted'
by Massimo Sgaravatto 30 Aug '19

30 Aug '19

Hi I have a few old images that for some reasons are stuck in the deleted state, and I would like to remove them Since a simple "openstack image delete <id>" can't be used [*], is it safe to set images.deleted to '1' in the glance db and then remove the relevant file in the backend ? Or are there better/safer options ? I am now running OpenStack Rocky Thanks, Massimo [*] Failed to delete image with name or ID '70a784ec-b109-4d4a-8a63-7c58d8db866c': 400 Bad Request: Image status transition from deleted to deleted is not allowed (HTTP 400)

1 0

[loci] Non-candidacy for U cycle
by Chris Hoge 30 Aug '19

30 Aug '19

Thank you to the Loci team for having me serve as PTL. With the project seeing heavier usage in production, I feel it's important to hand over leadership to the developers who have more day-to-day usage. There are still lots of great enhancements that can be made to the project, and I'm excited to see what comes next. -Chris

2 1

[placement] update 19-34
by Chris Dent 30 Aug '19

30 Aug '19

HTML: https://anticdent.org/placement-update-19-34.html Welcome to placement update 19-34. Feature Freeze is the week of September 9th. We have features in progress in placement itself (consumer types) and osc-placement that would be great to land. # Most Important In addition to the features above, we really need to get started on tuning up the documentation so that `same_subtree` and friends can be used effectively. It is also time to start thinking about what features, if any, need to be pursued in Ussuri. If there are few, that ought to leave time and energy for getting the osc-placement plugin more up to date. And, there are plenty of stories (see below) that need attention. Ideally we'd end every cycle with zero stories, including removing ones that no longer make sense. # What's Changed * Tetsuro has picked up the baton for performance and refactoring work and found [some](https://review.opendev.org/677120) [improvements](https://review.opendev.org/677209) that have merged. There's additional work in progress (noted below). # Stories/Bugs (Numbers in () are the change since the last pupdate.) There are 25 (2) stories in [the placement group](https://storyboard.openstack.org/#!/project_group/placement). 0 (0) are [untagged](https://storyboard.openstack.org/#!/worklist/580). 5 (1) are [bugs](https://storyboard.openstack.org/#!/worklist/574). 4 (0) are [cleanups](https://storyboard.openstack.org/#!/worklist/575). 12 (1) are [rfes](https://storyboard.openstack.org/#!/worklist/594). 4 (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: 17 (-1). * Placement related nova [in progress bugs](https://goo.gl/vzGGDQ) on launchpad: 6 (2). # osc-placement osc-placement is currently behind by 12 microversions. * <https://review.opendev.org/666542> Add support for multiple member_of. There's been some useful discussion about how to achieve this, and a consensus has emerged on how to get the best results. * <https://review.opendev.org/640898> Adds a new `--amend` option which can update resource provider inventory without requiring the user to pass a full replacement for inventory and an `--aggregate` option to set inventory on all the providers in an aggregate. This has been broken up into three patches to help with review. This one is very close but needs review from more people than Matt. # Main Themes ## Consumer Types Adding a type to consumers will allow them to be grouped for various purposes, including quota accounting. * <https://review.opendev.org/#/q/topic:bp/support-consumer-types> A WIP, as microversion 1.37, has started. I picked this up yesterday and hope to have it finished next week, barring distractions. I figure having it in place for nova for Ussuri is a nice to have. ## Cleanup Cleanup is an overarching theme related to improving documentation, performance and the maintainability of the code. The changes we are making this cycle are fairly complex to use and are fairly complex to write, so it is good that we're going to have plenty of time to clean and clarify all these things. Performance related explorations continue: * <https://review.opendev.org/#/c/679385/> Refactor initialization of research context. This puts the code that might cause an exit earlier in the process so we can avoid useless work. One outcome of the performance work needs to be something like a _Deployment Considerations_ document to help people choose how to tweak their placement deployment to match their needs. The simple answer is use more web servers and more database servers, but that's often very wasteful. Discussions about [using a different JSON serializer](http://lists.openstack.org/pipermail/openstack-discuss/2019-Aug… terminated choosing not to use `orjson` because it presents some packaging and distribution issues that might be problematic. There's still an option to use one of the other alternatives, but that exploration has not started. # Other Placement Miscellaneous changes can be found in [the usual place](https://review.opendev.org/#/q/project:openstack/placement+status:op…. * <https://review.opendev.org/676982> Merge request log and request id middlewares is worth attention. It makes sure that _all_ log message from a single request use a global and local request id. There are two [os-traits changes](https://review.opendev.org/#/q/project:openstack/os-traits+status:… being discussed. And zero [os-resource-classes changes](https://review.opendev.org/#/q/project:openstack/os-resource-class…. # 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.opendev.org/659233> Cyborg: Placement report * <https://review.opendev.org/662229> helm: add placement chart * <https://review.opendev.org/#/q/topic:bp/virtual-persistent-memory> libvirt: report pmem namespaces resources by provider tree * <https://review.opendev.org/660852> Nova: Remove PlacementAPIConnectFailure handling from AggregateAPI * <https://review.opendev.org/670112> Nova: WIP: Add a placement audit command * <https://review.opendev.org/671793> Nova: libvirt: Start reporting PCPU inventory to placement A part of <https://review.opendev.org/#/q/topic:bp/cpu-resources> * <https://review.opendev.org/#/q/topic:bp/support-move-ops-with-qos-ports> Nova: support move ops with qos ports * <https://review.opendev.org/666202> Blazar: Create placement client for each request * <https://review.opendev.org/667952> nova: Support filtering of hosts by forbidden aggregates * <https://review.opendev.org/669079> blazar: Send global_request_id for tracing calls * <https://review.opendev.org/670696> tempest: Add placement API methods for testing routed provider nets * <https://review.opendev.org/672678> openstack-helm: Build placement in OSH-images * <https://review.opendev.org/674129> Correct global_request_id sent to Placement * <https://review.opendev.org/#/q/topic:bp/cross-cell-resize> Nova: cross cell resize * <https://review.opendev.org/674524> Nova: Scheduler translate properties to traits * <https://review.opendev.org/623558> Nova: single pass instance info fetch in host manager * <https://review.opendev.org/674708> Zun: [WIP] Claim container allocation in placement * <https://review.opendev.org/#/q/topic:bp/provider-config-file> Nova: using provider config file for custom resource providers # End ☃ -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent

1 0

[kolla] PTL candidacy
by Mark Goddard 30 Aug '19

30 Aug '19

Hi, I'd like to nominate myself to serve as the Kolla PTL for the Ussuri cycle. I have been PTL for the Train cycle, and would like the opportunity to continue to lead the team. In my Train nomination [1] I proposed a few things, including: * help those on the periphery of the project get more involved * try a new meeting time * hold a virtual PTG * adopt some of ironic's planning and tracking processes * continue improving CI testing During the cycle we have helped a number of new contributors get involved, and have taken on a new core contributor who is already one of the most active members. We polled for a new meeting time but found we were already optimal. The virtual PTG helped us to prioritise our efforts, and I expect we'll hold another this cycle. We now use a whiteboard [2] similar to ironic's, and went through a process of prioritisation of features for this cycle which we continue to use to guide our efforts. Finally, CI test coverage continues to improve - notably the new multinode upgrade job caught a pretty nasty MariaDB upgrade bug that we might not otherwise have spotted before release. If elected this cycle I'd like to continue to reflect on our processes, and encourage increasing test coverage for further stability. We recently added Kayobe [3] as a project deliverable, and I intend to ensure that these two overlapping communities come together effectively to make the most effective use of our combined resources. Thanks for reading, Mark Goddard (mgoddard) [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003617.ht… [2] https://etherpad.openstack.org/p/KollaWhiteBoard [3] https://docs.openstack.org/kayobe

1 0

Re: [User-committee] UC candidacy
by Ian Y. Choi 30 Aug '19

30 Aug '19

Hello, As an UC election official, I confirm that the candidate is eligible for UC election within nomination period. With many thanks, /Ian On Friday, August 30, 2019, Jaesuk Ahn <bluejay.ahn(a)gmail.com> wrote: > > Hi, > > This is Jaesuk Ahn from OpenStack Korea User Group. > I would like announce my candidacy to serve as the User Committee. > > As a strong advocate of OpenStack community, I have been involved in > OpenStack > from 2010, founded OpenStack Korea Community in 2011, and been a > coordinator of > the Korea community since then. I have devoted myself to build an open and > healthy local community, in addition, I have always been trying to be a > good > arbitrator between local and global community to embrace a diversity > together. > > Here are articles about various events that I have been one of main > organizers > and program chair of the events [1], [2], [3]. Please see the presentation > [4] > I did with two other community leaders on how we have built community in > Korea. > > From a technical point of view, I have been leading OpenStack dev team > since > 2010. I have switched companies during those years but was able to focus > on one > thing: deployment automation & lifecycle management of OpenStack. > OpenStack-Helm, > and Airship are the most recent efforts on this line of work in my career. > Here is my linkedin profile stating my work during the last 10 years [5]. > > I am currently leading a development team to work on > openstack-on-kubernetes in > SK Telecom. I have made an architectural decision to leverage kubernetes > for > OpenStack lifecycle management in 2016, that this decision eventually led > us to > collaborate with AT&T team. As a result of community collaboration with > AT&T, > I am happy to see both OpenStack-Helm project and Airship project active > in > the community. > > if I am chosen by the community, I am fully committed to hear various > voices > from many community members, especially from community members who has > difficulties in language and time barrier. I will do my best to > collaborate with others to > make OpenStack community more diverse and active. > > [1] https://superuser.openstack.org/articles/building-new- > foundations-openinfra-days-korea/ > [2] https://superuser.openstack.org/articles/openstack-korea-days-2017/ > [3] https://superuser.openstack.org/articles/openstack-day-in- > korea-2015-to-infinity-and-beyond/ > [4] https://www.slideshare.net/openstack_kr/boston-summit- > what-makes-it-possible-to-run-openstack-community-for-three-generations > [5] https://www.linkedin.com/in/jsahn/ > > > Thanks > > > *Jaesuk Ahn*, Ph.D. > Cloud Labs, SK Telecom >

1 0

[Packaging-Rpm] PTL Candidacy
by Javier Pena 30 Aug '19

30 Aug '19

Hello everyone, I would like to announce my candidacy to be the PTL for the Packaging Rpm project during the Ussuri development cycle. For the Ussuri cycle, my focus would be on: * Making sure all packages have been migrated to Python 3, so we can finally get rid of Python 2. * Transition the RDO CI and packages to CentOS 8, once it is released, and remove the now obsolete Fedora-based CI. That, of course, would be in addition to our common goals: expanding our contributor base, improving collaboration between RPM distributions, and keeping a high quality set of packages. Thanks, Javier

1 0

[cloudkitty] PTL candidacy
by Luka Peschke 30 Aug '19

30 Aug '19

Hello contributors, user, operators, I would like to submit my candidacy as CloudKitty's PTL for the Ussuri cycle. I've been contributing to the project for several releases and I've been the PTL for the last two releases. I'm very happy with the T cycle, as the goals we fixed ourselves have been achieved: the planned features have been implemented, some features that were planned for U might make it into T, and most importantly, our community has grown. If you want to have me as the project's PTL for the Ussuri cycle, I'd like to keep focusing on the points we addressed during the last few cycles: * Help CloudKitty's community to grow. This is a constant effort, and it is starting to pay off: people are gaining interest in CloudKitty, more and more questions and suggestions are being asked/made on IRC, and some external contributors are proposing patches. That's very rewarding for our small community, and we intent to keep it going! * Improving the documentation: A lot has been done during the last cycles, but with the growth of the v2 API, we need to keep putting effort into this; more specifically into tutorials, guides and into the developer documentation I'd also like to finally work on the new rating module. This has been planned and asked for too long, and we should finally work on this together. I will use this opportunity to thank everybody who's been involved in CloudKitty: developers, reviewers, users... The project lives thanks to you! Thank you for your attention, Luka Peschke

1 0

[Glance] PTL Candidacy
by Abhishek Kekane 29 Aug '19

29 Aug '19

Hello everyone, I would like to announce my candidacy for the role of PTL of Glance for the Ussuri cycle. I have been working closely with several previous PTL's like Erno and Brian and I am hoping to contribute back to the community as a PTL while following their excellent example. I've been working primarily with Glance since Icehouse and do work full-time on Glance upstream. During that time I've served community in release liaison role, as Glance core reviewer and part of Glance bugs team. I have represented Glance in interactions with various teams, such as the cross-projects interactions, API workgroup, documentation and OSIC. Even though I work in GMT+05:30 time zone, I am flexible enough to catchup with peoples who were in US or European time-zone. I have seen lots of highs and lows of the Glance and am proud that we have not only survived but also becoming strong. During the Train cycle we have managed to release glance-store version 1.0 which supports multiple stores configuration. This is how I want to focus for Ussuri cycle 1. Multiple stores support As glance-store v1.0 is out with multiple stores configuration support, I want to make sure Glance is able maintain it's backward compatibility and doesn't break any cross-project workflow. Most of the work is already done during Train cycle but in case if any bug occurs then it will be solved on the high priority. Multiple stores will also play role in Edge computing, so if any enhancement is required then it will be handled on top priority. 2. Glance cluster awareness With Interoperable Image Import and new edge usecases, Glance cluster awareness [0] is most important feature. Even the basic implementation has started during Train cycle, we want to use this in caching operations which will be carried out during this development cycle. 3. Bridging gap between Glance and Horizon Glance has now added new features such as new import workflow, import plugins, hidden images etc. Horizon is yet to implement these in the dashboards. I am going to put some efforts in communication with horizon team and help them to understand/implement/bridge this gap. 4. Catching up with tempest Similar to horizon, Glance needs to have tempest upto-date with new image import workflow, hidden images, multiples stores scenarios. I would like to catchup with tempest team and extend a hand to bridge this gap. 5. Community priorities Whatever community goals put forward by TC, as a PTL of Glance project will want to adopt these as a priority for Ussuri cycle. 6. Other As we are very short team at this moment, I would like to put some efforts in attracting some contributors, help them to understand how Glance functions and encourage them to contribute for Glance. Looking at past how Erno and Brian has steadied the ship, I know its a big task and with their help I will do my best not to fail the expectations. Thank you for consideration, Abhishek Kekane [0] https://review.opendev.org/#/c/664956/2/specs/train/approved/glance/cluster…

1 0

[all][election][TC] Candidacy for TC
by Kendall Nelson 29 Aug '19

29 Aug '19

Hello Everyone :) I am declaring my candidacy for the TC election. Roles like PTL and TC member are incredibly important when it comes to enabling others’ success and removing roadblocks that stand between contributors (new or established) and the work they want to do. Much of the work I have done over the years has had this focus, and as an elected member of the TC I think I could have an even larger impact. A little background on me: I have been working on OpenStack since 2015 (Liberty release). I started with getting involved organizing and mentoring in the Women of OpenStack’s mentoring programs and developing Cinder before branching out to os-brick and on to other roles. Since then, I have been involved in many different projects and efforts focused on supporting the larger community. Highlights: - Onboarded over 300 global contributors as instructor at OpenStack Upstream Institute (OUI) building our contributor community in places like Brazil, Korea, and Vietnam[1] - Developed the curriculum of OUI, including the Contributor Guide[2]. - Evolved OpenStack’s various mentoring programs[3] and actively participated in them, including our community’s involvement in the Outreachy Program[4]. - Established the First Contact SIG[5]. - Coordinated the community’s ongoing migration to StoryBoard from Launchpad - Presided over 5 releases of (Pike-Train) technical elections (both PTL and TC) as an election official - Served on the Release Management, Cinder, & Infrastructure (StoryBoard) teams - Helped organize Forums, PTGs, and other in-person gatherings - Collaborated with the k8s community to improve both our community’s various onboarding programs My experience teaching Upstream Institute and running the First Contact SIG has helped me build skills that will be beneficial as a TC member, such as making connections between new contributors and existing projects or efforts. This ability to make connections and start conversations will support our community’s cross project efforts as they continue to be a challenge that I will help the TC overcome. My previous work has afforded me the opportunity to interact with almost every OpenStack project and understand how they operate differently from one another. Each project has its own culture; understanding that and how to engage with each of them is incredibly important for the Technical Committee to achieve selected community goals and other cross project efforts. As a member of the TC, I will seek to lower the barrier to entry to roles like contributor or even PTL. There is a lot of duplicate and stale information for setting up the accounts and tools needed to get started which should be cleaned up. Individual project contributor documentation[6][7] doesn’t exist for all the projects currently and would be valuable. Individual project PTL guides (similar to the Release Management process doc[8]) would also benefit our community as it would smooth the transition from one PTL to another and minimize the loss of tribal knowledge, especially when these transitions happen in the middle of a cycle. I’ve proposed this contributor documentation focus as a community goal for the U release[9]. Anything we can do to make a cohesive path for new community members to work their way to roles like PTL will ensure the health and success of our future. I love this community and all the awesome people in it, serving on the TC would be a great experience and an honor. Thank you, Kendall Review history: https://review.opendev.org/#/q/reviewer:16708,n,z Commit history: https://review.openstack.org/#/q/owner:16708,n,z Foundation Profile: https://www.openstack.org/community/members/profile/35859/ Freenode: diablo_rojo [1] https://docs.openstack.org/upstream-training/ [2] https://docs.openstack.org/contributors/ [3] https://wiki.openstack.org/wiki/Mentoring [4] https://www.outreachy.org/ [5] https://wiki.openstack.org/wiki/First_Contact_SIG [6] https://docs.openstack.org/swift/latest/development_guidelines.html [7] https://docs.openstack.org/nova/latest/contributor/index.html [8] https://releases.openstack.org/reference/process.html [9] https://etherpad.openstack.org/p/PVG-u-series-goals

2 1

[openstack-dev] [neutron] Cancelling Neutron Drivers meeting on August 30th
by Miguel Lavalle 29 Aug '19

29 Aug '19

Dear Neutrinos, It turns out that this week we still have 3 out of 5 members of the drivers team off on vacation, so we won't have quorum for the meeting again. As a consequence, I am cancelling this week once more. We will resume on September 9th at the usual time. Best regards

1 0

Re: [User-committee] UC candidacy.
by Ian Y. Choi 29 Aug '19

29 Aug '19

Hello Natal, First of all, thanks a lot for your UC candidacy! UC election is applicable for Active User Contributors (AUCs) as defined by OpenStack User Committee Charter [1], and I would like to share that both UC election officials could not verify that you are an AUC. If you can share more details which support to verify that you are an AUC who is eligible for the election, please do not hesitate to share with the election officials before the due of the nomination period. Although the election officials could not confirm that you are an eilgible candidacy for the election, I am pretty sure that you can become AUC later, and can run for next UC election(s). With many thanks, /Ian [1] https://governance.openstack.org/uc/reference/charter.html#active-user-cont… Natal Ngétal wrote on 8/26/2019 9:29 PM: > Hi, > > I saw a mail on openstack-discuss about the new user committee election. I'm > Natal I principally contribute to the tripleo part. I have also contribute a > little to oslo projects and gertty, for example. I'm really interested to > candidate for this post, that can be seems weird, because I have started to > contribute in october 2018 only. But I think that can be interesting for the > project, a new eyes. I wish to implicate me more in the community. For example, > I want to organize local meetup regularly, go to the OpenStack summit and ptg > and started to give talk and write articles on the project. I wish also meet > more the customers and work with they to improve the project. Understand the > customers problems. With this role that can be more easy. For me, that can be > also really interesting to learn more the project and the community. That can > be also really source motivation and that can help me for my work. > > My gerrit profile: > > https://review.opendev.org/#/q/owner:hobbestigrou%2540erakis.eu > > > Thanks > > _______________________________________________ > User-committee mailing list > User-committee(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee

3 3

[Openstack][Swift] : Swift file-storage allocation policy
by Sai Vishwas 29 Aug '19

29 Aug '19

Hi all, I have the following questions regarding the file allocation policy in Openstack Swift: 1. Are the uploaded files/objects mapped to partitions solely based on the name by hashing? Is there any way that I could force a particular file to reside on a particular disk? 2. How are the partitions mapped to disks? Is there any way that I could force a particular partition to reside on a particular disk? 3. Are the sizes of all partitions the same? (I am aware that a partition is a virtual concept but I am interested in whether a limit is placed on how many files are assigned to a particular partition ) I am asking the above questions as I have a few files which are accessed very frequently and would like them to reside on one of the SSDs that we have. Does OpenStack Swift internally provide this option? If not how does Swift accommodate for such SLA bound requirements without violating the concept of partitions? It would be of great help if you could explain the internal working of swift with respect to this scenario. Regards, Sai Vishwas Padigi

2 1

[release] Release countdown for week R-6, September 2-6
by Sean McGinnis 29 Aug '19

29 Aug '19

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on September 05. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/train branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/…) In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (September 12) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, September 12. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/train branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/train branches are cut for a repo, the ability to approve any necessary backports into those branches for train will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please each out in the #openstack-stable channel. Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to Feature freeze on September 12. Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… knelson [at] openstack.org/diablo_rojo on IRC is available if you need help selecting or writing your highlights Upcoming Deadlines & Dates -------------------------- Non-client library freeze: September 05 (R-6 week) Client library freeze: September 12 (R-5 week) Train-3 milestone (feature freeze): September 12 (R-5 week) RC1 deadline: September 26 (R-3 week) Train final release: October 16 Forum+PTG at Shanghai summit: November 4

1 0

[neutron][election] PTL candidacy
by Slawek Kaplonski 29 Aug '19

29 Aug '19

Hi, I want to propose my candidacy for Neutron PTL. I have worked with OpenStack since the Havana release, first as a user and operator and later on as an upstream developer mostly focused on Neutron. I was appointed to the Neutron core team in the Queens cycle and joined the Neutron Drivers last September. I participated very actively and led the QoS sub-team and currently lead the project's CI group, focusing on identifying bugs and keeping our gate jobs squeaky clean. During my involvement with Neutron, I have been employed by an OpenStack operator, OVH, and one of the big distributions, Red Hat. This experience allows me to bring to the project a blend of operational and product development perspective. I think that my experience uniquely positions me to serve as an effective Neutron PTL. My priorities to focus on as a PTL are: * I would like to continue the team effort on merging the ML2/OVS+DVR solution with networking-ovn - it is quite a new initiative, described in https://review.opendev.org/#/c/658414/ which I want to continue in the next cycle. OVN backend in OpenStack scales better than Neutron’s current default solution with openvswitch agent. It already have some features which we are missing in core Neutron, like DVR based on OpenFlow, enabling DVR for OVS DPDK. OVN is also becoming more prominent backend in e.g. Kubernetes and is more and more popular with OpenStack operators. I think that we should use this momentum and finally include OVN as one of in-tree backends in Neutron, and consider it as a default at some future point. * Improve overall stability of our CI - we already did a lot of improvements in this area but I think that we must continue the effort in order to provide developers a great overall experience and the highest possible speed when working on new features. * Improve test coverage for existing features - this is very important to avoid regressions and find bugs in existing features. Stability of existing Neutron features is very important for users and operators and we, as developers should focus on this maybe even more than on providing new features. * Finish the transition to the new engine facade - it is a long standing blueprint already and we should focus to finally finish this transition and use the new engine facade everywhere in Neutron. * Improve stability of Neutron when it is running under uWSGI - since a couple of cycles ago we have the possibility to run Neutron in this way but it is not the default yet. We have some CI jobs to test Neuton in this configuration but those jobs are non-voting and quite unstable still. So I would like to make those jobs more stable and voting. I think that Miguel did a great job in the last four cycles as Neutron’s PTL and I would like to continue his work and his way of managing the team, like e.g. mentoring potential new core reviewers. I think that currently we have a pretty stable and good team, with quite enough number of cores so my goal is to keep it in good shape. Helping onboard new contributors is critical to the growth and success of our community and will be a priority during my tenure. — Slawek Kaplonski Senior software engineer Red Hat

1 0

[PTLs] [i18n] Call for help for Project Onboarding in Shanghai
by Jimmy McArthur 29 Aug '19

29 Aug '19

Hi everyone! We'd like to suggest that PTLs/presenters of Project Onboarding find a buddy to do Chinese translation in the room in Shanghai. We're hoping some local volunteers will step up to pair with each project. I've set up an etherpad here so community members can sign up to volunteer: https://etherpad.openstack.org/p/Shanghai_Project_Onboarding_Translation PTLs, if you know someone within your project that can help, please add them to the list. Cheers, Jimmy

1 0

How to prevent adding admin-role?
by Tavasti Markku EXT 29 Aug '19

29 Aug '19

Hi! I am trying to create 'domain admin' role which has permissions to create projects and users, and manage user roles in projects within own domain. I have pretty ok working set of policies done, but there is one critical security hole: domain admin can add 'admin' role to user, and after it user has superuser privileges. Is there any possibility to limit domain admin rights to give only _member_ roles? I am working in Queens-based Redhat OSP13. Tavasti, Openstack admin For Internal Use Only

2 3

[OSSA-2019-004] Ageing time of 0 disables linuxbridge MAC learning (CVE-2019-15753)
by Jeremy Stanley 29 Aug '19

29 Aug '19

================================================================= OSSA-2019-004: Ageing time of 0 disables linuxbridge MAC learning ================================================================= :Date: August 29, 2019 :CVE: CVE-2019-15753 Affects ~~~~~~~ - Os-vif: >=1.15.0<1.15.2, 1.16.0 Description ~~~~~~~~~~~ James Denton with Rackspace reported a vulnerability in os-vif, the Nova/Neutron network integration library. A hard-coded MAC ageing time of 0 disables MAC learning in linuxbridge, forcing obligatory Ethernet flooding for non-local destinations which both impedes network performance and allows users to possibly view the content of packets for instances belonging to other tenants sharing the same network. Only deployments using the linuxbridge backend are affected. Patches ~~~~~~~ - https://review.opendev.org/678098 (Stein) - https://review.opendev.org/672834 (Train) Credits ~~~~~~~ - James Denton from Rackspace (CVE-2019-15753) References ~~~~~~~~~~ - https://launchpad.net/bugs/1837252 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15753 -- Jeremy Stanley, on behalf of the OpenStack VMT

1 0

CEPH/RDMA + Openstack
by Volodymyr Litovka 29 Aug '19

29 Aug '19

Dear colleagues, does anyone have experience using RDMA-enabled CEPH with Openstack? How stable is it? Whether all Openstack components (Nova, Cinder) works with such specific configuration of Ceph? Any issues which can affect overall system reliability? Thank you. -- Volodymyr Litovka "Vision without Execution is Hallucination." -- Thomas Edison

3 6

[blazar] No IRC meeting today
by Pierre Riteau 29 Aug '19

29 Aug '19

Hello, I won't be able to chair the biweekly Blazar IRC meeting today. The next scheduled meeting is on September 12. Cheers, Pierre

1 0

[neutron][ovn] networking-ovn plugin support for multiple remote ovsdb-server
by Zufar Dhiyaulhaq 29 Aug '19

29 Aug '19

Hi All, I have testing OpenStack (Queens Version) with OVN and works, but when I want to cluster the ovsdb-server, OpenStack stuck to create neutron object. based on my discussion in openvswitch mailing list ( https://mail.openvswitch.org/pipermail/ovs-discuss/2019-August/049175.html) my ovsdb-server clustering databases are working. Is networking-ovn support to connect to multiple ovsdb-server? something like this in ml2_conf.ini [ovn] ovn_nb_connection = tcp:10.101.101.100:6641,tcp:10.101.101.101:6641,tcp: 10.101.101.102:6641 ovn_sb_connection = tcp:10.101.101.100:6642,tcp:10.101.101.101:6642,tcp: 10.101.101.102:6642 networking-ovn-metadata-agent.ini [ovn] ovn_sb_connection = tcp:10.101.101.100:6642,tcp:10.101.101.101:6642,tcp: 10.101.101.102:6642 Below is the full step to create ovsdb-server and neutron services. - step 1: bootstrapping ovsdb-server cluster : http://paste.openstack.org/show/766812/ - step 2: creating neutron service in controller : http://paste.openstack.org/show/766464/ - step 3: creating neutron service in compute : http://paste.openstack.org/show/766465/ But when I try to create neutron resource, Its always hang (only neutron resource). This is the full logs of all nodes, contain: http://paste.openstack.org/show/766461/ - all openvswitch logs - port (via netstat) - step bootstraping ovsdb-server Neutron logs in controller0: paste.openstack.org/show/766462/ Is networking-ovn support to connect to multiple ovsdb-server? Best Regards, Zufar Dhiyaulhaq

1 0

[Mistral] PTL candidacy
by Renat Akhmerov 29 Aug '19

29 Aug '19

Hi, I'd like to announce my PTL candidacy for Mistral in U cycle. In Train, we again made a big step towards having better performance, which turned to be very important for real production use cases. Mistral “join” mechanism is now much more CPU and RAM efficient (60-70% faster for same workflows). Mistral now also provides a mechanism to plug in an alternative scheduler implementation. The new implementation of scheduler, which designed to be more scalable, is now available and being tested. For U cycle I'd like to focus on making Mistral more usable: * Consistent and well-structured documentation * Additional tools that simplify creating custom actions and functions for Mistral * Easier debugging of workflow errors * Easier and smoother installation process Some of the mentioned activities are already going on. For example, we added the workflow execution report that, when requested, shows the entire execution tree (including sub workflows). That allows to see error paths (and hence root causes) w/o having to do many copy-paste actions. It's not a secret that in the last few cycles there was a struggle with attracting more active contributors. Now, we finally have several very talanted engineers fully allocated to work on Mistral. So it makes me believe that we'll be able to solve a number of big tasks (including cool user facing goodies) that we had to put on a shelve just for the lack of resources. As usually, anybody is welcome to join our team! It's a fun project to work on. The best way to get in touch with us is IRC channel #openstack-mistral or the openstack-discuss mailing list (with [mistral] tag in email subject). Renat [1] https://review.opendev.org/#/c/679191

1 0

[neutron][ovn] networking-ovn plugin support for multiple remote ovsdb-server
by Zufar Dhiyaulhaq 29 Aug '19

29 Aug '19

[neutron][ovn] networking-ovn plugin support for multiple remote ovsdb-server Hi All, I have testing OpenStack (Queens Version) with OVN and works, but when I want to cluster the ovsdb-server, OpenStack stuck to create neutron object. based on my discussion in openvswitch mailing list ( https://mail.openvswitch.org/pipermail/ovs-discuss/2019-August/049175.html) my ovsdb-server clustering databases are working. Are networking-ovn support to connect to multiple ovsdb-server? something like this in ml2_conf.ini [ovn] ovn_nb_connection = tcp:10.101.101.100:6641,tcp:10.101.101.101:6641,tcp: 10.101.101.102:6641 ovn_sb_connection = tcp:10.101.101.100:6642,tcp:10.101.101.101:6642,tcp: 10.101.101.102:6642 networking-ovn-metadata-agent.ini [ovn] ovn_sb_connection = tcp:10.101.101.100:6642,tcp:10.101.101.101:6642,tcp: 10.101.101.102:6642 Below is the full step to create ovsdb-server and neutron services. - step 1: bootstrapping ovsdb-server cluster : http://paste.openstack.org/show/766812/ - step 2: creating neutron service in controller : http://paste.openstack.org/show/766464/ - step 3: creating neutron service in compute : http://paste.openstack.org/show/766465/ But when I try to create neutron resource, Its always hang (only neutron resource). This is the full logs of all nodes, contain: http://paste.openstack.org/show/766461/ - all openvswitch logs - port (via netstat) - step bootstraping ovsdb-server Neutron logs in controller0: paste.openstack.org/show/766462/ Are networking-ovn support to connect to multiple ovsdb-server? Best Regards, Zufar Dhiyaulhaq

1 0

[ptl][zaqar][election]WangHao's candidacy for Zaqar PTL in U cycle
by hao wang 28 Aug '19

28 Aug '19

Hi all, I would like to announce my candidacy for Zaqar PTL for U I've been PTL for Zaqar for two cycles(Rocky and Stein), I still want to serve this project in the new cycle, so there is my self-nomination: In U release, we will continue our works in: 1) Keep the Zaqar health and stable 2) Continue to support more backends for topic resource 3) Consider removing the old API code and let it more clearly. 4) Support sms subscription in Zaqar Thanks for your consideration!

1 0

[ptl][searchlight][election] Trinh Nguyen's candidacy for Searchlight PTL in U cycle
by Trinh Nguyen 28 Aug '19

28 Aug '19

Hello. I would like to announce my candidacy for Searchlight PTL for U. I've been the PTL for Searchlight for the last two cycles (Stein and Train) which I believe have been giving me enough understanding and confidence to help to maintain it for at least one more release. Even though there was not much activity of Searchlight in the Train cycle, as I surveyed people and companies around my circle, there're still needs for a centralized resource indexing service as well as multi-cloud support as we laid out [1] in the use cases and vision documents [2]. Moreover, with a simple architecture and well-defined contributing process, I strongly think Searchlight would be a good starting point for future OpenStack contributors. Therefore, Searchlight has good reasons to live one. My jobs as a PTL for Searchlight in the U cycle as I envisioned are: * Welcome and help new contributors * Help to make Searchlight work with ElasticSearch 6.x, 7.x * Finish on-going blueprints and fix bugs Thank you for your consideration. Trinh Nguyen (dangtrinhnt) [1] https://docs.openstack.org/searchlight/latest/user/usecases.html [2] https://docs.openstack.org/searchlight/latest/contributor/searchlight-visio… -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

1 0

[election][ptl][magnum] PTL Candidacy
by feilong 28 Aug '19

28 Aug '19

Greeting, Over the last release, I have had the privilege and honor to serve as the PTL of Magnum. I would like to take this opportunity to express my appreciation for all your support and contribution to Magnum. And I look forward to working with you all over the next release. Therefore, I would like announce my candidacy to serve as the Magnum project team leader for the U cycle, if you will have me. In case if you don't know me, I've been working on and contributing to Magnum since Queens release as a core developer. And I have done a lot work for Magnum to help it getting production ready, e.g. the Calico network driver, nodes anti affinity, k8s health status check, Keystone auth, coreDNS autoscale, rolling upgrade, auto scaling, auto healing, private cluster, getting Magnum certified by CNCF and etc, etc. That said, I really understand the ups and downs which Magnum went through and I know the blueprints, direction and pains of this project, for interests from both private cloud and public cloud sides, which make me a good candidate for the PTL position. For U release (including the rest of Train cycle), things I'd like to do: 1. Fedora CoreOS The most matured driver for Kubernetes in Magnum is Fedora Atomic, however, the Fedora community is moving to Fedora CoreOS, so we should start to think about the migration. We have started the work but haven't finished it due to the limited resource among the team. This need to be done in Train or early of U cycle. 2. Node groups Node groups provide users with the ability to specify groups of nodes with different properties for different purposes. Within the scope of a group users are able to define labels, used image, flavor, etc depending on the purpose. We have merged part of this huge feature, but we do need to finish the rest of the work. 3. Security hardening Security is always the most important area we would like to improve for Magnum, there are still parts we need to improve to make Magnum more securer. 4. Containerize Kubernetes master This could be one of the most interesting features for Magnum and it's definitely hard work. Running Kubernetes master nodes in a seed/root Kubernetes could bring us a lot of benefits. 5. Rolling upgrade for node operating system With the big support from CERN, We have done the k8s version rolling upgrade, but we still need the rolling upgrade work for node operating system. I have already got a patch for that being reviewed now. It has been a fantastic experience working with this amazing team and I know without the dedication and hard work of everyone who has contributed to Magnum we can't get those good work done. So the PTL of this cool team is most like a facilitator, coordinator, and mentor. I would be pleased to serve as PTL for Magnum for the U cycle and I'd appreciate your vote. Thanks for your consideration! -- Cheers & Best regards, Feilong Wang (王飞龙) ------------------------------------------------------ Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang(a)catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------

1 0

[all] [tc] [osc] [glance] [train] [ptls] Legacy client CLI to OSC review 639376
by Alexandra Settle 28 Aug '19

28 Aug '19

Hi all, For the Train cycle Artem Goncharov proposed moving the legacy client CLIs to OSC. This goal did not move forward due to a broad range of concerns and was eventually -1'd by Erno Kuvaja (Glance PTL) as he was unable to support it from a Glance point of view. Moving forward, I'd like to end the discussion in the review [1] by abandoning the patch and move this to the mailing list. The following looks like it needs to happen: 1. This PR should be abandoned. It is not going to be accepted as a commmunity goal in this format and the debate within the comments is circular. Let's step out of here, and start having conversation elsewhere. 2. To start those conversations, a pop-up team would be a suitable alternative to begin driving that work. Someone needs to step forward to lead the pop-up team. The TC recommends two individuals step forwards as indicated in the pop-up team Governance document [2]. 3. I recommend the pop-up team include Erno Kuvaja or a representative from the Glance team and including Matt Reidemann (who has been working to close the compute API gaps). 4. The leaders must then identify a clear objective, and a clear disband criteria. If in case the pop-up team decide that this could be better drafted as a community goal for U, then that is a suitable alternative that can be defined using the new goal selection criteria that is being defined here [3] But this should not be decided before clear objectives are defined. Thanks, Alex IRC: asettle [1] https://review.opendev.org/#/c/639376/ [2] https://governance.openstack.org/tc/reference/popup-teams.html [3] https://review.opendev.org/#/c/667932/

8 10

[ptl][tripleo][election] PTL Candidacy
by Wesley Hayutin 28 Aug '19

28 Aug '19

Greetings, I would like to nominate myself for the TripleO PTL role for the U cycle. I have been working closely with several previous PTL's like Alex, Emilien and Juan Osorio and I am hoping to contribute back to the community as a PTL while following their excellent example. I would like to see Tripleo continue focusing on simplification and improving the user experience. Specifically continue the path set in previous TripleO cycles. - Push forward with tripleo-ansible and the transformation squad. - Work with the newly formed ansible sig group. - Help continue to simplify the stack of components where possible. - Help with new features like the undercloud minion node. - Continue to support the wider adoption of the Tripleo Single Node deployment as a development and test tool. - Continue the great work being done to clean up logging and error handling to improve operators ability to troubleshoot their installations. Thank you for the opportunity! Thanks, Wes Hayutin irc: weshay

1 0

[tripleo] TripleO CI Summary: Sprint 35
by Rafael Folco 28 Aug '19

28 Aug '19

Greetings, The TripleO CI team has just completed Sprint 35 / Unified Sprint 14 (Aug 08 thru Aug 28). The following is a summary of completed work during this sprint cycle: - Completed testing on the RHEL8 OVB featureset 001 job and added it to the periodic pipeline. - Added RHEL8 scenario{1-4} jobs to the periodic pipeline as non-voting. - Completed the design for staging environment as a zuul job for testing changes in the promoter server and also prepare for the multi-arch builds. - Created a staging promoter job and started implementing functional tests on molecule for the staging environment setup. - Completed a PoC for multi-arch container builds with tagging and manifests approach. The change [3] on build-containers role that introduces arch aware tagging is still under review. - Promotion status: green on all branches for most of the sprint cycle. - Removed Fedora and Pike jobs everywhere. - Bumped ansible to version 2.8 across tripleo ci jobs. The planned work for the next sprint [1] are: - Address issues for scenario{1-4} jobs for RHEL8 in the periodic pipeline and get jobs to green status. - Merge multi-arch container tagging support and change the promoter code to push manifests with annotated metadata for architecture in addition to the arch tagged containers strategy. - Implement the staging promoter job for testing changes in the promotion workflow. - Create functional test cases for the staging promoter setup using molecule. - Design a staging promotion workflow to emulate promotions using mock containers and test servers. The Ruck and Rover for this sprint are Gabriele Cerami (panda) and Sagi Shnaidman (sshnaidm). Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Ruck/rover notes are being tracked in etherpad [2]. Thanks, rfolco [1] https://tree.taiga.io/project/tripleo-ci-board/taskboard/unified-sprint-15 [2] https://etherpad.openstack.org/p/ruckroversprint15 [3] https://review.opendev.org/#/c/663977/

1 0

[oslo] Reminder: Feature Freeze is this Friday
by Ben Nemec 28 Aug '19

28 Aug '19

This is your friendly neighborhood PTL reminding you that if you need a feature to merge in Oslo this cycle, it should be in by this Friday. We feature freeze earlier than other projects so they have a chance to make use of any features we add before their feature freeze. After Friday, any new features in Oslo will require an exception from me. I don't see much in the way of feature reviews open against Oslo right now (at least none that are mergeable), but if I missed anything let me know. Thanks. -Ben

1 0

[requirements][placement] orjson instead of stdlib json
by Chris Dent 28 Aug '19

28 Aug '19

Requirements people: For the past few months we've been doing profiling of placement, modeling large clouds where many results (7000 resource providers) will be returned in response to common requests. One of the last remaining chunks of slowness is serializing the very large dicts representing those providers (and associated allocation requests) to JSON (greater than 100k lines when pretty printed). Using the oslo jsonutils (which is a light wrapper over the stdlib 'json' module) approximately 25% of time is consumed by dumps(). Using orjson [1] instead, time consumption drops to 1%, so this is something it would be good to make real in placement (and perhaps other projects that have large result sets). There's a WIP that demonstrates its use at [2]. I'm posting about it because JSON serialization seems like it might be an area that the requirements team has greater interest than some other areas. Also, orjson is only Python 3, so use needs to be adapted for Python 2, as shown in the WIP [2]. Otherwise it's fine: active, Apache2 or MIT license. Thoughts? [1] https://pypi.org/project/orjson/ [2] https://review.opendev.org/#/c/674661/ -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent

7 9

Re: [openstack-dev] Dropping lazy translation support
by Shengjing Zhu 28 Aug '19

28 Aug '19

Sorry for replying the old mail, and please cc me when reply. Matt Riedemann <mriedemos at gmail.com> writes: > This is a follow up to a dev ML email [1] where I noticed that some > implementations of the upgrade-checkers goal were failing because some > projects still use the oslo_i18n.enable_lazy() hook for lazy log message > translation (and maybe API responses?). > > The very old blueprints related to this can be found here [2][3][4]. > > If memory serves me correctly from my time working at IBM on this, this > was needed to: > > 1. Generate logs translated in other languages. > > 2. Return REST API responses if the "Accept-Language" header was used > and a suitable translation existed for that language. > > #1 is a dead horse since I think at least the Ocata summit when we > agreed to no longer translate logs since no one used them. > > #2 is probably something no one knows about. I can't find end-user > documentation about it anywhere. It's not tested and therefore I have no > idea if it actually works anymore. > > I would like to (1) deprecate the oslo_i18n.enable_lazy() function so > new projects don't use it and (2) start removing the enable_lazy() usage > from existing projects like keystone, glance and cinder. > > Are there any users, deployments or vendor distributions that still rely > on this feature? If so, please speak up now. I was pointed to this discussion when I tried to fix this feature in keystone, https://review.opendev.org/677117 For #2 translated API response, this feature probably hasn't been working for some time, but it's still a valid user case. Has the decision been settled? -- Regards, Shengjing Zhu

3 4

[openstack-ansible] weekly update
by Mohammed Naser 28 Aug '19

28 Aug '19

Hi everyone, Here’s the update of what happened in this week’s OpenStack Ansible Office Hours. - The uwsgi role is mostly done but there’s an issue with ansible-lint checks so we’re thinking of moving it to the integrated repository and towards using collections in the long term. - We’re still working on the os_murano role. - We finally fixed Rocky POST_FAILURES (thanks infra!) - Rabbit and Galera are still stuck on bind-to-mgmt work.. - We will also need new code in order to build images in test jobs for Octavia since right now they’re only usable in Master. Thanks! Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0