December 2021 - openstack-discuss

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

03 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 @ - Recording: https://www.youtube.com/watch?v=PwGYse8j4UY - Topic Info logs: https://meetings.opendev.org/meetings/tc/2021/tc.2021-12-02-15.02.log.html * Next week's meeting is on IRC on 9th Dec, Thursday 15:00 UTC, feel free the topic on the agenda[1] by 8th Dec. 2. What we completed this week: ========================= * Goal proposal for RBAC is merged and the next step is to select it[2] * Add ansible-collection-kolla repo to Kolla project[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. Open Reviews ----------------- * 9 open reviews for ongoing activities[5]. TC position on release cadence ------------------------------------- You might have seen the ML thread on the release cadence[6]. We discussed it in this week's TC meeting so that we can provide the TC stand on this. There are mixed amounts of opinions on the different proposals like doing 1-year release, no coordinated release, more releases, mixed LTS release and keeping it same which is 6-month release etc. One of the key things we discussed is how to improve the upgrade process which is one of the key points to revise the current release model. Dan made a good proposal on grenade testing the 'n-1' -> 'n' (current) and 'n-2' -> 'n' (new) so that we make sure 'n' release is upgrade-able from 'n-1' as well as 'n-2' release. For that, we need to think about the deprecation phase to be n+2 release then n+1. Along with that, we can add/improve our upgrade documentation. These are a few ideas we discussed but due to time constraints, we have not concluded yet. We will set up a separate call to continue the discussion sometime in Jan start(after the Christmas holidays) Yoga testing runtime ------------------------- We have an agreement now on Yoga testing runtime and keeping python3.6 support in Yoga, you can see the details in this ML[7] Fixing Zuul config error -------------------------- If your project is listed in zuul config error, please start planning to fix those[8] RBAC discussion: continuing from PTG ---------------------------------------------- The goal proposal is not merged and the next step is to select this goal which is in progress[8] with a good amount of positive votes and no objection yet. Community-wide goal updates ------------------------------------ * Proposed goals: ** RBAC goal is pretty much in good shape now, feel free to review it[9] * Under review: ** FIPS compatibility and compliance [10]. Adjutant need maintainers and PTLs ------------------------------------------- We are waiting to hear from Braden, Albert on permission to work on this project[11]. New project 'Skyline' proposal ------------------------------------ * TC is still waiting for skyline team to respond to open queries[12]. TC tags analysis ------------------- * TC agreed to remove the framework and it is communicated in ML[13]. Project updates ------------------- * Add NVidia vGPU plugin charm to OpenStack charms[14] * Retire js-openstack-lib [15] 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. 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/+/815158 [3] https://review.opendev.org/c/openstack/governance/+/819331 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [7] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026164… [8] https://etherpad.opendev.org/p/zuul-config-error-openstack [9] https://review.opendev.org/c/openstack/governance/+/818817 [10] https://review.opendev.org/c/openstack/governance/+/816587 [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [12] https://review.opendev.org/c/openstack/governance/+/814037 [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [14] https://review.opendev.org/c/openstack/governance/+/819856 [15] https://review.opendev.org/c/openstack/governance/+/807163 [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-16, Dec 06-10
by Előd Illés 03 Dec '21

03 Dec '21

Development Focus ---------------------------- The Yoga-2 milestone will happen in next month, on 06 January, 2022. Yoga-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org <https://releases.openstack.org/yoga/schedule.html>/yoga <https://releases.openstack.org/yoga/schedule.html>/schedule.html <https://releases.openstack.org/yoga/schedule.html>for details. General Information ---------------------------- Please remember that libraries need to be released at least once per milestone period. At milestone 2, the release team will propose releases for any library that has not been otherwise released since milestone 1. Other non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/ <https://opendev.org/openstack/releases/src/branch/master/deliverables/yoga>yoga <https://opendev.org/openstack/releases/src/branch/master/deliverables/yoga> You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/ <https://releases.openstack.org/yoga/schedule.html#y-mf>yoga <https://releases.openstack.org/yoga/schedule.html#y-mf>/schedule.html# <https://releases.openstack.org/yoga/schedule.html#y-mf>y <https://releases.openstack.org/yoga/schedule.html#y-mf>-mf <https://releases.openstack.org/yoga/schedule.html#y-mf> Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released, in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates ----------------------------------------- Yoga-2 Milestone:06 January, 2022 Előd Illés irc: elodilles

