- openstack-discuss - lists.openstack.org

[nova] instance device_metadata
by Arnaud Morin 16 Dec '21

16 Dec '21

Hey all, How is filled the device_metadata in instance_extra db? It's empty for my instances. It's supposed to be accessible then through metadata api, and contains at least network and block device info, but it's empty here. Thanks for any hint!

1 1

[manila] No IRC meeting on 30th Dec 2021
by Goutham Pacha Ravi 16 Dec '21

16 Dec '21

Hi Zorillas, As we discussed during our meeting today [1], we'll have our last IRC meeting for 2021 next week (23rd Dec 2021 at 1500 UTC) in OFTC's #openstack-meeting-alt. We'll skip the meeting on 30th Dec 2021 due to the year end holidays. As always, please feel free to add to the meeting agenda here: https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting Thanks, Goutham Pacha Ravi [1] https://meetings.opendev.org/meetings/manila/2021/manila.2021-12-16-15.01.l…

1 0

[all][tc][policy] Canceling policy popup team next meeting
by Ghanshyam Mann 16 Dec '21

16 Dec '21

Hello Everyone, Due to holiday weeks, we are cancelling the policy pop-up next meeting scheduled for 30th Dec. We will continue this biweekly meeting from 13th Jan. https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… -gmann

1 0

[cinder] festival of XS reviews 17 December 2021
by Brian Rosmaita 16 Dec '21

16 Dec '21

Hello Argonauts [0], Apologies for the lateness of this reminder, but hopefully everyone has already used the handy ICS file [1] to have this event on their personal calendars. The most recent edition of the Cinder Festival of XS Reviews will be held tomorrow (Friday 17 December). who: Everyone! what: The Cinder Festival of XS Reviews when: Friday 17 December 2021 from 1400-1600 UTC where: https://meetpad.opendev.org/cinder-festival-of-reviews etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews See you there! brian [0] At the Yoga PTG, the Cinder mascot was named "Argo" and the Cinder project team thereby became the "Argonauts". [1] http://eavesdrop.openstack.org/calendars/cinder-festival-of-reviews.ics

1 0

[cyborg][nova][qa]Question about Accelerator unbinding
by Di XiaoLi 15 Dec '21

15 Dec '21

hi, Cyborg and nova team: I am using cyborg with "Wallaby" release to manage my accelerator devices, while I'm trying to unbind the accelerator I found that the device was not actually unbound from the virtual machine. Here are my questions: 1. What is the function of the arq unbind command in cyborg ? 2. How to unbind the accelerator which bounded to vm? Does nova or cyborg support this function now？ Here are my steps: step1: openstack accelerator arq unbind ed205084-f58d-4fad-99b4-327a1398858f +---------------------+--------------------------------------+ | Field | Value | +---------------------+--------------------------------------+ | uuid | ed205084-f58d-4fad-99b4-327a1398858f | | state | Unbound | | device_profile_name | ssd | | hostname | None | | device_rp_uuid | None | | instance_uuid | None | | attach_handle_type | | | attach_handle_info | {} | +---------------------+--------------------------------------+ step2: login vm and check the device, but it still here. step3: stop vm and start vm, met the following error: "nova.exception.AcceleratorRequestOpFailed: Failed to get accelerator requests: Cyborg returned no accelerator requests for instance ca77ef4e-421c-4c6c-9d76-7618a90ec921"

4 9

[all][tc] Technical Committee next weekly meeting on Dec 16th at 1500 UTC
by Ghanshyam Mann 15 Dec '21

15 Dec '21

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

1 1

[stable][requirements][zuul] unpinned setuptools dependency on stable
by Balazs Gibizer 15 Dec '21

15 Dec '21

Hi, The latest setuptools (58.0) removed support for "use_2to3" [1] (deprecated since 46.2). Many OpenStack modules defines decorator==3.4.0 as lower constraints[2]. However, decorator 3.4.0 cannot be installed anymore with the latest setuptool as it depends on "use_2to3". On master, this can be solved easily by bumping the dependency to decorator 4.0.0. On stable/xena we can still solve it the same way with a new RC. But on older stable branches such solution might be against the stable policy as it would require a major bump on our dependencies. This issue is not limited to lower-constraints testing it just hit us there first. A similar break could happen in our upper constraints as well on old stable branches. The root of the problem is that we always use the latest setuptools in our CI testing even on old stable branches. Zuul's ensure-tox task[4] installs tox which installs the virtualenv package which bundles the latest setuptools package. This happens without applying any constraints. Then tox is used to install the project's dependencies under lower or upper constraints with the unconstrained setuptools available. During and after yesterday's nova meeting [3] we discussed possible solutions. Option 1: Bump the major version of the decorator dependency on stable. Pros: * easy to implement Cons: * might against the policy / breaks downstream packagers * needs to be done in each affected project[3] separately * not future proof. After a future setuptools release we can see a similar break with another of our dependencies. @Stable Cores: how do you feel about such bump? Option 2: Pin the setuptools version during tox installation Pros: * single solution for all affected projects * future proof against breaks introduced by future setuptools releases Cons: * complex change as it probably requires to extend the base task in zuul itself Option 3: turn off lower-constraints testing Pros: * easy to implement * some of us want to get rid of lower constraints anyhow Cons: * needs per project changes * not future proof against similar break affecting our upper constraints on old stable branches. Option 4: utilize pyproject.toml[6] to specify build-time requirements Unfortunately, I'm not sure if it is possible to restrict the maximum setuptools version with it As a side note I tried applying [tox]requires in tox.ini to restrict setuptools version[7] but It does not seem to take effect in our case[8]. @Stable Cores: what do you think what could be the way forward? Cheers, gibi [1] https://setuptools.pypa.io/en/latest/history.html#v58-0-2 [2] https://codesearch.openstack.org/?q=decorator%3D%3D3.4.0&i=nope&literal=nop… [3] https://meetings.opendev.org/irclogs/%23openstack-nova/%23openstack-nova.20… [4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-tox/tasks… [5] https://tox.readthedocs.io/en/latest/config.html#conf-requires [6] https://www.python.org/dev/peps/pep-0518/ [7] https://review.opendev.org/c/openstack/placement/+/810293/1/tox.ini [8] https://zuul.opendev.org/t/openstack/build/f78a0300c8734e7c8475309af1d2e1a4…

11 28

Re: [gate][tripleo] gate blocker
by Ananya Banerjee 15 Dec '21

15 Dec '21

Hi, We have a tripleo gate blocker. Patches 816991,16 and 821778 which fixes bugs needs to go first to unblock the rest. Can someone please get these two patches to the top of the queue? https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/821699/ https://review.opendev.org/c/openstack/tripleo-ci/+/821778/ Thanks, Ananya -- Ananya Banerjee, RHCSA, RHCE-OSP Software Engineer Red Hat EMEA <https://www.redhat.com/> anbanerj(a)redhat.com M: +491784949931 IM: frenzy_friday @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/>

3 3

[barbican][keystone] Weekly meetings to resume in 2022
by Douglas Mendizabal 15 Dec '21

15 Dec '21

Hi Barbican and Keystone contributors! I'll be taking some time off for the holidays starting next week and won't be available to chair the weekly meetings. I'll be back on January 11 to resume the weekly meetings for both Barbican and Keystone teams. Happy holidays, y'all! See you in 2022! - Douglas Mendizábal (redrobot)

1 0

[ops] [nova] problems with some default nova config values after update to Xena
by Massimo Sgaravatto 15 Dec '21

15 Dec '21

Hi After trying to update a CentOS8-stream testbed to Xena, there is a mess with some default values of nova In particular I see that: - everything (for all services) is being logged to syslog (it looks like that log_dir is using "none") - state_path for nova is using /usr/lib/python3.6/site-packages instead of /var/lib/nova Any hints on how to debug this? Thanks, Massimo

1 0

[Openstack][FOSDEM][CFP] Virtualization & IaaS Devroom
by Piotr Kliczewski 15 Dec '21

15 Dec '21

We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2022, to be hosted virtually on February 5th 2022. This year will mark FOSDEM’s 22nd anniversary as one of the longest-running free and open source software developer events, attracting thousands of developers and users from all over the world. Due to Covid-19, FOSDEM will be held virtually this year on February 5th & 6th, 2022. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors and virtual machine managers such as Xen Project, KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at users or developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 20th of December Acceptance notifications: 25th of December Final schedule announcement: 31st of December Recorded presentations upload deadline: 15th of January Devroom: 6th February 2022 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will need to be pre-recorded and put into our system at least a couple of weeks before the event. The presentations should be uploaded by 15th of January and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend the virtual FOSDEM event for the Q&A. We will not consider proposals from prospective speakers who are unsure whether they will be able to attend the FOSDEM virtual event. If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance with helping speakers to record the presentation as well as helping with streaming and chat moderation for the devroom. Please contact devroom mailing list [2] for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] https://penta.fosdem.org/submission/FOSDEM22 [2] iaas-virt-devroom at lists.fosdem.org

1 1

[cinder] Bug deputy report for week of 12-15-2021
by Sofia Enriquez 15 Dec '21

15 Dec '21

This is a bug report from 12-08-2021 to 12-15-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1953704 "Volume Type deletion error (image_volume_cache_enabled = True) - stable/xena". Unassigned. Incomplete - https://bugs.launchpad.net/cinder/+bug/1954613 "Blank volume's attach_status causes the volume list to fail". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1954664 "Customer has issues in removing the volumes on the hosts , volumes from 3par". Unassigned. Cheers -- 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

