October 2020 - openstack-discuss - lists.openstack.org

[ironic] Meetings cancelled Week of Summit and PTG
by Julia Kreger 12 Oct '20

12 Oct '20

Greetings fellow engineers and providers of irony... err I mean Ironic community members! We agreed in our weekly meeting this morning that we will cancel our weekly meetings for the next two weeks and resume November due to overlapping schedules and ultimately the pre-existing commitment to meet during the PTG. If you have any questions, please let us know! -Julia

1 0

external network on rhosp 16.1 all in one installation
by Chen Sagi 12 Oct '20

12 Oct '20

Hi all, I have an All in one installation of RHOSP for evaluation purposes and I am trying to understand external network and the Octavia service. I have a VM with the openstack installed on, with 2 NICs in the management network as required by Red hat. I tried using the RHOSP Octavia guide, and also tried to create an external network but I seem to be missing something. Notice: the network that I am using is a flat network and is not configured for VLANs at all, but is a routable address. Thanks in advance, Chen Sagi.

1 0

Re: [Ussuri] [openstack-ansible] [cinder] Can't attach volumes to instances
by Oliver Wenz 12 Oct '20

12 Oct '20

> However, I could not read the logs the way Dmitriy suggested, it simply > returns > > -- Logs begin at Mon 2020-10-05 14:30:22 UTC, end at Mon 2020-10-12 > 11:17:20 UTC. -- > -- No entries -- > > so I couldn't investigate the request. ( I tried this on both utility > and cinder api containers on the management node and on the storage and > respective compute node to be sure) ... it seems that I've missed the storage node, since I just tried again and got something: Oct 12 12:57:09 bc1bl10 cinder-volume[30198]: 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server [req-e9175ddf-8ee4-4135-b89b-6e9c61f63999 2223bca5520044b7b7646e2f8141a440 5fbba868d04b47fa87a72b9dd821ee12 - default default] Exception during message handling: cinder.exception.InvalidInput: Invalid input received: Connector doesn't have required information: initiator 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/cinder/volume/manager.py", line 4471, in _connection_create 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server self.driver.validate_connector(connector) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/cinder/volume/drivers/lvm.py", line 859, in validate_connector 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server return self.target_driver.validate_connector(connector) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/cinder/volume/targets/iscsi.py", line 297, in validate_connector 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server raise exception.InvalidConnectorException(missing='initiator') 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server cinder.exception.InvalidConnectorException: Connector doesn't have required information: initiator 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 276, in dispatch 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 196, in _do_dispatch 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/cinder/volume/manager.py", line 4554, in attachment_update 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server connector) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/cinder/volume/manager.py", line 4473, in _connection_create 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server raise exception.InvalidInput(reason=six.text_type(err)) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server cinder.exception.InvalidInput: Invalid input received: Connector doesn't have required information: initiator 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server Kind regards, Oliver

1 0

Fwd: DPDK+OVS with OpenStack
by Mark Wittling 12 Oct '20

12 Oct '20

Looking for someone who knows OpenStack with OpenVSwitch, and in addition to that, DPDK with OpenStack and OVS.I am using OpenStack Queens, with OpenVSwitch. The architecture I am using is documented here: https://docs.openstack.org/neutron/queens/admin/deploy-ovs-provider.htmlThe OVS I am using on the Compute Node, is compiled with DPDK, and I have enabled the datapath to netdev (DPDK) on br-prv (provider network bridge), and br-tun (tunneling bridge). But these two bridges, br-tun and br-prv, are patched into another OpenStack bridge, called br-int. I wasn’t actually sure about whether to tinker with this bridge, and wondered what datapath it was using.Then, I realized there is a parameter in the openvswitch_agent.ini file, which I will list here: # OVS datapath to use. 'system' is the default value and corresponds to the # kernel datapath. To enable the userspace datapath set this value to 'netdev'. # (string value) # Possible values: # system - <No description provided> # netdev - <No description provided> #datapath_type = system datapath_type = netdev So in tinkering with this, what I realized, is that when you set this datapath_type to system or netdev, it will adjust the br-int bridge to that datapath type.So here is my question. How can I launch a non-DPDK VM, if all of the bridges are using the netdev datapath type?Here is another question. What if one of the flavors don’t have the largepages property set on them? I assumed OpenStack would revert to a system datapath and not use DPDK for those VM interfaces. Well, I found out in testing, that is not the case. If you set all your bridges up for netdev, and you don’t set the property on the Flavor of the VM (largepages), the VM will launch, but it simply won’t work.Is there no way, on a specific Compute Host, to support both DPDK (netdev datapaths) and non-DPDK (system datapaths)?Either on a VM interface level (VM has one interface that is netdev DPDK and another that is system datapath non-DPDK)?Or on a VM by VM basis (VM 1 has 1 or more netdev datapath interfaces and VM 2 has 1 or more system datapath interfaces)?Am I right here? Once you set up a Compute Host for DPDK, it’s DPDK or nothing on that Compute Host? (edited)

