- openstack-discuss - lists.openstack.org

[neutron] Drivers meetings cancelled
by Slawek Kaplonski 30 Oct '19

30 Oct '19

Hi, Due to public holiday on November 1st and PTG on November 8th, lets cancel drivers meetings at those days. Next drivers meeting will take place at November 15th. -- Slawek Kaplonski Senior software engineer Red Hat

1 0

[neutron] CI meeting cencelled November 5th
by Slawek Kaplonski 30 Oct '19

30 Oct '19

Hi, Due to summit next week, lets cancel our CI meeting on November 5th. We will resume this meeting after the PTG on November 12th. -- Slawek Kaplonski Senior software engineer Red Hat

1 0

[neutron] Neutron team meeting cancelled
by Slawek Kaplonski 30 Oct '19

30 Oct '19

Hi, Due to the PTG/Summit next week, and public holiday in Poland on 11th Nov, lets cancel neutron team meetings in next 2 weeks. We will get back to this meeting as usuall on Tuesday, 19th Nov. See You in Shanghai :) -- Slawek Kaplonski Senior software engineer Red Hat

1 0

[ptg][nova][neutron][ironic][cinder][keystone][cyborg] Cross-project sessions
by Eric Fried 30 Oct '19

30 Oct '19

All- Time to coordinate cross-project sessions at the PTG. slaweq approached me about a nova/neutron session so I penciled it in on the nova etherpad [1]. If anyone has conflicts/objections with that time, please speak up and we'll try to coordinate. Other teams (including nova): If cross-project meetings are necessary, please suggest times in the etherpad and/or on this thread and/or by grabbing me (efried) on IRC. (Note that stephenfin (I think) will be running the room, but he's on vacation until the event.) Thanks, efried [1] https://etherpad.openstack.org/p/nova-shanghai-ptg

2 1

[octavia] Octavia weekly IRC meeting cancelled November 6th.
by Michael Johnson 30 Oct '19

30 Oct '19

As many of the cores are travelling to Shanghai and our meeting time would be at midnight, we are cancelling the November 6th Octavia IRC meeting. Safe travels everyone, Michael

1 0

Where do we support running tripleoclient
by Dougal Matthews 30 Oct '19

30 Oct '19

Hi all, Pretty much as the subject says. Do we specify where we support running tripleoclient? In theory it should run anywhere with the correct environment variables. However, as far as I understand most users run it on the undercloud itself. Is this something we have a position on? To give a little more context, this is relevant when replacing Mistral with Ansible. Can we assume that we are running ansible only against localhost or do we need to create an inventory for the undercloud? Cheers, Dougal

2 1

[neutron][ptg] Agenda for PTG
by Slawek Kaplonski 30 Oct '19

30 Oct '19

Hi neutrinos, I prepared agenda for our PTG sessions in Shanghai. It's available at [1]. Please check that and let me know if You need to add/change anything. [1] https://etherpad.openstack.org/p/Shanghai-Neutron-Planning -- Slawek Kaplonski Senior software engineer Red Hat

1 0

[ops][nova] Different quotas for different SLAs ?
by Massimo Sgaravatto 30 Oct '19

30 Oct '19

Dear all I would like to set different overcommitments factors for the compute nodes. In particular I would like to use some compute nodes without overcommitments, and some compute nodes with a cpu_allocation_ratio equals to 2.0. To decide if an instance should go to a compute node with or without overcommitment is easy; e.g. it could be done with host aggregates + setting metadata to the relevant flavors/images. But is it in some way possible to decide that a certain project has a quota of x VCPUs without overcommitment, and y VCPUs with overcommitments ? Or the only option is using 2 different projects for the 2 different SLAs (which is something that I would like to avoid) ? Thanks, Massimo

5 6

[PTG][interviews] We Want To Talk With YOU!
by Rain Leander 30 Oct '19

30 Oct '19

