Thursday, 2016-06-02

*** Swami has quit IRC00:11
*** atuvenie_ has joined #openstack-meeting-300:12
*** amotoki has joined #openstack-meeting-300:12
*** atuvenie_ has quit IRC00:16
*** tsv_ has quit IRC00:16
*** sdake_ is now known as sdake00:19
*** fitoduarte has quit IRC00:20
*** ivar-lazzaro has joined #openstack-meeting-300:27
*** stanchan has quit IRC00:30
*** VW has joined #openstack-meeting-300:31
*** amotoki has quit IRC00:32
*** mickeys has quit IRC00:33
*** mickeys has joined #openstack-meeting-300:34
*** VW has quit IRC00:36
*** mickeys has quit IRC00:38
*** mickeys has joined #openstack-meeting-300:38
*** hoangcx has joined #openstack-meeting-300:41
*** zz_dimtruck is now known as dimtruck00:45
*** kenji-i_ has joined #openstack-meeting-300:51
*** bpokorny_ has joined #openstack-meeting-300:51
*** kenji-i has quit IRC00:54
*** bpokorny_ has quit IRC00:54
*** bpokorny has quit IRC00:56
*** mickeys has quit IRC00:56
*** mickeys has joined #openstack-meeting-300:57
*** mickeys has quit IRC00:57
*** toddjohn has joined #openstack-meeting-300:57
*** mickeys has joined #openstack-meeting-300:57
*** toddjohn has quit IRC01:02
*** bryan_att has quit IRC01:03
*** mickeys has quit IRC01:03
*** pvaneck has quit IRC01:04
*** zhurong has joined #openstack-meeting-301:05
*** mickeys has joined #openstack-meeting-301:08
*** woodster_ has quit IRC01:08
*** caowei has joined #openstack-meeting-301:10
*** Sukhdev has quit IRC01:13
*** kzaitsev_mb has joined #openstack-meeting-301:13
*** Sukhdev has joined #openstack-meeting-301:14
*** amotoki has joined #openstack-meeting-301:15
*** Sukhdev has quit IRC01:19
*** fitoduarte has joined #openstack-meeting-301:20
*** mickeys has quit IRC01:21
*** mickeys has joined #openstack-meeting-301:21
*** amotoki_ has joined #openstack-meeting-301:24
*** mickeys_ has joined #openstack-meeting-301:24
*** shwetaap has joined #openstack-meeting-301:25
*** mickeys has quit IRC01:26
*** amotoki has quit IRC01:26
*** mickeys_ has quit IRC01:28
*** ivar-lazzaro has quit IRC01:29
*** Niham has joined #openstack-meeting-301:31
*** Niham has quit IRC01:32
*** Niham has joined #openstack-meeting-301:33
*** stanzgy has joined #openstack-meeting-301:33
*** amit213 has joined #openstack-meeting-301:39
*** amit213 has quit IRC01:41
*** caowei has quit IRC01:41
*** caowei has joined #openstack-meeting-301:42
*** amit213 has joined #openstack-meeting-301:44
*** caowei has quit IRC01:46
*** caowei has joined #openstack-meeting-301:46
*** sdake has quit IRC01:49
*** caowei has quit IRC01:50
*** s3wong has quit IRC01:54
*** mickeys has joined #openstack-meeting-301:54
*** banix has quit IRC01:55
*** mickeys has quit IRC01:58
*** kzaitsev_mb has quit IRC02:01
*** vishwanathj has joined #openstack-meeting-302:03
*** banix has joined #openstack-meeting-302:09
*** Niham has quit IRC02:10
*** yamahata has quit IRC02:11
*** iyamahat has quit IRC02:14
*** sdake has joined #openstack-meeting-302:16
*** rtheis_ has quit IRC02:17
*** sdake has quit IRC02:18
*** shwetaap has quit IRC02:18
*** shwetaap has joined #openstack-meeting-302:32
*** yujunz has joined #openstack-meeting-302:35
*** pt_15 has quit IRC02:36
*** galstrom is now known as galstrom_zzz02:38
*** VW has joined #openstack-meeting-302:38
*** VW has quit IRC02:43
*** toddjohn has joined #openstack-meeting-302:45
*** toddjohn has quit IRC02:50
*** claudiub has quit IRC02:52
*** kzaitsev_mb has joined #openstack-meeting-302:57
*** rbak has quit IRC02:59
*** rbak has joined #openstack-meeting-302:59
*** vishwanathj has quit IRC03:01
*** julim has joined #openstack-meeting-303:05
*** yamamoto_ has joined #openstack-meeting-303:10
*** yamahata has joined #openstack-meeting-303:28
*** shwetaap has quit IRC03:29
*** kzaitsev_mb has quit IRC03:35
*** julim has quit IRC03:36
*** dimtruck is now known as zz_dimtruck03:40
*** yamamoto_ has quit IRC03:42
*** yujunz has quit IRC03:46
*** Sukhdev has joined #openstack-meeting-303:48
*** shwetaap has joined #openstack-meeting-303:49
*** zhurong has quit IRC04:03
*** zhurong has joined #openstack-meeting-304:04
*** Niham has joined #openstack-meeting-304:09
*** Niham has quit IRC04:10
*** Niham has joined #openstack-meeting-304:11
*** yushiro has joined #openstack-meeting-304:12
*** yushiro has left #openstack-meeting-304:13
*** banix has quit IRC04:17
*** dmellado has quit IRC04:24
*** xiaohhui has quit IRC04:24
*** shinya_kwbt has quit IRC04:24
*** irenab has quit IRC04:24
*** shinya_kwbt has joined #openstack-meeting-304:25
*** xiaohhui has joined #openstack-meeting-304:25
*** dmellado has joined #openstack-meeting-304:27
*** yamamoto_ has joined #openstack-meeting-304:29
*** lipt has joined #openstack-meeting-304:30
*** kzaitsev_mb has joined #openstack-meeting-304:31
*** kzaitsev_mb has quit IRC04:36
*** Sukhdev has quit IRC04:48
*** mrmartin has joined #openstack-meeting-304:48
*** pgadiya has joined #openstack-meeting-304:55
*** mickeys has joined #openstack-meeting-304:55
*** ujuc has joined #openstack-meeting-304:56
*** Niham has quit IRC04:57
*** iyamahat has joined #openstack-meeting-304:59
*** mickeys has quit IRC05:03
*** mickeys has joined #openstack-meeting-305:03
*** Niham has joined #openstack-meeting-305:06
*** mickeys has quit IRC05:08
*** shwetaap has quit IRC05:10
*** jtomasek has joined #openstack-meeting-305:16
*** anilvenkata has joined #openstack-meeting-305:17
*** amotoki_ is now known as amotoki05:19
*** SarathMekala has joined #openstack-meeting-305:24
*** hdaniel has joined #openstack-meeting-305:30
*** lpetrut has joined #openstack-meeting-305:32
*** tfukushima has joined #openstack-meeting-305:41
*** tfukushima has quit IRC05:41
*** tfukushima has joined #openstack-meeting-305:41
*** ajnouri has quit IRC05:42
*** Niham has quit IRC05:46
*** Poornima has joined #openstack-meeting-305:46
*** mrmartin has quit IRC05:47
*** numans has joined #openstack-meeting-305:55
*** iyamahat has quit IRC06:14
*** zhurong has quit IRC06:16
*** zhurong has joined #openstack-meeting-306:19
*** hdaniel has quit IRC06:22
*** ajnouri has joined #openstack-meeting-306:27
*** andreas_s has joined #openstack-meeting-306:30
*** kzaitsev_mb has joined #openstack-meeting-306:32
*** kzaitsev_mb has quit IRC06:38
*** sarathcm_ has joined #openstack-meeting-306:38
*** sarathcm_ has quit IRC06:38
*** lpetrut has quit IRC06:39
*** numans has quit IRC06:44
*** coolsvap_ has joined #openstack-meeting-306:44
*** nkrinner_afk is now known as nkrinner06:46
*** yushiro1 has joined #openstack-meeting-306:48
*** yushiro1 has left #openstack-meeting-306:48
*** yushiro has joined #openstack-meeting-306:49
*** yushiro has left #openstack-meeting-306:49
*** Niham has joined #openstack-meeting-306:51
*** numans has joined #openstack-meeting-306:52
*** Niham has quit IRC06:57
*** sdake has joined #openstack-meeting-306:57
*** jlanoux has joined #openstack-meeting-306:57
*** lpetrut has joined #openstack-meeting-306:58
*** hoangcx has quit IRC07:00
*** hoangcx has joined #openstack-meeting-307:01
*** hdaniel has joined #openstack-meeting-307:11
*** coolsvap_ has quit IRC07:13
*** vishwanathj has joined #openstack-meeting-307:15
*** coolsvap_ has joined #openstack-meeting-307:15
*** vishwana_ has joined #openstack-meeting-307:15
*** ajnouri has quit IRC07:17
*** vishwanathj has quit IRC07:19
*** nkrinner has quit IRC07:25
*** jlanoux has quit IRC07:25
*** vishwana_ is now known as vishwanathj07:26
*** nkrinner has joined #openstack-meeting-307:27
*** lpetrut has quit IRC07:31
*** vishwanathj has quit IRC07:34
*** kzaitsev_mb has joined #openstack-meeting-307:34
*** pavel_bondar has quit IRC07:35
*** jtomasek_ has joined #openstack-meeting-307:37
*** kzaitsev_mb has quit IRC07:38
*** sdake has quit IRC07:39
*** lipt has quit IRC07:41
*** jtomasek_ has quit IRC07:44
*** lipt has joined #openstack-meeting-307:46
*** lipt has quit IRC07:46
*** jlanoux has joined #openstack-meeting-307:49
*** kzaitsev_mb has joined #openstack-meeting-307:51
*** lipt has joined #openstack-meeting-307:51
*** lipt has quit IRC07:51
*** lipt has joined #openstack-meeting-307:51
*** lipt has quit IRC07:51
*** dedery has joined #openstack-meeting-307:53
*** lipt has joined #openstack-meeting-307:56
*** lipt has quit IRC07:56
*** hoangcx has quit IRC07:57
*** matrohon has joined #openstack-meeting-307:59
*** coolsvap_ has quit IRC07:59
*** hoangcx has joined #openstack-meeting-308:00
*** claudiub has joined #openstack-meeting-308:02
*** lipt has joined #openstack-meeting-308:04
*** mbound has joined #openstack-meeting-308:08
*** vishwanathj has joined #openstack-meeting-308:14
*** dedery has quit IRC08:15
*** lipt has joined #openstack-meeting-308:15
*** lipt has quit IRC08:15
*** dedery has joined #openstack-meeting-308:16
*** Niham has joined #openstack-meeting-308:19
*** lipt has joined #openstack-meeting-308:19
*** lipt has quit IRC08:19
*** yujunz has joined #openstack-meeting-308:19
*** lipt has joined #openstack-meeting-308:20
*** lipt has quit IRC08:20
*** lipt has joined #openstack-meeting-308:21
*** lipt has quit IRC08:21
*** ihrachys has joined #openstack-meeting-308:21
*** lipt has joined #openstack-meeting-308:22
*** lipt has quit IRC08:22
*** mrmartin has joined #openstack-meeting-308:28
*** markvoelker has quit IRC08:29
*** markvoelker has joined #openstack-meeting-308:30
*** mrmartin has quit IRC08:33
*** fwdit has joined #openstack-meeting-308:39
*** mrmartin has joined #openstack-meeting-308:43
*** dedery_ has joined #openstack-meeting-308:44
*** dedery has quit IRC08:48
*** dedery_ has quit IRC08:49
*** mbound has quit IRC08:49
*** lpetrut has joined #openstack-meeting-308:53
*** yujunz has quit IRC09:03
*** irenab has joined #openstack-meeting-309:06
*** dtardivel has joined #openstack-meeting-309:08
*** irenab has quit IRC09:12
*** dedery has joined #openstack-meeting-309:13
*** sdake has joined #openstack-meeting-309:13
*** yamahata has quit IRC09:14
*** SarathMekala has quit IRC09:24
*** SarathMekala has joined #openstack-meeting-309:27
*** mrmartin has quit IRC09:35
*** kzaitsev_mb has quit IRC09:37
*** lpetrut has quit IRC09:39
*** VW has joined #openstack-meeting-309:39
*** lpetrut has joined #openstack-meeting-309:39
*** sdake has quit IRC09:40
*** irenab has joined #openstack-meeting-309:42
*** irenab has quit IRC09:43
*** VW has quit IRC09:44
*** ajnouri has joined #openstack-meeting-309:45
*** irenab has joined #openstack-meeting-309:47
*** tfukushima has quit IRC09:47
*** toddjohn has joined #openstack-meeting-309:48
*** ociuhandu has joined #openstack-meeting-309:51
*** sambetts|afk is now known as sambetts09:51
*** irenab has quit IRC09:56
*** vishwanathj has quit IRC09:57
*** ujuc has quit IRC09:58
*** amotoki has quit IRC10:01
*** amotoki has joined #openstack-meeting-310:04
*** vishwanathj has joined #openstack-meeting-310:07
*** zhurong has quit IRC10:10
*** ociuhandu has quit IRC10:16
*** vishwanathj has quit IRC10:21
*** Niham has quit IRC10:22
*** Niham has joined #openstack-meeting-310:24
*** itxaka has joined #openstack-meeting-310:26
*** hoangcx has quit IRC10:26
*** reedip has joined #openstack-meeting-310:34
*** ociuhandu has joined #openstack-meeting-310:36
*** kzaitsev_mb has joined #openstack-meeting-310:37
*** amotoki has quit IRC10:37
*** amotoki has joined #openstack-meeting-310:39
*** SarathMekala has quit IRC10:39
*** SarathMekala has joined #openstack-meeting-310:40
*** sdague has joined #openstack-meeting-310:46
*** rtheis has joined #openstack-meeting-310:46
*** toddjohn has quit IRC11:00
*** SarathMekala has quit IRC11:02
*** irenab has joined #openstack-meeting-311:05
*** amotoki has quit IRC11:07
*** irenab has quit IRC11:14
*** amotoki has joined #openstack-meeting-311:15
*** toddjohn has joined #openstack-meeting-311:20
*** jlanoux has quit IRC11:22
*** banix has joined #openstack-meeting-311:24
*** abalutoiu has joined #openstack-meeting-311:25
*** ccamacho has joined #openstack-meeting-311:25
*** julim has joined #openstack-meeting-311:31
*** banix has quit IRC11:42
*** jlanoux has joined #openstack-meeting-311:42
*** baoli has joined #openstack-meeting-311:43
*** baoli has quit IRC11:44
*** toddjohn has quit IRC11:44
*** baoli has joined #openstack-meeting-311:44
*** zhurong has joined #openstack-meeting-311:45
*** baoli_ has joined #openstack-meeting-311:46
*** baoli has quit IRC11:49
*** ajnouri has quit IRC11:54
*** irenab has joined #openstack-meeting-312:07
*** irenab has quit IRC12:08
*** irenab has joined #openstack-meeting-312:09
*** dtardivel has quit IRC12:10
*** tellesnobrega is now known as tellesnobrega_af12:11
*** amotoki has quit IRC12:11
*** kzaitsev_mb has quit IRC12:13
*** irenab has quit IRC12:17
*** amotoki has joined #openstack-meeting-312:18
*** amotoki has quit IRC12:18
*** vgridnev has joined #openstack-meeting-312:26
*** kzaitsev_mb has joined #openstack-meeting-312:29
*** tellesnobrega_af is now known as tellesnobrega12:33
*** irenab has joined #openstack-meeting-312:33
*** tangchen has joined #openstack-meeting-312:35
*** amotoki has joined #openstack-meeting-312:36
*** irenab has quit IRC12:38
*** stanzgy has quit IRC12:39
*** pgadiya has quit IRC12:40
*** julim has quit IRC12:41
*** Niham has quit IRC12:45
*** iurygregory has joined #openstack-meeting-312:51
*** crobertsrh has joined #openstack-meeting-312:52
*** amotoki has quit IRC12:53
*** jlanoux_ has joined #openstack-meeting-312:57
*** jlanoux has quit IRC12:57
*** yamamoto_ has quit IRC12:58
*** iyamahat has joined #openstack-meeting-312:59
*** dtroyer has joined #openstack-meeting-313:01
dtroyerGood morning OSC folk…13:03
tangchenhi~~13:03
rtheisgood morning13:03
dtroyer#startmeeting openstackclient13:03
openstackMeeting started Thu Jun  2 13:03:44 2016 UTC and is due to finish in 60 minutes.  The chair is dtroyer. Information about MeetBot at http://wiki.debian.org/MeetBot.13:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:03
*** openstack changes topic to " (Meeting topic: openstackclient)"13:03
openstackThe meeting name has been set to 'openstackclient'13:03
tangchenIt is night for me. :) hahaha13:04
rtheisgood night too :)13:04
tangchen:)13:04
*** stanchan has joined #openstack-meeting-313:04
*** shwetaap has joined #openstack-meeting-313:05
*** alaski has left #openstack-meeting-313:05
dtroyerShall we get started?13:05
dtroyer#topic releases13:05
*** openstack changes topic to "releases (Meeting topic: openstackclient)"13:05
tangchenlet's go13:06
dtroyerWe did the 2.5.0 release last week, the last planned release before 3.013:06
dtroyerI wanted to hold off making any breaking merges until we had a bit of time to make sure 2.5.1 was not immediately necessary13:06
dtroyerwe seem to be clear of that13:07
dtroyeranyone know of anything otherwise?13:07
rtheisdtroyer: I may have one...13:07
rtheisI just found an issue late yesterday that I think is related to --enable-beta-commands13:08
rtheisSomehow, --enable options are getting ignored on commands now13:08
rtheisI need to investigate further as to why this is.  Any ideas?13:09
dtroyeroh good grief…yes13:09
dtroyerglobal option names bite again13:09
dtroyerI forget the exact setting, but argparse will swallow up substring matches sometimes13:10
dtroyerthat's another reason we use —os on most global options13:10
rtheisoh boy13:10
rtheisso is it best to just change to --os prefix for this?13:11
dtroyerpossibly, or something similar13:11
*** mbound has joined #openstack-meeting-313:11
*** njohnston is now known as njohnston|afk13:11
dtroyereven just —os-beta-commands?13:11
rtheissure13:12
rtheisI like that13:12
rtheisI'll open a bug and work on a fix today.13:12
dtroyerok, thanks13:12
rtheisI didn't expect argparse to have such a "feature"13:12
dtroyerI have a feeling though that we'll need to jump to 2.6.0 based on what has already merged…I will review13:12
rtheisok13:13
*** mbound has quit IRC13:13
*** mbound has joined #openstack-meeting-313:13
dtroyerIIRC argparse does this when combined with… tab complete maybe?13:13
dtroyerno, not tab complete… dang, I forget exactly what it is13:14
*** julim has joined #openstack-meeting-313:14
rtheisthat's ok13:15
dtroyeranything else release-wise?  This means we need to still hold off on the bigger breaking things for a while, probably next week13:15
rtheisI don't have anything else13:15
*** mrmartin has joined #openstack-meeting-313:15
tangchennone for me13:15
dtroyer#topic reviews13:16
*** openstack changes topic to "reviews (Meeting topic: openstackclient)"13:16
*** yamahata has joined #openstack-meeting-313:16
dtroyerSo I was wanting to go through the stuff we have been holding back here13:16
dtroyerwe can still look at the list, but wait on them13:16
tangchenAre we going to do the ip refactor now ?  after 2.5.013:17
dtroyeryes, that set is one in this category13:17
tangchenI mean this series. https://review.openstack.org/#/c/300388/13:17
tangchenOK13:17
dtroyeralso Navid's KSA and it's follow on reviews from Alvaro13:18
dtroyerand Henry's role assignment13:18
rtheisok13:19
* dtroyer is looking at the list from last week13:19
dtroyerso the only things I am unsure about is what may be new since last Thursday13:20
dtroyerother than release-type issues, any reviews we need to talk about?13:21
rtheisLooking for opinions on command object for https://review.openstack.org/#/c/319522/13:21
rtheisThis is for neutron rbac policies13:22
*** stanchan has quit IRC13:22
dtroyerwow, yeah, yuck13:22
rtheisSimilar for https://review.openstack.org/#/c/320604/ which is start of OSC neutron plugin13:23
rtheisthat is, plugin for network advanced services13:23
rtheisno rush on these, just wanted to bring them up for attention13:24
dtroyersure, thanks, I had not seen them13:24
*** stanchan has joined #openstack-meeting-313:24
* dtroyer was sleeping much of yesterday, too much holiday weekend maybe :(13:24
rtheis:)13:25
dtroyerinterestingly enough, the recent ML thread about changing the *aaS release model brings up the near-deadness of at least two of those projects13:25
dtroyerback to the RBAC bit though, I don't think we can assume that 'rbac' is network-only in the long term13:26
dtroyerbut yes, it's a bad name all on its own13:26
*** lblanchard has joined #openstack-meeting-313:27
rtheisyeah, it seemed similar to qos in my mind13:27
dtroyerhow does 'network policy' fit?  it feels like it might still be too ambiguous13:27
rtheisnetwork has qos policies13:28
dtroyerqos has a better case though, as it is the common term in the networking world.  like IP13:28
rtheisand rbac policies13:28
dtroyerah, ok13:28
rtheiswe have "volume qos" today13:28
dtroyerwhat role does the R in RBAC refer to?13:28
dtroyerusers or servers?13:29
rtheistrying to sort that out now13:30
tangchenI think it is users.13:30
dtroyerI have always thought of it as user-related but don't see how that work in a neutron context13:30
rtheisit is users actions allowed for network objects enforced on a project13:31
rtheisI haven't played with it much13:31
dtroyerIdentity uses plain role here13:32
tangchenme nither...13:32
dtroyerso a) it owns that object, but b) doesn't use rbac13:32
dtroyername13:32
dtroyerok, let's keep the conversation going in the reviews13:33
dtroyerI'll leave some comments after the meeting13:33
rtheisthanks dtroyer13:33
tangchenthanks.13:33
dtroyertangchen: in https://review.openstack.org/#/c/321977/ I noticed you added an exception for when no option (—enable|—disable) is present13:34
dtroyerI thought we started removing those complaints13:34
dtroyerthinking that if the user does not specify a change, that is not an error13:34
*** crinkle has quit IRC13:35
tangchenWell, that makes sense. So, a warning msg ?13:35
tangchenI think we should let the user know nothing has changed.13:36
dtroyermaybe… I still lean toward nothing though13:36
dtroyermaybe an info message, that will be silent unless -v is set13:36
*** Niham has joined #openstack-meeting-313:37
*** crinkle has joined #openstack-meeting-313:37
tangchenI think nothing will be a little strange. The command is not complete. but it looks like it has been executed correctly.13:37
dtroyerbut it has been executed correctly13:37
dtroyerit did nothing correctly13:38
dtroyer:)13:38
*** Niham has quit IRC13:38
*** rbak has quit IRC13:38
tangchenWell, I'd vote for a warning, but info is also ok for me.13:38
*** hdaniel has quit IRC13:38
dtroyerset commands usually have more options, if this one grows more we would need to remove the specific warning about --enable13:38
dtroyerbecause then it would not be an issue13:38
tangchensorry, what specific warning about --enable ?13:40
dtroyerif we did the same thing to 'user set', for example, you would have a warning if —enable or —disable was not present13:41
*** tonytan4ever has joined #openstack-meeting-313:41
tangchenOh, I see13:41
dtroyerwhich is totally acceptable13:41
tangchenjust like service set13:41
tangchenOK13:42
*** mrmartin has quit IRC13:42
tangchenI'm OK with nothing output.13:42
tangchenThen we need to fix some other commands.13:42
dtroyeryes we do13:42
tangchenOK, I'm on it13:42
dtroyerthanks13:42
dtroyerany other reviews?13:43
rtheisnone from me13:43
tangchennone for me, but I have two things need some advice.13:43
tangchenplease give me 5 min in the end13:43
dtroyerok, will do13:44
dtroyer#topic bugs13:44
*** openstack changes topic to "bugs (Meeting topic: openstackclient)"13:44
dtroyerI saw https://bugs.launchpad.net/python-openstackclient/+bug/1587927 and never considered that before, we have another thing to sort out13:44
openstackLaunchpad bug 1587927 in python-openstackclient "Quotas command is not plugable" [Undecided,New]13:44
dtroyerthat is a good example of when we want a plugin to be able to modify another command13:45
dtroyerother times we don't want that13:45
dtroyerfun times ;)13:45
rtheisthat is interesting13:45
dtroyerI played with something similar by adding —ram —cpu and —disk to server create a while back via a plugin13:46
dtroyerbut that technique isn't viable for actual use because it depends on install order13:46
dtroyeralso, https://bugs.launchpad.net/python-openstackclient/+bug/1580870 is asking for what looks to be nova-net commands?13:47
openstackLaunchpad bug 1580870 in python-openstackclient "Fixed IP reserve/unreserve/show in computeV2" [Undecided,New] - Assigned to aohuanxuan (huanxuan-ao)13:47
dtroyerif they are part of Compute13:47
*** shwetaap1 has joined #openstack-meeting-313:47
rtheisnova-net is back to deprecated, isn't it?13:48
dtroyerlet's see… it is an even year, and even month, an even day, so I think yes?13:48
rtheis:)13:48
tangchenIf they are just for nova, yes.13:49
*** shwetaap has quit IRC13:49
dtroyerIf we do those for Network and adding them for Compute is near-trivial, then maybe.  Otherwise I think at this point we should have a Really Good Reason to add more nova-net-only commands13:49
*** Poornima has quit IRC13:49
dtroyerI'll ask that in the bug…13:50
rtheisagreed13:50
tangchenOK13:50
*** jmckind has joined #openstack-meeting-313:50
dtroyerother bugs to raise?13:50
tangchennon for me13:50
rtheisnothing else13:51
dtroyer#topic open discussion13:51
*** openstack changes topic to "open discussion (Meeting topic: openstackclient)"13:51
dtroyerwhat is on your ming, tangchen?13:51
tangchenhttps://blueprints.launchpad.net/python-openstackclient/+spec/log-usage13:51
tangchenNeed some advice for this13:51
tangchenI'm often confused the way to use a logger.13:52
tangchenI can see 3 loggers in OSC13:52
tangchenShall we give some rules on how to use them ?13:52
dtroyergood idea, yes13:53
rtheishttps://github.com/openstack/python-openstackclient/blob/master/openstackclient/common/command.py#L3713:53
dtroyerI can see places where all of those make sense though, the rule will probably be based on what type of message is being reported13:53
*** rbak has joined #openstack-meeting-313:53
rtheisI thought this was an attempt at that13:53
dtroyerrtheis: I would agree with that.13:54
tangchensorry, I don't quite understand13:54
dtroyerthe default for commands seems like it should be using self.log()13:54
tangchenwhat do you mean richard ?13:54
dtroyerself.app.log() should be for things that are not command-specific13:55
dtroyerso volume's use there probably needs to be changed13:55
tangchenyes13:55
*** mrmartin has joined #openstack-meeting-313:55
tangchenOK, I can start the work from volume.13:55
tangchenthen we can discuss more in the reviews, and give a rule in doc finally.13:56
dtroyerthe module-level LOG is likely the least necessary one for reporting13:56
dtroyersounds good13:56
tangchenone more thing13:56
tangchenhttp://docs.openstack.org/contributor-guide/writing-style/word-choice.html13:56
rtheistangchen: just wondering if we can expand what is already done so commands have less to worry about, but I realize more is needed as you point out13:57
tangchensomeone showed me this...13:57
tangchenOK, Richard. :)13:57
dtroyerooooh! nice!13:57
tangchenWhat I want to ask is, are we going to accept patches like this ?13:58
tangchenmaybe...openstack->OpenStack13:58
*** esikachev has joined #openstack-meeting-313:58
tangchentoo trivial, I think13:58
dtroyerfor fixing docs?13:58
tangchenyes13:58
rtheisdepends13:58
dtroyerwe'll accept them, but I really don't want to see one for each13:58
tangchenthere was one today.13:58
tangchenyes13:58
*** elmiko has joined #openstack-meeting-313:59
tangchenShe abandoned finally. And maybe will give a big one at last.13:59
dtroyerI used to do sweeps through fixing a bunch of help and docs all at once, broken by APi or something to keep it from getting too big13:59
*** emagana has joined #openstack-meeting-313:59
tangchenOK, I see.13:59
tangchenno question for me today. :)13:59
dtroyerbut style and form do matter, so we do want to fix these things14:00
*** mrmartin has quit IRC14:00
*** ddieterly has joined #openstack-meeting-314:00
rtheisagreed14:00
tangchenOK14:01
rtheisnothing else from me14:01
dtroyerok, we're out of time14:01
dtroyerthanks guys!14:01
dtroyer#endmeeting14:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:01
openstackMeeting ended Thu Jun  2 14:01:22 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstackclient/2016/openstackclient.2016-06-02-13.03.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstackclient/2016/openstackclient.2016-06-02-13.03.txt14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstackclient/2016/openstackclient.2016-06-02-13.03.log.html14:01
tangchenbey14:01
vgridnev#startmeeting sahara14:01
openstackMeeting started Thu Jun  2 14:01:36 2016 UTC and is due to finish in 60 minutes.  The chair is vgridnev. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: sahara)"14:01
openstackThe meeting name has been set to 'sahara'14:01
NikitaKonovalovo/14:01
vgridnev#link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda14:01
crobertsrhhello/14:01
elmikoo/14:01
vgridnevhello folks14:01
*** VW has joined #openstack-meeting-314:02
vgridnev#topic News / updates14:03
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:03
vgridnev#info Newton-1 is done for sahara https://review.openstack.org/#/c/323872/14:04
crobertsrhJust a few reviews for me.  I need to take a look at current specs again soon.14:04
vgridnev#info saharaclient release proposal https://review.openstack.org/#/c/324386/14:04
elmikosadly, not much to report for me. i've been looking over the apiv2 work in attempts to better plan how we will go forward.14:05
vgridnevalso, preparing several important back ports to mitaka14:05
*** yamamoto has joined #openstack-meeting-314:07
NikitaKonovalovThere's a feature in Nova which conflicts with our volume discovery. I've got a fix that is almost working.14:07
NikitaKonovalovI'll put it on review soon14:08
*** jlopezgu has joined #openstack-meeting-314:09
vgridnevelmiko, sad news. Just thoughts: since APIv2 is a experimental feature, that most probably will not touch our default behavior, maybe we can ignore specs and just move to the implementation? Much better commit message should describe changes proposed14:09
elmikovgridnev: that's an interesting thought14:10
elmikoi think the only spec we really need at this point in the microversion one14:11
elmikothe rest can wait, and we still have several work items that don't need them14:11
*** emagana has quit IRC14:11
*** lelyakin has joined #openstack-meeting-314:11
*** huichun has joined #openstack-meeting-314:12
vgridnevdo we need a API v2 topic?14:12
*** emagana has joined #openstack-meeting-314:13
elmikoi think we just covered it ;)14:13
*** claudiub has quit IRC14:13
elmikounless anyone else has something to add?14:13
vgridnev#topic API v2 progress14:13
*** openstack changes topic to "API v2 progress (Meeting topic: sahara)"14:13
*** egafford has joined #openstack-meeting-314:14
*** emagana has quit IRC14:14
vgridnevegafford, hello!14:14
vgridnev#undo14:14
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x7f2dd41d1290>14:14
*** emagana has joined #openstack-meeting-314:14
egaffordvgridnev: Hi there! Sorry; fighting flaky internet today. :/14:14
*** emagana has quit IRC14:14
*** emagana has joined #openstack-meeting-314:15
vgridnevanything new from you?14:15
egaffordMy status is minimal (still working on spec/code for image gen), but I'm happy to report (as I did to vgridnev yesterday) that most to all of the company internal issues that've been keeping me from Sahara for a while are resolving, so I'll be much more present, and will probably be able to recruit at least 1 other engineer for the community.14:16
*** yamamoto has quit IRC14:16
egaffordSo that's exciting.14:16
*** woodster_ has joined #openstack-meeting-314:17
elmikonice, good to hear =)14:18
*** zz_dimtruck is now known as dimtruck14:19
*** fwdit has quit IRC14:19
vgridnev#topic Open discussion14:19
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:20
vgridnevwould love to see some reviews for https://review.openstack.org/#/c/317520/14:20
*** banix has joined #openstack-meeting-314:20
*** dtroyer has left #openstack-meeting-314:20
elmikoack, adding it to my queue14:21
vgridnevand also, I've noticed that we have weird bug in saharaclient, https://bugs.launchpad.net/python-saharaclient/+bug/155129214:21
openstackLaunchpad bug 1551292 in Python client library for Sahara "0.12.0 is using sphinx-arparse but it's not in global requirements" [Undecided,Incomplete]14:21
vgridnevseems that we are using that for generating CLI docs14:23
elmikohuh14:24
*** banix_ has joined #openstack-meeting-314:24
*** yamamoto has joined #openstack-meeting-314:24
*** claudiub has joined #openstack-meeting-314:26
egaffordAre we implicitly depending on it through a stated dependency? Otherwise it's weird that we're not just breaking completely.14:27
*** banix has quit IRC14:27
egaffordStill best to depend on it directly in any case, in case the dep chains change, but weird...14:27
*** bswartz has quit IRC14:27
*** banix has joined #openstack-meeting-314:27
vgridnevwe depends only in CLI docs generation14:28
egaffordOk, I see; we're just breaking there. Sad.14:28
vgridnevhttps://github.com/openstack/python-saharaclient/blob/master/tox.ini#L1514:29
*** banix_ has quit IRC14:30
vgridnevmy thoughts just copy code of that library in our code for now (it's MIT licensed) and then try to push that to globals. if we success in step 2, we can remove copied code14:32
egaffordSeems reasonable.14:33
crobertsrh+114:33
elmikothat seems to be a popular trend14:33
*** ajmiller has joined #openstack-meeting-314:35
*** amotoki has joined #openstack-meeting-314:35
vgridnevok, seems that we agreed on that14:35
vgridnevanything else that we can discuss?14:35
*** SridarK has joined #openstack-meeting-314:38
*** banix_ has joined #openstack-meeting-314:38
*** ajmiller_ has quit IRC14:38
*** banix has quit IRC14:39
*** banix_ is now known as banix14:39
vgridnevok, thanks folks for attending14:40
vgridnev#endmeeting14:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:41
openstackMeeting ended Thu Jun  2 14:41:07 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2016/sahara.2016-06-02-14.01.html14:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2016/sahara.2016-06-02-14.01.txt14:41
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2016/sahara.2016-06-02-14.01.log.html14:41
elmikothanks vgridnev14:41
*** crobertsrh has left #openstack-meeting-314:42
*** mtanino has joined #openstack-meeting-314:42
*** yamamoto has quit IRC14:43
*** david-lyle has joined #openstack-meeting-314:44
*** devananda has quit IRC14:45
*** esikachev has quit IRC14:47
*** bswartz has joined #openstack-meeting-314:51
*** vgridnev has quit IRC14:52
*** vgridnev_ has joined #openstack-meeting-314:53
*** vgridnev_ has quit IRC14:53
*** claudiub|2 has joined #openstack-meeting-314:53
*** ajmiller has quit IRC14:55
*** claudiub has quit IRC14:56
*** devananda has joined #openstack-meeting-314:56
*** vgridnev has joined #openstack-meeting-314:56
*** zhurong has quit IRC14:57
*** mlavalle has joined #openstack-meeting-314:57
*** tidwellr has joined #openstack-meeting-314:58
*** yamamoto has joined #openstack-meeting-314:58
*** ajmiller has joined #openstack-meeting-314:59
*** elmiko has left #openstack-meeting-314:59
*** mickeys has joined #openstack-meeting-314:59
*** janzian has joined #openstack-meeting-314:59
*** john-davidge has joined #openstack-meeting-314:59
*** galstrom_zzz is now known as galstrom14:59
*** Na_Zhu has joined #openstack-meeting-314:59
mlavalle#startmeeting neutron_l314:59
openstackMeeting started Thu Jun  2 14:59:58 2016 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.14:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
mlavalle#chair carl_baldwin15:00
openstackCurrent chairs: carl_baldwin mlavalle15:00
*** brianstajkowski has joined #openstack-meeting-315:00
*** pavel_bondar has joined #openstack-meeting-315:00
mlavalle#chair tidwellr15:00
openstackCurrent chairs: carl_baldwin mlavalle tidwellr15:00
*** njohnston|afk is now known as njohnston15:00
carl_baldwinHi15:00
yamamotohi15:00
pavel_bondarhi15:00
john-davidgeHi15:00
haleybhi15:00
mlavalleHi everybody15:00
njohnstono/15:00
tidwellrhi15:00
johndperkinshi15:00
mlavalleAgenda is here: https://etherpad.openstack.org/p/neutron-l3-subteam15:01
mlavalle#topic Annoucements15:01
*** openstack changes topic to "Annoucements (Meeting topic: neutron_l3)"15:01
*** emagana has quit IRC15:01
*** kzaitsev_mb has quit IRC15:01
mlavalleNewton-1 is being cut this week, as we speak15:01
*** steve_ruan has joined #openstack-meeting-315:01
*** kzaitsev_mb has joined #openstack-meeting-315:02
mlavalleAlso the Neutron mid-cycle is confirmed to take place in Cork Ireland, August 17 -1915:02
*** emagana has joined #openstack-meeting-315:03
mlavalleAny other annoucements from the team?15:03
*** stanchan has quit IRC15:03
carl_baldwinNot from me15:04
mlavalleEtherpad for the mid-cycle is here:15:04
mlavalle#link https://etherpad.openstack.org/p/newton-neutron-midcycle15:04
*** fitoduarte has quit IRC15:04
mlavalleok, let's move on...15:04
mlavalle#topic Bugs15:04
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:04
mlavalleFirst up is https://bugs.launchpad.net/neutron/+bug/154309415:05
openstackLaunchpad bug 1543094 in neutron "[Pluggable IPAM] DB exceeded retry limit (RetryRequest) on create_router call" [High,In progress] - Assigned to Carl Baldwin (carl-baldwin)15:05
tidwellrhi15:05
*** johnbelamaric has joined #openstack-meeting-315:05
carl_baldwinI think this is about ready to merge.15:06
carl_baldwinI just wonder if the pluggable side of the changes are getting enough exercise.15:06
tidwellrme too15:06
carl_baldwinI'm comfortable with the non-pluggable side.15:06
*** konstantinos has quit IRC15:07
pavel_bondarI have rebased migration to pluggable ipam patch on top of that patch to see CI results15:07
carl_baldwintidwellr: BTW, I rolled that call to flush in to your patch the other day.15:07
*** Fdaisuke_ has left #openstack-meeting-315:07
carl_baldwinpavel_bondar: Great.  Any results yet?15:07
*** vdrok-afk has quit IRC15:07
tidwellrcarl_baldwin: thanks, barely treading water this week :)15:07
pavel_bondarSee two failed jobs, need to investigate deeper15:07
pavel_bondar#link https://review.openstack.org/#/c/181023/15:07
*** konstantinos has joined #openstack-meeting-315:08
carl_baldwinpavel_bondar: I can probably help a bit.  I'm pretty familiar with tidwellr 's change by now.15:08
tidwellrpavel_bondar: those are odd failures15:09
*** ajnouri has joined #openstack-meeting-315:09
pavel_bondarwe can try to do recheck to see if it is a fluctuation or not15:09
*** tellesnobrega is now known as tellesnobrega_af15:10
carl_baldwinpavel_bondar: It will help to recheck it a few times.  With this big a change, it helps to collect more data.15:10
*** vdrok-afk has joined #openstack-meeting-315:10
carl_baldwinI'd say recheck it any time you notice it is not in the check queue getting checked.15:10
pavel_bondarok :)15:11
pavel_bondarrechecking15:11
carl_baldwinWe're going to get this one soon, I think.15:12
carl_baldwinmlavalle: I think that's all for now.15:12
mlavalleok, let's move on...15:12
mlavalleNext up is https://bugs.launchpad.net/neutron/+bug/156433515:12
openstackLaunchpad bug 1564335 in neutron " [Pluggable IPAM] delete subnet in ml2 plugin does not comply with pluggable ipam (deletes ip allocations directly from db)" [High,In progress] - Assigned to Pavel Bondar (pasha117)15:12
pavel_bondartwo fixes are in gerrit for that15:13
pavel_bondar#link https://review.openstack.org/#/c/300984/ updated it today, fixed some comments15:13
pavel_bondar#link https://review.openstack.org/#/c/323345 is a WIP, UTs are pending, uploaded to get agreement about the approach15:14
*** kzaitsev_mb has quit IRC15:14
pavel_bondarinitial review fix #2 is strongly welcome15:15
carl_baldwinWill do15:15
pavel_bondarcarl_baldwin: thanks15:15
pavel_bondarso that is it from my side15:15
mlavalleThanks pavel_bondar for your update and hard work!15:16
mlavalleThose are the 2 high priority bugs we have for this week15:16
*** toddjohn has joined #openstack-meeting-315:16
mlavalleAny other bugs that the team wants to discuss here?15:16
*** vhoward has joined #openstack-meeting-315:17
mlavalleIf not, let's move on15:17
mlavalle#topic Routed Networks15:17
*** openstack changes topic to "Routed Networks (Meeting topic: neutron_l3)"15:17
*** kzaitsev_mb has joined #openstack-meeting-315:17
carl_baldwinHi15:17
*** anilvenkata has quit IRC15:18
carl_baldwinStill trying to work through the etherpad items.15:18
carl_baldwin#link https://etherpad.openstack.org/p/routed-provider-networks-notes15:18
carl_baldwinThe Nova spec has a +2 from John.15:18
mlavalleYeap15:18
carl_baldwinThe next highest priority patch is for IPAM15:18
mlavalleWe probably need to ping mriedem today to get his15:18
carl_baldwin#link https://review.openstack.org/#/c/314815/15:19
carl_baldwin... and the next one ...15:19
carl_baldwin#link https://review.openstack.org/#/c/32063115:19
*** irenab has joined #openstack-meeting-315:19
carl_baldwinThat's about it from me.  I'm starting to work on Nova and deferred IP ports.15:20
*** claudiub|2 has quit IRC15:21
*** abalutoiu has quit IRC15:22
mlavallecarl_baldwin: so we don't duplicate effort, could you elaborate on the Nova work you are doing?15:22
carl_baldwinmlavalle: A simple part.  Just getting Nova to accept a port without an IP until host binding.15:23
mlavalleok, cool15:23
mlavalleI just pinged mriedem in the Nova channel to get his review for https://review.openstack.org/#/c/26389815:23
carl_baldwinmlavalle: Essentially what I started with that Nova patch a while back.15:23
carl_baldwin#link https://review.openstack.org/#/c/29959115:23
carl_baldwinmlavalle: Thanks for helping that spec along.15:24
mlavalleok, let's move on...15:24
mlavalle#topic BGP Dynamic Routing15:25
*** openstack changes topic to "BGP Dynamic Routing (Meeting topic: neutron_l3)"15:25
tidwellrhi15:25
tidwellrI think we're ready to start dealing with RFE's and specs since the neutron-dynamic-routing repo is in reasonably good shape15:26
tidwellrthe last important item is to get test jobs up and running and get enough confidence in the jobs that we can turn them to voting jobs15:27
steve_ruanhi Ryan, when the test jobs ready?15:28
Na_Zhutidwellr: what is the plan about RFE?  Mickey and Steve are working on the RFE about BGP EVPN, is there anyone works on other RFEs?15:28
tidwellrsteve_ruan: we need to get the jobs so they actually run tests15:29
Na_Zhutidwellr: seems like vikram is working on bgp statistics, right15:29
tidwellrsteve_ruan: we have 2 jobs, but they don't run any tests and I think they are non-voting at the moment15:30
steve_ruantidwellr, thanks15:30
*** iyamahat has quit IRC15:30
Na_Zhutidwellr: can i take one confirmed RFE?15:30
tidwellrNa_Zhu: let's wait until the RFE goes to "accepted"15:31
*** yamahata has quit IRC15:31
Na_Zhutidwellr: ok15:32
mickeysWe submitted a spec for BGP EVPN IP Prefix Advertisement15:32
tidwellrNa_Zhu: I think we're still taking RFE's to the neutron drivers team, so that feedback is important15:32
mickeys#link https://review.openstack.org/#/c/322654/15:32
tidwellrmickeys: thanks for the pointer, I've been meaning to give that a look15:32
mickeystidwellr: We are looking forward to your feedback, and any feedback we can get from others15:33
tidwellr#action tidwellr to review EPVN spec15:34
tidwellrI didn't have anything else15:35
tidwellrmickeys, Na_Zhu, steve_ruan?15:35
mickeysNothing else from me15:35
steve_ruanyes, no update15:36
Na_Zhunothing to update15:36
Na_Zhunothing else to update15:37
mlavalletidwellr, mickeys, steve_ruan, Na_Zhu thanks for the update15:37
mlavalle#topic FWaaS15:37
*** openstack changes topic to "FWaaS (Meeting topic: neutron_l3)"15:37
mlavalleAre there any updates from the FWaaS team?15:37
SridarKmlavalle: we have been looking at the agent extensions15:38
njohnstonI drilled down on how the L2 agent extensions work and how the notification driver works15:38
njohnstonMy hope is to follow that as a common pattern15:38
SridarK+115:38
njohnstonThe L2 agent notification driver is build on top of the 'port_update' and 'network_update' RPCs15:39
*** kzaitsev_mb has quit IRC15:39
njohnstonso to follow their model I will need to gain more knowledge about what RPCs are in use by the L3 agent15:39
njohnstonThey had tried to implement a separate set of messaging, but they said that experiments with it proved to be a RabbitMQ-buster15:40
mlavallelol15:40
njohnstonSo research is ongoing, but I will add info to https://review.openstack.org/#/c/315745/ as I grok it15:40
carl_baldwinnjohnston: Thanks, I'll watch that spec.15:41
njohnstoncarl_baldwin: thanks!15:41
*** numans has quit IRC15:41
SridarKjust to add - we also got pointed to https://review.openstack.org/#/c/91532/15:42
SridarKwhich had done some earlier work on this area - we hope we can get some more data off that15:42
njohnstonyes, the author of that one said that it is dead but that we should feel free to plagiarize anything that looks usable.15:43
mlavalleSridarK, njohnston: anything else to share with the team?15:44
njohnstonnope15:44
SridarKmlavalle: nothing15:44
SridarKthx15:44
mlavalleThanks for your update!15:44
mlavalle#topic Open discussion15:45
*** openstack changes topic to "Open discussion (Meeting topic: neutron_l3)"15:45
mlavalleI have a topic to share with the team15:45
*** andreas_s has quit IRC15:45
mlavalleA few months ago, armax sent an email to carl_baldwin and me, asking us to cleanup some technical debt we had incurred when initially implementing DNS integration15:46
mlavalleSpecifically, to clean up calls in the DB core plugin to DNS15:46
mlavalleI have been working with one of my team members, Bin yu (yb is his irc nickname) on this:15:47
mlavalle#link https://review.openstack.org/#/c/31329115:47
mlavalleWe have iterated it several times. I think it is very close to be ready for reviews from carl_baldwin and other team members15:48
*** spzala has joined #openstack-meeting-315:48
carl_baldwinmlavalle: Thanks for following up on this.15:48
mlavalleI will review the last revision today and if I feel comfortable with it, I will ping carl_baldwin and others to get reviews15:48
mlavalledon't invest time on it until I let you know15:48
carl_baldwinmlavalle: sounds good.15:48
mlavallethat's all I have on this topic15:49
mlavalleany other topics from the team?15:49
*** iyamahat has joined #openstack-meeting-315:50
mlavalleThanks for attending today's meeting!15:51
carl_baldwinThanks!15:51
mlavalle#endmeeting15:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:51
openstackMeeting ended Thu Jun  2 15:51:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-06-02-14.59.html15:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-06-02-14.59.txt15:51
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-06-02-14.59.log.html15:51
SridarKThanks15:51
*** Na_Zhu has quit IRC15:52
*** yamahata has joined #openstack-meeting-315:52
*** iyamahat has quit IRC15:54
*** lblanchard has quit IRC15:55
*** steve_ruan has quit IRC15:56
*** ddieterly is now known as ddieterly[away]15:57
*** matrohon has quit IRC15:57
*** johnbelamaric has left #openstack-meeting-315:58
etoews#startmeeting api wg16:00
*** cdent has joined #openstack-meeting-316:00
openstackMeeting started Thu Jun  2 16:00:09 2016 UTC and is due to finish in 60 minutes.  The chair is etoews. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: api wg)"16:00
openstackThe meeting name has been set to 'api_wg'16:00
cdento/16:00
etoewshello16:00
cdentelmiko said he will be late16:00
cdentwere you/are you still at pycon?16:00
etoewsgot back yesterday16:01
etoewsjust catching up16:01
cdenttwitter made pycon sound very good16:01
*** mlavalle has left #openstack-meeting-316:01
*** lblanchard has joined #openstack-meeting-316:02
etoewsit was :)16:02
*** ddieterly[away] is now known as ddieterly16:02
etoews#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:02
etoews#topic previous meeting action items16:02
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"16:02
etoews#link http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-05-26-16.00.html16:03
etoews(none)16:03
etoewswell that's easy then16:03
cdentI think we did them all during the meeting16:03
cdentand they were all pretty much: prepare the newsletter16:03
etoewsright right16:03
etoews#topic send the weekly newsletter16:04
*** openstack changes topic to "send the weekly newsletter (Meeting topic: api wg)"16:04
etoews#link https://wiki.openstack.org/wiki/API_Working_Group_weekly_email_template16:04
etoews#link https://etherpad.openstack.org/p/api-wg-newsletter16:04
cdentI made  new guideline, so we can add that16:05
etoews\o/16:05
*** tidwellr has left #openstack-meeting-316:05
cdentand I think we also need to add a note that some of those guidelines that are up for review are old and need their authors back16:05
etoewsor we just mark them as abandoned. that's okay too.16:05
*** janzian has left #openstack-meeting-316:05
*** elmiko has joined #openstack-meeting-316:06
cdentat least two of them got some comments since the newsletter went out16:06
elmikoyo/16:06
cdentI reckon maybe we should abandon actions pending further cogitation?16:07
etoewsya16:07
*** iyamahat has joined #openstack-meeting-316:09
cdentso, to whoever put the recently merged back: is the idea that we'll just keep that as a rolling list of "recent", not "in the past week"?16:10
etoewsoh wait. were those two already in there and i didn't see them get deleted?16:10
*** jlanoux_ has quit IRC16:10
cdentetoews: yeah16:10
etoewsoops16:10
cdentbut I think it might be reasonable to re-advertise them if we want16:10
cdent?16:11
elmikowhich ones are we talking about?16:11
etoewselmiko: the merged on may 26 https://review.openstack.org/#/q/status:closed+project:openstack/api-wg16:12
*** breton_ is now known as breton16:13
etoewsi think it would look a bit odd to have them as "recently" merged for 2 weeks in a row.16:14
cdentI'm fine either way16:15
elmikoi could see that16:15
etoewsit also makes me wonder if we should be sending this every week. our velocity is such that bi-weekly might make more sense. ;)16:16
elmikotrue, but it seemed like we had a clear signal that more emails would be welcome16:16
cdentyes, and also from what I can tell people read the list in a very piecemeal fashion so it is easy to miss one week but see the next16:16
elmikois there perhaps other content we could add to them?16:16
etoewsokay. weekly is fine.16:16
cdentwe could editorialize16:17
elmikounder that guise, maybe having "recently merged" be slightly sticky is not a bad thing16:17
cdent"the other day, while reviewing nova api-ref docs, I realized that just about all the URIs in nova are awful, so I wrote a new guideline so we can avoid that in the future"16:17
elmikolol16:17
*** jmckind_ has joined #openstack-meeting-316:17
*** vgridnev has quit IRC16:17
*** vgridnev has joined #openstack-meeting-316:18
etoewsalright well let's keep them in recently merged then?16:19
*** jmckind has quit IRC16:20
elmikoyea, maybe just leave em in for a few emails. just to help drive the message home16:20
etoewsdone16:20
*** amotoki has quit IRC16:20
etoewsanything else to add to the newsletter or ready to send?16:21
cdentI think the content is correct, but since we're noodling over concerns with people's responses, will people get mego if it looks mostly identical to the last one?16:22
*** SridarK has quit IRC16:22
*** vgridnev has left #openstack-meeting-316:22
*** amotoki has joined #openstack-meeting-316:22
cdentOr should we be shaking it up somehow?16:22
*** toddjohn has quit IRC16:23
cdentmy style would be to vdiff with my memory16:23
etoewsthat was my concern.16:23
cdentso everything in the same place is good16:23
cdentbut I reckon for other people the addition of the new guideline will be completely lost (as that's the only concrete change)16:23
*** david-lyle has quit IRC16:24
etoewsdo we want to highlight "new guidelines" vs  "Guidelines currently under review"?16:24
elmikohmm, good point cdent16:24
etoewsright. maybe have a new section for "New guidelines"16:24
cdentseems reasonable16:24
elmikomight be nice to have some indication about what is "new"16:24
cdentor divvy into two broad parts "news" and "status"16:24
etoewsand rename "Guidelines currently under review" to "Decrepit guidelines"16:24
cdent:)16:25
elmikolol16:25
elmikonews/status sections seems ok to me16:25
* cdent looks around for more cans of paint16:25
etoewswhat would go under news?16:25
cdentin my mind it is basically anything that wasn't in the last week16:25
cdentor selections from the list of things that weren't there last week16:25
elmikoor do we just have an asterisk or something for new items?16:26
* elmiko grabs another brush16:26
etoewsasterisk (or the like) doesn't vdiff very well.16:26
elmikogood point16:27
cdentIf you're up for it, elmiko, as the current editor, you could just have an opening paragraph. The content that we currently have would be as it is16:27
etoewswe already have an awful lot of *  and # already16:27
cdentbut at the top you'd just write a little blurb16:27
cdent"This week nothing has merged but we've got a new guideline about..."16:27
elmikothat could work16:27
*** Swami has joined #openstack-meeting-316:27
cdentso much paint16:27
elmikoseems to me, we want this to be an email that is more than just a proceedurally generated thing16:28
cdentyes16:28
elmikoso, maybe the intro para. would help that out16:28
etoewsya16:28
cdent+516:28
etoewsja16:28
cdent(ones and twos are, like, so last week)16:28
elmiko"it was the best of times, it was the w...."16:28
cdentsomething like that?16:30
*** nkrinner has quit IRC16:31
elmikodo you have an etherpad up or something?16:31
cdent(I probably made a gazillion typos)16:31
cdentoh yeah elmiko , sorry about that, thought you had caught that:16:31
cdenthttps://etherpad.openstack.org/p/api-wg-newsletter16:31
elmikothanks16:31
cdentjust reusing the same one from last time16:31
etoewsyep. let's always just reuse that one.16:32
etoewslgtm btw ffs16:32
*** amotoki has quit IRC16:32
elmikolgtm as well16:32
*** sdake has joined #openstack-meeting-316:32
etoewscare to send it off elmiko ?16:32
elmikosure, i can do that16:33
cdentword16:33
elmikodone and done16:34
*** jmckind_ has quit IRC16:34
cdentossum16:34
etoews#topic API changes on limit / marker / sort in Newton16:35
*** openstack changes topic to "API changes on limit / marker / sort in Newton (Meeting topic: api wg)"16:35
etoews#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/095545.html16:35
etoewsi stumbled onto this the other day and didn't have a chance to dig into it16:35
*** jmckind has joined #openstack-meeting-316:35
etoewsthat was really just a reminder for me to do it16:36
etoewsthink there's anything in there we need to comment on?16:36
cdentah, yeah, I've been sort of observing that and eventually decided that it was fruitless to get too involved as the reasons for the decision are entirely based on bad mojo in nova's implementation16:36
*** sdake has quit IRC16:37
elmikoi had not seen this16:37
* elmiko reading16:37
*** kzaitsev_mb has joined #openstack-meeting-316:37
cdentit might be useful to clarify the target point that the wg has declared in existing guidelines while keeping aware that nova has pre-existing constraints16:37
etoewscdent: do we have a target point for pagination?16:39
etoewsall i'm aware of is this https://review.openstack.org/#/c/190743/21/guidelines/pagination_filter_sort.rst16:40
cdentetoews: that same file has existing sort_key guidelines in it16:41
etoewsright. http://specs.openstack.org/openstack/api-wg/guidelines/pagination_filter_sort.html but it sez nothing about pagination things like limit and marker16:42
cdentright, but the pending review does16:42
etoewswe should respond and at least point out these things.16:43
*** sdake has joined #openstack-meeting-316:44
*** stanchan has joined #openstack-meeting-316:44
cdentyou want that action?16:44
etoewsi'll do it right now16:45
etoews#topic get out of draft mode16:45
*** openstack changes topic to "get out of draft mode (Meeting topic: api wg)"16:45
* etoews be right back...16:46
cdentthis is quite the topic16:47
etoewswe can postpone it to next week16:48
*** claudiub|2 has joined #openstack-meeting-316:48
cdentI reckon before we figure out how to do it, we need to figure out what it means to be "out of draft mode"16:49
*** sambetts is now known as sambetts|afk16:50
*** julim has quit IRC16:51
cdentare we gonna hit anything in the next few minutes, if not, I've got dinner waiting on me and then unusually good evening weather to be somewhere other than at this desk16:53
etoewswhat does it mean to be "in draft mode"? :P16:54
*** numans has joined #openstack-meeting-316:54
etoewsi'm fine with ending early and putting stuff off to next week16:54
etoewsanother nice thing about weekly meetings!16:54
etoews#endmeeting16:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:55
openstackMeeting ended Thu Jun  2 16:55:08 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-06-02-16.00.html16:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-06-02-16.00.txt16:55
cdentSo I think origin of that is that the guidelines have a preface that say they are a draft: " THIS DOCUMENT IS CURRENTLY A DRAFT ONLY16:55
cdent"16:55
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-06-02-16.00.log.html16:55
elmikothanks etoews16:55
cdentyeah, thank both of you, I'm off16:55
cdento/16:55
*** huichun has quit IRC16:55
*** cdent has quit IRC16:55
*** singlethink has joined #openstack-meeting-316:56
etoewscheers16:56
*** elmiko has left #openstack-meeting-316:57
*** itxaka has quit IRC17:00
*** pvaneck has joined #openstack-meeting-317:05
*** coolsvap_ has joined #openstack-meeting-317:07
*** shwetaap1 has quit IRC17:08
*** s3wong has joined #openstack-meeting-317:09
*** jmckind has quit IRC17:10
*** toddjohn has joined #openstack-meeting-317:11
*** coolsvap_ has quit IRC17:11
*** jmckind has joined #openstack-meeting-317:11
*** spzala has quit IRC17:13
*** toddjohn has quit IRC17:16
*** tonytan4ever has quit IRC17:17
*** ivar-lazzaro has joined #openstack-meeting-317:22
*** shwetaap has joined #openstack-meeting-317:24
*** jmckind has quit IRC17:27
*** ddieterly is now known as ddieterly[away]17:32
*** amotoki has joined #openstack-meeting-317:32
*** tellesnobrega_af is now known as tellesnobrega17:33
*** amotoki has quit IRC17:38
*** igorn has quit IRC17:41
*** tonytan4ever has joined #openstack-meeting-317:42
*** toddjohn has joined #openstack-meeting-317:42
*** yamamoto has quit IRC17:43
*** SumitNaiksatam has joined #openstack-meeting-317:44
*** ihrachys has quit IRC17:45
*** VW has quit IRC17:46
*** toddjohn has quit IRC17:46
*** singlethink has quit IRC17:47
*** kzaitsev_mb has quit IRC17:56
*** VW has joined #openstack-meeting-317:57
*** hemanthravi has joined #openstack-meeting-317:58
*** rkukura has joined #openstack-meeting-317:59
SumitNaiksatamhemanthravi: rkukura igordcard ivar-lazzaro: hi18:00
igordcardhi SumitNaiksatam18:00
ivar-lazzaroSumitNaiksatam: hi18:00
rkukurahi SumitNaiksatam!18:00
SumitNaiksatam#startmeeting networking_policy18:00
hemanthravihi18:00
openstackMeeting started Thu Jun  2 18:00:28 2016 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: networking_policy)"18:00
openstackThe meeting name has been set to 'networking_policy'18:00
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#June_2nd.2C_May_26th.2C_201618:00
SumitNaiksatamis songole here?18:01
SumitNaiksatamif he is around we could discuss the bugs he entered18:01
hemanthravilet me get him18:01
SumitNaiksatamyesterday18:01
*** spzala has joined #openstack-meeting-318:01
SumitNaiksatamlet me start with the testing18:01
SumitNaiksatam#topic Testing18:01
*** openstack changes topic to "Testing (Meeting topic: networking_policy)"18:01
SumitNaiksataman update on the gate test job for Rally18:02
SumitNaiksatamit was broken for about a month18:02
*** john-davidge has quit IRC18:02
hemanthraviSumitNaiksatam: songole will be back in a few min18:02
SumitNaiksatami have fixed the Rally branch now, so the job is running again18:02
SumitNaiksatamhemanthravi: np, we will take that up when he is here18:02
SumitNaiksatamso please take a look at the rally job results when you review patches18:03
*** VW has quit IRC18:03
*** kzaitsev_mb has joined #openstack-meeting-318:04
SumitNaiksatamplease note that there are some tests which are not returning 100% success, and i think we had planned to remove those tests because they were not framed correctly18:04
SumitNaiksatami have it on my TODO list to do that clean up18:04
*** songole has joined #openstack-meeting-318:04
SumitNaiksatam#topic QoS impl18:05
*** openstack changes topic to "QoS impl (Meeting topic: networking_policy)"18:05
SumitNaiksatam#link https://review.openstack.org/#/c/301701/18:05
SumitNaiksatami think igordcard updated the patch but is still not passing the integration gate18:05
igordcardSumitNaiksatam: it's passing..18:05
SumitNaiksatamand also needs the devref that was requested18:05
*** tbachman has joined #openstack-meeting-318:06
* tbachman joins the part18:06
tbachmanparty18:06
*** spzala has quit IRC18:06
SumitNaiksatamigordcard: its passing py27 but not gate-group-based-policy-dsvm-functional18:06
*** songole has quit IRC18:06
SumitNaiksatamtbachman: hi18:06
*** galstrom is now known as galstrom_zzz18:06
tbachmanSumitNaiksatam: hi!18:06
tbachmansorry I’m late18:06
tbachman(again)18:06
SumitNaiksatamtbachman: np18:06
igordcardSumitNaiksatam: oh, I thought those always failed no matter what18:07
*** songole has joined #openstack-meeting-318:07
SumitNaiksatamigordcard: no, both those should pass18:07
SumitNaiksatamigordcard: it fails in Juno18:07
*** iurygregory_ has joined #openstack-meeting-318:07
SumitNaiksatamigordcard: the second one (rally) was failing for some time, but i have fixed it now18:07
igordcardSumitNaiksatam: where is the request for devref?18:07
SumitNaiksatamigordcard: and ideally we want the qos impl to be tested in the gate-group-based-policy-dsvm-functional job too18:07
*** galstrom_zzz is now known as galstrom18:08
igordcardSumitNaiksatam: there is no QoS neutron support in Juno18:08
SumitNaiksatamigordcard: i put it in the comment on May 26th18:08
SumitNaiksatamigordcard: yes sure, we dont need to backport this to Juno18:08
igordcardSumitNaiksatam: oh, my bad, I only read the file comments18:09
*** david-lyle has joined #openstack-meeting-318:09
SumitNaiksatamigordcard: np, i guessed as much (you addressed the inline comments)18:09
SumitNaiksatamigordcard: i think it will be easier for the other folks in the team to try this out once you have those two things18:10
SumitNaiksatamif there are no questions for igordcard we can let him go, we are standing between him and his dinner ;-)18:10
igordcardSumitNaiksatam: alright18:10
SumitNaiksatamigordcard: thanks18:10
igordcardSumitNaiksatam: lol :p18:10
SumitNaiksatam#topic Packaging18:11
*** openstack changes topic to "Packaging (Meeting topic: networking_policy)"18:11
SumitNaiksatamrkukura: thanks for joining in spite being on PTO18:11
SumitNaiksatamrkukura: anything to update here?18:11
rkukurano problem, and no update on packaging18:11
SumitNaiksatamrkukura: okay18:11
rkukuraI need to find someone at Red Hat who will respond regarding the Delorean integration18:11
SumitNaiksatamwe ran into an issue with using GBP with Fuel18:11
*** lpetrut has quit IRC18:12
SumitNaiksatamrkukura: true :-)18:12
rkukuraright, I was discussing the fuel issue with tbachman18:12
SumitNaiksatamthe issue we ran into with Fuel was that it patches released versions, and some of our monkey patches are incompatible18:12
rkukuraand SumitNaiksatam, sorry18:12
tbachmanrkukura: :)18:12
SumitNaiksatamrkukura: tbachman any thoughts?18:12
tbachmanSumitNaiksatam: no great idea just yet18:13
tbachmanit’s a tricky one18:13
SumitNaiksatamerr, i mean any solutions? :-P18:13
tbachmanas you pointed out, it would be nice to be able to divine a version somehow18:13
SumitNaiksatamtbachman: okay18:13
rkukuramonkey patching like we do is evil18:13
* tbachman nods18:13
SumitNaiksatamrkukura: i knew you were going to say that! :-)18:14
rkukuraso lets not blame fuel18:14
tbachmanlol18:14
SumitNaiksatamrkukura: yeah, no blame game18:14
SumitNaiksatambut problem remains18:14
rkukuraits my monkey patch anyway, so I could only blame myself18:14
SumitNaiksatamrkukura: it was a team decision to go that way18:15
rkukuraSumitNaiksatam: of course18:15
*** kzaitsev_mb has quit IRC18:15
rkukuraThis particular one was intended to be short term, right?18:15
SumitNaiksatamrkukura: right, and good point18:15
SumitNaiksatamrkukura: we can perhaps revisit if its really required18:16
rkukuraWe thought we might be hitting infinite loops, and wanted to see if this happens in the field18:16
SumitNaiksatamperhaps the infinite loop would not manifest any more18:16
rkukurado we know if this has been happening?18:16
SumitNaiksatamrkukura: it happens if you go and try to delete neutron resources for which corresponding GBP resources still exist18:16
*** toddjohn has joined #openstack-meeting-318:17
SumitNaiksatamthis is of course not supported and no one should be doing it, but we wanted to get out of the infinite loop situation18:17
rkukuraSumitNaiksatam: thanks for the reminder - this was due to the TX failing due to a FK, right?18:17
SumitNaiksatamrkukura: yeah18:17
rkukuraOr maybe not? Do we do FKs to neutron?18:17
SumitNaiksatamso the thing is that we are probably covered as far as Fuel is concerned even without the monkey patch18:17
tbachmanFK?18:18
rkukuraforeign key18:18
tbachmanah18:18
SumitNaiksatamhowever this will still break with RHEL install18:18
SumitNaiksatambreak -> infinite loop18:18
SumitNaiksatammy concern is that there might be a solution for this particular patch, but we have patched other things as well18:19
*** kzaitsev_mb has joined #openstack-meeting-318:19
SumitNaiksatamand it may or may not be straight forward to deal with those (if there is problem with those as well)18:19
SumitNaiksatamanyway, perhaps we need some more offline conversation on this before next week’s meeting18:20
*** egafford has left #openstack-meeting-318:20
SumitNaiksatamthanks for the input from everyone, and thanks tbachman for digging up all the details18:20
tbachmanSumitNaiksatam: wish I hadn’t18:21
* tbachman sticks head in sand18:21
SumitNaiksatamtbachman: lol!18:21
rkukuraI checked, and we do have FKs for neutron resources in our schema18:21
SumitNaiksatamrkukura: right18:21
SumitNaiksatam#topic NFP Impl patches18:21
*** openstack changes topic to "NFP Impl patches (Meeting topic: networking_policy)"18:21
SumitNaiksatamhemanthravi: songole: hi18:22
hemanthraviupdate on nfp.18:22
SumitNaiksatamhemanthravi: yes please go ahead18:22
hemanthravigbp gate tests are running, added nfp tests to gate18:22
hemanthraviusing namespace based fw and lb18:22
SumitNaiksatamhemanthravi: cool18:22
SumitNaiksatamhemanthravi: which patch adds the gate test?18:22
* SumitNaiksatam is lazy is to check ;-P18:23
hemanthravihttps://review.openstack.org/#/c/298385/8318:23
hemanthraviexercises/lb.sh, fw.sh18:23
*** julim has joined #openstack-meeting-318:23
hemanthravihttps://review.openstack.org/#/c/309145/83 has a README-NFP to try out nfp with devsatck18:24
hemanthravimissing one of the test scripts mentioned, will ask rajendra to commit it tonight18:24
hemanthravistarted adding content to the patches wiki https://wiki.openstack.org/wiki/GroupBasedPolicy/GerritQueries/NFP#NFP_Implementation_Patches18:24
hemanthraviwill complete this and work on the devref patches18:25
*** pt_15 has joined #openstack-meeting-318:25
SumitNaiksatamhemanthravi: just looked at the former patch where you mentioned the gate tests are added, looks promising18:25
SumitNaiksatamhemanthravi: the README also looks good18:26
hemanthravithe wiki lists the patches in the order to be reviewed, not all of them are required for the base mode without a service vm18:26
hemanthraviwill document this against the patches18:26
SumitNaiksatamhemanthravi: yeah, but i guess we need to be on the last patch to be able to install and check18:26
*** maishsk has joined #openstack-meeting-318:27
SumitNaiksatamhemanthravi: so at that point we would have pulled the code from all the patches18:27
hemanthraviyes, need to install the last patch18:27
SumitNaiksatamhemanthravi: so it will be good to have a description on all the patches in the wiki page right away18:27
hemanthraviwill install all the code, but won't be exerceised for the base mode18:27
*** mickeys has quit IRC18:27
SumitNaiksatamhemanthravi: okay18:27
hemanthravithe other code is required when you launch a service vm as we demod at the summit18:27
SumitNaiksatamhemanthravi: but overall this is good progress, and looks like is its at least at the point where people can try it out18:28
SumitNaiksatamhemanthravi: more information will further aid in reviewing18:28
hemanthraviwill do, hope to have most of it done over the weekend18:28
hemanthraviwill be helpful to get more reviews on the first 2 patches to start with18:29
SumitNaiksatamhemanthravi: sure18:29
*** spzala has joined #openstack-meeting-318:29
SumitNaiksatamhemanthravi:  i do see fw.sh in the integration job logs, so good18:30
SumitNaiksatamhemanthravi: one issue i am seeing right away is that the tests are leaving some service_profiles undeleted, not sure if the delete failed, or the test failed to delete18:31
SumitNaiksatambase_mode_lb and base_mode_fw18:31
hemanthraviwill check on that18:32
SumitNaiksatamhemanthravi: thanks, and for the update in general18:32
*** VW has joined #openstack-meeting-318:32
SumitNaiksatamany questions for hemanthravi on NFP?18:33
SumitNaiksatamhemanthravi: okay thanks much!18:33
SumitNaiksatam#topic Bugs18:33
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:33
SumitNaiksatamsongole: hi18:33
*** amotoki has joined #openstack-meeting-318:34
songoleSumitNaiksatam: hi18:34
*** hemanthravi has quit IRC18:34
songoleI filed a few bugs yesterday18:34
SumitNaiksatamwe were discussing a bunch of bugs over the past few days18:34
SumitNaiksatamsongole: yes18:34
songoleSome of them I believe are high priority18:34
SumitNaiksatamany particular ones you want to discuss here, get input from the team?18:34
SumitNaiksatamsongole:  okay, which ones?18:34
SumitNaiksatamif you can copy-paste the launchpad link, the bot will do the rest18:35
songolehttps://bugs.launchpad.net/group-based-policy/+bug/158810918:35
openstackLaunchpad bug 1588109 in Group Based Policy "APIC mapping: Neutron router not created for E <--> W L3 policy" [Undecided,New]18:35
*** david-lyle has quit IRC18:35
SumitNaiksatamsongole:  that is driver specific, lets check with ivar-lazzaro18:35
songoleok18:36
ivar-lazzaroyeah that is APIC specific18:36
ivar-lazzarodon't think RMD has the same issue18:36
SumitNaiksatamivar-lazzaro: right18:36
SumitNaiksatamivar-lazzaro: what do you think is a reasonable solution here?18:36
ivar-lazzarowhat happens is that in apic mapping Neutron routers are created only when L3Ps are attached to ES18:37
SumitNaiksatamivar-lazzaro: right18:37
*** ddieterly[away] is now known as ddieterly18:37
ivar-lazzaroI think that we could create a "default" one18:37
*** kzaitsev_mb has quit IRC18:37
ivar-lazzarothat is never attached to a ES18:37
SumitNaiksatamivar-lazzaro: okay18:37
ivar-lazzarobut I want to check with the author of the first patch here, to see if there's a compelling reason for not doing it18:37
SumitNaiksatamivar-lazzaro: makes sense18:38
SumitNaiksatamivar-lazzaro: should we assign this to you for now investigation (and you can later punt it to someone else if required)?18:38
SumitNaiksatam*for investigation18:38
*** amotoki has quit IRC18:39
ivar-lazzarosure18:39
SumitNaiksatamivar-lazzaro: okay thanks18:39
SumitNaiksatamsongole: whats next on your list?18:39
songoleSumitNaiksatam: if it is an easy fix, can we prioritize it?18:39
SumitNaiksatamsongole: okay, in LP medium priority is default for driver patches18:40
SumitNaiksatamdefault -> convention18:40
songoleSumitNaiksatam: ok18:40
SumitNaiksatamsongole: we can follow up offline to make progress on this18:40
songolehttps://bugs.launchpad.net/group-based-policy/+bug/158809918:40
openstackLaunchpad bug 1588099 in Group Based Policy "Neutron fip association doesn't work with service chains" [Undecided,New]18:40
songoleWe discussed this offline and I summarized the discussion in the bug18:41
ivar-lazzarosongole: not sure that should be a bug, since this was known at the time we made the implementation18:41
ivar-lazzarosongole: also, that is broken for explicit association only18:41
ivar-lazzarosongole: but yeah, we need to find a solution anyways18:42
songoleivar-lazzaro: right18:42
songolehttps://bugs.launchpad.net/group-based-policy/+bug/158810718:42
openstackLaunchpad bug 1588107 in Group Based Policy "Automate allocation of fip and static ip for loadbalancer vip" [Undecided,New]18:42
SumitNaiksatamsongole: anyone in your team can work on the suggestion made by ivar-lazzaro with retrieving all routers, and finding the candidate router from that based on the reachability?18:42
songoleSumitNaiksatam: I will check.18:43
SumitNaiksatamsongole: i am referring to 158809918:43
*** sarob has joined #openstack-meeting-318:43
*** ddieterly has quit IRC18:43
songolegot it.18:44
*** yamamoto has joined #openstack-meeting-318:44
songole1588107 is about the same provider being used externally (n-s) and internally (e-w)18:45
songoleI need to check the behavior of ip-single nat-pool option18:45
SumitNaiksatamsongole: so for 1588107 what is your expectation?18:45
*** jmckind has joined #openstack-meeting-318:46
*** galstrom is now known as galstrom_zzz18:47
*** vhoward has quit IRC18:47
songoleThe intent should be to allocate fixed ip and assign floating ip to it18:47
SumitNaiksatamsongole: so per our discussion, i am finding it hard to understand “2n'd option above just creates a floating IP which the consumer could directly use. It doesn't allocate a local ip.”18:48
SumitNaiksatamsongole: as you said, it will be helpful if you can confirm that is indeed the case18:48
songoleokay18:48
SumitNaiksatamsongole: thanks18:48
songoleSumitNaiksatam: I have another bug which I haven't filed yet18:49
SumitNaiksatamsongole: if that was not the case, and the local ip was getting allocated, this is not a bug any more?18:49
ivar-lazzarosongole, SumitNaiksatam: the local IP is not allocated?18:49
songoleSumitNaiksatam: I will verify it18:49
ivar-lazzaromeaning that there's no fixed IP in the LB VIP port?18:49
SumitNaiksatamivar-lazzaro: yes thats the claim, and i am not sure how that can be the case18:50
songoleivar-lazzaro: that is my understanding based on the code.18:50
ivar-lazzaroThat would be a huge bug, probably in Neutron too18:50
ivar-lazzaroyeah let's verify that :D18:50
songoleSumitNaiksatam: I believe proxy ptg is created by admin for the end user18:51
SumitNaiksatamsongole: admin can create proxy ptg18:52
songoleSumitNaiksatam: this is regarding a check to not allow cross tenant resource creation. this check only exists for neutron18:52
songoleand not for apic18:52
songolebecause of it, a non admin tenant will not be able to launch service chain on neutron18:52
SumitNaiksatamsongole: finding it difficult to grok, perhaps you can file the bug, and it might be easier to explain there?18:53
songoleok18:53
songolehttps://github.com/openstack/group-based-policy/blob/master/gbpservice/neutron/services/grouppolicy/drivers/resource_mapping.py#L37118:53
*** yamamoto has quit IRC18:53
ivar-lazzarois it because of _reject_cross_tenant_ptg_l2p ?18:54
songoleivar-lazzaro: yes18:54
songoleI don't see a similar check for apic_mapping driver18:54
*** MeganR has joined #openstack-meeting-318:55
songolehttps://github.com/openstack/group-based-policy/blob/master/gbpservice/neutron/services/grouppolicy/drivers/cisco/apic/apic_mapping.py#L80618:55
*** dc_mattj has joined #openstack-meeting-318:55
*** kzaitsev_mb has joined #openstack-meeting-318:55
*** cartik has joined #openstack-meeting-318:56
ivar-lazzarosongole: we need to see the implications of doing that18:56
songoleivar-lazzaro: is there a specific reason behind that validation?18:56
songoleivar-lazzaro: validation is required but it can be relaxed for admin?18:57
ivar-lazzarosongole: maybe it could18:57
ivar-lazzaroso you want the subnet to be owned by the admin18:57
*** shamail has joined #openstack-meeting-318:57
ivar-lazzaroand the network by the tenant18:57
ivar-lazzaroif Neutron allows that, I don't see why not18:58
*** numans has quit IRC18:58
songoleivar-lazzaro: is it not an issue with apic mapping?18:58
SumitNaiksatamsongole: may be we can take this offline, you can create the bug18:59
songoleSumitNaiksatam: ok18:59
ivar-lazzarosongole: APIC mapping has his own neutron driver18:59
SumitNaiksatamwe have to yield to the next meeting in a few seconds18:59
SumitNaiksatamthanks all for joining!18:59
ivar-lazzaroadieu!19:00
SumitNaiksatambye!19:00
songolebye19:00
SumitNaiksatam#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Thu Jun  2 19:00:13 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-06-02-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-06-02-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-06-02-18.00.log.html19:00
rkukurabye19:00
*** rkukura has left #openstack-meeting-319:00
shamail#startmeeting nonatc19:00
openstackMeeting started Thu Jun  2 19:00:42 2016 UTC and is due to finish in 60 minutes.  The chair is shamail. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: nonatc)"19:00
openstackThe meeting name has been set to 'nonatc'19:00
*** songole has quit IRC19:00
*** tbachman has left #openstack-meeting-319:00
shamailHi everyone!  Who’s here for the AUC recognition meeting?19:00
maishskshamail: we should change that…. :)19:01
maishsko/19:01
MeganRo/19:01
shamailmaishsk: I will… I need to talk to tonyb first to see if log migrations are possible or whether we should change meeting info but keep “nonatc” as folder name19:01
shamail#chair maishsk19:01
openstackCurrent chairs: maishsk shamail19:01
*** dc_mattj has quit IRC19:01
shamailHi MeganR19:01
shamailWe offended dc_mattj19:01
maishskWhy?19:02
shamailIm just kidding :)  He just left the room (computer went to sleep)19:02
MeganRwe weren't entertaining enough!19:02
shamailthat must be it19:02
*** dc_mattj has joined #openstack-meeting-319:02
shamailhi dc_mattj19:02
dc_mattjevening19:02
shamailSo the agenda for today is small19:03
shamail#link https://wiki.openstack.org/wiki/AUCRecognition19:03
maishskYEY!19:03
maishskbeen a long day at the #OpenStackIL event19:03
dc_mattjlooked good19:03
shamailNice!  Good event?19:03
shamailWe’ll be posting a SuperuserTV video with interviews from the event by tomorrow19:03
dc_mattjorganised by the guys from Gigaspaces I think ?19:04
dc_mattjthey do all their OpenStack testing against our platform19:04
shamailnice19:04
shamailfirst agenda item...19:04
shamail#topic Updates on action items from 5/2619:04
*** openstack changes topic to "Updates on action items from 5/26 (Meeting topic: nonatc)"19:04
shamailThere were two action items from last week19:04
shamail1) rename group from non-atc to AUC19:04
dc_mattjnice :)19:05
shamailI’ve made progress on this one (wiki has changed, meeting reminders changed) but still have some work left19:05
shamailI will put in a patch to change the meeting information on eavesdrop19:05
shamailI want guidance from Tony Breeds as to whether it is possible to migrate logs or whether we can change meeting info but use “nonatc” to start meetings19:06
shamailif we change the meeting ID then historical logs will be more difficult to find19:06
*** cartik has quit IRC19:06
shamailanother workaround might be to change meeting ID but still include a link to the nonatc meeting logs in the wiki and put a disclaimer (e.g. for logs prior to 6/6, click here)19:07
maishskI would hope that they can be migrated19:07
shamailI hope to sort this out by next week19:07
dc_mattjsmall point I would think, we can always link19:07
shamailI hope so too maishsk but I’ve prepared a plan B just in case19:07
shamaildc_mattj: +119:07
maishskgood to know19:07
shamailthe other action item was19:07
shamail2) shamail: determine if ATC membership information is published anywhere (and, if so, what is published about them)19:07
shamailI saw your tweet maishsk (I was travelling so didn’t get a chance to reply) about the extra-ATC info in the governance repo19:08
maishskSo the info is definitely there19:08
shamailI think that addresses the question partially (e.g. extra ATC info is there) but I haven’t found a centralized ATC list anywhere19:08
shamailThe governance repo only shows extra-ATCs19:08
dc_mattjI've never seen a list like that either19:09
shamailI have emailed ttx to find out if they just run scripts to extract repo contributors or whether they post the aggregate results for ATC somewhere19:09
shamailTo be honest, I emailed him an hour ago so I probably won’t be able to provide an update until next week19:09
shamail:x19:09
maishskI stand corrected - it is only the extra ATC19:09
dc_mattjwe've always assumed stackalytics tells you19:10
dc_mattjalthough in Austin I learned not every commit gets you ATC now19:10
maishskthe ATC is not published publicly19:10
shamailI assumed they just run a script to find project contributors and leverage that19:10
shamailtrue dc_mattj19:10
maishskdc_mattj: you mentioned that last week - where / when was that decided?19:10
dc_mattjmaishsk, it was mentioned a few times in different sessions19:10
shamailIt was mentioned at the board meeting although I am not sure where it stands from an implementation perspective19:10
maishskI have not seen any communication - or reviews / decisions on that19:11
shamailcame up in the AUC recognition session too19:11
dc_mattjalthough never clarified properly, it was always to do with the issue of people committing typo fixes to comments to get ATC19:11
maishsk:)19:11
dc_mattjnot something any of my team have ever done, but apparently it happens19:11
shamailmaishsk: technically the OpenStack Foundation covers that benefit so it might not go through an actual governance review19:11
*** VW has quit IRC19:11
maishskfoundation covers the fact of a free pass19:12
shamailyep, they fund it19:12
dc_mattjit wasn't ever clear to me who was making that decision19:12
dc_mattjmaybe the PTL's ?19:12
*** VW has joined #openstack-meeting-319:12
maishskbut if someone has ATC status or not - they are not the same19:12
shamailI think OpenStack Foundation itself19:12
maishskthey are very different19:12
shamailI think people still qualify for ATC (if I am not mistaken)19:12
dc_mattjthat's a big job to trawl through every commit and decide worth19:12
shamailit was the free pass that was being adjusted?19:12
* maishsk is all for getting rid of the free pass19:12
MeganRI think they were trying to work around the one commit only to get a free pass19:13
shamailI can try to find someone who is more in-tune with the topic and see if they can recommend how we discuss this in the community19:13
maishskor at least making the bar a lot higher19:13
shamailMeganR: +119:13
shamailI think they also want people that are invested voting for TC as well19:13
shamailSo that was my update on the action items.. I give myself a C-19:14
dc_mattjmaishsk, I'm not sure on that - contributions are the key metric of any OS project, so getting people to contribute is vital19:14
shamail:(19:14
shamailI will make more progress by next week, sorry!19:14
dc_mattjmaybe comment typos shouldn't count though ;)19:14
shamailOkay to move to next topic?19:14
dc_mattjshamail, +119:14
maishsk+119:14
MeganR+119:14
shamailWanted to revisit some of the metrics that we deferred last week19:14
shamail#topic Metrics for WG participants (MeganR)19:15
*** openstack changes topic to "Metrics for WG participants (MeganR) (Meeting topic: nonatc)"19:15
MeganRSo, naturally I have more questions than answers at the moment.  For teams not using IRC, the team leads can enter the “meeting participant” information somewhere – to be determined.  If we go this route, then we need to specify what information needs to be entered – Name, Email, IRC Handle . . .19:15
MeganRHowever, it wasn’t ruled out to have people log into IRC, might help people get more comfortable with it.  If we go this route, is there somewhere that people could “log in” – otherwise, I don’t know if we would bump or interrupt meetings just to have individuals log in.19:15
MeganRI need guidance on which avenue we want to pursue19:15
shamailMeganR: One of the options that was discussed at the summit was to see if the foundation would let us clone the track chair tool19:15
shamailso that WG chairs could use it to manage their working groups19:15
dc_mattjdefinitely needs a low touch tool19:16
shamailUse the same tool but apply it to WG membership19:16
dc_mattjotherwise it's  just way too much work for people to do19:16
MeganRyes, as low touch as possible19:16
dc_mattjthe IRC thing is a bigger issue though I think19:16
maishskSo I think the first option is low touch enough19:16
MeganRshamail - would Kendall be the best person to reach out to about cloning that tool?19:17
shamailThis “re-using track chair tool” would be intermediate touch for WG chairs (membership doesnt change often) and no-touch for WG members19:17
dc_mattjthere's a lot of new working groups where IRC is alien to them - like Scientific WG19:17
maishskWG leads - fill out the active participants19:17
dc_mattjnot sure how relevant the track chair tool is here though19:17
shamailMeganR: I think Kendall with a CC to Tom would be a good place to start… he would have context19:17
dc_mattjI can't see the re-use19:17
shamaildc_mattj: It would not be full re-use19:17
shamailin the track chair tool, there is membership information for each tracks chairs19:18
MeganRok, I will reach out - we need a "database" for the WG leads to enter this info19:18
shamailin this use, think of track=WG and chair membership=WG membership19:18
dc_mattjtool IMO would need to be something where after a meeting, the chair could tick boxes to say who the contributors were19:18
dc_mattjbut if you mean the same kind of concept as the track chair app, then I agree19:18
shamailsimilar concept19:18
shamailgood way to phrase it dc_mattj19:18
dc_mattj+1 then19:18
maishskdc_mattj: or drop a text file with the names of the participants19:18
MeganRshamail - I am going to cc you on that email - in case there needs to be clarification19:19
dc_mattjmaishsk, that already sounds like too much friction19:19
shamailSounds good19:19
* maishsk thinks he is becoming to fluent in the ways of OpenStack … :(19:19
maishsktoo*19:19
shamailDo we think this will be a massive amount of folks?  Could we simply ask WG chairs once a cycle (near end) to give us a list of people who are active?19:19
dc_mattjideal would be that everyone uses the same comms mechanism and it's all automagically audible19:19
shamaildc_mattj: I agree, this could be done manually but I fear it might become a burden19:20
dc_mattjshamail, maybe. As a community of engineers we're always guilty of overthinking the problem19:20
shamailWG count continues to grow as do members19:20
MeganRI don't feel that it is a huge list - but would prefer they enter the info after each meeting, especially if there are different leads for the meetings19:20
shamailMeganR: Could you pursue an option 1 and option 2 recommendation?19:20
*** jlopezgu has left #openstack-meeting-319:20
dc_mattjI'm always warning my engineers not to over-engineer, but we do like perfection ;)19:20
maishskAnd also this is a way to track active participation19:20
dc_mattjthis is a small WG thought right ?19:21
MeganROption 1 - enter info after each meeting, Option 2 - enter info monthly ?19:21
dc_mattjemerging stuff like scientific and NFV are bigger, and potentially very big ?19:21
maishskdc_mattj: there are a number of WG19:21
shamailMaybe option 1: tooling to automate collection, option 2: manual methods19:21
MeganRThis is for WG that are not using IRC for their meetings19:21
maishskProduct and Enterprise are probably larger19:21
dc_mattjso we should also probably think about how many WG are NOT using IRC19:22
shamailWe already have a script to extract info for WGs using IRC (https://github.com/openstack/uc-recognition/blob/master/tools/get_active_wg_members.py)19:22
MeganRshamail - sorry, I am not following, are these the options to present to Kendall and Tom or to the WG leaders?19:22
shamaildc_mattj: +1, that would give us a good idea of whether the effort is worth it19:22
dc_mattjif the mainstream are all using IRC, then there's no point in overthinking the minority19:22
shamailMeganR: These are options that our AUC WG should recommend at the end of milestone-3 on how to account for WG members19:23
dc_mattjset the standard as IRC, then allow some manual process for anyone not using it ?19:23
MeganRahh - got it - ok, thank you19:23
maishskdc_mattj: sounds like a plan :)19:23
MeganRdc-mattj +119:23
*** shwetaap has quit IRC19:23
dc_mattjnot saying IRC is perfect, but it is fairly standardised and we have automation tooling19:23
shamailMeganR: You are determining now that we want to include WG members as AUC, how do we identify them.19:23
*** shwetaap has joined #openstack-meeting-319:23
dc_mattjchange from IRC is under the control of the WG chairs19:24
MeganRI have been focusing on the ones listed through the User Committee19:24
dc_mattjso if they change it, then maybe they need to work out how to recognise contribution ?19:24
shamailMeganR: +1, that is what we chose as criteria for being considered “official WGs"19:24
*** david-lyle has joined #openstack-meeting-319:24
shamailThey have to have information on the UC wiki19:24
MeganRyes - focusing there, and then if we need to expand in the future we can19:25
dc_mattjwhere does the official WG list live ?19:25
shamaildc_mattj: I am worried that if we leave the designation entirely unstandardized then questions on why someone was considered active versus not could arise19:25
shamail#link https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee19:26
shamailNear the bottom dc_mattj19:26
dc_mattjshamail, not sure what that means ? Can you explain ?19:26
dc_mattjin terms of contribution ?19:26
maishskdc_mattj: So I think that is part of Milestone #519:27
shamaildc_mattj: I was trying to say that we should be able to give criteria to WG chairs on how they should identify who they consider “active”.. if we let each WG determine (without publicly listing the criteria) then it could raise questions on why someone was “active” and someone else was deemed “not actove"19:27
shamailactive*19:27
dc_mattjYeah I get that. I think I'm saying that the mechanisms that exist right now in terms of number of lines during a meeting etc are probably good enough given the vast majority use IRC19:28
shamailmaishsk: +1, milestone 519:28
dc_mattjand for those that don't use IRC, we could have a fairly manual process for now19:28
shamaildc_mattj: ah, got it.19:28
dc_mattjalthough admittedly I don't know how many don't use IRC19:28
*** Sukhdev has joined #openstack-meeting-319:28
shamailOnly ones I know are enterprise.. does scientific?19:28
MeganRI was thinking of keeping it really simple for the first round - if someone is routinely attending WG meetings, they are considered active.  We can see what number that brings - ad then possibly refine it.19:29
shamailMeganR: +119:29
dc_mattj+119:29
dc_mattjexactly19:29
shamailAnything else on this topic MeganR?19:29
maishsk+119:29
dc_mattjuse what metrics we have right now and don't overthink19:29
MeganRNope - I'm good19:29
shamailThanks19:29
dc_mattjassume everyone is using IRC, and if they aren't then the WG chair has to provide that metric somehow19:29
shamail#topic Metrics for Ops meetup moderators (maishsk)19:29
*** openstack changes topic to "Metrics for Ops meetup moderators (maishsk) (Meeting topic: nonatc)"19:29
dc_mattjlol19:30
maishskSo I reached out to Tom - and got this19:30
dc_mattjsorry, was already ahead of myself19:30
maishsk#link https://docs.google.com/spreadsheets/d/1EUSYMs3GfglnD8yfFaAXWhLe0F5y9hCUKqCYe0Vp1oA/edit#gid=80351347719:30
shamailYep, that has all moderators19:30
maishskIt is an excel sheet with the list of all the moderators for all the moderators.19:30
dc_mattjI also talked to Tom about this19:30
shamaildc_mattj: Will the new meetup admin WG keep the same spreadsheet or do you plan to change where moderator info is kept?19:31
dc_mattjnot sure yet19:31
dc_mattjI am VERY familiar with this spreadsheet19:31
maishskSo we can get all the info from there19:31
dc_mattjbut it is a bit like to mouldy old bit of paper kept under your bed ;)19:31
shamaillol19:31
maishskThe question is just about ‘the how’19:31
maishsk;)19:31
dc_mattjagain, I think for this let's not overthink19:31
dc_mattjthe amount of folks who fall into this category is fairly small19:32
dc_mattjand easily manually treatable19:32
maishskcopy + paste a list - sounds good19:32
dc_mattjtreatable19:32
dc_mattjaargh19:32
shamailmaishsk: +119:32
dc_mattjautocorrect19:32
shamaillol19:32
dc_mattjwe can do it manually19:32
shamailtreatable19:32
dc_mattj;)19:32
maishskLOL19:32
dc_mattjcreate - able19:32
shamailgot it, treatable19:32
shamail:P19:32
dc_mattjLOL19:32
maishskdc_mattj has found a way to outsmart his computer :)19:32
shamailI agree19:32
dc_mattjI think we're agreeing19:33
shamailthe list has everything needed and its small enough to just copy/paste19:33
dc_mattjyup19:33
dc_mattj+119:33
shamailAnything else maishsk?19:33
maishskOn this topic - nope19:33
shamail#topic Review next steps19:33
*** openstack changes topic to "Review next steps (Meeting topic: nonatc)"19:33
shamailSo we’ve made good progress in identifying our data sources and how we might interface with them19:34
shamailThe next step would be to document our results from this milestone19:34
shamailI would also like to propose switching milestone 4 and 519:34
shamailmilestone 5 feels like a good continuation of mileston 319:34
*** amotoki has joined #openstack-meeting-319:34
shamailit would completely close out the who, what, and how19:34
dc_mattj+119:34
*** iyamahat has quit IRC19:35
*** sdake has quit IRC19:35
shamailWe can move to the exceptions discussion (e.g. review board) after establishing the norm19:35
dc_mattjI'd also say the review board for self nominated is the UC19:35
maishskshamail - that is very smart19:35
shamailAgree/disagree to switch?19:35
dc_mattj+119:35
dc_mattjagree19:35
maishsk+1 agree19:35
*** SumitNaiksatam has quit IRC19:36
shamaildc_mattj: I agree but would want to check with them first to see if they are fine with the workload19:36
MeganRagree19:36
shamailor if they want to delegate19:36
dc_mattjshamail, I suspect the workload is a tiny edge case19:36
shamaildc_mattj: +1, it should also get smaller each cycle19:36
dc_mattjI can't believe someone would not fall into any other category, and not be known by the UC19:36
shamailtrue19:36
shamailThanks everyone19:37
shamail#Agree we will change ordering and cover milestone 5 (now known as milestone 4) first and then milestone 4 (now known as milestone 5)19:37
dc_mattjlol19:37
shamailThat is probably the most complex way I could’ve written that sentence19:37
dc_mattjthat's not going to get confusing19:37
shamaillol19:38
*** sdake has joined #openstack-meeting-319:38
*** ociuhandu has quit IRC19:38
shamailWe know what it means!19:38
maishskand it should have been # agreed : )19:38
dc_mattjthis is all getting a bit Life of Brian19:38
shamailhaha19:38
dc_mattjfor any of you with a Monty Python interest19:38
maishskWe are all individuals19:38
MeganRfor this week - remind me again next week!19:38
shamaillol19:38
maishskWith a shrubbery19:38
*** amotoki has quit IRC19:39
MeganRlol19:39
maishskSo if there is nothing else on the agenda19:39
maishskI would like to share two things19:39
*** openstack has joined #openstack-meeting-319:42
*** ChanServ sets mode: +o openstack19:42
shamail#topic open19:42
shamailmaishsk, here?19:42
maishskfrom today’s OpenStackIL event - gave a presentation about the pain I (personally) feel regarding the exclusion of non-code contributors to OpenSTack19:42
maishsk*I gave19:42
shamailAre the slides online?19:42
maishskI must say that the reactions that I received were quite encouraging - and the direction of AUC was well received19:43
*** sdake has quit IRC19:43
dc_mattjmaishsk, +119:43
maishskNot yet - but I can put them up somehwere19:43
maishskthe message got through19:43
MeganRwow - that's great19:43
maishskwhich brings me to my second point19:43
shamailGreat to hear, I think people appreciate that progress is being made.19:43
maishskI had a chat with mordred and flaper87 who both there at the event19:44
maishskafter the session19:44
maishskAnd it was implied that we can easily make use of the extra ATC for pracitcally anyone who would like to ask for it19:45
maishskall we need to do is compile a list.19:45
dc_mattjI'm not sure that's the point though19:45
maishskcompletely not19:46
dc_mattjif I can add something, I've definitely felt my non-code contributions have been valued - although admittedly most of the big stuff I've done has co-incided with the big push in this area.19:46
shamailmaishsk: this was brought up in the Austin session as well.  The majority in the room wanted to be recognized and not simply leverage an existing method to add us to the existing criteria19:46
maishskdc_mattj: I completely agree19:46
maishskwith both of you.19:46
shamailthe goal, in the room, was to change the definition and not just obtain ATC benefits19:46
*** lpetrut has joined #openstack-meeting-319:46
dc_mattjshamail, +119:46
dc_mattjand I don't think it's even about free tickets19:46
shamailagreed19:47
dc_mattjlike all of us in open communities it's about feeling valued19:47
MeganR+119:47
maishskbut what was encouraging to me was the acceptance from the other side of the fence - that our side does need recognition19:47
MeganRthat is great!19:47
shamailmaishsk: +119:47
dc_mattj+119:47
maishskand the steps that we have started are appreciated on both sides19:47
shamailGlad to hear that19:48
shamailI would definitely like to see a copy of your slides once you get a chance to upload them!19:48
dc_mattjEdgar is also doing a sterling job in terms of trying to put the UC on the same footing as the TC19:48
dc_mattjand the rest of the UC19:48
* maishsk wanted to add one more thing - but for the life of him - he can’t remember what it was. 19:48
dc_mattj;)19:48
dc_mattjlol19:48
maishskOh yeah19:48
dc_mattjis it that we should rename ourselves to the Peoples Front ?19:49
MeganRlol19:49
maishskEdgar. I assume that you have all seen the document that he has been working on?19:49
dc_mattjyup19:49
shamailYes19:49
MeganRnope - but I am really behind on email19:49
maishskone sec #link https://docs.google.com/document/d/1QmLOeseAkjBWM_TXsUeKBErNaSHnuZp81II0T71ARfo/edit19:50
dc_mattjpersonally I think this is an important document19:51
MeganRthank you, but unfortunately I can not open that on my work network - will review later19:51
* maishsk wonders what kind of place MeganR works in that blocks Google Docs :) 19:51
shamailemagana made good progress on the sub-domain topic (where it will live) as well this week19:51
MeganRWalmart  :)19:51
maishskLOL19:51
dc_mattjshamail, good19:52
dc_mattjbecause I think it needs to be hosted there19:52
dc_mattjfor us as a community19:52
emaganasorry, I haven't followed the conversation.19:52
dc_mattj:)19:52
emaganaAnything needed from me?19:52
maishskas equals19:52
shamail#link http://lists.openstack.org/pipermail/openstack-tc/2016-June/001210.html19:52
dc_mattjhello edgar :)19:52
emaganaHi dc_mattj19:52
shamailno sir, keep doing great work emagana19:52
maishskof the People’s Front19:52
dc_mattjwe were just talking about what good work you are doing sir19:52
shamaillol19:52
maishsk+119:53
*** mbound has quit IRC19:53
shamailAny other topics for today?19:53
shamailAlrighty then19:53
shamailThanks for joining everyone, see you next week!19:53
MeganRBye!19:53
dc_mattjgood to talk :)19:54
emaganaN.p.19:54
shamail#endmeeting19:54
shamailI think bot is down19:54
*** VW has joined #openstack-meeting-319:54
maishskor you busted the bot :)19:55
shamail:[19:55
maishskfor those who wanted the links to the slides19:56
maishsk#link http://www.slideshare.net/maishsk/the-tale-of-2-openstack-contributors19:56
*** jlopezgu has joined #openstack-meeting-319:57
*** david-lyle has quit IRC19:57
shamailthanks19:58
*** shamail has left #openstack-meeting-319:58
dabukalamo/20:00
* dabukalam got his timezone confused20:00
*** galstrom_zzz is now known as galstrom20:04
*** dc_mattj has quit IRC20:04
*** spzala has quit IRC20:08
*** Sukhdev has quit IRC20:09
*** Sukhdev has joined #openstack-meeting-320:09
*** shwetaap has quit IRC20:11
*** Sukhdev has quit IRC20:13
*** iyamahat has joined #openstack-meeting-320:13
*** tqtran has joined #openstack-meeting-320:14
*** spzala has joined #openstack-meeting-320:14
*** ociuhandu has joined #openstack-meeting-320:18
*** shwetaap has joined #openstack-meeting-320:19
*** spzala has quit IRC20:19
*** jmckind has quit IRC20:19
*** emagana has quit IRC20:24
*** jmckind has joined #openstack-meeting-320:26
*** banix has quit IRC20:29
*** emagana has joined #openstack-meeting-320:30
*** emagana has quit IRC20:30
*** emagana has joined #openstack-meeting-320:30
*** kzaitsev_mb has quit IRC20:31
*** spzala has joined #openstack-meeting-320:33
*** piet_ has joined #openstack-meeting-320:34
*** amotoki has joined #openstack-meeting-320:35
*** jlopezgu has left #openstack-meeting-320:36
*** amotoki has quit IRC20:40
*** tonytan4ever has quit IRC20:41
*** MeganR has quit IRC20:50
*** mickeys has joined #openstack-meeting-320:50
*** julim has quit IRC20:53
*** mbound has joined #openstack-meeting-320:53
*** kzaitsev_mb has joined #openstack-meeting-320:54
*** mickeys has quit IRC20:55
*** mickeys has joined #openstack-meeting-320:55
*** mbound has quit IRC20:58
*** lblanchard has quit IRC21:02
*** kzaitsev_mb has quit IRC21:03
*** iurygregory_ has quit IRC21:03
*** baoli_ has quit IRC21:05
*** kzaitsev_mb has joined #openstack-meeting-321:12
*** shwetaap has quit IRC21:17
*** kzaitsev_mb has quit IRC21:19
*** claudiub|2 has quit IRC21:21
*** yamahata has quit IRC21:21
*** toddjohn has quit IRC21:24
*** kzaitsev_mb has joined #openstack-meeting-321:25
*** rtheis has quit IRC21:25
*** ShillaSaebi has joined #openstack-meeting-321:27
*** shwetaap has joined #openstack-meeting-321:30
*** ivar-laz_ has joined #openstack-meeting-321:30
njohnstono/21:31
ShillaSaebihello21:32
darrenchi!21:32
ShillaSaebi#startmeeting arch-ops-guide21:32
openstackMeeting started Thu Jun  2 21:32:42 2016 UTC and is due to finish in 60 minutes.  The chair is ShillaSaebi. Information about MeetBot at http://wiki.debian.org/MeetBot.21:32
njohnston#endmeeting21:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:32
*** openstack changes topic to " (Meeting topic: arch-ops-guide)"21:32
openstackThe meeting name has been set to 'arch_ops_guide'21:32
ShillaSaebihello all21:32
njohnstonoh good, glad that worked, since the last meeting had not ended properly21:33
ShillaSaebican we get a roll call for the ops/arch guide meeting:21:33
ShillaSaebioh good!21:33
njohnstono/21:33
darrencdo you need to end it first?21:33
darrenco/21:33
ShillaSaebii think were ok21:33
darrenccool21:34
ShillaSaebiso just the 3 of us aye?21:34
*** ivar-lazzaro has quit IRC21:34
darrencI guess so :)21:34
ShillaSaebiok21:34
ShillaSaebiwell lets go ahead and get started21:34
ShillaSaebi#topic Ops Guide21:34
darrencI think Shaun is moving countries21:34
*** openstack changes topic to "Ops Guide (Meeting topic: arch-ops-guide)"21:34
ShillaSaebioh wow really21:34
darrencSouth Africa -> Germany21:35
ShillaSaebioh right i remember he said he was going to Germany21:35
ShillaSaebiSo we still need more people to find and look for content that needs to be updated  #link https://etherpad.openstack.org/p/ops-guide-reorg21:35
*** amotoki has joined #openstack-meeting-321:36
darrencyeah so far it's just be me and tom21:36
darrencbeen*21:36
darrencI'm thinking of pushing up a patch with those changes21:36
darrencand hopefully that will get some response21:37
ShillaSaebiok21:37
darrencbut yeah, some ops ppl to pick a chapter or section and review it would be great21:37
ShillaSaebiDevon and Vic are interested in working on this too21:37
ShillaSaebiDevon may be joining us later today21:38
ShillaSaebiI can poke them tomorrow21:38
njohnstonVic sends his regrets, but is at a doctor's appointment21:38
darrencthat would be great, thanks21:38
*** katomo has joined #openstack-meeting-321:39
ShillaSaebiok21:40
darrencso any thoughts on getting more ops ppl to help?21:40
ShillaSaebii think maybe start joining their meetings21:40
ShillaSaebiwe've tried ML21:40
ShillaSaebiwe've tried other methods that didn't seem to make much traction21:41
njohnstonperhaps talking about docs in meetings like the ansible and puppet meetings21:41
darrencmailing lists only seems good for informing21:41
njohnstonthose are very ops-dominated21:41
ShillaSaebithats a good idea21:42
njohnston"Hey you're working on a puppet module update to configure haproxy, would you mind also checking the ops guide chapter XX to make sure it's up to date?"21:42
*** amotoki has quit IRC21:42
ShillaSaebithats a great idea21:42
darrenc+121:42
katomo+121:42
ShillaSaebihi katomo21:42
katomohi ShillaSaebi21:43
darrencNeed to checking ops meeting times, but I think they are held when I'm asleep21:43
ShillaSaebii wonder if there is an APAC one?21:44
darrencPerhap we can coordinate as a team who will go to what meeting21:44
*** kzaitsev_mb has quit IRC21:44
ShillaSaebithat works21:45
ShillaSaebidoes someone want to maybe gather the list of meetings first that are ops centric21:45
njohnston+1 coordination21:45
ShillaSaebithen we can look at the times and see who can go to what21:45
darrencI can do it21:46
njohnstonperhaps that can be collated and arranged via email21:46
darrencYep, I'll send out an email21:46
ShillaSaebiyeah email works21:46
ShillaSaebiok next thing21:47
ShillaSaebiSourcing enterprise ops documentation21:47
ShillaSaebiso we have a wiki filled with docs21:47
ShillaSaebinot really cleaned up21:47
ShillaSaebii can dump them somewhere as long as we don't put them up as official docs or anything. We need to really revise them and clean them up before putting them anywhere21:47
darrencI assume it has enterprise specific information in it?21:48
njohnstonbe sure to look at wiki docs with the coming reorganization in mind: http://lists.openstack.org/pipermail/openstack-dev/2016-June/096481.html21:49
*** ivar-laz_ has quit IRC21:49
*** ivar-lazzaro has joined #openstack-meeting-321:49
*** kzaitsev_mb has joined #openstack-meeting-321:50
*** spzala has quit IRC21:51
ShillaSaebiok21:51
ShillaSaebiyeah enterprise specific info21:52
ShillaSaebibut we can clean that up21:52
darrencI'm ok with it being dumped somewhere secure as long there is not company sensitive information in it21:52
darrencno*21:52
ShillaSaebiok21:52
ShillaSaebii can do google docs or something21:52
ShillaSaebiill work on that tomorrow21:52
darrencespecially if there are other team members from other companies21:52
darrenc*cough*21:53
darrenc:)21:53
katomogood21:53
ShillaSaebiok :D21:53
*** jmckind has quit IRC21:53
ShillaSaebiyeah sounds good to me21:53
darrencthanks, that would be great21:53
ShillaSaebiok next thing to bring up21:53
ShillaSaebiRevise Ops Guide spec with proposed content structure?21:53
ShillaSaebii think we already pretty much touched on this21:55
ShillaSaebiwith the new content structure that needs to be worked on21:55
*** yushiro has joined #openstack-meeting-321:55
*** yushiro has left #openstack-meeting-321:55
darrencWell I think the earlier point is removing old content21:55
darrencafter that, looking at the content structure with the arch guide in mind21:56
darrencso atm, I'm migrating the arch content in the ops guide to the arch guide21:57
*** galstrom is now known as galstrom_zzz21:57
darrencso content in each guide is segregated by what you want to do, rather than persona21:58
*** markvoelker has quit IRC21:58
darrencarch guide -> design a cloud21:59
*** kzaitsev_mb has quit IRC21:59
ShillaSaebiright21:59
darrencops guide -> deployment, maintain and trouble21:59
ShillaSaebiand operate21:59
ShillaSaebi:D21:59
darrencyep21:59
katomosounds reasonable to me21:59
ShillaSaebimakes sense21:59
darrenctroubleshoot*21:59
*** claudiub has joined #openstack-meeting-321:59
ShillaSaebiok22:01
ShillaSaebi#topic Arch Guide22:02
*** openstack changes topic to "Arch Guide (Meeting topic: arch-ops-guide)"22:02
ShillaSaebiWork items wiki page #link https://wiki.openstack.org/wiki/Architecture_Design_Guide_restructure_work_items22:02
ShillaSaebifor this section: migrate #link http://docs.openstack.org/ops-guide/architecture.htm content to the Arch Guide under the relevant sections22:02
ShillaSaebithe link should be updated22:02
darrencok, that was me22:03
darrencI've asked shaun to help populate the wiki page22:03
ShillaSaebigreat!22:03
*** megm has quit IRC22:03
ShillaSaebilgtm22:03
darrencand I'll some things to migrate the mitaka arch guide content as well22:04
darrencso some help with migration would be appreciated22:04
ShillaSaebinoted22:04
darrencSo I'm done one patch already https://review.openstack.org/#/c/324179/22:05
*** kzaitsev_mb has joined #openstack-meeting-322:05
*** tangchen has quit IRC22:05
ShillaSaebiawesome!22:05
darrencI've*22:05
katomoG!22:05
*** megm has joined #openstack-meeting-322:05
darrencprogress! :P22:06
*** tangchen has joined #openstack-meeting-322:06
ShillaSaebinice thank you darrenc22:07
*** shwetaap has quit IRC22:07
ShillaSaebiok lets move along22:07
ShillaSaebi#topic Open discussion22:07
*** openstack changes topic to "Open discussion (Meeting topic: arch-ops-guide)"22:07
ShillaSaebivolunteers volunteers volunteers!22:08
katomoyeah!22:08
ShillaSaebiSo we need volunteers to attend ops meetings and volunteers to identify outdated content or content to be removed #https://etherpad.openstack.org/p/ops-guide-reorg22:08
ShillaSaebiare there any other topics anyone wants to bring up22:08
*** shwetaap has joined #openstack-meeting-322:09
katomonothing from me22:10
darrencoh, anyone hear anything about the ops midcycle?22:10
ShillaSaebiSeattle?22:11
ShillaSaebiI think22:11
darrencoh really?22:11
darrencwhen?22:11
ShillaSaebiI think so but Im not 100% sure yet22:11
ShillaSaebinot sure of the date either22:11
ShillaSaebitheres a planning meeting though that goes on22:11
ShillaSaebiwe could probably eavesdrop it22:11
darrencok cool22:12
darrencsorry, coming back to the arch guide22:13
ShillaSaebisure22:13
*** banix has joined #openstack-meeting-322:13
darrenconce we have some work item to do, it might be useful to coordinate a chunk of time to focus on it22:14
darrencshaun suggested a series of one day sprints22:14
ShillaSaebiok22:14
katomogood22:14
ShillaSaebiyeah would rather see one day than 2-3 day allocations22:14
ShillaSaebii think it would work better that way22:14
ShillaSaebiagreed22:15
darrencwhich I thought is easier than a 2-3 day sprint22:15
darrencsnap22:15
ShillaSaebitrue eys22:15
ShillaSaebiyes*22:15
ShillaSaebihah22:15
ShillaSaebioh as far as the ops mid cycle goes: the next meeting is on:  ==> Tuesday, 14 of Jun at 1400 UTC[1] in #openstack-operators22:15
ShillaSaebifor the planning22:15
ShillaSaebiin case :)22:15
darrencah ok22:15
darrencthanks22:16
ShillaSaebiyw22:16
ShillaSaebianything else anyone wants to bring up?22:16
darrencit would be great to have another ops guide working session at the midcycle22:16
ShillaSaebiyes22:16
darrenclike at the Design Summit but longer22:16
ShillaSaebiyeah22:16
ShillaSaebiwe can plan around it once we know dates and location22:16
darrenc40 minutes wasn't a lot of time22:16
ShillaSaebiDevon from our team, is also part of the team for the ops midcycle planning22:17
ShillaSaebiIll sync with her on when the actual event is so we can plan something22:17
darrencwell the sooner it's planned, the greater the chance of international contributors attending22:17
ShillaSaebiyep!22:17
darrencoh great, thanks!22:18
ShillaSaebiok awesome, anything else?22:18
darrencthat's all from me22:18
ShillaSaebiok then! meeting adjourned22:18
ShillaSaebihave a good one!22:18
ShillaSaebi#endmeeting22:18
*** openstack changes topic to "Review next steps (Meeting topic: nonatc)"22:18
openstackMeeting ended Thu Jun  2 22:18:53 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/arch_ops_guide/2016/arch_ops_guide.2016-06-02-21.32.html22:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/arch_ops_guide/2016/arch_ops_guide.2016-06-02-21.32.txt22:18
openstackLog:            http://eavesdrop.openstack.org/meetings/arch_ops_guide/2016/arch_ops_guide.2016-06-02-21.32.log.html22:18
katomothanks, all22:19
*** katomo has quit IRC22:19
darrencthanks everyone!22:19
*** ShillaSaebi has quit IRC22:19
*** VW has quit IRC22:22
*** VW has joined #openstack-meeting-322:26
*** dimtruck is now known as zz_dimtruck22:29
*** VW has quit IRC22:35
*** njohnsto_ has joined #openstack-meeting-322:39
*** dedery_ has joined #openstack-meeting-322:43
*** njohnsto_ has quit IRC22:45
*** dedery has quit IRC22:47
*** dedery_ has quit IRC22:48
*** rbak has quit IRC22:49
*** lpetrut has quit IRC22:51
*** Adri2000 has quit IRC22:53
*** shwetaap has quit IRC22:54
*** Adri2000 has joined #openstack-meeting-322:54
*** markvoelker has joined #openstack-meeting-322:58
*** markvoelker has quit IRC23:03
*** emagana has quit IRC23:06
*** ociuhandu has quit IRC23:06
*** tonytan4ever has joined #openstack-meeting-323:06
*** ociuhandu_ has joined #openstack-meeting-323:06
*** iyamahat has quit IRC23:07
*** emagana has joined #openstack-meeting-323:15
*** pt_15 has quit IRC23:16
*** emagana has quit IRC23:19
*** david-lyle has joined #openstack-meeting-323:20
*** rbak has joined #openstack-meeting-323:27
*** zhurong has joined #openstack-meeting-323:36
*** mickeys has quit IRC23:36
*** mickeys has joined #openstack-meeting-323:37
*** amotoki has joined #openstack-meeting-323:39
*** zhurong has quit IRC23:40
*** mickeys has quit IRC23:41
*** mickeys has joined #openstack-meeting-323:41
*** amotoki has quit IRC23:44
*** mickeys has quit IRC23:46
*** mickeys has joined #openstack-meeting-323:47
*** vishwanathj has joined #openstack-meeting-323:49
*** mickeys has quit IRC23:51
*** kzaitsev_mb has quit IRC23:53
*** mickeys has joined #openstack-meeting-323:53
*** sdake has joined #openstack-meeting-323:54
*** sdake_ has quit IRC23:56
*** sdake has quit IRC23:57
*** sdake has joined #openstack-meeting-323:57
*** sdague has quit IRC23:58

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!