- openstack-discuss - lists.openstack.org

Openstack Cinder support matrix
by DANILO PAOLO DELL'ORTO 08 Mar '21

08 Mar '21

Hi, The Openstack Cinder driver support matrix (see link-1 below) lists the supported features for each storage and in the IBM Virtualize Family (SVC) section lacks support for 3 important features: Thin provisioning, Volume migration (storage assisted) and Active -Active high availability support. In the same site in section IBM Spectrum Virtualize volume driver (link-2 below), the functions described above seem to be supported and explained in more detail. Which of the two parts is true? Maybe the support matrix is out of date? best regards link-1 https://docs.openstack.org/cinder/latest/reference/support-matrix.html link-2 https://docs.openstack.org/cinder/latest/configuration/block-storage/driver…

2 1

[election][Octavia] PTL candidacy for Xena
by Gregory Thiemonge 08 Mar '21

08 Mar '21

Hi everyone, I would like to propose my candidacy for Octavia PTL during the Xena cycle. I have been an Octavia contributor for 2 years, and a core reviewer for 2 releases. Since then, I have been working in many areas in Octavia: adding support for new protocols (SCTP), fixing CI jobs, improving the octavia-dashboard. My focus will be to continue the work that the team has accomplished these last years, particularly adding many new features in Octavia (active/active load balancers, leveraging features provided by HAProxy 2.0) and improving our CI coverage (restoring CentOS jobs). Thanks for your consideration, Gregory

1 0

[neutron] Bug deputy report - week of March 1st
by Slawek Kaplonski 08 Mar '21

08 Mar '21

Hi, I was Neutron's bug deputy last week. Below is my summary. **critical** https://bugs.launchpad.net/neutron/+bug/1917487 - [FT] "IpNetnsCommand.add" command fails frequently - Assigned to Rodolfo https://bugs.launchpad.net/nova/+bug/1917610 - Migration and resize tests from tempest.scenario.test_minbw_allocation_placement.MinBwAllocationPlacementTest failing in neutron-tempest-dvr-ha-multinode-full - fix done in tempest https://review.opendev.org/c/openstack/tempest/+/778451 https://bugs.launchpad.net/neutron/+bug/1917793 - [HA] keepalived_state_change does not finish "handle_initial_state"execution - gate failure, assigned to Rodolfo **high** https://bugs.launchpad.net/neutron/+bug/1917409 - neutron-l3-agents won't become active - needs assignment https://bugs.launchpad.net/neutron/+bug/1917508 - Router create fails when router with same name already exists - related to ovn l3 plugin, needs assignment https://bugs.launchpad.net/neutron/+bug/1917370 - [functional] ovn maintenance worker isn't mocked in functional tests - **High** as it's causing gate failures or timeouts, assigned, patch: https://review.opendev.org/c/openstack/neutron/+/778080 - already merged https://bugs.launchpad.net/neutron/+bug/1917393 - [L3][Port forwarding] admin state DOWN/UP router will lose all pf-floating-ips and nat rules - assigned, In progress, Patch: https://review.opendev.org/c/openstack/neutron/+/778126 https://bugs.launchpad.net/neutron/+bug/1918108 - [OVN] IGMP snooping traps IGMP messages - assigned to Lucas already, **medium** https://bugs.launchpad.net/neutron/+bug/1917448 - GRE tunnels over IPv6 have wrong packet_type set in OVS - set as **Medium**, assigned, patch: https://review.opendev.org/c/openstack/neutron/+/778178, already merged **Wishlist** https://bugs.launchpad.net/neutron/+bug/1917437 - Enable querier for multicast (IGMP) in OVN, Assigned, In progress https://bugs.launchpad.net/neutron/+bug/1917866 - No need to fetch whole network object on port create - assigned to Oleg, patch proposed already https://review.opendev.org/c/openstack/neutron/+/778881 https://bugs.launchpad.net/neutron/+bug/1904559 - Designate driver: allow_reverse_dns_lookup doesn't works if dns_domain zone wasn't created - Switched to be RFE - please, especially drivers team members, check and triage it so we can discuss that on the drivers meeting, **undecided** https://bugs.launchpad.net/networking-ovn/+bug/1914857 - AttributeError: 'NoneType' object has no attribute 'db_find_rows' - Rodolfo and Lucas are triaging it, **Old bugs which needs attention** https://bugs.launchpad.net/neutron/+bug/1752903 - Floating IPs should not allocate IPv6 addresses - L3 subteam should take a look at it. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[election][neutron] PTL Candidacy for Xena
by Slawek Kaplonski 08 Mar '21

08 Mar '21

Hi, I want to propose my candidacy for Neutron PTL in the Xena cycle. Wallaby was my third cycle serving as Neutron PTL. I think I helped to keep the project in a healthy state and I would like to continue serving as the PTL and keep Neutron running well in the Xena cycle. In Wallaby we accomplished many important goals like e.g.: * finished migration to the engine facade, * improve our CI jobs and its overall stability, * and close of many feature parity gaps between OVN and OVS backends. But we also didn't finish some of the goals which were set for that cycle, like e.g. switching OVN to be the default Neutron backend in Devstack. If I will be elected, I would like to set it as my main goal for Xena cycle. We did a lot of work on adoption of the OVN backend in Neutron already and I think that we are now ready to move on and switch it to be the default backend in the Devstack. I want to focus on couple of things in the Xena cycle: * reduce our bug backlog as it is huge now, * maintenance and continue improvements of our CI, as this is "never ending story", * keep Neutron running in a smooth way. As I mentioned above, if I will be elected, Xena will be my 4th cycle as Neutron PTL and I would like to find some potential successors for the next cycles to help them onboard and understand what are the duties and responsibilities of the PTL. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cinder] Inflated version dependency in os-brick
by Thomas Goirand 08 Mar '21

08 Mar '21

Hi, As I've started packaging Wallaby for Debian, I noticed that os-brick has very inflated version dependencies: $ diff -u ../requirements.txt requirements.txt --- ../requirements.txt 2021-03-08 10:54:44.896134101 +0100 +++ requirements.txt 2021-03-08 10:54:48.848127942 +0100 @@ -2,17 +2,16 @@ # of appearance. Changing the order has an impact on the overall integration # process, which may cause wedges in the gate later. -pbr!=2.1.0,>=5.4.1 # Apache-2.0 -eventlet>=0.25.1 # MIT -oslo.concurrency>=3.26.0 # Apache-2.0 -oslo.context>=2.23.0 # Apache-2.0 -oslo.log>=3.44.0 # Apache-2.0 -oslo.i18n>=3.24.0 # Apache-2.0 -oslo.privsep>=1.32.0 # Apache-2.0 -oslo.serialization>=2.29.0 # Apache-2.0 -oslo.service!=1.28.1,>=1.24.0 # Apache-2.0 -oslo.utils>=3.34.0 # Apache-2.0 -requests>=2.14.2 # Apache-2.0 -six>=1.10.0 # MIT -tenacity>=6.0.0 # Apache-2.0 -os-win>=3.0.0 # Apache-2.0 +pbr>=5.5.1 # Apache-2.0 +eventlet>=0.30.1 # MIT +oslo.concurrency>=4.4.0 # Apache-2.0 +oslo.context>=3.1.1 # Apache-2.0 +oslo.log>=4.4.0 # Apache-2.0 +oslo.i18n>=5.0.1 # Apache-2.0 +oslo.privsep>=2.4.0 # Apache-2.0 +oslo.serialization>=4.1.0 # Apache-2.0 +oslo.service>=2.5.0 # Apache-2.0 +oslo.utils>=4.8.0 # Apache-2.0 +requests>=2.25.1 # Apache-2.0 +tenacity>=6.3.1 # Apache-2.0 +os-win>=5.4.0 # Apache-2.0 Some of the above is clearly abusing. For example, I don't think Cinder really needs version 5.5.1 of PBR, and 5.5.0 should really be enough. I've traced it back to: https://review.opendev.org/c/openstack/os-brick/+/778807 If this is a consequence of the project stopping to test lower bounds of requirements, then this has gone really insane, and the bad practice must stop immediately to restore sanity, and we must revert. We're back 5 years ago where each projects was uselessly requiring the latest version of everything for no reason... From a downstream package maintainer perspective, this is a disaster move. Haven't we learned from our mistakes? Cheers, Thomas Goirand (zigo)