I am attending OIS and PTG and will conduct interviews on Friday 08 November in room Liberty. If you're keen and able, I'd love to talk with you. [0] These interviews have several purposes. Please consider all of the following when thinking about what you might want to say in your interview: * Tell the users/customers/press what you've been working on in Rocky * Give them some idea of what's (what might be?) coming in Stein * Put a human face on the OpenStack project and encourage new participants to join us * You're welcome to promote your company's involvement in OpenStack but we ask that you avoid any kind of product pitches or job recruitment In the interview I'll ask some leading questions and it'll go easier if you've given some thought to them ahead of time: * Who are you? (Your name, your employer, and the project(s) on which you are active.) * What did you accomplish in Rocky? (Focus on the 2-3 things that will be most interesting to cloud operators) * What do you expect to be the focus in Stein? (At the time of your interview, it's likely that the meetings will not yet have decided anything firm. That's ok.) * Anything further about the project(s) you work on or the OpenStack community in general. Finally, note that there are only 33 interview slots available, so please consider coordinating with your project to designate the people that you want to represent the project, so that we don't end up with 12 interview about Neutron, or whatever. It's fine to have multiple people in one interview - Maximum 3, probably. Interview slots are 30 minutes, in which time we hope to capture somewhere between 10 and 20 minutes of content. It's fine to run shorter, but 15 minutes is probably an ideal length. [0] https://docs.google.com/spreadsheets/d/1XwRC_nHm2hZs37Hlrb5fUl4zGtOGgekj1oH… -- K Rain Leander OpenStack Community Liaison Open Source Program Office https://www.rdoproject.org/ http://community.redhat.com

3 2

[heat] Heat PTG Schedule. Please join us!
by Rico Lin 30 Oct '19

30 Oct '19

Dear all, As Summit and PTG is right next week. would like to update our schedule with you. Our PTG session will be hosted on 11/7 full-day from 9:00 am to 4:30 pm in room Grizzly. You can suggest PTG sessions in our etherpad: https://etherpad.openstack.org/p/PVG-heat We also have project update session <https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24364…> on Monday, November 4, 2:35pm-2:50pm at Shanghai Expo Center - 5th Floor - 515 And Some sessions with heat tags on for your consideration: - Quick, Solid, and Automatic - OpenStack Bare-metal Orchestration <https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24215…> - Monday, November 4, 1:20pm-2:00pm, on Shanghai Expo Center - 6th Floor - 619 - Forum: Project Resource Cleanup - followup <https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24407…> - Monday, November 4, 11:40am-12:20pm in Shanghai Expo Center - 4th Floor - 431 - Leveraging OpenStack IaaS to run a Cloud CI/CD pipeline <https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24091…> - Monday, November 4, 2:05pm-2:15pm in Shanghai Expo Center - 5th Floor - Marketplace Theater - The Little Bag O'Tricks: 10 things you might not know you can do with OpenStack <https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24202…> - Tuesday, November 5, 11:40am-12:20pm in Shanghai Expo Center - 6th Floor - 617 - Enabling a Secure Industry 4.0transition for ShangHai Electric with OpenStack based Edge Clouds <https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24187…> - Wednesday, November 6, 3:20pm-4:00pm in Shanghai Expo Center - 6th Floor - 617 Here's my Wechat ID if you would like to find me there: RicoLinCloudGeek See you all in Shanghai! -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[meta-sig] SIG PTG schedule. feel free to join!
by Rico Lin 30 Oct '19

30 Oct '19

Hi all PTG is right next week, so if you're interested in SIG governance or you like to walk by and say hello, please join us! Both TC and UC will have people there as well! Our session will be hosted on 11/6 for a quarter-day from 3:20 pm to 5:00 pm in room 431. You can suggest PTG sessions in our etherpad: https://etherpad.openstack.org/p/PVG-meta-sig Here's my Wechat ID, if you like to find me there: RicoLinCloudGeek See you all in Shanghai! -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 1

[scientific-sig] IRC Meeting today (about 10 minutes time)
by Stig Telfer 29 Oct '19

29 Oct '19

Hi All - We have a Scientific SIG IRC meeting coming up at 2100 UTC in channel #openstack-meeting. Everyone is welcome. Today’s agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_October_29th_2019 Cheers, Stig

1 0

[nova]review guide for the policy default refresh spec
by Ghanshyam Mann 29 Oct '19

29 Oct '19

