- openstack-discuss - lists.openstack.org

Regarding Nova's inability to delete the Cinder volume for creating virtual machines (version Y)
by 无数的星球 30 Oct '23

30 Oct '23

When creating a virtual machine in the dashboard, create a volume and choose to delete the virtual machine while also deleting the volume. When deleting the virtual machine, there is no normal uninstallation of the volume and the volume is not deleted. The relevant error logs are shown in the image, but the openstack CLI can delete its volume. The specific commands are as follows. CLI： source /etc/keystone/admin-openrc.sh (Verify password file) openstack volume set --detached　191e555c-3947-4928-be46-9f09e2190877（volumeID） openstack volume delete 191e555c-3947-4928-be46-9f09e2190877（volumeID） It seems that Nova is unable to interact with the Cinder API to delete(or detached) commands, but I am not very professional. I don't know if it's a bug? Note that I have seen similar bug patch files, but they are invalid. URL:   BUG page   https://bugs.launchpad.net/nova/+bug/2016173   Page for patching files   https://review.opendev.org/c/openstack/nova/+/880399 Is not working!!!

2 1

[openstack-ansible][ptg] OpenStack-Ansible 2024.1 (Caracal) vPTG Summary
by Dmitriy Rabotyagov 30 Oct '23

30 Oct '23

Hey everyone, We had quite a productive discussion on the PTG and I will provide a summary of them below. It was divided into multiple sections, like things we need to finish for 2023.2 (Bobcat) - since OpenStack-Ansible has trailing release model we have some time to wrap things up; plans for 2024.1 (Caracal) and some things that moved out of scope until better times. You can also find original PTG with discussions here [1] Finalizing 2023.1 (Bobcat): * Documentation on using pretty endpoint names (ie identity.cloud.org instead of cloud.org:5000). For 2024.1 we will try to simplify the way of using such naming to make it more convenient for end-users. * Finalize support of RabbitMQ Quorum queues for all services [2]. With that they will be disabled by default at least for 2023.2 release and we will revise the defaults for 2024.1 * Implement openstack_resources common rolem that will handle different resources creation, like OpenStack users, projects, networks, images, aggregates, etc. It will be also used in roles like Tempest, Octavia, Trove and Magnum to create such resources, instead of each role implementing its own flow of doing that. We agreed to add a separate playbook that will allow deployers to leverage the role and run it after setup-openstack. * Debian 12 support. Most patches have landed, but we also need to reflect it's support in documentation * Review and release Skyline role. Tough discussion was about defaults and how Skyline should co-exist with Horizon. As a result we decided to deploy both options, when both are defined in the inventory (as usual), but the playbook that is run last will basically configure HAProxy backends to itself, fully neglecting other available services. So if you want to have both Skyline and Horizon running and functional - you will need to apply some overrides for that. There are also no guarantees that we will be able to merge and release the role in time, so we may end up with making it as part of OSA only for 2024.1. Scoped improvements for 2024.1 (Caracal): * Adoption of PKI role to be used with PIPE modules, that will allow the role to be pointed to any file (like encrypted with ansible-vault) or external storage that supports lookup, instead of plain text files on a deploy host. With that we will also take a look at using Hishcorp Vault as a PKI source and adding it as another driver in addition to the "standalone" one. * Natively supporting multi-AZ deployments for Neutron. At the moment for OVS/LXB you need to define some overrides to make that working, while for OVN you would need to manually execute a bunch of commands. POC patch has been already proposed [3], but it still needs some love. * Finalize support of OVN driver for Octavia. Initial patch has been proposed, but it also needs some love, despite it works in general [4] * Resume work on ProxySQL implementation as a replacement for HAProxy balancing for MariaDB deployment. That should improve load distribution between MariaDB backends. * Allow to select OS for LXC containers. At the moment we're forcing to use the host OS, while in some cases it might be preferred to use a different one, like during OS upgrades or switching the OpenStack deployment from one distro to another. * With that we are excited about incus (LXD fork) having the first release and it being packaged with traditional packages (only .deb at the moment). This opens the door for implementation of incus as a manager for LXC containers, that may simplify our flows and day2 operations significantly. * Invest some time into decreasing the runtime, both for CI/CD and for end-user deployments. * In case improvements for Quorum Queues will land to the oslo.messaging [5] - add a set of variables to roles for nicely controlling the behaviour. [1] https://etherpad.opendev.org/p/osa-caracal-ptg [2] https://review.opendev.org/q/topic:osa%252Fquorum_queues [3] https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/858271 [4] https://review.opendev.org/c/openstack/openstack-ansible-os_octavia/+/868462 [5] https://review.opendev.org/q/topic:bug-2031497

1 0

[Glance] Caracal PTG Summary
by Pranali Deore 30 Oct '23

30 Oct '23

