September 2020 - openstack-discuss

device compatibility interface for live migration with assigned devices
by Yan Zhao 15 Sep '20

15 Sep '20

hi folks, we are defining a device migration compatibility interface that helps upper layer stack like openstack/ovirt/libvirt to check if two devices are live migration compatible. The "devices" here could be MDEVs, physical devices, or hybrid of the two. e.g. we could use it to check whether - a src MDEV can migrate to a target MDEV, - a src VF in SRIOV can migrate to a target VF in SRIOV, - a src MDEV can migration to a target VF in SRIOV. (e.g. SIOV/SRIOV backward compatibility case) The upper layer stack could use this interface as the last step to check if one device is able to migrate to another device before triggering a real live migration procedure. we are not sure if this interface is of value or help to you. please don't hesitate to drop your valuable comments. (1) interface definition The interface is defined in below way: __ userspace /\ \ / \write / read \ ________/__________ ___\|/_____________ | migration_version | | migration_version |-->check migration --------------------- --------------------- compatibility device A device B a device attribute named migration_version is defined under each device's sysfs node. e.g. (/sys/bus/pci/devices/0000\:00\:02.0/$mdev_UUID/migration_version). userspace tools read the migration_version as a string from the source device, and write it to the migration_version sysfs attribute in the target device. The userspace should treat ANY of below conditions as two devices not compatible: - any one of the two devices does not have a migration_version attribute - error when reading from migration_version attribute of one device - error when writing migration_version string of one device to migration_version attribute of the other device The string read from migration_version attribute is defined by device vendor driver and is completely opaque to the userspace. for a Intel vGPU, string format can be defined like "parent device PCI ID" + "version of gvt driver" + "mdev type" + "aggregator count". for an NVMe VF connecting to a remote storage. it could be "PCI ID" + "driver version" + "configured remote storage URL" for a QAT VF, it may be "PCI ID" + "driver version" + "supported encryption set". (to avoid namespace confliction from each vendor, we may prefix a driver name to each migration_version string. e.g. i915-v1-8086-591d-i915-GVTg_V5_8-1) (2) backgrounds The reason we hope the migration_version string is opaque to the userspace is that it is hard to generalize standard comparing fields and comparing methods for different devices from different vendors. Though userspace now could still do a simple string compare to check if two devices are compatible, and result should also be right, it's still too limited as it excludes the possible candidate whose migration_version string fails to be equal. e.g. an MDEV with mdev_type_1, aggregator count 3 is probably compatible with another MDEV with mdev_type_3, aggregator count 1, even their migration_version strings are not equal. (assumed mdev_type_3 is of 3 times equal resources of mdev_type_1). besides that, driver version + configured resources are all elements demanding to take into account. So, we hope leaving the freedom to vendor driver and let it make the final decision in a simple reading from source side and writing for test in the target side way. we then think the device compatibility issues for live migration with assigned devices can be divided into two steps: a. management tools filter out possible migration target devices. Tags could be created according to info from product specification. we think openstack/ovirt may have vendor proprietary components to create those customized tags for each product from each vendor. e.g. for Intel vGPU, with a vGPU(a MDEV device) in source side, the tags to search target vGPU are like: a tag for compatible parent PCI IDs, a tag for a range of gvt driver versions, a tag for a range of mdev type + aggregator count for NVMe VF, the tags to search target VF may be like: a tag for compatible PCI IDs, a tag for a range of driver versions, a tag for URL of configured remote storage. b. with the output from step a, openstack/ovirt/libvirt could use our proposed device migration compatibility interface to make sure the two devices are indeed live migration compatible before launching the real live migration process to start stream copying, src device stopping and target device resuming. It is supposed that this step would not bring any performance penalty as -in kernel it's just a simple string decoding and comparing -in openstack/ovirt, it could be done by extending current function check_can_live_migrate_destination, along side claiming target resources.[1] [1] https://specs.openstack.org/openstack/nova-specs/specs/stein/approved/libvi… Thanks Yan

14 118

