September 2021 - openstack-discuss

[Image Encryption] Next Meeting on Monday 13
by Josephine Seifert 06 Sep '21

06 Sep '21

Hi everyone, as I am on vacation the next meeting will be next monday - the 13th of September. greetings Josephine (Luzi)

1 0

[nova][placement] Xena release
by Balazs Gibizer 06 Sep '21

06 Sep '21

Hi, We are getting close to the Xena release. So I created a tracking etherpad[1] with the schedule and TODOs. One thing that I want to highlight is that we will hit Feature Freeze on 3rd of September. As the timeframe between FF and RC1 is short I'm not plannig with FFEs. Patches that are approved before 3rd of Sept EOB can be rechecked or rebased if needed and then re-approved. If you have a patch that is really close but not approved before the deadline, and you think there are two cores that willing to review it before RC1, then please send a mail to the ML with [nova][FFE] subject prefix not later than 7th of Sept EOB. Cheers, gibi [1] https://etherpad.opendev.org/p/nova-xena-rc-potential

1 1

[cinder] discuss nas_secure options and root_squash (prohibiting root access to share)
by Stefan Hoffmann 06 Sep '21

06 Sep '21

Hi cinder team, like discussed in the last meeting, I prepared a list [1] of combinations of the nas_secure options and when to use them. If one want to prohibit root access to NFS share, only setting nas_secure_file_operations and nas_secure_file_permissions to true is a useful option, I think. (Option 4) But also the nas_secure_file_operations is not useful to determine if _qemu_img_info and fs access check at _connect_device should be done with root user or cinder user. So I will update the change [2] like proposed in the etherpad. Feel free to add other use cases and hints for the options to [1] and discuss about the proposed change. Regards Stefan [1] https://etherpad.opendev.org/p/gSotXYAZ3JfJE8FEpMpS [2] https://review.opendev.org/c/openstack/cinder/+/802882 Initial Bug: https://bugs.launchpad.net/cinder/+bug/1938196?comments=all

1 1

[manila][FFE] Feature freeze exception request
by Carlos Silva 03 Sep '21

03 Sep '21

Hello, everyone! I'd like to request feature freeze exceptions to some changes: [1] https://review.opendev.org/c/openstack/manila/+/803623 - Enhancements to Manila's share server migration mechanism. It will allow administrators to perform non-disruptive migrations of share servers in the cloud. [2] https://review.opendev.org/c/openstack/manila/+/803624 - New share server migration mechanism added to the NetApp ONTAP driver. With this, administrators will be able to migrate share servers nondisruptively. [3] https://review.opendev.org/c/openstack/manila/+/803622 Add support for FlexGroups in the NetApp ONTAP driver for Manila. With this feature, petabyte scale filesystems will be feasible. All changes I have mentioned were submitted in time in the feature proposal freeze for Manila, and there has been significant progress in the reviews until this point. We're working through the last of the minor enhancements reviewers have called for. These changes are isolated to the NetApp driver module, and have no impact to the manila database, REST/RPC API. Regards, carloss

2 1

[all][tc] What's happening in Technical Committee: summary 3rd Sept, 21: Reading: 5 min
by Ghanshyam Mann 03 Sep '21

