November 2022 - openstack-discuss

[neutron] metadata IPv6
by Roberto Bartzen Acosta 21 Nov '22

21 Nov '22

Hey folks, Can you confirm if the metadata should work in an ipv6-only environment? As I understand from this discussion on LP:1460177 <https://bugs.launchpad.net/neutron/+bug/1460177> and the fork of the discussion in many opendev reviews #315604 <https://review.opendev.org/c/openstack/neutron-specs/+/315604>, #738205 <https://review.opendev.org/c/openstack/neutron-lib/+/738205> #745705 <https://review.opendev.org/c/openstack/neutron/+/745705>, ..., it seems like it should work. However, this comment in the openstack doc [1] has me questioning if it really works. *"There are no provisions for an IPv6-based metadata service similar to what is provided for IPv4. In the case of dual-stacked guests though it is always possible to use the IPv4 metadata service instead. IPv6-only guests will have to use another method for metadata injection such as using a configuration drive, which is described in the Nova documentation on config-drive <https://docs.openstack.org/nova/latest/user/config-drive.html>."* Is anyone using metadata in an ipv6-only Openstack setup? Regards, Roberto [1] https://docs.openstack.org/neutron/latest/admin/config-ipv6.html#configurin… -- _‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’._ * **‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*

5 8

Unable to access Internet from an instance and accessing instance using floating-point IPs from external network
by vincent lee 21 Nov '22

21 Nov '22

Hi all, I have an OpenStack deployment using kolla-ansible <https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html> with the Yoga version. Our network setup is provided in the attachment ( *network.jpg*). The configuration file (*globals.yml)* and inventory ( *multinode*) are also attached to this email. After the deployment steps, I try to run the script *init-runonce* to create the images and the networks by modifying the external network parameters according to our network setup. I am successful in launching instances from the horizon dashboard. However, the instances were not able to connect to the Internet. I have tried attaching the floating point IPs to the instance, where the IPs are successfully allocated from the range I have specified in the* init-runonce* script. When I launched the instance and tried to ping the external network, it failed. It will be very helpful if anyone can advise me to resolve this issue. I am currently using Ubuntu 20.04.05 LTS version on the controller and compute nodes. Best regards, Vincent

2 1

In Need of Reviewer for Proposal
by Juan Pablo Suazo 21 Nov '22

21 Nov '22

Hello All, I'm in need of a reviewer to take a look at my kolla-ansible proposal, which consists of the modification of a couple of cinder tasks to support placing multiple ceph conf files in a cinder/ceph/ directory to make integrating multiple volume services easier. I have already received insight from another reviewer ( radoslaw.piliszek(a)gmail.com) and made changes to comply with conventions and fix bugs. I couldn't tend to this proposal for a while, and in that time my reviewer has stopped reviewing patches altogether so I'm unable to get the approval for merging. All Zuul tasks are currently successful and the change has been tested locally to ensure it works correctly, so the review should be pretty straight forward. Best wishes, *Juan Pablo Suazo* Cloud Developer Trainee jsuazo(a)whitestack.com

2 2

[TripleO] Intermittent gate failure - centos-9-content-provider jobs
by Ronelle Landy 21 Nov '22

21 Nov '22

Hello All, We are investigating an intermittent check/gate failure on content provider jobs related to DNS and mirror access/resolution: tripleo-ci-centos-9-content-provider <https://zuul.opendev.org/t/openstack/build/8a3afc815e8743568acf3906c92ee203> and the -zed and -wallaby versions. Details are in the related Launchpad bug: https://bugs.launchpad.net/tripleo/+bug/1997202. We will update the list as we know more. Thanks, TripleO CI Team.

1 0

[neutron] Bug deputy report (week starting on Nov-14-2022)
by Bernard Cafarelli 21 Nov '22

21 Nov '22

