Monday, 2016-01-18

*** edwardb has quit IRC00:02
*** balajiiyer has joined #openstack-meeting-alt00:03
*** edwardb has joined #openstack-meeting-alt00:07
*** irenab has quit IRC00:18
*** zotoff has quit IRC00:24
*** sankarshan_away is now known as sankarshan00:24
*** vishwanathj has joined #openstack-meeting-alt00:27
*** yamamoto has quit IRC00:27
*** vishwanathj has quit IRC00:27
*** harshs has quit IRC00:27
*** harshs has joined #openstack-meeting-alt00:36
*** sankarshan has quit IRC00:37
*** sankarshan has joined #openstack-meeting-alt00:37
*** dims has joined #openstack-meeting-alt00:39
*** balajiiyer has quit IRC00:57
*** edwardb has quit IRC01:01
*** dims has quit IRC01:01
*** zhangjn has joined #openstack-meeting-alt01:04
*** davidlenwell has quit IRC01:05
*** salv-orlando has quit IRC01:06
*** davideagnello has joined #openstack-meeting-alt01:06
*** salv-orlando has joined #openstack-meeting-alt01:07
*** davidlenwell has joined #openstack-meeting-alt01:07
*** harshs has quit IRC01:11
*** davideagnello has quit IRC01:12
*** dimtruck is now known as zz_dimtruck01:15
*** baoli has quit IRC01:20
*** wojdev has quit IRC01:25
*** harshs has joined #openstack-meeting-alt01:26
*** amotoki has joined #openstack-meeting-alt01:30
*** amotoki has quit IRC01:32
*** baoli has joined #openstack-meeting-alt01:33
*** MarkAtwood has quit IRC01:34
*** yamamoto_ has joined #openstack-meeting-alt01:42
*** MarkAtwood has joined #openstack-meeting-alt01:45
*** miqui has quit IRC01:49
*** amotoki has joined #openstack-meeting-alt01:50
*** zhurong has joined #openstack-meeting-alt01:50
*** Sukhdev has joined #openstack-meeting-alt01:51
*** zhhuabj has quit IRC01:54
*** zhhuabj has joined #openstack-meeting-alt01:54
*** iyamahat has quit IRC01:56
*** MarkAtwood has quit IRC01:57
*** amotoki has quit IRC02:02
*** balajiiyer has joined #openstack-meeting-alt02:04
*** MarkAtwood has joined #openstack-meeting-alt02:05
*** kebray has joined #openstack-meeting-alt02:07
*** kebray has quit IRC02:12
*** kebray has joined #openstack-meeting-alt02:13
*** yamahata has joined #openstack-meeting-alt02:15
*** kebray has quit IRC02:15
*** kebray has joined #openstack-meeting-alt02:16
*** zz_dimtruck is now known as dimtruck02:20
*** yamahata has quit IRC02:22
*** markvoelker_ has quit IRC02:26
*** houming has joined #openstack-meeting-alt02:26
*** chaozhechen_ has joined #openstack-meeting-alt02:35
*** Chaozhe has joined #openstack-meeting-alt02:35
*** tfukushima has joined #openstack-meeting-alt02:36
*** MarkAtwood has quit IRC02:39
*** vishwanathj has joined #openstack-meeting-alt02:43
*** zhangjn_ has joined #openstack-meeting-alt02:44
*** zhangjn has quit IRC02:47
*** eliqiao_ has joined #openstack-meeting-alt02:47
*** Chaozhe has quit IRC02:48
*** Chaozhe has joined #openstack-meeting-alt02:48
*** amotoki has joined #openstack-meeting-alt02:48
*** gcb has joined #openstack-meeting-alt02:49
*** eliqiao has quit IRC02:50
*** zhangjn_ has quit IRC02:50
*** baoli has quit IRC02:51
*** dims has joined #openstack-meeting-alt02:52
*** Chaozhe has quit IRC02:53
*** davideagnello has joined #openstack-meeting-alt02:54
*** chaozhechen_ has quit IRC02:54
*** davideagnello has quit IRC02:54
*** zhangjn has joined #openstack-meeting-alt02:56
*** zhangjn has quit IRC02:57
*** abcdefjjj has joined #openstack-meeting-alt02:58
*** abcdefjjj has quit IRC02:58
*** ccz has joined #openstack-meeting-alt02:59
*** baoli has joined #openstack-meeting-alt02:59
*** zhangjn has joined #openstack-meeting-alt02:59
*** qwebirc32867 has joined #openstack-meeting-alt03:00
*** baoli has quit IRC03:01
*** nikhil has quit IRC03:04
*** nikhil has joined #openstack-meeting-alt03:05
*** zhangjn has quit IRC03:09
*** dimtruck is now known as zz_dimtruck03:20
*** zhangjn has joined #openstack-meeting-alt03:28
*** baoli has joined #openstack-meeting-alt03:35
*** harshs has quit IRC03:39
*** baoli has quit IRC03:39
*** zhangjn has quit IRC03:44
*** salv-orl_ has joined #openstack-meeting-alt03:45
*** jjmb1 has joined #openstack-meeting-alt03:46
*** salv-orlando has quit IRC03:47
*** jjmb has quit IRC03:49
*** Sukhdev has quit IRC03:51
*** Liuqing has joined #openstack-meeting-alt03:54
*** watanabe_isao has joined #openstack-meeting-alt04:02
*** zhangjn has joined #openstack-meeting-alt04:07
*** baoli has joined #openstack-meeting-alt04:10
*** baoli has quit IRC04:11
*** tfukushima has quit IRC04:15
*** Sukhdev has joined #openstack-meeting-alt04:16
*** tfukushima has joined #openstack-meeting-alt04:16
*** tfukushima has quit IRC04:18
*** banix has joined #openstack-meeting-alt04:20
*** fawadkhaliq has joined #openstack-meeting-alt04:23
*** baoli has joined #openstack-meeting-alt04:23
*** hichihara has joined #openstack-meeting-alt04:26
*** yasui has joined #openstack-meeting-alt04:28
*** oomichi has joined #openstack-meeting-alt04:31
*** vishwanathj_ has joined #openstack-meeting-alt04:32
*** kebray_ has joined #openstack-meeting-alt04:37
*** kebray has quit IRC04:37
*** fawadkhaliq has quit IRC04:44
*** iyamahat has joined #openstack-meeting-alt04:48
*** oomichi has quit IRC04:50
*** tfukushima has joined #openstack-meeting-alt04:51
*** dims has quit IRC04:58
*** zhhuabj has quit IRC05:02
*** zhangjn has quit IRC05:03
*** Poornima has joined #openstack-meeting-alt05:10
*** coolsvap|away is now known as coolsvap05:11
*** zhangjn has joined #openstack-meeting-alt05:14
*** zhhuabj has joined #openstack-meeting-alt05:15
*** zhangjn has quit IRC05:15
*** baoli has quit IRC05:17
*** salv-orl_ has quit IRC05:20
*** salv-orlando has joined #openstack-meeting-alt05:20
*** zhangjn has joined #openstack-meeting-alt05:20
*** iyamahat has quit IRC05:30
*** nurla has quit IRC05:33
*** nurla has joined #openstack-meeting-alt05:34
*** fawadkhaliq has joined #openstack-meeting-alt05:34
*** sgotliv has joined #openstack-meeting-alt05:35
*** salv-orlando has quit IRC05:41
*** salv-orlando has joined #openstack-meeting-alt05:42
*** vilobhmm11 has joined #openstack-meeting-alt05:42
*** zhangjn has quit IRC05:46
*** edwardb has joined #openstack-meeting-alt05:47
*** zhangjn has joined #openstack-meeting-alt05:48
*** edwardb has quit IRC05:52
*** banix has quit IRC05:52
*** wojdev has joined #openstack-meeting-alt05:53
*** Watanabe has joined #openstack-meeting-alt05:59
*** watanabe_isao has quit IRC05:59
*** zhangjn has quit IRC06:04
*** zhhuabj has quit IRC06:06
*** zhangjn has joined #openstack-meeting-alt06:06
*** wojdev_ has joined #openstack-meeting-alt06:08
*** wojdev has quit IRC06:10
*** wojdev_ is now known as wojdev06:10
*** jjmb has joined #openstack-meeting-alt06:10
*** jjmb1 has quit IRC06:12
*** sputnik13 has quit IRC06:20
*** zhhuabj has joined #openstack-meeting-alt06:22
*** wojdev has quit IRC06:25
*** vilobhmm11 has quit IRC06:27
*** vilobhmm11 has joined #openstack-meeting-alt06:30
*** balajiiyer has quit IRC06:33
*** kebray_ has quit IRC06:35
*** harshs has joined #openstack-meeting-alt06:45
*** SridharG has joined #openstack-meeting-alt06:46
*** salv-orlando has quit IRC06:54
*** salv-orlando has joined #openstack-meeting-alt06:55
*** vilobhmm11 has quit IRC06:56
*** _nadya_ has joined #openstack-meeting-alt06:56
*** ccz has quit IRC06:57
*** Ich has joined #openstack-meeting-alt06:58
*** Ich is now known as Guest2379106:58
*** Guest23791 is now known as ccz06:58
*** zhangjn_ has joined #openstack-meeting-alt07:00
*** zhangjn_ has quit IRC07:02
*** salv-orlando has quit IRC07:03
*** salv-orlando has joined #openstack-meeting-alt07:04
*** zhangjn has quit IRC07:04
*** iyamahat has joined #openstack-meeting-alt07:10
*** houming has quit IRC07:12
*** ccz has quit IRC07:12
*** nkrinner has joined #openstack-meeting-alt07:12
*** houming has joined #openstack-meeting-alt07:16
*** coolsvap is now known as coolsvap|away07:18
*** evgenyf has joined #openstack-meeting-alt07:23
*** harshs has quit IRC07:24
*** e0ne has joined #openstack-meeting-alt07:25
*** zhhuabj has quit IRC07:27
*** baoli has joined #openstack-meeting-alt07:29
*** eranra has joined #openstack-meeting-alt07:30
*** baoli has quit IRC07:33
*** scheuran has joined #openstack-meeting-alt07:37
*** safchain has joined #openstack-meeting-alt07:39
*** j___ has joined #openstack-meeting-alt07:40
*** zhhuabj has joined #openstack-meeting-alt07:40
*** rcernin has joined #openstack-meeting-alt07:41
*** salv-orlando has quit IRC07:46
*** jtomasek has joined #openstack-meeting-alt07:46
*** salv-orlando has joined #openstack-meeting-alt07:47
*** dingboopt has joined #openstack-meeting-alt07:51
*** paul-carlton2 has joined #openstack-meeting-alt07:51
*** jprovazn has joined #openstack-meeting-alt07:53
*** macsz has joined #openstack-meeting-alt07:53
*** zeih has joined #openstack-meeting-alt07:54
*** jjmb1 has joined #openstack-meeting-alt07:55
*** wojdev has joined #openstack-meeting-alt07:56
*** paul-carlton2 has quit IRC07:57
*** jjmb has quit IRC07:58
*** zhangjn has joined #openstack-meeting-alt08:06
*** salv-orlando has quit IRC08:06
*** salv-orlando has joined #openstack-meeting-alt08:08
*** _nadya_ has quit IRC08:09
*** matrohon has joined #openstack-meeting-alt08:10
*** belmoreira has joined #openstack-meeting-alt08:11
*** fawadkhaliq has quit IRC08:12
*** salv-orlando has quit IRC08:13
*** fawadkhaliq has joined #openstack-meeting-alt08:13
*** vishwanathj has quit IRC08:15
*** hichihara has quit IRC08:17
*** sgotliv has quit IRC08:17
*** e0ne has quit IRC08:20
*** katyafervent is now known as katyafervent_awa08:21
*** akamyshnikova has quit IRC08:22
*** katyafervent_awa is now known as katyafervent08:22
*** oomichi has joined #openstack-meeting-alt08:23
*** irenab has joined #openstack-meeting-alt08:24
*** sylwesterB has joined #openstack-meeting-alt08:25
*** sylwesterB has quit IRC08:26
*** sylwesterB has joined #openstack-meeting-alt08:26
*** thomnico has joined #openstack-meeting-alt08:32
*** samuelBartel has joined #openstack-meeting-alt08:37
*** gibi has joined #openstack-meeting-alt08:39
*** dizquierdo has joined #openstack-meeting-alt08:39
*** wojdev_ has joined #openstack-meeting-alt08:39
*** Watanabe has quit IRC08:39
*** iyamahat has quit IRC08:39
*** wojdev has quit IRC08:40
*** wojdev_ is now known as wojdev08:40
*** pnavarro has joined #openstack-meeting-alt08:42
*** ozamiatin has joined #openstack-meeting-alt08:46
*** eliqiao has joined #openstack-meeting-alt08:46
*** Sukhdev has quit IRC08:49
*** eliqiao_ has quit IRC08:49
*** bauwser is now known as bauzas08:54
*** fawadkhaliq has quit IRC09:01
*** fawadkhaliq has joined #openstack-meeting-alt09:01
*** fzdarsky has joined #openstack-meeting-alt09:02
*** sylwesterB has quit IRC09:09
*** fzdarsky has quit IRC09:09
*** derekh has joined #openstack-meeting-alt09:11
*** irenab has quit IRC09:11
*** bharathm has joined #openstack-meeting-alt09:11
*** irenab has joined #openstack-meeting-alt09:12
*** reedip is now known as outofmemory09:16
*** HeOS has joined #openstack-meeting-alt09:17
*** fzdarsky has joined #openstack-meeting-alt09:17
*** dizquierdo has quit IRC09:21
*** sputnik13 has joined #openstack-meeting-alt09:21
*** zeih has quit IRC09:22
*** paul-carlton2 has joined #openstack-meeting-alt09:25
*** sputnik13 has quit IRC09:26
*** yasui has quit IRC09:26
*** tfukushima has quit IRC09:28
*** sgotliv has joined #openstack-meeting-alt09:32
*** _degorenko|afk is now known as degorenko09:33
*** zhangjn has quit IRC09:46
*** ihrachys has joined #openstack-meeting-alt09:47
*** irenab has quit IRC09:47
*** zhhuabj has quit IRC10:01
*** macsz1 has joined #openstack-meeting-alt10:02
*** macsz has quit IRC10:04
*** davideagnello has joined #openstack-meeting-alt10:05
*** zotoff has joined #openstack-meeting-alt10:08
*** zhangjn has joined #openstack-meeting-alt10:10
*** davideagnello has quit IRC10:10
*** e0ne has joined #openstack-meeting-alt10:11
*** marcusvrn_ has joined #openstack-meeting-alt10:13
*** zhhuabj has joined #openstack-meeting-alt10:14
*** zotoff has quit IRC10:15
*** zhhuabj has quit IRC10:30
*** kzaitsev_mb has joined #openstack-meeting-alt10:33
*** neiljerram has joined #openstack-meeting-alt10:34
*** bradjones has quit IRC10:38
*** bradjones has joined #openstack-meeting-alt10:40
*** bradjones has quit IRC10:40
*** bradjones has joined #openstack-meeting-alt10:40
*** regebro has joined #openstack-meeting-alt10:41
*** ddmitriev has joined #openstack-meeting-alt10:42
*** jjmb has joined #openstack-meeting-alt10:47
*** jjmb1 has quit IRC10:48
*** dims has joined #openstack-meeting-alt10:54
*** zotoff has joined #openstack-meeting-alt10:55
*** macsz1 has quit IRC10:57
*** sylwesterB has joined #openstack-meeting-alt10:58
*** macsz has joined #openstack-meeting-alt11:01
*** tpsilva has joined #openstack-meeting-alt11:01
*** tellesnobrega is now known as tellesnobrega_af11:03
*** vishwanathj_ has quit IRC11:05
*** zotoff has quit IRC11:08
*** zhhuabj has joined #openstack-meeting-alt11:09
*** _nadya_ has joined #openstack-meeting-alt11:10
*** flaper87 has quit IRC11:11
*** flaper87 has joined #openstack-meeting-alt11:11
*** amotoki has quit IRC11:13
*** zhurong has quit IRC11:22
*** irenab has joined #openstack-meeting-alt11:33
*** kzaitsev_mb has quit IRC11:36
*** kei_yama has quit IRC11:37
*** gcb has quit IRC11:41
*** irenab has quit IRC11:44
*** gcb has joined #openstack-meeting-alt11:45
*** wojdev has quit IRC11:49
*** oomichi is now known as oomichi_away11:51
*** yamamoto_ has quit IRC11:51
*** kzaitsev_mb has joined #openstack-meeting-alt11:56
*** dizquierdo has joined #openstack-meeting-alt12:05
*** irenab has joined #openstack-meeting-alt12:05
*** houming has quit IRC12:05
*** wojdev has joined #openstack-meeting-alt12:07
*** dims has quit IRC12:10
*** houming has joined #openstack-meeting-alt12:10
*** Poornima has quit IRC12:11
*** fawadkhaliq has quit IRC12:13
*** _nadya_ has quit IRC12:14
*** houming has quit IRC12:16
*** houming has joined #openstack-meeting-alt12:17
*** clopez has joined #openstack-meeting-alt12:18
*** zotoff has joined #openstack-meeting-alt12:23
*** baoli has joined #openstack-meeting-alt12:28
*** numans has joined #openstack-meeting-alt12:29
*** bradjones has quit IRC12:30
*** zhangjn has quit IRC12:30
*** baoli has quit IRC12:33
*** yamamoto has joined #openstack-meeting-alt12:38
*** fawadkhaliq has joined #openstack-meeting-alt12:40
*** rsyed_away is now known as rsyed12:51
*** amotoki has joined #openstack-meeting-alt12:52
*** jdob has joined #openstack-meeting-alt12:53
*** bharathm has quit IRC13:00
*** houming has quit IRC13:01
*** banix has joined #openstack-meeting-alt13:02
*** zhangjn has joined #openstack-meeting-alt13:03
*** dprince has joined #openstack-meeting-alt13:04
*** reedip has joined #openstack-meeting-alt13:07
*** zz_dimtruck is now known as dimtruck13:10
*** dims has joined #openstack-meeting-alt13:11
*** zhangjn has quit IRC13:13
*** _nadya_ has joined #openstack-meeting-alt13:14
*** rcernin has quit IRC13:19
*** banix has quit IRC13:19
*** jjmb1 has joined #openstack-meeting-alt13:19
*** _nadya_ has quit IRC13:19
*** jjmb has quit IRC13:21
*** zhurong has joined #openstack-meeting-alt13:22
*** _nadya_ has joined #openstack-meeting-alt13:25
*** weshay_xchat has joined #openstack-meeting-alt13:31
*** weshay_xchat is now known as weshay13:31
*** zhangjn has joined #openstack-meeting-alt13:32
*** kzaitsev_mb has quit IRC13:33
*** gcb has quit IRC13:34
*** fawadkhaliq has quit IRC13:34
*** gongysh has joined #openstack-meeting-alt13:37
*** gcb has joined #openstack-meeting-alt13:41
*** myoung has joined #openstack-meeting-alt13:43
*** jprovazn has quit IRC13:43
*** n0ano has joined #openstack-meeting-alt13:43
*** dimtruck is now known as zz_dimtruck13:44
*** kzaitsev_mb has joined #openstack-meeting-alt13:46
*** zz_dimtruck is now known as dimtruck13:47
*** irenab has quit IRC13:48
*** cdent has joined #openstack-meeting-alt13:51
*** zhangjn_ has joined #openstack-meeting-alt13:53
*** Liuqing has quit IRC13:54
*** zhurong has quit IRC13:55
*** balajiiyer has joined #openstack-meeting-alt13:56
*** zhangjn has quit IRC13:57
*** zhangjn_ has quit IRC13:57
*** dimtruck is now known as zz_dimtruck13:58
n0ano#startmeeting nova-scheduler13:59
openstackMeeting started Mon Jan 18 13:59:43 2016 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
*** openstack changes topic to " (Meeting topic: nova-scheduler)"13:59
openstackThe meeting name has been set to 'nova_scheduler'13:59
cdento/13:59
n0anoanyone here to talk abou the scheduler?13:59
edleafe\o14:00
cdenti'm here but happy to pass if there's nothing going (other than pointing at some reviews that need some eyes)14:00
* n0ano cdent is too quick too early in the morning14:00
*** bharathm has joined #openstack-meeting-alt14:00
n0anocdent, that's was kind of my idea14:00
n0anolet's see who all joins14:00
cdentIt's 2 in the afternoon for me, but that's still early for me14:00
n0anoedleafe, isn't it a holiday for you, take a break :-)14:01
edleafen0ano: not a work holiday, unfortunately14:01
*** gcb has quit IRC14:01
n0anohow odd, I thought MLK was pretty universal these days, oh well14:02
*** zhangjn has joined #openstack-meeting-alt14:02
bauzasoh méan14:03
*** dslevin has quit IRC14:03
bauzasI was waiting in #openstack-meeting :)14:03
bauzassooo14:03
* bauzas waves14:03
edleafeit's holiday, yeah, but not a paid day off14:03
n0anobauzas, NP, I've tried to kick people off #openstack-meeting in the past :-)14:04
bauzasis there an US holiday those days ?14:04
bauzasI can see some folks out14:04
n0anobauzas, yep, Martin Luther King day, it's an official holiday for me, not for edleafe14:04
*** wojdev has quit IRC14:04
bauzasok14:05
n0anoanyway, let's get started14:05
n0anoI like cdent idea, let's just have some quick opens and go, so14:05
n0ano#topic opens14:05
*** bharathm has quit IRC14:05
*** openstack changes topic to "opens (Meeting topic: nova-scheduler)"14:05
*** jecarey has quit IRC14:05
cdentgerrit ill?14:06
n0anocdent, reall? I got emails yesterday, if you think it is broke you should bring it up on #openstack-nova14:06
cdentNo, just now it was giving me 502s14:07
cdentseveral times14:07
cdentbut I guess it was a blip14:07
cdentI wanted to point at this: https://review.openstack.org/#/c/262561/ a documentation tuneup that's been sitting idle for a while14:07
bauzasgerrit wfm14:08
edleafecdent: I got blipped, too, but then it started working again14:08
n0anoworking now, hopefully OK14:08
* cdent shrugs, c'est le gerrit14:09
n0anocdent, looks like you need a couple of +2's on that14:09
*** banix has joined #openstack-meeting-alt14:09
*** gcb has joined #openstack-meeting-alt14:09
bauzascdent: cosmetic change only, right?14:09
cdentpretty much14:09
cdenttried to tune some grammar14:10
bauzasokay, I'll look at14:10
cdentand added links14:10
bauzasokay, because me is a French guy, so you know about my grammar14:10
n0anobauzas, s/me is/I am/ :-)  I see your point14:11
cdentIs jaypipes around or is he properly holidaying? It appears holidaying (no tab complete).14:11
cdentI'm wondering what the situation is on the resource-* specs. I've got https://review.openstack.org/#/c/263496/ this (and its relations) pending, but the spec is still out for review14:12
n0anocdent, jay is always iffy, looks like he's not here today14:13
n0anocdent, you might want to send him an email to see where he is on the spec14:14
bauzascdent: since the universe exploded with many specs, I reiterate my will to get the specs + patches in https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking14:14
cdentI poked him late last week he said that he'd have something at least by today14:15
cdenthe also said he'd put stuff on there but I guess that didn't happen. I'll do it.14:15
n0anocdent, then a polite reminder to him seems appropriate14:15
* cdent nods14:16
n0anoAOB (Any Other Business)?14:16
bauzasnot really14:17
cdentIs 'grep -i schedule tempest' a good way to find scheduler related tests in tempest?14:17
bauzasnot really IMJO14:18
cdentis there a good way?14:18
bauzascdent: you could look at the scenarios rather14:18
bauzascdent: what do you want to know actually14:18
bauzas?14:18
cdentI'm trying to do a simple analysis of the extent of scheduler coverage in tempest. I already know that it is pretty weak, but I'm just digging around for a bit more data. And given that tempest is generally inscrutable, I just wondered if there was a way to improve my filtering (so I don't have to read everything).14:19
*** macsz has quit IRC14:20
bauzascdent: so, you should rather see which filters are checked14:21
bauzascdent: by seeing which tests are modifying the CONF opts14:22
bauzascdent: since by default a very small portion of filters are enabled, it means that if no tempest tests are modifying that flag, you could guess that it's mostly because they don't use them14:22
* cdent nods14:23
bauzascdent: then, once you admit that 99% of tests (I leave my opinion to be accepting something I dunno) are using the default filters, you could just look at whether the boot requests use hints14:23
bauzasor flavor metadata14:23
bauzasor image extra specs14:24
bauzasby grepping over 'hints' or the other terms14:24
*** flaviof has joined #openstack-meeting-alt14:24
cdentThe implication of all that, though, is there's not much in the way of explicit scheduler testing, rather a lot of implicit stuff as a result of various instance boots14:24
bauzasand then, you'll see that 99% of the time, tempest doesn't care about providing more than just 'eh, scheduler, boot me a request'14:24
cdentyes14:24
bauzascdent: exactly14:25
*** jaypipes has joined #openstack-meeting-alt14:25
cdentspeak of the devil14:25
bauzascdent: that's my main worries here, all of the scheduler implications are implicit14:25
*** amitgandhinz has joined #openstack-meeting-alt14:25
bauzasso, lemme now tell you a story14:25
bauzasof someone modifying the scheduler and not having some explicit tempest tests14:25
*** yamamoto has quit IRC14:25
bauzasyou know how that guy can functionnally test that ?14:26
bauzashe runs the caching scheduler unittests + he runs the cinder functional tests14:26
*** akuznetsov has joined #openstack-meeting-alt14:26
bauzasthat's the only coverage we have14:26
cdent:(14:26
*** julim has joined #openstack-meeting-alt14:26
bauzasto be clear, just play locally and crash the scheduler14:26
bauzasyou'll see that only the caching scheduler should notice that14:27
bauzasnot speaking of a full crash14:27
bauzasjust something bad in the filters14:27
*** gcb has quit IRC14:28
cdentWell, my hope here is to gain some understanding of existing stuff so I can make it better (and be prepared for the summit session on the topic next week)14:28
*** sdake has joined #openstack-meeting-alt14:29
bauzascdent: sure, and that's a very valid point14:29
*** gcb has joined #openstack-meeting-alt14:30
bauzascdent: I'm just telling you that we have 3 levels of coverage : 2 in-tree (unit + functional) and one in Tempest and all of them are not veryfying the scheduler but implicitly14:30
cdentyes14:30
cdentI've figured that out14:30
bauzasby saying "implicitly", I mean "run the default filters with a default query and hope that the scheduler will return you a tuple"14:30
bauzass/hope/assert14:31
*** rossella_s has quit IRC14:31
*** esheffield has joined #openstack-meeting-alt14:31
* cdent nods14:31
n0anoone hessitates to say that at least that's something and testing can always be made better14:31
*** rossella_s has joined #openstack-meeting-alt14:31
* cdent nods at that too14:31
n0anoanyway, anything else?14:32
cdentnot from me14:32
bauzascrickets from me14:33
n0anonote that, barring arguements from anyone, I'll cancel next week's meeting, it should be a travel day for the mid-cycle for most14:33
bauzas++14:33
cdent+114:33
n0anoOK, tnx everyone, some will talk in person next week, the rest of us will be here in two weeks.14:34
*** neelashah has joined #openstack-meeting-alt14:34
n0ano#endmeeting14:34
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:34
openstackMeeting ended Mon Jan 18 14:34:19 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-01-18-13.59.html14:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-01-18-13.59.txt14:34
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-01-18-13.59.log.html14:34
*** banix has quit IRC14:35
*** cdent has left #openstack-meeting-alt14:36
*** fawadkhaliq has joined #openstack-meeting-alt14:38
*** ALUvial has joined #openstack-meeting-alt14:38
*** akuznetsov has quit IRC14:39
*** SridharG has quit IRC14:40
*** jecarey has joined #openstack-meeting-alt14:42
*** jecarey has quit IRC14:42
*** jecarey has joined #openstack-meeting-alt14:42
*** yamamoto has joined #openstack-meeting-alt14:42
*** myoung has quit IRC14:43
*** aluvial_ has joined #openstack-meeting-alt14:44
*** amotoki has quit IRC14:44
*** numans has quit IRC14:47
*** gongysh has quit IRC14:48
*** rsyed is now known as rsyed_away14:48
*** akuznetsov has joined #openstack-meeting-alt14:50
*** _nadya_ has quit IRC14:50
*** ralonso has joined #openstack-meeting-alt14:53
*** jmckind has joined #openstack-meeting-alt14:53
*** superdan is now known as dansmith14:54
*** banix has joined #openstack-meeting-alt14:54
*** sigmavirus24_awa is now known as sigmavirus2414:55
*** korzen has joined #openstack-meeting-alt14:56
*** rsyed_away is now known as rsyed14:57
*** mrmartin has joined #openstack-meeting-alt14:57
*** Poornima has joined #openstack-meeting-alt15:00
ihrachyswill start in 2 mins. waiting for folks.15:00
*** mhickey has joined #openstack-meeting-alt15:01
*** huyang has quit IRC15:01
rossella_sihrachys, I am here15:02
mhickeyHi15:02
mhickeythings are very quiet rossella_s!:)15:02
*** spotz_zzz is now known as spotz15:02
rossella_smhickey, is that bad or good?15:03
*** akuznetsov has quit IRC15:03
mhickeywho knows!:)15:03
ihrachysok let's start :)15:03
ihrachys#startmeeting neutron_upgrades15:03
openstackMeeting started Mon Jan 18 15:03:34 2016 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"15:03
openstackThe meeting name has been set to 'neutron_upgrades'15:03
*** _nadya_ has joined #openstack-meeting-alt15:03
*** irenab has joined #openstack-meeting-alt15:03
ihrachyslet's go straight to specific patches :)15:04
*** quade has joined #openstack-meeting-alt15:04
ihrachys#topic partial upgrade15:04
*** openstack changes topic to "partial upgrade (Meeting topic: neutron_upgrades)"15:04
*** zz_dimtruck is now known as dimtruck15:04
*** myoung has joined #openstack-meeting-alt15:04
ihrachyswe have some great progress on that front. specifically, we seem to understand the reason for job failures: bad mtu settings in multinode gate15:04
rossella_sihrachys, good news15:05
ihrachyswe have a gerrit topic for all those patches15:05
ihrachys#link https://review.openstack.org/#/q/status:open+topic:multinode-neutron-mtu15:05
rossella_sihrachys, MTU is always problematic...I hope we will fix it15:05
ihrachysit does not completely fix the job, but at least we go past initial resource creation, run tests, and only 3 of those fail15:06
ihrachys(all due to ssh not working on FIP)15:06
ihrachysfolks are looking further on those failures, maybe it's also mtu related, just now on br-ex side (previous issue was due to bad mtu from br-tun side)15:07
ihrachysok, let's move on :)15:07
ihrachys#topic objects15:07
rossella_sthanks for the recep ihrachys15:07
*** openstack changes topic to "objects (Meeting topic: neutron_upgrades)"15:07
korzenI had one patch on DVR multinode grenade experimental job - can we enable it in short while?15:07
ihrachysrossella_s: wanna update?15:07
rossella_sihrachys, yes15:07
ihrachyskorzen: sorry, let's return to that a bit later15:07
rossella_sihrachys, I updated the agenda too, so I have a patch regarding port the allowed address pairs extension15:07
korzenok, no problem15:07
*** thomnico has quit IRC15:08
rossella_shttps://review.openstack.org/#/c/268274/15:08
rossella_sfolks interested in having a task can look in the backlog, I have listed the extensions that needs to be ported15:08
*** davidsha has joined #openstack-meeting-alt15:08
*** thomnico has joined #openstack-meeting-alt15:08
*** j___ has quit IRC15:09
rossella_sregarding the port ovo, tests are passing, work is paused since I want to port all the extensions needed first so that we can move the whole port object to ovo15:09
ihrachysrossella_s: cool! patch seems quite clean on brief sight15:09
rossella_sreviews are welcome :)15:09
ihrachysnot invasive or smth :)15:09
rossella_sI tried ihrachys15:10
rossella_sanother patch to mention is https://review.openstack.org/#/c/268273/ "Handle OVO that don't have ID as primary key"15:10
rossella_sI'd appreciate if you ihrachys could have a look15:10
rossella_sit's a way of handling object that don't have the "id" field15:10
*** Poornima has left #openstack-meeting-alt15:10
rossella_sthat's all from me15:11
ihrachysoh right. that is indeed missing in base db api. will check.15:11
ihrachyskorzen: what's on your side?15:11
korzenso I have the patch: https://review.openstack.org/#/c/264273 - I have added the status there15:11
korzencurrent the unit tests are failing, I'll be working on fixing them15:12
korzenThe network OVO is used in one use case - DHCP requests15:12
ihrachysnice. also specific coverage should be added to all new objects.15:12
korzenyes, that's too15:12
*** vishwanathj_ has joined #openstack-meeting-alt15:13
korzencurrently there is only the GET method implemented using the ML2plugin15:13
ihrachysI see you added RBAC object. I think hdaniel had some patch for qos policies to add rbac support there that required objects. probably not sent to gerrit yet though.15:13
korzenyes, the NetworkRBAC is just for reference15:14
korzenI did not use it so can remove it from my patch15:14
korzenI have worked also on Subnet OVO15:14
ihrachysok cool. I will get back to hdaniel to see what's ETA on his side for RBAC aware objects15:14
korzenin the same patch15:14
ihrachyskorzen: will we be able to split it?15:15
korzenI can split but I guess that is can be also introduced in one patch Netrwork and Subnet15:15
*** rsyed is now known as rsyed_away15:15
ihrachysor there are some obstacles against doing it?15:15
*** rsyed_away is now known as rsyed15:15
ihrachysI prefer to split concerns. it's easier for reviewers to grasp15:16
korzenwithout subnet ovo the network ovo is using the custom JSON field15:16
ihrachysand hence merge :)15:16
rossella_sihrachys, +115:16
ihrachysthen I guess we first introduce subnets, then networks15:16
rossella_syep15:16
korzenok, I'm fine with it15:16
rossella_syour network patch can depend on the subnet on korzen15:16
korzenok, I will change it15:17
ihrachyskorzen: thanks!15:17
ihrachysany more updates on objects?15:17
korzenI have also introduced the RPC serialiazer15:17
ihrachyskorzen: what's that? link?15:17
korzenhttps://review.openstack.org/#/c/26905615:17
*** tfukushima has joined #openstack-meeting-alt15:17
*** tfukushima has quit IRC15:17
korzenit is the case where we are sending the OVO via RPC not dicts15:18
*** rsyed is now known as rsyed_away15:18
*** rsyed_away is now known as rsyed15:18
korzenthe output is that we can deserialize the object on the client side15:18
korzenand check for the compatible version15:18
*** cp16net has quit IRC15:18
korzencurrently we are using the OVO on server side15:19
ihrachyskorzen: what's the expected usage for the serializer in neutron?15:19
ihrachyskorzen: we also use it on agent side, for qos15:19
ihrachysthru rpc callbacks15:19
korzenand on client's, the info metadata about what is the version is lost15:19
*** cp16net has joined #openstack-meeting-alt15:20
*** baoli has joined #openstack-meeting-alt15:20
korzenwe can send the OVO via RPC and check on client side if it is matching the client's code15:20
korzenit is maily for future use, for example for backports15:20
ihrachysyeah, but it's assumed for now versions haven't changed. and once the ajo's patch for rolling upgrades for rpc callbacks is merged, agents should always receive their own version.15:20
*** rossella_s1 has joined #openstack-meeting-alt15:21
korzenIndirection API - ask server to translate the message to required lower version15:21
korzenit can also log the error message15:21
korzenfor admin usage15:21
ihrachyskorzen: we have it in some form for rpc callbacks. if we don't use them, yes, it may make sense.15:21
*** gcb has quit IRC15:22
*** diazjf has joined #openstack-meeting-alt15:22
ihrachysok, I guess we'll need to discuss it in review itself15:22
korzenare we going to use rpc callcabacks for ports and networks?15:22
ihrachyskorzen: yes, that was the assumption15:22
ihrachysusing rpc callbacks for all object state propagation from server to agents15:22
korzenok, so lets look into my patch and see if it is usable for neutron15:23
ihrachysright. should be considered in more broad context, looking it general rpc strategy we'll take.15:23
ihrachys#topic other patches15:24
*** openstack changes topic to "other patches (Meeting topic: neutron_upgrades)"15:24
*** rvyalov_ has joined #openstack-meeting-alt15:24
ihrachyskorzen: what was that about dvr?15:24
korzenlet me link it15:24
korzenhttps://review.openstack.org/#/c/25021515:25
*** baoli has quit IRC15:25
korzenCreate DVR multinode grenade job for Neutron upgrade tests15:26
korzenit is introducing the DVR gate job for grenade testing15:26
*** baoli has joined #openstack-meeting-alt15:26
ihrachysnot gate, experimental for now15:26
korzenyeap, I meant experimental15:27
*** evgenyf has quit IRC15:27
ihrachyskorzen: should we maybe fix legacy mode first as sc68cal suggested?15:27
*** diazjf has quit IRC15:28
korzenyes, this is my thinking also, but I wanted not to lost my commit there15:28
ihrachysas long as it's not abandoned, we won't loose it :)15:28
*** zhangjn has quit IRC15:29
ihrachysok, I have one small update to devref related to RPC rolling upgrades15:29
ihrachys#link https://review.openstack.org/26812515:29
ihrachysreviews welcome15:29
*** baoli has quit IRC15:29
rossella_s1Noted ;)15:29
ihrachysanything else worth attention? mhickey?15:29
*** mrmartin has quit IRC15:30
ihrachysok, probably nothing :)15:31
rossella_s1:)15:31
ihrachys#topic open discussion15:31
*** openstack changes topic to "open discussion (Meeting topic: neutron_upgrades)"15:31
*** HeOS has quit IRC15:31
ihrachysanything else anyone wants to share?15:31
korzendo you think we can land the OVO implementations for Mitaka?15:32
*** gcb has joined #openstack-meeting-alt15:32
rossella_s1We can try at least15:32
ihrachyskorzen: pieces of it, yes. I am not very optimistic about *all* the pieces we could in theory merge.15:32
*** neelashah1 has joined #openstack-meeting-alt15:32
*** neelashah has quit IRC15:32
ajohi, I'm around now15:33
korzenany advice how to proceed to get most of it merged?15:33
korzenmore decoupling?15:33
korzenmore manpower?15:33
ihrachyskorzen: well, we need reviews and proper test coverage.15:33
rossella_s1More tests15:33
ihrachyskorzen: yes, decoupling helps. one piece at a time15:33
ihrachysajo: ok tell us about rpc callbacks15:33
*** amitgandhinz has quit IRC15:34
ajoihrachys : ack, the core logic is up for review here: https://review.openstack.org/26534715:34
*** baoli has joined #openstack-meeting-alt15:34
mhickeyihrachys: sorry; was distrecated15:34
ajoand integration is WIP https://review.openstack.org/268040  I hope I will publish the final integration there tomorrow15:34
*** amitgandhinz has joined #openstack-meeting-alt15:35
mhickey*distracted*15:35
ajofirst patch is the one that calculates the version sets that need to be pushed over the wire,15:35
ihrachysI am proceed reviewing the ajo's patch, but more eyes would be welcome. I need to admit it's hard to understand and we may need to shuffle it for a bit.15:35
*** _nadya_ has quit IRC15:35
*** jmckind_ has joined #openstack-meeting-alt15:35
ajoand the second one, introduces the needed RPCs (agents->neutron-server) to update versions quickly to all running neutron servers as the agents come up15:35
rossella_s1I will have a look too...I put it in my queue15:36
mhickeyajo: i will give more feedback as I understand more15:36
ajoihrachys , ack, that's ok, the easier to understand, the better.15:36
mhickeyihrachys: need to sync with HenryG today on has_offline_migrations patch15:37
*** neelashah1 has quit IRC15:37
ihrachysfolks, that's re https://review.openstack.org/248190 ^15:37
ihrachysmhickey: I saw folks tested it and reported success back. nice.15:37
*** diazjf has joined #openstack-meeting-alt15:38
*** neelashah has joined #openstack-meeting-alt15:38
mhickeyihrachys: just need to see if solution is enough till the "one env"15:38
ihrachysmhickey: I see you need to hardcode table names for *aas15:38
*** jmckind has quit IRC15:38
ihrachysmhickey: does it mean it won't work with other subprojects?15:38
*** fredyx10 has joined #openstack-meeting-alt15:38
*** Sukhdev has joined #openstack-meeting-alt15:39
mhickeyihrachys: yes; most ugly but might be no point in doing more until the env are squashed15:39
mhickeyihrachys: what other subprojects?15:39
ihrachysI see. we need to think at least about how we handle those cases.15:39
ihrachysmhickey: well, any 3party plugin15:40
ihrachysmhickey: like vmware-nsx15:40
*** mtanino has joined #openstack-meeting-alt15:40
*** annegentle has joined #openstack-meeting-alt15:40
mhickeyihrachys: not if they are using a version table that is not "alembic_version"15:40
*** numans has joined #openstack-meeting-alt15:41
ihrachysmhickey: I suspect they don't, need to check with HenryG15:41
mhickeyihrachys: yes; if thats the case then we would need some configuration to help tell Neutron what is the version table name.15:41
ajoanother example: https://github.com/openstack/networking-sfc/tree/master/networking_sfc/db/migration/alembic_migrations/versions/liberty15:42
*** baoli has quit IRC15:42
ihrachysmhickey: https://github.com/openstack/networking-sfc/blob/master/networking_sfc/db/migration/alembic_migrations/env.py#L2615:42
*** bharathm has joined #openstack-meeting-alt15:42
*** roaet has joined #openstack-meeting-alt15:42
*** myoung has quit IRC15:42
ihrachysmhickey: yeah, I think I mentioned before we may need to have some API for plugins to pass the table names15:43
*** hyamauchi has joined #openstack-meeting-alt15:43
ajomay be using stevedore hooks?15:43
ihrachysmhickey: and if they don't, we can just bail out with an error.15:43
ihrachysajo: yes, that would be the idea15:43
mhickeyihrachys; my goodness, we are opening Pandora's box! :)15:43
ajomhickey pandora box was open long ago :D15:43
mhickeyajo: sure...15:43
ihrachysyeah, the day neutron repo was created15:43
ajolol15:44
rossella_s1ajo :D15:44
rossella_s1Lol15:44
mhickeylol15:44
ihrachysok, we'll need to figure out something for subprojects. :)15:44
*** sdake_ has joined #openstack-meeting-alt15:44
mhickeyok, let me investigate it more and see how I can try and bring the patch to a good state for merging.15:44
ihrachysok, let's wrap the meeting. seems like all is discussed.15:45
ihrachysthank you folks!15:46
ihrachys#endmeeting15:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:46
openstackMeeting ended Mon Jan 18 15:46:05 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-01-18-15.03.html15:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-01-18-15.03.txt15:46
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-01-18-15.03.log.html15:46
korzenthanks, bye :)15:46
mhickeybye, thanks15:46
rossella_s1Bye15:46
roaetfarewell15:46
*** rossella_s1 has quit IRC15:46
*** bharathm has quit IRC15:47
*** sylwesterB has quit IRC15:47
*** sdake has quit IRC15:48
*** annegentle has quit IRC15:50
*** gomarivera has joined #openstack-meeting-alt15:50
*** akuznetsov has joined #openstack-meeting-alt15:50
*** resker has quit IRC15:53
*** jprovazn has joined #openstack-meeting-alt15:55
*** quade has left #openstack-meeting-alt15:55
*** baoli has joined #openstack-meeting-alt15:57
*** haypo has joined #openstack-meeting-alt15:57
*** angdraug has joined #openstack-meeting-alt15:59
*** kgiusti has joined #openstack-meeting-alt15:59
dims#startmeeting oslo16:00
dimscourtesy ping for GheRivero, amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dougwig, e0ne, flaper87, garyk, harlowja, haypo,16:00
openstackMeeting started Mon Jan 18 16:00:04 2016 UTC and is due to finish in 60 minutes.  The chair is dims. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
dimscourtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, ozamiatin, redrobot, rpodolyaka, spamaps16:00
dimscourtesy ping for sergmelikyan, sreshetnyak, sileht, sreshetnyak, stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek, gcb16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** jimbobhickville has joined #openstack-meeting-alt16:00
*** openstack changes topic to " (Meeting topic: oslo)"16:00
openstackThe meeting name has been set to 'oslo'16:00
kgiustio/16:00
*** roaet has left #openstack-meeting-alt16:00
jecarey0/16:00
toabctlhi16:00
jd__hello16:00
bknudson_hi16:00
*** banix has quit IRC16:00
rpodolyakao/16:00
*** ozamiatin_ has joined #openstack-meeting-alt16:00
dimshi kgiusti jecarey toabctl jd__ bknudson_ rpodolyaka16:00
ozamiatin_o/16:00
bknudson_we actually don't have the day off here.16:01
*** sdake_ is now known as sdake16:01
dimsbknudson_ : aha16:01
*** lazy_prince has joined #openstack-meeting-alt16:01
dims#topic Red flags for/from liaisons16:01
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"16:01
rbradforo/16:01
bknudson_None for keystone -- I'm getting a little worried about some deprecated oslo.db stuff that we haven't fixed up yet... more of a yellow flag.16:02
ihrachysnone for neutron16:02
* rpodolyaka wonders what we deprecated recently in oslo.db16:02
dimsbknudson_ : haven't been fixed in keystone?16:02
dimsrpodolyaka : probably the engine facade?16:02
bknudson_yes, keystone has to change engine usage16:02
rpodolyakaah, yeah16:02
bknudson_last time I looked at it there were no docs. I think there's docs now.16:03
rpodolyakathe old version is going to stay for a while16:03
rpodolyakayeah, the action item is till on me to write a blog post on the new facade thing16:03
rpodolyakaor simply docs16:03
dimsrpodolyaka : +116:03
*** akuznetsov has quit IRC16:04
* rpodolyaka adds it to todo list16:04
dims#topic Releases for Mitaka16:04
*** openstack changes topic to "Releases for Mitaka (Meeting topic: oslo)"16:04
dimsdoes anyone need a release this week?16:04
*** baoli has quit IRC16:04
dimsdukhlov - was waiting on some docs for pika for o.m release16:05
*** harshs has joined #openstack-meeting-alt16:05
flaper87o/16:05
dimshey flaper8716:05
flaper87oh, that was to say hi16:06
flaper87I don't need a release16:06
flaper87:D16:06
dims:)16:06
* flaper87 should try ninja-entering meetings next time16:06
dims#topic - releases for stable branches16:06
*** openstack changes topic to "- releases for stable branches (Meeting topic: oslo)"16:06
dimsi see a bunch of discussion over on glance, so thought we could spend a little time here as well16:06
dimsstarting with an update from me16:06
*** nkrinner has quit IRC16:07
dimsoslo has stable branches but has not released any library from the stable branches16:07
dimsso far16:07
bknudson_couldn't call it stable if you kept doing releases.16:07
dimsthe current CI has upper-constraints in stable branches that are uncapped16:07
dimsso any releases will not affect any tests in the CI and so we would not even know if we broke something16:08
bknudson_so CI doesn't run with stable anyways16:08
dimsso mriedem and dhellmann and lifeless were trying to come up with a release-constraints file for stable/liberty16:08
dukhlovdims: will do tomorrow, is it ok?16:08
dimsand figure out a test matrix that will run against that16:09
dimsdukhlov : +116:09
dimsonce that's in place we can make stable/liberty library releases16:09
dimsso we'll end up with a set of oslo libraries cut from stable/liberty and a set of oslo libraries from master, both of which should not break say stable/liberty nova or keystone16:10
dimsper the openstack-spec in progress from lifeless16:10
*** baoli has joined #openstack-meeting-alt16:10
dimshaypo, flaper87, makes sense?16:10
*** wznoinsk has joined #openstack-meeting-alt16:11
haypodims: what i see is that it becomes much harder to change anything in oslo16:11
dimsthe idea is that packagers will still be able to use stable/liberty branches and corresponding libs and not have to pull from master16:11
haypodims: which is a real pain point for me16:11
dimshaypo : right that's a valid concern and one of my top problems as well16:11
haypodims: i don't understand the rationale behaviour always using the latest version of oslo for all openstack versions16:11
bknudson_packagers already use old releases and don't always get from master.16:12
*** armax has joined #openstack-meeting-alt16:12
haypodims: for me, it's perfectly fine to stop at oslo.context < 2.0 on liberty (for example)16:12
*** thomnico has quit IRC16:12
dimshaypo : you need to respond on https://review.openstack.org/#/c/226157/16:12
dimsbknudson_ : right16:12
*** rmoe has quit IRC16:12
haypothe problem is that it becomes really hard to estimate how much code will be broken if we change oslo and all openstack releases use the latest oslo versions16:12
*** rmoe has joined #openstack-meeting-alt16:13
dimshaypo : you should talk to mriedem on openstack-stable about the capping, he is in favor of it but it's very hard to do with experience from previous releases16:13
haypodims: i hesitate to qualify my change as a corner case, since it breaks the API16:13
bknudson_you would like to be able to upgrade the libraries to master and then upgrade the servers, so it makes sense to want to support some backwards compat.16:13
dimshaypo : yes, that the next problem on my list which is being able to predict what we break16:13
haypodims: and an obvious alternative is to keep the old attribute and add a new one, as dhellmann suggested16:13
*** baoli has quit IRC16:14
haypomy point is that python3 is *not* used by anything, so it's cheaper to break the API than having the dead slow deprecation process ... which does *not* work (see multiple discussions on openstack-dev)16:14
*** annegentle has joined #openstack-meeting-alt16:15
dimshaypo : for this specific thing let's talk to dhellmann once more when he is around.16:15
bknudson_keystone server doesn't support python3 yet.16:15
bknudson_not sure if it even will in M.16:15
haypobknudson_: yeah, openstack products are kind of certified with a set of oslo versions16:15
*** edtubill has joined #openstack-meeting-alt16:16
haypobknudson_: since we don't run functional tests on python 3, it would be unsane to deploy openstack on python 3 today16:16
dimsbknudson_ : haypo : we should start with comments on the spec and follow up with discussion on openstack-stable with mriedem, etc16:16
*** zeih has joined #openstack-meeting-alt16:17
dimshaypo : yes, for this change. i just want to be sure everyone else understands the implications for the rest of the work16:17
dimslet's get through one more item and then we can talk more16:18
dims#topic Add failure remoting best-of-breed spec16:18
dims#link https://review.openstack.org/#/c/229194/16:18
*** openstack changes topic to "Add failure remoting best-of-breed spec (Meeting topic: oslo)"16:18
dimsharlowja : around?16:18
haypodims: the concrete impact of my oslo.context change https://review.openstack.org/#/c/250731/ is that i will break python3 gates of some projects16:18
dimsi need some eyes on this review please per harlowja's request16:18
bknudson_the description sounds like a xkcd comic about standards.16:18
dimsbknudson_ : y commit message is funny, the actual spec is better :)16:19
*** Leo_ has joined #openstack-meeting-alt16:19
dims#topic Open discussion16:19
dimsAny other stuck reviews?16:19
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"16:19
rbradforI have a discussion point16:20
dimshaypo : do you want to ping PTL(s) about removing their python3 jobs in stable/liberty?16:20
ozamiatin_dims: I've got these minor changes: https://review.openstack.org/#/c/268097/, https://review.openstack.org/#/c/268110/16:20
ozamiatin_dims: And this big one, https://review.openstack.org/#/c/268792/ will get ready soon (pep8 etc)16:21
dimshaypo : you could get the ball rolling with a note on -dev.16:21
bknudson_what's the problem with python3 jobs on stable/liberty?16:21
dimsozamiatin_ : ack thanks, will add to my queue16:21
haypodims: i don't think that it's a good idea to remove py3 gates16:21
ozamiatin_dims: thanks16:21
dimshaypo : so what's left is the slow deprecation process?16:22
*** belmoreira has quit IRC16:22
haypodims: i just said it to explain that it will not impact anyone in practice, but it's usually a good practice to test code16:22
*** lazy_prince has quit IRC16:22
*** mixos has joined #openstack-meeting-alt16:22
haypodims: for the specific case of glance? well, there is still the option of accepting my patch which already has a +2 :-)16:22
*** lazy_prince has joined #openstack-meeting-alt16:22
haypodims: but i'm probably over confident, since ian is strongly opposed to that :)16:22
dimshaypo : i'll leave that to glance cores :)16:22
bknudson_I guess the unit test jobs on keystone don't get us anything since you can't run keystone that way anyways.16:23
dimskgiusti jecarey toabctl jd__ bknudson_ rpodolyaka - anything else to discuss?16:24
kgiustidims: nope16:24
rpodolyakano16:24
dimskgiusti : were you able to check on compression options for your driver?16:24
jd__nop16:24
dimsrpodolyaka : jd__ : thanks16:25
kgiustidims: sorry, no - I will do that today.16:25
*** lazy_prince has quit IRC16:25
jecareyNo16:25
bknudson_security midcycle was last week16:25
*** sbalukoff has quit IRC16:25
bknudson_keystone midcycle is next week16:25
dimsw00t: have fun bknudson_16:26
dimskgiusti : ack thanks16:26
bknudson_nova must be coming up too16:26
dimsjecarey : thanks16:26
dimsbknudson_ : next week i think16:26
dimsi won't make it to either one16:26
*** woodster_ has joined #openstack-meeting-alt16:27
dimsk let's wrap it up for this week. thanks everyone16:27
dims#endmeeting16:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:27
openstackMeeting ended Mon Jan 18 16:27:37 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-01-18-16.00.html16:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-01-18-16.00.txt16:27
*** sdake has quit IRC16:27
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-01-18-16.00.log.html16:27
*** kgiusti has left #openstack-meeting-alt16:27
*** tonytan4ever has joined #openstack-meeting-alt16:27
*** jimbobhickville has left #openstack-meeting-alt16:28
*** bnemec has quit IRC16:29
*** bana_k has joined #openstack-meeting-alt16:30
*** SridharG has joined #openstack-meeting-alt16:30
*** sdake has joined #openstack-meeting-alt16:31
*** banix has joined #openstack-meeting-alt16:33
*** haypo has left #openstack-meeting-alt16:33
*** eggmaster has quit IRC16:35
*** zotoff has quit IRC16:36
*** bnemec has joined #openstack-meeting-alt16:37
*** rvyalov_ has quit IRC16:37
*** zotoff has joined #openstack-meeting-alt16:38
*** paul-carlton2 has quit IRC16:38
*** _nadya_ has joined #openstack-meeting-alt16:39
*** irenab has quit IRC16:40
*** kencjohnston has joined #openstack-meeting-alt16:42
*** balajiiyer has quit IRC16:43
*** balajiiyer has joined #openstack-meeting-alt16:43
*** akuznetsov has joined #openstack-meeting-alt16:44
-openstackstatus- NOTICE: Gerrit is restarting quickly as a workaround for performance degradation16:49
*** kebray has joined #openstack-meeting-alt16:49
*** eranra has quit IRC16:51
*** kebray has quit IRC16:51
*** vahidh has joined #openstack-meeting-alt16:53
*** julim has quit IRC16:54
*** vishwanathj has joined #openstack-meeting-alt16:54
*** vishwanathj has quit IRC16:55
*** julim has joined #openstack-meeting-alt16:57
*** ninag has joined #openstack-meeting-alt16:59
ativelkovCourtesy meeting reminder: nikhil_k, ativelkov, mfedosin, docaedo - artifacts subteam meeting17:00
docaedoo/17:00
ativelkov#startmeeting glance_artifacts_sub_team17:00
openstackMeeting started Mon Jan 18 17:00:41 2016 UTC and is due to finish in 60 minutes.  The chair is ativelkov. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: glance_artifacts_sub_team)"17:00
openstackThe meeting name has been set to 'glance_artifacts_sub_team'17:00
docaedoo/17:00
ativelkovhi docaedo, it's great to have you here17:01
ativelkovFolks, anybody else for the artifacts updates?17:01
docaedo:)17:01
kzaitsev_mbeveryone's probably getting ready for m-2 =)17:02
docaedoSince you guys gave me a chance to vote on a new meeting time, and scheduled it at a time when I can actually make it, I'm happy to attend17:02
*** dshakhray has joined #openstack-meeting-alt17:02
ativelkovSo it seems like we don't have much attendance today17:02
ativelkovThe agenda is here: https://etherpad.openstack.org/p/glance-artifacts-sub-team-meeting-agenda17:02
dshakhrayo/17:02
ativelkovSo we have several specs which were frozen due to the spec freeze happened at the end of the year17:03
*** greg_a has joined #openstack-meeting-alt17:03
ativelkovI've asked for the formal FFE exception for them17:04
ativelkovOne is the API refactoring spec, called "Public API"17:04
*** matrohon has quit IRC17:04
ativelkov#link https://review.openstack.org/#/c/254710/17:04
ativelkovThis one addresses most of the defCore and API-WG concerns expressed during the last cycle17:05
*** jjmb has joined #openstack-meeting-alt17:05
*** dims_ has joined #openstack-meeting-alt17:05
ativelkovIts implementation is expected to be fast, however the API approval tends to be a looong process17:05
ativelkovSo, I've asked for the exception: I am sure we'll be able to land the implementation even if the design is approved close to the code freeze17:06
ativelkovAnd the second spec just adds more details on the separation of glance and glare daemon processes17:07
ativelkov#link https://review.openstack.org/#/c/259427/17:07
*** jjmb1 has quit IRC17:07
*** bana_k has quit IRC17:07
ativelkovIt's just a refinement of the previously approved spec, and its implementation is ready long ago.17:08
ativelkovSo I've asked for FFE for this one as well17:08
ativelkovflaper87 told that the decision on these FFE requests will be made later today17:08
docaedoHopefully you'll get it, would be unfortunate not to17:08
*** dims has quit IRC17:08
ativelkovThe third large glare-related spec - on pluggable DB backends seems to be frozen and will be postponed to the N release17:09
*** safchain has quit IRC17:09
*** armax has quit IRC17:09
ativelkovThat's ok, since its implementation requires the public API and other changes to be done first, so we are unlikely to land all of them in Mitaka17:10
*** jokke_ has joined #openstack-meeting-alt17:10
*** davideagnello has joined #openstack-meeting-alt17:10
* jokke_ == late lurker17:10
*** armax has joined #openstack-meeting-alt17:10
*** SridharG has quit IRC17:10
*** hockeynut_afk has joined #openstack-meeting-alt17:10
*** sankarshan is now known as sankarshan_away17:11
*** SridharG has joined #openstack-meeting-alt17:11
ativelkovdocaedo: it would be great if you and your team could review this spec anyway17:11
ativelkovsince it allows to change the DB implementation of glare for particular deployments17:11
*** mhickey has quit IRC17:11
docaedoI added myself as reviewer to the two on the etherpad and will try to read them carefully this morning17:11
ativelkovand is mostly inspired by our conversation at the summi17:11
ativelkov#link https://review.openstack.org/#/c/260447/17:12
docaedonice, I'll do that one too17:12
ativelkovthis one is the third one, it was not present in the etherpad17:12
ativelkovthanks!17:12
ativelkovSo, mfedosin (not present here) promised to begin the work on the actual implementation of Public API spec this week. He probably has something done already, but not submitted to gerrit yet17:13
ativelkovI hope to have some live patch from him on the next week17:13
*** akuznetsov has quit IRC17:13
*** mrmartin has joined #openstack-meeting-alt17:13
*** scheuran has quit IRC17:14
ativelkovOk, that was all on the status update, not much this time17:14
ativelkov#topic open discussion17:14
*** openstack changes topic to "open discussion (Meeting topic: glance_artifacts_sub_team)"17:14
ativelkovAnything else? Questions, suggestions?17:14
*** SridharG has quit IRC17:15
docaedoI'd like to start thinking about how we can 'experiment' with this in relation to the app catalog, but I'm not sure where the best place to start would be17:15
ativelkovdocaedo: well, kzaitsev_mb planned to prototype the current app catalog schema with the current version of the glare17:16
docaedoativelkov: do you have WIP or PoC code that I could play with? Or is it too early?17:16
docaedoah ok, will coordinate with kzaitsev_mb on that17:16
ativelkovtechnically we may use the same code which we showed on the summit for this purpose17:16
*** paul-carlton2 has joined #openstack-meeting-alt17:16
docaedothat's what I figured17:16
ativelkovPLus, we've added the CORS support to glance17:16
docaedo+117:17
ativelkovCORS was one of the issues we discussed with Kevin - he said it could be a blocker. Now we have it enabled for both glance-api and glare-api17:17
docaedothat's great! It would have been an issue (because of interaction between the web site and the horizon plugin)17:17
ativelkovSo we may attempt to use glare from app-catalog javascripts and see if it works as expected17:17
docaedocool, well let me/us know how we can help17:18
ativelkovSure. I'll sync up with kzaitsev on that, we'll let you know on app-catalog meeting on Thursday17:18
docaedogreat thank you!17:18
ativelkovAny other questions?17:19
docaedonot from me :)17:19
*** e0ne has quit IRC17:19
*** SridharG has joined #openstack-meeting-alt17:19
ativelkovOK, thanks, then we may wrap up for today17:19
ativelkovThanks for joining!17:19
jokke_thnx17:20
*** jokke_ has left #openstack-meeting-alt17:20
docaedosure see you later on17:20
ativelkov#endmeeting17:20
*** davidsha has quit IRC17:20
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:20
openstackMeeting ended Mon Jan 18 17:20:10 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance_artifacts_sub_team/2016/glance_artifacts_sub_team.2016-01-18-17.00.html17:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance_artifacts_sub_team/2016/glance_artifacts_sub_team.2016-01-18-17.00.txt17:20
openstackLog:            http://eavesdrop.openstack.org/meetings/glance_artifacts_sub_team/2016/glance_artifacts_sub_team.2016-01-18-17.00.log.html17:20
*** ihrachys has quit IRC17:20
*** iyamahat has joined #openstack-meeting-alt17:21
*** dizquierdo has quit IRC17:21
*** vahidh has quit IRC17:24
*** vishwanathj_ has quit IRC17:25
*** paul-carlton2 has quit IRC17:26
*** _nadya_ has quit IRC17:26
*** achanda has joined #openstack-meeting-alt17:30
*** mrmartin has quit IRC17:34
*** ozamiatin_ has quit IRC17:35
*** mrmartin has joined #openstack-meeting-alt17:35
*** samuelBartel has quit IRC17:35
*** dslevin has joined #openstack-meeting-alt17:36
*** mrmartin has quit IRC17:37
*** kzaitsev_mb has quit IRC17:37
*** mrmartin has joined #openstack-meeting-alt17:38
*** _nadya_ has joined #openstack-meeting-alt17:38
*** dshakhray has quit IRC17:38
*** vahidh has joined #openstack-meeting-alt17:38
*** yamamoto has quit IRC17:40
*** tonytan4ever has quit IRC17:40
*** mrmartin has quit IRC17:42
*** _nadya_ has quit IRC17:42
*** vishwanathj has joined #openstack-meeting-alt17:43
*** fnaval has joined #openstack-meeting-alt17:44
*** Sukhdev has quit IRC17:47
*** fnaval has quit IRC17:55
*** irenab has joined #openstack-meeting-alt17:57
*** vahidh has quit IRC18:00
*** vahidh has joined #openstack-meeting-alt18:00
*** vahidh has quit IRC18:00
*** samuelBartel has joined #openstack-meeting-alt18:01
*** neiljerram has quit IRC18:01
*** derekh has quit IRC18:03
*** macsz has joined #openstack-meeting-alt18:03
*** evgenyf has joined #openstack-meeting-alt18:04
*** zeih has quit IRC18:04
*** andrey-mp has joined #openstack-meeting-alt18:04
*** baoli has joined #openstack-meeting-alt18:04
*** _nadya_ has joined #openstack-meeting-alt18:05
*** fawadkhaliq has quit IRC18:06
*** sgotliv has quit IRC18:07
*** ralonso has quit IRC18:08
*** jjmb1 has joined #openstack-meeting-alt18:09
*** reedip has quit IRC18:09
*** fawadkhaliq has joined #openstack-meeting-alt18:10
*** jjmb has quit IRC18:10
*** fawadkhaliq has quit IRC18:11
*** vishwanathj_ has joined #openstack-meeting-alt18:12
*** paul-carlton2 has joined #openstack-meeting-alt18:13
*** SridharG has quit IRC18:14
*** yamahata has joined #openstack-meeting-alt18:15
*** SridharG has joined #openstack-meeting-alt18:16
*** jjmb has joined #openstack-meeting-alt18:16
*** jjmb1 has quit IRC18:17
*** Sukhdev has joined #openstack-meeting-alt18:17
*** macsz has quit IRC18:18
*** iyamahat has quit IRC18:18
*** jmckind_ has quit IRC18:18
*** irenab has quit IRC18:18
*** iyamahat has joined #openstack-meeting-alt18:18
*** hyamauchi has quit IRC18:19
*** rsyed is now known as rsyed_away18:19
*** angdraug has quit IRC18:19
*** evgenyf has quit IRC18:20
*** davidlenwell has quit IRC18:22
*** david-lyle has quit IRC18:23
*** vahidh has joined #openstack-meeting-alt18:23
*** davidlenwell has joined #openstack-meeting-alt18:24
*** degorenko is now known as _degorenko|afk18:27
*** bana_k has joined #openstack-meeting-alt18:27
*** zotoff has quit IRC18:28
*** dslevin has quit IRC18:30
*** akuznetsov has joined #openstack-meeting-alt18:30
*** evgenyf has joined #openstack-meeting-alt18:30
*** kebray has joined #openstack-meeting-alt18:30
*** rossella_s has quit IRC18:30
*** rossella_s has joined #openstack-meeting-alt18:31
*** neelashah has quit IRC18:32
*** paul-carlton2 has quit IRC18:32
*** SridharG has quit IRC18:33
*** neelashah has joined #openstack-meeting-alt18:33
*** paul-carlton2 has joined #openstack-meeting-alt18:33
*** paul-carlton2 has quit IRC18:36
*** harshs has quit IRC18:37
*** armax has quit IRC18:38
*** neelashah1 has joined #openstack-meeting-alt18:38
*** alexandrelevine has joined #openstack-meeting-alt18:38
*** SridharG has joined #openstack-meeting-alt18:38
*** armax has joined #openstack-meeting-alt18:39
*** neelashah has quit IRC18:39
*** david-lyle has joined #openstack-meeting-alt18:39
*** greg_a has quit IRC18:40
*** jjmb has quit IRC18:43
*** jjmb1 has joined #openstack-meeting-alt18:43
*** dslevin has joined #openstack-meeting-alt18:43
*** ozamiatin_ has joined #openstack-meeting-alt18:43
*** hockeynut_afk is now known as hockeynut18:43
*** david-lyle has quit IRC18:46
*** hyamauchi has joined #openstack-meeting-alt18:47
*** regebro has quit IRC18:47
*** regebro has joined #openstack-meeting-alt18:47
*** greg_a has joined #openstack-meeting-alt18:48
*** akuznetsov has quit IRC18:48
*** kebray has quit IRC18:50
*** annegentle has quit IRC18:51
*** mrmartin has joined #openstack-meeting-alt18:56
*** MarkBaker has joined #openstack-meeting-alt18:56
*** eranra has joined #openstack-meeting-alt18:57
*** pvaneck has joined #openstack-meeting-alt18:57
*** catherineD has joined #openstack-meeting-alt18:59
catherineD#startmeeting refstack19:00
openstackMeeting started Mon Jan 18 19:00:07 2016 UTC and is due to finish in 60 minutes.  The chair is catherineD. 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: refstack)"19:00
openstackThe meeting name has been set to 'refstack'19:00
*** rockyg has joined #openstack-meeting-alt19:02
rockygo/19:02
*** sslypushenko has joined #openstack-meeting-alt19:02
pvanecko/19:02
catherineDrockyg: hello..19:02
hogepodgeo/19:02
alexandrelevineo/19:02
*** Sukhdev has quit IRC19:02
sslypushenkoo/19:02
catherineD#link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-16-01-1819:03
catherineDhello everyone ...19:03
andrey-mpo/19:03
*** Sukhdev has joined #openstack-meeting-alt19:03
catherineDI think we finally get the ball rolling for the Vendor Registration Process tasks ... thx to alexandrelevine: and andrey-mp: ...19:04
*** evgenyf has quit IRC19:04
*** SridharG has quit IRC19:04
rockyg++19:05
catherineD#link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-16-01-1819:05
catherineD#topic DefCore Meeting Jan 13, 201619:05
*** openstack changes topic to "DefCore Meeting Jan 13, 2016 (Meeting topic: refstack)"19:05
catherineD#link I requested DefCore to review Alex's requirement doc https://goo.gl/bvo4FG19:06
*** tellesnobrega_af is now known as tellesnobrega19:06
alexandrelevinecatherineD: Thank you. That's good to hear.19:07
catherineDalexandrelevine: could you allow DefCore core member to add comments to the doc19:07
alexandrelevineAbsolutely, give me the emails19:07
*** ozamiatin_ has quit IRC19:08
*** kfarr has joined #openstack-meeting-alt19:08
catherineDsure rockyg: hogepodge: could you send alexandrelevine: your gmail?19:08
*** kzaitsev_mb has joined #openstack-meeting-alt19:08
catherineDnot sure gmail is really needed ... or any email will do?19:08
rockygit's the mailing list.  hold a sec.  Or Ican send to the list...19:09
*** _nadya_ has quit IRC19:09
rockygany will do.  you just need the link.19:09
hogepodgecatherineD: my openstack e-mail can read google documents19:09
catherineDrockyg: I think Chris, Mark, Egle and Rob will do ...19:09
catherineDfor now19:09
alexandrelevineI can share it with everybody to allow editing if you want19:09
catherineDalexandrelevine: that would be great19:09
*** pnavarro has quit IRC19:10
alexandrelevineEveryone can comment now19:10
*** baoli has quit IRC19:10
catherineDalexandrelevine: DefCore alsop would like to have a summary in Etherpad of the items that RefStack would like DefCore to review.19:10
*** david-lyle has joined #openstack-meeting-alt19:10
*** sbalukoff has joined #openstack-meeting-alt19:11
catherineDalexandrelevine: can you and I create and Etherpad before next DefCore meeting on Wed?19:11
catherineD#link After DefCore review the Etherpad we will request for Mark to update  https://review.openstack.org/#/c/226902/19:12
*** alexandrelevine_ has joined #openstack-meeting-alt19:12
*** tonytan4ever has joined #openstack-meeting-alt19:12
catherineDall good?19:12
*** alexandrelevine_ has joined #openstack-meeting-alt19:13
catherineDmoving to the next topic ...19:13
pvanecksure19:13
catherineD#topic RefStack implementation of Vendor Registration Process19:13
*** openstack changes topic to "RefStack implementation of Vendor Registration Process (Meeting topic: refstack)"19:13
rockygAlso, if you want to join the defcore list and just open the doc to people with the link, the ML is: defcore-committee@lists.openstack.org19:13
alexandrelevine_Sorry, I lost my connection and missed a couple of minutes.19:14
*** achanda has quit IRC19:14
*** alexandrelevine has quit IRC19:14
catherineDalexandrelevine_: we are onto the next topic in the agenda ..19:15
alexandrelevine_perfect19:15
catherineD#link Data model specs https://review.openstack.org/#/c/268922/19:15
catherineD#link https://review.openstack.org/#/c/269184/19:16
catherineDLet's discuss the comment in https://review.openstack.org/#/c/268922/19:16
catherineDDoe we want to add a role attribute at this time ?19:17
catherineDplease see comment in line 57 of https://review.openstack.org/#/c/268922/19:18
*** dslevin has quit IRC19:18
alexandrelevine_I just added a comment.19:19
alexandrelevine_I'm still against it altogether.19:19
alexandrelevine_I explained that regular Vendor users will be achieved by adding another built-in group ID (Users group) into Vendor record.19:19
sslypushenkocatherineD:  I'm little bit confusing from idea to get rid of user role... I saw some related discussion in comments but still can't get a point19:19
alexandrelevine_All of the Users in that Group will have non-admin rigths. No explicit roles required.19:20
sslypushenkoThat is mean that group can not have 2 admins?19:20
catherineDalexandrelevine_: you mean all of the users in that group will have admin right?19:20
alexandrelevine_Role - is a complex thing usually. And it is an extra thing. Unless we really need it I'd suggest we don't introduce it.19:20
sslypushenkoI don't see how things will be working without it19:21
alexandrelevine_catherineD: Each Vendor will have two built-in Groups: Admins (now already), Users (later when needed). That's it. In the Group table we'll be adding users to those two groups.19:21
andrey-mpit can be a two groups in the vendor records - admin group and user group...19:21
catherineDalexandrelevine_: I absolutely think that we need it ... maybe not now but for sure in the future19:21
rockygRole tends to  be a requirement that maps to an implementation, but most implementations implement roles via ACLs or other methods19:21
catherineDsslypushenko: ++19:21
alexandrelevine_We will have implicit role differentiation. I'm against having explicit roles.19:22
sslypushenkoandrey-mp: We can not put roles in vendor table19:22
rockyggroups is the way ACLs are done19:22
catherineDalexandrelevine_: why would we want to do that?  Let say in the future we want top add an other roles we will create an other user group?19:22
sslypushenkobecause vendor can have more than one product19:22
rockygcatherineD, Yup19:22
andrey-mpbtw, why we need regular users in the vendor object?19:23
*** baoli has joined #openstack-meeting-alt19:23
rockygactually, another group, but not user.  Some other name19:23
alexandrelevine_catherineD: Because I don't want to predict whatever requirements might or might not fall on us some long time from now. We need to keep things very simple to move fast..19:23
sslypushenkoAll this idea looks like a try to hardcode some ACL's logic in datastucture19:23
catherineDalexandrelevine_: andrey-mp: I did not see adding a role to the relationship would complicate the tasks.... in fact it helps19:23
alexandrelevine_andrey-mp: It's in the requirements. There is a use-case. I'll tell you in a moment.19:23
sslypushenkoI'm totally against it19:23
catherineDI really think that we should introduce role now ...19:24
alexandrelevine_andrey-mp: The use-case Cloud Operator allows some of his private results or Clouds to be visible for some Users19:24
sslypushenkocatherineD:  100500+ )19:24
catherineDand let a policy file dictate the role privilege ..19:25
catherineDalexandrelevine_: with a policy file ... you can add new role anytime .. no prediction needed ..19:25
*** AlanClark has joined #openstack-meeting-alt19:25
sslypushenkocatherineD: we can introduce policily latter... but we need roles now19:25
*** kzaitsev_mb has quit IRC19:26
alexandrelevine_catherineD: In this case the model doesn't suite at all. Because where would you put those regular users? In the admin group? Why would you want the admin group in the vendor at all in this case? It's just a completely different story.19:26
catherineDsslypushenko: agree19:26
*** kencjohn_ has joined #openstack-meeting-alt19:26
catherineDalexandrelevine_: we still agree with the model ...19:26
sslypushenkoalexandrelevine_:  why we need to put regular users anywere?19:27
alexandrelevine_catherineD: no, it doesn't work with the explicit roles. Role entity is not in the Domain model.19:27
alexandrelevine_catherineD: And it'll have to be rethought quite a bit and I still don't understand the point now.19:27
*** eranra has quit IRC19:27
*** jmckind has joined #openstack-meeting-alt19:27
*** david-lyle_ has joined #openstack-meeting-alt19:27
catherineDalexandrelevine_: the model assum all users that can create an entities are admins of that entities at this time19:28
*** dslev has joined #openstack-meeting-alt19:28
alexandrelevine_sslypushenko: Because they are regular users for some particular Vendor. They are allowed to read objects of such Vendor. No other regular users are allowed to.19:28
rockygalexandrelevine_, I think maybe an etherpad or doc walkthrough of how another "role" would be added via adding a group (or groups) might help with this discussion19:28
*** kencjohnston has quit IRC19:28
catherineDalexandrelevine_: those regular user will have the role=USER19:28
alexandrelevine_sslypushenko: See the use-case in question: 2619:28
*** baoli has quit IRC19:28
sslypushenkoalexandrelevine_:  Hmmm... So how public clouds will live in RefStack?19:29
alexandrelevine_catherineD: Role for what? A user can be an Admin for a couple of Vendors and a regular user for the rest of the objects19:29
*** silos has joined #openstack-meeting-alt19:29
alexandrelevine_Every User has basic rights. Users in Vendor Admin groups also have rights for those Vendors.19:30
rockygalexandrelevine_, an example of users and admins on a public cloud offering could help explain how you see this working.19:30
catherineDRepeat question 26: Cloud Operator allows some of his private results or Clouds to be visible for some Users19:30
*** numans has quit IRC19:30
pvaneckIs a vendor not just associated with one group id?19:30
rockygMaybe for next week?19:30
rockygVendor could be associated with multiple groups.19:31
*** david-lyle has quit IRC19:31
andrey-mppvaneck: right now we had such assumption )19:31
catherineDfor question 26.... if a User wants to see private data of an Cloud Operator , that user should belong to the group of the Cloud_operator with role=USER19:31
rockygVendor, vendor-product-admin, vendor-product-user, vendor-admin, vendor-product2-user, etc19:32
alexandrelevine_pvaneck: Vendor is associated with one Group ID. User can be in many groups.19:32
*** jmckind has quit IRC19:32
*** baoli has joined #openstack-meeting-alt19:32
*** salv-orlando has joined #openstack-meeting-alt19:32
andrey-mprockyg: what case of association vendor with many groups?19:32
alexandrelevine_andrey-mp: There is no such case19:33
sslypushenkoalexandrelevine_: So how we will give admin privileges?19:33
*** jjmb has joined #openstack-meeting-alt19:33
sslypushenkorecord in product table?19:33
alexandrelevine_sslypushenko: Users registered in particular built-in admin Vendor group will have admin priviliges for this vendor.19:33
andrey-mpi thought that all users in the group linked with vendor are admins of this vendor19:33
pvaneckwith just one group per vendor, then group roles should facilitate the different permission levels needed by these use cases19:33
rockygUnless all vendor associated groups (users, admins, plus all product options) are under one group id, vendor has to own multiple groups19:34
catherineDandrey-mp: that is the initial implementation ...19:34
catherineDpvaneck: ++19:34
sslypushenkoalexandrelevine_: It will be better to have product admin group instead on vendor admin...19:34
catherineDalexandrelevine_: I have a feeling that the term USER means different thing for you and for me sslypushenko: and pvaneck:19:34
sslypushenkoI think I manage to get your point19:34
rockygso, either multiple vendor owned groups, or single vendor group with roles.  Two ways to implement19:35
*** fawadkhaliq has joined #openstack-meeting-alt19:35
*** jjmb1 has quit IRC19:35
alexandrelevine_One Vendor - One Group. Users in this Group are admins of the Vendor.19:35
catherineDsslypushenko: this is the point that alexandrelevine_: had discussed ... a group should be associated to a product too ... but it will be the next implementation19:36
sslypushenkoalexandrelevine_: Hmm... but what about private test result?19:36
catherineDalexandrelevine_: One vendor , one group, Users in this group can be admin or read only user ...19:36
catherineDread only user can view private results of that vendor19:37
*** david-lyle_ has quit IRC19:37
catherineDand that is implemented by introducing role of user in that group ...19:37
pvaneckI feel like we just need a toggle for if a user is admin or non-admin in a specific group if you want some users to only have read-only access19:37
catherineDpvaneck: yup that is fine by we need role ... admin and non-admin19:38
catherineDso my vote is to keep the role column in the user-group relationship table ...19:38
sslypushenkocatherineD: +119:38
*** sgotliv has joined #openstack-meeting-alt19:39
catherineDshould we vote?19:39
*** david-lyle has joined #openstack-meeting-alt19:39
sslypushenkoat least 2 rooles19:39
catherineDyup19:39
rockygCould keep it in and if i looks like it adds no value, it can be removed later?19:39
alexandrelevine_I'm sorry. I have an urgent call now.19:39
catherineDalexandrelevine_: ok np19:39
*** baoli has quit IRC19:40
catherineDwe can just discuss the next item and will make decision with your present ..19:40
*** narengan has joined #openstack-meeting-alt19:40
*** achanda has joined #openstack-meeting-alt19:40
andrey-mplets move to next )19:40
catherineD#agree we will vote on having a role column in the user-group relationship table later19:41
*** baoli has joined #openstack-meeting-alt19:41
*** mrmartin has quit IRC19:41
catherineD#agreed we will vote on having a ROLE column in the usdr-group relationship table later19:41
catherineD#topic Auditability implementation for RefStack?  Do we need the "updated" columns?19:42
*** openstack changes topic to "Auditability implementation for RefStack? Do we need the "updated" columns? (Meeting topic: refstack)"19:42
*** baoli has quit IRC19:42
*** evgenyf has joined #openstack-meeting-alt19:42
catherineDplease see comments on line 126 of https://review.openstack.org/#/c/268922/19:42
catherineDI know this is not perfect .. but with the updated column .. at least we know who is updating the record last ...19:43
sslypushenkoI don't get a point of this field19:43
catherineDpreferly audit should be done by database log ...19:43
andrey-mpi think that if we need logging that it is better to create 'add-only' table with all records.19:44
andrey-mpis database can help? it contains operations from only one user - refstack site19:44
sslypushenkoIf we want to have some logging we should do it in some other way19:44
*** zeih has joined #openstack-meeting-alt19:44
catherineDsslypushenko: let say someone changes the role from user to admin ... the user who makes the update will be loggoed19:44
catherineDsslypushenko: agree ... but in the interim .... is there something we can do?19:45
sslypushenkobut do we need such kind of logging19:45
sslypushenko?19:45
andrey-mpi mean that all operations with refstack db is done by refstack site that means 'refstack' user.19:46
rockygdoes the DB have that function as part of the config?19:46
catherineDsslypushenko:  see line 163 of https://review.openstack.org/#/c/226902/19:46
catherineDrockyg: db will have the log ... but we need log analysis tools ...19:46
andrey-mpmay be it is better to implement 'add-only' logging table later?19:46
*** david-lyle has quit IRC19:46
catherineDandrey-mp: would that e an additional table?19:47
andrey-mpyes19:47
rockygcatherineD, if we've got the logging, then the analysis should be outside the db.19:48
catherineDwe can remove the updated column (which is not perfect for auditting )  we jsut need to communicate to DefCore that auditting will be implemanted later ..19:48
rockygAlthough last change would at least give a starting point on where to look in logs.19:48
andrey-mptable that doesn't linked with the system but contains all (or specific) write operations. and later some can analyse this table for information...19:48
catherineDandrey-mp: ++19:49
*** _nadya_ has joined #openstack-meeting-alt19:49
sslypushenkoandrey-mp: That is sounds good19:49
catherineDrockyg: hogepodge: DefCore should be OK with us not implementing auditting at the initial phase?19:49
andrey-mp:)19:49
catherineDso do we all agree that we do not need the updated columns?19:50
*** silos has quit IRC19:50
hogepodgecatherineD: I think so19:50
*** hyamauchi has quit IRC19:50
catherineDsslypushenko: pvaneck: rockyg: your thoughts?  I know andrey-mp: wants to have it removed ..19:51
*** salv-orlando has quit IRC19:51
rockygworks for me.  As long as logging is there, we have the info.  Just not great access.19:51
pvaneckYea, i think an eventual audit_log table would be best19:51
sslypushenkocatherineD: It looks like it is early for now19:51
sslypushenkopvaneck: +119:52
catherineD#agreed Autting function will be implemented later.  Remove the "updated" related columns in all tables.19:52
catherineD#topic Do we need the "deleted" columns?19:53
*** openstack changes topic to "Do we need the "deleted" columns? (Meeting topic: refstack)"19:53
*** alexandrelevine_ has quit IRC19:53
*** achanda has quit IRC19:53
sslypushenkoyeap19:53
catherineDpls see comment line 138 https://review.openstack.org/#/c/268922/19:53
sslypushenkoI think we need soft delete19:53
sslypushenkoit is part of functionality of oslo-db19:54
catherineDjust a time check ...we only have 6 mins to go ... could we continue our discussion at #refstack after this ...19:54
*** hyamauchi has joined #openstack-meeting-alt19:54
*** kzaitsev_mb has joined #openstack-meeting-alt19:54
sslypushenko+119:54
andrey-mpyes19:54
catherineDwe have the momentum going so I really like us to continue discussion .....19:55
catherineDthank you19:55
*** evgenyf has quit IRC19:55
catherineDsslypushenko: so I have not seen RefStack using the delete column in the existing tables...19:55
sslypushenkothat is right19:55
*** fawadkhaliq has quit IRC19:56
catherineDbut I guess if that is part of  oslo-db  ... then we may want to keep it19:56
sslypushenkobut I think we need it... it is kind of openstack way)19:56
*** e0ne has joined #openstack-meeting-alt19:56
catherineDalright ... but before our final decision let review the next topic ... because it is related ... we will come back to this item in a bit19:57
andrey-mpwe can leave these two columns and use them later )19:57
catherineD#topic Do we want to enforce organization/product name to be unique?19:57
*** openstack changes topic to "Do we want to enforce organization/product name to be unique? (Meeting topic: refstack)"19:57
*** narengan12 has joined #openstack-meeting-alt19:57
catherineDandrey-mp: +19:57
*** narengan has quit IRC19:57
catherineDThat means that the name will be unique based on spelling only not upper/lower case ... so Private Cloud and PRIVATE CLOUD are the same name for us ...19:59
*** jmckind_ has joined #openstack-meeting-alt19:59
catherineDlet move to #refstack ...19:59
sslypushenko+19:59
andrey-mpI don't have strong desicion on this but my thoughts that we don't need it19:59
andrey-mpmoving...19:59
catherineD#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:59
openstackMeeting ended Mon Jan 18 19:59:41 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2016/refstack.2016-01-18-19.00.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2016/refstack.2016-01-18-19.00.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2016/refstack.2016-01-18-19.00.log.html19:59
*** catherineD has left #openstack-meeting-alt20:00
redrobot#startmeeting barbican20:00
openstackMeeting started Mon Jan 18 20:00:46 2016 UTC and is due to finish in 60 minutes.  The chair is redrobot. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: barbican)"20:00
openstackThe meeting name has been set to 'barbican'20:00
redrobot#topic Roll Call20:00
*** openstack changes topic to "Roll Call (Meeting topic: barbican)"20:00
woodster_o/20:01
diazjf0/20:01
spotzo/20:01
jmckind_\o/20:01
edtubillo/20:01
kfarro/20:01
redrobotall the usual suspects :)20:02
*** andrey-mp has quit IRC20:02
*** arunkant has joined #openstack-meeting-alt20:02
arunkanto/20:02
redrobotAs usual the agenda can be found here:20:03
redrobot#link https://wiki.openstack.org/wiki/Meetings/Barbican#Agenda20:03
redrobot#topic Action Items20:04
*** openstack changes topic to "Action Items (Meeting topic: barbican)"20:04
redrobot#link http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-01-04-20.00.html20:04
redrobotI had a ton of action items, but only finished one20:04
redrobotso I have to punt on a couple20:04
redrobot#action redrobot to check on status of reported security bug20:04
redrobot#action redrobot to ping ccneill about the nova+cinder security bug20:04
*** neelashah has joined #openstack-meeting-alt20:05
*** baoli has joined #openstack-meeting-alt20:05
redrobot#topic Liaison Updates20:05
*** openstack changes topic to "Liaison Updates (Meeting topic: barbican)"20:05
redrobotI half-attended the oslo meeting this morning20:05
*** mp1 has joined #openstack-meeting-alt20:05
redrobotlooks like the mitaka-2 releases for oslo.* have been released20:05
redrobotAny other liaison updates?20:06
*** _nadya_ has quit IRC20:06
redrobothockeynut isn't here so I'll skip QA20:06
*** neelashah1 has quit IRC20:06
redrobotsomeone pinged me about documentation...  looks like we'll be having to write some WADLs and such to get our API docs up to spec20:07
redrobotbut I was busy with midcycle things so I haven't had a chance to look into all the work that needs to be done20:07
redrobot#action redrobot to follow up with Anne Gentle re: docs20:07
diazjfredrobot, I know a couple people here would like to join the effort on updating docs20:08
redrobotalee isn't here either so I'll skip the Magnum cross-project stuff20:08
redrobotdiazjf cool, I'll keep you posted with what I find out20:08
redrobotok, on to the agenda for today20:08
*** kebray has joined #openstack-meeting-alt20:08
redrobotwhich I'm going to make up on the fly, because nobody added anything to the wiki20:08
redrobot#topic Mid-Cycle Recap20:09
*** openstack changes topic to "Mid-Cycle Recap (Meeting topic: barbican)"20:09
redrobot#link https://etherpad.openstack.org/p/barbican-mitaka-midcycle20:09
*** neelashah1 has joined #openstack-meeting-alt20:09
redrobotThe mid-cycle meetup last week was awesome.  Many thanks to everyone who made the trip down to San Antonio20:09
*** silos has joined #openstack-meeting-alt20:09
*** neelashah has quit IRC20:09
edtubillthanks for having us it was fun.20:09
siloso/20:10
*** baoli has quit IRC20:10
*** shayneburgess has joined #openstack-meeting-alt20:10
*** shayneburgess has quit IRC20:10
redrobotThere's lots of notes in the etherpad, including a lot of ACTION items20:10
*** kebray has quit IRC20:10
redrobotsome of those have not been claimed, so if anyone is looking for things to do, have a gander at the etherpad20:10
*** rellerreller has joined #openstack-meeting-alt20:11
rellerrellero/ (sorry I'm late)20:12
redrobotalso, for those of you interested in Federation, diazjf will be working on a cross-project effort to get Push BYOK into OpenStack20:12
redrobotrellerreller gonna need you to stay for 12 min after the meeting is over. :-P20:12
rellerrellerredrobot booo :(20:12
diazjfredrobot, I'll have a spec up in OS-Security by the end of the week 8-)20:12
hockeynutredrobot hockeynut is in another meeting :-(20:13
*** fredyx10 has quit IRC20:13
*** spzala has joined #openstack-meeting-alt20:13
*** fredyx10 has joined #openstack-meeting-alt20:13
rellerrellerdiazjf is that for byok?20:13
redrobotrellerreller yep20:13
*** neelashah1 has quit IRC20:13
*** angdraug has joined #openstack-meeting-alt20:14
diazjfrellerreller, yup see https://etherpad.openstack.org/p/cEA79A5fG120:14
*** neelashah has joined #openstack-meeting-alt20:14
redrobotrellerreller we had a few cross-team discussions with the ossp folks, and the consensus was that Push-model (where the client always provides the key) would be a good starting point.20:14
diazjf^ general notes from the midcycle20:14
redrobotthe idea is to bring an implementation plan to the Austin summit and talk about it during the cross-project design sessions.20:15
redrobotanyway, awesome stuff during the midcycle20:16
redrobotalthough we didn't land much in the way of blueprints20:16
redrobotwhich brings me to the next topic20:16
redrobot#topic Blueprint: API healthcheck20:16
*** openstack changes topic to "Blueprint: API healthcheck (Meeting topic: barbican)"20:16
redrobot#link https://review.openstack.org/#/c/207317/20:16
redrobotthere were some concerns about this BP20:17
redrobotI think that as long as this is an optional endpoint, and disabled by default, then I would be for adding it20:17
*** dprince has quit IRC20:17
woodster_sounds reasonable20:18
*** kebray has joined #openstack-meeting-alt20:19
*** tonytan4ever has quit IRC20:19
redrobotrellerreller what do you think?  I recall you being concerned about the new unauthenticated resource20:19
rellerrellerI would rather see it have access controls in place and then if you want it like the spec describes then allow all read.20:20
rellerrellerI think it is better to have the security baked in up front as opposed to later.20:20
rellerrellerBut if it is optional it's not a big deal for me.20:20
woodster_rellerreller:  so deployers would mod their policy json files for that call then?20:21
redrobotrellerreller so you'd like to see the default policy need auth for it, even if it's opt-in ?20:21
rellerrellerwoodster_ yes20:21
rellerrellerwoodster_ you would modify policy to allow all and then continue as normal20:21
*** jhfeng has joined #openstack-meeting-alt20:21
rellerrellerredrobot yes20:21
redrobotseems reasonable to me.  I'll add a comment to the spec linking back to this meeting.20:22
rellerrellerI feel like if it is not added now then people will enable it and there will be informatio leak20:22
redrobot#agreed Healthcheck endpoint should be authenticated in the default policy file, and disabled in the default paste config.20:22
rellerrellerI also think it will fit the pattern of the other end points as well. This one won't look any different.20:22
*** korzen has quit IRC20:23
woodster_rellerreller:  shold this be an admin only access then?20:23
rellerrellerMy only other comment on that one was about the return value.20:23
*** annegentle has joined #openstack-meeting-alt20:23
rellerrellerwoodster_ I think admin would be good.20:23
redrobotrellerreller woodster_ to be clear, this should be accesible only by the service-admin (the account owned by the deployer)20:24
rellerrellerI was wondering why not return different error codes for different errors?20:24
redrobot?20:24
rellerrellerredrobot that sounds good to me.20:24
*** vishwanathj_ has quit IRC20:25
rellerrellerIt seems like if returning a more specific error code would be helpful. That way can begin to identify source of issue (db, threading, etc.)20:25
redrobotrellerreller haven't looked at an exhaustive list of 5xx errors lately, but it makes sense to return different ones where appropriate20:25
*** tonytan4ever has joined #openstack-meeting-alt20:25
redrobotI'll leave that as a comment as well, since jkf isn't here to talk about the spec20:26
rellerrellerredrobot not 5xx errors from web server, but application defined error codes.20:26
redrobotrellerreller ah I see...  I think there was a concern about information leak, but if we're locking it down by default, then error codes may make sense.20:26
*** fredyx10 has quit IRC20:26
rellerrellerredrobot those are my thoughts exactly.20:27
redrobotok, I think we've got enough to move this BP forward20:27
redroboton to the next one20:27
woodster_please add comments to the blueprint for sure20:27
rellerrellerwill do20:28
redrobot#topic Blueprint: Mutiple secret-store backends20:28
*** openstack changes topic to "Blueprint: Mutiple secret-store backends (Meeting topic: barbican)"20:28
redrobot#link https://review.openstack.org/#/c/263972/20:28
redrobotI don't particularly care for this BP.  I fundamentally disagree with the assumption that separate endpoints for distinct backends are "not a good user experience"20:29
*** fredyx10 has joined #openstack-meeting-alt20:29
redrobotthat said, I seemed to be the only dissenting one at the midcycle20:29
rellerrellerI am dissenting20:29
arunkantredrobot: I see some good comments from alee so will update this one. rellerreller: Is it possible to remove -2 so that larger community can provide comments on this.20:30
rellerrellerI don't see how the other services will know which backend to use.20:30
redrobotrellerreller I think you and I are the minority here20:30
redrobotAs I understand the BP, the backend would be configurable per-project20:30
rellerrellerredrobot what are your thoughts on -2?20:30
woodster_rellerreller:  it is similar to how CAs are discovered now...there would be a ca_id sort of thing optionally specified to designate a secret store backend20:31
rellerrellerredrobot I put -2 to make sure not merged because I have strong reservations against it. I did not want it to be merge, but I also don't want to block discussion.20:31
rellerrellerI'm not exactly sure of the policy on that stuff.20:31
woodster_rellerreller:  ...and project-configured default backends20:31
redrobotrellerreller I'm not sure whether -2 discourages reviews from other reviewers.20:32
*** sslypushenko has left #openstack-meeting-alt20:33
woodster_Overall I like the possibility of having different 'qualities of service' for secrets in barbican20:33
redrobotrellerreller I would personally only -1, because I disagree with the BP but I'm deferring to others to weigh in on it too, and possibly merged if it gets enough support.20:33
woodster_...but that is the sort of discussion to have on the blueprint CR I suppose :)20:33
redrobotrellerreller sounds like you have a hard stance against it though, so -2 seems appropriate.20:33
rellerrellerwoodster_ +1, but I'm not sure if this is the best way to achieve that.20:33
arunkantredrobot: I have seen people even not looking into spec if it has -2 on it.20:34
woodster_rellerreller:  if you can pitch an alternate approach that would be cool as well20:34
rellerrellerredrobot I do feel strongly about this one. Until I know for sure this will not break features, which I believe it will, then I would not like for this to merge. It is a big change.20:34
redrobotwoodster_ the alternate approach is already in the BP.  basically use different deployments of Barbican for different backends.20:34
woodster_redrobot:  oh got it I though rellerreller had a different idea in mind20:35
rellerrellerNo, that was it.20:35
*** vgridnev has joined #openstack-meeting-alt20:36
arunkantrellerreller: alee has already commented on transport key topic in spec and as per midcycle disucssion, I don't recall any isse around that during discussion20:36
rellerrellerI'm worried about relationships between keys and how that would work.20:36
*** sigmavirus24 is now known as sigmavirus24_awa20:37
redrobotso one of the use cases that made sense to me was for a big cloud offering Barbican aaS, then upselling the customer into a "more secure hsm-backed" backend for more $ and still have them use the same endpoint.20:37
rellerrellerLike can I create a container that has keys in two different backends?20:37
woodster_My preference is to tag secrets with quality of service explicitly, then the backend is selected automatically/optionally based on that, but that could wait till later.20:37
rellerrellerI would like to see key wrapping at some point. What if my keys are in two different backends?20:37
woodster_rellerreller:  containers are just lightweight collections of secrets...the secrets are independent20:37
*** sigmavirus24_awa is now known as sigmavirus2420:37
arunkantrellerreller: Whatever is the concern, that can be raised in spec review. Please jJust don't block the discussion. We have very valid use-cases around this.20:38
rellerrellerI'm not blocking the discussion. The discussion can happen and should.20:38
*** markvoelker has joined #openstack-meeting-alt20:38
redrobotarunkant if there are Barbican cores that are avoiding the review because of the -2 please let me/them know.  I don't think we should ignore reviews based on a single dissenting vote.20:39
*** weshay has quit IRC20:40
arunkantredrobot: What -2 means..that this spec can never be merged. The concerns raised have been discussed nd updated in spec. I don't see why it needs to have -2 if there are some specific concern.20:41
arunkantredrobot: I don't have any control on how other people behave when they see -2 or -1..but generally -2 means, its blocked so people would not even go there to review.20:43
arunkantredrobot: I think there was enough consensus in mid-cycle and people have interest in having this feature.20:44
redrobotarunkant I understand your concern, but I think that since rellerreller has a strong opinion on this, that the -2 from him is appropriate.  Like I said, if you feel other reviewers are not reviewing because of it, let me know.20:44
redrobotarunkant there was, but currently there are no +X votes on there.20:44
redrobotarunkant and I do apologize for not setting up a hangout last Friday20:45
arunkantredrobot: alee has already reviewed it and you were also reviewing in midcycle.20:45
redrobotarunkant I was tied up with OSSP mid-cycle20:45
arunkantI believe _woodster was also okay with the idea.20:46
woodster_it would probably be good for everyone's action items this week to review the blueprints out there...folks are standing by to implement them and we are running out of time in this cycle20:46
redrobotwoodster_ +120:46
woodster_arunkant:  the feature seems useful to me for sure20:47
*** mhickey has joined #openstack-meeting-alt20:47
arunkantI don't see any outstanding question from rellerreller on this..other than we may want to implement key wrapping in some future ..and that may have some issue.20:47
*** zeih has quit IRC20:47
*** dslevin has joined #openstack-meeting-alt20:48
redrobotI think the concern was around the added complexity of having concurrent backends and the implications for other features, such as containers.20:48
arunkantredrobot: I am not sure what complexity, it adds. Its new feature quite similar to CA support which alee added in liberty.20:49
rellerrellerYes, key dependencies/transport keys, added complexity, and implications for other features20:50
*** bana_k has quit IRC20:51
arunkantI don't see what kind of complexity is being talked here. Its opt-in feature which can be very useful in many private cloud deployments.20:51
redrobotI'm going to table this discussion...  maybe we can get alee and woodster_ to give some positive reviews of the BP20:51
redrobotthen revisit later this week, maybe do a google hangout20:52
redrobot#topic Blueprint: DB cleanup20:53
*** openstack changes topic to "Blueprint: DB cleanup (Meeting topic: barbican)"20:53
edtubillok20:53
redrobotedtubill you were talking about this yes?20:53
*** ihrachys has joined #openstack-meeting-alt20:53
arunkantredrobot: I am all for discussion and making the spec better if there are any technical or functional concern but cannot answer on future features.20:53
*** jjmb1 has joined #openstack-meeting-alt20:53
edtubillyes, there were some constraints that I was worried about, so I wanted to set up a hangout later on so we can discuss this.20:54
edtubillAnd wanted other people to join in if interested20:54
redrobotok, so to summarize for other folks20:54
redrobot(and try to fit into a few min)20:54
redrobotedtubill is working on a BP to clean up the DB20:54
*** annegentle has quit IRC20:55
redrobotedtubill a new function of barbican-manage would delete soft-deleted and expired secrets.20:55
*** amotoki has joined #openstack-meeting-alt20:55
*** weshay has joined #openstack-meeting-alt20:55
redrobothowever, currently Orders has a non-nullable reference to Secret20:55
*** jjmb has quit IRC20:55
*** annegentle has joined #openstack-meeting-alt20:55
edtubillok, so for that was a false concern20:55
redrobotwhich means we can't delete Secrets that were created by an order even if the Secret is soft-deleted or expired20:56
redrobot...20:56
edtubillI looked at it again and it is nullable, but I would need to set it to null first.20:56
redrobotor I may be making up stuff :D20:56
edtubill:) no that was my bad. But there was another thing for order_retry_tasks that I was worried about.20:56
*** hichihara has joined #openstack-meeting-alt20:56
edtubillfor what happens if someone deletes an order when it was in the retry queue20:56
redrobotedtubill does it affect the clean up Secrets BP?20:57
*** baoli has joined #openstack-meeting-alt20:57
edtubillit shouldn't really, but I'm more interested in getting info on implementation wise.20:57
*** stack_ has joined #openstack-meeting-alt20:57
edtubillThe blue print will be the same, I will make another blue print for expiring secrets.20:57
woodster_edtubill: the worker processing that request would raise an error due to a non-existent order, but would juts report/log that and the move on20:58
*** cloudrancher has joined #openstack-meeting-alt20:58
*** vgridnev has quit IRC20:58
redrobotedtubill  I thought the current BPs would focus on cleaning up Secrets only?20:58
edtubillwooderster_, but would it be cleaned up afterwards?20:58
edtubillredrobot, the blue print is for anything that is soft deletable20:58
*** lisaclark has joined #openstack-meeting-alt20:58
edtubillwe aren't touching orders unless it is soft deleted.20:59
redrobotedtubill ok, cool20:59
redrobotalmost out of time here... we can continue discussion on #openstack-barbican if people want to stick around.20:59
redrobotthanks for coming everyone20:59
redrobot#endmeeting20:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:59
woodster_edtubill:  I still think cleaning up deleted orders (or orders with deleted secrets) is important, just not a show stopper necessarily initially20:59
openstackMeeting ended Mon Jan 18 20:59:42 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-01-18-20.00.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-01-18-20.00.txt20:59
*** arunkant has left #openstack-meeting-alt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-01-18-20.00.log.html20:59
*** mp1 has left #openstack-meeting-alt21:00
*** silos has left #openstack-meeting-alt21:00
* hughhalf yawns21:00
*** baoli has quit IRC21:00
shamail#startmeeting product working group21:00
openstackMeeting started Mon Jan 18 21:00:47 2016 UTC and is due to finish in 60 minutes.  The chair is shamail. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: product working group)"21:00
openstackThe meeting name has been set to 'product_working_group'21:00
*** MeganR has joined #openstack-meeting-alt21:00
shamailHi everyone21:00
shamailRoll call?21:01
cloudrancherKau21:01
cloudrancherwow - can't type Jay21:01
shamail:)21:01
hughhalfHugh o/21:01
*** narengan12 has quit IRC21:01
* MarkBaker here21:01
rockygo/21:01
MeganRo/21:01
shamailHi cloudrancher, hughhalf, MarkBaker, MeganR, and rockyg21:01
thingeeo/21:01
shamailHi thingee21:02
kencjohn_o/21:02
shamailhi kencjohn_21:02
shamailpretty good turn out!21:02
*** stack_ is now known as narengan21:02
*** kencjohn_ has quit IRC21:02
sgordono/21:02
shamailBefore we get started, MarkBaker... Can you please do a brief introduction since you are new to the team?21:02
shamailhi sgordon21:03
*** kencjohnston has joined #openstack-meeting-alt21:03
kencjohnstono/21:03
shamailwelcome back21:03
kencjohnstonshamail thanks :)21:03
shamailping MarkBaker21:03
shamailToday's agenda...21:04
MarkBakershamail, of course: I am OpenStack Product manager at Canonical where I've been for 5 years. Previously Red Hat and MySQL21:04
shamailThanks MarkBaker!21:04
shamailWelcome to the team.21:04
*** ihrachys_ has joined #openstack-meeting-alt21:04
shamailHere is the agenda for today:21:04
shamail#link https://wiki.openstack.org/wiki/Meetings/product-team21:04
shamail#topic User Story Status Review21:04
*** openstack changes topic to "User Story Status Review (Meeting topic: product working group)"21:04
shamailLet's start with user story status updates... anyone want to begin?21:05
kencjohnstonI'll start21:05
shamailthanks.21:05
kencjohnstonFor rolling upgrades I was slow to submit a new patch based on initial comments21:05
kencjohnstonbut patch set 6 is up that I think clears up most of the comments21:05
kencjohnston#link https://review.openstack.org/#/c/255633/21:05
*** dark_15 is now known as FCC21:05
kencjohnstonMost of them came from arkady, who I don't see here.21:06
kencjohnstonBut he had great feedback on incorporating both updates and upgrades into the story21:06
kencjohnstonso you will see that throughout, not just in the gaps analysis21:06
*** Heidi_ has joined #openstack-meeting-alt21:06
*** FCC is now known as dark_1521:06
kencjohnstonNext step is incorporating current state into the tracker21:06
*** vilobhmm11 has joined #openstack-meeting-alt21:06
rockyg++21:06
kencjohnstonwhich I thnk is still pending review21:06
shamailArkady is unable to join today but I am sure he will see the change.21:06
*** ihrachy__ has joined #openstack-meeting-alt21:07
shamailThanks kencjohnston!  I'll review the new user story in the next couple of days too.21:07
kencjohnstonthanks shamail21:07
kencjohnstonany questions?21:07
kencjohnstoncomments, concerns, highfives?21:07
*** ihrachy__ is now known as ihrachysh21:07
* shamail gives kencjohnston a high five21:07
* hughhalf throws a streamer21:07
shamailWho's next?  sgordon, cloudrancher?21:08
kencjohnstonthanks shamail hughhalf I'm just going to take the rest of the year off21:08
shamaillol21:08
*** ihrachys has quit IRC21:08
*** nateziemann has joined #openstack-meeting-alt21:08
* rockyg pops a bottle of champaigne21:08
hughhalfseems legit kencjohnston21:08
*** nateziemann has quit IRC21:08
*** nateziemann has joined #openstack-meeting-alt21:09
shamailsgordon, can you please provide an update on CIM?21:09
shamailcloudrancher, are you here?21:09
*** ihrachys_ has quit IRC21:09
cloudrancheryes I am21:09
shamailOkay, let's move on to onboarding legacy infra21:10
shamailAny updates?21:10
cloudranchersubmitted patch to user story to incorporate toleration of changes by non openstack management21:10
cloudrancherprimarily driven by VMware21:10
sgordonno change atm, still clawing my way back to the top of the pile21:10
sgordoni have a separate submission i am working up to put in draft state21:10
shamailThanks sgordon21:10
shamailcloudrancher, thanks... I haven't had a chance to review the user story submission yet.  I'll put that on my list as well21:11
cloudrancherother than the patch to the user story work is proceeding on blueprints.21:11
cloudrancherthat's it for now21:11
kencjohnstoncloudrancher and all. I had a question about the intent of our review process.21:11
shamailDo you have a team identified that is helping with that piece?  Has gaps analysis been completed already?21:11
kencjohnstonPerhaps an agenda topic for another day.21:12
cloudranchersounds fair21:12
shamailWhat's the question kencjohnston?  That way we can either take it up or add as an agenda item?21:12
*** achanda has joined #openstack-meeting-alt21:12
kencjohnstonWhile reviewing should we debate the usefulness/priority/value of the user story?21:12
shamailMy take is that it depends on the stage of the user story21:13
shamailI don't think we should during submission to "draft"21:13
kencjohnstonOK, fair.21:13
shamailbut anything above that stage should include discussion on the usefulness21:13
rockyg++21:13
kencjohnstongot it shamail thanks21:14
shamailThanks, good question though... Maybe we should create a FAQ and add it (along with other questions that I am sure will come up)21:14
kencjohnstonsure, I can take an action item to start that FAQ21:14
shamailThanks for the update cloudrancher!!21:14
cloudranchernp21:14
shamailthanks kencjohnston21:14
*** iyamahat has quit IRC21:15
shamail#action kencjohnston will create FAQ on wiki for us to start building a knowledge base.21:15
kencjohnstonand just so I'm not speaking obliquely cloudrancher I'm sure you saw my review comments on your resent patch.21:15
kencjohnstontrying to find the link now21:15
cloudrancheryes21:15
cloudrancherI understand21:15
*** AlanClark has quit IRC21:15
kencjohnstonok, cool21:15
cloudrancherthe whole synchronization issue is peculiar to onboarding legacy21:15
shamailAlright, we'll skip onboarding legacy apps21:15
shamailLeong is off today!21:16
shamailFor lifecycle management, we still don't have a team but I know there is some interest in IBM21:16
shamailping nateziemann, are you here?21:16
*** achanda has quit IRC21:17
shamailHe might be afk, but i'll ask him later if we can identify people to help with that one.21:17
shamailThanks for the updates everyone!21:17
shamail#topic Review of action items assigned at previous meeting21:17
*** openstack changes topic to "Review of action items assigned at previous meeting (Meeting topic: product working group)"21:17
shamail#link http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-01-11-21.00.html21:17
shamailThere were a few action items from the last meeting and I believe most are closed...21:18
shamailA new etherpad has been created (by rockyg) to capture potential session ideas for Austin21:18
shamailwe will go through that during a later section in the agenda21:18
shamailI have not created the "CPL updates" calendar yet21:19
shamailI will create one this week and send to our ML21:19
shamailLeong did create a patch to make user stories be folders inside the "proposed" folder.21:19
shamailkencjohnston, the patch that you linked earlier... that one uses the new format... does it override the patch submitted by Leong?21:19
shamailWe currently have 2-3 patches open for rolling upgrades and I think only one needs to move forward while the others can be abandoned21:20
kencjohnstonshamail yes, he abandoned that patch due to dependency on my ongoing review21:20
shamailPerfect! thanks.21:20
*** fnaval has joined #openstack-meeting-alt21:20
shamailMoving to the next topic!21:20
*** tonytan4ever has quit IRC21:20
shamail#topic Review non-merged patches21:21
*** openstack changes topic to "Review non-merged patches (Meeting topic: product working group)"21:21
shamail#link https://review.openstack.org/#/q/status:open+project:openstack/openstack-user-stories21:21
shamailThe link directs you to all the open patches for openstack-user-stories... I would kindly ask that people save this link and try to review the patches once every week or two (at a minimum)21:21
kencjohnstonRolling upgrades is ongoing21:22
kencjohnstonTracker is ongoing21:22
shamailIt would be great to get additional feedback on the user stories (and templates) via gerrit21:22
shamailI have updated tracker to include your suggestions kencjohnston21:22
shamailPlease revisit it when you have time21:22
kencjohnstoncloudrancher I think https://review.openstack.org/268207 was in error21:22
kencjohnstonand was supposed to be a new patch on https://review.openstack.org/26606821:22
shamailagreed21:23
*** bana_k has joined #openstack-meeting-alt21:23
shamailThe ones with -1 on workflow should be abandoned21:23
shamailI think they have been superceded21:23
shamailDoes everyone agree?21:23
kencjohnstonshamail +121:24
cloudrancher+121:24
MeganR+121:24
*** neelashah has quit IRC21:24
*** neelashah1 has joined #openstack-meeting-alt21:24
shamailkencjohnston or I will abandon them by the end of the week... Please let us know via email if you think that action is incorrect.21:24
*** jhfeng has left #openstack-meeting-alt21:24
shamail(in case people who want to raise objection aren't here today)21:24
*** vishwanathj has quit IRC21:24
kencjohnstonok, yeah you can assign that action to me shamail21:25
shamailI think tracker and rolling upgrades both would benefit from additional reviews at this point.21:25
*** jmckind has joined #openstack-meeting-alt21:25
*** vgridnev has joined #openstack-meeting-alt21:25
*** fredyx101 has joined #openstack-meeting-alt21:25
shamailRolling upgrades needs to be +2'd so that we can continue moving forward21:25
kencjohnstonis rockyg our only hope?21:25
shamail#actionitem kencjohnston will abandon changes that have -1 workflow by the end of the week (please email if you object)21:25
shamail#action kencjohnston will abandon changes that have -1 workflow by the end of the week (please email if you objec)21:26
rockygI'll review it....;-)21:26
shamailnot sure where I got the item from :P21:26
shamailkencjohnston, I can +2 it as well but I was hoping other team members would +1 it21:26
kencjohnstonactionitem = corporate speak21:26
kencjohnstonaction = ninja speak21:26
shamailThis goes back to your earlier question... rolling upgrades is at a poin where the usefulness, approach, etc should be reviewed21:26
shamailso the more eyes the better.21:26
kencjohnstonshamail agreed21:26
*** fredyx10 has quit IRC21:27
nateziemannI personally think rolling upgrades should a topic at the ops summit, so we can gather more reviews/input21:27
sgordondumb question21:27
*** neelashah has joined #openstack-meeting-alt21:27
shamail#action Please review https://review.openstack.org/#/c/255633/ and add your feedback on usefulness, approach, additional gaps, etc.21:27
sgordonwhy do people not like items being -1 workflow?21:27
shamailsgordon, do you mean why we don't leave them in that state or why were they -1'd to begin with?21:28
*** jmckind_ has quit IRC21:28
*** kebray has quit IRC21:28
sgordonwell i have an item that is -1 workflow, i set it as that because it is - as that flag states21:28
sgordonWork In Progress21:28
shamailAh, got it.21:28
sgordonthe point of it is to be able to upload the WIP to gerrit without risk that it gets merged ahead of time21:29
*** neelashah1 has quit IRC21:29
sgordonotherwise you are back to sharing WIP via etherpad etc21:29
kencjohnstongot it sgordon - I will refrain from abandoning it21:29
shamailI thought that one was -1 because it had been replaced either through inclusion in another user story or as a new submission that was accepted21:29
shamailgood point sgordon21:29
kencjohnstonI had used -1 workflow on the other commit in question because I felt like it was in error. Perhaps a misuse of the -1 workflow.21:30
sgordonno21:30
shamailYou were using -1 workflow the proper way21:30
sgordonif it's superseded then you use abandon21:30
sgordonwhich is different :)21:30
rockygnateziemann, ++ on a session on rolling upgrades at the ops summit...21:30
shamailsgordon, exactly.. but we had people not doing that so we started using -1 to identify those items so the cores could abandon them in the future21:30
shamailYour method is the right method21:30
shamailWe will stop abusing -1 workflow :)21:30
shamailand use it properly21:30
shamailPlease feel free to add -1 on the 253228 again, we won't abandon it.21:31
*** vilobhmm11 has quit IRC21:31
shamailThe other one (268207) does need to be abandoned (not necessarily because it has a -1 workflow but because it has superceded)21:31
shamailThanks for bringing it up sgordon21:32
cloudrancheryes. KencJohnson helped me out there21:32
shamailThanks for the clarification on the -1 reason kencjohnston21:32
kencjohnstonshamail np21:32
shamailnateziemann, I think that is a good suggestion.. we can revisit in an upcoming topic on the agenda.21:33
shamailAny other items on this topic before we move on?21:33
shamail#topic Austin Talk Proposals21:33
*** openstack changes topic to "Austin Talk Proposals (Meeting topic: product working group)"21:33
nateziemannit appears, at least in my company getting strong operations participation is easier at events then day-to-day.21:33
shamail#link https://etherpad.openstack.org/p/austin_summit_product_wg21:33
shamailWe started brainstorming on sessions that could be proposed by product working group members at the upcoming summit21:34
shamailThe etherpad contains all of the ideas so far...21:34
shamailItem #1 is more of a FYI21:34
shamailsince it is being submitted by the OpenStack UX team21:34
shamailWho submitted items 2,3, and 4?21:35
shamail(in the etherpad)21:35
rockygnateziemann, ++  It's easier to schedule one-offs for ops folks then insert stuff into their firefighting/interrupt-driven daily work mode21:35
shamailOkay, I guess the people might not be here...21:35
kencjohnstonI'm feeling like an idiot, what is BOF?21:36
kencjohnstonBOF21:36
shamailBirds of a Feather21:36
nateziemanntweet tweet21:36
hughhalfBirds of Feather21:36
shamailIt is a session that is meant to bring together people of similar interests21:36
kencjohnstonahh, gotcha21:36
shamailto discuss topics (not a presentation, but more brainstormy)21:36
* hughhalf nods21:36
shamailnot a working session either though21:36
MeganR@kencjohnston: thank you for asking21:36
hughhalfYeah guess it tends to be more informal as shamail points out21:37
*** jprovazn has quit IRC21:37
rockygwe might consider a talk on rolling upgrades if we get the info we need to move forward on that...21:37
shamailIt basically is meant to be a spark... and if it takes, then usually a working session is the next step21:37
*** fnaval_ has joined #openstack-meeting-alt21:37
shamailTrue rockyg21:37
kencjohnstonSo are we brainstorming ideas for Product WG related sessions at the broader summit?21:38
shamailthat could be a part of "user story update"21:38
kencjohnstonOr ideas for our PWG meetings?21:38
shamailkencjohnston, yes for the broader summit21:38
*** tonytan4ever has joined #openstack-meeting-alt21:38
shamailthese would be talks that we would propose for various tracks21:38
kencjohnstongot it, ok21:38
shamailThe agenda for our own meeting is not related to this...21:38
*** fnaval has quit IRC21:39
shamailDo the topics make sense?21:39
shamailIf so, any volunteers to write the abstract and act as a lead for building the team/content?21:39
kencjohnstonThey do, just typing aload, I'd like a discussion around the real or perceived complexity problem for people investigating OpenStack.21:39
shamailI have added the roadmap session as item #521:39
shamailkencjohnston, can you expand on that? Is this about believing its "hard" without even trying it or the other way around (it's harder than it looks)21:40
MarkBakerkencjohnston, +1 on complexity problem - happy to help draft21:40
kencjohnstonshamail I added some notes in the etherpad, but that potential users often shy away for a variety of reasons that aren't software/feature focused21:41
shamailkencjohnston, can you add yourself as the lead for item #6?21:41
rockyg++  It's harder than most realize.  Especially devs, since they usually use devstack21:41
kencjohnstonlike - I have to hire a team of openstack developers. I don't udnerstand the projects or governance.21:41
shamailMarkBaker also volunteered to help!  It looks like 50%+ of your team is already established now.  :-)21:41
kencjohnstonI have to have a 24 hour ops team.21:41
kencjohnstonperfect : thanks MarkBaker21:41
shamailthanks kencjohnston, that makes complete sense.21:41
rockygI'll help...21:41
shamailgood topic21:42
shamailAny takes for items #2, 3, or 4?21:42
shamailtakers*21:42
shamailIf not, i'll send out an email on the mailing list to see if we can identify who added them....21:42
nateziemannit would be good to have a success story, and talk about navigating the complexity.  vs just discussing the 10 ways Openstack is indeed complex.21:43
rockygI think we can get Carol's help/lead on the state of...21:43
kencjohnstonnateziemann agreed, I have some ideas there :)21:43
rockygMaybe I can help on endusers?21:43
shamail#action shamail will send an email to mailing list to identify sponsors for Austin talk proposals.21:43
MarkBakershamail, I am +1 on topic 4, let me know when you find out who proposed it21:43
shamailMarkBaker, will do21:44
*** Heidi_ has quit IRC21:44
shamailgreat suggestion rockyg, especially since she started the dialog with Doug.21:44
shamailOn a related note, I will be sending an email to ask for volunteers again for the roadmap sub-team21:45
nateziemannI'm definitely +1 on helping more substantially w/ the roadmap session this go aroudn.21:45
shamailWe will probably have to do a lot of work around March. :)21:45
shamailThanks nateziemann21:45
shamailAre we done with this topic?21:45
thingeeOnce we had a roadmap, it would be great to start creating specs for projects, or cross-project specs to start getting attention on PTLs21:45
shamailAgreed thingee, this is something we need to discuss at our upcoming mid-cycle21:46
thingeeand start talking amongst the product working group to know who can provide resources21:46
shamailthe "roadmap" as it stands today is only a read-out of the plans from the various project teams21:46
nateziemannI'd like to see the most developed user stories get some airtime in the roadmap for "N" this time.21:46
shamailit doesn't include information on our user stories themselves21:46
thingeeok, well anything *we* want to drive from user survey should be  on the roadmap, no?21:46
*** lisaclark has quit IRC21:47
shamailthingee: +121:47
shamailHopefully we can make the roadmap a read-out + some future topics of interest21:47
thingeesome of that stuff projects aren't going to be aware of which goes back to http://specs.openstack.org/openstack/openstack-user-stories/workflow/workflow.html21:47
shamail#link http://specs.openstack.org/openstack/openstack-user-stories/workflow/workflow.html21:47
* thingee has an item for open discussion relating21:47
rockygYeah.  Rolling upgrades hopefully will make the roadmap21:48
shamailThat's great... thingee, please share details about the open discussion once its scheduled.  I'm certain some of us would love to participate21:48
*** kebray has joined #openstack-meeting-alt21:49
thingeeI meant I have an item for open discussion in this meeting21:49
*** rellerreller has quit IRC21:49
shamailAh, gotcha21:49
shamaillet's get there then! :)21:49
shamail#topic Ops Summit Topic Proposals from PWG21:49
*** openstack changes topic to "Ops Summit Topic Proposals from PWG (Meeting topic: product working group)"21:49
*** shayneburgess has joined #openstack-meeting-alt21:49
shamail#link https://etherpad.openstack.org/p/MAN-ops-meetup21:49
*** weshay has quit IRC21:49
shamailI put this item on the agenda in case we want to add potential topics to the upcoming ops-summit21:50
thingeeok so the workflow document talks about cross-project spec liaisons, but that team doesn't exist yet. If you have been part of the cross-project meetings, you would know that group is being defined21:50
shamailI know Carol has already submitted some topics21:50
thingeehttp://docs.openstack.org/project-team-guide/cross-project.html21:50
*** shashank_hegde has joined #openstack-meeting-alt21:50
*** jtomasek has quit IRC21:50
kencjohnstonOn the MAN-ops-meetup, I added an item for OSIC Bug Collection, working with Tom Fifeld to get that officially on the agenda.21:51
shamailPlease add items that you think might be beneficial (e.g. rolling upgrades, etc.) we can revisit next week...21:51
shamailawesome kencjohnston21:51
thingeeso this project team guide doc defines the liaisons role. These are people once signed up, should be people the product working group works with for various projects21:51
shamailI'm moving on to opens for now, this topic was more to start the brainstorming21:51
shamail#topic Opens21:51
thingeein cross-project related specs21:51
*** openstack changes topic to "Opens (Meeting topic: product working group)"21:51
thingeeoh whoops21:52
thingeeanyways there ya go21:52
shamailthingee, that makes sense21:52
shamailThe product WG itself has CPLs assigned to various projects too21:52
shamailSo it will most likely be the CPL from the Product WG working with the CPL from the project21:52
shamailWhile the user story owners are working with all the various CPLs from the Product WG21:52
shamailThis lets us build a scalable model to discuss/implement user stories21:53
kencjohnstonshamail I would still want the CPL from the PWG to be sitting with the project team in regular meetings21:53
thingeeyes, but these people are technical in their specific project. You'll need them to make sense of whether something fits with their project based on user survey and to work with there team on putting something in our roadmap on their prioritiy list21:53
kencjohnstonnot just interfacing one to one with a project CPL21:53
*** vgridnev has quit IRC21:53
shamailI did see the email about cross-project spec liasons, do you have a link handy to your message Mike?   I'd like to include it in the meeting minutes21:53
thingeeThe point is, I want to avoid the product working group working with PTLs if they don't want to be part of this effort.21:53
thingeeor anyone for that matter21:53
thingeehttp://docs.openstack.org/project-team-guide/cross-project.html21:54
kencjohnstonthingee can you talk a bit more about that "want to avoid PWG working with PTLs"21:54
nateziemannkind of difficult to drive broad cross project user stories without the support of the PTLs at some level...21:54
hughhalfhttp://lists.openstack.org/pipermail/openstack-dev/2016-January/084136.html for thingee's message to the ML21:54
thingeekencjohnston: sure, so if a ptl doesn't have time to work on this effort, they're not the best person to reach out to21:54
sgordoni think i understand the intent21:55
sgordonwhich is to funnel everyone through one place21:55
kencjohnstonthingee agreed, so that is a concern about PTL bandwidth21:55
kencjohnstonwhich I get21:55
sgordonversus distracting the PTLs21:55
thingeebecause I think every working group is saying "oh we'll go to the ptl for this"21:55
sgordonwho are already slammed21:55
kencjohnstonsgordon thingee understood and agreed21:55
thingeekencjohnston: yes and also not every ptl is up=to-date on cross-project initiatives. Which some of user stories touch on21:55
*** irenab has joined #openstack-meeting-alt21:55
shamailthingee, makes sense... We weren't planning on working exclusively with PTLs in the first place.. The goal of our CPLs was to be able to bring up items at the project meetings and get a volunteer identified from the project team to work with us21:55
kencjohnstonour intent was to have CPLs who participate in each individual team, not interface directly with the PTL specifically.21:55
thingeeso with history of ptls being unreliable here, I'd like to have a designated group for this. It defaults to PTLs but they can delegate to another group21:56
thingeethe cross project spec liaisons will be setup here eventually https://wiki.openstack.org/wiki/CrossProjectLiaisons21:56
shamailin this new scenario of cross-project specs, we would be working with xproj liaison to make our case to the project teanm21:56
kencjohnstonthingee - I see, so instead of saying we are working with the Nova team and the Nova PTL is our point person, we should say I'm workign with teh Nova team and the Nova CPL is my point person. Correct?21:56
shamail#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/084136.html21:57
thingeekencjohnston: sure, but you need to hold someone accountable to doing something in the group21:57
thingeesaying you're going to talk to a group of people has no one accountable for what you asked21:57
shamailOur user story team would work with our CPL to Nova, who would then work with the cross-project liaison for Nova in this new workflow.  Does that sound right?21:58
kencjohnstonhmm thingee I think my mindset wasn't that we just ask for things and then they get assigned and happen.21:58
thingeeso product working group liaisons and the CPL interaction can be seen here21:58
shamailThe product WG CPL and cross-project liaison would both be attending the nova meetings but one will be the technical point of contact while the other can provide context on the story21:58
* shamail looks at watch, 1 minute left21:59
thingeeshamail: yes21:59
kencjohnstonWe're almost out of time but I think it would be helpful to use real world examples instead of speaking in generalities of what cross projects might occur in the future.21:59
shamailthingee, I will make this an agenda item for next week.  Will you be able to attend?21:59
kencjohnstonI can take the action to take a stab at summarizing and sending around to the list?21:59
shamailthat would be good too kencjohnston21:59
kencjohnstonAnd then thingee you can provide feedback if I got it right?22:00
thingeeshamail: unfortuantely no22:00
shamailML discussion followed with an agenda item on the weekly meeting22:00
kencjohnstonor aligned with your thought process22:00
shamailthingee, which Monday would be good for follow-up?22:00
thingeekencjohnston: take a look at http://specs.openstack.org/openstack/openstack-user-stories/workflow/workflow.html22:00
*** mhickey has quit IRC22:00
thingeeit pretty much lays it out already22:00
shamail#action kencjohnston to summarize discussion on cross project liaisons and product WG22:00
shamail#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Mon Jan 18 22:00:57 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-01-18-21.00.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-01-18-21.00.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-01-18-21.00.log.html22:01
*** cloudrancher has quit IRC22:01
*** MeganR has quit IRC22:01
shamailthingee, I'll follow up with you on email to decide when we can add this on the agenda (based on your availability)22:01
*** nateziemann has quit IRC22:01
shamailThanks everyone!22:01
thingeeshamail: just feb 1 is good22:02
hughhalf:)22:02
shamailkencjohnston: you got quite a bit of action items this week.. please let me know if you want me to help with any. :)22:02
shamailthanks thingee, i'll add it for that week22:02
*** bknudson_ has quit IRC22:02
thingeeshamail: just can't do next week22:02
*** kzaitsev1mb has joined #openstack-meeting-alt22:02
shamailBye all.22:02
*** kzaitsev_mb has quit IRC22:02
kencjohnstonbye shamail22:03
kencjohnstonthanks22:03
*** diazjf has quit IRC22:03
*** weshay has joined #openstack-meeting-alt22:03
*** lisaclark has joined #openstack-meeting-alt22:03
*** mhickey has joined #openstack-meeting-alt22:04
*** kebray has quit IRC22:05
*** lisaclark has quit IRC22:16
*** tpsilva has quit IRC22:16
*** dims has joined #openstack-meeting-alt22:17
*** narengan has quit IRC22:17
*** dims_ has quit IRC22:18
*** narengan has joined #openstack-meeting-alt22:18
*** julim has quit IRC22:19
*** IlyaG has joined #openstack-meeting-alt22:21
*** IlyaG has quit IRC22:22
*** kencjohnston has quit IRC22:30
*** fredyx101 has quit IRC22:31
*** jmckind has quit IRC22:33
*** narengan12 has joined #openstack-meeting-alt22:34
*** fzdarsky has quit IRC22:36
*** pvaneck has quit IRC22:36
*** narengan has quit IRC22:37
*** spzala has quit IRC22:40
*** dizquierdo has joined #openstack-meeting-alt22:40
*** spzala has joined #openstack-meeting-alt22:40
*** ihrachysh has quit IRC22:42
*** balajiiyer has quit IRC22:44
*** dims has quit IRC22:44
*** dslevin has quit IRC22:45
*** spzala has quit IRC22:45
*** eliqiao has quit IRC22:46
*** hichihara has quit IRC22:47
*** dims has joined #openstack-meeting-alt22:47
*** eliqiao has joined #openstack-meeting-alt22:48
*** achanda has joined #openstack-meeting-alt22:48
*** sgotliv has quit IRC22:49
*** achanda has quit IRC22:50
*** weshay has quit IRC22:50
*** narengan12 has quit IRC22:51
*** achanda has joined #openstack-meeting-alt22:52
*** mhickey has quit IRC22:53
*** irenab has quit IRC22:54
*** amitgandhinz has quit IRC22:56
*** tonytan4ever has quit IRC22:56
*** greg_a has quit IRC22:59
*** gomarivera has quit IRC22:59
*** zotoff has joined #openstack-meeting-alt23:03
*** bknudson has joined #openstack-meeting-alt23:05
*** dims has quit IRC23:05
*** amotoki has quit IRC23:06
*** edtubill has quit IRC23:06
*** dims has joined #openstack-meeting-alt23:07
*** jjmb has joined #openstack-meeting-alt23:10
*** IlyaG has joined #openstack-meeting-alt23:11
*** jjmb1 has quit IRC23:12
*** baoli has joined #openstack-meeting-alt23:12
*** achanda has quit IRC23:14
*** jecarey has quit IRC23:15
*** sigmavirus24 is now known as sigmavirus24_awa23:15
*** lisaclark has joined #openstack-meeting-alt23:17
*** baoli has quit IRC23:17
*** mixos has quit IRC23:18
*** hyamauchi has quit IRC23:22
*** zotoff has joined #openstack-meeting-alt23:23
*** achanda has joined #openstack-meeting-alt23:23
*** banix has quit IRC23:24
*** diazjf has joined #openstack-meeting-alt23:26
*** lisaclark has quit IRC23:28
*** ninag has quit IRC23:30
*** dimtruck is now known as zz_dimtruck23:30
*** ativelkov has quit IRC23:31
*** dteselkin has quit IRC23:32
*** IgorYozhikov has quit IRC23:32
*** rakhmerov has quit IRC23:32
*** katyafervent has quit IRC23:33
*** salv-orlando has joined #openstack-meeting-alt23:33
*** jecarey has joined #openstack-meeting-alt23:33
*** hyamauchi has joined #openstack-meeting-alt23:33
*** dizquierdo has quit IRC23:35
*** ativelkov has joined #openstack-meeting-alt23:35
*** dims has quit IRC23:35
*** IgorYozhikov has joined #openstack-meeting-alt23:36
*** rakhmerov has joined #openstack-meeting-alt23:37
*** hyamauchi has quit IRC23:37
*** jecarey has quit IRC23:37
*** katyafervent has joined #openstack-meeting-alt23:37
*** davidlenwell has quit IRC23:38
*** dteselkin has joined #openstack-meeting-alt23:38
*** dims has joined #openstack-meeting-alt23:39
*** dslev has quit IRC23:40
*** spzala has joined #openstack-meeting-alt23:41
*** IlyaG has quit IRC23:42
*** kei_yama has joined #openstack-meeting-alt23:42
*** eliqiao_ has joined #openstack-meeting-alt23:45
*** outofmemory is now known as reedip23:46
*** spzala has quit IRC23:46
*** rockyg has left #openstack-meeting-alt23:47
*** eliqiao has quit IRC23:49
*** amotoki has joined #openstack-meeting-alt23:50
*** yasui has joined #openstack-meeting-alt23:50
*** achanda has quit IRC23:50
*** spotz is now known as spotz_zzz23:53
*** davidlenwell has joined #openstack-meeting-alt23:58
*** kei_yama has quit IRC23:59
*** dslevin has joined #openstack-meeting-alt23:59

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