Hello Everyone, We had our eighth virtual PTG between 23rd OCt to 26th OCT 2023. Thanks to everyone who joined the virtual PTG sessions. Using Opendev Meetpad we had all the discussion around different topics for glance. I have created etherpad[1] with notes from the session and also included the recordings of each session. Here is the short summary of the discussions. *Tuesday , OCT 24th 2023* # Bobcat Retrospective On a positive note we have completed few important things like adding support for weighting mechanism to store, support for RBD driver to move images to the trash if they cannot be deleted immediately due to having snapshots, putting efforts in bridging the gap between glanceclient and openstackclient and started new location API work which will replace the image-update mechanism for consumers like cinder and nova for OSSN-0090 and OSSN-0065. On the other side we decided to speedup the work we've had in flight and we decided to have recent patches reviews meeting once in a month and backlogs review parties before each milestone to speedup the reviews. Recording: https://drive.google.com/drive/u/0/folders/1oYrgVLV5L89keDZLx7r1JWcG8pk65918 - Bobcat Retrospective # Common Tempest Failures for Glance Glance has faced so many random CI failure and timeouts since bobcat mid cycle, though progress has been made on general issues and few of the project-specific issue also been addressed like post failures causing by image conversion failure, tried reducing concurrency but still we see some random timeouts, one of the common tempest failure has been observed that some glance related jobs like glance-multistore-cinder-import, nova-ceph-multistore are failing with race condition while saving image data, there is a short term solution proposed by sending image_id while creating the image to ensure that each test can utilize own image and race condition could be avoided. https://docs.google.com/document/d/1S41X3FSjqGF87ehTvqLEC9QsDIkULjS1NiqCagZ… Decided to reproduce 1st failure from the gdoc and debug more on failures Recording: https://drive.google.com/drive/u/0/folders/1oYrgVLV5L89keDZLx7r1JWcG8pk65918 - Common tempest failures # Add missing CLI support for some Glance API in Openstack Client The migration work for adding missing CLI was initiated in the antelope cycle. We have added the SDK support for cache API , images API and metadef API(in progress). On the client side support for cache API and images API has been added and for metadef is in progress. This cycle we have decided to cover the remaining client and sdk support for APIs by distributing the work among the team. Recordings: https://drive.google.com/drive/u/0/folders/1oYrgVLV5L89keDZLx7r1JWcG8pk65918 - Adding missing OSC support # Default Glance to configure multiple stores Glance has deprecated single stores configuration since Stein cycle and will remove the support of same in upcoming cycle by dividing the wrok in small parts like remove/migrate single store unit/functional tests. Goal for this cycle: list down the work we have to do with regards to tests. and migrate unit/functional test from "single-store only" to "multistore-only" and send email to the mailing list to urge users to migrate to multi-store. Recording: https://drive.google.com/drive/u/0/folders/1oYrgVLV5L89keDZLx7r1JWcG8pk65918 - Default glane to multistore support.webm *Wednesday, OCT 25th 2023* # Remove Location Strategy In Bobcat we added support for the weighing mechanism to store. So we can safely remove the location strategy and by default use the latest weighing mechanism which will be very easy and efficient. Decided to deprecate location strategy in C and remove it in D, notify operators and users on ML and have a spec for the same in Caracal Cycle. Recording: https://drive.google.com/drive/u/0/folders/1oYrgVLV5L89keDZLx7r1JWcG8pk65918 - Remove Location Strategy # Improve process of restoring image to active state which is set as 'pending_delete' At the moment glance supports delaying of image-data from the store by setting delayed_delete to True and when image gets deleted it actually keeps image data in the backend and then Scrubber daemon deletes it permanently later. To restore the image, the deployer needs to set the UUID of that image in glance-api.conf to the 'restore' option under the Default section. If there are multiple images that need to be restored then this process will be kind of time consuming as each time a new Id will be needed to set in the configuration file and rerun the scrubber if it is not running as Daemon. Decided to introduce admin only API to restore the image and restrict Scrubber daemon to delete the images which are in pending_delete state. The restore part from the scrubber for a couple of cycles until the new API is stable.The restore option from the scrubber will be deprecated in this cycle and then will be removed in the following cycle. Recording: https://drive.google.com/drive/u/0/folders/1oYrgVLV5L89keDZLx7r1JWcG8pk65918 - Restore Image # Deprecate cachemanage middleware Cache operations (CR(u)D) is now part of glance API. Even though we need to depend on cache/cachemanage middleware to enable it. There are two middlewares related to caching, one is `cache` and other is `cachemanage` and we can now get rid of `cachemanage` middleware and glance-cache-manage command line utility. Agreed on deprecating cachmanage middleware in C & remove in D cycle. Decided to have a spec lite for the same after verifying how the cache APIs will respond if cache middleware is not enabled. Recording: https://drive.google.com/drive/u/0/folders/1oYrgVLV5L89keDZLx7r1JWcG8pk65918 - Deprecate Cachemanage Middleware # Use mysql database for caching instead of sqlite There are two different database(s) used for glance, MySql for regular operations and sqlite for caching related operations. We have decided to use single database i.e. MySql for all glance related operations so that it will reduce the efforts to maintain both databases. The Spec is up for review now: https://review.opendev.org/c/openstack/glance-specs/+/899367/4 Recording: https://drive.google.com/drive/u/0/folders/1oYrgVLV5L89keDZLx7r1JWcG8pk65918 - Centralize DB for Caching *Thursday, OCT 26th 2023* # Unified limits Topic was discussed and decided to postpone it to the next cycle since no one volunteered to work on it. # New Location APIs We have decided to have support of new location api which will replace the image-update mechanism for consumers like cinder and nova for OSSN-0090 and OSSN-0065. The implementation patches are up for review along with the unit/functional tests, documentation, api version bump, client side support and tempest coverage[2] The Poc patches of nova and cinder are also there to test this new location api functionality. In this cycle we are going to work on some missing test scenarios & verify PoC patches of consumers like nova and cinder are working with new location api functionality. Recording: https://drive.google.com/drive/u/0/folders/1oYrgVLV5L89keDZLx7r1JWcG8pk65918 - New Location API Apart from above topics you can find other miscellaneous topics discussed in PTG etherpad [1] along with the recordings of the sessions and milestone wise priorities at the end. If you have any questions/suggestions then please join us in our weekly meeting(each Thursday on #openstack-meeting irc channel at 1400 UTC) [1]: https://etherpad.opendev.org/p/oct2023-ptg-glance#L10 [2]: https://review.opendev.org/q/topic:New-Location-Apis Thanks & Regards, Pranali Deore

1 0

[qa][ptg] QA Caracal vPTG Summary
by Martin Kopec 30 Oct '23

30 Oct '23

Hi everyone, here is a summary of the discussions. The full agenda can be found here [1]. == Bobcat Retrospective == Considering the still shrinking number of active contributors, we still manage making releases and doing code reviews. However, less contributors make it hard to react to sudden failures or provide as stable jobs as possible - that's e.g. the case of the Centos 9 topic. == Stop supporting Centos 9 Stream? == No, Centos 9 stays. As concluded during the session, Centos 9 is required for FIPS as other distros (their latest versions) are far behind with supporting FIPS. Apart from that, CS9 is required for Manila, Cinder integration with Ceph as Ceph is tested on Centos 9 too. The biggest pain point is that Centos9 Stream is not versioned and thus it's hard to build a reliable gate. One of the goals for the cycle is improving the connection between Centos and OpenStack community - it's beneficial for both sides. One of the ways might be a 3rd party CI or simply a solution that would provide a quick feedback to the Centos group, e.g. by running Devstack with the default configuration, but at the same time wouldn't affect all the jobs on the OpenStack side that run the distro. This way we could at least avoid simple issues found right away (e.g. some deps issues). The QA team is happy to assist. == Triage previous and write new priority items == The list of the priority items planned for this cycle as well as the ones which were carried over from the previous cycles, can be found here [2]. [1] https://etherpad.opendev.org/p/oct2023-ptg-qa [2] https://etherpad.opendev.org/p/qa-caracal-priority Thank you all for attending the PTG and contributing to the discussion, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

[interop][ptg] Interop Caracal vPTG Summary
by Martin Kopec 30 Oct '23

30 Oct '23

