December 2022 - openstack-discuss

[cinder] Cinder Midcycle - 1 (R-16) Summary
by Rajat Dhasmana 05 Dec '22

05 Dec '22

Hello Argonauts, The summary for midcycle-1 held on 30th November, 2022 between 1400-1600 UTC is available here[1]. Please go through the etherpad and recordings for the discussion. [1] https://wiki.openstack.org/wiki/CinderAntelopeMidCycleSummary - Rajat Dhasmana

1 0

Upgrade Ceph 16.2.10 to 17.2.x for Openstack Wallaby RBD storage
by Zakhar Kirpichenko 05 Dec '22

05 Dec '22

Hi! I'm planning to upgrade our Ceph cluster from Pacific (16.2.10) to Quincy (17.2.x). The cluster is used for Openstack block storage (RBD), Openstack version is Wallaby built on Ubuntu 20.04. Is anyone using Ceph Quincy (17.2.x) with Openstack Wallaby? If you are, please let me know if you've encountered any issues specific to these Ceph and Openstack versions. Many thanks! Best regards, Zakhar

1 0

Re: Unable to access Internet from an instance and accessing instance using floating-point IPs from external network
by Eugen Block 04 Dec '22

04 Dec '22

Hi, if you want people to reply you should keep the mailing list in the loop. Also please don't paste pictures but terminal output as plain text so it won't get lost. >> From my controller site: >> External-internet = 192.168.1.118 >> Internal-network = 10.42.0.189 Seems like you meant it the other way around looking at the other networks. >> My external network details is shown below I don't see a segmentation ID for the external network, we create provider (external) networks with the same segmentation ID as the corresponding VLAN in our environment has. The rest of the information on the pictures is not readable to me, please paste the security-group rules as text. >> Apart from all the above information, I will briefly talk about what I >> have enabled in my global.yml file. I have set the >> kolla_internal_vip_address to "192168.1.200", kolla_external_vip_address to >> "10.42.0.200", enable_haproxy to "yes" and other core components of >> openstack was enabled. I'm not familiar with kolla so I can't really say what else could be missing or not. You could disable the port security for your instance to see if that helps, otherwise use tcpdump on control and compute node to see where the packets get lost and which vlans are in use. I'm not sure if that will resolve it but I believe your external network should have a segmentation ID. Zitat von vincent lee <vincentlee676(a)gmail.com>: > Hi, one last thing I would like to add on is the setting of my openvswitch > configuration. > [image: image.png] > [image: image.png] > > > On Wed, Nov 30, 2022 at 1:39 PM vincent lee <vincentlee676(a)gmail.com> wrote: > >> Hi Eugen, >> Sorry for causing any confusion in my previous emails and I will summarize >> the main issue here. After deploying openstack from a fresh installation, I >> have not modified the security group when working creating an instance or a >> container. >> >> From my controller site: >> External-internet = 192.168.1.118 >> Internal-network = 10.42.0.189 >> >> For my compute host 1: >> Internal-network = 192.168.1.115 >> >> For my compute host 2: >> Internal-network = 192.168.1.108 >> >> My current issue is that when I created an instance which ran >> successfully, I was not able to ping that instance from my controller via >> the external network. Besides, I was also not able to ping the internet >> (8.8.8.8) inside of the instance. >> >> However, I was able to ping to the external network (10.42.0.67) from >> inside of the newly created instance itself. In other words, the router is >> communicating correctly. I have attached an image of my network topology as >> shown below. >> [image: image.png] >> Inside of my instance >> [image: image.png] >> I have attached an image of my router details as shown below >> [image: image.png] >> My external network details is shown below >> [image: image.png] >> external network's subnet detail is shown below >> [image: image.png] >> My internal network details is shown below >> [image: image.png] >> internal network's subnet is shown below >> [image: image.png] >> My floating IPs is shown below >> [image: image.png] >> My current security group rules is shown below >> [image: image.png] >> My system information is shown below >> [image: image.png] >> Apart from all the above information, I will briefly talk about what I >> have enabled in my global.yml file. I have set the >> kolla_internal_vip_address to "192168.1.200", kolla_external_vip_address to >> "10.42.0.200", enable_haproxy to "yes" and other core components of >> openstack was enabled. >> >> Best, >> Vincent >> >> >> >> On Wed, Nov 30, 2022 at 2:30 AM Eugen Block <eblock(a)nde.ag> wrote: >> >>> So you did modify the default security-group, ports 8000 and 8080 are >>> not open by default. Anyway, can you please clarify what doesn't work >>> exactly? >>> Does the instance have an IP in the public network but the router is >>> not pingeable (but that is not necessarily an issue) and you can't >>> access it via which protocols? Does SSH work? Is the access blocked by >>> a http_proxy? >>> >>> >>> Zitat von vincent lee <vincentlee676(a)gmail.com>: >>> >>> > To add on to my previous email, I have attached an image of my security >>> > group as shown below. >>> > >>> > Best regards, >>> > Vincent >>> > >>> > On Tue, Nov 22, 2022 at 3:58 AM Eugen Block <eblock(a)nde.ag> wrote: >>> > >>> >> Just one more thing to check, did you edit the security-group rules to >>> >> allow access to the outside world? >>> >> >>> >> Zitat von Adivya Singh <adivya1.singh(a)gmail.com>: >>> >> >>> >> > it should be missing a default route most of the time. >>> >> > or check IP tables on router namespace the DNAT and SNAT are working >>> >> > properly >>> >> > >>> >> > >>> >> > >>> >> > On Tue, Nov 22, 2022 at 9:40 AM Tobias McNulty < >>> tobias(a)caktusgroup.com> >>> >> > wrote: >>> >> > >>> >> >> On Mon, Nov 21, 2022 at 7:39 PM vincent lee < >>> vincentlee676(a)gmail.com> >>> >> >> wrote: >>> >> >> >>> >> >>> After reviewing the post you shared, I believe that we have the >>> correct >>> >> >>> subnet. Besides, we did not modify anything related to the >>> cloud-init >>> >> for >>> >> >>> openstack. >>> >> >>> >>> >> >> >>> >> >> I didn't either. But I found it's a good test of the network! If >>> you are >>> >> >> using an image that doesn't rely on it you might not notice (but I >>> >> >> would not recommend that). >>> >> >> >>> >> >> >>> >> >>> After launching the instances, we are able to ping between the >>> >> instances >>> >> >>> of the same subnet. However, we are not able to receive any >>> internet >>> >> >>> connection within those instances. From the instance, we are able >>> to >>> >> ping >>> >> >>> the router IP addresses 10.42.0.56 and 10.0.0.1. >>> >> >>> >>> >> >> >>> >> >> To make sure I understand: >>> >> >> - 10.42.0.56 is the IP of the router external to OpenStack that >>> provides >>> >> >> internet access >>> >> >> - This router is tested and working for devices outside of OpenStack >>> >> >> - OpenStack compute instances can ping this router >>> >> >> - OpenStack compute instances cannot reach the internet >>> >> >> >>> >> >> If that is correct, it does not sound like an OpenStack issue >>> >> necessarily, >>> >> >> but perhaps a missing default route on your compute instances. I >>> would >>> >> >> check that DHCP is enabled on the internal subnet and that it's >>> >> providing >>> >> >> everything necessary for an internet connection to the instances. >>> >> >> >>> >> >> Tobias >>> >> >> >>> >> >> >>> >> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> > >>> > -- >>> > thanks you. >>> > vincentleezihong >>> > 2garnet >>> > form2 >>> >>> >>> >>> >>> >> >> -- >> thanks you. >> vincentleezihong >> 2garnet >> form2 >> >> > > -- > thanks you. > vincentleezihong > 2garnet > form2

