- openstack-discuss - lists.openstack.org

[tc] selecting a vice chair
by Mohammed Naser 11 Mar '19

11 Mar '19

Hi everyone: Thanks for having me serve as chair for the upcoming session. As part of my duties getting started is appointing a vice chair[1]. I'd like to invite those who would like to run for vice chair to personally contact me, as I think it's a great way to ease into the TC workflow and learning more about the inner workings of how we (try?!) to keep things moving. I'll be assigning someone by Tuesday, so I just wanted to extend this for those who wanted to run to contact me. :) Thanks, Mohammed [1]: https://governance.openstack.org/tc/reference/charter.html#tc-chair -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 1

[horizon][plugins][vitrage][heat][ironic][manila] Integration tests on gates
by Ivan Kolodyazhny 11 Mar '19

11 Mar '19

Hi team, A few weeks ago we enabled horizon-integration-tests job[1]. It's a set of selenium-based test cases to verify that Horizon works as expected from the user's perspective. Like any new job, it's added in a non-voting mode for now. During the PTG, I'd got several conversations with project teams that it would be good to have such tests in each plugin to verify that plugin works correctly with a current Horizon version. We've got about 30 plugins in the Plugin Registry [2]. Honestly, without any kind of testing in most of the plugins, we can't be sure that they work well with a current version of Horizon. That's why we decided to implement some kind of smoke tests for plugins based on Horizon integration tests framework. These tests should verify that a plugin is installed and pages could be opened in a browser. We will run these tests on the experimental queue and/or on some schedule on Horizon gates to verify that plugins are maintained and working properly. My idea is to have such a list of 'tested' plugins, so we can add 'Maintained' label to the Plugin Registry. Once these jobs become voting, we can add a label 'Verified'. I think such a schedule looks reasonable: * Stein-Train release cycles - add non-voting jobs for each maintained plugin and introduce "Maintained" label * Train-U release cycles - makes stable jobs voting and introduce "Verified" label in the Horizon Plugin registry I do understand that some teams don't have enough resources to maintain integration tests, so I'm stepping as a volunteer to introduce such tests and jobs for the project. I already published patches for Vitrage and Heat [3] plugins and will do the same for Ironic and Manila dashboards in a short time. Any help or feedback is welcome:). [1] https://review.openstack.org/#/c/580469/ [2] https://docs.openstack.org/horizon/latest/install/plugin-registry.html [3] https://review.openstack.org/#/q/topic:horizon-integration-tests+(status:op… Regards, Ivan Kolodyazhny, http://blog.e0ne.info/

3 3

Firmware Update (cleaning step) issues
by Martin Sysadmin 11 Mar '19

11 Mar '19

Hi all I wondered if anybody had managed to update ILO firmware via openstack cleaning step? Details: openstack triple-o / RDO containerised deployment (ironic_conductor etc is a Docker container on the under cloud) I have constructed a JSON file with the contents as follows: [ { "interface": "management", "step": "update_firmware", "args": { "firmware_update_mode": "ilo", "firmware_images":[ { "url": "https://.../..../CP0xyz.scexe", "checksum": "<checksum_value>", "component": "ilo" } ] } } ] which I then initiate a clean step test using following: openstack baremetal node clean --clean-steps fw_update_test.json mytestnode.test.local and this fails with the error "Clean step update_firmware *failed* on node <<node_uid>> with the error: Unable to update firmware" when looking in /var/log/containers/ironic/ironic-conductor.log I have tested this myself by importing proliantutils into my own test Python script, it doesn't matter what URL I provide it fails with the error above. Has anyone managed to get this step working at all? I have also tried with unpacked image (.bin file) and the same error. Would appreciate any tips Thanks

2 2

[ptl][election][horizon] PTL candidacy
by Ivan Kolodyazhny 11 Mar '19

11 Mar '19

Hi, I would like to announce my candidacy for PTL of Horizon for Train release. I served this role during the last two releases and I still feel strong enough to do this role during the next six months. We did a good job as a team during the Stein release cycle: enabled integration tests both for Horizon and several plugins created a good list of priorities and TODOs to fix our huge feature gaps between UI and command-line clients and started work on them, so you can find a few more useful features in our release notes. During the Train cycle, I’m going to continue these efforts: * Add integration tests for all maintained plugins so we can be sure that we’ve got a verified list of working Horizon plugins. * Involve project teams in Horizon: even such contributions like feature requests are extremely important to understand what should we do to make cloud users and operators happier * We missed few community goals in the past and I’ll do my best to fix it in Train release. * Last, but not least, I’ll be happy to help new contributors to be a part of Horizon team. I hope you’ll give me a chance to wear a PTL hat for Train and help me with all these efforts. Thank you, Ivan Kolodyazhny (e0ne)

1 0

[ptl][manila][election] Tom Barron manila PTL candidacy
by Tom Barron 11 Mar '19

11 Mar '19