[all] Pending patches proposed by release bot
by Takashi Kajinami 15 Dec '21

15 Dec '21

(I'm using all tag instead of project specific tags because the list can be too long) Hi all, I noticed that many patches proposed by release bot are still pending on reviews. Because of this, I see several projects like; - unit tests are executed in old test runtimes, - release note for specific release is missing ... https://review.opendev.org/q/owner:infra-root%2540openstack.org+status:open I'd like to encourage each project to take a moment to move these forward, or abandon them if these are unnecessary. I'm trying to list up all projects affected but I might be missing some of them. So please check the above query to find anything maintained by your project. - heat - keystone - mistral - sahara - magnum - adjutant - monasca - murano - barbican - freezer - openstacksdk - zaqar - watcher - telemetry(ceilometer/aodh/panko) Thank you, Takashi

2 2

[baremetal-sig][ironic] Tue Dec 14, 2021, 2pm UTC: Metal3 Overview
by Arne Wiebalck 14 Dec '21

14 Dec '21

Dear all, The Bare Metal SIG will meet tomorrow Tue Dec 14, 2021, at 2pm UTC on zoom. The meeting will feature a "topic-of-the-day" presentation by Dmitry Tantsur (dtantsur) with an "Overview of Metal3" (and I hear there might be a demo even!) As usual, all details on https://etherpad.opendev.org/p/bare-metal-sig Everyone is welcome: come along, learn from the expert and bring your questions! Cheers, Arne

1 1

[swift][tempest][kolla]
by Michal Arbet 14 Dec '21

14 Dec '21

Hello to eveyrone, Please, could someone help me with swift capabilities not working when I'm tempesting openstack test stack ? Tempest : rm -rf /tmp/tempest-lock/; refstack-client test -v -c /opt/tempest/tempest.conf -- --regex tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest (.venv) root@ca6353106d83:/opt/refstack-client# rm -rf /tmp/tempest-lock/; refstack-client test -v -c /opt/tempest/tempest.conf -- --regex tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest 2021-12-13 17:44:33.001 4358 INFO tempest [-] Using tempest config file /etc/tempest/tempest.conf 2021-12-13 17:44:33,839 refstack_client:518 INFO Starting Tempest test... 2021-12-13 17:44:33.839 4358 INFO refstack_client [-] Starting Tempest test... {0} setUpClass (tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest) [0.000000s] ... FAILED Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/opt/refstack-client/.tempest/tempest/test.py", line 181, in setUpClass raise value.with_traceback(trace) File "/opt/refstack-client/.tempest/tempest/test.py", line 174, in setUpClass cls.resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/test_account_quotas_negative.py", line 36, in resource_setup super(AccountQuotasNegativeTest, cls).resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/base.py", line 95, in resource_setup body = cls.capabilities_client.list_capabilities() File "/opt/refstack-client/.tempest/tempest/lib/services/object_storage/capabilities_client.py", line 32, in list_capabilities self._error_checker(resp, body) File "/opt/refstack-client/.tempest/tempest/lib/common/rest_client.py", line 799, in _error_checker raise exceptions.Unauthorized(resp_body, resp=resp) tempest.lib.exceptions.Unauthorized: Unauthorized Details: {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'} ============================== Failed 1 tests - output below: ============================== setUpClass (tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest) ---------------------------------------------------------------------------------------------- Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/opt/refstack-client/.tempest/tempest/test.py", line 181, in setUpClass raise value.with_traceback(trace) File "/opt/refstack-client/.tempest/tempest/test.py", line 174, in setUpClass cls.resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/test_account_quotas_negative.py", line 36, in resource_setup super(AccountQuotasNegativeTest, cls).resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/base.py", line 95, in resource_setup body = cls.capabilities_client.list_capabilities() File "/opt/refstack-client/.tempest/tempest/lib/services/object_storage/capabilities_client.py", line 32, in list_capabilities self._error_checker(resp, body) File "/opt/refstack-client/.tempest/tempest/lib/common/rest_client.py", line 799, in _error_checker raise exceptions.Unauthorized(resp_body, resp=resp) tempest.lib.exceptions.Unauthorized: Unauthorized Details: {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'} ====== Totals ====== Ran: 1 tests in 0.0000 sec. - Passed: 0 - Skipped: 0 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 1 Sum of execute time for each test: 0.0000 sec. TEMPEST LOG : Response - Headers: {'content-type': 'application/json', 'content-length': '114', 'www-authenticate': 'Keystone uri=" http://192.168.205.254:5000"', 'x-trans-id': 'tx815e181e33fb4854b2631-0061b7787a', 'x-openstack-request-id': 'tx815e181e33fb4854b2631-0061b7787a', 'date': 'Mon, 13 Dec 2021 16:44:42 GMT', 'connection': 'close', 'status': '401', 'content-location': ' https://api.refstack.ultimum.cloud:8080/info'} Body: b'{"error": {"code": 401, "title": "Unauthorized", "message": "The request you have made requires authentication."}}' _log_request_full /opt/refstack-client/.tempest/tempest/lib/common/rest_client.py:450 Test from command line and from curl . /etc/kolla/refstack.sh ; curl -H "X-Auth-Token: $(openstack token issue -f value -c id)" https://api.refstack.ultimum.cloud:8080/info {"swift": {"version": "2.27.1.dev9", "strict_cors_mode": true, "policies": [{"name": "Policy-0", "aliases": "Policy-0", "default": true}], "allow_account_management": true, "account_autocreate": true, "max_file_size": 5368709122, "max_meta_name_length": 128, "max_meta_value_length": 256, "max_meta_count": 90, "max_meta_overall_size": 4096, "max_header_size": 8192, "max_object_name_length": 1024, "container_listing_limit": 10000, "account_listing_limit": 10000, "max_account_name_length": 256, "max_container_name_length": 256, "extra_header_count": 0}, "container_sync": {"realms": {}}, "bulk_upload": {"max_containers_per_extraction": 10000, "max_failed_extractions": 1000}, "bulk_delete": {"max_deletes_per_request": 10000, "max_failed_deletes": 1000}, "tempurl": {"methods": ["GET", "HEAD", "PUT", "POST", "DELETE"], "incoming_remove_headers": ["x-timestamp"], "incoming_allow_headers": [], "outgoing_remove_headers": ["x-object-meta-*"], "outgoing_allow_headers": ["x-object-meta-public-*"], "allowed_digests": ["sha1", "sha256", "sha512"]}, "ratelimit": {"account_ratelimit": 0.0, "max_sleep_time_seconds": 60.0, "container_ratelimits": [], "container_listing_ratelimits": []}, "container_quotas": {}, "account_quotas": {}, "slo": {"max_manifest_segments": 1000, "max_manifest_size": 8388608, "yield_frequency": 10, "min_segment_size": 1, "allow_async_delete": false}} Python Swiftclient : ubuntu@deploy:/opt/kolla-ansible$ . /etc/kolla/refstack.sh ; swift --os-auth-url http://192.168.205.254:5000/v3 --auth-version 3 --os-project-name refstack --os-project-domain-name default --os-username refstack --os-user-domain-name default --os-password SECRET capabilities Capabilities GET failed: http://192.168.205.254:8080/info 401 Unauthorized [first 60 chars of response] b'{"error": {"code": 401, "title": "Unauthorized", "message": ' Failed Transaction ID: txc1d8607e26eb4cd587459-0061b7791b It looks like swift client is broken, isn't it ? Or ? Maybe kolla-ansible is creating bad roles and config ? (operator_roles, reselleradmin_roel ..etc ? ) Tempest is from master Thank you very much, Kevko Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet(a)ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline>

3 5

[Diversity] D&I WG Meeting Time and IRC vs Video Poll
by Amy Marrich 14 Dec '21

14 Dec '21

Hi everyone, The Diversity and Inclusion WG is holding a poll to see if there would be interest in attending if it were on another day and time as well as if IRC vs Video would be preferred. We currently meet the first Monday of the month at 17:00 UTC. And hope to have a planning meeting as our first meeting of the year. Our first meeting of the new year is slated for January 3rd at 17:00 UTC and for IRC. We will take the poll results into consideration and may cancel the January meeting to allow folks to plan on attending in which case February's meeting would be the first of the year. Please vote for your preferred days and times AND also for IRC and/or Video. https://doodle.com/poll/mnzxkauzwf2isssm?utm_source=poll&utm_medium=link We are keeping to morning hours to encourage participation from EMEA but not overly early for PST folks to attend. We will keep the poll up through the end of the year. Please feel free to reach out with any questions or concerns and remember the Diversity and Inclusion WG is for ALL projects under the Open Infra Foundation! Thanks, Amy (spotz)

1 1

[keystone] OAuth2.0 implementation in Yoga
by Hiromu Asahina 14 Dec '21

14 Dec '21

Hi, Please, could any of the keystone core members give me some advice on this spec? https://review.opendev.org/c/openstack/keystone-specs/+/813152 We'd like to make the following points clear by the end of this year to forward the implementation. So, please kindly check it and please let me know your opinion. - OAuth2.0 scope [1]: As there are differences between OAuth2.0 scope format and the Application credentials access rule format and we haven't found a good solution to map them, we'd like to omit the implementation of the OAuth2.0 scope in Yoga. Is there any concerns? - Access policy configuration: - Which one is appropriate? (i) End-users can use the OAuth2.0 API if they have permission for the OAuth2.0 API even if they don't have permission for the Application credentials API (ii) End-users can use the OAuth2.0 API only if they have permission for both the OAuth2.0 API and the Application credentials API. - API endpoint: - Which one is appropriate? (i) `/identity/v3/auth/OS-OAUTH2/<user_id>/clients` (ii) `/identity/v3/users/{user_id}/OS-AUTH2/clients` (iii) other [1] https://datatracker.ietf.org/doc/html/rfc6749#page-23 Thanks, Hiromu Asahina (h_asahina)

