- openstack-discuss - lists.openstack.org

murano-dashboard 7.0.0.0rc1 (stein)
by no-reply＠openstack.org 19 Mar '19

19 Mar '19

Hello everyone, A new release candidate for murano-dashboard for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/murano-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/murano-dashboard/log/?h=stable/ste… Release notes for murano-dashboard can be found at: https://docs.openstack.org/releasenotes/murano-dashboard/

1 0

[all][tc][goals] train cycle goals discussion
by Mohammed Naser 19 Mar '19

19 Mar '19

Hi everyone, I'd like us to schedule an ad-hoc meeting to discuss the cycle goals in order to give enough time for developers to plan out their PTG. We would love to have community members as well as potential goal champions available to discuss, we'll be discussing these two reviews: https://review.openstack.org/#/c/639010/ https://review.openstack.org/#/c/639376/ We've setup a Framedate poll to pick one of the upcoming office hours to discuss this, please include your name so we can pick a time that works best. https://framadate.org/1Q5i7gqQsZDH9dBQ Thank you. Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

2 3

[scientific-sig] IRC meeting today 2100 UTC (in 2.5 hours): Nomad (Hashicorp) GPU cluster
by Blair Bethwaite 19 Mar '19

19 Mar '19

Hi all, Today we've got Joe Topjian from Cybera coming along to share some details on a PoC he's been working on recently, using Hashicorp's Nomad as a container based workload manager to support datascience and ML workloads (IIUC). Cheers, b1airo

1 0

DNS for instances
by Grant Morley 19 Mar '19

19 Mar '19

Hi all, I am having a bit of an issue with DNS for instances. We are wanting to update our DNS servers that all instances use. I have tested this by using google's nameservers for now and set both of our subnets to use "8.8.8.8 & 8.8.4.4", I have also changed the "dhcp_agent.ini" on our Neutron nodes to have: dnsmasq_dns_servers = 8.8.8.8, 8.8.4.4 I have restarted the dhcp agents on both nodes, however whenever a new instance is launched, it is still using the old DNS server setup. Is there anything else I need to do or anything I have missed to make sure instances use the updated DNS servers? Many thanks, Grant -- Grant Morley Cloud Lead Absolute DevOps Ltd Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP www.absolutedevops.io <http://www.absolutedevops.io/> grant(a)absolutedevops.io <mailto:grant@absolutedevops.io> 0845 874 0580

1 1

[ops] ops meetups team meeting 2019-3-19
by Chris Morgan 19 Mar '19

19 Mar '19

meeting minutes from today's meeting openstack> Meeting ended Tue Mar 19 14:58:06 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 10:58 AM Minutes: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… 10:58 AM Minutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… 10:58 AM O<•openstack> Log: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… meetings are held weekly at 10am EST on #openstack-operators Chris -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[release] Release countdown for week R-3, March 18-22
by Sean McGinnis 19 Mar '19

19 Mar '19

Another busy week. We are getting to the end of the Stein release cycle, so please read through for important actions needed as we prepare for wrapping things up. Development Focus ----------------- The Release Candidate (RC) deadline is this Thursday, the 21st. Work should be focused on any release-critical bugs and wrapping up and finalizing feature work. General Information ------------------- All cycle-with-rc and cycle-with-intermediary projects should cut their stable/stein branch by the end of the week. This branch will track the Stein release. Once stable/stein has been created, master will will be ready to switch to Train development. While master will no longer be frozen, please prioritize any work necessary for completing Stein plans. Please also keep in mind there will be stein patches competing with any new Train work to make it through the gate. Changes can be merged into stable/stein as needed if deemed necessary for an RC2. Once Stein is released, stable/stein will also be ready for any stable point releases. Whether fixing something for another RC, or in preparation of a future stable release, fixes must be merged to master first, then backported to stable/stein. Actions --------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from master. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/stein branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from master (which will technically then be Train) to this stable branch for any additional RCs before the final release. There have been a few teams that have added cycle-highlights so far. Please get those added to help in communicating Stein updates. We would like to have all of those by the RC1 deadline to give marketing time to compile them and come up with that messaging. http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003597.ht… Finally, any cycle-with-intermediary projects that have not done a release lately - we will need to use the last release point as the branching point for stable/stein unless you specify an updated one. Please make sure the stable branch will have everything you would like included to avoid needing to backport already merged changes. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 21 Final RC deadline: April 1 Final Stein release: April 10 -- Sean McGinnis (smcginnis)