Hi everyone, here is a summary of the discussions. The full agenda can be found here [1]. We had only one topic on the agenda - a new view on interoperability testing - don't confuse it with interop which is a certification program. The program just uses the interop tests for the certification purposes. The tests that are part of interop were long ago considered as enough for testing interoperability. However, as it's been pointed out as well as discussed many times already [2][3], the tests don't guarantee interoperability of tested clouds - they test only basic API thus they can be used for the certification program (related to OpenStack brand) at most. Interoperability is subjective, every user may be looking for a different level of interoperability. Read the ending of the article [2]. If there is someone who is interested in interoperability testing in OpenStack or even someone who requires that for various reasons, we could do something like this [4] - we could gather various tests from various testing platforms that test specific functionalities. It would provide anyone with metrics and thus allow them to compare clouds. It would be like when we're shopping, e.g. for a new computer - we have various metrics that help us decide which one suits us better like dimensions, weight, RAM, CPU, storage space etc. From the last PTG (and several one before) it, however, doesn't look like the community is interested in running actual interoperability testing. Let us know if you disagree, we don't want to develop something that is not needed by anyone. [1] https://etherpad.opendev.org/p/oct2023-ptg-interop [2] https://superuser.openinfra.dev/articles/new-view-on-interoperability-in-op… [3] https://etherpad.opendev.org/p/bobcat-ptg-interop [4] https://etherpad.opendev.org/p/openstack-interop-2.0 Thank you all for attending the PTG and contributing to the discussion, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

[neutron] Bugs deputy report October 23rd - 29th
by Miguel Lavalle 30 Oct '23

30 Oct '23

Hi Neutrinos, Here's this week's bugs deputy report: Critical ====== High ==== https://bugs.launchpad.net/neutron/+bug/2040166 [OVN] The neutron_sync_mode conf is ignored for SB DB sync. Assignee: Lucas Gomes. https://bugs.launchpad.net/neutron/+bug/2040172 [OVN] OvnSbSynchronizer - clean/delete segmenthostmappings for unrelated hosts. Assignee: Harald Jensas. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/899077 https://bugs.launchpad.net/neutron/+bug/2041609 FIP update removes QoS policy. Assignee Lajos Katona. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/899469 Medium ====== https://bugs.launchpad.net/neutron/+bug/2040517 host not removed from table ml2_vxlan_endpoints with the agent delete. Needs and owner https://bugs.launchpad.net/neutron/+bug/2041612 [n-d-r] DRAgent removed from bgp speaker automatically. Needs verification and owner Low === RFEs ==== https://bugs.launchpad.net/neutron/+bug/2040001 [N-D-R] Change neighbor connect mode when the BGP peer does not support passive mode. Assignee: Tiago Pires. This RFE was initially discussed during this week's vPTG. Proposed spec: https://review.opendev.org/c/openstack/neutron-specs/+/899210 Undecided ======== Invalid ======== https://bugs.launchpad.net/neutron/+bug/2040242 [ipam] Why prevent first ip < (subnet.first + 1) if version of subnet is ipv6. Assignee Liu Xie. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/899374 https://bugs.launchpad.net/neutron/+bug/2040457 [allocation_pools] Need re-generation new pools from cidr and gateway-ip after update one subnet with empty 'allocation_pools'. Assignee: Liu Xie. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/899373

1 0

Regarding Nova's inability to delete the Cinder volume for creating virtual machines (version Y)
by 无数的星球 28 Oct '23

28 Oct '23

When creating a virtual machine in the dashboard, create a volume and choose to delete the virtual machine while also deleting the volume. When deleting the virtual machine, there is no normal uninstallation of the volume and the volume is not deleted. The relevant error logs are shown in the image, but the openstack CLI can delete its volume. The specific commands are as follows. CLI： source /etc/keystone/admin-openrc.sh (Verify password file) openstack volume set --detached　191e555c-3947-4928-be46-9f09e2190877（volumeID） openstack volume delete 191e555c-3947-4928-be46-9f09e2190877（volumeID） It seems that Nova is unable to interact with the Cinder API to delete(or detached) commands, but I am not very professional. I don't know if it's a bug?

1 0

horizon - dashboard behavior - shows elements from previous project
by Miguel Casique Meneses 28 Oct '23

28 Oct '23

There is a horizon chart behaving quite strangely version: horizon-0.3.2 To recreate the issue: login to openstack >> change project (using dropdown) >> show containers (odd behaviour, such as change to old project, or lists containers from previous project) >> show instances (odd behaviour, changes projects, or at least shows the wrong project in dropdown) Basically, it sometimes shows the elements from the previous browsed project and not the current one that has been selected. If we reload the page, it goes back to project that has been selected, but sometimes it does not The logs are not showing nothing relevant, but we can see when project has been swapped

3 2

[Glance] Caracal PTG Updates
by Pranali Deore 27 Oct '23

27 Oct '23

Hello Everyone, We have concluded Glance Caracal vPTG yesterday. I will share the summary early next week. You can find tentative milestone wise priorities for glance in PTG etherpad[1]. Join us in the weekly meeting on Thursday if you have any doubts/suggestions. Thanks & Regards, Pranali [1]: https://etherpad.opendev.org/p/oct2023-ptg-glance#L277

1 0

[keystone] Weekly Meeting 11/1 Canceled
by Dave Wilde 27 Oct '23

27 Oct '23

Hello all, I'm on PTO the week of 11/1 so I'm canceling the Weekly meeting as well as the reviewathon on 11/3. Thanks! /Dave

1 0

[vPTG][Security SIG] Agenda / Planning etherpad
by Tony Breeds 27 Oct '23

27 Oct '23

Hello All, I'ms sorry for getting this out with so little notice. I've pulled together an agenda for the os-security SIG meeting at the vPTG When: https://www.timeanddate.com/worldclock/fixedtime.html?iso=2023-10-27T16:00:… Where: https://meetpad.opendev.org/oct2023-ptg-os-security Planning Etherpad: https://etherpad.opendev.org/p/oct2023-ptg-os-security Agenda: * Previous PTGs carryover ** https://etherpad.opendev.org/p/vancouver-june2023-os-security-sig *** Xstatic --https://review.opendev.org/c/openstack/xstatic-jquery-migrate/+/878923 ** https://etherpad.opendev.org/p/march2023-ptg-os-security *** image encryption pop-up team (Luzi) **** castellan consumers api is in place now, unblocking significant parts of the implementation * Should we meet outside of the PTG events [10 mins] * https://security.openstack.org/ Updates ** Sorting of OSSNs -- Something along the lines of -- https://review.opendev.org/c/openstack/releases/+/887691 ** Remove references to storyboard? * Other business? * VMT Business * Open public security bug triage/processing -- http://tiny.cc/public-ossn Yours Tony.

1 0

[glance][ops] FEEDBACK REQUEST: Deprecating VMWare Datastore store driver
by Takashi Kajinami 27 Oct '23

27 Oct '23

Hello, In glance_store we have maintained the VMWare Datastore store driver which stores image data in ESX/ESXi or vCenter Server. This store driver was added 9 years ago[1] to be used in the VMware environment with OpenStack. However now the vmwarapi virt driver was marked experimental and is being removed from nova[2], so it seems the original use case is no longer valid. I proposed deprecating this store driver during this cycle[3], so that we can remove it during D (or E) cycle, but I'm sending this email to gather early feedback before we merge the deprecation. In case if you are using the driver or have any concern, please reply to me (publicly or privately) or leave your comments in the review. [1] https://review.opendev.org/c/openstack/glance/+/58883 [2] https://review.opendev.org/c/openstack/nova/+/897017 [3] https://review.opendev.org/c/openstack/glance_store/+/893696 Thank you, Takashi