1 0

[infra][qe][nova] Would it be possible to host a custom cirros image somewhere for the nova-next job?
by Lee Yarwood 08 Mar '21

08 Mar '21

Hello all, I recently landed a fix in Cirros [1] to allow it to be used by the nova-next job when it is configured to use the q35 machine type [2], something that we would like to make the default sometime in the future. With no release of Cirros on the horizon I was wondering if I could instead host a build of the image somewhere for use solely by the nova-next job? If this isn't possible I'll go back to the Cirros folks upstream and ask for a release but given my change is the only one to land there in almost a year I wanted to ask about this approach first. Many thanks in advance, Lee [1] https://github.com/cirros-dev/cirros/pull/65 [2] https://review.opendev.org/c/openstack/nova/+/708701

4 9

Post to Openstack mail list
by DANILO PAOLO DELL'ORTO 08 Mar '21

08 Mar '21

Hi, I would like to post questions on the openstack mail lists, can you authorize me? best regards

1 0

[election][manila] PTL Candidacy for Xena
by Goutham Pacha Ravi 07 Mar '21

07 Mar '21

Greetings Zorillas & other Stackers, This is my candidacy to be the PTL for the OpenStack Manila team through the Xena cycle. I've had the great privilege of leading this unique team for the past three releases. During this time, we've had an enviable momentum and some fantastic achievements while building impactful software. I have enjoyed being a catalyst and an advocate for this motivated team, and I wish to do this a bit longer. In Wallaby, we harnessed our diverse strengths to mentor five new contributors through our student project internships, two of who were sponsored through Outreachy funding. They have all expressed their desire to become long term contributors. I am very proud of the manila team for their sincerity and enthusiasm in aiding new Stackers. I seek to further this outreach through the Xena release cycle. Testing and project quality will remain a top personal priority. The team was able to get new interop guidelines published last cycle, and we will focus on adding more test coverage under these guidelines, alongside addressing test gaps and innovating on more test scenarios. We have continued to implement the pro-active backport policy to get bug fixes back to stable branches and request timely releases of these stable branches. In the Xena cycle, I intend to codify this policy based on our learning and spread the release responsibility and know-how around the team. We split project maintenance into sub-teams during the Wallaby cycle, and recruited sub-team core reviewers. An increase in focus and velocity ensued across project code repositories. I intend to propose more additions to these sub-teams in the Xena cycle and encourage more contributors to take on project maintenance responsibilities. So, if you will have me, I wish to serve you through Xena and get things done. Thank you for your support, Goutham Pacha Ravi <gouthampravi(a)gmail.com> IRC: gouthamr

1 0

[horizon][i18n][infra] Renaming Chinese locales in Django from zh-cn/zh-tw to zh-hans/zh-hant
by Akihiro Motoki 07 Mar '21

07 Mar '21

Hi, The horizon team is planning to switch Chinese language codes in Django codes from zh-cn/zh-tw to zh-hans/zh-hant. Django, a framework used in horizon, recommends to use them since more than 5 years ago [1][2]. This change touches Chinese locales in the dashbaord codes of horizon and its plugins only. It does not change Chinese locales in other translations like documentations and non-Django python codes. This is to minimize the impact to other translations and the translation platform. ### What are/are not changed in repositories * horizon and horizon plugins * locales in the dashboard codes are renamed from zh-cn/zh-tw to zh-hans/zh-hant * locales in doc/ and releasenotes/ are not changed * other repositories * no locale change happens NOTE: * This leads to a situation that we have two different locales in horizon and plugin repositories (zh-hans/hant in the code folders and zh-cn/tw in doc and releasenotes folders), but it affects only developers and does not affect horizon consumers (operators/users) and translators. * In addition, documentations are translated in OpenStack-wide (not only in horizon and plugins). By keeping locales in docs, locales in documentation translations will be consistent. ### Impact on Zanata In Zanata (the translation platform), zh-cn/zh-tw continue to be used, so no change is visible to translators. The infra job proposes zh-cn/zh-tw GUI translatoins as zh-hans/zh-hant translations to horizon and plugin repositories. NOTE: The alternative is to create the corresponding language teams (zh-hans/zh-hant) in Zanata, but it affects Chinese translators a lot. They need to join two language teams to translate horizon (zh-hans/zh-hant) and docs (zh-cn/zh-tw). It makes translator workflow complicated. The proposed way has no impact on translators and they can continue the current translation process and translate both horizon and docs under a single language code. ### Changes in the infra scripts Converting Chinese locales of dashboard translations from zh-cn/zh-tw to zh-hans/zh-hant is handled by the periodic translation job. propose_translation_update job is responsible for this. [propose_translation_update.sh] * Move zh-cn/zh-tw translations related to Django codes in horizon and its plugins from zanata to zh-hans/hant directory. * This should happen in the master branch (+ future stable branhces such as stable/wallaby). ### Additional Remarks I18n SIG respects all language team coordinators & members, and is looking forward to seeing discussions and/or active contributions from the language teams. Currently all language codes follow the ISO 639-1 standard (language codes with relevant country codes), but the change introduces new language code forms like zh-hans/zh-hant. This follows IETF BCP 47 which recommends a combination of language codes and ISO 15924 script code (four letters). We now have two different language codes in OpenStack world. This is just to minimize the impact on the existing translations. It is not ideal. We are open for further discussion on language codes and translation support. ### References [1] https://code.djangoproject.com/ticket/18419 [2] https://www.djbook.ru/rel1.7/releases/1.7.html#language-codes-zh-cn-zh-tw-a… Thanks, Akihiro Motoki (irc: amotoki)

1 1

[all][tc][goals] Migrate RBAC Policy Format from JSON to YAML: Week R-6 Update
by Ghanshyam Mann 07 Mar '21

07 Mar '21

Hello Everyone, Please find the week's R-6 updates on 'Migrate RBAC Policy Format from JSON to YAML' wallaby community-wide goals. Gerrit Topic: https://review.opendev.org/q/topic:%22policy-json-to-yaml%22+(status:open%2… Progress Summary: =============== Tracking: https://etherpad.opendev.org/p/migrate-policy-format-from-json-to-yaml * Projects completed: 21 * Projects required to merge the patches: 8 * Projects required to push the patches: 2 (horizon and Openstackansible) * Projects do not need any work: 16 Patches ready to merge: ================== * Octavia: https://review.opendev.org/c/openstack/octavia/+/764578 * Magnum: https://review.opendev.org/c/openstack/magnum/+/767242 * Murano: https://review.opendev.org/c/openstack/murano/+/768520 * Panko: https://review.opendev.org/c/openstack/panko/+/768498 * Solum: https://review.opendev.org/c/openstack/solum/+/768381 * Zaqar: https://review.opendev.org/c/openstack/zaqar/+/768488 Updates: ======= * Fixed the lower constraints failure for all the current open patches. * Few project patches are failing on config object initialization, I am debugging those and will fix them soon. * It is important to merge all the service side patches so that JSON format deprecation happens in the Wallaby release. -gmann

2 2

[neutron-dynamic-routing] Support for multiple BGP speaker
by Manu B 07 Mar '21

07 Mar '21