03 Sep '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * TC held this week's IRC meeting (Video call) on Sept 2nd Thursday. * Most of the meeting discussions are summarized in the below sections (Completed or in-progress activities section). To know more details, you can check the video recording@ (we will find a better place to put the recording next time.) - https://drive.google.com/drive/folders/16NiC60Gm8BXjZw6XCJrto6lMi6OigTiQ?us… * We will have next week's meeting on Sept 9th, Thursday 15:00 UTC on IRC, feel free the topic in agenda [1] by Sept 8th. 2. What we completed this week: ========================= * Closeout Yoga TC Election[2] * Added two more release liaisons for Keystone[3] * Retired puppet-monasca[4] 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the etherpad[5] for Xena cycle working item. We will be checking and updating the status biweekly in the same etherpad. Open Reviews ----------------- * Five open reviews for ongoing activities[6]. Combined PTL/TC Election Season for Yoga ---------------------------------------------------- * TC election are closeout[2]. * TC chair and vice-chair nomination are also up for review/vote. * PTL election (Cyborg project having election) is going on. Leaderless projects ----------------------- * From the current nomination, we have six leaderless projects[7]. Out of them, we have five projects leaders volunteer (a few are late candidacy). One project 'Adjutant' still needs someone to step up to lead this project. Please add your name to etherpad if you are interested. Rico will also be reaching out to the previous PTL and team about it. New project application: 'Venus' -------------------------------------- * We discussed this application and all the queries are answered either on patch or ML. TC decided to start the voting in Gerrit patch[8]. Collecting Pain points from projects/SIGs/pop-up ----------------------------------------------------------- * We spend most of the meeting time on this topic. We have not gone through all the pain points mentioned in etherpad[9] but collecting two common pain points 1. rabbitMQ 2. OSC which we should continue or start discussing at the TC level. Other pain points are more project-specific. * We will continue discussing it in PTG, join us if you are interested to help/discuss this topic. Project updates ------------------- * Retiring js-openstack-lib [10] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [11]. * Current status: "Secure RBAC" is selected for Yoga cycle[12]. PTG planning ---------------- * We are collecting the PTG topics in etherpad[13], feel free to add any topic you would like to discuss. * We discussed the live stream of one of the TC PTG sessions like we did last time. Once we will have more topics in etherpad then we can select the appropriate one. Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[14], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. 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[15]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [16] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [17] 4. 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/+/806270 [3] https://review.opendev.org/c/openstack/governance/+/806615 [4] https://review.opendev.org/c/openstack/governance/+/805105 [5] https://etherpad.opendev.org/p/tc-xena-tracker [6] https://review.opendev.org/q/project:openstack/governance+status:open [7] https://etherpad.opendev.org/p/yoga-leaderless [8] https://review.opendev.org/c/openstack/governance/+/804824 [9] https://etherpad.opendev.org/p/pain-point-elimination [10] https://review.opendev.org/c/openstack/governance/+/798540 [11] https://etherpad.opendev.org/p/y-series-goals [12] https://review.opendev.org/c/openstack/governance/+/803783 [13] https://etherpad.opendev.org/p/tc-yoga-ptg [14] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [15] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [16] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [17] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

[release] Release countdown for week R-4, Sep 06 - Sep 10
by Herve Beraud 03 Sep '21

03 Sep '21

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the Xena deliverables can be proposed, well ahead of the final Xena release date (06 October, 2021). General Information ------------------- We are still finishing up processing a few release requests, but the Xena release requirements are now frozen. If new library releases are needed to fix release-critical bugs in Xena, you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in Xena that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By 30 September this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/xena branches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for Xena changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed Xena cycle-highlights yet, you are already late to the party. Please see http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024105.h… for details. Upcoming Deadlines & Dates -------------------------- RC1 deadline: 16 September (R-3 week) Final RC deadline: 30 September (R-1 week) Final Xena release: 6 October Thanks for your attention -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

[kolla][wallaby][neutron] router ha not working
by Ignazio Cassano 03 Sep '21

03 Sep '21

Hello Everyone, I am facing an issue with router-ha in kolla wallaby. In my neutron.conf I inserted l3_ha = True max_l3_agents_per_router = 3 l3_ha_net_cidr = 169.254.192.0/18 but router ha does not work. The router namespace is present only on one of the three contrllers and if the controller goes down routing stop to work. I am using ovs and not ovn. Any help,please ? Ignazio

1 4

[TripleO] "cs9" hashtag for changes related to CenOS Stream 9 support
by Cédric Jeanneret 03 Sep '21

03 Sep '21

Hello there, We currently see a nice effort in order to integrate CentOS Stream 9 support in code base and CI. In order to make everything easier to track, it would be really nice if everyone working on that topic could set a simple "cs9" hashtag on their changes. This will allow to follow things with this link: https://review.opendev.org/q/hashtag:%22cs9%22+(status:open%20OR%20status:m… Thank you in advance! Cheers, C. -- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/

1 0

[nova]is there support for discard/trim in virtio-blk?
by Sven Kieske 03 Sep '21

03 Sep '21

