- openstack-discuss - lists.openstack.org

[masakari] Wallaby PTG planning
by Radosław Piliszek 16 Sep '20

16 Sep '20

Hello, Masakarians*! *Anyone interested in Masakari. It's again this time of the century when a new OpenStack release is up on the horizon. As always, it means there will be a PTG (Project Team Gathering) to discuss the new cycle (and summarise the previous). This time it's going to be fully virtual so we call it a vPTG. I've booked us some time for the Wallaby PTG. [1] There are 4 (four) 2-hour sessions to accommodate both APAC and EMEA/Americas: Thursday October 29, 2020 06:00 - 08:00 (UTC) Thursday October 29, 2020 13:00 - 15:00 (UTC) Friday October 30, 2020 06:00 - 08:00 (UTC) Friday October 30, 2020 13:00 - 15:00 (UTC) I have also created an initial PTG page on Etherpad. [2] Please fill in your names if you are going to participate - with session times that suit you (please consider being flexible, it seems we are spanning the globe now). Add your proposals even if you can't participate directly (add your names to proposals). Please register for the event itself as well, to let the organisers know how many people are going to be there. [3] See YOU there! [1] https://ethercalc.openstack.org/7xp2pcbh1ncb [2] https://etherpad.opendev.org/p/masakari-wallaby-vptg [3] https://www.eventbrite.com/e/project-teams-gathering-october-2020-tickets-1… -yoctozepto

1 0

vPTG October 2020 Team Signup Reminder
by Kendall Waters 16 Sep '20

16 Sep '20

Hello Everyone! Wanted to give you all a reminder that the deadline for signing up teams for the PTG is approaching! The virtual PTG will be held from Monday October 26th to Friday October 30th, 2020. To signup your team, you must complete BOTH the survey[1] AND reserve time in the ethercalc[2] by September 11th at 7:00 UTC. We ask that the PTL/SIG Chair/Team lead sign up for time to have their discussions in with 4 rules/guidelines. 1. Cross project discussions (like SIGs or support project teams) should be scheduled towards the start of the week so that any discussions that might shape those of other teams happen first. 2. No team should sign up for more than 4 hours per UTC day to help keep participants actively engaged. 3. No team should sign up for more than 16 hours across all time slots to avoid burning out our contributors and to enable participation in multiple teams discussions. Once your team is signed up, please register[3]! And remind your team to register! Registration is free, but since it will be how we contact you with passwords, event details, etc. it is still important! If you have any questions, please let us know. -The Kendalls (diablo_rojo & wendallkaters) [1] Team Survey: https://openstackfoundation.formstack.com/forms/oct2020_vptg_survey <https://openstackfoundation.formstack.com/forms/oct2020_vptg_survey> [2] Ethercalc Signup: https://ethercalc.openstack.org/7xp2pcbh1ncb <https://ethercalc.openstack.org/7xp2pcbh1ncb> [3] PTG Registration: https://october2020ptg.eventbrite.com <https://october2020ptg.eventbrite.com/>

3 4

[Requirements] [FFE] python-troveclient 5.1.1
by Lingxian Kong 16 Sep '20

16 Sep '20

Hi, I'd like to ask FFE for bumping python-troveclient to 5.1.1[1] in Victoria. The patch version 5.1.1 includes a fix for multi-region support for python-troveclient[2] OSC plugin. [1]: https://review.opendev.org/#/c/752122/ [2]: https://review.opendev.org/#/q/Ia0580a599fc2385d54def4e18e0780209b82eff7 --- Lingxian Kong Senior Software Engineer Catalyst Cloud www.catalystcloud.nz

2 1

[openstack][cinder] volume revert to snapshot on stein
by Ignazio Cassano 16 Sep '20

16 Sep '20

Hello Stackers, does cinder revert to snapshot works on stein ? The command cinder revert-to-snapshot returns: error: argument <subcommand>: invalid choice: u'revert-to-snapshot' *I also tried using cinder v3 api* post /v3/{project_id}/volumes/{volume_id} /action but it returns : {"itemNotFound": {"message": "The resource could not be found.", "code": 404}} Please, anyone could help me ? Ignazio

2 3

[tripleo] distributed-project-leadership RFC
by Wesley Hayutin 16 Sep '20

16 Sep '20

Greetings, The TripleO project would like to hear your thoughts with regards to breaking down the typical PTL role into smaller roles. Please read through this document [1] and share your thoughts in this thread. If you are interested in growing your leadership skills and being responsible for any of the roles listed there please also indicate that in your response. Thanks all! [1] https://governance.openstack.org/tc/resolutions/20200803-distributed-projec…

3 4

[cinder] propose Lucio Seki for cinder core
by Brian Rosmaita 16 Sep '20

16 Sep '20

Lucio Seki (lseki on IRC) has been very active this cycle doing reviews, answering questions in IRC, and participating in the Cinder weekly meetings and at the midcycles. He's been particularly thorough and helpful in his reviews of backend drivers, and has also been helpful in giving pointers to new driver maintainers who are setting up third party CI for their drivers. Having Lucio as a core reviewer will help improve the team's review bandwidth without sacrificing review quality. In the absence of objections, I'll add Lucio to the core team just before the next Cinder team meeting (Wednesday, 16 September at 1400 UTC in #openstack-meeting-alt). Please communicate any concerns to me before that time. cheers, brian

10 11

[tripleo] Call for Topics
by Wesley Hayutin 16 Sep '20

16 Sep '20

Greetings, You folks know the drill. Please take a moment to add topics for discussion for the Wallaby PTG. https://etherpad.opendev.org/p/tripleo-wallaby-topics Thanks all!

1 0

[ansible-sig][openstack-ansible-modules][PTG] Wallaby PTG for Openstack Ansible collections
by Sagi Shnaidman 16 Sep '20

16 Sep '20

Hi, all We have a scheduled session for Openstack Ansible collection project in PTG: Wednesday 16.00 - 17.00 UTC The Etherpad for it is in https://etherpad.opendev.org/p/os-ansible-wallaby-ptg Please add your name if you plan to attend, questions and topics that you want to address in PTG. If it will be too much for one session, I'll schedule more. Thanks -- Best regards Sagi Shnaidman

1 0

[osc] load command in the CLI is no longer?
by Eric K. Miller 16 Sep '20

16 Sep '20

Hi, We use the "load" command in various OpenStack client CLIs to load a list of commands to run in a single session (one example is when loading a large number of Gnocchi metrics manually). However, when testing with a newer version of the OpenStack Client, it looks like it doesn't exist anymore. OSC version 4.0.0 has the load command, version 5.2.1 does not. Did something happen that justified removing this? Thanks! Eric

1 0

[Neutron] vxlan to vlan bridge
by Ignazio Cassano 16 Sep '20

16 Sep '20

Hello Stackers, is it possibile to create a vxlan to vlan bridge in openstack like vmware nsx does? Thanks Ignazio

3 2

neutron-l3-agent:l3-agent has been creating the "keepalived -P -f..." process
by 宋贺 15 Sep '20

15 Sep '20

we create a '--distributed=True,--ha=True" router in OpenStack Newton. We found that l3-agent cannot read the pid file of keepalived, thus creating the keepalived process again. As a result, a large number of keepalived processes appear on the host node.As picture 1 in the attachment. This problem can be solved when we execute the following content and modify the permissions of the pid file [root@fusion0 ~]# chown neutron:neutron /var/lib/neutron/ha_confs/2a20ab37-ffe8-4955-8148-cefdcb5b6be3.pid [root@fusion0 ~]# chown neutron:neutron /var/lib/neutron/ha_confs/2a20ab37-ffe8-4955-8148-cefdcb5b6be3.pid-vrrp I want to know how to solve this problem completely from the perspective of neutron. neutron-l3-agent.log file is in the attachment.

1 0

[all][elections][ptl][tc] Combined PTL/TC Election Season
by Jeremy Stanley 15 Sep '20

15 Sep '20

Election details: https://governance.openstack.org/election/ The nomination period officially begins Sep 22, 2020 23:45 UTC. Please read the stipulations and timelines for candidates and electorate contained in this governance documentation. Be aware that the Wallaby cycle elections are a few weeks behind schedule[1]. We're still making sure the new TC is confirmed and any PTL runoff polls are closed and resolved before Victoria release day. Due to circumstances of timing, PTL and TC elections for the coming cycle will run concurrently; deadlines for their nomination and voting activities are synchronized but will still use separate ballots. Please note, if only one candidate is nominated as PTL for a project team during the PTL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a project team's PTL position. If teams do not produce any PTL candidate during the nomination period, or are interested in considering alternatives prior to nominations, the TC may consider requests to switch to the new distributed leadership model they recently documented[2]. In keeping with the established plan[3] to gradually reduce the size of the Technical Committee, we will only fill four (4) seats in this coming election. There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you which to discuss in private please email any of the election officials[4] so that we may address your concerns. [1] https://governance.openstack.org/tc/reference/election-exceptions.html [2] https://governance.openstack.org/tc/resolutions/20200803-distributed-projec… [3] https://governance.openstack.org/tc/reference/charter.html#number-of-seats-… [4] https://governance.openstack.org/election/#election-officials -- Jeremy Stanley on behalf of the OpenStack Technical Election Officials

1 0

[tripleo][ci] Red Tuesday
by Wesley Hayutin 15 Sep '20

15 Sep '20