1 0

[neutron][openvswitch][antelope] Bridge eth1 for physical network provider does not exist
by ddorra＠t-online.de 26 Oct '23

26 Oct '23

Hello, I'm installing Openstack Antelope with network option 2 ( following https://docs.openstack.org/neutron/2023.2/install/compute-install-option2-u…) The interface name of the provider network is eth1, so I put this to bridge_mappings. The local IP is from the management network. #------------------------------------------------------ # /etc/neutron/plugins/ml2/openvswitch_agent.ini # [DEFAULT] [agent] [dhcp] [network_log] [ovs] bridge_mappings = provider:eth1 [securitygroup] enable_security_group = true firewall_driver = openvswitch [vxlan] local_ip = 192.168.2.71 l2_population = true #-------------------------------------------------------- However, the neutron log complains that bridger eth1 does not exist. Launching of instances fails neutron-openvswitch-agent.log: 2023-10-23 19:26:00.062 17604 INFO os_ken.base.app_manager [-] instantiating app os_ken.app.ofctl.service of OfctlService 2023-10-23 19:26:00.062 17604 INFO neutron.agent.agent_extensions_manager [-] Loaded agent extensions: [] 2023-10-23 19:26:00.108 17604 INFO neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_bridge [-] Bridge br-int has datapath-ID 00005e65b1943a49 2023-10-23 19:26:02.438 17604 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Mapping physical network provider to bridge eth1 vvvvvvv 2023-10-23 19:26:02.438 17604 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Bridge eth1 for physical network provider does not exist. Agent terminated! ^^^^^^^ 2023-10-23 19:26:03.914 17619 INFO neutron.common.config [-] Logging enabled! 2023-10-23 19:26:03.914 17619 INFO neutron.common.config [-] /usr/bin/neutron-openvswitch-agent version 20.4.0 2023-10-23 19:26:03.914 17619 INFO os_ken.base.app_manager [-] loading app neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_oskenapp ----------------------------------------- Additional information root@control:/var/log/neutron# openstack network list +--------------------------------------+----------+--------------------------------------+ | ID | Name | Subnets | +--------------------------------------+----------+--------------------------------------+ | 32f53edc-a394-419f-a438-a664183ee618 | doznet | e38e25c2-4683-48fb-a7a0-7cbd7d276ee1 | | 74e3ee6a-1116-4ff6-9e99-530c3cbaef28 | provider | 2d3c3de4-9a0d-4a21-9af1-8ecb9f6f16d5 | +--------------------------------------+----------+--------------------------------------+ root@control:/var/log/neutron# root@compute1:/etc/neutron/plugins/ml2# ip a 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 08:00:27:9f:c7:89 brd ff:ff:ff:ff:ff:ff inet 192.168.2.71/24 brd 192.168.2.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::a00:27ff:fe9f:c789/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 08:00:27:91:60:58 brd ff:ff:ff:ff:ff:ff inet 10.0.0.71/24 brd 10.0.0.255 scope global eth1 valid_lft forever preferred_lft forever inet6 fe80::a00:27ff:fe91:6058/64 scope link valid_lft forever preferred_lft forever 4: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether da:3b:3a:a0:59:97 brd ff:ff:ff:ff:ff:ff 5: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 5e:65:b1:94:3a:49 brd ff:ff:ff:ff:ff:ff 6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:53:87:59 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever What are the proper settings? Any help appreciated Dieter

4 5

[oslo] oslo-rootwrap daemon test failures
by Chuck Tuffli 26 Oct '23

26 Oct '23

There are a handful of failures when running the oslo-rootwrap test suite on FreeBSD. Most I have been able to fix, but I'm looking for some help understanding what is going wrong with the daemon tests. One example of a failing test is test_daemon_cleanup_client. The test reports: AssertionError: -9 == -9 : Server haven't stopped in one second which I _think_ occurs because of an exception while closing the connection (see below). Any suggestions as to what I might check (and where) to understand why this is happening? Thanks! Running the latest from git on FreeBSD 13.2 with Python 3.9 {2} oslo_rootwrap.tests.test_functional.RootwrapDaemonTest.test_daemon_cleanup_client [1.455829s] ... FAILED Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/usr/home/tuffli/dev/openstack/oslo.rootwrap.git/oslo_rootwrap/tests/test_functional.py", line 299, in test_daemon_cleanup_client self.client._finalize() File "/usr/local/lib/python3.9/contextlib.py", line 126, in __exit__ next(self.gen) File "/usr/home/tuffli/dev/openstack/oslo.rootwrap.git/oslo_rootwrap/tests/test_functional.py", line 289, in _test_daemon_cleanup self.assertNotEqual(-signal.SIGKILL, process.returncode, File "/usr/local/lib/python3.9/unittest/case.py", line 846, in assertNotEqual raise self.failureException(msg) AssertionError: -9 == -9 : Server haven't stopped in one second Captured daemon_log: ~~~~~~~~~~~~~~~~~~~~ 2023-10-19 18:33:10,718 | [ 1664]+DEBUG | Created temporary directory /tmp/rootwrap-snf7oiau 2023-10-19 18:33:10,718 | [ 1664]+DEBUG | Will listen on socket /tmp/rootwrap-snf7oiau/rootwrap.sock 2023-10-19 18:33:10,719 | [ 1664]+ INFO | Starting rootwrap daemon main loop 2023-10-19 18:33:11,719 | [ 1664]+ INFO | Got signal 2. Shutting down server 2023-10-19 18:33:11,719 | [ 1664]+DEBUG | Removing temporary directory /tmp/rootwrap-snf7oiau Traceback (most recent call last): File "/usr/home/tuffli/dev/openstack/oslo.rootwrap.git/.tox/py3/lib/python3.9/site-packages/oslo_rootwrap/daemon.py", line 166, in daemon_start server.serve_forever() File "/usr/local/lib/python3.9/multiprocessing/managers.py", line 184, in serve_forever sys.exit(0) SystemExit: 0 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/home/tuffli/dev/openstack/oslo.rootwrap.git/oslo_rootwrap/tests/run_daemon.py", line 58, in <module> cmd.daemon() File "/usr/home/tuffli/dev/openstack/oslo.rootwrap.git/.tox/py3/lib/python3.9/site-packages/oslo_rootwrap/cmd.py", line 62, in daemon return main(run_daemon=True) File "/usr/home/tuffli/dev/openstack/oslo.rootwrap.git/.tox/py3/lib/python3.9/site-packages/oslo_rootwrap/cmd.py", line 133, in main daemon_mod.daemon_start(config, filters) File "/usr/home/tuffli/dev/openstack/oslo.rootwrap.git/.tox/py3/lib/python3.9/site-packages/oslo_rootwrap/daemon.py", line 171, in daemon_start conn.close() File "/usr/home/tuffli/dev/openstack/oslo.rootwrap.git/.tox/py3/lib/python3.9/site-packages/oslo_rootwrap/jsonrpc.py", line 92, in close self._socket.shutdown(socket.SHUT_RDWR) OSError: [Errno 57] Socket is not connected Captured client_log: ~~~~~~~~~~~~~~~~~~~~ 2023-10-19 18:33:10,290 | [ 1610] DEBUG | Popen for ['/usr/home/tuffli/dev/openstack/oslo.rootwrap.git/.tox/py3/bin/python', '/usr/home/tuffli/dev/openstack/oslo.rootwrap.git/oslo_rootwrap/tests/run_daemon.py', '/tmp/tmpjri8_7we/rootwrap.conf'] command has been instantiated 2023-10-19 18:33:10,719 | [ 1610] INFO | Spawned new rootwrap daemon process with pid=1664 2023-10-19 18:33:10,728 | [ 1610] INFO | Stopping rootwrap daemon process with pid=1664 2023-10-19 18:33:11,733 | [ 1610] INFO | Rootwrap daemon process exit with status: -9

