November 2021 - openstack-discuss

[neutron] Neutron Team meeting - vote on time of the meeting
by Lajos Katona 08 Nov '21

08 Nov '21

Hi Neutrinos As we discussed during the PTG, let's start a poll to see which time fits best the need of the team for the Neutron Team meeting. I prepared a doodle, please check which time slot would be best for you: https://doodle.com/poll/m973q9eyag8k385w?utm_source=poll&utm_medium=link The dates for the doodle now for next week, but please ignore that. Lajos Katona (lajoskatona)

1 0

[all][tc] What's happening in Technical Committee: summary 5th Nov, 21: Reading: 10 min
by Ghanshyam Mann 05 Nov '21

05 Nov '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * TC this week IRC meeting held on Nov 5th Thursday. * Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full recording are available @ - https://www.youtube.com/watch?v=4bt6iNaR3oI - IRC chat summary (topics and links): https://meetings.opendev.org/meetings/tc/2021/tc.2021-11-04-15.02.log.html * Next week's meeting will be on IRC on Nov 11th, Thursday 15:00 UTC, feel free the topic on agenda[1] by Nov 10th. 2. What we completed this week: ========================= * Retired kolla-cli [2] * Removed oslo independent deliverables from stable policy[3] * Magnum PTL is changed from Feilong Wang to Spryos[4] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * I have started the etherpad to collect the Yoga cycle targets for TC[5]. Open Reviews ----------------- * Eleven open reviews for ongoing activities[6]. RBAC discussion: continuing from PTG ---------------------------------------------- We had a discussion on Wed and sort out the many points especially on get-all-project resources or system and project scoped isolation. Complete notes are in this etherpad[7]. Lance is re-working on the goal and new implementation/details, feel free to review it for more feedback[8]. We will continue the discussion on next Wed Nov 10th same time[9], feel free to join for any additional query related to your project specific and we will also discuss about what all bits we can do in Yoga cycle and what all to move as next targets. Decouple the community-wide goals from cycle release ----------------------------------------------------------------- * As discussed in PTG, we are de-coupling the community-wide goals from release cycle so that we can improve the community-wide goal selection and its completion workflow where goals are multi-cycle like RBAC etc. * Proposal is up, please review and add your feedback[10]. Yoga release community-wide goal ----------------------------------------- * With the continuing the discussion on RBAC, we are re-working on the RBAC goal, please wait until we finalize the implementation[11] * There is one more goal proposal for 'FIPS compatibility and compliance'[12]. Adjutant need maintainers and PTLs ------------------------------------------- You might have seen the email[13] from Adrian to call the maintainer for Adjutant project, please reply to that email or here or on openstack-tc channel if you are interested to maintain this project. We will wait for next week also and if no-one shows up for help then we will start the retirement process. New project 'Skyline' proposal ------------------------------------ * We discussed it in TC PTG and there are few open points about python packaging, repos, and plugins plan which we are discussion on ML. * Still waiting from skyline team to work on the above points[14]. Updating the Yoga testing runtime ---------------------------------------- * As centos stream 9 is released, I have updated the Yoga testing runtime[15] with: 1. Add Debian 11 as tested distro 2. Change centos stream 8 -> centos stream 9 3. Bump lowest python version to test to 3.8 and highest to python 3.9 Stable Core team process change --------------------------------------- * Current proposal is under review[16]. Feel free to provide early feedback if you have any. * This is ready to merge and I will do that week early, feel free to add feedback if any. Merging 'Technical Writing' SIG Chair/Maintainers to TC ------------------------------------------------------------------ * Work to merge this SIG to TC is up for review[17]. * No response on usage and maintaining help for openstack/training-labs repo[18] and in TC meeting we decided to retire it next week. If you use or would like to maintain this, this is last chance to raise hand. TC tags analysis ------------------- * TC agreed to remove the framework and it is communicated in ML[19]. Project updates ------------------- * Retiring js-openstack-lib [20] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[21]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [22] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [23] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/814603 [3] https://review.opendev.org/c/openstack/governance/+/816828 [4] https://review.opendev.org/c/openstack/governance/+/816431 [5] https://etherpad.opendev.org/p/tc-yoga-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] https://etherpad.opendev.org/p/policy-popup-yoga-ptg [8] https://review.opendev.org/c/openstack/governance/+/815158 [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025666… [10] https://review.opendev.org/c/openstack/governance/+/816387 [11] https://review.opendev.org/c/openstack/governance/+/815158 [12] https://review.opendev.org/c/openstack/governance/+/816587 [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025555.… [14] https://review.opendev.org/c/openstack/governance/+/814037 [15] https://review.opendev.org/c/openstack/governance/+/815851 [16] https://review.opendev.org/c/openstack/governance/+/810721 [17] https://review.opendev.org/c/openstack/governance/+/815869 [18] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025586.… [19] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [20] https://review.opendev.org/c/openstack/governance/+/807163 [21] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [22] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [23] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

