- openstack-discuss - lists.openstack.org

[Ansible] European Ansible Cntributors Summit
by Amy Marrich 03 Feb '20

03 Feb '20

This was shared on the OpenStack-Ansible channel this morning and I wanted to share with everyone using Ansible who might be interested in attending. https://groups.google.com/forum/#!topic/ansible-outreach/sLte90d5hdc Thanks, Amy (spotz)

1 0

[neutron] Bug Deputy Report Jan. 27 - Feb. 3
by Ryan Tidwell 03 Feb '20

03 Feb '20

Here's this week's bug report for neutron: https://bugs.launchpad.net/neutron/+bug/1861269 Functional tests failing due to failure with getting datapath ID from ovs Fix merged to master, backports in progress https://review.opendev.org/705401 https://review.opendev.org/705400 https://review.opendev.org/705399 https://review.opendev.org/705398 https://bugs.launchpad.net/neutron/+bug/1861442 QOS minimum bandwidth rejection of non-physnet network and updates should be driver specific This was discussed in the drivers meeting. The short-term plan is move where validation is done, then there is likely an RFE to tackle once this fixed. https://bugs.launchpad.net/neutron/+bug/1861496 All ports of server instance are open even no security group does allow this This one is worth a look as it involves security groups potentially not filtering things as expressed by the user. I asked a follow-up question in launchpad, others should chime in. https://bugs.launchpad.net/neutron/+bug/1861502 [OVN] Mechanism driver - failing to recreate floating IP Some errors related to the OVN ML2 driver are being observed in the gate "TypeError: create_floatingip() missing 1 required positional argument: 'floatingip'" https://bugs.launchpad.net/neutron/+bug/1861670 AttributeError: 'NetworkConnectivityTest' object has no attribute 'safe_client' Fix proposed - https://review.opendev.org/#/c/705413/ https://bugs.launchpad.net/neutron/+bug/1861674 Gateway which is not in subnet CIDR is unsupported in ha router This could use some follow-up by the team for clarification Some OVN scheduler-related issues: [OVN] GW rescheduling mechanism is triggered on every Chassis updated unnecessarily https://bugs.launchpad.net/bugs/1861510 Some PoC code up for review - https://review.opendev.org/#/c/705331/ https://bugs.launchpad.net/bugs/1861509 [OVN] GW rescheduling logic is broken RFE's: https://bugs.launchpad.net/neutron/+bug/1861032 Add support for configuring dnsmasq with multiple IPv6 addresses in same subnet on same port https://bugs.launchpad.net/neutron/+bug/1861529 A port's network should be changable -Ryan

1 0

Re: [magnum] Help / Pointers on mirroring https://opendev.org/starlingx in github.com for CNCF certification of starlingx
by Roman Gorshunov 03 Feb '20

03 Feb '20

