- openstack-discuss - lists.openstack.org

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

[swift][ptg] Ops Feedback Session - 25th October at 1300 UTC
by Matthew Oliver 24 Oct '23

24 Oct '23

As we've done in PTGs past, we're getting devs and ops together to talk about Swift: what's working, what isn't, and what would be most helpful to improve. We're meeting in Newton (https://www.openstack.org/ptg/rooms/newton) on Wednesday at 13:00UTC -- if you run a Swift cluster, we hope to see you there! Even if you can't make it, we'd appreciate it if you can offer some feedback on the etherpad ( https://etherpad.opendev.org/p/swift-caracal-ops-feedback) This has always been a highlight at every PTG for us swift devs. Have your say and help make Swift even better! Matt

1 0

[tacker] Cancelling IRC meetings
by Yasufumi Ogawa 24 Oct '23

24 Oct '23

Hi team, I'd like to skip today's IRC meeting since we are going to have the vPTG. Thanks, Yasufumi

1 0

Environmental Sustainability WG goes to the PTG!
by Kendall Nelson 23 Oct '23

23 Oct '23

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

[neutron] Meetings cancelled this week
by Brian Haley 23 Oct '23

23 Oct '23

Hi Neutrinos, I am cancelling the Neutron and Neutron Drivers meetings this week as we have the vPTG meetings. Please add any topics you would like to discuss to the etherpad, https://etherpad.opendev.org/p/oct2023-ptg-neutron Sorry I forgot to send this sooner. -Brian

1 0

[openstack-ansible] vPTG and Operator hours
by Dmitriy Rabotyagov 23 Oct '23

23 Oct '23

Hi folks, I am glad to announce the upcoming vPTG for OpenStack-Ansible team that will happen on Tuesday, October 24 from 14:00 till 17:00 UTC. Our team will also have an operator hours on Monday, October 23 from 17:00 till 18:00 UTC. All virtual events will take place in the Grizzly room [1]. Please, also check the vPTG agenda in the etherpad [2] and feel free to add topics for the discussion. [1] https://www.openstack.org/ptg/rooms/grizzly [2] https://etherpad.opendev.org/p/osa-caracal-ptg

2 1

[neutron] Bug deputy report for week of October 16th
by Brian Haley 23 Oct '23

23 Oct '23

Hi, I was Neutron bug deputy last week. Below is a short summary about the reported bugs. -Brian Critical bugs ------------- * None High bugs --------- * https://bugs.launchpad.net/neutron/+bug/2039417 - [master][stable/2023.2][functional] test_maintenance.TestMaintenance tests fails randomly - Needs owner Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/2039550 - [IPAM] During port bulk creation, if a "fixed_ip" request is incorrect, the previous IPAM allocations generated are not deleted - https://review.opendev.org/c/openstack/neutron/+/898549 * https://bugs.launchpad.net/neutron/+bug/2039586 - [CI] Update the cirros image versions - Many patches opened * https://bugs.launchpad.net/neutron/+bug/2039940 - test_resize_volume_backed_server_confirm which fails randomly with Kernel panic - Similar to https://bugs.launchpad.net/tempest/+bug/1888224 - Not sure what neutron can do Low bugs -------- * None Misc bugs --------- * https://bugs.launchpad.net/neutron/+bug/2039553 - dhcp-agent can not interact with neutron-server after neutron-server restarted - Asked for more information * https://bugs.launchpad.net/neutron/+bug/2039812 - [N-D-R] The dynamic routing service is not resilient to infrastructure outage - Duplicate of https://bugs.launchpad.net/neutron/+bug/2006145 Wishlist bugs ------------- * None

1 0

[sunbeam][ptg] Caracal vPTG
by James Page 23 Oct '23

23 Oct '23

Hi Sunbeamers! We were a little late to sign up but we are participating in the vPTG for Caracal this week. I've booked us 3 hours on Wednesday from 1300-1700 UTC [0]; please add topics for discussion to the etherpad [1]. I've ensured we don't overlap with the OpenStack Charms sessions as I suspect we may have quite a bit of crossover between participants. Thanks James -- [0] https://ptg.opendev.org/ptg.html [1] https://etherpad.opendev.org/p/oct2023-ptg-sunbeam

1 0

[nova][ptg][ops] Nova at the vPTG + our etherpad is broken \o/
by Sylvain Bauza 23 Oct '23

23 Oct '23

Hey folks, tl;dr: as a reminder, all nova sessions are marked in https://ptg.opendev.org/ptg.html I was about to remind you of the schedule for all our nova PTG sessions when I just figured that our etherpad got trashed. Until some admin is able to restore it, please find the agenda in some stored revision https://etherpad.opendev.org/p/nova-caracal-ptg/timeslider#13560 Operators, please gently note that we'll have a nova-operator-hour on Tuesday 1500UTC. As a reminder, this timeslot is dedicated to listening to your experiences and pain points so if you really would like to contribute to the Nova community by providing your insights, this is the right time ! This time, we'll be using the OIF Meetpad instance instead of Zoom. The URL is https://meetpad.opendev.org/nova-caracal-ptg The other Nova sessions will be Tuesday to Friday, 1pm to 5pm UTC. Should you want to attend, feel free to ping me (bauzas) on IRC #openstack-nova or drop me an email (to this address) until our etherpad becomes unstuck in order to let me know your availabilities and I'll try to sort our topics so that you could attend. Later, I'll add, like previously done, a courtesy ping list for every topic in the etherpad so you could register by writing your IRC nick. As a reminder, I'll also try hard to provide the status of the topics we're currently discussing and the next ones in https://ptg.opendev.org/ptg.html. Thanks, -Sylvain (who hopes the etherpad issue got fixed soon)

1 1

[kolla] Upgrading across supported OS's
by Aidan Collins 23 Oct '23

23 Oct '23

Hello! I have a question about the kola upgrade process. Thanks in advance. I am attempting to upgrade our kola version (Victoria to wallaby). The docs suggest it should entail getting the new version of the kolla-ansible pkg & deps, updating the config files & then running "kolla-ansible upgrade". However, what do we do if version N & version N+1 of kolla-ansible don't support the same host OS version? Thanks again -aidan

3 2