2 2

[designate] Release Patches
by Graham Hayes 19 Mar '19

19 Mar '19

Hi all, I have flagged patches I think we need to merge for this cycle's RC [1] Please have a look at these patches and we can try and get them in for the release. - Graham 1 - https://graham.hayes.ie/designate/release-dashboard

1 0

[placement] update 19-10
by Chris Dent 19 Mar '19

19 Mar '19

HTML: https://anticdent.org/placement-update-19-10.html Placement update 19-10 is here. We're fast approaching placement's first official release. # Most Important There are several tasks left before we can cut the release, mostly related to documentation and other writing related things. I've attempted to enumerate them in a "Prepping the RC" section below. These are things that need to be done before next Thursday, preferably sooner. It's also important to be thinking about how placement would like to engage (as a group) with the PTG (the Forum is already decided: there will be an extraction related Forum session). # What's Changed * Oh, hey, I'm, like, the placement PTL. Mel and I decided early in the week that whatever the official timetable, I'll take the baton from here. Thanks to everyone who helped to get placement to where we are now. * The stack of code that got rid of the List classes in favor of module level methods, which also happened to move each "object" type to its own module, has merged. I'm glad we got this in before release as it ought to make debugging and digging around a bit easier. * Lots of little documentation tuneups (from [story 2005190](https://storyboard.openstack.org/#!/story/2005190)) have merged, including pointing to storyboard for bugs. These chanages scrape the surface of what remains (listed below). * I wrote up a blog post on [profiling wsgi apps](https://anticdent.org/profiling-wsgi-apps.html) which I'd been doing to confirm that the many refactorings that have happened recently weren't having a negative impact (they are not). * We decided to wait for Train for the [negative-member-of](https://review.openstack.org/#/q/topic:bp/negative-aggr… functionality and the [allocation ratio](https://review.openstack.org/#/c/640898/) change in osc-placement. * Kolla has merged several changes for extracted placement. Thanks! # Specs/Blueprint/Features Skipping this section until after the release candidate(s) are done. # Bugs We've got a StoryBoard [project group](https://storyboard.openstack.org/#!/project_group/placement) now. I've started using it. Tagging bugs with `bug` and also making use of a `cleanup` tag to indicate things that needs to be cleaned up. There are worklists for both of these: * [bugs](https://storyboard.openstack.org/#!/worklist/574) * [cleanups](https://storyboard.openstack.org/#!/worklist/575) Please be prepared for these structures to evolve as we gain some understanding of how StoryBoard works. There are still bugs in launchpad and we need to continue to watch there: * Placement related [bugs not yet in progress](https://goo.gl/TgiPXb):13. No change. * [In progress placement bugs](https://goo.gl/vzGGDQ) 7. -2. Many of these are about nova's use of placement. At some point after RC we should do a bug review, and port placement-only things to StoryBoard. # osc-placement osc-placement is currently behind by 13 microversions. Pending changes: * [support for 1.19](https://review.openstack.org/#/c/641094/) * [support for 1.21](https://review.openstack.org/#/c/641123/) * [aggregate allocation ratio tool](https://review.openstack.org/#/c/640898/) # Prepping the RC Things that need to happen so we can cut a placement release candidate: * Anything currently open that we want in. There are only 6 pending patches that might be options (everything else is either waiting for Train or already +W), so a quick look [at them](https://review.openstack.org/#/q/project:openstack/placement+status:o… is worth the effort. * We've started a cycle-highlights etherpad, as announced by [this email](http://lists.openstack.org/pipermail/openstack-discuss/2019-March/00…. We've probably got enough, but feel free to add to it if you think of something. * There's a story for [preparing placement docs for stein](https://storyboard.openstack.org/#!/story/2005190). The story includes several tasks, many of which are already merged. Have a look and assign yourself a task if you can commit to having it done by early next week. There are some biggies: * Creating the canonical how to upgrade from placement-in-nova to placement-in-placement document. As stated very well by Tetsuoro, this is effectively translating the [grenade upgrade script](http://git.openstack.org/cgit/openstack-dev/grenade/tree/projects/6… to English. * Ensuring the install docs are sane and complete. [I have asked](http://lists.openstack.org/pipermail/openstack-discuss/2019-March/00… packaging-related people for their input, as they're the ones who know how their packages are (or will be) set up, but there's also an "install from-pypi" hole that needs to be filled. * The [releasenotes](https://docs.openstack.org/project-team-guide/release-managem… need to be evaluated for correctness and effective annotation of upgrade concerns. They will also need a prelude, probably pointing to the "upgrading from nova" doc mentioned above. For a sample, see nova's [rocky prelude](https://review.openstack.org/#/c/589303/). # Main Themes We'll come back to themes once the RC is cut. # Other Placement * <https://review.openstack.org/#/q/topic:cd/gabbi-tempest-job> Gabbi-based integration tests of placement. These recently found a bug that none of the functional, grenade, nor tempest tests did. Not release related, but useful testing. * <https://review.openstack.org/#/q/topic:bp/negative-aggregate-membership> Negative member of aggregate filtering resource providers and allocation candidates. Holding until Train opens. # Other Service Users We'll also hold off here until the RC is cut. In the future if you stick "placement" somewhere in your commit message I'll probably eventually find your in-progress placement-related changes. # End Once the release is released, it will be time to start thinking about what we want Train to look like. There are pending Stein feature specs that we will want to do (and will need to be put in our specs directory, once it exists), but other than the various ideas about ways to do multi-nova/cloud partitioning of resource providers and multi-service partitioning of allocations (both of which need much more well-defined uses cases before we start thinking about the solutions) I've not heard a lot of clamouring from services and operators for features in Placement. If you have heard, or are clamouring, please make yourself known. I'd personally like us to focus on enabling existing services that use or want to use placement (nova, neutron, blazar, cyborg) and its existing features rather than new features. No need to have any immediate thoughts or decisions on this, but some background thinking is warranted. Also, OMG, we need a logo. How about an Australian Magpie? They make a cool noise. <https://www.youtube.com/watch?v=oYEYc8Ge3nw> -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

