October 2022 - openstack-discuss - lists.openstack.org

[all][tc] What's happening in Technical Committee: summary 2022 Oct 7: Reading: 5 min
by Ghanshyam Mann 07 Oct '22

07 Oct '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Oct 6. Most of the meeting discussions are summarized in this email. Meeting recording is present @ https://www.youtube.com/watch?v=HhL67mf4uAY&t=464s and summary logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-10-06-15.00.log.html * Next TC weekly meeting will be a video call on Oct 13 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Oct 12. 2. What we completed this week: ========================= * Dedicated Zed release to Ilya Etingof[2] * Selected Ghanshyam as chair [3] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[4], Five are completed and other items are in-progress. Open Reviews ----------------- * Six open reviews for ongoing activities[5]. New community-wide goal "Migration CI/CD to Ubuntu 22.04" -------------------------------------------------------------------------------------- Dmitriy proposed to select this goal for 2023.1 cycle [6]. 2023.1 cycle Leaderless projects & TC Chair ---------------------------------------------------- * Zun project PTL appointment is under review[7][8]. * Slaweq volunteer to serve as Vice chair[9]. 2023.1 cycle TC PTG planning ------------------------------------ * Etherpads to add the topics: ** https://etherpad.opendev.org/p/tc-2023-1-ptg ** https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 * I sent an email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[10] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[11]. Feel free to check and provide feedback. Fixing Zuul config error ---------------------------- We request projects having zuul config error to fix them, Keep supported stable branches as priority and Extended maintenance stable branch as low priority[12][13]. Project updates ------------------- * None. 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/+/859464 [3] https://review.opendev.org/c/openstack/governance/+/858957 [4] https://etherpad.opendev.org/p/tc-zed-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://review.opendev.org/c/openstack/governance/+/860040 [7] https://review.opendev.org/c/openstack/governance/+/858980 [8] https://review.opendev.org/c/openstack/governance/+/860759 [9] https://review.opendev.org/c/openstack/governance/+/860352 [10] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [11] https://review.opendev.org/c/openstack/governance/+/836888 [12] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0305… [13] https://etherpad.opendev.org/p/zuul-config-error-openstack [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[horizon] Antelope PTG Schedule
by vishal manchanda 07 Oct '22

07 Oct '22

Hello Team, Please Find the Schedule for Horizon PTG in the eherpad [1]. Feel Free to add the topics you want to discuss in the PTG. Don't forget to register for PTG, if not done yet [2]. See you at the PTG! Thanks & Regards, Vishal Manchanda (irc: vishalmanchanda) [1] https://etherpad.opendev.org/p/horizon-antelope-ptg [2] https://openinfra-ptg.eventbrite.com/

1 0

[neutron] Drivers meeting agenda -06.10.2022.
by Lajos Katona 06 Oct '22

06 Oct '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have the following RFE to discuss: [RFE] Strict minimum bandwidth support for tunnelled networks (#link https://bugs.launchpad.net/neutron/+bug/1991965 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[neutron][tempest][all] Broken CI, any job inherited from "devstack"
by Rodolfo Alonso Hernandez 06 Oct '22

06 Oct '22

Hello all: I broke the OpenStack CI (good start as Neutron PTL). I pushed [1] testing only against the Neutron CI. After making the needed changes [2], I thought any other job would be safe. I've opened [3]. The default OVN version installed in the CI, using Ubuntu 20.04, is v20.03, that is a bit old. I've proposed to bump to v21.06, extensively tested in the Neutron CI. Any tempest job from any project is inherited from this one. Once we have migrated to Ubuntu 22.04 during this cycle, we'll remove this forced OVN installation from source. Regards. [1]https://review.opendev.org/c/openstack/neutron/+/859642 [2]https://review.opendev.org/c/openstack/neutron/+/860078/ [3]https://bugs.launchpad.net/devstack/+bug/1991952 [4]https://review.opendev.org/c/openstack/devstack/+/860577

5 8

Limit Access to a Group for a Project- Openstack 13 & 17
by samir oukessou 06 Oct '22

06 Oct '22

Dears, I have a question regarding Openstack, is it possible to limit access for a user to get read only on a specific project that he can only see the instances in that project and eliminate the actions edit,start,stop or delete instance ? i have tried some tests grant *member* role only to the group but all users in the group were able to do everything with the instances thank you in advance, Samir

2 1

[nova][cinder][glance][manila][masakari][tacker][oslo] Configurable soft-delete
by Stephen Finucane 06 Oct '22

06 Oct '22