Greetings, Well if you were working today you know there were several issues upstream. pip issues: https://bugs.launchpad.net/tripleo/+bug/1449136 containers-multinode: https://bugs.launchpad.net/tripleo/+bug/1895290 https://bugs.launchpad.net/tripleo/+bug/1895288 validations: https://launchpad.net/bugs/1895507 Everything I know of atm is either merged on or in the gate. https://review.opendev.org/#/c/751828/ https://review.opendev.org/#/c/751653/ There is a lot going on, please report bugs to launchpad and ping nick-ruck or nick-rover in #tripleo if you see something else. Thanks to everyone helping to push things along. 0/

1 0

Re: [Openstack-mentoring] Neutron subnet with DHCP relay - continued
by Thomas King 15 Sep '20

15 Sep '20

I got the metadata network accessible over a routed subnet! The breakthrough was making sure I pointed 169.254.169.254 to the Neutron DHCP address rather than the physical or bridge IP address, this route added to the physical router (L3 switch) that serves the subnet hosting the Ironic controller. Also, I made sure to add a host route for 169.254.169.254 to the baremetal remote subnet in Neutron so the baremetal nodes will have a proper route to the metadata subnet. There is still some network tweaking left to do. We have a separate subnet for ESXi mgmt vmkernels since they use virtual MAC addresses and neutron doesn't recognize them. However, enabling DHCP relay for that separate subnet breaks routing which also breaks cleaning and deploying, and I need to find out where. This is huge for our metal-as-a-service offering! Thanks, Tom King On Sat, Aug 22, 2020 at 12:53 AM Thomas King <thomas.king(a)gmail.com> wrote: > Ok, thanks. > > On Fri, Aug 21, 2020, 11:39 PM Ruslanas Gžibovskis <ruslanas(a)lpic.lt> > wrote: > >> No, I didn't. In the beginning I wanted to say "yes" but that is for >> overcloud. >> >> Now I am thinking, maybe even I do no have metadata on undercloud.... >> >> Will need to check on Monday. >> >> 2020-08-22, št 00:51, Thomas King <thomas.king(a)gmail.com> rašė: >> >>> Finally got it worked out except for reaching the metadata service IP >>> (169.254.169.254) from a remote network. Did you put specific routes in >>> place for that IP address on your physical network? >>> >>> Tom >>> >>> On Wed, Jul 22, 2020 at 3:19 AM Ruslanas Gžibovskis <ruslanas(a)lpic.lt> >>> wrote: >>> >>>> Ok >>>> >>>> here is a small copy paste: >>>> http://paste.openstack.org/show/o4Uay0DYbAdkcfUJGOLV/ >>>> >>>> also have relaunched previous commands, as I have redeployed overcloud >>>> :) >>>> >>>> and maybe you will be interested, in undercloud containers running: >>>> >>>> (undercloud) [stack@remote-u overcloud]$ sudo podman ps >>>> CONTAINER ID IMAGE >>>> COMMAND CREATED STATUS >>>> PORTS NAMES >>>> 39c684172ce7 >>>> docker.io/tripleomaster/centos-binary-neutron-dhcp-agent:current-tripleo >>>> /usr/sbin/dnsmasq... 7 days ago Up 7 days ago >>>> neutron-dnsmasq-qdhcp-e6d6c50b-fb69-4375-bb7d-0f6e0cfed5cb >>>> 30ccb169e666 >>>> docker.io/tripleomaster/centos-binary-ironic-pxe:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> ironic_pxe_http >>>> 6a62e08e8e10 >>>> docker.io/tripleomaster/centos-binary-ironic-pxe:current-tripleo >>>> /bin/bash -c BIND... 7 days ago Up 7 days ago >>>> ironic_pxe_tftp >>>> e4cbad7f7488 >>>> docker.io/tripleomaster/centos-binary-neutron-l3-agent:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> neutron_l3_agent >>>> d78d3828c420 >>>> docker.io/tripleomaster/centos-binary-neutron-openvswitch-agent:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago neutron_ovs_agent >>>> 3b67b6a69a87 >>>> docker.io/tripleomaster/centos-binary-neutron-dhcp-agent:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> neutron_dhcp >>>> 46d403293b54 >>>> docker.io/tripleomaster/centos-binary-swift-proxy-server:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> swift_proxy >>>> 15a9792d6f62 >>>> docker.io/tripleomaster/centos-binary-swift-object:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> swift_rsync >>>> 0e6cd094d6dc >>>> docker.io/tripleomaster/centos-binary-swift-object:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> swift_object_updater >>>> 80b7f26e742d >>>> docker.io/tripleomaster/centos-binary-swift-object:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> swift_object_server >>>> 765f79633499 >>>> docker.io/tripleomaster/centos-binary-swift-proxy-server:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> swift_object_expirer >>>> 0e53da61af88 >>>> docker.io/tripleomaster/centos-binary-swift-container:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> swift_container_updater >>>> 8c14cef58eb3 >>>> docker.io/tripleomaster/centos-binary-swift-account:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> swift_account_server >>>> 12930a63dc12 >>>> docker.io/tripleomaster/centos-binary-swift-container:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> swift_container_server >>>> 8a5cd45208c0 >>>> docker.io/tripleomaster/centos-binary-swift-account:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> swift_account_reaper >>>> b871400bfdd9 >>>> docker.io/tripleomaster/centos-binary-mistral-executor:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> mistral_executor >>>> 3e98e5f83f09 >>>> docker.io/tripleomaster/centos-binary-mistral-event-engine:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> mistral_event_engine >>>> 52d711dffca3 >>>> docker.io/tripleomaster/centos-binary-mistral-engine:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> mistral_engine >>>> 23dec12e650f >>>> docker.io/tripleomaster/centos-binary-iscsid:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago iscsid >>>> bafff227d9d7 >>>> docker.io/tripleomaster/centos-binary-haproxy:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago haproxy >>>> 4d17cbd60698 >>>> docker.io/tripleomaster/centos-binary-ironic-inspector:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> ironic_inspector_dnsmasq >>>> f77e49246c35 >>>> docker.io/tripleomaster/centos-binary-ironic-inspector:current-tripleo >>>> kolla_start 7 days ago Up 7 days ago >>>> ironic_inspector >>>> ec70f40bba04 >>>> docker.io/tripleomaster/centos-binary-rabbitmq:current-tripleo >>>> kolla_start 5 weeks ago Up 4 weeks ago rabbitmq >>>> f09c9a129d85 >>>> docker.io/tripleomaster/centos-binary-memcached:current-tripleo >>>> kolla_start 5 weeks ago Up 4 weeks ago >>>> memcached >>>> 0eb1e953dcaa >>>> docker.io/tripleomaster/centos-binary-nova-compute-ironic:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> nova_compute >>>> ac78778d2cb0 >>>> docker.io/tripleomaster/centos-binary-ironic-neutron-agent:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> ironic_neutron_agent >>>> 8660bf80fd9c >>>> docker.io/tripleomaster/centos-binary-ironic-conductor:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> ironic_conductor >>>> 9dead5068168 >>>> docker.io/tripleomaster/centos-binary-mistral-api:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> mistral_api >>>> f5c1c9d6166c >>>> docker.io/tripleomaster/centos-binary-ironic-api:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> ironic_api >>>> 48899d782dd5 >>>> docker.io/tripleomaster/centos-binary-nova-api:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> nova_api_cron >>>> 1b19c94834e8 >>>> docker.io/tripleomaster/centos-binary-nova-api:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago nova_api >>>> 5b66d128c930 >>>> docker.io/tripleomaster/centos-binary-glance-api:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> glance_api >>>> 7e63cdb8d6b4 >>>> docker.io/tripleomaster/centos-binary-placement-api:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> placement_api >>>> 2db105676f8b >>>> docker.io/tripleomaster/centos-binary-zaqar-wsgi:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> zaqar_websocket >>>> d3e5ae7368e6 >>>> docker.io/tripleomaster/centos-binary-zaqar-wsgi:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago zaqar >>>> 6332e26b40ec >>>> docker.io/tripleomaster/centos-binary-nova-scheduler:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> nova_scheduler >>>> a5b0e0904f0c >>>> docker.io/tripleomaster/centos-binary-nova-conductor:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> nova_conductor >>>> 4460302d97c8 >>>> docker.io/tripleomaster/centos-binary-neutron-server:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> neutron_api >>>> d418deb9ea13 >>>> docker.io/tripleomaster/centos-binary-cron:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> logrotate_crond >>>> 7225ff80b26d >>>> docker.io/tripleomaster/centos-binary-heat-engine:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> heat_engine >>>> 84d22b3b1663 >>>> docker.io/tripleomaster/centos-binary-heat-api:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago >>>> heat_api_cron >>>> 226e0d839772 >>>> docker.io/tripleomaster/centos-binary-heat-api:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago heat_api >>>> 6f7871a64325 >>>> docker.io/tripleomaster/centos-binary-keystone:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago keystone >>>> 8402ff823012 >>>> docker.io/tripleomaster/centos-binary-mariadb:current-tripleo >>>> kolla_start 7 weeks ago Up 4 weeks ago mysql >>>> (undercloud) [stack@remote-u overcloud]$ >>>> >>>

1 0

[Neutron] memchached connections
by Tony Liu 15 Sep '20

15 Sep '20