1 2

[telemetry][ptl][volunteer][tc] Telemetry PTL for Train
by Trinh Nguyen 19 Mar '19

19 Mar '19

Hi all, Because no one want to nominate for the PTL in Train [1], Telemetry has been marked as a leaderless project and may be removed of OpenStack. We and some companies are still using Ceilometer, AODH (parts of Telemetry) so we don't want that happen. Lingxian Kong (Trove and Qinling PTL), I (cc Julien Danjou, the current PTL of Telemetry) had a conversation about this and agree to work together to maintain the Telemetry projects. So I'm writing this email stating that I would like to volunteer to be the PTL for Telemetry in Train. Though I haven't been directly involved in the development of Telemetry ever, my experience as Searchlight PTL and core in Fenix and Freezer give me some technical understanding of Telemetry as well as OpenStack development procedure. You're in the good hands. Thanks, [1] https://governance.openstack.org/election/ -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

9 14

[cinder] setting `rbd_exclusive_cinder_pool = True` with multiple cinder-volume writing to the same pool
by Krzysztof Klimonda 19 Mar '19

19 Mar '19

Hi, Just doing a quick sanity check - I can set `rbd_exclusive_cinder_pool = True` (in pike, where the change landed first) even if more than one cinder-volume is writing to the same Ceph pool, right? Assuming nothing writes to the pool outside of cinder, we should be good as far as I understand the code. -Chris

2 3