June 2022 - openstack-discuss - lists.openstack.org

[kolla] restart mariadb container on host 1
by Gregory Orange 09 Jun '22

09 Jun '22

Hi all, I wanted to temporarily change a mariadb config in /etc/kolla/mariadb/galera.cnf so I intended to stop mariadb on host 1, make the change, start it again, then repeat in turn for hosts 2 and 3. Upon starting it on host 1, it doesn't rejoin, but creates its own separate cluster. Dutiful really, since logs show: WSREP: 'wsrep-new-cluster' option used, bootstrapping the cluster How do I avoid that? General advice on handling this kind of activity would also be welcome. Thank you, Greg.

2 2

[kolla-ansible][kolla] merge_configs module replacing colon to equal
by Sharath Ck 09 Jun '22

09 Jun '22

Hi, In kolla-ansible, I am using the merge_configs module to merge service configs files. I want to merge api-paste.ini config with my custom changes, however while merging if a line consists of one colon, it is getting replaced with equal sign. merge_configs splits the line by considering colon as delimiter and treats two parts as key and value. Later which will be substituted as key = value. Original */v2.1: oscomputeversion_v2* Merged */v2.1= oscomputeversion_v2 * Below, colon will be 1 and equal will be -1, *def _split_key_value(self, line): colon = line.find(':') equal = line.find('=') if colon < 0 and equal < 0: return self.error_invalid_assignment(line) if colon < 0 or (equal >= 0 and equal < colon): key, value = line[:equal], line[equal + 1:] else: key, value = line[:colon], line[colon + 1:] value = value.strip() if value and value[0] == value[-1] and value.startswith(("\"", "'")): value = value[1:-1] return key.strip(), [value]* I want to keep the config as it is and merge only my custom changes. Please let me know how to achieve this or colon can be escaped somehow. Regards, Sharath Regards, Sharath

3 3

[CLOUDKITTY] presentation used in the forum panels
by Rafael Weingärtner 08 Jun '22

08 Jun '22

Hello CloudKitters! It was a pleasure to meet you guys during the OpenStack summit. Also, it was a good surprise to see that so many people already use CloudKitty. I really hope that we can all collaborate together to keep improving CloudKitty, and making it more and more solid. Attached is the presentation we used during the Forum, so you all can consult this material. Also, as always, if you need some guidance/help/or anything else, let us know. Link for the presentation online: https://docs.google.com/presentation/d/15e37xGKCJoTMwbarrGcSlLpECUkcJ2exazW… -- Rafael Weingärtner

2 1

Re: ERROR openstack [-] Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat.| Openstack tripleo wallaby version
by Lokendra Rathour 08 Jun '22

08 Jun '22

