- openstack-discuss - lists.openstack.org

[swift] Erasure code hardware offloading
by Mark Kirkwood 22 May '20

22 May '20

Hi, Can Swift make use of an Erasure Code offload card (e.g https://community.mellanox.com/s/article/understanding-erasure-coding-offlo… regards Mark

2 1

[charms] Propose Aurelien Lourot for OpenStack Charms core
by Frode Nordahl 22 May '20

22 May '20

Hello all, I would like to propose adding Aurelien Lourot as core developer for the Charms project. -- Frode Nordahl

4 3

[release] Release countdown for week R-20, May 25 - 29
by Sean McGinnis 22 May '20

22 May '20

Welcome back to the release countdown emails! These will be sent at major points in the Victoria development cycle, which should conclude with a final release on October 16, 2020. Development Focus ----------------- At this stage in the release cycle, focus should be on planning the Victoria development cycle, assessing Victoria community goals and approving Victoria specs. General Information ------------------- Victoria is a 22 week development cycle, which is already underway. In case you haven't seen it yet, please take a look over the schedule for this release: https://releases.openstack.org/victoria/schedule.html By default, the team PTL is responsible for handling the release cycle and approving release requests. This task can (and probably should) be delegated to release liaisons. Now is a good time to review release liaison information for your team and make sure it is up to date: https://opendev.org/openstack/releases/src/branch/master/data/release_liais… By default, all your team deliverables from the Ussuri release are continued in the Victoria series with a similar release model. If you intend to drop a deliverable, or modify its release model, please do so before the victoria-1 milestone by proposing a change to the deliverable file at: https://opendev.org/openstack/releases/src/branch/master/deliverables/victo… Upcoming Deadlines & Dates -------------------------- Virtual Victoria PTG: June 1-5 Victoria-1 milestone: June 18

1 0

[neutron][operators]
by Dincer Celik 22 May '20

22 May '20

Hi, You know in public cloud world, most users prefer using VPCs (aka tenant networks for us), and when they need to connect two separate VPC, they have VPC peering functionality. For OpenStack, we have routers, RBACs, static routes and floating IPs, but there is nothing functioning like a real VPC peering. I see this was discussed at Stein PTG[1] under L3 topics but seems there is no progress about it. So I would like to ask what is the most common way to let two separate tenant networks under different accounts talk to each other? Thanks! Dincer [1] https://etherpad.opendev.org/p/neutron-stein-ptg

1 0

[charms] OpenStack Charms 20.05 release is now available
by Peter Matulis 21 May '20

21 May '20

The OpenStack Charms team is happy to announce the 20.05 charms release, introducing support for OpenStack Ussuri and Ceph Octopus on Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. This release also brings several new and valuable features to the existing OpenStack Charms deployments for Queens, Rocky, Stein, Train, Ussuri and many other stable combinations of Ubuntu + OpenStack. Please see the Release Notes for full details: https://docs.openstack.org/charm-guide/latest/2005.html == Highlights == * OpenStack Ussuri OpenStack Ussuri is now supported on Ubuntu 18.04 LTS (via UCA) and Ubuntu 20.04 LTS natively. * Ceph Octopus The Octopus release of Ceph is now supported, starting with OpenStack Ussuri. * New charms: MySQL 8 The MySQL 8 charms (mysql-innodb-cluster and mysql-router) have been promoted to supported status. These charms allow for a completely native cloud database HA cluster (no need for the hacluster charm). The legacy solution (percona-cluster charm) is not supported on Ubuntu 20.04 LTS. Migration documentation is available. * New charms: Masakari The Masakari charms (masakari and masakari-monitors) and the requisite pacemaker-remote charm have been promoted to supported status, starting with OpenStack Stein. Masakari provides automated recovery of OpenStack instances (shared storage required). * New charms: OVN The OVN charms (neutron-api-plugin-ovn, ovn-central, ovn-chassis, and ovn-dedicated-chassis) have been promoted to supported status. OVN provides virtual networking for Open vSwitch and is the preferred default for new deployments of OpenStack Ussuri. * Ceph iSCSI Ceph iSCSI gateway functionality is available as a tech preview. These gateways provide iSCSI targets backed by a Ceph cluster. == OpenStack Charms team == The OpenStack Charms team can be contacted on the #openstack-charms IRC channel on Freenode. == Thank you == Lots of thanks to the below 67 charm contributors who squashed 89 bugs, enabled support for a new release of OpenStack, improved documentation, and added exciting new functionality! James Page Alex Kavanagh Frode Nordahl Liam Young Peter Matulis David Ames Corey Bryant Chris MacNaughton Ghanshyam Mann Aurelien Lourot Sahid Orentino Ferdjaoui Stamatis Katsaounis Ryan Beisner inspurericzhang Tiago Pasqualini Andrew McLeod ShangXiao Edward Hope-Morley Felipe Reyes kangyufei Adam Dyess Andreas Jaeger wangfaxin Xuan Yandong Arif Ali José Pekkarinen Chris Johnston Hemanth Nakkina Alexandros Soumplis Jose Guedez Qitao Tytus Kurek Seyeong Kim Dmitrii Shcherbakov Dongdong Tao Drew Freiberger Haw Loeung Jorge Niedbalski Andrea Ieri Xav Paice Qiu Fossen Yanos Angelopoulos Syed Mohammad Adnan Karim JiaSiRui Sérgio Filipe Marques Manso Vladimir Grevtsev George Kraft Marco Filipe Moutinho da Silva Xiyue Wang Adam Dyess Jose Delarosa Alexander Balderson Facundo Ciccioli Jacek Nykis Eduardo Sousa Thobias Trevisan Rodrigo Barbieri Alejandro Santoyo Gonzalez Sean McGinnis Claudio Pisa Shuo Liu Matus Kosut Stephen Muss Camille Rodriguez zhangboye Aggelos Kolaitis Nicolas Bock -- OpenStack Charms Team

2 1

[neutron] Drivers meeting 22.05.2020
by Slawek Kaplonski 21 May '20

21 May '20

Hi, Due to lack of agenda for the next drivers meeting, lets cancel it this week. See You all next week. BTW. Please maybe check Nate's email [1] - this isn't exactly RFE but something which IMO drivers team should check too :) [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014820.html -- Slawek Kaplonski Senior software engineer Red Hat

1 0

[kolla] Kolla klub meeting
by Mark Goddard 21 May '20

21 May '20

Hi, Just a reminder that we will host a project onboarding session for the next Kolla Klub meeting on Thursday 21st May. We'll cover a variety of topics on the many different ways you can contribute to the project. Gaël Therond will also fill us in on some of the questions put to him since the last meeting about his case studies. https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_… Thanks, Mark

1 1

review of tripleo-ci-centos-8-standalone-on-multinode-ipa
by Wesley Hayutin 21 May '20

21 May '20

Greetings, Please review the following new standalone + ipa deployment [1]. The keystone folks would like this deployment to run by default on all THT changes vs. the current set of files [2]. Looking for any strong objects to running the job on any THT change and or more files to target the job against in [2] If you need specific information about the job please contact rlandy @ redhat pojadhav @ redhat Thanks [1] https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-8-standalone-o… [2] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/zuul…

1 0

[Heat] Heat Stack Create Authorization Failed
by İzzettin Erdem 21 May '20

21 May '20

Hello everyone, When I launch a cluster on Sahara, it gives a heat stack authorization error. I also use Murano service and it is working with heat. I could not find the solution and I discuss this error with the Sahara-devel team. They are also searching for this. Could you help me, please? Both the error log of Sahara and Heat are below. Sahara-engine: http://paste.openstack.org/show/793671/ Heat-engine: http://paste.openstack.org/show/793673/ Thanks. Regards.

4 4

[ptg][cyborg][neutron][nova]Smartnic support integration via cyborg neutron and nova? - Cyborg Pre-PTG Meeting
by yumeng bao 21 May '20

21 May '20

Hi, As agreed on the IRC, tomorrow, we will have a cyborg Pre-PTG Zoom Meeting. Shaohe Feng from Intel will introduce SmartNIC support from the following aspects: * the cyborg-neutron-nova integration workflow when creating a server with a port of SmartNIC which is managed by cyborg *what changes needs to be done in nova, neutron to support SmartNIC feature? Please find the Pre-PTG meeting Link below: Zoom URL: https://us04web.zoom.us/j/9575741145?pwd=cVZydHl6blYzTGtNVlU4QU96ZWxiZz09 Meeting ID：957 574 1145 Password：9XhFhK The reserved meeting time is in total one and a half hours, but divided into three time slots(if time is not enough, we can extend another half hour time slot). *May 22 Friday 2:30 UTC -3:00 UTC *May 22 Friday 3:00 UTC -3:30UTC *May 22 Friday 3:30 UTC -4:00UTC * *And Please be aware: The three slots use the same URL, same Meeting ID and same Password. This means, when time of the slot is running out,and if you're kicked out of the Zoom, then you will need to login to the same Zoom URL again to join the next time slot. (And there’s also possibility that we don’t need to do the re-login, this depends on the number of people.） For others interested but not quite familiar with this topic, here’s some background information: Cyborg, served as a general purpose management framework for acceleration resources, is trying to support various types of accelerators.(FPGA, GPU, SPDK and so on) We continuously got questions from operators if cyborg supports SmartNIC, and this motivated us to support SmartNIC. Actually, we’ve made a discussion on SmartNIC with neutron team at the Shanghai Summit[1] 2019. We are now planning to continue discussing SmartNICs support integration in the coming Virtual PTG and try to move forward in Victoria Release. Cyborg will discuss about this topic internally first, and then later discuss with nova and neutron at PTG cross-project session[2][3]. [1] https://etherpad.opendev.org/p/Shanghai-Neutron-Cyborg-xproj [2] https://etherpad.opendev.org/p/nova-victoria-ptg [3] https://etherpad.opendev.org/p/cyborg-victoria-goals Regards， Yumeng

1 0

[nova][cinder][linstor] VM creation failed with invalid libvirt xml <source dev='None'/>
by Volodymyr Litovka 21 May '20

21 May '20

Hi colleagues, does anybody here use Linstor as backend for Openstack? I can not launch VM (synopsis below) while everything looks fine until the last step :-) Few words about Openstack's storage configuration: - controllers: cinder-api, cinder-scheduler, cinder-volume (modified with latest driver from Linstor's git), linstor-client, python-linstor - compute nodes: linstor-controller, linstor-satellite, linstor-client, python-linstor; node types - Combined - cinder.conf[1] - volume-type registered with corresponding properties[2] I'm able to manipulate volumes - create/delete[3] and every existing volume has the corresponding drbd/linstor repr[4] and LVM LV[5] on the compute nodes, so, from storage point of view, it looks as correct and ready to use. The problem is when I try to create VM using $ openstack server create --flavor [...] --network [...] --volume 15c4fa98-76a5-44d6-9701-c89a8a848b82 fearst Nova fails[6] because of invalid VM's libvirt XML definition (note "source dev='None'" below): <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source dev='None'/> <target dev='vda' bus='virtio'/> <serial>15c4fa98-76a5-44d6-9701-c89a8a848b82</serial> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> I do not have another working DRBD/Linstor/Openstack installation and can't even imagine, where to look into the problem - whether it is in Nova, Cinder or in Linstor configuration itself. I will appreciate if anybody can give me some guidance on where to seek for the solution to the problem. In my lab I'm using Openstack Train on Ubuntu 18.04.4: nova-compute 2:20.1.1-0ubuntu1~cloud0 nova-compute-kvm 2:20.1.1-0ubuntu1~cloud0 nova-compute-libvirt 2:20.1.1-0ubuntu1~cloud0 nova-api 2:20.1.1-0ubuntu1~cloud0 nova-common 2:20.1.1-0ubuntu1~cloud0 nova-conductor 2:20.1.1-0ubuntu1~cloud0 nova-novncproxy 2:20.1.1-0ubuntu1~cloud0 nova-scheduler 2:20.1.1-0ubuntu1~cloud0 cinder-api 2:15.1.0-0ubuntu1~cloud0 cinder-common 2:15.1.0-0ubuntu1~cloud0 cinder-scheduler 2:15.1.0-0ubuntu1~cloud0 cinder-volume 2:15.1.0-0ubuntu1~cloud0 python3-cinder 2:15.1.0-0ubuntu1~cloud0 python3-cinderclient 1:5.0.0-0ubuntu2~cloud0 python3-nova 2:20.1.1-0ubuntu1~cloud0 python3-novaclient 2:15.1.0-0ubuntu2~cloud0 Thank you! ==================================== [1] cinder.conf [DEFAULT] enabled_backends = linstor default_volume_type = linstor [linstor] storage_availability_zone = nova volume_backend_name = linstor volume_driver = cinder.volume.drivers.linstordrv.LinstorDrbdDriver linstor_autoplace_count = 2 linstor_default_volume_group_name=DfltRscGrp linstor_default_uri=linstor://runner linstor_default_storage_pool_name=drbdpool linstor_default_resource_size=1 linstor_volume_downsize_factor=4096 where 'runner' is virtual ip of linstor-controller, protected by pacemaker. ==================================== [2] openstack volume type show linstor +--------------------+--------------------------------------+ | Field | Value | +--------------------+--------------------------------------+ | access_project_ids | None | | description | None | | id | d2025962-503a-4f37-93bd-b766bb346a42 | | is_public | True | | name | linstor | | properties | volume_backend_name='linstor' | | qos_specs_id | None | +--------------------+--------------------------------------+ ==================================== [3] openstack volume show fearst +--------------------------------+-----------------------------------------------------+ | Field | Value | +--------------------------------+-----------------------------------------------------+ | attachments | [] | | availability_zone | nova | | bootable | true | | consistencygroup_id | None | | created_at | 2020-05-21T08:42:11.000000 | | description | None | | encrypted | False | | id | 15c4fa98-76a5-44d6-9701-c89a8a848b82 | | migration_status | None | | multiattach | False | | name | fearst | | os-vol-host-attr:host | ctrl1@linstor#linstor | | os-vol-mig-status-attr:migstat | None | | os-vol-mig-status-attr:name_id | None | | os-vol-tenant-attr:tenant_id | 7acec404393344cbabde07a22bbe6b3f | | properties | | | replication_status | None | | size | 5 | | snapshot_id | None | | source_volid | None | | status | available | | type | linstor | | updated_at | 2020-05-21T08:42:18.000000 | | user_id | 1048a19e94234451a61c3d9d46907ceb | | volume_image_metadata | {'signature_verified': 'False', | | | 'image_id': '15e992e8-a601-44cd-a2f0-8f34588a4d18',| | | 'image_name': 'cirros', | | | 'checksum': '1d3062cd89af34e419f7100277f38b2b', | | | 'container_format': 'bare', | | | 'disk_format': 'qcow2', | | | 'min_disk': '0', | | | 'min_ram': '0', | | | 'size': '16338944'} | +--------------------------------+-----------------------------------------------------+ ==================================== [4] linstor r l ╭───────────────────────────────────────────────────────────────────────────────────╮ ┊ ResourceName ┊ Node ┊ Port ┊ Usage ┊ Conns ┊ State ┊ ╞═══════════════════════════════════════════════════════════════════════════════════╡ ┊ CV_15c4fa98-76a5-44d6-9701-c89a8a848b82 ┊ cmp1 ┊ 7000 ┊ Unused ┊ Ok ┊ UpToDate ┊ ┊ CV_15c4fa98-76a5-44d6-9701-c89a8a848b82 ┊ cmp2 ┊ 7000 ┊ Unused ┊ Ok ┊ UpToDate ┊ ╰───────────────────────────────────────────────────────────────────────────────────╯ Note, that cmp3 is arbiter and has no 'by-disk' representation: root@cmp1:~# ls -lR /dev/drbd* brw-rw---- 1 root disk 147, 1000 May 21 11:42 /dev/drbd1000 /dev/drbd/by-disk/sds: lrwxrwxrwx 1 root root 17 May 21 11:42 CV_15c4fa98-76a5-44d6-9701-c89a8a848b82_00000 -> ../../../drbd1000 /dev/drbd/by-res/CV_15c4fa98-76a5-44d6-9701-c89a8a848b82: lrwxrwxrwx 1 root root 17 May 21 11:42 0 -> ../../../drbd1000 root@cmp2:~# ls -lR /dev/drbd* brw-rw---- 1 root disk 147, 1000 May 21 11:42 /dev/drbd1000 /dev/drbd/by-disk/sds: lrwxrwxrwx 1 root root 17 May 21 11:42 CV_15c4fa98-76a5-44d6-9701-c89a8a848b82_00000 -> ../../../drbd1000 /dev/drbd/by-res/CV_15c4fa98-76a5-44d6-9701-c89a8a848b82: lrwxrwxrwx 1 root root 17 May 21 11:42 0 -> ../../../drbd1000 root@cmp3:~# ls -lR /dev/drbd* brw-rw---- 1 root disk 147, 1000 May 21 11:42 /dev/drbd1000 /dev/drbd/by-res/CV_15c4fa98-76a5-44d6-9701-c89a8a848b82: lrwxrwxrwx 1 root root 17 May 21 11:42 0 -> ../../../drbd1000 ==================================== [5] root@cmp1:~# lvdisplay [ ... ] --- Logical volume --- LV Path /dev/sds/CV_15c4fa98-76a5-44d6-9701-c89a8a848b82_00000 LV Name CV_15c4fa98-76a5-44d6-9701-c89a8a848b82_00000 VG Name sds LV UUID jGzcIQ-yRpH-RKxP-ExsH-JSn6-kTFn-8kpKYO LV Write Access read/write LV Creation host, time cmp1, 2020-05-21 11:42:14 +0300 LV Pool name thin LV Status available # open 2 LV Size 5.00 GiB Mapped size 0.02% Current LE 1280 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:4 root@cmp2:~# lvdisplay [ ... ] --- Logical volume --- LV Path /dev/sds/CV_15c4fa98-76a5-44d6-9701-c89a8a848b82_00000 LV Name CV_15c4fa98-76a5-44d6-9701-c89a8a848b82_00000 VG Name sds LV UUID 8pVwMo-e3ed-Sy0w-06IZ-M7Mh-YVIL-BtKZEG LV Write Access read/write LV Creation host, time cmp2, 2020-05-21 11:42:14 +0300 LV Pool name thin LV Status available # open 2 LV Size 5.00 GiB Mapped size 0.02% Current LE 1280 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:4 ==================================== [6] Traceback of nova-compute: 3304 ERROR nova.compute.manager [] Traceback (most recent call last): 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/nova/compute/manager.py", line 2419, in _build_and_run_instance 3304 ERROR nova.compute.manager [] block_device_info=block_device_info) 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 3474, in spawn 3304 ERROR nova.compute.manager [] power_on=power_on) 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 6261, in _create_domain_and_network 3304 ERROR nova.compute.manager [] destroy_disks_on_failure) 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 3304 ERROR nova.compute.manager [] self.force_reraise() 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 3304 ERROR nova.compute.manager [] six.reraise(self.type_, self.value, self.tb) 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/six.py", line 693, in reraise 3304 ERROR nova.compute.manager [] raise value 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 6230, in _create_domain_and_network 3304 ERROR nova.compute.manager [] post_xml_callback=post_xml_callback) 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 6164, in _create_domain 3304 ERROR nova.compute.manager [] guest.launch(pause=pause) 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/guest.py", line 143, in launch 3304 ERROR nova.compute.manager [] self._encoded_xml, errors='ignore') 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 3304 ERROR nova.compute.manager [] self.force_reraise() 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 3304 ERROR nova.compute.manager [] six.reraise(self.type_, self.value, self.tb) 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/six.py", line 693, in reraise 3304 ERROR nova.compute.manager [] raise value 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/guest.py", line 138, in launch 3304 ERROR nova.compute.manager [] return self._domain.createWithFlags(flags) 3304 ERROR nova.compute.manager [] File "/usr/local/lib/python3.6/dist-packages/eventlet/tpool.py", line 190, in doit 3304 ERROR nova.compute.manager [] result = proxy_call(self._autowrap, f, *args, **kwargs) 3304 ERROR nova.compute.manager [] File "/usr/local/lib/python3.6/dist-packages/eventlet/tpool.py", line 148, in proxy_call 3304 ERROR nova.compute.manager [] rv = execute(f, *args, **kwargs) 3304 ERROR nova.compute.manager [] File "/usr/local/lib/python3.6/dist-packages/eventlet/tpool.py", line 129, in execute 3304 ERROR nova.compute.manager [] six.reraise(c, e, tb) 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/six.py", line 693, in reraise 3304 ERROR nova.compute.manager [] raise value 3304 ERROR nova.compute.manager [] File "/usr/local/lib/python3.6/dist-packages/eventlet/tpool.py", line 83, in tworker 3304 ERROR nova.compute.manager [] rv = meth(*args, **kwargs) 3304 ERROR nova.compute.manager [] File "/usr/lib/python3/dist-packages/libvirt.py", line 1110, in createWithFlags 3304 ERROR nova.compute.manager [] if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self) 3304 ERROR nova.compute.manager [] libvirt.libvirtError: Cannot access storage file 'None': No such file or directory -- Volodymyr Litovka "Vision without Execution is Hallucination." -- Thomas Edison