Hello Everyone, As many of you might know that in Train, we are doing Nova policy changes to adopt the keystone's new defaults and scope type[1]. There are multiple changes required per policy as mentioned in spec. I am writing this review guide for the patch sequence and at the end how each policy will look like. I have prepared the first set of patches. I would like to get the feedback on those so that we can modify the other policy also on the same line. My plan is to start the other policy work after we merge the first set of policy changes. Patch sequence: Example: os-services API policy: ------------------------------------------------------------- 1. Cover/Improve the test coverage for existing policies: This will be the first patch. We do not have good test coverage of the policy, current tests are not at all useful and do not perform the real checks. Idea is to add the actual tests coverage for each policy as the first patch. new tests try to access the API with all possible context and check for positive and negative cases. - https://review.opendev.org/#/c/669181/ 2. Introduce scope_types: This will add the scope_type for policy. It will be either 'system', 'project' or 'system and project'. In the same patch, along with existing test working as it is, new tests of scope type will be added which will run with [oslo_policy] enforce_scope=True so that we can capture the real scope checks. - https://review.opendev.org/#/c/645427/ 3. Add new default roles: This will add new defaults which can be SYSTEM_ADMIN, SYSTEM_READER, PROJECT_MEMBER_OR_SYSTEM_ADMIN, PROJECT_READER_OR_SYSTEM_READER etc depends on Policy. Test coverage of new defaults, as well as deprecated defaults, are covered in same patch. This patch will add the granularity in policy if needed. Without policy granularity, we cannot add new defaults per rule. - https://review.opendev.org/#/c/648480/ (I need to add more tests for deprecated rules) 4. Pass actual Targets in policy: This is to pass the actual targets in context.can(). Main goal is to remove the defaults targets which is nothing but context'user_id,project_id only. It will be {} if no actual target data needed in check_str. - https://review.opendev.org/#/c/676688/ Patch sequence: Example: Admin Action API policy: 1. https://review.opendev.org/#/c/657698/ 2. https://review.opendev.org/#/c/657823/ 3. https://review.opendev.org/#/c/676682/ 4. https://review.opendev.org/#/c/663095/ There are other patches I have posted in between for common changes or fix or framework etc. [1] https://specs.openstack.org/openstack/nova-specs/specs/train/approved/polic… -gmann

1 2

WFH
by Arun SAG 29 Oct '19

29 Oct '19

I have a doctors appointment around 3:45pm PST. Will WFH today. -- Arun S A G http://zer0c00l.in/

1 0

Important Shanghai PTG Information
by Kendall Waters 29 Oct '19

29 Oct '19

Hello Everyone! As I’m sure you already know, the Shanghai PTG is going to be a very different event from PTGs in the past so we wanted to spell out the differences so you can be better prepared. Registration & Badges Registration for the PTG is included in the cost of the Summit. It is a single registration for both events. Since there is a single registration for the event, there is also one badge for both events. You will pick it up when you check in for the Summit and keep it until the end of the PTG. The Space Rooms The space we are contracted to have for the PTG will be laid out differently. We only have a couple dedicated rooms which are allocated to those groups with the largest numbers of people. The rest of the teams will be in a single larger room together. To help people gather teams in an organized fashion, we will be naming the arrangements of tables after OpenStack releases (Austin, Bexar, Cactus, etc). Food & Beverage Rules Unfortunately, the venue does not allow ANY food or drink in any of the rooms. This includes coffee and tea. Lunch will be from 12:30 to 1:30 in the beautiful pre-function space outside of the Blue Hall. Moving Furniture You are allowed to! Yay! If the table arrangements your project/team/group lead requested don’t work for you, feel free to move the furniture around. That being said, try to keep the tables marked with their names so that others can find them during their time slots. There will also be extra chairs stacked in the corner if your team needs them. Hours This venue is particularly strict about the hours we are allowed to be there. The PTG is scheduled to run from 9:00 in the morning to 4:30 in the evening. Its reasonably likely that if you try to come early or stay late, security will talk to you. So please be kind and respectfully leave if they ask you to. Resources Power While we have been working with the venue to accomodate our power needs, we won’t have as many power strips as we have had in the past. For this reason, we want to remind everyone to charge all their devices every night and share the power strips we do have during the day. Sharing is caring! Flipcharts While we won’t have projection available, we will have some flipcharts around. Each dedicated room will have one flipchart and the big main room will have a few to share. Please feel free to grab one when you need it, but put it back when you are finished so that others can use it if they need. Again, sharing is caring! :) Onboarding A lot of the usual PTG attendees won’t be able to attend this event, but we will also have a lot of new faces. With this in mind, we have decided to add project onboarding to the PTG so that the new contributors can get up to speed with the projects meeting that week. The teams gathering that will be doing onboarding will have that denoted on the print and digital schedule on site. They have also been encouraged to promote when they will be doing their onboarding via the PTGBot and on the mailing lists. If you have any questions, please let us know! Cheers, The Kendalls (wendallkaters & diablo_rojo)

4 5

[tc][all] Ussuri community goal candidate 1: 'Project Specific New Contributor & PTL Docs'
by Ghanshyam Mann 29 Oct '19

29 Oct '19