Hi Swogat, Thanks once again. with the files as shown below I am running the overcloud deploy for wallaby using this command: (undercloud) [stack@undercloud ~]$ cat deploy_overcloud_working_1.sh openstack overcloud deploy --templates \ -n /home/stack/templates/network_data.yaml \ -r /home/stack/templates/roles_data.yaml \ -e /home/stack/templates/environment.yaml \ -e /home/stack/templates/environments/network-isolation.yaml \ -e /home/stack/templates/environments/network-environment.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-conductor.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-overcloud.yaml \ -e /home/stack/templates/ironic-config.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \ -e /home/stack/containers-prepare-parameter.yaml (undercloud) [stack@undercloud ~]$ This deployment is on ipv6 using triple0 wallaby, templates, as mentioned below, are generated using rendering steps and the network_data.yaml the roles_data.yaml Steps used to render the templates: cd /usr/share/openstack-tripleo-heat-templates/ ./tools/process-templates.py -o ~/openstack-tripleo-heat-templates-rendered_at_wallaby -n /home/stack/templates/network_data.yaml -r /home/stack/templates/roles_data.yaml *Now if i try adding the related to VIP port I do get the error as:* 2022-05-30 10:37:12.792 979387 WARNING tripleoclient.v1.overcloud_deploy.DeployOvercloud [-] rendering j2 template to file: /home/stack/overcloud-deploy/overcloud/tripleo-heat-templates/puppet/controller-role.yaml 2022-05-30 10:37:12.792 979387 WARNING tripleoclient.v1.overcloud_deploy.DeployOvercloud [-] rendering j2 template to file: /home/stack/overcloud-deploy/overcloud/tripleo-heat-templates/puppet/compute-role.yaml 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud [-] Exception occured while running the command: ValueError: The environment is not a valid YAML mapping data type. 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud Traceback (most recent call last): 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/tripleoclient/command.py", line 34, in run 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud super(Command, self).run(parsed_args) 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/osc_lib/command/command.py", line 39, in run 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud return super(Command, self).run(parsed_args) 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/cliff/command.py", line 185, in run 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud return_code = self.take_action(parsed_args) or 0 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/tripleoclient/v1/overcloud_deploy.py", line 1189, in take_action 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud stack, parsed_args, new_tht_root, user_tht_root) 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/tripleoclient/v1/overcloud_deploy.py", line 227, in create_env_files 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud created_env_files, parsed_args, new_tht_root, user_tht_root) 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/tripleoclient/v1/overcloud_deploy.py", line 204, in build_image_params 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud cleanup=(not parsed_args.no_cleanup)) 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/tripleoclient/utils.py", line 1929, in process_multiple_environments 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud env_path=env_path, include_env_in_files=include_env_in_files) 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/heatclient/common/template_utils.py", line 326, in process_environment_and_files 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud env = environment_format.parse(raw_env) 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/heatclient/common/environment_format.py", line 50, in parse 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud raise ValueError(_('The environment is not a valid ' 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud ValueError: The environment is not a valid YAML mapping data type. 2022-05-30 10:37:14.455 979387 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud 2022-05-30 10:37:14.457 979387 ERROR openstack [-] The environment is not a valid YAML mapping data type. 2022-05-30 10:37:14.457 979387 INFO osc_lib.shell [-] END return value: 1 (undercloud) [stack@undercloud ~]$ This is more of a syntax error where it is not able to understand the passed VIP data file: undercloud) [stack@undercloud ~]$ cat /home/stack/templates/vip-data-default-network-isolation.yaml - dns_name: overcloud network: internal_api - dns_name: overcloud network: external - dns_name: overcloud network: ctlplane - dns_name: overcloud network: oc_provisioning - dns_name: overcloud network: j3mgmt Please advise, also please note that similar templates generated in prior releases such as train/ussuri works perfectly. Please check the list of *templates *files: drwxr-xr-x. 2 stack stack 68 May 30 09:22 environments -rw-r--r--. 1 stack stack 265 May 27 13:47 environment.yaml -rw-rw-r--. 1 stack stack 297 May 27 13:47 init-repo.yaml -rw-r--r--. 1 stack stack 570 May 27 13:47 ironic-config.yaml drwxrwxr-x. 4 stack stack 4096 May 27 13:53 network -rw-r--r--. 1 stack stack 6370 May 27 14:26 network_data.yaml -rw-r--r--. 1 stack stack 11137 May 27 13:53 roles_data.yaml -rw-r--r--. 1 stack stack 234 May 30 09:23 vip-data-default-network-isolation.yaml (undercloud) [stack@undercloud templates]$ cat environment.yaml parameter_defaults: OvercloudControllerFlavor: control OvercloudComputeFlavor: compute ControllerCount: 3 ComputeCount: 1 TimeZone: 'Asia/Kolkata' NtpServer: ['30.30.30.3'] NeutronBridgeMappings: datacentre:br-tenant NeutronFlatNetworks: datacentre (undercloud) [stack@undercloud templates]$ (undercloud) [stack@undercloud templates]$ cat ironic-config.yaml parameter_defaults: NovaSchedulerDefaultFilters: - AggregateInstanceExtraSpecsFilter - AvailabilityZoneFilter - ComputeFilter - ComputeCapabilitiesFilter - ImagePropertiesFilter IronicEnabledHardwareTypes: - ipmi - redfish IronicEnabledPowerInterfaces: - ipmitool - redfish IronicEnabledManagementInterfaces: - ipmitool - redfish IronicCleaningDiskErase: metadata IronicIPXEEnabled: true IronicInspectorSubnets: - ip_range: 172.23.3.100,172.23.3.150 (undercloud) [stack@undercloud templates]$ cat network_data.yaml - name: J3Mgmt name_lower: j3mgmt vip: true vlan: 400 ipv6: true ipv6_subnet: 'fd80:fd00:fd00:4000::/64' ipv6_allocation_pools: [{'start': 'fd80:fd00:fd00:4000::10', 'end': 'fd80:fd00:fd00:4000:ffff:ffff:ffff:fffe'}] mtu: 9000 - name: InternalApi name_lower: internal_api vip: true vlan: 418 ipv6: true ipv6_subnet: 'fd00:fd00:fd00:2000::/64' ipv6_allocation_pools: [{'start': 'fd00:fd00:fd00:2000::10', 'end': 'fd00:fd00:fd00:2000:ffff:ffff:ffff:fffe'}] mtu: 9000 - name: External vip: true name_lower: external vlan: 408 ipv6: true gateway_ipv6: 'fd00:fd00:fd00:9900::1' ipv6_subnet: 'fd00:fd00:fd00:9900::/64' ipv6_allocation_pools: [{'start': 'fd00:fd00:fd00:9900::10', 'end': 'fd00:fd00:fd00:9900:ffff:ffff:ffff:fffe'}] mtu: 9000 - name: OCProvisioning vip: true name_lower: oc_provisioning vlan: 412 ip_subnet: '172.23.3.0/24' allocation_pools: [{'start': '172.23.3.10', 'end': '172.23.3.50'}] mtu: 9000 (undercloud) [stack@undercloud templates]$ cat roles_data.yaml ############################################################################### # File generated by TripleO ############################################################################### ############################################################################### # Role: Controller # ############################################################################### - name: Controller description: | Controller role that has all the controller services loaded and handles Database, Messaging, and Network functions. CountDefault: 1 tags: - primary - controller # Create external Neutron bridge for SNAT (and floating IPs when using # ML2/OVS without DVR) - external_bridge networks: External: subnet: external_subnet InternalApi: subnet: internal_api_subnet OCProvisioning: subnet: oc_provisioning_subnet J3Mgmt: subnet: j3mgmt_subnet # For systems with both IPv4 and IPv6, you may specify a gateway network for # each, such as ['ControlPlane', 'External'] default_route_networks: ['External'] HostnameFormatDefault: '%stackname%-controller-%index%' RoleParametersDefault: OVNCMSOptions: "enable-chassis-as-gw" # Deprecated & backward-compatible values (FIXME: Make parameters consistent) # Set uses_deprecated_params to True if any deprecated params are used. uses_deprecated_params: True deprecated_param_extraconfig: 'controllerExtraConfig' deprecated_param_flavor: 'OvercloudControlFlavor' deprecated_param_image: 'controllerImage' deprecated_nic_config_name: 'controller.yaml' update_serial: 1 ServicesDefault: - OS::TripleO::Services::Aide - OS::TripleO::Services::AodhApi - OS::TripleO::Services::AodhEvaluator .. . ..############################################################################### # Role: Compute # ############################################################################### - name: Compute description: | Basic Compute Node role CountDefault: 1 # Create external Neutron bridge (unset if using ML2/OVS without DVR) tags: - compute - external_bridge networks: InternalApi: subnet: internal_api_subnet J3Mgmt: subnet: j3mgmt_subnet HostnameFormatDefault: '%stackname%-novacompute-%index%' RoleParametersDefault: FsAioMaxNumber: 1048576 TunedProfileName: "virtual-host" # Deprecated & backward-compatible values (FIXME: Make parameters consistent) # Set uses_deprecated_params to True if any deprecated params are used. # These deprecated_params only need to be used for existing roles and not for # composable roles. uses_deprecated_params: True deprecated_param_image: 'NovaImage' deprecated_param_extraconfig: 'NovaComputeExtraConfig' deprecated_param_metadata: 'NovaComputeServerMetadata' deprecated_param_scheduler_hints: 'NovaComputeSchedulerHints' deprecated_param_ips: 'NovaComputeIPs' deprecated_server_resource_name: 'NovaCompute' deprecated_nic_config_name: 'compute.yaml' update_serial: 25 ServicesDefault: - OS::TripleO::Services::Aide - OS::TripleO::Services::AuditD - OS::TripleO::Services::BootParams (undercloud) [stack@undercloud templates]$ cat environments/network-environment.yaml #This file is an example of an environment file for defining the isolated #networks and related parameters. resource_registry: # Network Interface templates to use (these files must exist). You can # override these by including one of the net-*.yaml environment files, # such as net-bond-with-vlans.yaml, or modifying the list here. # Port assignments for the Controller OS::TripleO::Controller::Net::SoftwareConfig: OS::Heat::None # Port assignments for the Compute OS::TripleO::Compute::Net::SoftwareConfig: OS::Heat::None parameter_defaults: # This section is where deployment-specific configuration is done # ServiceNetMap: IronicApiNetwork: oc_provisioning IronicNetwork: oc_provisioning # This section is where deployment-specific configuration is done ControllerNetworkConfigTemplate: 'templates/bonds_vlans/bonds_vlans.j2' ComputeNetworkConfigTemplate: 'templates/bonds_vlans/bonds_vlans.j2' # Customize the IP subnet to match the local environment J3MgmtNetCidr: 'fd80:fd00:fd00:4000::/64' # Customize the IP range to use for static IPs and VIPs J3MgmtAllocationPools: [{'start': 'fd80:fd00:fd00:4000::10', 'end': 'fd80:fd00:fd00:4000:ffff:ffff:ffff:fffe'}] # Customize the VLAN ID to match the local environment J3MgmtNetworkVlanID: 400 # Customize the IP subnet to match the local environment InternalApiNetCidr: 'fd00:fd00:fd00:2000::/64' # Customize the IP range to use for static IPs and VIPs InternalApiAllocationPools: [{'start': 'fd00:fd00:fd00:2000::10', 'end': 'fd00:fd00:fd00:2000:ffff:ffff:ffff:fffe'}] # Customize the VLAN ID to match the local environment InternalApiNetworkVlanID: 418 # Customize the IP subnet to match the local environment ExternalNetCidr: 'fd00:fd00:fd00:9900::/64' # Customize the IP range to use for static IPs and VIPs # Leave room if the external network is also used for floating IPs ExternalAllocationPools: [{'start': 'fd00:fd00:fd00:9900::10', 'end': 'fd00:fd00:fd00:9900:ffff:ffff:ffff:fffe'}] # Gateway router for routable networks ExternalInterfaceDefaultRoute: 'fd00:fd00:fd00:9900::1' # Customize the VLAN ID to match the local environment ExternalNetworkVlanID: 408 # Customize the IP subnet to match the local environment OCProvisioningNetCidr: '172.23.3.0/24' # Customize the IP range to use for static IPs and VIPs OCProvisioningAllocationPools: [{'start': '172.23.3.10', 'end': '172.23.3.50'}] # Customize the VLAN ID to match the local environment OCProvisioningNetworkVlanID: 412 # List of Neutron network types for tenant networks (will be used in order) NeutronNetworkType: 'geneve,vlan' # Neutron VLAN ranges per network, for example 'datacentre:1:499,tenant:500:1000': NeutronNetworkVLANRanges: 'datacentre:1:1000' # Customize bonding options, e.g. "mode=4 lacp_rate=1 updelay=1000 miimon=100" # for Linux bonds w/LACP, or "bond_mode=active-backup" for OVS active/backup. BondInterfaceOvsOptions: "bond_mode=active-backup" (undercloud) [stack@undercloud templates]$ (undercloud) [stack@undercloud templates]$ cat environments/network-isolation.yaml # NOTE: This template is now deprecated, and is only included for compatibility # when upgrading a deployment where this template was originally used. For new # deployments, set "ipv6: true" on desired networks in network_data.yaml, and # include network-isolation.yaml. # # Enable the creation of Neutron networks for isolated Overcloud # traffic and configure each role to assign ports (related # to that role) on these networks. resource_registry: # networks as defined in network_data.yaml OS::TripleO::Network::J3Mgmt: ../network/j3mgmt_v6.yaml OS::TripleO::Network::InternalApi: ../network/internal_api_v6.yaml OS::TripleO::Network::External: ../network/external_v6.yaml OS::TripleO::Network::OCProvisioning: ../network/oc_provisioning.yaml # Port assignments for the VIPs OS::TripleO::Network::Ports::J3MgmtVipPort: ../network/ports/j3mgmt_v6.yaml OS::TripleO::Network::Ports::InternalApiVipPort: ../network/ports/internal_api_v6.yaml OS::TripleO::Network::Ports::ExternalVipPort: ../network/ports/external_v6.yaml OS::TripleO::Network::Ports::OCProvisioningVipPort: ../network/ports/oc_provisioning.yaml # Port assignments by role, edit role definition to assign networks to roles. # Port assignments for the Controller OS::TripleO::Controller::Ports::J3MgmtPort: ../network/ports/j3mgmt_v6.yaml OS::TripleO::Controller::Ports::InternalApiPort: ../network/ports/internal_api_v6.yaml OS::TripleO::Controller::Ports::ExternalPort: ../network/ports/external_v6.yaml OS::TripleO::Controller::Ports::OCProvisioningPort: ../network/ports/oc_provisioning.yaml # Port assignments for the Compute OS::TripleO::Compute::Ports::J3MgmtPort: ../network/ports/j3mgmt_v6.yaml OS::TripleO::Compute::Ports::InternalApiPort: ../network/ports/internal_api_v6.yaml parameter_defaults: # Enable IPv6 environment for Manila ManilaIPv6: True (undercloud) [stack@undercloud templates]$ On Tue, May 24, 2022 at 5:04 PM Lokendra Rathour <lokendrarathour(a)gmail.com> wrote: > Thanks, I'll check them out. > will let you know in case it works out. > > On Tue, May 24, 2022 at 2:37 PM Swogat Pradhan <swogatpradhan22(a)gmail.com> > wrote: > >> Hi, >> Please find the below templates: >> These are for openstack wallaby release: >> >> (undercloud) [stack@hkg2director workplace]$ cat custom_network_data.yaml >> - name: Storage >> name_lower: storage >> vip: true >> mtu: 1500 >> subnets: >> storage_subnet: >> ip_subnet: 172.25.202.0/26 >> allocation_pools: >> - start: 172.25.202.6 >> end: 172.25.202.20 >> vlan: 1105 >> - name: StorageMgmt >> name_lower: storage_mgmt >> vip: true >> mtu: 1500 >> subnets: >> storage_mgmt_subnet: >> ip_subnet: 172.25.202.64/26 >> allocation_pools: >> - start: 172.25.202.72 >> end: 172.25.202.87 >> vlan: 1106 >> - name: InternalApi >> name_lower: internal_api >> vip: true >> mtu: 1500 >> subnets: >> internal_api_subnet: >> ip_subnet: 172.25.201.192/26 >> allocation_pools: >> - start: 172.25.201.198 >> end: 172.25.201.212 >> vlan: 1104 >> - name: Tenant >> vip: false # Tenant network does not use VIPs >> mtu: 1500 >> name_lower: tenant >> subnets: >> tenant_subnet: >> ip_subnet: 172.25.202.128/26 >> allocation_pools: >> - start: 172.25.202.135 >> end: 172.25.202.150 >> vlan: 1108 >> - name: External >> name_lower: external >> vip: true >> mtu: 1500 >> subnets: >> external_subnet: >> ip_subnet: 172.25.201.128/26 >> allocation_pools: >> - start: 172.25.201.135 >> end: 172.25.201.150 >> gateway_ip: 172.25.201.129 >> vlan: 1103 >> >> (undercloud) [stack@hkg2director workplace]$ cat custom_vip_data.yaml >> - network: ctlplane >> #dns_name: overcloud >> ip_address: 172.25.201.91 >> subnet: ctlplane-subnet >> - network: external >> #dns_name: overcloud >> ip_address: 172.25.201.150 >> subnet: external_subnet >> - network: internal_api >> #dns_name: overcloud >> ip_address: 172.25.201.250 >> subnet: internal_api_subnet >> - network: storage >> #dns_name: overcloud >> ip_address: 172.25.202.50 >> subnet: storage_subnet >> - network: storage_mgmt >> #dns_name: overcloud >> ip_address: 172.25.202.90 >> subnet: storage_mgmt_subnet >> >> (undercloud) [stack@hkg2director workplace]$ cat >> overcloud-baremetal-deploy.yaml >> - name: Controller >> count: 4 >> defaults: >> networks: >> - network: ctlplane >> vif: true >> - network: external >> subnet: external_subnet >> - network: internal_api >> subnet: internal_api_subnet >> - network: storage >> subnet: storage_subnet >> - network: storage_mgmt >> subnet: storage_mgmt_subnet >> - network: tenant >> subnet: tenant_subnet >> network_config: >> template: /home/stack/templates/controller.j2 >> default_route_network: >> - external >> instances: >> - hostname: overcloud-controller-0 >> name: dc1-controller2 >> #provisioned: false >> - hostname: overcloud-controller-1 >> name: dc2-controller2 >> #provisioned: false >> - hostname: overcloud-controller-2 >> name: dc1-controller1 >> #provisioned: false >> - hostname: overcloud-controller-no-ceph-3 >> name: dc2-ceph2 >> #provisioned: false >> #- hostname: overcloud-controller-3 >> #name: dc2-compute3 >> #provisioned: false >> >> - name: Compute >> count: 5 >> defaults: >> networks: >> - network: ctlplane >> vif: true >> - network: internal_api >> subnet: internal_api_subnet >> - network: tenant >> subnet: tenant_subnet >> - network: storage >> subnet: storage_subnet >> network_config: >> template: /home/stack/templates/compute.j2 >> instances: >> - hostname: overcloud-novacompute-0 >> name: dc2-compute1 >> #provisioned: false >> - hostname: overcloud-novacompute-1 >> name: dc2-ceph1 >> #provisioned: false >> - hostname: overcloud-novacompute-2 >> name: dc1-compute1 >> #provisioned: false >> - hostname: overcloud-novacompute-3 >> name: dc1-compute2 >> #provisioned: false >> - hostname: overcloud-novacompute-4 >> name: dc2-compute3 >> #provisioned: false >> >> - name: CephStorage >> count: 4 >> defaults: >> networks: >> - network: ctlplane >> vif: true >> - network: internal_api >> subnet: internal_api_subnet >> - network: storage >> subnet: storage_subnet >> - network: storage_mgmt >> subnet: storage_mgmt_subnet >> network_config: >> template: /home/stack/templates/ceph-storage.j2 >> instances: >> - hostname: overcloud-cephstorage-0 >> name: dc2-controller1 >> #provisioned: false >> # - hostname: overcloud-cephstorage-1 >> # name: dc2-ceph2 >> - hostname: overcloud-cephstorage-1 >> name: dc1-ceph1 >> # provisioned: false >> - hostname: overcloud-cephstorage-2 >> name: dc1-ceph2 >> #provisioned: false >> - hostname: overcloud-cephstorage-3 >> name: dc2-compute2 >> #provisioned: false >> >> >> You must use these templates to provision network, vip and nodes. >> You must use the output files generated during the provisioning step in >> openstack overcloud deploy command using -e parameter. >> >> With regards, >> Swogat Pradhan >> >> >> On Mon, May 23, 2022 at 8:33 PM Lokendra Rathour < >> lokendrarathour(a)gmail.com> wrote: >> >>> Hi Swogat, >>> I tried checking your solution and my templates but could not relate >>> much. >>> But issue seems the same >>> >>> http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028401.html >>> >>> I tried somemore ways but looks like some issue with templates. >>> Can you please share the templates used to deploy the overcloud. >>> >>> Mysetup have 3 controller and 1 compute. >>> >>> Thanks once again for reading my mail. >>> >>> Waiting for your reply. >>> >>> -Lokendra >>> >>> On Fri, 20 May 2022, 08:25 Swogat Pradhan, <swogatpradhan22(a)gmail.com> >>> wrote: >>> >>>> Hi, >>>> Yes I was able to find the issue and fix it. >>>> The issue was with the overcloud-baremetal-deployed.yaml file i was >>>> trying to provision controller-0, controller-1 and controller-3 and kept >>>> controller-2 aside for later, but the tripleo scripts are built in such a >>>> way that they were taking controller- 0, 1 and 2 inplace of controller-3, >>>> so the network ports and vip were created for controller 0,1 and 2 but not >>>> for 3 , so this error was popping off. Also i would request you to check >>>> the jinja nic templates and once the node provisioning is done check the >>>> /etc/os-net-config/config.json/yaml file for syntax if using bonded nic >>>> template. >>>> If you need any more infor please let me know. >>>> >>>> With regards, >>>> Swogat Pradhan >>>> >>>> >>>> >>>> On Fri, May 20, 2022 at 8:01 AM Lokendra Rathour < >>>> lokendrarathour(a)gmail.com> wrote: >>>> >>>>> Hi Swogat, >>>>> Thanks for raising this issue. >>>>> Did you find any solution? to this problem ? >>>>> >>>>> Please let me know it might be helpful >>>>> >>>>> >>>>> On Tue, Apr 19, 2022 at 12:43 PM Swogat Pradhan < >>>>> swogatpradhan22(a)gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> I am currently trying to deploy openstack wallaby using tripleo arch. >>>>>> I created the network jinja templates, ran the following commands >>>>>> also: >>>>>> >>>>>> #openstack overcloud network provision --stack overcloud --output >>>>>> networks-deployed-environment.yaml custom_network_data.yaml >>>>>> # openstack overcloud network vip provision --stack overcloud >>>>>> --output vip-deployed-environment.yaml custom_vip_data.yaml >>>>>> # openstack overcloud node provision --stack overcloud >>>>>> --overcloud-ssh-key /home/stack/sshkey/id_rsa >>>>>> overcloud-baremetal-deploy.yaml >>>>>> >>>>>> and used the environment files in the openstack overcloud deploy >>>>>> command: >>>>>> >>>>>> (undercloud) [stack@hkg2director ~]$ cat deploy.sh >>>>>> #!/bin/bash >>>>>> THT=/usr/share/openstack-tripleo-heat-templates/ >>>>>> CNF=/home/stack/ >>>>>> openstack overcloud deploy --templates $THT \ >>>>>> -r $CNF/templates/roles_data.yaml \ >>>>>> -n $CNF/workplace/custom_network_data.yaml \ >>>>>> -e ~/containers-prepare-parameter.yaml \ >>>>>> -e $CNF/templates/node-info.yaml \ >>>>>> -e $CNF/templates/scheduler-hints.yaml \ >>>>>> -e $CNF/workplace/networks-deployed-environment.yaml \ >>>>>> -e $CNF/workplace/vip-deployed-environment.yaml \ >>>>>> -e $CNF/workplace/overcloud-baremetal-deployed.yaml \ >>>>>> -e $CNF/workplace/custom-net-bond-with-vlans.yaml >>>>>> >>>>>> Now when i run the ./deploy.sh script i encounter an error stating: >>>>>> >>>>>> ERROR openstack [-] Resource >>>>>> OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type >>>>>> OS::Neutron::Port and the Neutron service is not available when using >>>>>> ephemeral Heat. The generated environments from 'openstack overcloud >>>>>> baremetal provision' and 'openstack overcloud network provision' must be >>>>>> included with the deployment command.: >>>>>> tripleoclient.exceptions.InvalidConfiguration: Resource >>>>>> OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type >>>>>> OS::Neutron::Port and the Neutron service is not available when using >>>>>> ephemeral Heat. The generated environments from 'openstack overcloud >>>>>> baremetal provision' and 'openstack overcloud network provision' must be >>>>>> included with the deployment command. >>>>>> 2022-04-19 13:47:16.582 735924 INFO osc_lib.shell [-] END return >>>>>> value: 1 >>>>>> >>>>>> Can someone tell me where the mistake is? >>>>>> >>>>>> With regards, >>>>>> Swogat Pradhan >>>>>> >>>>> >>>>> >>>>>

