November 2022 - openstack-discuss

[Openstack][FOSDEM][CFP] Virtualization & IaaS Devroom
by Piotr Kliczewski 10 Nov '22

10 Nov '22

We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2023, to be hosted on February 4th 2023. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 10th, 2022. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors or virtual machine managers such as Xen Project, KVM, bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, 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 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: 10th December 2022 Acceptance notifications: 15th December 2022 Final schedule announcement: 20th December 2022 Devroom: First half of 4th February 2023 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 be recorded 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 FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Submission Guidelines Mentored presentations will have 25-minute slots, where 20 minutes will include the presentation and 5 minutes will be reserved for questions. The number of newcomer session slots is limited, so we will probably not be able to accept all applications. You must submit your talk and abstract to apply for the mentoring program, our mentors are volunteering their time and will happily provide feedback but won't write your presentation for you! 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. How to Apply In addition to agreeing to video recording and confirming that you can attend FOSDEM in case your session is accepted, please write "speaker mentoring program application" in the "Submission notes" field, and list any prior speaking experience or other relevant information for your application. 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 watching time for the speakers, and helping with video 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/FOSDEM17> https://penta.fosdem.org/submission/FOSDEM23 [2] iaas-virt-devroom at lists.fosdem.org

1 0

[ansible-openstack-modules] 2023.1 Antelope PTG summary
by Rafael Castillo 10 Nov '22

10 Nov '22

We held our ansible-collections-openstack PTG a few weeks ago. Thanks to everyone who participated! Here's a belated summary of the discussions that took place. Etherpad: https://etherpad.opendev.org/p/oct2022-ptg-os-ansible-modules The plan for the Antelope cycle is to continue our current course of porting all remaining modules to support the new SDK. Our tentative release date for 2.0.0 is January 1st 2023. While porting modules will be the priority first and foremost, we discussed some proposals for enhancement during our session. These will remain on the backburner and will be addressed on a best effort basis. # Proposals for improvement ## Consistent module naming In order to make the modules more self-describing, avoid prefixes like federation_idp and keep names obvious. Change module names to be consistent with openstack-client. Change return values to match module names where possible. ## Documentation updates Highlight in docs that module results can differ depending on the cloud they use. Our module docs are currently based on devstack. Keep different documentation pages on galaxy between stable and master, as the two differ quite a bit. Update README and docs folder with more current information. ## Migrate current tests to use ansible-test The ansible-test integration test runner has some nice features. There's examples of the OTC modules using this we can take a look at. ## Write sdk logs to module results instead of writing to file Can be more convenient to have logs available right in ansible output. Counter-point is that these logs grow to be huge sometimes. ## Drop pbr based installation? We should focus on supporting ansible-galaxy as the preferred method of installing ansible collections. Again, thanks for participating in the collections process. Have a good weekend.

1 0

[nova][placement] Happy Specs review day next Tuesday (Nov 15) !
by Sylvain Bauza 09 Nov '22

09 Nov '22

Hey, as said above, like every 6-month cycle, we'll have a specs review day to make sure we can jab the open specs. You are a reviewer (even not a core) ? Make sure you can review the specs on Nov 15th. You are a contributor and you have an open spec ? Make sure you can look at Gerrit during this day because you could see new comments and you could then rebase your spec for providing a new revision :) -Sylvain

1 0

Neutron : Routed Provider Networks (no subnets declared in compute placement API: consequences?)
by Andrew West 09 Nov '22

09 Nov '22

Hi neutron experts Have a cloud built with multiple network segments (RPN) . (kolla-ansible, openstack ussuri), things are running OK (on the network level): networks have DHCP agents ok (*os network agent list --agent-type dhcp --network $networkID* ) all network segments are listed in Host Aggregates BUT if I run through all the existing segments , NONE have a (compute service) inventory declared for each segment IPv4 subnet i.e *os resource provider inventory list $segmentID * returns no output. (official doc on RPN says this should exist) What feature may not function if this inventory is missing ? I don't quite understand what role this IPv4 subnet compute service inventory plays here (during placement? port declaration ?) thanks Andrew

