September 2019 - openstack-discuss

[manila][ptl][election] PTL candidacy for Ussuri
by Goutham Pacha Ravi 03 Sep '19

03 Sep '19

Greetings Zorillas & other Stackers, I would like to submit my candidacy to be the PTL of Manila for the Ussuri cycle. I have been a contributor to OpenStack since the Liberty release and a maintainer of Manila and its associated deliverables since the Ocata release. I have had the opportunity to work closely with, and learn from, two stellar engineers who have served as PTLs so far. I've also had the privilege of collaborating with contributors from varied backgrounds. This taught me the technical aspects of orchestrating Open Infrastructure Storage at cloud scale. I attribute the tremendous growth of the project to each of us in the project internalizing and espousing the "OpenStack Way" of upstream open-source development. My strongest qualification for this job is that I wake up excited about the problems we're solving. As an engineer I see features left to implement; as an ambassador, I see untapped use cases; as a maintainer, I see new contributors and technical debt. So, if you'll have me, as the PTL, I will work towards maturing Manila, tackling its technical debt, advocating its usage and sustaining its neutrality. I'll also continue doing the thing I love most: mentoring new members and preserving this well-knit community. In the near term, I propose that you and I: - Continue hard on the path to growing contributors: Stein/Train was an exciting time for us; we worked hard on this goal! We lowered the barrier of entry for new contributors by relaxing our review norms [1] and provided quick and easy tutorials [2] to bootstrap with our free and open source storage drivers, among many other things. We had an opportunity to mentor interns under Outreachy [3], Google Summer of Code [4] and the Open University of Israel [5] internship programs. Let's do more of this and ensure we have able successors. Let's also mentor reviewers and create more maintainers. - Complete integration to openstackclient/openstacksdk and evolve manila-csi by reaching feature parity to the rich feature-set we already provide. - Continue the work on reliability, availability and fault tolerance of individual components and allow for more flexible deployment scenarios. - Gather feedback from edge/telco/scientific computing consumers and address pain points. Thank you for your support, Goutham Pacha Ravi <gouthampravi(a)gmail.com> IRC: gouthamr [1] https://docs.openstack.org/manila/latest/contributor/manila-review-policy.h… [2] https://docs.openstack.org/manila/latest/contributor/development-environmen… [3] https://www.outreachy.org/apply/rounds/may-2019-august-2019-outreachy-inter… [4] https://summerofcode.withgoogle.com/projects/#5067835716403200 [5] https://review.opendev.org/#/q/committer:gilboa.nir%2540gmail.com+status:me… [6] Candidacy submission: https://review.opendev.org/679881

1 0

[adjutant][ptl] Adrian Turjak as Adjutant U cycle PTL
by Adrian Turjak 03 Sep '19

03 Sep '19

Hello OpenStackers, I'm submitting myself as the PTL for Adjutant during the U cycle. At this time I think I'm still the best suited to continue leading the project, with the best understanding of the codebase and the direction that the service is taking. The Train cycle was sadly not as productive as I'd have liked, purely because of how much big refactor work we've been in the middle of. The progress of that though has been good, and it should lay the groundwork for a very productive U cycle. The planned work for the next cycle is: - introduce partial policy support rather than relying on hardcoded decorators. - finish the long planned support for sub-project management - add project (and resource) termination logic - rework the identity manager as a pluggable construct. Cheers, Adrian Turjak

1 0

[qa][nova][migrate]CPU doesn't have compatibility
by 崔恒香 03 Sep '19

03 Sep '19

Hi This is my ERROR info(ocata): 2019-09-03 10:00:46.518 25163 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 5229, in check_can_live_migrate_destination 2019-09-03 10:00:46.518 25163 ERROR oslo_messaging.rpc.server disk_over_commit) 2019-09-03 10:00:46.518 25163 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 5240, in _do_check_can_live_migrate_destination 2019-09-03 10:00:46.518 25163 ERROR oslo_messaging.rpc.server block_migration, disk_over_commit) 2019-09-03 10:00:46.518 25163 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5670, in check_can_live_migrate_destination 2019-09-03 10:00:46.518 25163 ERROR oslo_messaging.rpc.server self._compare_cpu(None, source_cpu_info, instance) 2019-09-03 10:00:46.518 25163 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5938, in _compare_cpu 2019-09-03 10:00:46.518 25163 ERROR oslo_messaging.rpc.server raise exception.InvalidCPUInfo(reason=m % {'ret': ret, 'u': u}) 2019-09-03 10:00:46.518 25163 ERROR oslo_messaging.rpc.server InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have compatibility.

3 4

review.opendev.org Outage September 16 to Perform Project Renames
by Clark Boylan 03 Sep '19

03 Sep '19