2 1

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

03 Dec '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 30. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-30-16.00.log.html * Next TC weekly meeting will be on Dec 7 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Dec 6. 2. What we completed this week: ========================= * FIPS testing on Ubuntu paid subscription We discussed it in TC meeting and after considering the currently available options, TC agreed to go for this[2]. We know it is paid subscription (given by Ubuntu as free to OpenStack upstream CI) and we should use the free open source things to test the upstream code but we do not have any other setup ready for FIPS testing (CentOSstream is not stable enough to add voting job, Debian is not tested broadly in all projects so it may take more time to add the voting job in projects) For now, testing FIPS with Ubuntu paid token is best possible go ahead and if we have any open source/free/stable version available in any distro then we can move FIPS job on that. * Added Skyline repository for OpenStack-Ansible[3] * Added the manila-infinidat charm to Openstack charms[4] * Added the cinder-infinidat charm to Openstack charms[5] 3. Activities In progress: ================== TC Tracker for 2023.1 cycle --------------------------------- * Current cycle working items and their progress are present in 2023.1 tracker etherpad[6]. Open Reviews ----------------- * Three open reviews for ongoing activities[7]. Technical Election changes (Extending Nomination and voting period) ---------------------------------------------------------------------------------- This is in review and positive response so far[8]. Renovate translation SIG i18 ---------------------------------- * No specific update for this week and it will be discussed with the Foundation staff and Board members in Dec 6th board meeting. Adjutant situation (project is not active) ----------------------------------------------- Proposal to mark Adjutant as inactive is up[9] and ready for review. I have emailed about it to current PTL also. Project updates ------------------- * Add the infinidat-tools subordinate charm to OpenStack charms[10] 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[11]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [12] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-30-16.00.log.html#… [3] https://review.opendev.org/c/openstack/governance/+/863166 [4] https://review.opendev.org/c/openstack/governance/+/864068 [5] https://review.opendev.org/c/openstack/governance/+/863958 [6] https://etherpad.opendev.org/p/tc-2023.1-tracker [7] https://review.opendev.org/q/projects:openstack/governance+status:open [8] https://review.opendev.org/c/openstack/governance/+/865367 [9] https://review.opendev.org/c/openstack/governance/+/849153 [10] https://review.opendev.org/c/openstack/governance/+/864067 [11] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [12] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 02 Dec '22

