August 2022 - openstack-discuss - lists.openstack.org

[Ansible] [Yoga] Set rsyslog not to containerise
by Father Vlasie 15 Aug '22

15 Aug '22

Hello everyone! I am trying to deploy Openstack Ansible with Rocky Linux 8.6. I have a rsyslog host that is somewhat underpowered (RAM and CPU) and I thought it might help to run rsyslog without containerisation. I have searched but I have not been able to find an example of this.My guess is that I need to create a file in /etc/openstack_deploy/env.d What syntax and commands do I need? I have searched but I could not find any examples... Thank you very much! Father Vlasie

2 1

[ironic] Proposing Jacob Anders to sushy-core
by Iury Gregory 15 Aug '22

15 Aug '22

Hello ironic-cores and sushy-cores, I would like to propose Jacob Anders (janders irc) for sushy-core. He made great contributions to improve sushy to cover corner cases from different HW in the last releases, you can find some of his contributions in [1], please vote with +1/-1. [1] https://review.opendev.org/q/owner:janders%2540redhat.com+project:openstack… -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

3 2

[Ansible] [Yoga] Not recognising Rocky Linux as supported
by Father Vlasie 13 Aug '22

13 Aug '22

Hello everyone! I am trying to deploy Openstack Ansible with Rocky Linux 8.6 on my target hosts. The documentation here (https://docs.openstack.org/project-deploy-guide/openstack-ansible/latest/ta…) says " • Centos 8 Stream 64-bit * Derivitives: Rocky Linux” under the list of supported operation systems. Ansible does not seem to check for the existence of RHEL 8 systems. :( But when I run “openstack-ansible setup-hosts.yml” I get the error: TASK [Check for a supported Operating System] ***************************************************************************************** fatal: [infra1]: FAILED! => { "assertion": "(ansible_facts['distribution'] == 'Debian' and ansible_facts['distribution_release'] == 'bullseye') or (ansible_facts['distribution'] == 'Ubuntu' and ansible_facts['distribution_release'] == 'focal') or (ansible_facts['distribution'] == 'Ubuntu' and ansible_facts['distribution_release'] == 'jammy') or (ansible_facts['os_family'] == 'RedHat' and ansible_facts['distribution_major_version'] == '9')", "changed": false, "evaluated_to": false, "msg": "The only supported platforms for this release are Debian 11 (Bullseye), Ubuntu 20.04 LTS (Focal), Ubuntu 22.04 (Jammy) and CentOS 9 Stream.\n” What should I do? Thank you!

3 2

[all][tc] What's happening in Technical Committee: summary 2022 Aug 12: Reading: 5 min
by Ghanshyam Mann 13 Aug '22

13 Aug '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 11. Most of the meeting discussions are summarized in this email. Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-08-11-15.00.log.html * Next TC weekly meeting will be on Aug 18 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 17. 2. What we completed this week: ========================= * None in this week. 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], Two are completed and others items are in-progress. Open Reviews ----------------- * Two open reviews for ongoing activities[4]. OpenStack TC + Board member meeting ------------------------------------------------ As you might know, OpenStack TC and Board member had a informal meeting on Aug 10[5][6], I am summarizing the discussion here. The Openstack TC has presented the 'OpenStack Updates' to Board meeting in berlin. One of the key part of the updates were 'OpenStack community Challenges' and we could not finish the discussion or brainstorm on these in berlin meeting. We decided to continue the discussion on those (Slide#21)[7]. In this call, we can only cover the first challenge only 'Less Interaction with Operators & Users'. There is no doubt that we are facing this issue at noticeable level (RBAC is good example where we lacked the operator/user feedback). A lot of things including ML, events are discussed on why it is happening and how to improve it. Having ops meetup as a separate event is something many members raised concern about and it will be good to merge these events into other community events like Summit, PTG etc. To try the first step towards that we can invite or welcome operators in Oct virtual PTG and give them a feeling on merging the events with developers event can be beneficial to both the group. On that, Dan suggested the idea of scheduling the 'Operatos Hours' per project in PTG and there we will keep the discussion on operator-centric and the format they want. We continued the discussion on this in TC weekly meeting where we had mixed suggestions on the 'Operator Hours' schedule, either to ask each project to schedule it in their room and operator join or other way around. Before deciding any format, we will be asking operators about their preference. We will continue the discussion on 'OpenStack community Challenges' in the next call which is schedule on 20:00 UTC on Wednesday, November 16[8]. If anyone is interested, feel free to join it. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- Not much update on this but we will be seeing the election schedule proposed soon. 2023.1 cycle TC PTG planning ------------------------------------ We discussed about how to best encourage/invite operators into the PTG (I wrote in the above section) and based on the operators feedback we will proceed next. We will continue the discussion in the next meeting also. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[9]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [10] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]12]. Project updates ------------------- * Retire openstack-helm-addons[13] 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[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [15] 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/+/849997 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029886.… [6] https://etherpad.opendev.org/p/2022-08-board-openstack-sync [7] https://docs.google.com/presentation/d/1yCiZy_9A6hURXD0BRdr33OlK7Ugch5EgSvF… [8] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029968.… [9] https://review.opendev.org/c/openstack/governance/+/836888 [10] https://review.opendev.org/c/openstack/governance/+/849606 [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [13] https://review.opendev.org/c/openstack/governance/+/849997 [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Re: [Ansible] [Yoga] Not recognising Rocky Linux as supported
by Father Vlasie 12 Aug '22

12 Aug '22

> On Aug 12, 2022, at 3:13 PM, openstack-discuss-request(a)lists.openstack.org wrote: > > Comparing https://opendev.org/openstack/openstack-ansible/src/branch/stable/yoga/play… <https://opendev.org/openstack/openstack-ansible/src/branch/stable/yoga/play…> to https://opendev.org/openstack/openstack-ansible/src/branch/master/playbooks… <https://opendev.org/openstack/openstack-ansible/src/branch/master/playbooks…> it appears that OpenStack Ansible has removed CentOS Stream/RHEL/Rocky 8 support on master, but the assertion allows it under Yoga. Based on the failure above you must be running master OSA? I would try running the Yoga branch instead. > > The master branch documentation likely needs to be updated as well. That worked perfectly, thank you! :)

1 0

[tc] November 2022 OpenInfra Board Sync
by Jeremy Stanley 12 Aug '22

12 Aug '22

The Open Infrastructure Foundation Board of Directors is endeavoring to engage in regular check-ins with official OpenInfra projects. The goal is for a loosely structured discussion one-hour in length, involving members of the board and the OpenStack TC, along with other interested community members. This is not intended to be a formal presentation, and no materials need to be prepared in advance. I've started an Etherpad where participants can brainstorm potential topics of conversation, time-permitting: https://etherpad.opendev.org/p/2022-11-board-openstack-sync At the conclusion of the August 10 discussion, we agreed to tentatively schedule the next call for 20:00 UTC on Wednesday, November 16, so I've attached a calendar file which can serve as a convenient schedule hold for this, in case anyone needs it. -- Jeremy Stanley

1 0

OpenStack User Survey
by Jimmy McArthur 12 Aug '22

12 Aug '22

Hi Everyone - Just a quick reminder to please take the OpenStack User Survey [1] This vitally important survey provides direct, anonymized feedback to our Project Teams to help them build better software. If you run a deployment, no matter the size, please take 30 min out of your day to take this survey! Thank you, Jimmy [1] https://openstack.org/user-survey/

1 0

[release] Release countdown for week R-7, Aug 15 - 19
by Előd Illés 12 Aug '22

12 Aug '22

Development Focus ----------------- We are entering the last weeks of the Zed development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-ATC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Technical Contributor and allowed to vote. This is done by adding extra-atcs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-ATC freeze on August 18th, 2022. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (August 25th, 2022). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (September 1st, 2022) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, September 1st, 2022. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (September 15th, 2022) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (September 29th, 2022) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to Feature freeze (September 1st, 2022). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… knelson [at] openstack.org/diablo_rojo on IRC is available if you need help selecting or writing your highlights Upcoming Deadlines & Dates -------------------------- Extra-ATC freeze: August 18th, 2022 (R-7 week) Non-client library freeze: August 25th, 2022 (R-6 week) Client library freeze: September 1st, 2022 (R-5 week) Zed-3 milestone: September 1st, 2022 (R-5 week) Next PTG: October 17-21, 2022 (virtual PTG!!!) Előd Illés irc: elodilles

1 0

[tripleo] gate blocker tripleo-ci-centos-9-undercloud-upgrade
by Marios Andreou 12 Aug '22

12 Aug '22

o/ tripleo please hold rechecks on master tripleo branch - we have a gate blocker for tripleo-ci-centos-9-undercloud-upgrade https://bugs.launchpad.net/tripleo/+bug/1984175 package/conflict/mirror issue not clear yet - grateful for pointers if you have them

5 10

About the meaning of compute nodes
by 정재철 11 Aug '22

11 Aug '22

If there are many nodes, is it possible to create a high-performance VM? (e.g. Can 2 1 core cpu nodes create 1 2 core cpu VM)

5 5