September 2019 - openstack-discuss

issues creating a second vm with numa affinity
by Manuel Sopena Ballesteros 27 Sep '19

27 Sep '19

Dear Openstack user community, I have a compute node with 2 numa nodes and I would like to create 2 vms, each one using a different numa node through numa affinity with cpu, memory and nvme pci devices. Openstack flavor openstack flavor create --public xlarge.numa.perf.test --ram 200000 --disk 700 --vcpus 20 --property hw:cpu_policy=dedicated --property hw:emulator_threads_policy=isolate --property hw:numa_nodes='1' --property pci_passthrough:alias='nvme:4' The first vm is successfully created openstack server create --network hpc --flavor xlarge.numa.perf.test --image centos7.6-image --availability-zone nova:zeus-53.localdomain --key-name mykey kudu-1 However the second vm fails openstack server create --network hpc --flavor xlarge.numa.perf --image centos7.6-kudu-image --availability-zone nova:zeus-53.localdomain --key-name mykey kudu-4 Errors in nova compute node 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [req-b5a25c73-8c7d-466c-8128-71f29e7ae8aa 91e83343e9834c8ba0172ff369c8acac b91520cff5bd45c59a8de07c38641582 - default default] [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] Instance failed to spawn: libvirtError: internal error: qemu unexpectedly closed the monitor: 2019-09-27T06:45:19.118089Z qemu-kvm: kvm_init_vcpu failed: Cannot allocate memory 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] libvirtError: internal error: qemu unexpectedly closed the monitor: 2019-09-27T06:45:19.118089Z qemu-kvm: kvm_init_vcpu failed: Cannot allocate memory 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] Numa cell/node 1 (the one assigned on kudu-4) has enough cpu, memory, pci devices and disk capacity to fit this vm. NOTE: below is the information relevant I could think of that shows resources available after creating the second vm. [root@zeus-53 ~]# numactl -H available: 2 nodes (0-1) node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 28 29 30 31 32 33 34 35 36 37 38 39 40 41 node 0 size: 262029 MB node 0 free: 52787 MB node 1 cpus: 14 15 16 17 18 19 20 21 22 23 24 25 26 27 42 43 44 45 46 47 48 49 50 51 52 53 54 55 node 1 size: 262144 MB node 1 free: 250624 MB node distances: node 0 1 0: 10 21 1: 21 10 NOTE: this is to show that numa node/cell 1 has enough resources available (also nova-compute logs shows that kudu-4 is assigned to cell 1) [root@zeus-53 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/md127 3.7T 9.1G 3.7T 1% / ... NOTE: vm disk files goes to root (/) partition [root@zeus-53 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 59.6G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 16G 0 part [SWAP] nvme0n1 259:8 0 1.8T 0 disk └─nvme0n1p1 259:9 0 1.8T 0 part └─md127 9:127 0 3.7T 0 raid0 / nvme1n1 259:6 0 1.8T 0 disk └─nvme1n1p1 259:7 0 1.8T 0 part └─md127 9:127 0 3.7T 0 raid0 / nvme2n1 259:2 0 1.8T 0 disk nvme3n1 259:1 0 1.8T 0 disk nvme4n1 259:0 0 1.8T 0 disk nvme5n1 259:3 0 1.8T 0 disk NOTE: this is to show that there are 4 nvme disks (nvme2n1, nvme3n1, nvme4n1, nvme5n1) available for the second vm What "emu-kvm: kvm_init_vcpu failed: Cannot allocate memory" means in this context? Thank you very much NOTICE Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed.

2 1

Re: [ironic] FFE: Add idrac HW type Redfish virtual media boot interface (Ruby Loo)
by prakash RAMCHANDRAN 27 Sep '19

27 Sep '19

Julia & Richard, We in airship 2.0 need vIrtual media boot up for our work in remoteboot direct using Ironic redfish interface. This is to use both for Ehemeral BareMetalHost as well for target cluter BareMetal Nodes redfish based Virtual Media booting. We in Airship community strongly endorse the exception to include this feature in Train. I am copying few of our TC & WC members who too can confirm my ask on behalf of Airship 2.0 team. ThanksPrakash Ramchandran(pramchan) Sent from Yahoo Mail on Android

4 7

