September 2022 - openstack-discuss

[adjutant][magnum][mistral][sahara][watcher][zaqar][tc] broken gate for deliverables
by Előd Illés 05 Sep '22

05 Sep '22

Hi, Now that we have passed Zed-3 milestone, Release team starts to check the health of deliverables via their gate healthiness. The 1st round of checks showed that the following deliverables seem to have blocked gates: python-adjutantclient [1] python-magnumclient [2] python-mistralclient [3] python-saharaclient [4] python-watcherclient [5] python-zaqarclient [6] We are asking the teams to fix their gates and propose a release after it is fixed as soon as possible, otherwise these deliverables might not be part of the official Zed release. [1] https://review.opendev.org/c/openstack/python-adjutantclient/+/855763 [2] https://review.opendev.org/c/openstack/python-magnumclient/+/855778 [3] https://review.opendev.org/c/openstack/python-mistralclient/+/855781 [4] https://review.opendev.org/c/openstack/python-zaqarclient/+/855796 [5] https://review.opendev.org/c/openstack/python-watcherclient/+/855795 [6] https://review.opendev.org/c/openstack/python-saharaclient/+/855787 Thanks, Előd Illés irc: elodilles

2 1

http proxy support
by Oliver Weinmann 02 Sep '22

02 Sep '22

Hi, I was wondering if there is a way to set a http proxy in kolla-ansible during deployment / update etc. Today I wanted to pull new containers and this saturates our internet connection. What we usually do is have machine that massively download stuff from the internet use a squid proxy that throttles their bandwidth. I found the following feature request: https://bugs.launchpad.net/kolla-ansible/+bug/1829586 And it seems some work had been done, but I can't seem to find any info if the change really made it into production: https://review.opendev.org/c/openstack/kolla-ansible/+/692006/ Any help or hints are highly appreciated. Cheers, Oliver

2 4

[all][tc] What's happening in Technical Committee: summary 2022 Sept 2: Reading: 5 min
by Ghanshyam Mann 02 Sep '22

02 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 01. Most of the meeting discussions are summarized in this email. Meeting full recording is available @ https://www.youtube.com/watch?v=WDfOx1m-wog and summary logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-01-15.01.log.html * Next TC weekly meeting will be on Sept 08 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 07. 2. What we completed this week: ========================= * Appointed Dale Smith as Adjutant PTL for Zed cycle[2] * Switched requirements to distributed leadership [3] * Added Exception for the combined 2023.1(Antelope) elections [4] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[5], four are completed and others items are in-progress. Open Reviews ----------------- * Four open reviews for ongoing activities[6]. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- By considering the holiday weeks, we decided to extend the nomination by a week[7]. The new deadline for nomination is Sept 7 [8]. We request you not to delay your nomination for PTL or TC. Define 2023.1 cycle testing runtime ------------------------------------------- Testing runtime for the 2023.1 cycle is up for review [9]. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * "TC + Leader interaction" sessions is scheduled for Oct 17 Monday 15-17 UTC[10], * I have created the TC PTG etherpad to collect the topic[11]. * I sent email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[12] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[13]. Feel free to check and provide feedback. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[14]15]. Project updates ------------------- * Switch release management to distributed leadership[16] 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[17]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [18] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/849606 [3] https://review.opendev.org/c/openstack/governance/+/854685 [4] https://review.opendev.org/c/openstack/governance/+/854624 [5] https://etherpad.opendev.org/p/tc-zed-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030241.… [8] https://governance.openstack.org/election/ [9] https://review.opendev.org/c/openstack/governance/+/854375 [10] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [11] https://etherpad.opendev.org/p/tc-2023-1-ptg [12] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] https://etherpad.opendev.org/p/zuul-config-error-openstack [15] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [16] https://review.opendev.org/c/openstack/governance/+/855276 [17] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [18] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[tc][ptl] TC + Community Leaders interaction in 2023.1 Antelope Virtual PTG
by Ghanshyam Mann 02 Sep '22

02 Sep '22

Hello Everyone, We had successful TC+Community leaders interaction sessions in the last couple of PTG, and we will continue the same for 2023.1 cycle PTG also. I have created the poll to select the best suitable time. It will be for two hours (single or two sessions) either on Monday or Tuesday. Please add your preference in the below doodle poll (including TC members): - https://framadate.org/zsOqRxfVcmtjaPBC Also, I have created the below etherpad with the draft agenda, If you as PTL or project representatives or SIG Chair and would like to attend this session, please add your name: - https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 -gmann

1 1

[tripleo] gate blocker tripleo-ci-centos-9-content-provider
by Chandan Kumar 02 Sep '22

02 Sep '22

Hello tripleo, Please hold your recheck on master tripleo branch, we have a gate blocker for tripleo-ci-centos-9-content-provider. https://bugs.launchpad.net/tripleo/+bug/1988514 The team is currently working on fixing it. With Regards, Chandan Kumar

2 1

[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