Hi, As understood from the code, currently the neutron dynamic routing supports only one BGP speaker per host *# os-ken can only support One *speaker if* self.cache.get_hosted_bgp_speakers_count() == 1: raise bgp_driver_exc.BgpSpeakerMaxScheduled(count=1) * Could you please let me know if this is due to some limitation of the os-ken driver? Or are there any other reasons for this limitation? Thanks, Manu

1 0

[Neutron][Nova][Ironic][Cinder][Keystone][Glance][Swift] OVN as the default network backend for DevStack
by Lucas Alvares Gomes 06 Mar '21

06 Mar '21

Hi all, As part of the Victoria PTG [0] the Neutron community agreed upon switching the default backend in Devstack to OVN. A lot of work has been done since, from porting the OVN devstack module to the DevStack tree, refactoring the DevStack module to install OVN from distro packages, implementing features to close the parity gap with ML2/OVS, fixing issues with tests and distros, etc... We are now very close to being able to make the switch and we've thought about sending this email to the broader community to raise awareness about this change as well as bring more attention to the patches that are current on review. Note that moving DevStack to ML2/OVN does not mean that ML2/OVS is discontinued and/or not supported anymore. The ML2/OVS driver is still going to be developed and maintained by the upstream Neutron community. Below is a e per project explanation with relevant links and issues of where we stand with this work right now: * Keystone: Everything should be good for Keystone, the gate is happy with the changes. Here is the test patch: https://review.opendev.org/c/openstack/keystone/+/777963 * Glance: Everything should be good for Glace, the gate is happy with the changes. Here is the test patch: https://review.opendev.org/c/openstack/glance/+/748390 * Swift: Everything should be good for Swift, the gate is happy with the changes. Here is the test patch: https://review.opendev.org/c/openstack/swift/+/748403 * Ironic: Since chainloading iPXE by the OVN built-in DHCP server is work in progress, we've changed most of the Ironic jobs to explicitly enable ML2/OVS and everything is merged, so we should be good for Ironic too. Here is the test patch: https://review.opendev.org/c/openstack/ironic/+/748405 * Cinder: Cinder is almost complete. There's one test failure in the "tempest-slow-py3" job run on the "test_port_security_macspoofing_port" test. This failure is due to a bug in core OVN [1]. This bug has already been fixed upstream [2] and the fix has been backported down to the branch-20.03 [3] of the OVN project. However, since we install OVN from packages we are currently waiting for this fix to be included in the packages for Ubuntu Focal (it's based on OVN 20.03). I already contacted the package maintainer which has been very supportive of this work and will work on the package update, but he maintain a handful of backports in that package which is not yet included in OVN 20.03 upstream and he's now working with the core OVN community [4] to include it first in the branch and then create a new package for it. Hopefully this will happen soon. But for now we have a few options moving on with this issue: 1- Wait for the new package version 2- Mark the test as unstable until we get the new package version 3- Compile OVN from source instead of installing it from packages (OVN_BUILD_FROM_SOURCE=True in local.conf) What do you think about it ? Here is the test patch for Cinder: https://review.opendev.org/c/openstack/cinder/+/748227 * Nova: There are a few patches waiting for review for Nova, which are: 1- Adapting the live migration scripts to work with ML2/OVN: Basically the scripts were trying to stop the Neutron agent (q-agt) process which is not part of an ML2/OVN deployment. The patch changes the code to check if that system unit exists before trying to stop it. Patch: https://review.opendev.org/c/openstack/nova/+/776419 2- Explicitly set grenade job to ML2/OVS: This is a temporary change which can be removed one release cycle after we switch DevStack to ML2/OVN. Grenade will test updating from the release version to the master branch but, since the default of the released version is not ML2/OVN, upgrading from ML2/OVS to ML2/OVN as part of the grenade job is not supported. Patch: https://review.opendev.org/c/openstack/nova/+/776934 3- Explicitly set nova-next job to ML2/OVS: This job uses the QoS minimum bandwidth feature which is not yet supported by ML2/OVN [5][6] therefore we are temporarily enabling ML2/OVS for this job until that feature lands in core OVN. Patch: https://review.opendev.org/c/openstack/nova/+/776944 I also spoke briefly with Sean Mooney (irc: sean-k-mooney) about these changes and he suggested keeping all the Nova jobs on ML2/OVS for now because he feels like a change in the default network driver a few weeks prior to the upstream code freeze can be concerning. We do not know yet precisely when we are changing the default due to the current patches we need to get merged but, if this is a shared feeling among the Nova community I can work on enabling ML2/OVS on all jobs in Nova until we get a new release in OpenStack. Here's the test patch for Nova: https://review.opendev.org/c/openstack/nova/+/776945 * DevStack: And this is the final patch that will make this all happen: https://review.opendev.org/c/openstack/devstack/+/735097 It changes the default in DevStack from ML2/OVS to ML2/OVN. It's been a long and bumpy road to get to this point and I would like to say thanks to everyone involved so far and everyone that read the whole email, please let me know your thoughts. [0] https://etherpad.opendev.org/p/neutron-victoria-ptg [1] https://bugs.launchpad.net/tempest/+bug/1728886 [2] https://patchwork.ozlabs.org/project/openvswitch/patch/20200319122641.47377… [3] https://github.com/ovn-org/ovn/commit/0c26bc03064f2c21d208f0f860b48d8ab3938… [4] https://mail.openvswitch.org/pipermail/ovs-discuss/2021-February/050961.html [5] https://github.com/openstack/nova/blob/ded25f33c734ebff963f06984707a99fe76a… [6] https://docs.openstack.org/neutron/latest/ovn/gaps.html Cheers, Lucas

8 16

[manila] Wallaby Collab Review - CephFS drivers updates (Mar 8th)
by Victoria Martínez de la Cruz 05 Mar '21

05 Mar '21

Hi everyone, Next Monday (March 8th) we will hold a Manila collaborative review session in which we'll go through the code and review the latest changes introduced in the CephFS drivers [0][1] This meeting is scheduled to last one hour, starting at 5.00pm UTC. It might extend a bit, but the most important should be covered within the hour. Meeting notes and relevant links are available in [2] Your feedback will be truly appreciated. Cheers, V [0] https://review.opendev.org/q/topic:%22bp%252Fupdate-cephfs-drivers%22+(stat… [1] https://review.opendev.org/q/topic:%22bp%252Fcreate-share-from-snapshot-cep… [2] https://etherpad.opendev.org/p/update-cephfs-drivers-collab-review

1 1

Re: [openstack-community] Keystone deprecated policies problem
by Amy 05 Mar '21

05 Mar '21