Hey neutrinos, last bug deputy rotation of the year started: https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy and I was deputy last week, here are the reported bugs. Overall all bugs have patches or at least assignees Critical * [neutron-lib] Stable py3x jobs failing - https://bugs.launchpad.net/neutron/+bug/1996776 Patch and backports by ralonsoh merged - https://review.opendev.org/q/I3a4a27ec4672f8ea8848d7c04651730dae6f40ff * [CI] "test_live_migration_with_trunk" failing - https://bugs.launchpad.net/neutron/+bug/1997025 Caused by recent os-vif bump, workaround suggested by ralonsoh to block this newer version - https://review.opendev.org/c/openstack/neutron/+/865026 High * With new RBAC enabled (enforce_scope and enforce_new_defaults): 'router:external' field is missing in network list response - https://bugs.launchpad.net/neutron/+bug/1996836 Assigned to slaweq, fixed with https://review.opendev.org/c/openstack/neutron/+/865032 Also a related neutron-lib patch merged https://review.opendev.org/c/openstack/neutron-lib/+/864809 * With new RBAC enabled (enforce_scope and enforce_new_defaults): some security groups aren't visible for admin user - https://bugs.launchpad.net/neutron/+bug/1997089 Also assigned to slaweq, patch in progress https://review.opendev.org/c/openstack/neutron/+/865040 * Metadata service broken after minor neutron update when OVN 21.09+ is used - https://bugs.launchpad.net/neutron/+bug/1997092 Fix by ihrachys merged, backports in progress - https://review.opendev.org/c/openstack/neutron/+/864777 Medium * Unit test failure with Python 3.11 - https://bugs.launchpad.net/neutron/+bug/1996527 Fix by haleyb merged - https://review.opendev.org/c/openstack/neutron/+/864448 * OVN metadata randomly stops working - https://bugs.launchpad.net/neutron/+bug/1996594 Happening with xena and OVS 2.16, otherwiseguy investigating (may be caused by OVS version too low for RAFT) * QoS rules policies do not work for "owners" - https://bugs.launchpad.net/neutron/+bug/1996606 Assigned to ralonsoh * [OVN] support update fixed_ips of metadata port - https://bugs.launchpad.net/neutron/+bug/1996677 Patch in progress by huanghailun - https://review.opendev.org/c/openstack/neutron/+/864715 * Add support for DHCP option 119 (domain-search) for IPv4 in ML2/OVN - https://bugs.launchpad.net/neutron/+bug/1996759 Fix by lucasagomes merged - https://review.opendev.org/c/openstack/neutron/+/864740 * [OVN] Enabling and disabling networking log objects doesn't work as expected - https://bugs.launchpad.net/neutron/+bug/1996780 Patch in progress by elvira - https://review.opendev.org/c/openstack/neutron/+/864152 * [ovn-octavia-provider] HM created at fully populated loadbalancer stuck in PENDING_CREATE - https://bugs.launchpad.net/neutron/+bug/1997094 Assigned to froyo * ML2 When OVN mech driver is enabled dhcp extension is disabled - https://bugs.launchpad.net/neutron/+bug/1997185 When OVN is enabled with another driver (linuxbridge here), DHCP extension is disabled. Fix suggested by author to mark extension as supported in OVN - https://review.opendev.org/c/openstack/neutron/+/865081 Low * Replace the Linux Bridge references with Open vSwitch in the installation manuals - https://bugs.launchpad.net/neutron/+bug/1996772 Discussed in team meeting, this part of the doc is quite outdated Patch by ralonsoh merged - https://review.opendev.org/c/openstack/neutron/+/864748 * Install and configure controller node in Neutron - https://bugs.launchpad.net/neutron/+bug/1996889 Doc fix on domain names case, patch by haleyb - https://review.opendev.org/c/openstack/neutron/+/864921 RFE * add address scope to OVN Southbound/Northbound - https://bugs.launchpad.net/neutron/+bug/1996741 Enhancement to use ovn-bgp-agent with non-SNATed tenant networks Patch in review: https://review.opendev.org/c/openstack/neutron/+/861719 Opinion * The virtual network is broken on the node after neutron-openvswitch-agent is restarted if RPC requests return an error for a while - https://bugs.launchpad.net/neutron/+bug/1996788 ralonsoh++ jumped in on that one, issue on OVS agent start when RPC fails. Not much we can do here probably, but left as opinion for potential further discussion Incomplete * [OpenStack-OVN] Poor network performance - https://bugs.launchpad.net/neutron/+bug/1996593 Reported much lower performance with security groups enabled between ML2/OVS and ML2/OVN, more details asked on deployment setup -- Bernard Cafarelli

1 0

Kolla Ansible Image add python package.
by Nguyễn Hữu Khôi 20 Nov '22

20 Nov '22

Hello guys. I read https://docs.openstack.org/kolla/latest/admin/image-building.html but I would like to know how to install python packages for all images at building time. I would be very glad if I can get some guides. Nguyen Huu Khoi