1 0

[ironic][meeting] Postpone meeting time until end of March 2022
by Riccardo Pittau 03 Dec '21

03 Dec '21

Hello ironicers! Due to some overlapping time with other meetings that cause me to attend to 2 (or sometimes 3.....) meetings at the same time, I'd like to propose to move the time for the weekly ironic upstream meeting 1 hour later, so from the current 15:00-16:00 UTC to 16:00-17:00 UTC, until the next Daylight saving time change that should happen at the end of March 2022. Thank you! Ciao, Riccardo

4 5

[neutron] Drivers meeting agenda - 03.12.2021
by Lajos Katona 03 Dec '21

03 Dec '21

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. I would like to discuss one bug which I feel is more an RFE: * https://bugs.launchpad.net/neutron/+bug/1952867 : [ml2][ovs] allow multiple physical networks map to one physical ovs bridge As physnet-bridge mapping is deep in Neutron I feel that a discussion is necessary to have a common understanding of the possible benefits and pitfalls of such shange. I wrote to Liu to ask him to join, but I'm not sure if he can participate. We have one more "On Demand" topic from Rodolfo: * https://review.opendev.org/c/openstack/python-openstackclient/+/819627/1: To deprecate "force" behaviour in OSC "quota" commands. This is currently the default behaviour in Neutron; what is proposed in this patch is to move Neutron to, by default, check the quota limits and use "--force" parameter to commit the quota limits without any check. [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 1

