- openstack-discuss - lists.openstack.org

[horizon] Horizon PTG planning
by Ivan Kolodyazhny 06 Mar '19

06 Mar '19

Hi team, I created etherpad to collect topics for PTG. Feel free to add any topic you would like to discuss face to face. [1] https://etherpad.openstack.org/p/horizon-train-ptg Regards, Ivan Kolodyazhny, http://blog.e0ne.info/

1 0

[ptl][docs][election] Stephen Finucane's candidacy for Documentation PTL
by Stephen Finucane 06 Mar '19

06 Mar '19

Hey, I'd like to announce my candidacy for Docs PTL for the Train cycle. I've been involved in the documentation project since the heady days of 2016, back when the documentation team centrally managed the user-facing docs of every core OpenStack project. My initial contributions mostly focused on correcting and expanding the documentation related to my primary focus area in OpenStack, NFV enablement, though this slowly expanded as I built up competence in all things docs. At some point, for many disparate reasons, *os-manuals-migration* happened [1]_, and each project began taking responsbility for their own documentation. I assisted with the migration of the nova docs in particular and have been continuously involved ever since. As a result of *os-manuals-migration*, today's documentation team is mainly intended to act as a liason to other teams, stepping in to help with various documentation-related questions and, where necessary, providing additional tooling. In my opinion, this is both a pragmatic and a sustainable approach and I would like to see the documentation project continue on this trajectory, changing course only if/when necessary. As such, my focus areas for the upcoming cycle would be continued work on making documentation easier to contribute to (or unnecessary, where docs can be generated from code), cleaning up the remaining warts in the existing documentation and documentation processes, and generally ensuring the documentation team is as helpful as possible for the projects that need us. I feel I am well equipped to handle this, and I hope you do too. Cheers, Stephen (stephenfin) .. [1] https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migr…

1 0

[nova] address comments about the show-server-numa-topology
by yonglihe 06 Mar '19

06 Mar '19

Hi, All Thanks Sean's good comments. Cause there lots of links and discuss, I come out with a docs for collections comments, options, and investigating. please move to google docs for discuss, thanks: https://docs.google.com/document/d/1kRRZFq_ha0T9mFDOEzv0PMvXgtnjGm5ii9mSzdq… links: https://review.openstack.org/#/c/621476/ show server numa_topology https://blueprints.launchpad.net/nova/+spec/show-server-numa-topology (yonglihe) Regards Yongli He

1 0

[senlin] Senlin Monthly(ish) Newsletter Jan/Feb 2019
by Duc Truong 06 Mar '19

06 Mar '19

HTML: https://dkt26111.wordpress.com/2019/02/21/senlin-monthlyish-newsletter-janu… This is the January/February edition of the Senlin monthly(ish) newsletter. The goal of the newsletter is to highlight happenings in the Senlin project. If you have any feedback or questions regarding the contents, please feel free to reach out to me in the #senlin IRC channel. News ---- * We are almost at Stein-3 milestone which coincides with the feature freeze during the week of March 4. Please submit your changes for review before then. Blueprint Status ---------------- * Fail fast locked resource - https://blueprints.launchpad.net/senlin/+spec/fail-fast-locked-resource - Working on documentation and release notes. * Multiple detection modes - https://blueprints.launchpad.net/senlin/+spec/multiple-detection-modes - Working on documentation and release notes. Community Goal Status --------------------- * Python 3 - All patches by Python 3 goal champions for zuul migration, documentation and unit test changes have been merged. - We have set py35 functional tests as voting in gate. * Upgrade Checkers - I have added a patch set to check for unsupported health policies: https://review.openstack.org/#/c/638284/ Reviews Needed -------------- * Improve Health Manager to avoid duplicate health checks: https://review.openstack.org/#/c/634811/ * Fixing devstack tempest jobs for master and stable/rocky: https://review.openstack.org/#/c/637664/ https://review.openstack.org/#/c/635638/

2 1

Using Trove with Rocky
by Ankit Awal 06 Mar '19

06 Mar '19

I am trying to use Trove with Rocky. i am able to make a qcow image using the scripts provided in trove [ disk builder ] . Unfortunately, when i start trove, the status shows building but the instance is up and running. I feel that the problem is regarding the improper setup of the trove image. Can someone guide me with the steps to create a trove image and launch it using kolla ansible *With Regards,* *Ankit Awal* *Niveus Solutions Private Limited* *Email: ankit.awal(a)niveussolutions.com <vishnuprasad.i(a)niveussolutions.com>*

1 0

[ptl][searchlight][election] Trinh nguyen's candidacy for Searchlight PTL
by Trinh Nguyen 06 Mar '19

06 Mar '19