[loci] Stepping down from core reviewer
by Jean-Philippe Evrard 27 Sep '19

27 Sep '19

Hello folks, I no longer have enough time to contribute meaningfully or review in a timely manner to LOCI, so I will step down of the project. It's been great working with you folks! There are so many things that can be done to simplify the project further, and reduce tech debt, rely more on infra/zuul's existing roles and features, but sadly I don't have enough time to tackle those things. If you have extra time and want to step up for changing LOCI don't hesitate to come to me to discuss those ideas :) All the best, Jean-Philippe Evrard (evrardjp)

1 0

[placement] update 19-∞
by Chris Dent 27 Sep '19

27 Sep '19

HTML: https://anticdent.org/placement-update-19-.html Let's call this placement update 19-∞, as this will be my last one. It's been my pleasure to provide this service for nearly [three years](http://lists.openstack.org/pipermail/openstack-dev/2016-November/107…. I hope it has been as useful to others as it has been for me. The goal all along was to provide some [stigmergic](https://en.wikipedia.org/wiki/Stigmergy) structures to augment how we, the placement team, collaborated. I guess it worked: yesterday we released a candidate that will likely become the Train version of placement. The first version where the only placement you can get is from its own repo/project. Thanks to everyone who has made this possible over the years. # Most Important Tetsuro will be the next placement PTL. He and Gibi are working on the project update and other Summit/PTG-related activities for Shanghai. If you have thoughts on that, please contact them. The [now worklist](https://storyboard.openstack.org/#!/worklist/754) I made a couple weeks ago has had some progress, but some tasks remain. None of them were critical for the release, except perhaps the ongoing need for better documentation of how to most effectively use the service. Since we're expecting the Ussuri release to be one where we consolidate how other services make use of placement, most of the items on that list can fit well with that. We should be on the lookout for bugs reported by people trying to the release candidate(s). # Stories/Bugs (Numbers in () are the change since the last pupdate.) There are 21 (-2) stories in [the placement group](https://storyboard.openstack.org/#!/project_group/placement). 0 (0) are [untagged](https://storyboard.openstack.org/#!/worklist/580). 7 (2) are [bugs](https://storyboard.openstack.org/#!/worklist/574). 2 (-2) are [cleanups](https://storyboard.openstack.org/#!/worklist/575). 9 (-1) are [rfes](https://storyboard.openstack.org/#!/worklist/594). 4 (-1) are [docs](https://storyboard.openstack.org/#!/worklist/637). If you're interested in helping out with placement, those stories are good places to look. * Placement related nova [bugs not yet in progress](https://goo.gl/TgiPXb) on launchpad: 15 (-2). * Placement related nova [in progress bugs](https://goo.gl/vzGGDQ) on launchpad: 6 (0). # osc-placement There are [several](https://review.opendev.org/#/q/project:openstack/osc-placement+sta… osc-placement changes, many of which are related to the cutting of a stable/train branch. # Main Themes ## Consumer Types Adding a type to consumers will allow them to be grouped for various purposes, including quota accounting. * <https://review.opendev.org/#/q/topic:bp/support-consumer-types> No one had the time to address the fix ups for this before Train was cut, so consumer types will be a part of Ussuri. If anyone is available to adopt this, please let me and/or tssurya know. ## Cleanup Cleanup is an overarching theme related to improving documentation, performance and the maintainability of the code. The changes we made this cycle are fairly complex to use and were fairly complex to write. We need to make sure, with the coming cycle, that we help people use them well. # Other Placement Miscellaneous changes can be found in [the usual place](https://review.opendev.org/#/q/project:openstack/placement+status:op…. There are two [os-traits changes](https://review.opendev.org/#/q/project:openstack/os-traits+status:… being discussed. And zero [os-resource-classes changes](https://review.opendev.org/#/q/project:openstack/os-resource-class…. # Other Service Users Since we're in RC period I'll not bother listing pending changes. During Ussuri the placement team hopes to be available to facilitate other projects using the service. Keeping track of those is what this section has been trying to do. Besides general awareness of what's going on, I've also used [this gerrit query](https://review.opendev.org/#/q/(message:placement+OR+comment:placeme… to find things that might be related to placement. # End 🙇 -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent

1 0

[Oslo][TaskFlow] Accepting any decider
by Jiří Rája 27 Sep '19