3 8

[cinder] Bug deputy report for week of 06-08-2022
by Sofia Enriquez 08 Jun '22

08 Jun '22

This is a bug report from 06-01-2022 to 06-08-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1976499 "[IBM Storwize] lsfcportsetmember is being called in the wrong SVC code level." Fix proposed to master. Wishlist - https://bugs.launchpad.net/cinder/+bug/1977868 "When create volume from image, image is fetched twice." Unassigned. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[Tripleo] - Provisioning Baremetal Instances in Wallaby Openstack
by Anirudh Gupta 08 Jun '22

08 Jun '22

Hi Harald/Julia/Openstack Team I had successfully installed Ironic Service in Tripleo Train, Ussuri Release with the help of openstack discuss team members. https://lists.openstack.org/pipermail/openstack-discuss/2022-February/02704… I had custom network configuration for which I had passed Service net map as below in network-environment file. parameter_defaults: ServiceNetMap: IronicApiNetwork: oc_provisioning IronicNetwork: oc_provisioning But with the Wallaby Release, since the deployment format has changed There is no network-environment file. So I tried passing it in a separate environment.yaml file along with the templates. Command to deploy in wallaby: openstack overcloud deploy --templates \ --networks-file /home/stack/templates/custom_network_data.yaml \ --vip-file /home/stack/templates/custom_vip_data.yaml \ --baremetal-deployment /home/stack/templates/overcloud-baremetal-deploy.yaml --deployed-server \ --network-config \ -e /home/stack/templates/environment.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-conductor.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-overcloud.yaml \ -e /home/stack/templates/ironic-config.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ptp.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \ -e /home/stack/containers-prepare-parameter.yaml Without Service Net Map, deployment was successful but TFTP of image was an issue since we are going with custom network approach. Passing Service Net map details in a seperate file environment.yaml, is giving the below error: 24d-f43f-6f76-000000006ce9 | TASK | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_3 2022-06-07 11:16:46.806982 | | WARNING | ERROR: Can't run container ironic_db_sync stderr: Error: statfs /var/lib/config-data/puppet-generated/ironic_api: no such file or directory 2022-06-07 11:16:46.809252 | 525400fd-f24d-f43f-6f76-000000006c79 | FATAL | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_3 | overcloud-controller-1 | error={"changed": false, "msg": "Failed containers: ironic_db_sync"} 2022-06-07 11:16:46.810197 | 525400fd-f24d-f43f-6f76-000000006c79 | TIMING | tripleo_container_manage : Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_3 | overcloud-controller-1 | 0:11:40.574944 | 10.62s 2022-06-07 11:16:47.683400 | | WARNING | ERROR: Can't run container ironic_db_sync stderr: Error: statfs /var/lib/config-data/puppet-generated/ironic_api: no such file or directory 2022-06-07 11:16:47.684455 | 525400fd-f24d-f43f-6f76-000000006ce9 | FATAL | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_3 | overcloud-controller-2 | error={"changed": false, "msg": "Failed containers: ironic_db_sync"} Can you please suggest the place we can pass the service net map details in Wallaby Release to resolve this issue? Regards Anirudh Gupta

