Monday, 2015-12-07

*** cknight has joined #openstack-meeting-alt00:00
*** vilobhmm11 has quit IRC00:09
*** kzaitsev_mb has joined #openstack-meeting-alt00:09
*** kzaitsev_mb has quit IRC00:22
*** dims has quit IRC00:25
*** dims has joined #openstack-meeting-alt00:26
*** jet-rongl has joined #openstack-meeting-alt00:29
*** dims has quit IRC00:35
*** salv-orlando has joined #openstack-meeting-alt00:37
*** kzaitsev_mb has joined #openstack-meeting-alt00:38
*** mestery_ has joined #openstack-meeting-alt00:40
*** mestery has quit IRC00:41
*** mestery_ is now known as mestery00:41
*** salv-orlando has quit IRC00:44
*** kzaitsev_mb has quit IRC00:51
*** kzaitsev_mb has joined #openstack-meeting-alt00:52
*** gjayavelu has joined #openstack-meeting-alt00:57
*** gjayavelu has quit IRC00:58
*** hoangcx has joined #openstack-meeting-alt00:58
*** kzaitsev_mb has quit IRC00:59
*** neilus has quit IRC01:00
*** shaohe_feng has joined #openstack-meeting-alt01:00
*** mestery has quit IRC01:01
*** mestery has joined #openstack-meeting-alt01:02
*** zhangjn has joined #openstack-meeting-alt01:08
*** jet-rongl has left #openstack-meeting-alt01:08
*** shaohe_feng has quit IRC01:10
*** hoangcx has left #openstack-meeting-alt01:12
*** gjayavelu has joined #openstack-meeting-alt01:12
*** kzaitsev_mb has joined #openstack-meeting-alt01:15
*** zhhuabj has joined #openstack-meeting-alt01:16
*** cknight has quit IRC01:18
*** kencjohnston has quit IRC01:21
*** kencjohnston has joined #openstack-meeting-alt01:21
*** tchaypo_cloud has quit IRC01:21
*** kzaitsev_mb has quit IRC01:22
*** kzaitsev_mb has joined #openstack-meeting-alt01:24
*** gjayavelu has quit IRC01:25
*** annp has joined #openstack-meeting-alt01:29
*** kzaitsev_mb has quit IRC01:29
*** kebray has joined #openstack-meeting-alt01:30
*** mestery has quit IRC01:30
*** kebray has quit IRC01:31
*** sdake has quit IRC01:31
*** tfukushima has joined #openstack-meeting-alt01:33
*** sdake has joined #openstack-meeting-alt01:33
*** sweston has quit IRC01:35
*** kebray has joined #openstack-meeting-alt01:35
*** wangqun has joined #openstack-meeting-alt01:36
*** mestery has joined #openstack-meeting-alt01:36
*** mestery has quit IRC01:37
*** mestery has joined #openstack-meeting-alt01:38
*** sylwesterB has joined #openstack-meeting-alt01:39
*** ganso has quit IRC01:40
*** sweston has joined #openstack-meeting-alt01:40
*** mestery has quit IRC01:40
*** mestery has joined #openstack-meeting-alt01:40
*** ganso has joined #openstack-meeting-alt01:41
*** tfukushima has quit IRC01:41
*** mestery_ has joined #openstack-meeting-alt01:42
*** hrybacki has quit IRC01:43
*** sylwesterB has quit IRC01:43
*** tfukushima has joined #openstack-meeting-alt01:44
*** hrybacki has joined #openstack-meeting-alt01:44
*** sdake has quit IRC01:50
*** neilus has joined #openstack-meeting-alt01:52
*** EricGonczer_ has joined #openstack-meeting-alt01:55
*** sdake has joined #openstack-meeting-alt01:55
*** aroma has quit IRC01:56
*** zhurong has joined #openstack-meeting-alt01:56
*** aroma has joined #openstack-meeting-alt01:56
*** neilus has quit IRC01:58
*** baoli has joined #openstack-meeting-alt02:06
*** hoangcx has joined #openstack-meeting-alt02:10
*** hoangcx has left #openstack-meeting-alt02:10
*** zhangjn has quit IRC02:10
*** EricGonczer_ has quit IRC02:12
*** ajmiller has quit IRC02:18
*** mestery has quit IRC02:23
*** mestery_ is now known as mestery02:23
*** zhurong has quit IRC02:24
*** baoli has quit IRC02:24
*** baoli has joined #openstack-meeting-alt02:25
*** zhurong has joined #openstack-meeting-alt02:25
*** baoli has quit IRC02:31
*** dave-mccowan has quit IRC02:33
*** baoli has joined #openstack-meeting-alt02:35
*** balajiiyer has joined #openstack-meeting-alt02:35
*** gcb has joined #openstack-meeting-alt02:45
*** dave-mccowan has joined #openstack-meeting-alt02:46
*** baoli has quit IRC02:50
*** baoli has joined #openstack-meeting-alt02:51
*** shwetaap has joined #openstack-meeting-alt02:52
*** tfukushima has quit IRC02:52
*** houming has joined #openstack-meeting-alt02:53
*** shwetaap has quit IRC03:00
*** shwetaap has joined #openstack-meeting-alt03:00
*** baoli has quit IRC03:01
*** zhangjn has joined #openstack-meeting-alt03:03
*** zhangjn has quit IRC03:03
*** zhangjn has joined #openstack-meeting-alt03:05
*** shaohe_feng has joined #openstack-meeting-alt03:06
*** zhurong has quit IRC03:12
*** crc32 has joined #openstack-meeting-alt03:13
*** zhangjn has quit IRC03:15
*** baoli has joined #openstack-meeting-alt03:19
*** baoli has quit IRC03:27
*** Poornima has joined #openstack-meeting-alt03:27
*** gongysh has quit IRC03:32
*** gongysh has joined #openstack-meeting-alt03:33
*** kencjohnston has quit IRC03:35
*** yamamoto has joined #openstack-meeting-alt03:35
*** gjayavelu has joined #openstack-meeting-alt03:37
*** gcb has quit IRC03:38
*** neilus has joined #openstack-meeting-alt03:41
*** gjayavelu has quit IRC03:41
*** gcb has joined #openstack-meeting-alt03:42
*** neilus has quit IRC03:47
*** gcb has quit IRC03:48
*** banix has quit IRC03:48
*** shaohe_feng has quit IRC03:50
*** gcb has joined #openstack-meeting-alt03:51
*** houming_ has joined #openstack-meeting-alt03:55
*** houming has quit IRC03:56
*** houming_ is now known as houming03:56
*** gcb has quit IRC03:56
*** dims has joined #openstack-meeting-alt04:03
*** wanghua has quit IRC04:03
*** lazy_prince has joined #openstack-meeting-alt04:06
*** gcb has joined #openstack-meeting-alt04:09
*** crc32 has quit IRC04:10
*** dave-mccowan has quit IRC04:12
*** vilobhmm11 has joined #openstack-meeting-alt04:12
*** crc32 has joined #openstack-meeting-alt04:13
*** vilobhmm111 has joined #openstack-meeting-alt04:20
*** vilobhmm11 has quit IRC04:23
*** zhangjn has joined #openstack-meeting-alt04:32
*** katyafervent is now known as katyafervent_awa04:33
*** dims has quit IRC04:34
*** sdake has quit IRC04:35
*** sdake has joined #openstack-meeting-alt04:35
*** neilus has joined #openstack-meeting-alt04:35
*** tfukushima has joined #openstack-meeting-alt04:37
*** cknight has joined #openstack-meeting-alt04:38
*** neilus has quit IRC04:40
*** tfukushima has quit IRC04:43
*** kzaitsev_ws has quit IRC04:45
*** vilobhmm111 has quit IRC04:50
*** vilobhmm11 has joined #openstack-meeting-alt04:50
*** sdake has quit IRC04:54
*** sdake has joined #openstack-meeting-alt04:55
*** vilobhmm11 has quit IRC04:55
*** sdake has quit IRC04:56
*** shaohe_feng has joined #openstack-meeting-alt05:04
*** shaohe_feng1 has joined #openstack-meeting-alt05:06
*** shaohe_feng has quit IRC05:09
*** chandankumar has joined #openstack-meeting-alt05:09
*** vahidh has joined #openstack-meeting-alt05:11
*** vahidh has quit IRC05:15
*** sylwesterB has joined #openstack-meeting-alt05:16
*** sylwesterB has quit IRC05:21
*** shaohe_feng has joined #openstack-meeting-alt05:23
*** shaohe_feng1 has quit IRC05:24
*** dims has joined #openstack-meeting-alt05:24
*** cknight has quit IRC05:30
*** neilus has joined #openstack-meeting-alt05:30
*** crc32 has quit IRC05:31
*** zhangjn has quit IRC05:33
*** sylwesterB has joined #openstack-meeting-alt05:33
*** neilus has quit IRC05:34
*** tfukushima has joined #openstack-meeting-alt05:35
*** tfukushima has quit IRC05:37
*** shaohe_feng1 has joined #openstack-meeting-alt05:39
*** shaohe_feng has quit IRC05:42
*** numans has joined #openstack-meeting-alt05:45
*** dims has quit IRC05:46
*** zhangjn has joined #openstack-meeting-alt05:49
*** amotoki_ has joined #openstack-meeting-alt05:54
*** sdake has joined #openstack-meeting-alt05:57
*** tfukushima has joined #openstack-meeting-alt06:00
*** hoangcx has joined #openstack-meeting-alt06:01
*** hoangcx has left #openstack-meeting-alt06:01
*** killer_prince has joined #openstack-meeting-alt06:03
*** jmcbride has quit IRC06:04
*** killer_prince has quit IRC06:05
*** zhangjn has quit IRC06:05
*** killer_prince has joined #openstack-meeting-alt06:05
*** lazy_prince has quit IRC06:06
*** zhangjn has joined #openstack-meeting-alt06:07
*** irenab has quit IRC06:08
*** lazy_prince has joined #openstack-meeting-alt06:09
*** killer_prince has quit IRC06:11
*** SridharG has joined #openstack-meeting-alt06:19
*** neilus has joined #openstack-meeting-alt06:24
*** neilus has quit IRC06:28
*** _nadya_ has joined #openstack-meeting-alt06:29
*** amotoki has quit IRC06:30
*** amotoki_ is now known as amotoki06:30
*** dims has joined #openstack-meeting-alt06:32
*** boris-42_ has quit IRC06:33
*** _nadya_ has quit IRC06:35
*** evgenyf has joined #openstack-meeting-alt06:35
*** dims has quit IRC06:45
*** irenab has joined #openstack-meeting-alt06:48
*** dims has joined #openstack-meeting-alt06:52
*** kebray has quit IRC06:55
*** vilobhmm11 has joined #openstack-meeting-alt06:57
*** killer_prince has joined #openstack-meeting-alt07:05
*** lazy_prince has quit IRC07:06
*** lazy_prince has joined #openstack-meeting-alt07:08
*** jtomasek has quit IRC07:10
*** killer_prince has quit IRC07:10
*** nkrinner has joined #openstack-meeting-alt07:13
*** _nadya_ has joined #openstack-meeting-alt07:17
*** jaypipes has joined #openstack-meeting-alt07:18
*** SridharG has quit IRC07:19
*** neilus has joined #openstack-meeting-alt07:20
*** wanghua has joined #openstack-meeting-alt07:22
*** sdake has quit IRC07:23
*** shaohe_feng1 has quit IRC07:27
*** neilus has quit IRC07:27
*** SridharG has joined #openstack-meeting-alt07:34
*** vilobhmm11 has quit IRC07:37
*** scheuran has joined #openstack-meeting-alt07:42
*** shaohe_feng has joined #openstack-meeting-alt07:42
*** safchain has joined #openstack-meeting-alt07:45
*** zeih has joined #openstack-meeting-alt07:48
*** bgaifullin has joined #openstack-meeting-alt07:54
*** vahidh has joined #openstack-meeting-alt07:54
*** shaohe_feng1 has joined #openstack-meeting-alt07:55
*** zhangjn has quit IRC07:55
*** shaohe_feng has quit IRC07:57
*** vahidh has quit IRC07:59
*** jprovazn has joined #openstack-meeting-alt08:02
*** tremble has joined #openstack-meeting-alt08:03
*** tremble has quit IRC08:03
*** tremble has joined #openstack-meeting-alt08:03
*** paul-carlton1 has joined #openstack-meeting-alt08:06
*** jichen has joined #openstack-meeting-alt08:09
*** ttx has joined #openstack-meeting-alt08:09
*** salv-orlando has joined #openstack-meeting-alt08:09
*** _nadya_ has quit IRC08:10
*** salv-orlando has quit IRC08:12
*** paul-carlton1 has quit IRC08:14
*** shakamunyi has quit IRC08:14
*** zhangjn has joined #openstack-meeting-alt08:16
*** _nadya_ has joined #openstack-meeting-alt08:20
*** _nadya_ has quit IRC08:21
*** oomichi has quit IRC08:22
*** iyamahat has joined #openstack-meeting-alt08:26
*** matrohon has joined #openstack-meeting-alt08:26
*** paul-carlton1 has joined #openstack-meeting-alt08:28
*** katyafervent_awa is now known as katyafervent08:30
*** e0ne has joined #openstack-meeting-alt08:31
*** neilus has joined #openstack-meeting-alt08:31
*** _nadya_ has joined #openstack-meeting-alt08:32
*** iyamahat has quit IRC08:33
*** zhangjn has quit IRC08:33
*** _nadya_ has quit IRC08:34
*** neilus has quit IRC08:36
*** sgotliv_ has quit IRC08:37
*** igordcard has joined #openstack-meeting-alt08:37
*** yamahata has joined #openstack-meeting-alt08:40
*** j___ has joined #openstack-meeting-alt08:41
*** evgenyf has quit IRC08:43
*** zhangjn has joined #openstack-meeting-alt08:46
*** zhangjn has quit IRC08:46
*** evgenyf has joined #openstack-meeting-alt08:53
*** e0ne has quit IRC08:55
*** [1]evgenyf has joined #openstack-meeting-alt08:57
*** mkoderer has quit IRC08:59
*** andreykurilin__ has joined #openstack-meeting-alt08:59
*** dizquierdo has joined #openstack-meeting-alt08:59
*** evgenyf has quit IRC08:59
*** [1]evgenyf is now known as evgenyf08:59
*** zhangjn has joined #openstack-meeting-alt09:00
*** mkoderer has joined #openstack-meeting-alt09:00
*** e0ne has joined #openstack-meeting-alt09:00
*** paul-carlton1 has quit IRC09:01
*** jichen has quit IRC09:02
*** egallen has joined #openstack-meeting-alt09:03
*** e0ne has quit IRC09:03
*** zhangjn has quit IRC09:04
*** gjayavelu has joined #openstack-meeting-alt09:04
*** neilus has joined #openstack-meeting-alt09:04
*** chandankumar has quit IRC09:06
*** gjayavelu has quit IRC09:09
*** zhangjn has joined #openstack-meeting-alt09:09
*** neilus has quit IRC09:09
*** zhangjn has quit IRC09:10
*** sdake has joined #openstack-meeting-alt09:11
*** bgaifullin has quit IRC09:12
*** zhangjn has joined #openstack-meeting-alt09:13
*** zhangjn has quit IRC09:13
*** SridharG has quit IRC09:15
*** tfukushima has quit IRC09:16
*** tfukushima has joined #openstack-meeting-alt09:16
*** tfukushima has quit IRC09:17
*** alex_didenko has quit IRC09:17
*** tfukushima has joined #openstack-meeting-alt09:17
*** egallen has quit IRC09:19
*** dizquierdo has quit IRC09:19
*** egallen has joined #openstack-meeting-alt09:20
*** chandankumar has joined #openstack-meeting-alt09:22
*** SridharG has joined #openstack-meeting-alt09:22
*** salv-orlando has joined #openstack-meeting-alt09:22
*** bgaifullin has joined #openstack-meeting-alt09:27
*** shaohe_feng1 has quit IRC09:28
*** shaohe_feng has joined #openstack-meeting-alt09:29
*** omartsyniuk has quit IRC09:29
*** oomichi has joined #openstack-meeting-alt09:32
*** zhangjn has joined #openstack-meeting-alt09:32
*** fzdarsky has joined #openstack-meeting-alt09:34
*** thomnico has joined #openstack-meeting-alt09:34
*** chandankumar_ has joined #openstack-meeting-alt09:37
*** SridharG has quit IRC09:37
*** jtomasek has joined #openstack-meeting-alt09:37
*** zhangjn has quit IRC09:40
*** chandankumar has quit IRC09:40
*** alex_didenko has joined #openstack-meeting-alt09:42
*** dklenov has joined #openstack-meeting-alt09:43
*** chandankumar_ is now known as chandankumar09:43
*** houming has quit IRC09:47
*** zhangjn has joined #openstack-meeting-alt09:47
*** zhangjn has quit IRC09:47
*** dims has quit IRC09:48
*** houming has joined #openstack-meeting-alt09:49
*** sgotliv_ has joined #openstack-meeting-alt09:54
*** e0ne has joined #openstack-meeting-alt09:56
*** MarkAtwood has joined #openstack-meeting-alt09:58
*** evgenyf has quit IRC10:04
*** evgenyf has joined #openstack-meeting-alt10:05
*** vgridnev has joined #openstack-meeting-alt10:06
*** SridharG has joined #openstack-meeting-alt10:11
*** annp has quit IRC10:13
*** dizquierdo has joined #openstack-meeting-alt10:14
*** egallen has quit IRC10:15
*** salv-orlando has quit IRC10:23
*** evgenyf has quit IRC10:28
*** shwetaap has quit IRC10:33
*** wangqun has quit IRC10:36
*** vahidh has joined #openstack-meeting-alt10:37
*** dklenov_ has joined #openstack-meeting-alt10:37
*** dklenov has quit IRC10:38
*** dklenov_ is now known as dklenov10:38
*** jaypipes has quit IRC10:39
*** jaypipes has joined #openstack-meeting-alt10:40
*** neilus has joined #openstack-meeting-alt10:40
*** vahidh has quit IRC10:41
*** kzaitsev_mb has joined #openstack-meeting-alt10:43
*** tellesnobrega_af is now known as tellesnobrega10:43
*** johnthetubaguy has quit IRC10:43
*** dizquierdo has quit IRC10:45
*** neilus has quit IRC10:46
*** johnthetubaguy has joined #openstack-meeting-alt10:49
*** _nadya_ has joined #openstack-meeting-alt10:52
*** artem_panchenko_ has left #openstack-meeting-alt10:54
*** dizquierdo has joined #openstack-meeting-alt11:00
*** matrohon has quit IRC11:07
*** sdake has quit IRC11:07
*** neiljerram has joined #openstack-meeting-alt11:07
*** igordcard_ has joined #openstack-meeting-alt11:09
*** igordcard has quit IRC11:11
*** evgenyf has joined #openstack-meeting-alt11:15
*** katyafervent is now known as katyafervent_awa11:17
*** katyafervent_awa is now known as katyafervent11:19
*** dklenov_ has joined #openstack-meeting-alt11:19
*** dklenov has quit IRC11:19
*** dklenov_ is now known as dklenov11:19
*** yamamoto has quit IRC11:21
*** shaohe_feng has quit IRC11:21
*** johnthetubaguy has quit IRC11:21
*** johnthetubaguy has joined #openstack-meeting-alt11:21
*** _nadya_ has quit IRC11:23
*** dklenov has quit IRC11:26
*** tfukushima has quit IRC11:28
*** dklenov has joined #openstack-meeting-alt11:28
*** Poornima has quit IRC11:34
*** igordcard__ has joined #openstack-meeting-alt11:35
*** dave-mccowan has joined #openstack-meeting-alt11:35
*** bogdando has quit IRC11:35
*** neilus has joined #openstack-meeting-alt11:35
*** igordcard_ has quit IRC11:37
*** jtomasek has quit IRC11:42
*** neilus has quit IRC11:43
*** sdake has joined #openstack-meeting-alt11:45
*** jtomasek has joined #openstack-meeting-alt11:45
*** jtomasek has quit IRC11:46
*** chandankumar has quit IRC11:47
*** jtomasek has joined #openstack-meeting-alt11:48
*** bogdando has joined #openstack-meeting-alt11:49
*** SridharG has left #openstack-meeting-alt11:50
*** Poornima has joined #openstack-meeting-alt11:52
*** SridharG has joined #openstack-meeting-alt11:56
*** timsim has quit IRC11:56
*** alexus is now known as alex_xu11:57
*** slagle has joined #openstack-meeting-alt11:57
*** timsim has joined #openstack-meeting-alt11:58
*** neilus has joined #openstack-meeting-alt12:02
*** slagle has quit IRC12:02
*** andreykurilin__ has quit IRC12:02
*** salv-orlando has joined #openstack-meeting-alt12:03
*** salv-orlando has quit IRC12:03
*** slagle has joined #openstack-meeting-alt12:03
*** salv-orlando has joined #openstack-meeting-alt12:04
*** yamamoto has joined #openstack-meeting-alt12:05
*** kzaitsev_mb has quit IRC12:05
*** dizquierdo has quit IRC12:06
*** neilus has quit IRC12:06
*** EvgenyF_ has joined #openstack-meeting-alt12:07
*** thomnico has quit IRC12:07
*** thomnico has joined #openstack-meeting-alt12:08
*** dims has joined #openstack-meeting-alt12:08
*** EvgenyF__ has joined #openstack-meeting-alt12:11
*** jaypipes has quit IRC12:12
*** Poornima has quit IRC12:13
*** sdake has quit IRC12:13
*** EvgenyF_ has quit IRC12:14
*** flaper87 has quit IRC12:17
*** flaper87 has joined #openstack-meeting-alt12:17
*** fnaval has quit IRC12:18
*** fnaval has joined #openstack-meeting-alt12:18
*** kzaitsev_mb has joined #openstack-meeting-alt12:20
*** houming has quit IRC12:21
*** kei_yama has quit IRC12:21
*** cdelatte has joined #openstack-meeting-alt12:22
*** banix has joined #openstack-meeting-alt12:22
*** tellesnobrega is now known as tellesnobrega_af12:24
*** tellesnobrega_af is now known as tellesnobrega12:27
*** banix has quit IRC12:29
*** timirnich_ has quit IRC12:36
*** timirnich has joined #openstack-meeting-alt12:37
*** baoli has joined #openstack-meeting-alt12:41
*** balajiiyer has quit IRC12:42
*** balajiiyer has joined #openstack-meeting-alt12:42
*** andymaier has joined #openstack-meeting-alt12:42
*** balajiiyer has quit IRC12:43
*** baoli_ has joined #openstack-meeting-alt12:43
*** baoli_ has quit IRC12:45
*** baoli_ has joined #openstack-meeting-alt12:46
*** andymaier has quit IRC12:46
*** baoli has quit IRC12:46
*** andymaier has joined #openstack-meeting-alt12:47
*** yamamoto has quit IRC12:47
*** chandankumar has joined #openstack-meeting-alt12:48
*** hoangcx has joined #openstack-meeting-alt12:48
*** amrith is now known as _amrith_12:50
*** hoangcx has quit IRC12:51
*** _amrith_ is now known as amrith12:52
*** neilus has joined #openstack-meeting-alt12:52
*** hoangcx has joined #openstack-meeting-alt12:54
*** hoangcx has quit IRC12:55
*** neilus has quit IRC12:56
*** yamamoto has joined #openstack-meeting-alt12:57
*** jdob has joined #openstack-meeting-alt12:58
*** chandankumar has quit IRC12:58
*** gcb has quit IRC12:58
*** yamamoto_ has joined #openstack-meeting-alt12:58
*** akuznetsov has joined #openstack-meeting-alt13:00
*** _nadya_ has joined #openstack-meeting-alt13:01
*** yamamoto has quit IRC13:02
*** akuznetsov has quit IRC13:05
*** wanghua_ has joined #openstack-meeting-alt13:05
*** wanghua has quit IRC13:05
*** wanghua_ is now known as wanghua13:05
*** EricGonczer_ has joined #openstack-meeting-alt13:06
*** rpodolyaka has quit IRC13:08
*** EricGonczer_ has quit IRC13:09
*** tlbr has quit IRC13:09
*** akuznetsov has joined #openstack-meeting-alt13:17
*** alyson_ has joined #openstack-meeting-alt13:20
*** balajiiyer has joined #openstack-meeting-alt13:24
*** alyson__ has joined #openstack-meeting-alt13:26
*** alyson_ has quit IRC13:27
*** alyson__ is now known as alyson_13:27
*** neilus has joined #openstack-meeting-alt13:28
*** jaypipes has joined #openstack-meeting-alt13:30
*** balajiiyer has quit IRC13:30
*** dprince has joined #openstack-meeting-alt13:30
*** neilus has quit IRC13:33
*** matrohon has joined #openstack-meeting-alt13:36
*** neelashah has joined #openstack-meeting-alt13:45
*** tlbr has joined #openstack-meeting-alt13:50
*** rpodolyaka has joined #openstack-meeting-alt13:50
*** neelashah has quit IRC13:51
*** boris-42_ has joined #openstack-meeting-alt13:52
*** cknight has joined #openstack-meeting-alt13:55
*** jaypipes_ has joined #openstack-meeting-alt13:55
*** jaypipes_ has quit IRC13:58
*** chandankumar has joined #openstack-meeting-alt13:58
lxslio/13:59
*** julim has joined #openstack-meeting-alt13:59
edleafelxsli: early bird?14:00
*** rsyed_away is now known as rsyed14:01
n0ano#startmeeting nova-scheduler14:01
openstackMeeting started Mon Dec  7 14:01:09 2015 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** dingboopt has joined #openstack-meeting-alt14:01
*** openstack changes topic to " (Meeting topic: nova-scheduler)"14:01
openstackThe meeting name has been set to 'nova_scheduler'14:01
n0anoanyone here (other than edleafe & lxsli ) to talk about the scheduler14:01
lxslibauzas: ping14:01
*** cdent has joined #openstack-meeting-alt14:02
johnthetubaguylurking, ish14:02
edleafelxsli: he's busy with ndipanov atm14:02
n0anoI wonder if jaypipes has that other meeting again14:03
cdento/14:03
*** thomnico has quit IRC14:03
*** yamamoto_ has quit IRC14:03
*** thomnico has joined #openstack-meeting-alt14:04
n0anocdent, welcome14:04
cdentthanks14:04
Yingxino/14:04
*** yamamoto has joined #openstack-meeting-alt14:04
n0anowell, let's start, might be a relatively quick meeting today14:04
n0ano#topic specs & BPs14:04
*** openstack changes topic to "specs & BPs (Meeting topic: nova-scheduler)"14:04
n0anoI see from the etherpad, https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking, that the only outstanding BP is one from jaypipes on request spec, is everyone else happy with their BPs14:05
*** neilus has joined #openstack-meeting-alt14:05
n0anoI guess we'll take silence as assent so I think the specs are under control, speak up if you have any concerns14:06
n0anomoving on14:07
n0ano#topic bugs14:07
*** openstack changes topic to "bugs (Meeting topic: nova-scheduler)"14:07
n0anonot much change in the bug list, if anything it's gotten one or two bugs added so we need to think about that14:08
n0anoI'm going to see if I can get the Intel team in San Antonio to look into the scheduler bug list, I need to talk to them this week14:08
YingxinI proposed 3 bugs just now14:08
Yingxinthink they are related to scheduler14:09
n0anoYingxin, you're supposed to clear them not add new ones :-)14:09
*** yamamoto has quit IRC14:09
cdentIf someone wants to (or can) point me to a bug or two related to the scheduler that might be a good starting point, that would be excellent.14:09
n0anoNP, they'll just have to be triaged to make sure that's correct14:09
edleafen0ano: there's a new guy on the SA Intel team I know from the Python world. Fresh to OpenStack.14:09
n0anocdent, start from here https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler14:09
edleafen0ano: I'd be happy to help him work on Scheduler bugs14:10
cdentYup, n0ano already  made it that far but the list is not short :)14:10
*** neilus has quit IRC14:10
n0anoedleafe, sure, feel free to reach out14:10
*** amrith is now known as _amrith_14:10
*** akuznetsov has quit IRC14:10
n0anocdent, feel free to scan the list and attack any bugs that looks interesting14:10
edleafen0ano: his name is Yarko - I assume he's the only Yarko there :)14:11
johnthetubaguyn0ano: sorry, got distracted there. Heads up on specs, we are in the freeze period for all specs now, so any other specs will need to apply for an exception ASAP14:11
n0anoedleafe, probably, we're pulling in some people from Poland so that is not that strange14:11
* bauzas waves late14:11
edleafen0ano: he's from Chicago :)14:11
* n0ano has to stop sterotyping :-)14:12
n0anojohnthetubaguy, the only one open is jaypipes and hopefully he's aware of the schedule, if not he will be now14:12
n0ano#action jaypipes to apply for exception on his request spec BP14:13
*** _nadya_ has quit IRC14:13
*** wanghua has quit IRC14:13
n0anoanyway, we have a list of bugs, please try and address any you can (and encourage others to look at our bug list)14:14
n0ano#opens14:14
n0ano#topic opens14:14
*** openstack changes topic to "opens (Meeting topic: nova-scheduler)"14:14
cdent✔14:14
n0anoso, anything new for today?14:14
*** neelashah has joined #openstack-meeting-alt14:14
*** EricGonczer_ has joined #openstack-meeting-alt14:15
* n0ano listening to crickets14:16
*** dims has quit IRC14:16
n0anoOK, for once I didn't jinx it and it was a short meeting14:16
jaypipesn0ano: you mean the resource-pools spec?14:16
Yingxinhttps://review.openstack.org/#/c/246476/ can I add this to https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking to get noticed?14:16
*** hogepodge has quit IRC14:17
n0anojaypipes, yes, that's the only one not striked out so and it has -1's, are you going to update it?14:17
YingxinIt implements the bp use stevedore for scheduler host manager14:17
*** weshay_xchat has joined #openstack-meeting-alt14:17
*** weshay_xchat is now known as weshay14:17
*** yamahata has quit IRC14:17
*** alaski has quit IRC14:17
n0anoYingxin, note johnthetubaguy comment about spec freeze, it'll probably require an exception14:17
YingxinIt is approved as specless14:18
*** chandankumar has quit IRC14:18
jaypipesn0ano: yes. I actually have broken the resource-providers spec out into smaller more consumable chunks. I will try to get all of the chunks pushed today.14:18
cdentchunks++14:18
n0anoYingxin, Oh, in that case you should be good, I don't see a problem adding it to the priorities page, we can take if off it's a problem.14:19
Yingxinn0ano: thanks14:19
n0anojaypipes, cool but it looks like you'll have to ask for an extension for it14:19
jaypipesn0ano: yes understood.14:20
n0anoanything else anyone?14:21
*** neelashah has quit IRC14:21
jaypipesn0ano: Moscow is cold.14:21
jaypipesthere, I said it.14:21
n0anojaypipes, actually I think that only true something like 10-11 months out of the year :-)14:22
*** mdbooth_ has joined #openstack-meeting-alt14:22
edleafejaypipes: controversial~14:22
edleafes/~/!14:22
jaypipeshehe14:22
*** cknight has quit IRC14:22
*** irenab has quit IRC14:22
n0anoOK, tnx everyone, we'll talk again next week14:22
*** merooney has joined #openstack-meeting-alt14:23
n0ano#endmeeting14:23
*** openstack changes topic to "Bugs (Meeting topic: neutron_dvr)"14:23
openstackMeeting ended Mon Dec  7 14:23:08 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2015/nova_scheduler.2015-12-07-14.01.html14:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2015/nova_scheduler.2015-12-07-14.01.txt14:23
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2015/nova_scheduler.2015-12-07-14.01.log.html14:23
*** mdbooth has quit IRC14:23
*** bauzas has quit IRC14:23
*** zynzel has quit IRC14:23
*** matrohon has quit IRC14:23
*** ttx has quit IRC14:23
*** bauzas has joined #openstack-meeting-alt14:23
*** mdbooth_ is now known as mdbooth14:23
*** Leom has joined #openstack-meeting-alt14:24
bauzasmeh I had some network blip14:24
*** matrohon has joined #openstack-meeting-alt14:24
*** ttx has joined #openstack-meeting-alt14:24
bauzasn0ano: jaypipes: cdent: sorry I was just chatting, but I had a network issue14:25
n0anobauzas, bummer, did you have anything else (maybe we can raise it on the ML if necessary)14:25
*** banix has joined #openstack-meeting-alt14:25
bauzas(15:17:33) bauzas: n0ano: s/request spec/resource providers/ spec14:25
bauzas(15:17:48) bauzas: n0ano: tbc, we're talking about resource usage, not request data :)14:25
bauzas(15:18:14) bauzas: cdent: something is missing that I think you could help14:25
bauzas(15:18:28) bauzas: cdent: atm, we don't do functional testing on all the filters combinations14:25
bauzas(15:19:03) bauzas: cdent: we only rely on some tempest testing for the default filters + the standard config14:25
bauzasn0ano:  ^14:25
bauzascdent: ^14:26
cdentright on bauzas, that seems like a good idea14:26
bauzascdent: I had a local venv for that but that's basically a POC14:27
*** zynzel has joined #openstack-meeting-alt14:27
cdenttell me more over openstack-nova?14:27
bauzasack14:27
n0anobauzas, I think jaypipes is restrucuring that BP so it'll probably all change slightly14:27
jaypipesbauzas: just breaking it into smaller pieces.14:28
bauzasjaypipes: yup, I saw, you referring to the PCI work ?14:29
*** pballand has quit IRC14:29
jaypipesbauzas: actually, no... I broke out the resource classes, generic resource pools, and RESTful API changes into separate specs and narrowed the resource-providers spec to just the work of handling inventory management...14:30
*** lazy_prince has quit IRC14:31
*** yamahata has joined #openstack-meeting-alt14:32
*** superdan is now known as dansmith14:32
*** dims has joined #openstack-meeting-alt14:34
*** dizquierdo has joined #openstack-meeting-alt14:40
*** kebray has joined #openstack-meeting-alt14:41
*** yamamoto has joined #openstack-meeting-alt14:41
*** ajmiller has joined #openstack-meeting-alt14:42
*** raginbajin has quit IRC14:44
*** evgenyf has quit IRC14:44
*** chandankumar has joined #openstack-meeting-alt14:44
*** fawadkhaliq has joined #openstack-meeting-alt14:44
*** cdent has quit IRC14:45
*** EvgenyF__ has quit IRC14:45
*** amitgandhinz has joined #openstack-meeting-alt14:45
*** raginbajin has joined #openstack-meeting-alt14:46
*** balajiiyer has joined #openstack-meeting-alt14:46
*** amitgandhinz has quit IRC14:47
*** numans has quit IRC14:47
*** amitgandhinz has joined #openstack-meeting-alt14:47
*** EvgenyF__ has joined #openstack-meeting-alt14:48
*** ajmiller has quit IRC14:48
*** evgenyf has joined #openstack-meeting-alt14:48
*** gcb has joined #openstack-meeting-alt14:50
*** jprovazn has quit IRC14:53
*** cknight has joined #openstack-meeting-alt14:54
*** alaski has joined #openstack-meeting-alt14:55
*** c00p3r has quit IRC14:56
*** _amrith_ is now known as amrith14:56
*** c00p3r has joined #openstack-meeting-alt14:57
*** mwagner_lap has quit IRC14:57
*** neelashah has joined #openstack-meeting-alt14:57
*** roaet has joined #openstack-meeting-alt14:57
*** bgaifullin_ has joined #openstack-meeting-alt14:58
*** nelsnelson has joined #openstack-meeting-alt14:58
*** yamamoto has quit IRC14:59
sc68calHi all15:00
roaethi15:00
sc68cal#startmeeting neutron_upgrades15:00
openstackMeeting started Mon Dec  7 15:00:37 2015 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"15:00
openstackThe meeting name has been set to 'neutron_upgrades'15:00
*** carl_baldwin_ has joined #openstack-meeting-alt15:00
sc68calIhar is off this week and asked me to run the meeting in his absence15:00
roaetthanks sc68cal15:01
sc68cal#link https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam#Agenda Agenda15:01
*** bgaifullin has quit IRC15:01
sc68calIhar updated the agenda section on friday before he left15:02
*** jmcbride has joined #openstack-meeting-alt15:02
*** dims has quit IRC15:02
sc68cal#topic Announcements15:03
*** openstack changes topic to "Announcements (Meeting topic: neutron_upgrades)"15:03
*** yamamoto has joined #openstack-meeting-alt15:03
*** mhickey has joined #openstack-meeting-alt15:03
sc68calpartial multinode grenade has hit a snag where we are seeing issues with the initial resource creation phase15:04
*** sdake has joined #openstack-meeting-alt15:04
sc68calso, we need to resolve the bugs so that the job can actually get to the upgrade phase15:05
*** irenab has joined #openstack-meeting-alt15:05
sc68calihar put some notes down for the OVO pieces - the good news is no spec needed, RFE may not be needed; devref documenting conversion process is required; one or two objects to be chosen for Mitaka cycle15:06
sc68calanyone else have any announcements?15:07
*** absubram has quit IRC15:08
roaetnot i15:09
*** sdake has quit IRC15:09
mhickeyno15:10
*** korzen has joined #openstack-meeting-alt15:10
sc68calI don't see rossella on, but a patch has been posted for her work piece https://review.openstack.org/#/c/253641/15:11
*** kzaitsev_mb has quit IRC15:11
sc68cal#topic Open Discussion15:12
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_upgrades)"15:12
sc68calIt seems a little dead today15:13
*** yamamoto has quit IRC15:13
*** banix has quit IRC15:13
*** hogepodge has joined #openstack-meeting-alt15:14
roaeta little15:14
*** spotz_zzz is now known as spotz15:15
*** _nadya_ has joined #openstack-meeting-alt15:15
*** kencjohnston has joined #openstack-meeting-alt15:15
*** kebray has quit IRC15:15
*** kencjohnston has quit IRC15:15
*** sdake has joined #openstack-meeting-alt15:15
*** kebray has joined #openstack-meeting-alt15:16
*** Leom has quit IRC15:17
*** Leom has joined #openstack-meeting-alt15:18
*** tonytan4ever has joined #openstack-meeting-alt15:19
sc68calyep it seems pretty dead. I think we'll go ahead and wrap up for the day15:19
roaetthanks for running it anywho sc68cal15:19
*** snackewm has joined #openstack-meeting-alt15:19
sc68calroaet: thanks :)15:19
sc68calsee you all next week!15:20
*** shwetaap has joined #openstack-meeting-alt15:20
sc68cal#endmeeting15:20
*** openstack changes topic to "Bugs (Meeting topic: neutron_dvr)"15:20
openstackMeeting ended Mon Dec  7 15:20:12 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2015/neutron_upgrades.2015-12-07-15.00.html15:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2015/neutron_upgrades.2015-12-07-15.00.txt15:20
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2015/neutron_upgrades.2015-12-07-15.00.log.html15:20
*** sigmavirus24_awa is now known as sigmavirus2415:22
*** delattec has joined #openstack-meeting-alt15:23
*** cdelatte has quit IRC15:26
*** mtanino has joined #openstack-meeting-alt15:27
*** zz_dimtruck is now known as dimtruck15:31
*** kzaitsev_mb has joined #openstack-meeting-alt15:31
*** korzen has quit IRC15:32
*** jichen has joined #openstack-meeting-alt15:32
*** kfarr has joined #openstack-meeting-alt15:33
*** Leom_ has joined #openstack-meeting-alt15:35
*** Leom has quit IRC15:36
*** korzen has joined #openstack-meeting-alt15:36
*** julim has quit IRC15:37
*** nkrinner has quit IRC15:37
*** shwetaap has quit IRC15:38
*** zeih has quit IRC15:38
*** julim has joined #openstack-meeting-alt15:40
*** shwetaap has joined #openstack-meeting-alt15:40
*** neilus has joined #openstack-meeting-alt15:40
*** korzen has quit IRC15:40
*** jaypipes has quit IRC15:41
*** rvyalov_ has joined #openstack-meeting-alt15:42
*** Leom has joined #openstack-meeting-alt15:43
*** alyson_ has quit IRC15:43
*** xyang1 has joined #openstack-meeting-alt15:44
*** neilus has quit IRC15:44
*** vgridnev has quit IRC15:44
*** Sukhdev has joined #openstack-meeting-alt15:45
*** Leom_ has quit IRC15:46
*** sylwesterB has quit IRC15:47
*** alyson_ has joined #openstack-meeting-alt15:47
*** dave-mccowan has quit IRC15:47
*** iyamahat has joined #openstack-meeting-alt15:48
*** SridharG has quit IRC15:48
*** sylwesterB has joined #openstack-meeting-alt15:48
*** jprovazn has joined #openstack-meeting-alt15:49
*** johnsom_ has joined #openstack-meeting-alt15:49
*** kencjohnston has joined #openstack-meeting-alt15:50
*** fawadkhaliq has quit IRC15:51
*** sylwesterB has quit IRC15:53
*** ddmitriev has quit IRC15:54
*** kencjohnston has quit IRC15:56
*** harlowja_at_home has joined #openstack-meeting-alt15:58
*** EvgenyF__ has quit IRC15:59
*** evgenyf has quit IRC15:59
harlowja_at_home#startmeeting oslo16:00
openstackMeeting started Mon Dec  7 16:00:20 2015 UTC and is due to finish in 60 minutes.  The chair is harlowja_at_home. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: oslo)"16:00
amrith./16:00
openstackThe meeting name has been set to 'oslo'16:00
johnsom_o/16:00
harlowja_at_homehowdy16:00
bknudsonhi16:00
ozamiatino/16:00
rpodolyakao/16:00
harlowja_at_home(let's see if dims shows up, he's traveling so I might be taking over, but he said he might be on)16:00
gcbo/16:00
*** dave-mccowan has joined #openstack-meeting-alt16:01
harlowja_at_homecourtesy ping for GheRivero, amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dougwig, e0ne, flaper87, garyk, haypo,16:01
dhellmanno/16:01
harlowja_at_homecourtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, ozamiatin, redrobot, rpodolyaka, spamaps16:01
*** haypo has joined #openstack-meeting-alt16:01
harlowja_at_homeok, i guess we'll just see if dims arrives late, if not thats ok to16:01
haypohello16:01
harlowja_at_homehola16:01
harlowja_at_home#topic Red flags for/from liaisons16:02
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"16:02
johnsom_This just popped up on my radar, so I haven't had time to search, is oslo going to go through and rename tenant->project like neutron is doing?  i.e. oslo_context16:02
rbradforo/16:02
bknudsonNothing from keystone as far as I know16:02
harlowja_at_homejohnsom_, seems like we should, how about we bring that up in a little16:02
* amrith listens intently to the answer to johnsom_ question as it would impact Trove.16:03
johnsom_Otherwise I don't have anything16:03
amrithI have a question re: oslo.db and downgrades16:03
amrithbut that's not a 'red flag'16:03
harlowja_at_home:)16:03
amrithI will wait.16:03
harlowja_at_homeso seems like nothing to raise, which is great :)16:04
harlowja_at_homeless red the better :-P16:04
harlowja_at_home#topic Releases for Mitaka16:04
*** openstack changes topic to "Releases for Mitaka (Meeting topic: oslo)"16:04
harlowja_at_homeso dims seems to have put up https://review.openstack.org/#/c/253860/16:04
*** snackewm has quit IRC16:05
harlowja_at_homeso check that out if you need a release, or if you don't need one...16:05
harlowja_at_homeseems like dhellmann wanted confirmation about 2.6 dropping on some of those, hopefully that got resolved though (but just incase folks check that out)16:06
*** mwagner_lap has joined #openstack-meeting-alt16:06
dhellmannyep, I'm happy with that. I left the request there for dims to process, but I can do it if he'd like since he's traveling16:06
*** jecarey has joined #openstack-meeting-alt16:06
harlowja_at_homecool16:07
haypogcb: ^^16:07
bknudsonwe do a lot of releases.16:07
gcbhaypo, yes will do that better16:08
haypodhellmann: if i recall correctly, recent 2.6 changes were restricted to unit tests16:08
gcband remove python 2.6 work around16:08
harlowja_at_homebknudson, we def do16:08
dhellmannhaypo : yes, that has been confirmed. I asked for more descriptive commit messages in the future to cut down on the heart-attack factor when reviewing release requests ;-)16:08
harlowja_at_homelol16:08
*** Leom has quit IRC16:09
*** pballand has joined #openstack-meeting-alt16:09
*** jungleboyj has joined #openstack-meeting-alt16:09
*** Guest69903 is now known as cfouts16:09
jungleboyjHello all.16:09
harlowja_at_homejungleboyj, hello16:09
*** Leom has joined #openstack-meeting-alt16:09
harlowja_at_home#topic Rename tenant->project idea16:10
*** openstack changes topic to "Rename tenant->project idea (Meeting topic: oslo)"16:10
bknudsonoslo_context should use tenant rather than project16:10
harlowja_at_homejohnsom_, so whats the whole status of this discussion16:10
johnsom_Ha!  Not my idea, but trying to keep up.16:10
bknudsonI was embarrassed to propose use of oslo_context to keystone since it used tenant :(16:11
dhellmannto change that we'll have to add an alias in one direction or the other so that both names work16:11
johnsom_Neutron is going through and re-naming tenant->project.  I don't have the background link handy.  We were updating Octavia and noticed some of the oslo APIs use tenant.16:11
johnsom_We were just wondering if those are going to change and if so when.16:12
johnsom_dhellmann +116:12
hayposorry, i don't know the plan. do you (who?) want to *drop* the tenant name, or just make an alias?16:12
bknudsonas far as I know nobody proposed the change yet. it's on my todo list (not that I'll likely ever get to it)16:13
harlowja_at_homehttp://docs.openstack.org/developer/debtcollector/api.html#debtcollector.moves.moved_read_only_property (could be the alias mechanism)?16:13
*** xyang1 has quit IRC16:13
harlowja_at_homeanyone know how many places use tenant though, probably useful to figure that out also and see how to address each place16:13
rbradforbknudson, I'm happy to pick it up from your list.16:13
bknudson(it's not documented as read-only)16:13
dhellmannhaypo : other teams are trying to standardize on "project" apparently (we seem to change this every other year or so)16:13
*** absubram has joined #openstack-meeting-alt16:13
harlowja_at_homeok http://docs.openstack.org/developer/debtcollector/api.html#debtcollector.moves.moved_property bknudson i guess that then :-P16:13
dhellmannhaypo : for us to support that, we would have to produce releases that used both names, then deprecate tenant over some period of time16:14
*** cdelatte has joined #openstack-meeting-alt16:14
bknudsonjust use the moved_property decorator if you can16:14
rbradfordhellmann, what would you consider as length of deprecation, after M?16:14
dhellmannunless someone is really excited about doing that work, I think I'd put it off to see how far the migration gets in other projects16:14
*** delattec has quit IRC16:15
*** sbalukoff has quit IRC16:15
*** bgaifullin_ has quit IRC16:15
* harlowja_at_home remembers back in the day when this was brought up like 3 years ago, ha16:15
harlowja_at_homeoh the good ole days16:15
harlowja_at_homelol16:15
gcbDo we need a openstack-spec for that ?16:15
dhellmannrbradfor : well, lifeless wants "never break the API" so maybe "forever"? but we have standard rollout requirements for removing deprecated things http://governance.openstack.org/reference/tags/assert_follows-standard-deprecation.html16:15
*** jaypipes has joined #openstack-meeting-alt16:16
johnsom_#link http://article.gmane.org/gmane.comp.cloud.openstack.devel/70846/match=rename+tenant+project+discussion16:16
bknudsonwe need to leave it there for all supported releases, so when M goes out of support16:16
johnsom_That seems to be the start of the recent neutron thread on the topic16:16
*** tremble has quit IRC16:16
harlowja_at_homejohnsom_, thanks16:16
dhellmannbknudson : ++16:16
bknudson... so I think that means can be removed in the P release16:17
dhellmannbknudson : assuming all consuming projects have been updated16:17
harlowja_at_homeso i'm somewhat agreed with dhellmann if someone really is itching to do this work, sure, but it also might be worthwhile to let that ML discussion bake a little more?16:17
dhellmannyeah, let's keep an eye on this but not jump right on it16:17
bknudsonI'll get around to it eventually if nobody else does16:17
harlowja_at_home(i've also seen the project/tenant renaming toggle for the last 3-4 years, ha)16:17
dhellmannsomeone should come up with a 3rd word so we can stop toggling back and forth16:18
harlowja_at_homebknudson,  fair enough, if rbradfor u want to, thats ok to16:18
harlowja_at_homedhellmann, protenant16:18
bknudsonif rbradfor does it I'll be happy to review16:18
rbradforharlowja_at_home, bknudson happy to monitor ML discussion and take this on.16:19
harlowja_at_hometenaproj16:19
bknudsonwe switched keystone to use unicorn for a while16:19
harlowja_at_home:)16:19
*** j___ has quit IRC16:19
*** sneti has joined #openstack-meeting-alt16:19
harlowja_at_homerbradfor, cool, feel free :)16:19
bknudsonhttps://review.openstack.org/#/c/97838/16:20
harlowja_at_homelol16:20
rbradforlol16:20
harlowja_at_homenice16:20
*** kzaitsev_mb has quit IRC16:20
harlowja_at_home#topic oslo.db and downgrades16:21
*** openstack changes topic to "oslo.db and downgrades (Meeting topic: oslo)"16:21
harlowja_at_homeamrith, yt16:21
harlowja_at_homewhat did u want to bring up?16:21
harlowja_at_homeok guess we'll have to skip that :)16:22
amrithyes16:22
amritham here, was looking for a link16:22
harlowja_at_homeah16:22
harlowja_at_homekk16:22
amrithcan't find it now16:22
amrithit is about the cross project spec16:22
amrithre: downgrades16:22
amrithI was wondering whether all projects are doing this16:23
amrithand whether oslo.db couldn't just handle it16:23
bknudsonkeystone doesn't support downgrades16:23
dhellmann#link http://specs.openstack.org/openstack/openstack-specs/specs/no-downward-sql-migration.html16:23
amrithwithout a change in the projects.16:23
rpodolyakaamrith: I believe you would still need to update the projects code16:23
rpodolyakae.g. to modify CLI16:23
dhellmannI think the spec is just "stop doing downgrades" right? Do we have to change any code?16:24
*** fawadkhaliq has joined #openstack-meeting-alt16:24
amrithhttps://review.openstack.org/#/c/152337/16:24
amrithso there's code change16:24
bknudsonlooks like we've got some code for it: http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/sql/migration_helpers.py#n15216:24
*** kzaitsev_mb has joined #openstack-meeting-alt16:24
amrithand we have to remove all the downgrade actions16:24
amrithI was wondering (a) whether that is required and (b) whether there's abetter way16:24
amrithhere are mor elinks16:25
amrithmore links16:25
amrith.. [1] https://review.openstack.org/#/c/152337/16:25
amrith.. [2] https://review.openstack.org/#/c/167554/216:25
amrith.. [3] https://review.openstack.org/#/c/167834/16:25
amrith.. [4] https://review.openstack.org/#/c/167189/216:25
amrith.. [5] https://review.openstack.org/#/c/165740/16:25
*** kzaitsev_mb has quit IRC16:25
amrithI get these from a trove spec https://review.openstack.org/#/c/252477/16:25
*** kzaitsev_mb has joined #openstack-meeting-alt16:25
amrithI'm wondering why each project must do this; shouldn't there be an easier and more centralized way of handling this16:25
amrithsay, in OSLO?16:25
amriththat's the question.16:25
harlowja_at_homeseems like a decent question16:26
harlowja_at_homeperhaps http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/sql/migration_helpers.py#n152 should live in oslo.db ?16:26
rbradforamrith, I am not part of this discussion but as a person with some large RDBMS experience, removing downgrades is a bad idea. Restore to a known backup has multiple failure points.16:26
amrithRon, hello16:26
amrithI think you know who I am ;)16:26
rbradforamrith, of course!16:27
bknudsonamrith: what code?16:27
amrithI'm asking with my Trove hat, not with a "database guy" hat16:27
*** thomnico has quit IRC16:27
rpodolyakaamrith: harlowja_at_home: so I'd leave this to projects.  IMO, oslo.db should allow one to do downgrades. as it's a library16:27
harlowja_at_homerpodolyaka, ya its a tough thing to have oslo.db enforce16:27
amriththat's the point rpodolyaka ... if the TC feels that downgrades are not a good idea, why wouldn't oslo.db enforce it?16:28
bknudsonthere's a work item in the spec that says to upgrade oslo.db to return errors on downgrade16:28
dhellmannI think we could eventually drop something in oslo.db but as rpodolyaka says we want oslo libs to enable the projects to support the features they want to have16:28
*** neilus has joined #openstack-meeting-alt16:28
bknudsonif oslo.db added something we could use it in keystone16:28
harlowja_at_homebknudson, right, or maybe its a variation of that thing in keystone, not sure16:28
amrithI feel that operationally, projects and deployers are being put in an awkward situation by this change to declare downgrades as "bad".16:28
dhellmannamrith : the spec is not "do not ever do downgrades" it says "downgrades do not need to be supported"16:29
dhellmannso it's up to the project teams to decide whether they want to support downgrades or not16:29
rpodolyaka+16:29
amrithdhellmann, this may be semantic16:29
amrithbut the cross project spec states:16:29
amrith* Stop support of migrations with downgrade functions across all16:29
amrith  projects16:29
harlowja_at_homeamrith, for that discussion, it would probably be better on the ML, i don't necessarily disagree, but undoing http://specs.openstack.org/openstack/openstack-specs/specs/no-downward-sql-migration.html is another can of worms :)16:29
amrithI read that as a TC mandate that projects should not support downgrade16:29
rpodolyaka:)16:30
*** sgotliv_ has quit IRC16:30
amrithand since the listed alternative (which is dismissed) is that "Downgrade paths can continue to be supported."16:30
harlowja_at_homei'm not saying it can't be undone, its just ummm, a much bigger thing that i'm pretty sure oslo can't resolve :)16:30
amrithI interpret it to mean that downgrades SHALL NOT be supported.16:30
*** armax has quit IRC16:31
*** kevinbenton has quit IRC16:31
*** Prem__ has joined #openstack-meeting-alt16:31
dhellmannamrith : ok, I didn't read it as such a strongly worded thing. Regardless, I don't think we need oslo.db to enforce that.16:31
amrithOK, thanks16:31
amrithso it is up to the projects to do it. thanks!16:31
*** Prem__ is now known as Prem16:31
*** kevinbenton has joined #openstack-meeting-alt16:31
amrithwill let the guy submitting the code go ahead in that case, and not hold it up expecting an oslo.db solution. that's the (actually, a) resolution I was looking for16:31
*** EricGonc_ has joined #openstack-meeting-alt16:31
harlowja_at_homeamrith, i think so (and if u feel that the spec should be undone, def start that discussion, software isn't frozen in time)16:31
bknudsonsince we're going to try supporting rolling upgrades in keystone maybe we can do downgrades in a limited way16:32
bknudsonas in, you can downgrade as long as you haven't started any new keystones16:32
amrithharlowja_at_home, bknudson ... I cannot credibly speak as the voice of deployers since I'm not one, and don't play one on TV. I'm sure they have a voice and if and when they feel this is important they will raise it.16:32
harlowja_at_homeit will always be a tradeoff imho, downgrades, upgrades, correctness of either, where will people spend the time to ensure it works...16:32
harlowja_at_homewell what do u play on TV?16:33
bknudsonmfisch is an operator and is a co-author of the no-downgrades spec16:33
*** _nadya_ has quit IRC16:33
amrithI got an answer, I'm fine with moving on. On TV I play politician (also in real life).16:33
amrithtrue: am elected16:33
harlowja_at_homedonald is that u16:33
* amrith searches for hair piece.16:34
harlowja_at_homeha16:34
amrithfyi: donald is not elected.16:34
amrithso no.16:34
harlowja_at_homelol16:34
harlowja_at_homeok, moving on16:34
amriththanks!16:34
harlowja_at_homenp16:34
harlowja_at_home#topic Open oslo-specs16:34
*** openstack changes topic to "Open oslo-specs (Meeting topic: oslo)"16:34
harlowja_at_homesooo just wanted to bring any needed attention to any oslo specs if needed16:35
harlowja_at_home#link https://review.openstack.org/#/q/project:openstack/oslo-specs,n,z16:35
*** alex_xu has quit IRC16:35
*** EricGonczer_ has quit IRC16:35
harlowja_at_homemore eyes/views on  https://review.openstack.org/#/c/247902/ i think would be good16:35
harlowja_at_home'Replace incubator with unstable libraries.'16:35
harlowja_at_homealso I think https://review.openstack.org/#/c/226157/ is nice for oslo folks to look at16:36
harlowja_at_homein general its the larger openstack spec for backwards compat by lifeless16:36
*** vgridnev has joined #openstack-meeting-alt16:36
*** snackewm has joined #openstack-meeting-alt16:36
harlowja_at_homeand i think the creator(s) wanted to ensure oslo folks read over it espeically16:36
harlowja_at_home'Backwards compat for libraries and clients.'16:37
harlowja_at_homeso if people get some time, please checks those out (if u haven't already)16:37
*** Yingxin has quit IRC16:38
*** ajmiller has joined #openstack-meeting-alt16:38
harlowja_at_homeAny other specs people want to raise besides those?16:38
*** Yingxin has joined #openstack-meeting-alt16:38
*** zeih has joined #openstack-meeting-alt16:38
harlowja_at_homeok, assuming not then :-P16:39
*** eliqiao has quit IRC16:39
harlowja_at_home#topic Open discussion16:39
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"16:39
*** eliqiao has joined #openstack-meeting-alt16:39
*** mhickey has quit IRC16:39
harlowja_at_homeanything else from folks that they want to bring up?16:39
harlowja_at_home(if not that's ok to)16:40
*** neilus has quit IRC16:40
harlowja_at_homeif people are interested in any etcd or consul stuff feel free to review some of this showing up @ https://review.openstack.org/#/q/status:open+project:openstack/tooz,n,z16:40
* rbradfor hears crickets in the background16:40
harlowja_at_homeu may want to get your place checked for bugs16:41
harlowja_at_homelol16:41
harlowja_at_homeok, going one16:41
gcbIs there any plan to clean up bugs ?16:41
harlowja_at_homesure16:42
gcbsome bugs were fixed , but still  in progress status16:42
harlowja_at_homeactually i'm not sure, whats the thoughts there?16:42
harlowja_at_homeseems like a good idea to clean up bugs16:42
gcbI try to triage bug and close some16:42
harlowja_at_homegcb, where u just thinking of closing some, changing progress and all?16:43
*** Guest18099 is now known as redrobot16:43
harlowja_at_homei'd be ok with that, maybe let's find dims after this and see what he thinks16:43
*** alex_xu has joined #openstack-meeting-alt16:43
*** zeih has quit IRC16:43
dhellmanngcb : http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html16:44
harlowja_at_homegcb, where u thinking of more cleanup than in ^ ?16:45
*** Swami has joined #openstack-meeting-alt16:45
gcbI just did some clean up in oslo.policy16:45
gcband found some bugs were fixed in code , but still in confirmed and other "open" status16:46
harlowja_at_homeya, that seems like general cleanup then16:46
*** jtomasek has quit IRC16:46
dhellmannyeah, that's the sort of thing we need to do by hand. thanks for starting that, gcb16:46
harlowja_at_homemaybe during one of our doc sprints, we should also do a doc/bug sprint16:46
harlowja_at_homedoc/bug cleanup sprint16:46
harlowja_at_homeor just do it as u find them16:47
gcbyes , maybe I set up  a  etherpad  to record the to-do list16:47
dhellmannharlowja_at_home : ++16:47
harlowja_at_homegcb, that'd be great16:47
*** carl_baldwin_ is now known as carl_baldwin16:48
harlowja_at_home#action gcb harlowja talk with dims about doc/bug cleanup sprint day (maybe before next year?)16:49
harlowja_at_homeseems like we could get one of those in before next year16:49
harlowja_at_home*maybe*16:49
harlowja_at_homelol16:49
*** david-lyle has joined #openstack-meeting-alt16:49
harlowja_at_homeworth a try, but unsure, never know with peoples vacations16:49
gcbI didn't have vactions this month :-)16:50
gcbI don't16:50
harlowja_at_home:)16:50
harlowja_at_homeokie dokie, i guess for anything else we can move back into #openstack-oslo16:51
harlowja_at_homegoing once16:51
harlowja_at_homegoing twice16:52
harlowja_at_homesold16:52
harlowja_at_home#end-meeting16:52
harlowja_at_home#endmeeting16:52
*** openstack changes topic to "Bugs (Meeting topic: neutron_dvr)"16:52
openstackMeeting ended Mon Dec  7 16:52:24 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2015/oslo.2015-12-07-16.00.html16:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2015/oslo.2015-12-07-16.00.txt16:52
harlowja_at_homelol16:52
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2015/oslo.2015-12-07-16.00.log.html16:52
jungleboyjThanks.16:52
harlowja_at_homenp :16:52
harlowja_at_home:)16:52
*** johnsom_ has left #openstack-meeting-alt16:53
*** rvyalov_ has quit IRC16:53
*** kozhukalov_ has joined #openstack-meeting-alt16:54
*** kzaitsev_mb has quit IRC16:58
*** vahidh has joined #openstack-meeting-alt17:00
*** balajiiyer has quit IRC17:01
*** Leom_ has joined #openstack-meeting-alt17:04
*** scheuran has quit IRC17:04
*** Leom has quit IRC17:05
*** kzaitsev_mb has joined #openstack-meeting-alt17:07
*** kozhukalov_ has quit IRC17:08
*** Leom has joined #openstack-meeting-alt17:09
*** harlowja_at_home has quit IRC17:10
*** Leom_ has quit IRC17:12
*** Leom has quit IRC17:14
*** gcb has quit IRC17:15
*** matrohon has quit IRC17:19
*** amitgandhinz has quit IRC17:21
*** rmoe has quit IRC17:21
*** rmoe has joined #openstack-meeting-alt17:22
*** amitgandhinz has joined #openstack-meeting-alt17:23
*** weshay has quit IRC17:24
*** davideagnello has joined #openstack-meeting-alt17:24
*** salv-orl_ has joined #openstack-meeting-alt17:25
*** e0ne has quit IRC17:27
*** kozhukalov_ has joined #openstack-meeting-alt17:27
*** salv-orlando has quit IRC17:28
*** dizquierdo has quit IRC17:29
*** amotoki has quit IRC17:32
*** Sukhdev has quit IRC17:34
*** balajiiyer has joined #openstack-meeting-alt17:34
*** yamahata has quit IRC17:36
*** iyamahat has quit IRC17:36
*** sylwesterB has joined #openstack-meeting-alt17:37
*** kfarr has quit IRC17:39
*** sylwesterB has quit IRC17:42
*** lbelivea has quit IRC17:43
*** tonytan4ever has quit IRC17:46
*** ogelbukh has quit IRC17:46
*** armax has joined #openstack-meeting-alt17:49
*** c00p3r has quit IRC17:50
*** c00p3r has joined #openstack-meeting-alt17:50
*** fawadkhaliq has quit IRC17:52
*** shwetaap1 has joined #openstack-meeting-alt17:53
*** ogelbukh has joined #openstack-meeting-alt17:54
*** banix has joined #openstack-meeting-alt17:55
*** lbelivea has joined #openstack-meeting-alt17:55
*** shwetaap has quit IRC17:56
*** sdake has quit IRC17:58
*** iyamahat has joined #openstack-meeting-alt17:58
*** shwetaap1 has quit IRC17:58
*** kzaitsev_mb has quit IRC17:59
*** shwetaap has joined #openstack-meeting-alt17:59
*** sgotliv_ has joined #openstack-meeting-alt18:00
*** fawadkhaliq has joined #openstack-meeting-alt18:02
*** iyamahat has quit IRC18:05
*** safchain has quit IRC18:05
*** iyamahat has joined #openstack-meeting-alt18:05
*** Leo_ has joined #openstack-meeting-alt18:08
*** julim has quit IRC18:08
*** yamahata has joined #openstack-meeting-alt18:09
*** neelashah has quit IRC18:09
*** yamamoto has joined #openstack-meeting-alt18:14
*** dims has joined #openstack-meeting-alt18:16
*** andymaier has quit IRC18:16
*** mgrohar has joined #openstack-meeting-alt18:17
*** weshay_xchat has joined #openstack-meeting-alt18:18
*** yamamoto has quit IRC18:18
*** e0ne has joined #openstack-meeting-alt18:24
*** rsyed is now known as rsyed_away18:25
*** sdake has joined #openstack-meeting-alt18:27
*** MarkAtwood has quit IRC18:29
*** Leo_ has quit IRC18:29
*** Leo_ has joined #openstack-meeting-alt18:30
*** vahidh has quit IRC18:31
*** kozhukalov_ has quit IRC18:34
*** s3wong has joined #openstack-meeting-alt18:34
*** salv-orlando has joined #openstack-meeting-alt18:35
*** salv-orl_ has quit IRC18:35
*** tonytan4ever has joined #openstack-meeting-alt18:36
*** mgrohar has quit IRC18:42
*** catherineD has joined #openstack-meeting-alt18:44
*** markvan has quit IRC18:48
*** markvan has joined #openstack-meeting-alt18:50
*** jaypipes has quit IRC18:52
*** vahidh has joined #openstack-meeting-alt18:53
*** rockyg has joined #openstack-meeting-alt18:53
*** julim has joined #openstack-meeting-alt18:53
*** neilus has joined #openstack-meeting-alt18:53
*** neiljerram has quit IRC18:54
*** Leo_ has quit IRC18:54
*** jprovazn has quit IRC18:56
*** pvaneck has joined #openstack-meeting-alt18:58
*** dwalleck has joined #openstack-meeting-alt18:59
*** neilus has quit IRC18:59
catherineD#startmeeting refstack19:00
openstackMeeting started Mon Dec  7 19:00:10 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
markvoelkero/19:00
dwallecko/19:00
rockygo/19:00
pvanecko/19:00
*** alevine has joined #openstack-meeting-alt19:01
*** aginwala has joined #openstack-meeting-alt19:01
catherineDhello everyone19:01
catherineD#link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-15-12-0719:01
davidlenwellhi19:02
*** sslypushenko__ has joined #openstack-meeting-alt19:03
catherineD#topic     Review mapping ( https://etherpad.openstack.org/p/mitaka-refstack-ation-items  ) of   "RefStack Enhancement" document ( https://goo.gl/hDC6U3 ) to RefStack Mitaka priority  ( https://etherpad.openstack.org/p/refstack-tokyo-summit )19:03
*** openstack changes topic to "Review mapping ( https://etherpad.openstack.org/p/mitaka-refstack-ation-items ) of "RefStack Enhancement" document ( https://goo.gl/hDC6U3 ) to RefStack Mitaka priority ( https://etherpad.openstack.org/p/refstack-tokyo-summit ) (Meeting topic: refstack)"19:03
sslypushenko__o/19:03
*** alevine has quit IRC19:03
*** rsyed_away is now known as rsyed19:03
catherineDsslypushenko__: agenda https://etherpad.openstack.org/p/refstack-meeting-15-12-0719:04
*** sigmavirus24 is now known as sigmavirus24_awa19:04
*** chandankumar has quit IRC19:04
sslypushenko__thx!19:04
*** sigmavirus24_awa is now known as sigmavirus2419:05
catherineDso Alex Levin send us a document describing the enhancements for Refstack19:05
*** alevine has joined #openstack-meeting-alt19:05
catherineD#link RefStack enhancement doc from Alex Levin https://goo.gl/hDC6U319:06
*** neelashah has joined #openstack-meeting-alt19:06
sslypushenko__Really good doc!19:06
dwalleckVery detailed :-) There's a lot of good ideas here19:06
*** mestery has quit IRC19:06
sslypushenko__It is some what was missing19:06
catherineDbasically there are 5 majoir areas:  1 Register cloud, 2 Run test, 3 Run external test suitesm, 4 Show cloud achievement, 5 Simplify test preparation19:07
*** mestery has joined #openstack-meeting-alt19:07
*** vahidh has quit IRC19:08
catherineD+2 agree with everyone that it is a very good doc ... so the refstack team will seriously looking to implement those that is applicable ...19:08
sslypushenko__It looks like a lot of work19:09
hogepodgeo/19:09
davidlenwellit looks very close to the original vision of refstack19:09
rockygSounds like time for a multi-cycle road map!19:09
sslypushenko__rockyg +119:10
catherineDyes it is a lot of work but we can prioritize at the minimum to implement the building blocks first ...19:10
sslypushenko__We need aplan)19:10
*** vahidh has joined #openstack-meeting-alt19:10
rockyg++19:10
davidlenwellsounds like we should sit down and compare it against the existing use cases and then reprioritize everything and make a plan19:10
catherineDyes ... we need a plan ... so I did a quick mapping documented in https://etherpad.openstack.org/p/mitaka-refstack-ation-items19:10
*** alevine has quit IRC19:11
catherineD#link quick mapping of Alex's doc to Mitak priority https://etherpad.openstack.org/p/mitaka-refstack-ation-items19:11
*** alevine has joined #openstack-meeting-alt19:12
catherineDthe three areas that I think we could prioritize to implement for Mitaka is 1) register cloud .. this map very well to what we want to do any way for vendor registration19:13
*** agireud has joined #openstack-meeting-alt19:14
catherineDnext is Item #3 in Alex's doc Run external test suite ---> RefStack wants to implement this for this cycle too19:14
*** alevine has quit IRC19:15
pvaneckI think we can go ahead with the vendor/product stuff and start implementing that. Already have a lot of details regarding that from the summit19:15
catherineDand #4 Show cloud achievement --> If RefStack will allow testing of external test suite we need a way to render data .... t19:15
*** kozhukalov_ has joined #openstack-meeting-alt19:15
*** alevine has joined #openstack-meeting-alt19:15
alevineo/19:16
catherineDpvaneck: +1 ... we could go ahead with that ..19:16
catherineDalevine: hi ... agenda link https://etherpad.openstack.org/p/refstack-meeting-15-12-0719:16
alevinesorry I'm late. I got the beginning of the meeting. I wanted to remind that a large part of the mentioned functionality is already implemented. At least as a working prototype19:17
catherineDalevine: please take a look at the mapping in  https://etherpad.openstack.org/p/mitaka-refstack-ation-items19:17
*** sbalukoff has joined #openstack-meeting-alt19:18
alevineCatherineD: I did see it beforehand. Thank you.19:18
*** rcurran has joined #openstack-meeting-alt19:18
catherineDalevine: yup ... I have seen your prototype site19:19
alevineWe're more than happy to implement and contribute what's stated in the doc if you give us green light.19:19
alevineIt'd really save us time and effort if you won't make us to create all of the specs and let us refine the doc according to any comments that can arise, and then implement the thing.19:20
catherineD#link Alex's team prototype  http://refstack.cloudscaling.com:8000/#/19:20
alevineEverybody: Sorry, you need to use the fake sign-in at the right to get access to all functionality.19:21
sslypushenko__alevine Sounds reasonable19:21
*** edwardb has joined #openstack-meeting-alt19:21
catherineDalevine: the 3 building block areas that we would like to see implemented first is 1) Register cloud 2) external text 3) show cloud achievement19:22
catherineDalevine: How about if I write the specs for the three areas mentioned above ...?19:23
alevinecatherineD: Absolutely. How about running tests from the panel though?19:23
*** neilus has joined #openstack-meeting-alt19:23
catherineDalevine: we can discuss running test in the next few meetings ...19:23
alevinecatherineD: Whatever you say. I can also help with righting the specs if you think it's required.19:24
catherineDas davidlenwell: indicated earlier this is our original design ...19:24
catherineDwe have encountered a few challenging areas that I would like the team to discuss further ...19:24
sslypushenko__catherineD It looks like we just need to convert google document into rst spec19:25
alevinecatherineD: The problem is - it's much easier to test all of the other features you mentioned when you can do everything from the panel. :) So I guess we can at least have it in some draft, experimental form just to use.19:25
catherineDalevine: I think we should have the spec ..19:25
dwalleckI think having a working prototype makes writing the specs easier. I think the spec process will help make sure we flesh out the features appropriately19:25
alevine"writing the specs", sorry :)19:25
catherineDalevine: I think a prototype would be very helpful ...19:26
*** jtomasek has joined #openstack-meeting-alt19:26
*** sylwesterB has joined #openstack-meeting-alt19:26
alevinedwalleck: agree. I suggest we bring the prototype up to speed with the design if the design is approved overall. And then it'll be very easy to reflect it in the specs.19:26
catherineDif we agree that we will implement the building block as our first phase ... I would like to review our data model next ..19:27
alevinecatherineD: Ok. Sounds great. We can enhance the data model described in your doc with additional data required for new functionality.19:28
*** neilus has quit IRC19:28
catherineDalevine: thx ...19:28
catherineD#topic Review and agree on data models19:29
*** openstack changes topic to "Review and agree on data models (Meeting topic: refstack)"19:29
dwalleckalevine: I totally agree. To add to what catherineD said, I think we just want to make sure we're adding expandable bases19:29
catherineD#link data model https://goo.gl/zWYnoq19:29
catherineDcould everyone look at slide# 719:29
catherineDslide# 6 was what we discussed before ...19:30
catherineDafter review alevine: 's doc I feel like we need a "product" entiry ...19:30
*** sylwesterB has quit IRC19:31
dwalleckRight now Tempest tests aren't directly tied to a product. Where would that data come from?19:32
catherineDonm slide#7 the new tables are role, group, product, vendor and grp_suer_role_relationship (used for many to many mapping of role, user, group)19:32
*** dprince has quit IRC19:32
catherineDdwalleck: good question ..19:33
catherineDeveryone please go to slide#219:33
*** neelashah has quit IRC19:33
catherineDso product can be created (register) by vendor (item 2 ) or any user (item 3)19:34
alevinedwalleck: We suggest that Tempest tests are tied to Schemas, while test configurations are tied to clouds/products.19:34
*** neelashah has joined #openstack-meeting-alt19:34
dwalleckAhh, product as in a product within a vendor, not within OpenStack. I see now19:34
*** bana_k has joined #openstack-meeting-alt19:34
catherineDdwalleck: yup19:34
catherineDany inputs for slide#2 and slide#7?19:35
alevinecatherineD: We'll need more users and roles later19:35
sslypushenko__LGTM19:35
catherineDsslypushenko__: pvaneck: I think you suggested earlier that the product info can be saved in meta table ....19:36
catherineDbut with alevine: concept if cloud testing ... I think that maps well with product having its own table19:37
alevinecatherineD: Sorry, I see you covered all roles, except Guest.19:37
sslypushenko__Now product gets more sense19:37
pvaneckthat was before we had a product table19:37
sslypushenko__Any way it requires time to think19:37
catherineDalevine: we can add add Guest to our table ...19:37
sslypushenko__I will put comments in doc if I come up with something19:37
catherineDsslypushenko__: absolutely ... that is why I would like to have us think about all of this before implementation ...19:38
catherineDsslypushenko__: please do ...19:38
catherineDI think having a good data model will help a lot ....19:38
sslypushenko__for sure19:39
sslypushenko__Any way it is a good start19:39
catherineDHow about we let everyone take sometime to review the data model until next week ... then we start to implement data model and its aspect like API for model CRUD19:40
catherineD#action all RefStack team members to review data model described in https://goo.gl/zWYnoq19:41
alevinecatherineD: wouldn't you want to have schemas objects in data model later as well?19:41
catherineDalevine: that is what I want to discuss next  about schemas19:42
*** Leo_ has joined #openstack-meeting-alt19:42
catherineDalevine: are you refering to schema for data rendering?19:42
catherineDor data base schema?19:42
alevinecatherineD: For describing external test suites and Target Programs.19:42
*** neilus has joined #openstack-meeting-alt19:43
alevinecatherineD: I'm sorry I'm not aware of any other schemas - I'm using the term from my doc.19:43
catherineDalevine: yup ... currently we usde DefCore schena ..19:43
alevinecatherineD: Of course :)19:43
hogepodgecatherineD: guideline is probably better terminology19:44
hogepodgethe guideline has an ad-hoc schema (we haven't actually formally defined it)19:44
*** aginwala has quit IRC19:44
catherineDalevine: I think we were talking about the ad-hoc schema  right?  schema is what we use to render the content of the Guideline ...19:45
alevinecatherineD: hogepodge: I was trying to use a parallel term from www.w3c.org - like XSD schemas for XML. So here we can define our schemas.19:45
*** e0ne has quit IRC19:45
sslypushenko__alevine schemas will be stored in DB anyway, so model should meet this fact19:45
*** Leo_ has quit IRC19:46
alevinessplypushenko__: No problem. Though we might consider having external schemas in outside URLs like XSD and WSDL schemas reside.19:47
catherineDalevine: sslypushenko__: hogepodge: I think each of us may talk about different things here... I suggest that we discuss this in refstack IRC after this meeting ....19:47
*** pballand has quit IRC19:47
catherineDI do want to discuss externl testing next now that we have DefCore member here ...19:47
*** sdake has quit IRC19:47
*** pballand has joined #openstack-meeting-alt19:48
*** vilobhmm11 has joined #openstack-meeting-alt19:48
*** aginwala has joined #openstack-meeting-alt19:48
sslypushenko__IMO, we should try to make data model as abstract as possible and get rid of details. It will give us a required level of flexibility19:48
catherineDto sumarize, everyone will review the data model ... next week we will log our agreement and then proceed to implementation19:48
*** spzala has joined #openstack-meeting-alt19:49
catherineDsslypushenko__: +119:49
sslypushenko__alevine: Is it possible to look on code of our team prototype?19:49
catherineDso everyone please voice your opion on the update needed on the data model via IRC, email, or update the doc ...19:50
alevinesslypushenko__: Absolutely. Could you send me a link, please, just to be sure that's what you want us to look to?19:50
sslypushenko__http://refstack.cloudscaling.com:8000/ this one19:51
alevinesslypushenko__: I'm sorry I got you wrong. I thought you want my team to look at your prototype :). You want to look at our code? Sure.19:51
catherineD#topic Pending reviews19:52
*** openstack changes topic to "Pending reviews (Meeting topic: refstack)"19:52
catherineD#link     Another way to use additional tests for tempest  https://review.openstack.org/#/c/249160/19:52
alevinesslypushenko__: Here is the repo: https://github.com/cloudscaling/refstack19:52
sslypushenko__alevine thx!19:53
*** dave-mccowan has quit IRC19:53
*** jtomasek has quit IRC19:53
catherineDalevine:  both sslypushenko__:  and I agree that https://review.openstack.org/#/c/249160/   is a very approached to bring in external tests19:53
*** dizquierdo has joined #openstack-meeting-alt19:53
sslypushenko__catherineD I think it is kind of POC19:53
*** fawadkhaliq has quit IRC19:54
*** pballand has quit IRC19:54
catherineDalevine: may question is should we install non-DefCore package like (ec2-api) out of the box ... or should we provide instruction for users to add non-DefCore test packages19:54
*** annilai has joined #openstack-meeting-alt19:55
catherineDsslypushenko__: what is a  POC?19:55
alevinecatherineD: Yes the instruction about how to create tempest plugin and new schema would be very helpful. We have such a thing internally now.19:55
sslypushenko__catherineD: proof of concept19:55
dwalleckcatherineD: I'd vote for installing any other test suites as a separate step. That avoids any install by default bias19:55
catherineDalevine: but the question is should we add ec2-api into the tempest-additional-requirements.txt file?19:56
alevinecatherineD: I'd say that tempest-additoinal-requiremens.txt should be empty in RefStack repo. They are "additional". The baseline reqs should be in other .txt files.19:57
hogepodgecatherineD: it's not part of the defcore guideline, and never will be19:57
*** diazjf has joined #openstack-meeting-alt19:57
sslypushenko__dwalleck It depends on Defcore requirements. There is a plan include some swift tests into Defcore schema19:57
catherineDhogepodge: markvoelker: rockyg: I think that question should be toe DefCore ... should RefStack out-of-the-box installed only DefCore required external packages?19:57
*** pdesai has joined #openstack-meeting-alt19:57
alevinecatherineD: Yes, no ec2-api in RefStack repo.19:57
hogepodgecatherineD: but what external tests you want to install is up to the refstack team19:58
catherineDalevine: great ...19:58
*** jkf has joined #openstack-meeting-alt19:58
alevinecatherineD: defcore tests are all in core tempest, aren't they?19:58
*** igueths has joined #openstack-meeting-alt19:58
alevinecatherineD: Then they shouldn't be in tempest-additional-requirements.txt either. It's just a placeholder.19:58
*** jhfeng has joined #openstack-meeting-alt19:58
dwallecksslypushenko__: Agreed. I think anything DefCore requires should be installed by default (including external tests). Anything extra should be supported, but not installed by default19:58
hogepodgealevine: we may allow some tests to be sourced externally, like swift, assuming they adopt the tempest plugin architecture19:58
* redrobot pokes head in19:59
catherineDalevine: I think DefCore is looking at bring in Swift in-tree test ... from refstack point of view ... it is like external but required test19:59
hogepodge#link https://review.openstack.org/#/c/214206/19:59
catherineDwe need to end our meeting soon ... could we continue on #refstack19:59
*** dprince has joined #openstack-meeting-alt19:59
alevinehogepodge: I'd say that if we suggestion tempest-addtional-requirements.txt for external usage, we better not mix anything core into it. If we want swift as a plugin - fine. But it shouldn't go there I guess anyways.19:59
*** e0ne has joined #openstack-meeting-alt19:59
*** silos has joined #openstack-meeting-alt20:00
alevine"suggest"20:00
catherineD#endmeeting20:00
*** openstack changes topic to "Bugs (Meeting topic: neutron_dvr)"20:00
openstackMeeting ended Mon Dec  7 20:00:13 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-07-19.00.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2015/refstack.2015-12-07-19.00.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2015/refstack.2015-12-07-19.00.log.html20:00
redrobot#startmeeting barbican20:00
openstackMeeting started Mon Dec  7 20:00:25 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
*** alee has joined #openstack-meeting-alt20:00
*** dwalleck has quit IRC20:00
redrobot#topic Roll Call20:00
elmikoo/20:00
*** openstack changes topic to "Roll Call (Meeting topic: barbican)"20:00
*** arunkant_ has joined #openstack-meeting-alt20:00
aleeo/20:00
jkfo/20:00
arunkant_o/20:00
silos\o/20:00
diazjfo/20:00
iguethsØ20:00
*** kfarr has joined #openstack-meeting-alt20:00
*** rellerreller has joined #openstack-meeting-alt20:01
rellerrellero/20:01
jhfengo/20:01
redrobotAwesome, lots of barbicaneers here!20:02
kfarro/20:02
*** alevine has left #openstack-meeting-alt20:02
redrobotAs usual the agenda can be found here:20:02
*** e0ne has quit IRC20:02
redrobot#link https://wiki.openstack.org/wiki/Meetings/Barbican20:02
*** lisaclark1 has joined #openstack-meeting-alt20:02
redrobot#topic Action Items from last meeting20:03
*** openstack changes topic to "Action Items from last meeting (Meeting topic: barbican)"20:03
*** vilobhmm11 has quit IRC20:03
redrobot#link http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-11-30-20.00.html20:03
*** vilobhmm11 has joined #openstack-meeting-alt20:03
redrobotalee any updates on the blog post on testing Cinder volume encryption20:03
spotzo/ is late20:04
redrobotalee bueller?20:04
aleeredrobot, yeah -- just a sec .20:04
redrobotalee cool20:05
aleehttps://vakwetu.wordpress.com/20:05
redrobotalee awesome!20:05
*** woodster_ has joined #openstack-meeting-alt20:05
lisaclark1o/20:05
aleeredrobot, may be worthwhile linking it somewhere ..20:05
redrobotalee I was going to ask if you'd had a chance to advertise it on the ML?20:05
kfarralee very cool!20:06
*** dizquierdo has quit IRC20:06
aleeredrobot, not yet , but thats a good idea20:06
*** dave-mccowan has joined #openstack-meeting-alt20:06
woodster_o/20:06
dave-mccowano/20:06
*** dizquierdo has joined #openstack-meeting-alt20:06
*** vilobhmm11 has quit IRC20:06
aleeredrobot, I'll shoot off an email later today20:06
redrobot#action alee to advertise barbican+volume encription blog20:06
*** sslypushenko__ has quit IRC20:07
aleelet me know if anything is incorrect ..20:07
redrobotdiazjf any updates on the Barbican context blueprint ?20:07
diazjfredrobot, None yet, I have an internal meeting about that with the swift encryption and security team this week20:08
redrobotdiazjf ok, I'll bump it to next week20:08
redrobot#action diazjf to update the Barbican context blueprint20:08
diazjfredrobot, awesome thanks20:08
redrobotlisaclark1 ping?20:08
lisaclark1pong20:08
redrobotlisaclark1 do you have any  links to hotel recommendations and mid-cycle eventbrite link ?20:09
lisaclark1one sec and i'll pull them up20:09
lisaclark1#link https://wiki.openstack.org/wiki/Sprints/BarbicanMitakaSprint20:09
lisaclark1#link https://www.eventbrite.com/e/openstack-barbican-mitaka-midcycle-tickets-1978467449420:09
lisaclark1the first link has been updated with hotel recommendations20:09
lisaclark1the barbican midcycle has also been updated on the sprints wiki20:10
lisaclark1#link https://wiki.openstack.org/wiki/Sprints20:10
redrobotlisaclark1 awesome!20:10
lisaclark1OSSP's midcycle is also up.  any interested barbicaneers should also sign up for the OSSP midcycle if there's planned attendance there20:10
lisaclark1#link https://etherpad.openstack.org/p/security-mitaka-midcycle20:10
*** vilobhmm11 has joined #openstack-meeting-alt20:11
*** binean has joined #openstack-meeting-alt20:11
redrobotlisaclark1 good stuff!20:11
redrobotthat's it for action items20:11
redroboton to the agenda....20:11
redrobot#topic Mid-Cycle20:12
*** openstack changes topic to "Mid-Cycle (Meeting topic: barbican)"20:12
kfarrredrobot, I think there were a few for you from two meetings ago, but they didn't carry over on our notes20:12
redrobotlisaclark1 pretty much covered everything regarding the mid cycle20:12
redrobotit's just 4 weeks away, so now's the time to make arrangements to come down20:13
redrobotkfarr sorry, it's my first day back to work and I have no idea what's going on. :)20:13
redrobotkfarr but I'm pretty sure I didn't do anything during my vacation... ;)20:14
dave-mccowanthe security project also has their mid-cycle that week, also in the castle.  so for folks interested in both projects, plan to stay the whole week.20:14
redrobotany other questions/comments about the mid-cycle ?20:14
*** cknight has quit IRC20:15
lisaclark1thanks dave-mccowan.  also, please be sure to signup on both midcycle signup forms.  this will ensure the planners can coordinate appropriately for total attendees20:15
dave-mccowan#link https://etherpad.openstack.org/p/security-mitaka-midcycle20:16
elmikowe should probably copy lisaclark1's hotel info to the security pad too20:16
elmiko(sorry, wrong meeting for that topic)20:16
lisaclark1elmiko: i'll do that now20:17
elmikolisaclark1: thanks!20:17
redrobotawesome, ok, moving on ...20:17
redrobot#topic Mitaka-1 Milestone Release20:17
*** openstack changes topic to "Mitaka-1 Milestone Release (Meeting topic: barbican)"20:17
redrobot#link http://lists.openstack.org/pipermail/openstack-dev/2015-December/081419.html20:17
redrobotMany thanks to kfarr for taking care of the release20:18
redrobot...  I think it was kfarr anyway ...20:18
kfarrredrobot, yup, sure thing!20:18
elmikokfarr++20:18
diazjf+++++20:19
redrobotkfarr did we have release notes written up for it?  I recall there being a new release not process?20:19
rellerrellerkfarr woot! woot!20:19
*** e0ne has joined #openstack-meeting-alt20:19
*** e0ne has quit IRC20:19
kfarrredrobot, the requirement for the release was to integrate reno20:19
*** e0ne has joined #openstack-meeting-alt20:19
kfarr(the release notes manager)20:19
*** e0ne has quit IRC20:20
lisaclark1are release notes now auto generated?20:20
kfarrI did not write release notes for this release, but for future ones we can now add the notes directly to our repository20:20
redrobotkfarr I see...  I'll have to look into that.  Do you know if we're still on the hook to maintain the Launchpad release pages?20:20
*** Sukhdev has joined #openstack-meeting-alt20:20
kfarrredrobot, the launchpad release notes pages are now auto-generated from the release notes we add to our repo20:21
kfarrOh, no, I meant the wiki release notes page is auto-generated from our repo20:21
redrobotkfarr interesting...  the launchpad page seems like it needs some tlc.  I'll look into cleaning it up.20:21
redrobot#action redrobot to clean up Launchpad mitaka-1 page20:21
*** EricGonc_ has quit IRC20:22
redrobotThat's all that I had on my mental agenda...  and there doesn't seem to be anything else on the wiki agenda20:22
redrobot#topic Open Discussion20:22
*** openstack changes topic to "Open Discussion (Meeting topic: barbican)"20:22
diazjfredrobot, Barbican Federation??20:22
redrobotAlso, many thanks to rellerreller for steering the boat while I was gone.20:22
rellerrellerredrobot np20:23
*** annilai has quit IRC20:23
redrobotdiazjf sure20:23
redrobot#topic Federation20:23
*** openstack changes topic to "Federation (Meeting topic: barbican)"20:23
redrobotdiazjf any updates here?20:23
*** baoli_ has quit IRC20:24
diazjfNo updates on our part, just wanted to see if anyone had gone over the usecases. I think most of the discussion will happen during the mid-cycle though.20:24
redrobotdiazjf  I sent the link to the use cases to Joe Savak before I took off for Spain... just got back in today and haven't had a chance to catch up with him yet.20:25
diazjfredrobot, no worries, whenever you get a chance. :)20:26
redrobot#link https://wiki.openstack.org/wiki/Barbican/Discussion-Federated-Barbican20:27
*** kzaitsev_mb has joined #openstack-meeting-alt20:27
*** _nadya_ has joined #openstack-meeting-alt20:28
*** catherineD has left #openstack-meeting-alt20:28
*** matrohon has joined #openstack-meeting-alt20:30
redrobot#link https://etherpad.openstack.org/p/barbican-federation-use-cases20:30
redrobothad to dig out that second link20:30
redrobotanything else on Federation or any other topic?20:31
redrobotI still have some catching up to do on my email and ML and such ....20:31
*** balajiiyer has quit IRC20:31
diazjfjust that thanks redrobot20:31
*** rcurran has quit IRC20:32
redrobotgoing once ...20:33
*** aginwala has quit IRC20:33
redrobotlast chance ...20:33
diazjfsold20:33
redrobotok, we all get 25 min back!20:33
redrobotthanks for coming!20:33
redrobot#endmeeting20:33
*** openstack changes topic to "Bugs (Meeting topic: neutron_dvr)"20:34
*** silos has left #openstack-meeting-alt20:34
openstackMeeting ended Mon Dec  7 20:33:59 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-12-07-20.00.html20:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-12-07-20.00.txt20:34
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-12-07-20.00.log.html20:34
elmikothanks redrobot, congrats too ;)20:34
redrobotelmiko  thanks! :D20:34
*** arunkant_ has left #openstack-meeting-alt20:34
* igueths waves to all20:34
*** igueths has left #openstack-meeting-alt20:34
*** shwetaap has quit IRC20:37
*** jhfeng has left #openstack-meeting-alt20:37
*** binean has quit IRC20:37
*** barrett has joined #openstack-meeting-alt20:37
*** jkf has left #openstack-meeting-alt20:38
*** kzaitsev_mb has quit IRC20:38
*** lisaclark1 has quit IRC20:41
*** pdesai has quit IRC20:41
*** aginwala has joined #openstack-meeting-alt20:41
*** haypo has left #openstack-meeting-alt20:41
*** rellerreller has quit IRC20:43
*** jaosorior has joined #openstack-meeting-alt20:43
*** jaosorior has quit IRC20:45
*** dizquierdo has quit IRC20:46
*** diazjf has quit IRC20:46
*** baoli has joined #openstack-meeting-alt20:48
*** baoli has quit IRC20:48
*** baoli has joined #openstack-meeting-alt20:49
*** xyang1 has joined #openstack-meeting-alt20:49
*** kzaitsev_mb has joined #openstack-meeting-alt20:49
*** matrohon has quit IRC20:51
*** _nadya_ has quit IRC20:51
*** hoangcx has joined #openstack-meeting-alt20:52
*** igordcard__ has quit IRC20:52
*** hyakuhei_ has joined #openstack-meeting-alt20:54
*** mhickey has joined #openstack-meeting-alt20:54
*** MeganR has joined #openstack-meeting-alt20:55
*** hichihara has joined #openstack-meeting-alt20:56
*** alyson_ has quit IRC20:56
*** lisaclark1 has joined #openstack-meeting-alt20:57
*** aginwala has quit IRC20:57
*** kencjohnston has joined #openstack-meeting-alt20:58
*** yamamoto has joined #openstack-meeting-alt20:58
*** scohen1 has joined #openstack-meeting-alt20:59
*** Mr_T has joined #openstack-meeting-alt21:00
*** dpk_ has joined #openstack-meeting-alt21:00
barrett#startmeeting Product Working Group21:00
openstackMeeting started Mon Dec  7 21:00:39 2015 UTC and is due to finish in 60 minutes.  The chair is barrett. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: Product Working Group)"21:00
openstackThe meeting name has been set to 'product_working_group'21:00
*** pchadwick has joined #openstack-meeting-alt21:00
barrettHi Folks - Who is here for the Product WG team meeting?21:00
pchadwickI'm hre21:01
pchadwickhere21:01
*** leong has joined #openstack-meeting-alt21:01
pchadwickHi Carol21:01
*** cknight has joined #openstack-meeting-alt21:01
leongo/21:01
kencjohnstono/21:01
barrettHI Pete21:01
*** cloudrancher has joined #openstack-meeting-alt21:01
scohen1o/21:01
cloudranchero/21:01
dpk_o/21:02
sgordono/21:02
MeganRo/21:02
barrettgreat21:03
barrett#topic Agenda21:03
*** openstack changes topic to "Agenda (Meeting topic: Product Working Group)"21:03
barrett#link:  https://wiki.openstack.org/wiki/Meetings/product-team#December_7.2C_2015_Product_Team_Meeting_Agenda21:03
barrettYou can find the agenda for today at the link21:03
*** annilai has joined #openstack-meeting-alt21:03
barrett#topic User Story Updates21:03
*** openstack changes topic to "User Story Updates (Meeting topic: Product Working Group)"21:03
barrettLeong & Kenny - Can you lead off with an update on Rolling Upgrades?21:04
kencjohnstonSure21:04
barrettThanks21:04
kencjohnstonFrankly not much movement since last week. I've been compiling updates to the User Story in the form of a gaps analysis21:04
*** nateziemann has joined #openstack-meeting-alt21:04
*** mwagner_lap has quit IRC21:04
kencjohnstonwhich has been happening offline21:04
kencjohnstonI need to contribute those ammendments21:04
*** balajiiyer has joined #openstack-meeting-alt21:04
*** pashkin has quit IRC21:04
barrettDo you have a target date for the completion of the gaps analysis?21:05
*** rockyg_ has joined #openstack-meeting-alt21:05
kencjohnstonbut work is being planned, across versioned object support, schema migration, and live migrate21:05
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:05
kencjohnstonI'd like to make the ammendments to teh user story on Wednesday.21:05
leongbased on the current product wg workflow, i wondering if we should move this rolling upgrade user stories to "tracked"21:05
leong#link: https://wiki.openstack.org/wiki/ProductTeam/User_Stories#User_Story_Workflow21:05
rockyg_o/21:05
kencjohnstonleong I would think we need the gaps analysis first to target what we are tracking21:05
barrettHi Rockyg21:05
*** Shamail has joined #openstack-meeting-alt21:06
kencjohnstonBut I agree that we should be able to do that this week21:06
barrettLeong - Great point.21:06
leongGap Analysis is in phase "track"21:06
kencjohnstonI've broken down what is in flight for the Mitaka release21:06
Arkady_Kanevskyno phone bridge today?21:06
kencjohnstonoh, sorry, I didn't read the link :)21:06
kencjohnstonthen yes we should promote it to tracked21:06
kencjohnstonleong I can do that when I commit the gaps analysis changes21:06
barrettarkady_kanevsky: nope, we're going IRC only for our team meetings starting today21:06
Arkady_Kanevskyok21:07
barrettkencjohnston: +121:07
kencjohnstonor we can do it today. It is definitely resourced.21:07
Shamail(hi all, sorry for being late)21:07
leongfor Proposed stage, the next criteria to move into "tracked" is commit resource21:07
barrettHi Shamail21:07
leonghi shamail21:07
kencjohnstonbarrett OK, if there isn't any other thoughts I'll plan on doing that.21:07
leongwe are proposing moving "rolling upgrade" into "tracked"21:07
kencjohnstonCan I register an action for myself?21:07
Arkady_Kanevskyso need to be done to move it to tracked? just move from one diretcory to another?21:07
*** stanchan has joined #openstack-meeting-alt21:08
sgordoni believe a chair needs to record actions (or chair someone to do it)21:08
barrettkencjohnston: No, but I will do it for you :)21:08
kencjohnstonArkady_Kanevsky correct21:08
*** harlowja has quit IRC21:08
barrett#action Kencjohnston move Rolling Upgrades to Tracked folder21:08
*** harlowja has joined #openstack-meeting-alt21:08
kencjohnstonactually, for review purposes I'll split them up.21:08
kencjohnstonI'll first move it to tracked, since the gaps anayslsis isn't required and we can all review that commit21:08
Shamailkencjohnston: +121:09
kencjohnstonthen I'll add the gaps analysis so we can comment on that one separately21:09
kencjohnstonI'll do the tracked thing tonight.21:09
*** kzaitsev_mb has quit IRC21:09
ShamailI'll go ahead and create a fracker template in the repo too... That way we can at least populate the necessary information even if the final place is tbd21:09
barrettkencjohnston: Sounds good. Will the gaps analysis be in a Google doc or are you going to create something that can be posted to repo?21:09
*** qwebirc11014 has joined #openstack-meeting-alt21:09
ShamailTracker*21:09
barrettshamail: +121:09
*** baoli has quit IRC21:09
kencjohnstonShamail oh, great, I was going to do it via text in the user story21:10
*** baoli has joined #openstack-meeting-alt21:10
ShamailCan you please assign that action to barrett?21:10
kencjohnstonShamail process wise? DO I upload a version of the template into the tracked folder?21:10
leongcan the gap analysis be created in repo?21:10
*** pballand has joined #openstack-meeting-alt21:10
barrett#action Shamail to create a Tracker template and post to repo21:10
ShamailIt's actually supposed to live outside since the user story can change and others could fall under the same tracker eventually21:10
ShamailYes Leong, makes sense21:11
*** baoli has quit IRC21:11
ShamailMy first reply was to tracker, not gap analysis21:11
*** baoli has joined #openstack-meeting-alt21:11
barrettShamail - I'm confused. Are you going to post a tracker template to the Repo?21:11
*** eilert has joined #openstack-meeting-alt21:12
*** nurla has quit IRC21:12
ShamailYes barrett... It will have fields like blueprints, specs, market segments, team, etc21:12
barrettGreat.21:13
barrettAnything else on Rolling Upgrades?21:13
kencjohnstonbarrett Shamail I'll get with shamail on the process offline21:13
kencjohnstonnothing else for me21:13
Arkady_Kanevskydo we have a user story for update not upgrade?21:13
Arkady_Kanevskythat is minor version not major version change?21:13
annilaigood question21:14
pchadwickwhat is the definition of a minor version?21:14
kencjohnstonArkady_Kanevsky I think they have all been rolled in together21:14
leongu mean like "patches"?21:14
barrettArkady_kanevsky: What is the difference?21:14
Arkady_Kanevskythink of liberty.0 vs. liberty.121:14
kencjohnstonThe user story includes "Immediate Upgrade" to capture CVEs and other security patches21:15
*** nurla has joined #openstack-meeting-alt21:15
Arkady_Kanevskysome bug fixes do fix schema or ohter things that impact updgrade21:15
*** sylwesterB has joined #openstack-meeting-alt21:15
Arkady_Kanevskybut the only version tested for upgrade is GA release21:15
barrettsounds like the intention is to cover them.21:15
Arkady_Kanevskyagree on intension.21:15
barrettArkady_Kanevsky: Can you review the user story and add comments where you think there are gaps?21:15
rockyg_++21:16
sgordonmmm, bug fixes from where?21:16
Arkady_Kanevskygive me that AI.21:16
rockyg_stable branch21:16
Arkady_KanevskyI was justing if that is udner upgrade story or we want seperate story for update scenarios.21:16
sgordonanything that requires a schema upgrade is more likely part of the "major version" upgrade21:16
leongthat might be cover under Usage Scenario section21:16
sgordonyeah but stable branch doesnt allow that21:16
sgordonkind of my point21:16
barrett#action Arkday Kanevsky: Review the Rolling Upgrade User story and add comments describing any gaps for updates21:17
leong#link: http://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/rollingupgrades.html21:17
Shamailsgordon: +1 and barrett: +1 to comments on user story21:17
Arkady_Kanevskythank you21:17
barrettLet's move on....21:17
barrettJay/Deric can you give an update on Onboarding Hosts?21:17
cloudranchersure21:18
barrettThanks21:18
cloudrancherWe added new members from Platform9 as outcome from Tokyo21:18
cloudrancherSo we have been taking turns explaining each teams approach to onboarding: Platform9 and IBM PowerVC team21:18
cloudrancherEach team approaches has gaps and advantages21:18
*** pashkin has joined #openstack-meeting-alt21:18
cloudrancherPresentations in Onboarding Google Drive https://drive.google.com/drive/u/0/folders/0B0gXxpcL9MhGMy1tOU5ZbEFjRVU21:18
cloudrancherwe decided to split the blueprint drafts into three parts. Cinder changes, Neutron changes and a new project that will interact with Nova21:19
*** sylwesterB has quit IRC21:19
cloudrancherthat was just done last week. Unfortunately we have been slow due to RealJob(TM) workloads21:19
*** dklenov has quit IRC21:20
barrett:)21:20
cloudrancherso we have the new drafts in the google drive21:20
*** bradjones has quit IRC21:20
cloudrancherand will be discussing this Friday. We are still using voice bridge for now, but will be adding IRC21:20
kencjohnstoncloudrancher - what is driving separating the overall story?21:20
*** baoli has quit IRC21:21
cloudrancherif anybody could sent a scheduling IRC meetings dummies guide that would be good21:21
leongis the "onboarding resource" user stories ready to move into "proposed"?21:21
*** cknight has quit IRC21:21
Arkady_Kanevskyfor new platforms is there a requirement for Ironic?21:21
cloudrancherso, overall, taking lots of time and the new project is going to be a real challenge21:21
ShamailI thought blueprints were being split, not user story?21:21
cloudrancherno Ironic at this time21:21
kencjohnstonShamail Ahh, I see, sorry I can't read. Makes sense21:22
cloudrancherkeeping it simple but Nova was pretty clear we need to be in a new project21:22
cloudrancherand nobody on the team has done that yet21:22
cloudrancherbut overall we are makign progress21:22
*** bradjones has joined #openstack-meeting-alt21:22
*** bradjones has quit IRC21:22
*** bradjones has joined #openstack-meeting-alt21:22
barrettcloudrancher: what's your timeframe for moving from Draft to Proposed?21:23
cloudrancherthats about it. We will probaly have last meeting this week due to holidays, then restart in Jan.21:23
cloudrancherI think we need to spend more time on the blueprints first21:23
cloudrancherso Jan it probably the best21:23
cloudrancherin reality it is unlikly we will get anything into Mitaka other than PTL awareness21:24
barrettBlueprints aren't required for this per our work flow21:24
leongsorry... pls correct me if i'm wrong.. based on the "workflow", the "blueprint" is address in "Tracked21:24
cloudrancheryes, but I think we need to get a better idea of what we are trying to do21:24
cloudrancherthe Platform9 team had a much broader scope with VMWare21:25
cloudrancherand the IBM team had more SAN and Neutron than Platform921:25
cloudrancherso - things are moving around a bit21:25
Shamailleong: correct... I agree with Barrett about possibly considering a move to proposed... You can still refine items...21:25
barrettMoving from Draft to proposed requires a good user story write-up that describes the requirements, etc.21:25
barrettNot the solution21:25
ShamailBarrett: +121:25
leongi think at this stage ("draft"), the team should focus on the "stories" or "problem statements" but not so much on "blueprint".21:25
barrettSee the work flow here:21:25
barrett#link: https://wiki.openstack.org/wiki/ProductTeam/User_Stories#User_Story_Workflow21:25
cloudrancherright. I'd like to give it a few more weeks because the requirements may change21:25
*** mhickey has quit IRC21:26
*** aginwala has joined #openstack-meeting-alt21:26
cloudrancherThe intial user story was a one way trip to OpenStack from KVM/other but the Platform9 approach was two way21:26
cloudrancherso, there was lots of value in that and it's not reflected in the User Story right now21:26
leongif the team thinks that the existing "stories/problem statements" is sufficient, then it can be considered moving into "proposed"  or even "tracked"21:26
pchadwickIsn't that "outboarding"?21:27
*** mhickey has joined #openstack-meeting-alt21:27
*** jungleboyj has quit IRC21:27
pchadwickIf we want to do it bi-directionally, then it should be called migration or something.21:27
pchadwickFWIW, most of the customers I talk to view it as one-way.21:27
cloudrancherit's interesting because the two way capabiloity allows for leveraging both management interfacs21:27
Shamailpchadwick: +121:27
cloudrancherwe may end up there21:27
ShamailI wouldn't want that part delaying the rest of it...21:28
pchadwickshamail: +121:28
barrettpchadwick: this is about onboarding infrastructure for the purpose of tracking...not onboarding legacy apps21:28
pchadwickright - and once the infrastructure is there, why would anyone move it back?21:28
cloudrancherI won't think it will, but adding abotu 30% more team is taking some time to integrate views21:28
*** mhickey has quit IRC21:28
*** Swami has quit IRC21:28
barrettcloudrancher: pls look over the work flow. If you really need more time to capture the requirements fine. I'd like to see us follow the work flow as much as we can, as we execute through it theses first couple of times to test it out and be ready to refine it at our midcyle in Feb21:28
leongthe current "onboarding infrastructure resources" are leaning towards a "two-way" capabilities rather than just "one-way" migration.21:29
cloudrancherok. I'll work on21:29
cloudrancherit a bit21:29
*** Swami has joined #openstack-meeting-alt21:29
*** kencjohn_ has joined #openstack-meeting-alt21:29
*** kencjohnston has quit IRC21:29
cloudrancherI'm just saying we need a bit more time to digest21:29
barrettOK - Any other comments/questions on this one?21:29
cloudranchernope. thats it for now21:29
barrettThanks21:29
barrettNext up is Onboarding Legacy Apps - Gerd are you here?21:30
barrettI think that team is still in the forming stage. I will connect with Gerd offline and ask him to send an update on the ML.21:30
leongGerd has drafted a Google Doc here to kick start the process.21:31
leong#link: https://drive.google.com/open?id=122EzpeD2d-ZzpGyoruoOANCNvQv-ms70og6neQCMpsk21:31
barrettThanks LEong21:31
barrettNext up is Complex Instance Placement - Steve can you give an update?21:31
ShamailPing ago rdon21:31
ShamailPing sgordon21:32
sgordonmmmyes21:32
barrettThanks21:32
sgordonalthough i briefly lost my link, second21:32
sgordonso the open review for updates is21:33
sgordon#link https://review.openstack.org/#/c/251442/21:33
sgordoni haven't had a chance to integrate the feedback as yet21:33
*** mhickey has joined #openstack-meeting-alt21:33
kencjohn_ok, I think barrett is ready to approve once you and Callum get to a consensus point21:33
*** EricGonczer_ has joined #openstack-meeting-alt21:34
barrettkencjohn: +1 It seemed like there was some discussion going on with Arkday21:34
Arkady_KanevskyI +1 it already and I am original owner21:35
Arkady_Kanevskybut I do not have +2 priviliges21:35
kencjohn_Arkady_Kanevsky Actually you -1'd21:35
barrettAre all of the questions resolved sgordon?21:35
sgordon???21:35
sgordonyeah and you arent the original owner21:35
sgordonlol21:36
ShamailArkady_Kanevsky: I believe you are referring to lifecycle management, not CIm21:36
sgordonit's all from calum21:36
ShamailCIM*21:36
sgordonwith minor edits21:36
ShamailPlease let us know once you and Calum close the loop.21:37
sgordonwill do21:37
barrettshamail +121:37
barrettOK - Any other User Stories to be discussed?21:37
kencjohn_one quick note on the ROlling upgrades21:37
kencjohn_#link ttps://review.openstack.org/25438921:37
kencjohn_is a review to promote to Tracked21:37
leongone more user story: db_hygience21:38
*** xyang1 has quit IRC21:38
leongi think db_hygience is ready to merged into "draft", now pending "core reviewer" approval.21:38
barrettkencyjohn: +121:38
kencjohn_ack bad link21:38
leong#link: https://review.openstack.org/#/c/237178/21:38
ShamailThanks kencjohn_ and me ong21:38
Shamailleong*21:38
kencjohn_#link https://review.openstack.org/#/c/254389/21:38
ShamailMy mobile IRC client is bad.21:39
barrettThanks Leong - will check the user story and make comments.21:39
barrettAnything else?21:39
barrett#topic Mid Cycle Planning21:40
*** openstack changes topic to "Mid Cycle Planning (Meeting topic: Product Working Group)"21:40
*** aginwala has quit IRC21:40
barrettAs far as I can tell Ops is set on 2/15 & 16 in Manchester21:40
barrettRackspace has offered to host our Midcycle at their London offices right after that21:41
leongare we going to meet in Manchester or London? or both?21:41
*** xyang1 has joined #openstack-meeting-alt21:41
ShamailI had an action to confirm whether Manchester is the "official" ops summit.  I sent an email on the ops list but did not hear back... I think based on what I've seen... Manchester is the main one this time21:41
ShamailAlthough others might happen in North America, Asia still21:41
*** kzaitsev_mb has joined #openstack-meeting-alt21:41
kencjohn_leong I thinkt he idea is yes, Ops meetup in Manchester, three hour train to London and then PWG Mid-Cycle21:41
Shamailleong: we would need to do both if we are co-locating21:41
barrettShamail: I think Manchester is the offical one and satelite ops meetups might happen21:42
leongi see...need to add that into travel plan for approval.. :-)21:42
barrettkencjohn: That is the proposal21:42
ShamailYep. That's the likely scenario21:42
barrettWho would not be able to make a meet-up in London in Feb?21:42
rockyg_Do we have better dates on that?21:43
kencjohn_2/17-1821:43
rockyg_Cool.  I can make that.21:43
barrettkencjohn_ +121:43
cloudrancherI'm doubtful I could go at this point21:43
*** mwagner_lap has joined #openstack-meeting-alt21:43
pchadwickshould be ok for me21:43
MeganRI need to put in for approval, so I am tentative at this point21:43
ShamailThanks kencjohn_21:44
leongmine also pending approval21:44
Arkady_KanevskyI will not be able to make it to Manchester.21:44
barrettcloudrancher: Can you check it with your management?21:44
ShamailI can confirm after January but no conflicts21:44
Arkady_Kanevskyshould be able to make it in USA.21:44
barrettMegan: Can you check with your management?21:44
cloudrancherI'll have to check after Jan21:44
barrettI was hoping to nail down date and time by end of next week.21:45
MeganR@barrett: I probably won't know until after the holiday - that's the main focus right now21:45
barrettMeganR: Understand21:45
Shamailill try to confirm before then...21:45
ShamailMeganR: welcome to retail :)21:45
kencjohn_barrett Should we ask the reverse, who can confirm today?21:45
barrettMegan, Cloudrancher: Getting confirmation in Jan would apply to a UK based midcycle or US base midcycle, right?21:45
leongor do we want to plan for a USA meet-up, seems like more people can do in USA21:46
MeganR:)21:46
annilaii most likely can make it to Manchester21:46
ShamailI think co-location withs ops summit is important...21:46
annilaiUS is better21:46
rockyg_Maybe we send emissaries to England and meet in US?21:46
MeganR@barrett: I am aiming for Manchester - have already mentioned it to mgmt.21:46
barrettWe could do 2 things: Have a subset of our team attend Ops in Manchester and then have a US based midcycle immediately afterwards21:47
Shamailrockyg: that might make approval for some harder... The "2-in-1" value prop wouldnt exist21:47
pchadwickJust to be clear, we would attend the Ops Summit and then have the Product meeting?21:47
kencjohn_I'm happy to be the emissary but I likely won't make a US meetup if I travel for the Ops mid-cycle21:47
sgordoni believe we had at least two folks who cand make it21:47
sgordon*can21:47
barrettpchadwich: +121:47
*** eilert has quit IRC21:47
leongwhat about this: everyone pls check with manegement approval and feedback early Jan (give a date).21:47
*** xyang1 has quit IRC21:47
leongif majority people cannot got, then plan for a local USA meetup?21:48
annilaiI can21:48
kencjohn_Shamail rockyg_ I'd be affected by the lack of 2-in-121:48
rockyg_OK.  Good to know.21:48
ShamailI could foresee the same... I can easily justify our mid-cycle but would have a hard time making tbe ops summit without it21:48
MeganR+121:49
barrettWe can put this on the agenda for 1/11 meeting. Everyone pls work on understanding what they can do ahead of that meeting.21:49
leongtime track.. we have less than 10 minutes21:49
pchadwickThis team meeting would be more important for me as well.21:49
barrettLeong: Thanks21:49
barrett#topic Stable Branch Project21:49
*** openstack changes topic to "Stable Branch Project (Meeting topic: Product Working Group)"21:49
*** vgridnev has quit IRC21:49
Shamailbarrett: lets revisit next week?  While all of us try to figure out commit for UK?21:49
barrettRockyG - Can you take this one?21:49
barrettShamail: +121:50
rockyg_Yah.  So a very quick write up here:https://etherpad.openstack.org/p/Stable_Release_Maintenance_-_Prod_WG21:50
*** spzala has quit IRC21:50
barrett#link: https://etherpad.openstack.org/p/Stable_Release_Maintenance_-_Prod_WG21:50
rockyg_There are converging interests on getting releases supported beyond the 1 year point21:51
Arkady_Kanevskyreview.openstack.org is not responding. so cannot comment on reviews21:51
kencjohn_rockyg_ In reading the document, why was it deemed that PWG would be a good contributor above say, the Ops or other User Committees?21:51
rockyg_Minimum for upgrade, but also to reduce work across companies who provide support21:51
pchadwickIs there any converging interest on picking one release per year to be long term supported?21:51
pchadwickthat is the only real way to reduce the multi-company workload.21:52
rockyg_Mainly because it's a corporate thing.  Companies provide the long support21:52
rockyg_So, it is pretty much a "product"21:52
rockyg_with the same planning and support needs21:52
rockyg_Users and ops are consumers21:53
annilai also, we need business case for it21:53
kencjohn_Hmm, ok, I guess I have some concern with the general approach especially as it relates to Rolling Upgrades.21:53
annilaithat's why product WG is a good forum for it.21:53
rockyg_There is talk of that, but first, we need to figure out how to just extending a release could work21:53
Shamailkencjohn_: probably because the main limiting factor will be development resources, therefore asking the majority of contributing companies to get involved is the logical next step.21:53
barrettI think that many view the Product WG as the planning arm for OpenStack - and this is a product planning issue21:53
kencjohn_I realize this stable branch project is moving forward, but I'd rather see this group focus on things that remove the barriers to upgrades instead of adding additional stickiness to any given release21:54
rockyg_The first focus is how to keep the upgrade tests working.21:54
Shamailbarrett: +121:54
cloudrancherEven with rolling upgrades companies like to test and validate new releases21:54
kencjohn_That way new features are in the hands of users more quickly, instead of a multiyear feedback sycle21:54
barrettkencjohn_: I think that finding that balance point will be part of the exercise for defining criteria and process21:54
rockyg_barrett: ++21:55
barrettFor today, I'd like to get a show of hands of who would be interested in joining a subteam to work on this?21:55
pchadwickWe need to define what "support" means:21:55
pchadwickaccepting bug fix?21:55
rockyg_Also, if only one company has to backport any patch, the amount of work in each company participating lessens21:55
barrettTarget time frame for 1st proposal is end of Jan21:55
rockyg_o/21:55
kencjohn_barrett o/21:55
barrettThanks Rockyg21:55
sgordonw.r.t. development resources i would think these showing up to help maintain stable21:56
barrettThanks Kencjohn_21:56
sgordonwould be a precursor to extending the lifecycle21:56
rockyg_sgordon: ++21:56
pchadwickyes - but most of us already do it.21:56
rockyg_Likely some framework effort, too.21:56
sgordonpchadwick, well that's kinda what im getting at21:56
sgordonwe do in fact have multiple working on upstream stable21:56
pchadwickAnecdotally, the problem is that the core teams are sometimes slow to accept backports.21:57
sgordonthis conversation is posited on the fact that others dont21:57
sgordonso why is that?21:57
rockyg_sgordon:  exactly.  if we each contribute directly, not only does the workload go down for each, but we get credit for it in the community21:57
*** edwardb has quit IRC21:57
sgordonim skeptical that it's just because the branch closes21:57
sgordonbecause they aren't there before that either21:57
Shamailrockyg_: +121:57
barrettFolks - Don't mean to cut-off discussion, but we've got 3 mins left. Let's get a team formed where there can be more discussion to create a proposal. Then they can bring it back into this group for review/feedback. OK?21:57
rockyg_The stable team will be doing the accepting of the backports21:57
leongbarrett: +121:58
Shamailbarrett: +121:58
annilai+121:58
pchadwick+121:58
MeganRbarrett +121:58
pchadwickI can work on the team.21:58
rockyg_sgordon: lots more.  Rolling python package cahnges makes old code break21:58
barrettThanks pchadwick21:58
Shamailbarrett: I'd like to defer the CPL topic to next week but I'll send an email to the ML this week on it.21:58
cloudrancherrope me in too21:58
rockyg_Kewl.21:58
barrettRockyg: Will you take the action to pull together the interested folks for an initial meeting?21:58
kencjohn_cloudrancher "rope" nice :)21:58
rockyg_Sure.21:59
Shamailkencjohn_: lol21:59
cloudrancher<unintentional pun>21:59
rockyg_This will likely dovetail into some of the other rolling upgrades/updates21:59
barrett#action RockyG setup kick off meeting for Stable Branch team with Kenny, Jay, Pete, Carol.21:59
kencjohn_cloudrancher I could hear the Texas drawl through my screen21:59
barrettGreat22:00
pchadwickOne interesting question for the mid-cycle ops is how many ops will really do regular upgrades22:00
cloudranchersorry - I really do talk that way sometimes22:00
sgordoni would also like to be involved in framing the plan for stable22:00
pchadwickvs most of my customers wanting to wait 12 months minimum22:00
sgordonas a rep of a distributor who already has people contributing to stable...22:00
barrett#action Rocky  Include Steve in the kickoff meeting too22:00
sgordonwhich is where a lot of my questions are coming from22:00
barrettThanks folks - we22:00
rockyg_I think the 12 months minimum is pretty standard at customer sites22:00
barrettWe're out of time for today.22:00
Shamailbarrett: i have to leave but did my plan on CPL sound good?22:00
pchadwickshamail: +122:01
leongshamail: +122:01
annilai+122:01
barrettShamail: Is the plan to address at midcycle?22:01
ShamailNo, ill send to ML and would like to have it on agenda next week22:01
rockyg_Good.22:01
barrettShamail - OK.22:01
barrett#endmeeting22:01
*** openstack changes topic to "Bugs (Meeting topic: neutron_dvr)"22:01
openstackMeeting ended Mon Dec  7 22:01:53 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2015/product_working_group.2015-12-07-21.00.html22:01
ShamailML this week and IRC next week.22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2015/product_working_group.2015-12-07-21.00.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2015/product_working_group.2015-12-07-21.00.log.html22:01
pchadwickbye22:02
rockyg_Thanks all.22:02
ShamailThanks all!! Bye22:02
*** pchadwick has left #openstack-meeting-alt22:02
*** Shamail has quit IRC22:02
*** leong has quit IRC22:02
*** barrett has left #openstack-meeting-alt22:02
*** Mr_T has left #openstack-meeting-alt22:03
*** kozhukalov_ has quit IRC22:04
*** scohen1 has left #openstack-meeting-alt22:05
*** dpk_ has quit IRC22:05
*** aginwala has joined #openstack-meeting-alt22:08
*** merooney has quit IRC22:11
*** rockyg_ has quit IRC22:13
*** cknight has joined #openstack-meeting-alt22:13
*** yamamoto has quit IRC22:14
*** aginwala has quit IRC22:15
*** e0ne has joined #openstack-meeting-alt22:15
*** hoangcx has quit IRC22:15
*** lbelivea has quit IRC22:16
*** Arkady_Kanevsky has quit IRC22:16
*** lbelivea has joined #openstack-meeting-alt22:16
*** mhickey has quit IRC22:18
*** hoangcx has joined #openstack-meeting-alt22:18
*** lisaclark1 has quit IRC22:19
*** hoangcx has quit IRC22:20
*** aginwala has joined #openstack-meeting-alt22:21
*** edwardb has joined #openstack-meeting-alt22:25
*** dprince has quit IRC22:27
*** eliqiao_ has joined #openstack-meeting-alt22:27
*** lisaclark1 has joined #openstack-meeting-alt22:28
*** eliqiao has quit IRC22:28
*** Leo_ has joined #openstack-meeting-alt22:29
*** lisaclark1 has quit IRC22:30
*** annilai has quit IRC22:31
*** lisaclark1 has joined #openstack-meeting-alt22:31
*** jungleboyj has joined #openstack-meeting-alt22:32
*** aginwala has quit IRC22:34
*** eilert has joined #openstack-meeting-alt22:34
*** balajiiyer has quit IRC22:35
*** Leo_ has quit IRC22:36
*** lisaclark1 has quit IRC22:38
*** lisaclark1 has joined #openstack-meeting-alt22:38
*** kfarr has quit IRC22:39
*** lisaclark1 has quit IRC22:42
*** neelashah has quit IRC22:46
*** pdesai has joined #openstack-meeting-alt22:48
*** rsyed is now known as rsyed_away22:48
*** amitgandhinz has quit IRC22:48
*** pdesai has left #openstack-meeting-alt22:49
*** Sukhdev has quit IRC22:50
*** sneti has quit IRC22:52
*** ashleighfarnham has joined #openstack-meeting-alt22:56
*** aginwala has joined #openstack-meeting-alt22:58
*** gyee has joined #openstack-meeting-alt23:01
*** jecarey has quit IRC23:01
*** edwardb has quit IRC23:02
*** sylwesterB has joined #openstack-meeting-alt23:04
*** e0ne has quit IRC23:04
*** jmcbride has quit IRC23:06
*** spotz is now known as spotz_zzz23:06
*** minwang2 has joined #openstack-meeting-alt23:06
*** Leo_ has joined #openstack-meeting-alt23:08
*** jichen has quit IRC23:09
*** sylwesterB has quit IRC23:09
*** Leo_ has quit IRC23:12
*** Leo_ has joined #openstack-meeting-alt23:12
*** kzaitsev_mb has quit IRC23:12
*** Leom has joined #openstack-meeting-alt23:14
*** kencjohn_ has quit IRC23:14
*** Leo_ has quit IRC23:14
*** Leo_ has joined #openstack-meeting-alt23:15
*** Leom has quit IRC23:19
*** weshay_xchat has quit IRC23:19
*** nurla has quit IRC23:21
*** absubram has quit IRC23:23
*** boris-42_ has quit IRC23:23
*** nurla has joined #openstack-meeting-alt23:25
*** yamamoto has joined #openstack-meeting-alt23:25
*** salv-orl_ has joined #openstack-meeting-alt23:25
*** nurla has joined #openstack-meeting-alt23:25
*** banix has quit IRC23:28
*** salv-orlando has quit IRC23:28
*** alex_xu has quit IRC23:29
*** yamamoto has quit IRC23:31
*** alex_xu has joined #openstack-meeting-alt23:31
*** kei_yama has joined #openstack-meeting-alt23:34
*** spzala has joined #openstack-meeting-alt23:36
*** aginwala has quit IRC23:40
*** aginwala has joined #openstack-meeting-alt23:41
*** kzaitsev_mb has joined #openstack-meeting-alt23:47
*** jecarey has joined #openstack-meeting-alt23:48
*** amitgandhinz has joined #openstack-meeting-alt23:49
*** nateziemann has quit IRC23:50
*** tonytan_brb has joined #openstack-meeting-alt23:51
*** boris-42_ has joined #openstack-meeting-alt23:52
*** jecarey has quit IRC23:53
*** dimtruck is now known as zz_dimtruck23:54
*** tonytan_brb has quit IRC23:54
*** amitgandhinz has quit IRC23:54
*** tonytan4ever has quit IRC23:55
*** cknight has quit IRC23:55
*** Leo_ has quit IRC23:57
*** sigmavirus24 is now known as sigmavirus24_awa23:57
*** lisaclark1 has joined #openstack-meeting-alt23:58
*** slagle has quit IRC23:58
*** hyakuhei_ has quit IRC23:59
*** edwardb has joined #openstack-meeting-alt23:59
*** slagle has joined #openstack-meeting-alt23:59

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