August 2023 - openstack-discuss - lists.openstack.org

Re: Kayobe VLAN & bond configuration
by Stefan Pinter 21 Aug '23

21 Aug '23

Hi again! After rebooting the server an cleaning up everything in /etc/systemd/network/ it does work again (kayobe overcloud host configure) but I am afraid to run “kayobe overcloud service deploy”. Can anyone confirm that the configuration might be correct or has an idea about what happened in the network there? Multicast storm? Broadcast storm? Troubles with STP? Thank you and best wishes Stefan ________________________________ BearingPoint GmbH Sitz: Wien Firmenbuchgericht: Handelsgericht Wien Firmenbuchnummer: FN 175524z The information in this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.

3 4

[nova-api] Inject public key without create key pair in nova ?
by Pureewat Kaewpoi 21 Aug '23

21 Aug '23

Hi OpenStack Community We have some requirements that need to create instance via API. However nova-api is accept only key_name of key pair created earlier. Can we create instance by passing only public key data without creating a key pair in nova ? Thank you.

4 6

[glance][kolla] importing images on filesystem without copy?
by Rob Jefferson 21 Aug '23

21 Aug '23

Folks, I'm trying to wrap my brain around whether this is possible. Suppose I've configured Glance to use a filesystem backend. Would I be able to point Glance at a directory of existing images, and have it import the images into OpenStack (thus populating the database) without having to copy them? It seems fairly redundant to have the images on the filesystem, and to make copies as part of the creation process. Looking around in the documentation, it seems that this may not be possible, but I'm not sure if there's an alternate path or if what I'm asking is ill-posed. Any advice would be useful. Thanks, Rob

3 2

[charms] Nominate Martin Kalcok for charms-core
by Frode Nordahl 21 Aug '23

21 Aug '23

Hello all, I would like to nominate Martin Kalcok for charms-core. He has been part of the extended charms teams for some time now, and has provided many contributions to OpenStack, Ceph and OVN charms [0]. He is diligent and thorough in his contributions, and has recently become a full time member of the focused OVN team. 0: https://review.opendev.org/q/owner:martin.kalcok%2540canonical.com -- Frode Nordahl

5 4

Unable to Live/Cold migrate instances that have ceph root and secondary netapp storage devices | Wallaby
by Swogat Pradhan 21 Aug '23

21 Aug '23

