- openstack-discuss - lists.openstack.org

mistral-extra 9.0.0.0rc1 (train)
by no-reply＠openstack.org 28 Sep '19

28 Sep '19

Hello everyone, A new release candidate for mistral-extra for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral-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/mistral-extra/src/branch/stable/train Release notes for mistral-extra can be found at: https://docs.openstack.org/releasenotes/mistral-extra/

1 0

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

28 Sep '19

Hello everyone, A new release candidate for mistral for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral/ 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/mistral/src/branch/stable/train Release notes for mistral can be found at: https://docs.openstack.org/releasenotes/mistral/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/mistral/+bugs and tag it *train-rc-potential* to bring it to the mistral release crew's attention.

1 0

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

27 Sep '19

Hello everyone, A new release candidate for barbican for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/barbican/ 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/barbican/src/branch/stable/train Release notes for barbican can be found at: https://docs.openstack.org/releasenotes/barbican/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/barbican/+bugs and tag it *train-rc-potential* to bring it to the barbican release crew's attention.

1 0

[release][glance] FFE glance_store 1.0.1
by Erno Kuvaja 27 Sep '19

27 Sep '19

Hi all, Glance RC1 is currently pending small refactoring on glance_store we'd like to release as 1.0.1. this is related to how multi-store is handling config option registration for reserved stores (like tasks workdir and import staging). On glance_store 1.0.0 release when the config options are processed we end up registering the option groups with oslo_config without actually registering the options into those groups. we would like to have this issue solved so we can merge the last items for Train RC1 an get that hopefully tagged early next week. Best, Erno "jokke" Kuvaja

2 1

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

27 Sep '19

Hello everyone, A new release candidate for masakari for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/masakari/ 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/masakari/src/branch/stable/train Release notes for masakari can be found at: https://docs.openstack.org/releasenotes/masakari/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/masakari/+bugs and tag it *train-rc-potential* to bring it to the masakari release crew's attention.

1 0

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

27 Sep '19

Hello everyone, A new release candidate for masakari-dashboard for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/masakari-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/masakari-dashboard/src/branch/stable/train Release notes for masakari-dashboard can be found at: https://docs.openstack.org/releasenotes/masakari-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/masakari/+bugs and tag it *train-rc-potential* to bring it to the masakari-dashboard release crew's attention.

1 0

masakari-monitors 8.0.0.0rc1 (train)
by no-reply＠openstack.org 27 Sep '19

27 Sep '19

Hello everyone, A new release candidate for masakari-monitors for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/masakari-monitors/ 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/masakari-monitors/src/branch/stable/train Release notes for masakari-monitors can be found at: https://docs.openstack.org/releasenotes/masakari-monitors/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/masakari-monitors/+bugs and tag it *train-rc-potential* to bring it to the masakari-monitors release crew's attention.

1 0

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

27 Sep '19

Hello everyone, A new release candidate for designate-dashboard for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/designate-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/designate-dashboard/src/branch/stable/train Release notes for designate-dashboard can be found at: https://docs.openstack.org/releasenotes/designate-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/designate-dashboard/+bugs and tag it *train-rc-potential* to bring it to the designate-dashboard release crew's attention.

1 0

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

27 Sep '19

Hello everyone, A new release candidate for senlin for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/senlin/ 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/senlin/src/branch/stable/train Release notes for senlin can be found at: https://docs.openstack.org/releasenotes/senlin/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/senlin/+bugs and tag it *train-rc-potential* to bring it to the senlin release crew's attention.

1 0

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

27 Sep '19

Hello everyone, A new release candidate for magnum for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/magnum/ 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/magnum/src/branch/stable/train Release notes for magnum can be found at: https://docs.openstack.org/releasenotes/magnum/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/magnum/+bugs and tag it *train-rc-potential* to bring it to the magnum release crew's attention.

1 0

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

27 Sep '19

Hello everyone, A new release candidate for heat-dashboard for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/heat-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/heat-dashboard/src/branch/stable/train Release notes for heat-dashboard can be found at: https://docs.openstack.org/releasenotes/heat-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/heat-dashboard/+bugs and tag it *train-rc-potential* to bring it to the heat-dashboard release crew's attention.

1 0

[release] Release countdown for week R-2, September 30 - October 4
by Sean McGinnis 27 Sep '19

27 Sep '19

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the Train deliverables. Teams should be working on any release critical bugs that would require another RC or intermediary release before the final release. Actions ---------- Early in the week, the release team will be proposing stable/train branch creation for all deliverables that have not branched yet, using the latest available Train release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/train branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/train branch before releasing out of the stable/train branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for Ussuri development, though the focus should still be on finishing up Train until the final release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final Train release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targetted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the Train version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: October 10 (R-1 week) Final Train release: October 16 Forum+PTG at Shanghai summit: November 4

1 0

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

27 Sep '19

Hello everyone, A new release candidate for blazar for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/blazar/ 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/blazar/src/branch/stable/train Release notes for blazar can be found at: https://docs.openstack.org/releasenotes/blazar/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/blazar/+bugs and tag it *train-rc-potential* to bring it to the blazar release crew's attention.

1 0

[release][ptl] RC1 Deadline Approaching
by Sean McGinnis 27 Sep '19

27 Sep '19

Hey everyone, Just a reminder that we are hours away from the end of the planned RC1 deadline. There are still quite a few projects that have not done an RC yet. We really could use everyone's help to make this go smoothly. JP was able to generate a set of RC patches for all projects. They can be found here: https://review.opendev.org/#/q/status:open+project:openstack/releases+branc… If you are ready for the RC release, please indicate so by leaving a +1 on the patch so the release team knows it is safe to go ahead with processing the release request. If you are still trying to get some last minute things through the gate, it would also help us if you left a -1 on the release patch with any comments that can help us gauge how long we need to wait yet to do the release. Of course, if you are ready but there have been commits merged since the autogeneration of the patch, please update it with the right commit hash to use. The release, and the stable/train branch, will be created off of this point. One final thing to keep in mind - this is just the initial RC for train. We have a couple weeks to do an RC2 (or even RC3 if needed) so if you are waiting on a few nice to have bugfixes, it is still possible to get those in even if it looks like they will take a little longer. But also keep in mind that with the stable/train branch creation on RC1, those would also need to be backported after merging to master (ussuri) at this point. Thanks for your help as we try to get the train out. Sean

1 1

[openstack-ansible] office hours update
by Mohammed Naser 27 Sep '19

27 Sep '19

Hi everyone, Here’s an update of what happened in this week’s OpenStack Ansible Office Hours. We combined the ironic and inspector virtual environments. The ironic patch needs to be reviewed. We didn’t have much activity because a bunch of us were at AnsibleFest. Thanks for tuning in! Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0

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