1 0

[nova] Spawning instance that will do PXE booting
by Thomas Goirand 14 Dec '21

14 Dec '21

Hi, In order to test OCI [1] within OpenStack itself, I would need my instances to do PXE booting. This would be with something like this on the qemu command line: qemu-system-x86_64 -boot n I believe this would also mean setting-up network cards that can do PXE booting, like the e1000, which Qemu supports. If that is possible, then I would setup DHCP + tftp-hpa on another instance, wired on the same private network. Your thoughts? Is this possible? Cheers, Thomas Goirand (zigo) [1] https://salsa.debian.org/openstack-team/debian/openstack-cluster-installer

8 18

[all] testtools and support for Python 3.10 (error du to deprecation of distutils)
by Thomas Goirand 14 Dec '21

14 Dec '21

Hi, When I try to build rally-openstack, I get this, in the test discovery: /usr/lib/python3/dist-packages/rally/common/cfg.py:19: in <module> from oslo_config import fixture # noqa /usr/lib/python3/dist-packages/oslo_config/fixture.py:18: in <module> import fixtures /usr/lib/python3/dist-packages/fixtures/__init__.py:81: in <module> from fixtures.fixture import ( /usr/lib/python3/dist-packages/fixtures/fixture.py:34: in <module> from fixtures.callmany import ( /usr/lib/python3/dist-packages/fixtures/callmany.py:31: in <module> MultipleExceptions = try_import( /usr/lib/python3/dist-packages/testtools/helpers.py:30: in try_import __import__(module_name) /usr/lib/python3/dist-packages/testtools/__init__.py:99: in <module> from testtools.distutilscmd import TestCommand /usr/lib/python3/dist-packages/testtools/distutilscmd.py:7: in <module> from distutils.core import Command /usr/lib/python3.10/distutils/__init__.py:19: in <module> warnings.warn(_DEPRECATION_MESSAGE, E DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives This warning makes it impossible to discover rally-openstack tests, because of the imports here: https://github.com/testing-cabal/testtools/blob/master/testtools/distutilsc… Can someone work on removing distutils support from Testtools? Or is there a way to trick pytest to not fail? Help would be greatly appreciated here. Cheers, Thomas Goirand (zigo)

4 8

bug deputy report (week of Dec 6)
by Akihiro Motoki 14 Dec '21

14 Dec '21

Hi, I was a bug deputy last week. Here is a summary of last week. Two needs-attention bugs need what neutron should behave, so they need more investigation. Two OVN bugs and one gate-failure bug also need assignees and investigations. Thanks, Akihiro Motoki (amotoki) # Needs attention - https://bugs.launchpad.net/neutron/+bug/1953478 Resize and shelve server fails in the multinode CI jobs intemittent It was reported to nova by slawek, but gibi moved it to neutron as there is a question on when neutron send vif-plugged event to nova. We need to clarify when the vif-plugged event is sent and what is the expected behavior. - https://bugs.launchpad.net/neutron/+bug/1954384 Neutron doesn't use set dns-domain for Nova instance It would be nice if folks familiar with DNS integration can look into it. # OVN https://bugs.launchpad.net/neutron/+bug/1953510 neutron_ovn_metadata_agent doesn`t work after reconnect to new OVN Southbound leader DB https://bugs.launchpad.net/neutron/+bug/1953295 neutron-ovn-metadata-agent AttributeError: 'MetadataAgent' object has no attribute 'sb_idl' # Gate failures https://bugs.launchpad.net/neutron/+bug/1953479 Timeout in the scenario jobs' execution # Assigned https://bugs.launchpad.net/neutron/+bug/1953716 Improve message in the NetworkInUse exception # In Progress https://bugs.launchpad.net/neutron/+bug/1954316 In VXLAN interface creation, we must provide always a device https://bugs.launchpad.net/neutron/+bug/1954662 Quota driver "DbQuotaNoLockDriver" can lock when removing the expired reservations https://bugs.launchpad.net/neutron/+bug/1953480 Agents API test failed due to not expected "alive" status of the agent

1 0

[wallaby][ovn][Open vSwitch] HA for OVN DB servers using pacemaker
by Faisal Sheikh 14 Dec '21

14 Dec '21

Hi, I am using Openstack Wallaby release with OVN on Ubuntu 20.04. My environment consists of 2 compute nodes and 1 controller node. ovs-vswitchd (Open vSwitch) 2.15.0 Ubuntu Kernel Version: 5.4.0-88-generic - compute node1 172.16.30.1 - compute node2 172.16.30.3 - controller-khi01/Network node/Primary ovs-db IP 172.16.30.46 - backup ovs-db 172.16.30.47 I want to run OVSDB server to run in Active/Passive mode. Active OVSDB-server is on node "controller-khi01" and Passive OVSDB-server is on "controller02-khi01". I have setup Pacemaker to manage the ovn-northd(Open vSwitch) service between primary and backup ovn-db server. You can see the "pcs status" output below. But I am unable to replicate database state between primary and backup OVSDB server. If i execute "ovsdb-server --sync-from=server" command, getting below error. root@controller-khi01# ovsdb-server --sync-from=172.16.30.47 2021-12-14T09:16:29Z|00001|lockfile|WARN|/var/lib/openvswitch/.conf.db.~lock~: cannot lock file because it is already locked by pid 14121 ovsdb-server: I/O error: /etc/openvswitch/conf.db: failed to lock lockfile (Resource temporarily unavailable) root@controller-khi01# pcs status Cluster name: cluster1 Cluster Summary: * Stack: corosync * Current DC: controller-khi01 (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Tue Dec 14 07:53:06 2021 * Last change: Tue Dec 14 06:16:21 2021 by hacluster via crmd on controller02-khi01 * 2 nodes configured * 3 resource instances configured Node List: * Online: [ controller-khi01 controller02-khi01 ] Full List of Resources: * Clone Set: ovndb_servers-clone [ovndb_servers] (promotable): * Masters: [ controller-khi01 ] * Slaves: [ controller02-khi01 ] * ovn-virtual-ip (ocf::heartbeat:IPaddr2): Started controller-khi01 Failed Resource Actions: * ovndb_servers_monitor_10000 on controller02-khi01 'master' (8): call=17, status='complete', exitreason='', last-rc-change='2021-12-14 06:48:26Z', queued=0ms, exec=0ms Daemon Status: corosync: active/enabled pacemaker: active/enabled pcsd: active/enabled I would really appreciate any input in this regard. Best regards, Faisal Sheikh

1 0

[tripleo] Initial plans around stable/wallaby branch on CentOS Stream 9
by Chandan Kumar 14 Dec '21

14 Dec '21

Hello, The tripleo-ci team is working on drafting the plans for bootstrapping tripleo stable/wallaby branch on CentOS Stream 9. During adding the support of CentOS Stream 9 for tripleo master, we have added lots of patches for example: * tripleo-common: https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%252… * tripleo-heat-templates: https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%252… * https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%252… Backporting these patches in chains for stable/wallaby, will create lots of merge conflicts (few of them are big changes) and might get messy. RDO wallaby DLRN builder bootstrap has also started. In order to avoid that, we are coming with following plan: - Pick the major change and backport that one and add all the remaining changes in that itself (not a clean backport): https://review.opendev.org/c/openstack/tripleo-common/+/821511 - Make sure these backported changes passed on CentOS-8 CI jobs - Once the RDO CS9 wallaby packages are available, Start bootstrapping the container and Image build job on CS9 via testproject. Let us know your thoughts around this. Thanks, Chandan Kumar

3 3

[openstack-helm] No Meetings Rest of 2021
by Gage Hugo 13 Dec '21

13 Dec '21

Hey team, Due to the upcoming holidays and the lack of topics for tomorrow's meeting the next 3 meetings are canceled. We will start back up in the new year on Jan 4th at the usual time. Happy Holidays!

1 0

[security][security sig] Retiring the security-specs repo
by Gage Hugo 13 Dec '21

13 Dec '21

Hey folks, The security SIG has been going through the current list of repositories that we are managing and one of them, the "security-specs"[0] repository, has been unused for several years now so the consensus was to retire the repo. If there are no objections, we will look to retire the repo here relatively soon. Should anyone have any other information about it, please let the security SIG know. Thanks! [0] https://github.com/openstack/security-specs

1 0

[nova] Next spec review day on Tuesday Dec 14th
by Sylvain Bauza 13 Dec '21

13 Dec '21

Hola, As agreed during today's Nova meeting, we will have another spec review day on Dec 14th. Please sharpen your pens and write your specs in advance, and just be around during this day if you want to discuss with the reviewers. Thanks, -Sylvain

1 1

[tempest][swift][kolla]
by Michal Arbet 13 Dec '21

13 Dec '21