Hello Bin, Yes, that's correct. When you are connecting to the GitHub, your username should be git. GitHub recognizes you by your SSH key [0]. Example: [roman@pc ~]$ ssh git(a)github.com PTY allocation request failed on channel 0 Hi gorshunovr! You've successfully authenticated, but GitHub does not provide shell access. Connection to github.com closed. [roman@pc ~]$ As you may see, GitHub has recognized me as 'gorshunovr', despite I was using 'git' as a username for SSH. [0] https://help.github.com/en/github/authenticating-to-github/testing-your-ssh… Please, use mailing list for the communication, not direct e-mail. Thank you. Best regards, -- Roman Gorshunov On Mon, Feb 3, 2020 at 3:53 PM Qian, Bin <Bin.Qian(a)windriver.com> wrote: > > Hi Roman, > > Thank you for the information about GitHub mirroring. > Based on the info below, I think what we want to do is to: > 1. create a GitHub account, which has the privilege to commit to our repos, > 2. with the account, create ssh key on zuul server and upload the ssh key to GitHub > 3. use zuul tool [3] to create zuul job secret, embed it to the upload job in zuul.yaml > 4. add the upload job a post job > > But I am not very sure about the step 1, as in the reference [4] below, it states, > "For GitHub, the user parameter is git, not your personal username." > > Would you please let me know if my steps above is correct? > > Thanks, > > Bin > > ________________________________ > From: Waines, Greg > Sent: Thursday, January 30, 2020 10:21 AM > To: Qian, Bin > Cc: Eslimi, Dariush; Khalil, Ghada > Subject: FW: [magnum] Help / Pointers on mirroring https://opendev.org/starlingx in github.com for CNCF certification of starlingx > > fyi > > > > From: Roman Gorshunov <paye600(a)gmail.com> > Date: Thursday, January 30, 2020 at 11:38 AM > To: "openstack-discuss(a)lists.openstack.org" <openstack-discuss(a)lists.openstack.org> > Subject: Re: [magnum] Help / Pointers on mirroring https://opendev.org/starlingx in github.com for CNCF certification of starlingx > > > > Hello Greg, > > > > - Create a GitHub account for the starlingx, you will have URL on > > GitHub like [0]. You may try to contact GitHub admins and ask to > > release starlingx name, as it seems to be unused. > > - Then create SSH key and upload onto GitHub for that account in > > GitHub interface > > - Create empty repositories under [1] to match your existing > > repositories names here [2] > > - Encrypt SSH private key as described here [3] or here [4] using this tool [5] > > - Create patch to all your projects under [2] to '/.zuul.yaml' file, > > similar to what is listed here [6] > > - Change job name shown on line 407 via URL above, description (line > > 409), git_mirror_repository variable (line 411), secret name (line 414 > > and 418), and SSH key starting from line 424 to 463, to match your > > project's name, repo path on GitHub, and SSH key > > - Submit changes to Gerrit with patches for all your project and get > > them merged. If all goes good, the next change merged would trigger > > your repositories to be synced to GitHub. Status could be seen here > > [7] - search for your newly created job manes, they should be nested > > under "upload-git-mirrorMirrors a tested project repository to a > > remote git server." > > > > Hope it helps. > > > > [0] https://github.com/starlingxxxx > > [1] https://github.com/starlingxxxx/... > > [2] https://opendev.org/starlingx/... > > [3] https://docs.openstack.org/infra/manual/zuulv3.html#secret-variables > > [4] https://docs.openstack.org/infra/manual/creators.html#mirroring-projects-to… > > [5] https://opendev.org/zuul/zuul/src/branch/master/tools/encrypt_secret.py > > [6] https://opendev.org/airship/deckhand/src/commit/51dcea4fa12b0bcce65c381c286… > > [7] https://zuul.openstack.org/jobs > > > > Sample content of your addition (patch) to your '/.zuul.yaml' files: > > =================================================== > > - job: > > name: starlingx-compile-upload-git-mirror > > parent: upload-git-mirror > > description: Mirrors starlingx/compile to starlingxxxx/compile > > vars: > > git_mirror_repository: starlingxxxx/compile > > secrets: > > - name: git_mirror_credentials > > secret: starlingx-compile-github-secret > > pass-to-parent: true > > > > - secret: > > name: starlingx-compile-github-secret > > data: > > user: git > > host: github.com > > host_key: github.com ssh-rsa > > AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ== > > ssh_key: !encrypted/pkcs1-oaep > > - <here goes encrypted SSH private key> > > =================================================== > > > > Best regards, > > -- > > Roman Gorshunov > > > >

2 1

[qa] Proposing Radosław Piliszek to devstack core
by Ghanshyam Mann 03 Feb '20

03 Feb '20

Hello Everyone, Radosław Piliszek (yoctozepto) has been doing nice work in devstack from code as well as review perspective. He has been helping for many bugs fixes nowadays and having him as Core will help us to speed up the things. I would like to propose him for Devstack Core. You can vote/feedback on this email. If no objection by end of this week, I will add him to the list. -gmann

4 4

[Watcher] confused about meeting schedule
by info＠dantalion.nl 03 Feb '20

03 Feb '20

Hello everyone, The documentation for Watcher states that meetings will be held on a bi-weekly basis on odd-weeks, however, last meeting was held on the 8th of January which is not an odd-week. Today I was expecting a meeting as the meetings are held bi-weekly and the last one was held on the 8th of January, however, there was none. Can someone clarify when the next meeting will be held and the subsequent one after that? If these are on even weeks we should also update Watcher's documentation. Kind regards, Corne lukken

3 4

[openstack-dev][kuryr] How to add new worker node
by VeeraReddy 03 Feb '20

03 Feb '20

Hi , I successfully install kuryr-kubernetes using below linkhttps://docs.openstack.org/kuryr-kubernetes/latest/installation/devstac… How to add a new external worker node to existing controller node. Regards, Veera.