2 1

[release][ptg] Wallaby PTG planning
by Herve Beraud 12 Oct '20

12 Oct '20

Hello, As you know our PTG starts on 26th October, we already have some topics to bring there, if you'd like to discuss something else during the session please add topics at https://etherpad.opendev.org/p/relmgmt-wallaby-ptg . If you plan to assist our meeting don't hesitate to add your name to the attendee list. I already proposed a date but if it doesn't fit your availability don't hesitate to propose another date. Cheers, -- Hervé Beraud Senior Software Engineer Red Hat - Openstack Oslo irc: hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

[sdk] empty image dict if volume is attached
by thoralf schulze 12 Oct '20

12 Oct '20

hi there, openstack instances that have a cinder volume attached as their primary block device won't return any information regarding the image that has been used during their creation: openstack server show -f shell -c image -c volumes_attached test1 image="" volumes_attached="id='c0650208-f39c-4427-a73b-e1aa88531016'" vs. openstack server show -f shell -c image -c volumes_attached test2 image="Ubuntu 20.04 LTS (5cf81857-0dba-497e-ad9a-23a88dd97506)" volumes_attached="" as a result, this information won't be available in ansible inventories created with the relevant plugin¹ either … this is unfortunate, since i need to set certain variables for ansible based on the image resp. the operating system an instance uses. now, the necessary information seems to be available as a volume's metadata: openstack volume show -f shell -c volume_image_metadata c0650208-f39c-4427-a73b-e1aa88531016 volume_image_metadata="{'signature_verified': 'False', 'hw_rng_model': 'virtio', 'hypervisor_type': 'qemu', 'os_distro': 'centos', 'os_type': 'linux', 'image_id': '1572c62f-438c-4a70-be84-973fef0d3c77', 'image_name': 'CentOS 8', 'checksum': 'd89eb49f2c264d29225cecf2b6c83322', 'container_format': 'bare', 'disk_format': 'qcow2', 'min_disk': '10', 'min_ram': '1024', 'size': '716176896'}" … would it be a good idea to extend openstacksdk to look for image_name in the volumes attached to an instance and use this value for the image key? thank you very much & with kind regards, t. ¹ - https://docs.ansible.com/ansible/latest/collections/openstack/cloud/opensta… , this plugin makes use of openstacksdk

1 1

[all][elections][ptl][tc] Combined PTL/TC Voting 48 Hours Remain
by Jeremy Stanley 11 Oct '20

11 Oct '20

We are coming down to the last hours for voting in the TC and Telemetry elections. Voting ends Oct 13, 2020 23:45 UTC. Search your Gerrit preferred email address[0] for the messages with subjects like... Poll: OpenStack Wallaby Cycle Technical Committee Election Poll That is your ballot and links you to the voting application. Please vote. If you have voted, please encourage your colleagues to vote. Candidate statements are linked to the names of all confirmed candidates: https://governance.openstack.org/election/ What to do if you don't see the email and have a commit in at least one of the official project teams' deliverable repositories[1]: * check the trash of your Gerrit Preferred Email address[0], in case it went into trash or spam * find the ID of at least one commit merged to an official deliverable repo[1] over the current or previous cycle, confirm you are an OpenStack Foundation Individual Member[2], and then email the election officials[3] or get in touch in the #openstack-elections channel on the Freenode IRC network. If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Please vote! Thank you, [0] Sign into review.openstack.org and go to Settings > Contact Information. Look at the email listed as your Preferred Email. That is where the ballot has been sent. [1] https://opendev.org/openstack/governance/src/tag/0.8.0/reference/projects.y… [2] https://www.openstack.org/profile/ [3] https://governance.openstack.org/election/#election-officials -- Jeremy Stanley