👋 I'm planning on bringing this up in the nova rooms at the PTG in a few weeks, but I'm also raising it here since this potentially affects other service projects and I can't attend all of those room :) Many projects use the concept of "soft delete" in their database models. A soft deletable model typically has two additional columns, 'deleted' and 'deleted_at'. When deleting such a model, instead of actually deleting the database row (i.e. 'DELETE FROM table WHERE condition'), we set 'deleted' to 'True' and populate the 'deleted_at' column. This is helpful for auditing purposes (e.g. you can inspect all resources ever created, even after they've been "deleted") but bad for database performance (your tables can grow without bound). To work around the performance issues, most projects implement some kind of archive or purge command that will allow operators to periodically clean up these deleted resources. However, at least in nova, we've long since come to the conclusion that soft deleting isn't as useful as initially suspected and the need to run these commands is additional work for no benefit. We've moved toward not using it for all new models. With this said, it's going to be difficult to get away from soft-delete quickly. Not only are there database migrations involved, but operators will need to rework their tooling to adapt to a new, no-soft-delete world. As such, I'd like to propose a half-way measure of making soft-delete configurable. To do this, I'd like to add a new flag in oslo.db, '[database] enable_soft_delete'. When set to 'False' anyone using the 'SoftDeleteMixin' from oslo.db would see these models hard deleted rather than soft deleted when calling 'soft_delete'. This would avoid the need for operators to run the various project-specific purge tooling. The RFC patch for this is available for review [1]. I can also do this on a project-specific basis and have proposed a similar patch for nova [2], however, doing it in oslo.db means every project that uses 'SoftDeleteMixin' in their models will get this for free. Projects that don't (glance, cinder) can switch to using this mixin and also get it for free. As noted above, I intend to discuss this in the nova room at the PTG, but I'd be interested in people's thoughts ahead of time. Do you think this is a good idea? Should we proceed with it? Perhaps there are there better ways to do this? Let me know! Cheers, Stephen [1] https://review.opendev.org/c/openstack/oslo.db/+/860407 [2] https://review.opendev.org/c/openstack/nova/+/860401

7 9

[zed] OpenInfra Live - October 6 at 1400 UTC
by Allison Price 06 Oct '22

06 Oct '22

Hi everyone, This week’s OpenInfra Live episode is brought to you by the OpenStack community who just delivered its 26th on-time release today! Join us to learn about the latest from community leaders about what was delivered in Zed and what we can expect in Antelope, OpenStack's 27th release targeting early 2023. Episode: OpenStack Zed: The End of the Alphabet, The Beginning of a New Era Date and time: October 6 at 1400 UTC You can watch us live on: YouTube: https://www.youtube.com/watch?v=MSbB3L9_MeY <https://www.youtube.com/watch?v=MSbB3L9_MeY> LinkedIn: https://www.linkedin.com/video/event/urn:li:ugcPost:6982723169144950786/ <https://www.linkedin.com/video/event/urn:li:ugcPost:6982723169144950786/> Facebook: https://www.facebook.com/events/390328576642133 <https://www.facebook.com/events/390328576642133> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Kendall Nelson, OpenInfra Foundation Carlos Silva, Manila Jay Faulkner, Ironic Sylvain Bauza, Nova Lajos Katona, Neutron Wu Wenxiang, Skyline Martin Kopec, Interop Working Group Liye Pang, Venus Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Thanks, Allison

1 1

[SECURITY] Openstack Security Assessments
by jackdaw blues 06 Oct '22

06 Oct '22

Hi all, I am currently leading a team of offensive security engineers and we are trying to create a checklist for each component of Openstack in the context of Security Assessment. At the end of the day what we want to end up with is common exploitable configuration weaknesses for each component. It will be against configuration or installation mistakes that result in unintended privileges or information disclosure, etc. Patch management isn't in scope. Not the exact output, but these links can give a good idea of the contents of the security assessment we are planning (these are for AWS): http://flaws.cloud/ http://flaws2.cloud/ Has anyone had any experience regarding the topic above? If so please feel free to connect. Regardless of the experience, if you want to contribute and at mark zero just like we are, you are still welcome and we can help each other create this assessment checklist. Cheers, Asil

2 1

[nova][placement] add your PTG topics before Oct-06 please !
by Sylvain Bauza 06 Oct '22

06 Oct '22

Hi folks, as I said in the nova meeting, I'd like to create an agenda for our PTG topics. Given the PTG is in 3 weeks, please provide your topics you'd like to discuss at the PTG in [1] so I could look at them and try to provide an agenda for them. Eventually, I'd love to have most of the topics by Oct 6th as I said in the title so the agenda would be on the Friday Oct 7th. Also, if you can't be in the Nova PTG sessions for all the PTG schedule (between Tues and Fri for Nova), just add in the topic when you would like to be around. Thanks, -Sylvain [1] https://etherpad.opendev.org/p/nova-antelope-ptg

1 1

Re: Query about networking-onos for newer OpenStack releases
by Rodolfo Alonso Hernandez 06 Oct '22