Adding the OpenStack discuss list. Thanks, Amy (spotz) > On Mar 5, 2021, at 3:19 PM, meberhardt(a)unl.edu.ar wrote: > > Hi, > > my installation complains about deprecated policies and throw errors when I try to run specific commands in cli as admin user(list projects or list users, for example). > > "You are not authorized to perform the requested action: identity:list_users." > > I tried to fix this by upgrading the keystone policies using oslopolicy-policy-generator and oslopolicy-policy-upgrade. Just found two places where I have those keystone policy files in my sistem: /etc/openstack_dashboard/keystone_policy.json and cd /lib/python3.6/site-packages/openstack_auth/tests/conf/keystone_policy.json > > I regenerated & upgraded it but Keystone still complains about the old polices. Where are it placed? How I shoud fix it? > > OS: CentOS 8 > Openstack version: Ussuri > Manual installation > > Thanks, > > Matias > > /* --------------------------------------------------------------- */ > /* Matías A. Eberhardt */ > /* */ > /* Centro de Telemática */ > /* Secretaría General */ > /* UNIVERSIDAD NACIONAL DEL LITORAL */ > /* Pje. Martínez 2652 - S3002AAB Santa Fe - Argentina */ > /* tel +54(342)455-4245 - FAX +54(342)457-1240 */ > /* --------------------------------------------------------------- */ > > > _______________________________________________ > Community mailing list > Community(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/community

1 0

[cinder] final patches for wallaby os-brick release need reviews
by Brian Rosmaita 05 Mar '21

05 Mar '21

Hello members of the cinder community: Please direct your attention to the following patches at your earliest convenience (i.e., right now): https://review.opendev.org/c/openstack/os-brick/+/777086 "NVMeOF connector driver connection information compatibility fix" - this fixes the regression in the nvmeof connector - patch has passed CI: Zuul, Mellanox SPDK (to detect the regression), and Kioxia (which uses the mdraid feature) - looks pretty much ready to go https://review.opendev.org/c/openstack/os-brick/+/778810 "Add release note for nvmeof connector" - the title says it all https://review.opendev.org/c/openstack/os-brick/+/778807 "Update requirements for wallaby release" - raises the minimum versions in the various requirements files to reflect what we're actually testing with right now - nothing major because of the adjustments made back in January to deal with the upgraded pip dependency resolver Happy reviewing! brian

2 2

[TripleO] Wallaby cycle highlights
by Marios Andreou 05 Mar '21

05 Mar '21

Hello all o/ Before you have a heart attack ;) Wallaby is still ~1 month away (and more like ~1.5 months+ for TripleO as we always trail the release) :) As mentioned in the last tripleo irc meeting [1] the deadline for wallaby cycle highlights is next Friday 12th March [2]. I had a go at and posted the proposal to https://review.opendev.org/c/openstack/releases/+/778971 . Please comment on the review or here if you want to update the wording and especially if I have forgotten to include something please accept my apologies if you let me know I can fix it :) thanks, marios [1] http://eavesdrop.openstack.org/meetings/tripleo/2021/tripleo.2021-03-02-14.… [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020714…

1 0

[glance] Doc about swift as backend
by Cristina Mayo Sarmiento 05 Mar '21

05 Mar '21

Hi everyone, Are there any specific documentation about how to configure Swift as backend of Glance service? I've found this: https://docs.openstack.org/glance/latest/configuration/configuring.html but I'm not sure what are the options I need. Firstly, I follow the installation guides of glance: https://docs.openstack.org/glance/latest/install/install-ubuntu.html and I have now file as store but I'rather change it. Thanks!

3 2

[release] Release countdown for week R-5 Mar 08 - Mar 12
by Herve Beraud 05 Mar '21

05 Mar '21

Development Focus ----------------- We are getting close to the end of the Wallaby cycle! Next week on 11 March 2021 is the Wallaby-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the Xena cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on 11 March, 2021. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/wallaby branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… 11 March, 2021 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also the deadline for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Cross-project events: - Wallaby-3 milestone (feature freeze): 11 March, 2021 (R-5 week) - RC1 deadline: 22 March, 2021 (R-3 week) - Final RC deadline: 5 April, 2021 (R-1 week) - Final Wallaby final release: 14 April, 2021 Project-specific events: - Cinder 3rd Party CI Compliance Checkpoint: 12 March, 2021 (R-5 week) -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

[kolla-ansible] partial upgrades / mixed releases in deployments
by Erik Panter 05 Mar '21

05 Mar '21

Hi, We are currently preparing to upgrade a kolla-ansible deployed OpenStack cluster and were wondering if it is possible to upgrade individual services independently of each other, for example to upgrade one service at a time to Ussuri while still using kolla-ansible to deploy and reconfigure the Train versions of the other services. Our idea was that either the Ussuri release of kolla-ansible is used to deploy Train and Ussuri services (with properly migrated configuration), or that two different releases and configurations are used for the two sets of services in the same deployment. Does anyone have experience if this is practical or even possible? Thank you in advance, Erik _____ Erik Panter Systementwickler | Infrastruktur Mittwald CM Service GmbH & Co. KG Königsberger Straße 4-6 32339 Espelkamp Tel.: 05772 / 293-900 Fax: 05772 / 293-333 Mobil: 0151 / 12345678 e.panter(a)mittwald.de https://www.mittwald.de Geschäftsführer: Robert Meyer, Florian Jürgens St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen Informationen zur Datenverarbeitung im Rahmen unserer Geschäftstätigkeit gemäß Art. 13-14 DSGVO sind unter www.mittwald.de/ds abrufbar.

2 1

Need help to get rally test suite
by Ankit Goel 04 Mar '21

04 Mar '21

Hello Experts, Need some help on rally. I have installed Openstack rally on centos. Now I need to run some benchmarking test suite. I need to know is there any pre-existing test suite which covers majority of test cases for Openstack control plane. So that I can just run that test suite. I remember earlier we use to get the samples under rally/samples/tasks/scenarios for each component but now I am not seeing it but I am seeing some dummy files. So from where I can get those samples json/yaml files which is required to run the rally tests. Awaiting for your response. Thanks in Advance Regards, Ankit Goel

3 3

[qa][election][ptl] PTL non-candidacy
by Masayuki Igawa 04 Mar '21

04 Mar '21

Hello all, I will not be running again for the QA PTL for the Xena cycle because I believe rotating leadership for open source projects is a good thing basically, and I will also have very limited bandwidth for the cycle. Therefore it would be best if someone else runs for QA PTL for the cycle. But I'll be around and continue to involve in OpenStack though it'll be downstream mostly. So, feel free to ping me if you want. Best Regards, -- Masayuki Igawa

1 0

[kolla][kolla-ansible] distro mixing on hosts
by Eric K. Miller 04 Mar '21

04 Mar '21

Hi, We have been pretty consistent in deploying CentOS 7 on physical hardware where Kolla Ansible deploys its containers. However, we're going to be switching to Debian 10.8. It looks like Kolla Ansible likely won't care which distro is installed on the physical hardware, and so some nodes could have CentOS 7 and others have Debian 10.8. Long-term, we'll replace the CentOS 7 machines with Debian 10.8 and re-deploy. Kolla Container images will still be CentOS 7, but we will be recreating Kolla images with Debian and deploying those long term too. Is this supported? Any obvious issues we should be aware of? We will have the same interface names, so we will be pretty consistent in terms of the environment - but wanted to see if there was any gotchas that we didn't think of. Also, I guess I should ask if there are any specific Debian 10.8 issues we should be aware of? Has anybody else done this? :) Thanks! Eric

2 2

[TripleO][Validation] Validation CLI simplification
by Mathieu Bultel 04 Mar '21

04 Mar '21