2 1

Kayobe Openstack deployment
by Tony Pearce 03 Feb '20

03 Feb '20

Hi all - I wanted to ask if there was such a reference architecture / step-by-step deployment guide for Openstack / Kayobe that I could follow to get a better understanding of the components and how to go about deploying it? The documentation is not that great so I'm hitting various issues when trying to follow what is there on the Openstack site. There's a lot of technical things like information on variables - which is fantastic, but there's no context about them. For example, the architecture page is pretty small, when you get further on in the guide it's difficult to contextually link detail back to the architecture. I tried to do the all-in-one deployment as well as the "universe from nothing approach" but hit some issues there as well. Plus it's kind of like trying to learn how to drive a bus by riding a micro-scooter :) Also, the "report bug" bug link on the top of all the pages is going to an error "page does not exist" - not sure that had been realised yet. Regards, *Tony Pearce* | *Senior Network Engineer / Infrastructure Lead**Cinglevue International <https://www.cinglevue.com>* Email: tony.pearce(a)cinglevue.com Web: http://www.cinglevue.com *Australia* 1 Walsh Loop, Joondalup, WA 6027 Australia. Direct: +61 8 6202 0036 | Main: +61 8 6202 0024 Note: This email and all attachments are the sole property of Cinglevue International Pty Ltd. (or any of its subsidiary entities), and the information contained herein must be considered confidential, unless specified otherwise. If you are not the intended recipient, you must not use or forward the information contained in these documents. If you have received this message in error, please delete the email and notify the sender.

2 3

[kolla] ujson issue affected to few containers.
by Eddie Yen 02 Feb '20

02 Feb '20

Hi everyone, I'm not sure it should be bug report or not. So I email out about this issue. In these days, I found the Rocky source deployment always failed at Ceilometer bootstrapping. Then I found it failed at ceilometer-upgrade. So I tried to looking at ceilometer-upgrade.log and the error shows it failed to import ujson. https://pastebin.com/nGqsM0uf Then I googled it and found this issue is already happened and released fixes. https://github.com/esnme/ultrajson/issues/346 But it seems like the container still using the questionable one, even today (Jan 30 UTC+8). And this not only affected to Ceilometer, but may also Gnocchi. I think we have to patch it, but not sure about the workaround. Does anyone have good idea? Many thanks, Eddie.

3 9

[horizon] [keystone] Re: [User-committee] Help
by Amy Marrich 01 Feb '20

01 Feb '20