06 Oct '22

Hello Aditya: If you don't have any specific requirement, I would choose one of the Neutron in-tree ML2 plugins: ML2/OVS or ML2/OVN (and ML2/SR-IOV, that can run with the other two). About which one you can choose, I won't point you to any of them. I would prefer you to review the different architectures: * OVS: https://docs.openstack.org/liberty/networking-guide/scenario-classic-ovs.ht… (this is an old but still valid document to see the different ML2/OVS deployments) * OVN: https://www.openstack.org/videos/summits/austin-2016/practical-ovn-architec… Regards. On Wed, Oct 5, 2022 at 10:37 PM Aditya Sathish <saditya(a)vt.edu> wrote: > Hi Lajos and Rodolfo, > > First of all thank you for your previous replies. After discussing it with > my team over here, we have decided to look at other alternatives beyond > ONOS for implementing an SDN controller with OpenStack. > > Lajos, as you mentioned about OVN, we can perform SDN control on the VM > instances using this. One extension we would like to do is to use OVN to > control an openflow hardware switch. The idea is to allow different users > over a network to access the VM instances. Any idea if I can get this done > through OVN? > > I also tried to check out OpenDayLight but even this has not been updated > in some time. > > Any replies would be greatly appreciated! > > Regards, > Aditya > > On Thu, Sep 22, 2022 at 12:22 PM Lajos Katona <katonalala(a)gmail.com> > wrote: > >> Seems gmail lost some chars from Rodolfo's address, resending. >> >> Lajos Katona <katonalala(a)gmail.com> ezt írta (időpont: 2022. szept. 22., >> Cs, 17:55): >> >>> Hi, >>> Thanks for considering this question. I do not add this topic now to the >>> agenda, of course it can be discussed any time :-) >>> In openstack OVN as an SDN controller is tested, and more and more >>> companies are using it, so for long term I would check it. >>> OVN is now in-tree in Neutron code base, meaning that you don't need any >>> extra code, you can just use Neutron. >>> OVN uses OVS as soft switch and the OVN code is written in C, and >>> originally started by the same team who develops OVS. >>> >>> If you need any advice, or would like to discuss any topics with the >>> team just ping us on #openstack-neutron channel. >>> >>> Best wishes >>> Lajos Katona (lajoskatona) >>> >>> >>> Aditya Sathish <saditya(a)vt.edu> ezt írta (időpont: 2022. szept. 22., >>> Cs, 17:00): >>> >>>> Hi Lajos, >>>> >>>> Thank you for the email. Unfortunately, I'm not sure if I can dedicate >>>> time to maintain this release-on-release. However, I forked the >>>> networking-onos repository and currently verified it with DevStack Zed >>>> along with tempest. (https://github.com/adityasathis/networking-onos) >>>> Considering the changes so far involved only replacing some code to account >>>> for changes in the ML2 callback interface, I think the support should not >>>> be too time consuming if we assume that the ML2 plugin interface remains >>>> the same. >>>> >>>> If we cannot find a way to support networking-onos for long-term >>>> support, do you know a better way to understand the industry implementation >>>> of using SDN controllers with OpenStack? >>>> >>>> Regards, >>>> Aditya. >>>> >>>> On Thu, Sep 22, 2022 at 10:46 AM Lajos Katona <katonalala(a)gmail.com> >>>> wrote: >>>> >>>>> Hi, >>>>> Do you think that you can maintain networking-onos, if you think yes, >>>>> we can discuss this topic on next drivers meeting (as Rodolfo wrote >>>>> previously). >>>>> Just ping me on IRC (#openstack-neutron lajoskatona) and I add this >>>>> topic for you to the agenda: >>>>> https://wiki.openstack.org/wiki/Meetings/NeutronDrivers >>>>> >>>>> Best Wishes >>>>> Lajos Katona (lajoskatona) >>>>> >>>>> Aditya Sathish <saditya(a)vt.edu> ezt írta (időpont: 2022. szept. 20., >>>>> K, 17:48): >>>>> >>>>>> Hello! >>>>>> >>>>>> I am trying to integrate an SDN controller with our lab's OpenStack >>>>>> network. Currently, we have already deployed a version of ONOS to serve our >>>>>> needs and I have been following the SONA project which uses the >>>>>> networking-onos ML2 plugin with OpenStack. However, it seems that the >>>>>> networking-onos project has been retired since the Train release. >>>>>> >>>>>> Is there any way I can get ONOS to work with OpenStack Yoga? If not, >>>>>> what is the go-to way to integrate an SDN controller with OpenFlow support >>>>>> with Neutron?? >>>>>> >>>>>> Any help will be much appreciated. >>>>>> >>>>>> Regards, >>>>>> Aditya. >>>>>> >>>>>

1 0