Wednesday, 2014-12-03

*** colinmcnamara has quit IRC00:00
*** baoli has quit IRC00:00
*** tdruiva has quit IRC00:01
*** sorrison_ has joined #openstack-meeting-alt00:05
*** edwardb has quit IRC00:06
*** sorrison_ has quit IRC00:08
*** david-lyle is now known as david-lyle_afk00:08
*** sorrison_ has joined #openstack-meeting-alt00:08
*** sorrison_ is now known as sorrison00:09
*** colinmcnamara has joined #openstack-meeting-alt00:09
*** tzn has quit IRC00:09
*** mwagner_lap has joined #openstack-meeting-alt00:09
*** edwardb has joined #openstack-meeting-alt00:09
*** sunnyr_ has quit IRC00:10
*** AJK__ has joined #openstack-meeting-alt00:10
*** Sukhdev has joined #openstack-meeting-alt00:10
*** tzn has joined #openstack-meeting-alt00:11
*** ivar-laz_ has joined #openstack-meeting-alt00:11
*** xuhanp has joined #openstack-meeting-alt00:13
*** sunnyr has joined #openstack-meeting-alt00:13
*** ivar-lazzaro has quit IRC00:14
*** safchain has quit IRC00:14
*** MarkAtwood has quit IRC00:15
*** MarkAtwood has joined #openstack-meeting-alt00:16
*** MarkAtwood has quit IRC00:16
*** yuanying has quit IRC00:23
*** edwardb has quit IRC00:23
*** yuanying has joined #openstack-meeting-alt00:23
*** yuanying has quit IRC00:24
*** jemangs has quit IRC00:25
*** jemangs_ has joined #openstack-meeting-alt00:25
*** EricGonczer_ has quit IRC00:26
*** daneyon has quit IRC00:26
*** colinmcnamara has quit IRC00:27
*** yuanying has joined #openstack-meeting-alt00:27
*** kebray has joined #openstack-meeting-alt00:28
*** tzn has quit IRC00:31
*** dims_ has joined #openstack-meeting-alt00:31
*** emagana_ has quit IRC00:32
*** edwardb has joined #openstack-meeting-alt00:33
*** dims has quit IRC00:34
*** pballand has joined #openstack-meeting-alt00:35
*** yamamoto has joined #openstack-meeting-alt00:36
*** colinmcnamara has joined #openstack-meeting-alt00:37
*** tellesnobrega has quit IRC00:37
*** xuhanp has quit IRC00:38
*** yamamoto has quit IRC00:40
*** tellesnobrega has joined #openstack-meeting-alt00:44
*** dave-mccowan_ has joined #openstack-meeting-alt00:46
*** dave-mccowan has quit IRC00:49
*** dave-mccowan_ is now known as dave-mccowan00:49
*** zz_dimtruck is now known as dimtruck00:56
*** tdruiva has joined #openstack-meeting-alt00:58
*** pballand has quit IRC00:58
*** pballand has joined #openstack-meeting-alt00:59
*** ijw has joined #openstack-meeting-alt01:01
*** pballand has quit IRC01:02
*** tdruiva has quit IRC01:02
*** emagana has joined #openstack-meeting-alt01:03
*** arnaud__ has joined #openstack-meeting-alt01:05
*** mattgriffin has joined #openstack-meeting-alt01:05
*** ijw has quit IRC01:06
*** emagana has quit IRC01:08
*** yuanying has quit IRC01:08
*** rmoe has quit IRC01:08
*** yuanying has joined #openstack-meeting-alt01:09
*** Sukhdev has quit IRC01:09
*** yuanying has quit IRC01:15
*** baoli has joined #openstack-meeting-alt01:15
*** yuanying has joined #openstack-meeting-alt01:16
*** yuanying has quit IRC01:17
*** yamamoto_ has joined #openstack-meeting-alt01:18
*** daneyon has joined #openstack-meeting-alt01:18
*** yuanying has joined #openstack-meeting-alt01:19
*** mattgriffin has quit IRC01:23
*** emagana has joined #openstack-meeting-alt01:23
*** teran has quit IRC01:24
*** dboik has joined #openstack-meeting-alt01:24
*** Longgeek has joined #openstack-meeting-alt01:25
*** Weiting has joined #openstack-meeting-alt01:26
*** dboik_ has joined #openstack-meeting-alt01:27
*** dimtruck is now known as zz_dimtruck01:28
*** dboik has quit IRC01:29
*** alex_xu has joined #openstack-meeting-alt01:29
*** mattgriffin has joined #openstack-meeting-alt01:30
*** Longgeek has quit IRC01:30
*** Riddhi has quit IRC01:30
*** spzala has quit IRC01:31
*** tsekiyam_ has joined #openstack-meeting-alt01:32
*** padkrish has quit IRC01:32
*** EricGonczer_ has joined #openstack-meeting-alt01:32
*** zhidong_ has joined #openstack-meeting-alt01:32
*** yuanying has quit IRC01:33
*** padkrish has joined #openstack-meeting-alt01:33
Weitingzhidong_: Test01:34
*** padkrish has quit IRC01:34
*** mtanino has quit IRC01:35
*** tsekiyama has quit IRC01:35
*** test_ has joined #openstack-meeting-alt01:35
*** rpjr has quit IRC01:35
*** tsekiyam_ has quit IRC01:36
*** rmoe has joined #openstack-meeting-alt01:36
*** rpjr has joined #openstack-meeting-alt01:36
*** padkrish has joined #openstack-meeting-alt01:37
*** yuanying has joined #openstack-meeting-alt01:38
*** markmcclain has quit IRC01:39
*** jaypipes has quit IRC01:39
*** yuanying has quit IRC01:40
*** rpjr_ has joined #openstack-meeting-alt01:40
*** rpjr has quit IRC01:40
*** nelsnelson has quit IRC01:43
*** zhidong_ has quit IRC01:44
*** yamamoto_ has quit IRC01:47
*** colinmcnamara has quit IRC01:47
*** EricGonczer_ has quit IRC01:47
*** emagana has quit IRC01:48
*** emagana has joined #openstack-meeting-alt01:48
*** test_ has quit IRC01:49
*** EricGonczer_ has joined #openstack-meeting-alt01:49
*** yuanying has joined #openstack-meeting-alt01:50
*** sunnyr has quit IRC01:52
*** sunnyr has joined #openstack-meeting-alt01:52
*** mattgriffin has quit IRC01:52
*** emagana has quit IRC01:52
*** emagana_ has joined #openstack-meeting-alt01:52
*** colinmcnamara has joined #openstack-meeting-alt01:54
*** daneyon has quit IRC01:54
*** zhidong_ has joined #openstack-meeting-alt01:55
*** nosnos has joined #openstack-meeting-alt01:56
*** emagana_ has quit IRC01:57
*** esker has quit IRC01:57
*** zhhuabj has quit IRC01:58
*** zhhuabj has joined #openstack-meeting-alt01:58
*** sarob has quit IRC01:59
*** tdruiva has joined #openstack-meeting-alt01:59
*** rpjr_ has quit IRC01:59
*** rpjr has joined #openstack-meeting-alt01:59
*** tdruiva has quit IRC02:03
*** rpjr has quit IRC02:03
*** Barker has joined #openstack-meeting-alt02:04
*** test_ has joined #openstack-meeting-alt02:06
test_who is huichun02:06
*** zhidong_ has quit IRC02:06
*** Weiting has quit IRC02:07
*** EricGonczer_ has quit IRC02:08
*** xuhanp has joined #openstack-meeting-alt02:08
*** kchen has joined #openstack-meeting-alt02:09
*** EricGonczer_ has joined #openstack-meeting-alt02:11
*** sunnyr has quit IRC02:11
*** jjmb has joined #openstack-meeting-alt02:12
*** sigmavirus24 is now known as sigmavirus24_awa02:12
*** huichun has joined #openstack-meeting-alt02:13
*** zz_dimtruck is now known as dimtruck02:13
huichuntest02:13
*** yamamoto_ has joined #openstack-meeting-alt02:14
*** huichun has quit IRC02:14
*** jde_ has joined #openstack-meeting-alt02:15
*** jde_ has left #openstack-meeting-alt02:15
*** kchen has left #openstack-meeting-alt02:17
*** kchen has joined #openstack-meeting-alt02:18
*** huichun has joined #openstack-meeting-alt02:21
*** EricGonczer_ has quit IRC02:22
*** kchen has quit IRC02:22
*** huichun has quit IRC02:22
*** ssw has joined #openstack-meeting-alt02:23
*** erkules_ has joined #openstack-meeting-alt02:23
*** ssw has quit IRC02:23
*** marcoemorais has quit IRC02:24
*** yuanying has left #openstack-meeting-alt02:24
*** huichun has joined #openstack-meeting-alt02:24
*** teran has joined #openstack-meeting-alt02:25
*** erkules has quit IRC02:25
*** kchen has joined #openstack-meeting-alt02:27
*** huichun has quit IRC02:29
*** teran has quit IRC02:29
*** padkrish has quit IRC02:29
*** huichun has joined #openstack-meeting-alt02:31
*** dims_ has quit IRC02:36
*** huichun has left #openstack-meeting-alt02:39
*** Barker has quit IRC02:41
*** huichun has joined #openstack-meeting-alt02:41
*** rushiagr_away is now known as rushiagr02:42
*** huichun has quit IRC02:43
*** huichun has joined #openstack-meeting-alt02:44
*** huichun has quit IRC02:45
*** test_ has quit IRC02:46
*** erkules_ has quit IRC02:49
*** erkules_ has joined #openstack-meeting-alt02:50
*** sigmavirus24_awa is now known as sigmavirus2402:52
*** salv-orlando has quit IRC02:53
*** mtanino has joined #openstack-meeting-alt02:54
*** esker has joined #openstack-meeting-alt02:57
*** dimtruck is now known as zz_dimtruck02:57
*** shwetaap has joined #openstack-meeting-alt03:01
*** ivar-laz_ has quit IRC03:03
*** ijw has joined #openstack-meeting-alt03:04
*** mattgriffin has joined #openstack-meeting-alt03:04
*** ivar-lazzaro has joined #openstack-meeting-alt03:04
*** edwardb_ has joined #openstack-meeting-alt03:07
*** edwardb has quit IRC03:07
*** dboik_ has quit IRC03:08
*** ijw has quit IRC03:08
*** ivar-lazzaro has quit IRC03:09
*** tzn has joined #openstack-meeting-alt03:09
*** Longgeek has joined #openstack-meeting-alt03:14
*** colinmcnamara has quit IRC03:15
*** dboik has joined #openstack-meeting-alt03:18
*** Longgeek has quit IRC03:19
*** sunrenjie has joined #openstack-meeting-alt03:21
*** ivar-lazzaro has joined #openstack-meeting-alt03:24
*** teran has joined #openstack-meeting-alt03:25
*** mattgriffin has quit IRC03:26
*** ivar-lazzaro has quit IRC03:26
*** rushiagr is now known as rushiagr_away03:27
*** ivar-lazzaro has joined #openstack-meeting-alt03:27
*** avozza is now known as zz_avozza03:27
*** alex_xu has quit IRC03:28
*** alex_xu has joined #openstack-meeting-alt03:29
*** Sukhdev has joined #openstack-meeting-alt03:30
*** teran has quit IRC03:30
*** david-ly_ has joined #openstack-meeting-alt03:32
*** zz_dimtruck is now known as dimtruck03:32
*** david-lyle_afk has quit IRC03:33
*** dims has joined #openstack-meeting-alt03:36
*** nosnos has quit IRC03:39
*** woodster_ has quit IRC03:40
*** ivar-laz_ has joined #openstack-meeting-alt03:41
*** kebray has quit IRC03:42
*** dims has quit IRC03:42
*** kchen has joined #openstack-meeting-alt03:43
*** achanda has joined #openstack-meeting-alt03:44
*** mattgriffin has joined #openstack-meeting-alt03:45
*** ivar-lazzaro has quit IRC03:45
*** ivar-laz_ has quit IRC03:46
*** harlowja_ is now known as harlowja_away03:47
*** hachao has quit IRC03:47
*** kchen has quit IRC03:47
*** hachao has joined #openstack-meeting-alt03:47
*** jaypipes has joined #openstack-meeting-alt03:48
*** ptoohill_ has joined #openstack-meeting-alt03:50
*** rwsu has quit IRC03:51
*** kchen has joined #openstack-meeting-alt03:52
*** rushiagr_away is now known as rushiagr03:53
*** markvoelker has quit IRC03:53
*** dboik has quit IRC03:57
*** zhidong has joined #openstack-meeting-alt03:58
*** kchen has quit IRC04:01
*** kchen has joined #openstack-meeting-alt04:01
*** kchen has left #openstack-meeting-alt04:01
*** zhidong has joined #openstack-meeting-alt04:02
*** mtanino has quit IRC04:02
*** ijw has joined #openstack-meeting-alt04:05
*** kchen has joined #openstack-meeting-alt04:05
*** kchen has quit IRC04:05
*** kchen has joined #openstack-meeting-alt04:06
*** kchen has left #openstack-meeting-alt04:06
*** edwardb_ has quit IRC04:08
*** ijw has quit IRC04:09
*** ptoohill_ has quit IRC04:09
*** kchen has joined #openstack-meeting-alt04:12
*** kchen has quit IRC04:13
*** kchen has joined #openstack-meeting-alt04:13
*** adrian_otto has joined #openstack-meeting-alt04:15
*** nosnos has joined #openstack-meeting-alt04:19
*** teran has joined #openstack-meeting-alt04:27
*** Haiying has joined #openstack-meeting-alt04:27
*** dave-mccowan has quit IRC04:29
*** SridharG has joined #openstack-meeting-alt04:31
*** teran has quit IRC04:31
*** zhidong has quit IRC04:35
*** zhidong has joined #openstack-meeting-alt04:37
*** mattgriffin has quit IRC04:38
*** achanda has quit IRC04:43
*** achanda has joined #openstack-meeting-alt04:43
*** achanda has quit IRC04:46
*** achanda_ has joined #openstack-meeting-alt04:46
*** bobmel has quit IRC04:46
*** sunrenjie has quit IRC04:46
*** SridharG has quit IRC04:47
*** david-ly_ has quit IRC04:48
*** david-lyle_afk has joined #openstack-meeting-alt04:49
*** carl_baldwin has joined #openstack-meeting-alt04:51
*** sunrenjie has joined #openstack-meeting-alt04:53
*** amotoki has joined #openstack-meeting-alt04:53
*** Riddhi has joined #openstack-meeting-alt04:56
*** Riddhi has joined #openstack-meeting-alt04:56
*** sunrenjie has quit IRC04:56
*** sunrenjie has joined #openstack-meeting-alt04:57
*** sunrenjie has quit IRC04:59
*** sunrenjie has joined #openstack-meeting-alt05:01
*** tdruiva has joined #openstack-meeting-alt05:01
*** Longgeek has joined #openstack-meeting-alt05:03
*** kopparam has joined #openstack-meeting-alt05:06
*** tdruiva has quit IRC05:06
*** sunrenjie has quit IRC05:06
*** sunrenjie has joined #openstack-meeting-alt05:07
*** Longgeek has quit IRC05:08
*** sunnyr has joined #openstack-meeting-alt05:08
*** zhidong has quit IRC05:09
*** sunrenjie has quit IRC05:10
*** Haiying has quit IRC05:13
*** Haiying has joined #openstack-meeting-alt05:13
*** alexiz has quit IRC05:15
*** sigmavirus24 is now known as sigmavirus24_awa05:15
*** sunrenjie has joined #openstack-meeting-alt05:16
*** kopparam has quit IRC05:20
*** kopparam has joined #openstack-meeting-alt05:21
*** Haiying has quit IRC05:22
*** achanda_ has quit IRC05:23
*** markvoelker has joined #openstack-meeting-alt05:24
*** teran has joined #openstack-meeting-alt05:27
*** weiting has joined #openstack-meeting-alt05:28
*** SridharG has joined #openstack-meeting-alt05:28
*** weiting has quit IRC05:29
*** Sukhdev has quit IRC05:29
*** marun has quit IRC05:30
*** tzn has quit IRC05:32
*** weiting has joined #openstack-meeting-alt05:32
*** teran has quit IRC05:33
*** Longgeek has joined #openstack-meeting-alt05:33
*** weiting has quit IRC05:33
*** weiting has joined #openstack-meeting-alt05:34
*** Haiying has joined #openstack-meeting-alt05:34
*** weiting has quit IRC05:34
*** weiting has joined #openstack-meeting-alt05:35
*** weiting has quit IRC05:35
*** sarob has joined #openstack-meeting-alt05:36
*** Haiying has quit IRC05:40
*** SridharG has quit IRC05:48
*** tzn has joined #openstack-meeting-alt05:48
*** Sukhdev has joined #openstack-meeting-alt05:50
*** achanda has joined #openstack-meeting-alt05:51
*** markvoelker has quit IRC05:51
*** markvoelker has joined #openstack-meeting-alt05:52
*** teran has joined #openstack-meeting-alt05:52
*** achanda has quit IRC05:55
*** markvoelker has quit IRC05:56
*** tzn has quit IRC05:59
*** kopparam has quit IRC06:00
*** tdruiva has joined #openstack-meeting-alt06:02
*** rpodolyaka1 has joined #openstack-meeting-alt06:02
*** sarob has quit IRC06:02
*** tzn has joined #openstack-meeting-alt06:03
*** tdruiva has quit IRC06:07
*** kopparam has joined #openstack-meeting-alt06:08
*** kopparam has quit IRC06:11
*** kopparam has joined #openstack-meeting-alt06:11
*** sunnyr has quit IRC06:12
*** woodster_ has joined #openstack-meeting-alt06:13
*** edwardb has joined #openstack-meeting-alt06:14
*** SridharG has joined #openstack-meeting-alt06:19
*** Longgeek has quit IRC06:20
*** k4n0 has joined #openstack-meeting-alt06:20
*** carl_baldwin has quit IRC06:20
*** Longgeek has joined #openstack-meeting-alt06:22
*** rpodolyaka1 has quit IRC06:26
*** carl_baldwin has joined #openstack-meeting-alt06:31
*** carl_baldwin has quit IRC06:33
*** markvoelker has joined #openstack-meeting-alt06:34
*** gyee_ has quit IRC06:36
*** nosnos has quit IRC06:38
*** sgotliv has joined #openstack-meeting-alt06:39
*** nosnos has joined #openstack-meeting-alt06:40
*** tzn has quit IRC06:43
*** rpjr has joined #openstack-meeting-alt06:47
*** SridharG has quit IRC06:49
*** Longgeek has quit IRC06:49
*** rpodolyaka1 has joined #openstack-meeting-alt06:52
*** arnaud__ has quit IRC06:53
*** _nadya_ has joined #openstack-meeting-alt06:54
*** nshaikh has joined #openstack-meeting-alt06:56
*** kopparam has quit IRC06:56
*** kopparam has joined #openstack-meeting-alt06:57
*** rpodolyaka1 has quit IRC06:59
*** rpodolyaka1 has joined #openstack-meeting-alt06:59
*** ijw has joined #openstack-meeting-alt07:00
*** teran has quit IRC07:01
*** Longgeek has joined #openstack-meeting-alt07:02
*** tdruiva has joined #openstack-meeting-alt07:03
*** arnaud__ has joined #openstack-meeting-alt07:03
*** ptoohill_ has joined #openstack-meeting-alt07:04
*** ptoohill_ has quit IRC07:04
*** ijw has quit IRC07:05
*** tdruiva has quit IRC07:08
*** ptoohill_ has joined #openstack-meeting-alt07:08
*** rpodolyaka1 has quit IRC07:11
*** anat_k has joined #openstack-meeting-alt07:12
*** anat_k has left #openstack-meeting-alt07:14
*** david-ly_ has joined #openstack-meeting-alt07:15
*** a_teem has quit IRC07:15
*** a_teem has joined #openstack-meeting-alt07:15
*** omelchek has quit IRC07:15
*** david-lyle_afk has quit IRC07:16
*** omelchek has joined #openstack-meeting-alt07:16
*** teran has joined #openstack-meeting-alt07:17
*** teran has quit IRC07:21
*** SridharG has joined #openstack-meeting-alt07:22
*** sgotliv has quit IRC07:26
*** tzn has joined #openstack-meeting-alt07:30
*** tzn has quit IRC07:41
*** arnaud__ has quit IRC07:43
*** jprovazn has joined #openstack-meeting-alt07:45
*** prmtl has joined #openstack-meeting-alt07:45
*** tzn has joined #openstack-meeting-alt07:46
*** arnaud__ has joined #openstack-meeting-alt07:49
*** Sukhdev has quit IRC07:50
*** alexbh has joined #openstack-meeting-alt07:51
*** ptoohill_ has quit IRC07:54
*** nkrinner has joined #openstack-meeting-alt07:59
*** SridharG has quit IRC08:00
*** ijw has joined #openstack-meeting-alt08:01
*** xuhanp has quit IRC08:03
*** teran has joined #openstack-meeting-alt08:03
*** tdruiva has joined #openstack-meeting-alt08:04
*** ijw has quit IRC08:06
*** _nadya_ has quit IRC08:07
*** tdruiva has quit IRC08:08
*** armax has quit IRC08:10
*** xuhanp has joined #openstack-meeting-alt08:16
*** ptoohill_ has joined #openstack-meeting-alt08:18
*** matrohon has joined #openstack-meeting-alt08:19
*** woodster_ has quit IRC08:20
*** salv-orlando has joined #openstack-meeting-alt08:25
*** ptoohill_ has quit IRC08:28
*** sergef has joined #openstack-meeting-alt08:28
*** arnaud__ has quit IRC08:29
*** arnaud__ has joined #openstack-meeting-alt08:29
*** Longgeek has quit IRC08:33
*** nyechiel has joined #openstack-meeting-alt08:33
*** Longgeek has joined #openstack-meeting-alt08:34
*** ajo has joined #openstack-meeting-alt08:37
*** jcoufal has joined #openstack-meeting-alt08:38
*** ihrachyshka has joined #openstack-meeting-alt08:47
*** jtomasek has joined #openstack-meeting-alt08:48
*** Longgeek has quit IRC08:49
*** safchain has joined #openstack-meeting-alt08:49
*** hareeshp has joined #openstack-meeting-alt08:51
*** Longgeek has joined #openstack-meeting-alt08:53
*** rpodolyaka1 has joined #openstack-meeting-alt08:55
*** rpodolyaka1 has left #openstack-meeting-alt08:57
*** erkules_ is now known as erkules09:00
*** dims has joined #openstack-meeting-alt09:03
*** sarob has joined #openstack-meeting-alt09:03
*** tdruiva has joined #openstack-meeting-alt09:05
*** ihrachyshka has quit IRC09:05
*** andreykurilin_ has joined #openstack-meeting-alt09:06
*** edwardb has quit IRC09:06
*** sarob has quit IRC09:08
*** dims has quit IRC09:08
*** edwardb has joined #openstack-meeting-alt09:09
*** tdruiva has quit IRC09:09
*** SridharG has joined #openstack-meeting-alt09:09
*** markvoelker has quit IRC09:10
*** markvoelker has joined #openstack-meeting-alt09:10
*** ddmitriev1 has quit IRC09:14
*** markvoelker has quit IRC09:15
*** pnavarro has joined #openstack-meeting-alt09:17
*** SridharG has quit IRC09:17
*** aleksandr_null has quit IRC09:21
*** e0ne has joined #openstack-meeting-alt09:24
*** xuhanp has quit IRC09:32
*** ndipanov_gone has quit IRC09:32
*** kopparam has quit IRC09:35
*** jcoufal has quit IRC09:40
*** alex_xu has quit IRC09:41
*** SridharG has joined #openstack-meeting-alt09:43
*** yamamoto_ has quit IRC09:44
*** xuhanp has joined #openstack-meeting-alt09:45
*** ndipanov has joined #openstack-meeting-alt09:48
*** sergef has quit IRC09:51
*** alexbh2 has joined #openstack-meeting-alt09:52
*** sergef has joined #openstack-meeting-alt09:52
*** alexbh has quit IRC09:52
*** SridharG has left #openstack-meeting-alt09:55
*** HeOS has joined #openstack-meeting-alt09:58
*** ijw has joined #openstack-meeting-alt10:03
*** tdruiva has joined #openstack-meeting-alt10:06
*** ijw has quit IRC10:08
*** tdruiva has quit IRC10:10
*** e0ne has quit IRC10:10
*** yamamoto_ has joined #openstack-meeting-alt10:11
*** e0ne has joined #openstack-meeting-alt10:12
*** sgotliv has joined #openstack-meeting-alt10:13
*** andreykurilin_ has quit IRC10:14
*** ihrachyshka has joined #openstack-meeting-alt10:14
*** zz_avozza is now known as avozza10:15
*** colinmcnamara has joined #openstack-meeting-alt10:20
*** arnaud__ has quit IRC10:26
*** Longgeek has quit IRC10:27
*** Longgeek has joined #openstack-meeting-alt10:30
*** kopparam has joined #openstack-meeting-alt10:30
*** Longgeek has quit IRC10:35
*** zz_johnthetubagu is now known as johnthetubaguy10:39
*** xuhanp has quit IRC10:40
*** Longgeek has joined #openstack-meeting-alt10:40
*** yamamoto_ has quit IRC10:41
*** shwetaap has quit IRC10:42
*** jcoufal has joined #openstack-meeting-alt10:42
*** Kiall_ is now known as Kiall10:48
*** _nadya_ has joined #openstack-meeting-alt10:48
*** derekh has joined #openstack-meeting-alt10:50
*** Longgeek has quit IRC10:50
*** Longgeek has joined #openstack-meeting-alt10:52
*** adrian_otto has quit IRC10:55
*** teran has quit IRC10:59
*** teran has joined #openstack-meeting-alt11:01
*** e0ne has quit IRC11:02
*** e0ne_ has joined #openstack-meeting-alt11:02
*** e0ne_ has quit IRC11:02
*** e0ne has joined #openstack-meeting-alt11:03
*** edwardb has quit IRC11:05
*** ijw has joined #openstack-meeting-alt11:05
*** edwardb has joined #openstack-meeting-alt11:05
*** tdruiva has joined #openstack-meeting-alt11:06
*** ijw has quit IRC11:09
*** tdruiva has quit IRC11:11
*** edwardb has quit IRC11:11
*** edwardb has joined #openstack-meeting-alt11:21
*** andreaf has joined #openstack-meeting-alt11:22
*** k4n0 has quit IRC11:23
*** alex_xu has joined #openstack-meeting-alt11:25
*** dims has joined #openstack-meeting-alt11:30
*** nshaikh has quit IRC11:31
*** sgotliv has quit IRC11:32
*** gholler has joined #openstack-meeting-alt11:32
*** yamahata has joined #openstack-meeting-alt11:38
*** yamamoto has joined #openstack-meeting-alt11:42
*** sgotliv has joined #openstack-meeting-alt11:44
*** _nadya_ has quit IRC11:46
*** yamamoto has quit IRC11:47
*** prmtl has quit IRC11:50
*** prmtl has joined #openstack-meeting-alt11:51
*** edwardb has quit IRC11:52
*** denis_makogon has joined #openstack-meeting-alt11:52
*** beagles has quit IRC11:52
*** beagles has joined #openstack-meeting-alt11:53
*** edwardb has joined #openstack-meeting-alt11:53
*** _amrith_ is now known as amrith11:54
*** yamahata has quit IRC11:57
*** _nadya_ has joined #openstack-meeting-alt11:58
*** ijw has joined #openstack-meeting-alt12:06
*** kopparam has quit IRC12:06
*** tdruiva has joined #openstack-meeting-alt12:07
*** kopparam has joined #openstack-meeting-alt12:09
*** ijw has quit IRC12:11
*** tdruiva has quit IRC12:11
*** tdruiva has joined #openstack-meeting-alt12:14
*** julim has joined #openstack-meeting-alt12:18
*** funzo has quit IRC12:20
*** kopparam has quit IRC12:27
*** Longgeek has quit IRC12:28
*** Longgeek has joined #openstack-meeting-alt12:30
*** colinmcnamara has quit IRC12:31
*** nyechiel has quit IRC12:31
*** nyechiel_ has joined #openstack-meeting-alt12:31
*** lpabon has joined #openstack-meeting-alt12:33
*** funzo has joined #openstack-meeting-alt12:40
*** EricGonczer_ has joined #openstack-meeting-alt12:41
*** shwetaap has joined #openstack-meeting-alt12:45
*** stannie has joined #openstack-meeting-alt12:48
*** ruhe has left #openstack-meeting-alt12:52
*** shwetaap has quit IRC13:00
*** woodster_ has joined #openstack-meeting-alt13:00
*** ijw has joined #openstack-meeting-alt13:07
*** cbouch has joined #openstack-meeting-alt13:08
*** Murali has joined #openstack-meeting-alt13:08
*** dprince has joined #openstack-meeting-alt13:09
*** rushiagr is now known as rushiagr_away13:10
*** nyechiel_ has quit IRC13:11
*** nyechiel_ has joined #openstack-meeting-alt13:11
*** ijw has quit IRC13:11
*** jrakerevelant has joined #openstack-meeting-alt13:11
*** kopparam has joined #openstack-meeting-alt13:12
*** radez_g0n3 is now known as radez13:16
*** DaSchab has joined #openstack-meeting-alt13:16
*** jjmb has quit IRC13:17
*** xuhanp has joined #openstack-meeting-alt13:17
*** mestery has quit IRC13:17
*** prmtl has quit IRC13:19
*** prmtl has joined #openstack-meeting-alt13:20
*** bknudson1 has quit IRC13:21
*** prmtl has quit IRC13:24
*** prmtl has joined #openstack-meeting-alt13:25
*** HeOS_ has quit IRC13:28
*** shwetaap has joined #openstack-meeting-alt13:32
*** EricGonc_ has joined #openstack-meeting-alt13:33
*** EricGonc_ has quit IRC13:33
*** kopparam has quit IRC13:33
*** jaypipes is now known as jaypipes-afk13:34
*** kopparam has joined #openstack-meeting-alt13:36
*** hogepodge has quit IRC13:37
*** hogepodge has joined #openstack-meeting-alt13:37
*** mattgriffin has joined #openstack-meeting-alt13:38
*** avozza is now known as zz_avozza13:39
*** oomichi has quit IRC13:40
*** bknudson has joined #openstack-meeting-alt13:40
*** mattgriffin has quit IRC13:41
*** zz_avozza is now known as avozza13:41
*** shadower has joined #openstack-meeting-alt13:44
*** DaSchab has quit IRC13:49
*** _nadya_ has quit IRC13:50
*** DaSchab has joined #openstack-meeting-alt13:50
*** markmcclain has joined #openstack-meeting-alt13:51
*** DaSchab_ has joined #openstack-meeting-alt13:51
*** madhumohan has joined #openstack-meeting-alt13:52
*** sigmavirus24_awa is now known as sigmavirus2413:54
*** avozza is now known as zz_avozza13:55
*** zz_avozza is now known as avozza13:55
*** adrian_otto has joined #openstack-meeting-alt13:55
*** DaSchab has quit IRC13:55
*** jcoufal has quit IRC13:55
*** bertys has joined #openstack-meeting-alt13:55
*** esker has quit IRC13:56
*** Moiz has joined #openstack-meeting-alt13:56
*** esker has joined #openstack-meeting-alt13:56
*** satish has joined #openstack-meeting-alt13:56
*** jcoufal has joined #openstack-meeting-alt13:56
*** jchapman has joined #openstack-meeting-alt13:57
*** The has joined #openstack-meeting-alt13:57
*** The has quit IRC13:58
*** ayyaz has joined #openstack-meeting-alt13:58
*** margaret__ has joined #openstack-meeting-alt13:58
*** thomasem has joined #openstack-meeting-alt13:58
*** dave-mccowan has joined #openstack-meeting-alt13:58
*** thomasem has quit IRC13:58
*** TheDarkKhan has joined #openstack-meeting-alt13:58
*** sgotliv has quit IRC13:59
*** sgotliv_ has joined #openstack-meeting-alt13:59
*** amrith is now known as _amrith_13:59
*** thomasem has joined #openstack-meeting-alt13:59
mkodererhi14:00
*** Zuqiang has joined #openstack-meeting-alt14:00
*** dkusidlo has joined #openstack-meeting-alt14:01
ajohi14:01
ajoNFV meeting?14:01
DaSchab_hi14:01
*** gmatefi has joined #openstack-meeting-alt14:01
*** erik_ has joined #openstack-meeting-alt14:01
*** ian_ott has joined #openstack-meeting-alt14:01
*** DaSchab_ has left #openstack-meeting-alt14:01
*** DaSchab_ has quit IRC14:01
*** DaSchab has joined #openstack-meeting-alt14:01
*** dalgaaf has joined #openstack-meeting-alt14:02
*** colinmcnamara has joined #openstack-meeting-alt14:02
madhumohanhi14:02
*** irenab has joined #openstack-meeting-alt14:02
*** ybabenko has joined #openstack-meeting-alt14:03
*** sgordon_ has joined #openstack-meeting-alt14:03
* sgordon_ sheepishly wanders in14:03
sgordon_#startmeeting telcowg14:03
openstackMeeting started Wed Dec  3 14:03:37 2014 UTC and is due to finish in 60 minutes.  The chair is sgordon_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: telcowg)"14:03
openstackThe meeting name has been set to 'telcowg'14:03
sgordon_#topic roll call14:03
*** openstack changes topic to "roll call (Meeting topic: telcowg)"14:03
*** r-mibu has joined #openstack-meeting-alt14:03
ian_otthi14:03
*** rprakash has joined #openstack-meeting-alt14:03
ybabenkohi14:03
mkodererhi14:03
DaSchabhi14:03
TheDarkKhanHi14:04
pczesnohi14:04
rprakashhi14:04
*** lpabon has left #openstack-meeting-alt14:04
cgoncalveshello14:04
gmatefihi14:04
madhumohanHi14:04
sgordon_hi all, sorry for the delay14:04
rprakashyes telcowg14:04
ajohi :)14:04
sgordon_looks like i forgot to update my calendar14:04
*** erik_ is now known as erikmoe14:04
sgordon_#topic use cases14:05
*** openstack changes topic to "use cases (Meeting topic: telcowg)"14:05
*** satish has quit IRC14:05
sgordon_i endeavored to update the wiki page to provide some guidance on contributing use cases14:05
sgordon_#link https://wiki.openstack.org/wiki/TelcoWorkingGroup/UseCases#Contributing_Use_Cases14:05
*** rushiagr_away is now known as rushiagr14:05
sgordon_and i see jrakerevelant has started a new entry:14:05
sgordon_#link https://wiki.openstack.org/wiki/TelcoWorkingGroup/UseCases#Access_to_physical_network_resources14:05
sgordon_did anyone have a chance to look at these?14:06
rprakashyou mean14:06
rprakashhttps://global.gotomeeting.com/join/84200762114:06
sgordon_probably not as they were created in the last 24 hrs i am guessing14:06
sgordon_rprakash, ?14:07
rprakashsorry delete thst14:07
rprakashv14:07
DaSchablink to nfv draft is broken14:07
rprakashPossible current implementations include:14:07
rprakash    L3 gateways14:07
rprakash        SNAT14:07
rprakash        L3 forwarding14:07
rprakash        Floating IPs14:07
rprakash    External provider networks, e.g. VLAN backed14:07
rprakash    L2 gateways, currently only possible with 3rd party software (?14:07
ian_ottnot yet, thanks for proposing the template14:08
*** ijw has joined #openstack-meeting-alt14:08
sgordon_DaSchab, looks like somebody modified it to point to a docbox14:08
sgordon_i had actually originally uploaded the pdf to the wiki14:08
*** EricGonczer_ has quit IRC14:08
rprakashI wanted to see GTP tunneling added and will be working on revising an old Blue Print14:09
ybabenkoshould we concentrate on "services" or "features" when we speak about usecases14:09
sgordon_ybabenko, so that is what i have tried to help frame14:09
ybabenkocurrently we have a mix : two "services" and one "feature"14:10
sgordon_consensus last week seemed to be that we want to focus on "what" we want to do14:10
sgordon_instead of "how"14:10
*** niclem_ has quit IRC14:10
ybabenkoI think we should target features of openstack which are either missing or are not there ß14:10
*** dboik has joined #openstack-meeting-alt14:10
*** mestery has joined #openstack-meeting-alt14:10
sgordon_that is we should use the use cases to THEN extract requirements14:10
sgordon_ybabenko, the problem is without a documented use case, can you get them added to openstack14:11
sgordon_the answer is increasingly, no14:11
margaret__hi14:11
*** dboik_ has joined #openstack-meeting-alt14:11
sgordon_for those coming in we're discussing https://wiki.openstack.org/wiki/TelcoWorkingGroup/UseCases14:11
rprakashAT the Paris Summit there were dicussions on what to do14:11
jrakerevelanthi14:12
jrakerevelantsry for being late14:12
*** niclem has joined #openstack-meeting-alt14:12
*** moizarif has joined #openstack-meeting-alt14:12
rprakashSince neutron dnsmaq is being replaced the code for any change for telcowg in neutron will be unstable14:12
sgordon_rprakash, yes - and one of the big items was to work harder on documenting use cases that we can then use to define and drive requirements14:13
*** ijw has quit IRC14:13
mkoderersgordon_: btw should we have reviews on that use-cases? I just wondering if gerrit would make more sense..14:14
rprakashOK  I added one for Mobile Carrier - "GTP tunnel support for mobile network for NFV VNFs like SGW, PGW, MME (https://blueprints.launchpad.net/neutron/+spec/provider-network.type-gtp -needs update for resubmission)14:14
sgordon_mkoderer, my thinking is that git/gerrit is a bit too heavy to get contributions from the people we want to hear from14:14
sgordon_particularly operator14:14
*** moizarif has quit IRC14:15
rprakashTHE BP is old one duing quatum time frame and anyone who wants to help me update is welcome14:15
*** dboik has quit IRC14:15
sgordon_mkoderer, ideally the use case ends up in the problem statement of blueprint(s) and is reviewed via gerrit then14:15
mkoderersgordon_: I just have the feeling that we end-up with many use-cases in totally different state and nobody reads them ;)14:16
rprakashHow many use cases we are planning to have for operators this K12?14:16
jrakerevelantsgordon_:  since i was late, did i miss any comments on my use case?14:16
mkoderersgordon_: but ure right... gerrit would be too heavy14:16
sgordon_mkoderer, rprakash i think i'll worry about upper limits when we actually have too many coming in14:17
sgordon_:)14:17
mkodererk14:17
*** _nadya_ has joined #openstack-meeting-alt14:17
sgordon_mkoderer, rprakash i would like to have 6 as a start to have a good baseline14:17
sgordon_and agree the quality is variable14:17
rprakashI did not see any discussions on any use case lets begin with number 114:17
sgordon_primarily atm there is very little editing of the wiki page aside from one or two individuals14:17
sgordon_the first two use cases were contributed loose cycle and agree, they dont necessarily meet the framing we discussed last week14:18
rprakashIs Virtual IMS the first one?14:18
sgordon_#link https://wiki.openstack.org/wiki/TelcoWorkingGroup/UseCases#Session_Border_Controller14:18
sgordon_no the SBC14:18
sgordon_i actually like the high level desc and characteristics put forward here14:19
sgordon_as calum did try somewhat to keep characteristics and requirements as separate things14:19
sgordon_any other thoughts?14:19
ybabenkoWhy use-cases is referring to a particular vendor?14:19
ybabenkoPerimeta Session Border Controller, Metaswitch Networks.14:19
*** satish has joined #openstack-meeting-alt14:20
rprakashThe SBC use case is folowed bt bunch of requirements that are mostly completed in Juno14:20
jrakerevelantso an application as a "use case" is desirable?14:20
ybabenkojrakerevelant: see discussion above14:20
jrakerevelantor shouldnt it be application : one or more use cases?14:20
margaret__An application as a use case helps focus all the features/gaps that need to be filled14:20
sgordon_ybabenko, because they submitted it14:20
sgordon_ybabenko, other vendors are welcome to do same14:20
jrakerevelantybabenko: oh sorry14:21
margaret__Else we get into a theoretical debate. I like the use case since it focuses on performance14:21
sgordon_ybabenko, theoretically different implementations of same function may have different requirements14:21
ybabenkosgordon_: that is fine as long as we stay vendor neutrol in wiki14:21
mkodererI guess the best way would be if Telcos would summit the use-cases :)14:21
dalgaafI would prefer to make it generic and independent of vendors14:21
sgordon_mkoderer, ++++++114:21
*** dboik_ has quit IRC14:21
sgordon_dalgaaf, great - generic use case is welcomed too14:22
rprakashThe seesion border use cas case will be a simple VoiP call from  end point 1 to end point 214:22
margaret__But the VNF vendors are will the rubber meets the road for the telcos14:22
jrakerevelantmkoderer: hey we did submit one :)14:22
dalgaafwould we even be able to check this use case against this vendors app from the openstack side?14:22
mkodererjrakerevelant: yeahh :)14:22
margaret__The SBC is focused on performance and the types of things which need to be configured to meet that which impacts openstack14:22
sgordon_dalgaaf, the key question for me is - are you willing to propose a generic version of the use case14:22
sgordon_if the answer is no14:22
jrakerevelantmkoderer: I still need to refine it though14:22
sgordon_then i am inclined to keep what we have14:23
sgordon_the more people helping with collating of relevant use cases, ideally from providers14:23
sgordon_the less this becomes an issue14:23
rprakashSure the VoiP call has o meet those criterion listed on site and we can quatify them like 150 ms end to end delay etc.14:23
jrakerevelantsgordon_: +114:23
margaret__If you look in details (which i only started doing now) - the SBC features drive features needed for high performance VNFs14:23
sgordon_right14:24
margaret__So unless you find a specific example that metaswitch suggested which is only useful for their app - i say we accept their proposal14:24
sgordon_calum intentionally took his high level characteristics14:24
jrakerevelantrprakash: QoS will be one of the hardest things to implement anyway, why not start with low hanging fruit?14:24
sgordon_and then spelled out what that means14:24
margaret__We need another use case that is focused more on instantiation of VNFs.14:25
ybabenkojrakerevelant: QoS and troughput performane with small packets14:25
*** satish_ has joined #openstack-meeting-alt14:25
rprakashTHE QoS of  one call in terms of RTT, delay, jitter,BW  of 1 session and then comes the capacity of VNF for VoIP to handles that capacity as a VM14:25
rprakashsay 1 million sessions per VNF14:26
sgordon_#info margaret__ notes we need a use case focussed more on instantiation of VNFs14:26
sgordon_#info rprakash notes requirements of a VoIP call, impacts on QoS in terms of RTT, delay, jitter, VW of 1 session and then comes the capacity of VNF for VoIP to handles that capacity as a VM14:27
jrakerevelantrprakash: that can only be proven/ disproven with a specific implementation of the function14:27
margaret__I didn't mean it to be a replacement of SBC proposal - just another angle which flushes out openstack issues14:27
rprakashSome can pickup Asterisk opensource or if Metswicth provides one and model the requirements14:27
sgordon_margaret__, understood14:27
*** kopparam has quit IRC14:27
sgordon_i guess what i would like to be able to get to is for a few volunteers with use cases in mind14:27
sgordon_to take the action item to try and write them up in the next week or so14:28
sgordon_it does not have to be exhaustive but rather something to get the conversation moving forward14:28
*** nosnos has quit IRC14:28
*** satish has quit IRC14:28
*** Longgeek has quit IRC14:29
margaret__I have been working with another vendor in the OPNFV group on a vPE instantiation - let me see if we can pull this together for this - but I can't attend the next IRCs for the rest of the year14:29
sgordon_yes understand14:29
rprakashOpenstack can provision any VNF  using heat template and provide Resources South Bound and API to call Nort Bound and treating VoIP media, all we need to know is how will data call be evaluated in terms of performance matrix we agree for VoIP call and how much the VoIP VNF can handle14:29
*** Zuqiang has quit IRC14:30
sgordon_i think if you just shoot us an email margaret__ we can try discuss14:30
sgordon_i am sure attendance will wane as we get closer to the break for many people14:30
rprakashOK then can we move to case 2 , assign few voluteers o this and move to second14:30
mkoderersgordon_: we will add use-cases for "securtiy segregation (dmz/mz concept)", VNF instantiation and seperation of Infra/App Orchestration14:31
*** _nadya_ has quit IRC14:31
jrakerevelantmkoderer: +114:31
mkodererDaSchab will do that ;)14:32
sgordon_#action margaret__ to work with another vendor in OPNFV group on vPE instantiation use case - will provide via mail (cant attend IRC meetings for remainder of year)14:32
rprakashSecurity segregation , its using Netwurn Security Group for VNF? using port level blocking etc?14:32
jrakerevelantmkoderer: if it is allowed I can add our examplary LLD14:32
sgordon_#action mkoderer and DaSchab to work on security segregation (dmz/mz concept), VNF instantiation and seperation of Infra/App Orchestration14:32
ybabenkojrakerevelant: your use-case is basically a HW-GW for legacy services if i understand correctly?14:33
jrakerevelantybabenko: yes14:33
jrakerevelantjrakerevelant: which is solvable14:33
jrakerevelantah talking to myself14:33
jrakerevelantybabenko: which is solvable14:33
mkodererjrakerevelant: we need to discuss that offline :P14:33
jrakerevelantmkoderer: sure14:33
jrakerevelantybabenko: it doesnt need to be HW14:34
rprakashwhere is the link for security Segreegation?14:34
*** dlenrow has joined #openstack-meeting-alt14:34
mkodererrprakash: no never had a closer look to that14:34
sgordon_#info jrakerevelant use case is effectively HW-GW for legacy services - though not necessarily HW14:34
mkodererrprakash: we will add our use-case soon :)14:34
DaSchab...and we will describe the use-cases in a generic way without vendor specific solutions14:34
*** _nadya_ has joined #openstack-meeting-alt14:35
*** dane_leblanc has joined #openstack-meeting-alt14:35
rprakashNote VNF isolation comes at mutiple levles - Tenant, Security Gruops, and may be Firewall and even some policy from  orchestartion tweaking Security Groups in neutron, so not clear to me here what specific we want to achieve here14:36
*** colinmcnamara has quit IRC14:36
*** juzuluag has joined #openstack-meeting-alt14:37
sgordon_ok14:38
jrakerevelantrprakash: one of the things you might want to have are separate physical servers for different VMs14:38
*** dimtruck is now known as zz_dimtruck14:38
sgordon_thank you to those who volunteered above, it is much appreciated14:38
sgordon_#topic orchestration14:38
*** openstack changes topic to "orchestration (Meeting topic: telcowg)"14:38
rprakashHW-GW  for legacy not clear to me how itf its the use case as even in OPNFV we want COTS based implementaions14:38
sgordon_mkoderer, i believe you had added some links to discuss to the agenda?14:38
sgordon_#chair mkoderer14:38
openstackCurrent chairs: mkoderer sgordon_14:38
sgordon_#link http://lists.openstack.org/pipermail/openstack-dev/2014-November/051473.html14:39
jrakerevelantrprakash: What do you mean, how will I e.g. connect a physical eNodeB to my vEPC14:39
mkodereryep14:39
jrakerevelantsorry for offtopic14:39
mkoderer#topic Telco Orchestration14:39
*** openstack changes topic to "Telco Orchestration (Meeting topic: telcowg)"14:39
sgordon_np14:39
ybabenkorprakash: we need HW-GW to connect to legacy services .... I would expect to terminate my overlay there14:40
mkodererso I had several discusstion about orchestration14:40
jrakerevelantwe can move that to the ML?14:40
jrakerevelantto close the use case discussion14:40
mkodererjrakerevelant: +114:40
sgordon_+114:40
sgordon_also it doesn't have to be perfect from the get go14:40
sgordon_we discuss and we iterate as needed14:41
jrakerevelantplease continue mkoderer :)14:41
*** esker has quit IRC14:41
mkodererok so I try to finalize the document14:41
mkoderer#link https://etherpad.openstack.org/p/telco_orchestration14:41
*** jaypipes-afk is now known as jaypipes14:41
mkoderercurrent state is more or less a brain storming document14:41
rprakashwell eNodeB (Physical) to vEPC (virtual) will have a tenant *(carrier) specific link (pipe) that will be secured using the two end point interfaces terminating on those phy/virt devices14:41
rprakashlets move to Orchestartion (sorry folks)14:42
mkodererso I will work on that the next day and then push it to the wiki14:42
*** jprovazn has quit IRC14:42
mkoderersgordon_: I also included that "internal" and "external" questions14:43
sgordon_right14:43
sgordon_i like the framing of it14:44
rprakashThis is very extensive staring VNF to template to TOSCA not sure I have studied this to comment but certainly if its for NFV, we need to split this at VIM, VNF , OSS?BSS layaers fpor Orchestration as functions to implement14:44
sgordon_i think on that thread angus was looking very specifically for examples of "what do you need from heat that we arent addressing today"14:44
*** kopparam has joined #openstack-meeting-alt14:44
*** dboik has joined #openstack-meeting-alt14:44
sgordon_i think some of it is in here and this is a good manifesto14:44
rprakashI will go over it and can I edit ie?14:45
*** dboik has quit IRC14:45
sgordon_but we may need to break it up into digestable chunks for consideration14:45
*** juzuluag has quit IRC14:45
rprakashor send comment to whoever owns it?14:45
mkodererrprakash: sure feel free.. you can also respond via M/L14:45
*** dboik has joined #openstack-meeting-alt14:45
mkoderer#link http://lists.openstack.org/pipermail/openstack-dev/2014-November/051473.html14:45
ybabenkorprakash: do you have a better suggestion for the format of VNF? how would you like it to be packaged for orhestration?14:45
*** mestery has quit IRC14:46
mkodererand there is already an intressting spec for heat that solves some of the internal OpenStack issues14:47
mkoderer#link https://review.openstack.org/#/c/53313/14:47
mkodererso it's multi region support for heat14:47
sgordon_yes14:48
mkodererI already talked to the heat ppl.. they would we quite open to help us with our requirments14:48
sgordon_seems to be making good progress too14:48
sgordon_yes14:48
sgordon_i think they need help navigating the acronym soup and getting to the heart of what you need14:49
ybabenkomkoderer: i think we should really make this topic (multi site support) a killer req for NFV so that enough attention is given to it in the community?14:49
mkoderersgordon_: should I put that document as seperate wiki page under telcowg?14:49
sgordon_hopefully that is where we can work together :)14:49
rprakashYes multi-region in heat as a resource is scheduled for Kilo and this will allow disctributed orchestaion of VNFs, but more of such we will have to compile to get orchestartions as its very wide14:49
sgordon_mkoderer, the etherpad?14:49
jrakerevelantmulti-region heat will be great14:49
ybabenkomkoderer: +1 for separate wiki page14:49
*** prmtl has quit IRC14:49
mkoderersgordon_: at the end when it's "mature" enough14:49
sgordon_yes i think so14:49
*** Longgeek has joined #openstack-meeting-alt14:49
margaret__multi-site is a definite for NFV crowd14:49
sgordon_etherpad is good for continuing to massage the content14:49
sgordon_#info heat multi-region support progressing well14:50
rprakashWe can possibly compile different BPs for Orchetsration together on our telcowg site14:50
*** pwac has joined #openstack-meeting-alt14:50
sgordon_#link https://wiki.openstack.org/wiki/Heat/Blueprints/Multi_Region_Support_for_Heat14:50
sgordon_#link https://blueprints.launchpad.net/heat/+spec/multi-region-support14:51
mkodererok fine.. that's all from my side14:51
mkodererany other topics?14:51
*** Swami has joined #openstack-meeting-alt14:52
sgordon_#topic other business14:52
*** openstack changes topic to "other business (Meeting topic: telcowg)"14:52
sgordon_i had a question that's actually about a requirement14:52
mkoderersgordon_: I received a mail about an "Telco WG Ecosystem" meeting14:52
sgordon_vlan trunking into vms, there are a couple of proposals related to this to at least allow it when using LinuxBridge14:53
sgordon_im trying to gauge interest/demand in doing something about same for OVS...14:53
rprakashI wanted to add Mobile Network use case for GTP tunneling and will bring it next week14:53
sgordon_mkoderer, yes carol is setting that up at the moment14:53
jrakerevelantsgordon_:  How many people are requesting this?14:53
sgordon_#action rprakash add ingMobile Network use case for GTP tunneling and will bring it next week14:53
sgordon_#undo14:53
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x3c43ad0>14:53
sgordon_#action rprakash adding Mobile Network use case for GTP tunneling and will bring it next week14:53
sgordon_rprakash, thanks !14:54
sgordon_jrakerevelant, that's the million dollar question :)14:54
*** Swami has quit IRC14:54
ybabenkojrakerevelant: +114:54
sgordon_i believe it's coming up from vEPC use cases, or more specifically implementations thereof14:54
*** _amrith_ is now known as amrith14:54
gmatefisgordon_ : vlan trunking mainly interesting for packet processing related applications, where linux bridge is not considered to be powerful enough14:55
sgordon_right14:55
sgordon_the reason that the work is starting with LB is that doing it for OVS is going to be more...involved14:55
*** EricGonczer_ has joined #openstack-meeting-alt14:56
rprakashMost 3GPP use GTP U & GTP  C (v2) and so may split this into two and will think over how to do that in Control and Data planes14:56
ybabenkobut this means that you must use OVS, right?14:56
ybabenkobut OVS is used only in part of SDN solutions which we would probably see in NFV environment14:56
rprakashYes it will require OVS in Data Plane (GTP-U) and possibly GTP-C in MME path14:56
*** betsy has quit IRC14:57
*** mattgriffin has joined #openstack-meeting-alt14:57
*** betsy has joined #openstack-meeting-alt14:57
*** Swami has joined #openstack-meeting-alt14:57
*** alex_xu has quit IRC14:58
rprakashis it time we leave the floor to neutron-DVR14:59
Swamirprakash: thanks14:59
rprakashAny conclusions for telocwg?14:59
jrakerevelantthanks sgordon_ for hosting15:00
sgordon_yes it is15:00
sgordon_lots of volunteers for use cases15:00
sgordon_which is excellent15:00
*** jdandrea has joined #openstack-meeting-alt15:00
mkodererthx all15:00
sgordon_thank you all for that!15:00
sgordon_#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
*** david-ly_ is now known as david-lyle15:00
openstackMeeting ended Wed Dec  3 15:00:23 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/telcowg/2014/telcowg.2014-12-03-14.03.html15:00
jrakerevelantbye15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/telcowg/2014/telcowg.2014-12-03-14.03.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/telcowg/2014/telcowg.2014-12-03-14.03.log.html15:00
*** r-mibu has quit IRC15:00
*** betsy has quit IRC15:00
*** erikmoe has quit IRC15:01
*** bertys has quit IRC15:01
*** DaSchab has quit IRC15:01
*** Moiz has quit IRC15:01
*** TheDarkKhan has quit IRC15:01
Swamihi dvr folks15:01
*** ayyaz has quit IRC15:01
Swami#startmeeting distributed_virtual_router15:01
openstackMeeting started Wed Dec  3 15:01:44 2014 UTC and is due to finish in 60 minutes.  The chair is Swami. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: distributed_virtual_router)"15:01
openstackThe meeting name has been set to 'distributed_virtual_router'15:01
*** cloudon has joined #openstack-meeting-alt15:02
Swamiping rajeev15:02
*** armax has joined #openstack-meeting-alt15:02
Swamiarmax: hi15:03
*** tdruiva is now known as tdruiva|away15:03
*** tdruiva|away has quit IRC15:03
Swami#topic agenda15:03
*** openstack changes topic to "agenda (Meeting topic: distributed_virtual_router)"15:03
SwamiDVR update15:03
SwamiBug scrum15:03
SwamiDocumentation15:03
*** cloudon has left #openstack-meeting-alt15:03
SwamiFunctional testing15:04
SwamiOpen Discussions15:04
rprakashAnhy links?15:04
*** dims has quit IRC15:04
Swamirprakash: Are you looking for the links to the agenda.15:04
rprakashyes15:04
*** dims has joined #openstack-meeting-alt15:04
SwamiNo I don't have the link to the agenda, this will be updated to the meeting log and we can keep track of it.15:05
*** jchapman has quit IRC15:05
*** uschreiber has joined #openstack-meeting-alt15:05
Swami#link https://wiki.openstack.org/wiki/Meetings/Distributed-Virtual-Router15:06
Swamirprakash: you can refer to the meeting minutes from the above link15:06
Swami#topic DVR Update15:06
*** openstack changes topic to "DVR Update (Meeting topic: distributed_virtual_router)"15:06
rprakashThanks so we are following on last meets continuing on Functional testing15:07
SwamiLast week we went through the technical debts for DVR15:07
*** madhumohan has quit IRC15:07
SwamiSome of the backlog items for the technical debts had been addressed.15:08
Swami#topic DVR migration from legacy to distributed15:08
*** openstack changes topic to "DVR migration from legacy to distributed (Meeting topic: distributed_virtual_router)"15:08
rprakashDid we have DVR eith vR's for a Tenant in different Hosts/Hypervisors and same and different uses cases for it?15:08
MuraliHi swami15:08
*** AJK__ has quit IRC15:09
SwamiMurali: welcome back15:09
*** AJK__ has joined #openstack-meeting-alt15:09
rprakashlegacy you mean physical routers to DVR?15:09
Swamirprakash: can you reframe your question.15:09
MuraliThanks Swami I have small bug fix for DVR which is hanging from long time https://review.openstack.org/#/c/102512/15:10
*** yamamoto has joined #openstack-meeting-alt15:10
*** mestery has joined #openstack-meeting-alt15:10
Swamirprakash: This patch was to convert the existing centralized legacy virtual routers to distributed virtual routers.15:10
*** woodster_ has quit IRC15:10
MuraliI need some help  to fix other CI failures. I fixed all the unit testcases15:11
Swami#link https://bugs.launchpad.net/neutron/+bug/134830915:11
uvirtbotLaunchpad bug 1348309 in neutron "Migration of legacy router to distributed router not working" [High,Fix committed]15:11
rprakashOK  I am just catching up and so assume I am just an observer for now,15:11
Swami#link https://review.openstack.org/10585515:12
Swamithe above patch was merged recently that would allow a legacy router to be converted to a distributed virtual router.15:12
*** esker has joined #openstack-meeting-alt15:12
SwamiMurali: Can you point me to the bug that you are working on.15:13
Murali https://review.openstack.org/#/c/102512/15:13
MuraliSwami the bug ##130783815:14
SwamiMurali: I thought that is something similar to what I was working on earlier.15:14
Muralihttps://bugs.launchpad.net/neutron/+bug/130783815:14
uvirtbotLaunchpad bug 1307838 in neutron "Scheduling the router on the Node Even though if there are no interface ports on that router. This happen when l3-agent calls sync routers" [Undecided,In progress]15:14
Muraliyes that is the bug15:15
SwamiMurali: Can you tag this bug to "dvr-backlog"15:15
*** EricGonczer_ has quit IRC15:15
SwamiMurali: sorry tag it to "l3-dvr-backlog"15:16
rprakashYou mean bug due to presence of /etc/mysql in brocade-ci15:16
SwamiI don't see it from our backlog list.15:16
*** jecarey has joined #openstack-meeting-alt15:16
Muraliok Swami I will tag it15:16
*** marun has joined #openstack-meeting-alt15:17
MuraliI posted the fix I need some help to fic CI failures15:17
SwamiMurali: I will take a look at it today and review it.15:17
MuraliThanks Swami15:17
Swamithere are couple of other patches that are related to the migration or manual move.15:18
Swami#link https://review.openstack.org/#/c/123815/15:18
Swamimrsmith: is working on this patch right now and the review is in progress.15:18
*** zz_dimtruck is now known as dimtruck15:19
SwamiAnother related patch for manul move of snat is up for review.15:19
Swami#link https://review.openstack.org/#/c/122024/15:19
SwamiThe patch below validates if there are any services associated with a router before a move.15:20
Swami#link https://review.openstack.org/#/c/123273/15:20
*** EricGonczer_ has joined #openstack-meeting-alt15:20
*** Riddhi has quit IRC15:21
SwamiAlso for manual move or binding a router to a particular agent we do have a patch for review.15:21
Swami#link https://review.openstack.org/#/c/118491/15:21
SwamiThe last four patches that I have posted above is up for review, and please feel free to review it.15:21
*** jprovazn has joined #openstack-meeting-alt15:22
SwamiThat's all for the DVR migration from legacy to distributed.15:22
Swami#topic DVR VLAN support15:22
*** openstack changes topic to "DVR VLAN support (Meeting topic: distributed_virtual_router)"15:22
SwamiIs vivek online15:22
Swamivivek is currently working on the DVR VLAN support.15:23
rprakashany links Swami?15:23
Swami#link https://review.openstack.org/#/c/131800/15:24
rprakashthanks15:24
SwamiThe above is the link to the specs.15:24
Swamivivek also has a patch for the vlan support15:24
*** mtanino has joined #openstack-meeting-alt15:24
Swami#link https://review.openstack.org/#/c/129884/15:24
SwamiThis patch is still a wip.15:25
*** shwetaap has quit IRC15:25
SwamiThat's the update on the DVR vlan support.15:25
Swami#topic VPNaaS for DVR15:25
*** openstack changes topic to "VPNaaS for DVR (Meeting topic: distributed_virtual_router)"15:25
*** teran has quit IRC15:26
SwamiThe VPNaaS support for DVR work is done and it is currenlty on review.15:26
SwamiI have tested and seems to work.15:27
Swami#link https://review.openstack.org/#/c/127133/515:27
SwamiThis patch is up for review and folks please provide your review comments.15:27
rprakashHave added to review for Vivek's DVR VLAN15:27
*** shwetaap has joined #openstack-meeting-alt15:27
Swamirprakash: Thanks15:28
Swami#topic DVR and L3 HA15:29
*** openstack changes topic to "DVR and L3 HA (Meeting topic: distributed_virtual_router)"15:29
*** shakamunyi has joined #openstack-meeting-alt15:29
*** shakamunyi has quit IRC15:29
*** dboik_ has joined #openstack-meeting-alt15:29
SwamiThis topic is under investigation. Both the DVR team and the L3 HA team are working together to come up with a single solution that would support both the DVR and the L3 HA.15:29
rprakashAny links for this?15:30
SwamiRight now we have some issues related to control plane that is interfering with the data plane.15:30
*** nelsnelson has joined #openstack-meeting-alt15:30
rprakashin Neutron CP/DP?15:30
*** thangp has joined #openstack-meeting-alt15:30
SwamiDVR has some dependency on l2pop.15:31
Swamirprakash: That is no patch yet for the DVR and L3 HA.15:31
Swami#link https://wiki.openstack.org/wiki/Neutron/DVR/ServiceNode-HA15:31
rprakashso its message broadcast from CP to take care of DP .. OK i see15:32
SwamiThis is the link to the wiki patch were both the teams share there investigation items.15:32
*** gmatefi has quit IRC15:32
*** dboik has quit IRC15:33
Swami#topic DVR and IPv615:33
*** openstack changes topic to "DVR and IPv6 (Meeting topic: distributed_virtual_router)"15:33
SwamiPatch for review;15:33
Swami#link https://review.openstack.org/13694715:33
Swami#link https://review.openstack.org/13865415:34
*** kopparam has quit IRC15:34
Swami#topic Functional Testing15:35
*** openstack changes topic to "Functional Testing (Meeting topic: distributed_virtual_router)"15:35
haleybAnd https://review.openstack.org/#/c/134676/ for DVR/IPv615:35
*** dboik_ has quit IRC15:35
*** hareeshp has quit IRC15:35
*** dkusidlo has quit IRC15:36
*** dboik has joined #openstack-meeting-alt15:36
rprakashLast time had heard we are splitting L3 agent code seperating IPV6 and DVR is that part of this same?15:36
*** f13o has quit IRC15:36
SwamiLast week I mentioned that we had a joint meeting with Marun, amuller, myself, adolfo, rajeev, carl_baldwin and mrsmith for the functional test.15:36
*** uschreiber has quit IRC15:37
Swamirprakash: L3 agent code refactoring is a work in progress.15:37
SwamiThe above mentioned patches address a bug in DVR that does not allow both DVR and IPv6 to co-exist.15:37
rprakashI see thanks for the note swami15:38
SwamiSo we do have a couple of patches that we are currently work on for the functional test and have been posted.15:39
*** kopparam has joined #openstack-meeting-alt15:39
SwamiI don't have the link handy right now, but I will update it in the next meeting.15:39
Swami#topic Bug Scrum15:39
*** openstack changes topic to "Bug Scrum (Meeting topic: distributed_virtual_router)"15:39
*** xuhanp has quit IRC15:39
*** zz_jgrimm is now known as jgrimm15:39
SwamiMost of the above mentioned patches address the existing bugs.15:40
SwamiThere are couple of new bugs that popped up.15:40
Swami#link https://bugs.launchpad.net/neutron/+bug/139886515:40
uvirtbotLaunchpad bug 1398865 in neutron "DVR code can add duplicate routing rules" [Undecided,New]15:40
Swamihaleyb: is currently owning this bug.15:41
haleybyes, i had mentioned that last week but just filed today.  rajeev gave me some code, i am working on an update15:41
Swamihaleyb: thanks for creating a luanchpad entry for this bug as you mentioned last week.15:41
*** balajiiyer has joined #openstack-meeting-alt15:41
*** rpjr has quit IRC15:42
SwamiThere is another bug that was filed recently.15:42
Swami#link https://bugs.launchpad.net/neutron/+bug/139844615:42
uvirtbotLaunchpad bug 1398446 in neutron "Novacompute failed to detel VM port with DVR" [Undecided,New]15:42
*** rpjr has joined #openstack-meeting-alt15:42
*** Barker has joined #openstack-meeting-alt15:42
*** amotoki_ has joined #openstack-meeting-alt15:43
Swami#link https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-dvr-backlog15:43
SwamiAll our bugs are tracked in the above link, if i have missed any bugs please feel free to look at the above link.15:43
Swami#topic Documentation15:44
*** openstack changes topic to "Documentation (Meeting topic: distributed_virtual_router)"15:44
SwamiWe have provided the documentation details to the documentation team and they are working on documenting the DVR for the networking guide.15:44
*** baoli has quit IRC15:44
SwamiWe might be having a beta release by the end of January for review to the other folks.15:44
SwamiThis task is in track.15:45
SwamiAnything else for discussion15:45
*** teran has joined #openstack-meeting-alt15:45
*** betsy has joined #openstack-meeting-alt15:45
*** tonytan4ever has joined #openstack-meeting-alt15:46
SwamiI have a hard stop at 7.45a.m today.15:46
SwamiThanks everyone for joining the meeting today.15:46
rprakashAppreciate Swami for the great inputs15:46
SwamiSee you all next week same time.15:46
Swamibye15:46
Swami#endmeeting15:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:47
openstackMeeting ended Wed Dec  3 15:47:04 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-12-03-15.01.html15:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-12-03-15.01.txt15:47
openstackLog:            http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-12-03-15.01.log.html15:47
*** rpjr has quit IRC15:47
*** dboik has quit IRC15:48
*** dboik has joined #openstack-meeting-alt15:48
*** rpjr has joined #openstack-meeting-alt15:49
*** Sukhdev has joined #openstack-meeting-alt15:50
*** matrohon has quit IRC15:50
*** Swami has quit IRC15:51
*** kopparam has quit IRC15:51
*** EricGonczer_ has quit IRC15:52
*** SushilKM has joined #openstack-meeting-alt15:53
*** tsekiyama has joined #openstack-meeting-alt15:53
*** rprakash has quit IRC15:54
*** tdruiva|away has joined #openstack-meeting-alt15:54
*** Riddhi has joined #openstack-meeting-alt15:54
*** carl_baldwin has joined #openstack-meeting-alt15:57
*** manishg_ has joined #openstack-meeting-alt15:57
*** jmontemayor has joined #openstack-meeting-alt15:57
*** shivharis has joined #openstack-meeting-alt15:57
*** Riddhi has quit IRC15:58
*** dboik has quit IRC15:59
*** BrianB_ has joined #openstack-meeting-alt15:59
*** Riddhi has joined #openstack-meeting-alt15:59
*** banix has joined #openstack-meeting-alt15:59
*** balajiiyer has left #openstack-meeting-alt16:00
*** rkukura has joined #openstack-meeting-alt16:00
banixhi16:00
rkukurahi ML2’ers!16:00
*** sgordon_ has quit IRC16:00
yamamotohi16:01
*** sean-k-mooney has joined #openstack-meeting-alt16:01
*** jmontemayor_ has joined #openstack-meeting-alt16:01
rkukurabanix: welcome back!16:01
banixrkukura: thanks16:01
shivharishi all16:01
sean-k-mooneyo/16:01
*** jmontemayor has quit IRC16:01
rkukuraI’ll wait a minute or two for people to show up16:02
*** dboik has joined #openstack-meeting-alt16:02
SukhdevHello everybody16:02
manishg_hi16:02
*** pballand has joined #openstack-meeting-alt16:02
*** yalie has joined #openstack-meeting-alt16:02
*** sadasu has joined #openstack-meeting-alt16:03
*** rcurran has joined #openstack-meeting-alt16:03
*** BrianB_ has quit IRC16:03
rkukura#startmeeting networking_ml216:03
openstackMeeting started Wed Dec  3 16:03:57 2014 UTC and is due to finish in 60 minutes.  The chair is rkukura. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:04
*** openstack changes topic to " (Meeting topic: networking_ml2)"16:04
openstackThe meeting name has been set to 'networking_ml2'16:04
rkukura#topic: Agenda16:04
*** openstack changes topic to ": Agenda (Meeting topic: networking_ml2)"16:04
rkukura#link: https://wiki.openstack.org/wiki/Meetings/ML2#Agenda16:04
*** yalie has quit IRC16:04
*** asomya has joined #openstack-meeting-alt16:04
*** yalie has joined #openstack-meeting-alt16:05
rkukura#topic: Announcements16:05
*** openstack changes topic to ": Announcements (Meeting topic: networking_ml2)"16:05
rkukuraMid-cycle meetup: https://wiki.openstack.org/wiki/Sprints/NeutronKiloSprint16:05
*** kebray has joined #openstack-meeting-alt16:05
rkukuralooks like ML2 will be well-represented at this16:06
*** safchain has quit IRC16:06
SukhdevI noticed 4 ML2'ers have signed up for the sprint16:06
rkukuraAnyone going that’s not on the wiki?16:06
banixSukhdev: good16:06
*** jmontemayor_ has quit IRC16:06
Sukhdevbanix: how about you?16:06
Sukhdevbanix: missing this time?16:07
shivharismaybe for me16:07
banixSukhdev: cannot make it I am afraid16:07
Sukhdevshivharis: sign up please16:07
rkukuraLooks like all the agenda is relevant to ML216:07
irenabhi, sorry for being late16:07
banixrkukura: yes, good that there are ml2’ers there16:08
shivharisSukhdev: need to figure out a customer visit, will know shortly16:08
rkukuraSince both Sukhdev and will be at this next week, we’ll skip the IRC meeting unless someone else wants to chair it16:08
*** chellygel has joined #openstack-meeting-alt16:08
rkukuraAnd we can discuss the meetup at the following week’s ML2 meeting16:09
*** BrianB_ has joined #openstack-meeting-alt16:09
asomyawhat are some of the work items for ML2 at the mid cycle sprint?16:09
*** chellygel has left #openstack-meeting-alt16:09
*** zehicle has quit IRC16:09
*** safchain has joined #openstack-meeting-alt16:10
rkukuraasomya: I believe the API/RPC layer refactor and Core Plugin refactor will both have big impact on the plugins, especially ML216:10
*** ijw has joined #openstack-meeting-alt16:10
asomyaWill this be a good opportunity to address some of the proposed type driver refactor things we discussed in Paris?16:10
*** pballand has quit IRC16:10
asomyaOr should we do that after this sprint?16:11
*** jmontemayor has joined #openstack-meeting-alt16:11
rkukuraasomya: I’m sure there will be some opportunities to talk about that sort of thing, but I think the focus of this is a “code sprint”16:11
asomyarkukura: sounds good, i was debating whether to go for the sprint or not16:11
rkukuraOne concern i have is that I think the plan is (still?) to move all the existing extensions into the core API, and I’m not sure it will be possible for ML2 extension drivers to still add additional extensions16:12
Sukhdevasomya: i think you should attend, if you can afford to go16:12
asomyasukhdev: I'll try :)16:13
rkukuraIt would be useful to know what ML2 mechanism drivers require vendor-specific core resource extensions16:13
banixrkukura: i think at least on the spec that is posssible16:13
*** jecarey has quit IRC16:13
*** kebray has quit IRC16:13
*** SumitNaiksatam has quit IRC16:14
*** Longgeek has quit IRC16:14
rkukurabanix: OK, good to know16:14
rkukuraanything else on the meetup?16:14
rkukuraSub-teams charter https://wiki.openstack.org/wiki/NeutronSubteamCharters16:15
*** Murali has quit IRC16:15
sadasuport security extension and the rate limit extension that irenab brought up?16:15
banixwe need to add an End Goal section16:15
rkukuraSo I added the text from our etherpad to this, but we need to link the BP specs we are tracking during kilo16:15
sadasurkukura: I was still trying to answer your question on the previous topic!16:16
rkukurabanix: Not sure all teams need end goals?16:16
Sukhdevbanix: please elaborate?16:16
*** Longgeek has joined #openstack-meeting-alt16:16
banixSukhdev: rkukura there is a new section added to the template called End Goal16:16
*** markvoelker has joined #openstack-meeting-alt16:16
rkukurasadasu: Right - I’m a strong believer in exensibility as a facilitator for innovation16:17
*** rwsu has joined #openstack-meeting-alt16:17
shivharisml2 maybe an ongoing topic, so what does endgoal mean here?16:17
banixEnd Goal (When Are you Done?) Long lived sub-teams with no clear charter are bad. You should have a goal, a timeline, and a completion date in mind.16:17
rkukuraI guess we could say we have a clear charter instead16:17
*** pballand has joined #openstack-meeting-alt16:17
rkukuraDo we think we’ll be done at some point?16:18
Sukhdevrkukura :-)16:18
banixrkukura: all good things will come to an end :)16:18
rkukurabanix: OK, will we be done before neutron is done?16:18
banixrkukura: but i understand your point16:18
banixrkukura: exactly16:18
rkukuraI guess we could have a goal of eventually stabilizing the ML2 driver APIs and/or folding ML2 into the neutron core16:19
sadasuif one release goes by with no changes to core ML2 plugin, then can we say  that it has stabilized and "Done" /16:19
irenabsadasu: +116:19
rkukurasadasu: OK, I’ll add something along those lines16:19
sadasurkukura: +116:19
*** jecarey has joined #openstack-meeting-alt16:20
rkukuraKilo release schedule: https://wiki.openstack.org/wiki/Kilo_Release_Schedule16:20
rkukuraSo kilo-1 milestone is in 15 days, kilo-2 in February16:21
rkukuraMore critical, the SPD is this coming Monday!16:22
sadasurkukura: only critical ml2 driver fixes would be merged until the split happens, corrcet/16:22
*** sigmavirus24 has left #openstack-meeting-alt16:22
Sukhdevsadasu: that is my understanding16:22
*** woodster_ has joined #openstack-meeting-alt16:22
rkukurasadasu: I’m not sure about that, but we’ll discuss the split in a bit16:23
banixsadasu: Sukhdev hmmmm how come?16:23
rkukuraI’m should have the updated HPB spec submitted later today16:23
sadasuthat is what the split BP states16:23
Sukhdevbanix: based upon what is written in https://review.openstack.org/#/c/134680/16:23
banixgot it thanks16:24
sean-k-mooneythe split bp has not been merged /approved yet but yes that was its recomendation16:24
banixyes we need to review it16:24
banixi think that was one of the action items (uncalled) for the week16:25
rkukurabanix: agreed, and this is something that will probably become a concrete plan next week at the sprint16:25
Sukhdevbanix: I have been asking for all ML2'er to review it and post your comments16:25
sadasurkukura: yes, waiting to hear what decisions are made next week16:25
banixSukhdev: i know; dont see many though (myself included)16:26
rkukuralets all try to review that spec this week and get comments in16:26
*** esker has quit IRC16:27
sadasurkukura: confusing part is, are mech driver BP specs going to be reviewed by cores?16:27
rkukuraSo, spec proposal deadline is Monday - all specs need to be submitted for review by then16:27
*** shwetaap1 has joined #openstack-meeting-alt16:27
*** aleksandr_null has joined #openstack-meeting-alt16:27
rkukurasadasu: I don’t know16:27
Sukhdevsadasu: correct. I believe that is true for K cycle16:27
*** shwetaap has quit IRC16:28
rkukuraOther than HPB, what other specs are planned for Kilo that haven’t been submitted yet?16:28
Sukhdevsadasu: even I found it bit confusing - but, this requirement will go away in L-cycle16:28
asomyarkukura: I have to submit a spec for the refactor16:29
*** tzn has joined #openstack-meeting-alt16:29
shivharisI have a new mech driver that will be submitted today16:29
Sukhdevasomya: please submit ASAP16:29
rkukuraLets assume for now that vendor drivers need specs in kilo16:29
asomyawill do today16:29
sadasuSukhdev: correct.16:29
irenabrkukura: Ml2 extension for port rate limit spec will be subbmited soon16:29
*** andreaf has quit IRC16:29
rkukuraany others?16:30
*** BrianB_ has quit IRC16:30
Sukhdev12/8 is the deadline for all specs to be in...16:30
sean-k-mooney i submitted a spec for a new mech dirver an hour ago too.16:30
irenabalso just submitted https://blueprints.launchpad.net/neutron/+spec/network-settings-support-vnic-type16:30
rkukuraand 12/15 is the deadline for them to be approved16:30
rcurranvxlan support for cisco nexus (dep on HPB and asomya's type driver)16:30
*** mwagner_lap has quit IRC16:31
sadasuhere is a link to my mech driver spec: https://review.openstack.org/#/c/134056/16:31
rkukura#action everyone Submit kilo specs for review by 12/8, but ASAP since approval deadline is 12/1516:31
sadasuI have a few +1s already16:31
rkukuraDo we want to continue tracking these via the wiki?16:31
sadasuthanks to those who reviewed...you know who you are16:32
shivharisrkukura: +116:32
rkukuraIf so, it needs updating so that the top section is the actual kilo specs16:32
irenabrkukura: yes16:32
Sukhdevrkukura: banix and I used to baby sit that wiki :-)16:32
rkukura#topic bugs16:32
sean-k-mooneyi added the link to mine  https://review.openstack.org/#/c/138742/ to the wiki too but was not sure if it is still used16:32
*** openstack changes topic to "bugs (Meeting topic: networking_ml2)"16:32
rkukura#undo16:33
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x3db0210>16:33
rkukuraDoes anyone want to take an action to cleanup/reorganize the tracking wiki?16:33
manishg_I'll take it16:33
banixi tried to go through them a week or so ago but it may not be up to date16:33
banixmanishg_: thanks16:33
SukhdevIf the team believes it is useful, we can continue to maintain it16:33
shivharisI'll take joint ownership16:34
rkukura#action manishg_ Cleanup and reorganize https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews16:34
banixmainly, the owners of bps, need to keep it up to date16:34
*** BrianB_ has joined #openstack-meeting-alt16:34
rkukura#undo16:34
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x3ac0350>16:34
Sukhdevmanishg_, shivharis: you have to ensure that it is up-to-date16:34
sadasubanix: manishg: will update with mine16:35
shivharisSukhdev: +116:35
rkukura#action manishg_ and shivharis: Cleanup and reorganize https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews16:35
manishg_Sukhdev: +116:35
banixsounds good16:35
rkukuraOK, I think we covered the spec reviews topic, lets go back to bugs16:35
rkukura#topic bugs16:35
manishg_sadasu: thanks.16:35
*** openstack changes topic to "bugs (Meeting topic: networking_ml2)"16:35
rkukurashivharis: any update on this?16:35
shivharisHi16:35
shivharisThis is going to be fun. Since we are only going to get critical bugs in16:36
*** baoli has joined #openstack-meeting-alt16:36
shivharisand since we have no "critical" bugs we are done --- (just kidding)16:36
rkukurashivharis: Why only critical bugs?16:36
shivharisOnly critical bugs will be entertained for merge .(that is what i hear)16:37
*** EricGonczer_ has joined #openstack-meeting-alt16:37
shivharisHowever...16:37
rkukurashivharis: Is that for vendor drivers/plugins, or everything?16:37
shivharisWe hav 56 bugs, and many in medium and low.16:37
shivharisEarly in a cycle it is good to help onboard new team members16:38
*** daneyon has joined #openstack-meeting-alt16:38
*** ijw has quit IRC16:38
shivharisI would like folks to look at the bugs and please pick up these bugs (that get sidetracked) at the end of the tail end of the release16:39
shivharisrkukura: everything16:39
shivharisAlso it would be nice to have a list of primary maintainers of vendor plugins16:39
*** Sukhdev has quit IRC16:39
*** markmcclain1 has joined #openstack-meeting-alt16:40
shivharisSo please help out in picking up these bugs, some maybe low hanging fruit16:40
banixregarding #link https://review.openstack.org/#/c/113999/ looking at logs from a few weeks ago (when i was absent) it was mentioned i think by rkukura that we may not need the bug fix for bulks if the tasks stuff get done… the patch is almost there, almost got merged ;) at Juno RC1 and now need a rebase and addressing yamamoto ’s comments. should i get that done or simply abondon?16:40
sean-k-mooneyif im not mistakend dont all vendor plugins require a point of contact?16:40
banixsean-k-mooney: their CI systemdoes16:41
shivharissean-k-mooney: yes, but this is not done completely16:41
*** EricGonczer_ has quit IRC16:41
irenabwhat about not vendor specific, like OVS, LB, SRIOV?16:41
shivharisWe have vendor bugs sitting in q for a very long time16:41
sean-k-mooneybanix: thanks16:41
shivharisSo, please help out here.16:41
rkukurabanix: Lets see what happens at the meetup next week regarding the plugin APIs, and then decide whether to go with the proposed fix or not16:41
shivharisI am looking for new volunteers16:42
banixrkukura: ok16:42
*** markmcclain has quit IRC16:42
*** colinmcnamara has joined #openstack-meeting-alt16:42
rkukuraI’ve been out of the loop lately, but cannot believe bug fixes are not being merged16:42
manishg_shivharis: should the vendors not be fixing their own bugs?16:42
manishg_if the vendors don't care I wonder if should give them lower priority as compared to other bugs.16:43
*** ihrachyshka has quit IRC16:43
shivharisvendors usually fix their own bugs - but since it becomes community code anyone can jump in16:43
manishg_yeah they can jump in but in ML2 community should we first take care of other more important stuff?16:43
*** daneyon_ has joined #openstack-meeting-alt16:44
shivharisi am not seeing volunteers, so i will have to start assigning16:44
*** daneyon has quit IRC16:44
shivharismoving on16:44
*** jmontemayor has quit IRC16:44
shivharishttps://review.openstack.org/#/c/113999/16:44
manishg_I'll pick some of them but let's not assign vendor bugs unless someone really wants to.16:44
*** markmcclain1 has quit IRC16:44
shivharisbanix: ?16:44
banixshivharis: thanks i already jumed the gun as usual16:44
banixwondering whether to work on it or not; rob suggesting wait until next week which sounds reasonable16:45
shivharisok16:45
rkukurabanix: My view is that we’ll likely go with this fix, but lets see what impact the plugin API changes has16:45
banixrkukura: sure; meanwhile i rebase and address yamamato’s concern16:46
shivharismanishg_: I will try to assign the vendors specific bugs to relevant folks they may re-assign16:46
shivharisthat is all I have for bugs16:46
rkukurabanix: make sense to me16:46
*** daneyon_ has quit IRC16:46
rkukurashivharis: thanks16:46
manishg_shivharis: thanks16:46
rkukura#topic driver repo discussion16:46
*** openstack changes topic to "driver repo discussion (Meeting topic: networking_ml2)"16:46
rkukurawe already discussed this a bit16:46
*** daneyon has joined #openstack-meeting-alt16:46
*** esker has joined #openstack-meeting-alt16:47
rkukuraI don’t yet fully grasp the current proposal - still need to read it in detail16:47
*** EricGonczer_ has joined #openstack-meeting-alt16:47
rkukuraBut I get the impression the drivers themselves stay in the neutron repo. Is that correct?16:47
*** tzn has quit IRC16:48
*** arnaud__ has joined #openstack-meeting-alt16:48
banixrkukura: no just a thin part of them16:48
sean-k-mooneythe ovs mech drive will at least but i belive the rest are moved out16:48
rkukuraThat thin part is what I meant by “the drivers themselves"16:48
banixrkukura: that will interface with the out of tree piece16:48
*** jeegn-chen has joined #openstack-meeting-alt16:48
banixrkukura: yes then :)16:48
manishg_rkukura: no drivers move out.  except ovs (as sean-k-mooney said) - initially.  later that moves out too.16:48
*** esker has quit IRC16:49
manishg_s/no drivers/no, drivers/  :)16:49
rkukuraso there is not thin peice remaining in tree, not even the driver entry point?16:49
*** alexbh2 has quit IRC16:49
*** jeegn-chen has quit IRC16:49
*** n0ano has joined #openstack-meeting-alt16:49
sadasurkukura: db, config and requirements.txt stays in tree for each driver16:49
rkukuras/not/no/16:49
rkukuradoes this make sense to anyone?16:50
sadasurkukura: all other code lives outside the tree16:50
*** timsim has joined #openstack-meeting-alt16:50
sadasurkukura: all other code -> all other mech driver code16:50
*** jmontemayor has joined #openstack-meeting-alt16:50
shivharishow will tempest/unit tests run?16:51
banixwhen i refered to a thin part staying in tree that was for mono plugins16:51
irenabalso agent entry point is kept in the tree16:51
sadasurequirements.txt points to the outside repo where driver code lives and also specifies other packages that the driver needs to import etc16:51
sadasuirenab: correct16:52
*** EricGonc_ has joined #openstack-meeting-alt16:52
rkukuraI’m concerned its going to become extremely difficult to evolve the driver APIs with this plan16:52
rkukuraWe are running short on time. Lets all review the spec and get our comments in.16:53
shivharisI believe we will need some example drivers to remain in16:53
irenabI guess as ML2 subteam we may propose some way to support ML2 pieces (Mech. and Extension Drivers)16:53
sean-k-mooneyi belive the intention is to keep the ovs driver for the gate and as an example16:54
amotoki_how can we version the driver API? I think we need to consider some versioning for internal APIs.16:54
*** achanda has joined #openstack-meeting-alt16:54
amotoki_it is not achieved in the plugin API yet.... :-(16:54
rkukuraamotoki_: Are you suggesting that we make ML2 support multiple driver API versions simultaneously? That would add significant complexity!16:54
*** johnbelamaric has joined #openstack-meeting-alt16:55
amotoki_rkukura: at least,  if we support two versions, out-of-tree drivers can migrate to new API .16:55
amotoki_but i understand it is not an easy thing of courses.16:56
*** EricGonczer_ has quit IRC16:56
*** vinod1 has joined #openstack-meeting-alt16:56
sean-k-mooneyamotoki: would we then evolve the api in lockstep over each cycle depreacting the older api16:56
*** shwetaap1 has quit IRC16:56
rkukuraamotoki_: I’m not sure this whole approach is worth it. I’d much rather see the drivers stay in tree, but be made as thin as possible wrappers around external libraries that deal with the backends.16:57
*** Sukhdev has joined #openstack-meeting-alt16:57
*** shwetaap has joined #openstack-meeting-alt16:57
rkukuraonly 4 minutes left16:57
Sukhdevsorry - I lost power at my home16:57
SukhdevI am back now16:57
sadasurkukura: +116:57
*** mugsie has joined #openstack-meeting-alt16:57
banixbefore running out of time, note the l2 agent work may have some implications as well; review the proposal pls https://review.openstack.org/#/c/137808/16:57
amotoki_rkukura: it is just an idea, but I don't have a good concrete plan right now.16:57
rkukura#topic Modular L2 agent16:57
*** openstack changes topic to "Modular L2 agent (Meeting topic: networking_ml2)"16:57
*** paul_glass has joined #openstack-meeting-alt16:58
sadasuI was hoping that the split would slice it that way, but it isn't16:58
*** rjrjr_ has joined #openstack-meeting-alt16:58
banix#link https://review.openstack.org/#/c/137808/16:58
rkukuraamotoki_: makes sense in theory16:58
banixl2 improvement spec ^^^16:58
manishg_rosella already put a spec out.16:58
manishg_banix: thanks.16:58
rkukuraSo is this something the ML2 team should track through kilo?16:59
*** ksushil_ has joined #openstack-meeting-alt16:59
banixnot sure17:00
rkukuraAnd is any “modularity” being proposed, or is that something we’d pursue seperately?17:00
manishg_Looks like currently it's going on independently.  I may be helping with it.17:00
*** ksushil_ has quit IRC17:00
*** esker has joined #openstack-meeting-alt17:00
*** ksushil_ has joined #openstack-meeting-alt17:00
banixrkukura: no modularity; was asked to postpone17:00
rkukuraok17:01
rkukurawe are out of time17:01
rkukurathanks everyone!17:01
*** rmoe has quit IRC17:01
manishg_thanks.17:01
banixbye17:01
rkukura#endmeeting17:01
yamamotobye17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
openstackMeeting ended Wed Dec  3 17:01:10 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
SukhdevThanks rkukura17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-12-03-16.03.html17:01
sean-k-mooneybye17:01
Sukhdevbye17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-12-03-16.03.txt17:01
irenabthanks17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-12-03-16.03.log.html17:01
*** manishg_ has left #openstack-meeting-alt17:01
rkukurabye17:01
*** shivharis has quit IRC17:01
*** paul_glass has left #openstack-meeting-alt17:01
irenabbye17:01
sadasuthanks!17:01
amotoki_good night17:01
*** rkukura has left #openstack-meeting-alt17:01
Kiall#startmeeting Designate17:01
openstackMeeting started Wed Dec  3 17:01:38 2014 UTC and is due to finish in 60 minutes.  The chair is Kiall. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** sadasu has quit IRC17:01
*** openstack changes topic to " (Meeting topic: Designate)"17:01
openstackThe meeting name has been set to 'designate'17:01
*** asomya has quit IRC17:01
KiallHeya - Who's about?17:01
rjrjr_o/17:01
*** vishwanathj has joined #openstack-meeting-alt17:01
timsimo/17:01
mugsieo/17:02
*** sean-k-mooney has quit IRC17:02
Kiallvinod1 / betsy about today?17:02
KiallGuess not :)17:02
*** achanda has quit IRC17:02
*** SushilKM has quit IRC17:02
timsimThey'll be along shortly I bet17:03
KiallQuick off-agenda item - Kilo-1 status page .. Anything we're missing from it, please add https://launchpad.net/designate/+milestone/kilo-117:03
betsyyes17:03
betsyo/17:03
Kiall#topic Actions Items from last week17:03
*** openstack changes topic to "Actions Items from last week (Meeting topic: Designate)"17:03
*** BrianB_ has quit IRC17:03
KiallI'll skip a few of these that are duplicates ;)17:03
Kialltimsim file bug for PUT behavior in the API - Done17:03
KiallKiall give timsim mockup code for totalcount - Done17:03
Kiallmugsie push horzion code upstream - Done - Needs a +A17:04
*** padkrish has joined #openstack-meeting-alt17:04
*** rcurran has quit IRC17:04
rjrjr_transition powerdns backend to MDNS. - is that needed?17:04
*** esker has quit IRC17:04
Kiallpeople review ekarlso- 's secondary zones / v2 API bindings - Any takers on that one?17:04
Kiallrjrjr_: I think it needs to be renamed to pools :)17:04
vinod1I am looking at the secondary zones17:04
timsimI reviewed secondary zones, I think vinod did/is in progress17:04
*** nlahouti has joined #openstack-meeting-alt17:04
mugsie^ is just an initial push of internal code, so unless there is glaring errors, can we get it merged?17:04
KiallAnyway - We can discuss those in detail next week, I'll be putting Kilo release status on17:04
Kiallthe agenda from then on17:04
vinod1i can do a quick scan of the horizon code today17:05
*** paul_glass1 has joined #openstack-meeting-alt17:05
KiallJust want people to fill  out any missing stuff before next week :)17:05
Kiallvinod1: excellent :)17:05
KiallOkay - Moving on!17:05
Kiall#topic Pools - Where are we? (kiall)17:05
*** openstack changes topic to "Pools - Where are we? (kiall) (Meeting topic: Designate)"17:05
KiallSo - We've got lots merged, where do we go from here? :)17:05
betsyI’ve still got my work17:06
mugsiei think testing multiple pools, (even with manual switching) and seeing what breaks17:06
*** irenab has quit IRC17:06
betsyAlmost done just getting the tests working17:06
mugsiebetsy: cool17:06
rjrjr_i'm in the middle of a integrating pool manager with central without going through the backend proxy.17:06
Kiallmugsie: ++17:06
*** SridharRamaswamy has joined #openstack-meeting-alt17:06
betsyAfraid there’s going to be crazy merge issues17:06
mugsiebetsy: there always is17:07
KiallBeyond that - We'll need to port over the backends (PowerDNS, Fake, NSD4 etc. We'll discuss IPA style in the next topic)17:07
betsy:)17:07
*** Sukhdev has quit IRC17:07
KiallI've started PowerDNS - But hit a blocker and it was late ;)17:07
rjrjr_we also need to decide how to display via CLI/API the status and action.17:07
KiallDo we have any takers for the other easily portable backends?17:07
*** kebray has joined #openstack-meeting-alt17:07
mugsiei will have a look at nsd17:08
rjrjr_i handled fake already. 8^)17:08
timsimrjrjr_: You're doing bind9 too or no?17:08
KiallEasily portable: Fake (done), NSD4 (mugsie), PowerDNS (me), DynECT17:08
*** sgordon has joined #openstack-meeting-alt17:08
rjrjr_bind9 is done.17:09
KiallI'm guessing myself / ekarlso- / mugsie will need to do DynECT due to having an account with them17:09
*** margaret__ has quit IRC17:09
timsimCool.17:09
KiallI'll ask ekarlso- to, as he wrote it the first time ;)17:09
*** arnaud__ has quit IRC17:09
KiallOkay .. During porting - I'd suggest we replace the old backend, rather than add a new _pool version. Thoughts?17:09
vinod1+117:09
rjrjr_i think we should wait until we have pool manager integrated completely.17:10
*** achanda has joined #openstack-meeting-alt17:10
Kiallwell - there's a catch-22 there of can't kill the old code without breaking all the old-style backends17:10
rjrjr_never mind.  you are correct.  go for it.17:10
*** nlahouti has left #openstack-meeting-alt17:10
vinod1rjrjr_: With your current patchset - would the pool manger integration be complete?17:11
rjrjr_when it is  completed, yes.17:11
Kiallokay - so, beyond those ports (and IPA style backends, which we'll come to in the next topic). API chanegs to expose the status etc was suggested as a next step?17:11
rjrjr_i have questions about unit testing, but i'll wait until the open discussion.17:11
*** amrith is now known as _amrith_17:11
*** gyee_ has joined #openstack-meeting-alt17:12
Kiallkk.. I guess that leads into the next topic then.. Any more general pools status / progress / questions?17:12
vinod1Kiall - your code for recordsets seems to be propagating to pool attributes and now domain attributes17:12
*** pwac has quit IRC17:12
vinod1so we need to get that cleaned up17:12
Kiallvinod1: ah yes, timsim filed a bug for that..17:13
*** marcoemorais has joined #openstack-meeting-alt17:13
KiallDo we have any takers on it?17:13
mugsiewhats the bug?17:13
Kiall(I can't remember if tim assigned himself, or just filed it)17:13
*** johnbelamaric1 has joined #openstack-meeting-alt17:13
timsimNah I didn't assign it to myself.17:13
Kiallbug 139672017:13
uvirtbotLaunchpad bug 1396720 in designate "PUT on a Recordset with multiple Records results in delete/recreation of all Records" [High,Triaged] https://launchpad.net/bugs/139672017:13
*** johnbelamaric has quit IRC17:13
*** johnbelamaric has joined #openstack-meeting-alt17:14
mugsieI can look at it17:14
*** _amrith_ is now known as amrith17:14
mugsiehavent done much upstream workn this month ;)17:14
KiallThanks mugsie ..17:14
rjrjr_i hope we are not making any big changes to central until i get this patch in.  just a wish really. 8^)17:14
Kiallrjrjr_: lol...17:14
mugsierjrjr_: I am going to change everyhthing17:15
*** Leonr has joined #openstack-meeting-alt17:15
KiallIt should be an API layer fix ;)17:15
mugsiejust for the fun of it ;)17:15
KiallOkay.. Moving on :)17:15
*** marcoemorais1 has joined #openstack-meeting-alt17:15
Kiall#topic Pools - Removing the old backend code, migration path for IPA style backends? (kiall)17:15
*** openstack changes topic to "Pools - Removing the old backend code, migration path for IPA style backends? (kiall) (Meeting topic: Designate)"17:15
*** vishwanathj has quit IRC17:15
Kiallrjrjr_: patchset has started this, but myself and mugsie started talking about it last night..17:15
*** marcoemorais1 has quit IRC17:16
KiallWe're thinking we really need to provide the migration path for IPA style backends (also applies to the InfoBlox backend which should arrive soon)17:16
*** pnavarro has quit IRC17:16
rjrjr_based on the conversation yesterday, it seems like we will drop support for IPA in Kilo and add it back in the next cycle. 8^)17:16
mugsieI think that we can avoid that - hopefully17:17
timsimWhat does that entail?17:17
Kiallmugsie managed to change my mind on that, so wanted to discuss with the group and come to a decision.17:17
*** marcoemorais1 has joined #openstack-meeting-alt17:17
KiallWe figure it kinda fits into timsim's new-agent proposal ..17:17
*** rmoe has joined #openstack-meeting-alt17:17
mugsieI would think that we can re purpose the "new agent", by extending it slightly17:17
*** marcoemorais has quit IRC17:17
*** johnbelamaric1 has quit IRC17:17
KiallIf we wanted old-style backends to work as is.. Agent listens for NOTIFY, does AXFR (i.e copy the secondary zone code), then splits that into a backend - for bind - that would just re-render the zonefile and rndc reload..17:18
timsimWhat extra work is there for that backend for IPA style things?17:18
KiallFor IPA, it might do an AXFR against IPA, compare, and call the old-style backend methods to write our the changes17:18
timsimSeems doable.17:18
mugsieyeah, i think so17:18
KiallYea, I think it sounds doable at 1000 ft alright :)17:19
mugsiei just don't want to dump some of the backends, with out an attempt to help them work17:19
betsykiall: It always does :D17:19
rjrjr_so, what does that mean for my current work?17:19
rjrjr_once it is accepted, IPA is broken. 8^(17:19
rjrjr_the timing here is going to be tricky.17:20
mugsiei think we can get ^ done fairly quickly17:20
KiallAnyway, If we want to ensure we keep that support - then getting that work (work == bones of new-agent) done becomes a priority... thoughts?17:20
timsimI'd agree.17:20
Kiallrjrjr_: yea, that's where I'm hoping we come to a decision and get the bones written up really quickly so as to not block you for too long17:20
rjrjr_i'm concerned, but that's because i see what still needs to happen with pool manager.17:21
mugsieI would like to make it a prioroty17:21
timsim(The Agent is a rather large RAX priority, so it looks like I was going to be working on it anyway)17:21
Kiallrjrjr_: Yea, finding the balance is the fun one ;)17:21
Kiall#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule17:21
mugsiei think that we can have 2 groups working in tandem, and then we can do some git foo to have the switch done right17:21
timsimmugsie: We can do a topic branch! oh wait...17:22
Kiallk1 is Dec 18th, and we've been hoping for Pools to be effectively feature complete by then..17:22
mugsietimsim: funnily, neutron has topic branches17:22
*** mwagner_lap has joined #openstack-meeting-alt17:22
mugsie:D17:22
*** nyechiel_ has quit IRC17:22
Kiallwhich is  431 commits behind master ;)17:22
timsimKiall: So would you want to wait on merging any "agent" stuff until after k1?17:23
KiallGonna be a fun rebase!17:23
mugsieI think we can look a tthe spec for the agent, propose changes today / tomorrow, and get work started quickly17:23
rjrjr_but, pool manager implies broken IPA without agent.17:23
mugsiefor K1 the agent doesnt have to pretty or quick17:23
Kialltimsim: well, I dunno.. Do we break IPA style for K1, and fix it in K2? or not have 100% pools in K1?17:23
mugsiehave to be*17:23
*** AJK__ has quit IRC17:23
rjrjr_i think pools should be the priority.  but i'm biased. 8^)17:23
KiallI think I'm OK with breaking IPA style in K1, assuming we commit to fixing it in K217:24
timsimKiall: Might be a stretch to get the agent+IPA business done by K117:24
mugsiei think we can postpone that call till next week. if next week there is not much progress, we break IPA in K117:24
timsimI think that seems reasonable.17:24
*** yalie has quit IRC17:25
timsimSo action people to review the agent spec then?17:25
rjrjr_i'm okay with that.17:25
mugsieyup17:25
KiallAny other opinions or shall we call it break IPA-style in K1,commit to fixing in K2, unless we can agree next week that Pools+Agent is doable by K1?17:25
Kiall#action all review new-agent spec17:25
*** ndipanov is now known as ndipanov_gone17:25
mugsieaim to keep it, and decide next week17:25
timsimmugsie: +117:25
Kiallmugsie: yea, aim to keep, see how reality based that is17:25
timsim#link https://review.openstack.org/#/c/131530/2 Agent spec17:26
rjrjr_this is going to be fun...17:26
mugsierjrjr_: :)17:26
Kiallrjrjr_: yea, sorry :(17:26
KiallOn the plus side, you'll learn more about git rebase :D17:26
* Kiall ducks for cover17:26
timsimYou're going to be a rebase master rjrjr_ :P17:26
rjrjr_yeah, there is that.17:26
KiallOkay - Anything else on this before Open Discussion17:27
Kiall?*17:27
mugsieI am good.17:27
timsimI'm good.17:27
Kiall#topic Open Discussion17:27
*** openstack changes topic to "Open Discussion (Meeting topic: Designate)"17:27
rjrjr_mid-cycle summit - will rackspace be able to attend in San Jose?17:27
vinod1rjrjr: Just wanted to check if you had any inputs on the horizon code17:27
KiallAny other topics? rjrjr_, you had one?17:27
*** johnbelamaric1 has joined #openstack-meeting-alt17:28
vinod1since ebay was interested in horizon17:28
rjrjr_i handed the code to PK.  he is in the process of getting it up and running.  i'll check with him today and get back to you about it.17:28
*** johnbelamaric has quit IRC17:28
*** johnbelamaric2 has joined #openstack-meeting-alt17:28
rjrjr_mid-cycle summit?17:28
Kiallrjrjr_: if he's stick, ping us :)17:28
Kiallstuck*17:28
mugsieyeah, I have been talkig to him17:28
rjrjr_sure.  stick or stuck.17:28
Kiallkk17:28
vinod1for the mid-cycle summit - i still haven't heard back anything from the higher ups17:29
rjrjr_okay.17:29
KiallIf I remember right - Joe had said it should be fine, but official approval etc etc17:30
*** jcoufal has quit IRC17:30
vinod1correct17:30
timsimYeah, that's what it looks like.17:30
rjrjr_can we get a go/no go by 12/24?17:30
timsimWe can try17:30
KiallIt's a "go" from HP anyway...17:30
rjrjr_cool!17:30
timsimWe'll sick Joe on it :P17:30
rjrjr_okay, now a question about unit testing...17:31
rjrjr_so, if i'm understanding what i'm seeing, i need to have central, pool manager, and mdns running.17:31
rjrjr_pool manager will use the fake backend i wrote.17:31
*** avozza is now known as zz_avozza17:31
rjrjr_mdns needs fake stuff too, correct?17:31
KiallIdeally, we fix Pool Mgr's shiney new tests to, well, not need all that17:31
rjrjr_the problem is central is failing miserably on tests.17:32
*** johnbelamaric1 has quit IRC17:32
*** mattfarina has joined #openstack-meeting-alt17:32
rjrjr_ideally, mdns would have fake calls for NOTIFY, AXFR, etc.17:33
rjrjr_ since we won't really have a backend.17:33
*** stannie has quit IRC17:33
KiallIf I remember right, all central calls -> pools are cast - i.e. fire and forget - those can be mocked easily, and we can just validate the right stuff has been passed into the call17:33
rjrjr_so, a mock pool manager then?  do we have an example of a mock service?17:33
KiallWell, not a full mock... you can do something like this..17:34
rjrjr_i'm new to Python unit testing, so any guidance you can provide is appreciated.17:34
*** zz_avozza is now known as avozza17:34
Kiallwith mock.patched(pool_manager_api, 'some_method') as m:17:34
*** SushilKM has joined #openstack-meeting-alt17:34
Kiallthen when central calls "some_method" it'll be just record the args and return nothing (like the real call would)17:34
Kialland m.calls[0].args or similar will let you validate the correct things are passed in17:35
*** bubbva has quit IRC17:36
rjrjr_okay.  this is a learning curve for me.  this might take me a couple of days.17:36
*** bubbva has joined #openstack-meeting-alt17:36
Kiallhttps://github.com/openstack/designate/blob/master/designate/tests/test_mdns/test_notify.py#L3717:36
Kiall^ Similar example from mDNS code17:37
KiallIn that case, patching the dns.query.udp() method17:37
*** teran has quit IRC17:37
KiallWe can sync up after the meet if you like?17:37
rjrjr_okay.17:37
*** ksushil_ has quit IRC17:38
*** johnbelamaric2 has quit IRC17:38
KiallCool - Any other topics?17:38
*** johnbelamaric has joined #openstack-meeting-alt17:38
timsimI'm good.17:38
*** johnbelamaric has left #openstack-meeting-alt17:38
Kiallmugsie / vinod1 / betsy ?17:38
mugsienopoe17:38
vinod1Nothing from me17:38
*** sergef has quit IRC17:39
betsyI’m good17:39
KiallCool, will call it a day then :)17:39
*** ijw has joined #openstack-meeting-alt17:39
Kiallrjrjr_: give me 10 mins and I'll ping you if your free then...17:39
KiallThanks all :)17:39
Kiall#endmeeting17:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:39
openstackMeeting ended Wed Dec  3 17:39:47 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-12-03-17.01.html17:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-12-03-17.01.txt17:39
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-12-03-17.01.log.html17:39
*** vinod1 has left #openstack-meeting-alt17:40
*** rjrjr_ has quit IRC17:40
*** armax has quit IRC17:41
*** mugsie has left #openstack-meeting-alt17:41
*** ddmitriev has quit IRC17:42
*** tdruiva|away is now known as tdruiva17:43
*** edwardb has quit IRC17:44
*** SushilKM has quit IRC17:44
*** yamamoto has quit IRC17:45
*** vishwanathj has joined #openstack-meeting-alt17:45
*** jaypipes has quit IRC17:45
*** HeOS has quit IRC17:46
*** nshaikh has joined #openstack-meeting-alt17:46
*** hogepodge has quit IRC17:47
*** ddmitriev has joined #openstack-meeting-alt17:47
*** colinmcnamara has quit IRC17:47
*** edwardb has joined #openstack-meeting-alt17:48
*** hogepodge has joined #openstack-meeting-alt17:49
*** gmatefi has joined #openstack-meeting-alt17:49
*** jmontemayor has quit IRC17:50
*** avozza is now known as zz_avozza17:50
*** Barker has quit IRC17:50
*** armax has joined #openstack-meeting-alt17:50
*** colinmcnamara has joined #openstack-meeting-alt17:50
*** _nadya_ has quit IRC17:51
*** armax has quit IRC17:52
*** shayneburgess has joined #openstack-meeting-alt17:56
*** SlickNik has joined #openstack-meeting-alt17:57
*** ian_ott has quit IRC17:57
*** shayneburgess has quit IRC17:57
*** sunnyr has joined #openstack-meeting-alt17:58
*** tonytan4ever has quit IRC17:59
SlickNik#startmeeting trove17:59
openstackMeeting started Wed Dec  3 17:59:08 2014 UTC and is due to finish in 60 minutes.  The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot.17:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:59
*** openstack changes topic to " (Meeting topic: trove)"17:59
openstackThe meeting name has been set to 'trove'17:59
SlickNikGiving folks a few minutes to trickle in.17:59
*** _nadya_ has joined #openstack-meeting-alt18:00
SlickNikThe meeting agenda is at:18:00
*** derekh has quit IRC18:00
SlickNik#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting18:00
amrith./18:00
sgotliv_./18:00
amrithoh crap, he showed up.18:00
*** AJ74 has joined #openstack-meeting-alt18:00
esmute0/18:01
schango/18:01
sgotliv_amrith, I didn't see that ;-)18:01
amrithsgotliv_, I was counting on that.18:01
*** AJaeger_ has joined #openstack-meeting-alt18:01
vgnbkro/18:01
peterstaco/18:01
dougshelley66o/18:02
edmondko/18:02
SlickNik#topic Discuss merge order for various OSLO related patches18:02
*** openstack changes topic to "Discuss merge order for various OSLO related patches (Meeting topic: trove)"18:02
*** AJK__ has joined #openstack-meeting-alt18:02
*** _nadya_ has quit IRC18:02
*** gmatefi has quit IRC18:02
kanzaroso/18:02
*** edwardb has quit IRC18:02
amrithsounds like mine.18:02
SlickNikamrith:  go for it18:03
abramleyo/18:03
amrithso, I'd like to discuss with the group the order in which we get these large oslo patches in.18:03
amrithI have several.18:03
amrithSergey has RPC messaging.18:03
georgelorcho/18:03
amrithMine are simple (largely changes to requirements.txt)18:03
amrithgated behind my changes are 3 sets of changes18:03
*** balajiiyer has joined #openstack-meeting-alt18:03
amrith1. processutils -> oslo.serialization18:03
*** dboik has quit IRC18:03
amrith2. resynch oslo incubator18:03
amrith3. some security related changes which didn't make it to juno18:04
amrithI would like to get the deprecated modules changes done18:04
*** dboik has joined #openstack-meeting-alt18:04
amrithso I can move forward.18:04
*** padkrish has quit IRC18:04
amrithI need core reviewers18:04
amrithto +2 and wf +118:04
*** harlowja_away is now known as harlowja_18:04
amriththe earlier decision was to wait for rpc messaging18:04
amrithbut that seems to be also not moving.18:05
SlickNikSo at the summit we decided we'd push oslo.messaging through first since that was the biggest and riskiest change.18:05
*** edwardb has joined #openstack-meeting-alt18:05
amrithso I'm raising the general issue of how we move forward.18:05
*** padkrish has joined #openstack-meeting-alt18:05
*** emagana has joined #openstack-meeting-alt18:05
amrithSlickNik, yes, I know that. two questions. should we revisit that, or should we put some urgency on merging oslo.messaging.18:05
amrithI don't care about the order.18:05
*** bdpayne has joined #openstack-meeting-alt18:05
esmuteALL: THe fire alarm just went off here in the Seattle office...18:05
amrithbut I know which would be easier (for me).18:05
amriththat's the oslo.messaging patch.18:06
amrithsometimes it does that18:06
esmuteif you talk to us and we dont respond, we are not ignoring you18:06
amrithwell, try recheck18:06
amrithit works sometimes.18:06
*** Sukhdev has joined #openstack-meeting-alt18:06
amrithsgotliv_, you've got to address the issue of oslo.messaging patch setting off the fire alarm.18:06
SlickNikWell, we were waiting on an updated spec which was updated yesterday.18:06
*** slagun has left #openstack-meeting-alt18:07
*** andreykurilin_ has joined #openstack-meeting-alt18:07
SlickNikAnd amrith when I talked with you yesterday, you said you were still in the process of pulling down the oslo.messaging changes and going through them.18:08
*** Leonr has quit IRC18:08
amrithI am18:08
amrithand it is taking time.18:08
*** sbalukoff has quit IRC18:08
amrithI have to do that, no matter the merge order.18:08
*** Leonr has joined #openstack-meeting-alt18:08
SlickNikThere's also an issue of them making the int-tests run slower, which is pushing the dsvm job past its time limit.18:08
amrithat issue now is the question not of whether oslo.messaging must merge or not but rather whether it should hold up other things that are ready.18:08
*** balajiiyer has left #openstack-meeting-alt18:09
amriththe deprecated modules changes had (no longer) spec dependencies. we opted to go for the bug instead.18:10
amriththe code itself is (largely) updates to requirements.txt18:10
amrithhence my request to change the order.18:10
sgotliv_I have no problem with the order18:10
*** Barker has joined #openstack-meeting-alt18:10
sgotliv_I just want to understand messaging status18:11
*** shwetaap has quit IRC18:11
amrithSlickNik, if we don't want to change the order, that's fine too. could I get the changes +2'ed and pending a WF change.18:11
amrithit would be ideal to merge18:12
sgotliv_amrith, your changes are very important18:12
sgotliv_they close several issues18:12
amrithbecause that would make the oslo-incubator rebase easier to handle18:12
*** paul_glass1 has quit IRC18:12
*** dimtruck is now known as zz_dimtruck18:12
*** Leonr has quit IRC18:13
SlickNikI'm fine with changing the order — someone would have to take on the job of rebasing the oslo.messaging patch (again).18:13
sgotliv_I will do that18:13
amrithI will help18:14
amrithin any way I can18:14
amrithincluding doing that rebase if required; the intersection is small.18:14
*** Leonr has joined #openstack-meeting-alt18:14
SlickNikOkay, then. Let's move forward with that plan.18:15
SlickNiksgotliv_: Right now for status — I'm good with the messaging changes and spec — just trying to understand why they cause the int-tests to run slower and fail in the given time limit, or see if we can extend that.18:15
*** edwardb has quit IRC18:15
SlickNikI'll work on getting that piece ironed out.18:15
sgotliv_SlickNik, can I help?18:16
*** arnaud__ has joined #openstack-meeting-alt18:16
sgotliv_I didn't realize that there is a problem18:16
amrithSlickNik, is that the reason for the gate failures on the messaging change?18:17
*** markmcclain has joined #openstack-meeting-alt18:17
*** jrakerevelant has quit IRC18:17
SlickNikamrith / sgotliv_: The dsvm-functional tests seem to be timing out on every patchset.18:17
SlickNikeg: http://logs.openstack.org/84/94484/46/check/gate-trove-functional-dsvm-mysql/d53d0fd/console.html.gz18:17
*** johnthetubaguy is now known as zz_johnthetubagu18:17
*** rushiagr is now known as rushiagr_away18:17
SlickNikif you scroll to the very bottom you'll see it.18:18
sgotliv_I will take a look18:18
amrithah, 95 minute deadline18:18
*** hareeshpc has joined #openstack-meeting-alt18:18
amrithshould see how close to it we are without the messaging patch18:18
*** tzn has joined #openstack-meeting-alt18:19
*** dboik has quit IRC18:19
sgotliv_i see 30minutes gap between last test result and the next line18:19
sgotliv_looks weird18:19
SlickNikIt's usually 70-85 mins depending on how slow the node is.18:19
peterstacWhat test is it trying to run that times out?18:19
amriththe one after detach replica18:20
amriththere is a test18:20
*** zz_avozza is now known as avozza18:20
peterstac(i.e. waht comes after test_slave_is_not_read_only?)18:20
amriththat I saw the review for yesterday18:20
amriththat didn't have a timeout18:20
amrithit had a poll_until18:20
amrithwith no timeout18:20
*** achanda has quit IRC18:20
amrithmariam had a comment on the review questioning whether a timeout should be added18:20
amrithyes, had to do with slave readonly18:20
amrithor was the test immediately after that18:21
*** shwetaap has joined #openstack-meeting-alt18:21
SlickNikSo perhaps that test is always failing for the oslo.messaging patch.18:21
SlickNikI saw that as well.18:21
peterstacThe read_only one seems to pass pretty quickly (4.22 s)18:21
*** tbarron has joined #openstack-meeting-alt18:21
*** achanda has joined #openstack-meeting-alt18:21
SlickNikit's     def test_slave_user_removed(self):18:22
peterstacThat shouldn't take long - think there's a bug in the test?18:23
sgotliv_usually when tests stuck means Trove try to reach out to the real queue18:23
sgotliv_I have to check mocks18:23
*** SumitNaiksatam has joined #openstack-meeting-alt18:23
SlickNiksgotliv_: There's no mocks in the int-tests.18:23
sgotliv_oh18:23
amrithhttps://review.openstack.org/#/c/135398/2/trove/tests/api/replication.py,cm18:23
SlickNik(in real mode)18:24
peterstacThis test looks like it was doing real work18:24
amrithtest_slave_user_removed18:24
amriththat's the test in question18:24
peterstacBut still shouldn't take long (removing a user should be pretty quick)18:24
amrithshouldn't but it sure appears that it is.18:24
*** danritchie has joined #openstack-meeting-alt18:24
*** vkmc has joined #openstack-meeting-alt18:24
SlickNikpeterstac: possibly something else going on here with the message?18:24
*** Leon has joined #openstack-meeting-alt18:25
*** Leon is now known as Guest4473218:25
sgotliv_I suggest to discuss it in the main room later18:25
amrithok18:25
*** colinmcnamara has quit IRC18:26
SlickNikAnyway, that's probably the last issue to look into before the merge — all the other tests pass, and that's one of the last few tests to run18:26
amrithso popping stack, on the present topic.18:26
SlickNikThanks sgotliv_18:26
*** esker has joined #openstack-meeting-alt18:26
amrithare we ok with merging decrepit and geriatric oslo-incubator modules change first?18:26
amrithit was called something else but I can't remember what it was18:27
*** jjmb has joined #openstack-meeting-alt18:27
SlickNikYes, let's do that.18:27
amrithobsolete and deprecated, that's what it was.18:28
amrithok, thanks.18:28
*** esker has quit IRC18:28
*** Leonr has quit IRC18:28
SlickNikanything else on this before we move on?18:28
*** jjmb has quit IRC18:29
SlickNik.18:29
SlickNik#topic Discuss status of moving guest agent to its own repository patch set18:29
*** openstack changes topic to "Discuss status of moving guest agent to its own repository patch set (Meeting topic: trove)"18:29
amrithI put this on the agenda as well because it is a significant change18:29
*** jjmb has joined #openstack-meeting-alt18:29
amrithand we discussed some (several) weeks ago that we should queiesce the tree18:30
amrithwhen we want this to merge.18:30
amrithI wanted to get a sense of where we are with this change and how it impacts other (potentially large) changes that are in the pipe.18:30
schangamrith, other then the occasional rebase, I haven't don't anything else on it.18:31
schangamrith, it's waiting for more feedback.18:31
amrithok.18:31
sgotliv_it definitely has a huge impact on messaging patch18:31
amrithyup18:32
vgnbkrIs this about moving the guest agent to it's own git repo, or just the refactoring?18:32
SlickNikvgnbkr: just the refactoring — in the same repo18:32
schangfyi, https://review.openstack.org/#/c/119425/18:32
vgnbkrok, great.18:33
SlickNikAlso this needs to be reviewed first https://review.openstack.org/#/c/136918/18:33
SlickNiki.e. the corresponding spec18:33
amrithsgotliv_, why is there a large overlap with o.m?18:33
amrithshould be small to non-existant, I thought.18:33
amrithlet me check18:33
SlickNikamrith: I would think it changes the guest RPC endpoints for every datastore.18:34
SlickNik(i.e. all the managers)18:34
*** esker has joined #openstack-meeting-alt18:35
amrithok, I'll look later but I recall at a previous meeting where it was discussed and the consensus (or statment) was that the overlap would be small.18:35
amrithgiven that the overlap may be large18:36
sgotliv_amrith, try to rebase messaging patch on top of that one18:36
amrithit may not make sense for one of the two parties to continually rebase code now, until the other major change is merged.18:36
amrithwe need to pick the ordering18:36
*** armax has joined #openstack-meeting-alt18:36
amrithwhat do we want to do?18:36
SlickNikSo it looks like we need more feedback / reviews on this — and oslo.messaging seems to be farther along.18:37
*** armax has quit IRC18:37
SlickNikSo I'd recommend merging that one first, while we get more reviews on this, and then rebasing this on top of that and merging it.18:38
*** nkrinner has quit IRC18:38
amrithas I recall there was some urgency at RAX to get this one done18:38
amrithis that no longer the case18:38
*** armax has joined #openstack-meeting-alt18:38
amrithanyone at rax here?18:38
sgotliv_SlickNik, you propose to merge messaging after that patch?18:38
SlickNiksgotliv_: other way round. merge oslo.messaging first.18:39
sgotliv_thanks you!!!!18:39
*** padkrish has quit IRC18:40
*** banix has quit IRC18:40
amrithphew18:40
*** gholler_ has joined #openstack-meeting-alt18:40
sgotliv_amrith, I am not sure that reason is valid!18:40
amriththe sigh that sergey let out was so loud that it was detected by seismometers all over the world.18:40
sgotliv_we don't represent companies upstream18:41
sgotliv_remember?18:41
SlickNikamrith: Don't get me wrong, it's still an important patch to merge18:41
*** padkrish has joined #openstack-meeting-alt18:41
SlickNikSo we should look into reviews + feedback.18:42
*** gholler__ has joined #openstack-meeting-alt18:43
SlickNikand merging it soon.18:43
amrithSlickNik, fine with me. The last time when this was discussed some from RAX (maybe robert myers but also others) had expressed an interest in merging soon.18:43
*** gholler has quit IRC18:44
*** jjmb1 has joined #openstack-meeting-alt18:44
amrithI think we're set with this18:44
*** yamahata has joined #openstack-meeting-alt18:45
SlickNikSounds good. Any other questions wrt this?18:45
amrithso the conclusion was that the order would be18:45
SlickNik.18:45
*** yamamoto has joined #openstack-meeting-alt18:45
amrith1. obsolete modules18:45
amrith2. messaging18:45
amrith3. split guest agent18:45
amriththx18:46
SlickNikmore like:18:47
SlickNik1. obsolete modules18:47
SlickNik1. messaging18:47
SlickNik3. split guest agent18:47
*** gholler_ has quit IRC18:47
*** dboik has joined #openstack-meeting-alt18:47
*** jjmb has quit IRC18:47
*** zz_dimtruck is now known as dimtruck18:48
*** ivar-lazzaro has joined #openstack-meeting-alt18:48
SlickNikSince we're saying that we'll let the obsolete modules merge — but if oslo.messaging makes in in after some of them while others are still in review, that's okay since there isn't an implicit ordering between those.18:48
*** jjmb1 has quit IRC18:48
amrithok, I'm confused. but that's fine.18:49
*** Haiying has joined #openstack-meeting-alt18:49
SlickNiki.e. we're allowing obsolete modules to merge before oslo.messaging, but not requiring it.18:49
amrithok18:50
*** bknudson has quit IRC18:50
SlickNik#topic Open Discussion18:50
*** openstack changes topic to "Open Discussion (Meeting topic: trove)"18:50
dougshelley66i have one18:50
SlickNikdougshelley66: go for it18:51
dougshelley66just wanted to introduce Nirav Shah (nshah) - he joined our community this week18:51
*** achanda has quit IRC18:51
dougshelley66(Note to sgotliv_ - notice i didn't say he joined Tesora :) )18:51
*** yamamoto has quit IRC18:51
SlickNikWelcome nshah!18:51
*** achanda has joined #openstack-meeting-alt18:52
sgotliv_welcome nshah!18:52
*** achanda has quit IRC18:52
*** achanda has joined #openstack-meeting-alt18:52
sgotliv_dougshelley66, I have a feeling you will say it in the future :-)18:52
edmondkwelcome!18:52
dougshelley66sgotliv_, have to eat....18:53
SlickNikFeel free to hit me (or any of the others) up in #openstack-trove if you have any questions.18:53
nshahThanks all!18:53
SlickNikOn the same note — I'd like you all to meet danritchie as well18:54
dougshelley66welcome danritchie!18:54
esmuteWelcome danritchie!18:54
sgotliv_wellcome18:54
schanghello danritchie18:54
SlickNikHe's ramping up on trove, and is hoping to have his first contribution in soon. :)18:55
peterstachi danritchie!18:55
amrithhello! welcome to trove!18:55
amrithwhile we are doing intros, and before sergey says it ... please also welcome vkmc to the trove community. Welcome Victoria!18:55
danritchieThanks all!  Cheers...18:56
edmondkWelcome Victoria!18:56
*** rcleere is now known as rcleere_away18:56
SlickNikvkmc: Welcome aboard. :)18:56
SlickNikWow so many new faces.18:56
*** sdake has quit IRC18:56
vkmco/18:56
schangvkmc: hello :)18:56
SlickNikGood to see it.18:56
esmuteWelcome vkmc18:56
vkmcthanks all :)18:56
dougshelley66SlickNik, do we still have that policy where the new people have to buy drinks at mid-cycle?18:57
esmute@SlickNik Any update about the mid-cyle meetup?18:57
peterstacYeah, like the policy dougshelley66 is talking about ;)18:57
SlickNikesmute: confirmed to be Feb 3-518:57
esmutedougshelley66: And tell a joke too18:57
amrithdougshelley66, yes, that is the policy. VKMC bought drinks in Paris.18:57
vkmchaha :)18:58
*** grapex_ has joined #openstack-meeting-alt18:58
*** padkrish has quit IRC18:59
amrithSlickNik, any updates on hotes18:59
amrithhotels18:59
SlickNikesmute: Good reminder that I need to update the wiki with this info.18:59
*** Barker has quit IRC18:59
amrithand block rates18:59
*** Sam-I-Am has joined #openstack-meeting-alt18:59
*** dboik has quit IRC18:59
*** teran has joined #openstack-meeting-alt18:59
SlickNikamrith: Haven't heard back yet :(. I need to follow up.18:59
*** edwardb has joined #openstack-meeting-alt18:59
*** esker has quit IRC18:59
amrithneed a hand?18:59
*** emagana has quit IRC19:00
SlickNik#action Slicknik to follow up on hotels and block rates for mid-cycle. And update the wiki.19:00
sgotliv_Guys, I apologize, but I have to go. Have a nice day.19:00
*** padkrish has joined #openstack-meeting-alt19:00
*** dboik has joined #openstack-meeting-alt19:00
*** emagana has joined #openstack-meeting-alt19:00
SlickNikamrith: I'll ping you if I do, thanks!19:00
SlickNikAnything else?19:00
*** Sukhdev has quit IRC19:01
*** annegent_ has joined #openstack-meeting-alt19:01
SlickNik.19:01
*** emagana_ has joined #openstack-meeting-alt19:01
SlickNik#endmeeting19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
openstackMeeting ended Wed Dec  3 19:01:30 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-12-03-17.59.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-12-03-17.59.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-12-03-17.59.log.html19:01
SlickNikThanks all!19:01
*** esker has joined #openstack-meeting-alt19:01
annegent_#startmeeting docteam19:02
openstackMeeting started Wed Dec  3 19:02:04 2014 UTC and is due to finish in 60 minutes.  The chair is annegent_. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: docteam)"19:02
openstackThe meeting name has been set to 'docteam'19:02
annegent_I'll go ahead and use "docteam" here so logs are easy to find19:02
AJaeger_thanks, annegent_19:02
annegent_who all is here?19:02
Sam-I-Amhi19:02
zigoo/19:02
AJaeger_\o/19:02
AJaeger_Enough to start ;)19:02
annegent_and o/19:02
annegent_cool19:02
*** baoli has quit IRC19:03
annegent_Okay, the agenda is in the mailing list post from today19:03
*** mwagner_lap has quit IRC19:03
*** virtuallynathan_ has joined #openstack-meeting-alt19:03
annegent_#link http://lists.openstack.org/pipermail/openstack-docs/2014-December/005568.html19:03
annegent_let's start with current status19:03
annegent_#topic Description of current state19:03
*** openstack changes topic to "Description of current state (Meeting topic: docteam)"19:03
*** juzuluag has joined #openstack-meeting-alt19:04
*** Barker has joined #openstack-meeting-alt19:04
annegent_Lots of fact finding, I actually had to look up some stuff for this :)19:04
annegent_So, we currently publish four Install Guides19:04
annegent_from one directory in openstack-manuals repo19:04
*** sgotliv_ has quit IRC19:04
*** jmontemayor has joined #openstack-meeting-alt19:04
*** emagana has quit IRC19:04
annegent_The files are automatically built and also the translation automation is in place for these.19:05
Sam-I-Amyep19:05
annegent_Last release, this blueprint addressed an audit of the install guides: https://blueprints.launchpad.net/openstack-manuals/+spec/installation-guide-improvements19:06
*** rcleere_away is now known as rcleere19:06
Sam-I-Amstill not finished, but pretty close.19:06
Sam-I-Amhuge amount of work19:06
annegent_just the facts :)19:07
*** yamahata has quit IRC19:07
annegent_oh also19:07
annegent_#link19:07
annegent_er19:07
annegent_#link https://wiki.openstack.org/wiki/Documentation/InstallationGuideImprovements19:07
*** safchain has quit IRC19:07
*** KLevenstein has joined #openstack-meeting-alt19:08
*** grapex_ has left #openstack-meeting-alt19:08
annegent_The blueprint addressed "Replace openstack-config (crudini) commands with general configuration file editing."19:08
*** baoli has joined #openstack-meeting-alt19:09
annegent_There's a chapter about debconf output for the apt-debian version19:09
*** andreykurilin__ has joined #openstack-meeting-alt19:09
annegent_#link http://docs.openstack.org/juno/install-guide/install/apt-debian/content/ch_debconf.html19:09
*** andreykurilin_ has quit IRC19:09
*** gholler_ has joined #openstack-meeting-alt19:09
annegent_And this one I had to look up, what's documented for DevStack?19:09
Sam-I-Amwhat do you mean?19:10
annegent_#link http://docs.openstack.org/developer/devstack/19:10
annegent_Only Ubuntu 14.04 (Trusty), Fedora 20 and CentOS/RHEL 6.5 are documented here. OpenStack also runs and is packaged on other flavors of Linux such as OpenSUSE and Debian.19:10
annegent_from that page ^^19:10
annegent_I wanted to include that fact finding since Tom brought up DevStack in the thread19:10
Sam-I-Amahh19:10
*** baoli has quit IRC19:10
zigoAs much as I know, what is written for Devstack in Ubuntu also works for Debian.19:11
annegent_good to know19:11
annegent_wasn't sure myself!19:11
annegent_Then there are install tools documented by different companies in their own domains or doc sites19:11
zigoThere used to be a few glitches which were corrected, though it's been a long time I didn't try.19:12
annegent_anything else relevant?19:12
annegent_Oh I thought of one more thing.19:12
*** timsim has left #openstack-meeting-alt19:12
Sam-I-Amsome aspects of openstack are kernel specific (neutron comes to mind)19:12
AJaeger_zigo: The document says that it works for Debian but that it's not documented further...19:12
Sam-I-Amwhich might be why they support certain distro releases19:12
annegent_I found this in the InstallationGuideImprovments wiki page "Modularize install guides for re-use as basic install guide for training guides.(dguitarbite/Pranav Salunke)" but I don't know how that was resolved exactly?19:12
zigoAJaeger_: Perfect then!19:12
annegent_because I think training plays into the goals for the install guide too, so wanted to bring that up while stating current state.19:13
annegent_I think current state for training is "working on a blueprint?"19:13
*** gholler has joined #openstack-meeting-alt19:13
annegent_anyone know?19:13
AJaeger_annegent_: they're still playing with the Install Guide, I helped them to build it only for Ubuntu, they did not profile at all19:13
Sam-I-Amannegent_: the original idea is that the training guide would follow the install guide since it covers basic service installation19:13
annegent_AJaeger_: ok19:13
*** gholler__ has quit IRC19:13
AJaeger_had a guide for "Debian;Ubuntu;Fedora;openSUSE" or something like that19:13
AJaeger_That looked funny ;(19:13
annegent_Sam-I-Am: in Paris they wanted their own chapter too19:14
annegent_AJaeger_: heh19:14
annegent_but I didn't know latest state there19:14
AJaeger_Sam-I-Am: they're moving closer know19:14
AJaeger_s/know/now/19:14
annegent_Okay AJaeger_ was it basically a conditional but new guide?19:14
Sam-I-Amannegent_: they could do X and get a version that meets the training guide needs (e.g., stick with neutron, not nova-or-neutron)19:14
AJaeger_annegent_: it was our Install Guide, they just did not profile properly.19:14
annegent_Sam-I-Am: yeah it was the mechanics of that we hadn't figured out19:14
annegent_and those mechanics may be useful here, not real sure though19:15
annegent_AJaeger_: ah ok19:15
Sam-I-AmAJaeger_: last i spoke with them, they wanted a top-level guide that only includes the files they want19:15
*** gholler_ has quit IRC19:15
AJaeger_Sam-I-Am: We made some progress in Paris19:15
AJaeger_but let's not discuss that further now19:16
*** gholler_ has joined #openstack-meeting-alt19:16
Sam-I-Amyes19:16
annegent_ok, yeah don't want to dig too deep there, just wanted to know current state19:16
annegent_which sounds like "training wants a certain install guide but haven't figured out how to build it yet"19:16
annegent_yeah?19:16
Sam-I-Ampretty much19:16
AJaeger_yep19:16
annegent_Okay let's move into stated goals then. I did some etherpad digging!19:17
annegent_First, all the way back to Grizzly19:17
annegent_#link https://etherpad.openstack.org/p/restructure-docs-session19:17
annegent_My favorite quote, "What about for Havana, jettisoning the Install guides and focusing on configuration guides. Doc sequestration?"19:17
annegent_now we all know that didnt' happen19:17
annegent_there were board members who wanted to be sure there's an upstream install guide19:17
annegent_so they gave us donated resources19:18
annegent_But some other history is in there19:18
annegent_themes like "Consistency for IP ranges" and "One happy path"19:18
annegent_"One or two compute nodes" vs "all-in-one" was still being discussed19:18
*** mattgriffin has quit IRC19:19
annegent_some audience analysis, and also asking "what is the main goal for the install?"19:19
*** gholler has quit IRC19:19
* sgordon sneaks in late19:19
annegent_hey sgordon welcome19:19
annegent_so, anyone want to throw out "main goal for install"19:20
annegent_I can try19:20
Sam-I-Am"basic working system"19:20
sgordonlook mum i ran a vm!19:20
annegent_"As an admin, I want to try to install OpenStack to learn about how the components work together so that I can automate an install"19:20
sgordonand it can download pictures of cats!19:20
Sam-I-Amservices and their interactions are too complex to figure out from a config reference19:20
Sam-I-Amplus all the underlying dependencies (networking is hard)19:21
annegent_"As a beginner, I want to install OpenStack on hardware I have available so that I can learn enough to ask more questions about OpenStack."19:21
Sam-I-Amnothing works without networking, so we need a place to hand-hold19:21
zigoannegent_: This is *not* a guide about teaching how to do automation, if it was the goal, then we failed it.19:21
Sam-I-Amsgordon: lol19:21
Sam-I-Amzigo: but once you have a manual installation, you know what your automation system needs to do19:22
annegent_"As an architect, I want to install OpenStack enough times that I understand it well enough to provide an analysis for its applicability to my organization."19:22
*** dboik has quit IRC19:22
zigoSam-I-Am: Yes, but that's not the goal, IMO.19:22
*** HeOS has joined #openstack-meeting-alt19:22
zigoJust a consequence ...19:22
*** dboik has joined #openstack-meeting-alt19:22
annegent_zigo: but if automation needs to become a goal we'd revise, so this exercise is about us agreeing on the goals19:22
Sam-I-Amconfigure prereqs, install and configure openstack services in a specific order, run openstack commands to populate services, etc.19:23
annegent_In the early days, say 2 years ago, I always wanted an Install Guide that was one-up from DevStack.19:23
zigo"As an OpenStack user, I want to know how to install OpenStack on multiple machines"19:23
*** sarob has joined #openstack-meeting-alt19:23
annegent_Closer to production than not. However as more complexity has gone into OpenStack, documenting production installs were not really possible.19:23
Sam-I-Amplus the variations on 'production'19:24
annegent_was? anyway, grammar is hard :)19:24
Sam-I-Amlike... do we include HA? how many of each service to we run? etc.19:24
annegent_is it one up from devstack just due to the mulit-node-ness?19:24
Sam-I-Ammost peoples eyes would roll back before they even got to the openstack services19:24
Sam-I-Amyou'd always use multi-node in production19:25
annegent_If the only goal is multi-node install then yes, HA comes into question. H.19:25
annegent_er, I mean Hm.19:25
sgordondoes it tho19:25
zigoI don't think HA is in the scope of the install-guide, unless we contain it to a specific chapter.19:25
Sam-I-Amso it gives people an idea of how the services generally fit on different servers19:25
AJaeger_Agreed, this is not a production ready setup - otherwise we would need to cover HA and scalability concerns19:25
sgordonbecause at that point19:25
sgordonyou end up talking more about pacemaker or whatever19:25
sgordonthan openstack19:25
*** cp16net has joined #openstack-meeting-alt19:25
annegent_"As an OpenStack aficionado, I want to install OpenStack services of interest to me to poke at so I can figure out what all the fuss is about."19:25
*** tonytan4ever has joined #openstack-meeting-alt19:26
zigoI don't know what you call "production", but for many users, it doesn't mean huge deployment with HA and 100s of machines.19:26
annegent_Ok, so we're somewhere between "not really production" and "not devstack" -- I think that's fair.19:26
Sam-I-Ami think one of the main goals is lowering the barrier to entry and giving people a usable system from which they can add more complexity later to support scalability, performance, security, etc.19:26
zigoMany users have only a few compute nodes without HA, and are very happy with it.19:26
zigoWe need to have an answer for them too.19:26
annegent_I think most companies are doing a better job at lowering the barrier to entry than we ever can do :)19:26
zigoFor such a complex setup, I don't think you'd be doing things by hand anyway.19:26
Sam-I-Amthe minimal # of things to do that ends up with a system that doesn't run in screen or disappear when you reboot (devstack)19:26
AJaeger_annegent_: Agreed.19:27
annegent_I think a goal is also "I need to install the open source cloud on open source platforms."19:27
AJaeger_(but I'm biased ;)19:27
Sam-I-Amfrankly only jenkins should use devstack19:27
annegent_so I actually don't think it's about lowering barrier, I think it's about describing complexity.19:27
*** sarob has quit IRC19:27
annegent_which may mean putting up barriers in some cases19:27
*** tzn has quit IRC19:28
zigoIf we're about to describe HA setups, would you guys think it's ok to have it only in a single chapter?19:28
annegent_Okay, so the goal for the Install Guide is "Readers should have a working OpenStack on minimal hardware using open source tooling."19:28
annegent_zigo: we have a whole HA guide for that19:28
zigoannegent_: Ok, so we shouldn't talk about HA at all in the install-guide no?19:29
annegent_readers goals: understand complexity, understand OpenStack options, have a working install when they're done?19:29
Sam-I-Amannegent_: also the case of 'i have an existing system and i want to try adding a new service to it, whats the minimal way to try it out?"19:29
Sam-I-Amhence the topic-based install guide19:29
annegent_zigo: we don't now, but we also could do a better job at pointers to other guides, I think19:29
AJaeger_zigo, HA has it's only guide. I would rather enhance the HA guide so that it builds on top of what the Install Guide does...19:29
*** matrohon has joined #openstack-meeting-alt19:30
zigoI'm all for pointers! :)19:30
*** sbalukoff has joined #openstack-meeting-alt19:30
annegent_zigo: yeah I like pointers, it makes people less angry when the install guide doesn't do what _they_ think it should19:30
annegent_I feel pretty comfortable defending and documenting those goals19:30
annegent_I'll take an action to write that down in our wiki pages19:30
annegent_as long as we're agreed19:30
annegent_and we're okay with "minimal hardware" -- hm.19:31
Sam-I-Amthats the barrier to entry thing19:31
Sam-I-Amthere's even people who dont have three nodes19:31
Sam-I-Amor three VMs...19:31
annegent_I can write use cases up, yep, it's up to us to define minimal.19:32
annegent_I'm comfortable with 2 nodes minimal19:32
annegent_not one node, I prefer to leave that to devstack19:32
Sam-I-Ami've thrown around the idea of offering an all-in-one version of the install guide architecture19:32
annegent_but can be dissuaded19:32
Sam-I-Amlots of people understandably get fed up with devstack19:32
zigoThe biggest work for an all-in-one guide would be in Neutron, I believe.19:33
annegent_Lots of people use devstack for production. Can't be helped apparently.19:33
zigoOtherwise, there's not much change.19:33
Sam-I-Amits not bad to document, however... the issue comes with troubleshooting.19:33
annegent_Oh, and one more bit of history19:33
annegent_#link https://etherpad.openstack.org/p/installation-guide-audit19:33
*** vishwanathj has quit IRC19:33
Sam-I-Amtrying to trace networking problems on a single node is a pain19:33
annegent_that was from prior to that blueprint19:33
annegent_I don't see much about goals in it though.19:33
Sam-I-Amalso trying to get a mental image of how it all sticks together19:33
Sam-I-Amthis is why i tend to downplay all-in-ones19:33
*** MarkAtwood has joined #openstack-meeting-alt19:34
annegent_yeah to me, single node doesn't meet the goal of "understand complexity"19:34
Sam-I-Amsure, they use less hardware, but they make things overly complex19:34
Sam-I-Amand you'd never have an AIO in production19:34
zigoSam-I-Am: I agree.19:34
annegent_yeah19:34
Sam-I-Amso the config doesn't really apply19:34
Sam-I-Amyou can easily grow the two-node/three-node arch19:34
annegent_so let's make sure we've got the right audience in mind also19:34
sgordonSam-I-Am, for all in one would we be better off giving people pointers to throwing it up in VMs on a single machine...19:34
Sam-I-Ammuch of it is just config duplication with new IPs19:34
annegent_"poking at OpenStack" or "OpenStack planner"?19:34
sgordonSam-I-Am, thus allowing us to use same path for rest of instructions19:34
Sam-I-Amsgordon: we mention using VMs and i think a lot of people choose that route19:35
sgordonright19:35
Sam-I-Amthere's some caveats though19:35
annegent_we pretty much think the audience doesn't have a lot of spare hardware laying around?19:35
annegent_nor are they likely to do a manual install in any permanent system, right?19:35
AJaeger_And the scripts of the training team set up the Install Guide architecture.19:35
AJaeger_So, if you want to have an automatic setup, just uses their scripts!19:35
AJaeger_(all in three VMs)19:36
Sam-I-Amannegent_: people do manual installs on actual hardware19:36
sgordonannegent_, i think our audience depends!19:36
zigoannegent_: It's quite easy to get a single machine running multiple VMs to just try OpenStack.19:36
annegent_okay19:36
annegent_so our audience, more likely to do VMs or find hardware?19:36
AJaeger_zigo: agreed, I'll do it on my laptop ;)19:36
AJaeger_annegent_: yeah19:36
Sam-I-Amannegent_: depends on their goals19:36
annegent_Sam-I-Am: go on19:36
annegent_Sam-I-Am: goes into task analysis, which I also want to hear more about19:37
sgordoni really think the answer is both19:37
Sam-I-Amannegent_: you can't do a lot of realistic testing with VMs due to performance issues19:37
sgordoni dont think we could pigeon hole whether they will do VMs or find hardware19:37
annegent_task: proof of concept for work vs. task: home lab prior to work (Thinking of the BMW guy)19:37
*** jemangs_ has quit IRC19:37
*** shwetaap has quit IRC19:37
Sam-I-Ami've been working with someone the last few weeks who is using the install guide arch as a minimal way to test single-network-node performance19:38
annegent_task: install many times to learn enough to automate (that's the task I hear at user groups where I ask about the install guide)19:38
annegent_task: install with different configs for compare/contrast?19:38
*** avozza is now known as zz_avozza19:38
annegent_^^ wow is that really one of their tasks, ouch19:38
Sam-I-Amlots of novanet-vs-neutron goes on19:38
*** jemangs has joined #openstack-meeting-alt19:38
annegent_I say ouch because that makes my fingers and wrists ache19:38
Sam-I-Amand soon there will be dvr-vs-l3ha19:38
*** sergef has joined #openstack-meeting-alt19:39
Sam-I-Amthe networking guide builds minimal dvr and l3ha architectures off the install guide neutron architecture19:39
annegent_zigo: I know you had some tasks, one was "task: set up a small private cloud" I believe19:39
zigoYeah.19:39
annegent_zigo: multi node, right?19:39
zigoI had some feedback from users using the install-guide for that.19:39
zigoYup.19:39
annegent_okay19:40
annegent_any other tasks?19:40
*** gholler__ has joined #openstack-meeting-alt19:40
Sam-I-Amannegent_: did you cover the "i want to try swift" case?19:40
Sam-I-Amor $optionalservice19:40
annegent_oh yeah that too, we decided 3 nodes was okay for swift, right?19:40
annegent_task: set up storage-only cloud19:40
Sam-I-Amsometimes people build a minimal install, then add $optionalservice to try it out19:40
zigoSingle controler that also does networking, multiple compute, and often a small Ceph cluster.19:41
zigoI by the way would think it'd be great to cover Ceph in the install-guide.19:41
Sam-I-Amswift was a bad choice there. lets say cinder :)19:41
annegent_task: add on a service to an existing OpenStack cloud19:41
annegent_zigo: I want to document only upstream OpenStack please :)19:41
AJaeger_I would not add ceph setup to the guide19:41
annegent_zigo: and not get into governance/politics19:41
*** achanda has quit IRC19:41
sgordonwhere is the fun in that19:42
zigoCeph is often prefered to swift for small clouds, so that it does both object storage & volume in a distributed way.19:42
*** diemt has joined #openstack-meeting-alt19:42
annegent_sgordon: hee19:42
annegent_zigo: sure, but why would I use sparse resources for a non-OpenStack project?19:42
Sam-I-Ampretty sure the audience doesn't need more complexity19:42
*** mestery is now known as mestery_afk19:42
AJaeger_Looking at the November OpenStack users survey, the majority of installations uses ceph - so integration of an existing ceph cluster is something we probably should document somewhere19:42
sgordonmy take is that if someone wants to write a module for X19:42
sgordonwould we reject it19:42
*** achanda has joined #openstack-meeting-alt19:42
zigoannegent_: Because it's what people use in real deployments.19:42
Sam-I-Amceph feels like an HA thing?19:42
sgordonnot really19:42
annegent_I worry about maintenance ongoing19:42
sgordonany more than swift is19:43
AJaeger_This is something that belongs in one of the other guides19:43
annegent_ceph implements the swift api I think19:43
annegent_yeah I want more narrow definition for install guide19:43
Sam-I-Amwell, for another meeting :)19:43
annegent_heck we barely get to newly incubated now19:43
annegent_newly integrated I mean19:43
annegent_ok is that all the tasks?19:43
*** gholler has joined #openstack-meeting-alt19:43
AJaeger_We document the OpenStack setup in the Install Guide. And any other hardware or software enhancements will be documented elsewhere19:43
*** sarob has joined #openstack-meeting-alt19:43
*** sarob has quit IRC19:44
*** dboik has quit IRC19:44
zigoannegent_: It does, and soon we'll be able to use only swift-proxy with everything else on Ceph.19:44
Sam-I-Amannegent_: "where do i go from here" probably covers HA, ceph, automation, etc.19:44
annegent_pointers, yep.19:44
zigo(currently, there's only a ceph back-end for the object filesystem storage, so it's not great...)19:44
Sam-I-Amsecurity...19:44
*** dboik has joined #openstack-meeting-alt19:44
*** gholler_ has quit IRC19:44
annegent_scope: chosen audiences and tasks19:44
Sam-I-Amwe can include things like that at the end of the install guide "hey your VM works... now you can install $optionalservices and if you're ready to join the big leagues, check these docs"19:45
annegent_scope: only integrated OpenStack projects19:45
Sam-I-Amannegent_: i hear there is an openstack-ansible thing :)19:45
annegent_scope: open source tooling19:45
annegent_scope: enable translation19:45
annegent_I think all those scopes are agreed to?19:45
AJaeger_such a generic chapter "Next steps" would be a welcome addition. But let's make it short and abstract19:45
*** gholler__ has quit IRC19:45
annegent_oh one more scope:19:45
Sam-I-AmAJaeger_: we have the structure already.19:45
Sam-I-AmAJaeger_: it was one of the icehouse neutron reorg topics19:46
annegent_who are the maintainers as we go towards more and more added services? the project teams or distro teams or upstream team?19:46
*** adrian_otto has quit IRC19:46
*** dboik has quit IRC19:46
*** achanda has quit IRC19:46
annegent_and then really we can dive into solutions, I think we've laid out a lot of the considerations to keep in mind19:46
Sam-I-Amannegent_: i dont mind adding content to the install guide, but i would like a source of "here are the minimal requirements, here is a minimal tested working config, maybe some diagrams"19:46
annegent_(hopefully 15 mins is enough to work on solutions)19:47
*** armax has quit IRC19:47
Sam-I-Amthose of us that maintain the install guide generally know how services need to fit in19:47
annegent_so upstream docs is the maintainer? Or is it a chapter maintainer per service?19:48
AJaeger_Sam-I-Am: Next steps currently points to the next chapter. I was thinking of a total new chapter - but then let's call it differently. But that's another discussion, not for now19:48
sgordoni think it depends19:48
Sam-I-Amannegent_: we'd lose consistency with chapter maintainers19:48
Sam-I-Amthis has happened before19:48
sgordontrove is an example where it seems there is a dedicated resource19:48
sgordonbut i think most people contribute across the guide19:48
sgordonnot to a single section19:48
Sam-I-Ami dont necessarily need to write the content, but i definitely want to be involved before it gets merged19:49
annegent_sgordon: yeah there's definitely not a "glance maintainer" for example19:49
annegent_there's a "nova neutron glance keystone" set19:49
annegent_and a "swift" set19:49
annegent_and a "added on services" set that may be more easily distributed19:49
sgordonwe might see more of the trove-style approach as more *aaS are added19:49
*** yapeng has quit IRC19:49
Sam-I-Amif we had project docs liasons, they would get poked at prior to release saying "did anything change that affects the install guide? here's what we do now"19:49
zigoDo we really have to establish this kind of rules? Sometimes, chaos works out well ... :P19:49
sgordonbut not sure it applies now19:49
annegent_zigo: heh. yeah I hear that a lot, and will have to get more towards chaos this release, completely understand that19:50
Sam-I-Amzigo: any way to reduce the chaos that is openstack is a good idea.19:50
annegent_but for now I'm holding the line for install / config19:50
annegent_since those are release deliverables19:50
Sam-I-Ampeople have one goal: launch a VM19:50
*** armax has joined #openstack-meeting-alt19:51
annegent_When I play out the distributed teams route, I nearly always figure we'd have to give up conditional per-distro output.19:51
Sam-I-Amand we get them there in a step-by-step process so it isn't all magic19:51
*** Haiying has quit IRC19:51
annegent_and I'm not ready to give that up yet19:51
*** mwagner_lap has joined #openstack-meeting-alt19:51
annegent_cept for those who just want to store something19:51
annegent_and ping the vm19:52
Sam-I-Amannegent_: given persistent packaging issues, i'd like to install just openstack from source, but rely on the distro for dependencies (read: rpc)19:52
Sam-I-Amthen we can pretty much be distro-agnostic as long as you meet the dependency requirements19:52
annegent_Sam-I-Am: for ease of documenting as a goal?19:52
annegent_dependency-management are the value add from a distro right?19:53
Sam-I-Amthe conditionals and testing all these distros is a lot of overhead... and we also don't see packages until after release.19:53
*** Haiying has joined #openstack-meeting-alt19:53
AJaeger_annegent_: and also integration into the distribution, for example start/stop scripts19:53
Sam-I-AmAJaeger_: thats one caveat, but we have things to write those.19:53
annegent_real basic question, do distros need their OpenStack Install docs on docs.openstack.org?19:53
*** TrevorV_ has joined #openstack-meeting-alt19:54
*** sunnyr has quit IRC19:54
AJaeger_It's also distros versus products.19:54
*** Longgeek has quit IRC19:54
zigoannegent_: It's not at least for Ubuntu, as I'm doing all of their work in this regard! :)19:54
zigo(I mean, they did zero dependency packaging for Juno...)19:54
AJaeger_For our OpenStack product - SUSE Cloud - we have the documentation including Crowbar for setup at the SUSE pages. I think Red Hat does it similar...19:54
annegent_not their value add? Heh. We document for them too. All take no give?19:54
sgordonannegent_, well i think we put them there for manual install instructions19:55
sgordonif it wasnt using the packaged install there we would focus on RDO site19:55
sgordon(same as we do for automation w/ packstack)19:55
*** sunnyr has joined #openstack-meeting-alt19:55
Sam-I-Amsome other distros have their own install guides, but often wrapped around products (read: automation)... sometimes pay products.19:55
zigoI do believe it's important for me to have docs in the official OpenStack site.19:55
annegent_so Sam-I-Am if there was this non-packaged way to install, what becomes the doc dependency for maintenance? Ansible scripts?19:56
sgordoni would hope not19:56
Sam-I-Ami also hear that the distro-specific docs dont always go to the level of detail we do with explaining stuff. explaining stuff is a BIG part of the install guide.19:56
annegent_zigo: okay, seems that way for debian and ubuntu (I dont' know of Canonical docs site ?)19:56
zigoThere's no "products" or "vendor" in my case, so we do rely on community, and nobody will do a specific Debian install-guide.19:56
*** tonytan4ever has quit IRC19:56
*** hareeshpc has quit IRC19:56
annegent_sgordon: you would hope not, referring to?19:57
zigoSam-I-Am: Yeah, that's the point. The install-guide really goes into details which is good.19:57
sgordonannegent_, your comment wrt ansible19:57
*** jamiem has joined #openstack-meeting-alt19:57
Sam-I-Amannegent_: yeah, ansible scripts.19:57
*** hareeshpc has joined #openstack-meeting-alt19:57
sgordonit would seem weird to go to all this effort to keep specific automation tools out of the guide19:57
sgordonthen annoint one19:57
*** hareeshpc has quit IRC19:57
Sam-I-Amannegent_: we have a good source of those, though.19:57
annegent_sgordon: ok, yeah want to uncover what we would be dependent upon working (and what we would have to troubleshoot)19:57
*** sunnyr has left #openstack-meeting-alt19:57
AJaeger_annegent_: Do we have to finish soon or can we stay longer in the room?19:57
annegent_AJaeger_: ah, time got away19:57
*** armax has quit IRC19:57
annegent_Looking19:57
annegent_yeah Octavia's in here next19:58
*** johnsom has joined #openstack-meeting-alt19:58
annegent_Ok, let's make sure we know what we can do next.19:58
Sam-I-Amcan we beat them up?19:58
annegent_I want to document our goals19:58
rm_workSam-I-Am: T_T19:58
annegent_state the audience19:58
sbalukoff...19:58
Sam-I-Amlol19:58
annegent_state the tasks19:58
annegent_on the mailing list and wiki19:58
annegent_I'd also like to hear from training team19:58
Sam-I-Amwe didnt get to solutions, so maybe another meeting?19:59
*** mwang2 has joined #openstack-meeting-alt19:59
annegent_and I'll add it to the doc team agenda for next week, which is 1400 UTC (right?) Wed.19:59
*** xgerman has joined #openstack-meeting-alt19:59
*** jwarendt has joined #openstack-meeting-alt19:59
Sam-I-Amyep19:59
annegent_"it" being "solution discussion for Install Guide"19:59
annegent_does that work?19:59
Sam-I-Amsure. might consume the entire hour :P19:59
*** rohara has joined #openstack-meeting-alt19:59
annegent_there's only four to choose from :)20:00
*** tonytan4ever has joined #openstack-meeting-alt20:00
*** Haiying has quit IRC20:00
annegent_Okay, handing it over, thanks for making it work all.20:00
annegent_#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Wed Dec  3 20:00:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-12-03-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-12-03-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-12-03-19.02.log.html20:00
sbalukoff#startmeeting Octavia20:00
openstackMeeting started Wed Dec  3 20:00:29 2014 UTC and is due to finish in 60 minutes.  The chair is sbalukoff. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
xgermano/20:00
*** openstack changes topic to " (Meeting topic: Octavia)"20:00
sbalukoff#topic Roll Call20:00
TrevorV_o/20:00
openstackThe meeting name has been set to 'octavia'20:00
rm_worko/20:00
*** openstack changes topic to "Roll Call (Meeting topic: Octavia)"20:00
roharao/20:00
johnsomo/20:00
bloganhi20:00
xgermano/20:00
ajmillero/20:00
*** Sam-I-Am has left #openstack-meeting-alt20:00
sbalukoffHowdy folks!20:00
blogan\o/20:00
rm_workWell hello there!20:00
*** dboik has joined #openstack-meeting-alt20:01
jwarendtHi20:01
sbalukoffThis is our agenda for today: https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda#Agenda20:01
sbalukoff#topic Quick "Octavia" trademark update20:01
*** openstack changes topic to "Quick "Octavia" trademark update (Meeting topic: Octavia)"20:01
sbalukoff#link: http://tsdr.uspto.gov/#caseNumber=86319369&caseType=SERIAL_NO&searchType=statusSearch20:02
xgermanso we now can oppose :-)20:02
jamiemo/20:02
sbalukoffSo that came in yesterday. Apparently it's now published on the USPTO's publications that they intend to grant the trademark.20:02
bloganawesome20:02
xgerman+120:02
rm_workOctavia is one of the stylist's names in The Hunger Games :P20:03
sbalukoffAnd anyone who objects has 11 weeks to register their objection (and explain why granting the trademark would damage them.20:03
rm_worknoticed that this weekendf20:03
bloganim objecting20:03
xgermanme, too20:03
sbalukoffAfter 11 weeks, if there aren't objections (or sufficiently justified objections), the trademark gets granted.20:03
rm_workcool, so, by Kilo right? :)20:03
sbalukoffBasically, yes.20:03
sbalukoffAgain, assuming nobody goes through the legal paperwork / filing fees to seriously object.20:04
*** AJaeger_ has left #openstack-meeting-alt20:04
sbalukoffSo, anyway, I just wanted to keep you updated on the latest developments there.20:04
sbalukoff#topic Octavia hack-a-thon in December20:04
*** openstack changes topic to "Octavia hack-a-thon in December (Meeting topic: Octavia)"20:04
*** dboik has quit IRC20:04
*** dprince has quit IRC20:04
xgermanthis will be epic20:04
sbalukoff#link https://etherpad.openstack.org/p/octavia-kilo-meetup20:04
sbalukoffYes, I hope so!20:05
*** dboik has joined #openstack-meeting-alt20:05
sbalukoffI hope it's a really productive week for all of us, eh!20:05
rm_worksuch whiteboarding20:05
rm_workso collaboration20:05
rm_workwow20:05
*** barclaac has joined #openstack-meeting-alt20:05
sbalukoffHaha20:05
sbalukoffAs a reminder, please RSVP if you intend on coming so that HP can accommodate all of us.20:05
*** e0ne has quit IRC20:05
TrevorV_I'll go if HP pays for my room/board/travel :P20:05
sbalukoffAlso, as a reminder, if there are additional specific topics you'd like to see a whiteboarding / design session on, please list them at the end of that document.20:05
roharaRSVP is just putting name on the etherpad?20:06
barclaacCorrect20:06
xgermanyep20:06
sbalukoffrohara: Yes.20:06
roharaack20:06
*** SridharRamaswamy has quit IRC20:06
blogani know we can mix neutron lbaas and octavia subjects, but the agenda has a discussion point being about lbaas object sharing20:06
sbalukoffSo that's about 2 weeks away. I'm thinking there's time in the mean time to get some of the discussions underway on the mailing list or what have you so we can hit the ground running at the hack-a-thon20:07
bloganisn't that neutron lbaas?20:07
bloganor are we looking to do something similar in octavia as well?20:07
sbalukoffblogan: It is, but it does affect Octavia of course.20:07
*** dboik has quit IRC20:07
sbalukoffAs long as Octavia is using Neutron LBaaS as its user API front-end (ie. indefinitely, per the current plan), discussions of how that interface works do affect us.20:08
*** dboik has joined #openstack-meeting-alt20:08
sbalukoffNot to mention the fact that both groups share about 90% of the same people. :)20:08
bloganwell that is somethign we will discuss there as well20:08
*** esker has quit IRC20:08
sbalukoffSo, I think it's a good idea to actually have a mailing list discussion about status information, since that directly impacts the object model sharing, which directly impacts how the API works for the user.20:08
*** AndChat|58025 has joined #openstack-meeting-alt20:08
sbalukoffI can get that started if y'all like.20:09
bloganactually20:09
sbalukoffUnless y'all think it would be a bad idea to get that going now.20:09
*** nshaikh has left #openstack-meeting-alt20:09
xgermanI think it doesn't matter to the user where status is tored20:09
*** barclaac has quit IRC20:09
*** jorgem has joined #openstack-meeting-alt20:09
xgermanstored20:09
bloganwe can discuss on this bp20:09
bloganhttps://review.openstack.org/#/c/138205/20:09
*** annegent_ has quit IRC20:09
blogannothing about sharing there, but its the repoposed lbaas v2 spec for kilo20:09
sbalukoffblogan: Ok, sounds good.20:10
xgerman+120:10
jorgemsbalukoff: can you send the agenda link again? sorry just joined. I just want to add some items20:10
sbalukoffxgerman: It's not about where or how status is stored, it's about how it's represented to the user.20:10
bloganand i did make some changes, but if we wanted to do sharing like sam suggested, we would need to make that decision sooner rather than later20:10
sbalukoffjorgem: https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda#Agenda20:10
sbalukoffblogan: Sounds good.20:11
xgermansam explicitly talked about storing...20:11
sbalukoff#action everyone participate in LBaaSv2 object model discussion here: https://review.openstack.org/#/c/138205/20:11
sbalukoffxgerman: I don't think he understood what I was getting at either.20:11
sbalukoff(And that may be because I wasn't clear in what I was saying.)20:12
xgerman+120:12
sbalukoffAnyway, are there any other discussions we should "prime" prior to the hack-a-thon?20:12
sbalukoffMostly, I want to make sure the face-to-face time we have is used as effectively as possible.20:12
sbalukoffAnd it can be useful to test the waters a bit, as it were, before having a face-to-face discussion.20:13
bloganthe controller being split up into smaller stories would be a good one20:14
sbalukoffI agree!20:14
bloganbut that is dependent on a larger conversation that will be best had at the hackathon20:14
sbalukoffI'd love to see something about the discussions y'all apparently have been having at rackspace20:14
bloganbut we can start the controller monolithic story up in the ML20:14
blogandiscussions on how to overthrow you?20:14
*** kebray has quit IRC20:14
sbalukoffblogan: Do you have time to get that going?20:14
johnsomThe initial direction for the controller is up for WIP review.....20:15
sbalukoff(both of those? )20:15
sbalukoff;)20:15
*** markmcclain has quit IRC20:15
TrevorV_johnsom, link here please?20:15
sbalukoffOk, so let's have the discussion in gerrit then?20:15
bloganyeah we will try to get somethign out by the end of the week on teh ML20:15
sbalukoffblogan: Thanks20:15
bloganwell gerrit and resort to ML if it requires a huge writeup20:15
johnsom#link https://review.openstack.org/13654020:15
*** jmontemayor_ has joined #openstack-meeting-alt20:15
sbalukoff#action Rackspace team to get something out on the mailing list about whiteboard discussions they've been having / monolithic controller discussion20:15
johnsomPosted back on the 22nd20:16
*** tzn has joined #openstack-meeting-alt20:16
sballehey20:16
*** jmontemayor has quit IRC20:16
sbalukoffjohnsom: I'll take a look today or tomorrow. Thanks for posting that!20:16
TrevorV_yeah thanks johnsom20:16
sbalukoffOk...  moving on.20:16
sbalukoff#topic Progress reports20:17
*** openstack changes topic to "Progress reports (Meeting topic: Octavia)"20:17
*** Sukhdev has joined #openstack-meeting-alt20:17
rm_workyeah looks kinda similar to what we were talking about here, though our discussions have been more about HOW the communications happen20:17
rm_workmore than "what are the communication lines"20:17
*** kebray has joined #openstack-meeting-alt20:17
sbalukoffoperator-api:  Update from blogan / TrevorV?20:17
*** KLevenstein has left #openstack-meeting-alt20:17
TrevorV_I've added the controller spec to the prioritized reviews page for johnsom20:17
sbalukoffNice!20:18
bloganwell i can respond to your comment20:18
bloganright now20:18
bloganin taht decimal versions don't make sense20:18
sbalukoffUh-oh.20:18
sbalukoffWhy is that?20:18
johnsomIt was already on there....20:18
johnsomThe line above your new one...  Grin20:18
blogani know, thats something we'll need to fix20:18
sbalukoffOther APIs using versioning in OpenStack are using decimals.20:18
TrevorV_Lulz20:18
TrevorV_I'm observant, can you tell?20:19
bloganbut they never use the minor version, at least as far as i can tell20:19
*** _nadya_ has joined #openstack-meeting-alt20:19
sbalukoffxgerman: What are your thoughts on this?20:19
sballeI think we should do the decimal versions.20:19
xgerman+120:19
TrevorV_Oh good, you guys are talking about some stuff I was going to bring up ha ha20:20
sbalukoffsballe: Why?20:20
sballeIt makes the versioning consistent across the various services.20:20
sbalukoffI don't want to rat-hole on this too far... but if it's something we can resolve quickly, let's do so.20:20
*** crc32 has joined #openstack-meeting-alt20:20
sballeI am looking ofr a specific example20:20
xgermanwe had some discussion where we said we will only increase majore version in the API20:20
bloganneutron doesnt have a decimal20:20
sbalukoffIf we can't resolve this quickly, lets do it in comments on the gerrit review.20:20
xgermanneutron has LBaaS v1 in Beutron V220:20
sbalukoffblogan: I thought v2.0 would?20:21
rm_workI thought other services were moving away from decimals, but maybe not now, since nova stopped work on v3 and went to v2.120:21
rm_work>_>\20:21
*** ChuckC has quit IRC20:21
bloganok this will be a rathole20:21
sbalukoffHeh!20:21
bloganlol20:22
bloganlets do gerrit20:22
xgermanyeah, abandoning decimals seems premature20:22
sbalukoffOk, let's do it in gerrit.20:22
rm_workOH20:22
sballexgerman +120:22
rm_worki remembered why i didn't like decimals20:22
bloganplus i have to restart my brain to remember the good reasons i had20:22
xgermanrm_work do you like math in general?20:22
* TrevorV_ likes math20:22
rm_workbecause anything inside a major version should be backwards compatible, and we can SHOW the decimal versions, but it should never be part of a URL20:23
rm_workxgerman: i hate math in general :P20:23
sbalukoff#action Interested parties should have discussion over whether to have decimal version numbers for the api on the gerrit review for the same.20:23
*** padkrish has quit IRC20:23
rm_workso our URL should always be whatever.com/lbaas/v2/loadbalancer/12432545620:23
sbalukoffrm_work: Take it to gerrit, please20:23
rm_workbut our version could come back in the header as v2.1.3420:23
sbalukoffOk!20:23
TrevorV_sbalukoff, real quick, should that be on the documentation review or the actual operator API review?20:23
rm_worklol fine20:23
rm_worksbalukoff: spoilsport >_<20:23
sbalukoffTrevorV_: Aah, good question. I think the discussion is already happening on the Operator API review20:24
bloganyes do it on that review20:24
*** ihrachyshka has joined #openstack-meeting-alt20:24
TrevorV_Alright20:24
blogani should have responded with the reasons we came up with in IRC, but i am a jack ass20:24
sbalukoffThis one: https://review.openstack.org/#/c/121233/20:24
* TrevorV_ does not dispute20:24
sbalukoffHaha!20:24
*** dprince has joined #openstack-meeting-alt20:24
TrevorV_#link https://review.openstack.org/#/c/121233/20:25
sbalukoffOk, progress report on the amphora-api:20:25
*** padkrish has joined #openstack-meeting-alt20:25
sbalukoffI need some more eyes on the review: https://review.openstack.org/#/c/126801/20:25
sbalukoffAlso, I need rm_work to respond to my response to him. ;)20:26
rm_workack20:26
sbalukoffIt's been a hectic week, and I have not had heard back from davidlenwell about code progress there yet (he's remote, and text is our primary means of communication)20:26
sbalukoffSo... not much progress there.20:26
sballecould somebody remind me where the etherpad with all the reviews is?20:26
TrevorV_#link https://review.openstack.org/#/c/126801/20:27
*** ycombinator_ has joined #openstack-meeting-alt20:27
sbalukoffsballe: It's not been updated in a while20:27
sbalukoffI typically work off this: https://review.openstack.org/#/q/stackforge/octavia+status:open,n,z20:27
TrevorV_sbalukoff, I update it often20:27
*** tdruiva has quit IRC20:27
TrevorV_Just not sure on priority for reviews mostly20:27
blogani work off that too sbalukoff20:27
sbalukoffOh? Ok.20:27
johnsom#link https://etherpad.openstack.org/p/octavia-pending-reviews20:27
*** tdruiva has joined #openstack-meeting-alt20:28
sbalukoffjohnsom: Can you give us an update on the amphora base image creation scripts?20:28
johnsomYes, we need reviews!20:28
sbalukoffThat's probably going to be a theme here.20:28
johnsomI'm not a fan of adding versions to sub-components like the build script.20:28
TrevorV_sbalukoff, trending eh?20:29
sbalukoff#action We need people to do reviews. No seriously, we do.20:29
johnsomI also added a comment about the haproxy.conf template place holder in the notes.20:29
bloganpeople still recovering from thanksgiving20:29
*** markmcclain has joined #openstack-meeting-alt20:29
johnsomOther than that.  Nothing more to report.  Just needs reviews and +2s20:29
sbalukoffblogan: Agreed.20:29
sbalukoffjohnsom: Sounds good. Thanks!20:29
*** hareeshpc has joined #openstack-meeting-alt20:29
rm_workyeah, recovering from Thanksgiving and Yosemite20:30
sbalukoffOk, update on compute driver interface.  amiller and TrevorV?20:30
rm_workstupid Yosemite...20:30
TrevorV_Oh crap20:30
bloganlet me guess : reviews20:30
sbalukoffblogan +120:31
ajmilleras far as I am aware, by review is done and merged.20:31
TrevorV_Yeah, in this case though I also have some questions to have answered20:31
TrevorV_ajmiller, is correct20:31
xgermanhe always is :-)20:31
ajmillerI wish20:31
sbalukoffTrevorV_: Are they brief, or should we answer them elsewhere?20:31
TrevorV_sbalukoff, I responded in the review with my concerns for the management_network20:31
TrevorV_I feel they aren't brief ha ha20:31
sbalukoffYeah, that's definitely not a brief discussion.20:32
TrevorV_(They may turn out to be, but the unknown is best to assume the worst)20:32
bloganoh yeah i need more explanation on that one sbalukoff20:32
xgermanI am wondering if we can sidestep it for the sake of having that merged20:32
sbalukoffOk, I think in order to have that discussion, we need a better understanding of topologies.20:32
bloganive been assuming its only the network used for controller and amphorae communication20:32
*** obondarev_ has joined #openstack-meeting-alt20:32
sbalukoffWhich may not happen before the hack-a-thon20:32
TrevorV_blogan, sbalukoff, xgerman we can talk more during open discussion after the main topics are covered20:32
sbalukoffI would like to see the spec merged with the idea that it can always be modified based on later discussion.20:33
xgermank, sound sgood20:33
bloganfine by me20:33
*** padkrish has quit IRC20:33
sbalukoffNothing we do here is immutable, eh!20:33
TrevorV_+1 sbalukoff I have no problems with that thought process either20:33
blogansbalukoff: i hope everyone understands thats the case with every spec20:33
sbalukoffblogan: Me too!20:33
*** padkrish has joined #openstack-meeting-alt20:33
sbalukoffAgain, I'd rather not block the ability to get useful work done in the mean time as we figure out some of the larger issues.20:33
xgerman+120:34
sbalukoffAnd to me that means it should be OK to merge specs that leave some things as "To be determined"20:34
TrevorV_Least amount of ambiguity as the focus, eh?20:34
sballesbalukoff: +120:34
bloganthe spec not beign merged doesn't prevent anyone from working on the implementation, and the spec being merged doesn't mean it won't change20:34
sbalukoffTrevorV_: Yes20:34
sbalukoffblogan: +120:34
bloganso either way it shouldnt block20:35
*** obondarev has quit IRC20:35
sbalukoffblogan: Nevertheless, I sense that there is a mental block there-- people are less likely to work earnestly on implementation when the spec isn't' merged yet.20:35
bloganoh i know, its the checklist mentality20:35
sbalukoffblogan: I agree, I'm just sharing my observation.20:35
TrevorV_sbalukoff, I was dependent on a spec, an impl, and then another spec... didn't stop me ha ha ha20:35
sbalukoffOk, the last status update I have is on the controller-- and we've already talked a little bit about that, and I think we all know this is up for a major discussion20:36
sbalukoffboth prior to and at the hack-a-thon.20:36
bloganindeed20:36
TrevorV_agreed20:36
sballesbalukoff: I have time between now and the face 2 face to work on a spec. I like to volunteer to work on https://blueprints.launchpad.net/octavia/+spec/amphorae-scheduler spec.20:36
sbalukoffAnd again, I look forward to seeing something of a summary of the whiteboard discussions y'all at Rackspace have been having about this. :)20:36
sbalukoffsballe: Go for it!20:36
*** hareeshpc has quit IRC20:36
bloganyou sound like you really want details20:37
sballeI couldn;t assign it to myslef20:37
sbalukoffOk, are there any other progress reports I'm forgetting about?20:37
blogannetwork driver spec20:37
bloganhttps://review.openstack.org/#/c/135495/20:37
*** mattgriffin has joined #openstack-meeting-alt20:37
xgermansballe I think I can assign20:37
sbalukoffsballe: Aah, ok.20:37
bloganthis is one that will definitely change as we get further along20:37
sbalukoff#action sbalukoff to assign https://blueprints.launchpad.net/octavia/+spec/amphorae-scheduler to sballe20:37
*** padkrish has quit IRC20:37
bloganbut i think it is generic enough now to suit our needs20:38
sbalukoffblogan: Agreed.20:38
sbalukoffSo.... need reviews, right?20:38
TrevorV_The more info we can hash out before the hackathon the better though, so eyes on that review would be great20:38
bloganno just 2 +2s and a +A20:38
sbalukoffTrevorV_: +120:38
sballeblogan: understood. I want to make sure we use the right technologies for the affinity/anit-affnity so I am talking to our nova guys on the best way forward,20:38
TrevorV_I also have the review for the Operator API documentation that's still really lean.  Any help there would be great20:38
sballePlease I wrote a lot of the slurm scheduler so I feel I should be at home here20:39
sbalukoffblogan: Ok, I'll have a look.20:39
TrevorV_#link https://review.openstack.org/#/c/136499/20:39
xgermansballe it's yours20:39
sballexgerman: thx20:39
blogansballe: okay, that definitely affinity and anti-affinity definitely need attention20:39
sbalukoffTrevorV_: I will happily dole out more berating comments on that if you'd like. ;)20:39
*** thangp has quit IRC20:40
TrevorV_sbalukoff, that'll be welcome for the most part :D20:40
sbalukoffSeriously, though, it's a good start. :D20:40
TrevorV_I feel like I could have more description about stuff, and if anyone does want me to do a glossary or something, please let me know, because I may not have a full definition in mind when making it20:40
sbalukoffAnd yes, to the rest of y'all:  Please do review TrevorV_'s spec!20:40
TrevorV_So I'll have questions and such there too20:40
*** e0ne has joined #openstack-meeting-alt20:40
bloganmeeting TL;DR - all review everything!20:41
* TrevorV_ working on reviewing all the things!20:41
sbalukoffTrevorV_: We should discuss this afterward, but I do want to know if you're following a specific template in that. I followed a template I pulled out of my ass for the amphora API spec.20:41
sbalukoffblogan: Indeed!20:41
sbalukoff#action review all the things!20:41
*** balajiiyer has joined #openstack-meeting-alt20:41
sbalukoffOk!20:41
TrevorV_sbalukoff, simple answer, I followed glance's API docs.  Not intimately followed, but I used it as a starting point20:41
sbalukoffOk.20:41
bloganwe really need to look at JSONHome and JsonSchema for doc generation, per the apiwg20:42
sbalukoffI would like to see a little more detail than what you've got so far. ;)20:42
*** sreshetnyak has quit IRC20:42
TrevorV_blogan, I might be able to spend some cycles on that20:42
TrevorV_sbalukoff, Agreed20:42
bloganTrevorV_: go for it pelase20:42
*** sreshetnyak has joined #openstack-meeting-alt20:42
sbalukoffblogan: +120:42
sbalukoffOk!20:42
sbalukoffjorgem: Did you have something you wanted added to the agenda, because the next thing on the list is open discussion20:43
jorgemSure20:43
jorgemJust wanted to make sure we keep in mind versioning in Octavia20:43
sbalukoff#topic jorgem's agend item(s)20:43
*** openstack changes topic to "jorgem's agend item(s) (Meeting topic: Octavia)"20:43
sbalukoff#undo20:43
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x3db0e10>20:43
jorgemNot sure how it will fit in to Neutron as well as octavia20:43
TrevorV_sbalukoff, action me for checking into JsonSchema/JSONHome20:43
sbalukoff#topic jorgem's agenda item(s)20:43
*** openstack changes topic to "jorgem's agenda item(s) (Meeting topic: Octavia)"20:43
*** ihrachyshka has quit IRC20:43
sballelol20:44
sbalukoff#action TrevorV_ to look into JSONSchema / JSONHome20:44
xgermanversioning = good20:44
jorgemIt was brought up today and I'm not sure if it warrants a discussion20:44
jorgemAPI versioning is what I'm referring to to be explicit20:44
bloganwe need to also look into what nova and neutron are donig with microversionig20:44
bloganng20:44
jorgemBut I'd like the ability to deprecate and run multiple API versions at the same time in order to transition customers20:44
xgermanblogan +120:44
sbalukoffjorgem: So the plan was to have this discussion on the operator api gerrit review, where it's already started20:44
jorgemsweet20:45
sballeand I am assuming the API group will come out with a best practice20:45
xgermanand we have the same operator requirement at HP20:45
sballewe should touch base with jay20:45
sbalukoffsballe: Sure, but let's not hold our breath there.20:45
jorgemOther things to worry about that are slightly related are migrations (up AND down)20:45
bloganwhich alembic does20:45
jorgemIt is my understanding that most Openstack projects only migrate UP and not down20:45
xgermanwell, I would be happy if UP worked flawlessly :-)20:45
sbalukoffHaha20:46
bloganwell the migrations do have the ability to mgirate down20:46
sballexgerman: +1 yeah no kidding!20:46
TrevorV_xgerman, so far alembic seems to work flawlessly (knocks on wood)20:46
jorgemjust want to make sure we keep those things in the back of our minds when having design discussions20:46
sbalukoffjorgem: It's my impression that a "down" migration only happens when there's a serious problem with a new version that isn't discovered until an upgrade is attempted.20:46
jorgemno need to go into details now20:46
jorgem:)20:46
sbalukoffBut yes, our migrations should be able to go both ways.20:46
jorgemcorrect20:46
* TrevorV_ chuckles at "go both ways"20:47
*** sergef has quit IRC20:47
sballewhen we say migration are we talking about update and rollback?20:47
jorgemyes20:47
sbalukoffjorgem: Do you want to update our HACKING.rst or constitution with those design principles. (The versioning one is already there, but we aren't explicit about DB migrations working.)20:47
sbalukoff?20:47
sbalukoffThat was a question.20:47
bloganin alembic you define upgrade() and downgrade() methods20:47
jorgemsbalukoff: sure20:47
sballeyeah if Octavia can do this it will be the only service in OpenStack taht can :-( But of course we are all workign towards OpenStack services being able to do this20:47
sbalukoffblogan: I think his point is that sometimes nobody thinks about downgrade()20:48
xgermanyep, and what do you dow ith data in the new tables?20:48
xgermanwill bite you at the next upgrade20:48
xgerman...20:48
sbalukoffEverytime your downgrade() doesn't work, god kills a kitten.20:48
jorgemfor example FK contraints usually cause issues20:48
sballesbalukoff: HP does. The issue is that the tools we use such as Heat to deploy aren't mature enought to do a rollback.20:48
blogani have yet to see a migration that downgrade wasn't complete, however it is possible that it just couldn't be run due to other restrictions20:48
jorgemmigrations are with code as well though20:48
jorgemnot just DB albeit the DB is the one most people take into consideration20:49
*** daneyon has quit IRC20:49
jorgemRequirement is seamleass upgrades and downgrades20:49
xgermanjorgem +100020:49
blogani think thats when the microversioning comes into play20:49
sbalukoffOh boy.20:49
jorgemsballe: We almost have that completed with our CLB product20:50
jorgemsbalukoff: *sorry20:50
sbalukoffblogan: Weren't you against microversioning APIs?20:50
sbalukoffAnyway...20:50
jorgemanyways, I'll update the HACKING.rst file20:50
jorgemsbalukoff: link?20:50
sballeWho will go and investigate microversioning and come back next week and explain it to the rest of us?20:50
sbalukoff#action jorgem to update Octavia constitution.rst or hacking.rst with principles around seamless upgrades / downgrades20:51
blogansbalukoff: against it in the url20:51
xgermanor we invite jay as a guest speaker?20:51
*** Haiying has joined #openstack-meeting-alt20:51
sbalukoffjorgem: It's in the root of the octavia repository20:51
*** vishwanathj has joined #openstack-meeting-alt20:51
jorgemk thx20:51
bloganwe definitely need to version, just not show minor/micro versions in the url20:51
sbalukoffjorgem: what you're describing is probably best in the constitution.rst file.20:51
jorgemk20:52
sballejorgem: I do agree with this requirement and it will be nice when we have it20:52
sbalukoffblogan: Ok20:52
sbalukoffOk!20:52
sbalukoffjorgem: Anything else right now?20:52
jorgemJust want to make sure we don't perform upgrades like it's 1999!20:52
sbalukoffHaha20:52
sbalukoff#topic Open Discussion20:52
*** openstack changes topic to "Open Discussion (Meeting topic: Octavia)"20:52
jorgembut I do want to party like it :)20:52
sbalukoff+120:52
sbalukoffOk, folks, we've got 7 minutes left. What else do y'all want to discuss?20:53
sbalukoffTrevorV_: Wasn't there something you wanted to yell at me about?20:53
TrevorV_no yelling20:54
TrevorV_Just the management_network thing is getting to me20:54
sbalukoffAaw!20:54
bloganjust passive aggressive insults20:54
* TrevorV_ isn't like blogan20:54
*** jmontemayor_ has quit IRC20:54
dougwigoh nuts, timezone20:54
*** gholler_ has joined #openstack-meeting-alt20:54
sbalukoffOk. So that's likely to go beyond the 6 minutes we have left-- maybe we can do this in #openstack-lbaas afterward?20:54
bloganwtg dougwig20:54
sbalukoffdougwig: D'oh!20:54
dougwigsorry20:54
TrevorV_sbalukoff, I suggested that already :P  Sounds good, talk at you there20:54
TrevorV_(or with, if you prefer ha ha)20:54
*** AndChat|58025 has quit IRC20:55
sbalukoffHeh!20:55
sbalukoffOk, folks...  if there's nothing else right now, let's end this a few minutes early.20:55
TrevorV_Alrighty, take it easy all!20:55
*** Haiying has quit IRC20:55
TrevorV_o/20:55
sbalukoffThanks y'all!20:55
sballebye20:55
sbalukoff#endmeeting20:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:55
openstackMeeting ended Wed Dec  3 20:55:58 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/octavia/2014/octavia.2014-12-03-20.00.html20:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/octavia/2014/octavia.2014-12-03-20.00.txt20:56
openstackLog:            http://eavesdrop.openstack.org/meetings/octavia/2014/octavia.2014-12-03-20.00.log.html20:56
*** johnsom has left #openstack-meeting-alt20:56
*** jwarendt has quit IRC20:56
*** esker has joined #openstack-meeting-alt20:57
*** daneyon has joined #openstack-meeting-alt20:57
*** mattgriffin has quit IRC20:57
*** jmontemayor has joined #openstack-meeting-alt20:57
*** gholler has quit IRC20:57
*** TrevorV_ has left #openstack-meeting-alt20:58
*** mattgriffin has joined #openstack-meeting-alt20:58
*** rohara has left #openstack-meeting-alt20:58
*** juzuluag has quit IRC21:01
*** ycombinator_ has quit IRC21:01
*** sarob has joined #openstack-meeting-alt21:02
*** amrith is now known as _amrith_21:02
*** esker has quit IRC21:03
*** armax has joined #openstack-meeting-alt21:03
*** jtomasek has quit IRC21:06
*** barclaac has joined #openstack-meeting-alt21:06
*** SlickNik has left #openstack-meeting-alt21:08
*** ihrachyshka has joined #openstack-meeting-alt21:09
*** virtuallynathan_ has left #openstack-meeting-alt21:11
*** igordcard has joined #openstack-meeting-alt21:11
*** _nadya_ has quit IRC21:11
*** igordcard has quit IRC21:14
*** Haiying has joined #openstack-meeting-alt21:14
*** gholler__ has joined #openstack-meeting-alt21:15
*** dboik has quit IRC21:15
*** crc32 has quit IRC21:15
*** dboik has joined #openstack-meeting-alt21:16
*** MarkAtwood has quit IRC21:16
*** gholler_ has quit IRC21:18
*** ChuckC has joined #openstack-meeting-alt21:18
*** mestery_afk is now known as mestery21:18
*** Haiying has quit IRC21:19
*** denis_makogon_ has joined #openstack-meeting-alt21:19
*** adrian_otto has joined #openstack-meeting-alt21:20
*** dave-mccowan has quit IRC21:24
*** sgordon has left #openstack-meeting-alt21:24
*** carl_baldwin has quit IRC21:24
*** jprovazn has quit IRC21:25
*** emagana_ has quit IRC21:28
*** emagana has joined #openstack-meeting-alt21:28
*** mattgrif_ has joined #openstack-meeting-alt21:29
*** mattgriffin has quit IRC21:29
*** hareeshp has joined #openstack-meeting-alt21:32
*** carl_baldwin has joined #openstack-meeting-alt21:32
*** emagana has quit IRC21:33
*** Leonr has joined #openstack-meeting-alt21:34
*** mattgrif_ has quit IRC21:35
*** balajiiyer has quit IRC21:36
*** mattgriffin has joined #openstack-meeting-alt21:36
*** baoli has joined #openstack-meeting-alt21:36
*** Guest44732 has quit IRC21:37
*** emagana has joined #openstack-meeting-alt21:37
*** jjmb has joined #openstack-meeting-alt21:38
*** ptoohill_ has joined #openstack-meeting-alt21:39
*** Leonr has quit IRC21:39
*** ptoohill_ has quit IRC21:39
*** ptoohill_ has joined #openstack-meeting-alt21:40
*** denis_makogon has quit IRC21:40
*** denis_makogon_ is now known as denis_makogon21:40
*** padkrish has joined #openstack-meeting-alt21:40
*** dmakogon_ has joined #openstack-meeting-alt21:40
*** dave-mccowan has joined #openstack-meeting-alt21:40
*** dave-mccowan_ has joined #openstack-meeting-alt21:42
*** dave-mccowan has quit IRC21:45
*** dave-mccowan_ is now known as dave-mccowan21:46
*** jgrimm is now known as zz_jgrimm21:46
*** SridharRamaswamy has joined #openstack-meeting-alt21:47
*** hareeshp has quit IRC21:48
*** padkrish has quit IRC21:48
*** padkrish has joined #openstack-meeting-alt21:49
*** dprince has quit IRC21:49
*** jjmb has quit IRC21:49
*** jjmb has joined #openstack-meeting-alt21:49
*** andreykurilin_ has joined #openstack-meeting-alt21:53
*** diemt has quit IRC21:53
*** andreykurilin__ has quit IRC21:53
*** tdruiva has quit IRC21:54
*** ycombinator_ has joined #openstack-meeting-alt21:57
*** barclaac has quit IRC21:58
*** tzn has quit IRC21:59
*** ajo has quit IRC22:00
*** esker has joined #openstack-meeting-alt22:02
*** emagana has quit IRC22:02
*** emagana has joined #openstack-meeting-alt22:03
*** edwardb has quit IRC22:05
*** jjmb has quit IRC22:05
*** padkrish has quit IRC22:06
*** mattgriffin has quit IRC22:06
*** edwardb has joined #openstack-meeting-alt22:07
*** jorgem has quit IRC22:08
*** tbarron has quit IRC22:09
*** ycombinator_ has quit IRC22:10
*** Leonr has joined #openstack-meeting-alt22:12
*** noslzzp has quit IRC22:12
*** esker has quit IRC22:13
*** padkrish has joined #openstack-meeting-alt22:13
*** padkrish has quit IRC22:13
*** padkrish has joined #openstack-meeting-alt22:14
*** baoli has quit IRC22:15
*** Leon has joined #openstack-meeting-alt22:15
*** baoli has joined #openstack-meeting-alt22:16
*** Leon is now known as Guest6504922:16
*** mattgriffin has joined #openstack-meeting-alt22:16
*** Sukhdev has quit IRC22:17
*** Leonr has quit IRC22:19
*** yamamoto has joined #openstack-meeting-alt22:19
*** armax has quit IRC22:20
*** EricGonc_ has quit IRC22:24
*** cbouch has quit IRC22:24
*** marun has quit IRC22:25
*** esker has joined #openstack-meeting-alt22:26
*** gholler_ has joined #openstack-meeting-alt22:27
*** _amrith_ is now known as amrith22:29
*** gholler has joined #openstack-meeting-alt22:29
*** EricGonczer_ has joined #openstack-meeting-alt22:29
*** noslzzp has joined #openstack-meeting-alt22:30
*** mattfarina has quit IRC22:30
*** gholler__ has quit IRC22:30
*** tdruiva has joined #openstack-meeting-alt22:31
*** esker has quit IRC22:31
*** gholler_ has quit IRC22:32
*** tonytan4ever has quit IRC22:33
*** adrian_otto has left #openstack-meeting-alt22:34
*** tdruiva has quit IRC22:35
*** ihrachyshka has quit IRC22:36
*** tzn has joined #openstack-meeting-alt22:37
*** banix has joined #openstack-meeting-alt22:37
*** rwsu has quit IRC22:37
*** AJK__ has quit IRC22:42
*** matrohon has quit IRC22:46
*** yamamoto has quit IRC22:47
*** padkrish has quit IRC22:47
*** padkrish has joined #openstack-meeting-alt22:48
*** AJK__ has joined #openstack-meeting-alt22:48
*** EricGonczer_ has quit IRC22:49
*** yamamoto has joined #openstack-meeting-alt22:50
*** denis_makogon has quit IRC22:50
*** vkmc has quit IRC22:51
*** padkrish has quit IRC22:51
*** kebray has quit IRC22:52
*** kebray has joined #openstack-meeting-alt22:53
*** banix has quit IRC22:54
*** jorgem has joined #openstack-meeting-alt22:55
*** Longgeek has joined #openstack-meeting-alt22:55
*** Barker has quit IRC22:55
*** Barker has joined #openstack-meeting-alt22:56
*** banix has joined #openstack-meeting-alt23:00
*** Longgeek has quit IRC23:00
*** sarob has quit IRC23:00
*** Barker has quit IRC23:01
*** jmontemayor has quit IRC23:01
*** dboik has quit IRC23:02
*** gholler_ has joined #openstack-meeting-alt23:04
*** gholler has quit IRC23:07
*** gholler_ has quit IRC23:08
*** carl_baldwin has quit IRC23:09
*** betsy has quit IRC23:11
*** armax has joined #openstack-meeting-alt23:11
*** e0ne has quit IRC23:12
*** jorgem has left #openstack-meeting-alt23:14
*** tdruiva has joined #openstack-meeting-alt23:16
*** dimtruck is now known as zz_dimtruck23:17
*** emagana has quit IRC23:18
*** shardy is now known as shardy_z23:19
*** jecarey has quit IRC23:23
*** igordcard has joined #openstack-meeting-alt23:24
*** julim has quit IRC23:27
*** SridharRamaswam1 has joined #openstack-meeting-alt23:34
*** SridharRamaswamy has quit IRC23:36
*** baoli has quit IRC23:37
*** emagana has joined #openstack-meeting-alt23:37
*** marun has joined #openstack-meeting-alt23:38
*** baoli has joined #openstack-meeting-alt23:38
*** marrusl has quit IRC23:40
*** satish_ has quit IRC23:47
*** sarob has joined #openstack-meeting-alt23:47
*** banix has quit IRC23:48
*** marun has quit IRC23:48
*** SridharRamaswam1 has quit IRC23:49
*** marrusl has joined #openstack-meeting-alt23:53
*** sarob has quit IRC23:55
*** banix has joined #openstack-meeting-alt23:55
*** SridharRamaswamy has joined #openstack-meeting-alt23:56
*** baoli has quit IRC23:59

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