All, I served as Manila PTL for Rocky and Stein and am willing and able to take on that role in Train if you choose me. I continue to be less interested in adding new features to Manila itself than in improving its durability, ease of use, and consumability. I will continue to get the message out that Manila is loosely coupled with other OpenStack components and serves up storage via the network rather than through hypervisors so that it is ideally positioned to provide shared file storage both within and outside of OpenStack proper. I will work to make sure that storage vendors understand that if they maintain drivers for their back ends in Manila then this will at the same time enable them to provide storage for OpenStack consumers and also for Container Orchestrator clouds. I will continue to champion development of "**production quality**" 100% open source storage back ends for Manila. We have done a good job fostering new contributors and helping outreachy intern applicants get started. I want us to continue to be known as a friendly project and a good place to work. In Train we need to complete work already begun to: * build a manila CSI plugin * integrate manila into the OpenStack Client and SDK * integrate manila into OpenStack ansible and extend TripleO coverage to more storage back ends. In addition, in the Train cycle I want the Manila project to take up the challenge of shared storage as a service at the Edge. We need to: * Articulate use cases for shared storage (vs block or object) at the Edge. * Drive common understanding of appropriate service architecture for Edge. * Position vendors and open source software defined back ends for Edge deployments using Manila. These are the things that will drive me if you choose me as manila PTL. Thanks for listening, -- Tom Barron (tbarron)

1 0

[designate][election][ptl] PTL Candidacy
by Graham Hayes 11 Mar '19

11 Mar '19

Hi All, I would like to announce my candidacy for PTL of Designate for the Train cycle. I have been PTL for Mitaka, Newton, Ocata, Queens, Rocky, Stein (and hopefully Train), and have been a core for longer. I have been part of teams that ran Designate in production in public clouds, and also shipped products based on it. I feel that this gives a great viewpoint for where we should go. That said, leadership turn over is healthy, and is required to ensure that a project does not get stale, and in Designate we have been very bad at ensuring there is a good turn over (Designate has had 3 PTLs in its existance, 2 of which were originally from Managed I.T. - the company that founded it). As a result, Train will be my last cycle as PTL (if you see fit to elect me). My cycle goals will be to ensure a clean handover to the next PTL - writing down roadmaps, documenting what I do as PTL, and guiding anyone who is interested in taking on the role. While DNS is not something that is traditionally on a hype curve, we have had solid growth over the years, and the software we write is deployed in some of the largest OpenStack users. It is an important part of the Datacentre as a Service space, and we should be proud of it, and help promote its use where it fits. Thank you for taking the time to read this, and thank you for your support. - Graham (mugsie)

1 0

[ptl][election][mistral] PTL candidacy
by Renat Akhmerov 11 Mar '19

11 Mar '19

Hi, After a year break I'd like to announce my PTL candidacy for Mistral in Train cycle ([1] is the official patch to openstack/election). I’d like to thank Dougal Matthews who was the PTL from Feb 2018 up to the middle of Dec 2018 and performed really well in this period. In Dec Dougal decided to step down due to the changes in his work priorities and I agreed to take over. In the last two years we've been mainly focused on improving Mistral performance and the reason for this was that some big users began to adopt it for their production needs. The amount of work done in this area was huge and the result is orders of magnitude boost for a number of use cases. Although much was done and the core of the technology is pretty mature now, there's still a lot ahead: 1. Continue to improve performance (e.g. "join" tasks) 2. Make the technology more product-like. That is, eliminating obvious gaps in the documentation (inconsistent structure, lack of tutorials, etc.), installation and configuration tools, tools for developing custom actions and functions easier and plugging them in easier. The ultimate goal here is to make sure that a new user can start using the technology within minutes, and the experience should be as positive as possible. Another thing that I'd like to do is to attract more talented and qualified contributors, i.e. to make the project community stronger. So if one has interest in working on Mistral we're always open and ready to help witn getting up to speed. Most likely, not all of the things mentioned above will be done in Train but I want to make sure we finally started addressing #2 in a more serious way than before. The best way to get in touch with us is IRC channel #openstack-mistral or the openstack-discuss mailing list (with [mistral] tag in email subject). [1] https://review.openstack.org/#/c/642336 Thanks Renat Akhmerov @Nokia

1 0

[sdk] Request to release newer version of openstacksdk for Stein Cycle
by Patil, Tushar 11 Mar '19

11 Mar '19

Hi SDK team, I have requested a release of openstacksdk which includes changes to the instance-ha service to get the recovery workflow details of the notification. Kindly consider our request on behalf of Masakari team to release a newer version of openstacksdk so that we can use this newer version in masakari-dashboard [1] to render the recovery workflow details on the notification screen. Thank you in advance for your cooperation. [1] : https://review.openstack.org/#/c/640755/ Regards, Tushar Patil Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.

4 5

[neutron] Cancelling the Neutron Performance sub-team meeting
by Miguel Lavalle 11 Mar '19

11 Mar '19

Ho Team, I will be travelling March 11th on a business trip. As a consequence, we will cancel the performance sub-team meeting. We will resume normally on the 25th. Best regards Miguel

1 0

[cloudkitty] PTL candidacy
by Luka Peschke 11 Mar '19

11 Mar '19

Hello everybody, I would like to submit my candidacy as CloudKitty's PTL for the Train cycle. I've been contributing to the project since the Newton release and I've been the PTL for the Stein cycle. As a PTL, I'd like to keep working on the points we addressed during the last cycle: * Help CloudKitty's community to grow. Some work has been done during the stein cycle (IRC meetings have been reintroduced, the developer documentation has been improved...), but we need to keep putting effort into this. * Improve the documentation. Here again, this has been worked on in Stein (there have been a lot of documentation patches), but we are far from done. * Add missing features: I'd like to mentor developers willing to add endpoints to the v2 API, which has been added during the stein cycle. We have also been talking a lot about a new rating engine recently. It would be great to have a spec draft for this, on which we could work together. Thank you for your attention, Luka Peschke (peschk_l) Envoyé avec AquaMail pour Android https://www.mobisystems.com/aqua-mail

1 0