Hello to eveyrone, Please, could someone help me with swift capabilities not working when I'm tempesting openstack test stack ? Tempest : rm -rf /tmp/tempest-lock/; refstack-client test -v -c /opt/tempest/tempest.conf -- --regex tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest (.venv) root@ca6353106d83:/opt/refstack-client# rm -rf /tmp/tempest-lock/; refstack-client test -v -c /opt/tempest/tempest.conf -- --regex tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest 2021-12-13 17:44:33.001 4358 INFO tempest [-] Using tempest config file /etc/tempest/tempest.conf 2021-12-13 17:44:33,839 refstack_client:518 INFO Starting Tempest test... 2021-12-13 17:44:33.839 4358 INFO refstack_client [-] Starting Tempest test... {0} setUpClass (tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest) [0.000000s] ... FAILED Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/opt/refstack-client/.tempest/tempest/test.py", line 181, in setUpClass raise value.with_traceback(trace) File "/opt/refstack-client/.tempest/tempest/test.py", line 174, in setUpClass cls.resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/test_account_quotas_negative.py", line 36, in resource_setup super(AccountQuotasNegativeTest, cls).resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/base.py", line 95, in resource_setup body = cls.capabilities_client.list_capabilities() File "/opt/refstack-client/.tempest/tempest/lib/services/object_storage/capabilities_client.py", line 32, in list_capabilities self._error_checker(resp, body) File "/opt/refstack-client/.tempest/tempest/lib/common/rest_client.py", line 799, in _error_checker raise exceptions.Unauthorized(resp_body, resp=resp) tempest.lib.exceptions.Unauthorized: Unauthorized Details: {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'} ============================== Failed 1 tests - output below: ============================== setUpClass (tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest) ---------------------------------------------------------------------------------------------- Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/opt/refstack-client/.tempest/tempest/test.py", line 181, in setUpClass raise value.with_traceback(trace) File "/opt/refstack-client/.tempest/tempest/test.py", line 174, in setUpClass cls.resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/test_account_quotas_negative.py", line 36, in resource_setup super(AccountQuotasNegativeTest, cls).resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/base.py", line 95, in resource_setup body = cls.capabilities_client.list_capabilities() File "/opt/refstack-client/.tempest/tempest/lib/services/object_storage/capabilities_client.py", line 32, in list_capabilities self._error_checker(resp, body) File "/opt/refstack-client/.tempest/tempest/lib/common/rest_client.py", line 799, in _error_checker raise exceptions.Unauthorized(resp_body, resp=resp) tempest.lib.exceptions.Unauthorized: Unauthorized Details: {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'} ====== Totals ====== Ran: 1 tests in 0.0000 sec. - Passed: 0 - Skipped: 0 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 1 Sum of execute time for each test: 0.0000 sec. ============== Worker Balance ============== - Worker 0 (1 tests) => 0:00:00 2021-12-13 17:44:43,144 refstack_client:581 INFO Tempest test complete. 2021-12-13 17:44:43.144 4358 INFO refstack_client [-] Tempest test complete. 2021-12-13 17:44:43,146 refstack_client:582 INFO Subunit results located in: /opt/refstack-client/.tempest/.stestr/137 2021-12-13 17:44:43.146 4358 INFO refstack_client [-] Subunit results located in: /opt/refstack-client/.tempest/.stestr/137 2021-12-13 17:44:43,148 refstack_client:585 INFO Number of passed tests: 0 2021-12-13 17:44:43.148 4358 INFO refstack_client [-] Number of passed tests: 0 2021-12-13 17:44:43,150 refstack_client:597 INFO JSON results saved in: /opt/refstack-client/.tempest/.stestr/137.json 2021-12-13 17:44:43.150 4358 INFO refstack_client [-] JSON results saved in: /opt/refstack-client/.tempest/.stestr/137.json TEMPEST LOG : Response - Headers: {'date': 'Mon, 13 Dec 2021 16:44:41 GMT', 'server': 'Apache', 'content-length': '8013', 'x-subject-token': '<omitted>', 'vary': 'X-Auth-Token', 'x-openstack-request-id': 'req-00b11c98-7ffa-4a1a-88b1-a054fda5d7e9', 'content-type': 'application/json', 'connection': 'close', 'status': '201', 'content-location': 'http://192.168.205.254:35357/v3/auth/tokens'} Body: b'{"token": {"methods": ["password"], "user": {"domain": {"id": "default", "name": "Default"}, "id": "23ebe05900764afaa29f72519d40693a", "name": "refstack", "password_expires_at": null}, "audit_ids": ["4UgDYqQoSla7SWJOdjHXng"], "expires_at": "2021-12-14T16:44:42.000000Z", "issued_at": "2021-12-13T16:44:42.000000Z", "project": {"domain": {"id": "default", "name": "Default"}, "id": "704cf29c27d045199d11a11fe62206b6", "name": "refstack"}, "is_domain": false, "roles": [{"id": "89125ace2bc945af8f12d889c9f5589b", "name": "_member_"}, {"id": "47da66772503466881afc1ae391141e7", "name": "swiftoperator"}, {"id": "e47f85a3982f4a18a44d24d6c2ed6588", "name": "ResellerAdmin"}], "catalog": [{"endpoints": [{"id": "27daafd92ace480da6cf0fcaf4c054d7", "interface": "internal", "region_id": "RegionOne", "url": "http://192.168.205.254:8000/v1", "region": "RegionOne"}, {"id": "8ffc139d5a6c4d86b06557b01956dcb7", "interface": "admin", "region_id": "RegionOne", "url": " http://192.168.205.254:8000/v1", "region": "RegionOne"}, {"id": "e4b48ef6f9cd4bbea5f2e0fb9bf16af1", "interface": "public", "region_id": "RegionOne", "url": "https://api.refstack.ultimum.cloud:8000/v1", "region": "RegionOne"}], "id": "10b7ca67118d45dca197b8ac17f29349", "type": "cloudformation", "name": "heat-cfn"}, {"endpoints": [{"id": "06788107c3d94af9976b9fb4b3011d4f", "interface": "public", "region_id": "RegionOne", "url": "https://api.refstack.ultimum.cloud:5000", "region": "RegionOne"}, {"id": "0d745366b77546f7bd24259c04810b8b", "interface": "internal", "region_id": "RegionOne", "url": "http://192.168.205.254:5000", "region": "RegionOne"}, {"id": "1771c125743b4485b818a2aaa4d6f913", "interface": "admin", "region_id": "RegionOne", "url": " http://192.168.205.254:35357", "region": "RegionOne"}], "id": "1ee3179487894931a223ed3caaf8cdb5", "type": "identity", "name": "keystone"}, {"endpoints": [{"id": "1ce9a0af0c14454aa6043b5efe32dddb", "interface": "internal", "region_id": "RegionOne", "url": " http://192.168.205.254:9001", "region": "RegionOne"}, {"id": "5bcfbaa0af46423ab3de1e789affa187", "interface": "admin", "region_id": "RegionOne", "url": "http://192.168.205.254:9001", "region": "RegionOne"}, {"id": "cbc613e8806a48ac98cf4cc42cca80f2", "interface": "public", "region_id": "RegionOne", "url": "https://api.refstack.ultimum.cloud:9001", "region": "RegionOne"}], "id": "493ace4e817d4eae9aa4a1341bd01046", "type": "dns", "name": "designate"}, {"endpoints": [{"id": "18bea710b4284f5387081eac6833dc9e", "interface": "public", "region_id": "RegionOne", "url": " https://api.refstack.ultimum.cloud:8774/v2/704cf29c27d045199d11a11fe62206b6", "region": "RegionOne"}, {"id": "7f1bd52d8b154bc7973c0f32c57103f9", "interface": "internal", "region_id": "RegionOne", "url": " http://192.168.205.254:8774/v2/704cf29c27d045199d11a11fe62206b6", "region": "RegionOne"}, {"id": "c28543c29f574cc6b4320fba45394a83", "interface": "admin", "region_id": "RegionOne", "url": " http://192.168.205.254:8774/v2/704cf29c27d045199d11a11fe62206b6", "region": "RegionOne"}], "id": "52d1f52dc8f44e5ba7a40732a660a288", "type": "compute_legacy", "name": "nova_legacy"}, {"endpoints": [{"id": "33d722f6c2cf4865b3487b8c4ce96c14", "interface": "admin", "region_id": "RegionOne", "url": "http://192.168.205.254:9696", "region": "RegionOne"}, {"id": "4744e2aa77cb4ba186752fb0ef25e9d3", "interface": "internal", "region_id": "RegionOne", "url": "http://192.168.205.254:9696", "region": "RegionOne"}, {"id": "4a980da3677c429ebf645a0e1733949c", "interface": "public", "region_id": "RegionOne", "url": " https://api.refstack.ultimum.cloud:9696", "region": "RegionOne"}], "id": "56866ea275ec4f5e8f805a08f040c8e0", "type": "network", "name": "neutron"}, {"endpoints": [{"id": "4550e2b070aa4bd6a07ab00d72ef4266", "interface": "admin", "region_id": "RegionOne", "url": "http://192.168.205.254:8780", "region": "RegionOne"}, {"id": "86fc799751384f709c450db05d523d93", "interface": "public", "region_id": "RegionOne", "url": " https://api.refstack.ultimum.cloud:8780", "region": "RegionOne"}, {"id": "bfb36483e5dc40a5bfbf1b4ae6bf60cb", "interface": "internal", "region_id": _log_request_full /opt/refstack-client/.tempest/tempest/lib/common/rest_client.py:450 2021-12-13 17:44:42.789 4369 INFO tempest.lib.common.rest_client [req-4ee89585-59ff-4f5a-8ba3-9eebb1d5e6aa ] Request (AccountQuotasNegativeTest:setUpClass): 201 POST http://192.168.205.254:35357/v3/auth/tokens 0.548s 2021-12-13 17:44:42.790 4369 DEBUG tempest.lib.common.rest_client [req-4ee89585-59ff-4f5a-8ba3-9eebb1d5e6aa ] Request - Headers: {'Content-Type': 'application/json', 'Accept': 'application/json'} Body: <omitted> Response - Headers: {'date': 'Mon, 13 Dec 2021 16:44:42 GMT', 'server': 'Apache', 'content-length': '8015', 'x-subject-token': '<omitted>', 'vary': 'X-Auth-Token', 'x-openstack-request-id': 'req-4ee89585-59ff-4f5a-8ba3-9eebb1d5e6aa', 'content-type': 'application/json', 'connection': 'close', 'status': '201', 'content-location': 'http://192.168.205.254:35357/v3/auth/tokens'} Body: b'{"token": {"methods": ["password"], "user": {"domain": {"id": "default", "name": "Default"}, "id": "adcde758a0d5439ba6f8a1a35d641726", "name": "refstack2", "password_expires_at": null}, "audit_ids": ["0clvtk_FQQWVN-RRLSkCWg"], "expires_at": "2021-12-14T16:44:42.000000Z", "issued_at": "2021-12-13T16:44:42.000000Z", "project": {"domain": {"id": "default", "name": "Default"}, "id": "2aabe1b9860c44a08eabdc3133538089", "name": "refstack2"}, "is_domain": false, "roles": [{"id": "e47f85a3982f4a18a44d24d6c2ed6588", "name": "ResellerAdmin"}, {"id": "47da66772503466881afc1ae391141e7", "name": "swiftoperator"}, {"id": "89125ace2bc945af8f12d889c9f5589b", "name": "_member_"}], "catalog": [{"endpoints": [{"id": "27daafd92ace480da6cf0fcaf4c054d7", "interface": "internal", "region_id": "RegionOne", "url": "http://192.168.205.254:8000/v1", "region": "RegionOne"}, {"id": "8ffc139d5a6c4d86b06557b01956dcb7", "interface": "admin", "region_id": "RegionOne", "url": " http://192.168.205.254:8000/v1", "region": "RegionOne"}, {"id": "e4b48ef6f9cd4bbea5f2e0fb9bf16af1", "interface": "public", "region_id": "RegionOne", "url": "https://api.refstack.ultimum.cloud:8000/v1", "region": "RegionOne"}], "id": "10b7ca67118d45dca197b8ac17f29349", "type": "cloudformation", "name": "heat-cfn"}, {"endpoints": [{"id": "06788107c3d94af9976b9fb4b3011d4f", "interface": "public", "region_id": "RegionOne", "url": "https://api.refstack.ultimum.cloud:5000", "region": "RegionOne"}, {"id": "0d745366b77546f7bd24259c04810b8b", "interface": "internal", "region_id": "RegionOne", "url": "http://192.168.205.254:5000", "region": "RegionOne"}, {"id": "1771c125743b4485b818a2aaa4d6f913", "interface": "admin", "region_id": "RegionOne", "url": " http://192.168.205.254:35357", "region": "RegionOne"}], "id": "1ee3179487894931a223ed3caaf8cdb5", "type": "identity", "name": "keystone"}, {"endpoints": [{"id": "1ce9a0af0c14454aa6043b5efe32dddb", "interface": "internal", "region_id": "RegionOne", "url": " http://192.168.205.254:9001", "region": "RegionOne"}, {"id": "5bcfbaa0af46423ab3de1e789affa187", "interface": "admin", "region_id": "RegionOne", "url": "http://192.168.205.254:9001", "region": "RegionOne"}, {"id": "cbc613e8806a48ac98cf4cc42cca80f2", "interface": "public", "region_id": "RegionOne", "url": "https://api.refstack.ultimum.cloud:9001", "region": "RegionOne"}], "id": "493ace4e817d4eae9aa4a1341bd01046", "type": "dns", "name": "designate"}, {"endpoints": [{"id": "18bea710b4284f5387081eac6833dc9e", "interface": "public", "region_id": "RegionOne", "url": " https://api.refstack.ultimum.cloud:8774/v2/2aabe1b9860c44a08eabdc3133538089", "region": "RegionOne"}, {"id": "7f1bd52d8b154bc7973c0f32c57103f9", "interface": "internal", "region_id": "RegionOne", "url": " http://192.168.205.254:8774/v2/2aabe1b9860c44a08eabdc3133538089", "region": "RegionOne"}, {"id": "c28543c29f574cc6b4320fba45394a83", "interface": "admin", "region_id": "RegionOne", "url": " http://192.168.205.254:8774/v2/2aabe1b9860c44a08eabdc3133538089", "region": "RegionOne"}], "id": "52d1f52dc8f44e5ba7a40732a660a288", "type": "compute_legacy", "name": "nova_legacy"}, {"endpoints": [{"id": "33d722f6c2cf4865b3487b8c4ce96c14", "interface": "admin", "region_id": "RegionOne", "url": "http://192.168.205.254:9696", "region": "RegionOne"}, {"id": "4744e2aa77cb4ba186752fb0ef25e9d3", "interface": "internal", "region_id": "RegionOne", "url": "http://192.168.205.254:9696", "region": "RegionOne"}, {"id": "4a980da3677c429ebf645a0e1733949c", "interface": "public", "region_id": "RegionOne", "url": " https://api.refstack.ultimum.cloud:9696", "region": "RegionOne"}], "id": "56866ea275ec4f5e8f805a08f040c8e0", "type": "network", "name": "neutron"}, {"endpoints": [{"id": "4550e2b070aa4bd6a07ab00d72ef4266", "interface": "admin", "region_id": "RegionOne", "url": "http://192.168.205.254:8780", "region": "RegionOne"}, {"id": "86fc799751384f709c450db05d523d93", "interface": "public", "region_id": "RegionOne", "url": " https://api.refstack.ultimum.cloud:8780", "region": "RegionOne"}, {"id": "bfb36483e5dc40a5bfbf1b4ae6bf60cb", "interface": "internal", "region_id _log_request_full /opt/refstack-client/.tempest/tempest/lib/common/rest_client.py:450 2021-12-13 17:44:42.849 4369 INFO tempest.lib.common.rest_client [tx815e181e33fb4854b2631-0061b7787a ] Request (AccountQuotasNegativeTest:setUpClass): 401 GET https://api.refstack.ultimum.cloud:8080/info 0.049s 2021-12-13 17:44:42.849 4369 DEBUG tempest.lib.common.rest_client [tx815e181e33fb4854b2631-0061b7787a ] Request - Headers: {'Content-Type': 'application/json', 'Accept': 'application/json'} Body: None Response - Headers: {'content-type': 'application/json', 'content-length': '114', 'www-authenticate': 'Keystone uri=" http://192.168.205.254:5000"', 'x-trans-id': 'tx815e181e33fb4854b2631-0061b7787a', 'x-openstack-request-id': 'tx815e181e33fb4854b2631-0061b7787a', 'date': 'Mon, 13 Dec 2021 16:44:42 GMT', 'connection': 'close', 'status': '401', 'content-location': ' https://api.refstack.ultimum.cloud:8080/info'} Body: b'{"error": {"code": 401, "title": "Unauthorized", "message": "The request you have made requires authentication."}}' _log_request_full /opt/refstack-client/.tempest/tempest/lib/common/rest_client.py:450 Test from command line and from curl . /etc/kolla/refstack.sh ; curl -H "X-Auth-Token: $(openstack token issue -f value -c id)" https://api.refstack.ultimum.cloud:8080/info /usr/lib/python3/dist-packages/secretstorage/dhcrypto.py:15: CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead from cryptography.utils import int_from_bytes /usr/lib/python3/dist-packages/secretstorage/util.py:19: CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead from cryptography.utils import int_from_bytes {"swift": {"version": "2.27.1.dev9", "strict_cors_mode": true, "policies": [{"name": "Policy-0", "aliases": "Policy-0", "default": true}], "allow_account_management": true, "account_autocreate": true, "max_file_size": 5368709122, "max_meta_name_length": 128, "max_meta_value_length": 256, "max_meta_count": 90, "max_meta_overall_size": 4096, "max_header_size": 8192, "max_object_name_length": 1024, "container_listing_limit": 10000, "account_listing_limit": 10000, "max_account_name_length": 256, "max_container_name_length": 256, "extra_header_count": 0}, "container_sync": {"realms": {}}, "bulk_upload": {"max_containers_per_extraction": 10000, "max_failed_extractions": 1000}, "bulk_delete": {"max_deletes_per_request": 10000, "max_failed_deletes": 1000}, "tempurl": {"methods": ["GET", "HEAD", "PUT", "POST", "DELETE"], "incoming_remove_headers": ["x-timestamp"], "incoming_allow_headers": [], "outgoing_remove_headers": ["x-object-meta-*"], "outgoing_allow_headers": ["x-object-meta-public-*"], "allowed_digests": ["sha1", "sha256", "sha512"]}, "ratelimit": {"account_ratelimit": 0.0, "max_sleep_time_seconds": 60.0, "container_ratelimits": [], "container_listing_ratelimits": []}, "container_quotas": {}, "account_quotas": {}, "slo": {"max_manifest_segments": 1000, "max_manifest_size": 8388608, "yield_frequency": 10, "min_segment_size": 1, "allow_async_delete": false}} Swiftclient : ubuntu@deploy:/opt/kolla-ansible$ . /etc/kolla/refstack.sh ; swift --os-auth-url http://192.168.205.254:5000/v3 --auth-version 3 --os-project-name refstack --os-project-domain-name default --os-username refstack --os-user-domain-name default --os-password refstack capabilities /usr/lib/python3/dist-packages/secretstorage/dhcrypto.py:15: CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead from cryptography.utils import int_from_bytes /usr/lib/python3/dist-packages/secretstorage/util.py:19: CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead from cryptography.utils import int_from_bytes Capabilities GET failed: http://192.168.205.254:8080/info 401 Unauthorized [first 60 chars of response] b'{"error": {"code": 401, "title": "Unauthorized", "message": ' Failed Transaction ID: txc1d8607e26eb4cd587459-0061b7791b It looks like swift client is broken, isn't it ? Thank you very much, Kevko Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet(a)ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline>