2 3

Using infiniband for openstack network communications
by A Monster 08 Jun '22

08 Jun '22

Is it possible to use the infiniband port for openstack networks without having to use the infiniband port as an ethernet port ?

4 3

[cinder][drivers] Register blueprints for your drivers
by Rajat Dhasmana 07 Jun '22

07 Jun '22

Hello Driver Maintainers, If you are planning to submit your driver in the Zed development cycle, make sure you have a blueprint registered against your driver. There is a doc available[1] describing how to register a blueprint and also information related to its attributes. Also take a look at the previously filed blueprints here[2] for reference. We had a discussion in the last mid cycle (1st June) and the following is a list of drivers that are currently proposed. If your driver is in the list or not, please file a blueprint and mention the driver patches in the work items section of the blueprint that will help us prioritize the review of that driver for the Zed development cycle. 1) DataCore (reintroduced), FC and iSCSI: https://review.opendev.org/c/openstack/cinder/+/836996 2) YADRO Tatlin.UNIFIED, FC and iSCSI: https://review.opendev.org/c/openstack/cinder/+/825492 3) Dell EMC PowerStore, NFS: https://review.opendev.org/c/openstack/cinder/+/797608 4) Pure Storage, NVMe-RoCE: https://review.opendev.org/c/openstack/cinder/+/799871 5) HPE XP Storage, FC and iSCSI: https://review.opendev.org/c/openstack/cinder/+/815582 [1] https://wiki.openstack.org/wiki/Blueprints [2] https://blueprints.launchpad.net/cinder Thanks and regards Rajat Dhasmana

1 0

[Octavia] Weekly meeting cancelled
by Gregory Thiemonge 07 Jun '22

07 Jun '22

Hi, This week's upstream meeting is cancelled, because it conflicts with the OpenInfra Summit (and I'm also on PTO), See you next week, Thanks, Gregory

1 0

[sdk] specify mac address when creating ports with nova
by jdratlif＠globalnoc.iu.edu 07 Jun '22

07 Jun '22

When using connection.compute.create_server(), what is the structure of the networks parameter? I see in the example is a list of objects with a single key in the list being the uuid of the network. I know there are other parameters that could be in this list though. The os-migrate ansible playbooks add fixed_ip to this. fixed_ip is not a Network or a Port class parameter. Port has fixed_ips, but that would be a list. I want to add mac address to this port, but I'm not sure if that's possible or what key I would need to add. Is the structure of the networks object documented somewhere? Thanks --- John Ratliff Systems Automation Engineer GlobalNOC @ Indiana University

2 3

[ansible] [openstack-cloud] how to find port by IP address in ansible
by jdratlif＠globalnoc.iu.edu 07 Jun '22

07 Jun '22

How can I get a port by it's IP address using the openstack cloud ansible modules? This is what I'm trying, but it never yields any results. I do get results if I use mac_address or device_id until filters, but I need to find the port by it's IP. - name: get port info openstack.cloud.port_info: filters: fixed_ips: - 'ip_address=123.124.125.126' auth: "{{ auth_dict }}" region_name: "{{ region }}" Thanks --- John Ratliff Systems Automation Engineer GlobalNOC @ Indiana University

1 0

trove, error - Exception during message handling: AttributeError: 'TroveContext' object has no attribute 'notification', please help to fix
by Vasiliy Bragin 07 Jun '22

07 Jun '22