Hello, We will be taking a Gerrit outage of about an hour on September 16 at 14:00 UTC to perform project renames. Please let us know if this scheduling does not work for some reason. We have tried to schedule this for a quiet time at the end of OpenStack's Train release cycle. Also, if you'd like to rename a project, now is the time to start prepping for that. Feel free to ask us any questions you have or bring up your concerns with us. Thank you for your patience, Clark

1 0

[nova][ptl] Eric Fried candidacy for Nova U PTL
by Eric Fried 03 Sep '19

03 Sep '19

I would be honored to continue serving as the Nova PTL in the Ussuri release [0]. Please note that I will not be in Shanghai. As Train PTL, I am working to delegate the project update [1]. If reelected for Ussuri, I intend to do the same for PTG responsibilities, including doing as much as possible via "virtual pre-PTG" on the mailing list. Being PTL for Train has been a growth experience. It has forced me to take a broader view of the project versus my previous focus on my topics of interest [2]. The flip-side is that I have had less time to devote to those things, and that has been a sacrifice. As such, I intend to be bolder about delegating this time around. In my stump speech for Train [3] I expressed a desire to grow contributor participation. I feel we have seen positive movement with new and existing non-cores showing improved code and review activity. Let's maintain the encouraging atmosphere and continue to grow in this space. However, core participation has not seen the same health, and it shows in the relatively low volume of feature work that has been accomplished to date in Train (more on this below). This has been one of my main frustrations as Nova Cat-Herder: like cats, Nova cores are mysterious beings motivated by forces beyond my ability to control. I would like to find ways to make core review activity more consistent as a step toward being able to predict more accurately what we can expect to get done in a cycle. This should make everyone's (project) managers happier, a delicious treat made with real tuna. Feature-wise, I was disappointed in the lack of progress exploiting nested resource providers. The Placement team worked hard to deliver the dependencies [4] to allow us to express things like subtree affinity for NUMA, but Nova missed the boat (train) due to lack of resource [5] and inability to agree on how to move forward [6]. Expressing NUMA in Placement is going to be the next major inflection point for scheduling robustness and performance; we need to get serious about making it a priority. But first we should finish what we started, closing on the many almost-there features that are looking risky for Train. We should be conservative about committing to new features until those are done. Thanks, Eric Fried (efried) (say it like "freed") [0] https://review.opendev.org/679862 [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-August/thread.h… [2] meaning things my employer cares about, areas where I have background/expertise, and things that sound fun and/or further some mission of Nova/OpenStack [3] https://opendev.org/openstack/election/src/branch/master/candidates/train/N… [4] https://docs.openstack.org/placement/latest/specs/train/approved/2005575-ne… [5] insert Placement joke here [6] https://review.opendev.org/#/c/650963/

1 0

[tc] weekly update
by Mohammed Naser 03 Sep '19

03 Sep '19

Hi everyone, Here’s the update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. # General changes - Added kayobe as a deliverable of the kolla project: https://review.opendev.org/#/c/669299/ Thanks! 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

[ptl] [docs] [election] PTL Candidacy for Ussuri
by Alexandra Settle 03 Sep '19

03 Sep '19

Hey all, I would like to submit my candidacy for the documentation team's PTL for the Ussuri cycle. Stephen Finucane (Train PTL) will be unofficially serving alongside me in a co-PTL capacity so we can equally address documentation-related tasks and discussions. I served as the documentation PTL for Pike, and am currently serving as an elected member of the Technical Committee in the capacity of vice chair. I have been a part of the community since the beginning of 2014, and have seen the highs and the lows and continue to love working for and with this community. The definition of documentation for OpenStack has been rapidly changing and the future of the documentation team continues to evolve and change. I would like that opportunity to help guide the documentation team, and potentially finish what myself, Petr, Stephen and many others have started and carried on. Thanks, Alex -- Alexandra Settle <a.settle(a)outlook.com> IRC: asettle

3 3

[elections][tc] Announcing Candidacy for OpenStack Technical Committee
by Jay Bryant 03 Sep '19

03 Sep '19