Hi TripleO Folks, I'm raising this topic to the ML because it appears we have some divergence regarding some design around the way the Validations should be used with and without TripleO and I wanted to have a larger audience, in particular PTL and core thoughts around this topic. The current situation is: We have an openstack tripleo validator set of sub commands to handle Validation (run, list ...). The CLI validation is taking several parameters as an entry point and in particular the stack/plan, Openstack authentication and static inventory file. By asking the stack/plan name, the CLI is trying to verify and understand if the plan or the stack is valid, if the Overcloud exists somewhere in the cloud before passing that to the tripleo-ansible-inventory script and trying to generate a static inventory file in regard to what --plan or stack has been passed. The code is mainly here: [1]. This behavior implies several constraints: * Validation CLI needs Openstack authentication in order to do those checks * It introduces some complexity in the Validation code part: querying Heat to get the plan name to be sure the name provided is correct, get the status of the stack... In case of Standalone deployment, it adds more complexity then. * This code is only valid for "standard" deployments and usage meaning it doesn't work for Standalone, for some Upgrade and FFU stages and needs to be bypassed for pre-undercloud deployment. * We hit several blockers around this part of code. My proposal is the following: Since we are thinking of the future of Validation and we want something more robust, stronger, simpler, usable and efficient, I propose to get rid of the plan/stack and authentication functionalities in the Validation code, and only ask for a valid inventory provided by the user. I propose as well to create a new entry point in the TripleO CLI to generate a static inventory such as: openstack tripleo inventory generate --output-file my-inv.yaml and then: openstack tripleo validator run --validation my-validation --inventory my-inv.yaml By doing that, I think we gain a lot in simplification, it's more robust, and Validation will only do what it aims for: wrapp Ansible execution to provide better logging information and history. The main concerns about this approach is that the user will have to provide a valid inventory to the Validation CLI. I understand the point of view of getting something fully autonomous, and the way of just kicking *one* command and the Validation can be *magically* executed against your cloud, but I think the less complex the Validation code is, the more robust, stable and usable it will be. Deferring a specific entry point for the inventory, which is a key part of post deployment action, seems something more clear and robust as well. This part of code could be shared and used for any other usages instead of calling the inventory script stored into tripleo-validations. It could then use the tripleo-common inventory library directly with tripleoclient, instead of calling from client -> tripleo-validations/scripts -> query tripleo-common inventory library. I know it changes a little bit the usage (adding one command line in the execution process for getting a valid inventory) but it's going in a less buggy and racy direction. And the inventory should be generated only once, or at least at any big major cloud change. So, I'm glad to get your thoughts on that topic and your overall views around this topic. Thanks, Mathieu [1] https://github.com/openstack/tripleo-validations/blob/master/tripleo_valida…

3 3

[neutron] Drivers meeting 05.03.2021 cancelled
by Slawek Kaplonski 04 Mar '21

04 Mar '21

Hi, Due to lack of agenda let's cancel tomorrow's drivers meeting. Have a great weekend and see You on the meeting next week. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[Consultation] SFC issue
by Jhen-Hao Yu 04 Mar '21

04 Mar '21

Dear Sir, We are testing a simple SFC in OpenStack (Stein) + OpenDaylight (Neon) + Open vSwitch (v2.11.1). It's an all-in-one deployment. We have read the document: https://readthedocs.org/projects/odl-sfc/downloads/pdf/latest/ and https://github.com/opnfv/sfc/blob/master/docs/release/scenarios/os-odl-sfc-… [image: image.png] Our SFC topology: [image: enter image description here] <https://i.stack.imgur.com/7QMWh.png> All on the same compute node. Build SFC through API: 1. openstack sfc flow classifier create --source-ip-prefix 10.20.0.0/24 --logical-source-port p0 FC1 2. openstack sfc port pair create --description "Firewall SF instance 1" --ingress p1 --egress p1 --service-function-parameters correlation=None PP1 3. openstack sfc port pair group create --port-pair PP1 PPG1 4. openstack sfc port chain create --port-pair-group PPG1 --flow-classifier FC1 --chain-parameters correlation=nsh PC1 Ping from client to server, but packet did not pass through firewall，open vswitch log show: [image: enter image description here] <https://i.stack.imgur.com/eucDz.png> Flow table: [image: enter image description here] <https://i.stack.imgur.com/cx3rJ.jpg> trace flow: [image: enter image description here] <https://i.stack.imgur.com/Jhi8M.png> Is there something wrong with the OpenStack instructions? It seems SFC proxy not work or there may be some bugs in "networking-sfc"? Thanks! Sincerely, Jhen-Hao >From NTU CSIE [image: Mailtrack] <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=sig…> Sender notified by Mailtrack <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=sig…> 03/04/21, 05:26:34 PM

1 0

[election][release] Hervé Beraud candidacy for Release Management PTL for Xena
by Herve Beraud 04 Mar '21

04 Mar '21