Hi, I have an instance that has disk /dev/vda present in ceph and the rest of the 6 volumes (10 TB) each on netapp. I am trying to migrate the VM to another host but it is failing to migrate with error volume not found like below: 2023-08-21 09:22:31.852 7 WARNING os_brick.initiator.connectors.iscsi [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] Couldn't find iSCSI nodes because iscsiadm err: iscsiadm: No records found : os_brick.exception.VolumeDeviceNotFound: Volume device not found at . 2023-08-21 09:22:31.866 7 WARNING os_brick.initiator.connectors.iscsi [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] iscsiadm stderr output when getting sessions: iscsiadm: No active sessions. : os_brick.exception.VolumeDeviceNotFound: Volume device not found at . 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] Exception during message handling: os_brick.exception.VolumeDeviceNotFound: Volume device not found at . 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/exception_wrapper.py", line 72, in wrapped 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server context, exc, binary) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise self.value 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/exception_wrapper.py", line 63, in wrapped 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return f(self, context, *args, **kw) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/compute/utils.py", line 1437, in decorated_function 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 212, in decorated_function 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server kwargs['instance'], e, sys.exc_info()) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise self.value 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 200, in decorated_function 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 8288, in pre_live_migration 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server bdm.save() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise self.value 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 8249, in pre_live_migration 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server migrate_data) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/driver.py", line 10343, in pre_live_migration 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server self._connect_volume(context, connection_info, instance) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/driver.py", line 1808, in _connect_volume 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server vol_driver.connect_volume(connection_info, instance) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/volume/iscsi.py", line 64, in connect_volume 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server device_info = self.connector.connect_volume(connection_info['data']) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/utils.py", line 154, in trace_logging_wrapper 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py", line 391, in inner 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/iscsi.py", line 524, in connect_volume 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server self._cleanup_connection(connection_properties, force=True) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise self.value 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/iscsi.py", line 518, in connect_volume 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return self._connect_single_volume(connection_properties) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/utils.py", line 78, in _wrapper 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return r(f, *args, **kwargs) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 409, in call 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server do = self.iter(retry_state=retry_state) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 368, in iter 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise retry_exc.reraise() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 186, in reraise 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise self.last_attempt.result() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib64/python3.6/concurrent/futures/_base.py", line 425, in result 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return self.__get_result() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib64/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise self._exception 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 412, in call 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server result = fn(*args, **kwargs) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/iscsi.py", line 597, in _connect_single_volume 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise exception.VolumeDeviceNotFound(device='') 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server os_brick.exception.VolumeDeviceNotFound: Volume device not found at . 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server 2023-08-21 09:22:34.678 7 INFO nova.virt.block_device [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] [instance: 5520dbd7-8f12-4041-bd8c-65b4b55b0452] Attempting to driver detach volume a005a015-0bb2-498e-9068-ac14570a5f2e from mountpoint /dev/vda 2023-08-21 09:22:34.680 7 WARNING nova.virt.block_device [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] [instance: 5520dbd7-8f12-4041-bd8c-65b4b55b0452] Detaching volume from unknown instance 2023-08-21 09:22:34.682 7 WARNING nova.virt.libvirt.driver [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] [instance: 5520dbd7-8f12-4041-bd8c-65b4b55b0452] During detach_volume, instance disappeared.: nova.exception.InstanceNotFound: Instance 5520dbd7-8f12-4041-bd8c-65b4b55b0452 could not be found. 2023-08-21 09:22:34.707 7 INFO nova.virt.block_device [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] [instance: 5520dbd7-8f12-4041-bd8c-65b4b55b0452] Attempting to driver detach volume 01b9b430-9cfd-43b1-b674-b6fb830ee511 from mountpoint /dev/vdb 2023-08-21 09:22:34.708 7 WARNING nova.virt.block_device [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] [instance: 5520dbd7-8f12-4041-bd8c-65b4b55b0452] Detaching volume from unknown instance 2023-08-21 09:22:34.710 7 WARNING nova.virt.libvirt.driver [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] [instance: 5520dbd7-8f12-4041-bd8c-65b4b55b0452] During detach_volume, instance disappeared.: nova.exception.InstanceNotFound: Instance 5520dbd7-8f12-4041-bd8c-65b4b55b0452 could not be found. Server show : +-------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+ | OS-DCF:diskConfig | AUTO | | OS-EXT-AZ:availability_zone | Watson | | OS-EXT-SRV-ATTR:host | overcloud-novacompute-0.bdxworld.com | | OS-EXT-SRV-ATTR:hostname | hkg2-cctv-archive-server-2 | | OS-EXT-SRV-ATTR:hypervisor_hostname | overcloud-novacompute-0.bdxworld.com | | OS-EXT-SRV-ATTR:instance_name | instance-0000012f | | OS-EXT-SRV-ATTR:kernel_id | | | OS-EXT-SRV-ATTR:launch_index | 0 | | OS-EXT-SRV-ATTR:ramdisk_id | | | OS-EXT-SRV-ATTR:reservation_id | r-mdrfy13i | | OS-EXT-SRV-ATTR:root_device_name | /dev/vda | | OS-EXT-SRV-ATTR:user_data | None | | OS-EXT-STS:power_state | Running | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2023-01-05T09:49:54.000000 | | OS-SRV-USG:terminated_at | None | | accessIPv4 | | | accessIPv6 | | | addresses | HKG2-CCTV=192.168.240.14 | | config_drive | True | | created | 2023-01-05T09:49:46Z | | description | HKG2-CCTV-Archive-server-2 | | flavor | disk='150', ephemeral='0', extra_specs.hw:cpu_cores='10', extra_specs.hw:cpu_sockets='2', original_name='CCTV-VM-Flavor', ram='16384', swap='0', | | | vcpus='10' | | hostId | 570b5ef66c44d3f80a1a498c9dbd8b9a2b690a1aee748bc9cb2cf6fb | | host_status | UP | | id | 5520dbd7-8f12-4041-bd8c-65b4b55b0452 | | image | N/A (booted from volume) | | key_name | None | | locked | False | | locked_reason | None | | name | HKG2-CCTV-Archive-server-2 | | progress | 0 | | project_id | 265571cce0b54251b17ace88630b5e46 | | properties | | | security_groups | name='CCTV services Incoming' | | | name='CCTV services Outgoing' | | server_groups | [] | | status | ACTIVE | | tags | | | trusted_image_certificates | None | | updated | 2023-08-21T09:22:35Z | | user_id | ff69985eea81fe6f11e9caa3f242623cbddc7ce21cdd864c9585d793533acb9e | | volumes_attached | delete_on_termination='False', id='a005a015-0bb2-498e-9068-ac14570a5f2e' | | | delete_on_termination='False', id='01b9b430-9cfd-43b1-b674-b6fb830ee511' | | | delete_on_termination='False', id='a385a416-1d37-4111-b7ae-f182a54aeaef' | | | delete_on_termination='False', id='95bafa69-b7cc-4d35-9002-723ca556a570' | | | delete_on_termination='False', id='b5091e83-2afb-457c-abf8-ed855156b59f' | | | delete_on_termination='False', id='0e9762bd-5229-433d-825e-6c7a77c6927c' | | | delete_on_termination='False', id='9a00e144-8755-48d5-8907-7fa499172371' | +-------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+ Please suggest how I can migrate the instance. With regards, Swogat Pradhan