1 0

[neutron][release] Missing tarballs for networking-mlnx, networking-l2gw and vmware-nsx
by Mark Goddard 21 May '20

21 May '20

Hi, There are no tarballs published for ussuri networking-mlnx or vmware-nsx. The most recently published tarballs were in February. Is this expected? networking-l2gw also has no ussuri tarballs, although master was updated recently. Thanks, Mark

7 8

[kolla] deprecating kolla-cli
by Mark Goddard 20 May '20

20 May '20

Hi, We previously planned to retire kolla-cli due to lack of interest, but at the last minute there was an offer to help support it. That support is no longer available, and we are not aware of the project having gained traction since our original decision. We are therefore adding a deprecation notice [1] to the Ussuri release notes, with a plan to remove it from governance in Victoria if there is no response to the call for help. [1] https://review.opendev.org/729855 Thanks, Mark

1 0

[keystone][ldap]
by Amjad Kotobi 20 May '20

20 May '20

Hi all, I’m integrating keystone with LDAP, and having “service account” e.g. Nova, keystone etc.. which are in database. As soon as connecting it to ldap all authentication getting failed, how can I have both “service account” and “LDAP users” connected to Keystone? Here is my keystone.conf ################### [ldap] url = ldap://XXXXX user = uid=XXX,cn=sysaccounts,cn=etc,dc=XXX,dc=de password = dkrzprox user_tree_dn = cn=users,cn=accounts,dc=XXX,dc=de user_objectclass = posixAccount user_id_attribute = uid user_name_attribute = uid user_allow_create = false user_allow_update = false user_allow_delete = false group_tree_dn = cn=groups,cn=accounts,dc=XXX,dc=de group_objectclass = groupOfNames group_id_attribute = cn group_name_attribute = cn group_member_attribute = member group_desc_attribute = description group_allow_create = false group_allow_update = false group_allow_delete = false use_pool = true use_auth_pool = true debug_level = 4095 query_scope = sub [identity] driver = ldap ##################### OS: Centos7 OpenStack-Release: Train Any idea or example of options gonna be great! Thank you