Pradeep, I am sending this to the OpenStack discuss mailing list where you might be able to receive more help. I have tagged both the Horizon and Keystone teams as the error seems to be from Horizon and concerning Keystone. In order to provide more assistance, information as to what you were doing at the time will be needed. Please confirm this is OpenStack Rocky on CentOS and how you installed, from scratch, TripleO, OpenStack-Ansible, etc. Thanks, Amy (spotz) > On Feb 1, 2020, at 7:11 AM, pradeep pal <pspal83(a)hotmail.com> wrote: > > > Rocky+Centos 7.7 64bit, > > 2020-02-01 18:26:38.063938 ArgsAlreadyParsedError: arguments already parsed: cannot register CLI option > 2020-02-01 18:26:38.549453 mod_wsgi (pid=82228): Target WSGI script '/usr/bin/keystone-wsgi-public' cannot be loaded as Python module. > 2020-02-01 18:26:38.549516 mod_wsgi (pid=82228): Exception occurred processing WSGI script '/usr/bin/keystone-wsgi-public'. > 2020-02-01 18:26:38.549558 Traceback (most recent call last): > 2020-02-01 18:26:38.549600 File "/usr/bin/keystone-wsgi-public", line 54, in <module> > 2020-02-01 18:26:38.549666 application = initialize_public_application() > 2020-02-01 18:26:38.549695 File "/usr/lib/python2.7/site-packages/keystone/server/wsgi.py", line 24, in initialize_public_application > 2020-02-01 18:26:38.549763 name='public', config_files=flask_core._get_config_files()) > 2020-02-01 18:26:38.549799 File "/usr/lib/python2.7/site-packages/keystone/server/flask/core.py", line 149, in initialize_application > 2020-02-01 18:26:38.549862 keystone.server.configure(config_files=config_files) > 2020-02-01 18:26:38.549897 File "/usr/lib/python2.7/site-packages/keystone/server/__init__.py", line 28, in configure > 2020-02-01 18:26:38.549958 keystone.conf.configure() > 2020-02-01 18:26:38.549988 File "/usr/lib/python2.7/site-packages/keystone/conf/__init__.py", line 125, in configure > 2020-02-01 18:26:38.550040 help='Do not monkey-patch threading system modules.')) > 2020-02-01 18:26:38.550084 File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2501, in __inner > 2020-02-01 18:26:38.550137 result = f(self, *args, **kwargs) > 2020-02-01 18:26:38.550164 File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2776, in register_cli_opt > 2020-02-01 18:26:38.550225 raise ArgsAlreadyParsedError("cannot register CLI option") > 2020-02-01 18:26:38.550276 ArgsAlreadyParsedError: arguments already parsed: cannot register CLI option > > > > > _______________________________________________ > User-committee mailing list > User-committee(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee

2 1

[nova] I would like to add another option for cross_az_attach
by Kim KS 01 Feb '20

01 Feb '20

Hello all, In nova with setting [cinder]/ cross_az_attach option to false, nova creates instance and volume in same AZ. but some of usecase (in my case), we need to attach new volume in different AZ to the instance. so I need two options. one is for nova block device mapping and attaching volume and another is for attaching volume in specified AZ. [cinder] cross_az_attach = False enable_az_attach_list = AZ1,AZ2 how do you all think of it? Best, Kiseok

4 4

[cinder] last call for ussuri spec comments
by Brian Rosmaita 01 Feb '20

01 Feb '20

The following specs have two +2s. I believe that all expressed concerns have been addressed. I intend to merge them at 22:00 UTC today unless a serious issue is raised before then. https://review.opendev.org/#/c/684556/ - support volume-local-cache https://review.opendev.org/#/c/700977 - add backup id to volume metadata cheers, brian

3 3

"encoding error when doing console log show" in Rocky
by Albert Braden 31 Jan '20

31 Jan '20

We're running openstack-ansible Rocky and seeing the "encoding error when doing console log show." I see here that there is a patch: https://bugs.launchpad.net/python-openstackclient/+bug/1747862 How can I apply this patch to our Rocky install? Do I need to just copy the file over the existing /usr/lib/python2.7/dist-packages/openstackclient/compute/v2/console.py on controllers and hypervisors? Or is there a better way?

2 13

[tripleo] no rechecks
by Wesley Hayutin 31 Jan '20

31 Jan '20

Greetings, Hey folks we need a few patches to land before it's safe to blindly recheck. A few minor patches need to land before you can expect to get +1 from zuul in a lot of cases. We appreciate your patience while we resolve the issues. Thanks * TRIPLEO GATES ARE BROKEN* * need two patches to fix - * https://review.opendev.org/#/c/705051/ - * https://review.opendev.org/#/c/704885/ - * Also need - * https://review.rdoproject.org/r/#/c/24754/

1 1

[all][requirements][qa] zipp failing py3.5 again
by Radosław Piliszek 31 Jan '20

31 Jan '20

Folks, we are running circles here. [1] merged breaking zipp again for py3.5 The script which generates these proposals needs to learn python version constraints. Reproposed [2]. [1] https://review.opendev.org/705128 [2] https://review.opendev.org/705184 -yoctozepto

3 4

[ironic] An approach to removing WSME
by Steve Baker 31 Jan '20

31 Jan '20

I've put together a set of changes for removing WSME which involves copying just enough of it into ironic, and I think we need to have the conversation about whether this approach is desirable :) This git branch[1] finishes with WSME removed and existing tests passing. Here are some stats about lines of code (not including unit tests, calculated with cloc): 4500 wsme/wsme 6000 ironic/ironic/api master 7000 ironic/ironic/api story/1651346 In words, we need 1000 out of 4500 lines of WSME source in order to support 6000 lines of ironic specific API code. Switching to a replacement for WSME would likely touch a good proportion of that 6000 lines of ironic specific API code. If we eventually replace it with a new library I think it would be easier if the thing being replaced is inside the ironic source tree to allow for a gradual transition. So this approach could be an end in itself, or it could be a step towards the final goal. My strategy for copying in code was to pull in chunks of required logic while removing some unused features (like request pass-through and date & time type serialization). I also replaced py2/3 patterns with pure py3. There is likely further things which can be removed or refactored for simplicity, but what exists currently works. If there is enough positive feedback for this approach I'll start on unit test coverage for the new code. [1] https://review.opendev.org/#/q/topic:story/1651346

3 2

[oslo] AFK this week
by Ben Nemec 31 Jan '20

31 Jan '20

I am going to be out most or all of this week. If someone wants to run the meeting on Monday then feel free to have it without me again. I may not be back right away next week either. A lot of stuff is still to be determined at this point. -Ben

1 1

[keystone] Keystone Team Update - Week of 27 January 2020
by Vishakha Agarwal 31 Jan '20

31 Jan '20

# Keystone Team Update - Week of 27 January 2020 ## News ### User Support and Bug Duty Every week the duty is being rotated between the members. The person-in-charge for bug duty for current and upcoming week can be seen on the etherpad [1] [1] https://etherpad.openstack.org/p/keystone-l1-duty ## Open Specs Ussuri specs: https://bit.ly/2XDdpkU Ongoing specs: https://bit.ly/2OyDLTh ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 19 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 26 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ### Priority Reviews * Ussuri Roadmap Stories - Groups in keystone SAML assertion https://tree.taiga.io/project/keystone-ussuri-roadmap/us/33 https://review.opendev.org/#/c/588211/ Add openstack_groups to assertion - Add support for modifying resource options to CLI tool https://tree.taiga.io/project/keystone-ussuri-roadmap/us/53 https://review.opendev.org/#/c/697444/ Adding options to user cli * Community Goals https://review.opendev.org/#/c/699119/ [ussuri][goal] Drop python 2.7 support and testing python-keystoneclient * Special Requests https://review.opendev.org/#/c/703578/ Updating tox -e all-plugin command https://review.opendev.org/#/c/704736/ Remove six usage ## Bugs This week we opened 4 new bugs and closed 4. Bugs opened (4) Bug #1860478 (keystone:Low): fetching role assignments should handle domain IDs in addition to project IDs - Opened by Harry Rybacki https://bugs.launchpad.net/keystone/+bug/1860478 Bug #1860252 (keystone:Undecided): security problem，one user can change other user's password without admin - Opened by kuangpeiling https://bugs.launchpad.net/keystone/+bug/1860252 Bug #1861264 (keystone:Undecided): Help information should be returned when executing 'placement-status' alone - Opened by Eric Xie https://bugs.launchpad.net/keystone/+bug/1861264 Bug #1861279 (keystone:Undecided): incomplete instruction in "Install and configure" in keystone in https://docs.openstack.org/keystone/train/install/keystone-install-rdo.html - Opened by Arie Maron https://bugs.launchpad.net/keystone/+bug/1861279 Bugs closed (4) Bug #1860252 (keystone:Undecided) https://bugs.launchpad.net/keystone/+bug/1860252 Bug #1861264 (keystone:Undecided) https://bugs.launchpad.net/keystone/+bug/1861264 Bug #1856904 (keystone:Undecided): CADF Notifications are missing user name in initiator object - Fixed by Gage Hugo https://bugs.launchpad.net/keystone/+bug/1856904 Bug #1858012 (keystone:Undecided): List role assignments by role ID may leak extra system assignments outside of filter - Fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1858012 ## Milestone Outlook https://releases.openstack.org/ussuri/schedule.html Milestone 2 is in two weeks, which means spec freeze is coming up followed closely by feature proposal freeze. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

[cinder][nova] Migrating servers' root block devices from a cinder backend to another
by Jean-Philippe Méthot 30 Jan '20

30 Jan '20

Hi, We have a several hundred VMs which were built on cinder block devices as root drives which use a SAN backend. Now we want to change their backend from the SAN to Ceph. We can shutdown the VMs but we will not destroy them. I am aware that there is a cinder migrate volume command to change a volume’s backend, but it requires that the volume be completely detached. Forcing a detached state on that volume does let the volume migration take place, but the volume’s path in Nova block_device_mapping doesn’t update, for obvious reasons. So, I am considering forcing the volumes to a detached status in Cinder and then manually updating the nova db block_device_mapping entry for each volume so that the VM can boot back up afterwards. However, before I start toying with the database and accidentally break stuff, has anyone else ever done something similar? Got any tips or hints on how best to proceed? Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc.

7 10

[openstack-ansible][ansible-sig][tripleo] Openstack Ansible modules - update on progress, new meeting time
by Sagi Shnaidman 30 Jan '20

30 Jan '20

Hi, all because no people have been available in the meeting, I'll write a quick summary in ML. Agenda and progress are tracked here as usual: https://etherpad.openstack.org/p/openstack-ansible-modules 1. Because people had overlapping meetings I've created a poll for better meeting time. I think we can switch now to the bi-weekly meeting if no objections to it. The poll is here: https://xoyondo.com/dp/ITMGRZSvaZaONcz 2. We have the same coverage as we had in Ansible repository, so now we can start to improve our testing. It should include a matrix with various ansible versions and openstacksdk versions. We had already some issues with versions mismatch [1] Also we should start to do a better module design. 3. In case of critical patches to 2.9 and when openstack modules will be removed from Ansible repo, please submit patches directly to the 2.9-stable branch of Ansible. Confirmed that with Ansible folks. 4. The CI job in Ansible repository now is failing with a message about moving modules. I hope it won't block from 2.9 patches to land but will do more checking. But at least we've got attention to the fact modules are moving. 5. Jobs for pushing collections to ansible-galaxy are in progress and please review patches in the repo in your time: [1] https://review.opendev.org/705054 [2] https://review.opendev.org/#/q/project:openstack/ansible-collections-openst… -- Best regards Sagi Shnaidman

1 0

[ops] Federated Identity Management survey
by Colleen Murphy 30 Jan '20

30 Jan '20

Hello operators, A researcher from the University of Kent who was influential in the design of keystone's federation implementation has asked the keystone team to gauge adoption of federated identity management in OpenStack deployments. This is something we've neglected to track well in the last few OpenStack user surveys, so I'd like to ask OpenStack operators to please take a few minutes to complete the following survey about your usage of identity federation in your OpenStack deployment (even if you don't use federation): https://uok.typeform.com/to/KuRY0q The results of this survey will benefit not only university research but also the keystone team as it will help us understand where to focus our efforts. Your participation is greatly appreciated. Thanks for your time, Colleen (cmurphy)