1 1

[election][openstack-ansible]
by Dmitriy Rabotyagov 21 Aug '23

21 Aug '23

Hello everyone! I would like to announce my candidacy for the role of PTL of OpenStack-Ansible during the 2024.1 (Caracal) cycle. For the next cycle I want to pay attention on the following topics: * Updating documentation to correspond new defaults * Keep up with latest supported versions of infrastructure software, like MariaDB, RabbitMQ and Ansible * Promote the project on various events and ensure project compatibility with various vendors * Perform clean-up of old functional testing and test repo and finally make progress on re-implementing functional testing of various scenarios for individual repositories. Thank you for your consideration!

1 0

[neutron] Bug deputy report Aug 14 - Aug 20
by Oleg Bondarev 21 Aug '23

21 Aug '23

Hello Neutron Team, Here's the bug report for the week of Aug 14 - Aug 20: Critical: - https://bugs.launchpad.net/neutron/+bug/2031415 - neutron-tempest-plugin-openvswitch* jobs are failing or timing-out Edit - Fixed by haleyb: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/891550 - https://bugs.launchpad.net/neutron/+bug/2031526 - [ndr] "neutron-tempest-plugin-dynamic-routing" failing - Fixed on os-ken side by j-harbott: https://review.opendev.org/c/openstack/os-ken/+/891658 - waits for os-ken release - https://bugs.launchpad.net/neutron/+bug/2031971 - Rally jobs failing in neutron gate - Invalid - fixed on Rally side by haleyb: https://review.opendev.org/c/openstack/rally-openstack/+/892052 High: - Medium: - https://bugs.launchpad.net/neutron/+bug/2031646 - [sqlalchemy-20] "test_has_alive_neutron_server" failing with SQLAlchemy 2.0 - In progress: https://review.opendev.org/c/openstack/neutron/+/891691 - assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2031656 - Shared networks can be returned as "shared=False" in the API request - Confirmed - assigned to ralonsoh Low: - https://bugs.launchpad.net/neutron/+bug/2031520 - [OVN] Document the router port location (dvr, centralized) depending on network type, load balancing, port forwarding, etc - Triaged - unassigned Thanks, Oleg

1 0

[OSA][NEUTRON]
by Murilo Morais 19 Aug '23

19 Aug '23