02 Dec '22

Hello Neutrinos: Due to the lack of agenda, *today's meeting is cancelled*. I have one topic [1] I would like to discuss but I'll wait until I test the code and I'm sure the feature is working. Once this is done, I'll ask you to review it and vote for this RFE. Have a good weekend! [1]https://bugs.launchpad.net/neutron/+bug/1998202

1 0

[openstack-ansible] Removing support for Calico Network driver
by Dmitriy Rabotyagov 02 Dec '22

02 Dec '22

Hi everyone, Due to lack of maintainers of Calico driver support in OpenStack-Ansible we have decided to remove support for this driver. Eventually, CI was failing for Calico jobs for the last few cycles and we haven't seen any interest in further support of the feature. Patches for Calico removal are already proposed: https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/866123 https://review.opendev.org/c/openstack/openstack-ansible/+/866119 If you're interested in this driver and want to step in for fixing CI and supporting the feature, please let us know either by replying to this email or by voting accordingly for the mentioned patches. In case no negative feedback will be received we will merge them by the end of the next week, December 9 2022.

1 0

[Magnum] ls /etc/cni/net.d/ is emty
by Nguyễn Hữu Khôi 01 Dec '22

01 Dec '22

Hello guys. I use Magnum on Xena and I custom k8s cluster by labels. But My cluster is not ready and there is nothing in /etc/cni/net.d/ and my cluster said: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized And this is my labels kube_tag=v1.21.8-rancher1,container_runtime=containerd,containerd_version=1.6.10,containerd_tarball_sha256=507f47716d7b932e58aa1dc7e2b3f2b8779ee9a2988aa46ad58e09e2e47063d8,calico_tag=v3.21.2,hyperkube_prefix= docker.io/rancher/ Note: I use Fedora Core OS 31 for images. Thank you. Nguyen Huu Khoi

2 3