[kolla[ Issue running masakari-hostmonitor
by Chris DiLorenzo 03 Dec '21

03 Dec '21

Hello, I am running Kolla-12.0.0 with Openstack Victoria. I have mostly successfully deployed masakari. The instance monitoring works, I can set up segments in Horizon and via CLI. But I can't get masakari-hostmonitor to start: 2021-12-02 16:50:44.999 7 INFO oslo.privsep.daemon [-] Running privsep helper: ['sudo', 'privsep-helper', '--config-file', '/etc/masakari-monitors/masakari -monitors.conf', '--privsep_context', 'masakarimonitors.privsep.monitors_priv', '--privsep_sock_path', '/tmp/tmpf_65hc7m/privsep.sock'] 2021-12-02 16:50:44.892 261 INFO oslo.privsep.daemon [-] privsep daemon starting 2021-12-02 16:50:44.898 261 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0 2021-12-02 16:50:44.902 261 ERROR oslo.privsep.daemon [-] [Errno 1] Operation not permitted Traceback (most recent call last): File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 593, in helper_main Daemon(channel, context).run() File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 403, in run self._drop_privs() File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 439, in _drop_privs capabilities.drop_all_caps_except(self.caps, self.caps, []) File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/capabilities.py", line 156, in drop_all_caps_except raise OSError(errno, os.strerror(errno)) PermissionError: [Errno 1] Operation not permitted 2021-12-02 16:50:45.001 7 DEBUG oslo_privsep.comm [-] EOF on privsep read channel _reader_main /var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep /comm.py:149 2021-12-02 16:50:45.475 7 WARNING oslo.privsep.daemon [-] privsep log: [Errno 1] Operation not permitted 2021-12-02 16:50:45.565 7 INFO oslo.privsep.daemon [-] Spawned new privsep daemon via rootwrap 2021-12-02 16:50:45.565 7 DEBUG oslo.privsep.daemon [-] Accepted privsep connection to /tmp/tmpf_65hc7m/privsep.sock __init__ /var/lib/kolla/venv/lib/pytho n3.8/site-packages/oslo_privsep/daemon.py:371 2021-12-02 16:50:45.467 267 INFO oslo.privsep.daemon [-] privsep daemon starting 2021-12-02 16:50:45.471 267 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0 2021-12-02 16:50:45.474 267 ERROR oslo.privsep.daemon [-] [Errno 1] Operation not permitted Traceback (most recent call last): File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 593, in helper_main Daemon(channel, context).run() File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 403, in run self._drop_privs() File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 439, in _drop_privs capabilities.drop_all_caps_except(self.caps, self.caps, []) File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/capabilities.py", line 156, in drop_all_caps_except raise OSError(errno, os.strerror(errno)) PermissionError: [Errno 1] Operation not permitted sudoers in the container appears to be set up correctly. Thanks Chris

2 3

python_requires >= 3.8 during Yoga
by Stephen Finucane 03 Dec '21

03 Dec '21

gmann has been helpfully proposing patches to change the versions of Python we're testing against in Yoga. I've suggested that we might want to bump 'python_requires' in 'setup.cfg' to indicate that we no longer support any version of Python before 3.8 [1]. As gmann has noted, doing so would mean nova would no longer be installable on Python 3.6 or 3.7 and there has been a small bit of back and forth on the pros and cons of this. I'm wondering what other people's thoughts on this are. Is this something we should be doing? Should we do it for libraries too or just services? Do we ever want to do this? Thoughts, please! Stephen [1] https://review.opendev.org/c/openstack/nova/+/819194/comment/72ecf24f_2bd29…

17 61

[cyborg] Cancel IRC meeting
by Brin Zhang(张百林) 03 Dec '21

03 Dec '21

Hi all, Due to the conflict between the team members and the IRC meeting time, the IRC meeting of this week will be cancelled. If you have any questions, please feel free to ping us through ML or #openstack-cyborg channel. Thanks. brinzhang Inspur Electronic Information Industry Co.,Ltd.

1 0

[cinder] R-17 midcycle followup meeting poll
by Brian Rosmaita 02 Dec '21

02 Dec '21

We had some very useful discussions at yesterday's midcycle but ran out of time before we could discuss Gorka's new quotas proposals. It turns out that due to 8 December being a public holiday in many locations, the next Cinder meeting won't work for a video followup, so we'll hold a special half-hour video meeting on this topic next week. The meeting will be 1400-1430 UTC on one of Tuesday, Thursday, or Friday. If you have a preference, please express it in this poll: https://doodle.com/poll/mnddwtp99uu6hsuq The poll closes at 1300 UTC on Monday 6 December, and I'll announce the selected time shortly thereafter. cheers, brian

1 0

Windows imaging process
by Gaël THEROND 02 Dec '21

02 Dec '21

Hi everyone, On one of our Openstack platforms, we maintain windows based workloads. We currently have the following build process: 1°/- We download windows ISO image. 2°/- Use hyper-v to create a gold image that bring virtio drivers. 3°/- We upload this image on glance and publish it for our users. 4°/- Our users use packer to create their own windows custom image from our gold image. This workflow works pretty fine, it’s simple enough and as Microsoft isn’t releasing a new major Windows every two months it’s pretty ok not having all the steps automated until now. However, I’m wondering if there is a way to automate my first two steps using Openstack? So far, from my early tests, I didn’t managed to get all of appropriate gears to work together, did I missed something? I need to create a VM that at least can use the Windows ISO plus a virtio ISO as a second cdrom device and an additional user-data payload that will instruct the Windows installer to go automatically through the installation steps plus loads missing drivers from the virtio iso. This is perfectly working on a native kvm as you can add multiple cdrom device but I didn’t find a way to replicate that on Openstack. Starting from an unaltered Microsoft originated ISO image is a mandatory requirement for this project (Because of security constraints that I can’t have any impact on). Help from anyone that already had to deal with such situation would be very appreciated ! Thanks!

2 3

[kuryr] Propose to EOL stable branches (Stein, Rocky and Queens) for all the kuryr scope
by Maysa De Macedo Souza 02 Dec '21

02 Dec '21

Hello, We have plenty of stable branches in Kuryr repositories still open with the oldest being stable/queens. We haven't seen many backports[0] proposed to Stein, Rocky and Queens, so I would like to propose retiring these branches. Let me know if anybody is interested in keeping any of those branches. [0] https://review.opendev.org/q/(project:%255Eopenstack/kuryr.*)AND((branch:st… Thank you, Maysa Macedo.

2 3