27 Sep '19

Hi, I wrote the code in the attachment and I would like to ask if it's possible to execute next task (step3) even if one decider returns True (link from step 1 to step 3) and one returns False (link from step 2 to step 3). If it is possible could you alter the code? Or is there any other way to do it? And if the task wouldn't have to wait for all of the links, it would be great. Thank you! Looking forward to hearing from you. All the best, Rája

1 0

sahara-extra 10.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for sahara-extra for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-extra/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/sahara-extra/src/branch/stable/train Release notes for sahara-extra can be found at: https://docs.openstack.org/releasenotes/sahara-extra/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/sahara/+bugs and tag it *train-rc-potential* to bring it to the sahara-extra release crew's attention.

1 0

sahara 11.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for sahara for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/sahara/src/branch/stable/train Release notes for sahara can be found at: https://docs.openstack.org/releasenotes/sahara/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/sahara/+bugs and tag it *train-rc-potential* to bring it to the sahara release crew's attention.

1 0

[neutron] Is a provider of the "router" extension required also to provide the "extraroute" extension?
by Neil Jerram 27 Sep '19

27 Sep '19

Hi Neutrinos - Calico's plugin has recently started failing CI, at the point where devstack initial network creation does "openstack router create ...", with the classic error "'NoneType' object is not iterable" [1], and I think this is because openstackclient assumes [2] that the returned router dict will always have a 'routes' field. If my analysis is correct, is that a correct assumption, or should openstackclient be more forgiving here? [1] https://openstack.fortnebula.com:13808/v1/AUTH_e8fd161dc34c421a979a9e6421f8… [2] https://opendev.org/openstack/python-openstackclient/src/branch/master/open… Many thanks, Neil

2 2

sahara-image-elements 11.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for sahara-image-elements for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-image-elements/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/sahara-image-elements/src/branch/stable/train Release notes for sahara-image-elements can be found at: https://docs.openstack.org/releasenotes/sahara-image-elements/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/sahara/+bugs and tag it *train-rc-potential* to bring it to the sahara-image-elements release crew's attention.

1 0

sahara-plugin-ambari 2.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for sahara-plugin-ambari for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-plugin-ambari/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/sahara-plugin-ambari/src/branch/stable/train Release notes for sahara-plugin-ambari can be found at: https://docs.openstack.org/releasenotes/sahara-plugin-ambari/ If you find an issue that could be considered release-critical, please file it at: https://storyboard.openstack.org/#!/project/1101 and tag it *train-rc-potential* to bring it to the sahara-plugin-ambari release crew's attention.

1 0

designate 9.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for designate for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/designate/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/designate/src/branch/stable/train Release notes for designate can be found at: https://docs.openstack.org/releasenotes/designate/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/designate/+bugs and tag it *train-rc-potential* to bring it to the designate release crew's attention.

1 0

sahara-dashboard 11.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for sahara-dashboard for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/sahara-dashboard/src/branch/stable/train Release notes for sahara-dashboard can be found at: https://docs.openstack.org/releasenotes/sahara-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/sahara/+bugs and tag it *train-rc-potential* to bring it to the sahara-dashboard release crew's attention.

1 0

sahara-plugin-storm 2.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for sahara-plugin-storm for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-plugin-storm/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/sahara-plugin-storm/src/branch/stable/train Release notes for sahara-plugin-storm can be found at: https://docs.openstack.org/releasenotes/sahara-plugin-storm/ If you find an issue that could be considered release-critical, please file it at: https://storyboard.openstack.org/#!/project/1105 and tag it *train-rc-potential* to bring it to the sahara-plugin-storm release crew's attention.

1 0

sahara-plugin-vanilla 2.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for sahara-plugin-vanilla for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-plugin-vanilla/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/sahara-plugin-vanilla/src/branch/stable/train Release notes for sahara-plugin-vanilla can be found at: https://docs.openstack.org/releasenotes/sahara-plugin-vanilla/ If you find an issue that could be considered release-critical, please file it at: https://storyboard.openstack.org/#!/project/1106 and tag it *train-rc-potential* to bring it to the sahara-plugin-vanilla release crew's attention.

1 0