1 0

OpenStack: Can't create instances using KVM on host.
by Seyed Amir Hossein Ahmadi 19 Nov '22

19 Nov '22

I have a Dockerize installation from Devstack all-in-one. The goal for me is to connect to the host's KVM and create instances there. Nova was configured as follows for this purpose. *# /etc/nova/nova.conf# /etc/nova/nova-cpu.conf# [libvirt]# connection_uri = qemu+ssh://root@172.10.1.1/system <http://root@172.10.1.1/system>* When I try to build the instance, I get the following error. *# Build of instance cdd6f8b4-6dcf-4a43-b96a-fb6166b20235 aborted: Failed to allocate the network(s), not rescheduling.* ovs-vsctl commands cause the error. What is the problem? Does this need to be done differently?

1 0

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

18 Nov '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * * We had this week's meeting on Nov 16. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-16-16.00.log.html * Next week (Nov 23) TC weekly meeting is canceled[1]. 2. What we completed this week: ========================= * Defined process for the TC chair nomination & election[2] * Updated the 2023.1 cycle testing runtime[3] * Documented the upgrade patch testing in PTI[4] * Added zookeeper role under OpenStack-Ansible governance[5] * TC stopped using Storybooard. We were not using it for many cycles but TC officially decided [6] to clear all story and close the governance repo in Storyboard[7]. We will not use any other task tracking tool, etherpad or tracking things in meetings are working fine. 3. Activities In progress: ================== TC Tracker for 2023.1 cycle --------------------------------- * Current cycle working items and their progress are present in 2023.1 tracker etherpad[8]. Open Reviews ----------------- * Four open reviews for ongoing activities[9]. OpenInfra Board + OpenStack Syncup Call -------------------------------------------------- We continued the syncup call with Board members on Nov 16[10]. We discussed two topic in this call 1. "Less Diversity" and 2. i18 SIG. Most of the discussion was around first topic. There were multiple ideads were shared and discussed including: - Spreading and encouraging the contribution to wider audiance including large deployement, users, company manager. - Making contribution process more easy for part time contributorts. operators etc by helping them in testing requirement, process, half-baked patches to merge. - Reachout out to platinum members company and company executives to know the reason for not contributing in community and explain/encourage them to contribution. There was no concrete action or step to improve the Diversity but we all togehther need to put effort in all direction to improve it slowly. i18 SIG proposal by Brian about Weblate funding which is ~1500 Euro/year and this sounds reasonable to do from foundation but Brian need to write the foaml proposal to foundation before Board meeting on Dec 6th so that it can be discussed there is needed. Thanks Brian for working and following up on this. The next syncup call will be on Feb 2022-02-08 at 20:00 UTC. If anyone is interested, feel free to join it. Renovate translation SIG i18 ---------------------------------- * We discussed it in Board syncup call and Brian will take it forward to put the Weblate funding formal proposal to foundation. TC Video meeting discussion ---------------------------------- Based on the feedback JayF has abandoned the resolution patch[11]. Thanks JayF for proposal and discussion. Project updates ------------------- * Add Skyline repository for OpenStack-Ansible[12] * Add the cinder-infinidat charm to Openstack charms[13] * Add the infinidat-tools subordinate charm to OpenStack charms[14] * Add the manila-infinidat charm to Openstack charms[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:00 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. See you all next week in PTG! [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://governance.openstack.org/tc/reference/tc-chair-elections.html [3] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03122… [4] https://governance.openstack.org/tc/reference/project-testing-interface.htm… [5] https://review.opendev.org/c/openstack/governance/+/863161 [6] https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-16-16.00.log.html#… [7] https://review.opendev.org/c/openstack/project-config/+/864771 [8] https://etherpad.opendev.org/p/tc-2023.1-tracker [9] https://review.opendev.org/q/projects:openstack/governance+status:open [10] https://etherpad.opendev.org/p/2022-11-board-openstack-sync [11] https://review.opendev.org/c/openstack/governance/+/863685 [12] https://review.opendev.org/c/openstack/governance/+/863166 [13] https://review.opendev.org/c/openstack/governance/+/863958 [14] https://review.opendev.org/c/openstack/governance/+/864067 [15] https://review.opendev.org/c/openstack/governance/+/864068 [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

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

18 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 18 Nov '22

18 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