1 0

Is heat-cfntools still an active project?
by Thomas Goirand 13 Dec '21

13 Dec '21

Hi, The last release of heat-cfntools was in 2016, and in Debian, we're considering removing removing boto (as boto is unmaintained upstream, replaced by boto3). If nobody does anything, we may remove both boto and heat-cfntools from Debian. Thoughts anyone? Cheers, Thomas Goirand (zigo)

2 1

[CLOUDKITTY] Missed CloudKitty meeting today
by Rafael Weingärtner 13 Dec '21

13 Dec '21

Hello guys, I would like to apologize for missing the CloudKitty meeting today. I was concentrating on some work, and my alarm for the meeting did not ring. Isee that you guys already merged some things, thanks for picking the meeting up. I will add more alarms in my calendar, to avoid this situation in the future. If you need something, just let me know. Again, sorry for the inconvenience; see you guys at our next meeting. -- Rafael Weingärtner

1 0

[Triple0][Undercloud ] Deployment failed because of Bonds
by Lokendra Rathour 13 Dec '21

13 Dec '21

Hi Team, we have created a bond with name bond-mgmt for the provisioning n/w and passed that name as local interface: Undercloud.conf: *..* *..* *# Network interface on the Undercloud that will be handling the PXE* *# boots and DHCP for Overcloud instances. (string value)* *local_interface = bond-mgmt* *..* *..* Because of this undercloud deployment is getting failed with the error as below: [root@localhost ~]# ovs-vsctl show b3db7071-58f7-4201-8fd5-9577dec0020e Bridge br-ctlplane fail_mode: standalone Port bond-mgmt Interface bond-mgmt error: "could not open network device bond-mgmt (No such device)" Port br-ctlplane Interface br-ctlplane type: internal ovs_version: "2.12.0" [root@localhost ~]# Query: - is bonding supported in Undercloud installation for provisioning n/w? - if yes then what is the correct way to do so. we are trying to deploy Train on Centos 8. -- ~ Lokendra skype: lokendrarathour