Hello, team trove! trove, error - Exception during message handling: AttributeError: 'TroveContext' object has no attribute 'notification', please help to fix release openstack - yoga, CentOS, CentOS Stream release 8 instance trove - ubuntu, Linux version 5.4.0-113-generic (buildd@lcy02-amd64-067) (gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)) #127-Ubuntu SMP Wed May 18 14:30:56 UTC 2022 On Yoga Trove guest-agent inside instance not work at all: log 2022-06-01 15:31:13.263 908 DEBUG trove.common.rpc.service [-] Creating RPC server for service guestagent.15e4e2e9-13a4-42f6-bafb-f63fdd074d76 start /opt/guest-agent-venv/lib/python3.8/site-packages/trove/common/rpc/service.py:56 *2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server [-] Exception during message handling: AttributeError: 'TroveContext' object has no attribute 'notification'* 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.8/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.8/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.8/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.8/site-packages/osprofiler/profiler.py", line 160, in wrapper 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server result = f(*args, **kwargs) 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.8/site-packages/trove/guestagent/datastore/manager.py", line 213, in prepare 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server with EndNotification(context, instance_id=CONF.guest_id): 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.8/site-packages/trove/common/notification.py", line 48, in __init__ 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server self.context.notification.payload.update(kwargs) 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server AttributeError: 'TroveContext' object has no attribute 'notification' 2022-06-01 15:31:13.610 908 ERROR oslo_messaging.rpc.server Trove guest-agent on instance execute. But DB don't work and not started. After restart guest-agent on instance next log: 2022-06-06 12:51:09.443 4503 DEBUG trove.common.rpc.service [-] Creating RPC server for service guestagent.15e4e2e9-13a4-42f6-bafb-f63fdd074d76 start /opt/guest-agent-venv/lib/python3.8/site-packages/trove/common/rpc/service.py:56 2022-06-06 12:52:09.541 4503 DEBUG oslo_service.periodic_task [-] Running periodic task Manager.update_status run_periodic_tasks /opt/guest-agent-venv/lib/python3.8/site-packages/oslo_service/periodic_task.py:210 *2022-06-06 12:52:09.546 4503 INFO trove.guestagent.datastore.manager [-] Database service is not installed, skip status check* Please tell me how can I fix this errors? -- Vasily Bragin

1 0

[summit][ops][nova] Ops feedback session
by Sylvain Bauza 07 Jun '22

07 Jun '22

Hi all, You probably haven't noticed but we'll run a Forum session at Berlin about Nova pain points and features you'd like to have : https://etherpad.opendev.org/p/nova-berlin-meet-and-greet This will be held tomorrow at 14:50 CEST but your feedback is absolutely welcome even if you can't attend our session. Please take a few minutes to look at the etherpad above and provide your thoughts, that'd be more than welcome. The more we have feedback, the better we could have a productive discussion :-) See you hopefully in-person for whose who are lucky to be present at the Summit. -Sylvain and gibi

1 0

[cinder] Failed to delete volume
by Michal Arbet 07 Jun '22

07 Jun '22

Hi, I would like to ask if someone saw issue when volume failed to delete, log below : This is happening from time to time. 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server [req-80b56352-81b5-47b6-841e-94fface5974e fce19e20993647db8ae39d67094a4294 c8d8a385912c4731832bf1f2cf4727fb - - -] Exception during message handling: EOFError 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/eventlet/greenio/base.py", line 359, in _recv_loop 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server self._read_trampoline() 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/eventlet/greenio/base.py", line 331, in _read_trampoline 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server timeout_exc=socket_timeout('timed out')) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/eventlet/greenio/base.py", line 210, in _trampoline 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server mark_as_closed=self._mark_as_closed) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/eventlet/hubs/__init__.py", line 159, in trampoline 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server return hub.switch() 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/eventlet/hubs/hub.py", line 298, in switch 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server return self.greenlet.switch() 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server eventlet.hubs.IOClosed: [Errno 107] Operation on closed file 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/osprofiler/profiler.py", line 160, in wrapper 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server result = f(*args, **kwargs) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/osprofiler/profiler.py", line 160, in wrapper 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server result = f(*args, **kwargs) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "<decorator-gen-754>", line 2, in delete_volume 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/cinder/coordination.py", line 144, in _synchronized 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server with lock(blocking): 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/tooz/locking.py", line 29, in __enter__ 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server return self.lock.__enter__(*self.args, **self.kwargs) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/tooz/locking.py", line 49, in __enter__ 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server acquired = self.acquire(*args, **kwargs) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/tooz/drivers/redis.py", line 58, in wrapper 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server return func(*args, **kwargs) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/tooz/drivers/redis.py", line 110, in acquire 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server blocking=blocking, blocking_timeout=timeout) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/redis/lock.py", line 182, in acquire 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server if self.do_acquire(token): 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/redis/lock.py", line 197, in do_acquire 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server if self.redis.set(self.name, token, nx=True, px=timeout): 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/redis/client.py", line 1519, in set 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server return self.execute_command('SET', *pieces) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/redis/client.py", line 839, in execute_command 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server return self.parse_response(conn, command_name, **options) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/redis/client.py", line 853, in parse_response 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server response = connection.read_response() 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/redis/sentinel.py", line 55, in read_response 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server return super(SentinelManagedConnection, self).read_response() 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/redis/connection.py", line 700, in read_response 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server response = self._parser.read_response() 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/redis/connection.py", line 310, in read_response 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server response = self._buffer.readline() 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/redis/connection.py", line 242, in readline 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server self._read_from_socket() 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/redis/connection.py", line 184, in _read_from_socket 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server data = recv(self._sock, socket_read_size) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/redis/_compat.py", line 71, in recv 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server return sock.recv(*args, **kwargs) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/eventlet/greenio/base.py", line 365, in recv 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server return self._recv_loop(self.fd.recv, b'', bufsize, flags) 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/eventlet/greenio/base.py", line 362, in _recv_loop 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server raise EOFError() 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server EOFError 2022-05-23 10:15:24.414 833 ERROR oslo_messaging.rpc.server Thanks, Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet(a)ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline>

1 0

[neutron] Bug deputy report for week of May 30th
by Brian Haley 06 Jun '22

06 Jun '22

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/1976357 - [sqlalchemy-20] Missing DB context in subnetpool methods - https://review.opendev.org/c/openstack/neutron/+/844024 * https://bugs.launchpad.net/neutron/+bug/1976360 - [sqlalchemy-20] Missing DB context in networking-sfc flow classifier - Rodolfo assigned to himself as he's working on a number of these Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/1976292 - [OVN] AgentCache.agents can change during an iteration operation - https://review.opendev.org/c/openstack/neutron/+/843933 * https://bugs.launchpad.net/neutron/+bug/1976323 - [functional/fullstack][master] move fips periodic job to CentOS 9-Stream - https://review.opendev.org/c/openstack/neutron/+/843252 * https://bugs.launchpad.net/neutron/+bug/1976345 - The sync_routers interface takes too long - Needs owner and further investigation * https://bugs.launchpad.net/neutron/+bug/1976366 - OVN: Metadata is not provisioned for a network with DHCP turned off - Related to https://bugs.launchpad.net/neutron/+bug/1918914 ? * https://bugs.launchpad.net/neutron/+bug/1976439 - The database ml2_port_binding_levels and ml2_distributed_port_bindings tables have a lot of redundant data - Needs assignee * https://bugs.launchpad.net/neutron/+bug/1976355 - remove eager subquery load for PortBindingLevel - Recent fix https://review.opendev.org/c/openstack/neutron/+/841823 - https://review.opendev.org/c/openstack/neutron/+/844699 (potential) - Other suggestions from Oleg as well Low bugs -------- * https://bugs.launchpad.net/neutron/+bug/1977629 - [ovn]agent's heartbeat time is error - Zhou Heng took ownership Misc bugs --------- * https://bugs.launchpad.net/neutron/+bug/1977485 - Neutron deletes port in use and nova errors out when cleaning the VM XML - Possible Nova issue, posted comment * https://bugs.launchpad.net/neutron/+bug/1977470 - [networking-bgpvpn] zed unit test failures - Closed as invalid Wishlist bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1976270 - [RFE] Improve performance of bulk port create/delete with networking-generic-switch

1 0

Re: Using infiniband for openstack network communications
by A Monster 06 Jun '22

06 Jun '22

Thank you for your reply, I'll check the link you've sent to me immediately.

3 3

[all][tc] Canceling this week TC meetings
by Ghanshyam Mann 06 Jun '22

06 Jun '22

Hello Everyone, We are cancelling this week's TC meeting and will be meeting next on 16 June. -gmann

1 0

[all][doc] the openstack-tox-docs job is broken with Sphinx >= 5.0.0
by Takashi Kajinami 06 Jun '22

06 Jun '22