3 2

[keystone]
by Amjad Kotobi 20 May '20

20 May '20

Hi, I have keystone running in HA multiple nodes, and after reboot one of the node it started in logs to pop up below messages “""WARNING keystone.server.flask.application [req-fe993224-cc7e-4e5f-83a8-1e925e60b995 24dfa0beaaaa48848b4eee68e449f2de d1fecbdb49ef4871b94b201b7856eed3 - default default] Could not recognize Fernet token: TokenNotFound: Could not recognize Fernet token””” And in command line “”"Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-1145c696-6275-4c78-9486-a690b98548ed)””" During command lines when request lands on machine which hasn’t rebooted or so, the result comes but on the rest fore-mentioned message always in place. Openstack release Train, and deployed manually. How can I tackle it down? Any ideas? Thanks Amjad

2 1

[docs][all] Important changes in recent openstackdocstheme updates
by Andreas Jaeger 20 May '20

20 May '20

A couple of changes recently merged into openstackdocstheme to fix problems reported. These had some surprises in it and we'd like to inform you about the changes: * Config options are now prefixed with openstackdocs_, the old names will be removed in a future release * The 'project' config option is now only respected (and displayed in the left menu) if 'openstackdocs_auto_name = False' is set. By default, the theme uses the package name (from setup.cfg) * The HTML files show the version number by default (with exception of releasenotes and api docs) calculated from git. If you want to use your own version number or disable it, set 'openstackdocs_auto_version = False' and manually configure the 'version' and 'release' options. * Previously, the theme always used 'pygments_style = "native"' and overrode the setting of 'sphinx' that many repos have. Now the setting is respected. For a few repos this lead to unreadable code snippets. If you see this or want to go back to the previous theme, configure 'pygments_style = "native"'. * Many projects have written PDF documents. openstackdocstheme can now optionally link to them. Set 'openstackdocs_pdf_link' to True to show the icon with path. Note that the PDF file is placed on docs.openstack.org in the top of the html files while in check/gate it's in a separate PDF folder. Thus, the site preview will show in check/gate a broken link - but it works fine, check [2]. * Both reno (since version 3.1.0) and openstackdocsstheme are now declared parallel safe, the CI jobs automatically build releasenotes in parallel [1]. You can modify your local tox job to do this by adding the '-j auto' parameter to your 'sphinx-build' invocation. We're releasing openstackdocstheme version 2.2.1 soon with two further fixes: * PDF documents will now show the version number like html document, no need to configure versions in conf.py for this anymore [3]. * small bug fix (if you set auto_name = False in doc/source/conf.py, this hit so far 5 repos)[4]. Everything is documented in the documentation of openstackdocstheme [2]. If there are any questions, best ask in #openstack-oslo. Andreas has started pushing changes to update projects with topic:reno-openstackdocstheme. Hope that's all for Victoria on the openstackdocstheme, Stephen and Andreas [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014902.html [2] https://docs.openstack.org/openstackdocstheme/ [3] https://review.opendev.org/729554 [4] https://review.opendev.org/729031 -- Andreas Jaeger aj(a)suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB

1 0

[Neutron] How to change the MAC address of Gateway interface of the router
by Rahul Sharma 20 May '20

20 May '20

Hi, I have setup a multi-host openstack cloud on AWS consisting of 3 servers i.e. Controller, Compute & Network Everything is working as expected. My requirement is that the compute instances should be able to communicate with the internet and vice-versa. However, AWS due to its security policies will drop all traffic that is sourced from the VMs because the VM traffic will have the MAC address of the gateway interface of the router when it hits the AWS switch. This MAC address is not know to AWS hence it drops this traffic. AWS will allow only that traffic that contains the registered MAC address as its source address So I need to change the MAC address of the gateway interface of the L3 router on the network node. I tried googling but could not find any solution. Is there any solution/command to do this ? Thanks, Kaushik

2 2

[largescale-sig] Next meeting: May 20, 8utc
by Thierry Carrez 20 May '20

20 May '20

Hi everyone, The Large Scale SIG will have a meeting this week on Wednesday, May 20 at 8 UTC[1] in the #openstack-meeting-3 channel on IRC: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200520T08 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting A reminder of the TODOs we had from last meeting, in case you have time to make progress on them: - amorin to propose patch against Nova doc - ttx to create an empty oslo-metric repository - masahito to finalize oslo.metric POC code release Talk to you all on Wednesday, -- Thierry Carrez

1 1

[operators] multi release upgrades?
by Fabian Zimmermann 20 May '20

20 May '20

Hi, Does anybody did already some multi release upgrades f.e. queens->train and is able to share his knowhow? Thanks, Fabian

3 2

Re: [Cyborg][PTG]Virtual PTG Planning
by yumeng bao 19 May '20

19 May '20

Hi team, I have booked the following slots for Cyborg Virtual PTG [1] based on the doodle poll results. * June 2 Tuesday 6:00 UTC - 8:00 UTC, Room Cactus * June 3 Wednesday 6:00 UTC - 8:00 UTC,Room Cactus * June 4 Thursday 6:00 UTC - 8:00 UTC,Room Cactus *June 5 Friday 6:00 UTC - 8:00 UTC,Room Bexar Moreover, I have synced with Slaweq and gibi, and we agreed to have a Nova-Neutron-Cyborg cross project discussion on Friday from 14:00 UTC to 15:00 UTC in Room Juno (Thanks to Nova for sharing this time slot!) There are two weeks to go before the virtual PTG. So I would like to encourage you to LOOK AT the etherpad[2] and ADD YOUR NAME to the Attendance section if you are planning to attend! If you have topics for the PTG, please try to start discussing them now either in the etherpad[2] or in a spec or just on the ML. (Such preparation is especially necessary for those cross project topics to get agreements/directions internally first, we have very limited time to conclude the topics during the PTG.) Let’s continue discussing this at tomorrow’s weekly meeting. [1] https://ethercalc.openstack.org/126u8ek25noy [2] https://etherpad.opendev.org/p/cyborg-victoria-goals Regards， Yumeng

1 0

[tripleo][ci] remove upstream multinode scenario jobs (queens, rocky)
by Wesley Hayutin 19 May '20

19 May '20

Greetings, I'd like to propose that we start removing multinode ( 2 node ) based scenario jobs from the upstream that still exist in queens and rocky. We will continue to support a basic multinode deployment [1 ] across all the branches. From stable/stein on we only maintain one multinode job, and the scenarios have all been migrated to single node deployments. The loss of coverage will be augmented by the RDO promotion pipeline [2] that should be verifying all the upstream check/gate jobs across the branches. Issues will be caught periodically vs. on a per patch basis. Issues will be reported, debugged and sent to the appropriate teams. I am not proposing we do this overnight or in one giant patch, but over time start to remove the upstream coverage. We also need to ensure that the upstream version is properly covered in RDO software factory. WHY??? Two node deployments in upstream infrastructure are very unreliable and often timeout. Generally devolving into noise and wasted resources and time spent by developers trying to land patches [3]. Comments / Questions?? [1] tripleo-ci-centos-[7,8]-containers-multinode [2] https://review.rdoproject.org/zuul/builds?pipeline=openstack-periodic-wedne… [3] https://bugs.launchpad.net/tripleo/+bug/1879565

1 0

Virtual PTG Schedule Live & Registration Reminder
by Kendall Waters 19 May '20

19 May '20

Hey everyone, The June 2020 Project Teams Gathering is right around the corner! The official schedule has now been posted on the PTG website [1], the PTGbot has been updated[2], and we have also attached it to this email. Friendly reminder, if you have not already registered, please do so [3]. It is important that we get everyone to register for the event as this is how we will contact you about tooling information and other event details. Please let us know if you have any questions. Cheers, The Kendalls (diablo_rojo & wendallkaters) [1] www.openstack.org/ptg <http://www.openstack.org/ptg> [2] http://ptg.openstack.org/ptg.html <http://ptg.openstack.org/ptg.html> [3] https://virtualptgjune2020.eventbrite.com <https://virtualptgjune2020.eventbrite.com/>

1 0

[ironic] trusted delgation cores?
by Julia Kreger 19 May '20

19 May '20

Greetings awesome people and AIs! Earlier today, I noticed Iury (iurygregory) only had +1 rights on the ironic-prometheus-exporter. I noted this in IRC and went to go see about adding him to the group, and realized we didn't have a separate group already defined for ironic-prometheus-exporter, which left a question, do we create a new group, or just grant ironic-core membership. And the question of starting to engage in trusted delegation of core rights came up in IRC[0]. I think it makes a lot of sense, but wanted to see what everyone thought? Specifically in Iury's case: I feel he has proven himself, in ironic and non-ironic cases, and I think it makes sense to grant him core rights under the premise that he is unlikely to approve non-trivial changes to merge that he is not confident in. Thoughts, concerns, congratulations? For both questions? -Julia [0]: http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-iro…

6 5

[tripleo][ptg] schedule posted
by Wesley Hayutin 19 May '20

19 May '20

Greetings owls, Victoria Schedule has been posted [1]. There are a lot of great topics so we're going to limit the time slots to 1/2 hour each. Creating a blueprint and spec for your topic prior to the PTG will help you make your point and win the game of influence [2]. Please feel free to self sign up on the schedule, I will cross check any unassigned topics prior to the event and punt them to the last day. For now we're going to close adding new topics to fit the schedule. There is spare time on the calendar for Q&A and random ad hoc topics [3] if needed. To prepare for your presentations please ensure you are comfortable w/ the video conferencing [4] as much as possible. Looking forward to seeing you all Thanks!! [1] https://etherpad.opendev.org/p/tripleo-ptg-victoria [2] https://review.opendev.org/#/q/project:openstack/tripleo-specs+status:open https://blueprints.launchpad.net/tripleo [3] https://ethercalc.openstack.org/126u8ek25noy [4] https://meetpad.opendev.org/

1 0

[keystone] scope enforcement ready for prime time?
by Mark Goddard 19 May '20

19 May '20

Hi, I have a use case which I think could be fulfilled by scoped tokens: Allow an operator to delegate the ability to an actor to create users within a domain, without giving them the keys to the cloud. To do this, I understand I can assign a user the admin role for a domain. It seems that for this to work, I need to set [oslo_policy] enforce_scope = True in keystone.conf. The Train cycle highlights suggest this is now fully implemented in keystone, but other most projects lack support for scopes. Does this mean that in the above case, the user would have full cloud admin privileges in other services that lack support for scopes? i.e. while I expect it's safe to enable scope enforcement in keystone, is it "safe" to use it? Cheers, Mark

3 3

[Watcher]IRC meeting on May 20
by licanwei 19 May '20

19 May '20

Hi, Tomorrow at 08:00 UTC on #openstack-meeting-alt. pls update the meeting agenda if you have something want to be discussed. thanks, | | licanwei_cn | | 邮箱：licanwei_cn(a)163.com | 签名由网易邮箱大师定制

1 0

[neutron] Recent incompatible change in stable/rocky branch
by Neil Jerram 19 May '20

19 May '20

I'm sorry, but this is a moan. This merge - https://opendev.org/openstack/neutron/commit/a6fb2faaa5d46656db9085ad6bcfc6… - to the Neutron stable/rocky branch on April 23rd, has broken my team's Neutron plugin, by requiring 3rd party LinuxInterfaceDriver subclasses to take a new 'link_up' argument in their 'plug_new' method. IMO, it should have been obvious to folk proposing or reviewing this, that it would cause breakage. Does Neutron have a different understanding of "stable" than I do? Or do plugins other than OVN not matter anymore?

2 5

[neutron] WSREP: referenced FK check fail: Lock wait index
by Fabian Zimmermann 18 May '20

18 May '20

Hi, im just upgrading my galera nodes from 5.6 to 5.7 and pike -> queens. Now im seeing this lines hitting my mysql.log: -- 2020-05-19T05:41:39.516879Z 11861 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` -- Is this a known issue? Anything I may/should do? Thank a lot, Fabian

1 1

[ironic] III SPUC - The Sanity Preservation Un-Conference
by Iury Gregory 18 May '20

18 May '20

Hello everyone \o/ It's time for the third edition of SPUC! It will happen this Friday (May 22) at 5pm UTC! For those who doesn't know what is SPUC check [0]. We will be using Julia's bluejeans: https://bluejeans.com/u/jkreger Etherpad for <crazy> ideas: https://etherpad.opendev.org/p/IIISanityPreservationUnConference [0] http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013521.ht… -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

2 1

[all] Virtual Ussuri Celebration
by Kendall Nelson 18 May '20

18 May '20

Hello Everyone! I wanted to invite you all to a virtual celebration of the release! Next Friday, May 15th at 20:00 UTC, I invite you to join me in celebrating :) The purpose of this meeting will be two fold: 1. To celebrate all that our community has accomplished over the last release since we can't get together in person in June. I was thinking with trivia and a baking contest (I was going to attempt a cake in the shape of the OpenStack logo or maybe the actual Ussuri logo) :) There was also a request for piano karaoke which is also still on the table.. 2. To test out the OpenDev team's meetpad instance and work out kinks so that it can be vetted for PTG use. Here is the room we will be testing: https://meetpad.opendev.org/virtual-ussuri-celebration Worst case scenario, I'll share my zoom. Can't wait to see you all there (and what you've baked)! -Kendall (diablo_rojo) <https://meetpad.opendev.org/virtual-ussuri-celebration>

3 4

[tc][tricircle] Retiring the Tricircle project
by Ghanshyam Mann 18 May '20

18 May '20

Hello Everyone, As you know, Tricirlce is a leaderless project for the Victoria cycle means there is no PTL candidate for Victoria cycle. 'No PTL' is one of the criteria which triggers TC to start checking the health, maintainers of the project for dropping project from OpenStack Governance[1]. TC discussed the Tricircle project in today's meeting[2] and checked if the project has maintainers but no PTL or it is missing the maintainer completely. By looking at the Ussuri cycle development work, it seems no activity related to Tricircle except few gate fixes or community goal commits[2]. Based on all these checks, we are going to start the process of removing Tricircle from governance in the Victoria cycle as specified in the Mandatory Repository Retirement resolution [4] and detailed in the infra manual [5]. NOTE: release team is trying to do Ussuri release for Tricircle's deliverables if we can get this reno fix merge - https://review.opendev.org/#/c/721697/ >From the Victoria cycle, Tricircle will move out of OpenStack governance by keeping their repo under OpenStack namespace with an empty master branch with 'Not Maintained' message in README. If someone from old or new maintainers shows interest to continue its development then it can be re-added to OpenStack governance. With that thanks to all Tricircle contributors and PTLs for maintaining this project. [1] https://governance.openstack.org/tc/reference/dropping-projects.html [2] http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-04-21-15.01.log.html [3] https://www.stackalytics.com/?metric=commits&release=ussuri&module=tricircl… [4] https://governance.openstack.org/tc/resolutions/20190711-mandatory-reposito… [5] https://docs.opendev.org/opendev/infra-manual/latest/drivers.html#retiring-… -gmann

1 1

[nova][ptg] Ussuri Retrospective
by Balázs Gibizer 18 May '20

18 May '20

Hi, There is a common but seemingly not that popular topic on each nova PTG, the retrospective. I added the retrospective to the PTG etherpad [0]. Please collect retrospective topics there or tell me privately if you have a sensitive topic you want me to bring up. If there won't be any topic collected until the PTG then we will simply skip the retrospective. Cheers, gibi [0] https://etherpad.opendev.org/p/nova-victoria-ptg

1 0

[blazar] IRC meeting cancelled on May 19
by Pierre Riteau 18 May '20

18 May '20

Hello, Due to a scheduling conflict, I will not be able to chair the Blazar IRC meeting on Tuesday May 19. I propose to cancel and meet as usual on May 26, when we will finalise the agenda for the PTG meeting. Best wishes, Pierre Riteau (priteau)

1 0

[neutron] bug deputy report for week of 2020-05-11
by Bence Romsics 18 May '20

18 May '20

Hi Neutrinos, Here's the deputy report for last week: High: * https://bugs.launchpad.net/neutron/+bug/1878042 SRIOV agent does not parse correctly "ip link show <dev>" fix proposed: https://review.opendev.org/726918 * https://bugs.launchpad.net/neutron/+bug/1878160 [OVN] Functional tests environment is using old OVN fix proposed (wip): https://review.opendev.org/727193 Medium: * https://bugs.launchpad.net/neutron/+bug/1877977 [DVR] Recovery from openvswitch restart fails when veth are used for bridges interconnection unassigned * https://bugs.launchpad.net/neutron/+bug/1875981 Admin deleting servers or ports leaves orphaned DNS records fix proposed (wip): https://review.opendev.org/728385 related test: https://review.opendev.org/728409 * https://bugs.launchpad.net/neutron/+bug/1878299 [floatingip port_forwarding] changing external port to used value hangs with retriable exception unassigned * https://bugs.launchpad.net/neutron/+bug/1878358 OVN migration doesn't clean up the existing ml2-ovs agents fix proposed: https://review.opendev.org/727648 * https://bugs.launchpad.net/neutron/+bug/1878632 Race condition in subnet and segment delete: The segment is still bound with port(s) assigned, no fix proposed yet test reproducing the bug: https://review.opendev.org/728904 * https://bugs.launchpad.net/neutron/+bug/1878916 When deleting a network, delete the segment RP only when the segment is deleted fix proposed: https://review.opendev.org/728507 Incomplete: * https://bugs.launchpad.net/neutron/+bug/1877978 SNAT Problem Floating IP * https://bugs.launchpad.net/neutron/+bug/1878719 DHCP Agent's iptables CHECKSUM rule causes skb_warn_bad_offload kernel * https://bugs.launchpad.net/neutron/+bug/1879009 attaching extra port to server raise duplicate dns-name error See you on the meeting, Bence

1 0

[nova][gate] openstack-tox-pep8 job failing
by melanie witt 18 May '20

18 May '20

Hey all, The openstack-tox-pep8 job is now failing too since hacking 3.1.0 was released [1], which brings in a newer flake8 version, which adds new checks to the code and we have a few failures. We have a change that would pin hacking >= 3.0.1 and < 3.1.0 [2] to prevent new checks from rolling in automatically, but it is stuck behind the failing openstack-tox-docs job [3]. This is unfortunately a chicken and egg situation. The proposed nova patch for the docs job, as mentioned from my other ML post: https://review.opendev.org/727898 fails the pep8 job and the proposed nova patch for the pep8 job [2] fails the docs job. I'm not sure how people will want to proceed here because a nova-side-only gate fix would involve squashing ^ and [2]. If we can get another fix or revert to openstackdocstheme to take care of the docs job, we'd then only need [2] on the nova side to unblock the nova gate. Cheers, -melanie [1] https://review.opendev.org/728016 [2] https://review.opendev.org/727347 [3] http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014876.html

3 5

[gate] parallel releasenotes job builds
by melanie witt 18 May '20

18 May '20

Hi all, We recently merged a change [1] that will run the build-openstack-releasenotes job with 'sphinx-build -j auto' to allow the build to run on multiple CPUs. With the recent releases of reno 3.1.0 and openstackdocstheme 2.1.2, both libraries advertise that they are parallel_read_safe and thus can support the '-j' option. This effort was inspired by the nova build-openstack-releasenotes job which typically takes 52m to > 1h to run. The job timeout is 1h, so we were occasionally seeing TIMED_OUT job failures. With parallel sphinx-build, the nova job run time is reduced down to about 15m (awesome!). I wanted to say thanks to smcginnis, dhellmann, clarkb, and AJaeger for helping this newbie to reno and docs builds. If anyone encounters any issues around the parallel reno builds in their projects, please let us know. Cheers, -melanie [1] https://review.opendev.org/727473

3 2

[kolla] Ceph transition plan
by Eric K. Miller 17 May '20

17 May '20

Hi, I noticed that in Kolla's master branch that Ceph has been removed, as expected for a deprecated component (I'm sad, though, since it works so well!). In the release notes, it is noted that "Prior to this we will ensure a migration path to another tool such as Ceph Ansible is available." Is this migration path documented since it appears that the latest release will not have the Kolla Ceph container available? Thanks! Eric

2 1

[ops] ops meetups team meeting 2020-5-5
by Chris Morgan 15 May '20

15 May '20

Hey all, The openstack ops meetups team has been fairly dormant recently for obvious reasons. However with the realisation that in-person meetups, conferences, summits etc are simply not coming back any time soon, we've started to regroup to discuss next steps. We are also seeing some requests for virtual meetups from some operators via the OpsMeetup twitter account. Thus we had a quick IRC meeting today, and also a trial run at an open source based video conference meeting using jitsi via an instance running on infra provided by Erik McCormick. This seems to be promising. We'll look into trialling some ops related events leveraging this. We also agreed to try and have an operators session during the upcoming virtual PTG (replacing the Vancouver event now cancelled). More info will be shared as and when we can. I hope you're all doing as well as can be expected. Chris - on behalf of the ops meetups team Meeting minutes: Minutes: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2020/ops_meetup_tea… 12:01 PM Minutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2020/ops_meetup_tea… 12:01 PM Log: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2020/ops_meetup_tea… -- Chris Morgan <mihalis68(a)gmail.com>

5 9

[barbican] Nominating Moisés Guimarães for barbican-core
by Douglas Mendizabal 15 May '20

15 May '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I would like to nominate Moisés Guimarães to be added to the barbican-core team. Moisés has been very helpful in helping us review barbican patches, and has done an excellent job of helping maintain the castellan library. If there are no objections, we will officially add Moisés to the team next week. Thanks, Douglas Mendizábal Barbican PTL -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEwcapj5oGTj2zd3XogB6WFOq/OrcFAl6+9XMACgkQgB6WFOq/ OrdzzxAAgxxymvuA+yGDuitEcjqwlggPJBYGb5PlHqqTkXcrS6IEcneG1eEJ/Rp2 JovTMN5sv3PwhtSMxjEmyrBVR9g6MKbQoQvDk1p77fFIL9ofIFV3xKOpZutnb3ig Y2/gSMWNDfuz7DPpNofUsyzvK5eBNWC8aBbpSeN0R4qLAlyOPFe6ftOAI1RvIX4W s6CwOiMQGGGNUK8TZgvG9BOOJorgMZ+maq4tFRN8P6bLA6q7kcsUob/LBIwCpoEF xdl9EO/IaRM4kMP8y/quIzDnBJV9Im4t8WrJ5sYNPnpfS+0yXseuCACAMYWSNp63 Zf9oRyIuv3Z/+z6qjcpkct/xhijdtB+Sc0MpmGv43RSoEHkYAGU6ue2nlZkVIow9 GO5Itq38WbORBIFwlGK+J+u40ikY+EjldzIwsxoBZDvuNMsGltpVclAkyW2VUwL3 HOyKPCm0dLiVz3qYo2dTH2eC2cdSbGxF91gckke1m5o69RDK9vYi6YQxtO0ms7Em yZoVQ6OnA4KCZUEd4sby7jWm/1ueXZq05BQgnB1tXbdMa6hDp6CwVKSAfH0fHS6D 5dCuo1EoDWxCTsh3lH0wogeODcCBReNTNCWEy/ia19aOO4cXrlpLznP6GONENwEo zbaPfwnmdw5Q1ARmLcEpgsbVF+mIymVkqGpNZ8DFA/wR+mQ/fkU= =Syoj -----END PGP SIGNATURE-----

2 1

[all][InteropWG] Request to PTLs for highligting Core Feature add-remove
by prakash RAMCHANDRAN 15 May '20

15 May '20

Hi all, Interop WG needs patches to complete the 2020.06 Ussuri guidelines. PTL or team members of CoreNovaNeutronCinderKeystoneGlanceSwiftadd-onHeat -OrchedtrationDesignate - DNS potential for Victoria add-onsIronicZunSenlinKolla & KuryrPlease suggest others Open Infra (Potential Bare Metal & Container APIs)StarlingXAirshipKata We are reviewing your release notes, but if you can advice us on non-amin APIs for Objects that you can qualify as core for current or future release please send Advisory with your module name. eg.Nova: Advisory - Cell API is potential candidate for core. etc. Alternate visit the TODO plan as on etherpad for interop next week callhttps://etherpad.opendev.org/p/interop Validate your APIs in community sitehttps://refstack.openstack.org/#/community_results Add your items for next week Fri 10 AM PDT call for Fri May 22nd. Plus if you want to attend and Present in PTG interopWG please add your topics and +1 those you like to see on June 1st 6-8 AM PDThttps://etherpad.opendev.org/p/interop_virtual_ptg_planning_june_2020 Thankson behalf ofChair - InteropWG PrakashVice Chair - Mark T Voelker Sent from Yahoo Mail on Android

1 0

[neutron] 15-05-2020 drivers meeting agenda
by Slawek Kaplonski 15 May '20

15 May '20

Hi, For tomorrow's drivers meeting we have only one RFE to discuss: * https://bugs.launchpad.net/neutron/+bug/1877301 - L3 Router support ndp proxy It was initially triaged by Brian (Thank You) and discussed already on L3 subteam meeting. See You all tomorrow and have a nice day :) -- Slawek Kaplonski Senior software engineer Red Hat

2 1

[swift] Adding disks - one by one or all lightly weighted?
by Mark Kirkwood 14 May '20

14 May '20

Hi, We are wanting to increase the number of disks in each of our storage nodes - from 4 to 12. I'm wondering whether it is better to: 1/ Add 1st new disk (with a reduced weight)...increase the weight until full, then repeat for next disk etc 2/ Add 'em all with a (much i.e 1/8 of that in 1/ ) reduced weight...increase the weights until done Thoughts? regards Mark

2 2

[all] pep8 job failing due to flake8 3.8.0
by Ghanshyam Mann 14 May '20

14 May '20

Hello Everyone. You might have noticed that few or most of the projects pep8 job started failing. That is because flake8 new version 3.8.0 added the new pycodestyle with new rules. Hacking capped it with 4.0.0 version not with the minor version for 3.*. The new hacking version 3.0.1 is released which cap the flake8<3.8.0. Thanks to dtantsur and stephenfin for tacking care of it. To fix your pep8 job you can, - Either fix the pep8 error in code if easy and fast to fix. - Or bump the hacking minimum version to 3.0.1. I have proposed it for a few projects failing pep8. - https://review.opendev.org/#/q/topic:hacking-fix+(status:open+OR+status:mer… If pep8 job is passing then you do not need to do anything. The existing hacking version cap will work fine. -gmann

4 12

OpenStack Ussuri Community Meeting Recordings & Presentation Decks
by Allison Price 14 May '20

14 May '20

Hi everyone, Thanks to all who joined or created content and presented at the community meetings yesterday! There were quite a few project updates presented for the Ussuri release. If you missed the meetings, you can find the recordings in this playlist [1] and links to the presentations are also included in the video abstracts. We have also posted both meeting recordings on Tencent Cloud, so you can watch the first community meeting [2] or the second community meeting [3] there as well. If you have any trouble accessing these resources, please let me know. Cheers, Allison [1] https://www.youtube.com/playlist?list=PLKqaoAnDyfgpYADSiOfIVwgKb5zbL0GJE <https://www.youtube.com/playlist?list=PLKqaoAnDyfgpYADSiOfIVwgKb5zbL0GJE>[2] https://v.qq.com/x/page/q0966o61rz9.html <https://v.qq.com/x/page/q0966o61rz9.html> [3] https://v.qq.com/x/page/d09667otaf1.html <https://v.qq.com/x/page/d09667otaf1.html> Allison Price OpenStack Foundation allison(a)openstack.org

1 0

[nova][gate] openstack-tox-docs job failure
by melanie witt 14 May '20

14 May '20

Howdy all, There's a upper-constraints bump to openstackdocstheme 2.1.0 which has recently merged [1] which is going to break the openstack-tox-docs job for nova. I've proposed a patch to fix it here: https://review.opendev.org/727898 if people could please take a look. Cheers, -melanie [1] https://review.opendev.org/727850

2 2

[neutron] parent ports for trunks being claimed by instances
by Nate Johnston 14 May '20

14 May '20

Neutron developers, I am currently working on an issue with trunk ports that has come up a few times in my direct experience, and I hope that we can create a long term solution. I am hoping that developers with experience in trunk ports can validate my approach here, especially regarding fixing current behavior without introducing an API regression. By way of introduction to the specifics of the issue, let me blockquote from the LP bug I raised for this [1]: ---- When you create a trunk in Neutron you create a parent port for the trunk and attach the trunk to the parent. Then subports can be created on the trunk. When instances are created on the trunk, first a port is created and then an instance is associated with a free port. It looks to me that's this is the oversight in the logic. From the perspective of the code, the parent port looks like any other port attached to the trunk bridge. It doesn't have an instance attached to it so it looks like it's not being used for anything (which is technically correct). So it becomes an eligible port for an instance to bind to. That is all fine and dandy until you go to delete the instance and you get the "Port [port-id] is currently a parent port for trunk [trunk-id]" exception just as happened here. Anecdotally, it's seems rare that an instance will actually bind to it, but that is what happened for the user in this case and I have had several pings over the past year about people in a similar state. I propose that when a port is made parent port for a trunk, that the trunk be established as the owner of the port. That way it will be ineligible for instances seeking to bind to the port. ---- Clearly the above behavior indicates buggy issue that should be rectified in master and stable branches. Nobody wants a VM that can't be fully deleted because the port can't ever be deleted. This is especially egregious when it causes heat stack deletion failures. I am mostly concerned that by adding the trunk as an owner of the parent port, then the trunk will need to be deleted before the parent port can be deleted, otherwise a PortInUse error will occur when the port is deleted (i.e. on tempest test teardown). That to me seems indicative of an inadvertent API change. Do you think it's all right to say that if you delete a port that is a parent port of a trunk, and that trunk has no other subports, that the trunk deletion is implicit? Is that the lowest impact to the API that we can incur to resolve this issue? Your wisdom is appreciated, Nate [1] https://bugs.launchpad.net/neutron/+bug/1878031

5 6

[oslo][nova][vmware] Replacement for suds library
by Stephen Finucane 14 May '20

14 May '20

The suds-jurko library used by oslo.vmware is emitting the following warnings in nova tests. /nova/.tox/py36/lib/python3.6/site-packages/suds/resolver.py:89: DeprecationWarning: invalid escape sequence \% self.splitp = re.compile('({.+})*[^\%s]+' % ps[0]) /nova/.tox/py36/lib/python3.6/site-packages/suds/wsdl.py:619: DeprecationWarning: invalid escape sequence \s body.parts = re.split('[\s,]', parts) These warnings are going to be errors in Python 3.10 [1]. We have over 18 months before we need to worry about this [2], but I'd like to see some movement on this well before then. It seems the suds-jurko fork is dead [3] and movement on yet another fork, suds-community, is slow [4]. How difficult would it be to switch over to something that does seem maintained like zeep [5] and, assuming it's doable, is anyone from VMWare/SAP able to do this work? Stephen [1] https://docs.python.org/3.9/whatsnew/3.9.html#you-should-check-for-deprecat… [2] https://www.python.org/dev/peps/pep-0596/ [3] https://bitbucket.org/jurko/suds/src/default/ [4] https://github.com/suds-community/suds/pull/32 [5] https://python-zeep.readthedocs.io/en/master/

5 6

[ironic] [release] Proposal for a new release model for ironic projects
by Dmitry Tantsur 14 May '20

14 May '20

Hi folks, I would like to formally present this proposal: https://review.opendev.org/#/c/725547/ It is largely driven by a desire to produce frequent supported and tested intermediate releases for standalone consumers, as well as address a few minor issues we've found over time. I would like to try applying it to Victoria already. Please read and comment. Thanks, Dmitry

1 0

[RDO][OpenStack] Removal of Pike and Ocata Trunk repos
by Yatin Karel 13 May '20

13 May '20

Hi, The topic was discussed in yesterday's RDO meeting[1] and to reach a wider audience it's being raised here. Ocata and Pike are in the Extended maintenance phase[2] for more than a year now, The promotion jobs which used to test these repos were dropped long ago[3][4]. Now we are planning to drop these trunk repos[5][6] in the first week of June, 2020. We already stopped building new commits for pike/ocata[7]. So if anyone still using these repos consider moving to upgrade to queens or any later releases. If something is blocking you to stop relying on ocata/pike repos raise your voice here so we can consider it before dropping the repos. [1] https://lists.rdoproject.org/pipermail/dev/2020-May/009379.html [2] https://releases.openstack.org/ [3] https://review.rdoproject.org/r/#/q/topic:remove_pike [4] https://review.rdoproject.org/r/#/c/16485/ [5] http://trunk.rdoproject.org/centos7-ocata/ [6] http://trunk.rdoproject.org/centos7-pike/ [7] https://softwarefactory-project.io/r/#/c/18347/ On Behalf of RDO Team Thanks and Regards Yatin Karel

1 0

[all] OpenStack Ussuri Community Meeting in 30 Minutes
by Allison Price 13 May '20

13 May '20

Hi everyone, I just wanted to remind you that there is a community meeting in 30 minutes to cover OpenStack Ussuri highlights. The meeting will be moderated by Mohammed Naser from the OpenStack Technical Committee and include project updates from: - Slawek Kaplonski, Neutron - Michael Johnson, Octavia - Goutham Pacha Ravi, Manila - Mark Goddard, Kolla - Balazs Gibizer, Nova - Brian Rosmaita, Cinder You can find dial-in information in this etherpad [1]. The recording and slides will be shared on the mailing list after the meeting. There will also be another meeting tomorrow, Thursday May 14 at 0200 UTC, moderated by Rico Lin from the OpenStack TC, and you can see who will be presenting here [1]. [1] https://etherpad.opendev.org/p/CommunityMeeting_Ussuri <https://etherpad.opendev.org/p/CommunityMeeting_Ussuri> Allison Price OpenStack Foundation allison(a)openstack.org

3 2