3 4

[CloudKitty] Cancelling weekly meeting 30 of October
by Rafael Weingärtner 25 Oct '23

25 Oct '23

Hello guys, As we discussed in the vPTG, we will be cancelling the next CloudKitty bi-weekly meeting that would take place on October the 30. If you need any assistance until the next meeting, you can reach me via e-mail. Best regards, -- Rafael Weingärtner

1 0

[manila] Oct 26th upstream meeting is cancelled
by Carlos Silva 25 Oct '23

25 Oct '23

Hello everyone! Cancelling this week's upstream meeting as we will be focused on the OpenStack Manila PTG [1]. Next meeting will take place on Nov 2nd. [1] https://etherpad.opendev.org/p/caracal-ptg-manila Thanks, carloss

1 0

[cinder] Cancelling this week's meeting (25 Oct)
by Rajat Dhasmana 25 Oct '23

25 Oct '23

Hello Argonauts, We have the 2024.1 Caracal PTG this week so cancelling the upstream meeting. See you at the PTG! Dates: 24 October (Tuesday) - 27 October (Friday), 2023 Time: 1300 - 1700 UTC Room: Cactus Meeting Link: https://www.openstack.org/ptg/rooms/cactus Thanks Rajat Dhasmana

1 0

[neutron][octavia] New deployment / suggestions for network
by Eric K. Miller 25 Oct '23

25 Oct '23

Hi, We have been deploying OpenStack for quite some time, using Kolla-Ansible, and typically choose DVR and OVS with Amphorae deployed by Octavia for load balancing. With the issues that DVR has with Octavia's Amphorae and Virtual IPs, with essentially non-functional automated fail-over, we have always wanted to move to OVN since it appears to be the popular approach now. I have also read that OVN appears to work properly with allowed-address-pairs correctly, whereas with DVR, OVS does not, and thus some of the issues with Amphorae Virtual IPs. However, OVN, from what I understand, has issues with, or doesn't support, VPNaaS, which we use extensively. Plus, it only supports Layer 4 load balancing, whereas with Amphorae, we get Layer 7 load balancing - also used extensively. I'm not sure, though - maybe OVN with Octavia still supports Amphorae if we need Layer 7 load balancing? Am I wrong regarding any of the comments above? What is the best back-end networking architecture that provides scalability (so, not VLANs), Layer 7 load balancing with Octavia, along with VPNaaS, in a brand new install with the latest version of OpenStack? Note that we used Midonet long long ago, and it seemed to have everything we wanted, but shortly after purchasing it, Midokura immediately decided to abandon support for OpenStack and went the Kubernetes route. Not sure if they still do this, but needless to say, Midonet isn't a valid solution unfortunately. Tungsten Fabric appears like an alternate solution to Midonet, but that project is sunsetting in 2024, so that's dead too. :( Thank you for any suggestions! Eric

4 6

[kolla] Cancelling weekly meeting tomorrow (25th Oct 2023)
by Michał Nasiadka 25 Oct '23

25 Oct '23

Hello, Cancelling tomorrows weekly meeting since we’re already meeting at vPTG sessions. Thanks, Michal

1 0

RDO Bobcat 2023.2 Released
by Amy Marrich 24 Oct '23

24 Oct '23

RDO Bobcat Released The RDO community is pleased to announce the general availability of the RDO build for OpenStack 2023.2 Bobcat for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Bobcat is the 28th release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available for CentOS Stream 9 on the CentOS mirror network in: http://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-bobcat/ The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Stream and is a member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. The highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/bobcat/highlights.html but here are some highlights: - New Cinder driver features were added, notably, QoS support for Fujitsu ETERNUS DX driver, replication-enabled consistency groups support for Pure Storage driver, and Active/Active support for NetApp NFS driver. - Glance added support for RBD driver to move images to the trash if they cannot be deleted immediately due to having snapshots. - The Neutron service has enabled the new API policies (RBAC) with system scope and default roles by default. - The Nova legacy quota driver is now deprecated and a nova-manage limits command is provided in order to migrate the orginal limits into Keystone. We plan to change the default quota driver to the unified limits driver in an upcoming release. It is recommended that you begin planning and executing a migration to unified limits as soon as possible. OpenStack Bobcat is not marked as Skip Level Upgrade Release Process or SLURP. According to this model ( https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…) this means that upgrades will only be supported from the Antelope 2023.1 release. RDO Bobcat 2023.2 has been built and tested with the recently released Ceph 18.2.0 Reef version (https://docs.ceph.com/en/latest/releases/reef/) which has been published by the CentOS Storage SIG in the official CentOS repositories. *Note:* Follow the instructions in [RDO documentation]( https://www.rdoproject.org/install/install-with-ceph/) to install OpenStack and Ceph services in the same host. During the Bobcat 2023.2 development cycle, the RDO community has implemented automatic dependency detection at run and build time. We expect that these changes will lead to more accurate dependency chains in OpenStack packages and less manual maintenance tasks for community maintainers. Following upstream retirement, some packages are not present in RDO Bobcat 2023.2 release: - python-networking-odl - python-networking-omnipath - python-networking-vmware-nsx - python-oswin-tests-tempest - python-os-xenapi - python-patrole - python-stackviz - python-vmware-nsxlib - python-vmware-nsx-tests-tempest Contributors - During the Bobcat cycle, we saw the following new RDO contributors: - Arkady Shtempler - Dariusz Smigiel - Dave Wilde - Fabricio Aguiar - Jakub Skunda - Joan Francesc Gilabert - Maor Blaustein - Mohammad Abunemeh - Szymon Datko - Yadnesh Kulkarni Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all 47 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and rdo-website repositories: - Alfredo Moralejo Alonso - Amy Marrich - Ananya Banerjee - Arkady Shtempler - Artom Lifshitz - Arx Cruz - Bhagyashri Shewale - Bohdan Dobrelia - Chandan Kumar - Daniel Pawlik - Dariusz Smigiel - Dave Wilde - Douglas Viroel - Enrique Vallespi Gil - Fabricio Aguiar - Giulio Fidente - Goutham Pacha Ravi - Gregory Thiemonge - Grzegorz Grasza - Ihar Hrachyshka - Jakub Skunda - Jiří Podivín - Jiří Stránský - Joan Francesc Gilabert - Joel Capitao - Karolina Kula - Karthik Sundaravel - Luca Miccini - Lucas Alvares Gomes - Luigi Toscano - Luis Tomas Bolivar - Maor Blaustein - Marios Andreou - Mathieu Bultel - Matthias Runge - Mohammad Abunemeh - Rodolfo Alonso Hernandez - Ronelle Landy - Sandeep Yadav - Slawomir Kaplonski - Soniya29 vyas - Szymon Datko - Takashi Kajinami - Tobias Urdin - Tom Weininger - Yadnesh Kulkarni - Yatin Karel The Next Release Cycle At the end of one release, focus shifts immediately to the next release i.e Caracal. Get Started To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. Finally, for those that don’t have any hardware or physical resources, there’s the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. Get Help The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org. The #rdo channel on OFTC IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS IRC channels (#centos, #centos-cloud, #centos-devel in Libera.Chat network), however we have a more focused audience within the RDO venues. Get Involved To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and on the OFTC IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube.