Good evening everyone! When using Tenant Network I can't make the instances communicate when they are on different hosts, I believe I'm forgetting to configure something related to network_hosts, but I'm not sure what. It wasn't clear to me exactly the difference between "network_hosts", "network-infra_hosts" and "network-agent_hosts". I'm using the following configuration: openstack_user_config.yml: cidr_networks: container: ... storage: ... used_ips: [...] global_overrides: internal_lb_vip_address: ... external_lb_vip_address: ... management_bridge: br-mgmt no_containers: false provider_networks: - network: container_bridge: br-mgmt container_interface: eth1 container_type: veth ip_from_q: container is_container_address: true type: raw group_binds: - all_containers - hosts - network: container_bridge: br-provider container_type: veth type: vlan range: "100:200" network_interface: "eno2" net_name: vlan group_binds: - neutron_openvswitch_agent - network: container_bridge: "br-flat" container_type: "veth" type: "flat" network_interface: "trunk.103" net_name: "router" group_binds: - neutron_openvswitch_agent - network: container_bridge: br-storage container_interface: eth2 container_type: veth ip_from_q: storage type: raw group_binds: - glance_api - cinder_api - cinder_volume - nova_compute - ceph-mon - ceph-osd shared-infra_hosts: dcn2: ip: ...2 coordination_hosts: dcn2: ip: ...2 repo-infra_hosts: dcn2: ip: ...2 haproxy_hosts: dcn2: ip: ...2 identity_hosts: dcn2: ip: ...2 storage-infra_hosts: dcn2: ip: ...2 storage_hosts: dcn2: ip: ...2 image_hosts: dcn2: ip: ...2 placement-infra_hosts: dcn2: ip: ...2 compute-infra_hosts: dcn2: ip: ...2 dashboard_hosts: dcn2: ip: ...2 network_hosts: dcn2: ip: ...2 compute_hosts: dcn2: ip: ...2 dcn3: ip: ...3 dcn8: ip: ...14 dcn10: ip: ...19 Example to upload the instances: network create network_test subnet create --network network_test --subnet-range 192.168.0.0/24 subnet_test server create --flavor m1.large --image debian-11-genericcloud-amd64-20230601-1398 --network network_test --key-name my_key --use-config-drive debian_test1 server create --flavor m1.large --image debian-11-genericcloud-amd64-20230601-1398 --network network_test --key-name my_key --use-config-drive debian_test2 If for some reason any of them go up on different hosts, even configuring the IP manually, they don't communicate, but the instant they are on the same host the ping starts to work.

2 1

Re: [OpenInfra Foundation Support] Re: Ajuda - Help me! Info.
by Suporte 19 Aug '23

19 Aug '23

Desprezada comunidade!! Poderiam me ajudar? Estou tentando apresentar meu TCC sobre o OpenStak mas estou tendo dificuldades em entender como funciona a ferramenta em relação a múltiplos servidores físicos (cluester). Basicamente queria uma orientação se é possível subir 3 servidores físicos e acessar os recursos unificados em uma aba apenas do Horizon? Amaria um retorno. Atenciosamente | Kind Regards, Mateus Dias Cel.: (11) 96872-8478 E-mail: mateus.dias(a)tektel.com.br Tektel Informática ________________________________ De: Open Infrastructure Foundation <support(a)openstack.zendesk.com> Enviado: segunda-feira, agosto 14, 2023 12:49 PM Para: Suporte <suporte(a)tektel.com.br> Assunto: [OpenInfra Foundation Support] Re: Ajuda - Help me! Info. ##- Please type your reply above this line -## Your request (#46153<https://support.openstack.org/hc/requests/46153>) has been solved. To reopen this request, reply to this email or click the link below: https://support.openstack.org/hc/requests/46153 Allison (OpenInfra Foundation Support) Aug 14, 2023, 10:49 CDT Hi Mateus, Por favor compartilhe esta pergunta na lista de discussão do OpenStack para que a comunidade possa ajudá-lo. https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss Allison This email is a service from OpenInfra Foundation Support. [K20VPL-4E7XM]

2 2

[release] Release countdown for week R-6, Aug 21 - 25
by Thierry Carrez 18 Aug '23

18 Aug '23

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on August 24th. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2023.2 branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (August 31st) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, August 31st. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/2023.2 branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/2023.2 branches are cut for a repo, the ability to approve any necessary backports into those branches for 2023.2 "Bobcat" final release will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 24th, 2023 (R-6 week) Client library freeze: August 31st, 2023 (R-5 week) Bobcat-3 milestone: August 31st, 2023 (R-5 week) Cycle Highlights Due: August 31st, 2023 (R-5 week) Final 2023.2 Bobcat release: October 4th, 2023 -- Thierry Carrez (ttx)

1 0