Hi, It seems the openstack-tox-docs job is broken in some projects because of the following change made in Sphinx >= 5.0.0 . https://github.com/sphinx-doc/sphinx/commit/a3d09835522e6487cf93dcc871179db… We currently have Sphinx 4.5.0 in upper-constraints.txt but some projects (eg. Heat, Nova, Neutron) are using only their own docs-constraints.txt and pull the latest version which is 5.0.1 . IMO we need to fix the problem by the following two steps, but I'd appreciate if anybody can share a better idea. 1. Update tox.ini to honor upper-constraints.txt. This is needed in master and stable/branches as well. 2. Update docs/source/conf.py to hard-code the language parameter to 'en'. This is required in master so that we can bump the upper version later. Thank you, Takashi Kajinami

4 5

Re: Using infiniband for openstack network communications
by A Monster 06 Jun '22

06 Jun '22

Alright, thank you again Sir.

1 0

[kolla] weekly meeting 8th June
by Michał Nasiadka 06 Jun '22

06 Jun '22

Hello koalas, This Wednesday (8th June) meeting is cancelled due to OpenInfra Summit in Berlin. See you on a meeting next week. Michal -- Michał Nasiadka mnasiadka(a)gmail.com

1 0

masakari-hostmonitor error
by Parsa Aminian 06 Jun '22

06 Jun '22

hello on kolla ansible masakari-hostmonitor container on wallaby version I have this error : 2022-06-05 23:30:51.880 7 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication using 'eth0' is failed.: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. 2022-06-05 23:30:51.881 7 ERROR masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication is failed. 2022-06-05 23:31:22.042 7 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] Exception caught: Unexpected error while running command. Command: crmadmin -S myhostname Exit code: 102 Stdout: '' Stderr: 'error: Could not connect to controller: Connection refused\nerror: Command failed: Connection refused\n': oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. Could you please help me ?

2 1

masakari bug
by Parsa Aminian 05 Jun '22

05 Jun '22

on kolla ansible masakari-hostmonitor container on wallaby version I have this error : 2022-06-05 23:30:51.880 7 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication using 'eth0' is failed.: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. 2022-06-05 23:30:51.881 7 ERROR masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication is failed. 2022-06-05 23:31:22.042 7 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] Exception caught: Unexpected error while running command. Command: crmadmin -S myhostname Exit code: 102 Stdout: '' Stderr: 'error: Could not connect to controller: Connection refused\nerror: Command failed: Connection refused\n': oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command.

1 0

[openstack-ansible] Meeting on Jun 7th 2022 is cancelled
by Dmitriy Rabotyagov 05 Jun '22

05 Jun '22

Hi everybody! The next meeting on Jun 7th is cancelled due to the Berlin summit. Hope seeing you in person instead! We will have next meeting Jun 14th. -- Kind regards, Dmitriy Rabotyagov

1 0

[tacker] Weekly IRC meeting on Jun 7th cancelled
by Yasufumi Ogawa 05 Jun '22

05 Jun '22

Hi team, The next meeting on Jun 7th is cancelled due to the Berlin summit. Cheers, Yasufumi

1 0

[sdk][openstacksdk][keystone] Does openstacksdk support v3tokenlessauth?
by hai wu 04 Jun '22

04 Jun '22

Does openstacksdk support keystone auth type "v3tokenlessauth"? I got this error message when trying to enable openstacksdk with auth_type="v3tokenlessauth" openstack.exceptions.NotSupported: The identity service for TEST: exists but does not have any supported versions. The following are the possible relevant documents I could find, and there is no place mentioning the support for tokenless auth using openstacksdk: https://docs.openstack.org/openstacksdk/latest/user/config/configuration.ht… https://docs.openstack.org/keystone/train/admin/configure_tokenless_x509.ht…

2 2

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

03 Jun '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on 02 June. Most of the topics I am summarizing in this email. This was a video call and recordings are available @ https://www.youtube.com/watch?v=nHG2WJNceMs And logs summary are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-06-02-15.02.log.html * We are cancelling next week's meeting. The next TC weekly meeting will be on 16 June Thursday at 15:00 UTC, feel free to add the topic to the agenda[1] by 15 June. 2. What we completed this week: ========================= * TC resolution[2] and documentation[3] for OpenStack release identification schema. This clarify what place we need to use the release number and name. * Security SIG chair rotation from Gage to Jeremy[4] * Removed security-analysis repo from Security SIG[5] * Added a repository for the Large Scale SIG[6] * Added project stats check tool[7] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[8], many items are in-progress. Open Reviews ----------------- * Four open reviews for ongoing activities[9]. New release cadence "SLURP" open items -------------------------------------------------- 1. release notes strategy: Brian proposal for ""SLURP release notes approach is up for review[10]. Improve project governance --------------------------------- Slawek has the proposal the framework up and it is under review[11]. New ELK service dashboard: e-r service ----------------------------------------------- dpawlik working on ansible playbooks to deploy e-r and functional tests. TripleO team and dpawlik are working on the e-r repo merge. Consistent and Secure Default RBAC ------------------------------------------- We had a call yesterday and discussed about presenting this to the ops meetup in berlin and getting feedback, especially on the 'scope' concept. knikolla plan to moderate this topic in the ops meetup but unfortunately he will not be to make it to the summit. I have added a few notes and what questions we need to ask the operator in etherpad[12]. Please note that operator feedback is very important for us to proceed on 'scope' in SRBAC. If you are operator or know anyone around you, we request you to provide feedback. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[13]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- No updates on this. Only Adjutant project is leaderless/maintainer-less. We will check Adjutant's the situation again on ML and hope Braden will be ready with their company side permission[14]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[15][16]. Project updates ------------------- * Add a repository for the Large Scale SIG[17] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [19] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/843214 [3] https://review.opendev.org/c/openstack/governance/+/841800 [4] https://review.opendev.org/c/openstack/governance-sigs/+/844446 [5] https://review.opendev.org/c/openstack/governance/+/844463 [6] https://review.opendev.org/c/openstack/governance/+/843535 [7] https://review.opendev.org/c/openstack/governance/+/810037 [8] https://etherpad.opendev.org/p/tc-zed-tracker [9] https://review.opendev.org/q/projects:openstack/governance+status:open [10] https://review.opendev.org/c/openstack/project-team-guide/+/843457 [11] https://review.opendev.org/c/openstack/governance/+/839880 [12] https://etherpad.opendev.org/p/ops-meetup-berlin-2022-planning#L53 [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [17] https://review.opendev.org/c/openstack/project-config/+/843534 [18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all][tc] Change OpenStack release naming policy proposal
by Slawek Kaplonski 03 Jun '22

03 Jun '22

Hi, During the last PTG in April 2022 in the TC meeting we were discussing our release naming policy [1]. It seems that choosing appropriate name for every releases is very hard and time consuming. There is many factors which needs to be taken into consideration there like legal but also meaning of the chosen name in many different languages. Finally we decided that now, after Zed release, when we will go all round through alphabet it is very good time to change this policy and use only numeric version with "year"."release in the year". It is proposed in [2]. This is also good timing for such change because in the same release we are going to start our "Tick Tock" release cadence which means that every Tick release will be release with .1 (like 2023.1, 2024.1, etc.) and every Tock release will be one with .2 (2023.2, 2024.2, etc.). [1] https://etherpad.opendev.org/p/tc-zed-ptg#L265[1] [2] https://review.opendev.org/c/openstack/governance/+/839897[2] -- Slawek Kaplonski Principal Software Engineer Red Hat -------- [1] https://etherpad.opendev.org/p/tc-zed-ptg#L265 [2] https://review.opendev.org/c/openstack/governance/+/839897

16 42

Fwd: [Forum] Meet the Projects Session!
by Kendall Nelson 03 Jun '22

03 Jun '22

Hello :) I wanted to take a moment to invite project maintainers, core contributors, PTLs, governance officials, etc to a meet the projects (projects being the OIF top level ones- Kata, Zuul, OpenStack, StarlingX, and Airship) session during the Forum at the upcoming Summit in Berlin. It will take place Tue, June 7, 11:20am - 12:30pm local in A - A06. The idea is to gather in a single place so that newer members of the community or people unfamiliar with the project can come and meet some of the active participants and ask questions. It's all really informal so there is no need to prepare anything ahead of time. I realize it is pretty late in everyone's planning their schedules for the summit, but if you have a few minutes to spare to come hang out and meet some people and network, please do! We would love to see you there. -Kendall

5 4

[sdk] openstacksdk 0.99.0 breaks swift object header setting
by Clark Boylan 03 Jun '22

03 Jun '22