1 0

Re: [kolla-ansible][yoga] Cannot authenticate to openstack after deploying self-signed cert
by wodel youchi 24 Oct '23

24 Oct '23

Hi, From the beginning I had kolla_verify_tls_backend: "no" in globals.yml The weird thing is that the openstack cli works fine. I even created a new user with admin role, I get the same behavior. Horizon does not connect, the cli works. I activated the debug mode on keystone [root@rscdeployer ~]# cat /etc/yogakolla/config/keystone.conf [DEFAULT] debug = True insecure_debug= True But nothing in the log file, when I try to login via horizon, I don't get anything on keystone.log. I tested with a wrong password to see the behavior of the platform, and this is what I got on keystone.log : - Openstack CLI with wrong pass, I got : 2023-10-22 13:51:02.344 43 WARNING keystone.server.flask.application [req-73100d88-8357-42ce-8865-e36c34a9bfa9 - - - - -] Authorization failed. The request you have made requires authentication. from 10.10.3.16: keystone.exception.Unauthorized: The request you have made requires authentication. - Openstack Horizon with wrong pass, I got : Nothing How can I follow up this, how can I be sure that it's not a horizon problem or something else? Regards. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> Le mer. 18 oct. 2023 à 13:17, Kaster, Jörn <Joern.Kaster(a)epg.com> a écrit : > Hi wodel, > nice to hear that the patch helps you. > > With the keystone problem i can't help, but i think the certs are correct. > Two thoughts about that. > > - If you have in the respective configurations of the OpenStack > Services the IP address instead of any DNS Name configured (here is this > the case) then the certificates don't need the dns name in it. > - Could you please look for any error Messages in the keystone logs > and also check if you can establish a connection to the keystone on the > mentioned port with openssl s_client. If so, it could be possible that you > have to disable the certificate verification in the deployment. > > > ------------------------------ > *Von:* wodel youchi <wodel.youchi(a)gmail.com> > *Gesendet:* Mittwoch, 18. Oktober 2023 11:55 > *An:* Kaster, Jörn <Joern.Kaster(a)epg.com> > *Cc:* OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > *Betreff:* Re: [kolla-ansible][yoga] Cannot authenticate to openstack > after deploying self-signed cert > > > OUTSIDE-EPG! > > Thanks Jörn, it worked for cloudkitty, after applying the patch the > deployment went well. But : > > - I still can't access the web console : An error occurred authenticating. > Please try again later. > > - in cloudkitty-processor.log I am still having : > 2023-10-18 10:46:25.271 8106 WARNING keystoneauth.identity.generic.base > [-] Failed to discover available identity versions when contacting > https://dinternal.cloud.domain.tld:35357. Attempting to parse version > from URL.: keystoneauth1.exceptions.connection.SSLError: SSL exception > connecting to https:// dinternal.cloud.domain.tld :35357: > HTTPSConnectionPool(host=' dinternal.cloud.domain.tld ', port=35357): Max > retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: > CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897)'),)) > > > When generating the self-signed certificate, I noticed that the process > had generated : > - two haproxy certificates, one for the internet with the external FQDN > and the second for internal communication with the local internal FQDN. > > - It also generated a backend certificate, that contains only the IP > addresses of the 03 controllers as Subject Alternate Names without any > mention of the domain I am using, is this correct? > > [root@rscdeployer ~]# openssl x509 -noout -text -in > /etc/yogakolla/certificates/backend-cert.pem > Certificate: > Data: > Version: 3 (0x2) > Serial Number: > 1c:66:7e:37:85:cf:ca:1c:da:42:f6:f1:1f:dc:1e:97..... > Signature Algorithm: sha256WithRSAEncryption > Issuer: CN = KollaTestCA > Validity > Not Before: Oct 17 15:04:26 2023 GMT > Not After : Oct 15 15:04:26 2025 GMT > Subject: C = US, ST = NC, L = RTP, OU = kolla > Subject Public Key Info: > Public Key Algorithm: rsaEncryption > RSA Public-Key: (2048 bit) > Modulus: > ..... > ..... > e6:23:a4:7f:30:74:ac:0c:2d:22:00:95:b6:ab:20: > 98:6b > Exponent: 65537 (0x10001) > X509v3 extensions: > > *X509v3 Subject Alternative Name: IP Address:10.10.3.5, IP > Address:10.10.3.9, IP Address:10.10.3.13* > Signature Algorithm: sha256WithRSAEncryption > 36:86:cb:b4:9a:fe:33:0d:ff:af:87:5e:00:9d:69:4e:32:21: > > > > Regards. > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > Virus-free.www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_-6993449584919071302_x_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > Le mer. 18 oct. 2023 à 07:12, Kaster, Jörn <Joern.Kaster(a)epg.com> a > écrit : > > Hello wodel, > the problem with cloudkitty deployment with self signed certs could > resolve to the following bugreport [1]. > > [1] https://bugs.launchpad.net/kolla-ansible/+bug/1998831 > Bug #1998831 “CloudKitty bootstrap fails when using internal TLS...” : > Bugs : kolla-ansible > <https://bugs.launchpad.net/kolla-ansible/+bug/1998831> > When InfluxDB is behind HAProxy's internal TLS, CloudKitty fails to > bootstrap its InfluxDB database with the following error: TASK [cloudkitty > : Creating Cloudkitty influxdb database] > *************************************************************************************************************************** > fatal: [controller01 -> controller01]: FAILED! => changed=false action: > influxdb_database msg: ('Connection aborted.', RemoteDisconnected('Remote > end closed connection without response... > bugs.launchpad.net > > > ------------------------------ > *Von:* wodel youchi <wodel.youchi(a)gmail.com> > *Gesendet:* Mittwoch, 18. Oktober 2023 01:33 > *An:* OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > *Betreff:* [kolla-ansible][yoga] Cannot authenticate to openstack after > deploying self-signed cert > > > OUTSIDE-EPG! > > Hi, > > Our ssl certificate expired a couple of days ago, and we started > experiencing failed login, to workaround the problem rapidly we decided to > deploy the self-signed certificates generated by kolla. > > We generated the certificates then we did a reconfigure, but still the > problem remains : An error occurred authenticating. Please try again later. > > on horizon.log we have : > [Wed Oct 18 00:25:55.379383 2023] [wsgi:error] [pid 103:tid > 140182314505984] [remote 10.10.3.5:40848] Login failed for user "admin" > using domain "default", remote address 10.10.3.5 > > The openstack command line works fine. > > How can we debug this? > > The second problem we have is with cloudkitty that refuses to reconfigure > with the generated self-signed certificate, we had to ignore it from the > reconfiguration process by putting the cloudkitty variable to no before > restarting the reconfigure process. > > How can we debug this? > > > > > Regards. > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > Virus-free.www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_-6993449584919071302_x_m_9147058937014271290_x_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > >

2 4

[ironic] [baremetal-sig] Feedback on ironic "ilo" or "ilo5" driver features
by Nisha Agarwal 24 Oct '23

24 Oct '23

Hello, We had a discussion with baremetal-sig in PTG yesterday(23rd Oct 2023). Below are some of the ironic ilo driver features discussed and the summary of our understanding: - In-band and OOB RAID configuration and disk erase : · Cleaning steps are invoked via operator-written scripts for RAID, disk erase etc. The OS commands are directly invoked in the scripts for these tasks. · We are not clear if iLO driver inband RAID feature is used or not. · OOB RAID configuration and disk-erase is not used. - Out-of-Band Inspection: · We are not clear if OOB inspection is used or not. · LLDP data based inventory is most desired. Not all BMCs provide this data today. · Inspection is also used for getting the DHCP information especially, hostname. - UEFI HTTPS boot: · UEFI HTTPS boot feature of ilo driver is not used. · vMedia is the preferred way of deploy in the field. · UEFI HTTP deploy is proposed this cycle in redfish driver. · Some customers use PXE boot. - Smart Update Manager (SUM)-based firmware update: · Firmware update feature of ilo drivers is not used, rather redfish driver is used. Above is our understanding from the discussion in the baremetal-sig operator in PTG. Please correct/clarify our understanding. Basically, we are trying to figure out if any of the following ilo driver features are used : In-band and out-of-band RAID configuration In-band and out-of-band diskerase UEFI-HTTPS boot One button secure erase Smart Update Manager (SUM)-based firmware update Updating security parameters as manual cleaning step GPU hardware inspection We like to also know if proliantutils is used separately as a hardware manager or independently for any of the OOB/Inband features. Regards Nisha

1 0

[Octavia] cancelling meeting Oct 25
by Gregory Thiemonge 24 Oct '23

24 Oct '23

Hi Folks, As discussed in the previous meeting, tomorrow's meeting is cancelled. See you at the vPTG! Gregory

1 0

[cinder][PTG] Cinder 2024.1 Caracal PTG
by Rajat Dhasmana 24 Oct '23

24 Oct '23

Hi All, We will be conducting the Cinder 2024.1 (Caracal) PTG next week. I've finalized the schedule for Cinder PTG here[1]. Also I've booked slots from Tuesday to Friday 1300-1700 UTC[2]. Following are the details of the event: Dates: 24 October (Tuesday) - 27 October (Friday), 2023 Time: 1300 - 1700 UTC Room: Cactus Video conference Tool: Zoom (Link can be found on the PTG page[2] by clicking on Cinder slot) Following are some of the interesting sessions to attend: *Operator Hour:* Wednesday, 1400-1500 UTC *Nova-Cinder Cross Project: *Wednesday, 1600-1700 UTC *Manila-Cinder Cross Project: *Thursday, 1600-1700 UTC *Team Photo: *Wednesday, 1345-1400 UTC We have the Friday slot vacant so if you feel like adding a topic, add it to the planning etherpad[3] and we can adjust it on Friday's schedule. See you at the PTG next week! [1] https://etherpad.opendev.org/p/caracal-ptg-cinder [2] https://ptg.opendev.org/ptg.html [3] https://etherpad.opendev.org/p/caracal-ptg-cinder-planning Thanks Rajat Dhasmana

1 1

RE: openstack-discuss Digest, Vol 60, Issue 51 Multinode Cluster setup
by Asma Naz Shariq 24 Oct '23

24 Oct '23