2 5

[nova][cinder][devstack][qa] ceph installs python3-logutils which conflicts with neutron
by Sean Mooney 13 Dec '21

13 Dec '21

hi o/ gibi noticed that the nova-ceph-multistore job started failing this morning with ERROR: Cannot uninstall 'logutils'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall. https://bugs.launchpad.net/nova/+bug/1954427 we quickly identifed that python3-logutils was beeing pulled in by the devstack-plugin-ceph as a sideeffect fo installing ceph. functions-common:apt_get:1207 : sudo DEBIAN_FRONTEND=noninteractive http_proxy= https_proxy= no_proxy= apt-get --option Dpkg::Options::=--force-confold --assume-yes install ceph libnss3- tools python3-rados python3-rbd Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: libboost-iostreams1.71.0 libboost-thread1.71.0 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ceph-base ceph-common ceph-mgr ceph-mgr-modules-core ceph-mon ceph-osd libbabeltrace1 libcephfs2 libdw1 libgoogle-perftools4 libjaeger libleveldb1d liblttng-ust-ctl4 liblttng-ust0 libnuma1 liboath0 librabbitmq4 librados2 libradosstriper1 librbd1 librdkafka1 librgw2 libsnappy1v5 libtcmalloc-minimal4 liburcu6 logrotate python-pastedeploy-tpl python3-bcrypt python3-bs4 python3-ceph-argparse python3-ceph-common python3-cephfs python3-cffi-backend python3-cherrypy3 python3-cryptography python3-dateutil python3-jwt python3-logutils python3-mako python3-markupsafe python3-openssl python3-paste python3-pastedeploy python3-pecan python3-prettytable python3-rgw python3-simplegeneric python3-singledispatch python3-soupsieve python3-tempita python3-waitress python3-webob python3-webtest python3-werkzeug to adress this i have proposed a patch based on how we workaround unremovable python packages in devstack fixup_tools script too the devstack-plugin-ceph repo to adress this. https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/821396/ untill that merges expect to see all ceph based jobs to fail when installing neutron. regards sean

2 1

[CLOUDKITTY][VICTORIA] - policy prohibit report:get_summary to admin
by Gaël THEROND 13 Dec '21

13 Dec '21

Hi everyone! Today I faced a weird situation with one of our cloud platforms using victoria release. When trying to get a summary of projects rates would it be through Horizon or CLI using the admin user of the platform we've got the following error message: https://paste.opendev.org/show/bIgG6owrN9B2F3O7iqYG/ >From my understanding of the default policies of cloudkitty, this error seems to be a bit odd as the admin user profile actually match the default rules. At least as exposed in: https://opendev.org/openstack/cloudkitty/src/branch/stable/victoria/cloudki… and https://opendev.org/openstack/cloudkitty/src/branch/stable/victoria/cloudki… Unless I misunderstood something (please correct me if I'm wrong), it's supposed to at least be ok with the matching.

3 7

[nova] How to update OS-EXT-SRV-ATTR:hostname
by Kamil Madáč 13 Dec '21

13 Dec '21

Hello, I would like to ask, how to update OS-EXT-SRV-ATTR:hostname via openstack CLI? We changed hostnames on bunch of instances, but metadata service still serves old hostname which causes that every future rebuild of instance reverts hostname (`hostname` command in instance console) back to old one. Kamil Madáč Slovensko IT a.s.

3 4

[Triple0] Overcloud Deployment Network Queries
by Lokendra Rathour 13 Dec '21

13 Dec '21

Hi Team, As we are trying to deploy Triple0, regarding this we have the following queries: 1. On the Overcloud machine, I have four NICs available so is there a way to bind a particular NIC to a physnet. 1. Also, can we create multiple physnet, one being flat and the other being VLAN, binded with two different NICs respectively? 2. We have created a local registry during Undercloud installation on Undercloud, What is the way to configure local registry images for overcloud deployment? -- ~ Lokendra skype: lokendrarathour

1 0

[Interop] No WG meeting on Dec 23 and 30.
by Arkady Kanevsky 11 Dec '21

11 Dec '21

Happy holidays. -- Arkady Kanevsky, Ph.D. Phone: 972 707-6456 Corporate Phone: 919 729-5744 ext. 8176456

3 2

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