[manila][ptg] Wallaby PTG Planning
by Goutham Pacha Ravi 15 Sep '20

15 Sep '20

Hello Zorillas and Interested Stackers, As you're aware, the virtual PTG for the Wallaby release cycle is between October 26-30, 2020. If you haven't registered yet, you must do so as soon as possible! [1]. We've signed up for some slots on the PTG timeslots ethercalc [2]. The PTG Planning etherpad [3] is now live. Please go ahead and add your name/irc nick and propose any topics. You may propose topics even if you wouldn't like to moderate the discussion. Thanks, and hope to see you all there! Goutham [1] https://www.eventbrite.com/e/project-teams-gathering-october-2020-tickets-1… [2] https://ethercalc.openstack.org/7xp2pcbh1ncb [3] https://etherpad.opendev.org/p/wallaby-ptg-manila-planning

1 0

[Outreachy] Call for mentors, projects by Sep 29
by Samuel de Medeiros Queiroz 15 Sep '20

15 Sep '20

Hey Stackers, *TL;DR OpenStack is participating in the Outreachy internship program once again!* *Please submit projects as soon as possible, with final deadline being Sept. 29, 2020 at 4 pm UTC: https://www.outreachy.org/communities/cfp/openstack/ <https://www.outreachy.org/communities/cfp/openstack/>* Outreachy's goal is to support people from groups underrepresented in the technology industry. Interns will work remotely with mentors from our community. We are seeking mentors to propose projects that Outreachy interns can work on during their internship. If you want help crafting your project proposal, please contact me < samueldmq(a)gmail.com> or Mahati Chamarthy <mahati.chamarthy(a)gmail.com>. Mentors should read the mentor FAQ: https://www.outreachy.org/mentor/mentor-faq Full details about the Outreachy program and the internship timeline can be found on the Call for Participation page on the Outreachy website: https://www.outreachy.org/communities/cfp/ Thank you, Samuel Queiroz

1 0

memchached connections
by Tony Liu 15 Sep '20

15 Sep '20

Hi, Is there any guidance or experiences to estimate the number of memcached connections? Here is memcached connection on one of the 3 controllers. Connection number is the total established connections to all 3 memcached nodes. Node 1: 10 Keystone workers have 62 connections. 11 Nova API workers have 37 connections. 6 Neutron server works have 4304 connections. 1 memcached has 4973 connections. Node 2: 10 Keystone workers have 62 connections. 11 Nova API workers have 30 connections. 6 Neutron server works have 3703 connections. 1 memcached has 4973 connections. Node 3: 10 Keystone workers have 54 connections. 11 Nova API workers have 15 connections. 6 Neutron server works have 6541 connections. 1 memcached has 4973 connections. Before I increase the connection limit for memcached, I'd like to understand if all the above is expected? How Neutron server and memcached take so many connections? Any elaboration is appreciated. BTW, the problem leading me here is memcached connection timeout, which results all services depending on memcached stop working properly. Thanks! Tony

3 6

WIndows 10 instance hostname not updating
by its-openstack＠zohocorp.com 15 Sep '20

15 Sep '20

Dear openstack, I have installed openstack train branch, I am facing issue with windows image. all windows 10 instance dosen't get its hostname updated from the metadata, but able to get the metadata(hostname) from inside the instance using powershell. ``` $ Invoke-WebRequest http://169.254.169.254/latest/meta-data/hostname -UseBasicParsing ``` windows2016 instance no issue. using the stable cloudbase-init package for preparation of windows 10 (tried bot in v1909 and v2004). windows2016 server dosen't have this issue. if you would so kindly help us with this issue Regards sysadmin

2 1

[TC] Seats Available in Upcoming Elections
by Kendall Nelson 14 Sep '20

14 Sep '20

Hello :) Wanted to make you all aware of the conversation that happened in the TC channel today[1] which was a reminder of a previous conversation about reducing the size of the TC. It was concluded by the previous TC that we would gradually reduce from 13 seats to 9 over the course of two elections (dropping two seats each election). From that point on, we would continue with the normal cadence of cycling about half the seats each election ( 4 seats and 5 seats)[2]. So, this coming election 6 members will be up for reelection with 4 seats available. Hope this all makes sense! -Kendall Nelson (diablo_rojo) - Both a TC member up for re-election and a former election official :) [1] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/latest.log.html#t202… [2] https://review.opendev.org/#/c/681266/

