July 2019 - openstack-discuss - lists.openstack.org

Instance (vm guest) not getting PCI card
by Mauricio Tavares 03 Jul '19

03 Jul '19

Newbie and easy questions: I have two cards, one in each stein (centos) compute node setup for kvm, which I want to be able to handle to a vm guest (instance). Following https://docs.openstack.org/nova/latest/admin/pci-passthrough.html, I 1. Setup both computer nodes to vt-t and iommu. 2. On the controller 2.1. Create a PCI alias based on the vendor and product ID alias = { "vendor_id":"19fg", "product_id":"4000", "device_type":"type-PF", "name":"testnic" } - The PCI address for the card is different on each compute node 2.2. Create a flavor, say, n1.large openstack flavor create n1.large --id auto --ram 8192 --disk 80 --vcpus 4 --property "pci_passthrough:alias"="testnic:1" 2.3. Restart openstack-nova-api 3. On each compute node 3.1. Create a PCI alias based on the vendor and product ID alias = { "vendor_id":"19fg", "product_id":"4000", "device_type":"type-PF", "name":"testnic" } 3.2. Create passthrough_whitelist entry passthrough_whitelist = { "vendor_id":"19fg", "product_id":"4000" } 3.3. Restart openstack-nova-compute 4. Create instance (vm guest) using the n1.large flavor. 5. Login to instance and discover dmesg and lspci does not list card 6. Do a "virsh dumpxml" for the instance on its compute node and discover there is no entry for the card listed in the xml file. I take nova would automagically do what I would if this was a kvm install, namely ensure card cannot be accessed/used by the host and then edit the guest xml file so it can see said card. Questions: Q1: If a device is sr-iov capable, do I have to use that or can I just pass the entire card to the vm guest? Q2: Is there anywhere I can look for clues to why is the libvirt xml file for the instance not being populated with the pci card info? So far I only looked in the controller node's nova_scheduler.log file.

2 2

[magnum][queens] Floating ip error
by Ignazio Cassano 03 Jul '19

03 Jul '19

Hello All, I've just install queens kolla openstack qith magnum but when I try to create a docker swarm cluster the magnum conductor reports: <file:///var/lib/kolla/venv/lib/python2.7/site-packages/magnum/drivers/common/templates/lb.yaml>: : The Resource Type (Magnum::Optional::Neutron::LBaaS::FloatingIP) could not be found. I tried lbaas and floating ip works of magnum context. Does it requires octavia ? Regards Ignazio

1 0

[all][qa] Tempest jobs are swapping
by Clark Boylan 03 Jul '19

03 Jul '19

I've been working to bring up a new cloud as part of our nodepool resource set and one of the things we do to sanity check that is run a default tempest full job. The first time I ran tempest it failed because I hadn't configured swap on the test node and we ran out of memory. I added swap, reran things and tempest passed just fine. Our base jobs configure swap as a last ditch effort to avoid failing jobs unnecessarily but the ideal is to avoid swap entirely. In the past 8GB of memory has been plenty to run the tempest testsuite so I think something has changed here and I think we should be able to get us running back under 8GB of memory again. I bring this up because in recent weeks we've seen different groups attempt to reduce their resource footprint (which is good), but many of the approaches seem to ignore that making our jobs as quick and reliable as possible (eg don't use swap) will have a major impact. This is due to the way gating works where a failure requires we discard all results for subsequent changes in the gate, remove the change that failed, then re enqueue jobs for the changes after the failed change. On top of that the quicker our jobs run the quicker we return resources to the pool. How do we debug this? Devstack jobs actually do capture dstat data as well as memory specific information that can be used to identify resource hogs. Taking a recent tempest-full job's dstat log we can see that cinder-backup is using 785MB of memory all on its own [0] (scroll to the bottom). Devstack also captures memory usage of a larger set of processes in its peakmem_tracker log [1]. This includes RSS specifically which doesn't match up with dstat's number making me think dstat's number may be virtual memory and not resident memory. This peakmem_tracker log identifies other processes which we might look at for improving this situation. It would be great if the QA team and various projects could take a look at this to help improve the reliability and throughput of our testing. Thank you. [0] http://logs.openstack.org/81/665281/3/check/tempest-full/cf5e17e/controller… [1] http://logs.openstack.org/81/665281/3/check/tempest-full/cf5e17e/controller…

3 2

[Scientific] No Scientific SIG meeting Jul 3rd
by Martial Michel 03 Jul '19

03 Jul '19

Sending this email to inform you that we will not be having a Scientific SIG meeting Today. Hopefully next week -- Martial

1 0

[Shanghai Summit] CFP Deadline TONIGHT
by Ashlee Ferguson 03 Jul '19

03 Jul '19

