Friday, 2018-11-02

*** hongbin has joined #openstack-meeting00:17
*** ssbarnea has quit IRC00:25
*** Liang__ has joined #openstack-meeting00:36
*** longkb has joined #openstack-meeting00:44
*** cloudrancher has quit IRC00:53
*** cloudrancher has joined #openstack-meeting00:54
*** fanzhang has joined #openstack-meeting00:54
*** cloudrancher has quit IRC00:56
*** cloudrancher has joined #openstack-meeting00:56
*** diablo_rojo has quit IRC01:16
*** Liang__ has quit IRC01:20
*** hongbin has quit IRC01:32
*** iyamahat has quit IRC01:48
*** yamahata has quit IRC01:48
*** munimeha1 has quit IRC02:08
*** mhen has quit IRC02:11
*** hongbin has joined #openstack-meeting02:12
*** mhen has joined #openstack-meeting02:13
*** hle21 has joined #openstack-meeting02:24
*** yamamoto has joined #openstack-meeting02:31
*** bobh has joined #openstack-meeting02:37
*** cloudrancher has quit IRC02:38
*** cloudrancher has joined #openstack-meeting02:38
*** jamesmcarthur has joined #openstack-meeting02:43
*** cloudrancher has quit IRC02:43
*** cloudrancher has joined #openstack-meeting02:44
*** jamesmcarthur has quit IRC02:44
*** jamesmcarthur has joined #openstack-meeting02:45
*** bobh has quit IRC02:57
*** yamamoto has quit IRC03:09
*** yamamoto has joined #openstack-meeting03:09
*** yamamoto has quit IRC03:09
*** cloudrancher has quit IRC03:21
*** cloudrancher has joined #openstack-meeting03:21
*** jamesmcarthur has quit IRC03:25
*** jamesmcarthur has joined #openstack-meeting03:26
*** yamamoto has joined #openstack-meeting03:30
*** jamesmcarthur has quit IRC03:39
*** akhil_jain has joined #openstack-meeting03:57
*** ekcs has joined #openstack-meeting04:00
ekcstime for congress meeting04:01
ekcs#startmeeting congressteammeeting04:01
openstackMeeting started Fri Nov  2 04:01:31 2018 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: congressteammeeting)"04:01
openstackThe meeting name has been set to 'congressteammeeting'04:01
ekcstopics collected here as usual.
ekcsfeel free to add your topics there!04:03
akhil_jainekcs: Hi!04:05
ekcshi akhil_jain !04:05
ekcshappy friday!04:05
akhil_jainHappy friday04:06
ekcsok let’s get started then!04:06
ekcs#topic gate04:06
*** openstack changes topic to "gate (Meeting topic: congressteammeeting)"04:06
ekcsjust want to give a quick update on gate.04:06
ekcsHere’s the discussion on check & gate slowness from a while back.
ekcsI merged a change that reduced congress CI footprint to help make the situation better and also help our own productivity.04:08
*** david-lyle has joined #openstack-meeting04:08
ekcsthe idea is that if non-replicated congress on mysql and replicated congress on postgres both pass, then the other combinations are unlikely to be problematic.04:09
ekcsif we have any issues we can certainly add back in.04:09
*** dklyle has quit IRC04:09
*** cloudran_ has joined #openstack-meeting04:09
ekcsseems like things have gotten much better since two weeks ago.04:09
ekcsFor example this patch submitted a hour ago is almost done checks:
akhil_jainyes, it seems working fine. zuul passed on my recent patches04:10
*** cloudrancher has quit IRC04:10
*** _pewp_ has quit IRC04:11
*** _pewp_ has joined #openstack-meeting04:11
ekcsok moving on then04:11
ekcs#topic tacker test in tempest04:11
*** openstack changes topic to "tacker test in tempest (Meeting topic: congressteammeeting)"04:11
ekcsakhil_jain: you wanna start us off on that topic? assuming you added it =)04:12
akhil_jainyes, i have one doubt about it04:12
*** toabctl has quit IRC04:13
akhil_jainfor testing tacker driver in tempest we need to create a vnfd that would require a sample template04:13
akhil_jainlike :
akhil_jainwhich is quiet too lengthy. so i need your suggestion on how should we use it or where we keep it04:14
*** toabctl has joined #openstack-meeting04:14
*** ramineni has joined #openstack-meeting04:15
ramineniekcs: hi04:15
ekcshmm ok help me understand the concern. is the concern that the template would be too resource intensive to deploy in CI? or that the template text is big?04:15
akhil_jainekcs: there will be more questions when i will start working on it, but for now this is my primary concern04:15
ekcshi ramineni ! welcome back!!04:15
ekcsakhil_jain: to clarify, is it resource or is it length of the template text?04:16
ramineniekcs: thanks :)04:16
akhil_jainNo, resourse I can minimize by lowering the requirement. but text i dont feel right to add in test file04:17
*** hongbin has quit IRC04:17
ekcsI’m looking through tacker repo a little bit to see if I can find how they do it.04:18
ekcsgenerally length of the file doesn’t really need to be a concern though IMO. There are ways to keep it organized.04:19
akhil_jaini was thinking of some samples directory or something04:20
akhil_jainor if its ok to add vnfd template in test file. i can proceed with that too04:21
ekcsPersonally I think to start with adding straight to test file is fine.04:22
akhil_jainok great, i can start with that04:23
ekcsThose python triple quoted strings can be helpful =)04:23
ekcsI’m having some trouble finding tacker test stuff….04:23
akhil_jaini will have to go through tacker. but maybe some functional test is there for same04:24
akhil_jaini will share once i find the same04:25
ekcsyea they run a funcitonal test… but I can’t seem to find the code for the test.04:25
ekcsthe config seems to be here:
ekcsbut I don’t understand it. seems like there isn’t enough information to configure the tests. probably cuz I don’t understand the non-legacy zuulv3 config.04:26
ekcswell anyway.04:27
ekcsI guess we should move on for now?04:27
akhil_jainyes,  we can continue later with more reserch04:28
ekcsfor later reference, this is some information about the functional test they run on devstack:
ekcs would have a lot of info but takes a while to dig through.04:30
ekcsok well moving on then.04:30
ekcs#topic patches or open discussion04:30
*** openstack changes topic to "patches or open discussion (Meeting topic: congressteammeeting)"04:30
ekcsI don’t have other topics. anything else we want to talk about today?04:31
ekcsand ramineni it’s great to have you back! It’s great to have your code reviews again =)04:31
ramineniekcs: :) still trying to catch up04:31
ramineniekcs: good to see that monasca webhook driver merged04:32
ekcsramineni: yes it was great akhil_jain and gmann pulled things together between congress and monasca and got things in rocky.04:33
ramineniekcs: ohok, that's great04:33
ramineniekcs: any etherpad for stein items?04:33
raminenitargeted items**04:34
ekcsoh I also want to mention that the tacker-monasca-congress work is pretty cool especially with the coordination between all the projects. I included it in my update to a TC member which may make it into to the upcoming openstack board meeting.04:35
ramineniekcs: +1 , that's really great :)04:37
ekcsramineni: no we didn’t set any special targets this cycle. but we still have the same backlog etherpad we can continue to update for stein:
ekcsas well as the blueprints on launchpad.04:38
ramineniekcs: ah, ok, sure04:39
ekcsit seemed like we all had a pretty solid idea of what we wanted to work on =)04:40
ekcsbut we can definitely have more discussions if desired.04:40
ekcsok anything else we want to talk about today? or should we end for now?04:42
ramineniekcs: nothing from my side04:42
akhil_jainnone from my side04:42
ekcsoh one last thing in case ramineni doesn’t know we moved to meeting every two weeks. which means next meeting is in two weeks. we can change again if it doesn’t work well.04:44
ekcsoh but in two weeks it’s the summit.04:44
ramineniekcs: ok , ya04:45
ramineniekcs: you would be in berlin?04:46
ekcsyes i’ll be in berlin.04:47
ekcswell let’s do this. I added a space in meeting topics to put down topics. if we have topics we want to talk about 11-09 we can call an additional meeting.04:47
ekcsotherwise we’ll meet after the summit.04:48
*** janki has joined #openstack-meeting04:48
*** iyamahat has joined #openstack-meeting04:48
ekcslet’s add any topics by 11-07 if we want to have a meeting to discuss on 11-09.04:48
ekcsdoes that work?04:49
akhil_jainok noted04:49
ekcsok let’s end meeting then. have a great weekend all!04:51
akhil_jainThanks and same to you :)04:51
ekcsok then bye akhil_jain. bye ramineni !04:52
*** openstack changes topic to "OpenStack Meetings ||"04:52
openstackMeeting ended Fri Nov  2 04:52:38 2018 UTC.  Information about MeetBot at . (v 0.1.4)04:52
openstackMinutes (text):
*** ekcs has quit IRC04:53
*** yamahata has joined #openstack-meeting05:07
*** apetrich has quit IRC06:27
*** tetsuro has joined #openstack-meeting06:39
*** ramineni has quit IRC06:42
*** apetrich has joined #openstack-meeting06:43
*** tetsuro has quit IRC06:48
*** ramineni has joined #openstack-meeting06:54
*** erlon has joined #openstack-meeting07:14
*** pcaruana has joined #openstack-meeting07:20
*** Douhet has quit IRC07:22
*** Douhet has joined #openstack-meeting07:22
*** Douhet has quit IRC07:33
*** ramineni has quit IRC07:37
*** Douhet has joined #openstack-meeting07:37
*** fanzhang has quit IRC07:40
*** fanzhang has joined #openstack-meeting07:40
*** armax has quit IRC07:43
*** ramineni has joined #openstack-meeting07:50
*** slaweq has joined #openstack-meeting08:17
*** ralonsoh has joined #openstack-meeting08:26
*** bauzas is now known as bauwser08:52
*** shrasool has joined #openstack-meeting09:11
*** erlon has quit IRC09:13
*** ssbarnea has joined #openstack-meeting09:16
*** ttsiouts has joined #openstack-meeting09:17
*** ramineni has quit IRC09:28
*** ramineni has joined #openstack-meeting09:41
*** e0ne has joined #openstack-meeting09:51
*** shrasool has quit IRC09:54
*** shrasool has joined #openstack-meeting10:01
*** jamesmcarthur has joined #openstack-meeting10:05
*** jamesmcarthur has quit IRC10:09
*** shrasool has quit IRC10:11
*** shrasool has joined #openstack-meeting10:14
*** ttsiouts has quit IRC10:16
*** yamamoto has quit IRC10:24
*** EmilienM is now known as EvilienM10:25
*** yamamoto has joined #openstack-meeting10:28
*** ttsiouts has joined #openstack-meeting10:32
*** ramineni has quit IRC10:41
*** stephenfin is now known as finucannot10:44
*** longkb has quit IRC10:50
*** tssurya has joined #openstack-meeting10:54
*** ramineni has joined #openstack-meeting10:55
*** shrasool has quit IRC10:59
*** electrofelix has joined #openstack-meeting11:00
*** shrasool has joined #openstack-meeting11:01
*** erlon has joined #openstack-meeting11:06
*** shrasool has quit IRC11:13
*** shrasool has joined #openstack-meeting11:16
*** ramineni has left #openstack-meeting11:20
*** lpetrut has joined #openstack-meeting11:32
*** yamamoto has quit IRC11:33
*** yamamoto has joined #openstack-meeting11:39
*** raildo has joined #openstack-meeting11:45
*** yamamoto has quit IRC11:48
*** shrasool has quit IRC12:02
*** shrasool has joined #openstack-meeting12:02
*** lpetrut has quit IRC12:13
*** jamesmcarthur has joined #openstack-meeting12:34
*** yamamoto has joined #openstack-meeting12:36
*** ttsiouts has quit IRC12:39
*** jamesmcarthur has quit IRC12:39
*** jamesmcarthur has joined #openstack-meeting12:45
*** yamamoto has quit IRC12:47
*** yamamoto has joined #openstack-meeting12:49
*** janki has quit IRC12:53
*** raildo has quit IRC12:53
*** janki has joined #openstack-meeting12:53
*** raildo has joined #openstack-meeting12:54
*** jaypipes is now known as leakypipes12:56
*** yamamoto has quit IRC12:56
*** bobh has joined #openstack-meeting12:59
*** dustins has joined #openstack-meeting13:00
*** jamesmcarthur has quit IRC13:04
*** yamamoto has joined #openstack-meeting13:08
*** yamamoto has quit IRC13:08
*** rbudden has joined #openstack-meeting13:08
*** yamamoto has joined #openstack-meeting13:08
*** yamamoto has quit IRC13:13
*** shrasool has quit IRC13:14
*** janki has quit IRC13:27
*** mriedem has joined #openstack-meeting13:28
*** ttsiouts has joined #openstack-meeting13:32
*** efried is now known as fried_rice13:35
*** lpetrut has joined #openstack-meeting13:42
*** cloudran_ has quit IRC13:45
*** cloudrancher has joined #openstack-meeting13:45
*** eharney has joined #openstack-meeting13:50
*** jamesmcarthur has joined #openstack-meeting13:55
*** njohnston has joined #openstack-meeting13:56
*** mlavalle has joined #openstack-meeting13:59
*** yamamoto has joined #openstack-meeting13:59
mlavalle#startmeeting neutron_drivers14:00
openstackMeeting started Fri Nov  2 14:00:18 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_drivers)"14:00
openstackThe meeting name has been set to 'neutron_drivers'14:00
mlavallelet's hold 1 minute for others to join14:01
*** Chenjie_ has joined #openstack-meeting14:02
mlavalle#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_drivers)"14:02
mlavalleNext week I will be travelling to the Berlin Summit and I don't know whether I will be able to facilitate this meeting or not14:03
mlavalleIn two weeks, I know I won't be able to attend because I will be flying back14:03
*** liuyulong_ has joined #openstack-meeting14:03
mlavalleslaweq: would you run the meeting next week?14:04
slaweqmlavalle: sure, I can14:04
*** awaugama has joined #openstack-meeting14:04
mlavallehow about the weekk after?14:04
slaweqif we will have quorum14:04
slaweqI can run it both weeks14:04
slaweqthat's fine for me14:04
mlavallewe can work together in the agenda14:04
mlavalleFor those in the US, please remember that starting next week, this meeting will be one earlier in your local time14:05
mlavallewe are falling back to Standard Time14:05
mlavalleLet's move on14:06
mlavalle#topic RFEs14:06
*** openstack changes topic to "RFEs (Meeting topic: neutron_drivers)"14:06
*** armax has joined #openstack-meeting14:06
mlavalleLast week liuyulong_ I think wanted to discuss this when we hit the end of the meeting:
openstackLaunchpad bug 1796824 in neutron "Port in some type of device_owner should not allow update IP address" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)14:07
mlavalleso let's start here14:07
hle21mlavalle: i would like community help to review 2 issues for any solutions later14:07
openstackLaunchpad bug 1800599 in neutron "[RFE]Neutron API server: unexpected behavior with multiple long live clients" [Undecided,New]14:08
liuyulong_Let's quota something from the LP bug: Some L3 ports can now be directly modify the IP address, but there are some type of device_owner, for instance network:router_centralized_snat, should not allow to change the IP address, otherwise it will make things really complicated.14:08
liuyulong_Why it is complicated, it's because the L3 agent side does not handle the 'network:router_centralized_snat' port IP change for dvr router. If try to allow the IP change for these type of ports, seems we need a lot of work to do, such as change the qr- or sg- device IP address, change the iptables rules, change the route rules etc. And IMO, such IP change for these port is not so much useful, and even it is sometimes not visible to the14:08
liuyulong_normal user.14:08
*** hongbin has joined #openstack-meeting14:09
*** ttsiouts_ has joined #openstack-meeting14:09
mlavallehle21: that RFE hasn't been triaged yet. I will go through it today and give my feedback. Please don't expect us to discuss it in this meeting, unless we have time left at the end14:09
hle21mlavalle: sure, thanks!14:10
mlavalleliuyulong_: right now, if we change those IP addresses, nothing really happens in the data plane, right?14:11
*** rfolco is now known as rfolco|off14:11
liuyulong_Yes, but except router public gateway port.14:12
*** ttsiouts has quit IRC14:12
liuyulong_  network:router_centralized_snat14:12
liuyulong_  network:router_ha_interface14:12
liuyulong_  network:router_interface14:12
liuyulong_  network:router_interface_distributed14:12
liuyulong_These router related port types have nothing happens in L3 agent side.14:13
*** dansmith is now known as SteelyDan14:13
mlavalleliuyulong_: so the proposed change wouldn't disallow changing the ip address for public gateway port, right?14:13
liuyulong_Yes, network:router_gateway will still be allowed.14:13
haleybsorry i'm late14:15
mlavalleI don't think there are many users out there changing the IP address of these port owners. Otherwise, we would have already heard from them14:15
slaweqI agree mlavalle but still I think that change this and give user proper feedback on API level will be good14:16
mlavallehaving said that, as long as the change is discoverable, it doesn seem to hurt14:16
liuyulong_Yes, but it can change now. We should disallow it as early as possile.14:17
mlavallenot executing an action silently is not a correct thing, as slaweq points out14:17
*** tssurya has quit IRC14:18
mlavallewhat do others think?14:19
liuyulong_And it has some bad side effect, such as IP multipoint installation14:19
*** shrasool has joined #openstack-meeting14:20
liuyulong_Device IP never changed in L3 agent side, but neutron DB think it is free, then a new port uses it.14:20
mlavallethat's true14:20
haleybi think it's fine.  if at some point someone wants to do all the hard, complicated work they can14:20
mlavalleyeah, if we find the use case for it, then we can do the hard work14:21
slaweqI agree14:22
liuyulong_Yep, the current implementation has a easy way to override it.14:22
liuyulong_Thanks to Manjeet Singh Bhatia14:22
mlavalleany concerns to approve this?14:22
liuyulong_The neutron built-in l3 plugin supply the port types:
liuyulong_Any subprojects and easily override it.14:23
liuyulong_Any subprojects can easily override it14:24
liuyulong_Just do not use the built-in l3 plugin or override the port type list there, yamamoto14:25
*** ttsiouts_ has quit IRC14:25
hongbinbut using the same api extension?14:25
*** artom has quit IRC14:26
yamamotoliuyulong_: it would work for monolithic plugins but not for drivers like
*** lpetrut has quit IRC14:26
hongbinor if the port type list is override, it should present a different api extension?14:27
liuyulong_yamamoto, such project will not meet these port types, right?14:28
yamamotowhat do you mean by "meet"?14:28
liuyulong_I'm not familar to network_odl, will it have some port type related to DVR? for instance, network:router_centralized_snat?14:29
yamamotoi guess dvr specific ones are ok. but your list includes network:router_interface14:30
*** lpetrut has joined #openstack-meeting14:30
liuyulong_hongbin, this is about update port IP, it's L2 API, but port belongs to L3, and L3 do not want change the IP. So extension seems not so much needed.14:31
*** artom has joined #openstack-meeting14:31
hongbini see there is an extension 'L3_port_ip_change_not_allowed'14:32
liuyulong_yamamoto, OK, that can be removed from the list, please leave a comment here:
hongbinhowever, i heard that other plugin can override the port type list but still using this extension?14:33
liuyulong_hongbin, slaweq suggests me to add a shim extension to notify user that there some L3 behavior change.14:33
hongbinliuyulong_: ack14:34
slaweqI just wanted to make this new behaviour to be discoverable14:35
mlavalleyeah, that is important14:35
liuyulong_slaweq, agree, thanks14:35
*** ttsiouts has joined #openstack-meeting14:35
hongbinyes, then if other plugin can override what kind of port should be disallowed to change ip address, but present the same api extension, this behavior is still discoveralble?14:36
liuyulong_hongbin, yes, it is.14:36
*** lpetrut has quit IRC14:37
mlavalleit probably is, as long as that plugin documents properly the list of ports14:37
mlavalleand BTW, if we implement this, we should do the same14:38
liuyulong_The IP change detection code is right now code directly to the L2 IPAM.14:38
liuyulong_OK, DOC work added to my list.14:38
mlavalleThat would include a section in devref, indicating how other plugins can override the list14:39
hongbinmlavalle: i think the extension itself is the best place to document the list of port types it is going to support, but push it down to the plugin is also fine with me14:40
mlavallehongbin: you make a good point. we can disucss this detail in gerrit. as long as it is properly documented14:40
mlavalleyamamoto: are you ok now with this?14:41
hongbinmlavalle: ack14:41
liuyulong_hongbin, good point, but like I said in the patch inline comments, it is an requirement from L3 to L2: we do not want these port change IP, we can give the port types.14:41
hongbinliuyulong_: ok14:42
yamamotoas far as its scope is only device_owner types which are specific to the reference implementation, i'm ok with it14:42
mlavalleany other concerns?14:42
*** akhil_jain has left #openstack-meeting14:43
mlavalleok, we'll approve this14:43
mlavalleyamamoto: I'll include your latest remark in the approval comment in the RFE14:44
*** armstrong has joined #openstack-meeting14:44
yamamotomlavalle: thank you14:44
*** davidsha_ has joined #openstack-meeting14:44
liuyulong_Many thanks to everyone.14:45
mlavalleliuyulong_: thanks for your submission14:46
openstackLaunchpad bug 1796824 in neutron "Port in some type of device_owner should not allow update IP address" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)14:46
yamamotoliuyulong_: FYI, at least midonet allows updates of ips on router_interface ports. i don't think it's well tested though. :-)14:47
yamamotomlavalle: looks fine14:47
liuyulong_yamamoto, thanks, I'll do some code search.14:47
mlavalleliuyulong_: I have another RFE in the agenda from you:
openstackLaunchpad bug 1796925 in neutron "[RFE] port forwarding floating IP QoS" [Wishlist,New] - Assigned to LIU Yulong (dragon889)14:48
mlavallewe will probably not have time to discuss it today14:49
mlavallecan we move it to next week?14:49
liuyulong_OK, I'm fine with it.14:49
mlavallecool, thanks :-)14:49
mlavalleso let's move one14:50
mlavalle#topic On demand agenda14:50
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_drivers)"14:50
mlavalleralonsoh brings up this question:14:50
mlavalleShould we add a new extension just to modify an integer parameter validation? Reduce the port range from 0-64K to 1-64K. This change is trivial and both APIs (new/old) can coexist without any clash. Review:
ralonsohliuyulong_, you are just changing the validation of this parameter, reducing the valid range14:52
hongbini would vote for no14:52
mlavalleat first glance, from a pragmatical point of view, I agree with ralonsoh14:52
ralonsohwe have plenty of extensions, too many14:52
liuyulong_Yes, I just do not want it too, since patch set 1 is done it in the simple way14:52
liuyulong_But how to apply this change to the master neutron is the main problem, since neutron does not use the neutron-lib master branch yet.14:53
liuyulong_So copy this changed extension file to neutron repo as a new temp work around? That is totally same to current change.14:53
liuyulong_Quoted from the gerrit ^^^14:53
mlavalleand from a pragmatical point of view, port forwarding is such a young feature, that I don't think we are going to affect many users out there14:53
slaweqI agree that it may be a bit too much but from the other side, it's API change - if user now created PF with port=0 and it was fine from API PoV, then it will not raise exception14:53
slaweq*now raise exception14:54
njohnstonpossibility for an upgrade check, slaweq?14:54
mlavallestrictly speaking, that's true14:54
yamamotowhat's the current behaviour for port=0?14:54
slaweqnjohnston: it's not related to upgrade check IMO14:54
mlavallebut how many users are there in this situation, reallistically, since we released this a copuple of months ago14:54
slawequpgrade check is tool for operators, and this is user's API change14:54
liuyulong_ this simple change is also my favorite, : )14:55
hongbinslaweq:  if passing port=0 is considered a bug, then raise an exception is ok becuase it is not considered as api change14:55
mlavallehongbin: right, I think that is the correct way to see the issue14:56
liuyulong_hongbin, yes, for now it is 500 error to user14:56
mlavalleas a bug that we are now fixing14:56
slaweqif it raises exception (500 for example) now then it's IMO perfectly fine to fix it without new extension14:56
slaweqI thought that it's now returning 200 OK instead14:56
mlavalleand let's include a fixes section in the release notes14:57
mlavalledocumenting the change14:57
mlavallewe all agree?14:57
mlavalleok, cool for the overwhelming consensus.... LOL14:58
slaweq+2 :)14:58
mlavalleralonsoh: thanks for bringing this up14:58
mlavalleThe next one I will leave for next meeting, ok slaweq ?14:59
mlavalleThanks everybody14:59
slaweqhave a great weekend :)14:59
mlavallebelieve or not, I will miss you the next two weeks14:59
njohnstonsafe travels, all those bound for Berlin!14:59
mlavalleeach one of you: slaweq, haleyb, yamamoto, njohnston, ralonsoh, liuyulong_ :-)14:59
*** openstack changes topic to "OpenStack Meetings ||"15:00
openstackMeeting ended Fri Nov  2 15:00:03 2018 UTC.  Information about MeetBot at . (v 0.1.4)15:00
slaweqwe will miss You too mlavalle :)15:00
openstackMinutes (text):
yamamotogood night15:00
slaweqgood night yamamoto15:00
*** Chenjie_ has quit IRC15:00
*** diablo_rojo has joined #openstack-meeting15:02
smcginnis#startmeeting releaseteam15:03
openstackMeeting started Fri Nov  2 15:03:02 2018 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: releaseteam)"15:03
openstackThe meeting name has been set to 'releaseteam'15:03
smcginnisSorry for the delay.15:03
smcginnisCurrently around line 12515:03
*** ttsiouts has quit IRC15:04
smcginnis#topic Should we allow cycle-with-rc final releases without RC first15:04
*** openstack changes topic to "Should we allow cycle-with-rc final releases without RC first (Meeting topic: releaseteam)"15:04
*** gagehugo has left #openstack-meeting15:04
smcginnisPatch where this was noticed. ^15:05
*** ttsiouts has joined #openstack-meeting15:05
smcginnisI think we talked about it a little in channel.15:05
ttxyes, I fear it's easy to miss on human review15:05
smcginnisdhellmann: I think you confirmed my assumption that we don't enforce that in case we need to do something unusual.15:06
smcginnisttx: I agree. I wonder how likely it would be that we would a) want, and b) need to release something without at least a cursory RC first.15:06
dhellmannsmcginnis : I'm assuming that, too. I may just have been lazy when I wrote the validation15:06
ttxAlso I'm not sure how we'd fix it if we ended up letting one pass15:06
dhellmannif we do have an "emergency" we can easily change the release model at the same time15:06
*** liuyulong_ has quit IRC15:07
smcginnisYeah, seems to be safer if we don't rely on human eyes to notice that.15:07
dhellmannso I think if we're concerned about it we can add the validation15:07
*** liuyulong has joined #openstack-meeting15:07
smcginnisttx: Did you want to take that action?15:07
ttxunless it's extra impossible to test for15:08
ttxI can take the action, unless we want it really soon15:08
smcginnisEh, we've gone this long. I wouldn't consider it a high priority item.15:08
fungiwhat's the risk? that neutron almost tagged 14.0.0 when they didn't mean to release this early in the cycle?15:08
*** ssbarnea has quit IRC15:08
smcginnisYeah. Then if they wanted to make any significant changes for the rest of the cycle they would need to bump another major version in one cycle.15:09
ttxat the very least it would be a violation of their release model15:09
dhellmannfungi : yes, basically that someone would say they're going to publish release candidates and then they don't15:09
smcginnisWhich I suppose is OK, but a little different than normal.15:09
* ttx creates SB story15:09
smcginnis#action ttx to follow up with adding RC check to validation15:10
ttxI think it's OK, IF they change to cycle-with-intermediary on the same request15:10
*** ssbarnea has joined #openstack-meeting15:10
smcginnisThat would be OK since they would then still be following the declared release model.15:11
smcginnis#topic Summit prep15:11
*** openstack changes topic to "Summit prep (Meeting topic: releaseteam)"15:11
smcginnisI have slides put together for the onboarding.15:11
* smcginnis goes to look that up...15:12
dhellmannwe had a slide deck in git somewhere, didn't we? did you update that or start over?15:12
smcginnisI will likely add some more notes and tweaks there.15:12
ttx#link!/story/2004239 for the previous topic15:12
smcginnisYeah, it was in the retired release-tools repo. :/15:12
dhellmannI can be present in the room to help answer questions15:12
dhellmannoh, bummer15:12
ttxI have a conflict, last time I checked... when is it?15:13
smcginnisThat's OK, it was a useful exercise putting together a new one.15:13
smcginnisttx: We'll just tell attendees to direct all future questions to you.15:13
ttxsounds fair... wait NO15:13
*** munimeha1 has joined #openstack-meeting15:14
diablo_rojoI'm planning on being there to learn!15:14
dhellmannoh, good, we can tell everyone to ask diablo_rojo instead15:14
diablo_rojoAssuming I have no conflicts :/ Havent checked that yet.15:14
ttxah yes, I'll stuck in a "press conference"15:15
diablo_rojodhellmann, I'm there to learn not to teach :)15:15
smcginnisAny suggestions for the presentation, just let me know.15:15
dhellmanndiablo_rojo : the best way *to* learn is to teach!15:15
smcginnisI don't believe we have any other release related sessions there.15:15
ttxdhellmann: nice try15:15
diablo_rojodhellmann, touche15:15
smcginnisAnything else we need to prep for?15:15
ttxany session worthy of our divine presence?15:16
smcginnisI expect to spend my time walking from session to session and not actually getting there due to hallways conversations like in Vancouver.15:16
ttxdhellmann: if you want to see how that company used reno, come attend
dhellmannttx: yes, I spotted that one after you mentioned their name15:17
dhellmannit's definitely on my schedule15:17
smcginnisOh, intersting.15:17
dhellmannI haven't really looked through the other presentations closely, yet15:17
dhellmannI have a bunch of forum sessions selected15:17
ttxok, well, if you see something we (relmgt) should probably attend, let team know15:18
smcginnisSame here, I focused on forum sessions and will fill in with summit sessions where I can.15:18
fungiwill do15:18
ttxalthough my schedule starts to be pretty full15:18
armstrong@dhellmann: I am interested in learning Reno too15:19
smcginnis#topic Next two meetings15:19
*** openstack changes topic to "Next two meetings (Meeting topic: releaseteam)"15:19
smcginnisWith travel starting next week and then the Summit, I think skipping is in order.15:19
dhellmannarmstrong : I'm happy to help!15:19
dhellmannsmcginnis : ++15:19
smcginnis#info No meeting the next two weeks due to Summit travel and event15:20
armstrong@smcginnis : are you given any special training during the summit at Berlin?15:20
smcginnisWe have a release team onboarding session. That's the only release management specific thing.15:21
armstrong ok15:21
smcginnisdiablo_rojo and others will be part of a general new contributor session that is always useful too.15:21
smcginnis#topic Open discussion15:21
*** openstack changes topic to "Open discussion (Meeting topic: releaseteam)"15:21
smcginnisThat happens just prior to the actual Summit.15:22
armstrongsuper interesting15:22
smcginnisarmstrong: Are you going to Berlin?15:22
armstronglet me save it on my agenda right now15:22
armstrongYes I am15:22
diablo_rojoarmstrong, its Upstream Institute- the day and a half long training you've already come to a few times ;)15:23
diablo_rojoI see you RSVPed again though :)15:23
armstrong @diablo_rojo:OK i see15:23
smcginnisI've found it useful mentoring. Still learning things from the different questions folks ask.15:24
smcginnisAny other meeting items to discuss?15:24
dhellmanndid we end up with any b1 tags?15:25
armstrongI just got one of two papers I was working on accepted for SANER 2019, but I have minor corrections to submit final paper15:25
* ttx looks up current reviews15:25
armstrongOpenStack release team was my case study15:26
smcginnisarmstrong: Oh, interesting. I would be interested in seeing that.15:26
smcginnisdhellmann: We had searchlight.15:26
dhellmannit looks like I should update list-deliverables to support that sort of query15:26
*** gyee has joined #openstack-meeting15:26
dhellmannso far it just lists missing things15:26
dhellmannI see horizon and searchlight with grep though15:27
smcginnisOh yeah, horizon too since they are still kind of a library for their plugins.15:27
dhellmannI wonder how they'll get a beta library to install, but ok15:28
smcginnisarmstrong: Do you know if the sessions from SANER are recorded and publicly available?15:28
smcginnisdhellmann: I try to remain ignorant with all of that. :)15:28
dhellmannsmcginnis : yeah, I'm worried they'll work around the constraints system somehow15:29
ttxany reason to hold on ?15:29
armstrong@smcginnis: Yes, its recorded but I don't know if its available for the public since its an IEEE event15:29
armstrongbut in any case, I will record  my talk15:29
dhellmannttx: I don't think so.15:29
ttxpleas w+1 then15:29
smcginnisttx: Approved15:29
smcginnis is also ready.15:30
ttxdhellmann: too15:30
smcginnisI had it -2 so I think it didn't show up in the list.15:30
dhellmannI'll take a look at those after the meeting15:31
ttxsmcginnis: that one is a library on a Friday, we usually don't approve those15:31
smcginnisAlthough we've relaxed that a bit since there is the requirements checkpoint to go through too.15:31
ttxok, if nothing else, I would not mind getting 30 minutes extra time on this day15:31
smcginnisOK, thanks all!15:32
fungithanks smcginnis!15:32
ttxthanks smcginnis !15:32
diablo_rojothanks smcginnis!15:32
*** openstack changes topic to "OpenStack Meetings ||"15:32
openstackMeeting ended Fri Nov  2 15:32:30 2018 UTC.  Information about MeetBot at . (v 0.1.4)15:32
openstackMinutes (text):
*** Swami has joined #openstack-meeting15:34
*** eharney has quit IRC15:36
*** eharney has joined #openstack-meeting15:51
*** bnemec is now known as beekneemech16:00
*** cloudrancher has quit IRC16:01
*** cloudrancher has joined #openstack-meeting16:02
*** aagate has quit IRC16:03
*** yamamoto has quit IRC16:03
*** yamamoto has joined #openstack-meeting16:05
*** yamamoto has quit IRC16:05
*** yamamoto has joined #openstack-meeting16:05
*** artom has quit IRC16:07
*** artom has joined #openstack-meeting16:08
*** yamamoto has quit IRC16:10
*** armstrong has quit IRC16:11
*** artom is now known as temka16:14
*** imacdonn has quit IRC16:15
*** imacdonn has joined #openstack-meeting16:15
*** cloudrancher has quit IRC16:16
*** pcaruana has quit IRC16:17
*** cloudrancher has joined #openstack-meeting16:17
*** fried_rice is now known as fried_rolls16:30
*** shrasool has quit IRC16:33
*** e0ne has quit IRC16:33
*** yamahata has quit IRC16:34
*** iyamahat has quit IRC16:34
*** ttsiouts has quit IRC16:38
*** ttsiouts has joined #openstack-meeting16:39
*** ttsiouts has quit IRC16:43
*** jiaopengju has quit IRC16:44
*** jiaopengju has joined #openstack-meeting16:45
*** iyamahat has joined #openstack-meeting16:49
*** iyamahat_ has joined #openstack-meeting16:52
*** iyamahat has quit IRC16:56
*** davidsha_ has quit IRC16:58
*** yamamoto has joined #openstack-meeting16:59
*** Swami has quit IRC17:01
*** yamamoto has quit IRC17:07
*** yamahata has joined #openstack-meeting17:09
*** ekcs has joined #openstack-meeting17:25
*** shrasool has joined #openstack-meeting17:28
*** cloudrancher has quit IRC17:29
*** cloudrancher has joined #openstack-meeting17:30
*** mriedem has quit IRC17:30
*** mriedem has joined #openstack-meeting17:35
*** cloudrancher has quit IRC17:35
*** ralonsoh has quit IRC17:35
*** cloudrancher has joined #openstack-meeting17:35
*** cloudrancher has quit IRC17:37
*** cloudrancher has joined #openstack-meeting17:37
*** cloudrancher has quit IRC17:39
*** cloudrancher has joined #openstack-meeting17:39
*** cloudrancher has quit IRC17:41
*** cloudrancher has joined #openstack-meeting17:42
*** rbudden has quit IRC17:50
*** rbudden has joined #openstack-meeting17:55
*** fanzhang has quit IRC18:01
*** cloudrancher has quit IRC18:11
*** cloudrancher has joined #openstack-meeting18:12
*** jamesmcarthur has quit IRC18:23
*** electrofelix has quit IRC18:24
*** shrasool has quit IRC18:27
*** pcaruana has joined #openstack-meeting18:27
*** e0ne has joined #openstack-meeting18:34
*** shrasool has joined #openstack-meeting18:42
*** fried_rolls is now known as fried_rice18:46
*** jamesmcarthur has joined #openstack-meeting18:47
*** mlavalle has left #openstack-meeting18:52
*** EvilienM is now known as EmilienM18:53
*** bobh has quit IRC19:04
*** e0ne has quit IRC19:05
*** pcaruana has quit IRC19:08
*** jamesmcarthur has quit IRC19:08
*** apetrich has quit IRC19:24
*** eharney has quit IRC19:24
*** bobh has joined #openstack-meeting19:25
*** shrasool has quit IRC19:27
*** jamesmcarthur has joined #openstack-meeting19:28
*** shrasool has joined #openstack-meeting19:32
*** cloudrancher has quit IRC19:32
*** cloudrancher has joined #openstack-meeting19:33
*** lpetrut has joined #openstack-meeting19:34
*** finucannot is now known as stephenfin19:35
*** apetrich has joined #openstack-meeting19:38
*** shrasool has quit IRC19:41
*** jamesmcarthur has quit IRC20:07
*** eharney has joined #openstack-meeting20:15
*** Swami has joined #openstack-meeting20:27
*** jamesmcarthur has joined #openstack-meeting20:28
*** lpetrut has quit IRC20:35
*** eharney has quit IRC20:46
*** bobh has quit IRC20:59
*** bobh has joined #openstack-meeting21:03
*** jamesmcarthur has quit IRC21:04
*** yamamoto has joined #openstack-meeting21:05
*** jamesmcarthur has joined #openstack-meeting21:05
*** jamesmcarthur has quit IRC21:08
*** bobh has quit IRC21:09
*** yamamoto has quit IRC21:09
*** jamesmcarthur has joined #openstack-meeting21:13
*** njohnston has quit IRC21:16
*** awaugama has quit IRC21:16
*** njohnston has joined #openstack-meeting21:17
*** raildo has quit IRC21:19
*** dustins has quit IRC21:22
*** shrasool has joined #openstack-meeting21:23
*** rbudden has quit IRC21:28
*** hle21 has quit IRC21:34
*** ekcs has quit IRC21:38
*** ttsiouts has joined #openstack-meeting21:38
*** jamesmcarthur has quit IRC21:38
*** jamesmcarthur has joined #openstack-meeting21:42
*** ttsiouts has quit IRC21:43
*** jamesmcarthur has quit IRC21:47
*** jamesmcarthur has joined #openstack-meeting21:48
*** jamesmcarthur has quit IRC21:52
*** ttsiouts has joined #openstack-meeting21:53
*** rbudden has joined #openstack-meeting22:04
*** jamesmcarthur has joined #openstack-meeting22:06
*** munimeha1 has quit IRC22:06
*** jamesmcarthur has quit IRC22:10
*** rbudden has quit IRC22:12
*** rossella_s has quit IRC22:21
*** shrasool has quit IRC22:24
*** shrasool has joined #openstack-meeting22:27
*** shrasool has quit IRC22:28
*** erlon has quit IRC22:43
*** bobh has joined #openstack-meeting22:44
*** jamesmcarthur has joined #openstack-meeting22:47
*** bobh has quit IRC22:50
*** jamesmcarthur has quit IRC22:51
*** cloudrancher has quit IRC22:57
*** cloudrancher has joined #openstack-meeting22:57
*** ianychoi has quit IRC23:02
*** ttsiouts has quit IRC23:17
*** mriedem has quit IRC23:18
*** shrasool has joined #openstack-meeting23:19
*** markvoelker has joined #openstack-meeting23:41
*** hongbin has quit IRC23:44
*** Swami has quit IRC23:44
*** markvoelker has quit IRC23:46
*** gyee has quit IRC23:48
*** ianychoi has joined #openstack-meeting23:55

Generated by 2.15.3 by Marius Gedminas - find it at!