1 3

[neutron][drivers team] Proposing Nate Johnston as drivers team member
by Slawek Kaplonski 30 Jan '20

30 Jan '20

Hi Neutrinos, I would like to propose Nate Johnston to be part of Neutron drivers team. Since long time Nate is very active Neutron's core reviewer. He is also actively participating in our Neutron drivers team meetings and he shown there that he has big experience and knowledge about Neutron, Neutron stadium projects as well as whole OpenStack. I think that he really deservers to be part of this team and that he will be great addition it. I will wait for Your feedback for 1 week and if there will be no any votes agains, I will add Nate to drivers team in next week. -- Slawek Kaplonski Senior software engineer Red Hat

5 5

[nova] API updates week 20-5
by Ghanshyam Mann 30 Jan '20

30 Jan '20

Hello Everyone, Please find the Nova API updates of this week. Please add if I missed any BPs/API related work. API Related BP : ============ COMPLETED: 1. Add image-precache-support spec: - https://blueprints.launchpad.net/nova/+spec/image-precache-support Code Ready for Review: ------------------------------ 1. Nova API policy improvement - Topic: https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh+(status:ope… - Weekly Progress: First set is merged and 4 APIs policy are ready to review. I will push more changes in this week. - Review guide over ML - http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008504.h… Specs are merged and code in-progress: ------------------------------ ------------------ 1. Non-Admin user can filter their instance by availability zone: - Topic: https://review.opendev.org/#/q/topic:bp/non-admin-filter-instance-by-az+(st… - Weekly Progress: Spec is just merged. 2. Boot from volume instance rescue - Topic: https://review.opendev.org/#/q/topic:bp/virt-bfv-instance-rescue+(status:op… - Weekly Progress: Code is in progress. WIP as of now. Spec Ready for Review or Action from Author: --------------------------------------------------------- 1. Support specifying vnic_type to boot a server -Spec: https://review.opendev.org/#/c/672400/ - Weekly Progress: As discussed in spec, this is something can be done via heat or other automation instead of doing it in nova. 2. Add action event fault details -Spec: https://review.opendev.org/#/c/699669/ - Weekly Progress: This seems good to go, it has two +2. 3. Allow specify user to reset password -Spec: https://review.opendev.org/#/c/682302/5 - Weekly Progress: One +2 on this but other are disagree on this idea. More discussion on review. 4. Support re-configure deleted_on_termination in server -Spec: https://review.openstack.org/#/c/580336/ - Weekly Progress: This is old spec and there is no consensus on this till now. Others: 1. None Bugs: ==== I will track the bug data from next report. 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

