March 2019 - openstack-discuss - lists.openstack.org

[all] Last call for "Train" TC Election voting
by Jeremy Stanley 04 Mar '19

04 Mar '19

We are coming down to the last hours for voting in the TC election. Voting ends Mar 05, 2019 23:45 UTC. Search your gerrit preferred email address[0] for the following subject: Poll: 'Train' TC Election (note the unfortunate escaping of quotes around the release cycle name, we'll strive to do better for the PTL polls) That is your ballot and links you to the voting application. Please vote. If you have voted, please encourage your colleagues to vote. Candidate statements are linked to the names of all confirmed candidates: https://governance.openstack.org/election/#train-tc-candidates What to do if you don't see the email and have a commit in at least one of the official programs projects[1]: * check the trash of your gerrit Preferred Email address[0], 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[1] and email the election officials[2]. 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. Please vote! Thank you, [0] 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. [1] https://git.openstack.org/cgit/openstack/governance/plain/reference/project… [2] https://governance.openstack.org/election/#election-officials -- Jeremy Stanley

1 0

[placement] Placement and Storyboard
by Chris Dent 04 Mar '19

04 Mar '19

As discussed in today's scheduler meeting [1]: Placement now has a home in Storyboard for all four of placement, osc-placement, os-resource-classes and os-traits. https://storyboard.openstack.org/#!/project_group/placement For the rest of Stein we will be using both existing launchpad projects and storyboard for reporting and managing placement-related bugs. The reason for the transition is simply to not surprise anyone nor lose bugs while we are nearing a release. In Train placement-related projects will solely use Storyboard for bugs and feature tracking. For the rest of Stein, placement developers should watch both places for bugs. For remembering features or other work that is planned for Train, make a story in Storyboard. Based on discussion we've had thus far, "stories" seem the best choice for a replacement for blueprints. People who experience placement bugs and report them to launchpad, that's okay. We'll notice and try to do our best to deal with them, starting at least in Train, but maybe sooner, we may respond with "could you please report this in Storyboard instead". Note that because placement bugs lived in the nova project, there's no way to "shut down" launchpad once we migrate to Storyboard. We will need to be conscious of that for quite some time. We'll all be learning to use Storyboard as we go, so there may be a few hiccups. It's okay. We'll deal. As Ed pointed out in the meeting "Be prepared for a "moving to git from svn" brain reshuffling. The workflow is not 1:1 to launchpad" Because of that I think that rather than hewing to a strict process we should be aware of our intentions and be flexible. With luck our general trend of "not that many bugs" (thus easy to manage) will continue. If you have questions, concerns, or suggestions for how to make it all delightful, please share them. /me knocks wood Thanks. [1] http://eavesdrop.openstack.org/meetings/nova_scheduler/2019/nova_scheduler.… -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

1 0

[fenix] starting bi-weekly meetings
by Juvonen, Tomi (Nokia - FI/Espoo) 04 Mar '19

04 Mar '19

Hi, Now reaching a point with the Fenix project where we should start to have meetings in #openstack-fenix. I propose to have a bi-weekly meeting at 6 AM UTC, starting from 11th March. Please give your +1 or indicate if the time does not suit to you. For those who have not heard about the project, you can find more from [1]. Currently working to have the rolling OpenStack upgrade implemented before ONS summit and then make it a job to be run on each patch later on. What is awesome is that I use multinode DevStack environment and I am modifying the scripts to do most of the node upgrade for me just by passing "UPGRADE=True" in local.conf. Let's see how it goes, might be a quite generic solution for anybody to test upgrade with own changes to projects. [1] https://wiki.openstack.org/wiki/Fenix Regards, Tomi Fenix PTL

2 3

[cyborg] [ptg] Denver Train PTG etherpad available
by Nadathur, Sundar 03 Mar '19

03 Mar '19

Hi all, The Cyborg etherpad for Denver PTG is available [1]. Please feel free to add topics or comment on the proposed ones. [1] https://etherpad.openstack.org/p/cyborg-ptg-train Regards, Sundar

1 0

[infra] CI at ustack.com sending results to graphite.opendev.org
by Ian Wienand 03 Mar '19

03 Mar '19

Hello, I didn't find any contact details for ustack.com on [1], but it seems an internal Zuul+nodepool setup there (my best guess based on the names of variables in the packet contents) is sending all its stats to graphite.openstack.org (recently migrated to graphite.opendev.org) The address ends with .139.162 if that helps. It isn't really a problem because it doesn't pass our firewall; but if you know who maintains this you might like to point it somewhere more useful :) Cheers, -i [1] https://wiki.openstack.org/wiki/ThirdPartySystems

1 0

[openstack-helm] support per-host auto_bridge_add
by Li, Cheng1 03 Mar '19

03 Mar '19

Hi Pete, Sorry for disturbing you, but I really would like to merge this patch ASAP. I have updated the patch https://github.com/stackanetes/kubernetes-entrypoint Could you please help review it again? Thanks. Thanks, Cheng

1 1

[all][ops] Ops Meetup Agenda Planning - Berlin Edition
by Erik McCormick 03 Mar '19

03 Mar '19

Hello All, The time is rapidly approaching for the Ops Meetup in Berlin. In preparation, we need your help developing the agenda. i put an [all] tag on this because I'm hoping that anyone, not just ops, looking for discussion and feedback on particular items might join in and suggest sessions. It is not required that you attend the meetup to post session ideas. If there is sufficient interest, we will hold the session and provide feedback and etherpad links following the meetup. Please insert your session ideas into this etherpad, add subtopics to already proposed sessions, and +1 those that you are interested in. Also please put your name, and maybe some contact info, at the bottom. If you'd be willing to moderate a session, please add yourself to the moderators list. https://etherpad.openstack.org/p/BER-ops-meetup I'd like to give a big shout out to Deutsche Telekom for hosting us and providing the catering. I look forward to seeing many of you in Berlin! Cheers, Erik

3 3

[dev] [qa][ptg] Train PTG Planning for QA
by Ghanshyam Mann 03 Mar '19

03 Mar '19

Hello Everyone, I have prepared the etherpad[1] to collect the Train cycle PTG topic ideas for QA. Please start adding your item/topic you want to discuss in PTG or comment on proposed topics. Even you are not making to PTG physically, still, add your topic which you want us to discuss or give a thought. Anyone is welcome to add the cross-project testing topics they want to discuss related to QA. For example, keystone (lance) is planning one for system-scope testing. [1] https://etherpad.openstack.org/p/qa-train-ptg -gmann

1 0

sriov bonding
by Manuel Sopena Ballesteros 03 Mar '19

03 Mar '19

Hi, Is there a documentation that explains how to setup bonding on SR-IOV neutron? Thank you Manuel NOTICE Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed.

6 7

networking-vpp 19.03 now available
by Ian Wells 02 Mar '19

02 Mar '19

Hello All, We'd like to invite you all to try out networking-vpp 19.03. As many of you may already know, VPP is a fast user space forwarder based on the DPDK toolkit. VPP uses vector packet processing algorithms to mininmise the CPU time spent on each packet to maxmise throughput. Networking-vpp is a ML2 mechanism driver that controls VPP on your control and compute hosts to provide fast L2 forwarding under Neutron. This latest version is updated to work with VPP 19.01. In the 19.03 release, we added a few features: - To complement the GPE overlay, there is now also a L3 solution for port mirroring (OpenStack TaaS) connections. When you're using GPE, the overlay is L3 and you may have routers between your compute nodes, so moving the TAP traffic around also requires an L3 overlay. We use VXLAN point to point connections to get that copy of traffic to the VM destination, and these can be routed over L3. We automatically use VXLAN connections when you're tapping ports on GPE networks and VLAN connections for L2 networks so this should all Just Work. - We've worked on out Python 3 compatibility in preparation for the EOL of Pythnon 2. Both the Neutron server's driver components and the agent components that control VPP should now support Python 3, but this work is ongoing and if you do find any issues please report them on the Launchpad page. - We've worked on our L3 Neutron routers support and added functionality that allows you to use NAT from multiple routers simultaneously - ideal if, for instance, you like to use one router per tenant and in more unusual cases routers with different external networks. - We've been doing the usual round of bug fixes and updates - the code will work with both VPP 18.10 and 19.01 and has been updated to keep up with Neutron Rocky and Stein. The README [1] explains how you can try out VPP using devstack: the devstack plugin will deploy the mechanism driver and VPP and should give you a working system with a minimum of hassle. We will be continuing our development for VPP's 19.04 release. We welcome anyone who would like to come help us. -- Ian & Naveen

1 0