Monday, 2015-12-14

*** hyakuhei has joined #openstack-meeting-alt00:00
*** rmoe_ has joined #openstack-meeting-alt00:00
*** rmoe has quit IRC00:01
*** hyakuhei has quit IRC00:01
*** davideagnello has joined #openstack-meeting-alt00:01
*** hyakuhei has joined #openstack-meeting-alt00:03
*** rmoe_ has quit IRC00:05
*** rmoe has joined #openstack-meeting-alt00:06
*** davideagnello has quit IRC00:06
*** salv-orlando has joined #openstack-meeting-alt00:08
*** markvoelker_ has quit IRC00:10
*** kebray has quit IRC00:11
*** kebray has joined #openstack-meeting-alt00:12
*** rmoe has quit IRC00:12
*** rmoe has joined #openstack-meeting-alt00:13
*** cknight has quit IRC00:14
*** vilobhmm11 has quit IRC00:15
*** hyakuhei has quit IRC00:15
*** sdake has joined #openstack-meeting-alt00:27
*** salv-orl_ has joined #openstack-meeting-alt00:53
*** salv-orlando has quit IRC00:55
*** zhangjn has joined #openstack-meeting-alt00:58
*** iNeilus has quit IRC00:58
*** neilus has joined #openstack-meeting-alt01:00
*** salv-orl_ has quit IRC01:02
*** balajiiyer has quit IRC01:02
*** dave-mccowan has joined #openstack-meeting-alt01:07
*** hoangcx has joined #openstack-meeting-alt01:10
*** davideagnello has joined #openstack-meeting-alt01:10
*** markvoelker has joined #openstack-meeting-alt01:10
*** davideagnello has quit IRC01:14
*** markvoelker has quit IRC01:15
*** hoangcx has left #openstack-meeting-alt01:15
*** annp has joined #openstack-meeting-alt01:19
*** mixos has joined #openstack-meeting-alt01:28
*** zhurong has joined #openstack-meeting-alt01:46
*** Jet has joined #openstack-meeting-alt01:51
*** tfukushima has joined #openstack-meeting-alt02:04
*** zhangjn has quit IRC02:06
*** salv-orlando has joined #openstack-meeting-alt02:07
*** salv-orlando has quit IRC02:11
*** zhangjn has joined #openstack-meeting-alt02:13
*** davideagnello has joined #openstack-meeting-alt02:18
*** davideagnello has quit IRC02:22
*** neilus has quit IRC02:25
*** neilus has joined #openstack-meeting-alt02:25
*** neilus has quit IRC02:25
*** Sukhdev has joined #openstack-meeting-alt02:31
*** neilus has joined #openstack-meeting-alt02:35
*** baoli has joined #openstack-meeting-alt02:37
*** houming has joined #openstack-meeting-alt02:38
*** neilus has quit IRC02:44
*** houming has quit IRC02:44
*** merooney has quit IRC02:45
*** zz_dimtruck is now known as dimtruck02:49
*** houming has joined #openstack-meeting-alt02:50
*** merooney has joined #openstack-meeting-alt02:50
*** kebray has quit IRC02:54
*** davideagnello has joined #openstack-meeting-alt02:59
*** baoli has quit IRC03:00
*** dimtruck is now known as zz_dimtruck03:00
*** gcb has joined #openstack-meeting-alt03:02
*** davideagnello has quit IRC03:04
*** kebray has joined #openstack-meeting-alt03:08
*** salv-orlando has joined #openstack-meeting-alt03:09
*** kebray has quit IRC03:10
*** kebray has joined #openstack-meeting-alt03:11
*** markvoelker has joined #openstack-meeting-alt03:11
*** salv-orlando has quit IRC03:14
*** markvoelker has quit IRC03:16
*** wanghua has joined #openstack-meeting-alt03:18
*** baoli has joined #openstack-meeting-alt03:18
*** cknight has joined #openstack-meeting-alt03:18
*** shwetaap has joined #openstack-meeting-alt03:22
*** neilus has joined #openstack-meeting-alt03:31
*** MarkAtwood has quit IRC03:33
*** zz_dimtruck is now known as dimtruck03:35
*** neilus has quit IRC03:37
*** merooney has quit IRC03:38
*** Liuqing has joined #openstack-meeting-alt03:39
*** Sukhdev has quit IRC03:47
*** yamamoto has joined #openstack-meeting-alt03:55
*** zhangjn has quit IRC03:56
*** dave-mccowan has quit IRC03:57
*** houming has quit IRC04:05
*** gcb has quit IRC04:06
*** davideagnello has joined #openstack-meeting-alt04:07
*** sdake_ has joined #openstack-meeting-alt04:08
*** sdake has quit IRC04:08
*** vilobhmm11 has joined #openstack-meeting-alt04:09
*** houming has joined #openstack-meeting-alt04:10
*** vilobhmm111 has joined #openstack-meeting-alt04:11
*** davideagnello has quit IRC04:11
*** vilobhmm11 has quit IRC04:13
*** MarkAtwood has joined #openstack-meeting-alt04:14
*** sdake_ has quit IRC04:15
*** baoli has quit IRC04:18
*** gcb has joined #openstack-meeting-alt04:18
*** kebray has quit IRC04:18
*** aginwala has joined #openstack-meeting-alt04:19
*** dims has joined #openstack-meeting-alt04:20
*** kebray has joined #openstack-meeting-alt04:21
*** houming has quit IRC04:25
*** gcb has quit IRC04:26
*** houming has joined #openstack-meeting-alt04:27
*** fawadkhaliq has joined #openstack-meeting-alt04:29
*** zhangjn has joined #openstack-meeting-alt04:35
*** Sukhdev has joined #openstack-meeting-alt04:36
*** gcb has joined #openstack-meeting-alt04:39
*** tfukushima has quit IRC04:43
*** MarkAtwood has quit IRC04:44
*** neilus has joined #openstack-meeting-alt04:46
*** MarkAtwood has joined #openstack-meeting-alt04:49
*** ig0r_ has quit IRC04:50
*** neilus has quit IRC04:51
*** Poornima has joined #openstack-meeting-alt04:54
*** ig0r_ has joined #openstack-meeting-alt04:55
*** markvoelker has joined #openstack-meeting-alt05:12
*** davideagnello has joined #openstack-meeting-alt05:15
*** markvoelker has quit IRC05:17
*** baoli has joined #openstack-meeting-alt05:19
*** zhangjn has quit IRC05:19
*** davideagnello has quit IRC05:20
*** sylwesterB has joined #openstack-meeting-alt05:20
*** tfukushima has joined #openstack-meeting-alt05:21
*** zhangjn has joined #openstack-meeting-alt05:21
*** aginwala has quit IRC05:26
*** chandankumar has joined #openstack-meeting-alt05:31
*** MarkAtwood has quit IRC05:32
*** jrist has quit IRC05:36
*** zhurong has quit IRC05:37
*** Liuqing has quit IRC05:37
*** jrist has joined #openstack-meeting-alt05:38
*** jrist has quit IRC05:38
*** jrist has joined #openstack-meeting-alt05:38
*** cknight has quit IRC05:40
*** mrmartin has joined #openstack-meeting-alt05:44
*** zhhuabj has quit IRC05:44
*** shwetaap has quit IRC05:45
*** shwetaap has joined #openstack-meeting-alt05:46
*** dingboopt has joined #openstack-meeting-alt05:47
*** gcb has quit IRC05:48
*** Liuqing has joined #openstack-meeting-alt05:49
*** dims has quit IRC05:53
*** dimtruck is now known as zz_dimtruck05:55
*** mixos has quit IRC05:56
*** zhhuabj has joined #openstack-meeting-alt05:57
*** sgotliv__ has joined #openstack-meeting-alt05:59
*** zhangjn has quit IRC05:59
*** zhangjn has joined #openstack-meeting-alt06:01
*** gcb has joined #openstack-meeting-alt06:05
*** Jet has left #openstack-meeting-alt06:07
*** vahidh has joined #openstack-meeting-alt06:09
*** Jet has joined #openstack-meeting-alt06:09
*** Jet has joined #openstack-meeting-alt06:12
*** ig0r_ has quit IRC06:12
*** IlyaG has joined #openstack-meeting-alt06:12
*** SridharG has joined #openstack-meeting-alt06:13
*** IlyaG has quit IRC06:14
*** numans has joined #openstack-meeting-alt06:15
*** neilus has joined #openstack-meeting-alt06:15
*** gcb has quit IRC06:15
*** mrmartin has quit IRC06:15
*** neilus has quit IRC06:20
*** gcb has joined #openstack-meeting-alt06:28
*** _nadya_ has joined #openstack-meeting-alt06:30
*** amotoki has joined #openstack-meeting-alt06:31
*** vahidh has quit IRC06:34
*** davideagnello has joined #openstack-meeting-alt06:37
*** red_trela| has joined #openstack-meeting-alt06:37
*** red_trela| has quit IRC06:37
*** salv-orlando has joined #openstack-meeting-alt06:39
*** zhangjn has quit IRC06:41
*** zhangjn has joined #openstack-meeting-alt06:41
*** davideagnello has quit IRC06:42
*** salv-orlando has quit IRC06:43
*** chandankumar_ has joined #openstack-meeting-alt06:47
*** chandankumar has quit IRC06:49
*** zhangjn has quit IRC06:49
*** MarkAtwood has joined #openstack-meeting-alt06:49
*** zhurong has joined #openstack-meeting-alt06:55
*** zhangjn has joined #openstack-meeting-alt06:57
*** zhangjn has quit IRC06:57
*** zhangjn has joined #openstack-meeting-alt06:58
*** rcernin has joined #openstack-meeting-alt07:01
*** zhangjn has quit IRC07:03
*** zhangjn has joined #openstack-meeting-alt07:04
*** irenab has quit IRC07:04
*** chandankumar_ has quit IRC07:05
*** openstackstatus has joined #openstack-meeting-alt07:06
*** ChanServ sets mode: +v openstackstatus07:06
*** vilobhmm111 has quit IRC07:06
*** boris-42_ has joined #openstack-meeting-alt07:09
*** salv-orlando has joined #openstack-meeting-alt07:11
*** miqui has quit IRC07:13
*** markvoelker has joined #openstack-meeting-alt07:13
*** paul-carlton2 has joined #openstack-meeting-alt07:13
*** davideagnello has joined #openstack-meeting-alt07:17
*** markvoelker has quit IRC07:17
*** bana_k has joined #openstack-meeting-alt07:18
*** chandankumar has joined #openstack-meeting-alt07:20
*** shwetaap has quit IRC07:22
*** shwetaap has joined #openstack-meeting-alt07:22
*** davideagnello has quit IRC07:23
*** sgotliv__ has quit IRC07:24
*** irenab has joined #openstack-meeting-alt07:30
*** kebray has quit IRC07:35
*** paul-carlton2 has quit IRC07:36
*** dims has joined #openstack-meeting-alt07:39
*** scheuran has joined #openstack-meeting-alt07:39
*** paul-carlton2 has joined #openstack-meeting-alt07:39
*** georgelorch has quit IRC07:41
*** tfukushima has quit IRC07:43
*** tfukushima has joined #openstack-meeting-alt07:44
*** fzdarsky_ has joined #openstack-meeting-alt07:46
*** sdake has joined #openstack-meeting-alt07:48
*** georgelorch has joined #openstack-meeting-alt07:49
*** MarkAtwood has quit IRC07:55
*** ihrachys has joined #openstack-meeting-alt07:56
*** nkrinner has joined #openstack-meeting-alt07:58
*** davideagnello has joined #openstack-meeting-alt07:59
*** jprovazn has joined #openstack-meeting-alt08:00
*** pnavarro has joined #openstack-meeting-alt08:01
*** ihrachys has quit IRC08:02
*** davideagnello has quit IRC08:03
*** _nadya_ has quit IRC08:06
*** pnavarro has quit IRC08:07
*** MarkAtwood has joined #openstack-meeting-alt08:09
*** salv-orlando has quit IRC08:12
*** paul-carlton2 has quit IRC08:12
*** dingboopt has quit IRC08:15
*** paul-carlton2 has joined #openstack-meeting-alt08:26
*** sdake has quit IRC08:30
*** fawadkhaliq has quit IRC08:30
*** fawadkhaliq has joined #openstack-meeting-alt08:31
*** fawadkhaliq has quit IRC08:31
*** fawadkhaliq has joined #openstack-meeting-alt08:32
*** safchain has joined #openstack-meeting-alt08:32
*** matrohon has joined #openstack-meeting-alt08:37
*** MarkAtwood has quit IRC08:37
*** Sukhdev has quit IRC08:39
*** sdake has joined #openstack-meeting-alt08:41
*** iyamahat has joined #openstack-meeting-alt08:48
*** sdake has quit IRC08:49
*** fawadkhaliq has quit IRC08:49
*** fawadkhaliq has joined #openstack-meeting-alt08:49
*** eranra has joined #openstack-meeting-alt08:50
*** iyamahat has quit IRC08:54
*** sdake has joined #openstack-meeting-alt08:54
*** paul-carlton2 has quit IRC08:55
*** houming has quit IRC08:59
*** houming has joined #openstack-meeting-alt08:59
*** bana_k has quit IRC09:00
*** gcb has quit IRC09:00
*** zhangjn has quit IRC09:00
*** zhangjn has joined #openstack-meeting-alt09:03
*** davideagnello has joined #openstack-meeting-alt09:07
*** zeih has joined #openstack-meeting-alt09:08
*** fzdarsky_ has quit IRC09:10
*** davideagnello has quit IRC09:12
*** gcb has joined #openstack-meeting-alt09:12
*** thomnico has joined #openstack-meeting-alt09:13
*** fzdarsky has joined #openstack-meeting-alt09:13
*** markvoelker has joined #openstack-meeting-alt09:14
*** jaypipes has joined #openstack-meeting-alt09:15
*** chandankumar has quit IRC09:16
*** rm_you has joined #openstack-meeting-alt09:17
*** houming has quit IRC09:17
*** rvyalov_ has joined #openstack-meeting-alt09:17
*** houming has joined #openstack-meeting-alt09:18
*** markvoelker has quit IRC09:18
*** mrmartin has joined #openstack-meeting-alt09:19
*** mrmartin has quit IRC09:20
*** neiljerram has joined #openstack-meeting-alt09:22
*** chandankumar has joined #openstack-meeting-alt09:25
*** ikutukov has joined #openstack-meeting-alt09:25
*** jrist has quit IRC09:26
*** paul-carlton2 has joined #openstack-meeting-alt09:27
*** jrist has joined #openstack-meeting-alt09:30
*** jrist has quit IRC09:30
*** jrist has joined #openstack-meeting-alt09:30
*** amotoki has quit IRC09:31
*** yamahata has quit IRC09:32
*** vgridnev has joined #openstack-meeting-alt09:38
*** ig0r_ has joined #openstack-meeting-alt09:38
*** paul-carlton2 has quit IRC09:46
*** jrist has quit IRC09:46
*** jrist has joined #openstack-meeting-alt09:47
*** salv-orlando has joined #openstack-meeting-alt09:47
*** sgotliv has joined #openstack-meeting-alt09:47
*** davideagnello has joined #openstack-meeting-alt09:48
*** hyakuhei has joined #openstack-meeting-alt09:49
*** akiskourtis has quit IRC09:49
*** hyakuhei has quit IRC09:51
*** davideagnello has quit IRC09:52
*** bharathm has quit IRC09:53
*** bharathm has joined #openstack-meeting-alt09:54
*** dizquierdo has joined #openstack-meeting-alt09:54
*** zhurong has quit IRC09:55
*** vgridnev has quit IRC09:55
*** zhangjn has quit IRC09:56
*** SridharG has left #openstack-meeting-alt09:56
*** vgridnev has joined #openstack-meeting-alt09:56
*** Liuqing has quit IRC09:57
*** jrist has quit IRC09:57
*** ikutukov has quit IRC09:57
*** _nadya_ has joined #openstack-meeting-alt09:58
*** jrist has joined #openstack-meeting-alt09:59
*** jrist has quit IRC09:59
*** jrist has joined #openstack-meeting-alt09:59
*** MarkAtwood has joined #openstack-meeting-alt10:00
*** zhangjn has joined #openstack-meeting-alt10:01
*** zhangjn has quit IRC10:01
*** zhangjn has joined #openstack-meeting-alt10:03
*** MarkAtwood has quit IRC10:05
*** fawadkhaliq has quit IRC10:05
*** ganso has joined #openstack-meeting-alt10:05
*** jtomasek has joined #openstack-meeting-alt10:06
*** ndipanov has joined #openstack-meeting-alt10:07
*** bharathm has quit IRC10:10
*** houming has quit IRC10:16
*** neiljerram has quit IRC10:17
*** zeih has quit IRC10:23
*** fawadkhaliq has joined #openstack-meeting-alt10:25
*** _nadya_ has quit IRC10:25
*** rcernin has quit IRC10:25
*** romcheg has left #openstack-meeting-alt10:28
*** davideagnello has joined #openstack-meeting-alt10:28
*** jaypipes has quit IRC10:29
*** chandankumar has quit IRC10:31
*** pleia2 has quit IRC10:32
*** jaypipes has joined #openstack-meeting-alt10:32
*** davideagnello has quit IRC10:33
*** neiljerram has joined #openstack-meeting-alt10:36
*** _degorenko|afk is now known as degorenko10:37
*** shwetaap has quit IRC10:40
*** chandankumar has joined #openstack-meeting-alt10:44
*** dizquierdo has quit IRC10:44
*** jaypipes has quit IRC10:46
*** omartsyniuk has joined #openstack-meeting-alt10:47
*** paul-carlton2 has joined #openstack-meeting-alt10:54
*** sdake has quit IRC10:56
*** mrmartin has joined #openstack-meeting-alt10:58
*** sbog has quit IRC11:00
*** dburmistrov has quit IRC11:00
*** nurla has quit IRC11:00
*** vkramskikh_ has quit IRC11:00
*** mrmartin has quit IRC11:03
*** e0ne has joined #openstack-meeting-alt11:05
*** zhangjn has quit IRC11:07
*** kei_yama has quit IRC11:09
*** akiskourtis has joined #openstack-meeting-alt11:12
*** dims has quit IRC11:13
*** zhangjn has joined #openstack-meeting-alt11:13
*** markvoelker has joined #openstack-meeting-alt11:15
*** tfukushima has quit IRC11:15
*** SridharG has joined #openstack-meeting-alt11:16
*** zhangjn has quit IRC11:18
*** markvoelker has quit IRC11:20
*** chandankumar has quit IRC11:20
*** chandankumar_ has joined #openstack-meeting-alt11:20
*** davideagnello has joined #openstack-meeting-alt11:23
*** davideagnello has quit IRC11:28
*** dburmistrov has joined #openstack-meeting-alt11:31
*** tellesnobrega is now known as tellesnobrega_af11:40
*** nurla has joined #openstack-meeting-alt11:41
*** _nadya_ has joined #openstack-meeting-alt11:43
*** dizquierdo has joined #openstack-meeting-alt11:45
*** derekh has joined #openstack-meeting-alt11:47
*** MarkAtwood has joined #openstack-meeting-alt11:48
*** vgridnev has quit IRC11:49
*** annp has quit IRC11:51
*** houming has joined #openstack-meeting-alt11:51
*** MarkAtwood has quit IRC11:53
*** slagle has quit IRC11:53
*** slagle has joined #openstack-meeting-alt11:54
*** tellesnobrega_af is now known as tellesnobrega11:57
*** chandankumar_ has quit IRC11:59
*** zeih has joined #openstack-meeting-alt12:01
*** baoli has quit IRC12:03
*** davideagnello has joined #openstack-meeting-alt12:03
*** davideagnello has quit IRC12:08
*** igordcard has joined #openstack-meeting-alt12:09
*** Akis_ has joined #openstack-meeting-alt12:19
*** shwetaap has joined #openstack-meeting-alt12:21
*** akiskourtis has quit IRC12:22
*** ihrachys has joined #openstack-meeting-alt12:31
*** vgridnev has joined #openstack-meeting-alt12:34
*** Poornima has quit IRC12:36
*** ihrachys has quit IRC12:37
*** ihrachys has joined #openstack-meeting-alt12:37
*** dprince has joined #openstack-meeting-alt12:38
*** vgridnev_ has joined #openstack-meeting-alt12:39
*** vgridnev has quit IRC12:39
*** ddmitriev has joined #openstack-meeting-alt12:40
*** barclaac has quit IRC12:43
*** houming has quit IRC12:43
*** zhangjn has joined #openstack-meeting-alt12:45
*** markvoelker has joined #openstack-meeting-alt12:45
*** igordcard_ has joined #openstack-meeting-alt12:46
*** weshay_xchat has joined #openstack-meeting-alt12:48
*** weshay_xchat is now known as weshay12:48
*** dims has joined #openstack-meeting-alt12:48
*** shwetaap has quit IRC12:48
*** shwetaap has joined #openstack-meeting-alt12:49
*** barclaac has joined #openstack-meeting-alt12:49
*** markvoelker has quit IRC12:49
*** chandankumar has joined #openstack-meeting-alt12:50
*** ihrachys has quit IRC12:50
*** vgridnev_ has quit IRC12:50
*** ihrachys has joined #openstack-meeting-alt12:51
*** chandankumar has quit IRC12:51
*** chandankumar has joined #openstack-meeting-alt12:51
*** salv-orl_ has joined #openstack-meeting-alt12:54
*** dave-mccowan has joined #openstack-meeting-alt12:54
*** vgridnev_ has joined #openstack-meeting-alt12:54
*** baoli has joined #openstack-meeting-alt12:55
*** salv-orlando has quit IRC12:56
*** houming has joined #openstack-meeting-alt12:57
*** fzdarsky_ has joined #openstack-meeting-alt12:57
*** davideagnello has joined #openstack-meeting-alt12:58
*** jaypipes has joined #openstack-meeting-alt13:00
*** fzdarsky has quit IRC13:00
*** davideagnello has quit IRC13:03
*** jdob has joined #openstack-meeting-alt13:03
*** ihrachys has quit IRC13:04
*** regebro is now known as Guest9342313:05
*** ihrachys has joined #openstack-meeting-alt13:05
*** salv-orl_ has quit IRC13:05
*** regebro has joined #openstack-meeting-alt13:05
*** vgridnev_ has quit IRC13:05
*** vgridnev has joined #openstack-meeting-alt13:05
*** zhangjn has quit IRC13:06
*** bharathm has joined #openstack-meeting-alt13:11
*** Akis__ has joined #openstack-meeting-alt13:14
*** Akis_ has quit IRC13:14
*** bharathm has quit IRC13:15
*** neilus has joined #openstack-meeting-alt13:17
*** chandankumar has quit IRC13:21
*** davideagnello has joined #openstack-meeting-alt13:26
*** banix has joined #openstack-meeting-alt13:27
*** davideagnello has quit IRC13:31
*** flaviof has joined #openstack-meeting-alt13:31
*** MarkAtwood has joined #openstack-meeting-alt13:37
*** chandankumar has joined #openstack-meeting-alt13:38
*** elmiko_ is now known as elmiko13:39
*** igordcard__ has joined #openstack-meeting-alt13:40
*** zhangjn has joined #openstack-meeting-alt13:41
*** jaypipes has quit IRC13:41
*** MarkAtwood has quit IRC13:41
*** julim has joined #openstack-meeting-alt13:42
*** igordcard has quit IRC13:42
*** paul-carlton2 has quit IRC13:43
*** zhangjn has quit IRC13:44
*** zhangjn has joined #openstack-meeting-alt13:45
*** mwagner_lap has quit IRC13:49
*** ihrachys has quit IRC13:50
*** chandankumar has quit IRC13:50
*** gcb has quit IRC13:51
*** akiskourtis has joined #openstack-meeting-alt13:52
*** banix has quit IRC13:53
*** Akis__ has quit IRC13:54
*** neilus has quit IRC13:54
*** _gryf has joined #openstack-meeting-alt13:55
*** ihrachys has joined #openstack-meeting-alt13:55
*** dslevin_ has joined #openstack-meeting-alt13:55
*** paul-carlton2 has joined #openstack-meeting-alt13:56
*** neilus has joined #openstack-meeting-alt13:57
*** kzaitsev_mb has joined #openstack-meeting-alt13:59
n0ano#startmeeting nova-scheduler14:00
openstackMeeting started Mon Dec 14 14:00:15 2015 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova-scheduler)"14:00
openstackThe meeting name has been set to 'nova_scheduler'14:00
n0anoAnyone here to talk about the scheduler?14:00
*** tellesnobrega is now known as tellesnobrega_af14:00
edleafe\o14:00
_gryfhi14:01
bauzas\o14:01
* carl_baldwin lurks14:01
n0anocarl_baldwin, _gryf welcome to some new names14:02
*** zhangjn has quit IRC14:02
*** neilus has quit IRC14:02
* n0ano notes that lurkers are welcome although they could get assigned tasks :-)14:02
_gryfoh my :)14:02
edleafen0ano doesn't mess around14:03
n0anolet's get started14:03
n0ano#topic specs & BPs14:03
*** openstack changes topic to "specs & BPs (Meeting topic: nova-scheduler)"14:03
bauzasso...14:04
bauzasMusic and mythology, Einstein and astrology14:04
bauzasIt all started with the big bang!14:04
n0anoI think we're in relatively good shape on BPs, jay's resource providers is the only open one and he's asked for an exception on it, hopefully that will be OK14:04
bauzasby that ^, I meant that jaypipes began to split resource-providers14:04
n0anobauzas, tnx for the explaination, you lost me completely for a minute :-)14:04
n0anoyeah, I think he'll get it14:05
n0anodoes anyone else have any BPs they are concerned about?14:05
*** amrith is now known as _amrith_14:05
*** zhangjn has joined #openstack-meeting-alt14:05
bauzasn0ano: tribute to The Big Bang Theory TV show14:06
n0anoonly, let's go to a different topic (I meant to add this to the agenda and got confused at midnight)14:06
n0ano#topic patches14:06
*** openstack changes topic to "patches (Meeting topic: nova-scheduler)"14:06
*** cdent has joined #openstack-meeting-alt14:06
cdento/14:06
bauzasthings are going pacefully for the req-spec BP14:06
n0anoare there any patches people have concerns about that we need to discuss14:06
n0anobauzas, yeah, now it's time to worry about implementations14:07
bauzasI have some soft-affinity patches for ServerGroups that I'm reviewing closely because they depend from the spec-obj BP14:07
*** igordcard has joined #openstack-meeting-alt14:07
*** igordcard__ has quit IRC14:08
n0anobauzas, do you need help with reviews or is that going OK for now?14:08
cdentI'm trying to spin up my review frequency, but I'm still a bit too ignorant to be really good.14:08
*** markus_z has joined #openstack-meeting-alt14:08
n0anocdent, not to worry, we learn by doing here so don't be intimidated14:09
*** zimboboyd has quit IRC14:09
* cdent promises to flail wildly14:09
*** zeih has quit IRC14:09
n0anocdent, WFM :-)14:10
bauzasn0ano: well, reviews are always good :)14:10
bauzascdent: so you had other stuff for us to review ?14:10
bauzasin terms of doc ?14:10
cdentbauzas: not written yet.14:11
bauzascdent: ack, no worries, take your time14:11
*** dims has quit IRC14:11
*** numans has quit IRC14:11
n0anoOK, not hearing any problems with patches (that'll probably change with time) let's move on14:11
n0ano#topic bugs14:11
*** openstack changes topic to "bugs (Meeting topic: nova-scheduler)"14:11
n0anoI actually have some good news here14:12
*** Jet has left #openstack-meeting-alt14:12
*** dingboopt has joined #openstack-meeting-alt14:12
*** neilus has joined #openstack-meeting-alt14:12
n0anowe have a team in San Antonio that is looking into bugs and I've started the process to get them to look at scheduler bugs14:12
n0anowe should be getting some activity on this issue soon14:12
* markus_z jumps with joy14:13
n0anowon't solve them all but I'm hoping to make a big dent in the list14:13
edleafen0ano: being in SA, I can be a contact with no TZ issues14:13
bauzasn0ano: okay, provided they don't all jump on saying "eh, the scheduler is racy !"14:14
*** zhurong has joined #openstack-meeting-alt14:14
markus_zn0ano: FWIW, I wrote down what I know about the process at http://markuszoeller.github.io/posts/openstack-bugs/14:14
n0anomarkus_z, excellent, I'll make sure that gets forwarded on14:14
n0anobauzas, hopefully we'll spread the effort around, races are not the only issue14:15
bauzasn0ano: I could even troll by saying that the scheduler isn't racy, but that's maybe a bit harsh :D14:15
markus_z#info: 5 scheduler related bugs open at https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler&field.status%3Alist=NEW14:16
bauzaswell, it's not that the scheduler isn't racy, it's rather that *it is by design* :D14:16
n0anobauzas, I just saw the email about this today and haven't had a chance to read it yet, we can maybe discuss that at the next meeting14:16
*** neilus has quit IRC14:16
bauzasthat's a very long story, not sure we can be that interested14:17
bauzas:)14:17
cdentbauzas: at some point I'd like to hear that history14:18
bauzascdent: take 3 shots of coffee first :)14:18
*** eranra_ has joined #openstack-meeting-alt14:18
*** migi has joined #openstack-meeting-alt14:18
n0anoOK, hope to see progress on bugs but let's move on14:18
n0ano#topic opens14:18
*** openstack changes topic to "opens (Meeting topic: nova-scheduler)"14:18
edleafecdent: I'm not sure you do. :)14:19
n0anoI have one - future meetings with the holidays14:19
*** dims has joined #openstack-meeting-alt14:19
* cdent loves to know all the goss14:19
bauzasn0ano: cancel with joy ?14:19
cdentcancel++14:19
bauzasbtw. about the midcycle14:19
*** ajmiller has joined #openstack-meeting-alt14:19
cdentbauzas: 3 shots? that's well under par14:20
bauzasdo we know who can't attend it, and who would like to still voice ?14:20
n0anobauzas, hold off on that for a second14:20
*** davideagnello has joined #openstack-meeting-alt14:20
n0anocancel seems to be a winner, shall we cancel the next two and start up again on 1/4?14:20
bauzas+214:20
bauzasfor that proposal14:21
edleafe+1 from me14:21
bauzasbut I'm French, so I guess I shouldn't be representative about vacations14:21
*** jaypipes has joined #openstack-meeting-alt14:21
n0anobauzas, it's not summer, you're good :-)14:21
*** eranra has quit IRC14:21
* cdent laughs14:21
*** eranra_ has quit IRC14:22
bauzasn0ano: well, France is still freezed by those dates, so you know...14:22
bauzasthat - and May14:22
cdent+1 on return on the 4th14:22
*** cknight has joined #openstack-meeting-alt14:22
n0anoI've got two +1s and a +2, that means we merge it :-)  Meet again on 1/4/1614:22
*** ikutukov has joined #openstack-meeting-alt14:22
n0anoback to mid-cycle14:23
bauzasn0ano: merge by only +2, horrible !14:23
bauzasby only *one14:23
n0anobauzas, I'm a little loose, what can I say14:23
n0anoback to the mid-cycle14:23
*** neelashah has joined #openstack-meeting-alt14:23
bauzasn0ano: so, just wanted to know who can't attend14:23
n0anoI'ts in Britain so I'm not even sure I'll make it this time, anybody else here know their plans14:23
cdentI'll be there14:24
bauzasedleafe: ?14:24
edleafeNot me14:24
bauzasack14:24
cdentI can report that jay*pipes and timofei will be there14:24
bauzasok14:24
*** zhangjn has quit IRC14:25
n0anocdent, that's good so we'll have mostly a quorum for the scheduler14:25
bauzasn0ano: edleafe: so I don't know if it's planned to be hangouted yet, but I'd propose you to ask for it :)14:25
*** davideagnello has quit IRC14:25
n0anobauzas, yeah, I'll make sure that's at least considered14:25
edleafebauzas: hmmm... it'll start at 3am my time14:26
*** regebro has quit IRC14:26
bauzasoh right14:26
edleafeso save the good stuff for the afternoon :)14:26
bauzasedleafe: I could ask to have the scheduler decisions by the afternoons14:26
n0anoedleafe, +114:26
bauzasedleafe: of course, this is a meetup style, but yeah I guess you got my idea14:26
*** yamamoto has quit IRC14:26
edleafebauzas: that would work14:26
n0anoanything else for today?14:27
bauzaswell, provided I arrive safe in Bristol, given I should drive by lefy14:27
bauzasleft14:27
cdentbauzas: take train!14:27
*** dims has quit IRC14:28
*** ikutukov has quit IRC14:28
n0anobauzas, driving left on the roads is fine, parking lots on the other hand will kill you :-)14:28
*** ikutukov has joined #openstack-meeting-alt14:28
* cdent still struggles with the parking lots14:28
bauzascdent: walking on January in Bristol seems a bad idea :)14:29
n0anoOK, I'm hearing crickets (and idle chatter :-) so let's close14:29
bauzas++14:29
* cdent nods14:29
n0anotnx everyone, have a great holiday and we'll meet again next year on 1/414:29
n0ano#endmeeting14:30
*** openstack changes topic to "Bugs (Meeting topic: neutron_dvr)"14:30
openstackMeeting ended Mon Dec 14 14:30:04 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2015/nova_scheduler.2015-12-14-14.00.html14:30
*** dims has joined #openstack-meeting-alt14:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2015/nova_scheduler.2015-12-14-14.00.txt14:30
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2015/nova_scheduler.2015-12-14-14.00.log.html14:30
*** neelashah1 has joined #openstack-meeting-alt14:30
*** neelashah has quit IRC14:30
*** regebro has joined #openstack-meeting-alt14:31
*** zeih has joined #openstack-meeting-alt14:31
*** neilus has joined #openstack-meeting-alt14:32
*** inteq has quit IRC14:33
*** banix has joined #openstack-meeting-alt14:33
*** merooney has joined #openstack-meeting-alt14:33
*** neilus has quit IRC14:36
*** kencjohnston has joined #openstack-meeting-alt14:37
*** dane has joined #openstack-meeting-alt14:37
*** kencjohnston has quit IRC14:38
*** kencjohnston has joined #openstack-meeting-alt14:38
*** korzen has joined #openstack-meeting-alt14:39
*** zhurong has quit IRC14:40
*** zeih has quit IRC14:41
*** NazcaLines has joined #openstack-meeting-alt14:41
*** markvoelker has joined #openstack-meeting-alt14:43
*** stpierre has joined #openstack-meeting-alt14:45
*** j______ has quit IRC14:46
*** mwagner_lap has joined #openstack-meeting-alt14:46
*** j___ has joined #openstack-meeting-alt14:48
*** kencjohnston has quit IRC14:48
*** zeih has joined #openstack-meeting-alt14:48
*** zeih has quit IRC14:48
*** zeih has joined #openstack-meeting-alt14:48
*** SridharG has quit IRC14:52
*** zhangjn has joined #openstack-meeting-alt14:52
*** kencjohnston has joined #openstack-meeting-alt14:53
*** zhangjn has quit IRC14:53
*** ski1 has joined #openstack-meeting-alt14:53
*** gcb has joined #openstack-meeting-alt14:54
*** egallen has joined #openstack-meeting-alt14:54
*** sylwesterB has joined #openstack-meeting-alt14:55
*** salv-orlando has joined #openstack-meeting-alt14:55
*** shwetaap has quit IRC14:55
*** ajmiller has quit IRC14:56
*** mhickey has joined #openstack-meeting-alt14:58
*** jprovazn has quit IRC14:59
ihrachyshi all for the upgrades meeting. we'll start in a minute.15:00
*** akamyshnikova has joined #openstack-meeting-alt15:00
korzenhi15:00
mhickeyHi15:00
akamyshnikovahi!15:01
*** cdent has left #openstack-meeting-alt15:01
ajoo/15:01
* ajo creeps15:01
ihrachysajo: I will ping you if/when you are needed15:01
ihrachysok...15:01
ihrachys#startmeeting neutron_upgrades15:01
openstackMeeting started Mon Dec 14 15:01:45 2015 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:01
*** MarkAtwood has joined #openstack-meeting-alt15:02
ihrachyshi all. I read the meeting notes from the previous week, seems like it was a quiet meeting ;) thanks sc68cal for handling it anyway.15:02
ihrachysthere are no announcements from my side. let's go straight to the matter.15:03
*** dklenov has joined #openstack-meeting-alt15:03
ihrachys#topic Organisational matters15:03
*** openstack changes topic to "Organisational matters (Meeting topic: neutron_upgrades)"15:03
*** balajiiyer has joined #openstack-meeting-alt15:03
*** sriram has joined #openstack-meeting-alt15:03
*** rossella_s has joined #openstack-meeting-alt15:03
ihrachysone thing I wanted to ask you folks is whether we need a separate Launchpad tag for upgrade related issues. I think it could be useful once we get more stuff to care.15:03
rossella_slet's wait then till we see the real need for it15:04
rossella_s(sorry for being late)15:04
ihrachysthat's reasonable. then let's wait. :)15:04
*** ig0r_ has quit IRC15:04
* ihrachys waves at rossella_s 15:04
mhickeyagree15:04
akamyshnikovaagreed15:05
*** irenab has quit IRC15:05
ihrachysok next thing is15:05
ihrachys#topic Partial Multinode Grenade15:05
*** openstack changes topic to "Partial Multinode Grenade (Meeting topic: neutron_upgrades)"15:05
ihrachyssc68cal: korzen: dare to update what's the job state and where we can help?15:05
*** sigmavirus24_awa is now known as sigmavirus2415:05
*** AndroUser has joined #openstack-meeting-alt15:05
*** eggmaster has joined #openstack-meeting-alt15:05
*** _amrith_ is now known as amrith15:06
korzenI was not able to handle the grenade job lately15:06
ihrachyskorzen: pointers where to start for those who could have time to help?15:06
korzenbut the latest status is that we've got problem during resource creation phase15:06
*** neilus has joined #openstack-meeting-alt15:07
*** yonglihe has joined #openstack-meeting-alt15:07
korzenyeap, anyone able to help is welcome15:07
korzenthe status is on mailing list15:07
korzenlet me search for it15:07
ihrachyskorzen: it's http://lists.openstack.org/pipermail/openstack-dev/2015-November/079344.html ?15:07
ihrachysand below15:07
*** zhangjn has joined #openstack-meeting-alt15:07
*** amitgandhinz has joined #openstack-meeting-alt15:07
korzenyes, this is the thread15:08
* ihrachys should spare some cycles to look at what we have now15:08
ihrachysI hope we have more eyes glaring this week.15:08
korzenI hoped that sc68cal would take a look last week15:08
ihrachyskorzen: is there a way to trigger new runs? is it 'check experimental'?15:09
ihrachysor 'recheck'?15:09
korzenyes, it is the 'check experimental'15:09
*** neilus has quit IRC15:09
korzenis there a way to get the job stats?15:09
korzenfrom jenkins?15:09
ihrachyskorzen: you mean, the number of failures vs. successes?15:10
korzenyes15:10
ihrachyskorzen: I know little, but I have heard folks use graphite for that: http://graphite.openstack.org15:10
ihrachyskorzen: infra (sdague?) probably should have an answer. I know Sean actively monitors failures for some gate jobs.15:11
korzenihrachys, ok I will ask them15:12
ihrachysok, everyone welcome to look at latest results, and collect them.15:12
ihrachyslet's move on15:12
ihrachys#topic Object implementation15:12
*** openstack changes topic to "Object implementation (Meeting topic: neutron_upgrades)"15:12
ihrachysrossella_s: I believe it's your turn :)15:12
rossella_syay!15:13
*** zz_dimtruck is now known as dimtruck15:13
rossella_sso in case you didn't have a look, there's a WIP https://review.openstack.org/#/c/25364115:13
rossella_sthanks ihrachys for the review15:13
rossella_sI wanted to see if we can use the ObjectField to model extensions15:14
rossella_sit seems to work15:14
ihrachysrossella_s: that's a really good start, even though we need to iterate a bit on it.15:14
rossella_sI didn't want to spend too much time on it, I wanted to receive feedback from people who worked with ovo before15:14
rossella_sihrachys, yes15:14
rossella_smore than a bit15:14
ihrachysrossella_s: :)15:14
rossella_sjust wanted to get some feeback before spending weeks on it :p15:15
korzenI will post a WIP patch on network later this week15:15
korzennetwork OVO15:15
rossella_skorzen, great!15:15
*** yamamoto has joined #openstack-meeting-alt15:15
ihrachysI guess extensions, more test coverage could be the first steps. it would also be great to see whether it would be easy to plug the code into some existing code using dicts to see how it plays there. I think kevinbenton wanted to get it into notification layer, so that could be a good start.15:15
rossella_sso my plan for next week it's to keep working on this patch, adding tests as a first step15:15
*** sylwesterB has quit IRC15:16
korzenthe network OVO has dependency on port, subnet and NetworkRBAC15:16
ihrachyskorzen: I am very glad to hear more good news!15:16
rossella_sagreed ihrachys15:16
rossella_sfirst let's add more tests, then let's try to introduce it in the code15:16
ihrachyskorzen: for rbac, we need to think how we integrate it into objects. AFAIK there is a patch by hdaniel that should come up with some general rbac solution, starting with qos policies.15:17
*** shwetaap has joined #openstack-meeting-alt15:17
ihrachysthat one: https://review.openstack.org/25008115:17
ihrachysso probably worth a look15:17
korzenMy current approach is to have Network OVO with custom JSON fields for port and subnet in it - this is the today's aproach, I'll see how it will work...15:17
rossella_skorzen, please no custom JSON field15:18
*** sylwesterB has joined #openstack-meeting-alt15:18
*** sylwesterB has quit IRC15:18
ihrachysrossella_s: I guess it's temp solution until port object is ready15:18
ihrachysobviously not for merge15:18
*** zimboboyd has joined #openstack-meeting-alt15:18
rossella_sihrachys, ok then, let's put a big TODO there :)15:18
ihrachysa huge one15:18
korzenrossella_s, the problem is that subnet is introducing the 5 more OVO object to implement15:19
rossella_skorzen, then I would say let's start with one of those object and leave network for later15:19
ihrachyskorzen: I am afrain that's something we'll be forced to unravel. :(15:19
*** mtanino has joined #openstack-meeting-alt15:19
ihrachysyeah, I guess starting with leaves is the right approach. it's nevertheless good we started with network because now we should have better understanding of the tree.15:20
*** Leom has joined #openstack-meeting-alt15:20
rossella_syeah15:20
korzenI will try to post some patch with both aproaches15:20
ihrachyskorzen: cool!15:21
korzenI'll see how it woudl work in the end...15:21
korzens/woudl/would15:21
ihrachyson general object stuff side, I was reminded by nova folks we need some validation against unintended object schema changes in the gate. nova has something called object hasher that allows to hash on object schema definitions in the registry, I will need to look into adopting the approach.15:22
rossella_sihrachys, nice15:22
*** eranra has joined #openstack-meeting-alt15:22
ihrachysok, so thanks everyone for working on the objects side, and looking forward for more ;)15:22
ihrachyslet's move on15:22
rossella_s:)15:22
ihrachys#topic Patches on review15:22
*** openstack changes topic to "Patches on review (Meeting topic: neutron_upgrades)"15:22
ihrachysso rossella_s's patch https://review.openstack.org/#/c/253641/ was already discussed.15:23
ihrachysanother upgrades thing was devref update for upgrade strategy for RPC callbacks by ajo: https://review.openstack.org/241154 it's now merged. kudos to ajo!15:23
*** sneti has joined #openstack-meeting-alt15:23
ihrachysajo: when do we expect to start nitpicking on code for the devref?15:23
mhickeywell done ajo; lot of hard PSes! :)15:23
*** iben_ has joined #openstack-meeting-alt15:24
ihrachysok, let's get back to ajo later, seems like he is deep into something right now :)15:24
ihrachysI have one more patch for has_offline_migrations CLI for neutron-db-manage: https://review.openstack.org/248190 but it's still not really ready for merge, so let's not waste time on it15:25
ihrachysany more patches for the team to look at?15:25
korzenI have to drop the meeting, bye all!15:26
ihrachyskorzen: o/15:26
*** banix_ has joined #openstack-meeting-alt15:26
ihrachysok, I guess nothing else to review for now. which is fine, let's move on.15:26
ihrachys#topic Open discussion15:27
*** openstack changes topic to "Open discussion (Meeting topic: neutron_upgrades)"15:27
ihrachysI had one think in the agenda and was hoping to hear from rossella_s and akamyshnikova since you both know a great deal about OVS agent backend side15:27
*** banix has quit IRC15:27
ihrachysspecifically,15:27
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2015-December/081264.html15:27
* rossella_s looking15:27
ihrachysthat's a proposal to introduce some structure into how we manage flows for features15:28
*** eranra_ has joined #openstack-meeting-alt15:28
ihrachysI suspect it may impact rolling upgrades (in terms of data plane disruption), so it would be great to hear what you think.15:28
rossella_sI had read it briefly and was planning to comment on it15:28
rossella_sok, will answer later today15:28
ihrachyssame for overall proposal, since it honestly can make little sense.15:29
*** kfarr has joined #openstack-meeting-alt15:29
ihrachysrossella_s: thanks!15:29
ihrachysakamyshnikova: and thanks in advance your way ;)15:29
*** banix_ is now known as banix15:29
rossella_scool, anything else?15:30
ihrachysone more thing that was raised by mhickey is we probably have little stuff to tackle for those who would like to get more involved.15:30
rossella_sihrachys, we can find something15:30
ihrachysso I was wondering whether folks see where we can spin off some tasks for those who have time?15:30
mhickeyI am willing! :)15:30
*** chandankumar has joined #openstack-meeting-alt15:30
rossella_sI will try to do that, once I get the ovo port in a better shape15:31
* ihrachys now wonders whether the objects hasher thing can be a great candidate for exact that goal15:31
*** korzen has quit IRC15:31
rossella_sihrachys, good point15:31
rossella_smaybe we should have an action for next meeting to fill a list of tasks that can be given to people willing to join15:31
ihrachysmhickey: ok, let's discuss then in neutron channel what's that about and how you can help once you feel less burdened by other stuff you handle.15:32
*** eranra has quit IRC15:32
ihrachysrossella_s: that's a great idea!15:32
*** migi has quit IRC15:32
*** NazcaLines has quit IRC15:32
ihrachys#action ihrachys to start a detailed list of tasks to do for folks with free time15:32
mhickeyihrachys: sure; might be able to get something rolling before the holidays.15:32
ihrachysrossella_s: is it ok to maintain it on wiki? or should it be etherpad?15:32
rossella_sihrachys, I think for now the wiki is ok...I don't expect a long list15:33
*** migi has joined #openstack-meeting-alt15:33
ihrachysrossella_s: ok. thanks for the suggestion.15:33
ski1ihrachys: i have 2 developers dedicated to this effort to attack those details15:33
rossella_sihrachys, thank you actually :)15:33
ihrachysski1: oh that's nice to hear. let's discuss details off the meeting!15:33
ski1ihrachys: sounds good15:34
ihrachysanyone else for the open discussion?15:34
*** _nadya_ has quit IRC15:34
*** _nadya_ has joined #openstack-meeting-alt15:34
ihrachys#action rossella_s to reply on ovs agent flow maintenance email thread15:35
ihrachysok, I guess that's it, we call a day.15:35
rossella_sihrachys, thanks15:35
ihrachysthanks everyone for joining!15:35
ihrachys#endmeeting15:35
*** openstack changes topic to "Bugs (Meeting topic: neutron_dvr)"15:35
openstackMeeting ended Mon Dec 14 15:35:24 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2015/neutron_upgrades.2015-12-14-15.01.html15:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2015/neutron_upgrades.2015-12-14-15.01.txt15:35
mhickeythanks15:35
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2015/neutron_upgrades.2015-12-14-15.01.log.html15:35
mhickeybye15:35
*** _nadya_ has quit IRC15:35
ihrachysski1: please join #openstack-neutron15:35
*** dslevin_ has quit IRC15:36
*** sylwesterB has joined #openstack-meeting-alt15:37
*** superdan is now known as dansmith15:38
*** haypo has joined #openstack-meeting-alt15:39
*** sdake has joined #openstack-meeting-alt15:40
*** pballand has quit IRC15:41
*** eranra_ has quit IRC15:41
*** davideagnello has joined #openstack-meeting-alt15:41
*** hyakuhei has joined #openstack-meeting-alt15:42
*** cbouch has joined #openstack-meeting-alt15:45
*** davideagnello has quit IRC15:47
*** jmckind has joined #openstack-meeting-alt15:48
*** Sukhdev has joined #openstack-meeting-alt15:48
*** dave-mccowan has quit IRC15:48
*** sgotliv has quit IRC15:53
*** Akanksha08 has joined #openstack-meeting-alt15:53
*** sylwesterB has quit IRC15:54
*** vgridnev has quit IRC15:54
*** tonytan4ever has joined #openstack-meeting-alt15:56
*** yamamoto has quit IRC15:56
*** 21WAAGP61 has quit IRC15:57
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:57
*** andreaf_ has joined #openstack-meeting-alt15:57
*** yamamoto has joined #openstack-meeting-alt15:58
*** johnsom has joined #openstack-meeting-alt15:58
*** sneti has quit IRC15:59
dimshi15:59
johnsomMorning15:59
dims#startmeeting oslo15:59
dimscourtesy ping for GheRivero, amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dougwig, e0ne, flaper87, garyk, harlowja, haypo,15:59
openstackMeeting started Mon Dec 14 15:59:42 2015 UTC and is due to finish in 60 minutes.  The chair is dims. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
dimscourtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, ozamiatin, redrobot, rpodolyaka, spamaps15:59
dimscourtesy ping for sergmelikyan, sreshetnyak, sileht, sreshetnyak, stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek, gcb15:59
*** sneti has joined #openstack-meeting-alt15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
*** openstack changes topic to " (Meeting topic: oslo)"15:59
openstackThe meeting name has been set to 'oslo'15:59
lxsliohai15:59
*** kgiusti has joined #openstack-meeting-alt15:59
bknudsonhi15:59
gcbo/15:59
johnsomo/15:59
*** dave-mccowan has joined #openstack-meeting-alt15:59
silehto/16:00
rbradforo/16:00
kgiustio/16:00
haypohello oslo16:00
ozamiatino/16:00
dimsgood morning/afternoon/evening/night - johnsom lxsli bknudson gcb sileht rbradfor kgiusti haypo ozamiatin16:00
haypomaybe we can say hoslo for hello16:00
dimshaha16:00
johnsomha16:00
*** jimbobhickville has joined #openstack-meeting-alt16:01
dims#topic Red flags for/from liaisons16:01
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"16:01
bknudsonnone for keystone16:01
johnsomNone from LBaaS land16:01
*** houming has quit IRC16:01
dimsthe grenade job for kilo->liberty should be green now. had to fix oslo.middleware to put back oslo namespace stuff16:01
dimsthanks bknudson johnsom16:02
*** Prem has joined #openstack-meeting-alt16:02
bogdandohi16:02
dimsbknudson : did any of the other projects adopt the way keystone does tests for deprecated stuff yet?16:02
dimshi bogdando16:02
bknudsondims: I haven't seen anything16:02
*** dave-mcc_ has joined #openstack-meeting-alt16:02
haypoFYI i'm the assigned liaison for nova, but i'm not working on nova anymore16:03
haypomaybe nova needs a new liaison?16:03
dimshaypo : ack, can you please tell Nova PTL?16:03
*** Akanksha08 has quit IRC16:03
*** jecarey has joined #openstack-meeting-alt16:03
haypodims: right, will do16:03
*** zhangjn has quit IRC16:03
dimshaypo : thanks for the heads up16:03
dims#topic Releases for Mitaka16:03
*** openstack changes topic to "Releases for Mitaka (Meeting topic: oslo)"16:03
dimsDoes anyone need releases today? please file reviews in openstack/releases repo.16:03
haypodims: i will need a release of oslo.service for liberty16:04
haypodims: is it possible to get it for next week? the required change is not merged yet :-D16:04
*** amitgandhinz has quit IRC16:04
dimshaypo : y just file a review when ready16:05
dims#topic New Spec Review16:05
*** openstack changes topic to "New Spec Review (Meeting topic: oslo)"16:05
*** HeOS has joined #openstack-meeting-alt16:05
dimsbogdando : can you please introduce this16:05
*** mrmartin has joined #openstack-meeting-alt16:05
dims#link https://review.openstack.org/256342 (Add a spec for a work queue messaging pattern)16:05
dimssileht : around?16:05
haypodims: a review for the releases repo, right? (FYI the fix is https://review.openstack.org/#/c/256443/ a regression in signal handler, a race condition)16:05
bogdandothis spec is logical continuation of numerous openstack-dev ML topics16:06
silehtdims, yes16:06
*** dave-mccowan has quit IRC16:06
dimssileht : bogdando : sounds like a new parallel API to me, right?16:06
*** dukhlov has joined #openstack-meeting-alt16:06
bogdandoit is not clear what and how we already have implemented for worq-queue pattern in Oslo messaging16:06
dimsbogdando : right all we know is that we can't break anyone :)16:07
bogdandoyes, this is supposed to became so. But alternatives assume to figure out and rework the current state16:07
dimssileht : prefer a fresh start here, right?16:07
dimsgiven the troubles we had enforcing the current API16:08
dims(sequence of calls)16:08
bogdandomain points are clearly defined claims and failure modes16:08
bogdandoand hopefully new API docs...16:08
*** jmckind has quit IRC16:09
silehtIt's still unclear for me what we will add to oslo.messaging (I haven't yet read the latest patchset of this afternoon)16:09
*** davideagnello has joined #openstack-meeting-alt16:09
*** thomnico has quit IRC16:09
bogdandoWorkQueue API16:09
bogdandoand I added new alt, "use celery and touch nothing please"16:10
silehtlol16:10
*** timello- has quit IRC16:10
dimshaha16:10
*** EricGonczer_ has joined #openstack-meeting-alt16:10
*** thomnico has joined #openstack-meeting-alt16:10
* dims googles for "work queue api"16:10
dimsok let's continue discussion on the spec itself. thanks bogdando16:11
dims#link https://review.openstack.org/#/c/256431/  (Support RBAC with LDAP in oslo.policy)16:11
dimsis anyone here for this spec?16:11
*** tonytan4ever has quit IRC16:11
dimsbknudson, stevemar : wanted to catch your eye ^^16:11
*** dizquierdo has quit IRC16:12
dimsnot sure how it lines up with the dynamic policy work16:12
bknudsonthere is no dynamic policy work.16:12
bknudsonwhat do you think about putting this in keystone-specs ?16:12
dimsbknudson : deep sixed16:12
*** snackewm has joined #openstack-meeting-alt16:12
dimsbknudson : what happened to the work?16:13
dims"dynamic policy work"?16:13
*** rmoe_ has joined #openstack-meeting-alt16:13
*** rmoe has quit IRC16:13
bknudsondims: dynamic policy was abandoned16:13
*** davideagnello has quit IRC16:13
bknudsonwe don't have any bps in m for dynamic policy.16:13
dimsbknudson : interesting thanks. please leave a note on that review to move to keystone-specs16:14
haypobknudson: what are the "operations" managed in LDAP?16:14
bknudsonhaypo: I don't know what operations means?16:14
haypobknudson: who is responsible to handle these permissions on these operations? oslo.policy or keystone?16:14
stevemardims: bknudson is it really related to dynamic policy?16:14
bknudsonthe work is in oslo.policy.16:14
haypobknudson: https://review.openstack.org/#/c/256431/7/specs/mitaka/ldap-rbac.rst : "Permission is which ROLE can do OPERATION with OBJECT"16:14
bknudsonI don't think oslo.policy should be an oslo project and belongs in keystone16:14
bknudsonthe operation is like "list users" "boot instance"16:15
dimsstevemar : bknudson the source of the information in policy.json picked up "dynamically" from another source?16:15
dimsnot policy.json16:15
stevemardims: gotcha16:15
haypobknudson: i'm replying to "what do you think about putting this in keystone-specs ?"16:15
dimsbknudson : +2A to move it16:16
stevemardims: but like bknudson said, we abandoned it. not enough of a need from operators to have the work done16:16
haypobknudson: you want to move the spec, or the whole oslo.policy, inside keystone? i don't understand :-/16:17
dimsstevemar : so this seems like a light-weight alternative16:17
dimshaypo : let's stick to the spec for now :)16:17
bknudsonhaypo: I want to move the whole oslo.policy to keystone16:17
*** ihrachys has quit IRC16:17
haypobknudson: oh ok. so yes, it makes sense to move the spec16:17
dimsbknudson : do you envision a rename?16:17
stevemardims: i hope not :P16:18
bknudsonI don't think renaming the library is worth it16:18
haypomaybe we need another to move oslo.policy inside keystone? :)16:18
haypoanother spec*16:18
dimsbknudson : +1 to get the ball rolling on a ML thread16:19
dimsthen we can do a governance patch16:19
dimshaypo : don't think we need another spec :)16:19
*** kebray has joined #openstack-meeting-alt16:20
*** kebray has quit IRC16:20
bknudson#action bknudson to send note to -dev list to request move oslo.policy to keystone16:20
*** Akanksha08 has joined #openstack-meeting-alt16:20
dimsk. now that spec is off the table for us :)16:20
dims#topic OpenStack Spec Review16:20
dims#link https://review.openstack.org/#/c/226157/ (Backwards compat for libraries and clients.)16:20
*** openstack changes topic to "OpenStack Spec Review (Meeting topic: oslo)"16:20
*** kebray has joined #openstack-meeting-alt16:20
dimsneed some +1's on ^^ per request from TC16:20
bknudson+1 from me16:21
dimsnet, net. we can't break any active release...all active releases may use newest oslo libs16:21
dimss/release/releases/16:21
bknudsonwe already broke that since we dropped 2.6 support16:21
dimswe have to figure out the test matrices to help us figure out16:21
*** andreaf has quit IRC16:21
*** andreaf_ is now known as andreaf16:21
dimsbknudson : that spec is not in effect yet :)16:21
bknudsonwe should make sure to drop support for stuff before the spec gets merged16:22
*** jtomasek has quit IRC16:22
dimsbknudson : LOL as long you don't break CI jobs16:22
dimsthen folks would spot it :)16:22
*** jmckind has joined #openstack-meeting-alt16:23
dims#topic Open discussion16:23
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"16:23
*** thomnico has quit IRC16:23
lxsliI'd like to discuss https://review.openstack.org/#/c/25312516:23
*** banix has quit IRC16:23
johnsomI will not be at these meetings until the 4th16:23
dimsjohnsom ack thanks for the heads up16:23
amrith./16:24
*** matrohon has quit IRC16:24
lxsliharlowja left a comment, I've requested a couple of times in channel to discuss it but not been able to raise anyone16:24
amrithI'd asked a questions some days agon on the channel, I'd like to ask here16:24
amrithdims was out when I asked ...16:24
amrithabout strutils.mask_password()16:24
*** tonytan4ever has joined #openstack-meeting-alt16:24
amrithdims, ok to ask now?16:24
dimsharlowja : TZ issues i think, will review it16:25
lxslidims: thanks!16:25
*** sbalukoff has quit IRC16:25
dimsamrith : shoot16:25
amriththx16:25
amriththe issue is with mask_password()16:25
*** nkrinner has quit IRC16:25
amrithcurrently it is setup to mask a string16:25
amrithI'd like to extend the same capability to a dictionary16:25
amrithwhere the keys are in the 'list' that mask_password() uses16:25
amriththe list of keys is the same.16:26
amrithand I'm wondering whether I can add it to mask_password()16:26
haypoamrith: accept dict as input type? why not using a dict comprehension for example?16:26
amrithor whether it is not a 'strutils' thing.16:26
amrithyes, I want to mask passwords in a dictionary16:26
haypoamrith: i don't think that it's worth to make the function more complex16:26
amrithsuch as { "password": "u812hhx", ... }16:27
haypoamrith: you should write your own helper in your application16:27
amrithI would like to add mask_dict_password()16:27
amrithand put it in strutils16:27
*** amitgandhinz has joined #openstack-meeting-alt16:27
haypoi prefer to keep oslo.utils simple16:27
amrithone second,  I have a request for a plan (b)16:27
dimsamrith : if we see more projects doing that then may be we can consider it. haypo's point seems valid to me16:28
dimsack16:28
amrithmay I change _SANITIZE_KEYS to SANITIZE_KEYS16:28
amrithmaking it explicit that other modules may use it16:29
amrithand add a comment there.16:29
haypoamrith: dhellmann was opposed to that16:29
amriththen I'll write my helper routine.16:29
amrithhaypo, sorry didn't see dhellmann's reply16:29
amrithapologies16:29
amriththen what do y'all suggest?16:29
haypoamrith: dict((mask_password(key), value) for key, value in dict.iteritems()) doesn't fit your use case?16:29
*** cbouch has quit IRC16:29
haypoamrith: it's just one line, no?16:29
haypo"then what do y'all suggest?" again, develop such helper in your application16:30
*** rossella_s has quit IRC16:30
amrithhaypo, I'm trying to understand how this would work16:30
amrithI'll think about your suggestion (1 line) and get back to you16:30
*** rossella_s has joined #openstack-meeting-alt16:30
*** cbouch has joined #openstack-meeting-alt16:31
amriththx16:31
dimshaypo : guessing you need to mask the value and not the key16:31
amrithdims, good for now16:31
haypoamrith: i'm not sure that i understood your use case16:31
haypodims: ah16:31
amrithdims, yes16:31
haypoin this case, you cannot use mask_password() in its current shape16:31
amrithif the dictionary is as I said earlier  { "password": "u812hhx", ... }16:31
haypoamrith: open a review for that and explain your use case16:31
amrithI want to mask the "u812hhx",16:31
amrithwith "****"16:31
amrithI don't think the 1 line proposed would work16:32
amrithhaypo, that's the use-case16:32
amrith1 line above16:32
amrithgiven a dict like { "password": "u812hhx", ... }16:32
amrithmask the "u812hhx" and replace with "***"16:32
haypoamrith: dhellmann was opposed to allow applications to pass new keys to hide to mask_password()16:32
amrithwhere "password" is any one of the values in _SANITIZE_KEYS16:32
haypoamrith: it's different from getting the list of keys16:32
amrithI don't want to pass new keys to mask_password()16:33
amrithI want to write a helper function that uses _SANITIZE_KEYS16:33
haypoamrith: but maybe it's worth to add a new function16:33
amrithand the leading "_" implies private16:33
amrithI would be fine changing _SANITIZE_KEYS to SANITIZE_KEYS16:33
amrithand importing it in my helper16:33
amrithand implementing the logic for dictionaries16:33
amrithall I want is the change to the variable name16:33
amrithin strutils.py16:33
haypodon't use _SANITIZE_KEYS outside strutils.py16:33
amrithfrom _SANITIZE_KEYS to SANITIZE_KEYS16:34
amrithhaypo, you don't16:34
amrithmy helper function would.16:34
dimsamrith : which review #?16:34
haypoamrith: i changed my mind. propose a change to add a new function to strutils16:34
amrithdims, don't have one yet.16:34
amrithhaypo, I will do that and submit a review16:34
amriththat may make it more concrete16:34
amrithas an example of the intended use-case.16:34
haypoamrith: ok. add me (victor stinner) in the reviewers16:34
dimsk lets start with a new function for dict with a concrete test16:34
amrithhaypo, dims understood.16:34
amriththanks16:35
amrithI will do that16:35
dimsthanks16:35
dimsjohnsom lxsli bknudson gcb sileht rbradfor kgiusti haypo ozamiatin - anything else?16:35
haypolxsli: sorry i'm not a big fan of oslo.config, so i'm not really excited by extended it (so i didn't review your change)16:35
haypodims: nope16:35
kgiustinope16:35
gcbIn last meeting , we talked  how to  clean up  bugs with wrong status, I created an etherpad: https://etherpad.openstack.org/p/oslo_bug_track16:35
bknudsonnothing for me16:35
stpierrei'd like comments on the approach in https://review.openstack.org/#/c/256584/, if anyone can give me some direction. if it looks like the right way to tackle the issue, i've got some paperwork to do before it can be merged16:35
*** AndroUser has quit IRC16:36
lxslihaypo: that's OK, it's harlowja torpedoing it and running away I mind :)16:36
dimsstpierre : ack will add it to review queue16:36
bknudsonwhat's wrong with the current timestamps?16:36
stpierretyvm16:36
dimslxsli : LOL, poor guy, does so much and you are accusing him :)16:37
johnsomNothing here16:37
*** kebray has quit IRC16:37
lxslidims: haha not sharpening my daggers just yet :)16:37
dimsthanks everyone16:37
dimsspecial bye from Kharkiv, talk to you all from Boston next week16:38
*** ttx has quit IRC16:38
*** kgiusti has left #openstack-meeting-alt16:38
dims#endmeeting16:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:38
openstackMeeting ended Mon Dec 14 16:38:42 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2015/oslo.2015-12-14-15.59.html16:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2015/oslo.2015-12-14-15.59.txt16:38
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2015/oslo.2015-12-14-15.59.log.html16:38
*** johnsom has left #openstack-meeting-alt16:38
*** ttx has joined #openstack-meeting-alt16:39
*** stpierre has left #openstack-meeting-alt16:39
*** haypo has left #openstack-meeting-alt16:39
*** dslevin has quit IRC16:39
*** dslevin has joined #openstack-meeting-alt16:40
*** dukhlov has quit IRC16:42
*** jimbobhickville has left #openstack-meeting-alt16:42
*** dslevin has quit IRC16:42
*** dims has quit IRC16:42
*** gcb has quit IRC16:42
*** paul-carlton2 has quit IRC16:43
*** dukhlov has joined #openstack-meeting-alt16:43
*** dslevin has joined #openstack-meeting-alt16:43
*** jaypipes has quit IRC16:44
*** dslevin has quit IRC16:44
*** Swami_ has joined #openstack-meeting-alt16:46
*** armax has joined #openstack-meeting-alt16:47
*** dslevin has joined #openstack-meeting-alt16:48
*** pleia2 has joined #openstack-meeting-alt16:48
*** e0ne has quit IRC16:48
*** davideagnello has joined #openstack-meeting-alt16:49
*** iyamahat has joined #openstack-meeting-alt16:52
*** absubram has joined #openstack-meeting-alt16:52
*** gyee has joined #openstack-meeting-alt16:53
*** hyakuhei has quit IRC16:54
*** kebray has joined #openstack-meeting-alt16:54
*** davideagnello has quit IRC16:54
*** ashleighfarnham has joined #openstack-meeting-alt16:54
*** yamamoto has quit IRC16:59
*** Akanksha08 has quit IRC16:59
*** Akanksha08 has joined #openstack-meeting-alt17:00
*** sputnik13 has quit IRC17:00
*** salv-orlando has quit IRC17:01
*** tellesnobrega_af is now known as tellesnobrega17:02
*** cbouch has quit IRC17:03
*** jmckind_ has joined #openstack-meeting-alt17:04
*** jmckind has quit IRC17:05
*** jmckind has joined #openstack-meeting-alt17:05
*** jmckind_ has quit IRC17:06
*** kzaitsev_mb has quit IRC17:13
*** Akanksha08 has quit IRC17:14
*** ashleighfarnham has quit IRC17:16
*** madhu_ak has joined #openstack-meeting-alt17:17
*** aginwala has joined #openstack-meeting-alt17:18
*** crinkle has joined #openstack-meeting-alt17:18
*** Akanksha08 has joined #openstack-meeting-alt17:18
*** jtomasek has joined #openstack-meeting-alt17:18
*** kzaitsev_mb has joined #openstack-meeting-alt17:19
*** openstackstatus has quit IRC17:20
*** madhu_ak has quit IRC17:22
*** openstackstatus has joined #openstack-meeting-alt17:22
*** ChanServ sets mode: +v openstackstatus17:22
*** vahidh has joined #openstack-meeting-alt17:22
*** HeOS has quit IRC17:22
*** paul-carlton2 has joined #openstack-meeting-alt17:22
*** igordcard has quit IRC17:23
*** scheuran has quit IRC17:23
*** dingboopt has quit IRC17:25
*** sgotliv has joined #openstack-meeting-alt17:25
*** pballand has joined #openstack-meeting-alt17:26
*** rvyalov_ has quit IRC17:26
*** hyakuhei has joined #openstack-meeting-alt17:26
*** mrmartin has quit IRC17:27
*** ijw has joined #openstack-meeting-alt17:27
*** yamamoto has joined #openstack-meeting-alt17:28
*** cbouch has joined #openstack-meeting-alt17:29
*** xyang1 has joined #openstack-meeting-alt17:30
*** chandankumar has quit IRC17:30
*** ashleighfarnham has joined #openstack-meeting-alt17:30
*** balajiiyer has quit IRC17:31
*** jmckind has quit IRC17:31
*** snackewm has quit IRC17:31
*** mrmartin has joined #openstack-meeting-alt17:32
*** sneti_ has joined #openstack-meeting-alt17:33
*** sneti has quit IRC17:34
*** e0ne has joined #openstack-meeting-alt17:34
*** Akanksha08 has quit IRC17:35
*** Akanksha08 has joined #openstack-meeting-alt17:36
*** snackewm has joined #openstack-meeting-alt17:39
*** vishwanathj has quit IRC17:40
*** iyamahat has quit IRC17:40
*** vishwanathj has joined #openstack-meeting-alt17:40
*** tonytan4ever has quit IRC17:40
*** davideagnello has joined #openstack-meeting-alt17:44
*** hyakuhei has quit IRC17:44
*** yamamoto has quit IRC17:46
*** Akanksha08 has quit IRC17:47
*** davideagnello has quit IRC17:49
*** mhickey has quit IRC17:49
*** ashleighfarnham has quit IRC17:50
*** hyakuhei has joined #openstack-meeting-alt17:51
*** ashleighfarnham has joined #openstack-meeting-alt17:53
*** amrith is now known as _amrith_17:56
*** hyakuhei has quit IRC17:58
*** iNeilus has joined #openstack-meeting-alt17:59
*** chandankumar has joined #openstack-meeting-alt18:00
*** _amrith_ is now known as amrith18:00
*** iyamahat has joined #openstack-meeting-alt18:00
*** salv-orlando has joined #openstack-meeting-alt18:02
*** iNeilus has quit IRC18:02
*** iNeilus has joined #openstack-meeting-alt18:02
*** yamahata has joined #openstack-meeting-alt18:02
*** salv-orlando has quit IRC18:03
*** salv-orlando has joined #openstack-meeting-alt18:03
*** derekh has quit IRC18:04
*** zeih has quit IRC18:04
*** zhhuabj has quit IRC18:05
*** sdake has quit IRC18:06
*** sputnik13 has joined #openstack-meeting-alt18:06
*** Aish has joined #openstack-meeting-alt18:07
*** sdake has joined #openstack-meeting-alt18:12
*** markus_z has quit IRC18:12
*** ashleighfarnham has quit IRC18:13
*** HeOS has joined #openstack-meeting-alt18:14
*** aginwala has quit IRC18:20
*** Aish has quit IRC18:20
*** aginwala has joined #openstack-meeting-alt18:20
*** zhhuabj has joined #openstack-meeting-alt18:21
*** vilobhmm11 has joined #openstack-meeting-alt18:22
*** amrith is now known as _amrith_18:22
*** dave-mcc_ has quit IRC18:23
*** Sukhdev has quit IRC18:23
*** bana_k has joined #openstack-meeting-alt18:23
*** _amrith_ is now known as amrith18:23
*** Aish has joined #openstack-meeting-alt18:24
*** ashleighfarnham has joined #openstack-meeting-alt18:25
*** neelashah1 has quit IRC18:27
*** kzaitsev_mb has quit IRC18:28
*** eilert has joined #openstack-meeting-alt18:28
*** amrith is now known as _amrith_18:30
*** vgridnev has joined #openstack-meeting-alt18:31
*** paul-carlton2 has quit IRC18:31
*** _amrith_ is now known as amrith18:33
*** chandankumar has quit IRC18:34
*** dave-mccowan has joined #openstack-meeting-alt18:36
*** banix has joined #openstack-meeting-alt18:38
*** kfarr has quit IRC18:38
*** dizquierdo has joined #openstack-meeting-alt18:38
*** ig0r_ has joined #openstack-meeting-alt18:39
*** aginwala has quit IRC18:41
*** david-lyle_ has joined #openstack-meeting-alt18:42
*** s3wong has joined #openstack-meeting-alt18:42
*** bharathm has joined #openstack-meeting-alt18:42
*** catherine has joined #openstack-meeting-alt18:42
*** catherine is now known as Guest7556518:43
*** david-lyle has quit IRC18:45
*** baoli has quit IRC18:47
*** chandankumar has joined #openstack-meeting-alt18:48
*** dslevin_ has joined #openstack-meeting-alt18:48
*** alevine has joined #openstack-meeting-alt18:49
*** ikutukov has quit IRC18:49
*** catherineD has joined #openstack-meeting-alt18:50
*** merooeny_ has joined #openstack-meeting-alt18:50
*** balajiiyer has joined #openstack-meeting-alt18:51
*** merooney has quit IRC18:52
*** davideagnello has joined #openstack-meeting-alt18:52
*** davideagnello has quit IRC18:54
*** davideagnello has joined #openstack-meeting-alt18:55
*** iNeilus has quit IRC18:55
*** aginwala has joined #openstack-meeting-alt18:57
*** agireud has joined #openstack-meeting-alt18:57
*** Shamail has joined #openstack-meeting-alt18:59
*** shwetaap has quit IRC18:59
catherineD#startmeeting refstack19:00
openstackMeeting started Mon Dec 14 19:00:06 2015 UTC and is due to finish in 60 minutes.  The chair is catherineD. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: refstack)"19:00
openstackThe meeting name has been set to 'refstack'19:00
catherineD#link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-15-12-1419:00
*** pvaneck has joined #openstack-meeting-alt19:01
pvanecko/19:01
*** pvaneck_ has joined #openstack-meeting-alt19:02
catherineDpvaneck_: Hi ...19:02
alevineo/19:02
catherineDalevine: Hi .. I need to apologize that my internet maybe slow today ... I am not in the office19:03
catherineDalevine: Thanks for all the activities from your team .. together we can make a different in RefStack19:05
pvaneck_Do you have an agenda link19:05
catherineD#link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-15-12-1419:05
catherineDLet's start19:06
*** sparkyco_ has joined #openstack-meeting-alt19:06
catherineD#topic Confirm on data model ( https://goo.gl/zWYnoq) agreement and proceed to implementation19:07
*** openstack changes topic to "Confirm on data model ( https://goo.gl/zWYnoq) agreement and proceed to implementation (Meeting topic: refstack)"19:07
*** iNeilus has joined #openstack-meeting-alt19:07
*** kencjohnston has quit IRC19:08
*** sslypushenko___ has joined #openstack-meeting-alt19:09
sslypushenko___o/19:09
*** kencjohnston has joined #openstack-meeting-alt19:09
*** tonytan4ever has joined #openstack-meeting-alt19:09
catherineDI just see Mark submitted a patch today https://review.openstack.org/#/c/226902/19:09
pvaneck_No real objections here to the data model19:10
*** rockyg has joined #openstack-meeting-alt19:11
catherineDsslypushenko___:  we are at topic 1 on https://etherpad.openstack.org/p/refstack-meeting-15-12-14https://etherpad.openstack.org/p/refstack-meeting-15-12-1419:11
rockygo/19:11
catherineDrockyg: Hi agenda https://etherpad.openstack.org/p/refstack-meeting-15-12-1419:11
sslypushenko___catherineD Thx!19:11
rockygTHx!19:12
*** iNeilus has quit IRC19:12
sslypushenko___Suggested data model works for me19:12
catherineDwe also need to make sure that the model works for alevine: ... so I suggest that we do not make decision today .... so that we can review Mark's patch ..19:13
sslypushenko___I think we can discuss details during implementation19:13
catherineDsslypushenko___: +119:13
alevinecatherineD: I sent my comments by email earlier today. Have you got it?19:13
catherineDsslypushenko___: maybe I just sumit a spec and then we can make further comments...19:13
sslypushenko___catherineD yeap, that will work19:14
catherineDalevine: Yes ... Just see it thx a lot!  I want to review and make sure that the model works for you ...19:14
alevinecatherineD: In short I don't see why do we need roles. And I don't see why do we still need meta.19:14
*** alex_xu has quit IRC19:15
catherineDalevine: 's question is why do we store openid in meta rather than in the test table ?  Let us know if I do not phase your question correctly19:15
alevinecatherineD: And we'd need to add schemas table with properties: id, owner_id, version, name, json. Something like it.19:15
*** sbalukoff has joined #openstack-meeting-alt19:15
*** alex_xu has joined #openstack-meeting-alt19:16
sslypushenko___catherineD, Can you please forward alevine's mail to me?19:16
catherineDthe reason we put user_id in meta because sometime we have anonymous data  upload ... in this case we do not have user ID19:16
alevinecatherineD: Yes, I don't see why. user_id used to run the test is one of the important properties for the test. I understand, historically you didn't want to put public_key there but now it's possible to store user_id along with cpid.19:16
*** EricGonczer_ has quit IRC19:17
alevinecatherineD: You can make it optional then.19:17
*** yamahata has quit IRC19:17
*** yamahata has joined #openstack-meeting-alt19:17
sslypushenko___alevine We are trying to keep as much data as it possible in metadata19:18
catherineDsslypushenko___: good idea ... I just forwarded  alevine: 's email ...19:18
alevinecatherineD: It doesn't stop us at all. It's just it seems more straight and readable to me as a data model. This is a primary property, not to be buried in some meta-data key-value, I'd say.19:18
sslypushenko___catherineD Got it, thx19:19
catherineDalevine: another reason is originallywhen the data was uploaded it was owned by the user...but once the data is associated to a product as described in slide 4 ... it will be onwed by the product_group ... user no longer valide19:19
*** EricGonczer_ has joined #openstack-meeting-alt19:20
alevinecatherineD: As I understand the new model now from you doc - the user should be authorized to upload data for some particular vendor's product. In which case, this user should be in vendor's or product's group - not just some guest. No?19:21
catherineDin this case the user_id field will mostly empty for the 2 case 1) anonymous upload 2) ownership change19:21
catherineDalevine: as designe any one can upload data ... no pre-requirement that the user belong to a any vendor or product ...19:22
alevinecatherineD: I don't understand the idea of ownership change in view of groups, products and vendors. Could you please explain?19:22
alevinecatherineD: How do you guarantee then that it's a valid upload which results can be used for certification?19:22
catherineDso if user John upload data .. at firest he owns it19:22
alevinecatherineD: Only because this user has public key?19:22
*** salv-orlando has quit IRC19:22
catherineDalevine: yes19:23
*** fawadkhaliq has quit IRC19:23
catherineDso say there is product foo19:23
alevinecatherineD: In which case I actually do not care about the uploading user. I care about the ownership. Meaning that public key was also generated for some identity, right? I'd say we should use that one in the user_id field.19:24
catherineDand foo has a group_foo which john is a user in the group wirh role admin19:24
catherineDhe then can change the owner of the data to foo_group ...19:24
catherineDgroup will allow more than one users19:25
alevinecatherineD: Or if we do not care about the owner at all, then why would we need to store user_id at all? Even in meta? Isn't cpid (product_id) enough?19:25
catherineDincase user quit comapany or absent19:25
catherineDwe store the user_id so he can associate data to a product19:25
alevinecatherineD: What is cpid than? Isn't it the cloud_id=product_id?19:26
alevine"then"19:26
*** woodster_ has joined #openstack-meeting-alt19:26
sslypushenko___alevine Not exactly19:27
Guest75565once a data is associated to a product all user belongs to that product_group would admin role can manage the data19:27
alevinesslypushenko: What's the difference?19:28
sslypushenko___It is unique id for some cloud19:28
*** sparkyco_ has quit IRC19:28
sslypushenko___We can not be sure that in the wild cpid will acts like an product_id19:29
alevinesslypushenko: If it's just a subproduct why do we need to store it in our test table? We need to convert it into product_id and store the very one.19:29
sslypushenko___The most value from cpid it is UX19:29
alevinesslypushenko: If we can't convert it to product_id then we have absolutely no idea what was tested. What's the point of such results?19:29
*** dizquierdo has quit IRC19:30
sslypushenko___cpid contains some info about product, but it is not 1-to-1 relation19:30
*** bharathm has quit IRC19:31
Guest75565sslypushenko__: +119:31
sslypushenko___We should trust users, because we don't have a choice,  so we any can assume that user will provide product_id correctly19:32
Guest75565I really want to discuss the next subject which is about CPID19:32
alevinesslypushenko: :) I still don't quite understand. I understand the use-case - someone tested some cloud and uploads results. We need to figure out what cloud was that, right? In our new terms it's called product_id. If cpid contains some more info we can store it too, but product_id is the primary info out of it, no?19:32
sslypushenko___We means refstack-team?19:32
Guest75565can I suggest that I take the first pass to response to Alex's note ... we can then discuss from there?19:32
*** dprince has quit IRC19:32
alevinesslypushenko: Of course.19:33
*** Shamail has quit IRC19:33
sslypushenko___product_id is the primary info out of it - you absolutely right!19:33
Guest75565catherin is Guest75565 :-)19:33
sslypushenko___but it is quite tricky to make it works19:33
alevinecatherineD: sure. Don't mind me. Just go ahead.19:33
sslypushenko___Refstack try to keep things simple19:34
sslypushenko___so we just stick to cpid for a while19:34
Guest75565I think it is relevant could we go to the next  topic to discuss CPID?19:34
alevinesslypushenko: Yes, but we're discussing the data model. It should be transparent. Especially the relation between test and it's source. Isn't it?19:34
alevinecatherineD: yes :)19:35
sslypushenko___Yeap)19:35
Guest75565#topic Use cloud access URL to generate CPID.19:35
Guest75565#link https://review.openstack.org/#/c/255607/19:35
sslypushenko___I'm +1 for using access URL only as a failover19:36
Guest75565the discussion is about should we keep using keystone ID for CPID...19:36
Guest75565one of the big thing coming up is in19:37
Guest75565#link https://bugs.launchpad.net/refstack/+bug/150028019:37
openstackLaunchpad bug 1500280 in refstack "RefStack client should use session based keystone auth for CPID" [Medium,Confirmed] - Assigned to Daryl Walleck (dwalleck)19:37
Guest75565if we keep using CPID we need to upgrade as describe in the bug ...19:37
rockygthanks Guest75565 for identifying yourself!19:38
alevineGuest75565: Where is possible to read about the meaning of CPID and it's purpose? Is it just a technical varchar ID which is used to identify the cloud tests were run on or something else as well?19:38
Guest75565why take the resource to develop something that if it does not work will go to using URL19:38
sslypushenko___We spent a lot of affords on make current code working19:38
pvaneck_I think one of the use cases of cpid was to be able match the test runs of the same cloud together19:39
Guest75565rockyg: sorry catherine switch to web interface so still have the other client log in19:39
alevinepvaneck_: That's the obvious one. Anything else?19:39
sslypushenko___ pvaneck_ It will not work19:39
Guest75565sslypushenko___: I know ... I know ... and it will demand more time to upgrade ...19:40
sslypushenko___Every cloud have a bunch of endpoints19:40
sslypushenko___at least one per region19:40
Guest75565alevine: read about CPID in https://github.com/openstack/refstack/blob/master/specs/prior/implemented/refstack-org-api-cloud-uuid.rst19:41
Guest75565#link orginal spec for CPID https://github.com/openstack/refstack/blob/master/specs/prior/implemented/refstack-org-api-cloud-uuid.rst19:42
alevineGuest75565: Thank you19:42
Guest75565#link current suggested spec for CPID https://review.openstack.org/#/c/255607/19:42
sslypushenko___from POV new CPID mechanism is not significantly better then previous one19:43
Guest75565really I just do not see the value of using Keystone ID now that we learn more about Keystone19:43
sslypushenko___except that it will work even for public clouds19:43
*** tonytan4ever has quit IRC19:43
alevineNow that we introduce vendors and products and stuff, does it still make sense to have such a strange id? Wouldn't we want to record some info (mac-address, url, ...) during product registration and use it afterwards?19:44
Guest75565sslypushenko__: +1 both are not perfect  .. but one is with less effort19:44
sslypushenko___May we should keep it both?19:44
Guest75565alenvine: for the case of anonymous data upload yes ... we need something19:44
alevineGuest75565: I mean that in that old spec, it's stated that cpid is needed to 'somehow' group results together. It sounds really weird for certification cases now, doesn't it? Sorry if I'm mistaken.19:45
Guest75565if we keep both .... do we need to upgrade to catch up with Keystone?19:45
Guest75565I am OK to keep both if we do not spend any effort ..19:45
*** jmckind has joined #openstack-meeting-alt19:45
Guest75565on development to keep up with Keystone19:45
alevineGuest75565: I don't quite understand what is anonymous data upload now. What is the purpose of it?19:45
*** sylwesterB has joined #openstack-meeting-alt19:46
*** ijw has quit IRC19:46
alevineGuest75565: I mean how would we even show it? As some results for some cloud? What's the point?19:46
sslypushenko___alevine People want just to try what RefStack is19:47
Guest75565to encourage people to upload data or test (once we offer centralize testing ) ... this is for any user of the cloud not necessary the vendor or product onwer19:47
Guest75565most of the community data in RefStack today is uploaded anonymously ... we do that ti encourage larger user base to use RefStack with minimum intimidation19:49
alevinessplypushenko___: Ok. Let's suppose I'm such a user. How would I see my results afterwards? I should be a registered user in RefStack to be able to somehow see those results. I understand that it's possible to find me by my public-key used, no? Then you'd want to allow results without registered cloud, right?19:49
*** ajmiller has joined #openstack-meeting-alt19:50
Guest75565so I guess the agreement is to keep current CPID creation but add URL generation option with no Keystone update?19:50
*** maxabidi has joined #openstack-meeting-alt19:50
sslypushenko___alevine During uploading you will get a link on your results19:50
Guest75565time check ... 10 mins left ... I really need to get to the next topic ... wihich is do we need to have meeting for the next 2 weeks?19:51
alevinesslypushenko: Oh, ok.19:51
*** MarkAtwood has quit IRC19:51
*** e0ne has quit IRC19:51
sslypushenko___So you can review uploaded results and get some UX experience from RefStack19:51
alevineGuest75565: We're quite fine with what we have. I guess the rest can be discussed in email.19:52
*** diazjf has joined #openstack-meeting-alt19:52
Guest75565sorry everyone ...19:52
*** e0ne has joined #openstack-meeting-alt19:52
sslypushenko___catherineD May be we will establish meeting with alevin, if there are some questions for disscuss19:52
Guest75565do we need to meet on 12/21/2015?19:52
Guest75565I will be here ... just want to see everyone else's schedule ?19:53
sslypushenko___12/21 will work for me19:53
Guest75565sslypushenko__: +1 to have additional meeting with SAlex19:53
alevineGuest75565: Whatever you decide, I'm fine.19:54
Guest75565I will schedule ...19:54
pvaneck_Will be on vacation, but can join19:54
Guest75565#agreed we will have meeting on 12/21/201519:54
Guest75565how about 12/28?19:54
*** dprince has joined #openstack-meeting-alt19:54
*** fzdarsky_ has quit IRC19:54
sslypushenko___will work for me too19:54
Guest75565#agreed Caterine will call addtiional meeting with RefStack cores and Alex for futher discussion19:55
*** jhfeng has joined #openstack-meeting-alt19:55
alevineall: One last thing. I might be wrong, but it seems to me that we're changing the RefStack quite a bit so maybe it's time to rethink old use-cases like having UX experience from RefStack or just playing with it. They won't nicely fit into new world as they are, I'm afraid.19:55
Guest75565I will be on vacation on 12/28 ..19:55
Guest75565but can join the meeting too ...19:55
Guest75565looks like we will have meeting on 12/28 too :-)19:56
sslypushenko___Let decide it on next meeting)19:56
Guest75565+1 good idea19:56
Guest755654 mins left ..19:56
Guest75565I will schedule additional meeting before net Monday19:56
sslypushenko___But it really looks that some F2F meeting can help us to get understanding19:57
pvaneck_+1 on reevaluating Ux19:57
Guest75565how about web meeting and phone like we did last time ..19:57
*** silos has joined #openstack-meeting-alt19:57
sslypushenko___+119:57
*** NazcaLines has joined #openstack-meeting-alt19:57
alevinesslypushenko__: If as I presume you're in the same city as we are, we can meet here and you can convey all the sacred knowledge to us much easier :)19:58
Guest75565I will schedule .... hope your skype did not charge you last time ..19:58
*** rellerreller has joined #openstack-meeting-alt19:58
sslypushenko___alevine I'm in Ukraine)19:58
Guest75565wow that works ... I should ask to have a mid-cycle in Moscow? :-)19:58
alevinesslypushenko___: Ouch. My mistake :)19:58
Guest75565oh ...19:59
*** arunkant has joined #openstack-meeting-alt19:59
Guest75565ok I will schedule a conf call and then we will go from there ...19:59
sslypushenko___Keiv would be better)19:59
rockygWould love to visit Kiev19:59
Guest75565RefStack is a truly global team19:59
sslypushenko___Your are welcome)19:59
Guest75565I need to end the meeting19:59
Guest75565thx you all ...19:59
alevinesslypushenko___: I'd love too. Was there several times. But you know, it might be problematic :)19:59
*** dizquierdo has joined #openstack-meeting-alt20:00
sslypushenko___Thx 2 all!20:00
rockygGrandmother is from Simferopol20:00
rockygThanks!20:00
*** alee has joined #openstack-meeting-alt20:00
Guest75565#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Mon Dec 14 20:00:30 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2015/refstack.2015-12-14-19.00.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2015/refstack.2015-12-14-19.00.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2015/refstack.2015-12-14-19.00.log.html20:00
redrobot#startmeeting barbican20:00
openstackMeeting started Mon Dec 14 20:00:51 2015 UTC and is due to finish in 60 minutes.  The chair is redrobot. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: barbican)"20:00
openstackThe meeting name has been set to 'barbican'20:00
*** sslypushenko___ has quit IRC20:00
*** kebray has quit IRC20:01
redrobot#topic Roll Call20:01
*** openstack changes topic to "Roll Call (Meeting topic: barbican)"20:01
silos\o/20:01
rellerrellero/20:01
jmckindo/20:01
jhfengo/20:01
redrobotAs usual the meeting agenda can be found here:20:01
woodster_o/20:01
redrobot#link https://wiki.openstack.org/wiki/Meetings/Barbican20:01
NazcaLineso/20:01
diazjfo/20:01
maxabidio/20:01
arunkanto/20:01
elmikoo/20:01
aleeo/20:01
*** jaosorior has joined #openstack-meeting-alt20:01
*** alevine has left #openstack-meeting-alt20:01
* redrobot waves at maxabidi 20:01
*** kfarr has joined #openstack-meeting-alt20:02
kfarro/20:02
redrobotmaxabidi I don't recognize your nick... mind introducing yourself?20:02
*** catherineD has left #openstack-meeting-alt20:02
redrobota couple of new Barbicaneers... how exciting! :D20:02
* redrobot feels a little out of the loop still...20:02
maxabidiHello, I am a new member at HPE20:03
woodster_redrobot:  still in that honeymoon period?20:03
redrobotwoodster_  hehe, something like that :)20:03
*** sylwesterB has quit IRC20:03
arunkantredrobot: maxabidi is new barbicaneer from hpe20:03
*** ikutukov has joined #openstack-meeting-alt20:03
redrobotarunkant awesome20:03
redrobotwelcome maxabidi20:03
redrobotI don't recognize NazcaLines either...20:03
*** iNeilus has joined #openstack-meeting-alt20:03
jaosorioro/20:04
*** kebray has joined #openstack-meeting-alt20:04
NazcaLines I'm a newcomer  :)20:04
redrobotwelcome NazcaLines !20:04
NazcaLinesthanks20:04
redrobot#topic Action Items from last meeting20:04
*** openstack changes topic to "Action Items from last meeting (Meeting topic: barbican)"20:04
redrobot#link http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-12-07-20.00.html20:04
*** tonytan4ever has joined #openstack-meeting-alt20:04
*** Guest75565 has quit IRC20:05
*** Aish has quit IRC20:05
redrobotalee had an action to advertise his blog post20:05
redrobotwhich he did here20:05
redrobot#link http://lists.openstack.org/pipermail/openstack-dev/2015-December/081749.html20:05
aleeyup20:05
redrobotalee good write up!20:05
aleelooks like I have at one person trying my write up20:05
aleeat least ..20:05
dave-mccowano/20:06
*** tellesnobrega is now known as tellesnobrega_af20:06
stevemardiazjf: thanks for the heads up20:06
jhfengalee: very useful, thanks20:06
*** pvaneck_ has quit IRC20:06
diazjfstevemar, no worries20:06
aleejhfeng, cool - let me know if anything is wrong/ doesn't work ..20:06
redrobotdiazjf did you get a chance to update the Barbican Context BP?20:06
diazjfredrobot, sure did20:07
redrobotdiazjf link?20:07
diazjfhttps://review.openstack.org/#/c/241068/20:07
redrobotdiazjf thanks!20:07
*** whydidyoustealmy has quit IRC20:07
*** panatl has joined #openstack-meeting-alt20:07
*** shakamunyi has quit IRC20:07
redrobotand lastly, I was supposed to clean up the mitaka-1 Launchpad page... which I started doing today20:07
hockeynuto/20:07
redrobotbut I'm not quite done yet20:07
redrobotso I'll bump that to next week20:08
*** sylwesterB has joined #openstack-meeting-alt20:08
redrobot#action redrobot to finish cleaning up Launchpad mitaka-1 page20:08
redrobotThat's it for last week's action items20:08
redroboton to this week's agenda20:08
*** iNeilus has quit IRC20:09
redrobot#topic Barbican SAML Authentication20:09
*** openstack changes topic to "Barbican SAML Authentication (Meeting topic: barbican)"20:09
redrobot#link https://review.openstack.org/#/c/241068/20:09
redrobotdiazjf you want to talk about this?20:09
*** fzdarsky_ has joined #openstack-meeting-alt20:09
stevemardiazjf: i'm interested in hearing about it :O20:09
diazjfAwesome, great to have everyone here.20:10
*** balajiiyer1 has joined #openstack-meeting-alt20:10
*** david-lyle_ has quit IRC20:10
diazjf So as a refresher the reason why this was needed is because there needed to be a way for Swift to use Barbican without Keystone.20:11
diazjfThe reason being is because most swift deployments come with another authentication system.20:11
*** yonglihe has quit IRC20:11
stevemarso, barbican - right now, can be run without keystone? and it's usable?20:11
* notmyname isn't really here, but wants to respond to that20:12
*** sylwesterB has quit IRC20:12
redrobotstevemar the Barbican auth requirement is that X-Project-Id and X-Roles must be present in the request... we don't really care how they get there, but the obvious way to get them there is to use keystonemiddleware20:12
notmynameI don't want castellan to be tied to keystone. if the backend requires keystone, that's ok. if the backend doesn't (eg another I write myself) I don't20:12
*** david-lyle has joined #openstack-meeting-alt20:12
jaosoriorstevemar: Yeah, in order to do that we use another context middleware that we ship with the barbican server code20:13
*** neiljerram has quit IRC20:13
notmynameI want castellan to pass on whatever creds are given and the backend interprets it20:13
*** sneti_ has quit IRC20:13
elmikonotmyname: +120:13
*** balajiiyer has quit IRC20:13
redrobotnotmyname ack20:13
*** sneti has joined #openstack-meeting-alt20:13
jaosoriorstevemar: Basically it requires the client to set the headers redrobot mentioned20:13
redrobotnotmyname I think that was the general agreement last time we talked about it...20:13
redrobotnotmyname last time I was here anyway...20:13
notmynameI mean, I think it would be swell to use barbican without keystone, but I think that's unreasonable to ask for ;-)20:14
elmikoredrobot, yea, i think that is consistent with the last discussion i was involved with20:14
notmyname(here's my ignorance of castellan) I want basically some parameter I pass in to go on to the backend. without caring what the type is20:14
redrobotnot sure how we arrived at a SAML middleware though20:14
notmynameeg if barbican needs an oslo.context that works with keystone, ok20:14
notmynameif my own needs an hmac and whatever, then I'll pass a dictionary.20:15
*** jrichli has joined #openstack-meeting-alt20:15
stevemarwhats the relationship between castellan and barbican? castellan depends on barbican?20:15
elmikoiirc, castellan is just blindly passing the context object on to the barbicanclient20:15
*** salv-orlando has joined #openstack-meeting-alt20:15
elmikostevemar: castellan is a keymanager abstraction layer library20:15
kfarrstevemar castellan is sort of a wrapper for barbican20:15
kfarror any other key manager back end20:16
redrobotstevemar  no, castellan is an interface.  there is a castellan implementation that uses python-barbicanclient20:16
*** Sukhdev has joined #openstack-meeting-alt20:16
notmynamehmm...ok20:16
redrobotstevemar idea is that you integrate your project with Castellan, then you pick a castellan implementation at deploy time20:16
rellerrellercastellan is designed to be a generic key manager interface that can support any key manager implementation20:16
*** _nadya_ has joined #openstack-meeting-alt20:16
stevemargotcha, generic, can be used with barbican or something else20:17
rellerrellerthe goal is to provide a common interface that easily allows different key management solutions to be used in a plug and play manner20:17
notmynameso is castellan the interface or an implementation?20:17
rellerrellerThe context object is designed to be a generic blob. The backend is responsible for interpreting the data.20:17
notmynameie API contract or something I actually import20:17
redrobotnotmyname the castellan lib includes both the interface and implementations20:17
rellerrellerCastellan is the name of the library that provides a KeyManager interface20:17
rellerrellerIt also provides a Barbican implementation as redrobot pointed out.20:18
rellerrellerThe plan is to include a KMIP implementation in the future20:18
redrobotrellerreller the problem with the "blobl" definintion is that it defeats the purpose of having a pluggable backend.20:18
*** jmckind_ has joined #openstack-meeting-alt20:18
redrobotin any case, we're way off topic from SAML Auth20:18
redrobotdiazjf did you want to talk about SAML ?20:18
rellerrellerredrobot yes, I know. We have discussed this in the past. My definition is different than users.20:18
rellerrellerThere will be a common credentials class like KMIP defines and subclasses that implement different types.20:19
redrobotrellerreller awesome!20:19
rellerrellerAn example woudl be a UsernamePasswordCredential object that contains username and password20:19
stevemarredrobot: i imagine SAML is what diazjf is proposing to chat between swift and castellan20:19
rellerrellerAnother example is KeystoneCredential where you pass it a keystone context.20:19
diazjfredrobot, I was thinking it would be necessary for swift not using keystone.20:20
rellerrellerYes, I could easily see another Credential for SAML20:20
*** chandankumar has quit IRC20:20
redrobotdiazjf do we expect most Swift deployments to be using SAML for auth?20:20
diazjfnotmyname, I thought originally this is what was needed in order for Castellan to be accepted in Swift's keymaster20:20
*** hyakuhei has joined #openstack-meeting-alt20:21
*** jmckind has quit IRC20:21
*** dslevin_ has quit IRC20:21
diazjfredrobot, I had a meeting a while back with alee, kfarr, and elmiko, the SAML assertion will be generated by Barbican Client20:21
*** bharathm has joined #openstack-meeting-alt20:22
diazjfSo it will be values in the conf or environment the client can use to build an assertion20:22
diazjfand gain access to Barbican20:22
notmynamediazjf: I think the conversation wandered away from the actual use cases, and we somehow got to SAML (and that's not a critique. it just happend)20:22
*** baoli has joined #openstack-meeting-alt20:23
*** dimtruck is now known as zz_dimtruck20:23
*** fzdarsky_ has quit IRC20:23
diazjfnotmyname, redrobot, I'm ok with keeping Keystone. Just want to know whats required to get Castellan into the Swift Keymanager20:23
redrobotI'm not super familiar with SAML, but as I understand it, the assertion is created by someone with authority...  like a directory service, for example...  not sure what authority barbicanclient has to generate saml assertions?20:24
aleenotmyname, Its not so much that it veered away from actual use-cases as we started thinking about what would actually be passed through and accepted by barbican.20:24
*** baoli has quit IRC20:24
panatlyes, Barbican client generating SAML Assertion .. something is worng20:24
*** baoli has joined #openstack-meeting-alt20:24
notmynamealee: that's fair20:24
aleeat the time, we started thinking about what would need to implemented on the barbican side.  seems like if we need to implment some kind of auth protocol in the middleware on the barbican sider, then we should do something standard20:25
aleeand saml is pretty standard20:25
notmynamediazjf: from the swift perspective, to use castellan, we need to not have any extra requirements beyond what the backend key manager requires. that will allow us to use barbican or something else in testing and prod20:25
*** hyakuhei has quit IRC20:25
notmynamejrichli: does that sound right?20:26
aleebetter yet -- if we implement saml support, then we put barbican behind/ as an apache module, and have apache modules do what we need to do20:26
jrichlinotmyname: agreed20:26
redrobotnotmyname iirc, for the first pass at a castellan implementation, it would be limited to a single credential to the keystore.  Basically Swift will own all keys, yes?20:26
*** sneti has quit IRC20:27
notmynameredrobot: that is correct. swift owns the keys (except perhaps the root key). and it's swift the service (as opposed to end users) who has the creds to get that root key20:27
notmynameredrobot: or rather, swift has creds to get that root key20:27
*** jmckind has joined #openstack-meeting-alt20:27
*** kebray has quit IRC20:28
aleeredrobot, yes - as a first implementation - that might be ok.  we were thinking beyond that -- can we avoid having an all powerful swift service user that has access to all the keys?20:28
*** zz_dimtruck is now known as dimtruck20:28
notmynamealee: that's up to swift, right?20:29
aleetrue20:29
*** dims has joined #openstack-meeting-alt20:29
notmynamealee: and at that point, it will probably require that the end user identity management is the same used by the key manager20:29
notmynameunless you're proposing some bridge there. and that sounds *really* complicated20:29
*** jmckind_ has quit IRC20:30
redrobotyeah, SAML sounds like overkill for a middleware that just needs to verify a single password20:30
redrobotfor an MVP I think we would need something like a Pre-Shared Key middleware20:30
*** jmckind has quit IRC20:31
rellerrellerredrobot MVP?20:31
aleeredrobot, for a single password, thats absolutely true.20:31
redrobotrellerreller minimum viable product20:31
*** neelashah has joined #openstack-meeting-alt20:32
notmynameso I think it sounds like you (barbican peoples) understand the swift needs. are there other questions about that, as it applies to the auth betweent he two?20:32
notmynamejrichli: are we missing covering anything?20:32
jrichlinotmyname: sounds like there is an understanding.20:33
notmynamediazjf: alee: redrobot: good from your end?20:33
redrobotnotmyname  I'm good... may need to sync up with diazjf regarding the SAML blueprint though20:34
notmynameredrobot: you may need to or I may need to?20:34
diazjfredrobot, sure I'd like to have a talk about what the best step to take forward would be.20:34
redrobotnotmyname I'll syinc up with him20:34
notmynameok :-)20:34
*** kzaitsev_mb has joined #openstack-meeting-alt20:34
aleenotmyname, jrichli - do you guys have any preference in terms of creds ?  user/password, or shared key?20:34
diazjfnotmyname, thanks for attending, I appreciate it20:35
*** jmckind has joined #openstack-meeting-alt20:35
diazjfalee, I think user/pass would be fine20:35
notmynamealee: I think that's up to whatever the key manager backend is. why does that actually matter?20:35
notmynamealee: ok ok, yeah there are leaky abstractions there20:35
diazjfbut I have no preference20:35
aleenotmyname, so here is my understanding on what is needed ..20:36
redrobotnotmyname I think alee is asking about the barbican-sans-keystone preference20:36
notmynamealee: can I write a key manager backend that uses hmac with a shared secret?20:36
aleeright20:36
aleeso if we dont have keystone, we need some way for swift to auth to barbican20:37
*** kebray has joined #openstack-meeting-alt20:37
aleeand we would have castellan pass through those credentials20:37
elmikoalee: wouldn't those just be encapsulated in the context object?20:37
notmynameas a first pass, I'm ok with barbican requiring keystone20:37
notmynameit might be that pushes me to reimplement something else (unfortunately), but I don't know at this point20:38
aleeand they would be interpreted by some auth middleware that would convert those params into keystone like options ..20:38
*** gariveradlt__ has joined #openstack-meeting-alt20:38
elmikoi thought the deepest abstraction for castellan was the context object, and anything in that object would just get passed on to the consumer for them to do with as they please.20:39
diazjfelmiko, correct as long as there's a auth-middleware in Barbican that knows what the context is20:39
notmynamejust as long as I can make FakeKeyManager for castellan in my tests and my own AwesomeKeyManager for castellan in my own deployment20:39
elmikoand i'm not saying oslo.context, just some object known as context in cast.20:39
notmynameelmiko: oh good :-)20:39
rellerrelleralee: I thought swift would authenticate with some service and the result of that (SAML assertion) would be passed to Barbican?20:39
elmikonotmyname: we implement a custom key manager in sahara, you could do that20:40
*** _nadya_ has quit IRC20:40
notmynameelmiko: and the context parameter could be a disctionary. or string. or oslo.context.20:40
rellerrellerThe SAML assertion would live in a SamlCredential object20:40
*** eilert has quit IRC20:40
elmikonotmyname: right, whatever you need. it's just an object to castellan that gets forwarded to the key manager impls20:40
rellerrellernotmyname kfarr, don't we have a basic key manager for testing that always returns the same key?20:41
notmynamerellerreller: please let it be 4220:41
jrichli:-)20:41
kfarrrellerreller, no, that's a fixed key manager.  That was in the original implementations in cinder and nova, but not in Castellan20:41
elmikohmm, i know there is NotImplementedKeyManager, was there also FakeKeyManager?20:41
rellerrellernotmyname 42?20:41
aleerellerreller, yes - but of course thats overkill for a single user/password20:41
elmikonotmyname: it would have to ;)20:41
redrobotI think we've beaten this to death here...20:42
aleerellerreller, the answer to life , the universe and everything ..20:42
kfarrthere was one in the test directories that has an in-memory database for storing keys20:42
notmynamerellerreller: https://en.wikipedia.org/wiki/42_(number)#The_Hitchhiker.27s_Guide_to_the_Galaxy20:42
redrobotwe can iron out the details over a BP20:42
elmikoredrobot: +120:42
*** mrmartin has quit IRC20:42
diazjfredrobot +120:42
redrobotok, thanks notmyname and jrichli for stoping by!20:42
jrichliyw20:42
notmynameyou're welcome20:43
diazjfthanks everyone :)20:43
redrobotmoving on...20:43
redrobot#topic Add PUT support for Generic Containers20:43
*** openstack changes topic to "Add PUT support for Generic Containers (Meeting topic: barbican)"20:43
redrobot#link https://review.openstack.org/#/c/207249/20:43
diazjfredrobot, we can talk more about this sometime this week20:43
NazcaLinesi add it.20:43
redrobotdiazjf for sure!20:43
redrobotNazcaLines go ahead20:43
NazcaLinesBP:https://blueprints.launchpad.net/barbican/+spec/api-containers-add-put20:43
NazcaLinesCommit: https://review.openstack.org/#/c/207249/20:44
NazcaLinesI'm working on it now.20:44
NazcaLinesThe question is that:20:44
NazcaLinesi plan to support add new secret ref and delete existing secret ref in a container.20:44
NazcaLinesbut it's different with 'replace-all-refs' committed by @Kevin Bishop at first.20:45
* redrobot senses a PUT vs PATCH debate brewing...20:45
NazcaLineswhat do you think? Is it worth  supporting "add"&"delete"? Maybe "replace-all-refs" is better?20:45
*** Sukhdev has quit IRC20:45
elmikoredrobot: lol20:45
*** baoli has quit IRC20:45
*** baoli has joined #openstack-meeting-alt20:46
redrobotI _think_ it comes down to PUT vs PATCH semantics20:46
redrobotiirc we decided to do a replace-all for PUT and then punted on PATCH because JSONPATCH looked unfriendly20:46
*** baoli has quit IRC20:46
dave-mccowani was pretty happy with chelsea's last commit (patch set 8). it just needed some clean up. i think "replace all" with PUT is a clean, simple, and sufficient solution.20:47
*** baoli has joined #openstack-meeting-alt20:47
redrobotdave-mccowan do you have the link?20:47
elmikoredrobot: that sounds about right, although doing partial updates through PATCH is within the boundaries of reasonable20:47
elmikothe key is to choose one way, partial updates or jsonpatch, and stick with it.20:47
*** barrett has joined #openstack-meeting-alt20:48
redrobotelmiko +120:48
redrobotNazcaLines does that make sense?20:48
*** jmckind_ has joined #openstack-meeting-alt20:48
dave-mccowansame link that NazcaLines posted above20:48
*** dizquierdo has quit IRC20:49
redrobotdave-mccowan ack, thanks20:50
*** jmckind_ has quit IRC20:50
NazcaLinesimagine that if we have many secrets in a container and we want to replace some of them. In 'replace-all-refs' mode, we should write all secret_refs into the json request data.20:50
woodster_I recall the API team suggesting turning PATCH things into simpler semantics if possible...so DELETE /containers/<container UUID>/secrets/<secrets UUID> to remove one secret (for example)20:50
redrobotseems like this would be best to sort out in a spec?20:50
silosWe could also mirror ACL's and provide both PUT and PATCH? PUT is used to replace the existing ACLS while PATCH is used to update it. At least that's what the documentation shows.20:51
elmikowoodster_: i've seen it discussed both ways for PATCH, the best guidance was pick whichever works for your project and be consistent.20:51
*** jmckind has quit IRC20:51
dave-mccowanNazcaLines I applaud your ambition to do a more robust solution with PATCH and add/deletes, but I don't think it's necessary.  (if we did, then we'd want a spec as it would be an API change.)  With PUT only, it is the same API as a 2-part create, so I don't think a spec would be needed.20:51
redrobotsilos  +1 for API consistency20:51
*** EricGonc_ has joined #openstack-meeting-alt20:52
*** sneti has joined #openstack-meeting-alt20:52
elmikosilos: that works too20:52
*** jmckind has joined #openstack-meeting-alt20:53
elmikodave-mccowan, NazcaLines, if you want a robust add/delete/update methodology, then just use the jsonpatch stuff through the PATCH method20:53
elmiko#link https://tools.ietf.org/html/rfc6902.html20:53
elmikofor reference20:53
elmikoit's probably more heavyweight than needed though, at a guess20:54
*** jrichli has left #openstack-meeting-alt20:54
woodster_elmiko: yeah that is why I favor the non-PATCH approaches20:54
*** kebray has quit IRC20:55
elmikoi kinda do too, much simpler to implement/maintain20:55
aleewoodster_, +1, PATCH is hard to get right.20:55
woodster_alee: agreed20:55
*** Mr_T has joined #openstack-meeting-alt20:55
*** EricGonczer_ has quit IRC20:55
elmikoi agree with redrobot thought, we should argue it out on a spec =)20:55
redrobotok, so regarding NazcaLines 's question... I think we should review what ACLs is doing with PATCh/PUT and then write a Spec for the change20:56
redrobotNazcaLines would that work for you?20:56
*** kebray has joined #openstack-meeting-alt20:56
redrobot#link http://git.openstack.org/cgit/openstack/barbican-specs/tree/README.rst20:56
dave-mccowani think we're unanimous on use PUT for replace only.  are there any dissenters?20:57
NazcaLinesYes. i'd like to do it.20:57
redrobotNazcaLines ok, sounds good20:58
elmikodave-mccowan: if that's the consensus, we should review the metadata spec as it allows for deletion through PUT20:58
redrobotonly a couple of minutes left here20:58
redrobot#topic Mitaka Mid-Cycle20:58
*** openstack changes topic to "Mitaka Mid-Cycle (Meeting topic: barbican)"20:58
redrobotDetails about the mid-cycle can be found here:20:58
redrobot#link https://wiki.openstack.org/wiki/Sprints/BarbicanMitakaSprint20:58
redrobotAlso, please start adding topics to the etherpad:20:58
redrobot#link https://etherpad.openstack.org/p/barbican-mitaka-midcycle20:59
*** amrith is now known as _amrith_20:59
*** thingee has joined #openstack-meeting-alt20:59
jhfengeveryone, please review https://review.openstack.org/#/c/253719/. This should be a simple one20:59
*** sdake has quit IRC20:59
*** scohen1 has joined #openstack-meeting-alt20:59
redrobotjhfeng will do.20:59
redrobotthanks everyone for coming!20:59
redrobot#endmeeting20:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:59
openstackMeeting ended Mon Dec 14 20:59:56 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-12-14-20.00.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-12-14-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-12-14-20.00.log.html21:00
*** silos has left #openstack-meeting-alt21:00
elmikothanks redrobot21:00
diazjfthanks everyone o/21:00
*** Shamail has joined #openstack-meeting-alt21:00
*** arunkant has left #openstack-meeting-alt21:00
*** jhfeng has left #openstack-meeting-alt21:01
*** rellerreller has quit IRC21:01
*** david-lyle has quit IRC21:01
barrett#startmeeting Product Working Group21:01
openstackMeeting started Mon Dec 14 21:01:55 2015 UTC and is due to finish in 60 minutes.  The chair is barrett. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: Product Working Group)"21:01
openstackThe meeting name has been set to 'product_working_group'21:02
thingeeo/21:02
*** balajiiyer1 has quit IRC21:02
*** banix has quit IRC21:02
hughhalfo/21:02
*** MeganR has joined #openstack-meeting-alt21:02
ShamailHi all21:02
barrettHi - Who's here for the Product WG meeting?21:02
MeganRo/21:02
hughhalfo/21:02
*** pchadwick has joined #openstack-meeting-alt21:02
*** pchadwick has left #openstack-meeting-alt21:03
*** ijw has joined #openstack-meeting-alt21:03
sgordono/21:03
scohen1o/21:03
*** Shamail_ has joined #openstack-meeting-alt21:03
kencjohnstono/21:03
barrett#link agenda: https://wiki.openstack.org/wiki/Meetings/product-team21:03
barrettLink to the agenda21:04
barrett#topic Mid cycle planning21:04
*** openstack changes topic to "Mid cycle planning (Meeting topic: Product Working Group)"21:04
*** pchadwick has joined #openstack-meeting-alt21:04
*** harlowja has quit IRC21:04
rockygo/21:04
pchadwicko/21:04
barrett#link: mid cycle planning etherpad https://etherpad.openstack.org/p/PWG_Mitaka_Midcycle21:04
*** leong has joined #openstack-meeting-alt21:05
barrettIn last week's meeting we talked about the UK option and asked folks to touch base with their management on whether it would be possible for folks to travel21:05
*** aginwala has quit IRC21:06
Shamail_The etherpad shows preference for UK21:06
*** Aish has joined #openstack-meeting-alt21:06
barrettwere people able to talk to their mgrs?21:06
barrettI've added a section into the planning etherpad for folks to enter their names if they know they can attend21:06
*** Shamail has quit IRC21:06
*** Shamail_ is now known as Shamail21:06
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:06
*** neelashah has quit IRC21:06
Arkady_Kanevskyhello21:07
*** harlowja has joined #openstack-meeting-alt21:07
*** david-lyle has joined #openstack-meeting-alt21:07
*** baoli has quit IRC21:08
barrettIt I also added a section for people to add their names if they know they cannot attend21:08
* hughhalf regrets he will be unable to travel to the midcycle due to non-work commitments21:08
ShamailI'll make it.21:08
*** baoli has joined #openstack-meeting-alt21:08
barretttoo bad Hughhalf21:08
rockygHey, Arkady_Kanevsky21:09
hughhalfAye, just a couple of (admittedly otherwise pleasant) things on that time of year21:09
Arkady_Kanevskyhere mam21:09
*** dslevin_ has joined #openstack-meeting-alt21:09
barrettIdeally we can determine if we will haev a quorum if we hold this in the UK before the holiday break21:09
*** baoli has quit IRC21:09
Arkady_KanevskyRocky how can I help?21:09
barretthi Arkady21:09
Arkady_KanevskyI am reviewing rollingupgrade now21:09
pchadwickHow big is a quorum?21:10
*** baoli has joined #openstack-meeting-alt21:10
*** NazcaLines has quit IRC21:10
barrettpchadwick - good question - enough folks to review/prioritize user stories, revise work flow, volunteer to take leadership on user stories21:10
barrettWhat do folks think is the minimum attendance that would make the midcycle viable?21:11
*** harlowja_ has joined #openstack-meeting-alt21:11
rockygJust being neighborly, Arkady_Kanevsky21:12
*** Leong_ has joined #openstack-meeting-alt21:12
kencjohnstonbarrett Good question, I'm not sure what our actual team size is. If we used the number of folks involved in the roadmap + contributors to the repo I think we'd be in the 10-12 range.21:12
*** david-lyle has quit IRC21:12
scohen1what about possible date poll?21:13
Arkady_Kanevskythank you Rocky.21:13
Shamailkencjohnston: that number sounds about right, 12-15 active.21:13
kencjohnstonBut we'd also discussed reaching out to get new members from European companies.21:13
barrettkennycjohnston - That's a good starting place.21:13
barrettkencjohnston: +121:13
*** Swami_ has quit IRC21:13
*** matrohon has joined #openstack-meeting-alt21:13
rockygArkady_Kanevsky, Mikal Still is trying to collect/triage live upgrade bugs issues; you might connect with him on the user stories.21:13
pchadwickDo I count as a European company ;)?21:13
*** harlowja has quit IRC21:13
barrettscohen1: We could do that21:13
*** Swami_ has joined #openstack-meeting-alt21:13
kencjohnstonSo if we had 7 current members plus five new members I'd consider it a success21:14
Arkady_Kanevskysure Rocky. Do you have his email?21:14
*** leong has quit IRC21:14
barrettkencjohnston - agree21:14
Shamailkencjohnston: +121:15
Leong_+121:15
kencjohnstonArkady_Kanevsky his handle is mikal he's in #openstack right now21:15
Arkady_Kanevsky+1 on number for midcycle21:15
kencjohnstonSo we are at 7 current right now21:16
*** iNeilus has joined #openstack-meeting-alt21:16
*** iNeilus has quit IRC21:16
*** iNeilus has joined #openstack-meeting-alt21:16
barrettWe could send out a doodle and see if the response aligns with the goal. Because some people get their emails bundled, we would need to leave the doodle open for a week. I'm concerned that we'd need to do this in Jan, which is getting a bit close to the event for making plans21:17
Arkady_KanevskyFor upgrade iser story that have been merge how do you want me comment on it? Updating Wwbapge is too entrusive. email on product reflector?21:17
* hughhalf notes mikal normally has a school run around this time, but will be back in about 60 minutes if you don't catch him now21:17
Arkady_Kanevskythanks hughhalf21:18
*** Aish has quit IRC21:18
Arkady_Kanevskydoodle wpork last time for midcycle planning.21:18
Shamailbarrett: I agree with this approach... It will still let us finalize location before the holidays if we send it out this week.21:18
barrettShamail - I'll be a pumpkin next week, can you take the action item to do this?21:18
ShamailSure thing21:19
barrettThanks21:19
Arkady_Kanevskyso what is the proposal for the place fore mid cycle in NA?21:19
*** jaosorior has left #openstack-meeting-alt21:19
kencjohnstonArkady_Kanevsky NA?21:19
ShamailTo clarify.... I will use doodle to vote for locations... The timing will probably align with ops summit in any case, right?21:19
Leong_North America?21:19
Arkady_KanevskyNorth America21:19
ShamailOr will we change timing if we don't do UK?21:20
barrett#action Shamail to send out Doodle to close on whether or not we can get sufficent attendance at a mid-cycle held in London 2/17 & 1821:20
barrettWe have more options on timing if we don't meet in UK21:20
*** e0ne has quit IRC21:20
kencjohnstonbarrett Shamail is it a doodle or a poll?21:20
Arkady_KanevskyI thought we want to try to have two. One in UK and one in North America.21:20
Leong_Also take into considerarion in case EWG was in Uk but Pwg in Us?21:20
ShamailPerfect.. (It will be a poll)21:20
*** jmckind has quit IRC21:21
barrettLeong: +121:21
MeganRLeong: +121:21
ShamailArkady_Kanevsky: not the plan yet, we can revisit if we get more active members.21:21
*** banix has joined #openstack-meeting-alt21:21
Shamailleong: +121:21
Arkady_KanevskyOK21:21
barrettarkady_kanevsky: Ideally we'd have 1. Travel budgets aren't likely able to support 2.21:21
* hughhalf nods at barrett 21:21
Arkady_Kanevsky+1 on doodle21:22
scohen1+2 on doodle21:22
*** baoli has quit IRC21:22
barrettOk - I think we have defined the path to closure. Shamail will let us know the results of the poll and we'll go from there.21:22
Leong_Ok21:22
Shamail+121:22
barrettAnything else on this one?21:22
barrettOK21:23
barrett#topic Revisiting CPL Assignments21:23
*** openstack changes topic to "Revisiting CPL Assignments (Meeting topic: Product Working Group)"21:23
barrettShamail - Can you lead this one?21:23
*** e0ne has joined #openstack-meeting-alt21:23
*** aginwala has joined #openstack-meeting-alt21:23
ShamailI have a couple of topics related to CPLs that will be a part of this discussion.  I'll start with the reassignment topic first.21:23
Shamailbarrett: sure thing21:23
ShamailBased on recent changes in responsibilities, we have three vacancies for CPLs (Neutron, Magnum, and Keystone).  We need to find new volunteers to act as CPL (cross-project liaison) for these projects?21:23
kencjohnstonShamail can I suggest that we de-prioritize Magnum, since it is not a core service?21:24
ShamailI'd also like to thank Mike Cohen and Sheena Gregson for helping out with these projects.  They will still be involved with PWG but can not keep the CPL roles.21:24
Shamailkencjohnston: +1, agreed21:24
sgordoni would actually be willing to look into taking magnum21:25
ShamailOthers?21:25
kencjohnstonI'm happy to serve as a spot CPL for Magnum if need be21:25
sgordonaligns with other work i have on my plate21:25
*** alex_xu has quit IRC21:25
ShamailThanks sgordon and kencjohnston ... Any preference between you two?21:25
kencjohnstonsure thing sgordon, I work closely with Adrian Otto and can do an intro if need be21:25
sgordonsure21:25
*** gariveradlt__ has quit IRC21:26
*** jmckind has joined #openstack-meeting-alt21:26
ShamailPerfect.  Thanks kencjohnston and sgordon21:26
Shamail#info sgordon is new CPL for magnum21:26
*** eilert has joined #openstack-meeting-alt21:26
ShamailAny one willing to help with keystone or neutron?  Those are rather important so I don't think we should leave them vacant for long...21:27
*** alex_xu has joined #openstack-meeting-alt21:27
Arkady_KanevskyI am CPL for Tempest and Rally. Where should I document the roadmap for these to track?21:27
*** dprince has quit IRC21:28
ShamailFurthermore, there are a lot of other projects that currently do not have a CPL from PWG.  I'll post the open projects on our mailing list to continue this conversation.  We'll list core services as priority in the ML thread21:28
barrettJust wondering - Is the issue for people to volunteer time or knowledge of the project?21:28
Arkady_KanevskyShamail, do we have wiki or webpage where we track CPLs?21:28
ShamailArkady_Kanevsky: I'll reach out to you on this topic... More important to also start joining the weekly meetings for those projects21:28
kencjohnstonbarrett My reluctance is for time21:28
ShamailYes (looking up the link)21:28
barrett#link: https://wiki.openstack.org/wiki/CrossProjectLiaisons21:29
Arkady_Kanevskyagree21:29
kencjohnstonI think I would struggle to attend appropriate meetings and stay up to speed21:29
ShamailThanks barrett21:29
pchadwickMy concern is time as well.21:29
kencjohnstonMaybe we should let the CPL priorities be determined by needs from the tracked User Stories?21:29
*** royoung has joined #openstack-meeting-alt21:30
*** akiskourtis has quit IRC21:30
Shamailkencjohnston: good idea, I was going to continue the topic on ML and I'll try to list of user story mapping in that thread.21:30
hughhalfGood call kencjohnston - taht would help us naturally prioritise21:30
kencjohnstonAlthought then you lose the general feedback loop from the Roadmap creation process because you wouldn't have CPLs established for all projects at all times21:30
barrettkencjohnston: +121:30
kencjohnstonShamail cool, thanks21:30
ShamailThere are a lot of other projects that currently do not have a CPL from PWG.  I'll post the open projects on our mailing list to continue this conversation.  Naturally, the core services and ones with user story implications would be listed as priority.21:30
ShamailCan you please assign the action item barrett?21:31
barrettShamail: +1. we're unlikely to be able to cover all of the projects21:31
ShamailLastly, can people who are CPLs currently give an update on whether they have been able to start attending the weekly time meeting for their project(s)?  I have been attending cinder meetings, but have missed the last 2-3.21:31
ShamailI'd like to also propose that we make this a regular agenda item, like user story updates, except less frequently (maybe once a month to start)... So that we can bring up relevant topics from the projects and update the team.21:31
pchadwickShamail - same here for Manila21:31
barrett#action Shamail send out an email to the ML call for CPLs, with a list of the projects currently identified as involved in a prioritized user story21:32
kencjohnstonShamail +1 on updates21:32
barrettShamail - Will do on the agenda21:32
ShamailThanks pchadwick21:32
rockygEverybody, if you miss the meetings, it's often worthwhile to review the logs for it.  Helps a lot.21:32
Shamailrockyg: +121:32
Arkady_Kanevsky+1 on shamail proposal21:32
MeganRDo we still need someone on the OpenStack Client meetings? I have been attending those, but don't see it listed on the Wiki/21:33
pchadwickrockyg - where are the logs?21:33
*** kfarr has quit IRC21:33
Shamail#link http://eavesdrop.openstack.org/irclogs/21:33
pchadwicknever mind - I just googled it.21:33
rockyghttp://eavesdrop.openstack.org/meetings21:33
*** mwagner_lap has quit IRC21:34
barrettMeganR: It's there..called OSClient21:34
rockygwhen this meeting ends, look at the links that get auto-posted.21:34
*** kzaitsev_mb has quit IRC21:34
barrett#link:  PWG list of CPLs https://wiki.openstack.org/wiki/CrossProjectLiaisons#Product_Working_Group21:34
rockygthen go up-tree a bit.  You can work your way back down.21:34
ShamailThat's all I had on this topic... We got magnum covered and hopefully we get coverage for neutron and keystone via ML21:35
MeganRbarrett: thank you, I was looking at the wrong section21:35
*** sdake has joined #openstack-meeting-alt21:35
ShamailI look forward to project updates, that will be really beneficial21:35
*** kzaitsev_mb has joined #openstack-meeting-alt21:36
ShamailAny comments, questions before we move on?21:36
barrettnope21:36
ShamailFloor is yours barrett :)21:36
barrettThanks21:36
barrett#topic User Story Updates21:37
*** openstack changes topic to "User Story Updates (Meeting topic: Product Working Group)"21:37
barrettDo any of the User Story owners have updates to share?21:37
kencjohnstonbarrett I posted a revision to Rolling Upgrades which contains Gaps Analysis text21:37
kencjohnston#link https://review.openstack.org/#/c/255633/21:37
Arkady_KanevskyDB hygiene have been merged. DItto for complex user scenarios21:37
barrettOk - let's start with Rolling Upgrades21:38
thingeeWhat is the goal of editing the rolling upgrades user stories. These kind of things are already being developered by various projects.21:38
*** korzen has joined #openstack-meeting-alt21:39
kencjohnstonthingee I agree most of the items are already inflight, the intent was to capture the entire "outcome" in one place21:39
sgordoni tend to agree with thingee here in as much as what is in the doc does not look so much like a use case21:39
sgordonas a list of items that are already being worked on21:39
thingeekencjohnston: got it21:39
*** e0ne has quit IRC21:40
*** dklenov has quit IRC21:40
barrettThe tracker should ideally contain what's underway as well as the gas21:40
barrettgaps21:40
rockygMight be worth putting links to bps, bugs, reviews in where things are in-flight21:40
kencjohnstonI will say that I still struggle to find the status of all the various items that are inflight21:40
Shamailkencjohnston: +1 and also helps keep additional details (like context, justification, etc.) to help share why it was tracked through PWG21:40
kencjohnstonrockyg I think that is the job of the tracker document21:40
ShamailThat will be the tracker21:40
thingeekencjohnston: yeah it's not easy, because some projects have bits and pieces that work towards the goal.21:40
rockygWhat Shamail said.  +121:40
kencjohnstonIn my mind 1) Gaps contains written form of gaps in context of high level use case21:41
kencjohnston2) Tracker contains specific work items happening across projects and releases21:41
thingeekencjohnston: it would help if CPL's communicate with projects on putting things under one topic branch in gerrit21:41
ShamailI was trying to get a template created by today but hopefully will submit patch tomorrow.21:41
thingeekencjohnston: so it's easy to spot the work happening21:41
Arkady_Kanevskyhttps://review.openstack.org/#/c/237178/ - closed (DB hygiene)21:41
Shamailthingee: that's a great idea21:41
kencjohnstonthingee Talk more about that...21:41
*** absubram has left #openstack-meeting-alt21:41
kencjohnstonAll projects would put work in the same named topic branch?21:42
rockygkencjohnston, +1.  thingee, talk...21:42
*** kzaitsev_mb has quit IRC21:42
*** cbouch has quit IRC21:42
thingeeso a lot of the times where we're doing cross project development, we put things under one topic branch. that way you can search by gerrit that topic branch and find things across different projects for the same initiative21:42
* thingee finds an example21:42
rockygdoes the branch span repos or we just name it the same in each?21:42
ShamailName it the same.21:42
rockygAnswered *my* question...Thanks!21:43
kencjohnstonthingee OK, I think I get it. I'll get a communication to the CPLs with that ask for rolling upgrades21:43
kencjohnstonCan someone take that action for me?21:43
thingeeso recently in OpenStack we rolled a new way for capturing release notes. The topic is called "add-reno" ... reno being the tool to capture release notes21:44
thingeehttps://review.openstack.org/#/q/topic:+add-reno,n,z21:44
thingeeso you can see all the projects integrating reno^21:44
Arkady_KanevskyAre we covering rolling upgrade in each project or one person responsible for it for all projects?21:44
Shamailthingee: this is a good addition to the workflow... Good thing is that everything is done via patch so the topic could show everything except blueprints.21:44
*** cknight has quit IRC21:44
*** barrett has quit IRC21:44
kencjohnstonArkady_Kanevsky All projects21:44
ShamailCode + specs would all show up.21:44
*** barrett has joined #openstack-meeting-alt21:45
*** alex_xu has quit IRC21:45
Shamailbarrett: can you please assign an action item to kencjohnston: "ask CPLs to share common branch topic with projects for rolling upgrades "21:46
barrettArkady_Kanevsky: CPLs cover all User Stories21:46
barrett#action kencjohnston ask CPLs to share common branch topic with projects for rolling upgrades21:46
thingeebarrett: can I get an action item to update the workflow doc for the topic branch addition?21:46
Arkady_Kanevskysorry for confusion. We have an owner of user story. That may span multiple projects.21:46
Arkady_KanevskyAnd we have CPL that tracks roadmap for individual project.21:47
barrett#Action Thingee Update workflow doc to include Topic Branch additions21:47
*** jecarey has quit IRC21:47
thingeethank you21:47
*** Sukhdev has joined #openstack-meeting-alt21:48
Arkady_KanevskySo who owns tracking a user story "blueprint" in specific project? CPL? story owner? or both?21:48
*** alex_xu has joined #openstack-meeting-alt21:48
thingeeArkady_Kanevsky: wait, there's a separate blueprint for the user story?21:48
ShamailCPL, but aggregated status is tracked by user story owner.21:48
barrettdoes anyone knowif the #commands are case sensitive?21:49
barrettAnything else on rolling upgrades?21:49
kencjohnstonbarrett none from me21:49
Arkady_KanevskyThe work in each individual project is driven by blueprints and specs.21:49
Shamailnot sure barrett21:49
thingeeThere should just be a user story, which can include the user stories if there is not spec. If there is a spec in a project, CPLs should be providing the user stories in a spec update.21:49
thingeethere should just be one blueprnt*21:49
Arkady_KanevskyOnce the user story is merged we either add blueprints and spec if they exsists in various projects to track it. Or create ones for each project21:50
Shamailbarrett: time check... 10 min21:50
thingeeArkady_Kanevsky: yeah I think we're on the same page21:50
Arkady_Kanevskysingle blueprint can not handle multiple projects21:51
*** Prem has quit IRC21:51
*** baoli has joined #openstack-meeting-alt21:51
thingeeArkady_Kanevsky: right, but a spec can21:51
*** korzen has quit IRC21:51
thingeeArkady_Kanevsky: http://specs.openstack.org/openstack/openstack-user-stories/workflow/workflow.html#cross-project-specifications21:51
thingeeeach blueprint should be listed in the cross-project spec21:52
Arkady_Kanevskyagree21:52
thingee:)21:52
ShamailAny other user story owners online?21:53
Arkady_Kanevskyeasier to track completion of all project dependent work for a user story if it in project specific blueprint or spec.21:53
*** barrett has quit IRC21:54
Shamailcloudrancher: ping21:54
*** barrett has joined #openstack-meeting-alt21:54
ShamailI don't think Deric and Jay are here21:55
Shamailsgordon: ping21:55
Arkady_Kanevskylooks like we are done early. No more calls till New year?21:55
*** jtomasek has quit IRC21:55
sgordonyo21:55
barrettWeird, the channel went away for a while for me...back now21:55
ShamailAny updates on Complex Instance?21:55
sgordonwe merged a thing, so that was nice21:55
barrettLast meeting of this year. Next one is 1/11.21:55
rockyg++21:55
Shamail:)21:55
Arkady_Kanevsky+221:55
sgordonnow i have to find the link again of course21:56
Arkady_KanevskyHappy Holidays to ALL21:56
*** barrett has quit IRC21:56
kencjohnstonand barrett is on sabatical right?21:56
thingeewould like to informally add an agenda item... going back a couple of meetings on whether we should have drafts or not?21:56
ShamailAre you now focusing on building out "add capacity" or gap analysis for Complex Instances?21:56
*** pchadwick has left #openstack-meeting-alt21:56
sgordon#link https://review.openstack.org/#/c/251442/21:56
sgordonyes21:56
*** sdake has quit IRC21:56
Leong_Carol on sabbatical, I will cover her21:56
ShamailYes kencjohnston, that is accurate... She will be on sabbatical21:56
*** kebray has quit IRC21:56
kencjohnstoncross talk thingee +121:56
ShamailYes = both sgordon ?21:57
rockygthingee, +1  Maybe add to next agenda?21:57
sgordonboth21:57
rockygIf we don't get to it.21:57
kencjohnstonalthough that might be a better discussion for our midcycle21:57
thingeerockyg: ok21:57
ShamailHi thingee... We'll add it21:57
ShamailWe have 3 min.. Defer to next meeting?21:57
*** barrett has joined #openstack-meeting-alt21:57
rockygsgordon, any ready for review yet?21:57
ShamailThanks sgordon21:57
barrettYes -  I think so21:58
kencjohnstonShamail I think we have to21:58
thingeeI would also like to remind that I think it would benefit us to start thinking of stuff we want for N release, and start putting that in the heads of project maintainers now21:58
*** sriram has quit IRC21:58
Arkady_Kanevskyagree. Post any new user story to review21:58
sgordonrockyg, we have been merging them as they come, the link is above...21:58
kencjohnstonthingee +121:58
thingeeand what resources we can bring forward from our respected companies on certain initiatives.21:58
barrettthingee: +121:58
ShamailAgreed.  We'll add it to 1/201621:58
barrettthingee: +121:58
ShamailDid we decide to skip 1/4?21:58
Shamailthingee: ++21:58
barrettshamail: Yes we did21:58
sgordoni believe we did21:58
ShamailOkay21:58
ShamailThaknks21:59
sgordonpeople anticipating some really good new years parties i guess21:59
ShamailThanks*21:59
sgordon;p21:59
* kencjohnston jumps to another call thanks all, Happy Holidays!21:59
ShamailLol sgordon21:59
barrettHappy Holiday folks - see ya next year!21:59
Arkady_Kanevskybye21:59
ShamailHappy holidays everyone!! Talk to you on the mailing list.21:59
barrett#endmeeting21:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:59
openstackMeeting ended Mon Dec 14 21:59:34 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2015/product_working_group.2015-12-14-21.01.html21:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2015/product_working_group.2015-12-14-21.01.txt21:59
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2015/product_working_group.2015-12-14-21.01.log.html21:59
*** scohen1 has left #openstack-meeting-alt21:59
rockygHave some great holidays!21:59
*** Shamail has quit IRC21:59
*** barrett has left #openstack-meeting-alt21:59
*** royoung has left #openstack-meeting-alt22:00
*** Leong_ has left #openstack-meeting-alt22:00
*** MeganR has quit IRC22:00
*** safchain has quit IRC22:00
*** rockyg has quit IRC22:00
*** kebray has joined #openstack-meeting-alt22:01
*** sdake has joined #openstack-meeting-alt22:02
*** jecarey has joined #openstack-meeting-alt22:06
*** julim has quit IRC22:08
*** merooeny_ has quit IRC22:08
*** Aish has joined #openstack-meeting-alt22:11
*** jecarey has quit IRC22:11
*** Mr_T has left #openstack-meeting-alt22:13
*** matrohon has quit IRC22:13
*** cknight has joined #openstack-meeting-alt22:13
*** aginwala has quit IRC22:14
*** vilobhmm11 has quit IRC22:14
*** vilobhmm11 has joined #openstack-meeting-alt22:15
*** vilobhmm11 has quit IRC22:16
*** vilobhmm11 has joined #openstack-meeting-alt22:16
*** vilobhmm11 has quit IRC22:16
*** vilobhmm11 has joined #openstack-meeting-alt22:17
*** vilobhmm11 has quit IRC22:17
*** vilobhmm11 has joined #openstack-meeting-alt22:17
*** vilobhmm11 has quit IRC22:18
*** vilobhmm11 has joined #openstack-meeting-alt22:18
*** aginwala has joined #openstack-meeting-alt22:22
*** ijw has quit IRC22:31
*** vilobhmm11 has quit IRC22:31
*** cknight has quit IRC22:31
*** vilobhmm11 has joined #openstack-meeting-alt22:31
*** rmoe_ has quit IRC22:32
*** rmoe has joined #openstack-meeting-alt22:33
*** mwagner_lap has joined #openstack-meeting-alt22:33
*** Arkady_Kanevsky has quit IRC22:34
*** kencjohnston has quit IRC22:37
*** vgridnev has quit IRC22:38
*** david-lyle has joined #openstack-meeting-alt22:39
*** tonytan4ever has quit IRC22:40
*** jckasper__ has joined #openstack-meeting-alt22:40
*** vilobhmm11 has quit IRC22:41
*** vilobhmm11 has joined #openstack-meeting-alt22:41
*** jmckind has quit IRC22:43
*** amitgandhinz has quit IRC22:45
*** weshay has quit IRC22:47
*** Arkady_Kanevsky has joined #openstack-meeting-alt22:49
*** Sukhdev has quit IRC22:50
*** MarkAtwood has joined #openstack-meeting-alt22:50
*** agireud has quit IRC22:50
*** diazjf has quit IRC22:51
*** Sukhdev has joined #openstack-meeting-alt23:00
*** vilobhmm11 has quit IRC23:01
*** vilobhmm11 has joined #openstack-meeting-alt23:01
*** kzaitsev_mb has joined #openstack-meeting-alt23:03
*** banix has quit IRC23:09
*** ashleighfarnham has quit IRC23:10
*** neiljerram has joined #openstack-meeting-alt23:10
*** kzaitsev_mb has quit IRC23:13
*** neiljerram has quit IRC23:16
*** iNeilus has quit IRC23:16
*** dave-mccowan has quit IRC23:20
*** sigmavirus24 is now known as sigmavirus24_awa23:22
*** sbalukoff has quit IRC23:22
*** xyang1 has quit IRC23:24
*** georgelorch has quit IRC23:25
*** georgelorch has joined #openstack-meeting-alt23:26
*** reed_ has joined #openstack-meeting-alt23:27
*** shobhar_ has joined #openstack-meeting-alt23:30
*** georgelorch has quit IRC23:32
*** kei_yama has joined #openstack-meeting-alt23:32
*** georgelorch has joined #openstack-meeting-alt23:32
*** Arkady_Kanevsky has quit IRC23:36
*** maxabidi has quit IRC23:44
*** aginwala has quit IRC23:51
*** Prem has joined #openstack-meeting-alt23:52
*** shobhar_ has quit IRC23:52
*** aginwala has joined #openstack-meeting-alt23:54
*** ashleighfarnham has joined #openstack-meeting-alt23:55
*** markvoelker has quit IRC23:55
*** iNeilus has joined #openstack-meeting-alt23:56
*** sdake_ has joined #openstack-meeting-alt23:58
*** sdake has quit IRC23:58

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