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/quickstart... 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@lists.openstack.org <openstack-discuss-request@lists.openstack.org> Sent: Tuesday, October 24, 2023 9:42 AM To: openstack-discuss@lists.openstack.org Subject: openstack-discuss Digest, Vol 60, Issue 51 Send openstack-discuss mailing list submissions to openstack-discuss@lists.openstack.org To subscribe or unsubscribe via email, send a message with subject or body 'help' to openstack-discuss-request@lists.openstack.org You can reach the person managing the list at openstack-discuss-owner@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@openinfra.dev> Subject: [ptls] [tc] 2023 OpenStack Deployment Data To: openstack-discuss <openstack-discuss@lists.openstack.org> Message-ID: <AB576C9A-95CB-4BCD-9215-0AC1D3E64A25@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/1ehlabuqOnNK4M7xtN1GXvhLoeHn4JBaISih6... ------------------------------ Message: 2 Date: Mon, 23 Oct 2023 22:46:23 +0200 From: Sławek Kapłoński <skaplons@redhat.com> Subject: Re: [neutron][openvswitch][antelope] Bridge eth1 for physical network provider does not exist To: "openstack-discuss@lists.openstack.org" <openstack-discuss@lists.openstack.org> Cc: "ddorra@t-online.de" <ddorra@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@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@gmail.com> Subject: Environmental Sustainability WG goes to the PTG! To: OpenStack Discuss <openstack-discuss@lists.openstack.org> Message-ID: <CAJ6yrQgbdvFW7NcUGJ5zLyXagx=hMt6R7ib0tk=1Y+sm06MY=w@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