[docs] Double headings on every page
by Peter Matulis 04 Nov '21

04 Nov '21

Hi, I'm hitting an oddity in one of my projects where the titles of all pages show up twice. Example: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/wall… Source file is here: https://opendev.org/openstack/charm-deployment-guide/src/branch/master/depl… Does anyone see what can be causing this? It appears to happen only for the current stable release ('wallaby') and 'latest'. Thanks, Peter

5 6

[neutron] Drivers meeting - Friday 5.11.2021 - cancelled
by Lajos Katona 04 Nov '21

04 Nov '21

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. Lajos Katona (lajoskatona)

1 0

[baremetal-sig][ironic] Tue Nov 9, 2021, 2pm UTC: Hardware burn-in
by Arne Wiebalck 04 Nov '21

04 Nov '21

Dear all, The Bare Metal SIG will meet next week on Tue Nov 9, 2021, at 2pm UTC on zoom. The meeting will feature a "topic-of-the-day" presentation by Emmanouil Bagakis (CERN) on "Hardware Burn-in with Ironic" As usual, all details on https://etherpad.opendev.org/p/bare-metal-sig Everyone is welcome! Cheers, Arne

1 0

[barbican] Simple Crypto Plugin kek issue
by Ammad Syed 04 Nov '21

04 Nov '21

Hi, I have installed barbican and using it with openstack magnum. When I am using the default kek describe in document below, works fine and magnum cluster creation goes successful. https://docs.openstack.org/barbican/latest/install/barbican-backend.html But when I generate a new kek with below command. python3 -c "from cryptography.fernet import Fernet ; key = Fernet.generate_key(); print(key)" and put it in barbican.conf, the magnum cluster failed to create and I see below logs in barbican. 2021-10-29 12:53:28.932 568554 INFO barbican.plugin.crypto.simple_crypto [req-aaac01e9-82af-421b-b85a-ff998d904972 ad702ac807f44c73a32a9b7a795b693c d782069f335041138f0cb141fde9933f - default default] Software Only Crypto initialized 2021-10-29 12:53:28.932 568554 DEBUG barbican.model.repositories [req-aaac01e9-82af-421b-b85a-ff998d904972 ad702ac807f44c73a32a9b7a795b693c d782069f335041138f0cb141fde9933f - default default] Getting session... get_session /usr/lib/python3/dist-packages/barbican/model/repositories.py:364 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers [req-aaac01e9-82af-421b-b85a-ff998d904972 ad702ac807f44c73a32a9b7a795b693c d782069f335041138f0cb141fde9933f - default default] Secret creation failure seen - please contact site administrator.: cryptography.fernet.InvalidToken 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers Traceback (most recent call last): 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/cryptography/fernet.py", line 113, in _verify_signature 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers h.verify(data[-32:]) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/cryptography/hazmat/primitives/hmac.py", line 70, in verify 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers ctx.verify(signature) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/cryptography/hazmat/backends/openssl/hmac.py", line 76, in verify 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers raise InvalidSignature("Signature did not match digest.") 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers cryptography.exceptions.InvalidSignature: Signature did not match digest. 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers During handling of the above exception, another exception occurred: 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers Traceback (most recent call last): 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/api/controllers/__init__.py", line 102, in handler 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers return fn(inst, *args, **kwargs) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/api/controllers/__init__.py", line 88, in enforcer 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers return fn(inst, *args, **kwargs) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/api/controllers/__init__.py", line 150, in content_types_enforcer 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers return fn(inst, *args, **kwargs) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/api/controllers/secrets.py", line 456, in on_post 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers new_secret, transport_key_model = plugin.store_secret( 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/plugin/resources.py", line 108, in store_secret 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers secret_metadata = _store_secret_using_plugin(store_plugin, secret_dto, 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/plugin/resources.py", line 279, in _store_secret_using_plugin 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers secret_metadata = store_plugin.store_secret(secret_dto, context) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/plugin/store_crypto.py", line 96, in store_secret 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers response_dto = encrypting_plugin.encrypt( 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/plugin/crypto/simple_crypto.py", line 76, in encrypt 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers kek = self._get_kek(kek_meta_dto) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/plugin/crypto/simple_crypto.py", line 73, in _get_kek 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers return encryptor.decrypt(kek_meta_dto.plugin_meta) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/cryptography/fernet.py", line 76, in decrypt 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers return self._decrypt_data(data, timestamp, ttl, int(time.time())) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/cryptography/fernet.py", line 125, in _decrypt_data 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers self._verify_signature(data) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/cryptography/fernet.py", line 115, in _verify_signature 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers raise InvalidToken 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers cryptography.fernet.InvalidToken Any advise how to fix it ? - Ammad

2 1

[all][tc] Technical Committee next weekly meeting on Nov 4th at 1500 UTC
by Ghanshyam Mann 03 Nov '21