2 1

[largescale-sig] Next meeting: Nov 9, 15utc
by Thierry Carrez 09 Nov '22

09 Nov '22

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. Note that most countries are no longer in DST! You should doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221109T15 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[oslo] Moving back oslo deliverables to the cycle with intermediary release model
by Herve Beraud 09 Nov '22

09 Nov '22

Hey Osloers, Months ago we moved a couple of oslo deliverables to the independent release model [1][2], however it led us to issues with backports [3]. Backports are not an option for those deliverables. During the previous release management team' PTG we discussed this topic and we decided [4] to move back the oslo deliverables to the cycle-with-intermediary model. You can follow the transition to the CWI model through this patch https://review.opendev.org/c/openstack/releases/+/864095 Do not hesitate to react directly to the patch. Thanks for your time. [1] https://lists.openstack.org/pipermail/openstack-discuss/2020-November/01852… [2] https://opendev.org/openstack/releases/commit/5ecb80c82ed3ab0144c8e5860ee62… [3] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0306… [4] https://etherpad.opendev.org/p/oct2022-ptg-rel-mgt -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

4 5

Need assistance
by Gk Gk 09 Nov '22

09 Nov '22

Hi All, I have a OSA setup. I am trying to trace the control flow of nova-api using pdb in the file "/openstack/venvs/nova-20.2.1/lib/python3.6/site-packages/nova/objects/instance.py". My goal is to trace the flow for "nova list --all" command. I am launching the nova-api service manually from the command line as follows: #/openstack/venvs/uwsgi-20.2.1-python3/bin/uwsgi --ini /etc/uwsgi/nova-api-os-compute.ini --workers 1 I am executing "nova list --all" command in another terminal. I have inserted pdb in instance.py as follows: ---- @base.remotable_classmethod def get_all(cls, context, expected_attrs=None): import pdb; pdb.set_trace() """Returns all instances on all nodes.""" db_instances = db.instance_get_all( context, columns_to_join=_expected_cols(expected_attrs)) return _make_instance_list(context, cls(), db_instances, expected_attrs) --- But when I fire the nova list --all command, I see no pdb prompt being shown in the nova-api window. Can anyone help me how to use the pdb to trace the flow of control for "nova list --all" command ? Thanks Kumar

3 3

[cinder] Bug report from 10-26-2022 to 11-08-2022
by Sofia Enriquez 09 Nov '22

09 Nov '22

This is a bug report from 10-26-2022 to 11-08-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1995204 "Fail to unify allocation_capacity_gb values among multiple Active-Active Cinder-Volume services ." Unassigned. - https://bugs.launchpad.net/python-cinderclient/+bug/1995883 "cinderclient against wallaby fails to create a snapshot." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1995863 "Failed to create multiple instances with boot volumes at the same time in version 20.0.2.dev11." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1996049 " Backup fails with VolumeNotFound but not set to error." Fix proposed to master. Incomplete - https://bugs.launchpad.net/cinder/+bug/1995838 "Reimage results are stuck in downloading state." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1996039 "Volume State Update Failed After Backup Completed." Assigned to wanghelin. Cheers, Sofia -- 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

[kolla] Weekly meeting 9th Nov 22 cancelled
by Michał Nasiadka 09 Nov '22

09 Nov '22

Hola Koalas, The weekly meeting today is cancelled (I’m on full day workshops) - let’s talk next week. Michal

1 0

(Openstack-Keystone)Regarding Authentication issue of one user while login to Open Stack using AD password
by Adivya Singh 09 Nov '22

09 Nov '22

Hi Team, There is one issue , where a user is getting " Authenticated Failure" all of a sudden, and this user is the only user who is facing this problem. I tried to disable and enable the project if, Check the logs but do not found anything related to Keystone authentication Delete the Project id and Create it again , Results are same , Any insights what i can do more to fix this issue Regards Adivya Singh

2 8