- openstack-discuss - lists.openstack.org

[Cyborg][IRC] The Cyborg IRC meeting will be held Wednesday at 0300 UTC
by Li Liu 26 Feb '19

26 Feb '19

Sorry for the late reminder The IRC meeting will be held Wednesday at 0300 UTC, which is 10:00 pm est(Tuesday) / 7:00 pm pst(Tuesday) /11 am Beijing time (Wednesday) -- Thank you Regards Li

1 0

[all] 'Train' TC Election Voting Period Begins!
by Kendall Nelson 26 Feb '19

26 Feb '19

Hello All! The poll for the TC Election is now open and will remain open until Mar 05, 2019 23:45 UTC. We are selecting 7 TC members, please rank all candidates in your order of preference. You are eligible to vote if you are a Foundation individual member[1] that also has committed to one of the official programs projects[2] over the Feb 09, 2018 00:00 UTC - Feb 19, 2019 00:00 UTC timeframe (Rocky to Stein) or if you are one of the extra-atcs.[3] What to do if you don't see the email and have a commit in at least one of the official programs projects[2]: * check the trash or spam folder of your gerrit Preferred Email address[4], in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from the program project repos[2] and email the election officials[1]. If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Our democratic process is important to the health of OpenStack, please exercise your right to vote. Candidate statements/platforms can be found linked to Candidate names[6]. Happy voting! Thank you, -Kendall Nelson (diablo_rojo) [1] http://www.openstack.org/community/members/ [2] https://git.openstack.org/cgit/openstack/governance/plain/reference/project… [3] Look for the extra-atcs element in [2] [4] Sign into review.openstack.org: Go to Settings > Contact Information. Look at the email listed as your preferred email. That is where the ballot has been sent. [5] http://governance.openstack.org/election/#election-officials [6] http://governance.openstack.org/election/#stein-tc-candidates

2 1

[cinder] extra_capabilities for scheduler filters
by Sam Morrison 26 Feb '19

26 Feb '19

Hi, Just wondering if extra_capabilities should be available in backend_state to be able to be used by scheduler filters? I can't seem to use my custom capabilities within the capabilities filter. Thanks, Sam

2 2

[tc][election] New series of campaign questions
by Jean-Philippe Evrard 26 Feb '19

26 Feb '19

Hello, Here are my questions for the candidates. Keep in mind some might overlap with existing questions, so I would expect a little different answer there than what was said. Most questions are intentionally controversial and non-strategic, so please play this spiritual game openly as much as you can (no hard feelings!). The objective for me with those questions is not to corner you/force you implement x if you were elected (that would be using my TC hat for asking you questions, which I believe would be wrong), but instead have a glimpse on your mindset (which is important for me as an individual member in OpenStack). It's more like the "magic wand" questions. After this long introduction, here is my volley of questions. A) In a world where "general" OpenStack issues/features are solved through community goals, do you think the TC should focus on "less interesting" technical issues across projects, like tech debt reduction? Or at the opposite, do you think the TC should tackle the hardest OpenStack wide problems? B) Do you think the TC must check and actively follow all the official projects' health and activities? Why? C) Do you think the TC's role is to "empower" project and PTLs? If yes, how do you think the TC can help those? If no, do you think it would be the other way around, with PTLs empowering the TC to achieve more? How and why? D) Do you think the community goals should be converted to a "backlog"of time constrained OpenStack "projects", instead of being constrained per cycle? (with the ability to align some goals with releasing when necessary) E) Do you think we should abandon projects' ML tags/IRC channels, to replace them by focus areas? For example, having [storage] to group people from [cinder] or [manila]. Do you think that would help new contributors, or communication in the community? F) There can be multiple years between a "user desired feature across OpenStack projects", and its actual implementation through the community goals. How do you think we can improve? G) What do you think of the elections process for the TC? Do you think it is good enough to gather a team to work on hard problems? Or do you think electing person per person have an opposite effect, highlighting individuals versus a common program/shared objectives? Corollary: Do you think we should now elect TC members by groups (of 2 or 3 persons for example), so that we would highlight their program vs highlight individual ideas/qualities? Thanks for your patience, and thanks for your application! Regards, Jean-Philippe Evrard (evrardjp)

7 6

Introducing myself - Namrata Jha.
by Namrata Jha 26 Feb '19

26 Feb '19

Hello everyone! I am Namrata Jha, from India and I am an Outreachy 2019 aspirant. I am extremely excited to learn a lot and benefit from this community! :) I looked through the GitHub repository for the project "Storyboard Database Query Optimizations" and found that there are no existing issues on the repository yet. It would be really kind if someone could guide me how do I go about code contribution. Thank you. Regards, Namrata Jha. P.S. I was having some issues in joining the IRC. The error message says, "Disconnected: Failed to connect - Invalid hostname (Your hostname looks invalid: freenode Check your host, port and ssl settings <https://www.irccloud.com/irc/freenode>);" I might be missing something already stated, but please help me out I'd be really grateful to you.