10 Dec '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * TC this week IRC meeting held on Oct 14th Thursday. * Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @ - https://meetings.opendev.org/meetings/tc/2021/tc.2021-10-14-15.00.log.html * Next week's meeting is cancelled as we are meeting in PTG. We will have the next IRC meeting on Oct 28th, Thursday 15:00 UTC, feel free the topic on agenda[1] by Oct 27th. 2. What we completed this week: ========================= * None in this week. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ * TC is using the etherpad[2] for Xena cycle working item. We will be checking it in PTG * Current status is: 9 completed, 3 to-be-discussed in PTG, 1 in-progress Open Reviews ----------------- * Six open reviews for ongoing activities[3]. New project 'Skyline' proposal ------------------------------------ * You might be aware of this new dashboard proposal in the previous month's discussion. * A new project 'Skyline: an OpenStack dashboard optimized by UI and UE' is now proposed in governance to be an official OpenStack project[4]. * Skyline team is planning to meet in PTG on Tue, Wed and Thu at 5UTC, please ask your queries or have feedback/discussion with the team next week. Place to maintain the external hosted ELK, E-R, O-H services ------------------------------------------------------------------------- * We had a final discussion or I will say just a status update on this which was mentioned in last week's email summary[5]. * Now onwards, discussion and migration work will be done in TACT SIG (#openstack-infra IRC channel). Add project health check tool ----------------------------------- * No updates on this, we will continue discussing it in PTG for the next steps on this and what to do with TC liaison things. * Meanwhile, we are reviewing Rico proposal on collecting stats tools [6]. Stable Core team process change --------------------------------------- * Current proposal is under review[7]. Feel free to provide early feedback if you have any. Call for 'Technical Writing' SIG Chair/Maintainers ---------------------------------------------------------- * As agreed in last week's TC meeting, we will be moving this SIG work towards TC. * TC members have been added to the core members list in the SIG repos. * We will be discussing where to move the training repos/work in PTG. TC tags analysis ------------------- * Operator feedback is asked on open infra newsletter too, and we will continue the discussion in PTG and will take the final decision based on feedback we receive, if any[9]. Complete the policy pop up team ---------------------------------------- * Policy pop team has served its purpose and we have new RBAC as one of the the community-wide goal for the Yoga cycle. * We are marking this popup team as completed[10]. Project updates ------------------- * Retiring js-openstack-lib [11] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [12]. * Current status: "Secure RBAC" is selected for Yoga cycle[13]. PTG planning ---------------- * We will be meeting in PTG next week, please check the details in this etherpad [14] * Do not forget to join the TC+community leaders sessions on Monday, Oct 18 15 UTC - 17 UTC. Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[15], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [18] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/tc-xena-tracke [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://review.opendev.org/c/openstack/governance/+/814037 [5]http://lists.openstack.org/pipermail/openstack-discuss/2021-October/02525… [6] https://review.opendev.org/c/openstack/governance/+/810037 [7] https://review.opendev.org/c/openstack/governance/+/810721 [9] https://governance.openstack.org/tc/reference/tags/index.html [10] https://review.opendev.org/c/openstack/governance/+/814186 [11] https://review.opendev.org/c/openstack/governance/+/798540 [12] https://review.opendev.org/c/openstack/governance/+/807163 [13] https://etherpad.opendev.org/p/y-series-goals [14] https://etherpad.opendev.org/p/tc-yoga-ptg [15] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [18] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

9 25

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

10 Dec '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @ https://meetings.opendev.org/meetings/tc/2021/tc.2021-12-09-15.00.log.html * Next week's meeting is on IRC on 16th Dec, Thursday 15:00 UTC, feel free the topic on the agenda[1] by 15th Dec. 2. What we completed this week: ========================= * 'Consistent and Secure Default RBAC' is selected as community-wide goal [2] * Add NVidia vGPU plugin charm to OpenStack charms[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. Open Reviews ----------------- * 5 open reviews for ongoing activities[5]. OpenStack Pain points discussion ---------------------------------------- We had a separate video call on Wed 8th Dec and discussed four projects' pain points[6] and also added the tag to categorize them. Details are sent by Rico in a separate email[7] and we will continue the discussion in Jan. Stay tuned on that ML thread to know the next meeting details. Skyline as an official project --------------------------------- Discussion going on in ML thread[8] regarding the things/improvement to do in Skyline project for various things to make it consistent with other OpenStack projects. Skyline team has confirmed to work on all those points on the governance patch[9] which is under review by TC. TC position on release cadence ------------------------------------- Discussion is in-progress in ML thread[10]. No other updates from TC on this and we will set up a separate call to continue the discussion sometime in Jan (after the Christmas holidays). Yoga testing runtime ------------------------- Governance patch is up for review on keeping python3.6 support in Yoga[11] Fixing Zuul config error -------------------------- If your project is listed in zuul config error, please start planning to fix those[12] Community-wide goal updates ------------------------------------ You might have seen my email[13] about goal status and planning the work, below is the current status: * Selected (active) goals[14]: ** Migrate from oslo.rootwrap to oslo.privsep ** Consistent and Secure Default RBAC * Goal proposal under review: ** FIPS compatibility and compliance [15]. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[16]. Project updates ------------------- * Retire js-openstack-lib [17] 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[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [19] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [3] https://review.opendev.org/c/openstack/governance/+/819856 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://etherpad.opendev.org/p/pain-point-elimination [7] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [8] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026206… [9] https://review.opendev.org/c/openstack/governance/+/814037 [10] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [11] https://review.opendev.org/c/openstack/governance/+/820195 [12] https://etherpad.opendev.org/p/zuul-config-error-openstack [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026218… [14] https://governance.openstack.org/tc/goals/selected/index.html [15] https://review.opendev.org/c/openstack/governance/+/816587 [16] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [17] https://review.opendev.org/c/openstack/governance/+/798540 [18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Force specific Region for resource creation
by Ryan Bannon 09 Dec '21

09 Dec '21

Hello all, Question: is there any way to associate a Region to a Project? Would this require custom code/development in OpenStack? (By my understanding, a Project lives outside the concept of a Region, and resources associated with a Project can target any Region.) Tx, Ryan

1 0

[neutron] Drivers meeting - Friday 10.12.2021 - cancelled
by Lajos Katona 09 Dec '21

09 Dec '21

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. We have only one RFE from last week: https://bugs.launchpad.net/neutron/+bug/1953170 ([RFE] Unify quota engine API) but we discussed that last week (see [0]). See You on the meeting next week. [0]: https://meetings.opendev.org/meetings/neutron_drivers/2021/neutron_drivers.… Lajos Katona (lajoskatona)

1 0

[mistral] How to import openstack actions from mistral-extra
by Oleksandr Mykhalskyi 09 Dec '21

09 Dec '21

Hello, In release Pike, I was able to import openstack actions to mistral DB using "mistral-db-manage --config-file /etc/mistral/mistral.conf populate" As I understood, from release Ussuri, all openstack actions were moved to separate mistral-extra library. But it`s unclear, how to import openstack actions to DB now. Command "mistral-db-manage populate" creates only few std* actions. I didn`t find any info in mistral documentation https://docs.openstack.org/mistral/latest/user/index.html about these changes. In https://github.com/openstack/mistral-extra also there is no useful readme. Can you please clarify, how to work with mistral-extra library and openstack actions in latest openstack releases? Thank you! Oleksandr Mykhalskyi, System Engineer, IT Servers and Services, LAUT Netcracker Technology +38 (044) 238-8727 ext 6404 | office ________________________________ The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

1 0

RE: [ops] [kolla] RabbitMQ High Availability
by Braden, Albert 09 Dec '21

09 Dec '21

I read this with great interest because we are seeing this issue. Questions: 1. We are running kola-ansible Train, and our RMQ version is 3.7.23. Should we be upgrading our Train clusters to use 3.8.x? 2. Document [2] recommends policy '^(?!(amq\.)|(.*_fanout_)|(reply_)).*'. I don't see this in our ansible playbooks, nor in any of the config files in the RMQ container. What would this look like in Ansible, and what should the resulting container config look like? 3. It appears that we are not setting "amqp_durable_queues = True". What does this setting look like in Ansible, and what file does it go into? Does anyone have a sample set of RMQ config files that they can share? It looks like my Outlook has ruined the link; reposting: [2] https://wiki.openstack.org/wiki/Large_Scale_Configuration_Rabbit -----Original Message----- From: Arnaud Morin <arnaud.morin(a)gmail.com> Sent: Monday, November 29, 2021 2:04 PM To: Bogdan Dobrelya <bdobreli(a)redhat.com> Cc: DHilsbos(a)performair.com; openstack-discuss(a)lists.openstack.org Subject: [EXTERNAL] Re: [ops]RabbitMQ High Availability Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, After a talk on this ml (which starts at [1]), we endup building a documentation with Large Scale group. The doc is accessible at [2]. Hope this will help. [1] http://secure-web.cisco.com/1gFccuTyEVGnFd9aBOZ-RTPG0hbVIPGAbuLBNnoXP4onSZG… [2] https://secure-web.cisco.com/1OtQ3pcnPPBNwevAFxS8yOS2xFlkHo0tY4SmkFE-wpAU_Y… On 24.11.21 - 11:31, Bogdan Dobrelya wrote: > On 11/24/21 12:34 AM, DHilsbos(a)performair.com wrote: > > All; > > > > In the time I've been part of this mailing list, the subject of RabbitMQ high availability has come up several times, and each time specific recommendations for both Rabbit and Open Stack are provided. I remember it being an A or B kind of recommendation (i.e. configure Rabbit like A1, and Open Stack like A2, OR configure Rabbit like B1, and Open Stack like B2). > > There is no special recommendations for rabbitmq setup for openstack, > but probably a few, like instead of putting it behind a haproxy, or the > like, list the rabbit cluster nodes in the oslo messaging config > settings directly. Also, it seems that durable queues makes a very > little sense for highly ephemeral RPC calls, just by design. I would > also add that the raft quorum queues feature of rabbitmq >=3.18 does > neither fit well into the oslo messaging design for RPC calls. > > A discussable and highly opinionated thing is also configuring > ha/mirror queue policy params for queues used for RPC calls vs > broad-casted notifications. > > And my biased personal humble recommendation is: use the upstream OCF RA > [0][1], if configuring rabbitmq cluster by pacemaker. > > [0] https://secure-web.cisco.com/1N1wD9gW7NZho0LdTVNuiU2ZIB7NW-eJMfDgVzBH3D3E6U… > > [1] > https://secure-web.cisco.com/1iDK1NnL9JTkQqkpBda06xTQNrWY2W0pVOTDwUoadfQbSX… > > > > > Unfortunately, I can't find the previous threads on this topic. > > > > Does anyone have this information, that they would care to share with me? > > > > Thank you, > > > > Dominic L. Hilsbos, MBA > > Vice President - Information Technology > > Perform Air International Inc. > > DHilsbos(a)PerformAir.com > > www.PerformAir.com > > > > > > > > > -- > Best regards, > Bogdan Dobrelya, > Irc #bogdando > >

5 4

Re: [ops] [kolla] RabbitMQ High Availability
by Bogdan Dobrelya 08 Dec '21

08 Dec '21

Please see inline >> I read this with great interest because we are seeing this issue. Questions: >> >> 1. We are running kola-ansible Train, and our RMQ version is 3.7.23. Should we be upgrading our Train clusters to use 3.8.x? >> 2. Document [2] recommends policy '^(?!(amq\.)|(.*_fanout_)|(reply_)).*'. I don't see this in our ansible playbooks, nor in any of the config files in the RMQ container. What would this look like in Ansible, and what should the resulting container config look like? >> 3. It appears that we are not setting "amqp_durable_queues = True". What does this setting look like in Ansible, and what file does it go into? > > Note that even having rabbit HA policies adjusted like that and its HA > replication factor [0] decreased (e.g. to a 2), there still might be > high churn caused by a large enough number of replicated durable RPC > topic queues. And that might cripple the cloud down with the incurred > I/O overhead because a durable queue requires all messages in it to be > persisted to a disk (for all the messaging cluster replicas) before they > are ack'ed by the broker. > > Given that said, Oslo messaging would likely require a more granular > control for topic exchanges and the durable queues flag - to tell it to > declare as durable only the most critical paths of a service. A single > config setting and a single control exchange per a service might be not > enough. Also note that therefore, amqp_durable_queue=True requires dedicated control exchanges configured for each service. Those that use 'openstack' as a default cannot turn the feature ON. Changing it to a service specific might also cause upgrade impact, as described in the topic [3]. [3] https://review.opendev.org/q/topic:scope-config-opts > > There are also race conditions with durable queues enabled, like [1]. A > solution could be where each service declare its own dedicated control > exchange with its own configuration. > > Finally, openstack components should add perhaps a *.next CI job to test > it with durable queues, like [2] > > [0] https://www.rabbitmq.com/ha.html#replication-factor > > [1] > https://zuul.opendev.org/t/openstack/build/aa514dd788f34cc1be3800e6d7dba0e8… > > [2] https://review.opendev.org/c/openstack/nova/+/820523 > >> >> Does anyone have a sample set of RMQ config files that they can share? >> >> It looks like my Outlook has ruined the link; reposting: >> [2] https://wiki.openstack.org/wiki/Large_Scale_Configuration_Rabbit > > > -- > Best regards, > Bogdan Dobrelya, > Irc #bogdando -- Best regards, Bogdan Dobrelya, Irc #bogdando

2 1

Swift Account Reaper Deletion Status
by Matthew Grinnell 08 Dec '21

08 Dec '21

Hello, I was curious about expected account-reaper behavior after deleting an account and if there is a way to be able to tell when all data for the account has been reaped. When I issue a delete on a swift account, I see subsequent HEAD requests on the account then return 410 Gone. Testing with debug logging I can see that after passing the delay_reaping time I see the reaper report my test object is deleted, HEAD requests against the account still return the same 410 Gone. Is there a way to tell when everything for an account has been purged, ie does the 410 return change at some point when that happens? Thanks, Matt

2 1

[all][tc] Technical Committee next weekly meeting on Dec 9th at 1500 UTC
by Ghanshyam Mann 08 Dec '21

08 Dec '21

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

1 1

[nova][placement] Cancelling Dec 21st and Dec 28th IRC meetings
by Sylvain Bauza 08 Dec '21

08 Dec '21

As we agreed on yesterday's meeting [1] we are about to cancel Dec 21st and Dec 28th meetings as we won't have a quorum for contributors during those weeks :-) -Sylvain [1] https://meetings.opendev.org/meetings/nova/2021/nova.2021-12-07-16.00.html

1 0

[Triple0] [Undercloud] Overcloud deployment getting failed at Introspection
by Lokendra Rathour 08 Dec '21

08 Dec '21

Hi Team, we are trying to deploy the triple0 Stein release on Centos 7. Undercloud is getting deployed successfully but the introspection of the overcloud node is getting failed with the reason as below: *on the DNS podman logs:* ()[root@undercloud dhcp-hostsdir]# tail -f /var/log/ironic-inspector/dnsmasq.log Dec 7 11:21:08 dnsmasq-dhcp[8]: DHCPDISCOVER(br-ctlplane) f8:f2:1e:9e:82:51 ignored Dec 7 11:21:08 dnsmasq-dhcp[8]: DHCPDISCOVER(br-ctlplane) f8:f2:1e:9e:82:50 ignored Dec 7 11:21:12 dnsmasq-dhcp[8]: DHCPDISCOVER(br-ctlplane) f8:f2:1e:9e:82:51 ignored *Checking the TCPDUMP at the same time gives:* 11:38:38.308660 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from f8:f2:1e:9e:82:51 (oui Unknown), length 300 11:38:38.435173 IP6 fe80::f53a:6448:4a29:e051 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 11:38:38.435184 IP6 fe80::f53a:6448:4a29:e051 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 11:38:41.155784 IP6 fe80::322d:3253:e3b2:316e > ff02::2: ICMP6, router solicitation, length 8 11:38:41.394304 IP6 fe80::f53a:6448:4a29:e051 > ff02::2: ICMP6, router solicitation, length 8 11:38:42.563182 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from f8:f2:1e:9e:82:50 (oui Unknown), length 300 11:38:42.611973 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from f8:f2:1e:9e:82:51 (oui Unknown), length 300 *We observed that DHCP Server is not offering the IP to the baremetal. * *DHCP discovery comes at br-ctlplane but no ip is offered.* Any input would be really helpful. Best Regards, Lokendra

2 3

[cinder] Bug deputy report for week of 12-08-2021
by Sofia Enriquez 08 Dec '21

08 Dec '21

This is a bug report from 11-24-2021 to 12-08-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1953168 ``Argument error in log message capacity filter". Assigned to caiquemello and Fix proposed. - https://bugs.launchpad.net/cinder/+bug/1952804 "cinder schedules backups on disabled backup services". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1953185 "[IBM Storwize] Restore VM snapshot issue with replication volumes". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1952927 "HPE 3PAR: migrating the vm attached with volume has been retyped will cause old volume to attach back again". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1952805 "[posix] cinder schedules incremental backups on the wrong node". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1952355 "[powerflex] Allocated capacity calculation doesn't work with powerflex driver". Unassigned. Low - https://bugs.launchpad.net/cinder/+bug/1953050 "A service should use a service specific control exchange for rpc". Fix proposed on master. *Quotas and more:* - https://bugs.launchpad.net/cinder/+bug/1952420 "Quota shows warnings on backup creation". Assigned to Gorka and Fix proposed. - https://bugs.launchpad.net/cinder/+bug/1952635 "When changing no_snapshot_gb_quota the gigabytes are wrong". Assigned to Gorka and Fix proposed. - https://bugs.launchpad.net/cinder/+bug/1952463 " Quota defaults and limits are not deleted when a volume type is deleted". Assigned to Gorka and Fix proposed. - https://bugs.launchpad.net/cinder/+bug/1952443 "Slow listings with many projects and deleted resources". Assigned to Gorka and Fix proposed. - https://bugs.launchpad.net/cinder/+bug/1952456 " Incorrect limit for private type volumes". Assigned to Gorka and Fix proposed. - https://bugs.launchpad.net/cinder/+bug/1952683 "Documentation typos". Fix proposed on master. Incomplete - https://bugs.launchpad.net/cinder/+bug/1952998 "[Ceph] Volume backup created with multiple snapshots preventing removal". Unassigned. Cheers -- 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

[ironic] [ops] RFC: deprecating instance network boot in Ironic
by Dmitry Tantsur 08 Dec '21

08 Dec '21

Hi folks, As discussed at the PTG, I'd like to collect thoughts about this proposal. I would like to deprecate support for network-booting **normal instances**. This does not concern the deployment process, ramdisk deploy or booting from volume! Historically, Ironic has been able to boot the final instances from network (or ISO in case of virtual media). This is no longer the recommended mode, except for the ramdisk deploy or boot-from-volume. It adds quite a bit of complexity to deploy interfaces and has one serious security implication: there is no way to update kernel/ramdisk once the instance is deployed (without rebuilding it). For this reason, I don't think anybody should use instance network booting in production. I would like to announce the deprecation in the Yoga cycle with the intention of removing the feature in Z. Then we can also get rid of the boot_option capability (which is not really a capability). Am I missing something? Any objections? Dmitry -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill

1 0

How to config vGPU in cyborg
by norman.kern 08 Dec '21

08 Dec '21

Hi guys, I want to config cyborg with kolla in openstack wallaby cluster, but I found that few docs can be found to config vGPU, Where can I find the details in configuration from openstack website? And I found another question, Cyborg can not config different types of vGPU for a pGPU. Waiting for you replies. Thanks.

1 0

[horizon] No Weekly meeting today
by vishal manchanda 07 Dec '21

07 Dec '21

Hello Team, Since there are no agenda items [1] to discuss for today's horizon weekly meeting. So let's cancel today's weekly meeting. Next weekly meeting will be on 15 December. Thanks & Regards, Vishal Manchanda [1] https://etherpad.opendev.org/p/horizon-release-priorities

1 0

[all][ptl][tc] Updates on Community wide goal: Current Active goals
by Ghanshyam Mann 07 Dec '21

07 Dec '21

Hello Everyone, You might know, TC has de-coupled the community-wide goals from the release cycle[1]. As per the new structure, community-wide goals are tied or have to be finished within the release cycle. Instead, it can have target dates which can be a particular cycle release date or multi-cycle or even in between a release cycle. Target dates will be selected by considering the amount of work needed and the community bandwidth. This will help to make sure the goal is ready to start and also continue working on the goal until work is completed. 'Secure RBAC' goal is one example of a new structure that has different milestones targeting the different set of work[2]. I think this will be helpful for PTLs and project teams to plan the active goals for their project. Current Selected (Active) Goals: ------------------------------------- We have two Selected/Active goals. The project team can start/continue working on: 1. Migrate from oslo.rootwrap to oslo.privsep [3]. This is contouring from the previous cycle. 2. Consistent and Secure Default RBAC [4]. New design/implementation details are finalized now, please read those and for any queries, plan to attend the policy popup team biweekly meeting[5]. [1] https://review.opendev.org/c/openstack/governance/+/816387 [2] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [3] https://governance.openstack.org/tc/goals/selected/migrate-to-privsep.html [4] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [5] https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… -gmann

1 0