sahara-plugin-mapr 2.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for sahara-plugin-mapr for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-plugin-mapr/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/sahara-plugin-mapr/src/branch/stable/train Release notes for sahara-plugin-mapr can be found at: https://docs.openstack.org/releasenotes/sahara-plugin-mapr/ If you find an issue that could be considered release-critical, please file it at: https://storyboard.openstack.org/#!/project/1103 and tag it *train-rc-potential* to bring it to the sahara-plugin-mapr release crew's attention.

1 0

Re: openstack-placement 2.0.0.0rc1 (train)
by Thomas Goirand 27 Sep '19

27 Sep '19

On 9/26/19 11:53 AM, no-reply(a)openstack.org wrote: > Hello everyone, > > A new release candidate for openstack-placement for the end of the Train > cycle is available! You can find the source code tarball at: > > https://tarballs.openstack.org/placement/ > > Unless release-critical issues are found that warrant a release > candidate respin, this candidate will be formally released as the > final Train release. You are therefore strongly encouraged > to test and validate this tarball! > > Alternatively, you can directly test the stable/train release > branch at: > > https://opendev.org/openstack/openstack-placement/src/branch/stable/train > > Release notes for openstack-placement can be found at: > > https://docs.openstack.org/releasenotes/placement/ Any reason why there's no [release-announce] tag in the subject, thus breaking everyone's filters? Cheers, Thomas Goirand (zigo)

2 2

sahara-plugin-spark 2.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for sahara-plugin-spark for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-plugin-spark/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/sahara-plugin-spark/src/branch/stable/train Release notes for sahara-plugin-spark can be found at: https://docs.openstack.org/releasenotes/sahara-plugin-spark/ If you find an issue that could be considered release-critical, please file it at: https://storyboard.openstack.org/#!/project/1104 and tag it *train-rc-potential* to bring it to the sahara-plugin-spark release crew's attention.

1 0

sahara-plugin-cdh 2.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for sahara-plugin-cdh for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-plugin-cdh/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/sahara-plugin-cdh/src/branch/stable/train Release notes for sahara-plugin-cdh can be found at: https://docs.openstack.org/releasenotes/sahara-plugin-cdh/ If you find an issue that could be considered release-critical, please file it at: https://storyboard.openstack.org/#!/project/1102 and tag it *train-rc-potential* to bring it to the sahara-plugin-cdh release crew's attention.

1 0

cinder 15.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for cinder for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/cinder/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/cinder/src/branch/stable/train Release notes for cinder can be found at: https://docs.openstack.org/releasenotes/cinder/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/cinder/+bugs and tag it *train-rc-potential* to bring it to the cinder release crew's attention.

1 0

openstack-cyborg 3.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for openstack-cyborg for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/cyborg/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/openstack-cyborg/src/branch/stable/train Release notes for openstack-cyborg can be found at: https://docs.openstack.org/releasenotes/cyborg/

1 0

keystone 16.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for keystone for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/keystone/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/keystone/src/branch/stable/train Release notes for keystone can be found at: https://docs.openstack.org/releasenotes/keystone/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/keystone/+bugs and tag it *train-rc-potential* to bring it to the keystone release crew's attention.

1 0

nova 20.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for nova for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/nova/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/nova/src/branch/stable/train Release notes for nova can be found at: https://docs.openstack.org/releasenotes/nova/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/nova/+bugs and tag it *train-rc-potential* to bring it to the nova release crew's attention.

1 0

horizon 16.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for horizon for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/horizon/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/horizon/src/branch/stable/train Release notes for horizon can be found at: https://docs.openstack.org/releasenotes/horizon/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/horizon/+bugs and tag it *train-rc-potential* to bring it to the horizon release crew's attention.

1 0

tacker 2.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for tacker for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/tacker/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/tacker/src/branch/stable/train Release notes for tacker can be found at: https://docs.openstack.org/releasenotes/tacker/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/tacker/+bugs and tag it *train-rc-potential* to bring it to the tacker release crew's attention.

1 0

manila EMC Unity driver Doc review
by Dong.Ding＠dell.com 27 Sep '19

27 Sep '19

Hi, As suggested we have submitted the Doc change of Unity in Manila. Keep both Doc almost same and will update both of the changes in the future. Can you help to take a look, here is the link https://review.opendev.org/#/c/681381/ Thanks, Ding Dong

1 0