2 2

[nova] nova spec show-server-group response format
by yonglihe 26 Feb '19

26 Feb '19

Hi, guys The approved spec show-server-group had 2 options for response. 1. First one(current spec): "server": { "server_groups": [ # not cached "0b5d2c72-12cc-4ba6-a8d7-3ff5cc1d8cb8" ] } } related discuss: https://review.openstack.org/#/c/612255/11/specs/stein/approved/show-server… digest: This decouple the current implementation of server groups then get a generic API. 2 Second one: "server": { "server_group": { "name": "groupA", "id": "0b5d2c72-12cc-4ba6-a8d7-3ff5cc1d8cb8" } related discuss: https://review.openstack.org/#/c/612255/4/specs/stein/approved/list-server-… digest: people have tried to change the api to allow adding/removing servers to/from groups, but still not implement yet. we need align this for continuing this work. thanks. Reference: bp: https://blueprints.launchpad.net/nova/+spec/show-server-group spec: https://review.openstack.org/#/c/612255/13/specs/stein/approved/show-server… code: https://review.openstack.org/#/c/621474/23 Regards Yongli He

3 2

[openstack-helm] Initial spec for multiple container distribution support
by Pete Birley 26 Feb '19

26 Feb '19

Hi, One of the items that came up in the meeting this week was to get a spec together for supporting multiple distributions in containers managed via OpenStack-Helm. Currently, we ubiquitously use Ubuntu-based images, but would also like to support both CentOS and OpenSUSE in addition. As there's a lot to discuss here, I've created the following etherpad to allow us to work through these issues prior to the next meeting - at which point we should hopefully be at the point where we can start writing a formal spec. * https://etherpad.openstack.org/p/openstack-helm-container-distro-support Cheers Pete

1 0

[openstack-helm] Team Meeting (5th March 2019)
by Pete Birley 26 Feb '19

26 Feb '19

Hey! The next OpenStack-Helm meeting will be held on the 5th March, at 3pm UTC in #openstack-meeting-4 in freenode IRC. Thanks to all those who could attend the one we held on the 26th Feb: * the agenda we used is here: https://etherpad.openstack.org/p/openstack-helm-meeting-2019-02-26 * the minutes logged here: http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.… It would be great if people interested in OSH could attend, though we appreciate that's not possible, or desirable, for many. The agenda for the next meeting is here: https://etherpad.openstack.org/p/openstack-helm-meeting-2019-03-05 please feel free to add to it, even if you cannot attend. Look forward to seeing you all either in IRC or here. Cheers Pete

1 0

[ops] ops meetups team meeting in 5 minutes - Berlin NEXT WEEK!
by Chris Morgan 26 Feb '19

26 Feb '19

Those of you interested or attending, please join us on #openstack-operators to have a final chat about next week's ops meetup in Berlin. Chris -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[nova][neutron][os-vif] upcoming release of os-vif
by Sean Mooney 26 Feb '19

26 Feb '19

hi everyone. As many people know the non-client lib freeze is thursday the 28th so it is time to do the final os-vif release for stein. there are a number of pending patches to os-vif https://review.openstack.org/#/q/project:openstack/os-vif+status:open+branc… while i think we can merge several of them i have sorted them into groups below. required: remove use of brctl from vif_plug_linux_bridge https://review.openstack.org/636822 remove use of brctl from vif_plug_linux_bridge https://review.openstack.org/636821 prefer to merge: Add native implementation OVSDB API https://review.openstack.org/482226 make functional tests run on python 3 https://review.openstack.org/638053 nice to have: modify functional base.py to allow using vscode https://review.openstack.org/638058 docs: Add API docs for VIF types https://review.openstack.org/637009 doc: Use sphinx.ext.todo for profile, datapath offload types https://review.openstack.org/638405 docs: Start using sphinx.ext.autodoc for VIF types https://review.openstack.org/638404 docs: Add API docs for profile, datapath offload types https://review.openstack.org/638395 defer: Add 'SUPPORT_BW_CONFIG' option to VIFs https://review.openstack.org/636933 the required patches are makeing there way though the gate. i would hope we can merge most of the patches in the prefer and nice to have buckets but my intent is to propose a patch to the release repo tonight with the head of master proably at or after 20:00 UTC which will be around noon PST. that will give eu and us folks that want to review these changes a resonably amount of time. ideally we can try and get the release out early tommorow. once that is done os-vif will go into a a feature freeze until RC1 is released of nova and neutron at which point it will unfreeze. once i submit the patch for the release until thursday i would like to do a full code freeze on os-vif so that if there are any bugs that show up in the gate we can fix those without accepting any other changes. once we pass the non-client lib freeze on thrusday non feature patches such as docs changes or testing changes are fine but features should wait to RC1. regards sean

2 2