Hello Everyone, We are starting the next step for the Ussuri Cycle Community Goals. We have four candidates till now as proposed in etherpad[1]. The first candidate is "Project Specific New Contributor & PTL Docs". Kendall (diablo_rojo) volunteered to lead this goal as Champion. Thanks to her for stepping up for this job. This idea was brought up during Train cycle goal discussions also[2]. The idea here is to have a consistent and mandatory contributors guide in each project which will help new contributors to get onboard in upstream activities. Also, create PTL duties guide on the project's side. Few projects might have the PTL duties documented and making it consistent and for all projects is something easy for transferring the knowledge. Kendall can put up more details and highlights based on queries. We would like to open this idea to get wider feedback from the community and projects team before we start defining the goal in Gerrit. What do you think of this as a community goal? Any query or Improvement Feedback? [1] https://etherpad.openstack.org/p/PVG-u-series-goals [2] https://etherpad.openstack.org/p/BER-t-series-goals -gmann & diablo_rojo

2 2

[neutron][performance] Cancelling Neutron performance meeting on November 4th
by Miguel Lavalle 29 Oct '19

29 Oct '19

Hi everybody, Due to the Summit/ Forum / PTG in Shanghai, we will cancel the Neutron performance meeting on November 4th. We will resume on the 18th Regards Miguel

1 0

[tripleo] October 5th TripleO meeting canceled
by Wesley Hayutin 29 Oct '19

29 Oct '19

Greetings, Due to the OpenStack PTG, the TripleO meeting scheduled for October 5th will be cancelled. Thank you!!

1 1

[nova] spec for feature liasion needed
by Brin Zhang(张百林) 29 Oct '19

29 Oct '19

Hi，nova core team: In Ussuri we add the feature liaison to lead the feature to do [1], now there are some specs needed find a feature liaison, as follows: 1. https://review.opendev.org/#/c/580336/ Support re-configure deleted_on_termination in server 2. https://review.opendev.org/#/c/663563/ Add flavor group 3. https://review.opendev.org/#/c/682302/ Allow specify user to reset password 4. https://review.opendev.org/#/c/691651/ Support fuzzy querying instance by tag [1] http://specs.openstack.org/openstack/nova-specs/readme.html#feature-liaison… Thanks. Brin Zhang

1 0

[PTG] Unoffical Game Night
by Kendall Nelson 29 Oct '19

29 Oct '19

Hello! While we won't have space in any official capacity, I am planning on bringing games and thinking Thursday would be a good night to play them if anyone wants to bring games and join me. Myself + other OSF staff are planning on hanging out at the Shanghai Marriott Hotel City Centre (Address: 555 Xizang Middle Rd, Huangpu, Shanghai, China, 200003) lobby bar starting at 8:00. For those interested I'm gathering an etherpad of people + games[1]. Hope to see you there! -Kendall (diablo_rojo) [1] https://etherpad.openstack.org/p/pvg-game-night

2 1

[tripleo] Stable policy and tripleoclient stdout
by Dougal Matthews 29 Oct '19

29 Oct '19