Dear all, I want to deployed Openstack through kolla-ansible release zed. The cluster architecture is as follows: 1- Controller Node same as Network Node. 2- Compute Node same as Storage Node. On Controller Node, I have followed all the steps mentioned at https://docs.openstack.org/project-deploy-guide/kolla-ansible/zed/quickstar… and set the hosts name with ip at /etc/hosts on controller node to resolve the compute node. When I tried to check the connectivity of controller-node with compute node, it encountered an error with: Controller Node IP | FAILED! => { "msg": "Missing sudo password" } localhost | SUCCESS => { "ansible_facts": { "discovered_interpreter_python": "/usr/bin/python3" }, "changed": false, "ping": "pong" } Compute Node IP | FAILED! => { "msg": "Missing sudo password Can anyone guide me how to resolve this error, and setup multi node environment to which steps should I follow to make baseline cluster of one controller node and one compute node. Thanks, -----Original Message----- From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Sent: Tuesday, October 24, 2023 9:42 AM To: openstack-discuss(a)lists.openstack.org Subject: openstack-discuss Digest, Vol 60, Issue 51 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. [ptls] [tc] 2023 OpenStack Deployment Data (Allison Price) 2. Re: [neutron][openvswitch][antelope] Bridge eth1 for physical network provider does not exist (Sławek Kapłoński) 3. Environmental Sustainability WG goes to the PTG! (Kendall Nelson) 4. [tacker] Cancelling IRC meetings (Yasufumi Ogawa) 5. Re: openstack Vm shutoff by itself (AJ_ sunny) ---------------------------------------------------------------------- Message: 1 Date: Mon, 23 Oct 2023 15:16:05 -0500 From: Allison Price <allison(a)openinfra.dev> Subject: [ptls] [tc] 2023 OpenStack Deployment Data To: openstack-discuss <openstack-discuss(a)lists.openstack.org> Message-ID: <AB576C9A-95CB-4BCD-9215-0AC1D3E64A25(a)openinfra.dev> Content-Type: text/plain; charset=us-ascii Hi everyone, Apologies for sending this during the PTG as I intended to send this prior, but below is a link to the anonymized data including responses to many project or TC contributed questions. I have removed a significant number of fields to preserve the anonymity of the organizations, but if there is a particular data point that would help your team, please let me know. Cheers, Allison https://docs.google.com/spreadsheets/d/1ehlabuqOnNK4M7xtN1GXvhLoeHn4JBaISih… ------------------------------ Message: 2 Date: Mon, 23 Oct 2023 22:46:23 +0200 From: Sławek Kapłoński <skaplons(a)redhat.com> Subject: Re: [neutron][openvswitch][antelope] Bridge eth1 for physical network provider does not exist To: "openstack-discuss(a)lists.openstack.org" <openstack-discuss(a)lists.openstack.org> Cc: "ddorra(a)t-online.de" <ddorra(a)t-online.de> Message-ID: <5895770.MhkbZ0Pkbq@p1gen4> Content-Type: multipart/signed; boundary="nextPart1790705.VLH7GnMWUR"; micalg="pgp-sha256"; protocol="application/pgp-signature" Hi, You need to create bridge (e.g. br-ex), add your eth1 to that bridge and put name of the bridge in the bridge_mapping. Dnia poniedziałek, 23 października 2023 21:44:43 CEST ddorra(a)t-online.de pisze: > > Hello, > > I'm installing Openstack Antelope with network option 2 ( following > https://docs.openstack.org/neutron/2023.2/install/compute-install-opti > on2-ubuntu.html) The interface name of the provider network is eth1, > so I put this to bridge_mappings. > The local IP is from the management network. > > #------------------------------------------------------ > # /etc/neutron/plugins/ml2/openvswitch_agent.ini > # > [DEFAULT] > [agent] > [dhcp] > [network_log] > [ovs] > bridge_mappings = provider:eth1 > [securitygroup] > enable_security_group = true > firewall_driver = openvswitch > [vxlan] > local_ip = 192.168.2.71 > l2_population = true > #-------------------------------------------------------- > > However, the neutron log complains that bridger eth1 does not exist. > Launching of instances fails > neutron-openvswitch-agent.log: > 2023-10-23 19:26:00.062 17604 INFO os_ken.base.app_manager [-] > instantiating app os_ken.app.ofctl.service of OfctlService > 2023-10-23 19:26:00.062 17604 INFO > neutron.agent.agent_extensions_manager > [-] Loaded agent extensions: [] > 2023-10-23 19:26:00.108 17604 INFO > neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_brid > ge [-] Bridge br-int has datapath-ID 00005e65b1943a49 > 2023-10-23 19:26:02.438 17604 INFO > neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] > Mapping physical network provider to bridge eth1 vvvvvvv > 2023-10-23 19:26:02.438 17604 ERROR > neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] > Bridge > eth1 for physical network provider does not exist. Agent terminated! > ^^^^^^^ > 2023-10-23 19:26:03.914 17619 INFO neutron.common.config [-] Logging > enabled! > 2023-10-23 19:26:03.914 17619 INFO neutron.common.config [-] > /usr/bin/neutron-openvswitch-agent version 20.4.0 > 2023-10-23 19:26:03.914 17619 INFO os_ken.base.app_manager [-] loading > app > neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_oske > napp > > ----------------------------------------- > Additional information > root@control:/var/log/neutron# openstack network list > +--------------------------------------+----------+--------------------------------------+ > | ID | Name | Subnets | > +--------------------------------------+----------+--------------------------------------+ > | 32f53edc-a394-419f-a438-a664183ee618 | doznet | > e38e25c2-4683-48fb-a7a0-7cbd7d276ee1 | > | 74e3ee6a-1116-4ff6-9e99-530c3cbaef28 | provider | > 2d3c3de4-9a0d-4a21-9af1-8ecb9f6f16d5 | > +--------------------------------------+----------+--------------------------------------+ > root@control:/var/log/neutron# > > root@compute1:/etc/neutron/plugins/ml2# ip a > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel > state UP group default qlen 1000 link/ether 08:00:27:9f:c7:89 brd > ff:ff:ff:ff:ff:ff inet 192.168.2.71/24 brd 192.168.2.255 scope global > eth0 valid_lft forever preferred_lft forever > inet6 fe80::a00:27ff:fe9f:c789/64 scope link valid_lft forever > preferred_lft forever > 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel > state UP group default qlen 1000 link/ether 08:00:27:91:60:58 brd > ff:ff:ff:ff:ff:ff inet 10.0.0.71/24 brd 10.0.0.255 scope global eth1 > valid_lft forever preferred_lft forever > inet6 fe80::a00:27ff:fe91:6058/64 scope link valid_lft forever > preferred_lft forever > 4: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN > group default qlen 1000 link/ether da:3b:3a:a0:59:97 brd > ff:ff:ff:ff:ff:ff > 5: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group > default qlen 1000 link/ether 5e:65:b1:94:3a:49 brd ff:ff:ff:ff:ff:ff > 6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue > state DOWN group default qlen 1000 link/ether 52:54:00:53:87:59 brd > ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope > global virbr0 valid_lft forever preferred_lft forever > > > What are the proper settings? > Any help appreciated > Dieter > > > -- Slawek Kaplonski Principal Software Engineer Red Hat-------------- next part -------------- A message part incompatible with plain text digests has been removed ... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: This is a digitally signed message part. ------------------------------ Message: 3 Date: Mon, 23 Oct 2023 16:36:20 -0500 From: Kendall Nelson <kennelson11(a)gmail.com> Subject: Environmental Sustainability WG goes to the PTG! To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Message-ID: <CAJ6yrQgbdvFW7NcUGJ5zLyXagx=hMt6R7ib0tk=1Y+sm06MY=w(a)mail.gmail.com> Content-Type: multipart/alternative; boundary="000000000000e3ee26060869044d" Hello Everyone! Last minute, but I wanted to make sure you saw that we are planning to meet at the PTG, tomorrow (Tuesday Oct 24th) from 13:00 UTC. I have the room booked for two hours, but I don't think we will need all of that time. If there are topics you would like to discuss, please add them to the agenda[1]. Hope to see you there! -Kendall Nelson [1] https://etherpad.opendev.org/p/oct2023-ptg-env-sus

1 0