03 Nov '21

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Nov 4th at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Nov 3rd, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[TripleO] Branching our documentation
by James Slagle 03 Nov '21

03 Nov '21

Hello TripleO Owls, Our documentation, particularly the deploy guide, has become overly complex with all the branches that TripleO has supported over the years. I see notes that document functionality specific to releases all the way back to Mitaka! In ancient history, we made the decision to not branch our documentation because the work to maintain multiple branches outweighed the effort to just document all releases at once in the same branch. I think the scale has now tipped in the other direction. I propose that we create a stable/wallaby in tripleo-docs, and begin making the master branch specific to Yoga. This would also mean we could clean up all the old notes and admonitions about previous releases on the master branch. Going forward, if you make a change to the docs that applies to Yoga and Wallaby, you would need to backport that change to stable/wallaby. If you needed to make a change that applied only to Wallaby (or a prior release), you would make that change only on stable/wallaby. I'm not sure of all the plumbing required to make it so that the OpenStack Wallaby deploy guide builds from stable/wallaby, etc, but I wanted to get the idea out there first for feedback. Please let me know your thoughts. Thank you! -- -- James Slagle --

4 4

[ptl][release][stable][EM] Extended Maintenance - Ussuri
by Előd Illés 03 Nov '21

03 Nov '21

Hi, As Xena was released last week and we are in a less busy period, now it is a good time to call your attention to the following: In a month Ussuri is planned to transition to Extended Maintenance phase [1] (planned date: 2021-11-12). I have generated the list of the current *open* and *unreleased* changes in stable/ussuri for the follows-policy tagged repositories [2] (where there are such patches). These lists could help the teams who are planning to do a *final* release on Ussuri before moving stable/ussuri branches to Extended Maintenance. Feel free to edit and extend these lists to track your progress! * At the transition date the Release Team will tag the *latest* Ussuri releases of repositories with *ussuri-em* tag. * After the transition stable/ussuri will be still open for bug fixes, but there won't be official releases anymore. *NOTE*: teams, please focus on wrapping up your libraries first if there is any concern about the changes, in order to avoid broken (final!) releases! Thanks, Előd [1] https://releases.openstack.org/ [2] https://etherpad.opendev.org/p/ussuri-final-release-before-em

1 1

Attach Nvidia Jetson as compute node to openstack (aarch64)
by Pavlos Basaras 03 Nov '21

03 Nov '21

Hello everyone, I am relatively new to the community, thanks in advance for your time and help. I have an openstack cluster ready, working with several compute nodes based on x86 architecture. My current installation is based on Ussuri. I have recently acquired a couple of nvidia Jetson devices ( https://www.nvidia.com/en-us/autonomous-machines/embedded-systems/jetson-ag…) which I want to connect to the cluster. The arm cpu model name is ARMv8 Processor rev 0 (v8l). CPU flags on the arm architecture are different and hence egrep -c '(vmx|svm)' /proc/cpuinfo is empty to the best of my knowledge. However, i re-build the custom linux kernel (i.e, Tegra) of the Jetson device, enabling the KVM module. So once i used: *sudo kvm-ok* INFO: /dev/kvm exists KVM acceleration can be used *dmesg | grep -i kvm* [ 1.372478] kvm [1]: 16-bit VMID [ 1.372489] kvm [1]: IDMAP page: 80fa1000 [ 1.372498] kvm [1]: HYP VA range: 4000000000:7fffffffff [ 1.374185] kvm [1]: Hyp mode initialized successfully [ 1.374299] kvm [1]: vgic-v2@3884000 [ 1.374763] kvm [1]: vgic interrupt IRQ1 [ 1.374790] kvm [1]: virtual timer IRQ4 *dmesg | grep -i 'CPU features'* [ 0.687366] CPU features: detected feature: Privileged Access Never [ 0.687372] CPU features: detected feature: LSE atomic instructions [ 0.687378] CPU features: detected feature: User Access Override [ 0.687385] CPU features: detected feature: 32-bit EL0 Support Does this suffice to say that I can use KVM with libvirt for the nova openstack? The version of libvirt is 6.0.0. >From the nova logs i see the following with *virt_type = qemu* WARNING nova.virt.libvirt.driver [-] The libvirt driver is not tested on qemu/aarch64 by the OpenStack project and thus its quality can not be ensured. For more information, see: https://docs.openstack.org/nova/latest/user/support-matrix.html And as it detects the aarch64 device: CPU mode "host-passthrough" was chosen If i try to launch an instance i get the following error with qemu libvirt.libvirtError: unsupported configuration: CPU mode 'host-passthrough' for aarch64 qemu domain on aarch64 host is not supported by hypervisor where as i i use *virt_type= kvm* the error after trying to launch an instance is libvirt.libvirtError: unsupported configuration: Emulator '/usr/bin/qemu-system-aarch64' does not support virt type 'kvm' Any advice on how to proceed? all the best Pavlos.

1 0