Hey all, As some of you will know there is work going on to replace Mistral with Ansible. There is an initial spec[1] and a few in-flight patches here to create the initial playbooks. In doing this work, I hit an issue I wanted to get some input in. first the tl;dr - what is our policy on changing the output from tripleoclient? It is proving difficult to keep it the same and in some cases changes will be required (we won't have Mistral execution IDs to print for example). As a quick reminder, in the current code we print from tripleoclient and Mistral sends messages via Zaqar to tripleoclient (which it then prints). This allows for "real time" updates from workflows. For example, introspection will print updates as introspection of nodes is completed. With Ansible it is tricky to have this same result. I can think of three options; 1. We run Ansible in the background, essentially hiding it and then polling OpenStack services to look for the expected state changes. We can then display this to the user. 2. We go for a "ansible native" approach and stream the ansible output to the user. This will be familiar to anyone familiar with Ansible but it will mean the output completely changes. This is also the easiest option (from an implementation point of view) 3. I have not tested this idea, but I think we could have a custom Ansible module that writes messages to a tempfile. tripleoclient could then consume them and display them to the user. This would be similar to idea 1, but rather than polling services we constantly read a file and display those "messages" from ansible. This would be closest to the current Mistral and Zaqar solution. Personally I am a bit torn. One of the reasons we want to use Ansible is because developers/users are more familiar with debugging it. However, if we hide ansible that might not help very much. So I think in the long run option 2 might be best. However, that completely changes the output, it limits us to what Ansible can output and frankly, in my experience, Ansible output is ugly and often hard to read. I am curious to know what y'all think and hopefully there are some other options too. Thanks, Dougal [1] https://review.opendev.org/#/c/679272/ [2] https://review.opendev.org/#/q/status:open+topic:mistral_to_ansible

3 3

[kuryr][kuryr-kubernetes] does kuryr-kubernetes support dynamic subnet by pod namespace or annotation?
by Yi Yang (杨�D)-云服务集团 29 Oct '19

29 Oct '19

Hi, Folks We need to create containers on baremetal for different tenants, so pod belongs to tenant VPC or tenant subnet, can we specify subnet by namespace or annotation in pod spec? I don’t mean multiple VIFs by additional subnets, I just need single OVS port for pod.

4 7

[docs][oslo] docs-tools repos now fully part of oslo
by Andreas Jaeger 28 Oct '19

28 Oct '19

In Juni, the following repos became part of Oslo project [1]: openstack/openstack-doc-tools openstack/os-api-ref openstack/openstackdocstheme openstack/whereto The ACL changes for these have been merged now [2] and IRC notifications happen now in #openstack-oslo [3]. The openstack-doc-tools launchpad project has also been assigned to the Oslo team [4]. Thanks Oslo team for adopting these tools. If there're any open topics or questions, feel free to ask Stephen Finucane or myself, Andreas References: [1] https://review.opendev.org/#/c/657141/ [2] https://review.opendev.org/670269 [3] https://review.opendev.org/670483 [4] https://launchpad.net/openstack-doc-tools -- Andreas Jaeger aj(a)suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

[neutron] Bug deputy report for week of October 25th
by Brian Haley 28 Oct '19

28 Oct '19

Hi, I was Neutron bug deputy last week. Below is a short summary about reported bugs. -Brian Critical bugs ------------- None High bugs --------- * https://bugs.launchpad.net/neutron/+bug/1849463 - linuxbridge packet forwarding issue with vlan backed networks - Related to https://bugs.launchpad.net/os-vif/+bug/1837252 - Asked for Rodolfo to add more information from IRC discussion - Marked High simply due to reverence to CVE * https://bugs.launchpad.net/neutron/+bug/1849976 - "networkdhcpagentbindings.binding_index" autoincrement parameter is not working - Caused by https://review.opendev.org/#/c/288271/ - Somehow merged even though DB migration script was in wrong dir - Should it be reverted? - https://review.opendev.org/#/c/691641/ is alternative fix-up Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/1849392 - Neutron - Stein - Having two external networks will prevent the router from being created - Could not reproduce, more information requested * https://bugs.launchpad.net/neutron/+bug/1849479 - neutron l2 to dhcp lost when migrating in stable/stein 14.0.2 - Might be related to 1849392 - Assigned to Slawek since triaging other bug might lead to answer * https://bugs.launchpad.net/neutron/+bug/1849449 - get_link_id() traceback in case of non-existing interface is misleading - https://review.opendev.org/#/c/690514/ * https://bugs.launchpad.net/neutron/+bug/1849676 - DHCP agents time out during startup at 60s when there is enough agents - https://review.opendev.org/#/c/682241/ is a possible fix? Low bugs -------- Wishlist bugs ------------- Invalid bugs ------------ Further triage required ----------------------- * https://bugs.launchpad.net/neutron/+bug/1849690 - designate not creating recordsets - Asked mlavalle to triage * https://bugs.launchpad.net/neutron/+bug/1849726 - Routed Networks DHCP agents getting ports in unconnected segments - Does look like a bug, triaging

1 0

[Kuryr] Meeting move to office hours on #openstack-kuryr and 1500 UTC
by Michał Dulko 28 Oct '19

28 Oct '19

Hi, The attendance at the Kuryr meetings was very low recently, making most of them just my monologues (e.g. [1], [2], [3], [4]). Given that I made a decision to switch to office hours model on our #openstack-kuryr channel. If you have anything to discuss, just drop by and ping me (dulek) or ltomasbo on the channel. Moreover most of the team is based in Europe and have a conflict after last weekend DST change, so I'm moving the meeting to 1500 UTC. Also please note that next week's meeting falls during OpenInfra Summit that I'm attending, so we'll be skipping that meeting. The commit doing the changes is at [5]. Thanks, Michał [1] http://eavesdrop.openstack.org/meetings/kuryr/2019/kuryr.2019-10-28-14.33.l… [2] http://eavesdrop.openstack.org/meetings/kuryr/2019/kuryr.2019-10-21-14.00.l… [3] http://eavesdrop.openstack.org/meetings/kuryr/2019/kuryr.2019-09-23-14.04.l… [4] http://eavesdrop.openstack.org/meetings/kuryr/2019/kuryr.2019-09-16-14.03.l… [5] https://review.opendev.org/#/c/691703/

1 0