Hi everyone, The Shanghai Summit Call for Presentations [1] deadline is TONIGHT, July 2 at 11:59 pm PT (July 3, 2019 at 15:00 China Standard Time)! Submit your presentations, panels, and Hands-on Workshops for the Open Infrastructure Summit [2] by the end of today, and join the global community in Shanghai, November 4-6, 2019. Sessions will be presented in both Mandarin and English, so you may submit your presentation in either language. Tracks [4]: 5G, NFV & Edge AI, Machine Learning & HPC CI/CD Container Infrastructure Getting Started Hands-on Workshops Open Development Private & Hybrid Cloud Public Cloud Security Other Helpful Shanghai Summit & PTG Information-- * Register now [5] before the early bird registration deadline in early August (USD or RMB options available) * Apply for Travel Support [6] before August 8. More information here [7]. * Interested in sponsoring the Summit? [8]. * The content submission process for the Forum and Project Teams Gathering will be managed separately in the upcoming months. We look forward to your submissions! Cheers, Ashlee [1] https://cfp.openstack.org/ <https://cfp.openstack.org/> [2] https://www.openstack.org/summit/shanghai-2019/ <https://www.openstack.org/summit/shanghai-2019/> [3] https://cfp.openstack.org/ <https://cfp.openstack.org/> [4] https://www.openstack.org/summit/shanghai-2019/summit-categories/ <https://www.openstack.org/summit/shanghai-2019/summit-categories/> [5] https://www.openstack.org/summit/shanghai-2019/ <https://www.openstack.org/summit/shanghai-2019/> [6] https://openstackfoundation.formstack.com/forms/travelsupportshanghai <https://openstackfoundation.formstack.com/forms/travelsupportshanghai> [7] https://www.openstack.org/summit/shanghai-2019/travel/ <https://www.openstack.org/summit/shanghai-2019/travel/> [8] https://www.openstack.org/summit/shanghai-2019/sponsors/ <https://www.openstack.org/summit/shanghai-2019/sponsors/>

3 2

RE: HPE 3PAR Cinder driver-Multiattach: Fails to detach second instance from volume
by RAI, SNEHA 03 Jul '19

03 Jul '19

Hi All, Is there a way to find in cinder how many instances are attached to a volume? Thanks & Regards, Sneha Rai From: RAI, SNEHA Sent: Monday, July 1, 2019 5:26 PM To: openstack-dev(a)lists.openstack.org Subject: HPE 3PAR Cinder driver-Multiattach: Fails to detach second instance from volume Hi Team, There is a bug on 3PAR Cinder driver https://bugs.launchpad.net/cinder/+bug/1834660. I am able to attach multiple instances to 3PAR volume but only the first instance gets detached successfully. For the second instance, volume goes into detaching status due to "Host does not exist" error. What is happening here is, the first detach call invokes _delete_3par_host() which removes the compute host entry from 3PAR which ideally should be done only when the last instance is to be detached. It would be great if someone could help me understand if this needs to be handled in driver code or nova would internally take care of it. Code changes done to support multiattach-https://review.opendev.org/#/c/659443 Thanks & Regards, Sneha Rai

3 2

[Watcher] team meeting at 08:00 UTC today
by li.canwei2＠zte.com.cn 03 Jul '19

03 Jul '19

Hi all, Watcher team will have a meeting at 08:00 UTC today in the #openstack-meeting-alt channel. The agenda is available on https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda feel free to add any additional items. Thanks! Canwei Li

1 0

[PTL] update FC_SIG liaison list reminder
by Matthew Oliver 03 Jul '19

03 Jul '19

Hey PTLs, I'm one of your friendly First Contact SIG (FC_SIG) representatives, and previously emailed you fine folk asking if you could take a look at the FC_SIG liaison list[0] and update it as needed. As mentioned in the PTL guide[1]. For those of you who have already done that thing, awesome, thanks so much. If you haven't had a chance yet it would be fantastic if you could! What is a FC_SIG liaison, they will be the person we contact or add to a review when a new contributor contacts us and wants to work on your project or we find a new patch from a new contributor and we want to make sure they get all the love they need to get them engaged. So what's important here is having the liaison's details, including timezone, up to date. Also note more then 1 liaison in more then 1 timezone would be preferred (if it can be manged), so we can connect new contributors with someone closer to them. If a project doesn't have a liaison then it'll default to the PTL, but we'd still rather have the PTL in the list with timezones as that makes it easier for us. So talk about it in your teams. Thanks, Matt [0] - https://wiki.openstack.org/wiki/CrossProjectLiaisons#First_Contact_SIG [1] - https://docs.openstack.org/project-team-guide/ptl.html#at-the-beginning-of-…

1 0

[Zun][Kata] Devstack plugin for installing Kata container
by Hongbin Lu 03 Jul '19

03 Jul '19

Hi all, I have a patch [1] that adds support for installing kata Container in devstack. Right now, it configures kata container to run with Docker. In the future, I plan to add support for containerd's cri plugin, which basically allows running pods with kata container. Initially, OpenStack Zun will use this plugin to install Kata container, but I believe it would be beneficial for other projects. Appreciate if anyone interest to cast your feedback on the patch. [1] https://review.opendev.org/#/c/668490/ Best regards, Hongbin

2 1

[TripleO] The Transformation Squad meeting canceled - 4 July, 2019
by Kevin Carter 02 Jul '19

02 Jul '19

Hello all, I wanted to let everyone know that the Transformation Squad team meeting will be canceled this coming Thursday; 4 July, 2019 @ 13:00UTC. We will continue with regular meetings on 11 July, 2019 @ 13:00UTC. If there are questions about this cancellation, or anything else, please let us know. Thank you and have a great week. -- Kevin Carter IRC: cloudnull

1 0