[NOVA] instance hostname vs display_name vs dns_name
by Volodymyr Litovka 30 Jan '20

30 Jan '20

Dear colleagues, I'm using DNS Integration and just faced an issue - after renaming instance, I can't bind port to the instance using new name: 1) I've created intances with name 'devel' 2) then I renamed it to devel (openstack server set --name packager devel) 3) when binding port with dns_name using new name ('packager' in my case), the following error appear: ERROR nova.api.openstack.wsgi PortNotUsableDNS: Port c3a92cf6-b49b-4570-b69b-0c23af1d1f94 not usable for instance 6aa78bd5-099e-4878-a5ac-90262505a924. Value packager assigned to dns_name attribute does not match instance's hostname devel and yes, record in DB still uses an old hostname: mysql> select display_name from instances where hostname='devel'; +--------------+ | display_name | +--------------+ | packager | +--------------+ 1 row in set (0.00 sec) and hostname remains the same (initial) regardless of any changes to display_name. I'm on Rocky. Is it bug or feature and are there ways to work around this? Thank you. -- Volodymyr Litovka "Vision without Execution is Hallucination." -- Thomas Edison

2 2

[goals][Drop Python 2.7 Support] Week R-15 Update (# 2.5 weeks left to complete)
by Ghanshyam Mann 29 Jan '20

29 Jan '20

Hello Everyone, Below is the progress on "Drop Python 2.7 Support" for R-15 week. Schedule: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html#sc… Highlights: ======== * Schedule is to finish the py2-drop from every deliverable (except requirement repo) by m-2 on R13. Only 2.5 weeks left to finish the work. * There are still cases where Tempest and plugins does not work due to py2 drops. New plan & option has been sent in separate ML thread [1] and work in progress. * Few services merged the patches but not all. If your project is in the below list, I request PTLs to review it on priority. Project wise status and need reviews: ============================ Phase-1 status: The OpenStack services have not merged the py2 drop patches: NOTE: This was supposed to be completed by milestone-1 (Dec 13th, 19). * Adjutant * Karbor * Masakari * Tacker * Qinling * Tricircle Phase-2 status: This is ongoing work and I think most of the repo have patches up to review. Try to review them on priority. If any query and I missed to respond on review, feel free to ping me in irc. * Open review: https://review.opendev.org/#/q/topic:drop-py27-support+status:open How you can help: ============== - Review the patches. Push the patches if I missed any repo. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012241.… -gmann

1 0

[largescale-sig] Meeting summary and next actions
by Thierry Carrez 29 Jan '20

29 Jan '20

Hi everyone, The Large Scale SIG held a meeting today. You can access the summary and logs of the meeting at: http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_si… Regarding progress on our "Documenting large scale operations" goal, we turned our collection of relevant articles more as a group background activity than an immediate TODO. The idea is more to remember to add links to the etherpad[1] when we come across relevant content. oneswig mentioned the list to the Scientific SIG, in hopes that it would trigger more entries. [1] https://etherpad.openstack.org/p/large-scale-sig-documentation On the "Scaling within one cluster, and instrumentation of the bottlenecks" goal, nobody filed a scaling story yet on the etherpad[2] set up to collect them. masahito produced a first draft of the oslo.metrics blueprint[3], up for the group review. Finally, oneswig signed up to prepare a show-and-tell about some investigation they have been doing in this area, for presentation at next meeting. [2] https://etherpad.openstack.org/p/scaling-stories [3] https://review.opendev.org/#/c/704733/ Between now and next meeting, group members should prioritize: - Reviewing oslo.metrics draft at https://review.opendev.org/#/c/704733/ and comment so that we can iterate on it - Reading page on golden signals at https://landing.google.com/sre/sre-book/chapters/monitoring-distributed-sys… Other action items: - oneswig to prepare show-and-tell for presentation at next meeting - ttx to add meeting to eavesdrop on a every-two-week cadence - all post short descriptions of what happens (what breaks first) when scaling up a single cluster to https://etherpad.openstack.org/p/scaling-stories The next meeting will happen on February 12, at 9:00 UTC on #openstack-meeting. Cheers, -- Thierry Carrez (ttx)

2 1