- openstack-discuss - lists.openstack.org

Call for Participation: Sovereign Cloud DevRoom at FOSDEM 2023
by Felix Kronlage-Dammers 19 Nov '22

19 Nov '22

# FOSDEM 2023 In Person – Sovereign Cloud DevRoom Call for Participation! The twenty-third edition of FOSDEM takes place Saturday 4th and Sunday 5th February 2023 in Brussels, Belgium. For the first time there will be a DevRoom that focuses on the subject of Sovereign Cloud and its practical aspect for digital sovereignty. ## Key dates tl;dr: - Conference dates 4-5 February, 2023 In person - Sovereign Cloud DevRoom date: Saturday 4th February - Submission deadline: Friday December 9th, 2022 - 23:59 UTC. - Announcement of selected talks: Thursday 15th December - You must be available in person to present your talk ## About the Sovereign Cloud DevRoom ### Overview The Sovereign Cloud DevRoom is for discussing topics and issues of user privacy and sovereignty and the intersection with the needs of infrastructure providers in the cloud computing era. A few topic examples to illustrate (a longer list is below): - Can all operations be open, or may there be a need for a two+ tier openess (country specific laws or company secrets)? - How can privacy relevant data be anonymized instead of being deleted, without losing the useful information? - Open Operations is more than just sharing runbooks, how is knowledge shared and fostered best across organizations? - Navigating our personal data lakes -- we're going to need better tools that are easier to use by more people for managing and curating encrypted data lakes - The role of machine learning in conducting data science on anonymized information - Countering the risks of integrated platforms These are just a few example suggestions, we welcome proposals on any aspects around these topic. More topic ideas and details on how to submit proposals is below. ### Discussing the Sovereign Cloud The recent EU focus on digital sovereignity has brought fresh attention and innovation to a problem area many of us have been interested in and working on for a long time. This DevRoom focuses on a practical aspect of digital sovereignty: how it affects user-oriented and potentially privacy-containing infrastructure in the cloud computing era. This aspect is the _sovereign cloud_, the intersection of digital sovereignty and a modern cloud-centric way to create and sustain infrastructure, operations, and development to address the needs of users (which may be other cloud services or actual, real people.) With the rise of the Confidential Computing Consortium (https://confidentialcomputing.io/) some people feel we are beginning to achieve "sovereign enough" where it comes to the balance of the needs of the individual and the needs of tech companies et al. But there are just as many other voices calling attention to potential problems and unfulfillable needs of staying on that path. Looking at the entire landscape of the problem, it's clear that Confidential Computing also aligns with usage on a sovereign cloud. It is a tool to ensure the least amount of provider trust, and it is still a good idea until we've moved new processor architectures into the mainstream that are less impacted by predictive execution vulnerabilities. So while it is not perfect, making it harder for an attacker is always a good idea where feasible. In looking for other paths to fill more needs, we naturally come to the intersection of Free/Open where interests from different backgrounds pursuing different goals suddenly find themselves working together in a common direction. Two of those groups are part of the organizing committee for this devroom: As a way of addressing the holistic needs and supporting a truly balanced digital sovereignty, organizations such as the overeign Cloud Stack (https://scs.community/) have come together to provide a complete technology solution, standards as well as reference implementations, that can be proven and recognized by everyone as a truly sovereign cloud. In this area where the requirements of a sovereign cloud are being met is another intersection from the ecosytem of Free and Open Source software development. The idea of Open Operations is essential to projects such as Operate First that provide a developer-friendly post-CI/CD platform for running, testing, and proving Open Source services. Longer list of topic ideas - this is not an exclusive list, feel free to submit further ideas: - Can all operations be open, or may there be a need for a two+ tier openess (country specific laws or company secrets)? - How can privacy relevant data be anonymized instead of being deleted, without losing the useful information? - Discussion: How open can software be called, if it relies on closed operations and closed infrastructure? - Do we need to refine the definition of upstream in the idea of Open Operations? - Is hybrid accelerating Open Operations or can it be a slow-downer/ separator? Or the solution to possible privacy issues? - Interoperability, transparency, and independence are the go to goals, what can be accepted on our way until we are there? - Open Operations is more than just sharing runbooks, how is knowledge shared and fostered best across organizations? - Share experiences and stories on creating environments of psychological safety so that failures indeed make us experts - Building communities of practice across organizations - Navigating our personal data lakes -- we're going to need better tools that are easier to use by more people for managing and curating encrypted data lakes - The role of machine learning in conducting data science on anonymized information - Countering the risks of integrated platforms Again, these are just suggestions. We welcome proposals on any aspects around these topic. Format and lengths of submissions: - Long (40 minutes, including Q&A) - Short (20 minutes, including Q&A) - Lightning (5 minutes, no Q&A) Aside from Presentation also Meetings/Discussions are welcome for topics where a BoF-style (Birds of Feather) session is appropriate. HOW TO SUBMIT A TALK - Head to the FOSDEM 2023 Pentabarf <https://penta.fosdem.org/submission/FOSDEM23> website. - If you already have a Pentabarf account, please don’t create a new one. - If you forgot your password, reset it. - Otherwise, follow the instructions to create an account. - Once logged in, select “New Event” and click on “Show All” in the top right corner to display the full form. Your submission must include the following information: - First and last name / Nickname (optional)/ Image - Email address - Mobile phone number (this is a very hard requirement as there will be no other reliable form of emergency communication on the day) - Title and subtitle of your talk (please be descriptive, as titles will be listed with ~500 from other projects) - Track: Select “Sovereign Cloud DevRoom” as the track - Event type: - Lightning Talk OR - Meeting or Discussion OR - Presentation - Persons: Add yourself as the speaker with your bio - Description: Abstract (required)/ Full Description (optional) - Links to related websites / blogs etc. - Beyond giving us the above, let us know if there’s anything else you’d like to share as part of your submission – Twitter handle, GitHub activity history – whatever works for you. We especially welcome videos of you speaking elsewhere, or even just a list of talks you have done previously. First time speakers are, of course, welcome! - For issues with Pentabarf, please contact cloud-devroom-manager(a)fosdem.org. Feel free to send a notification of your submission to that email. If you need to get in touch with the organisers or program committee of the Sovereign Cloud DevRoom, email us at cloud-devroom-manager(a)fosdem.org FOSDEM website <https://fosdem.org/2023/> / FOSDEM code of conduct <https://fosdem.org/2023/practical/conduct/>