Hi, according to our research discard/trim is commonly documented as "not supported by virtio-blk" in the wider community and in openstack nova[0]. I understand that this was not supported by the kernel or qemu when discard support was initially implemented[1] in openstack, but times have changed. Virtio-blk in upstream Kernel[2] and in qemu[3] does clearly support discard/trim, which we discovered thanks to StackExchange[4]. So my question is, has someone successfully used trim/discard with virtio-blk in nova provisioned vms? [1] makes me guess, that there is no codepath that works with virtio-blk, but I'm not sure I understood all the codepaths in nova yet. we are still working our way through it, though. We currently use the train release in conjunction with ceph rbd volumes for testing this feature but weren't yet able to use it successfully. Looking at nova's master branch not much seems to have changed regarding trim support. If this is no supported configuration currently, should I submit a blueprint to enable this feature? Would there be other devs/ops interested in this? Any help or pointers would be appreciated. [0]: https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L… (nova debug log saying discard is unsupported for virtio) [1]: https://blueprints.launchpad.net/nova/+spec/cinder-backend-report-discard (initial implementation of discard support in openstack) [2]: https://github.com/torvalds/linux/commit/1f23816b8eb8fdc39990abe166c10a18c1… (available since linux 5.0-rc1) [3]: https://github.com/qemu/qemu/commit/37b06f8d46fe602e630e4bdce24e80a3e0f70cc2 (available since qemu 4.0.0) [4]: https://unix.stackexchange.com/a/518223 -- Mit freundlichen Grüßen / Regards Sven Kieske Systementwickler / systems engineer Mittwald CM Service GmbH & Co. KG Königsberger Straße 4-6 32339 Espelkamp Tel.: 05772 / 293-900 Fax: 05772 / 293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer, Florian Jürgens St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen Informationen zur Datenverarbeitung im Rahmen unserer Geschäftstätigkeit gemäß Art. 13-14 DSGVO sind unter www.mittwald.de/ds abrufbar.

4 4

Unable to attach a Volume to Openstack WIndows instance
by KK CHN 02 Sep '21

02 Sep '21

List, I am trying to import a multi disk Windows VM ( 100GB bootable disk and 600 GB data volume disk) exported from HyperV to Openstack(Ussuri, Qemu-KVM, Glance image store, Cinder volume with Ceph backend). I am able to import the First bootable disk(vhdx converted to qcow2 ) with Windows VM in the OpenStack and its up and running able to login. ONE BASIC queston I not perfomed the *"Virt IO Injection steps"* as I am not sure whether for existing Windows VMs exported from HyperV need this Injection or not . Some one can clarify or defend this statement * " That Any Windows VM with Volume disks attached to it running on Other HyperVisor( say HyperV in my case, oVirt) exported to openstack which uses qemu-kvm needed the VirtIO Injection must done before importing to OpenStack with KVM for these Windows VMs for up and running and for attaching volume disks which also exported from other hypervisors . " OR only performance improvement only VirtIO injection do, so that I can avoid VirtIO injection for importing WIndowsVMs with multi disk to OpenStack.* used this step to import the converted bootable disk to my openstack. # openstack image create “Your_Windows_VM_NAME_Blaah” --file Windows_VM_disk1.qcow2 --disk-format qcow2 --container-format bare --public --property hw_firmware_type=uefi --property os_secure_boot=required --property hw_disk_bus=ide I am trying to import the second disk # openstack image create “Your_Windows_VM_NAME_Blah” --file Windows_VM_disk2.qcow2 --disk-format qcow2 --public and tried to create Volume through horizon dashboard with this image and 600 GB space. But volume creation itself showing status creating for more than 1 hour for now . Is this usual behaviour or some this wrong ? Note: so this volume creation from image is taking long time. As trial and error method I tried to create a small plain volume and attach this to the running WIndows VM(Windows2012 RC). But failed. I tried to create a plain 20 GB volume from the Horizon GUI and its created with in 30 seconds.. And tried to attach this volume to the Windows VM disk1 which is running and not got attached. ( I shutdown the Windows VM and tried to attach) same result. not attached. A plain volume also unable to got attached to the Windows VM ? why ? But the large 600GB goes for long hours. ( yesterday also tried and it was in creating state for 5 to 10 hours and I was waiting with no use, then I used the cinder command to change the volume status to "available" and then removed the volume which had not yet changed the state from "creating" to ``available" . Why do these volume creations with large disk space go for hours ? Are there any short steps to make it fast ? Any hints most

1 0