September 2022 - openstack-discuss

[PTL][release] Zed Cycle Highlights
by Előd Illés 02 Sep '22

02 Sep '22

Hi, This is a reminder, that *this week* is the week for Cycle highlights [1][2]! They need to be added to deliverable yamls so that they can be included in release marketing preparations. (See the details about how to add them at the project team guide [3].) [1]https://releases.openstack.org/zed/schedule.html [2]https://releases.openstack.org/zed/schedule.html#z-cycle-highlights [3] https://docs.openstack.org/project-team-guide/release-management.html#cycle… Thanks, Előd Illés irc: elodilles

4 6

[release] Release countdown for week R-4, Sep 05 - 09
by Előd Illés 02 Sep '22

02 Sep '22

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

1 0

Kolla-ansible Openstack : Queries on Metering and Rating Module
by KK CHN 02 Sep '22

02 Sep '22

I have installed all-in-one using Kolla-ansible wallaby on a Virtual Machine (Debian 10) By default configurations up and running are able to create VMs .. with the default Cirros image. I want the Metering and Billing modules for a deployment scenario. So I used this setup as a PILOT and use ceilometer with cloudkitty and gnocchi.. I have enabled ( correct me If I am wrong or missing any other directives for metering and rating other than this if required => enable_ceilometer : "yes" enable_cloudkitty : "yes" enable_gnocchi : "yes" , enable_horizon_cloudkitty : "{{ enable_cloudkitty |bool }}" cloudkitty_collector_backend: "gnocchi" in /etc/kolla/globals.yml Then re deployed the all in one $ ( (venvopenstack) cloud@wallaby:~$ kolla-ansible -i ./all-in-one bootstrap-servers , (venvopenstack) cloud@Xena:~$ kolla-ansible -i ./all-in-one prechecks, (venvopenstack) cloud@Xena:~$ kolla-ansible -i ./all-in-one deploy ) .. All went well up and able to access horizon dashboard. How to view the metrics and ratings :: I am able to get Admin => Rating tab Enabled the three Rating Modules there. (Hashmap, noop, pyscripts) .. Rating Summary : I am getting as below All CloudTotal 0 LL <http://10.184.48.94/admin/rating_summary/ALL> Cloud Total <http://10.184.48.94/admin/rating_summary/ALL> 0 Hashmap and pyscrips tab nothing to view , its empty. How can I use this Rating module and how to get useful values there ? Or is there any other configurations I have to make to get a better metering and billing utility using these tools. Kindly share your tips and expertise with these tools. What / where to refer to get a nice Rating/metering configurations using these tools.( Or do I need to enable / configure more directives or resources ??) I have not seen a highly populated Rating Module interface in Horizon so it should be. Any reference images and configurations are most welcome. Thank you, Krish

3 5

[heat][elections] PTL Candidacy for Antelope Cycle
by Brendan Shephard 02 Sep '22

02 Sep '22

Hi all, I first wanted to thank Rico for his ongoing commitment to the project over the last cycles. He has provided lots of guidance and help to the Heat project for a long time and his contribution deserves recognition. I am proposing my candidacy for Heat PTL during the Antelope cycle. I have worked with the Heat project for several years both as a user and more recently over the last 2 years as a contributor. I see great potential in the project for our users and look forward to continuing work in order to support features and functionality of the project. Some of my objectives for the next few cycles are: Remove the dependencies on legacy python-*client libraries and instead shift to the openstacksdk client library. While the legacy libraries have served us well, they are starting to show their limitations and the delta in servicibilty will only increase as each project moves towards leveraging the openstacksdk. So this change, while quite extensive will ensure future compatibility with the other OpenStack project teams. Continue ensuring Heat supports the most up-to-date and recent features provided by each project. To ensure Heat is the default and best choice for our users, we need to ensure we are able to leverage the latest available features from the complimentary OpenStack projects. This is an ongoing challenge to stay up-to-date with the changes each cycle and work towards implementing them in Heat. Thank you all for you consideration, and I look forward to the next cycle and continuing to work with you all. Regards, Brendan

3 2

Unable to change the app-name / programname for barbican-api service
by Rohit Singh 02 Sep '22

02 Sep '22

Hi guys, I am facing issues with barbican-api logging with syslog. I have configured rsyslog for barbican service and want to write the logs on remote host based on %programname properties, But I observed that the barbican-api app-name is not set ,so by default it's logging into loadwsgi.py.log . Is there any way to set the app-name for barbican-api service ? Regards Rohit Singh Mob : +91- 88824 68891

1 0

Unable to change the app-name / programname for barbican-api service
by Rohit Kumar Singh 02 Sep '22

02 Sep '22

Hi guys, I am facing issues with barbican-api logging with syslog. I have configured rsyslog for barbican service and want to write the logs on remote host based on %programname properties, but i observed barbican-api app-name is not set ,so by default it's logging into loadwsgi.py.log . I s there any way to set the app-name for barbican-api service ?

1 0

[all][elections][tc] TC Election Non-Candidacy ...
by Jay Bryant 02 Sep '22

02 Sep '22

All, I wanted to take a moment to let everyone know that I am not going to be running for the TC, this time around. The last two years on the TC have been a great experience and I am grateful for the trust the community put in me. At this point, however, I think it is best to let others who may want to join the TC have the opportunity to do so. Again, thank you for this opportunity to support the community over the last couple of years! Sincerely, Jay Bryant (jungleboyj)

3 2

[manila] Feature freeze exceptions
by Carlos Silva 01 Sep '22

01 Sep '22

Hello, Zorillas and interested stackers! During today's Manila weekly meeting we went over the status of our open changes that are eligible for feature freeze. Some candidates for the deadline were successfully merged over the course of this week, but there are also a few other changes that are receiving feedback from reviewers. Those changes will need some extra time to get in. We are in a shortage of reviewers to take care of all of the changes at once, and we are extending the deadline by one week. The changes yet to be merged and receiving the feature freeze exception are: *Metadata for share snapshots [1]* During the Yoga cycle, Manila metadata APIs were changed to be more generic and be able to accommodate metadata for other resources. For Zed, we planned to have metadatas being added to the snapshot resources. This change has received some reviews and seems to be quite close to being merged. During the tests, the manipulation of metadata for share snapshots seems to work just fine, and we are only getting some final tweaks to the implementation. *Refactor the Ceph NFS driver to use Cephadm NFS [2]* This is a driver-only change and it does not impact the Manila core itself. It is important for people consuming the Ceph drivers, and does not impact the current driver implementation. *Support share transfer between project [3]* This change is currently under review and is a good addition to the Manila core. Due to the shortage of reviewers, we only got more people looking at the change and testing the functionality late in the cycle. The three changes aforementioned should be merged by next Thursday (08 september 2022). [1] https://review.opendev.org/c/openstack/manila/+/825008 [2] https://review.opendev.org/c/openstack/manila/+/848987 [3] https://review.opendev.org/c/openstack/manila/+/843832 In case you have questions or concerns, please let me know. Thank you, carloss

1 0

[all] [oslo.messaging] Interest in collaboration on a NATS driver
by Tobias Urdin 01 Sep '22

01 Sep '22

Hello everyone, Before continuing on, yes this kind of is a massive effort but it doesn’t have to be, it would be very cool to get a replacement for RabbitMQ as I’m probably not the only one not satisfied with it. I've proposed a very bare POC in [1] but it's long way from being finished, but atleast some basic devstack is passing. NATS [2] is a cloud-native scalable messaging system that supports the one-to-many and pub-sub methods that we can use to implement it as a oslo.messaging driver. This would make OpenStack easier to deploy in a highly available fashion, reduce outages related to RabbitMQ, free up memory and CPU usage by RabbitMQ (it’s insane when using clustering) and embrace a more cloud-native approach for our software that runs the cloud, alternatives is also welcome :) The POC has a lot of things that could be improved for example: • Do retries and acknowledgements in the library (since NATS does NOT persist messages like RabbitMQ could) • Handle reconnects or interruptions (for example resubscribe to topics etc) • Timeouts need to be implemented and handled • Investigate maximum message payload size • Find or maintain a NATS python library that doesn't use async like the official one does • Add a lot of testing • Cleanup everything noted as TODO in the POC code Now I couldn’t possibly pull this off myself without some collaboration with all of you, even though I’m very motivated to just dig in and do this for the rest of the year and migrate our test fleet there I unfortunately (like everyone else) is juggeling a lot of balls at the same time. If anybody, or any company, out there would be interested in collaborating in a project to bring this support and maintain it feel free to reach out. I’m hoping somebody will bite but atleast I’ve put it out there for all of you. Best regards Tobias [1] https://review.opendev.org/c/openstack/oslo.messaging/+/848338 [2] https://nats.io

4 7

[neutron] Drivers meeting - Friday 02.09.2022 - cancelled
by Lajos Katona 01 Sep '22

01 Sep '22

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

1 0