1 0

[all][tc] Canceling next week TC meetings
by Ghanshyam Mann 19 Nov '22

19 Nov '22

Hello Everyone, As many of us will not be available due to thanks giving, we are cancelling the next week's (Nov 23) TC meeting. -gmann

1 0

[Glance] No weekly meeting next week
by Pranali Deore 18 Nov '22

18 Nov '22

Hello, I will be on PTO from Tuesday, 22nd Nov to Friday, 25th Nov, so I won't be available for the weekly meeting next week. If anyone has anything important to be discussed feel free to add in the meeting agenda etherpad[1] and it would be nice if someone from the glance team volunteers to chair the meeting based on the agenda. [1]: https://etherpad.opendev.org/p/glance-team-meeting-agenda#L70 Thanks, Pranali

1 0

[release] Release countdown for week R-17, Nov 21 - 25
by Herve Beraud 18 Nov '22

18 Nov '22

Development Focus ----------------- We are now past the Antelope-1 milestone. Teams should now be focused on feature development and completion of release cycle goals [0]. [0] https://governance.openstack.org/tc/goals/selected/ General Information ------------------- Our next milestone in this development cycle will be Antelope-2, on January 5, 2023. This milestone is when we freeze the list of deliverables that will be included in the 2023.1 final release, so if you plan to introduce new deliverables in this release, please propose a change to add an empty deliverable file in the deliverables/antelope directory of the openstack/releases repository. Now is also generally a good time to look at bugfixes that were introduced in the master branch that might make sense to be backported and released in a stable release. If you have any question around the OpenStack release process, feel free to ask on this mailing-list or on the #openstack-release channel on IRC. Upcoming Deadlines & Dates -------------------------- Antelope-2 Milestone: January 5, 2023 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

