Monday, 2016-01-11

*** baoli has quit IRC00:00
*** dgonzalez has joined #openstack-meeting-alt00:01
*** agireud has quit IRC00:02
*** kencjohnston has quit IRC00:04
*** agireud has joined #openstack-meeting-alt00:04
*** agireud has quit IRC00:12
*** jet-rongl has joined #openstack-meeting-alt00:14
*** dgonzalez has quit IRC00:16
*** dgonzalez has joined #openstack-meeting-alt00:17
*** cknight has quit IRC00:17
*** dgonzalez has quit IRC00:17
*** dgonzalez has joined #openstack-meeting-alt00:18
*** dgonzalez has quit IRC00:20
*** bana_k has joined #openstack-meeting-alt00:21
*** dgonzalez has joined #openstack-meeting-alt00:23
*** mattoliverau has quit IRC00:24
*** dgonzalez has quit IRC00:29
*** dgonzalez has joined #openstack-meeting-alt00:29
*** dgonzalez has quit IRC00:30
*** dgonzalez has joined #openstack-meeting-alt00:30
*** dgonzalez has quit IRC00:31
*** dgonzalez has joined #openstack-meeting-alt00:32
*** dgonzalez has quit IRC00:32
*** dgonzalez has joined #openstack-meeting-alt00:33
*** dgonzalez has quit IRC00:34
*** dgonzalez has joined #openstack-meeting-alt00:34
*** dgonzalez has quit IRC00:35
*** dgonzalez has joined #openstack-meeting-alt00:37
*** zhhuabj has joined #openstack-meeting-alt00:41
*** bana_k has quit IRC00:42
*** vahidh has joined #openstack-meeting-alt00:44
*** Sukhdev has joined #openstack-meeting-alt00:45
*** fredyx10 has joined #openstack-meeting-alt00:45
*** Sukhdev has quit IRC00:46
*** zhangjn has joined #openstack-meeting-alt00:47
*** greg_a has joined #openstack-meeting-alt00:48
*** zhangjn_ has joined #openstack-meeting-alt00:53
*** mixos has joined #openstack-meeting-alt00:53
*** zhangjn has quit IRC00:53
*** hoangcx has joined #openstack-meeting-alt00:53
*** cknight has joined #openstack-meeting-alt00:54
*** houming has joined #openstack-meeting-alt01:00
*** dims has quit IRC01:03
*** spzala has joined #openstack-meeting-alt01:04
*** spzala has quit IRC01:04
*** mattoliverau has joined #openstack-meeting-alt01:06
*** agireud has joined #openstack-meeting-alt01:10
*** jjmb has joined #openstack-meeting-alt01:11
*** matt6434 has joined #openstack-meeting-alt01:13
*** mixos has quit IRC01:13
*** markvoelker has joined #openstack-meeting-alt01:14
*** mixos has joined #openstack-meeting-alt01:15
*** hoangcx has quit IRC01:15
*** hoangcx has joined #openstack-meeting-alt01:16
*** banix has quit IRC01:18
*** markvoelker has quit IRC01:19
*** mattoliverau has quit IRC01:19
*** matt6434 is now known as mattoliverau01:19
*** kebray has quit IRC01:26
*** kebray has joined #openstack-meeting-alt01:26
*** hoangcx has quit IRC01:27
*** agireud has quit IRC01:28
*** hoangcx has joined #openstack-meeting-alt01:29
*** kebray has quit IRC01:29
*** agireud has joined #openstack-meeting-alt01:31
*** yonglihe has joined #openstack-meeting-alt01:34
*** dims has joined #openstack-meeting-alt01:37
*** zhhuabj_ has joined #openstack-meeting-alt01:38
*** mixos has quit IRC01:39
*** zhhuabj has quit IRC01:41
*** zhhuabj has joined #openstack-meeting-alt01:49
*** zhhuabj_ has quit IRC01:50
*** bana_k has joined #openstack-meeting-alt01:50
*** cknight has quit IRC01:52
*** greg_a has quit IRC01:55
*** julim has quit IRC01:56
*** mixos has joined #openstack-meeting-alt01:57
*** zhangjn_ has quit IRC02:03
*** agireud has quit IRC02:05
*** dims has quit IRC02:07
*** agireud has joined #openstack-meeting-alt02:08
*** zhurong has joined #openstack-meeting-alt02:08
*** zhurong has quit IRC02:19
*** zhurong has joined #openstack-meeting-alt02:19
*** bana_k has quit IRC02:20
*** houming has quit IRC02:21
*** Sukhdev has joined #openstack-meeting-alt02:21
*** houming has joined #openstack-meeting-alt02:21
*** hoangcx has quit IRC02:25
*** armax has joined #openstack-meeting-alt02:32
*** hoangcx has joined #openstack-meeting-alt02:36
*** weshay has quit IRC02:36
*** adrian_otto has joined #openstack-meeting-alt02:36
*** hoangcx has quit IRC02:37
*** hoangcx has joined #openstack-meeting-alt02:37
*** hoangcx has quit IRC02:38
*** agireud has quit IRC02:38
*** hoangcx has joined #openstack-meeting-alt02:40
*** agireud has joined #openstack-meeting-alt02:40
*** hoangcx_ has joined #openstack-meeting-alt02:42
*** zhangjn has joined #openstack-meeting-alt02:43
*** hoangcx has quit IRC02:44
*** zhangjn has quit IRC02:45
*** zz_dimtruck is now known as dimtruck02:47
*** zhhuabj_ has joined #openstack-meeting-alt02:47
*** fredyx10 has quit IRC02:49
*** sdake has joined #openstack-meeting-alt02:51
*** zhhuabj has quit IRC02:52
*** salv-orlando has quit IRC02:52
*** salv-orlando has joined #openstack-meeting-alt02:53
*** markvoelker has joined #openstack-meeting-alt02:53
*** zhhuabj_ has quit IRC02:55
*** zhangjn has joined #openstack-meeting-alt02:56
*** dimtruck is now known as zz_dimtruck02:57
*** zhangjn has quit IRC03:01
*** zz_dimtruck is now known as dimtruck03:02
*** zhangjn has joined #openstack-meeting-alt03:03
*** zhangjn has quit IRC03:04
*** zhangjn has joined #openstack-meeting-alt03:08
*** agireud has quit IRC03:10
*** kencjohnston has joined #openstack-meeting-alt03:11
*** zhangjn has quit IRC03:12
*** agireud has joined #openstack-meeting-alt03:13
*** kebray has joined #openstack-meeting-alt03:14
*** dimtruck is now known as zz_dimtruck03:15
*** zhangjn has joined #openstack-meeting-alt03:17
*** kencjohnston has quit IRC03:27
*** zz_dimtruck is now known as dimtruck03:38
*** sgotliv_ has joined #openstack-meeting-alt03:41
*** zhangjn has quit IRC03:42
*** sgotliv has quit IRC03:43
*** vilobhmm111 has joined #openstack-meeting-alt03:52
*** vilobhmm11 has quit IRC03:55
*** hoangcx_ is now known as hoangcx03:56
*** salv-orl_ has joined #openstack-meeting-alt04:09
*** salv-orlando has quit IRC04:11
*** shwetaap has joined #openstack-meeting-alt04:19
*** vilobhmm111 has quit IRC04:26
*** agireud has quit IRC04:26
*** jjmb1 has joined #openstack-meeting-alt04:26
*** agireud has joined #openstack-meeting-alt04:28
*** jjmb has quit IRC04:30
*** bana_k has joined #openstack-meeting-alt04:31
*** davidlenwell_ is now known as davidlenwell04:35
*** agireud has quit IRC04:39
*** agireud has joined #openstack-meeting-alt04:41
*** coolsvap|away is now known as coolsvap04:41
*** agireud has quit IRC04:48
*** agireud has joined #openstack-meeting-alt04:52
*** armax has quit IRC04:58
*** dimtruck is now known as zz_dimtruck04:58
*** shwetaap has quit IRC04:59
*** agireud has quit IRC04:59
*** david-lyle has quit IRC05:00
*** david-lyle has joined #openstack-meeting-alt05:00
*** agireud has joined #openstack-meeting-alt05:02
*** mixos has quit IRC05:02
*** yamamoto has joined #openstack-meeting-alt05:04
*** yamamoto has quit IRC05:04
*** yamamoto has joined #openstack-meeting-alt05:05
*** yamamoto has quit IRC05:05
*** agireud has quit IRC05:06
*** agireud has joined #openstack-meeting-alt05:09
*** Poornima has joined #openstack-meeting-alt05:09
*** adrian_otto has quit IRC05:11
*** adrian_otto has joined #openstack-meeting-alt05:11
*** zz_dimtruck is now known as dimtruck05:13
*** vishwanathj has joined #openstack-meeting-alt05:13
*** adrian_otto has quit IRC05:16
*** adrian_otto has joined #openstack-meeting-alt05:18
*** yamamoto has joined #openstack-meeting-alt05:18
*** yamamoto has quit IRC05:22
*** yamamoto has joined #openstack-meeting-alt05:22
*** yamamoto has quit IRC05:25
*** zhangjn has joined #openstack-meeting-alt05:28
*** vilobhmm11 has joined #openstack-meeting-alt05:29
*** gcb_ has joined #openstack-meeting-alt05:41
*** gcb has joined #openstack-meeting-alt05:45
*** gcb_ has quit IRC05:50
*** SridharG has joined #openstack-meeting-alt05:53
*** _nadya_ has joined #openstack-meeting-alt05:55
*** dave-mccowan has joined #openstack-meeting-alt06:02
*** dave-mcc_ has joined #openstack-meeting-alt06:03
*** dave-mccowan has quit IRC06:06
*** adrian_otto has quit IRC06:15
*** baoli_ has quit IRC06:15
*** _nadya_ has quit IRC06:15
*** dimtruck is now known as zz_dimtruck06:18
*** cnlucius has quit IRC06:19
*** dave-mcc_ has quit IRC06:21
*** yamamoto has joined #openstack-meeting-alt06:22
*** nkrinner has joined #openstack-meeting-alt06:23
*** zhurong_ has joined #openstack-meeting-alt06:27
*** zhurong has quit IRC06:29
*** salv-orl_ has quit IRC06:31
*** salv-orlando has joined #openstack-meeting-alt06:31
*** zhangjn has quit IRC06:36
*** SridharG has quit IRC06:37
*** SridharG has joined #openstack-meeting-alt06:38
*** zhangjn has joined #openstack-meeting-alt06:41
*** _nadya_ has joined #openstack-meeting-alt06:46
*** _nadya_ has quit IRC06:49
*** yamahata has quit IRC07:05
*** scheuran has joined #openstack-meeting-alt07:07
*** jtomasek_ has joined #openstack-meeting-alt07:10
*** jtomasek_ is now known as jtomasek07:11
*** gcb has quit IRC07:12
*** irenab has joined #openstack-meeting-alt07:15
*** zhurong_ has quit IRC07:20
*** zhurong has joined #openstack-meeting-alt07:21
*** markvoelker has quit IRC07:22
*** vilobhmm11 has quit IRC07:24
*** paul-carlton2 has joined #openstack-meeting-alt07:31
*** zhhuabj has joined #openstack-meeting-alt07:33
*** sgotliv_ has quit IRC07:36
*** yamamoto has quit IRC07:37
*** zhhuabj has quit IRC07:39
*** safchain has joined #openstack-meeting-alt07:39
*** sylwesterB has joined #openstack-meeting-alt07:40
*** sylwesterB has quit IRC07:41
*** sylwesterB has joined #openstack-meeting-alt07:41
*** vahidh has quit IRC07:41
*** regebro has joined #openstack-meeting-alt07:45
*** zhhuabj has joined #openstack-meeting-alt07:51
*** edwardb has joined #openstack-meeting-alt07:52
*** j___ has joined #openstack-meeting-alt08:00
*** jprovazn has joined #openstack-meeting-alt08:01
*** belmoreira has joined #openstack-meeting-alt08:05
*** edwardb has quit IRC08:06
*** ihrachys has joined #openstack-meeting-alt08:08
*** Sukhdev has quit IRC08:08
*** katyafervent is now known as katyafervent_awa08:13
*** katyafervent_awa is now known as katyafervent08:14
*** fzdarsky has joined #openstack-meeting-alt08:18
*** zhurong has quit IRC08:23
*** matrohon has joined #openstack-meeting-alt08:26
*** boris-42 has joined #openstack-meeting-alt08:28
*** zeih has joined #openstack-meeting-alt08:32
*** kebray has quit IRC08:32
*** yamamoto has joined #openstack-meeting-alt08:37
*** bauwser is now known as bauzas08:44
*** yamamoto has quit IRC08:44
*** bana_k has quit IRC08:44
*** salv-orlando has quit IRC08:44
*** salv-orlando has joined #openstack-meeting-alt08:45
*** apetrich_ has quit IRC08:49
*** FallenPegasus has joined #openstack-meeting-alt08:49
*** FallenPegasus has quit IRC08:49
*** apetrich has joined #openstack-meeting-alt08:50
*** thomnico has joined #openstack-meeting-alt08:51
*** macsz has joined #openstack-meeting-alt08:51
*** markvoelker has joined #openstack-meeting-alt08:54
*** vgridnev has joined #openstack-meeting-alt08:55
*** markvoelker has quit IRC08:59
*** _nadya_ has joined #openstack-meeting-alt09:00
*** zhangjn has quit IRC09:03
*** derekh has joined #openstack-meeting-alt09:03
*** paul-carlton2 has quit IRC09:05
*** e0ne has joined #openstack-meeting-alt09:05
*** dizquierdo has joined #openstack-meeting-alt09:06
*** vahidh has joined #openstack-meeting-alt09:07
*** zhangjn has joined #openstack-meeting-alt09:09
*** numans has joined #openstack-meeting-alt09:09
*** rvyalov_ has joined #openstack-meeting-alt09:09
*** zhhuabj has quit IRC09:10
*** vahidh has quit IRC09:12
*** zhhuabj has joined #openstack-meeting-alt09:18
*** pnavarro has joined #openstack-meeting-alt09:22
*** blazej_kw has quit IRC09:23
*** ndipanov has joined #openstack-meeting-alt09:25
*** ndipanov has quit IRC09:26
*** paul-carlton2 has joined #openstack-meeting-alt09:27
*** zhhuabj has quit IRC09:34
*** dizquierdo has quit IRC09:35
*** yamamoto has joined #openstack-meeting-alt09:36
*** yamamoto has quit IRC09:38
*** sgotliv_ has joined #openstack-meeting-alt09:38
*** yamamoto has joined #openstack-meeting-alt09:39
*** zhangjn has quit IRC09:40
*** bana_k has joined #openstack-meeting-alt09:40
*** salv-orlando has quit IRC09:40
*** salv-orlando has joined #openstack-meeting-alt09:41
*** apetrich has quit IRC09:43
*** ndipanov has joined #openstack-meeting-alt09:44
*** bana_k has quit IRC09:47
*** kzaitsev_mb has joined #openstack-meeting-alt09:54
*** zhhuabj has joined #openstack-meeting-alt09:56
*** zhangjn has joined #openstack-meeting-alt09:57
*** sdake has quit IRC09:57
*** yamamoto has quit IRC09:57
*** yamamoto has joined #openstack-meeting-alt09:57
*** zeih has quit IRC09:57
*** DinaBelova has quit IRC10:01
*** DinaBelova has joined #openstack-meeting-alt10:01
*** zeih_ has joined #openstack-meeting-alt10:02
*** SergeyLukjanov has quit IRC10:02
*** SergeyLukjanov2 has joined #openstack-meeting-alt10:02
*** SergeyLukjanov2 is now known as SergeyLukjanov10:02
*** zeih__ has joined #openstack-meeting-alt10:02
*** apetrich has joined #openstack-meeting-alt10:03
*** ozamiatin has quit IRC10:03
*** ganso has joined #openstack-meeting-alt10:06
*** zeih_ has quit IRC10:07
*** yamamoto has quit IRC10:10
*** salv-orl_ has joined #openstack-meeting-alt10:10
*** yamamoto has joined #openstack-meeting-alt10:11
*** salv-orlando has quit IRC10:12
*** zhangjn has quit IRC10:19
*** zhangjn has joined #openstack-meeting-alt10:23
*** zhangjn has quit IRC10:24
*** zhangjn has joined #openstack-meeting-alt10:25
*** mrmartin has joined #openstack-meeting-alt10:43
*** zhangjn has quit IRC10:53
*** markvoelker has joined #openstack-meeting-alt10:55
*** tellesnobrega_af is now known as tellesnobrega10:55
*** hoangcx has quit IRC10:58
*** yamamoto has quit IRC11:00
*** yamamoto has joined #openstack-meeting-alt11:00
*** markvoelker has quit IRC11:00
*** dizquierdo has joined #openstack-meeting-alt11:00
*** zhangjn has joined #openstack-meeting-alt11:02
*** yamamoto has quit IRC11:03
*** mrmartin has quit IRC11:03
*** salv-orl_ has quit IRC11:03
*** yamamoto has joined #openstack-meeting-alt11:03
*** salv-orlando has joined #openstack-meeting-alt11:04
*** sdake has joined #openstack-meeting-alt11:04
*** salv-orlando has quit IRC11:05
*** salv-orlando has joined #openstack-meeting-alt11:05
*** zeih has joined #openstack-meeting-alt11:08
*** ozamiatin has joined #openstack-meeting-alt11:11
*** zeih__ has quit IRC11:12
*** baoli has joined #openstack-meeting-alt11:14
*** coolsvap is now known as coolsvap|away11:17
*** dims_ has joined #openstack-meeting-alt11:18
*** neilus has joined #openstack-meeting-alt11:21
*** yamamoto has quit IRC11:26
*** bana_k has joined #openstack-meeting-alt11:28
*** neilus has quit IRC11:33
*** kzaitsev_mb has quit IRC11:33
*** bana_k has quit IRC11:33
*** Poornima has quit IRC11:34
*** bauzas has quit IRC11:35
*** jaypipes has joined #openstack-meeting-alt11:37
*** neilus has joined #openstack-meeting-alt11:37
*** sputnik13 has joined #openstack-meeting-alt11:40
*** neilus has quit IRC11:41
*** fredyx10 has joined #openstack-meeting-alt11:43
*** fredyx10 has quit IRC11:44
*** fredyx10 has joined #openstack-meeting-alt11:44
*** sdake_ has joined #openstack-meeting-alt11:46
*** sdake has quit IRC11:47
*** fredyx10 has quit IRC11:48
*** sdake_ has quit IRC11:50
*** sdake has joined #openstack-meeting-alt11:51
*** kzaitsev_mb has joined #openstack-meeting-alt11:52
*** sdake has quit IRC11:53
*** markvoelker has joined #openstack-meeting-alt11:56
*** SridharG has quit IRC11:56
*** HeOS has joined #openstack-meeting-alt11:59
*** HeOS_ has quit IRC12:00
*** markvoelker has quit IRC12:00
*** tellesnobrega is now known as tellesnobrega_af12:02
*** zhangjn has quit IRC12:03
*** apetrich has quit IRC12:04
*** zeih has quit IRC12:07
*** zeih has joined #openstack-meeting-alt12:10
*** zeih has quit IRC12:14
*** derekh has quit IRC12:15
*** irenab has quit IRC12:17
*** irenab has joined #openstack-meeting-alt12:19
*** ozamiatin__ has joined #openstack-meeting-alt12:24
*** tellesnobrega_af is now known as tellesnobrega12:25
*** tellesnobrega is now known as tellesnobrega_af12:25
*** derekh has joined #openstack-meeting-alt12:25
*** yamamoto has joined #openstack-meeting-alt12:26
*** HenryG has quit IRC12:27
*** HenryG has joined #openstack-meeting-alt12:27
*** yamamoto has quit IRC12:30
*** tobasco has joined #openstack-meeting-alt12:33
*** zeih has joined #openstack-meeting-alt12:37
*** zeih has quit IRC12:41
*** mrmartin has joined #openstack-meeting-alt12:43
*** pnavarro has quit IRC12:46
*** ozamiatin_ has joined #openstack-meeting-alt12:46
*** ozamiatin__ has quit IRC12:48
*** jjmb1 has quit IRC12:48
*** apetrich has joined #openstack-meeting-alt12:50
*** fredyx10 has joined #openstack-meeting-alt12:51
*** fredyx10 has quit IRC12:51
*** fredyx10 has joined #openstack-meeting-alt12:51
*** fredyx10 has quit IRC12:54
*** salv-orlando has quit IRC12:55
*** sdake has joined #openstack-meeting-alt12:56
*** sputnik13 has quit IRC12:56
*** salv-orlando has joined #openstack-meeting-alt12:56
*** markvoelker has joined #openstack-meeting-alt12:57
*** jdob has joined #openstack-meeting-alt12:57
*** houming has quit IRC13:00
*** markvoelker has quit IRC13:01
*** yamamoto has joined #openstack-meeting-alt13:02
*** zhangjn has joined #openstack-meeting-alt13:05
*** zeih has joined #openstack-meeting-alt13:05
*** sdake_ has joined #openstack-meeting-alt13:05
*** fredyx101 has joined #openstack-meeting-alt13:06
*** sdake has quit IRC13:06
*** jet-rongl has quit IRC13:11
*** salv-orlando has quit IRC13:11
*** salv-orlando has joined #openstack-meeting-alt13:12
*** fredyx101 has quit IRC13:13
*** fredyx10 has joined #openstack-meeting-alt13:14
*** sdake has joined #openstack-meeting-alt13:16
*** sdake_ has quit IRC13:16
*** bana_k has joined #openstack-meeting-alt13:16
*** weshay_xchat has joined #openstack-meeting-alt13:18
*** markvoelker has joined #openstack-meeting-alt13:20
*** bana_k has quit IRC13:21
*** dprince has joined #openstack-meeting-alt13:26
*** obondarev has joined #openstack-meeting-alt13:32
*** bauzas has joined #openstack-meeting-alt13:33
*** fredyx10 has quit IRC13:36
*** fredyx10 has joined #openstack-meeting-alt13:36
*** sdake has quit IRC13:39
*** amrith is now known as _amrith_13:40
*** jecarey has quit IRC13:41
*** yamamoto has quit IRC13:42
*** n0ano has joined #openstack-meeting-alt13:43
*** scheuran has quit IRC13:55
*** cdent has joined #openstack-meeting-alt13:56
*** cbouch has joined #openstack-meeting-alt13:59
n0ano#startmeeting nova-scheduler13:59
openstackMeeting started Mon Jan 11 13:59:53 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
n0anoanyone here to talk about the scheduler14:00
lxslio/14:00
*** bana_k has joined #openstack-meeting-alt14:00
tobascoyes14:00
jaypipesmorning all14:00
carl_baldwino/14:00
lxslistaff meeting...14:02
*** yamamoto has joined #openstack-meeting-alt14:02
n0anolxsli, so, I'm in two meetings right now myself :-)14:02
bauzasheya14:02
bauzas\o14:02
jaypipesn0ano: me too :)14:02
edleafeo/14:02
n0anolooks like we have quorum so let's go14:02
n0ano#topic specs, BPs, patches14:02
*** openstack changes topic to "specs, BPs, patches (Meeting topic: nova-scheduler)"14:02
* bauzas attending his first '16 sched meeting \o/14:03
* johnthetubaguy lurks14:03
n0anothe big one here belongs to you jaypipes , what's happening with your resource providers BP?14:03
jaypipesn0ano: I have split it into resource-classes, resource-providers, generic-resource-pools, and compute-node-inventory blueprints.14:04
jaypipesn0ano: still working on compute-node-allocations blueprint, which is final one in series.14:04
bauzasand some of them are being implemented, right?14:04
jaypipesbauzas: yes, cdent is working on resource-classes (patches pushed already I believe) and we are working on others slowly14:05
*** esker has quit IRC14:05
bauzascoolness14:05
cdentoh, hi, I'm here14:05
jaypipesI apologize for not being able to attend these meetings for a couple months :(14:05
cdentyeah: I pushed some resource-classes stuff14:05
jaypipesand for being so slow on the spec stuff :(14:05
cdentbut have held off on the next step waiting on the specs to progress14:05
bauzasI'd advocate for using the etherpad of doom then :)14:05
*** bana_k has quit IRC14:05
n0anojaypipes, NP, my only concern is we're beyond feature freeze, do we need to get exceptions for these 5 BPs?14:05
bauzasie. https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking14:06
bauzasn0ano: no14:06
bauzasn0ano: no exceptions are possible now14:06
*** _nadya_ has quit IRC14:06
n0anobauzas, then what's the implication for Mitaka?14:07
bauzasn0ano: we can continue to work, but no merges14:07
jaypipesn0ano: need to chat with johnthetubaguy about it. I was under the impression that the resource-providers work was a bit of an exception to the rule.14:07
n0anojaypipes, +114:07
bauzascdent: jaypipes: like I said above, would it be possible to mention all the specs + implems in https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking ?14:08
johnthetubaguyif we get it reviewed, and folks to work on the follow up bits, thats OK I think14:08
* bauzas was pretty dotted-line during the past weeks14:08
jaypipesbauzas: yes. I will do that ASAP.14:08
johnthetubaguyyeah, in that etherpad sounds like a good plan14:09
n0anojohnthetubaguy, do we have a hard cutoff date for getting the BPs approved?14:09
johnthetubaguyit was a few months back14:09
cdent:)14:09
johnthetubaguybut the process is here to help, so if we need exceptions, and everyone wants it, lets do what we can14:10
*** fredyx10 has quit IRC14:10
n0anoso no, we'll just work with asap14:10
bauzashonestly, I'm not that concerned by the Mitaka freeze14:10
johnthetubaguyif it were not a priority item thats blocking os many things, it would be a hard no, but will to see what other folks think for this14:10
n0anoso, if jaypipes  can update the epad with links to all the BPs we'll try and get them reviewed and approved as soon as possible14:11
bauzasie. we should be able to accept specs for Nxxx sooner or later14:11
bauzasand we could just make sure that if we get enough stuff stable, it could be iterated very quickly for landing in N before Summit14:11
bauzaslike we did for ReqSpec14:11
bauzasno precise need for bypassing what was agreed14:12
n0anoI don't think we're bypassing so much as interpreting guidelines :-)14:12
n0anoanyway, let's see if we can get it approved as soon as possible.14:13
*** jmckind has joined #openstack-meeting-alt14:13
n0anoI think that's it for BPs, all others have either been approved or deferred to N, are they any specific patches people want to discuss today?14:14
*** dslev has quit IRC14:14
cdentI pushe a bug fix that needs some review: https://review.openstack.org/#/c/264349/14:14
cdentwas rated as "high"14:14
n0anocdent, excellent, let's all try to review it14:14
*** sriram has joined #openstack-meeting-alt14:15
*** dslevin has quit IRC14:15
carl_baldwinI pushed a backlog spec here at we talked about last week:  https://review.openstack.org/#/c/263898/14:16
bauzascdent: in my pip14:16
bauzaspipe even14:16
n0anocarl_baldwin, cool, you should also update the mitaka topics page at https://etherpad.openstack.org/p/mitaka-nova-midcycle14:17
carl_baldwinn0ano: See L7314:17
johnthetubaguycarl_baldwin: I was talking with armax about making sure we find time for the neutron related things, its on my mental list as well14:18
n0anocarl_baldwin, I'm blnd, I didn't scroll down :-)14:18
carl_baldwinjohnthetubaguy: many thanks14:18
carl_baldwinn0ano: No worries, it is a busy agenda.14:18
n0anokind of seques into the next topic14:19
n0ano#topic mid-cycle meetup14:19
*** openstack changes topic to "mid-cycle meetup (Meeting topic: nova-scheduler)"14:19
n0anogiven that the neutron scheduling is on one day and a general scheduler topic is on day one I think we're covered unless anyone14:20
bauzasI feel so14:20
*** sriram has left #openstack-meeting-alt14:20
n0anoI should note that scheduler testing is a suggested topic but not on a specific day yet, hopefully that won't be forgotten14:20
*** huyang has joined #openstack-meeting-alt14:21
johnthetubaguyshould be good I think14:21
*** thrash|g0ne is now known as thrash14:22
n0anoOK, moving on14:22
n0ano#topic bugs14:22
*** openstack changes topic to "bugs (Meeting topic: nova-scheduler)"14:22
cdentI was looking into working on this: https://bugs.launchpad.net/nova/+bug/143129114:22
openstackLaunchpad bug 1431291 in OpenStack Compute (nova) "Scheduler Failures are no longer logged with enough detail for a site admin to do problem determination" [High,Confirmed] - Assigned to Pranav Salunke (dguitarbite)14:22
*** shwetaap has joined #openstack-meeting-alt14:22
n0anoI note that the current list is still at 38 (37 once we push cdent 's ing)14:22
cdentbut it feels like reality and the bug have gone in different directions since the bug was created14:23
cdentso I was wondering if someone with a bit more experience could make some statement about the current desired functionality (on the bug)?14:23
bauzascdent: I feel it would be worth discussing that at the midcycle14:23
bauzascdent: because it's more a placeholder bug saying "meh, logs suck"14:23
*** zhangjn has quit IRC14:23
cdentYeah, it kinda felt that way.14:23
cdentIs there something more tractable I could/should work on in the meantime?14:24
n0anopersonally I don't have a problem with closing bugs out with `NOTABUG'14:24
bauzascdent: I guess you saw johnthetubaguy's mentions of what has been done in the past with that bug ?14:24
tobascoI have a bug I would like some insight in, I recently marked mine as a duplicate and posted a comment in this one https://bugs.launchpad.net/nova/+bug/1469179 can't really tell if it's the correct room but got directed by johnthetubaguy14:24
openstackLaunchpad bug 1469179 in OpenStack Compute (nova) "instance.root_gb should be 0 for volume-backed instances" [Undecided,In progress] - Assigned to Feodor Tersin (ftersin)14:24
cdentbauzas: yes14:24
bauzasn0ano: agreed, I feel we could close that one by mentioning what has been done already and ask to reopen if something more specific is needed14:25
n0anobauzas, +114:25
johnthetubaguybauzas: +114:25
*** mhickey has joined #openstack-meeting-alt14:25
johnthetubaguyfeels out of date post last release14:25
bauzasokay, I can do that14:25
*** jecarey has joined #openstack-meeting-alt14:25
*** tellesnobrega_af is now known as tellesnobrega14:26
n0anotobasco, johnthetubaguy not seeing where this bug is scheduler related, I don't know if anyone here has any insight on this14:28
*** jmckind has quit IRC14:28
johnthetubaguyah, sorry14:28
*** jecarey has quit IRC14:28
johnthetubaguylooking again14:28
johnthetubaguythis is more resource tracker14:29
*** jecarey has joined #openstack-meeting-alt14:29
bauzasthat's even a driver-specific problem, nope ?14:29
johnthetubaguyI was thinking the resource providers work, so we track shared storage better, would improve things14:29
bauzasbecause the RT is dumpb14:29
*** pnavarro has joined #openstack-meeting-alt14:29
bauzasdumb14:29
n0anojohnthetubaguy, which we are effectively re-writing so maybe this bug might become irrelevant14:29
johnthetubaguyI think this is cinder volumes confusing local storage space14:29
bauzasit only persists what the driver is providing to it14:29
bauzasn0ano: not exactly14:30
n0anobauzas, but sounds like this might be cinder related then14:30
johnthetubaguyso I think most folks doing cinder only would disable the diskfilter and not spot the bug14:30
bauzasn0ano: IIUC, the problem is about what's provided as disk space when you have a volume-backed instance14:30
tobascobauzas: Nova is reading root_gb for cinder volumes so effectively this is the resource tracker which creates the wrong stats14:30
*** dslevin has joined #openstack-meeting-alt14:30
johnthetubaguybut if you are mix and match, it affects you, I guess14:30
*** julim has joined #openstack-meeting-alt14:30
bauzasso, to be clear, possibly something has to be done on the RT classes14:31
tobascoAt the same time this effects the scheduler since the DiskFilter combined with the wrong stats created bad scheduling14:31
bauzasunless I'm wrong, the DiskFilter is not a default filter14:31
tobascoOnly solution so far is to exclude DiskFilter or set the disk_allocation_ratio config value14:31
tobascobauzas: The DiskFilter was introduced as a default in liberty iirc14:32
johnthetubaguybauzas: it got added, I think14:32
johnthetubaguyit might have been dropped since then, lol14:32
n0anotobasco, affects the scheduler but it's still doing the right thing, give it the wrong data it will correctly make the wrong decision14:32
bauzasoh snap, it is indeed14:32
tobascon0ano: yes14:32
bauzasso, yeah, the scheduler only schedules based on what the RT provides14:32
johnthetubaguyso my through was about resource providers14:32
bauzas++14:32
tobascoI just want to shine some more light into this since running a complete Cinder backed Nova today gives quite some headache14:33
johnthetubaguypart of that is deciding the cinder vs local resources14:33
bauzaszactly, we need jaypipes and cdent at wrok14:33
bauzaswork14:33
n0anoshould tobasco maybe have a discussion with some of the cinder people about this?14:33
cdenttotes14:33
johnthetubaguytobasco: you probably should just disable the disk filter if you are doing that mind, or is there something missing?14:33
johnthetubaguynot sure we need cinder folk for this, seems a very Nova issue here14:33
bauzasa possible workaround could be docs14:34
bauzasie. specify that DiskFilter should be disabled if Cinder backed volumes14:34
bauzasas a known limitation14:34
johnthetubaguyif there are no local disks in the BDM, we should ignore the flavor disk_gb in the resource tracker claim, and the scheduler stuff14:34
tobascojohnthetubaguy: In our production environment I have disabled the DiskFilter however this still gives me the wrong stats and should be fixed iirc since it's wrong, or atleast have a look at it.14:34
tobasco*imo14:34
johnthetubaguytobasco: ok, true, its more that it changes the priority14:34
bauzaswell, I guess the resource-providers epic already has lots of attention14:35
tobascoFor example, we run our hypervisors on very low disk and having the wrong statistics on what's actually on local disk is quite scary for people that doesn't know about this.14:35
bauzasI feel it's a real bug14:35
bauzaswith a real problem14:35
bauzasand with a possible solution that could be resource-providers14:36
*** rsyed_away is now known as rsyed14:36
n0anobauzas, yeah but it sounds like this is not really a RT problem, it's being given the wrong data14:36
bauzasn0ano: if so, it's not nova14:36
tobascoI agree with n0ano if only instances processed by the resource tracker and in the database would have root_gb set to 0 the scheduler nor the stats would have any issues14:36
tobascoroot_gb = 0 where Cinder backed Nova instances that would say, as root disk.14:37
n0anotobasco, but who should be setting it to 0, nova or cinder?14:37
*** dane has joined #openstack-meeting-alt14:37
bauzasI remember some conditional in the RT about root_gb, hold on14:37
bauzasmeh, nevermind14:38
tobascon0ano: I saw some comment about the scheduler using the compute api is_volume_backed_instance function to check and set the root_gb to zero, however I assume this is only theoretical and not tested. I can't really be of very much help, I can troubleshoot code however I'm not so familar with the OpenStack concepts and codebase that I yet can help out.14:38
*** numans has quit IRC14:39
tobascoI would be more than happy to help out and discuss this issue with other people further if it's needed, I have seen a lot of people having this issue and including myself so I would like to shine some light and get it resolved, that's all :)14:39
johnthetubaguybauzas: so it might be the spec object population code14:39
johnthetubaguybauzas: https://github.com/openstack/nova/blob/master/nova/scheduler/filters/disk_filter.py#L3614:39
johnthetubaguybut yeah, lets take this into the openstack-nova channel I guess14:40
bauzas+114:40
n0anotobasco, having the scheduler do this check seems wrong, I'd like to see what cinder says about this14:40
n0anojohnthetubaguy, +1 to the nova channel14:40
bauzasyeah, I'd be very against any change in the scheduler codebase14:41
n0anotobasco, tnx for bringing this up but I think you'll get a better answer on #nova14:41
bauzasIMHO, it's a resource issue, not a placement decision issue14:41
johnthetubaguyn0ano: its the spec object population, rather than the scheduler, but yeah, lets talk about that over the other side14:41
tobascoOk, I'm satisfied, johnthetubaguy can you please help me out to get this further either by helping or giving me some hints on how to proceed. I would be glad to help out.14:41
bauzasmoving on ?14:42
johnthetubaguytobasco: yup, sounds like bauzas might be able to help us too ;-)14:42
n0anobauzas, indeed14:42
*** ralonsoh has joined #openstack-meeting-alt14:42
johnthetubaguyaye14:42
n0ano#topic opens14:42
*** openstack changes topic to "opens (Meeting topic: nova-scheduler)"14:42
tobasco+114:42
n0anothat's all from me, anything new?14:42
*** zhangjn has joined #openstack-meeting-alt14:42
cdentI have a bit of a blue sky question: Has anybody done any experimentation with using pandas DataFrames as the scheduler's data structure?14:43
* cdent is looking for prior art14:43
* cdent doesn't have any immediate plans, just playing14:43
n0anocdent, ed leafe looked at using Cassandra but we dropped that work, talk to him might be good14:43
n0anocdent, there wasn't really much interest in changing the back end14:44
johnthetubaguythe selection loop didn't seem that slow, compared to overall time in the scheduler, so I stopped looking at that bit of the scheduler14:44
* cdent nods14:44
*** banix has joined #openstack-meeting-alt14:44
bauzaswhat johnthetubaguy said14:44
bauzaswe want to have a scalable scheduler from zero to beyond infinite14:45
cdentIt's more of an exercise in understanding the conceptual stuff, not really coming up with a new solution14:45
johnthetubaguythere is a fun unit test14:45
bauzascdent: luckily, any out-of-tree implementation can be done14:45
bauzascdent: you just need to implement the interfaces and rock on14:45
* cdent nods14:45
n0anocdent, but expect issues if you want to merge such a thing back in14:46
edleafecdent: the main advantage of the cassandra design was that the scheduler claimed the resournces14:46
* bauzas could joke on numpy dependency tho14:46
edleafecdent: it eliminated the raciness14:46
*** annegentle has joined #openstack-meeting-alt14:46
johnthetubaguycdent: https://github.com/openstack/nova/blob/master/nova/tests/unit/scheduler/test_caching_scheduler.py#L20514:47
*** annegentle has quit IRC14:47
*** xyang1 has joined #openstack-meeting-alt14:47
cdentthanks johnthetubaguy14:47
n0anoanything else?14:48
*** annegentle has joined #openstack-meeting-alt14:48
*** neelashah has joined #openstack-meeting-alt14:49
n0anohearing more crickets14:49
*** fredyx10 has joined #openstack-meeting-alt14:49
*** miqui has joined #openstack-meeting-alt14:49
cdentI think we're done14:49
n0anotnx everyone, we'll talk again next week14:49
n0ano#endmeeting14:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:49
openstackMeeting ended Mon Jan 11 14:49:54 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-01-11-13.59.html14:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-01-11-13.59.txt14:49
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-01-11-13.59.log.html14:50
*** EricGonczer_ has joined #openstack-meeting-alt14:50
*** balajiiyer has joined #openstack-meeting-alt14:51
*** cknight has joined #openstack-meeting-alt14:51
*** jprovazn has quit IRC14:55
*** merooney has joined #openstack-meeting-alt14:56
*** ralonsoh has quit IRC14:57
*** korzen has joined #openstack-meeting-alt14:59
ihrachyso/ to all upgrades folks. we'll wait a minute for others.14:59
*** huyang has left #openstack-meeting-alt15:00
*** cdent has left #openstack-meeting-alt15:00
korzenhi all15:00
*** rossella_s has joined #openstack-meeting-alt15:00
roaethi15:01
ihrachysroaet: hi!15:01
ihrachysok, let's get it rolling15:01
ihrachys#startmeeting neutron_upgrades15:01
openstackMeeting started Mon Jan 11 15:01:55 2016 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"15:01
openstackThe meeting name has been set to 'neutron_upgrades'15:02
mhickeyHello15:02
ihrachyso/ everyone15:02
roaeto/15:02
ihrachyshello everyone after Christmas break15:02
ihrachysthis is the first meeting this year15:03
ihrachyslet's go straight into topics15:03
roaethoo ah15:03
ihrachys#topic partial grenade15:03
*** openstack changes topic to "partial grenade (Meeting topic: neutron_upgrades)"15:03
ihrachyssc68cal: wanna update the team?15:03
ihrachysok, probably Sean is not avail for now, so I will try to accommodate15:04
*** akamyshnikova has joined #openstack-meeting-alt15:04
*** xyang1 has quit IRC15:04
ihrachysthe status is we still see grenade job failing on resource creation when ssh-ing into a cirros image, and it occurs not consistently15:04
ihrachyssc68cal made some modifications for grenade to see ssh debug output, and it seems that connection is established, but then dropbear never responds15:05
*** _amrith_ is now known as amrith15:05
ihrachysI had an idea today that maybe it's because of tunnelling headers not squeezing into mtu15:05
*** xyang1 has joined #openstack-meeting-alt15:06
*** dave-mccowan has joined #openstack-meeting-alt15:06
*** Sam-I-Am has joined #openstack-meeting-alt15:06
ihrachysposted some test patches for that, but seems like they are not enough to validate the fix: https://review.openstack.org/#/q/status:open+project:openstack/neutron+topic:bug/152767515:06
Sam-I-Ammorning15:06
ihrachysbut we'll see15:06
ihrachysthe patch passed once, though I am not sure it's because of the patch, or I was just lucky15:06
ihrachysso rechecking more15:07
*** dave-mcc_ has joined #openstack-meeting-alt15:07
ihrachysapart from that, I believe sc68cal also has this grenade patch in this context: https://review.openstack.org/26388415:08
ihrachysthat should change the way how we test for ssh connectivity, and should collect more logs for us.15:08
ihrachysbtw if that's indeed mtu issue, we may want to enable MTU advertisement as in: https://review.openstack.org/263486 (also from sc68cal)15:08
*** KarthikB has joined #openstack-meeting-alt15:09
ihrachysthat's on partial grenade. any questions? korzen? sc68cal?15:09
korzennothing from my side15:09
ihrachysok; let's move on15:09
ihrachys#topic versioned objects15:09
*** openstack changes topic to "versioned objects (Meeting topic: neutron_upgrades)"15:09
ihrachysrossella_s: wanna update on port?15:10
rossella_sihrachys, yep15:10
rossella_sihrachys, unfortunately I didn't have as much time as I wanted...anyway I think I figured out a way to split tasks15:10
ihrachysrossella_s: cool. that could be interesting to roaet and ski2 who were hungry for work items :)15:11
rossella_sthe thing is that port is composed by many part...I mean every extension defines some new attributes. I will take time to port everything15:11
*** dave-mccowan has quit IRC15:11
ihrachysrossella_s: what's the plan?15:12
*** neelashah has quit IRC15:12
*** neelashah has joined #openstack-meeting-alt15:12
rossella_sso I was planning to start from the leaf of the three...I will submit a patch later today/tomorrow to port a leaf, something simple like extra dhcp opts15:13
rossella_sthen other people can do the same for other extensions15:13
rossella_sthen we can finally go back to the port object15:13
ihrachysrossella_s: do we have a list of extensions to port? what do we do with extensions that are not in the tree?15:13
roaetare the ovo extensions going to patch in attributes?15:13
*** obondarev has quit IRC15:14
*** migi has quit IRC15:14
*** tellesnobrega is now known as tellesnobrega_af15:14
ihrachysroaet: I think we cannot just patch attrs in the object, since it changes its API. I would think of having a single field for the list of extension attrs.15:14
rossella_sihrachys, I can create a list of extensions, regarding extensions out of the tree they need to be ported too of course, I'd leave that for a second stage15:14
*** obondarev has joined #openstack-meeting-alt15:15
ihrachysrossella_s: we will need to think for some compatibility layer for at least a cycle I guess?15:15
roaethrmm. I guess I'll have to see it. I'm a bit puzzled about how to go about doing it.15:15
*** neelashah1 has joined #openstack-meeting-alt15:15
rossella_sroaet, an example is here https://review.openstack.org/#/c/253641 , see how binding is handled15:15
rossella_sihrachys, yes15:15
*** migi has joined #openstack-meeting-alt15:16
rossella_sihrachys, tbh I expected it to be less work ...I was too optimistic15:16
*** mixos has joined #openstack-meeting-alt15:16
ihrachysrossella_s: heh. isn't it always that way? :)15:16
rossella_sihrachys, yo15:17
*** neelashah has quit IRC15:17
ihrachysok, apart from ports, any news for network object? afair roaet was going to analyze the hierarchy for that.15:17
*** thrash has quit IRC15:17
korzenihrachys, yes, #link: https://review.openstack.org/#/c/26427315:18
roaetI'm in process of manually making an ERD for neutron15:18
*** sreshetnyak has quit IRC15:18
roaetAnd it was suggested to make this an automated process for devref docs as well15:18
korzenI have posted the Network and Subnet OVO patch15:18
ihrachyskorzen: niiice15:18
ihrachysroaet: korzen: you need to sync guys.15:18
ihrachysroaet: do you have specific ideas for automation?15:18
roaetthrowing it into tox's doc step as a separate python process15:19
roaetnot openstack-manuals, just neutron15:19
ihrachysroaet: what would be the output?15:19
roaeta png erd15:19
*** neelashah has joined #openstack-meeting-alt15:19
roaetbut I'm doing it manually first so I can get the OVO stuff done15:20
ihrachysok, I guess you will unravel it, and then we'll see how it looks like :)15:20
roaetthe erd automation is not necessary for OVO15:20
ihrachysroaet: see the patch from korzen ^ I haven't checked it yet, but I guess there is something already done there15:20
roaetbut the erd would be very helpful for discussions15:20
roaetI looked at that patch some days ago.15:20
*** neelashah1 has quit IRC15:20
ihrachysroaet: yeah, ERD is useful out of network object context.15:20
*** akamyshnikova has quit IRC15:20
*** thrash has joined #openstack-meeting-alt15:20
*** thrash has quit IRC15:20
*** thrash has joined #openstack-meeting-alt15:20
roaetit also shows all the relationships between the in-tree extensions and their 'parents'15:21
ihrachysroaet: ok. as long as you sync with korzen on what's missing, I am happy. :)15:21
roaetcool :D15:21
korzenI have taken the DHCP get_active_networks call and tried to mock it with Network OVO15:21
*** quade1 has joined #openstack-meeting-alt15:21
korzenall the attr are there15:21
korzenbut please take a look if you are in favor of my solution15:22
ihrachysok, another thing related to objects is mhickey's 'hasher' test that should from now on forbid unexpected changes to object API: https://review.openstack.org/25802615:22
ihrachyskorzen: haven't seen the patch till now; will take a look.15:22
*** akamyshnikova has joined #openstack-meeting-alt15:22
ihrachysthe hasher test is merged, so those messing with objects may get new test failures.15:23
mhickeyihrachys: patch for hasher done. patch in for o.vo to wrap temp registry pattern. #link: https://review.openstack.org/#/c/26380015:23
ihrachysmhickey: yay. thanks for that and the follow up.15:23
mhickeyihrachys: np. that should be near to finisht. then just add the wrapped methods to neutron.15:24
ihrachysaye aye15:24
ihrachysspeaking of object backports, ajo also posted a WIP patch for rpc callbacks upgrades: https://review.openstack.org/265347 everyone is welcome to check it out.15:24
*** belmoreira has quit IRC15:24
ihrachysajo: wanna update us on that one?15:24
ajohi, sure, I was running AFK, but I'm here yet :)15:24
*** jmckind has joined #openstack-meeting-alt15:25
ajoBasically, this implements the devref we proposed for such mechanism, but it's still incomplete,15:25
ajowhat I posted in that WIP is the core logic for it, so it's really worth reviewing even if marked as WIP15:25
*** Leo_ has joined #openstack-meeting-alt15:25
ajoprobably I will remove the WIP, and push the other bulletpoints of the commit message as a separate/separate patches15:25
*** mixos has quit IRC15:25
*** sreshetnyak has joined #openstack-meeting-alt15:26
ihrachyscool. folks, let's review that one. btw I will update the agenda for the meeting with links to new patches.15:26
ihrachysajo: if it's splittable, yeah15:26
ihrachys#topic bugs15:27
*** openstack changes topic to "bugs (Meeting topic: neutron_upgrades)"15:27
*** mixos has joined #openstack-meeting-alt15:27
*** nkrinner has quit IRC15:27
ihrachysI suspect we may have more content for the topic in the future, so let's adopt the habit of having one :)15:27
*** yamahata has joined #openstack-meeting-alt15:27
ihrachysI have one bug here to mention15:27
ihrachys#link https://bugs.launchpad.net/neutron/+bug/153177215:27
openstackLaunchpad bug 1531772 in neutron "Liberty server and Kilo security group aware agent fail to refresh firewall for DHCP and router IPv6 ports" [High,New] - Assigned to Ihar Hrachyshka (ihar-hrachyshka)15:27
ihrachysthat's basically rolling upgrade scenario broken for kilo to liberty upgrade for security groups15:28
ihrachysI don't have a patch yet; anyhow, I think some may find it worth checking the description and why it's broken. the brief idea is we made incompat change to rpc interface15:28
ihrachysrossella_s: could use your attention to that later ^ :)15:29
*** AlanClark has joined #openstack-meeting-alt15:29
rossella_sihrachys, of course15:29
ihrachysbtw see I marked the bug with 'upgrade' tag. it's unofficial, but better than nothing. if you have more bugs like that, please mark the same way.15:29
ihrachysok...15:30
ihrachys#topic open floor15:30
*** openstack changes topic to "open floor (Meeting topic: neutron_upgrades)"15:30
ihrachysanyone have stuff to raise?15:30
mhickeyihrachys: yes15:30
ihrachysmhickey: floor is yours15:30
mhickeyihrachys: https://review.openstack.org/#/c/248190/ : how to progress following conversation with HenryG today15:31
*** esheffield has joined #openstack-meeting-alt15:31
ihrachysmhickey: ok. first, let's update the review with some comments from discussion today. it's otherwise not clear what you refer to. :)15:31
mhickeyihrachys: sure. will I add a comment then?15:32
*** amitgandhinz has joined #openstack-meeting-alt15:32
*** weshay_xchat is now known as weshay15:33
ihrachysfor those unaware, that's a patch to allow to determine whether there are pending contract scripts in alembic. and there is some issue due to every subproject using a separate env.py with a separate version table that is not seen in scope of neutron-db-manage db context. we probably need some subproject API that could be consumed by neutron-db-manage to determine version table names.15:33
ihrachysmhickey: yeah, comment to add. it should give some more info to all reviewers.15:33
mhickeyihrachys: ok, thanks15:33
*** sdake has joined #openstack-meeting-alt15:33
ihrachysmhickey: I would suggest to talk to HenryG about when we expect his alternative idea of converging all projects to single env.py to arrive. if it's not Mitaka, I better search for alternative way to tackle it.15:34
ihrachysdoes that sound right?15:34
mhickeyihrachys: my thinking also. probably need some solution for M.15:34
mhickeyihrachys: kewl15:34
ihrachysmhickey: yeah, I already told ansible folks a command will be avail in M, so I would need to deliver :D15:35
*** kebray has joined #openstack-meeting-alt15:35
*** spzala has joined #openstack-meeting-alt15:35
mhickey:)15:35
ihrachysmhickey: they were otherwise introducing some huge hacks for that15:35
mhickeyihrachys: ack15:35
ihrachyslike walking thru the scripts, checking their file names...15:35
ihrachysok, anything else worth attention?15:36
*** kfarr has joined #openstack-meeting-alt15:36
*** sdake has quit IRC15:36
ihrachys3...15:36
ihrachys2...15:36
*** sdake has joined #openstack-meeting-alt15:36
ihrachys1...15:37
*** kebray has quit IRC15:37
ihrachysok thanks everyone for joining. will see you all in a week! happy hacking!15:37
ihrachyso/15:37
mhickeybye all. thanks ihrachys :)15:37
ihrachys#endmeeting15:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:37
openstackMeeting ended Mon Jan 11 15:37:27 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-01-11-15.01.html15:37
korzenbye15:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-01-11-15.01.txt15:37
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-01-11-15.01.log.html15:37
roaetsee you all15:37
rossella_sbye15:37
*** zz_dimtruck is now known as dimtruck15:37
*** roaet has left #openstack-meeting-alt15:38
*** kebray has joined #openstack-meeting-alt15:38
*** annegentle has quit IRC15:39
*** macsz has left #openstack-meeting-alt15:40
*** kebray has quit IRC15:40
*** spotz_zzz is now known as spotz15:42
*** neelashah1 has joined #openstack-meeting-alt15:42
*** neelashah has quit IRC15:43
*** Sukhdev has joined #openstack-meeting-alt15:44
*** neelashah has joined #openstack-meeting-alt15:45
*** Sam-I-Am has left #openstack-meeting-alt15:46
*** vgridnev has quit IRC15:46
*** zhangjn has quit IRC15:46
*** neelashah1 has quit IRC15:46
*** stanchan has quit IRC15:48
*** neelashah has quit IRC15:49
*** sylwesterB has quit IRC15:49
*** hyamauchi has joined #openstack-meeting-alt15:50
*** neelashah has joined #openstack-meeting-alt15:50
*** spotz is now known as spotz_zzz15:52
*** zeih has quit IRC15:52
*** gcb has joined #openstack-meeting-alt15:53
*** sdake_ has joined #openstack-meeting-alt15:53
*** tonytan4ever has joined #openstack-meeting-alt15:53
*** neelashah1 has joined #openstack-meeting-alt15:53
*** mtanino has joined #openstack-meeting-alt15:53
*** neelashah has quit IRC15:54
*** zeih has joined #openstack-meeting-alt15:54
*** sdake has quit IRC15:54
*** lazy_prince has joined #openstack-meeting-alt15:56
*** mrmartin has quit IRC15:56
*** balajiiyer has quit IRC15:57
*** neelashah has joined #openstack-meeting-alt15:57
*** sbalukoff has quit IRC15:57
*** neelashah1 has quit IRC15:58
*** kgiusti has joined #openstack-meeting-alt15:58
*** haypo has joined #openstack-meeting-alt15:58
*** spzala has quit IRC15:58
*** spzala has joined #openstack-meeting-alt15:59
dims_#startmeeting oslo16:00
dims_courtesy ping for GheRivero, amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dougwig, e0ne, flaper87, garyk, harlowja, haypo,16:00
dims_courtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, ozamiatin, redrobot, rpodolyaka, spamaps16:00
dims_courtesy ping for sergmelikyan, sreshetnyak, sileht, sreshetnyak, stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek, gcb16:00
openstackMeeting started Mon Jan 11 16:00:49 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
rpodolyakao/16:00
*** openstack changes topic to " (Meeting topic: oslo)"16:00
openstackThe meeting name has been set to 'oslo'16:00
kgiustio/16:00
toabctlhi16:01
dhellmanno/16:01
ozamiatin_o/16:01
jecarey0/16:01
gcbo/16:01
rbradforo/16:01
dims_hi rpodolyaka kgiusti toabctl dhellmann jecarey ozamiatin_ gcb rbradfor16:01
ihrachyso/16:01
dims_hi ihrachys16:01
dims_#topic Red flags for/from liaisons16:01
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"16:01
kragnizo/16:01
flaper87o/16:01
*** esker has joined #openstack-meeting-alt16:01
*** esker has quit IRC16:01
ihrachysnothing from neutron side, or I am ignorant :)16:01
*** annegentle has joined #openstack-meeting-alt16:02
dims_ihrachys : thanks16:02
*** balajiiyer has joined #openstack-meeting-alt16:02
gcbnothing from nova as I know :-)16:02
*** resker has joined #openstack-meeting-alt16:02
dims_thanks gcb16:02
amrith./16:02
dims_gcb there's a oslo.cache review in nova that we'll need to resurrect16:03
*** IlyaG has joined #openstack-meeting-alt16:03
amrithnothing from trove.16:03
dims_#topic Releases for Mitaka16:03
dims_#link https://review.openstack.org/#/c/265673/16:03
*** openstack changes topic to "Releases for Mitaka (Meeting topic: oslo)"16:03
dims_i have not lined up pbr or oslo.messaging or taskflow for this round16:03
*** neelashah1 has joined #openstack-meeting-alt16:03
*** spzala has quit IRC16:04
dims_oslo.messaging has the pika driver merged from feature branch to master, so i'd like folks to look at the code that was merged16:04
dims_please16:04
*** quade1 has left #openstack-meeting-alt16:04
*** neelashah has quit IRC16:04
*** kebray has joined #openstack-meeting-alt16:04
dims_my travis setup looks green with the latest in master branches of oslo.* - https://travis-ci.org/dims/ except for may be a py34 test case in nova for which they have a blacklist file that can be updated16:05
ihrachysdims_: speaking of pbr, are we going to release one for kilo? we had some issues with testr lately, that could be fixed by pbr release with some backports.16:05
*** kebray has quit IRC16:05
*** regebro is now known as Guest6873616:06
*** regebro has joined #openstack-meeting-alt16:06
dims_ihrachys : this one? https://review.openstack.org/#/c/265684/16:06
*** kebray has joined #openstack-meeting-alt16:06
ihrachysdims_: right16:06
*** Prem has joined #openstack-meeting-alt16:06
*** rsyed is now known as rsyed_away16:06
dims_ihrachys : let's get lifeless to +1 that one and then chat about it in #openstack-release if it is still stuck16:07
dims_cool?16:07
*** neelashah has joined #openstack-meeting-alt16:07
ihrachysaye16:07
dims_k next topic16:07
dims_#topic osprofiler adoption spec16:07
dims_#link https://review.openstack.org/#/c/103825/16:07
*** openstack changes topic to "osprofiler adoption spec (Meeting topic: oslo)"16:07
dims_there's a bunch of +1's so far16:08
*** neelashah1 has quit IRC16:08
dims_may i please have +1's from folks here? please add it to your review queue for today?16:08
dims_dhellmann : would love to see your vote16:09
*** salv-orl_ has joined #openstack-meeting-alt16:09
dhellmanndims_ : sure, I'll take a look. Is there a separate cross-project spec or is this just an oslo thing16:09
dhellmann?16:09
dims_dhellmann : this one proposes oslo as a home for the library16:10
dhellmannah16:10
dims_k next one is slightly more controversial16:10
dims_#topic oslo.messaging compression16:11
*** openstack changes topic to "oslo.messaging compression (Meeting topic: oslo)"16:11
dims_#link https://review.openstack.org/#/c/247668/16:11
*** annegentle has quit IRC16:11
dims_the issue with this one was kombu has a easy toggle to switch on compression https://review.openstack.org/#/c/249215/5/oslo_messaging/_drivers/impl_rabbit.py16:11
dims_and zmq does not convert the full payload to json before shipping16:12
*** salv-orlando has quit IRC16:12
dhellmanndoes that make it a feature of the driver, instead of the library, then?16:12
dims_so it's a toss up between how we can use existing mechanisms to switch on compression vs do we force drivers to json first then send the message16:12
dims_dhellmann : right16:13
ozamiatin_dims_: dhellmann: ++ for making it a feature of a driver16:13
dhellmannI haven't read the spec, but it seems like the easy win for now is to make it a driver option and then when all of the drivers support it we can deprecate those options in favor of a central one16:13
dims_dhellmann : y, that's what i was leaning towards as well. we'll learn first from that exercise in a single driver16:14
dhellmannright16:14
*** spotz_zzz is now known as spotz16:14
dims_flaper87 : kgiusti : any opinions?16:14
dims_ozamiatin_ : ack agree16:15
kgiustidims_: +1 to driver for now.16:15
dims_kgiusti : ok, please vote on the spec when you get a chance to review16:15
*** snackewm has joined #openstack-meeting-alt16:16
kgiustidims_: will do16:16
flaper87no objections from me16:16
*** sigmavirus24_awa is now known as sigmavirus2416:16
dims_cool thanks16:16
dims_#topic Open discussion16:16
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"16:16
dims_Any other reviews? specs?16:16
ozamiatin_dims_: Need review of https://review.openstack.org/#/c/261546/ and https://review.openstack.org/#/c/265414/16:16
dims_ozamiatin_ : ack starred them both16:17
*** annegentle has joined #openstack-meeting-alt16:17
ozamiatin_dims_: thanks16:17
dims_rpodolyaka : ping about the discussion with zzzeek on ML16:18
dims_rpodolyaka : do we propose any changes in oslo libs for that discussion?16:18
rpodolyakanot yet16:19
dims_#link http://markmail.org/message/k3vpwqihums3obtv16:19
rpodolyakabut looks like we should - at least for oslo.service16:19
rpodolyakabut probably for oslo.db too16:19
rpodolyakaI'll go over the thread once again and probably ping mhorban and ezhova16:20
*** snackewm has quit IRC16:20
dims_rpodolyaka : much appreciated :)16:20
rpodolyakanp16:20
dims_kgiusti toabctl dhellmann jecarey ozamiatin_ gcb rbradfor kragniz ihrachys flaper87 amrith - any other things to talk about today?16:20
rpodolyakacredit really goes to zzzeek who spotted this16:20
dims_yep +100016:20
amrithyes16:20
amrithsince change https://review.openstack.org/#/c/257561/ (077fee4d439a6ecfa95e4e5626e4c5a3f9e7a72d) has now merged, I'd like to know when we'd get a new version of the oslo.utils so we can update requirements.txt and begin to use the new method.16:20
*** snackewm has joined #openstack-meeting-alt16:21
dims_amrith : i've lined up a release for today, you can propose a g-r update when the release goes out. as policy we don't automatically bump versions in g-r16:21
amrithok, wilco16:21
dims_thanks16:22
dims_i am missing harlowja :) hey, you around?16:22
dims_last call before we wrap up :)16:23
*** apetrich has quit IRC16:23
dims_i'll wait today for any last feedback on the osprofiler spec16:23
*** jmckind has quit IRC16:24
dims_and we can get that rolling tomorrow16:24
dims_boris-42 : ^^16:24
*** jmckind has joined #openstack-meeting-alt16:24
dims_anyone involved in oslo.messaging, please look through the pika code16:24
dims_thanks everyone!16:24
dims_#endmeeting16:24
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:25
openstackMeeting ended Mon Jan 11 16:24:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-01-11-16.00.html16:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-01-11-16.00.txt16:25
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-01-11-16.00.log.html16:25
*** lazy_prince has quit IRC16:25
*** killer_prince has joined #openstack-meeting-alt16:26
*** lazy_prince has joined #openstack-meeting-alt16:26
*** lazy_prince has quit IRC16:26
*** edtubill has joined #openstack-meeting-alt16:26
*** sdake_ is now known as sdake16:27
*** diazjf has joined #openstack-meeting-alt16:28
*** mixos has quit IRC16:30
*** j___ has quit IRC16:30
*** thomnico has quit IRC16:31
*** gcb has quit IRC16:31
*** rsyed_away is now known as rsyed16:32
*** _nadya_ has joined #openstack-meeting-alt16:33
*** paul-carlton2 has quit IRC16:34
*** dizquierdo has quit IRC16:37
*** kgiusti has left #openstack-meeting-alt16:37
*** rvyalov_ has quit IRC16:38
*** kebray has quit IRC16:39
*** sylwesterB has joined #openstack-meeting-alt16:42
*** ninag has joined #openstack-meeting-alt16:44
*** vgridnev has joined #openstack-meeting-alt16:44
*** Swami has joined #openstack-meeting-alt16:45
*** mixos has joined #openstack-meeting-alt16:46
*** sylwesterB has quit IRC16:47
boris-42dims_: ok great16:49
*** vahidh has joined #openstack-meeting-alt16:50
*** haypo has left #openstack-meeting-alt16:50
*** regebro has quit IRC16:53
*** yamamoto has quit IRC16:53
*** regebro has joined #openstack-meeting-alt16:53
*** regebro has quit IRC16:53
*** regebro has joined #openstack-meeting-alt16:54
*** mhickey has quit IRC16:55
*** armax has joined #openstack-meeting-alt16:55
*** ihrachys has quit IRC16:55
*** dims has joined #openstack-meeting-alt16:56
*** dims_ has quit IRC16:56
*** matrohon has quit IRC16:57
*** spzala has joined #openstack-meeting-alt16:58
*** yamahata has quit IRC16:58
*** migi has quit IRC16:58
*** migi has joined #openstack-meeting-alt16:58
*** vishwana_ has joined #openstack-meeting-alt17:00
*** HeOS has quit IRC17:00
*** jprovazn has joined #openstack-meeting-alt17:01
*** kebray has joined #openstack-meeting-alt17:01
*** mixos has quit IRC17:01
ativelkovCourtesy artifact team meeting reminder: nikhil_k, ativelkov, mfedosin, flaper8717:02
*** spzala has quit IRC17:02
ativelkovFolks, anybody here for the artifacts meeting?17:02
*** mfedosin has joined #openstack-meeting-alt17:02
*** vishwanathj has quit IRC17:03
*** sgotliv_ has quit IRC17:03
*** mixos has joined #openstack-meeting-alt17:03
*** jokke_ has joined #openstack-meeting-alt17:04
jokke_o/17:04
mfedosino/17:04
*** kairat_ has joined #openstack-meeting-alt17:05
ativelkov#startmeeting glance-artifacts17:05
openstackMeeting started Mon Jan 11 17:05:07 2016 UTC and is due to finish in 60 minutes.  The chair is ativelkov. Information about MeetBot at http://wiki.debian.org/MeetBot.17:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:05
*** openstack changes topic to " (Meeting topic: glance-artifacts)"17:05
openstackThe meeting name has been set to 'glance_artifacts'17:05
*** eranra has joined #openstack-meeting-alt17:05
kairat_o/17:05
ativelkovHi folks17:05
*** FallenPegasus has joined #openstack-meeting-alt17:05
mfedosinhi!17:05
jokke_hello17:05
* jokke_ is lurking around17:06
*** FallenPegasus is now known as MarkAtwood17:06
ativelkovThe agenda is supposed to be here https://etherpad.openstack.org/p/glance-artifacts-sub-team-meeting-agenda but we don't have anything for today, since most of the artifacts team were on the new-year vacation17:06
kzaitsev_mbo/17:06
ativelkov#topic status update17:07
*** openstack changes topic to "status update (Meeting topic: glance-artifacts)"17:07
*** gyee has joined #openstack-meeting-alt17:08
ativelkovTechnically I don't have much to update (since the long vacation period). All our specs got frozen due to the specFreeze happened one week before the NY17:08
mfedosinI think I can upload a draft code for public glare api tomorrow or on Wednesday17:09
*** sigmavirus24 is now known as sigmavirus24_awa17:09
ativelkovmfedosin: having a draft for the un-approved API spec is a bit too brave :)17:09
kairat_+117:09
ativelkovBut let's have some work started anyway17:09
kairat_Are we going to request FFE for artifacts? or it is assumed by default?17:10
mfedosinbut it requires some update in Alex patch17:10
*** safchain has quit IRC17:10
*** killer_prince has quit IRC17:10
mfedosinativelkov, should I drop this job? :)17:10
*** mixos has quit IRC17:11
ativelkovkairat_: this needs to be discussed with the Drivers. Technically Glare is an experimental feature, and it has the FastTrack concept, so we may drive it faster then the rest of the Glance, however the proper guidance from the drivers team is neede17:11
jokke_I'd be pro of getting code draft up ... might help to get the SFE going through if there is something done to achieve the goal even the agreement comes in late17:12
*** mixos has joined #openstack-meeting-alt17:12
*** paul-carlton2 has joined #openstack-meeting-alt17:12
ativelkovmfedosin: of course not :) Just don't forget that anything which is not approved may be changed at any moment. But let's get the code going17:13
*** yamamoto has joined #openstack-meeting-alt17:13
ativelkovjokke_: ++17:13
*** yamamoto has quit IRC17:13
mfedosinanyway we need this code (glare public api), so there's nothing bad to have it on review17:13
jokke_++17:13
ativelkovmfedosin: right, it also simplifies the API review if some implementation is present17:13
ativelkovjust don't forget to put a WiP tag to not confuse the reviewers17:14
ativelkovWe may revisit this questions after tomorrow's drivers meeting17:14
ativelkovglance /v3 -> glare v0.1 patch is still waiting for more reviews at https://review.openstack.org/#/c/255274/17:15
mfedosinativelkov, okay, I will. But let me skip functional tests for the first ps ;)17:15
*** _nadya_ has quit IRC17:15
ativelkovmfedosin: ok, np17:16
ativelkovmfedosin: btw, you had some questions on the patch above, if I remember correctly. Please make sure you leave your comments there17:16
ativelkovThat's all for the status update I believe17:17
ativelkov#topic open discussion17:17
*** openstack changes topic to "open discussion (Meeting topic: glance-artifacts)"17:17
mfedosinI'm writing it17:17
ativelkovAny other questions?17:17
*** _nadya_ has joined #openstack-meeting-alt17:17
*** tellesnobrega_af is now known as tellesnobrega17:18
mfedosinnothing from my side17:18
ativelkovOk, then we are probably done17:19
*** zeih has quit IRC17:19
ativelkovIt's still the beginning of the year here in Russia, everything is sooo slow :)17:19
ativelkovThanks everyone17:19
ativelkov#endmeeting17:19
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:19
openstackMeeting ended Mon Jan 11 17:19:46 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:19
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance_artifacts/2016/glance_artifacts.2016-01-11-17.05.html17:19
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance_artifacts/2016/glance_artifacts.2016-01-11-17.05.txt17:19
openstackLog:            http://eavesdrop.openstack.org/meetings/glance_artifacts/2016/glance_artifacts.2016-01-11-17.05.log.html17:19
*** rvyalov_ has joined #openstack-meeting-alt17:22
*** yamahata has joined #openstack-meeting-alt17:22
*** kairat_ has left #openstack-meeting-alt17:22
*** zeih has joined #openstack-meeting-alt17:22
*** tonytan4ever has quit IRC17:23
*** bana_k has joined #openstack-meeting-alt17:28
*** bharathm has joined #openstack-meeting-alt17:28
*** nikhil has joined #openstack-meeting-alt17:33
*** ajmiller_ has joined #openstack-meeting-alt17:33
*** bana_k has quit IRC17:35
*** minwang2 has joined #openstack-meeting-alt17:36
*** ajmiller__ has joined #openstack-meeting-alt17:36
*** ajmiller has quit IRC17:36
*** kzaitsev_mb has quit IRC17:36
*** pvaneck has joined #openstack-meeting-alt17:37
*** bana_k has joined #openstack-meeting-alt17:37
*** ajmiller_ has quit IRC17:38
*** amrith is now known as _amrith_17:39
*** _amrith_ is now known as amrith17:40
*** mrmartin has joined #openstack-meeting-alt17:43
*** neelashah1 has joined #openstack-meeting-alt17:44
*** vahidh has quit IRC17:45
*** eranra has quit IRC17:45
*** neelashah has quit IRC17:45
*** vishwanathj has joined #openstack-meeting-alt17:46
*** neelashah has joined #openstack-meeting-alt17:47
*** vishwana_ has quit IRC17:48
*** hyamauchi has quit IRC17:48
*** neelashah1 has quit IRC17:48
*** ajmiller__ is now known as ajmiller17:49
*** derekh has quit IRC17:51
*** neelashah1 has joined #openstack-meeting-alt17:51
*** _nadya_ has quit IRC17:51
*** neelashah has quit IRC17:52
*** sdake has quit IRC17:53
*** numans has joined #openstack-meeting-alt17:55
*** pnavarro has quit IRC17:55
*** neelashah1 has quit IRC17:56
*** neelashah has joined #openstack-meeting-alt17:56
*** sputnik13 has joined #openstack-meeting-alt17:59
*** zeih has quit IRC17:59
*** ijw has joined #openstack-meeting-alt17:59
*** e0ne has quit IRC18:01
*** ihrachys has joined #openstack-meeting-alt18:04
*** shwetaap has quit IRC18:04
*** ijw has quit IRC18:04
*** numans has quit IRC18:06
*** SpamapS has quit IRC18:10
*** dizquierdo has joined #openstack-meeting-alt18:11
*** shwetaap has joined #openstack-meeting-alt18:12
*** yamamoto has joined #openstack-meeting-alt18:13
*** nsun1 has joined #openstack-meeting-alt18:13
*** nsun1 has quit IRC18:14
*** sdake has joined #openstack-meeting-alt18:15
*** qwebirc90355 has joined #openstack-meeting-alt18:16
*** qwebirc90355 has quit IRC18:17
*** sileht has quit IRC18:17
*** Sukhdev has quit IRC18:17
*** balajiiyer has quit IRC18:19
*** Sukhdev has joined #openstack-meeting-alt18:20
*** yamamoto has quit IRC18:21
*** rossella_s has quit IRC18:22
*** rossella_s has joined #openstack-meeting-alt18:22
*** mrmartin has quit IRC18:23
*** Aish has joined #openstack-meeting-alt18:27
*** Sukhdev has quit IRC18:28
*** diazjf has quit IRC18:29
*** bana_k has quit IRC18:32
*** bharathm has quit IRC18:33
*** sileht has joined #openstack-meeting-alt18:33
*** rsyed is now known as rsyed_away18:35
*** SpamapS has joined #openstack-meeting-alt18:36
*** paul-carlton2 has quit IRC18:36
*** ozamiatin_ has quit IRC18:38
*** flaviof has joined #openstack-meeting-alt18:40
*** diazjf has joined #openstack-meeting-alt18:40
*** bharathm has joined #openstack-meeting-alt18:40
*** rcurran has joined #openstack-meeting-alt18:41
*** annegentle has quit IRC18:43
*** neelashah has quit IRC18:44
*** jmckind has quit IRC18:44
*** davideag_ has quit IRC18:46
*** apetrich has joined #openstack-meeting-alt18:48
*** catherineD has joined #openstack-meeting-alt18:49
*** e0ne has joined #openstack-meeting-alt18:49
*** davideagnello has joined #openstack-meeting-alt18:50
*** mrmartin has joined #openstack-meeting-alt18:51
*** rsyed_away is now known as rsyed18:53
*** ijw has joined #openstack-meeting-alt18:53
*** Prem has quit IRC18:55
*** barra204 has joined #openstack-meeting-alt18:55
*** shakamunyi has quit IRC18:56
*** spzala has joined #openstack-meeting-alt18:56
*** diazjf has quit IRC18:59
*** alevine has joined #openstack-meeting-alt19:01
*** alevine has left #openstack-meeting-alt19:01
*** rockyg has joined #openstack-meeting-alt19:01
*** shwetaap has quit IRC19:01
*** nelsnels_ has quit IRC19:02
*** nelsnelson has joined #openstack-meeting-alt19:03
*** s3wong has joined #openstack-meeting-alt19:03
*** pvaneck has quit IRC19:03
catherineD#startmeeting refstack19:03
openstackMeeting started Mon Jan 11 19:03:27 2016 UTC and is due to finish in 60 minutes.  The chair is catherineD. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: refstack)"19:03
openstackThe meeting name has been set to 'refstack'19:03
*** pvaneck has joined #openstack-meeting-alt19:03
rockygo/19:03
pvanecko/19:03
catherineDHappy New Year!!!19:04
*** shwetaap has joined #openstack-meeting-alt19:05
rockygand in return!19:05
catherineDLet wait for a few minutes19:05
catherineD#link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-16-01-1119:06
catherineDWe did not have a meeting last week because most of the team members were on vacation19:07
*** alevine has joined #openstack-meeting-alt19:07
alevineo/19:07
catherineDalevine: welcome back ... Is today your first day back from holiday?19:08
alevinecatherineD: Yes :)19:08
hogepodgeo/19:08
*** thomnico has joined #openstack-meeting-alt19:08
*** fredyx10 has quit IRC19:08
catherineD#link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-16-01-1119:08
catherineDlet's start19:09
*** fredyx10 has joined #openstack-meeting-alt19:09
*** annegentle has joined #openstack-meeting-alt19:09
catherineD#topic Alex Levin's RefStack Requirements document19:09
*** openstack changes topic to "Alex Levin's RefStack Requirements document (Meeting topic: refstack)"19:09
catherineD#link https://docs.google.com/document/d/1s_dAIuluztlCC6AZ-WO4_FR2CLje1QyS6kbMxlFHaMk/edit?usp=sharing19:09
catherineDI know rockyg: and hogepodge: may not have a chance to review this doc ...19:10
rockyggot that right, but skimming now...19:10
catherineDalevine: seems like pvaneck: does not have the privilege to add comments ...19:10
pvaneckno i got that now19:11
pvanecklooks good19:11
catherineDpvaneck: that is great ..19:11
pvaneck Seems to me the main remaining issue is in regards to to how regular users (user's not associated to a vendor) creating products should be handled?19:11
alevinecatherineD: Have you had a chance to share it with Mark? Because I reviewed his spec and some of the explanations would've been given in the doc more clearly then in my comments to his spec.19:11
*** vilobhmm11 has joined #openstack-meeting-alt19:11
*** vilobhmm11 has quit IRC19:11
*** vilobhmm11 has joined #openstack-meeting-alt19:11
catherineDalevine: I view your doc is the requirment and his spec is for implementation ...19:12
*** shakamunyi has joined #openstack-meeting-alt19:12
*** barra204 has quit IRC19:12
alevinecatherineD: Nope19:12
*** amrith is now known as _amrith_19:13
alevinecatherineD: His spec is mostly about requirement.19:13
catherineDalevine: did you see  my comments on Mark's spec?19:13
alevinecatherineD: Yes. There were a couple.19:13
catherineDalevine: I think the major disagreement is on how to handle group of users ...19:14
catherineDIn Mark's spec and my opinion, we manage this by creating a group entity19:15
*** neelashah has joined #openstack-meeting-alt19:15
catherineDalevine: maybe you can explain your idea of build-in user group?19:15
*** rcurran has quit IRC19:16
alevinecatherineD: I did in the doc.19:16
alevinecatherineD: Let me copy-paste it here19:16
alevineBy explicit Group I meant Group visible to the end-user. Internally a Group entity will exist and will be stored in the DB. Its ID will be an attribute of the corresponding Organization. It would be created along with Organization and destroyed along with it. It won't exist as a standalone thing. As I said - the built-in group. Same as a built-in groups, say, in Windows.19:17
alevinecatherineD: I'm against having Group entity exposed to end user. I see it as an unnecessary complication for our implementation. Maybe it's not what's requested by Mark but it's how he wrote it.19:18
rockygI think maybe it's kinda the default group for an entity, maybe?19:18
alevinerockyg: Exactly19:19
catherineDIf group is not exposed to end users, how would this group be managed?19:19
alevinerockyg: The thing is, what I'm saying is that no other groups are needed besides those default ones.19:19
*** ninag has left #openstack-meeting-alt19:19
rockyggroup managed by entity owner19:19
alevinecatherineD: Not as a group. User won't be able to create a new group or remove an existing one or list groups. He'll be able to manage user-admins for particular organization instead. Add them (Users), remove, list and so on.19:20
catherineDrockyg: and entity owner is an end user , therefore group needed to be expose to end user19:20
alevinecatherineD: Not the group. Its users.19:20
alevinecatherineD: I'm saying there won't be means to list groups or manage them. But there will be means list and manage admins of particular organization.19:20
pvaneckI'm okay with this model19:21
rockygwould the org-admin be able to list members of group?19:21
alevinerockyg: Of course.19:22
alevineI don't want us to implement "GROUP management". I want us to deal with "USER management" only.19:23
catherineDpvaneck: perhaps you can describe the model per your understanding19:23
rockygso, all those functions are admin functions and end-user function is limited to listing name of the group and other properties, like maybe admin (need a contact in there;-)19:23
pvaneckjust no explicit group creation/deletion that a user can initiate19:23
pvaneckgroup creations will be tied to the creation of orgs/products19:23
alevinepvaneck: Exactly19:24
pvaneckI think that is a reasonable way to go about it19:24
catherineDalevine: from pvaneck: 's statement a group will also create when a product is created ..19:25
*** diazjf has joined #openstack-meeting-alt19:25
alevinecatherineD: Could you rephrase? :)19:25
catherineDMy understanding of pvaneck: 's statement are:19:26
catherineD1) when an organization is created ... a group will also be created19:26
alevinecatherineD: Ah :) Yes a group will be created along with an organization (vendor). Not a product.19:26
alevine1) correct19:27
catherineD2) when an product is created ... a group will also be created ...19:27
alevine2) Not initially. Only when we would introduce the per-product admins, which is not in the initial version. So, no. Initially it's not true.19:27
catherineDwho will manage the product ?19:28
alevineAdmins of the Organization19:28
alevineThe one which created the Product19:28
catherineDso we need to have an Organization created before a product can be created ..?19:29
rockygsounds like.19:29
alevineYes, that's why I wrote about hidden vendor for each User unless he's an admin of a registered vendor.19:29
catherineDalevine: that is the point that I am not confortable with ... hidden vendor ...19:30
catherineDhow does RefStack differentiate hidden vs real vendors?19:30
alevineThat's reasonable I guess. Product cannot be created out of thin air. So it's either Organization or User should create it. However I suggest simplifying the model by associating each User with his "self-employed" company, unless he works officially for a registered Vendor.19:31
alevineWhat do you mean by RefStack?19:31
*** neelashah has quit IRC19:31
alevineDescribe the use-case.19:31
catherineDIn the RefStack code19:31
*** neelashah has joined #openstack-meeting-alt19:31
alevineA new user is registered. When he/she wants to create a product we create a Vendor for him/her, unless existed. Then the product is associated with that Vendor. That Vendor is not listed or anything. It's tightly associated with the User.19:32
*** kzaitsev_mb has joined #openstack-meeting-alt19:32
catherineDalevine: we agree with DefCore that vendor  list will be provided by the Foundation ...19:33
rockygRedhat vs Rockys-redhat?  What if a user submits multiple test results for multiple clouds?  Let's call that user Monty ;-)19:33
pvaneckwould having a product-group association eliminate the need for the hidden vendor creation. Just when a regular user creates a product, a group is created with the user as the admin?19:33
alevinecatherineD: And?19:33
*** spzala has quit IRC19:33
alevinerockyg: I tried to describe in the use-cases listed in the doc all the cases. I'll check this particular one.19:34
catherineDRefStack will not provide  vendor registration ....19:34
*** spzala has joined #openstack-meeting-alt19:34
*** minwang2 has quit IRC19:34
alevinepvaneck: No. It won't.19:34
catherineDsince vendor list will be imported from a list provided by foundation19:34
alevinepvaneck: It'll just drastically change the model and make it a little strange. Also, there is such a thing as Guidelines which also should be "owned" and they are not a Product.19:35
rockygalevine, I'm confused about #12 on pg 6.19:35
alevinecatherineD: Ok. Let's say there is an "Organization" - some Organization, not requiring any registration. A private company. And there is Vendor which is registered by RefStack. Vendor will have official registration.19:36
rockygYeah.  Those guidelines are what are confusing me, as I am only aware of DefCore guidelines?19:36
rockygOr is this to allow things like EC2 guidelines added by a different group?19:36
catherineDrockyg: that is the idea19:36
*** _amrith_ is now known as amrith19:37
*** spzala_ has joined #openstack-meeting-alt19:37
catherineDrockyg: but we still want to take care of the DefCore cases first19:37
alevinecatherineD: #12 is about user submitting new Guidelines for a someone else's Product.19:37
alevinerockyg: Yes, those are the external Products guidelines.19:37
*** hyamauchi has joined #openstack-meeting-alt19:38
rockygWhy would a vendor need to approve the guidelines?  They should be out there and if a vendor wants to run the tests, fine, they're official, but if others do, it's just a user's test set?19:38
alevinerockyg: You can see an example here: http://refstack.cloudscaling.com:8000/#/schemas19:38
catherineDalevine: I don't think we want to have any one to create a Guideline19:38
alevinerockyg: They are called Schemas there at the moment. You can see AWS and PCF schemas.19:38
*** spzala has quit IRC19:38
catherineDGuideline should be created by a standard body like DefCore19:38
alevinerockyg: If I submit a new Guidelines for testing OpenStack definitely the Foundation would want to approve them before allowing anybody to test OpenStack with it, right? Same goes for any other Product.19:39
*** rsyed is now known as rsyed_away19:39
catherineDalevine: we are really confused if we keep using the same term like "schema" for different things19:39
alevinecatherineD: We already have. You won't be able to add external Products without new Guidelines. See the AWS. The won't be accepted by Foundation so we had to create and manage them.19:39
catherineDfor RefStack schema means what is stored in https://github.com/openstack/defcore/tree/master/doc/source/schema19:40
alevinecatherineD:  That's why I changed it in the doc to "Guidelines". It just stays named "schema" in the prototype for now. We'll change later of course.19:40
*** sdake has quit IRC19:40
alevinecatherineD: Of course I know. I mentioned it in the doc as well.19:40
*** spzala_ has quit IRC19:41
*** kzaitsev1mb has joined #openstack-meeting-alt19:42
alevineSuppose you created a new component for the OpenStack which is not yet accepted (or never be), say Manila (I don't remeber if it's accepted yet), and I want my users to start using Manila and validating clouds against my tests - I have to supply the tests and Guidelines for this, right?19:42
*** kzaitsev_mb has quit IRC19:44
*** kzaitsev1mb is now known as kzaitsev_mb19:44
rockygAh.  So, doc needs more clarity on definitions.  Guidelines are any test set specified by DefCore or approved for use on RefStack by Defcore.19:45
catherineDalevine: I would say that scenareo will be managed by DefCore19:46
catherineDand DefCore will put out a new Guideline as it did with 2016.01 (today)19:46
rockygProduct includes non-openstack cloud apis and ecosystem products that are approved for testing against in Refstack19:46
catherineDrockyg: Guideline is the like today's DefCore Guideline (2015.07, 2016.01 ..)19:47
alevinerockyg: No, not approved by DefCore. The won't manage external testing and external Products - that's what they said. And I agree.19:47
alevinerockyg: Guidelines - Output of the DefCore process detailing which sections and capabilities are required. Guidelines will be approved on a regular cadence and identified by the date of approval. Expressed by json. Guidelines must conform to one of the schema defined in https://github.com/openstack/defcore/tree/master/doc/source/schema19:47
alevinerockyg: That's the definition of DefCore. I didn't change it there. I can add that Guidelines can be created for External Products not managed and approved by DefCore.19:48
*** stevebaker has quit IRC19:49
rockygOK.  So, the EC2 list of tests aren't "guidelines", so "other compatability test sets"? Or some such?19:49
alevinerockyg: Product is refers to "software" or "cloud". Both are Products of some Vendor. Software is installed on Cloud and can be tested by some defined Guidelines.19:49
rockygAnd if DefCore isn't the body saying which test sets are ok to add to Refstack, who is?  Foundation?  TC?19:50
alevinerockyg: List of tests is not a Guidelines. But the json containing this list and names of tests and target programs is.19:50
alevinerockyg: Vendor. For its Products.19:50
*** mspreitz has joined #openstack-meeting-alt19:51
rockygBecause if it's a vendor, then Amazon would have to be the vendor to approve the EC2 tests, wouldn't it?19:51
alevinerockyg: Right now DefCore is such a Vendor for the Product OpenStack.19:51
*** NazcaLines has joined #openstack-meeting-alt19:51
*** stevebaker has joined #openstack-meeting-alt19:51
alevinerockyg: That's correct. However Amazon doesn't care so we'll be representing it, since we created the EC2 API layer.19:51
pvaneckSo i seem to see where you are going with the hidden vendor for each user creating a product or guideline.19:52
rockygHmmm.  So, again, who gives the go ahead to add to Refstack server since it's a foundation server?19:52
pvaneckalevine: If the same regular user creates multiple products, all these products would fall under the same hidden vendor for that user, right?19:52
alevinepvaneck: Great :)19:53
*** rsyed_away is now known as rsyed19:53
catherineDalevine: pvaneck: I like that19:53
rockygIn EC2 case, vendor would have to demonstrate right to use the trademarks and make the claims of compatibility?19:53
catherineDhidden vendor is associated to a user not a product19:54
hogepodgeWhy can't refstack just take an external guideline as a parameter and evaluate a test result against it?19:54
alevinerockyg: According to the agreement with the DefCore guys the do not care if external tests get into their DB, so the Foundation (DefCore) manages and approves only the OpenStack related Products/Guidelines and each other  Vendor works with his own stuff.19:54
hogepodgeIt's essentially what it does right now, just with the external uris hard coded to pull defcore because it is a special primary use case for refstack19:54
alevinepvaneck: Yes, exactly.19:54
hogepodgeThen everyone can bring whatever guideline they want to the table, without a complex interface19:55
catherineDok we are discussing 2 topics at the same time now19:55
rockygOK.  I suspect the Foundation would want to verify if any guideline claims compat to trademarked products, though.19:55
alevinerockyg: We're not doing nothing official for non-OpenStack Vendors. Those are just validations and the results. So no need to care about trademarks I guess.19:56
alevinehogepodge: Pretty much.19:56
catherineDnotes that 4 mins remaining ...19:56
pvaneckhogepoge: that is doable19:56
catherineDI will need to end the meeting soon ... let's go to #refstack after this ...19:57
alevinerockyg: Well, I don't see why would they? There are no "claims" only results of tests and some "badges" (pictures) we show as a result of successful validation.19:57
catherineDbut I want to document our agreement regarding explicit/implicit user group creation19:57
rockygOK.  Just the presence of the trademarked names, if there, might need to have some legalese or something...asterisk with the note at bottom of owner, etc.19:58
alevinecatherineD: I'm sorry, can we continue tomorrow?19:58
rockygcatherineD, ++19:58
catherineDsure ...19:58
catherineDby one agreement we can log19:58
rockygAnd clarification in the doc, please?19:58
alevinerockyg: Probably you're right. We can take the trademarked names and base64-encode them to avoid problems :) (just a joke)19:59
catherineD#agreed Group will be created implicitly.  So, RefStack will provide user management and not group management.19:59
alevinerockyg: Clarification about the Guidelines which can be external? Could you please put your comments in the doc wherever you need any clarification?19:59
alevineI'll be more than happy to clarify19:59
rockyg<snicker>19:59
catherineD#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Mon Jan 11 20:00:06 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
*** minwang2 has joined #openstack-meeting-alt20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2016/refstack.2016-01-11-19.03.html20:00
*** spzala has joined #openstack-meeting-alt20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2016/refstack.2016-01-11-19.03.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2016/refstack.2016-01-11-19.03.log.html20:00
*** angdraug has joined #openstack-meeting-alt20:00
*** alevine has quit IRC20:01
*** balajiiyer has joined #openstack-meeting-alt20:02
*** amitgandhinz has quit IRC20:03
*** bharathm has quit IRC20:04
*** merooney has quit IRC20:04
*** dane has quit IRC20:05
*** MarkAtwood has quit IRC20:06
*** neilus has joined #openstack-meeting-alt20:07
*** mp1 has joined #openstack-meeting-alt20:11
*** IlyaG has quit IRC20:11
*** dane has joined #openstack-meeting-alt20:12
*** markmcclain has quit IRC20:12
*** ihrachys has quit IRC20:12
*** neilus has quit IRC20:12
*** markmcclain has joined #openstack-meeting-alt20:12
*** mspreitz has quit IRC20:13
*** mfedosin has quit IRC20:18
*** mhickey has joined #openstack-meeting-alt20:19
*** mrmartin has quit IRC20:20
*** sgotliv_ has joined #openstack-meeting-alt20:23
*** aginwala has joined #openstack-meeting-alt20:23
*** sdake has joined #openstack-meeting-alt20:24
*** dslevin has quit IRC20:25
*** sdake has quit IRC20:28
*** Sukhdev has joined #openstack-meeting-alt20:29
*** NazcaLines has quit IRC20:29
*** dane has quit IRC20:31
*** merooney has joined #openstack-meeting-alt20:31
*** cbouch has quit IRC20:32
*** mp1 has left #openstack-meeting-alt20:34
*** bharathm has joined #openstack-meeting-alt20:36
*** dane has joined #openstack-meeting-alt20:38
*** aginwala has quit IRC20:41
*** shwetaap has quit IRC20:42
*** fzdarsky has quit IRC20:42
*** markmcclain has quit IRC20:50
*** cloudrancher has joined #openstack-meeting-alt20:51
*** amotoki has joined #openstack-meeting-alt20:52
*** markmcclain has joined #openstack-meeting-alt20:52
*** diazjf has quit IRC20:56
*** hichihara has joined #openstack-meeting-alt20:56
*** aginwala has joined #openstack-meeting-alt20:57
*** leong has joined #openstack-meeting-alt20:58
*** Ning has joined #openstack-meeting-alt20:58
*** Ning has quit IRC20:58
*** pchadwick has joined #openstack-meeting-alt20:58
*** shamail has joined #openstack-meeting-alt20:59
*** annilai has joined #openstack-meeting-alt20:59
*** njohnston has joined #openstack-meeting-alt20:59
leonghi folks21:00
shamail#startmeeting product working group21:00
*** piet has joined #openstack-meeting-alt21:00
openstackMeeting started Mon Jan 11 21:00:23 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
leongo/21:00
shamailHi leong!21:00
*** dpk_ has joined #openstack-meeting-alt21:00
shamailHi everyone!21:00
dpk_Hello21:00
shamailRoll-call, who's here today?21:00
leongo/21:00
annilaiHappy new year !21:00
annilaianni21:00
dpk_Deepak21:01
shamailHappy New Year everyone21:01
dpk_Happy New Year21:01
shamailPretty light attendance, should we wait a few minutes?21:01
annilaiok21:01
dpk_y21:01
leongok21:01
dpk_yes21:01
pchadwicko/21:01
cloudranchero/21:01
sgordono/21:01
thingeeo/21:01
shamailHi Pete, Jay, Steve, and Mike.21:01
pieto/21:02
pchadwickHappy New Year21:02
shamailHi Piet21:02
pietHowdy!21:02
shamailOkay, let's get started... seems like we have a decent sized group21:02
shamailToday's Agenda21:02
shamail#link https://wiki.openstack.org/wiki/Meetings/product-team21:02
*** amitgandhinz has joined #openstack-meeting-alt21:02
shamail#Topic User Story Updates21:02
*** openstack changes topic to "User Story Updates (Meeting topic: product working group)"21:02
shamailKenny will not be able to join today but he emailed a brief update on "rolling upgrades"21:03
shamailRolling Upgrades - Gaps Analysis continues to be under review with next action for Kenny to submit a new Patch with suggestions.21:03
shamailhttps://review.openstack.org/#/c/255633/21:03
*** Ning has joined #openstack-meeting-alt21:03
*** MeganR has joined #openstack-meeting-alt21:03
*** korzen has quit IRC21:03
shamailSeems like there has been a good discussion on this user story and Kenny will be submitting a new patchset21:03
shamailPlease review it and add comments if you haven't done so already...21:04
leongin addition to the Gap Analysis: trying to understand what has/has-not been implemented on each project (nova, neutron, etc)21:04
shamailThanks leong, do we already have a planned approach to that?21:04
annilaiI've sent Shamail a user story too but haven't uploaded21:04
leongyes...21:04
annilaiit's re. maintains EOL'ed releases21:04
shamailThanks annilai, I just saw the email.21:05
annilaiwe need to get more operators' input21:05
shamailleong, I guess I was asking if there is a timeline or CPL requirement>21:05
shamailsorry for being vague21:05
annilaiand distro vendor's input.21:05
leongoh. CPL.Not yet.21:05
shamailGot it!21:05
shamailMoving on to onboarding legacy infra... any updates cloudrancher?21:06
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:06
cloudrancherOnboarding for management team met Friday. I have an patch to drop for the user story to drop today or tomorrow.21:06
cloudrancherWe've had discussions on the three blueprint drafts in the google drive. https://drive.google.com/drive/u/0/folders/0B0gXxpcL9MhGMy1tOU5ZbEFjRVU21:06
Arkady_Kanevskyhello product team21:06
cloudrancherso once the patch has been done and approved, we should be able to more out of draft21:06
* shamail waves21:06
cloudranchermove out of draft21:06
shamailThanks cloudrancher, please submit the repo when you think it's ready.21:07
cloudrancherthats it for now21:07
shamailleong, any updates on onboarding legacy apps?21:07
leongnope.. need to catch up on that..21:07
shamailNP, thanks.21:07
*** pchadwick has left #openstack-meeting-alt21:07
leongwill talk to Gerg for that use case21:08
*** pchadwick has joined #openstack-meeting-alt21:08
*** diazjf has joined #openstack-meeting-alt21:08
shamailsgordon, how's Complex instance going?21:08
sgordoni got back from vacation 1am today21:08
Arkady_Kanevskyany new bluepints or user stories to review?21:08
sgordonso not great ;)21:08
shamail:-)21:08
shamailAll good.. will you be submitting the second one from the telco-wg soon as well?21:09
sgordonyes21:09
Arkady_Kanevskysteve put me on review list21:09
shamailThat's good news.21:09
leongFYI, I'm in discussion with an Enterprise company about "HA VM" use case.21:09
leongwill probably submit that into draft folder this month21:10
*** scohen1 has joined #openstack-meeting-alt21:10
shamailArkady_Kanevsky, we are reviewing the prioritized user stories... there will be some new ones coming (from annilai and sgordon)... you'll see an email or can check repo.21:10
pchadwickleong: That would be good to see21:10
Arkady_KanevskyIS this HA for VM or HA for application?21:10
shamail+1, thanks leong!21:10
leongHA for VM21:10
leongseems like multiple vendor has different approach.. but i'm trying to understand from the actual customer viewpoint21:11
Arkady_Kanevsky+121:11
shamailThat will be a good perspective to have... any env details (hypervisor type, etc.) would be good to know if they can share.21:11
annilaiThat's great Leong!21:11
*** ihrachys has joined #openstack-meeting-alt21:11
shamailI'll go ahead and speak on lifecycle management...21:11
*** stephenwalli has joined #openstack-meeting-alt21:11
shamailno progress on this user story but I know there is some interest (and prototypes) at IBM.  I am trying to find the right people to engage to see if someone can formally participate.21:12
shamailWill keep everyone updated...21:12
shamailSome pre-work is still needed for this story too since it was originally supposed to combine 2-3 different user stories discussed at the last mid-cycle21:13
*** merooney has quit IRC21:13
*** hichihara has quit IRC21:13
shamailThe quota and capacity management user story still has noone from PWG working on it21:13
shamailThat one might need to be discussed (and maybe re-prioritized) at our mid-cycle21:14
shamailAny other questions/discussions on user stories?21:14
shamailmoving on...21:14
sgordoncap management leong and i had been working out how to (re)split at one point21:14
sgordoni think i had a draft submission for part of it21:14
shamailyeah, I recall that sgordon21:14
sgordonbased on leong's write up21:14
leongprobably need more time/resources for cap mgmt.21:15
shamailsubmitted or in a google doc?21:15
sgordonhttps://review.openstack.org/#/c/253228/21:15
shamailthanks!21:15
shamail#link https://review.openstack.org/#/c/253228/21:15
sgordonit was an etherpad but i had reworked it into the above21:15
sgordonthis does not cover absolutely everything that was in the original capacity management doc from the midcycle tho21:15
shamailAwesome21:15
shamailI missed this, will review later this week.21:16
leong+121:16
shamailthanks sgordon21:16
rockygoops.  Sorry I'm late....21:16
shamail#topic OpenStack Summit in Austin - Call For Speakers21:16
*** openstack changes topic to "OpenStack Summit in Austin - Call For Speakers (Meeting topic: product working group)"21:16
shamailnp rockyg, welcome21:16
shamailThe deadline for submissions is 2/121:16
stephenwalliSorry. I’m late as well.21:16
Arkady_Kanevskydo we have etherpad for ideas for submittion?21:17
shamailWe wanted to discuss if there are any topics that we want to submit as a working group21:17
shamailhi stephenwalli21:17
shamailWe can create one... do you want to take the action item?21:17
shamailThe roadmap session will be submitted again this time...21:17
shamaillast time, we had 2-3 submissions21:17
*** aginwala has quit IRC21:17
Arkady_Kanevskysure21:18
shamailDoes anyone have any ideas that we should build an abstract for and identify presenters?21:18
pchadwickAre these presentations or feedback sessions?21:18
Arkady_Kanevskycreated new etherped and will take AIs there21:18
Arkady_Kanevskyhttps://etherpad.openstack.org/p/austin_summit_product_wg21:18
leong+1. create a etherpad to for the team track/propose topic for submission.21:18
shamailpchadwick: these are presentations... feedback sessions will most likely be in the ops-summit track and we could even propose a BoF21:18
pietI know the OpenStack UX project is planning to propose a session for the personas.  We're hoping someone PWG will present with us if accepted.21:19
pchadwickshamail - thanks21:19
shamail#action Arkady_Kanevsky will create etherpad for discussing call for speakers21:19
*** sigmavirus24_awa is now known as sigmavirus2421:19
shamailThanks piet21:19
Arkady_Kanevskydone21:19
*** annilai_ has joined #openstack-meeting-alt21:19
shamailpiet, is the abstract available anywhere so that potential interested parties can discuss with you?21:19
shamailPlease add it to the etherpad that Arkady_Kanevsky will send out to the mailing list.21:20
pietYep - one sec21:20
*** jprovazn has quit IRC21:20
shamailI'm trying to also figure out how working sessions will be scheduled this time around at the summit..21:20
Arkady_KanevskyState of cross releases epochs that we started at Mitaka - proposal21:21
shamailFor Austin, working group sessions (and BoFs) will also be submitted through the CFS (Call for Speakers) process21:21
pietHere is a list of proposals.  A bit chaotic, but were hoping to submit a few.  https://etherpad.openstack.org/p/mitaka-openstackux-summitpresentations21:21
shamailThat's a good one Arkady_Kanevsky...21:21
shamailthanks piet21:21
pietnp21:21
shamail#link https://etherpad.openstack.org/p/mitaka-openstackux-summitpresentations21:21
shamailLast time we were able to ask for a specific time for the working session (we chose to make it closer to the conclusion of the summit)21:22
pietLondon UX Mid-Cycle planning is here: https://etherpad.openstack.org/p/mitaka-openstackux-mid-cycle21:22
shamailI'm not sure if scheduling preferences are still being honored this time but I can ask.21:22
shamail#link https://etherpad.openstack.org/p/mitaka-openstackux-mid-cycle21:23
shamailAlright, so let's move on... we can continue discussion in the pending etherpad21:23
shamail#topic Sample Tracker walk-through21:23
*** openstack changes topic to "Sample Tracker walk-through (Meeting topic: product working group)"21:23
shamail#link https://review.openstack.org/#/c/265998/21:23
rockygI'd like to see a session on how vendors/users can get involved in the review and especially the gap analysis phases of user stories.21:23
shamailThe rolling upgrade user story is at a point where they need gaps analysis and a tracker21:23
Arkady_KanevskyDo we want to have a BOF on big tent and openstack releases?21:24
rockygIf we can get their input, it would be easier to get to a point where we create RFEs, specs, bps, etc.21:24
shamailI submitted this sample tracker as an example21:24
Arkady_KanevskyThere is a lot of confusion on when/where we will have multuple releases at the same time. Say one for enterprise, one for NFV, one for public lcoud...21:24
shamailArkady_Kanevsky: please add it to the etherpad21:24
shamailCan we keep this discussion for 'opens'?21:25
*** e0ne has quit IRC21:25
shamailThe sample tracker has fields to track the overall user story implementation21:26
shamailthe cross-project spec21:26
shamailand requirements for individual projects21:26
shamailthe idea is to eventually build a front-end that can display this data21:26
Arkady_KanevskyShamail not sure how. I think you just open https://etherpad.openstack.org/p/austin_summit_product_wg and it assigne you color to make changes21:26
shamailthingee, would like to have your feedback on whether there are items that we are missin21:26
shamailmissing*21:26
Arkady_Kanevskyi SEE 2 other people on etherpad alerady21:26
rockygQuestion:  any Open Source tool we could use for that?  Easier for folks to read, maybe? ;-)21:26
shamailrockyg, if you find one... please share it.  The idea behind the data being in JSON was to make building a front-end simpler21:27
rockygArkady_Kanevsky, exactly right21:27
shamailHopefully, we wont be reading the JSON directly21:27
pchadwickNot exactly human friendly ;)21:28
shamailArkady_Kanevsky, just go to https://etherpad.openstack.org and enter a new name for the new etherpad21:28
shamailpchadwick, agreed.. the intention was to make it machine friendly. :)21:28
*** dslev has joined #openstack-meeting-alt21:28
rockygshamail, already there:21:28
rockyg[11:03] *** now talking in #openstack-meeting-alt21:28
rockyg[11:03] *** topic is OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings21:28
rockyg[11:03] *** set by openstack!~openstack@openstack/openstack on Mon Jan 11 09:19:47 201621:28
rockyg[11:03] *** channel #openstack-meeting-alt mode is +cnt21:28
rockyg[11:03] *** channel created at Mon Dec 03 15:22:17 201221:28
rockyg[11:03] *** shwetaap quit (Read error: Connection reset by peer)21:28
rockyg[11:04] *** nelsnels_ quit (Read error: Connection reset by peer)21:28
rockyg[11:04] *** nelsnelson (~nelsnelso@cpe-66-68-190-65.austin.res.rr.com) joined21:28
rockyg[11:04] *** s3wong (~s3wong@50-0-126-163.dedicated.static.sonic.net) joined21:28
rockygsorry.  Dang cut and paste grrrr!21:29
shamailIf for some reason the front-end gets delayed for too long then we can revisit making a human-readable format21:29
shamailnp rockyg21:29
leongLet's get the JSON first, then we can work on the Front-end later on21:29
shamail+121:29
rockygaustin_summit_product_wg21:29
Arkady_Kanevskycreated new one https://etherpad.openstack.org/p/oepnstack_product_wg_austin_summit <shamail>21:29
Arkady_Kanevskywhat do you want there?21:29
shamail#action ALL - please review the tracker file and provide feedback.21:30
shamail#link https://etherpad.openstack.org/p/oepnstack_product_wg_austin_summit21:30
*** iNeilus has joined #openstack-meeting-alt21:30
leongArkady_Kanevsky: there is a typo in the link21:30
shamailArkady_Kanevsky, maybe just a heading that says the purpose (e.g. "Austin Call For Speaker Product WG Proposals"21:30
shamailA related question to the tracker... how do we want to handle the gaps analysis?21:31
Arkady_Kanevskydone21:31
shamailShould we just update the user stories (gap) section?21:31
rockygshamail,  check #link https://etherpad.openstack.org/p/austin_summit_product_wg  stuff already there...21:31
shamailor should that be a seperate file that is co-located with the tracker?21:31
shamail#link https://etherpad.openstack.org/p/austin_summit_product_wg21:31
shamailThoughts on how gaps analysis should be stored?21:32
shamailMy thought would be to update the existing user story since it has a section... but that can make the story a lot larger depending on how verbose the gaps analysis is...21:32
leongThough we can use the "Gap" section.. but have a concern if the analysis go too big to include within paragraphs21:32
shamailleong, same here21:32
rockygrequirements matrix/capabilities matrix with holes highlighted21:33
cloudrancherThe gaps seems to be an implementation concept, not a requirement concept21:33
shamailas a standalone artifact rockyg?21:33
cloudrancherso, somehow the user story might not be the best place for things as the understanding gets better21:34
pchadwickIsn't "filling a gap" a requirement  by definition21:34
shamailTrue cloudrancher... and yes, pchadwick, it is. :)21:34
*** iNeilus has quit IRC21:34
cloudrancherwell I think if we look at gaps as functional gaps, then the requirements is a good place21:34
pchadwickSo, user story > gaps > specs/bp21:35
shamailTo be honest, our group will most likely identify the gap as a requirement21:35
Arkady_Kanevskywhat about user story functionality with which peojects are inlvoved/impacted and status.21:35
shamailthe implementaion is up to the project teams to decide21:35
cloudrancherbut I am concerned that gaps will become an implementation story - as in Nova needs xxx21:35
cloudrancherNeed to think on this a bit21:35
Arkady_KanevskyWe cna create a spreadsheet with summry column at the end. rows for dunctionality21:35
pchadwickcloudrancher - fair enough21:35
shamailWe are not the best people for deciding the implementation21:35
rockyglinked to user stories.  a req. matrix generated from user story that then has capabilities mapped.  so req down, cap across or vice versa.21:35
cloudrancherthe challenge is how to keep requirement gaps seperate from project management gaps21:36
pchadwickmy engineers tell me that product mangers are never the best people for deciding implementation ;)21:36
leongwondering if we need to restructure the directory: user stories -> rolling upgrades -> story.rst21:36
rockygArkady_Kanevsky, ++ I thinkwe are converging.21:36
Arkady_Kanevskyhow does that maps to projects?21:36
leonguser stories -> rolling upgrades -> gaps -> gap1.rst gap2.rst etc/21:36
shamailrockyg, that makes sense.. I am leaning towards a seperate doc as well (only because some gaps analysis might be very large)21:36
cloudrancher+121:37
pchadwickWe can discuss that with the PTLs and get them to own21:37
shamailthat's a good idea leong21:37
pchadwick+121:37
annilai_+121:37
shamail+121:37
rockyg121:37
rockyg+21:37
cloudrancherdoes CPLs have a gaps concept?21:37
leongso instead of putting rolling_upgrade.rst, we put user-stories/rolling-upgrade/....21:37
shamail#action re-organize repo so that each user story is a folder with relevant RST files.21:37
leong+121:37
rockyg++21:37
cloudranchersounds right21:38
annilai_+21:38
Arkady_Kanevskyuser stories for rows, cloumns for projects. If text in cells is not green than means that there is a gap that this project is working on. Best to have blueprint or spec or code under review pointers in cell21:38
shamailwould we still want draft, proposed, etc?21:38
*** EricGonczer_ has quit IRC21:38
*** dprince has quit IRC21:38
leongyes.. i think we still need21:38
cloudrancherbut we need a proposal to review21:38
*** dpk_ has quit IRC21:38
shamailor does that become an empty file (or even a field in the user story)?21:38
Ningagree21:38
shamailActually, the folders make sense21:38
leongdraft and proposed probably can still kept in existing single file.. but when come into tracked, then need subdir21:38
shamailsince we can decide which stories are posted to our specs page by path21:39
*** macsz has joined #openstack-meeting-alt21:39
shamail+1 leong21:39
Arkady_Kanevskyhard to acess if they are not all on one page.21:39
leongbut need to make clear to the team (probably explain in README)21:39
rockygWe need the stories as the top level.  Requirements emerge from them, then the capabilities needs from the requirements21:39
shamailDo you want to submit the patch and also start discussion on ML leong or should I?21:39
cloudrancherif we use seperate file for gaps I would recommend we remove from user story21:39
Arkady_Kanevskyclicking thru directories and subdirectories for status is too much21:39
leongshamail: let's discuss offfline one that Action Item21:40
cloudrancherok21:40
shamailYou won't need to do that Arkady_Kanevsky... the user story contains the "what"... as does gaps analysis.. the status will be tracked via tracker.21:40
shamailsounds good leong21:40
Ning+21:40
leongI can submit a patch to restructure the Tracked/Rolling-Upgrade first21:40
rockygArkady_Kanevsky, if we use the simple name to url link convention, the cell is small, but will take you to the web doc21:40
shamailperfect21:40
leongshamail: put the AR to me21:41
shamail+1 rockyg21:41
*** ihrachys has quit IRC21:41
shamail#action leong will submit patch to break out the rolling-upgrade user story based on these discussions.21:41
*** ihrachys has joined #openstack-meeting-alt21:42
leong+121:42
*** kzaitsev_mb has quit IRC21:42
shamailok, next topic!21:42
rockygI've got an example of use case -> requrements -> functionality I can point folks to.21:42
*** aginwala has joined #openstack-meeting-alt21:42
Arkady_Kanevsky+ rocky21:42
shamail#topic Product WG CPL Updates Planning21:42
*** openstack changes topic to "Product WG CPL Updates Planning (Meeting topic: product working group)"21:42
rockygStarted it for Refstack.21:42
shamailrockyg, please do...21:42
rockygI'll send to ml21:42
shamailthx!21:43
shamailThis next topic is about CPLs21:43
rockygyup.21:43
*** njohnston has quit IRC21:43
*** vgridnev has quit IRC21:43
shamailWe have had some project coverage for a while and I wanted to propose a standing topic in our team meeting to have 1 or 2 CPLs provide an update on the projects they are covering21:43
Arkady_Kanevsky+121:44
shamailThis will give the team an idea of current hot topics, discussions, and plans on a per project basis21:44
rockygkewl!  +121:44
pchadwick+121:44
annilai_+121:44
shamailCurrently, we are not creating a feedback loop via CPLs21:44
shamailWe also do not have full coverage of projects21:45
leong+121:45
shamail#link https://wiki.openstack.org/wiki/CrossProjectLiaisons#Product_Working_Group21:45
leongstarting from "core" then move on with the rest?21:45
cloudrancherpwd21:46
shamailIf you can dedicate a small amount of time to participate in a weekly meeting for a project and act as a conduit between PWG and that project, please help by volunteering21:46
*** cknight has quit IRC21:46
shamailYes, leong... that would be the proposed schedule... I will create an etherpad and put dates next to each project so the CPL knows when they will be presenting the topic at our meeting21:46
leong+121:46
shamailThe etherpad will also allow people to swap time slots21:46
Ning+21:47
Arkady_Kanevskycan we put which CPL to present on agenda?21:47
*** stephenwalli has quit IRC21:47
shamailYes, the etherpad will be the master schedule but each agenda will also include the CPL for the upcoming meeting.21:47
Arkady_Kanevsky+121:48
pchadwickworks for me21:48
MeganR+1, great idea21:48
*** Sukhdev has quit IRC21:48
shamail#action shamail will create etherpad with "CPL updates" schedule and send link to ML21:48
shamailI will also propose a topic for the mid-cycle to revisit CPL coverage (to ensure we have coverage for user stories related projects)21:49
leong+121:49
Arkady_Kanevskygood idea21:49
shamailSegue!!!21:49
rockygAlso, if you could add stable release project to the list?  I plan on being ath the 2100 utc meetings, but could use coverage on the 1400 utc meetings (alternate every other week)21:49
shamail#topic Product WG Mid-Cycle Planning21:49
*** openstack changes topic to "Product WG Mid-Cycle Planning (Meeting topic: product working group)"21:49
shamailrockyg: +121:50
shamailPlease add it to the CPL page and add yourself as one of the CPLs21:50
rockygwill do21:50
shamailA few people had asked about logistics so Kenny (with help from Phil) put together an etherpad for those that are planning to attend the upcoming mid-cycle in the UK.21:51
shamail#link https://etherpad.openstack.org/p/PWG-LON16-MidCycle21:51
pchadwickThis is very useful - thanks.21:51
*** diazjf has quit IRC21:51
leongseems like day 1 and day 2 are in different location21:51
shamailPlease add your name to this etherpad once you are confirmed for attendance so that Rackspace can plan accordingly21:51
leong?21:51
*** sigmavirus24 is now known as sigmavirus24_awa21:51
*** ndipanov has quit IRC21:51
pchadwickMadhus is dinner21:52
shamailThanks pchadwick21:52
leongsorry..my fault...the second location is for the dinner !21:52
leongThanks  pchadwick21:52
*** fredyx10 has quit IRC21:52
Arkady_Kanevskyrocky is not coming to anni is?21:53
*** IlyaG has joined #openstack-meeting-alt21:53
*** lkoranda has quit IRC21:53
*** persia has quit IRC21:53
*** dstanek has quit IRC21:53
shamailIf you are planning on attending the mid-cycle and plan on attending the ops-summit as well, please make sure to purchase a ticket for the ops-summit.21:53
shamail#link https://www.eventbrite.com/e/european-openstack-operators-meetup-tickets-1940585543621:53
*** lkoranda has joined #openstack-meeting-alt21:53
*** persia has joined #openstack-meeting-alt21:53
*** dstanek has joined #openstack-meeting-alt21:53
leongThanks shamail.. i nearly forgot that... :-)21:53
shamailNP :)21:54
rockygBoth, I think...21:54
shamailThe current proposed items for the agenda can be found in this etherpad:21:54
shamail#link https://etherpad.openstack.org/p/PWG_Mitaka_Midcycle21:54
rockygI'll be there.  Gotta edit the etherpad, but bought my ops ticket already21:54
pietMe too21:55
shamailKeep proposing items!21:55
shamailthingee, will you be able to join us for the mid-cycle?21:55
pietAny advice on getting added to the User Summit schedule would be appreciated21:55
leongTime: 5 mins left21:55
*** ihrachys has quit IRC21:55
shamailI'll confirm with Mike via email21:56
Arkady_KanevskyAre yiu going to have phone bridge os kype session going for mid-cycle meeting?21:56
shamailpiet: speak with Tom Fifield21:56
Arkady_KanevskyFor remote folks to attend21:56
thingeeshamail: do we a confirmed date?21:56
pietReal quick: please start distributing the link to the persona validation survey https://www.surveymonkey.com/r/2C27W3C21:56
shamailthingee, yess.. please see https://etherpad.openstack.org/p/PWG-LON16-MidCycle for details21:56
*** ihrachys has joined #openstack-meeting-alt21:56
rockygand add proposed session to the etherpad, piet21:56
pietk21:57
shamailwill do piet21:57
shamailArkady_Kanevsky, we will try to setup a remote participation tool....21:57
shamailit's always tough but we'll keep trying!21:57
pietDoes someone have a link to the operator summit etherpad?21:57
Arkady_Kanevskythank you21:57
shamailyw21:57
shamail#link https://etherpad.openstack.org/p/MAN-ops-meetup21:58
*** Sukhdev has joined #openstack-meeting-alt21:58
shamail#link https://etherpad.openstack.org/p/european-ops-meetup-planning21:58
shamailthere are two etherpads, not sure if one superceded the other or whether both are still current.21:58
shamail#topic opens21:59
*** openstack changes topic to "opens (Meeting topic: product working group)"21:59
pietCan't emphasize enough...all PMs should be distributing the survey link: https://www.surveymonkey.com/r/2C27W3C21:59
thingeeshamail: I don't see anything preventing me on my calendar21:59
shamailThanks thingee, I believe Heidi Joy will be attending as well so you might be able to coordinate with her.21:59
*** jtomasek has quit IRC21:59
Arkady_Kanevskysow the survey. DO you know when we will have results?22:00
shamailAlright, well, Happy 2016!!!22:00
Arkady_KanevskyHappy 201622:00
shamailGreat meeting to start the new year.22:00
leongGreat meeting!22:00
annilai_+22:00
shamail#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Mon Jan 11 22:00:28 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-11-21.00.html22:00
pchadwick+122:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-01-11-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-01-11-21.00.log.html22:00
*** Arkady_Kanevsky has quit IRC22:00
rockygthanks all!22:00
*** MeganR has quit IRC22:00
pietI hope to present something by mid-Feb, but depends on sample size22:00
shamailttyl22:01
*** shamail has left #openstack-meeting-alt22:01
*** leong has quit IRC22:01
pietcheers22:01
*** pchadwick has left #openstack-meeting-alt22:01
*** dizquierdo has quit IRC22:01
*** Ning has quit IRC22:02
*** MarkAtwood has joined #openstack-meeting-alt22:04
*** scohen1 has quit IRC22:05
-openstackstatus- NOTICE: Gerrit is restarting to resolve java memory issues22:05
*** davidlenwell has quit IRC22:05
*** woodster_ has joined #openstack-meeting-alt22:06
*** rockyg has left #openstack-meeting-alt22:07
*** merooney has joined #openstack-meeting-alt22:07
*** salv-orlando has joined #openstack-meeting-alt22:09
*** merooney has quit IRC22:10
*** salv-orl_ has quit IRC22:12
*** ozamiatin_ has joined #openstack-meeting-alt22:13
*** spzala has quit IRC22:14
*** diazjf has joined #openstack-meeting-alt22:14
*** kzaitsev_mb has joined #openstack-meeting-alt22:14
*** spzala has joined #openstack-meeting-alt22:14
*** kebray has quit IRC22:18
*** spzala has quit IRC22:19
*** EricGonczer_ has joined #openstack-meeting-alt22:21
*** rossella_s has quit IRC22:22
*** rossella_s has joined #openstack-meeting-alt22:22
*** fredyx10 has joined #openstack-meeting-alt22:24
*** flaviof has quit IRC22:24
*** neilus has joined #openstack-meeting-alt22:24
*** aginwala has quit IRC22:25
*** ihrachys has quit IRC22:26
*** ihrachys has joined #openstack-meeting-alt22:28
*** aginwala has joined #openstack-meeting-alt22:28
*** neilus has quit IRC22:28
*** davidlenwell has joined #openstack-meeting-alt22:29
*** markmcclain has quit IRC22:29
*** thomnico has quit IRC22:29
*** sgotliv_ has quit IRC22:31
*** stanchan has joined #openstack-meeting-alt22:32
*** ihrachys has quit IRC22:32
*** diazjf has quit IRC22:32
*** jmckind has joined #openstack-meeting-alt22:33
*** mhickey has quit IRC22:33
*** sigmavirus24_awa is now known as sigmavirus2422:34
*** kebray has joined #openstack-meeting-alt22:34
*** julim has quit IRC22:37
*** spzala has joined #openstack-meeting-alt22:37
*** piet has quit IRC22:37
*** neelashah has quit IRC22:37
*** balajiiyer has quit IRC22:39
*** markmcclain has joined #openstack-meeting-alt22:41
*** amitgandhinz has quit IRC22:45
*** edtubill has quit IRC22:48
*** flaviof has joined #openstack-meeting-alt22:50
*** harshs has joined #openstack-meeting-alt22:50
*** mixos has quit IRC22:54
*** kfarr has quit IRC22:56
*** dane has quit IRC23:00
*** dslev has quit IRC23:00
*** dave-mcc_ has quit IRC23:00
*** rvyalov_ has quit IRC23:02
*** jmckind has quit IRC23:02
*** fredyx10 has quit IRC23:06
*** fredyx10 has joined #openstack-meeting-alt23:06
*** banix has quit IRC23:08
*** tellesnobrega is now known as tellesnobrega_af23:16
*** dimtruck is now known as zz_dimtruck23:16
*** miqui has quit IRC23:17
*** tellesnobrega_af is now known as tellesnobrega23:17
*** cloudrancher has quit IRC23:19
*** kebray has quit IRC23:20
*** annilai_ has quit IRC23:21
*** dizquierdo has joined #openstack-meeting-alt23:22
*** amotoki has quit IRC23:25
*** macsz1 has joined #openstack-meeting-alt23:26
*** markmcclain has quit IRC23:26
*** markmcclain has joined #openstack-meeting-alt23:26
*** IlyaG has quit IRC23:26
*** AlanClark has quit IRC23:26
*** spotz is now known as spotz_zzz23:26
*** kei_yama has joined #openstack-meeting-alt23:27
*** IlyaG has joined #openstack-meeting-alt23:27
*** sigmavirus24 is now known as sigmavirus24_awa23:28
*** rsyed is now known as rsyed_away23:28
*** macsz has quit IRC23:28
*** spzala has quit IRC23:30
*** spzala has joined #openstack-meeting-alt23:31
*** aginwala has quit IRC23:31
*** spzala has quit IRC23:32
*** xyang1 has quit IRC23:32
*** spzala has joined #openstack-meeting-alt23:32
*** rsyed_away is now known as rsyed23:34
*** aginwala has joined #openstack-meeting-alt23:35
*** spzala has quit IRC23:37
*** Sukhdev has quit IRC23:37
*** resker has quit IRC23:38
*** Sukhdev has joined #openstack-meeting-alt23:40
*** fredyx10 has quit IRC23:43
*** weshay has quit IRC23:43
*** zhhuabj has quit IRC23:47
*** jecarey has quit IRC23:49
*** hyamauchi has quit IRC23:50
*** macsz1 has quit IRC23:51
*** zz_dimtruck is now known as dimtruck23:51

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