Hello, Last week the OpenDev team upgraded Zuul which deployed zuul-executors with openstacksdk==0.99.0 installed. After this, test job logs uploaded to the rackspace swift location were no longer viewable in the Zuul dashboard. The reason for this is these objects did not have properly configured CORS headers any longer. The objects uploaded to OVH appear to have been fine (potentially because the headers are not required for OVH). Today we downgraded the version of openstacksdk on the zuul-executors to 0.61.0 and the rackspace uploaded job log objects have functional CORS headers again. For this reason we're fairly confident that something about the 0.99.0 release is impacting the setting of these headers. The code that does these uploads with openstacksdk can be found here [0]. I suspect that the problem is going to be related to this header set on line 227 [1]. In particular that appears to be rackspace specific and this issue is rackspace specific under 0.99.0. However, I wasn't able to find anything in openstacksdk that would have a problem with this. Does anyone else have ideas? I'm somewhat concerned that this represents a class of data loss (metadata is going missing) for swift object uploads. Additionally, we rely on setting the x-delete-after header to timeout, expire, and prune our logs in swift [2]. If there is a general problem with 0.99.0 setting headers on objects it is possible that all of the objects we created using 0.99.0 do not have this metadata set and will leak in their swift containers. [0] https://opendev.org/zuul/zuul-jobs/src/commit/e69d879caecb454c529a7d757b80a… [1] https://opendev.org/zuul/zuul-jobs/src/commit/e69d879caecb454c529a7d757b80a… [2] https://opendev.org/zuul/zuul-jobs/src/commit/e69d879caecb454c529a7d757b80a…

3 7

[ironic] No weekly meeting next week (June 6)
by Iury Gregory 02 Jun '22

02 Jun '22

Hello ironicers, As you probably already know, next week is the Open Infrastructure Summit in Berlin and some of us will be at the event. We will resume our weekly meeting on June 13. Thanks! -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL* *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

[release] Release countdown for week R-17, Jun 06 - 10
by Előd Illés 02 Jun '22

02 Jun '22

Development Focus ----------------- The Zed-2 milestone will happen in next month, on July 14th, 2022. Zed-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/ <https://releases.openstack.org/zed/schedule.html>zed <https://releases.openstack.org/zed/schedule.html>/schedule.html <https://releases.openstack.org/zed/schedule.html>for details. General Information ------------------- Please remember that libraries need to be released at least once per milestone period. At milestone 2, the release team will propose releases for any library that has not been otherwise released since milestone 1. Other non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/ <https://opendev.org/openstack/releases/src/branch/master/deliverables/zed>zed <https://opendev.org/openstack/releases/src/branch/master/deliverables/zed> You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/ <https://releases.openstack.org/zed/schedule.html#z-mf>zed <https://releases.openstack.org/zed/schedule.html#z-mf>/schedule.html# <https://releases.openstack.org/zed/schedule.html#z-mf>z <https://releases.openstack.org/zed/schedule.html#z-mf>-mf <https://releases.openstack.org/zed/schedule.html#z-mf> Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released, in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates -------------------------- Zed-2 Milestone: July 14th, 2022 OpenInfra Summit: June 7-9, 2022 (Berlin) Előd Illés irc: elodilles

1 0

[dev][docs][security-sig] Retiring security-analysis process and repo
by Jeremy Stanley 02 Jun '22

02 Jun '22

In 2016, what was then the Security Project Team embarked on an effort to centrally collect security analyses of OpenStack components. It accumulated a total of two, one for Barbican as of the Newton release, and another for KeystoneMiddleware as of Pike. The latter was finalized in 2017 and took nearly a year to merge due to already waning enthusiasm and reviewer availability: https://docs.openstack.org/security-analysis Given this effort was effectively abandoned years ago, the Security SIG members agree that the repository should be retired in order to reduce confusion. The vulnerability management oversight requirements were amended in February to remove any reference to this process, and we reached a consensus that this sort of documentation is better off inside the projects which are writing it rather than collected centrally with a disconnected (or in this case absent) group of reviewers and maintainers. This message serves as notice to the community that we will be pushing changes to follow the usual OpenStack repository retirement process for openstack/security-analysis in the coming days. As usual, the final state of the documents will be found in the parent commit of the one which wipes all the old files, but for posterity I'll link it here as well: https://opendev.org/openstack/security-analysis/src/commit/ac43025 Many thanks to those who attempted to provide and review these analyses in years past. The idea of maintaining information on the security risks and considerations for the systems we design is still a good one, and something I hope our contributor community might find more time to focus on in the years to come; but the place to document those things is right alongside the rest of the software's documentation, there's nothing inherently special or different about it. -- Jeremy Stanley

1 0

[all][tc] Technical Committee next weekly meeting on June 2, 2022 at 1500 UTC
by Ghanshyam Mann 02 Jun '22

02 Jun '22

Hello Everyone, The technical Committee's next weekly meeting is scheduled for June 2, 2022, at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, June 1, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

Resources to learn IT Infrastructure
by Raghav Gururajan 02 Jun '22

02 Jun '22

Hello All, I am stepping into infrastructure side of the IT world and was wondering if any of you could recommend best books, materials or videos for learning? Regards, Raghav "RG" Gururajan.

1 0

Re: Re: [vdi][daas][ops] What are your solutions to VDI/DaaS on OpenStack?
by Ümit Seren 02 Jun '22

02 Jun '22