I restarted neutron-server on all 3 nodes. Those memcached connections from neutron-server are gone. Everything is back to normal. It seems like that memcached connections are not closed properly in neutron-server. The connections pile up over time. Is there any know issue related? Could any Neutron experts comment here? Thanks! Tony > -----Original Message----- > From: Tony Liu <tonyliu0592(a)hotmail.com> > Sent: Friday, September 11, 2020 2:26 PM > To: openstack-discuss <openstack-discuss(a)lists.openstack.org> > Subject: memchached connections > > Hi, > > Is there any guidance or experiences to estimate the number of memcached > connections? > > Here is memcached connection on one of the 3 controllers. > Connection number is the total established connections to all 3 > memcached nodes. > > Node 1: > 10 Keystone workers have 62 connections. > 11 Nova API workers have 37 connections. > 6 Neutron server works have 4304 connections. > 1 memcached has 4973 connections. > > Node 2: > 10 Keystone workers have 62 connections. > 11 Nova API workers have 30 connections. > 6 Neutron server works have 3703 connections. > 1 memcached has 4973 connections. > > Node 3: > 10 Keystone workers have 54 connections. > 11 Nova API workers have 15 connections. > 6 Neutron server works have 6541 connections. > 1 memcached has 4973 connections. > > Before I increase the connection limit for memcached, I'd like to > understand if all the above is expected? > > How Neutron server and memcached take so many connections? > > Any elaboration is appreciated. > > BTW, the problem leading me here is memcached connection timeout, which > results all services depending on memcached stop working properly. > > > Thanks! > Tony

2 3

[tc] weekly update
by Mohammed Naser 15 Sep '20

15 Sep '20

Hi everyone, Here's an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. We've also included a few references to some important mailing list threads that you should check out. # Patches ## Open Reviews - Remove tc:approved-release tag https://review.opendev.org/749363 - Retire the devstack-plugin-zmq project https://review.opendev.org/748731 - Add openstack/osops to Ops Docs and Tooling SIG https://review.opendev.org/749835 - Retire devstack-plugin-pika project https://review.opendev.org/748730 - Reinstate weekly meetings https://review.opendev.org/#/c/749279/ - Resolution to define distributed leadership for projects https://review.opendev.org/744995 - Add assert:supports-standalone https://review.opendev.org/722399 ## Project Updates - Add openstack-helm-deployments to openstack-helm https://review.opendev.org/748302 - Add openstack-ansible/os_senlin role https://review.opendev.org/748677 - kolla-cli: deprecation - Mark as deprecated https://review.opendev.org/749694 ## General Changes - Create starter-kit:kubernetes-in-virt tag https://review.opendev.org/736369 # Other Reminders - PTG Brainstorming: https://etherpad.opendev.org/p/tc-wallaby-ptg Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[nova][barbican][qa] barbican-tempest-plugin change breaking bfv [ceph]
by Mohammed Naser 15 Sep '20

15 Sep '20

Hi everyone, We just had our gating break due to a change merging inside barbican-tempest-plugin which is the following: https://review.opendev.org/#/c/515210/ It is resulting in an exception in our CI: 2020-08-26 18:04:32.663188 | controller | Response - Headers: {'content-length': '257', 'content-type': 'application/json', 'x-openstack-request-id': 'req-7f55e463-c3de-445e-a814-ef79c5f21235', 'connection': 'close', 'status': '409', 'content-location': 'http://glance.openstack.svc.cluster.local/v2/images/dec14e17-0870-415f-82a6…'} 2020-08-26 18:04:32.663200 | controller | Body: b'{"message": "Image dec14e17-0870-415f-82a6-140c1b7e4a39 could not be deleted because it is in use: The image cannot be deleted because it is in use through the backend store outside of Glance.<br /><br />\\n\\n\\n", "code": "409 Conflict", "title": "Conflict"}' This is usually because it's trying to delete the Glance image before deleting an instance that is using it, the specific test that is failing is: barbican_tempest_plugin.tests.scenario.test_certificate_validation.CertificateValidationTest.test_signed_image_invalid_cert_boot_failure[compute,id-6d354881-35a6-4568-94b8-2204bbf67b29,image] This test landed yesterday, we're blacklisting the scenario right now. I do find it quite interesting that in the logs here: http://paste.openstack.org/show/797186/ That the instance reports that it _does_ indeed delete it, so maybe we are trying to delete the image afterwards _too quickly_ and need to wait for Nova to clean up? I'd love to enable that test again and continue full coverage, happy to hear discussion. Thanks Mohammed -- Mohammed Naser VEXXHOST, Inc.

2 1

[ops] picking up some activity
by Chris Morgan 15 Sep '20

15 Sep '20

Greetings! The OpenStack Operators ("ops") meetups team will attempt to have an IRC meeting at the normal time and place (#openstack-operators on freenode at 10am EST/DST) on *Sept 15th*( following a period of complete inactivity for obvious reasons. If you're an official member of the team or even just interested in what we do, please feel free to join us. Whilst we can't yet contemplate resuming in-person meetups during this global pandemic, we can resume attempting to build the openstack operators community, share knowledge and perhaps even do some more virtual get-togethers. See you then Chris on behalf of the openstack ops meetups team -- Chris Morgan <mihalis68(a)gmail.com>

3 2

Need help for stack update feature for scaling out use case or add new resources
by Rahul Kumar 15 Sep '20

15 Sep '20

Hi Team, I have a stack template with 3 nodes , each node having a volume attached ! Now i updated my template with additional node and additional volume for that node ! This results in user_data update of a node in template ! And when i perform stack update feature , it gives me error: Invalid volume: Volume 01e40c6e-4467-42fe-ba9d-ce7012db8978 status must be available or downloading to reserve, but the current status is in-use. This shows for the node (where user_data is changed) and yes it is currently in use ! Then how one can update the stack using stack update feature of openstack with volumes ? Rahul

1 0

device compatibility interface for live migration with assigned devices
by Yan Zhao 15 Sep '20

15 Sep '20

hi folks, we are defining a device migration compatibility interface that helps upper layer stack like openstack/ovirt/libvirt to check if two devices are live migration compatible. The "devices" here could be MDEVs, physical devices, or hybrid of the two. e.g. we could use it to check whether - a src MDEV can migrate to a target MDEV, - a src VF in SRIOV can migrate to a target VF in SRIOV, - a src MDEV can migration to a target VF in SRIOV. (e.g. SIOV/SRIOV backward compatibility case) The upper layer stack could use this interface as the last step to check if one device is able to migrate to another device before triggering a real live migration procedure. we are not sure if this interface is of value or help to you. please don't hesitate to drop your valuable comments. (1) interface definition The interface is defined in below way: __ userspace /\ \ / \write / read \ ________/__________ ___\|/_____________ | migration_version | | migration_version |-->check migration --------------------- --------------------- compatibility device A device B a device attribute named migration_version is defined under each device's sysfs node. e.g. (/sys/bus/pci/devices/0000\:00\:02.0/$mdev_UUID/migration_version). userspace tools read the migration_version as a string from the source device, and write it to the migration_version sysfs attribute in the target device. The userspace should treat ANY of below conditions as two devices not compatible: - any one of the two devices does not have a migration_version attribute - error when reading from migration_version attribute of one device - error when writing migration_version string of one device to migration_version attribute of the other device The string read from migration_version attribute is defined by device vendor driver and is completely opaque to the userspace. for a Intel vGPU, string format can be defined like "parent device PCI ID" + "version of gvt driver" + "mdev type" + "aggregator count". for an NVMe VF connecting to a remote storage. it could be "PCI ID" + "driver version" + "configured remote storage URL" for a QAT VF, it may be "PCI ID" + "driver version" + "supported encryption set". (to avoid namespace confliction from each vendor, we may prefix a driver name to each migration_version string. e.g. i915-v1-8086-591d-i915-GVTg_V5_8-1) (2) backgrounds The reason we hope the migration_version string is opaque to the userspace is that it is hard to generalize standard comparing fields and comparing methods for different devices from different vendors. Though userspace now could still do a simple string compare to check if two devices are compatible, and result should also be right, it's still too limited as it excludes the possible candidate whose migration_version string fails to be equal. e.g. an MDEV with mdev_type_1, aggregator count 3 is probably compatible with another MDEV with mdev_type_3, aggregator count 1, even their migration_version strings are not equal. (assumed mdev_type_3 is of 3 times equal resources of mdev_type_1). besides that, driver version + configured resources are all elements demanding to take into account. So, we hope leaving the freedom to vendor driver and let it make the final decision in a simple reading from source side and writing for test in the target side way. we then think the device compatibility issues for live migration with assigned devices can be divided into two steps: a. management tools filter out possible migration target devices. Tags could be created according to info from product specification. we think openstack/ovirt may have vendor proprietary components to create those customized tags for each product from each vendor. e.g. for Intel vGPU, with a vGPU(a MDEV device) in source side, the tags to search target vGPU are like: a tag for compatible parent PCI IDs, a tag for a range of gvt driver versions, a tag for a range of mdev type + aggregator count for NVMe VF, the tags to search target VF may be like: a tag for compatible PCI IDs, a tag for a range of driver versions, a tag for URL of configured remote storage. b. with the output from step a, openstack/ovirt/libvirt could use our proposed device migration compatibility interface to make sure the two devices are indeed live migration compatible before launching the real live migration process to start stream copying, src device stopping and target device resuming. It is supposed that this step would not bring any performance penalty as -in kernel it's just a simple string decoding and comparing -in openstack/ovirt, it could be done by extending current function check_can_live_migrate_destination, along side claiming target resources.[1] [1] https://specs.openstack.org/openstack/nova-specs/specs/stein/approved/libvi… Thanks Yan

14 118

[manila][ptg] Wallaby PTG Planning
by Goutham Pacha Ravi 14 Sep '20

14 Sep '20

Hello Zorillas and Interested Stackers, As you're aware, the virtual PTG for the Wallaby release cycle is between October 26-30, 2020. If you haven't registered yet, you must do so as soon as possible! [1]. We've signed up for some slots on the PTG timeslots ethercalc [2]. The PTG Planning etherpad [3] is now live. Please go ahead and add your name/irc nick and propose any topics. You may propose topics even if you wouldn't like to moderate the discussion. Thanks, and hope to see you all there! Goutham [1] https://www.eventbrite.com/e/project-teams-gathering-october-2020-tickets-1… [2] https://ethercalc.openstack.org/7xp2pcbh1ncb [3] https://etherpad.opendev.org/p/wallaby-ptg-manila-planning

1 0

[Outreachy] Call for mentors, projects by Sep 29
by Samuel de Medeiros Queiroz 14 Sep '20

14 Sep '20

Hey Stackers, *TL;DR OpenStack is participating in the Outreachy internship program once again!* *Please submit projects as soon as possible, with final deadline being Sept. 29, 2020 at 4 pm UTC: https://www.outreachy.org/communities/cfp/openstack/ <https://www.outreachy.org/communities/cfp/openstack/>* Outreachy's goal is to support people from groups underrepresented in the technology industry. Interns will work remotely with mentors from our community. We are seeking mentors to propose projects that Outreachy interns can work on during their internship. If you want help crafting your project proposal, please contact me < samueldmq(a)gmail.com> or Mahati Chamarthy <mahati.chamarthy(a)gmail.com>. Mentors should read the mentor FAQ: https://www.outreachy.org/mentor/mentor-faq Full details about the Outreachy program and the internship timeline can be found on the Call for Participation page on the Outreachy website: https://www.outreachy.org/communities/cfp/ Thank you, Samuel Queiroz

1 0

memchached connections
by Tony Liu 14 Sep '20

14 Sep '20

Hi, Is there any guidance or experiences to estimate the number of memcached connections? Here is memcached connection on one of the 3 controllers. Connection number is the total established connections to all 3 memcached nodes. Node 1: 10 Keystone workers have 62 connections. 11 Nova API workers have 37 connections. 6 Neutron server works have 4304 connections. 1 memcached has 4973 connections. Node 2: 10 Keystone workers have 62 connections. 11 Nova API workers have 30 connections. 6 Neutron server works have 3703 connections. 1 memcached has 4973 connections. Node 3: 10 Keystone workers have 54 connections. 11 Nova API workers have 15 connections. 6 Neutron server works have 6541 connections. 1 memcached has 4973 connections. Before I increase the connection limit for memcached, I'd like to understand if all the above is expected? How Neutron server and memcached take so many connections? Any elaboration is appreciated. BTW, the problem leading me here is memcached connection timeout, which results all services depending on memcached stop working properly. Thanks! Tony

3 6

WIndows 10 instance hostname not updating
by its-openstack＠zohocorp.com 14 Sep '20

14 Sep '20

Dear openstack, I have installed openstack train branch, I am facing issue with windows image. all windows 10 instance dosen't get its hostname updated from the metadata, but able to get the metadata(hostname) from inside the instance using powershell. ``` $ Invoke-WebRequest http://169.254.169.254/latest/meta-data/hostname -UseBasicParsing ``` windows2016 instance no issue. using the stable cloudbase-init package for preparation of windows 10 (tried bot in v1909 and v2004). windows2016 server dosen't have this issue. if you would so kindly help us with this issue Regards sysadmin

2 1

[TC] Seats Available in Upcoming Elections
by Kendall Nelson 14 Sep '20

14 Sep '20

Hello :) Wanted to make you all aware of the conversation that happened in the TC channel today[1] which was a reminder of a previous conversation about reducing the size of the TC. It was concluded by the previous TC that we would gradually reduce from 13 seats to 9 over the course of two elections (dropping two seats each election). From that point on, we would continue with the normal cadence of cycling about half the seats each election ( 4 seats and 5 seats)[2]. So, this coming election 6 members will be up for reelection with 4 seats available. Hope this all makes sense! -Kendall Nelson (diablo_rojo) - Both a TC member up for re-election and a former election official :) [1] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/latest.log.html#t202… [2] https://review.opendev.org/#/c/681266/