Host node monitoring
by KK CHN 18 Nov '22

18 Nov '22

List, A general question: Can nagios core be used for HCI nodes and other nodes which are installed with Type1 hypervisors ? ( Eg: ESXi hypervisor doesn't have an OS to install the nagios on to it.. as it a bare metal hypervisor . ) How do people monitor these base machines with configurable alerts/notifications to email, and mobile phones of people who manage ?' Krish

2 1

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 18 Nov '22

18 Nov '22

Hello Neutrinos: Due to the lack of agenda, today's drivers meeting is cancelled. Have a nice weekend!

1 0

[kolla-ansible][Yoga] Install with self-signed certificate
by wodel youchi 18 Nov '22

18 Nov '22

Hi, To deploy Openstack with a self-signed certificate, the documentation says to generate the certificates using kolla-ansible certificates, to configure the support of TLS in globals.yml and to deploy. I am facing a problem, my old certificate has expired, I want to use a self-signed certificate. I backported my servers to an older date, then generated a self-signed certificate using kolla, but the deploy/reconfigure won't work, they say : self._sslobj.do_handshake()\n File \"/usr/lib64/python3.6/ssl.py\", line 648, in do_handshakeself._sslobj.do_handshake()\nssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED certificate verify failed PS : in my globals.yml i have : *kolla_verify_tls_backend: "yes"* Regards.

2 11

[tc][policy] RBAC (policy-popup team) meeting time
by Ghanshyam Mann 18 Nov '22

18 Nov '22

Hello Everyone, I am starting the RBAC (policy-pop up) bi-weekly meeting on alternate Tuesday (starting Nov 22) at 17:00 UTC on #openstack-meeting IRC channel. Details: https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… ICS File: https://meetings.opendev.org/#Secure_Default_Policies_Popup-Team_Meeting -gmann

1 0

[all][tc] 2023.1 cycle updated testing runtime (recommended Upgrade Path testing)
by Ghanshyam Mann 18 Nov '22

18 Nov '22

Hello Everyone, You might have seen the TC discussion[1] in PTG for the best possible testing for smooth upgrade. When there is a distro version change in testing runtime, then we need to test both the old and the new distro versions (for the cycle when we are bumping the distro version). We have documented the recommended upgrade path testing in PTI also[2], refer to that for details. In 2023.1 cycle, we are moving from Ubuntu Focal (20.04) to Jammy (22.04)[3] and as per the upgrade path testing we should test the Focal (20.04) also. TC has merged these updates in the 2023.1 cycle testing runtime document[4] which are basically: 1. Testing Ubuntu Focal (20.04) in a single job (one job is enough to test the old version) in project gate. For example, neutron did[5]. This can be a new job or one of the existing jobs. 2. Python minimum version to test is python 3.8 (default version in Ubuntu Focal). We will be testing python 3.8 and python 3.10 unit/functional jobs. Unit test job template change has been merged[6] which will automatically start running py38 unit test job and functional jobs can be modified (if needed) by project side. [1] https://etherpad.opendev.org/p/tc-2023-1-ptg#L422 [2] https://governance.openstack.org/tc/reference/project-testing-interface.htm… [3] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubunt… [4] https://review.opendev.org/c/openstack/governance/+/860599 [5] https://review.opendev.org/c/openstack/neutron/+/862492 [6] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/864464 -gmann

1 0

[openstack-ansible] Designate: rndc config file not generated
by Taltavull Jean-François 17 Nov '22

17 Nov '22

Hello, I'm deploying Designate on OpenStack Wallaby/Ubuntu 20.04 with DNS servers located outside the OpenStack platform. After running 'os-designate-install.yml' playbook, 'bind9-utils' package is correctly installed but I can't find rndc config file anywhere inside the lxc container. This prevents rndc from running well and communicating with the DNS servers. Any idea ? Regards, Jean-Francois

3 4