Dear OpenStack Community, This note is to officially announce my candidacy for the OpenStack TC. For those of you that don’t know me, allow me to introduce myself: [1] I have been active in the OpenStack Community since early in 2013. After nine years of working on Super Computing Solutions with IBM I moved to OpenStack and started working on Neutron (Quantum back in those days) before moving over to a relatively new project called Cinder. Within IBM I worked to create the processes for IBM’s storage driver development teams to interact with and contribute to the Cinder project. I became a core member of the Cinder team in the middle of 2013 and have remained active ever since. [2] [3] I have been the Cinder PTL for the last two years, starting in the Queens release. Beyond Cinder I have sought opportunities to work across OpenStack projects. I was the liaison between the Cinder and Documentation teams. This lead to opportunities to learn how OpenStack’s documentation is developed and enabled me to help improve the Cinder team’s documentation. I have also served for quite some time as the liaison to the Oslo team. Education and on-boarding of new team members has been a focus of my tenure in OpenStack. I started helping to lead the OpenStack Upstream Institute at the fall 2016 Summit in Barcelona. After Barcelona I helped to revise the education to meet the needs of future Upstream Institute sessions and have coordinated with my current employer, Lenovo, to sponsor each OpenStack Upstream Institute at Summits since the Spring 2017 Summit in Boston. Lenovo will even be hosting the OUI session in Shanghai! I also created Cinder’s on-boarding education which I have presented at each Summit since the Fall 2017 Summit in Sydney. I have sought opportunities to mentor new contributors both within my employers and from the community in general. I have a long experience working with OpenStack and a broad understanding of how the community works, I also feel that I have a breadth of technical experience that will benefit the TC. I have experience in High Performance Computing and feel I can understand and represent the needs of the HPC community. I have years of experience in the storage realm and can represent the unique concerns that storage vendors bring to OpenStack and the subsequent concerns that our OpenStack distributors have supporting OpenStack and its many drivers. Since moving from IBM to Lenovo my focus has changed from development of OpenStack to developing solutions that leverage OpenStack. I have enjoyed the opportunity to become a consumer of OpenStack as it has given me an opportunity to better understand the versatility and complexity of OpenStack. I have been working with customers with an interest in both telco applications, particularly where Edge computing is concerned, as well as enterprise customers. Given my latest work I feel that I am able to understand and represent many interests from the OpenStack community. If elected to the TC here are some of the concerns that I would like to address: * Ensure that we continue to improve our on-boarding and educational processes. The days where people are assigned to only work on OpenStack are gone. The easier we make it for people to successfully contribute to and leverage OpenStack, the more likely they will be to continue to contribute. * Improve documentation of OpenStack and Project processes. There have been a lot of discussions lately regarding undocumented processes. There is a lot of tribal knowledge involved in OpenStack and this too makes it hard for new contributors to integrate. Improving the documentation/description of ‘how we build OpenStack’ is crucial. * I would like the community as a whole to seek ways to make OpenStack more consumable by our users and distributors. I think the move to having longer lived stable branches has been a good step, but it has not resolved all the issues posed by customers that stay on older releases of OpenStack. The stable backport policies need to be readdressed to seek a solution that allows vendors to backport code for their customers, improving OpenStack’s usability without risking its stability. * I would like to continue the work that has been started to increase the visibility of the TC’s contributions to OpenStack and increase the effort to have the TC be a resource to the whole community. * I want to seek opportunities for OpenStack to continue to inter-operate with other cloud solutions. Virtualization is not the only cloud approach available and customers, very often, do not want just one solution or the other. OpenStack needs to continue to expand to address these concerns to remain vibrant and relevant. I hope that the thoughts above have resonated with you and appreciate you considering me for a position on the Technical Committee. I am passionate about OpenStack and believe that we have a community like no other in the industry. It would be a great honor to represent this community in a new capacity. Sincerely, Jay Bryant [1] Foundation Profile: https://www.openstack.org/community/members/profile/8348/jay-bryant [2] Reviews: https://www.stackalytics.com/?user_id=jsbryant [3] Commits: https://www.stackalytics.com/?user_id=jsbryant&metric=commits IRC (Freenode): jungleboyj

1 0

[TripleO][CI] Outage on the rdoprojects.org server is causing jobs to fail
by Gabriele Cerami 03 Sep '19

03 Sep '19

Hi, this weekend, and outage caused trunk.rdoprojects.org servers to become unreachable. As main effect, all tripleo ci jobs were unable to download and install dlrn repositories for the needed hashes and failed. The outage has been resolved yesterday but there's a problem with DNS propagation and we're still seeing DNS queries returning incorrect IPs, and as a result, jobs are not consistently passing. You may see problems dowloading repos, building changes, installing packages We would advise to limit the rechecks until we are sure the DNS results are stable. Thanks.

2 1

[elections][ptl][tc][adjutant][cyborg][designate][i18n][manila][nova][openstacksdk][placement][powervmstackers][winstackers] Missing PTL/TC Candidates!
by Jeremy Stanley 03 Sep '19

03 Sep '19

A final reminder, we are now into the last few hours for declaring PTL and TC candidacies. Nominations are open until Sep 03, 2019 23:45 UTC. If you want to stand for election, don't delay, follow the instructions to make sure the community knows your intentions: https://governance.openstack.org/election/#how-to-submit-a-candidacy Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. With approximately six hours remaining, the 10 projects tagged in the Subject line of this message will be deemed leaderless if no eligible nominees step forward. In this case the TC will directly oversee PTL selection/appointment. We also need at least one more TC candidate to have enough to fill the six open seats on the OpenStack Technical committee. Thank you, -- Jeremy Stanley, on behalf of the OpenStack Technical Election Officials

1 0