1 0

REMINDER: 2020 Virtual Summit: Forum Submissions Now Accepted
by Jimmy McArthur 14 Sep '20

14 Sep '20

Hello Everyone! We are now accepting Forum [1] submissions for the 2020 Virtual Open Infrastructure Summit [2]. Please submit your ideas through the Summit CFP tool [3] through September 14th. Don't forget to put your brainstorming etherpad up on the Virtual Forum page [4]. This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. The timeline for submissions is as follows: Aug 31st | Formal topic submission tool opens: https://cfp.openstack.org. Sep 14th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. Sep 21st | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. Sept 28th | Forum schedule final Oct 19th | Forum begins! If you have questions or concerns, please reach out to speakersupport(a)openstack.org (mailto:speakersupport@openstack.org). Cheers, Jimmy [1] https://wiki.openstack.org/wiki/Forum [2] https://www.openstack.org/summit/2020/ [3] https://cfp.openstack.org [4]https://wiki.openstack.org/wiki/Forum/Virtual2020

4 5

[release] [heat] [karbor] [patrole] [requirements] [swift] [tempest] Cycle with Intermediary Deliverables Needing Releases?
by Kendall Nelson 14 Sep '20

14 Sep '20

Hello! Quick reminder that for deliverables following the cycle-with-intermediary model, the release team will use the latest victoria release available on release week. The following deliverables have done a victoria release, but it was not refreshed in the last two months: - heat-agents - karbor-dashboard - karbor - patrole - requirements - swift - tempest You should consider making a new one very soon, so that we don't use an outdated version for the final release. -Kendall Nelson (diablo_rojo) & the Release Team

1 0

Is Storyboard really the future?
by Radosław Piliszek 14 Sep '20

14 Sep '20

Hi fellow OpenStackers, The subject is the question I am posing. The general recommendation is to use Storyboard for new projects [1]. However, Storyboard does not seem to be receiving enough love recently [2] [3]. It's generally deemed as slow [4] and is missing quite a few usability enhancements [2]. Considering the alternative, and the actual previous recommendation, is Launchpad, I find it no-brainer to revert to recommending Launchpad still, even paving a way for projects wishing to escape the Storyboard nightmare. :-) Don't get me wrong, I really like the Story/Task orientation but Storyboard results in a frustrating experience. In addition to being slow, it has issues with search/filter, sorting and pagination which make issue browsing an utter pain. I know Launchpad is not without issues but it's certainly a much better platform at the moment. And many projects are still there. The Launchpad-Storyboard split is also introducing confusion for users [5] and coordinability issues for teams as we need to cross-link manually to get proper visibility. All in all, I ask you to consider recommending Launchpad again and encourage OpenStack projects to move to Launchpad. Extra note: I find it in a similar spot as ask.o.o - nice it has been tried, but unfortunately it did not stand the test of time. [1] https://docs.opendev.org/opendev/infra-manual/latest/creators.html [2] https://storyboard.openstack.org/#!/project/opendev/storyboard [3] https://opendev.org/opendev/storyboard/commits/branch/master [4] https://storyboard.openstack.org/#!/story/2007829 [5] https://storyboard.openstack.org/#!/story/2000890 -yoctozepto

5 11

[oslo] PTG Planning
by Ben Nemec 14 Sep '20

14 Sep '20

It's that time again. I've created an etherpad[0] for Oslo PTG planning. If you have anything to discuss at the PTG, please add it to the list. I've already requested a couple of hours of PTG time, but we can adjust that if we have more or less to talk about than normal. I don't have time/place details there yet, but it will be the same as last time: two hours starting at the regular meeting time. Thanks. -Ben 0: https://etherpad.opendev.org/p/oslo-wallaby-topics

1 0

Re: Is Storyboard really the future?
by Gaël THEROND 14 Sep '20

14 Sep '20