Hello. I would like to announce my candidacy for Searchlight PTL for Train. [4] I have been involved in OpenStack since the Queens cycle as it is needed for my research. Over the last three cycles, I learned a lot in both technical and organizational aspects. That is thank to the help of many community members, TCs, PTLs of the OpenStack projects that I am working on. That inspired me to take the role of Searchlight PTL to help survive the project. I could say I can commit my time for that responsibility with my current job. As many of you may know, at the end of the Rocky cycle, the TC intended to remove Searchlight from the Governance (OpenStack official projects). The reasons for that are because Searchlight has missed several milestones and lacked communication of the PTL. I couldn't stand the fact that a pretty cool project like Searchlight would be abandoned so I volunteered to be the PTL of Searchlight for the Stein cycle. I hoped that I could do something to revive it. With the help of some contributors, we finally could find a "light" for the project. In the first two milestones of Stein, Searchlight has identified itself as a useful tool in several use cases such as being a cloud resource lookup, a cloud resource repository, and a multi-cloud search solution [1]. We hope those use cases will attract more contributors and vendors to support and use Searchlight in the near future. Moreover, the team has developed a grand vision for Searchlight [2] to help sustain the project in alignment with the OpenStack Cloud Vision [3]. The very first thing to make that vision come true is building a strong foundation for Searchlight. I take that responsibility personally and passionately. Like many other OpenStack projects, there are always challenges in contributor participation. For that, I especially see the new contributor engagement is an important job of the PTL and always looking for opportunities to do that (e.g., conferences, meetup, training, etc.). That will not be changed whether you'll have me as the Searchlight PTL for Train or not. I will continue working on helping potential developers to come to Searchlight and build a strong community around it. I know that I knew nothing about Searchlight before Stein. I'm not trying to change things with big ideas here. I just want to help Searchlight succeed in Train and further if I can. Thank you for your consideration. Trinh Nguyen (dangtrinhnt) [1] https://docs.openstack.org/searchlight/latest/user/usecases.html [2] https://docs.openstack.org/searchlight/latest/contributor/searchlight-visio… [3] https://docs.openstack.org/searchlight/latest/contributor/vision-reflection… [4] https://review.openstack.org/#/c/641193/ -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

1 0

[ptl][nova][election] Eric Fried's Candidacy for Nova PTL
by Eric Fried 06 Mar '19

06 Mar '19

Greetings. I am hereby [1] announcing my candidacy for Nova PTL for Train. I am passionate about OpenStack, to the point where I (like many of you) changed companies so I wouldn't have to change jobs. My employer backs me as a 100% upstream developer and core in Nova and Placement, and fully supports my commitment to the role of Nova PTL if you'll have me. Nova is huge, in code as well as in history. I don't pretend to understand all (or even most) of it. It takes the cumulative skill of the whole team to make the project tick. I see the PTL as a facilitator and coordinator of that "group brain", making the whole greater than the sum of the parts. That takes organization, diplomacy, and patience: qualities I have demonstrated by running the nova-scheduler meetings, helping with the politics of extracting Placement, and engaging in tough and contentious design discussions in specs, PTGs, IRC, etc. As PTL, one of my main goals will be to keep those conversations moving and focused, avoiding unproductive tangents. We continue to face challenges in contributor (which includes reviewer!) participation. Partly this is due to the overall change in the character of the community; but I hope to break down barriers for new or part-time contributors who are willing and able to participate. In day-to-day operations this means being responsive and encouraging on IRC and gerrit. In forum and PTG sessions it means working to avoid the "echo chamber effect" and ceding the floor to these less-involved participants so they can be heard. I would also like to continue blueprint tracking including runways, which has been an effective way to ensure attention for efforts outside of our deemed main themes and priorities. Nova is on the cusp of being able to take advantage of advanced Placement features such as nested and sharing providers to solve some of the problems for which Placement was originally conceived. Nova will need to continue to work closely with Placement in its new position as an independent project. I intend to continue being an active Placement core regardless of the outcome of these elections to assist in that transition. We need to continue to foster our relationships with other teams, ensuring proper care and feeding of cross-project initiatives. This applies to the old guard (Cinder, Glance, Ironic, Keystone, Neutron, and Placement as noted) but also to nascent efforts such as Cyborg. This starts with forum and PTG logistics for Denver, and continues with constant communication during the cycle. I am aware that I am standing on the shoulders of giants. I'm not trying to do anything brilliantly new here. I want to follow the lead of my predecessors and continue to tap them for their expertise and experience to help Nova succeed in Train. Thank you for your consideration. Eric Fried (efried) (rhymes with 'deed', not with 'side') [1] https://review.openstack.org/#/c/641177/

2 1

[all] [elections]'Train' PTL Nominations Kickoff
by Kendall Nelson 06 Mar '19

06 Mar '19

Hello All! Nominations for OpenStack PTLs (Program Team Leads) are now open and will remain open until Mar 12, 2019 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at http://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the new candidacy file naming convention: candidates/<cycle>/<project_name>/<email_address>. In order to be an eligible candidate (and be allowed to vote) in a given PTL election, you need to have contributed to the corresponding team[0] during the Feb 09, 2018 00:00 UTC - Feb 19, 2019 00:00 UTC timeframe (Rocky to Stein). You must also be an OpenStack Foundation Individual Member in good standing. To check if your membership is up to date, go to https://www.openstack.org/community/members and search for your name. Additional information about the nomination process can be found here: https://governance.openstack.org/election/ Shortly after election officials approve candidates, they will be listed here: https://governance.openstack.org/election/#train-ptl-candidates The electorate is requested to confirm their email address in gerrit[1], prior to 2019-02-22 00:00:00+00:00 so that the emailed ballots are mailed to the correct email address. This email address should match that which was provided in your foundation member profile[2] as well. Happy running, -Kendall Nelson (diablo_rojo) [0] https://governance.openstack.org/tc/reference/projects/ [1] https://review.openstack.org/#/settings/contact [2] https://www.openstack.org/profile/

1 0

[zaqar] Need review for a Python3 related patch
by Emilien Macchi 06 Mar '19

06 Mar '19

Zaqar folks, please review https://review.openstack.org/#/c/639983/ when you have time. It would help to make Zaqar websocket working with Python 3. Thanks, -- Emilien Macchi

1 0

[scientific-sig] Today's SIG meeting CANCELLED
by Stig Telfer 06 Mar '19

06 Mar '19

Hi All - Unfortunately, we have to cancel today’s meeting. Apologies for the short notice. Cheers, Stig

1 0