We are using xpra (https://xpra.org/) together with VirtualGL (https://www.virtualgl.org/) on our virtualized OpenStack based SLURM cluster to support OpenGL accelerated applications such as MorphoGraphX (https://morphographx.org/) for our users. This works pretty well. There was a bit of work involved because it requires an X11 server to run on the compute nodes but once this was done it worked fairly well. Best Ümit On 02.06.22, 01:10, "Andy Botting" <andy(a)andybotting.com> wrote: Hi Radosław, > I am wondering if and how OpenStackers are approaching the subject of > VDI (Virtual Desktop Infrastructure), also nowadays commonly called > DaaS (Desktop as a Service) offering. > To be more specific, I am looking forward to a solution covering both > Linux and Windows desktops, pre-OS screen access optional, > well-integrated (i.e., having automation) with OpenStack Nova, > preferably also with Cinder and Glance, optionally with Keystone > (apart from self-auth of course!) and Heat, 3D acceleration optional > (most of the desktops here don't need it), nice to have read-only > sharing of screen. We just launched a service like this on the Nectar Research Cloud. Like you, I looked around but couldn't find any Open Source projects that would be suitable. In the end, we based ours on a project from the University of Melbourne that did initially support Windows, but we removed some of that support to simplify our codebase as we didn't need it. We called it Bumblebee, and the code is here: https://github.com/NeCTAR-RC/bumblebee It's a Django web app with a Redis-based task scheduler that launches Nova instances, booted from a Cinder volume, cloned from a base OS image. The Django app directly modifies Guacamole's database to create the connections once the OpenStack resources have been provisioned and provides the user with a link that takes them to their desktop. We used Keycloak with OIDC for authentication on the web app and Guacamole and it's fairly seamless transitioning between the two. We did initially look at using Heat, but we wanted to support a workflow of being able to destroy the VM and archive the OS image to Swift (and restore again later if needed) so it was easier to just manage the resources directly. There's no 3D acceleration in our solution yet, but we're planning on looking at things like virtual GPUs later on. Sadly, I'm not going to make it to Berlin either, but I was thinking it might make for a good talk at the next summit. I'm in the process of properly documenting it now, so I don't have much to share at this point, but I'm happy to go into more detail about anything. cheers, Andy

1 0

[all][tc] Lets talk about Flake8 E501
by Miro Tomaska 01 Jun '22

01 Jun '22

Hello All, This is probably going to be a hot topic but I was wondering if the community ever considered raising the default 79 characters line limit. I have seen some places where even a very innocent line of code needs to be split into two lines. I have also seen some code where I feel like variable names were abbreviated on purpose to squeeze everything into one line. How does the community feel about raising the E501 limit to 119 characters? The 119 character limit is the second most popular limit besides the default one. It's long enough to give a developer enough room for descriptive variables without being forced to break lines too much. And it is short enough for a diff between two files to look OK. The only downside I can see right now is that it's not easy to convert an existing code. So we will end up with files where the new code is 79+ characters and the "old" code is <=79. I can also see an argument where someone might have trouble reviewing a patch on a laptop screen (assuming standard 14" screen) ? Here is an example of one extreme, a diff of two files maxing out at 119 characters https://review.opendev.org/c/opendev/sandbox/+/843697/1..2 Thank you for your time and I am looking forward to this conversation :) -- Miro Tomaska irc: mtomaska Red Hat

9 11

[keystone] how to use v3tokenlessauth
by hai wu 01 Jun '22

01 Jun '22

I could not find any example/usage of v3tokenlessauth, using environment variables. There are no documents to be found. I assume we could need to have this one at least: export OS_AUTH_TYPE="v3tokenlessauth" What other environment variables are required if using this auth type? Would like to use HTTPs x509 auth. This is the only relevant doc found: https://docs.openstack.org/keystone/train/admin/configure_tokenless_x509.ht… [keystone_authtoken] memcached_servers = localhost:11211 cafile = /etc/keystone/ca.pem project_domain_name = Default project_name = service auth_url = https://192.168.0.10/identity/v3 auth_type = v3tokenlessauth certfile = /etc/glance/certs/glance.pem keyfile = /etc/glance/private/glance_private_key.pem But there are no environment variables mentioned in the above doc.

1 0

Novice question
by tim+openstack.org＠coote.org 01 Jun '22

01 Jun '22

Hullo Naïve question follows. Sorry. I’m trying a minimal OS install on a Virtualbox VM on a mac. I’d like to get to the point where I can launch a compute node. I’ve failed with `packstack` and I’m trying `devstack`. Should this work out of the box: ie Spin up a vm with vagrant: I’m using Centos Stream 9 to ensure that I get a current(ish) version of Python. It has 9GB RAM Ensure that SELinux and firewalls are turned off Clone devstack, cd to the directory and run `stack.sh` as user `vagrant` (this fails 1/3 of the time as some repo or other resets a connection. `stack.sh` doesn’t seem to be idempotent as reinvoking it may or may not install and run the OS environment Upload a ssh keypair through the web interface Use the web interface to launch the m1.nano flavor with Cirros image (I think that this flavor is quite new as some of the documentation refers to creating such a flavor with 64MB, whereas this one has 128MB. I did try the 64MB route [with `packstack`] and concluded that at least 96MB was needed and the documentation was wrong. I couldn’t log into launchpad.net <http://launchpad.net/> to report this ☹ At this point the launch process fails with the error message: “Build of instance 157bfa1d-7f8c-4a6c-ba3a-b02fb4f4b6a9 aborted: Failed to allocate the network(s), not rescheduling.” In the web ui Afaict, the vm has enough memory (just: it’s using a bit of swap, but more cache, so it could reclaim that). I’d expected the instance to launch, and I can well believe that I’ve missed something, but the documentation seems to point all over the place for various logs. Should this approach work? Is there an alternative that’s better (e.g. use Ubuntu: I’m not keen on apt/dpkg/.deb based distros as I’ve been tripped up in the past over the dependency handling and systemd integration, so I’ve avoided this, but I can see that Canonical is spending money on OS. But so is IBM/Redhat)? Where can I find info on how to trouble shoot the failing process? tia Tim

3 5

[neutron][networking-ovn] Propose to EOL stable/queens, stable/rocky and stable/stein branches of networking-ovn
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, The Queens, Rocky and Stein branches of networking-ovn see little activity and maintaining them and keeping their jobs running is a big effort. We discussed this topic during the team meeting (see [1]), and agreed to propose stable/queens, stable/rocky and stable/stein branches of networking-ovn End Of Life. I will wait until the end of next week for anyone who would like to step up as maintainer of those branches and who would at least try to fix CI of them. If there will be no volunteers for that, I will EOL those branches in networking-ovn. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-05-31… Lajos Katona (lajoskatona)

1 0

[neutron][tap-as-a-service] Propose to EOL stable/queens, stable/rocky and stable/stein branches of tap-as-a-service
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, The Queens, Rocky and Stein branches of tap-as-a-service see little activity and maintaining them and keeping their jobs running is a big effort. We discussed this topic during the team meeting (see [1]), and agreed to propose stable/queens, stable/rocky and stable/stein branches of tap-as-a-service End Of Life. I will wait until the end of next week for anyone who would like to step up as maintainer of those branches and who would at least try to fix CI of them. If there will be no volunteers for that, I will EOL those branches in tap-as-a-service. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-05-31… Lajos Katona (lajoskatona)

1 0

[neutron][neutron-fwaas] Propose to EOL stable/queens, stable/rocky and stable/stein branches of neutron-fwaas
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, The Queens, Rocky and Stein branches of neutron-fwaas see little activity and maintaining them and keeping their jobs running is a big effort. We discussed this topic during the team meeting (see [1]), and agreed to propose stable/queens, stable/rocky and stable/stein branches of neutron-fwaas End Of Life. I will wait until the end of next week for anyone who would like to step up as maintainer of those branches and who would at least try to fix CI of them. If there will be no volunteers for that, I will EOL those branches in neutron-fwaas. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-05-31… Lajos Katona (lajoskatona)

1 0

[neutron][networking-sfc] Propose to EOL stable/queens, stable/rocky and stable/stein branches of networking-sfc
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, The Queens, Rocky and Stein branches of networking-sfc see little activity and maintaining them and keeping their jobs running is a big effort. We discussed this topic during the team meeting (see [1]), and agreed to propose stable/queens, stable/rocky and stable/stein branches of networking-sfc End Of Life. I will wait until the end of next week for anyone who would like to step up as maintainer of those branches and who would at least try to fix CI of them. If there will be no volunteers for that, I will EOL those branches in networking-sfc. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-05-31… Lajos Katona (lajoskatona)

1 0

[neutron][networking-bagpipe][networking-bgpvpn] Propose to EOL stable/rocky and stable/stein branches of networking-odl
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, The Rocky and Stein branches of networking-bagpipe and networking-bgpvpn see little activity and maintaining them and keeping their jobs running is a big effort. We discussed this topic during the team meeting (see [1]), and agreed to propose stable/rocky and stable/stein branches of networking-bagpipe and networking-bgpvpn End Of Life. I will wait until the end of next week for anyone who would like to step up as maintainer of those branches and who would at least try to fix CI of them. If there will be no volunteers for that, I will EOL those branches in networking-bagpipe and networking-bgpvpn. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-05-31… Lajos Katona (lajoskatona)

1 2

[neutron][networking-odl] Propose to EOL stable/queens, stable/rocky and stable/stein branches of networking-odl
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, The Queens, Rocky and Stein branches of networking-odl see little activity and maintaining them and keeping their jobs running is a big effort. We discussed this topic during the team meeting (see [1]), and agreed to propose stable/queens, stable/rocky and stable/stein branches of networking-odl End Of Life. I will wait until the end of next week for anyone who would like to step up as maintainer of those branches and who would at least try to fix CI of them. If there will be no volunteers for that, I will EOL those branches in networking-odl. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-05-31… Lajos Katona (lajoskatona)

1 0

[cinder] Bug deputy report for week of 06-01-2022
by Sofia Enriquez 01 Jun '22

01 Jun '22

This is a bug report from 05-25-2022 to 06-01-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1976400 "[Storwize] Fix multiple SVC CLI calls for rc-relationship operations." Fix proposed to master. Wishlist - https://bugs.launchpad.net/cinder/+bug/1975794 "How to configure Cinder to use as much as possible, (post-provision)." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1976331 "Check attachment_specs may lead to poor performance." Unassigned. Cheers, Sofi -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[qa] Cancelling office hour on June 7th
by Martin Kopec 01 Jun '22

01 Jun '22

Hello everyone, QA team is cancelling the next office hour Tuesday June 7th, I'm gonna attend the OpenStack Summit. https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Offi… Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

error creating image from volume
by Russell Stather 01 Jun '22

01 Jun '22

Hi Trying to create an image from a volume. Getting this very unhelpful error message. igadmin@ig-umh-maas:~$ openstack image create --volume 57bc3efa-6cdc-4e2d-a0e2-262340cc6180 commvaultimage upload_to_image() got an unexpected keyword argument 'visibility' Anyone seen this before? Thanks Russell

3 2

[neutron] team meeting 7. 06. 2022 cancelled
by Lajos Katona 01 Jun '22

01 Jun '22

Hi, Next week I will attend the Openinfra summit in Berlin, so I can't drive the team meeting. See you online on the week after the summit, or I hope we can meet in Berlin. Lajos Katona (lajoskatona)

1 0

[neutron] Drivers meeting - Friday 2.6.2022 & 9. 6. 2022. - cancelled
by Lajos Katona 01 Jun '22

01 Jun '22

Hi Neutron Drivers! This Friday I will be at a conference and next Friday I will be travelling back from Berlin, so I can't drive these drivers' meetings, let's cancel them. I hope I can meet a few of you in Berlin, and see you online the week after the summit. Lajos Katona (lajoskatona)

1 0

[neutron] CI meeting 7.06.2022 cancelled
by Slawek Kaplonski 01 Jun '22

01 Jun '22

Hi, Next week there is OpenInfra summit in Berlin and some of us will be busy there, so we decided yesterday to cancel next week's Neutron CI meeting. Please ping me on IRC or email if there would be anything urgent related to our CI. See You all on the CI meeting on 14.06.2022 (and in Berlin if You will be there :)) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0