1 0

REMINDER: 2020 Virtual Summit: Forum Submissions Now Accepted
by Jimmy McArthur 14 Sep '20

14 Sep '20

Hello Everyone! We are now accepting Forum [1] submissions for the 2020 Virtual Open Infrastructure Summit [2]. Please submit your ideas through the Summit CFP tool [3] through September 14th. Don't forget to put your brainstorming etherpad up on the Virtual Forum page [4]. This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. The timeline for submissions is as follows: Aug 31st | Formal topic submission tool opens: https://cfp.openstack.org. Sep 14th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. Sep 21st | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. Sept 28th | Forum schedule final Oct 19th | Forum begins! If you have questions or concerns, please reach out to speakersupport(a)openstack.org (mailto:speakersupport@openstack.org). Cheers, Jimmy [1] https://wiki.openstack.org/wiki/Forum [2] https://www.openstack.org/summit/2020/ [3] https://cfp.openstack.org [4]https://wiki.openstack.org/wiki/Forum/Virtual2020

4 5

[release] [heat] [karbor] [patrole] [requirements] [swift] [tempest] Cycle with Intermediary Deliverables Needing Releases?
by Kendall Nelson 14 Sep '20

14 Sep '20

Hello! Quick reminder that for deliverables following the cycle-with-intermediary model, the release team will use the latest victoria release available on release week. The following deliverables have done a victoria release, but it was not refreshed in the last two months: - heat-agents - karbor-dashboard - karbor - patrole - requirements - swift - tempest You should consider making a new one very soon, so that we don't use an outdated version for the final release. -Kendall Nelson (diablo_rojo) & the Release Team

1 0

Is Storyboard really the future?
by Radosław Piliszek 14 Sep '20

14 Sep '20

Hi fellow OpenStackers, The subject is the question I am posing. The general recommendation is to use Storyboard for new projects [1]. However, Storyboard does not seem to be receiving enough love recently [2] [3]. It's generally deemed as slow [4] and is missing quite a few usability enhancements [2]. Considering the alternative, and the actual previous recommendation, is Launchpad, I find it no-brainer to revert to recommending Launchpad still, even paving a way for projects wishing to escape the Storyboard nightmare. :-) Don't get me wrong, I really like the Story/Task orientation but Storyboard results in a frustrating experience. In addition to being slow, it has issues with search/filter, sorting and pagination which make issue browsing an utter pain. I know Launchpad is not without issues but it's certainly a much better platform at the moment. And many projects are still there. The Launchpad-Storyboard split is also introducing confusion for users [5] and coordinability issues for teams as we need to cross-link manually to get proper visibility. All in all, I ask you to consider recommending Launchpad again and encourage OpenStack projects to move to Launchpad. Extra note: I find it in a similar spot as ask.o.o - nice it has been tried, but unfortunately it did not stand the test of time. [1] https://docs.opendev.org/opendev/infra-manual/latest/creators.html [2] https://storyboard.openstack.org/#!/project/opendev/storyboard [3] https://opendev.org/opendev/storyboard/commits/branch/master [4] https://storyboard.openstack.org/#!/story/2007829 [5] https://storyboard.openstack.org/#!/story/2000890 -yoctozepto

5 11

[oslo] PTG Planning
by Ben Nemec 14 Sep '20

14 Sep '20

It's that time again. I've created an etherpad[0] for Oslo PTG planning. If you have anything to discuss at the PTG, please add it to the list. I've already requested a couple of hours of PTG time, but we can adjust that if we have more or less to talk about than normal. I don't have time/place details there yet, but it will be the same as last time: two hours starting at the regular meeting time. Thanks. -Ben 0: https://etherpad.opendev.org/p/oslo-wallaby-topics

1 0