1 0

[all][tc][goals] Migrate CI/CD jobs to new Ubuntu LTS Focal : Final update
by Ghanshyam Mann 10 Oct '20

10 Oct '20

Hello Everyone, With the Integration testing moved to Ubuntu Focal, I am marking the 'Ubuntu Focal migration' community goal as complete. Tracking: https://storyboard.openstack.org/#!/story/2007865 Summary: ======== * Lot of work was involved in this. There are many changes required for this migration as compare to previous migration from Xenial to Bionic. ** Many dependencies lower constraint compatible with py3.8 and Focal distro had to be updated. Almost in all the repos. ** Mysql 8.0 caused many incompatible DB issues. * I missed the original deadline of m-2 to complete this goal due to falling gates and to avoid any gate block for any projects. * More than 300 repo had been fixed or tested in advance before migration happened. This helped a lot to keep gate green during this migration. * We had to keep few jobs in Bionic due to time constraints and move the rest of the other projects jobs on Focal. These are under work by the respective team. ** Manila, freezer-tempest, magnum-tempest-plugin-tests-api, ironic-python-agent-builder due to diskimage-builder[1] etc * Deployment projects are communicated (openstack-helm, tripleo if needed) or already in-progress (puppet-openstack) for this migration and the respective team need to check if any updates needed. I would like to convey special Thanks to everyone who helped in this goal and made it possible to complete it in Victoria cycle itself. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-October/017843.… -gmann

2 1

[Magnum][kolla-ansible][kayobe] Information gathering for 2 blocking issues
by Tony Pearce 09 Oct '20

09 Oct '20

Hi all, hope you are all keeping safe and well. I am looking for information on the following two issues that I have which surrounds Magnum project: 1. Magnum does not support Openstack API with HTTPS 2. Magnum forces compute nodes to consume disk capacity for instance data My environment: Openstack Train deployed using Kayobe (Kolla-ansible). With regards to the HTTPS issue, Magnum stops working after enabling HTTPS because the certificate / CA certificate is not trusted by Magnum. The certificate which I am using is one that was purchased from GoDaddy and is trusted in web browsers (and is valid), just not trusted by the Magnum component. Regarding compute node disk consumption issue - I'm at a loss with regards to this and so I'm looking for more information about why this is being done and is there any way that I could avoid it? I have storage provided by a Cinder integration and so the consumption of compute node disk for instance data I need to avoid. Any information the community could provide to me with regards to the above would be much appreciated. I would very much like to use the Magnum project in this deployment for Kubernetes deployment within projects. Thanks in advance, Regards, Tony

3 9

[release] Release countdown for week R-0 Oct 12-16
by Sean McGinnis 09 Oct '20

09 Oct '20

Development Focus ----------------- We will be releasing the coordinated OpenStack Victoria release next week, on October 14. Thanks to everyone involved in the Victoria cycle! We are now in pre-release freeze, so no new deliverable will be created until final release, unless a release-critical regression is spotted. Otherwise, teams attending the virtual PTG should start to plan what they will be discussing there, by creating and filling team etherpads. You can access the list of PTG etherpads at: http://ptg.openstack.org/etherpads.html General Information ------------------- On release day, the release team will produce final versions of deliverables following the cycle-with-rc release model, by re-tagging the commit used for the last RC. A patch doing just that will be proposed. PTLs and release liaisons should watch for that final release patch from the release team. While not required, we would appreciate having an ack from each team before we approve it on the 16th, so that their approval is included in the metadata that goes onto the signed tag. Upcoming Deadlines & Dates -------------------------- Final Victoria release: October 14 Open Infra Summit: October 19-23 Wallaby PTG: October 26-30

1 0