> > ---------- Forwarded message ---------- > From: Thomas Goirand <zigo(a)debian.org> > To: openstack-discuss <openstack-discuss(a)lists.openstack.org> > Cc: > Bcc: > Date: Mon, 14 Sep 2020 09:22:08 +0200 > Subject: Re: Is Storyboard really the future? > On 9/14/20 8:59 AM, Radosław Piliszek wrote: > > > On Sun, Sep 13, 2020 at 8:46 PM Thomas Goirand <thomas(a)goirand.fr> > wrote: > > >> > > >> On 9/10/20 6:45 PM, Radosław Piliszek wrote: > > >>> I feel you. I could not so far convince anyone to support me to work > > >>> on it, mostly because > > >>> Jira/GitHub/GitLab/Launchpad exists. > > >>> Not to mention many small internal projects are happy with just > Trello. :-) > > >> > > >> Did you just try to list all the non-free services you could in this > > >> thread? Seriously, don't you care a little bit? You probably don't > > >> realize it, but that's shocking, at least for me, and hopefully I'm not > > >> the only one. > > > > > > I feel offended by the accusations. > > > I *do* care about open source. > > > > > > Jeremy has already answered regarding GitLab and Launchpad. > > > Let's not forget GitHub actually *is* the largest, diverse open source > > > community, > > > even though the service itself is not. It hurts me as well so please > don't just > > > randomly attack people mentioning non-free software. > > > It can support open source software as well. > > > > You're the one mentioning Jira, GitHub, Trello as possible solution to > > solve the fact that you don't like Storyboard. This is IMO very far from > > the spirit of free software. Sorry if you took it as a personal attack: > > there's nothing personal here, just a strong opposition to using this > > kind of services. > > > > The fact that many projects are using these non-free services to produce > > free software is actually a problem, not a solution. Same for Github > > being (probably) the largest repository of free software: that's a huge > > problem, as huge as the number of projects hosted. Lucky, many just > > think of it as just free hosting and nothing more. > > > > Gitlab being open-core, as Jeremy pointed out, is also a problem (anyone > > that knows about the beginning of OpenStack and Eucalyptus knows why > > open core is problematic). > > > > > I did not propose that in any part. Launchpad is FLOSS and that is my > proposal. > > > The general idea behind my mail was to emphasise that Storyboard has > > > great aspirations > > > and assumptions but is far from delivering its full potential so > > > should not be recommended without > > > giving background and other possible solutions. > > > > Launchpad is hardly installable, and is tightly connected to > > Canonical/Ubuntu. It is a very good thing that the OpenStack community > > has made efforts to get out of it. It is IMO counter-productive to push > > projects to either go back to launchpad, or not migrate to Storyboard. > > > > The only viable solution is to contribute and make Storyboard better, or > > switching to another existing free software. There are many out there > > that could have done the job. > > > > Cheers, > > > > Thomas Goirand (zigo) > > > > > > _______________________________________________ > > openstack-discuss mailing list > > openstack-discuss(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss Hi everyone, So, thomas, your message was rude and can hurt because Yocto didn’t suggested to use those tools, he was answering you that he feel the pain as everyone is suggesting those tool when you talk with people on IRC etc. Even if I do understand your point and know the importance of being autonomous and do not rely on non-FLOSS software, the thruth being all those discussions is the pain in the ass that it is to contribute to Openstack projects compared with other Open source software based on Github or Github like workflow. The opensource community and especially the Openstack one need to understand that people really get a limited amount of time and so if you want to attract more people your contribution process have to be streamlined and on par with what most of us developers do experience on everyday. The foundation made a first step toward that by migrating every project on gitea, and honestly, I’m still amazed that while migrating those projects it wasn’t decided to use the issues/projects feature of gitea. There even is a cicd zuul plugin for gitea. As a community we propose things, but if the community don’t use them, it’s because it’s not what they’re waiting for. We also need to step back from time to time and admit that one software need to sunset and be migrated elsewhere. We want a fully floss project to host it? Fine it’s perfectly valid argument, then just reuse what’s already there with gitea and redirect development effort of the abandonned software to the new platform in order to support the missing part if ever required! > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss>

4 7

[cinder] need comments TODAY about DB handling for default_types
by Brian Rosmaita 14 Sep '20

14 Sep '20

There's a discussion going on about https://review.opendev.org/#/c/737707/23 , namely about how to handle the new default_types table. My view is that since it simply records a relation between a project and a volume_type, it's not the kind of thing that we need to keep a history of, and entries could be hard-deleted. The current patch keeps a history by introducing an additional is_active column. The additional complexity is worth it if we want to keep a history of this relation, but is not if we don't. Please leave your thoughts on the patch as soon as possible (i.e., in the next few hours) so Rajat can complete this feature. thanks, brian

2 1

[tripleo] TripleO CI Summary: Unified Sprint 32
by Rafael Folco 14 Sep '20

14 Sep '20

Greetings, The TripleO CI team has just completed **Unified Sprint 32** (Aug 21 thru Sep 10). The following is a summary of completed work during this sprint cycle: - Created new container build w/ ubi-8 and overcloud image jobs for rhos-16.2. - Created new rhos-16.2 integration and component pipelines with standalone job, OVB jobs, and standalone scenario jobs. - Added more jobs to the component and integration pipelines, like scenario12. - Changed promoter tests to cover TCIB/Kolla builds and container naming differences across branches (openstack-* vs distro-binary-*). - Continued the necessary changes to switch to the new configuration engine in promoter code. - Continued making improvements to the Tempest scenario manager. - Started design of upstream jobs to run w/ a parent that builds all packages and containers and children jobs that consume these artifacts. This will avoid the use of an upstream container registry. - Merged upstream parent/child jobs for centos-8 jobs running against openstack/tripleo-ci. https://review.opendev.org/#/c/747591/ - We are limiting where this new type of upstream job design is running atm to ensure quality and consistency. - More information can be found https://hackmd.io/ermQSlQ-Q-mDtZkNN2oihQ - Initial design for the dependency pipeline design to early detect breakages in the OS. - https://hackmd.io/I_CFKPXHTza-5i2kFDIs5Q#Dependency-Pipeline - Initial design for elastic-recheck service. - https://hackmd.io/HQ5hyGAOSuG44Le2x6YzUw - Ruck/Rover recorded notes [1]. The planned work for the next sprint extends the work started in the previous sprint and focuses on the following: - Continue adding jobs to RHOS 16.2 pipelines. - Apply new promoter configuration engine changes to consolidate all promoters into the same code. - Start a PoC implementation of the new dependency pipeline. - Start elastic-recheck containerization work. - Create upstream parent jobs to build containers for multiple jobs. - Continue the design and socialization of the openstack-tempest-skiplist project. The Ruck and Rover for this sprint are Bhagyashri Shewale (bhagyashris) and Rafael Folco (rfolco). Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Ruck/rover notes to be tracked in hackmd [2]. Thanks, rfolco [1] https://hackmd.io/FUalpr55TJuy28QLp2tLng [2] https://hackmd.io/7Q0YO5JKS0agcf9qwoD4IQ <https://hackmd.io/7Q0YO5JKS0agcf9qwoD4IQ> -- Folco

1 0

[neutron] Bug deputy report - week of 7.09.2020
by Slawek Kaplonski 14 Sep '20

14 Sep '20

Hi, Last week I was bug deputy. Below is summary of bugs reported during that time: *Critical* * https://bugs.launchpad.net/neutron/+bug/1894857 - lower-constraints job fail on Focal gate failure, Fixed already * https://bugs.launchpad.net/neutron/+bug/1894864 - ContextualVersionConflict with pecan 1.3.3 in networking-midonet - not assigned, related to the issue https://bugs.launchpad.net/neutron/+bug/1895196 *High* * https://bugs.launchpad.net/neutron/+bug/1894913 - haproxy permission issue, sounds as important issue but I didn't had time to confirm it so far - I asked for some more data what have change in their env recently and what could cause this issue, * https://bugs.launchpad.net/neutron/+bug/1894981 - [neutron-dynamic-routing] The self-service network can be bound to the bgp speaker, in progress * https://bugs.launchpad.net/neutron/+bug/1895038 - Flow drop on agent restart with ovs firewall driver - sounds as important issue but I didn't had time to confirm it so far, Already fixed in newer versions * https://bugs.launchpad.net/neutron/+bug/1895196 - pecan>=1.4.0 is greater than upper-constraints.txt - not assigned and it seems that we will need to revert our patch which bumped pecan version in neutron, at least for Victoria cycle, *Medium* * https://bugs.launchpad.net/neutron/+bug/1894825 - placement allocation update accepts only integers from 1 - in progress * https://bugs.launchpad.net/neutron/+bug/1895033 - When using ml2/OVN with other plugins with agents, non-OVN agents are broken for show/update/delete operations, in progress * https://bugs.launchpad.net/neutron/+bug/1895108 - ovn migration: db sync step doesn't work, in progress * https://bugs.launchpad.net/neutron/+bug/1894843 - [dvr_snat] Router update deletes rfp interface from qrouter even when VM port is present on this host - I didn't had time to confirm that, seems like something for L3 subteam, no assigned yet, *Low* * https://bugs.launchpad.net/neutron/+bug/1894799 - For existing ovs interface, the ovs_use_veth parameter don't take effect, in progress * https://bugs.launchpad.net/neutron/+bug/1895401 - [L3][IPv6][DVR] missing address scope mark for IPv6 traffic, in progress, — Slawek Kaplonski Principal software engineer Red Hat

1 0

[kolla-ansible] Ceph in Ussuri
by Klemen Pogacnik 14 Sep '20

14 Sep '20

I've done Ansible playbook to simplify Ceph integration with Openstack. It's based on cephadm-ansible project ( https://github.com/jcmdln/cephadm-ansible) Check: https://gitlab.com/kemopq/it_addmodule-ceph Any suggestions and/or help are appreciated! Klemen

2 1

Kolla-ansible ironic
by Thomas Wakefield 14 Sep '20

14 Sep '20

All- We are new to using OpenStack and are testing out Kolla-ansible with hopes of using Ironic as a deployment tool. Our issue is we can’t use the openstack baremetal command, it’s not found after deployment. Our current test environment is built using Train on CentOS 7. And all other basic OpenStack functionality seems to be working with our Kolla install (nova, glance, horizon, etc). We followed these docs, https://docs.openstack.org/kolla-ansible/train/reference/bare-metal/ironic-… , but when we get to running any “openstack baremetal” commands we don’t seem to have the baremetal commands available in openstack. Globals.yml lines that should be relavent: enable_horizon_ironic: "{{ enable_ironic | bool }}" enable_ironic: "yes" enable_ironic_ipxe: "yes" enable_ironic_neutron_agent: "{{ enable_neutron | bool and enable_ironic | bool }}" enable_ironic_pxe_uefi: "no" #enable_iscsid: "{{ (enable_cinder | bool and enable_cinder_backend_iscsi | bool) or enable_ironic | bool }}" ironic_dnsmasq_interface: "em1" # The following value must be set when enabling ironic, ironic_dnsmasq_dhcp_range: "192.168.2.230,192.168.2.239" ironic_dnsmasq_boot_file: "pxelinux.0" ironic_cleaning_network: "demo-net" Ironic is listed as an installed service, but you can see the baremetal commands are not found: root@orc-os5:~## openstack service list +----------------------------------+------------------+-------------------------+ | ID | Name | Type | +----------------------------------+------------------+-------------------------+ | 0e5119acbf384714ab11520fadce36bb | nova_legacy | compute_legacy | | 2ed83015047249f38b782901e03bcfc1 | ironic-inspector | baremetal-introspection | | 5d7aabf15bdc415387fac54fa1ca21df | ironic | baremetal | | 6d05cdce019347e9940389abed959ffb | neutron | network | | 7d9485969e504b2e90273af75e9b1713 | cinderv3 | volumev3 | | a11dc04e83ed4d9ba65474b9de947d1b | keystone | identity | | ad0c2db47b414b34b86a5f6a5aca597c | glance | image | | dcbbc90813714c989b82bece1c0d9d9f | nova | compute | | de0ee6b55486495296516e07d2e9e97c | heat | orchestration | | df605d671d88496d91530fbc01573589 | cinderv2 | volumev2 | | e211294ca78a418ea34d9c29d86b05f1 | placement | placement | | f62ba90bc0b94cb9b3d573605f800a1f | heat-cfn | cloudformation | +----------------------------------+------------------+-------------------------+ root@orc-os5:~## openstack baremetal openstack: 'baremetal' is not an openstack command. See 'openstack --help'. Did you mean one of these? credential create credential delete credential list credential set credential show Is there anything else that needs configured to activate ironic? Thanks in advance. Tom

3 3

[sdk] openstacksdk vs. server groups
by thoralf schulze 14 Sep '20

14 Sep '20

hi there, the current openstack-sdk crashes while trying to process instances that are part of a server group. to give an example: one of our instances shows up in the output of "openstack-inventory --list --debug" as […] REQ: curl -g -i -X GET https://redacted:8774/v2.1/servers/352307ba-0c06-43e5-ba21-467ec25a4a2e -H "OpenStack-API-Version: compute 2.72" -H "User-Agent: openstacksdk/0.49.0 keystoneauth1/4.2.1 python-requests/2. 22.0 CPython/3.8.2" -H "X-Auth-Token: redacted" -H "X-OpenStack-Nova-API-Version: 2.72" RESP: [200] Connection: Keep-Alive Content-Length: 2024 Content-Type: application/json Date: Fri, 11 Sep 2020 15:22:14 GMT Keep-Alive: timeout=5, max=92 OpenStack-API-Version: compute 2.72 Server: Apache/2.4.29 (Ubuntu) Vary: Op enStack-API-Version,X-OpenStack-Nova-API-Version X-OpenStack-Nova-API-Version: 2.72 x-compute-request-id: req-54078034-3b9e-42bc-afeb-c9c2288db568 x-openstack-request-id: req-54078034-3b9e-42bc-afeb-c9c2288db568 RESP BODY: {"server": {"id": "352307ba-0c06-43e5-ba21-467ec25a4a2e", "name": "dss-test-aaai2hq3gmjc-node-0", "status": "ACTIVE", "tenant_id": "56c37bc705364d34a5f423c531d9e1a7", "user_id": "120258b9dbc7831140ed30b57366fe91feaa77608c7a118da9cf0f6288f1886b", "metadata": {}, "hostId": "16e275df317b4699aa6fdb52b437295c4e3beb83b5e4d15276314660", "image": {"id": "41bb79e0-0962-4162-b9c5-ff178ab61218", "links": [{"rel": "bookmark", "href": "https://redacted/images/41bb79e0-0962-4162-b9c5-ff178ab61218"}]}, "flavor": {"vcpus": 8, "ram": 16384, "disk": 100, "ephemeral": 0, "swap": 0, "original_name": "tx.medium", "extra_specs": {"hw:mem_page_size": "large", "hw:watchdog_action": "reset", "hw_rng:allowed": "true", "hw_rng:rate_bytes": "24", "hw_rng:rate_period": "5000", "trait:CUSTOM_DC_CLASS_TEST": "required"}}, "created": "2020-07-10T07:09:48Z", "updated": "2020-07-10T07:09:59Z", "addresses": {"dss-test": [{"version": 4, "addr": "10.0.0.42", "OS-EXT-IPS:type": "fixed", "OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:62:3e:69"}, {"version": 4, "addr": "10.176.1.154", "OS-EXT-IPS:type": "floating", "OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:62:3e:69"}]}, "accessIPv4": "", "accessIPv6": "", "links": [{"rel": "self", "href": "https://redacted/v2.1/servers/352307ba-0c06-43e5-ba21-467ec25a4a2e"}, {"rel": "bookmark", "href": "https://redacted/servers/352307ba-0c06-43e5-ba21-467ec25a4a2e"}], "OS-DCF:diskConfig": "MANUAL", "progress": 0, "OS-EXT-AZ:availability_zone": "BARZ", "config_drive": "", "key_name": null, "OS-SRV-USG:launched_at": "2020-07-10T07:09:58.000000", "OS-SRV-USG:terminated_at": null, "security_groups": [{"name": "dss-test-aaai2hq3gmjc-secgroup_kube_minion-cjco6vmpgs6j"}], "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": "active", "OS-EXT-STS:power_state": 1, "os-extended-volumes:volumes_attached": [], "locked": false, "description": null, "tags": [], "trusted_image_certificates": null, "server_groups": ["2b9dfdd8-0a5e-45ec-af07-1a0437a7f61e"]}} due to the value of "server_groups" not being a dict, openstack/resource.py crashes while trying to process this instance: File "/home/ubuntu/.local/lib/python3.8/site-packages/openstack/resource.py", line 82, in _convert_type return data_type(value) ValueError: dictionary update sequence element #0 has length 1; 2 is required is server_groups really supposed to be just a list of uuids? having it dealt with in a manner akin to security_groups seems to be an obvious choice … thank you very much & with kind regards, t.

2 2

"This system does not support SSSE3" while creating an instance in openstack
by Subhajit Chatterjee 13 Sep '20

13 Sep '20

While creating a VM instance in openstack (created using devstack), , I have got an issue “this system does not support SSSE3”. The cpu_mode in both /etc/nova/nova.conf and nova-cpu.conf was "none" so I tried changing it to use "host-model" or "host-passthrough". It didn't work on both the cases. I still get the same SSSE3 not supported error. I did grep in "/proc/cpuinfo", and found the ssse3 entry. Then I tried changing LIBVIRT_CPU_MODE to host-passthrough of "devstack/lib/nova" file and ran unstack.sh and stack.sh. The issue still persists. Please suggest how to resolve this issue? -- Name:- Subhajit Chatterjee DEPT.:- Computer Science and Engineering IIT Delhi Email:- babu89jucse(a)gmail.com Phone number:- +91 9958555224

1 0

[Keystone] socket.timeout: timed out
by Tony Liu 11 Sep '20

11 Sep '20

Any clues on this timeout exception? 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context [req-534d9855-8113-450d-8f9f-d93c0d961d24 113ee63a9ed0466794e24d069efc302c 4c142a681d884010ab36a7ac687d910c - default default] timed out: socket.timeout: timed out 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context Traceback (most recent call last): 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/server/flask/request_processing/middleware/auth_context.py", line 103, in _inner 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context return method(self, request) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/server/flask/request_processing/middleware/auth_context.py", line 353, in process_request 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context resp = super(AuthContextMiddleware, self).process_request(request) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystonemiddleware/auth_token/__init__.py", line 411, in process_request 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context allow_expired=allow_expired) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystonemiddleware/auth_token/__init__.py", line 445, in _do_fetch_token 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context data = self.fetch_token(token, **kwargs) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/server/flask/request_processing/middleware/auth_context.py", line 248, in fetch_token 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context token, access_rules_support=ACCESS_RULES_MIN_VERSION) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/common/manager.py", line 115, in wrapped 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context __ret_val = __f(*args, **kwargs) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/token/provider.py", line 145, in validate_token 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context token = self._validate_token(token_id) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "</usr/lib/python3.6/site-packages/decorator.py:decorator-gen-26>", line 2, in _validate_token 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/cache/region.py", line 1360, in get_or_create_for_user_func 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context key, user_func, timeout, should_cache_fn, (arg, kw) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/cache/region.py", line 962, in get_or_create 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context async_creator, 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/lock.py", line 187, in __enter__ 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context return self._enter() 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/lock.py", line 94, in _enter 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context generated = self._enter_create(value, createdtime) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/lock.py", line 180, in _enter_create 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context return self.creator() 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/cache/region.py", line 916, in gen_value 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context *creator_args[0], **creator_args[1] 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/token/provider.py", line 179, in _validate_token 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context token.mint(token_id, issued_at) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/models/token_model.py", line 579, in mint 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context self._validate_token_resources() 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/models/token_model.py", line 471, in _validate_token_resources 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context if self.project and not self.project_domain.get('enabled'): 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/models/token_model.py", line 176, in project_domain 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context self.project['domain_id'] 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/common/manager.py", line 115, in wrapped 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context __ret_val = __f(*args, **kwargs) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "</usr/lib/python3.6/site-packages/decorator.py:decorator-gen-27>", line 2, in get_domain 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/cache/region.py", line 1360, in get_or_create_for_user_func 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context key, user_func, timeout, should_cache_fn, (arg, kw) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/cache/region.py", line 962, in get_or_create 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context async_creator, 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/lock.py", line 187, in __enter__ 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context return self._enter() 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/lock.py", line 87, in _enter 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context value = value_fn() 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/cache/region.py", line 902, in get_value 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context value = self.backend.get(key) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/keystone/common/cache/_context_cache.py", line 74, in get 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context value = self.proxied.get(key) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/dogpile/cache/backends/memcached.py", line 168, in get 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context value = self.client.get(key) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/oslo_cache/backends/memcache_pool.py", line 32, in _run_method 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context return getattr(client, __name)(*args, **kwargs) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/memcache.py", line 1129, in get 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context return self._get('get', key) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/memcache.py", line 1074, in _get 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context server, key = self._get_server(key) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/memcache.py", line 446, in _get_server 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context if server.connect(): 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/memcache.py", line 1391, in connect 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context if self._get_socket(): 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/memcache.py", line 1423, in _get_socket 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context self.flush() 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/memcache.py", line 1498, in flush 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context self.expect(b'OK') 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/memcache.py", line 1473, in expect 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context line = self.readline(raise_exception) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context File "/usr/lib/python3.6/site-packages/memcache.py", line 1459, in readline 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context data = recv(4096) 2020-09-10 10:10:33.981 28 ERROR keystone.server.flask.request_processing.middleware.auth_context socket.timeout: timed out Thanks! Tony

2 2

[cinder] FEATURE FREEZE in effect
by Brian Rosmaita 11 Sep '20

11 Sep '20

The Victoria feature freeze is now in effect. Please do not approve patches proposing features for master until after the stable/victoria branch is cut the week of 21 September. Due to gate shenanigans over the past week, the following reviews have a feature freeze exception, and may be merged to master during the next week: Default type overrides - https://review.opendev.org/#/c/737707/ Adding support for Adaptive QoS in NetApp driver - https://review.opendev.org/#/c/741327/ The following have been approved and have been making their way slowly through the gate today, but technically they haven't been merged yet, so these also have a FFE: - https://review.opendev.org/#/c/747540/ - https://review.opendev.org/#/c/746941/ - https://review.opendev.org/#/c/746813/ (Hopefully by the time you read this, they've already been merged.) cheers, brian

1 0

[oslo][release][requirement] FFE request for Oslo lib
by Ghanshyam Mann 11 Sep '20

11 Sep '20

Hello Team, This is regarding FFE for Focal migration work. As planned, we have to move the Victoria testing to Focal and base job switch is planned to be switched by today[1]. There are few oslo lib need work (especially tox job-based testing not user-facing changes) to pass on Focal - https://review.opendev.org/#/q/topic:migrate-to-focal-oslo+(status:open+OR+… If we move the base tox jobs to Focal then these lib victoria gates (especially lower-constraint job) will be failing. We can either do these as FFE or backport (as this is lib own CI fixes only) later once the victoria branch is open. Opinion? [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-September/01706… -gmann

3 6

[InteropWG] Seeking ideas for InteropWG Branding for Open Infra
by prakash RAMCHANDRAN 11 Sep '20

11 Sep '20

Hi all, Please add your ideas for discussions for Forum https://etherpad.opendev.org/p/2020-Wallaby-interop-brainstorming Since any Interop case, it's best presented by PTLs their requirments, like to invite Ironic/metal3/MaaS and Container Projects(Zun,kuryr, magnum, kolla...) to help us define the new Branding strategy for Open Infra projects like (Airship, Starlingx, Kata, Zuul, Openlabs ...) Note we see one opportunity coming out of BareMetal as a Service for Ironic routed through Metal3 which is now a CNCF Sandbox project. The other we see OpenInfa-ready-k8s-container and/or based on Zun- CRI (Docker, Containerd, Kata...), CNI (kuryr) & CSI (?) & COE as Magnum Please add your ideas and time you may need for us to go over these emerging ideas for re-imagining clusters in Open Infra with Baremetal as well VM Nodes over Private & Public clouds. ThanksFor InteropWGPrakash

1 0

[TC][PTG] Virtual PTG Planning
by Kendall Nelson 11 Sep '20

11 Sep '20

Hello! So as you might have seen, the deadline to sign up for PTG time by the end of next week. To coordinate our time to meet as the TC, please fill out the poll[1] that Mohammed kindly put together for us. *We need responses by EOD Thursday September 10th* so that we can book the time in the ethercalc and fill out the survey to reserve our space before the deadline. Also, I created this planning etherpad [2] to start collecting ideas for discussion topics! Can't wait to see you all there! -Kendall & Mohammed [1] https://doodle.com/poll/hkbg44da2udxging [2] https://etherpad.opendev.org/p/tc-wallaby-ptg

1 1

[neutron] Flow drop on agent restart with openvswitch firewall driver
by Alexis Deberg 11 Sep '20

11 Sep '20

Hi All, I'm looking for ideas as we need to upgrade our Neutron deployment and it looks like it would impact workloads a bit much for now to do so and i'm no master of the neutron code... We're running Neutron 14.0.2 with ml2 plugin and firewall_driver set as openvswitch. drop_flows_on_start is default False. Reading at some old bug reports my understanding was that a restart of the neutron-openvswitch-agent should not impact existing flows and be seamless, but this is not what I'm experiencing as I see some temporary drop(s) around when ovs-fctl del-flows/add-flows is called on br-int (either east-west traffic or north-south). I tried switching to iptables_hybrid driver instead and I don't see the issue in that case. e.g when a wget download is happening on an instance while the agent is restarting, I see the following: 2020-09-08 14:26:09 (12.2 MB/s) - Read error at byte 146971864/7416743936 (Success). Retrying I'm a bit lot so i'm wondering if that's expected/known behavior, if a workaround is possible.... Let me know if a bug report might be a better place to dig deeper or not or if you want additional information... or if I missed a closed bug. Thanks !

3 4

[manila][release] Some feature patches will merge today
by Goutham Pacha Ravi 11 Sep '20

11 Sep '20

Hello Stackers, As is unusual, we have found ourselves with a few unmerged feature patches at the wrong side of the feature freeze: [Container driver] Adds share and share server migration: https://review.opendev.org/740831/ [NetApp] Enables configuring NFS transfer limits: https://review.opendev.org/746568 [NetApp] Add support for share server migration: https://review.opendev.org/747048/ [NetApp] Adding support for Adaptive QoS in NetApp driver with dhss false: https://review.opendev.org/740532/ These patches have been getting review attention late in the cycle, and were caught up in CI failures and code collisions. The code changes above are isolated within driver modules in the code that are explicitly configured/optionally enabled by deployers. These changes do not: - introduce any new library dependencies to manila, or - modify the API, DB, RPC, driver interface layers - introduce new requirements into the client library (python-manilaclient) They do introduce translatable exception strings - however, manila has not received translation updates in the past. We're looking to get these merged today. Hope that's okay - do let me know of any gotchas. -- Goutham Pacha Ravi

1 0

"openstack server list" takes 30s
by Tony Liu 11 Sep '20

11 Sep '20

Hi, I built a Ussuri cluster with 3 controllers and 5 compute nodes. OpenStack CLI ran pretty fast at the beginning, but gets slower over time along with increased workloads. Right now, it takes about 30s to list 10 VMs. The CPU, memory and disk usage are on those 3 controllers are all in the range. I understand there are many API calls happening behind CLI. I'd like to figure out how this 30s is consumed, which call is the killer. Any guidance or hint would be helpful. Thanks! Tony

4 3

[release] Release countdown for week R-4 Sept 14 - 18
by Sean McGinnis 11 Sep '20

11 Sep '20

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the victoria deliverables can be proposed, well ahead of the final victoria release date. General Information ------------------- We are still finishing up processing a few release requests, but the victoria release requirements are now frozen. If new library releases are needed to fix release-critical bugs in victoria, you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in victoria that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By September 24 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/victoria branches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for victoria changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed victoria cycle-highlights yet, you are already late to the party. Please see http://lists.openstack.org/pipermail/openstack-discuss/2020-September/01694… for details. Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 24 (R-3) Final Victoria release: October 14 Open Infra Summit: October 19-23 Wallaby PTG: October 26-30

1 0

[Neutron] number of subnets in a network
by Tony Liu 11 Sep '20

11 Sep '20

Hi, Is there any hard limit to the number of subnets in a network? In theory, would it be ok to put, like 5000 subnets, in a network? Thanks! Tony

4 3

Instance cannot ping external (Lan/Internet) Openstack AllinOne Packstack Virtualbox
by dangerzone ar 11 Sep '20

11 Sep '20

Hi Team, I have been struggling to get the solution. I'm testing openstack and deploying it over virtualbox. I have shared my issue in SO with help from berndbausch <https://stackoverflow.com/users/3548109/berndbausch> and try to share it here also to get more help....as I have create and redeploy few times with different openstack release.. deployment methods..parameters....still the same problem. I don't think my deployment is different with others as i follow the guideline and common practise... just stuck on this problem...please do help and assist me further. Thank you to all.... Below is my environment setup. Windos10_Virtualbox----Centos7------Openstack----VM instance [192.168.0.0/24] - external network/public-ip Pc host - 192.168.0.160 Home Lan GW - 192.168.0.1 Centos7 - 192.168.0.12 (VM virtualbox) Openstack Router GW - 192.168.0.221 Virtualbox VM setting bridge (enp0s3) and promiscuous mode all selinux permissive add rules icmp and ssh. create public-ip 192.168.0.0/24 (pool 220-230) create router create private subnet 10.0.0.0/24 attach router to private subnet create router GW(public-ip) >From LAN I can ping and ssh vm instance but from vm instance i cannot ping to home Lan GW, pc host. VM instance can ping up to centos7 virtualbox and openstack Router GW. Instance created with centos and cirros using direct public-ip and also floating ip. Some instance created with direct public ip and some with private subnet and using floating ip. I have tested with queens, stein, train. With allinone and also using answerfile and all end up I cannot ping external. I follows guideline below:- *hxxps://www.linuxtechi.com/single-node-openstack-liberty-installation-centos-7/ <http://www.linuxtechi.com/single-node-openstack-liberty-installation-centos…>* *hxxps://www.rdoproject.org/install/packstack/ <http://www.rdoproject.org/install/packstack/>* This some of answer file parameters that i edited CONFIG_NEUTRON_L3_EXT_BRIDGE=br-ex CONFIG_NEUTRON_ML2_TYPE_DRIVERS=flat,vxlan CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=extnet:br-ex CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-ex:enp0s3 CONFIG_NEUTRON_OVS_BRIDGES_COMPUTE=br-ex CONFIG_PROVISION_DEMO=n ip netns list qrouter-f6967bba-986e-4bb3-838e-d035a684e2c4 (id: 2) qdhcp-dbd713cd-1af4-4e2c-9c57-d8a675a10608 (id: 1) qdhcp-fa6fb1d6-b65e-4eb2-a4a4-5552fde8bb08 (id: 0) [root@myospackanswer ~(keystone_admin)]# ip netns exec qrouter-f6967bba-986e-4bb3-838e-d035a684e2c4 arp -an ? (192.168.0.211) at <incomplete> on qg-0ba7da31-7f ? (192.168.0.227) at fa:16:3e:ed:19:81 [ether] on qg-0ba7da31-7f (Instance IP) ? (192.168.0.160) at d4:d2:52:73:de:80 [ether] on qg-0ba7da31-7f (host pc IP) ? (192.168.0.1) at 80:26:89:b2:98:50 [ether] on qg-0ba7da31-7f (home router GW) ? (10.0.0.4) at fa:16:3e:01:63:42 [ether] on qr-7e6f9436-40 (private subnet) ip r default via 192.168.0.1 dev br-ex169.254.0.0/16 dev enp0s3 scope link metric 1002169.254.0.0/16 dev br-ex scope link metric 1006192.168.0.0/24 dev br-ex proto kernel scope link src 192.168.0.121 qrouter-f6967bba-986e-4bb3-838e-d035a684e2c4 (id: 2) qdhcp-dbd713cd-1af4-4e2c-9c57-d8a675a10608 (id: 1) qdhcp-fa6fb1d6-b65e-4eb2-a4a4-5552fde8bb08 (id: 0) sudo ip netns exec qrouter-f6967bba-986e-4bb3-838e-d035a684e2c4 ip route default via 192.168.0.1 dev qg-0ba7da31-7f10.0.0.0/24 dev qr-7e6f9436-40 proto kernel scope link src 10.0.0.1192.168.0.0/24 dev qg-0ba7da31-7f proto kernel scope link src 192.168.0.221 ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master ovs-system state UP group default qlen 1000 link/ether 08:00:27:98:9b:a3 brd ff:ff:ff:ff:ff:ff inet6 fe80::a00:27ff:fe98:9ba3/64 scope link valid_lft forever preferred_lft forever 5: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 8a:17:8b:e5:dc:c2 brd ff:ff:ff:ff:ff:ff 6: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 08:00:27:98:9b:a3 brd ff:ff:ff:ff:ff:ff inet 192.168.0.121/24 brd 192.168.0.255 scope global br-ex valid_lft forever preferred_lft forever inet6 2001:e68:5435:d135:a00:27ff:fe98:9ba3/64 scope global mngtmpaddr dynamic valid_lft 86399sec preferred_lft 86399sec inet6 fe80::a00:27ff:fe98:9ba3/64 scope link valid_lft forever preferred_lft forever 7: br-int: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000 link/ether 32:ff:0f:26:18:43 brd ff:ff:ff:ff:ff:ff 8: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether d6:52:08:a9:68:4f brd ff:ff:ff:ff:ff:ff 29: qbr1f637f14-9c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000 link/ether 42:95:e8:c0:a3:07 brd ff:ff:ff:ff:ff:ff 30: qvo1f637f14-9c@qvb1f637f14-9c: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1450 qdisc noqueue master ovs-system state UP group default qlen 1000 link/ether 6e:2e:07:8d:79:86 brd ff:ff:ff:ff:ff:ff inet6 fe80::6c2e:7ff:fe8d:7986/64 scope link valid_lft forever preferred_lft forever 31: qvb1f637f14-9c@qvo1f637f14-9c: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1450 qdisc noqueue master qbr1f637f14-9c state UP group default qlen 1000 link/ether 42:95:e8:c0:a3:07 brd ff:ff:ff:ff:ff:ff inet6 fe80::4095:e8ff:fec0:a307/64 scope link valid_lft forever preferred_lft forever 32: tap1f637f14-9c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast master qbr1f637f14-9c state UNKNOWN group default qlen 1000 link/ether fe:16:3e:05:2d:50 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe05:2d50/64 scope link valid_lft forever preferred_lft forever

1 0

Ussuri - make added mptsas driver to introspection initramfs load automatically
by Oliver Weinmann 11 Sep '20

11 Sep '20

Hi, I already asked this question on serverfault. But I guess here is a better place. I have a very ancient hardware with a MPTSAS controller. I use this for TripleO deployment testing. With the release of Ussuri which is running CentOS8, I can no longer provision my overcloud nodes as the MPTSAS driver has been removed in CentOS8: https://www.reddit.com/r/CentOS/comments/d93unk/centos8_and_removal_mpt2sas… I managed to include the driver provided from ELrepo in the introspection image but It is not loaded automatically: All commands are run as user "stack". Extract the introspection image: cd ~ mkdir imagesnew cd imagesnew tar xvf ../ironic-python-agent.tar mkdir ~/ipa-tmp cd ~/ipa-tmp /usr/lib/dracut/skipcpio ~/imagesnew/ironic-python-agent.initramfs | zcat | cpio -ivd | pax -r Extract the contents of the mptsas driver rpm: rpm2cpio ~/kmod-mptsas-3.04.20-3.el8_2.elrepo.x86_64.rpm | pax -r Put the kernel module in the right places. To figure out where the module has to reside I installed the rpm on a already deployed node and used find to locate it. xz -c ./usr/lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko > ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/kernel/drivers/message/fusion/mptsas.ko.xz mkdir ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas sudo ln -sf /lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas.ko sudo chown root . -R find . 2>/dev/null | sudo cpio --quiet -c -o | gzip -8 > ~/images/ironic-python-agent.initramfs Upload the new image cd ~/images openstack overcloud image upload --update-existing --image-path /home/stack/images/ Now when I start the introspection and ssh into the host I see no disks: [root@localhost ~]# fdisk -l [root@localhost ~]# lsmod | grep mptsas Once i manually load the driver, I can see the disks: [root@localhost ~]# modprobe mptsas [root@localhost ~]# lsmod | grep mptsas mptsas 69632 0 mptscsih 45056 1 mptsas mptbase 98304 2 mptsas,mptscsih scsi_transport_sas 45056 1 mptsas [root@localhost ~]# fdisk -l Disk /dev/sda: 67.1 GiB, 71999422464 bytes, 140623872 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes But how can I make it so that it will automatically load on boot? Best Regards, Oliver

1 0

Re: [neutron][networking-midonet] Maintainers needed
by Sebastian Saemann 10 Sep '20

10 Sep '20

Hi Slawek, we at NETWAYS are running most of our neutron networking on top of midonet and wouldn't be too happy if it gets deprecated and removed. So we would like to take over the maintainer role for this part. Please let me know how to proceed and how we can be onboarded easily. Best regards, Sebastian -- Sebastian Saemann Head of Managed Services NETWAYS Managed Services GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB25207 https://netways.de | sebastian.saemann(a)netways.de ** NETWAYS Web Services - https://nws.netways.de **

6 17