(nomination posted to https://review.opendev.org/c/openstack/election/+/778623) Hello, I would like to continue serving as PTL for Release Management during the Xena cycle. Wallaby was my first PTL experience and it allowed me to deeply improve my knowledge about Openstack. I'd like to continue to work on growing the core team to constitute experienced team members to whom we could pass the torch. Anything we can do to help anyone to join the team and know what to do and how to do it will be better for us all. We have a lot of our processes mostly automated, but we also have few unfinished business from the Wallaby cycle. So as a PTL I have the intention to make the team focus on finishing these work. It has been an interesting, active and rewarding release cycle, and I am excited to continue learning and applying those lessons to keep things moving and looking for any ways I can add to the already great body of work we have in our release. I will be happy to do it if you give me the opportunity. Thanks for your consideration, Hervé -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

[election][TripleO] PTL candidacy for Xena
by Marios Andreou 03 Mar '21

03 Mar '21

(nomination posted to https://review.opendev.org/c/openstack/election/+/778500) Hello I would like to continue serving as PTL for TripleO during the Xena cycle. Wallaby was my first PTL experience and it has been challenging and rewarding. I've learnt a lot about release processes and other repo related admin (like moving projects to the Independent release cycle). As I said in the W candidacy nomination [1], nowadays TripleO works in self-contained squads that drive technical decisions. We've had a lot of work across these squads (as always) during W with progress in a number of areas including moving port/network creation outside of Heat (ports v2), tripleo-ceph/tripleo-ceph-client and switching out ceph-ansible for cephadm, removing swift and the deployment plan, BGP support with frrouter and using ephemeral Heat for the overcloud deployment. I'd like to continue what i started in W, which is, to increase socialisation across tripleo squads and try to reign in the multitude of repos that we have created (and some now abandoned) over the years. After a well attended Wallaby PTG we have reinstated our traditional IRC meetings in #tripleo. I've started to "tidy up" our repos, moving some of the older and no longer used projects to 'independent' (os-refresh-config and friends, tripleo-ipsec) and started the process to mark older branches as EOL, starting with Rocky. There is a lot more to do here and I will be happy to do it if you give me the opportunity, thanks for your consideration, marios [1] https://opendev.org/openstack/election/raw/branch/master/candidates/wallaby…

1 0

Puppet openstack modules
by Bessghaier, Narjes 03 Mar '21

03 Mar '21

Dear OpenStack team, My name is Narjes and I'm a PhD student at the University of Montréal, Canada. My current work consists of analyzing code reviews on the puppet modules. I would like to precisely know what the ruby files are used for in the puppet modules. As mentioned in the official website, most of unit test are written in ruby. Are ruby files destined to carry out units tests or destined for production code. I appreciate your help, Thank you

3 4

[election][nova] PTL Candidacy for Wallaby
by Balazs Gibizer 03 Mar '21

03 Mar '21

Hi, I would like to continue serving as the Nova PTL in the Xena cycle. In Wallaby I hope I helped to keep Nova alive and kicking and I intend to continue what I have started. My employer is supportive to continue spending time on PTL and core duties. If I am elected then I will try to focus on the following areas: * Keeping the Nova bug backlog under control * Working on changes that help the maintainability and stability of Nova * Finishing up things that are already ongoing before starting new items Also, I'd like to note that if elected then Xena will be my 3rd consecutive term as Nova PTL so I will spend some time during the cycle to find my successor for the Y cycle. Cheers, gibi

1 0

Train/SR-IOV direct port mode live-migration - question
by Heib, Mohammad (Nokia - IL/Kfar Sava) 03 Mar '21

03 Mar '21

Hi All, we recently moved to openstack Train and according to the version release notes the SR-IOV direct port live-migration support was added to this version. so we tried to do some live-migration to vm with two SR-IOV direct ports attached to bond interface on the vm (no vSwitch interface or a indirect only direct ports) but seems that we have an issue with maintaining the network connectivity during and after the live-migration, according to [1] i see that in order to maintain network connectivity during the migration we have to add one indirect or vswitch port to the bond and this interface will carry the traffic during the migration and once the migration completed the direct port will back to be the primary slave on the target VM bond. my question is if we don't add the indirect port we will lose the connectivity during the migration which makes sense to me, but why the connectivity does not back after the migration completed successfully, and why the bond master boot up with no slaves on the target VM? according to some documents and blueprints that I found in google (including [2],[3]) the guest os will receive a virtual hotplug add even and the bond master will enslave those devices and connectivity will back which is not the case here. so I wondering maybe I need to add some scripts to handle those events (if so where to add them) or some network flags to the ifcfg-* files or i need to use a specific guest os? [1] : https://specs.openstack.org/openstack/nova-specs/specs/stein/approved/libvi… <https://specs.openstack.org/openstack/nova-specs/specs/stein/approved/libvi…> [2] :https://www.researchgate.net/publication/228722278_Live_migration_with_pass-through_device_for_Linux_VM <https://www.researchgate.net/publication/228722278_Live_migration_with_pass…> [3] :https://openstack.nimeyo.com/72653/openstack-nova-neutron-live-migration-with-direct-passthru <https://openstack.nimeyo.com/72653/openstack-nova-neutron-live-migration-wi…> *bond master ifcfg file:* DEVICE=bond1 BONDING_OPTS=mode=active-backup HOTPLUG=yes TYPE=Bond BONDING_MASTER=yes BOOTPROTO=none NAME=bond1 ONBOOT=yes *slaves ifcfg files:* TYPE=Ethernet DEVICE=eth0 HOTPLUG=no ONBOOT=no MASTER=bond1 SLAVE=yes BOOTPROTO=none NM_CONTROLLED=no *guest OS:* CentOS Linux release 7.7.1908 (Core) * * */Thanks in advance for any help :)/,*

2 1

Re: [openstack-dev] Are we ready to put stable/ocata into extended maintenance mode?
by Alex Schultz 03 Mar '21

03 Mar '21

On Tue, Sep 18, 2018 at 1:30 PM Alex Schultz <aschultz(a)redhat.com> wrote: > > On Tue, Sep 18, 2018 at 1:27 PM, Matt Riedemann <mriedemos(a)gmail.com> wrote: > > The release page says Ocata is planned to go into extended maintenance mode > > on Aug 27 [1]. There really isn't much to this except it means we don't do > > releases for Ocata anymore [2]. There is a caveat that project teams that do > > not wish to maintain stable/ocata after this point can immediately end of > > life the branch for their project [3]. We can still run CI using tags, e.g. > > if keystone goes ocata-eol, devstack on stable/ocata can still continue to > > install from stable/ocata for nova and the ocata-eol tag for keystone. > > Having said that, if there is no undue burden on the project team keeping > > the lights on for stable/ocata, I would recommend not tagging the > > stable/ocata branch end of life at this point. > > > > So, questions that need answering are: > > > > 1. Should we cut a final release for projects with stable/ocata branches > > before going into extended maintenance mode? I tend to think "yes" to flush > > the queue of backports. In fact, [3] doesn't mention it, but the resolution > > said we'd tag the branch [4] to indicate it has entered the EM phase. > > > > 2. Are there any projects that would want to skip EM and go directly to EOL > > (yes this feels like a Monopoly question)? > > > > I believe TripleO would like to EOL instead of EM for Ocata as > indicated by the thead > http://lists.openstack.org/pipermail/openstack-dev/2018-September/134671.ht… > Bringing this backup to see what we need to do to get the stable/ocata branches ended for the TripleO projects. I'm bringing this up because we have https://review.openstack.org/#/c/647009/ which is for the upcoming rename but CI is broken and we have no interest in continue to keep the stable/ocata branches alive (or fix ci for them). Thanks, -Alex > Thanks, > -Alex > > > [1] https://releases.openstack.org/ > > [2] > > https://docs.openstack.org/project-team-guide/stable-branches.html#maintena… > > [3] > > https://docs.openstack.org/project-team-guide/stable-branches.html#extended… > > [4] > > https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.… > > > > -- > > > > Thanks, > > > > Matt > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

5 11

anti-affinity: what're the mechanics?
by Ken D'Ambrosio 03 Mar '21

03 Mar '21

Hey, all. Turns out we really need anti-affinity running on our (very freaking old -- Juno) clouds. I'm trying to find docs that describe its functionality, and am failing. If I enable it, and (say) have 10 hypervisors, and 12 VMs to fire off, what happens when VM #11 goes to fire? Does it fail, or does the scheduler just continue to at least *try* to maintain as few possible on each hypervisor? Thanks! -Ken

3 2

[victoria][nova] Instance Live Migration
by Ammad Syed 02 Mar '21

02 Mar '21

Hi, I am trying to configure live migration of instance backed by lvm iscsi storage. I have done below mentioned config in nova.conf. [libvirt] virt_type = kvm volume_use_multipath = True live_migration_uri = qemu+ssh://nova@%s/system The live migration is being failed with below logs. 2021-03-03 07:15:51.917 706290 INFO nova.compute.manager [-] [instance: 7de891d3-c712-434c-b39f-08e512e46e83] Took 6.02 seconds for pre_live_migration on destination host kvm12-a1-khi01. 2021-03-03 07:15:52.029 706290 ERROR nova.virt.libvirt.driver [-] [instance: 7de891d3-c712-434c-b39f-08e512e46e83] Live Migration failure: operation failed: Failed to connect to remote libvirt URI qemu+ssh://nova@kvm12-a1-khi01/system: Cannot recv data: Host key verification failed.: Connection reset by peer: libvirt.libvirtError: operation failed: Failed to connect to remote libvirt URI qemu+ssh://nova@kvm12-a1-khi01/system: Cannot recv data: Host key verification failed.: Connection reset by peer 2021-03-03 07:15:52.444 706290 ERROR nova.virt.libvirt.driver [-] [instance: 7de891d3-c712-434c-b39f-08e512e46e83] Migration operation has aborted 2021-03-03 07:15:52.489 706290 INFO nova.compute.manager [-] [instance: 7de891d3-c712-434c-b39f-08e512e46e83] Swapping old allocation on dict_keys(['3e5679c8-165e-4c35-9de5-ef0d3af0f9d8']) held by migration f519f768-5a62-4f17-9ac0-1cc2c814ec3a for instance 2021-03-03 07:15:55.927 706290 WARNING nova.compute.manager [req-116cf2ef-4720-421e-9aad-75451e3deafe b95c0ad0fb9848598988b5bff99ca55b abf41db7e6dc429086713f4b46cd3655 - default default] [instance: 7de891d3-c712-434c-b39f-08e512e46e83] Received unexpected event network-vif-unplugged-df7666d6-add3-4638-98e1-14db30122c3f for instance with vm_state active and task_state None. I am able to login from host1 to host2 via ssh without password. Also I have disabled hostkey check in ssh config of nova. (~/.ssh/config) Host * StrictHostKeyChecking no UserKnownHostsFile=/dev/null I am able to connect host2 from host 1 and vice versa via virsh uri. nova@kvm10-a1-khi01:~$ virsh -c qemu+ssh://nova@kvm12-a1-khi01/system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # exit No sure where i am missing something. - Ammad

1 0

Some questions about Ironic bare metal
by Ankele zhang 02 Mar '21

02 Mar '21

Hi, I have included Ironic service into my rocky OpenStack platform. Using the IPMI driver. The cleaning network and the provisioning network are my provider network. I have some questions about Ironic deleting and inspecting. 1、every time I delete my baremetal nodes, I need to delete the associated servers first. the servers delete successfully, but the associated servers filed in nodes are still exist. So I need to set nodes to maintenance mode before I can delete bare metal nodes. what's more, the port list in 'openstack port list' which belong to the nodes can not be deleted automatically. How can I delete nodes correctly? 2、If the new created baremetal nodes' system disks have exist OS data.I cannot inspect them, I need to clean them first, but the cleaning step need MAC address of the nodes and the MAC addresses are obtained by inspecting. So what should I do? I don't want to fill in the MAC addresses manually. I have got the PXE boot but was immediately plugged into the existing system as: [image: image.png] 0.1s later: [image: image.png] Looking forward to your help. Ankele.

2 1

[all][elections][ptl][tc] Combined PTL/TC April 2021 Nominations Kickoff
by Kendall Nelson 02 Mar '21

02 Mar '21

Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (5 positions) are now open and will remain open until Mar 09, 2021 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/xena/<Project_Name or "TC">/<email_address> (for example, "candidates/xena/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the Victoria to Wallaby timeframe, Apr 24, 2020 00:00 UTC - Mar 08, 2021 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Mar 12, 2021 23:45 UTC through to Mar 19, 2021 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the Victoria to Wallaby timeframe, Apr 24, 2020 00:00 UTC - Mar 08, 2021 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the Victoria to Wallaby timeframe, Apr 24, 2020 00:00 UTC - Mar 08, 2021 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ATCs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ATCs. Please find below the timeline: nomination starts @ Mar 02, 2021 23:45 UTC nomination ends @ Mar 09, 2021 23:45 UTC campaigning starts @ Mar 09, 2021 23:45 UTC campaigning ends @ Mar 11, 2021 23:45 UTC elections start @ Mar 12, 2021 23:45 UTC elections end @ Mar 19, 2021 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2021-03-08 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials -Kendall Nelson (diablo_rojo)

1 0

[all][elections][ptl][tc] IMPORTANT Note About March 2021 Elections
by Jeremy Stanley 02 Mar '21

02 Mar '21

Please note that to be eligible to vote in upcoming Technical Committee and Project Team Lead elections, you must make sure that your Preferred Email Address in Gerrit appears somewhere in your Open Infrastructure Foundation Individual Member profile. To check this, visit https://review.opendev.org/settings/#EmailAddresses while authenticated to Gerrit and make a note of which address has the Preferred button selected. Next visit https://openstackid.org/accounts/user/profile and (after authenticating) make sure that address appears in at least one of the Email, Second Email, or Third Email fields. If not, add it to one of the available Email fields there and click the Save button. This requirement has changed slightly from before (when any address known to Gerrit was sufficient), because of slightly stricter API handling in the newer Gerrit release we're now running. If you have any questions, please feel free to reply or reach out to the technical election officials in the #openstack-election IRC channel on Freenode. -- Jeremy Stanley

1 0

Re: [openstack-community] Ovn chassis error possibly networking config error.
by Amy Marrich 02 Mar '21

02 Mar '21

Deepesh, Forwarding to the OpenStack Discuss mailing list. Thanks, Amy (spotz) On Sat, Feb 27, 2021 at 12:42 PM Dees <motosingh(a)yahoo.co.uk> wrote: > Hi All, > > Deployed openstack all service yesterday and seemed to be running since > power cycling the openstack today. > > Then deployed and configured VM instance with networking but config > onv-chassis is reporting error, as I am new to openstack (having used it > number of years back) mind guiding where I should be looking any help will > be greatly appreciated. > > > > nova-compute/0* active idle 1 10.141.14.62 > Unit is ready > ntp/0* active idle 10.141.14.62 > 123/udp chrony: Ready > ovn-chassis/0* error idle 10.141.14.62 > hook failed: "config-changed" > > > Deployed VM instance using the following command line. > > > curl > http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img > | \ > openstack image create --public --container-format bare --disk-format > qcow2 \ > --property architecture=x86_64 --property hw_disk_bus=virtio \ > --property hw_vif_model=virtio "focal_x86_64" > > openstack flavor create --ram 512 --disk 4 m1.micro > > openstack network create Pub_Net --external --share --default \ > --provider-network-type vlan --provider-segment 200 > --provider-physical-network physnet1 > > openstack subnet create Pub_Subnet --allocation-pool > start=10.141.40.40,end=10.141.40.62 \ > --subnet-range 10.141.40.0/26 --no-dhcp --gateway 10.141.40.1 \ > --network Pub_Net > > openstack network create Network1 --internal > openstack subnet create Subnet1 \ > --allocation-pool start=192.168.0.10,end=192.168.0.199 \ > --subnet-range 192.168.0.0/24 \ > --gateway 192.168.0.1 --dns-nameserver 10.0.0.3 \ > --network Network1 > > Kind regards, > Deepesh > _______________________________________________ > Community mailing list > Community(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/community >

3 3

[neutron] Bug deputy report (week starting on 2021-02-22)
by Bernard Cafarelli 02 Mar '21

02 Mar '21

Hello neutrinos, this is our first new bug deputy rotation for 2021, overall a quiet week with most bugs already fixed or good progress. DVR folks may be interested in the discussion ongoing on the single High bug, also I left one bug in Opinion on OVS agent main loop Critical * neutron.tests.unit.common.test_utils.TestThrottler test_throttler is failing - https://bugs.launchpad.net/neutron/+bug/1916572 Patch was quickly merged: https://review.opendev.org/c/openstack/neutron/+/777072 High * [dvr] bound port permanent arp entries never deleted - https://bugs.launchpad.net/neutron/+bug/1916761 Introduced with https://review.opendev.org/q/I538aa6d68fbb5ff8431f82ba76601ee34c1bb181 Lengthy discussion in the bug itself and suggested fix https://review.opendev.org/c/openstack/neutron/+/777616 Medium * [OVN][QOS] OVN DB QoS rule is not removed when a FIP is dissasociated - https://bugs.launchpad.net/neutron/+bug/1916470 Patch by ralonsoh merged https://review.opendev.org/c/openstack/neutron/+/776916 * A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled - https://bugs.launchpad.net/neutron/+bug/1896734 Actually reported earlier on charm and oslo, ralonsoh looking into it from neutron side * StaleDataError: DELETE statement on table 'standardattributes' expected to delete 2 row(s); 1 were matched - https://bugs.launchpad.net/neutron/+bug/1916889 Spotted by Liu while looking at dvr bug, patch sent to neutron-lib https://review.opendev.org/c/openstack/neutron-lib/+/777581 Low * ovn-octavia-provider can attempt to write protocol=None to OVSDB - https://bugs.launchpad.net/neutron/+bug/1916646 This appears in some functional test results, otherwiseguy sent https://review.opendev.org/c/openstack/ovn-octavia-provider/+/777201 Opinion * use deepcopy in function rpc_loop of ovs-agent - https://bugs.launchpad.net/neutron/+bug/1916761 My hunch is that we are fine here, but please chime in other opinions Passing the baton to our PTL for next week! -- Bernard Cafarelli

2 2

Question about Ubuntu Server
by Eduardo Almeida Costa 02 Mar '21

02 Mar '21

Hello everybody. At my workplace, we will migrate from CentOS to Ubuntu Server. However, reading about it on forums and official documentation, it was not clear to me which version of Ubuntu Server is best for the production medium, 18.04 or 20.04. Can someone tell me what better version I can implement for production servers? My best regards. Eduardo.

5 7

[swift] Unable to get or create objects
by Cristina Mayo 02 Mar '21

02 Mar '21

Hello, I don't have a lot of knowledge about Openstack. I have installed Swift in my Openstack Ussuri cloud with one storage node but I am not be able to list or create objects. In the controller node I saw these errors: proxy-server: ERROR with Account server 10.20.20.1:6202/sdb re: Trying to HEAD /v1/AUTH_c2b7d6242f3140f09d283e8fbb88732a: Connection refused (txn: tx370fb5929a6c4cf397384-00603dfe35) proxy-server: Account HEAD returning 503 for [] (txn:tx370fb5929a6c4cf397384-00603dfe35) Any idea? Thanks in advance!

2 1

[all][elections][ptl][tc] Combined PTL/TC March 2021 Election Season
by Kendall Nelson 01 Mar '21

01 Mar '21

Election details: https://governance.openstack.org/election/ The nomination period officially begins Mar 02, 2021 23:45 UTC. Please read the stipulations and timelines for candidates and electorate contained in this governance documentation. 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. 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[1] so that we may address your concerns. Thank you, -Kendall Nelson (diablo_rojo) [1] https://governance.openstack.org/election/#election-officials

1 0

[cinder] bug deputy report for week of 2021-02-22
by Sofia Enriquez 01 Mar '21

01 Mar '21

This is a bug report from 2021-02-22 to 2021-02-26. Most of these bugs were discussed at the Cinder meeting last Wednesday 2021-02-24. Critical: - High: - https://bugs.launchpad.net/os-brick/+bug/1915678: "iSCSI+Multipath: Volume attachment hangs if session scanning fails''. Assigned to Takashi Kajinami (kajinamit). Medium: - https://bugs.launchpad.net/os-brick/+bug/1916264: "NVMeOFConnector can't connect volume ". Assigned to Zohar Mamedov (zoharm). - https://bugs.launchpad.net/python-cinderclient/+bug/1915996: "Fetching server version fails to support passing client certificates". Assigned to Sri Harsha mekala (harshayahoo). - https://bugs.launchpad.net/cinder/+bug/1915800: " XtremIO does not support ports filtering". Assigned to Vladislav Belogrudov (vlad-belogrudov). Low: - https://bugs.launchpad.net/cinder/+bug/1916258: "[docs] Install and configure a storage node in cinder ". Assigned to Sofia Enriquez (enriquetaso). Incomplete:- Undecided/Unconfirmed: - https://bugs.launchpad.net/cinder/+bug/1916980: "cinder sends old db object when delete an attachment". Assigned to wu.chunyang (wuchunyang). - https://bugs.launchpad.net/cinder/+bug/1916843: "Backup create failed: RBD volume flatten too long causing mq to timed out". Unassigned. Not a bug:- Feel free to reply/reach me if I missed something. Regards Sofi -- L. Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[openstack-helm] IRC Meeting Cancelled March 2nd
by Gage Hugo 01 Mar '21

01 Mar '21

Hello, Since there are no agenda items [0] for the IRC meeting tomorrow, March 2nd, we will cancel it. Our next IRC meeting will be March 9th. Thanks [0] https://etherpad.opendev.org/p/openstack-helm-weekly-meeting

1 0

[SIG][Containers][k8s] Merge? Retire?
by Kendall Nelson 01 Mar '21

01 Mar '21

Hello! As you might have noticed, we've been working on getting the sig governance site updated with current chairs, sig statuses. etc. Two SIGs that are in need of updates still. The k8s SIG's listed chairs have all moved on. The container SIG is still listed as forming. While not the exact same goal/topic, perhaps these can be merged? And if so, do we have any volunteers for chairs? The other option is to simply remove the Container SIG as its not completely formed at this point and retire the k8s SIG. Thoughts? Volunteers? -Kendall (diablo_rojo)

2 2

[all] April 2021 PTG Dates & Registration
by Kendall Nelson 01 Mar '21

01 Mar '21

Hello Everyone! I'm sure you all have been anxiously awaiting the announcement of the dates for the next virtual PTG[1]! The PTG will take place April 19-23, 2021! PTG registration is now open[2]. Like last time, it is free, but we will again be using it to communicate details about the event (schedules, passwords, etc), so please take two minutes to register! Early next week we will send out info to mailing lists about signing up teams. Also, the same as last time, we will have an ethercalc signup and a survey to gather some other data about your team. Can't wait to see you all there! -the Kendalls (diablo_rojo & wendallkaters) [1] https://www.openstack.org/ptg/ [2] https://april2021-ptg.eventbrite.com

4 5

VIP switch causing connections that refuse to die
by Michal Arbet 01 Mar '21

01 Mar '21

Hi, I found that keepalived VIP switch cause TCP connections that refuse to die on host where VIP was before it was switched. I filled a bug here -> https://bugs.launchpad.net/kolla-ansible/+bug/1917068 Fixed here -> https://review.opendev.org/c/openstack/kolla-ansible/+/777772 Video presentation of bug here -> https://download.kevko.ultimum.cloud/video_debug.mp4 I was just curious and wanted to ask here in openstack-discuss : If someone already seen this issue in past ? If yes, do you tweak net.ipv4.tcp_retries2 kernel parameter ? If no, how did you solve this ? Thank you, Michal Arbet ( kevko )

4 5

[puppet-openstack] stop using the ${pyvers} variable
by Thomas Goirand 01 Mar '21

01 Mar '21

Hi, Using the ${pyvers} so we can switch be between Python versions made sense 1 or 2 years ago. However, I'm in the opinion that we should stop using that, and switch to using python3 everywhere directly whenever possible. Though Tobias seems to not agree (see [1]), so I'm raising the topic in the list so we can discuss this together. Your thoughts? Cheers, Thomas Goirand (zigo) [1] https://review.opendev.org/c/openstack/puppet-swift/+/777564

5 10

[ironic] replacing the review priority list on the etherpad with hashtag
by Iury Gregory 01 Mar '21

01 Mar '21

Hello Ironicers! If you were present in the last weekly meeting, you are probably aware that we are using hashtags to track the patches that are in the priority list. If you are part of the ironic core group you can edit hashtags in any patch, if you are not core you can only add hashtags to the patches you are the Owner. In the gerrit UI you should be able to see Hashtags fields and a button ADD HASHTAG, the hashtag we are using is *ironic-week-prio* , so, if you have a patch that is in a good shape and ready for review you can add to the hashtag (just click in the ADD HASHTAG button, write the hashtag, click in SAVE). I will push a patch adding this information to our docs, I'm willing to do a session (or maybe two since we have people in different timezones) to explain. I will create a doodle and add to this thread. Thank you! -- *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>*

1 0

[baremetal-sig][ironic] Tue Mar 9, 2021, 2pm UTC: PTG input and Ironic Prometheus Exporter
by Arne Wiebalck 01 Mar '21

01 Mar '21

Dear all, The Bare Metal SIG will meet next week Tue Mar 9, 2021, at 2pm UTC on zoom. There will be two main points on the agenda: - A "topic-of-the-day" presentation/demo by Iury Gregory (iurygregory) on 'The Ironic Prometheus Exporter' and - Gathering (operator) input for the Ironic upstream team for the upcoming PTG: what are the pain points, what features should be added? The second item is also why this mail comes a week earlier than usual. Think about it, bring your items and/or add them to https://etherpad.opendev.or g/p/bare-metal-sig Everyone is welcome! Cheers, Arne

1 0

[TripleO] Moving stable/rocky for *-tripleo-* repos to End of Life OK?
by Marios Andreou 01 Mar '21

01 Mar '21

Hello all, it's been ~ 2 months now since my initial mail about $subject [1] and just under a month since my last bump on the thread [2] and I haven't heard any objections so far. So I think it's now appropriate to move forward with [3] which tags the latest commits to the stable/rocky branch of all tripleo-repos [4] as 'rock-eol' (except archived things like instack/tripleo-ui). Once it merges we will no longer be able to land anything into stable/rocky for all tripleo repos and the stable/rocky branch will be deleted. So, last chance! If you object please go and -1 the patch at [3] and/or reply here thanks, marios [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019338… [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019860.… [3] https://review.opendev.org/c/openstack/releases/+/774244 [4] https://releases.openstack.org/teams/tripleo.html

2 4