Wednesday, 2014-11-19

*** ranjitha has joined #openstack-meeting-alt00:00
*** shohel02 has quit IRC00:00
*** AJK__ has joined #openstack-meeting-alt00:01
*** tdruiva has quit IRC00:03
*** baoli has quit IRC00:03
*** carl_baldwin has joined #openstack-meeting-alt00:04
*** DaSchab has joined #openstack-meeting-alt00:04
*** banix has quit IRC00:06
*** david-lyle is now known as david-lyle_afk00:06
*** zz_avozza is now known as avozza00:07
*** DaSchab has quit IRC00:08
*** jjmb has joined #openstack-meeting-alt00:09
*** balajiiyer has joined #openstack-meeting-alt00:09
*** EricGonczer_ has joined #openstack-meeting-alt00:10
*** kebray has joined #openstack-meeting-alt00:13
*** SridharRamaswamy has quit IRC00:17
*** johnbelamaric has joined #openstack-meeting-alt00:17
*** johnbelamaric has quit IRC00:18
*** avozza is now known as zz_avozza00:20
*** chellygel has joined #openstack-meeting-alt00:22
*** padkrish has quit IRC00:24
*** padkrish has joined #openstack-meeting-alt00:25
*** SridharRamaswamy has joined #openstack-meeting-alt00:25
*** yamamoto has joined #openstack-meeting-alt00:25
*** EricGonczer_ has quit IRC00:26
*** betsy has quit IRC00:27
*** marcoemorais has quit IRC00:28
*** marcoemorais has joined #openstack-meeting-alt00:28
*** marcoemorais has quit IRC00:28
*** marcoemorais has joined #openstack-meeting-alt00:29
*** yamahata has joined #openstack-meeting-alt00:30
*** sicarie has quit IRC00:30
*** banix has joined #openstack-meeting-alt00:31
*** MarkAtwood has quit IRC00:31
*** nelsnelson has quit IRC00:32
*** banix has quit IRC00:32
*** carl_baldwin has quit IRC00:33
*** gholler has joined #openstack-meeting-alt00:33
*** tdruiva has joined #openstack-meeting-alt00:33
*** SridharRamaswamy has quit IRC00:35
*** yamahata has quit IRC00:36
*** banix has joined #openstack-meeting-alt00:37
*** yamahata has joined #openstack-meeting-alt00:37
*** yamamoto has quit IRC00:38
*** tdruiva has quit IRC00:38
*** gholler_ has joined #openstack-meeting-alt00:38
*** Sukhdev has joined #openstack-meeting-alt00:40
*** gholler__ has joined #openstack-meeting-alt00:41
*** banix has quit IRC00:41
*** gholler has quit IRC00:41
*** SridharRamaswamy has joined #openstack-meeting-alt00:43
*** oomichi has joined #openstack-meeting-alt00:43
*** gholler_ has quit IRC00:44
*** gholler__ has quit IRC00:45
*** banix has joined #openstack-meeting-alt00:47
*** alex_xu has joined #openstack-meeting-alt00:48
*** shohel02 has joined #openstack-meeting-alt00:50
*** shohel02 has quit IRC00:55
*** sunnyr has quit IRC01:01
*** banix has quit IRC01:02
*** annashen has quit IRC01:05
*** padkrish has quit IRC01:05
*** mfedosin_ has quit IRC01:05
*** Longgeek has joined #openstack-meeting-alt01:07
*** yamamoto_ has joined #openstack-meeting-alt01:09
*** colinmcnamara has quit IRC01:09
*** tsekiyam_ has joined #openstack-meeting-alt01:10
*** Longgeek has quit IRC01:12
*** mtanino has quit IRC01:12
*** mattgriffin has quit IRC01:13
*** tsekiyama has quit IRC01:14
*** banix has joined #openstack-meeting-alt01:14
*** ranjitha has quit IRC01:14
*** tsekiyam_ has quit IRC01:14
*** mattgriffin has joined #openstack-meeting-alt01:16
*** sunnyr has joined #openstack-meeting-alt01:19
*** mattgriffin has quit IRC01:31
*** rmoe has quit IRC01:31
*** sarob has quit IRC01:33
*** tdruiva has joined #openstack-meeting-alt01:34
*** mwagner_lap has joined #openstack-meeting-alt01:36
*** Sukhdev has quit IRC01:37
*** tdruiva has quit IRC01:39
*** gyee has quit IRC01:40
*** dboik has joined #openstack-meeting-alt01:41
*** dboik_ has joined #openstack-meeting-alt01:42
*** ycombinator_ has joined #openstack-meeting-alt01:42
*** ChuckC has quit IRC01:43
*** kebray has quit IRC01:45
*** Yuanying_ has joined #openstack-meeting-alt01:45
*** dboik has quit IRC01:46
*** rmoe has joined #openstack-meeting-alt01:48
*** shohel02 has joined #openstack-meeting-alt01:50
*** sunnyr has quit IRC01:52
*** DaSchab has joined #openstack-meeting-alt01:52
*** banix has quit IRC01:53
*** baoli has joined #openstack-meeting-alt01:54
*** zhhuabj has joined #openstack-meeting-alt01:54
*** Slower has quit IRC01:54
*** shohel02 has quit IRC01:54
*** zz_dimtruck is now known as dimtruck01:55
*** DaSchab has quit IRC01:57
*** zz_avozza is now known as avozza02:01
*** nosnos has joined #openstack-meeting-alt02:02
*** achanda_ has quit IRC02:04
*** bdpayne_ has quit IRC02:07
*** Yuanyin__ has joined #openstack-meeting-alt02:08
*** amcrn has quit IRC02:08
*** adrian_otto has joined #openstack-meeting-alt02:09
*** Yuanying_ has quit IRC02:10
*** EricGonczer_ has joined #openstack-meeting-alt02:11
*** avozza is now known as zz_avozza02:11
*** Riddhi has joined #openstack-meeting-alt02:19
*** tsekiyama has joined #openstack-meeting-alt02:21
*** tsekiyama has quit IRC02:25
*** jjmb has quit IRC02:26
*** dave-mccowan has joined #openstack-meeting-alt02:28
*** jjmb has joined #openstack-meeting-alt02:31
*** Longgeek has joined #openstack-meeting-alt02:33
*** dave-mccowan has quit IRC02:35
*** erkules_ has joined #openstack-meeting-alt02:36
*** dave-mccowan has joined #openstack-meeting-alt02:37
*** Longgeek has quit IRC02:38
*** padkrish has joined #openstack-meeting-alt02:38
*** erkules has quit IRC02:38
*** ChuckC has joined #openstack-meeting-alt02:39
*** woodster_ has quit IRC02:40
*** ycombinator_ has quit IRC02:42
*** jjmb has quit IRC02:43
*** soulxu_ has joined #openstack-meeting-alt02:43
*** mattgriffin has joined #openstack-meeting-alt02:43
*** marcoemorais has quit IRC02:43
*** AJK__ has quit IRC02:44
*** alex_xu has quit IRC02:46
*** Yuanyin__ has quit IRC02:46
*** Yuanying_ has joined #openstack-meeting-alt02:47
*** dave-mccowan has quit IRC02:50
*** shohel02 has joined #openstack-meeting-alt02:50
*** Yuanying_ has quit IRC02:51
*** soulxu__ has joined #openstack-meeting-alt02:52
*** EricGonczer_ has quit IRC02:52
*** bdpayne has joined #openstack-meeting-alt02:55
*** shohel02 has quit IRC02:55
*** soulxu_ has quit IRC02:55
*** soulxu_ has joined #openstack-meeting-alt02:58
*** banix has joined #openstack-meeting-alt03:00
*** soulxu__ has quit IRC03:02
*** SridharRamaswamy has quit IRC03:04
*** soulxu__ has joined #openstack-meeting-alt03:04
*** padkrish has quit IRC03:04
*** achanda has joined #openstack-meeting-alt03:04
*** bdpayne has quit IRC03:04
*** dims_ has quit IRC03:05
*** dims has joined #openstack-meeting-alt03:06
*** miqui has joined #openstack-meeting-alt03:07
*** soulxu_ has quit IRC03:07
*** padkrish has joined #openstack-meeting-alt03:09
*** achanda has quit IRC03:10
*** bradjones has quit IRC03:10
*** padkrish has quit IRC03:11
*** EricGonczer_ has joined #openstack-meeting-alt03:11
*** EricGonczer_ has quit IRC03:12
*** bradjones has joined #openstack-meeting-alt03:12
*** soulxu_ has joined #openstack-meeting-alt03:12
*** AJK__ has joined #openstack-meeting-alt03:15
*** soulxu__ has quit IRC03:16
*** harlowja is now known as harlowja_away03:16
*** soulxu__ has joined #openstack-meeting-alt03:18
*** AJK__ has quit IRC03:19
*** nosnos has quit IRC03:20
*** soulxu_ has quit IRC03:22
*** arnaud has quit IRC03:25
*** soulxu_ has joined #openstack-meeting-alt03:27
*** noslzzp has quit IRC03:27
*** jrist has quit IRC03:28
*** tdruiva has joined #openstack-meeting-alt03:29
*** soulxu__ has quit IRC03:31
*** tdruiva_ has joined #openstack-meeting-alt03:31
*** tdruiva has quit IRC03:31
*** achanda has joined #openstack-meeting-alt03:32
*** Longgeek has joined #openstack-meeting-alt03:34
*** Yuanying_ has joined #openstack-meeting-alt03:35
*** tdruiva_ has quit IRC03:36
*** MarkAtwood has joined #openstack-meeting-alt03:36
*** Longgeek has quit IRC03:38
*** dboik_ has quit IRC03:38
*** jrist has joined #openstack-meeting-alt03:40
*** DaSchab has joined #openstack-meeting-alt03:41
*** soulxu__ has joined #openstack-meeting-alt03:45
*** DaSchab has quit IRC03:46
*** soulxu_ has quit IRC03:48
*** sigmavirus24 is now known as sigmavirus24_awa03:49
*** funzo has quit IRC03:49
*** shohel02 has joined #openstack-meeting-alt03:50
*** funzo has joined #openstack-meeting-alt03:51
*** soulxu_ has joined #openstack-meeting-alt03:51
*** soulxu__ has quit IRC03:54
*** shohel02 has quit IRC03:55
*** funzo has quit IRC03:55
*** soulxu_ has quit IRC04:00
*** arnaud has joined #openstack-meeting-alt04:01
*** soulxu_ has joined #openstack-meeting-alt04:01
*** ycombinator_ has joined #openstack-meeting-alt04:04
*** zz_avozza is now known as avozza04:05
*** Riddhi has quit IRC04:07
*** jjmb has joined #openstack-meeting-alt04:07
*** noslzzp has joined #openstack-meeting-alt04:09
*** mattgriffin has quit IRC04:09
*** carl_baldwin has joined #openstack-meeting-alt04:12
*** nosnos has joined #openstack-meeting-alt04:12
*** avozza is now known as zz_avozza04:14
*** AJK__ has joined #openstack-meeting-alt04:16
*** daneyon has quit IRC04:17
*** SumitNaiksatam has quit IRC04:17
*** SumitNaiksatam has joined #openstack-meeting-alt04:17
*** flwang has quit IRC04:21
*** soulxu__ has joined #openstack-meeting-alt04:21
*** banix has quit IRC04:21
*** AJK__ has quit IRC04:21
*** otherwiseguy has joined #openstack-meeting-alt04:23
*** soulxu_ has quit IRC04:24
*** banix has joined #openstack-meeting-alt04:24
*** flwang has joined #openstack-meeting-alt04:24
*** MarkAtwood has quit IRC04:26
*** ycombinator_ has quit IRC04:28
*** soulxu_ has joined #openstack-meeting-alt04:31
*** teran has quit IRC04:31
*** tdruiva has joined #openstack-meeting-alt04:32
*** soulxu__ has quit IRC04:33
*** MarkAtwood has joined #openstack-meeting-alt04:35
*** soulxu__ has joined #openstack-meeting-alt04:36
*** tdruiva has quit IRC04:36
*** SumitNaiksatam has quit IRC04:37
*** SumitNaiksatam has joined #openstack-meeting-alt04:39
*** soulxu_ has quit IRC04:39
*** banix has quit IRC04:41
*** ivar-laz_ has joined #openstack-meeting-alt04:42
*** achanda has quit IRC04:42
*** ivar-lazzaro has quit IRC04:45
*** ivar-laz_ has quit IRC04:46
*** soulxu_ has joined #openstack-meeting-alt04:50
*** shohel02 has joined #openstack-meeting-alt04:50
*** jjmb has quit IRC04:51
*** soulxu__ has quit IRC04:53
*** pcarver has quit IRC04:53
*** mattgriffin has joined #openstack-meeting-alt04:55
*** tnurlygayanov has quit IRC04:55
*** shohel02 has quit IRC04:55
*** soulxu__ has joined #openstack-meeting-alt04:56
*** soulxu_ has quit IRC04:59
*** dimtruck is now known as zz_dimtruck05:01
*** padkrish has joined #openstack-meeting-alt05:02
*** marun has joined #openstack-meeting-alt05:03
*** Yuanying_ has quit IRC05:05
*** Yuanying_ has joined #openstack-meeting-alt05:05
*** MarkAtwood has quit IRC05:05
*** noslzzp has quit IRC05:09
*** soulxu_ has joined #openstack-meeting-alt05:09
*** Yuanying_ has quit IRC05:10
*** SridharRamaswamy has joined #openstack-meeting-alt05:10
*** soulxu__ has quit IRC05:12
*** SridharRamaswamy has quit IRC05:15
*** achanda has joined #openstack-meeting-alt05:25
*** DaSchab has joined #openstack-meeting-alt05:30
*** teran has joined #openstack-meeting-alt05:32
*** marun has quit IRC05:32
*** tdruiva has joined #openstack-meeting-alt05:33
*** DaSchab has quit IRC05:34
*** Yuanying_ has joined #openstack-meeting-alt05:36
*** teran has quit IRC05:36
*** tdruiva has quit IRC05:37
*** balajiiyer has quit IRC05:40
*** Yuanying_ has quit IRC05:40
*** soulxu__ has joined #openstack-meeting-alt05:42
*** miqui has quit IRC05:44
*** soulxu_ has quit IRC05:45
*** zz_avozza is now known as avozza05:49
*** shohel02 has joined #openstack-meeting-alt05:50
*** k4n0 has joined #openstack-meeting-alt05:52
*** soulxu_ has joined #openstack-meeting-alt05:53
*** shohel02 has quit IRC05:55
*** soulxu__ has quit IRC05:56
*** amotoki_ has quit IRC05:57
*** soulxu__ has joined #openstack-meeting-alt06:00
*** mattgriffin has quit IRC06:01
*** soulxu_ has quit IRC06:03
*** avozza is now known as zz_avozza06:04
*** prmtl has joined #openstack-meeting-alt06:08
*** sgotliv has joined #openstack-meeting-alt06:10
*** david-ly_ has joined #openstack-meeting-alt06:11
*** colinmcnamara has joined #openstack-meeting-alt06:12
*** david-lyle_afk has quit IRC06:12
*** soulxu_ has joined #openstack-meeting-alt06:12
*** carl_baldwin has quit IRC06:13
*** soulxu__ has quit IRC06:15
*** AJK__ has joined #openstack-meeting-alt06:18
*** AJK__ has quit IRC06:23
*** Longgeek has joined #openstack-meeting-alt06:23
*** padkrish has quit IRC06:23
*** otherwiseguy has quit IRC06:26
*** HeOS has quit IRC06:28
*** Longgeek has quit IRC06:28
*** xuhanp has joined #openstack-meeting-alt06:31
*** amotoki has joined #openstack-meeting-alt06:33
*** teran has joined #openstack-meeting-alt06:33
*** nshaikh has joined #openstack-meeting-alt06:34
*** tdruiva has joined #openstack-meeting-alt06:34
*** teran has quit IRC06:38
*** tdruiva has quit IRC06:38
*** k4n0 has quit IRC06:39
*** esker has quit IRC06:44
*** achanda has quit IRC06:48
*** colinmcnamara has quit IRC06:49
*** shohel02 has joined #openstack-meeting-alt06:50
*** Longgeek has joined #openstack-meeting-alt06:53
*** k4n0 has joined #openstack-meeting-alt06:54
*** nkrinner has joined #openstack-meeting-alt06:54
*** shohel02 has quit IRC06:55
*** Longgeek has quit IRC06:55
*** Longgeek has joined #openstack-meeting-alt06:56
*** achanda has joined #openstack-meeting-alt06:57
*** pcarver has joined #openstack-meeting-alt07:03
*** Yuanying_ has joined #openstack-meeting-alt07:08
*** jprovazn has joined #openstack-meeting-alt07:09
*** beagles has quit IRC07:11
*** Yuanying_ has quit IRC07:12
*** DaSchab has joined #openstack-meeting-alt07:16
*** armax has quit IRC07:16
*** david-ly_ has quit IRC07:18
*** beagles has joined #openstack-meeting-alt07:20
*** DaSchab has quit IRC07:20
*** beagles is now known as Guest721907:21
*** shohel02 has joined #openstack-meeting-alt07:21
*** kevinbenton has quit IRC07:22
*** shohel02 has quit IRC07:25
*** achanda has quit IRC07:26
*** k4n0 has quit IRC07:31
*** tdruiva has joined #openstack-meeting-alt07:34
*** soulxu_ is now known as alex_xu07:36
*** tdruiva has quit IRC07:39
*** k4n0 has joined #openstack-meeting-alt07:44
*** HeOS has joined #openstack-meeting-alt07:49
*** shohel02 has joined #openstack-meeting-alt07:54
*** sballe has quit IRC07:58
*** jtomasek has quit IRC07:58
*** AJK__ has joined #openstack-meeting-alt08:00
*** alexbh has joined #openstack-meeting-alt08:02
*** yamamoto_ has quit IRC08:02
*** DaSchab has joined #openstack-meeting-alt08:03
*** teran has joined #openstack-meeting-alt08:04
*** AJK__ has quit IRC08:04
*** azemlyanov has joined #openstack-meeting-alt08:04
*** pnavarro has joined #openstack-meeting-alt08:06
*** teran has quit IRC08:08
*** freemabr_ has joined #openstack-meeting-alt08:08
*** arnaud has quit IRC08:09
*** freemabr has quit IRC08:09
*** SridharG has joined #openstack-meeting-alt08:09
*** DaSchab has quit IRC08:13
*** alex_xu has quit IRC08:13
*** nadya has joined #openstack-meeting-alt08:14
*** nadya is now known as Guest3136508:14
*** Yuanying_ has joined #openstack-meeting-alt08:19
*** Yuanying_ has quit IRC08:23
*** sergef has joined #openstack-meeting-alt08:29
*** tdruiva has joined #openstack-meeting-alt08:35
*** Guest31365 has quit IRC08:37
*** igormarnat is now known as igormarnat_08:38
*** tdruiva has quit IRC08:40
*** nadya_ has joined #openstack-meeting-alt08:42
*** david-lyle_afk has joined #openstack-meeting-alt08:49
*** nadya_ has quit IRC08:49
*** tchaypo has left #openstack-meeting-alt08:50
*** DaSchab has joined #openstack-meeting-alt08:53
*** yamamoto_ has joined #openstack-meeting-alt08:53
*** DaSchab has quit IRC08:54
*** safchain has joined #openstack-meeting-alt08:58
*** jcoufal has joined #openstack-meeting-alt08:58
*** jcoufal has quit IRC09:01
*** jcoufal has joined #openstack-meeting-alt09:01
*** jcoufal has quit IRC09:01
*** jcoufal has joined #openstack-meeting-alt09:02
*** SumitNaiksatam has quit IRC09:06
*** SumitNaiksatam has joined #openstack-meeting-alt09:06
*** nosnos has quit IRC09:07
*** rpodolyaka_afk is now known as rpodolyaka_work09:07
*** rpodolyaka_work is now known as rpodolyaka_at_wo09:07
*** rpodolyaka_at_wo is now known as rpodolyaka_work09:07
*** nosnos has joined #openstack-meeting-alt09:08
*** sgotliv has quit IRC09:10
*** deepakcs has joined #openstack-meeting-alt09:11
*** deepakcs has quit IRC09:12
*** andreykurilin_ has joined #openstack-meeting-alt09:14
*** igordcard has joined #openstack-meeting-alt09:15
*** oomichi has quit IRC09:16
*** yamamoto_ has quit IRC09:18
*** erkules_ is now known as erkules09:18
*** nadya_ has joined #openstack-meeting-alt09:22
*** hyakuhei has quit IRC09:26
*** vipul has quit IRC09:27
*** teran has joined #openstack-meeting-alt09:28
*** nadya_ has quit IRC09:28
*** nshaikh has quit IRC09:33
*** zz_avozza is now known as avozza09:34
*** aglarendil has left #openstack-meeting-alt09:36
*** tdruiva has joined #openstack-meeting-alt09:36
*** nshaikh has joined #openstack-meeting-alt09:36
*** Longgeek has quit IRC09:38
*** tdruiva has quit IRC09:41
*** igormarnat_ is now known as igormarnat09:44
*** igormarnat is now known as igormarnat_09:45
*** Longgeek has joined #openstack-meeting-alt09:49
*** ddmitriev1 has quit IRC09:55
*** DaSchab has joined #openstack-meeting-alt09:55
*** jannis_rake-reve has joined #openstack-meeting-alt09:57
*** hachao has quit IRC09:58
*** igordcard has quit IRC09:59
*** niclem has quit IRC09:59
*** vipul has joined #openstack-meeting-alt09:59
*** DaSchab has quit IRC10:00
*** igormarnat_ is now known as igormarnat10:01
*** AJK__ has joined #openstack-meeting-alt10:01
*** hyakuhei has joined #openstack-meeting-alt10:04
*** pnavarro has quit IRC10:05
*** pnavarro has joined #openstack-meeting-alt10:05
*** AJK__ has quit IRC10:07
*** igormarnat is now known as igormarnat_10:14
*** deepakcs has joined #openstack-meeting-alt10:14
*** nadya_ has joined #openstack-meeting-alt10:16
*** pnavarro has quit IRC10:17
*** xuhanp has quit IRC10:17
*** yamamoto has joined #openstack-meeting-alt10:18
*** yamamoto has quit IRC10:23
*** pnavarro has joined #openstack-meeting-alt10:27
*** jtomasek has joined #openstack-meeting-alt10:27
*** reed has joined #openstack-meeting-alt10:27
*** stannie1 is now known as stannie10:27
*** igormarnat_ is now known as igormarnat10:28
*** hachao has joined #openstack-meeting-alt10:29
*** aglarendil has joined #openstack-meeting-alt10:30
*** sgotliv has joined #openstack-meeting-alt10:31
*** igormarnat is now known as igormarnat_10:31
*** nfedotov has quit IRC10:37
*** tdruiva has joined #openstack-meeting-alt10:37
*** tdruiva has quit IRC10:41
*** flwang has quit IRC10:44
*** nfedotov has joined #openstack-meeting-alt10:47
*** amotoki has quit IRC10:51
*** alexbh has quit IRC10:55
*** xianghui_ is now known as xianghui10:58
*** sgotliv has quit IRC10:59
*** andreykurilin__ has joined #openstack-meeting-alt11:03
*** nadya_ has quit IRC11:03
*** andreykurilin_ has quit IRC11:03
*** DaSchab has joined #openstack-meeting-alt11:03
*** prmtl has quit IRC11:06
*** nadya_ has joined #openstack-meeting-alt11:07
*** DaSchab has quit IRC11:08
*** dims has quit IRC11:09
*** dims has joined #openstack-meeting-alt11:09
*** arnaud__ has joined #openstack-meeting-alt11:10
*** e0ne has joined #openstack-meeting-alt11:13
*** arnaud__ has quit IRC11:14
*** zz_johnthetubagu is now known as johnthetubaguy11:14
*** denis_makogon has joined #openstack-meeting-alt11:14
*** freemabr_ has quit IRC11:16
*** teran has quit IRC11:18
*** prmtl has joined #openstack-meeting-alt11:20
*** niclem has joined #openstack-meeting-alt11:22
*** sgotliv has joined #openstack-meeting-alt11:34
*** teran has joined #openstack-meeting-alt11:36
*** igordcard has joined #openstack-meeting-alt11:37
*** DaSchab has joined #openstack-meeting-alt11:38
*** Yuanying_ has joined #openstack-meeting-alt11:38
*** tdruiva has joined #openstack-meeting-alt11:38
*** teran has quit IRC11:40
*** tdruiva has quit IRC11:42
*** Yuanying_ has quit IRC11:42
*** ekarlso- has quit IRC11:44
*** ekarlso- has joined #openstack-meeting-alt11:50
*** Guest7219 is now known as b3nt_pin11:50
*** DaSchab has quit IRC11:53
*** DaSchab has joined #openstack-meeting-alt11:54
*** AJK__ has joined #openstack-meeting-alt12:04
*** Yuanying_ has joined #openstack-meeting-alt12:05
*** mwagner_lap has quit IRC12:08
*** AJK__ has quit IRC12:08
*** Yuanying_ has quit IRC12:09
*** teran has joined #openstack-meeting-alt12:17
*** sgotliv has quit IRC12:18
*** enikanorov has quit IRC12:22
*** noslzzp has joined #openstack-meeting-alt12:24
*** enikanorov has joined #openstack-meeting-alt12:24
*** noslzzp has quit IRC12:26
*** deepakcs has quit IRC12:33
*** alex_xu has joined #openstack-meeting-alt12:34
*** Longgeek has quit IRC12:36
*** Longgeek has joined #openstack-meeting-alt12:36
*** tdruiva has joined #openstack-meeting-alt12:39
*** sgotliv has joined #openstack-meeting-alt12:42
*** tdruiva has quit IRC12:43
*** angelomatarazzo has joined #openstack-meeting-alt12:43
*** jjmb has joined #openstack-meeting-alt12:46
*** sgotliv has quit IRC12:49
*** ekarlso- has quit IRC12:50
*** ekarlso- has joined #openstack-meeting-alt12:50
*** yamamoto has joined #openstack-meeting-alt12:50
*** cbouch has joined #openstack-meeting-alt12:52
*** flwang has joined #openstack-meeting-alt12:52
*** tnurlygayanov has joined #openstack-meeting-alt12:52
*** yamamoto has quit IRC12:55
*** dims has quit IRC12:58
*** juzuluag has joined #openstack-meeting-alt12:58
*** DaSchab_ has joined #openstack-meeting-alt12:58
*** dims has joined #openstack-meeting-alt12:58
*** angmat has joined #openstack-meeting-alt12:58
*** angmat has left #openstack-meeting-alt12:59
*** angelomatarazzo has quit IRC12:59
*** angelomatarazzo has joined #openstack-meeting-alt13:00
*** amotoki has joined #openstack-meeting-alt13:01
*** DaSchab has quit IRC13:01
*** matrohon has joined #openstack-meeting-alt13:02
*** noslzzp has joined #openstack-meeting-alt13:04
*** sgotliv has joined #openstack-meeting-alt13:04
*** Yuanying_ has joined #openstack-meeting-alt13:05
*** Yuanyin__ has joined #openstack-meeting-alt13:07
*** Yuanying_ has quit IRC13:07
*** dims has quit IRC13:08
*** dims has joined #openstack-meeting-alt13:08
*** andreykurilin__ has quit IRC13:10
*** nadya_ has quit IRC13:10
*** Yuanyin__ has quit IRC13:12
*** tdruiva has joined #openstack-meeting-alt13:17
*** Longgeek has quit IRC13:18
*** yalie__ has joined #openstack-meeting-alt13:19
*** xuhanp has joined #openstack-meeting-alt13:24
*** ycombinator_ has joined #openstack-meeting-alt13:24
*** sgordon_ has joined #openstack-meeting-alt13:26
*** niclem has quit IRC13:26
*** markmcclain has joined #openstack-meeting-alt13:27
*** markmcclain has quit IRC13:27
*** markmcclain has joined #openstack-meeting-alt13:28
*** DaSchab_ has quit IRC13:30
*** DaSchab has joined #openstack-meeting-alt13:30
*** igormarnat_ is now known as igormarnat13:34
*** amrith is now known as _amrith_13:34
*** igormarnat is now known as igormarnat_13:43
*** dprince has joined #openstack-meeting-alt13:45
*** bertys has joined #openstack-meeting-alt13:48
*** satish has joined #openstack-meeting-alt13:48
*** erikmoe has joined #openstack-meeting-alt13:48
*** Longgeek has joined #openstack-meeting-alt13:50
*** amitry has joined #openstack-meeting-alt13:50
*** zz_dimtruck is now known as dimtruck13:53
*** amitry has quit IRC13:54
*** dgollub has joined #openstack-meeting-alt13:55
*** dalgaaf__ has joined #openstack-meeting-alt13:55
*** ybabenko has joined #openstack-meeting-alt13:56
*** tdruiva has quit IRC13:56
*** alee_ has left #openstack-meeting-alt13:56
*** yamahata has quit IRC13:57
*** noslzzp has quit IRC13:57
*** yamahata has joined #openstack-meeting-alt13:57
*** amitry has joined #openstack-meeting-alt13:59
*** pc_m has joined #openstack-meeting-alt14:00
*** betsy has joined #openstack-meeting-alt14:00
*** ajo has joined #openstack-meeting-alt14:00
ajohi :)14:01
*** margaret__ has joined #openstack-meeting-alt14:01
*** nyechiel__ has joined #openstack-meeting-alt14:01
*** nyechiel__ is now known as nyechiel14:01
ajohi nyechiel14:01
*** nadya_ has joined #openstack-meeting-alt14:01
sgordon_>.>14:01
nyechielhi ajo14:01
sgordon_#startmeeting TelcoWG14:02
openstackMeeting started Wed Nov 19 14:02:04 2014 UTC and is due to finish in 60 minutes.  The chair is sgordon_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: TelcoWG)"14:02
openstackThe meeting name has been set to 'telcowg'14:02
sgordon_#chair amitry14:02
openstackCurrent chairs: amitry sgordon_14:02
*** amuller has joined #openstack-meeting-alt14:02
*** esker has joined #openstack-meeting-alt14:02
sgordon_#topic roll call14:02
*** openstack changes topic to "roll call (Meeting topic: TelcoWG)"14:02
mkodererhi14:02
DaSchabhi14:02
ybabenkohi14:02
sgordon_hi all, who is here for the telco working group meeting (formerly nfv)14:02
amitryHello14:02
b3nt_pinhi14:02
amullerhiya14:02
margaret__hi14:02
dgollubhi14:02
ybabenkoDeutsche Telekom14:02
yamahatahello14:02
ajome :) hi14:02
*** padkrish has joined #openstack-meeting-alt14:03
angelomatarazzoHi14:03
margaret__I'm AT&T14:03
nyechielhi14:03
*** dimtruck is now known as zz_dimtruck14:03
amitryComcast14:03
mkodererDeutsche Telekom++14:03
sgordon_excellent, welcome all14:03
jannis_rake-revehi, deutsche telekom14:03
*** pask81 has joined #openstack-meeting-alt14:03
*** irenab has joined #openstack-meeting-alt14:03
*** gmatefi has joined #openstack-meeting-alt14:03
ybabenkoHi T-Labs >)14:03
jannis_rake-reve:)14:03
*** dkusidlo_ has joined #openstack-meeting-alt14:03
sgordon_#link https://etherpad.openstack.org/p/nfv-meeting-agenda14:03
*** shwetaap has joined #openstack-meeting-alt14:03
dkusidlo_hi14:03
sgordon_agenda is at the above location, feel free to add additional items if you need to14:03
sgordon_#topic wiki gardening14:04
*** openstack changes topic to "wiki gardening (Meeting topic: TelcoWG)"14:04
sgordon_#info team page moved to https://wiki.openstack.org/wiki/TelcoWorkingGroup14:04
*** prmtl has quit IRC14:04
sgordon_i got a start on updating the team page14:04
*** r-mibu has joined #openstack-meeting-alt14:04
sgordon_there is still refinement of mission/scope to do to add the clarity that seemed to be missing14:05
sgordon_#link https://wiki.openstack.org/wiki/TelcoWorkingGroup#Mission_statement_and_scope14:05
*** rtomasko has joined #openstack-meeting-alt14:05
sgordon_i have split out the membership page14:05
sgordon_and also intend to split out the use cases page(s)14:05
*** carl_baldwin has joined #openstack-meeting-alt14:05
sgordon_though we still need to move towards a different way of tracking these imo14:05
*** AJK__ has joined #openstack-meeting-alt14:06
sgordon_ideas tossed around at summit were google doc or possibly storyboard14:06
sgordon_i still need to do some investigation of the latter14:06
sgordon_#action sgordon_ to investigate current state of storyboard and report back14:06
*** aveiga has joined #openstack-meeting-alt14:06
mkoderersgordon_: but we can already start to create some google docs? or should we wait?14:06
sgordon_mkoderer, i dont think we necessarily need to wait14:07
sgordon_after all we already have *some* use cases now on the wiki14:07
sgordon_atm there is very variable depth though14:07
sgordon_#link https://wiki.openstack.org/wiki/TelcoWorkingGroup#Session_Border_Controller14:07
sgordon_#link https://wiki.openstack.org/wiki/TelcoWorkingGroup#Virtual_IMS_Core14:07
margaret__If I wanted to add other use cases where do i this - on the wiki?14:07
sgordon_#link https://wiki.openstack.org/wiki/TelcoWorkingGroup#VLAN_Trunking14:07
ybabenkosgordon > how to we decide/prioritize on use-cases? What are the criteria?14:07
*** akhila-chetlapal has joined #openstack-meeting-alt14:07
sgordon_margaret__, i think on the wiki in the first instance14:07
sgordon_margaret__, my thinking is to create https://wiki.openstack.org/wiki/TelcoWorkingGroup/UseCases and link from there14:08
DaSchabVirtual_IMS_Core and Session_Border_Controller are more or less ervices not a real use-case, isn't it?14:08
*** Yuanying_ has joined #openstack-meeting-alt14:08
sgordon_DaSchab, that's up to the group - atm it's the best we have14:08
aveigaDaSchab: I'd argue that they imply a use-case, though14:08
ybabenko"some" use-cases does not sound compeling to me - i think we should work on real pain points first?14:08
margaret__what is the goal of the use case?14:08
*** noslzzp has joined #openstack-meeting-alt14:08
sgordon_the rest are directly the ETSI use cases which arent as useful from an openstack developer perspective14:08
margaret__I think the goal of the use cases should be to flush out openstack - which is instantiation of a VNF service14:09
sgordon_+114:09
ybabenkoUse-case is a a telco scenario to be implemented on top of infra/open stack14:09
DaSchabtreu14:09
DaSchabtrue14:09
margaret__We are proposing this type of use cases in OPNFV as we speak - we can also submit it here14:09
margaret__But our goal is to actually try and execute it with openstack, odl....14:10
sgordon_right14:10
sgordon_we can also link to those directly if that makes sense rather than repeating14:10
sgordon_though ultimately we do need to provide enough use case info in a blueprint/spec that developers can understand why we're requesting/doing something14:10
*** AJK__ has quit IRC14:10
jannis_rake-revedoes it make sense to have use cases in there that do not need alterations/ additions to OS?14:10
ybabenkomargaret - let us stay in openstack community and use the tooling provided here - why double the work and do it in two places?14:10
margaret__oh that would be great - Metaswitch also submitted their SBC to OPNFV and here i noticed14:11
*** mwagner_lap has joined #openstack-meeting-alt14:11
jannis_rake-revee.g. Clearwater IMS14:11
*** carl_baldwin has quit IRC14:11
ybabenkoone use case for me would be a service chain use-case14:11
ybabenkodeployed either in one DC or multiple DC14:12
jannis_rake-reveybabenko: could you be more specific pls?14:12
sgordon_so, it seems there is a lot of enthusiasm to provide use cases and what is perhaps needed is some structure/guidance on where to put them?14:12
jannis_rake-reveas far as i understand we need a reference implementation eventually14:12
*** Yuanying_ has quit IRC14:12
*** nyechiel has quit IRC14:12
ybabenkoservice chain is a number of function connected in a particular way to produce a specific telco service. One example could be business VPN usecase with firewall. But again it is just an example14:12
mkoderersgordon_: a template would be useful ;)14:13
amitryAlso, maybe a default template that encourages enough depth14:13
jannis_rake-revesgordon_: +114:13
*** noslzzp has quit IRC14:13
sgordon_mkoderer, why do i have a feeling i took that action item :)14:13
mkoderersgordon_: :P14:13
ybabenkosgordon yes14:13
sgordon_amitry, right - i dont think the section in the specs template does this enough14:13
*** jjmb1 has joined #openstack-meeting-alt14:13
sgordon_#info need structure/guidance on where to put use cases14:13
sgordon_#info need a template that encourages enough depth14:14
ajo+114:14
sgordon_#action sgordon_ to update wiki structure and provide a draft template for discussion14:14
mkoderer+114:14
*** richm has joined #openstack-meeting-alt14:14
ybabenkoneed prioriy criteria - what is important for telco folks here? what is missing?14:14
sgordon_now on that note, do we think it's still useful to keep the minimal descriptions of the ETSI use cases on the page:14:14
*** mestery has quit IRC14:14
sgordon_#link https://wiki.openstack.org/wiki/TelcoWorkingGroup#ETSI-NFV_Use_Cases_-_High_Level_Description14:14
sgordon_the gap analysis document is relatively useful but i am not sure about the rest14:15
DaSchabdo we have the same understanding what the scope of a use-case should be?14:15
sgordon_DaSchab, i think margaret__ summed it up well earlier "I think the goal of the use cases should be to flush out openstack - which is instantiation of a VNF service"14:15
sgordon_does anyone see additional scope on top of this at least initially?14:16
margaret__I agree the HL use cases aren't useful - you need more specific instantiation flows14:16
*** jjmb has quit IRC14:16
ybabenkoUse-case is realisation of specific telco service on top of plain open stack?14:16
DaSchab...but not the service itself14:16
sgordon_ybabenko, i think it helps illustrate something "real" to the wider community14:16
*** tedross has joined #openstack-meeting-alt14:16
ybabenkono. not the service itself. service comes from some service folks14:16
*** noslzzp has joined #openstack-meeting-alt14:16
margaret__as part of telco instantiation - SDN controllers come into the picture.14:16
*** jay-s-b has joined #openstack-meeting-alt14:17
ybabenkomargaret - can you clarify?14:17
*** emagana has joined #openstack-meeting-alt14:17
sgordon_#topic use case scope14:17
*** openstack changes topic to "use case scope (Meeting topic: TelcoWG)"14:17
*** woodster_ has joined #openstack-meeting-alt14:17
sgordon_#info need to agree on scope/intent of use cases14:17
margaret__If you instantiate a VPN service - you may need to instantiate a vPE. well connectivity between vPE, TOR, LAN, WAN is needed - so where is this done? (SDN controller is one)14:18
ybabenkoSDN controller is not part of open stack - it will need to come as an addon - openstack will provide the necessary API via Neutron towards SDN controller14:18
margaret__will connect to vPE...14:18
*** ayyaz_ has joined #openstack-meeting-alt14:18
sgordon_question there is arguably, how much of this needs to be orchestrated using OpenStack APIs14:18
sgordon_ideally14:18
sgordon_ybabenko, right14:18
margaret__yes but you now need an SDN controller of some sort to maybe flush out neutron14:18
sgordon_ybabenko, and i think that is the key point - as regardless of controller backend we need  a common API yes?14:18
ybabenkoFor us it is important that we have stable neutron API14:19
ybabenkoas we would expect SDN vendor to comply to it14:19
margaret__placement becomes important due to latency - does that exist in openstack?14:19
matrohonmargaret__: VPN services does'nt need a vPE, we have a proposal for do it in neutron agent directly14:19
amitryMaybe the step one running VNF on top of openstack, step two orchestration  using openstack apis14:19
matrohonybabenko : +1 (from Orange)14:19
sgordon_#info "do we have the same understanding what the scope of a use-case should be?"14:20
margaret__matrohon_ don't understand why you say VPN doesn't need a vPE14:20
sgordon_#info "Use-case is realisation of specific telco service on top of plain open stack?"14:20
sgordon_#info "Maybe the step one running VNF on top of openstack, step two orchestration  using openstack apis"14:20
sgordon_so there are a number of areas touched on in the above conversation14:20
jannis_rake-revei believe it is also important to keep the API stable and focus in its core: so dont just add vendor feature to the api14:20
sgordon_as amitry notes14:20
sgordon_a good use case would ideally illustrate how these would be exercised in an ideal case14:21
sgordon_without delving into implementation so much14:21
ybabenkoDo we have a common understanding of SDN in this context? Does everyone see it as an additional component plugged via openstack api?14:21
ybabenkoWho "orchestrates" the stuff? The SDN controller?14:21
matrohonmargaret_ : the vPE can be the l3 agent or even the l2 agent from neutron. what is missing is the compatible dataplane and BGP speaker14:22
*** pc_m has left #openstack-meeting-alt14:22
jannis_rake-revemargaret__: what do you mean by placement14:22
margaret__That is the question - who connects everything and decides when to call the orchstrator to spin up the VNF14:22
*** pballand has quit IRC14:22
*** em845 has joined #openstack-meeting-alt14:22
DaSchabisn't that the job of an orchestrator?14:22
sgordon_+114:22
sgordon_but perhaps we have some terminology overload14:23
sgordon_when saying orchestrator14:23
jannis_rake-revemargaret__:  should OS be the overall orchestrator or rather "just" the infrastructure rchestrator14:23
ybabenkoBGP speaker is the gateway router,right? Or a VM running stuff like Quagga14:23
jannis_rake-revesgordon_:  yes14:23
sgordon_as there are potentially different levels of orchestration14:23
ybabenkoJannis +114:23
DaSchab+114:23
jannis_rake-reveShould we reference the NFV architecture first or is that too high level?14:24
DaSchabwe should decouple application from infrastructure orchestration14:24
margaret__matrohon_: I assume it isn't sufficient for us but that is another debate14:24
jannis_rake-reveDaSchab: yes14:24
DaSchabIaaS as demarcation line14:24
sgordon_jannis_rake-reve, i think it's useful at a high level for this group but not so much for broader community14:24
sgordon_jannis_rake-reve, i think it's useful for defining scope of this group though14:24
jannis_rake-reveDaSchab: although one might argue infrastructure goes beyond the OS datacentre14:24
sgordon_as i primarily see it as describing use of OpenStack as a VIM14:24
ybabenkoSo, can we vote on the start "use-case"?14:24
sgordon_and how an external orchestrator (whatever that may be) would use it14:25
margaret__So that is the next debate - what is the role of an SDN controller vs an orchestrator - we have our view which I know is different from others14:25
jannis_rake-revesgordon_: i agree14:25
mkoderersgordon_: I think we should move on and bring that topics to the ML14:25
aveigamargaret__: that's the real issue here, no matter what everyone will hav a different definition14:25
sgordon_+114:25
dgollubI guess what would be interesting for the community ... to clarify what this *orchestrator* actually is would be to fill/clarify following gap: TOSCA CSAR (or HOT) ----> ....*big orchestrator gap*.... ---> running VNF14:25
*** jjmb has joined #openstack-meeting-alt14:25
aveigado we define some of these thigns explicitly to avoid confusion?14:25
matrohonmargaret__ : +1 :) sorry for the troll14:25
sgordon_my proposal would be that i organize the wiki and draft a template14:25
sgordon_people can propose use cases, and then we can debate priorities, appropriateness etc14:26
*** akhila-chetlapal has left #openstack-meeting-alt14:26
*** erikmoe has quit IRC14:26
ybabenkosgordon +114:26
amitrySgordon_: +114:26
aveigasgordon_: I think we should really have a glossary in here for definining terms like "orchestrator"14:26
sgordon_i think this also drifts into the clarification of group scope14:26
aveigainsofar as we are able14:26
sgordon_aveiga, +1 i think that's a good idea14:26
*** mestery has joined #openstack-meeting-alt14:26
sgordon_we had discussed a glossary previously (as nfv team)14:27
sgordon_and didnt want to open that can of worms but i think a limited one would be good14:27
aveigaI don't think it's optional anymore, as we have differing opinions even within this group14:27
sgordon_does anyone want to take an action on the glossary aspect?14:27
jannis_rake-reveaveiga: I would really not like to reinvent the veil here but have a reference to sth existing, either a model, standard or implementation example14:27
*** nyechiel has joined #openstack-meeting-alt14:27
*** jjmb1 has quit IRC14:27
ajoaveiga +1 for the glossary14:27
aveigajannis_rake-reve: right, but which reference do you want to use?14:27
margaret__Should refer to ETSI ISG NFV docs on terminology before we re-invent... And then build from there14:27
*** dboik has joined #openstack-meeting-alt14:27
margaret__This also has been debated in ETSI ISG NFV14:28
jannis_rake-reveaveiga: I do not know since it depends on the people involved in this group14:28
*** akhila-chetlapal has joined #openstack-meeting-alt14:28
jannis_rake-revemargaret__:  yes, maybe14:28
*** Kiall has joined #openstack-meeting-alt14:28
aveigajannis_rake-reve: that's why I brought it up, since it can vary wildly14:28
sgordon_#action sgordon_ to kick off M/L discussion about template for use cases14:28
sgordon_#info need a glossary for overloaded terms, e.g. orchestration, to define common understanding14:28
dgollubI guess it would help if we could start mapping the ETSI NFV MANO components to existing OpenStack components/services ....14:29
sgordon_#info should refer to ETSI ISG NFV docs first14:29
jannis_rake-revesgordon_:  how can we get started with the gloss?14:29
sgordon_jannis_rake-reve, i would suggest just on the wiki14:29
*** funzo has joined #openstack-meeting-alt14:29
sgordon_either as a subsection of https://wiki.openstack.org/wiki/TelcoWorkingGroup14:29
sgordon_or create https://wiki.openstack.org/wiki/TelcoWorkingGroup/Glossary14:29
mkoderersgordon_: +1 for a new page14:30
ajoI'm new here, but are those ETSI NFV documents available?14:30
*** tdruiva has joined #openstack-meeting-alt14:30
margaret__I can pull in the ETSI terminology doc - I just can't attend these IRCs alot since this is my first one14:30
margaret__yes docs are available14:30
akhila-chetlapalwould the NFV orchestration be of interest to this group14:30
ajomargaret__, can they be linked to the wiki?14:30
jannis_rake-reveajo: yes :http://www.etsi.org/technologies-clusters/technologies/nfv14:30
sgordon_#link http://www.etsi.org/technologies-clusters/technologies/nfv14:31
margaret__there you go!14:31
mkodererakhila-chetlapal: we have it on the agenda for today14:31
ajothanks! :)14:31
*** giodeco has joined #openstack-meeting-alt14:31
jannis_rake-revei believe we can use them as a reference but not take them as a SPoT14:31
sgordon_akhila-chetlapal, per the enthusiastic discussion above it depends what we mean by orchestration ;)14:31
ybabenkomkodere +114:31
sgordon_ok being mindful of time, who wants to take the action to update the wiki wrt glossary?14:32
jannis_rake-revei have seen too much lobbying in that area, we need to focus on the ability to implement short to medium term14:32
*** AJK__ has joined #openstack-meeting-alt14:32
jannis_rake-revesgordon_:  shouldnt that be a grp effort anyway?14:32
sgordon_jannis_rake-reve, someone still needs to create the page etc14:33
jannis_rake-revesgordon_:  sure put me down14:33
sgordon_i also dont want to drift the group to far towards committee style interaction - i think it is fine for someone to propose something on the wiki14:33
akhila-chetlapalam specifically referring to the VNF lifecycle management which cannot happen via neutron plug-in components or SDN controllers14:33
sgordon_and then we debate/discuss either here or on M/L14:33
*** doude has quit IRC14:34
sgordon_#action jannis_rake-reve to create glossary page on wiki14:34
jannis_rake-revehow can we make sure that we dont overload on the gloss and drill down to the specification of the use cases?14:34
*** derekh has joined #openstack-meeting-alt14:34
sgordon_jannis_rake-reve, i would keep it limited to terms where we have contention specific to the openstack context14:34
amitrysgordon_: +114:34
sgordon_that arent covered in the ETSI material14:34
ajosgordon_: +114:35
akhila-chetlapali can put up a blueprint for review and update that based on comments so that we have a context for VNF orchestration14:35
*** jungleboyj has quit IRC14:35
sgordon_#info keep glossary limited to terms where there is contention specific to the openstack context that aren't covered in the ETSI material14:35
akhila-chetlapalor should it be in the NFV wiki14:35
*** doude has joined #openstack-meeting-alt14:35
sgordon_akhila-chetlapal, there is an item on orchestration in the other discussion that i think mkoderer14:36
*** _amrith_ is now known as amrith14:36
sgordon_let's try and get to it then14:36
sgordon_#topic Third Party CI14:36
*** openstack changes topic to "Third Party CI (Meeting topic: TelcoWG)"14:36
sgordon_there has been some ongoing discussion about the need for third party CI for some of the functionality that was implemented in juno and is being expanded in kilo14:36
sgordon_i dont think there is much to discuss atm other than that the relevant parties are working on it14:36
*** bobmel has joined #openstack-meeting-alt14:37
sgordon_e.g. imendel, ahoban, ijw, russellb and myself14:37
sgordon_#info third-party ci work and discussion continuing14:37
*** dave-mccowan has joined #openstack-meeting-alt14:37
sgordon_#topic Meeting times14:37
*** openstack changes topic to "Meeting times (Meeting topic: TelcoWG)"14:37
*** gholler has joined #openstack-meeting-alt14:38
sgordon_i proposed on mailing list an alternate time of Wednesday's @ 2200 UTC (starting next week)14:38
*** akhila-chetlapal has quit IRC14:38
sgordon_so we would alternate between 1400 UTC one week and 2200 UTC the next14:38
*** markmcclain has quit IRC14:38
*** akhila-chetlapal has joined #openstack-meeting-alt14:38
sgordon_i have not had any feedback/positive or negative on this but will confirm on monday hopefully14:38
sgordon_#action sgordon_ to lock in meeting time for next week on monday barring further feedback14:39
sgordon_i am going to skip over vlan trunking and come back to it if we have time14:39
amitryIsn't next Wednesday right before thanksgiving?14:39
*** dave-mccowan_ has joined #openstack-meeting-alt14:39
sgordon_amitry, yes14:39
*** alex_xu has quit IRC14:39
sgordon_so in general expecting not the highest attendance regardless of time14:39
aveigaamitry: mostly American holiday ;)14:39
amitryTrue14:40
jannis_rake-revesgordon_: i think for EU that alternation is fine14:40
aveigathat timeslot is for APAC, so we should still have the meeting14:40
sgordon_i live in the true white north so no holiday for me though14:40
*** Jakiro has joined #openstack-meeting-alt14:40
aveigayours was last month :)14:40
sgordon_:)14:40
jannis_rake-reveback to topic :)14:40
aveigasorry14:40
sgordon_we can pick up the most important piece (use cases) via M/L though14:40
amitrySorry14:40
jannis_rake-reveaveiga: np14:40
sgordon_#topic telco orchestration14:41
*** openstack changes topic to "telco orchestration (Meeting topic: TelcoWG)"14:41
mkodererall right14:41
sgordon_mkoderer, you had added https://etherpad.openstack.org/p/telco_orchestration14:41
sgordon_#link https://etherpad.openstack.org/p/telco_orchestration14:41
sgordon_#info (ijw) I think you'd need to make clear what orchestration would be an Openstack *service* and what would be better implemented as an Openstack *application* - what you've described there could be an application but pretty much all Openstack projects today are integrated services.14:41
mkodereryep, so we just have a short meeting and put things together14:41
jannis_rake-revemkoderer: i like it14:41
sgordon_ian had added the above feedback to the agenda, other comments etc. welcome14:41
*** dave-mccowan has quit IRC14:42
*** dave-mccowan_ is now known as dave-mccowan14:42
dgollubwtr. to ijw comment: I guess by service a full "service" telcos are offering to customers is meant ... e.g. a full fledged IMS deployment14:42
*** tdink has joined #openstack-meeting-alt14:42
sgordon_i think the key piece is the mapping on line 4514:42
mkodereryep... IMHO the goel would be to move as much as possible to OS components14:42
sgordon_and drilling down on the gaps on line 57 in much more detail14:42
*** esker has quit IRC14:42
aveigadgollub: that's an application though, as OpenStack doesn't offer IMS14:43
aveigait runs on top of it14:43
sgordon_right14:43
aveigait's a service from the telco POV, but an over the top application from OpenStack's view14:43
sgordon_ian is coming at it from the pov14:43
sgordon_of "im an openstack dev, what do i need to do to help you"14:43
*** esker has joined #openstack-meeting-alt14:43
aveigayup, and this WG should take a similar approach14:44
dgollubaveiga: good point ..then we should rewrite that statement and replace the term "service" with "application"14:44
aveigaotherwise the work won't get done14:44
jannis_rake-reve+114:44
mkodererdgollub: +114:44
*** mcall13 has joined #openstack-meeting-alt14:44
Jakirot+114:44
DaSchab+114:44
mkodererI think we spend some more time in the etherpad14:44
*** esker has quit IRC14:44
mkodererand then I would like to create a document in the wiki14:45
sgordon_#info need to rewrite to make clearer what's OpenStack "service" versus "application"14:45
sgordon_that seems reasonable14:45
dgollubupdated the etherpad ...14:45
sgordon_etherpad is good for quick collaborative editing14:45
ajo+1 service->application14:45
sgordon_once we have something everyone is comfortable with in terms of scope then it makes sense to put it in the wiki14:45
mkoderersgordon_: +114:45
jannis_rake-reveagree14:45
*** zz_gondoi is now known as gondoi14:45
akhila-chetlapalagree14:46
Jakiroagree14:46
sgordon_#info further edits to be done in etherpad, once consensus is reached move to wiki14:46
*** akoneru has joined #openstack-meeting-alt14:46
mkoderershould we also start a M/L discussion and point to the etherpad?14:46
sgordon_mkoderer, yes please14:46
mkoderersgordon_: ok, sound good to me14:47
*** waqas_riaz has joined #openstack-meeting-alt14:47
*** hareeshp has joined #openstack-meeting-alt14:47
sgordon_note that since we renamed the group atm i am using the [NFV] and [telco] tags to denote these messages14:47
jannis_rake-revemaybe focus on things that help other interest groups first14:47
sgordon_after a while probably makes sense to just use [telco]14:47
sgordon_#action mkoderer to kick off mailing list thread to get wider feedback14:47
sgordon_thanks for that14:48
mkodererjannis_rake-reve: do you have some suggestions?14:48
*** pkoniszewski has joined #openstack-meeting-alt14:48
dgollubjannis_rake-reve: we put this on the etherpad "Improve/extend OpenStack orchestration in such gerneral/common way that they are useful also outside Telco-OpenStack setups"14:48
jannis_rake-revemkoderer: IPv6 feature parity is the most obviious one14:48
ybabenkojannis  it looks like a lot of tention is around neutron?14:48
ybabenkoIPv6 +114:48
ybabenkomulti-site openstack support ?14:48
amitryIPv6 +114:49
*** otherwiseguy has joined #openstack-meeting-alt14:49
*** akoneru has quit IRC14:49
mkodererybabenko: yep, we would like to spend some effort to build a multi region heat for instance14:49
jannis_rake-revei would really like to have more standardized QoS APIs14:49
*** akoneru has joined #openstack-meeting-alt14:49
aveigafederation (multi-site) is in progress but will be a requirement for proper service chaining14:49
jannis_rake-reveand not rely on telling OS to use SRIOV etc14:49
*** ulikleber has joined #openstack-meeting-alt14:49
aveigajannis_rake-reve: +1 on QoS, you should talk to sc68cal...14:50
amitryQoS +114:50
jannis_rake-reveso rather specify certain limits / thresholds instead of tec14:50
ybabenkoaveiga: is a must for carrier setup with openstack14:50
jannis_rake-revesry -technology14:50
matrohonthere was an agreement on Qos in neutron design summit14:50
*** amotoki has quit IRC14:50
ybabenkojannis_rake-reve: QoS in OVS?14:50
jannis_rake-revematrohon: thanks didnt know that14:50
matrohona lightweight version of Qos should la,d, which deal only with traffic shaping14:51
jannis_rake-reveybabenko: should not be specific to OVS, and I know that it is hard14:51
dgollubcoming from the VNF vendor side: I would not underestimate the importance on setting an open source standard how to provision/configure an actual VNF ... if we as OS community take her the lead hopefully this will become the defacto standard without too much proprietary stuff on top of OS14:51
ybabenkomatrohon: who manages QoS settings? OpenStack Neutron?14:51
jannis_rake-revematrohon: yes as a start, do not overspecify14:51
*** armax has joined #openstack-meeting-alt14:51
*** jaypipes has joined #openstack-meeting-alt14:51
matrohonneutron yes; ovs and linuxbridge are targeted14:52
ybabenkojannis_rake-reve: QoS for overlays?14:52
mkodererdgollub: are you refering to netconf yang?14:52
*** nosnos has quit IRC14:52
ybabenkojannis_rake-reve: we are thinking mainly in terms of overlays, right? guess, few ppl will just use plaing VLAN Taggins14:52
jannis_rake-revemaybe we should take the QoS discussion to the etherpad14:52
dgollubmkoderer: for instance ... or what ever will be OS's answer to configure a VNF14:52
jannis_rake-reveas a subpoint of what makes VNFs special14:53
jannis_rake-reveas started by mkoderer14:53
jannis_rake-reveybabenko: yes, but it should be agnostic14:53
ybabenkodgollub: where NFV manager gets complete topology information? provided we have multi-site. This issues is still open for me14:53
dgollubright now vendors pushing in the market with random VNFs ... in different format with different interfaces... and want to put their metadata for provision/configuration in random places14:53
jannis_rake-revewe are now appraoching top down and bottom up at the same time :)14:54
aveigaso, middle-out?14:54
aveiga;)14:54
*** dguryanov has quit IRC14:54
*** e0ne has quit IRC14:54
*** cloudon has joined #openstack-meeting-alt14:54
jannis_rake-revehow about the expansion of https://etherpad.openstack.org/p/telco_orchestration or a dedicated pad14:54
jannis_rake-reveregarding "special" requirements14:54
sgordon_i completely agree with the line of thought wrt QoS14:54
aveigaybabenko: I'd caution against overlay-only.  I'm a telco, and I run VLAN tags...14:54
jannis_rake-revemkoderer: what do you think?14:55
dgollubybabenko: that is open for me as well ... that is why I wanted to move the attention again on a higher layer on the OS stack ...14:55
*** balajiiyer has joined #openstack-meeting-alt14:55
jannis_rake-reveaveiga: we are to and we mix overlay and underlay14:55
jannis_rake-reve*too14:55
mkodererjannis_rake-reve: yep sounds good.. this it acutally a very important topic14:55
*** ulikleber has quit IRC14:55
*** zuqiang has joined #openstack-meeting-alt14:55
ybabenkoaveiga: see no chance taking l2 failure domains, security and multitenancy into account14:56
margaret__another debate - overlay - underlay...14:56
*** jecarey has joined #openstack-meeting-alt14:56
*** igormarnat_ is now known as igormarnat14:56
jannis_rake-revemargaret__: thats why i would like to keep it agnostic14:56
jannis_rake-reveas OS already does14:56
margaret__agree14:57
jannis_rake-reveregarding the network creation e.g.14:57
*** tonytan4ever has joined #openstack-meeting-alt14:57
*** pawel-palucki has joined #openstack-meeting-alt14:57
*** doude has quit IRC14:57
*** avozza is now known as zz_avozza14:58
*** padkrish has quit IRC14:58
*** SridharG has left #openstack-meeting-alt14:58
sgordon_#info discussion aboute qos, underlay versus overlay, etc. ensues in the context of what makes a VNF special14:58
sgordon_wary that we're reaching the top of the hour here14:58
sgordon_lots of good discussion though14:58
sgordon_some of these points i feel would be well suited to further hashing out in that etherpad or on the mailing list14:59
jannis_rake-revedoes anyone have a link to the discussion on QoS in the summit and can link in the pad?14:59
mkoderersgordon_: yep I think let's bringt it to the ML14:59
sgordon_and ideally via use cases once i complete my action to provide a framework :)14:59
*** igormarnat is now known as igormarnat_14:59
jannis_rake-reve+114:59
*** doude has joined #openstack-meeting-alt14:59
*** ian_ott has joined #openstack-meeting-alt14:59
sgordon_ok14:59
margaret__what is ML?14:59
jannis_rake-revemailing list14:59
sgordon_mailing list, sorry14:59
mkoderermargaret__: Mailing list14:59
margaret__ok thanks14:59
*** jjmb has quit IRC15:00
sgordon_inventing more terminology ... :)15:00
sgordon_thanks all!15:00
amullerI'd like to mention that VLAN trunking in Neutron is kind of stuck15:00
*** rtomasko has quit IRC15:00
*** zz_avozza is now known as avozza15:00
matrohonjannis_rake-reve : tahre agreement on Qos has been decided on friday, so no ehepad15:00
sgordon_amuller, ah - i hadn't caught up on that thread and didn't see eric or ian so hadn't brought it up15:00
ybabenkosgordon_: thanks15:00
sgordon_need to discuss in neutron meeting monday i guess?15:00
amullersgordon_: We need to get Eric and Ian talking to one another and Neutron cores, otherwise it'll continue to be stuck15:01
jannis_rake-revematrohon: thx15:01
jannis_rake-revesgordon_: thanks for modding15:01
amullerin the upstream meeting or any other form15:01
sgordon_#info amuller notes vlan trunking stuck - need eric and ian to discuss amongst themselves and with cores15:01
sgordon_#action sgordon_ to follow up on vlan trunking15:01
sgordon_thanks amuller15:01
sgordon_#endmeeting15:02
*** balajiiyer has left #openstack-meeting-alt15:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:02
openstackMeeting ended Wed Nov 19 15:02:01 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/telcowg/2014/telcowg.2014-11-19-14.02.html15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/telcowg/2014/telcowg.2014-11-19-14.02.txt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/telcowg/2014/telcowg.2014-11-19-14.02.log.html15:02
*** jay-s-b has quit IRC15:02
*** r-mibu has left #openstack-meeting-alt15:02
*** jjmb has joined #openstack-meeting-alt15:02
*** em845 has left #openstack-meeting-alt15:02
*** dboik has quit IRC15:03
*** cloudon has left #openstack-meeting-alt15:03
*** bertys has quit IRC15:03
*** denis_makogon has quit IRC15:05
jannis_rake-reveybabenko: you still here?15:06
*** amitry has quit IRC15:06
*** e0ne has joined #openstack-meeting-alt15:06
*** ian_ott has quit IRC15:06
*** esker has joined #openstack-meeting-alt15:06
ybabenkojannis_rake-reve: yep15:07
*** nyechiel has quit IRC15:07
*** esker has quit IRC15:07
*** nelsnelson has joined #openstack-meeting-alt15:07
*** otherwiseguy has quit IRC15:08
*** doude has quit IRC15:08
*** ycombinator_ has quit IRC15:09
*** Yuanying_ has joined #openstack-meeting-alt15:09
*** padkrish has joined #openstack-meeting-alt15:09
*** jbl has joined #openstack-meeting-alt15:09
*** amuller has left #openstack-meeting-alt15:09
*** aveiga has quit IRC15:10
*** Jakiro has quit IRC15:11
*** akhila-chetlapal has quit IRC15:11
*** waqas_riaz has quit IRC15:12
*** Yuanying_ has quit IRC15:13
*** nyechiel has joined #openstack-meeting-alt15:14
*** zz_jgrimm is now known as jgrimm15:14
*** jbl has left #openstack-meeting-alt15:14
*** irenab has quit IRC15:15
*** zehicle has quit IRC15:15
*** ptoohill has joined #openstack-meeting-alt15:16
*** denis_makogon has joined #openstack-meeting-alt15:16
*** dkusidlo_ has quit IRC15:17
*** mcall13 has left #openstack-meeting-alt15:17
*** xuhanp has quit IRC15:18
*** betsy has quit IRC15:20
*** padkrish has quit IRC15:21
*** dboik has joined #openstack-meeting-alt15:22
*** enikanorov has quit IRC15:22
*** sigmavirus24_awa is now known as sigmavirus2415:23
*** sergef has quit IRC15:23
*** sergef has joined #openstack-meeting-alt15:23
*** enikanorov has joined #openstack-meeting-alt15:23
*** jungleboyj has joined #openstack-meeting-alt15:26
*** amotoki has joined #openstack-meeting-alt15:28
*** dboik_ has joined #openstack-meeting-alt15:28
*** markmcclain has joined #openstack-meeting-alt15:29
*** colinmcnamara has joined #openstack-meeting-alt15:31
*** andreykurilin_ has joined #openstack-meeting-alt15:31
*** shwetaap has quit IRC15:31
*** dboik has quit IRC15:32
*** shwetaap has joined #openstack-meeting-alt15:35
*** dboik_ has quit IRC15:37
*** dboik has joined #openstack-meeting-alt15:38
*** romilg has joined #openstack-meeting-alt15:41
*** DuaneDeC_ has quit IRC15:41
*** DaSchab has quit IRC15:41
*** zuqiang has quit IRC15:41
*** DuaneDeC7 has joined #openstack-meeting-alt15:41
*** carl_baldwin has joined #openstack-meeting-alt15:43
*** EricGonczer_ has joined #openstack-meeting-alt15:43
*** jmontemayor has joined #openstack-meeting-alt15:45
*** pballand has joined #openstack-meeting-alt15:45
*** DuaneDeC7 has quit IRC15:46
*** otherwiseguy has joined #openstack-meeting-alt15:48
*** achanda has joined #openstack-meeting-alt15:48
*** Barker has joined #openstack-meeting-alt15:48
*** daneyon has joined #openstack-meeting-alt15:48
*** dboik has quit IRC15:50
*** dboik has joined #openstack-meeting-alt15:50
*** dgollub has left #openstack-meeting-alt15:52
*** yamamoto has joined #openstack-meeting-alt15:52
*** shwetaap has quit IRC15:53
*** shivharis has joined #openstack-meeting-alt15:54
*** tbarron_zzz has quit IRC15:54
*** nyechiel has quit IRC15:54
*** nyechiel has joined #openstack-meeting-alt15:54
*** tbarron1 has joined #openstack-meeting-alt15:55
*** jprovazn is now known as jprovazn_afk15:56
*** achanda has quit IRC15:56
*** tbarron1 is now known as tbarron15:56
*** jjmb1 has joined #openstack-meeting-alt15:56
*** shwetaap has joined #openstack-meeting-alt15:56
*** yamamoto has quit IRC15:57
*** achanda has joined #openstack-meeting-alt15:57
*** rkukura has joined #openstack-meeting-alt15:58
*** tbarron has quit IRC15:58
*** mtanino has joined #openstack-meeting-alt15:58
*** tbarron has joined #openstack-meeting-alt15:58
*** EricGonczer_ has quit IRC15:58
*** EricGonczer_ has joined #openstack-meeting-alt15:59
*** yamamoto has joined #openstack-meeting-alt15:59
*** sadasu has joined #openstack-meeting-alt15:59
*** jjmb has quit IRC16:00
rkukurahi ML2ers!16:00
yamamotohi16:00
*** irenab has joined #openstack-meeting-alt16:01
yamahatahello16:01
yalie__hi16:01
romilgHi All16:01
sadasuhello!16:01
irenabhi16:01
*** Sukhdev has joined #openstack-meeting-alt16:02
shivharishi all16:02
rkukuralooks like we’ve got quorum16:02
SukhdevHello everybody16:03
rkukuraSukhdev: OK if I chair today?16:03
*** Longgeek has quit IRC16:03
Sukhdevsorry for being late16:03
*** hareeshp has quit IRC16:03
Sukhdevrkukura: yes, please16:03
rkukura#startmeeting networking_ml216:03
openstackMeeting started Wed Nov 19 16:03:36 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:03
*** openstack changes topic to " (Meeting topic: networking_ml2)"16:03
openstackThe meeting name has been set to 'networking_ml2'16:03
rkukura#link https://wiki.openstack.org/wiki/Meetings/ML2#Agenda16:03
rkukura#topic Announcements16:04
*** openstack changes topic to "Announcements (Meeting topic: networking_ml2)"16:04
*** absubram_ has joined #openstack-meeting-alt16:04
rkukuraThere will be a mid-cycle meetup in December in Utah16:04
*** yalie has joined #openstack-meeting-alt16:04
rkukuraInfo is at https://wiki.openstack.org/wiki/Sprints/NeutronKiloSprint16:05
Sukhdevrkukura: Looks like there will be ML2 related work in this sprint16:05
rkukuraThis is likely to be relevant to ML2 both in terms of vendor driver relocation and the core changes.16:06
*** chellygel has left #openstack-meeting-alt16:06
*** Riddhi has joined #openstack-meeting-alt16:06
*** mattgriffin has joined #openstack-meeting-alt16:06
rkukuraI encourage ML2ers to participate if possible16:06
rkukuraAny other announcements?16:06
rkukuraIf not…16:07
sadasuany possibility of remote attendance to the mid-cycle summit?16:07
rkukura#topic Bugs16:07
*** openstack changes topic to "Bugs (Meeting topic: networking_ml2)"16:07
*** manishg has joined #openstack-meeting-alt16:07
rkukurashivharis:16:07
manishghi16:07
shivharisHI16:07
sadasurkukura: any info on my previous question?16:07
*** tsekiyama has joined #openstack-meeting-alt16:07
shivharisI have not combed the latest list this time, my apologies. I will open it up for folk who are actively working on bugs and if they need help16:08
*** kebray has joined #openstack-meeting-alt16:08
Sukhdevshivharis is probably jet-lagged like me :-):-)16:08
shivharisthere is a bug entered in the agenda, https://review.openstack.org/#/c/113999/16:09
*** azemlyanov has quit IRC16:09
shivharisyup, keeping odd hours due to jet lag16:09
*** Yuanying_ has joined #openstack-meeting-alt16:09
rkukuraDoesn’t look like banix is online16:10
*** achanda has quit IRC16:10
shivharisappears very calm this time, lets get to these next time, i will be more prepared.16:10
shivharisback to you bob.16:10
rkukuraOk, any other bugs need discussion?16:10
rkukuraIf not…16:10
rkukura#topic Spec Reviews16:10
*** openstack changes topic to "Spec Reviews (Meeting topic: networking_ml2)"16:10
*** funzo has quit IRC16:10
*** shwetaap has quit IRC16:11
rkukurahttps://review.openstack.org/#/c/99873/16:11
*** Leonr has joined #openstack-meeting-alt16:11
yamahatahi.16:11
rkukuraThis is the portsecurity extension spec16:12
*** dave-mccowan has quit IRC16:12
*** banix has joined #openstack-meeting-alt16:12
manishgrkukura: I had something to discuss but I can wait16:12
rkukurayamahata: what’s the status on this?16:12
manishgtill open discussion.16:12
sadasuI would like reviewers for my spec on ML2 driver for UCS Manager16:12
rkukuramanishg: OK16:12
yamahataYes, there are three similar proposals. Now we are talking for combined spec.16:12
sadasu#link https://review.openstack.org/13405616:12
yamahataIf the basic direction is okay for you and other core devs, I'd like to get -2 removed.16:13
rkukurayamahata: Do you have links to the other proposals?16:13
Sukhdevsadasu: I saw some comments on this - I will review it later today16:14
*** Yuanying_ has quit IRC16:14
yamahatahttps://review.openstack.org/#/c/106222/16:14
rkukuraI see mestery’s -2 comment references one16:14
sadasuSukhdev: thanks!16:14
yamahatahttps://review.openstack.org/#/c/97715/16:14
*** shwetaap has joined #openstack-meeting-alt16:14
yamahatathey are in reference section of the spec.16:15
rkukuraI’d suggest asking mestery to remove his -2 if there is agreement on which spec(s) go forward16:15
yamamotoyamahata: will yours be the combined spec?16:15
*** atiwari has joined #openstack-meeting-alt16:15
yamahatayamamoto: Yes. At least I try to.16:16
*** jehb has joined #openstack-meeting-alt16:16
rkukuraI’ll try to catch up on this review by next week16:16
sadasuafaik, the other 2 spec owners are willing to collaborate with yamahata16:16
yamahatashwetaap: do you have oany pinion?16:17
*** kashyap has joined #openstack-meeting-alt16:17
yamahatas/oany/any16:17
sadasubased on discussions during the summit16:17
*** ptoohill has quit IRC16:17
rkukuraany other spec reviews to discuss?16:18
rkukuraI have not posted the updated HPB spec yet, but will very soon.16:18
sadasuhave a general question on spec reviews16:19
SukhdevWe used to have a big list of specs - that got moved to Kilo - see this table https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review16:19
rkukurasadasu: go ahead16:19
rkukuraSukhdev: Thanks.16:19
rkukuraLets continue to update the wiki as specs are submitted.16:20
sadasuare spec approvals linked to what happens regarding reloaction of ML2 driver code?16:20
banixThis should be a straightforwrd spec: https://review.openstack.org/#/c/132226/16:20
shwetaapSorry but I am having a little bit of a connection problem here. What I had worked on for last cycle was to extend Aaron's port security extension in ML2. But the spec now is to have a port security as an extension driver in Ml2. I am in agreement with that. And  yamahata , I would be interested in taking up any work in this regard16:20
*** phil_h has joined #openstack-meeting-alt16:20
*** BrianB_ has joined #openstack-meeting-alt16:21
rkukurabanix: Looks like we are continuing the spec process for vendor drivers, at least until the repository move is resolved.16:22
*** ptoohill has joined #openstack-meeting-alt16:22
banixrkukura: thanks for letting me know. I missed that point.16:22
Sukhdevbanix: welcome back!!!16:22
banixSukhdev: thanks16:22
*** DuaneDeC7 has joined #openstack-meeting-alt16:23
rkukurashwetaap, yamahata: Let us know if we need to put portsecurity on the agenda for next week16:23
rkukuraAnything else on specs?16:23
manishgsadasu: don't think spec approvals are linked to decision about ml2 driver code relocation (afaik)16:24
*** betsy has joined #openstack-meeting-alt16:24
*** marun has joined #openstack-meeting-alt16:24
*** angelomatarazzo has quit IRC16:25
rkukuramanishg, sadasu, banix: My view is we should continue the spec process for vendor drivers for now. This might change if all vendor drivers move to vendor-specific repos.16:25
rkukuraWe’ll discuss that in a bit.16:25
sadasumanishg: good to know...we can make progress there16:25
irenabI do not have the spec yet, but we want to add QoS support for SRIOV ports, based on previously proposed patches by Sean Collins with some changes. It will require ML2 extension for QoS mapping to port and support for extendable get_device_details call into Extension Drivers. Can we discuss it here or need to push the spec first?16:25
sadasubanix: are you just looking for a 2nd core reviewer for your spec?16:26
manishgirenab: is this really qos or just throttling?16:26
*** dave-mccowan has joined #openstack-meeting-alt16:26
banixsadasu: yes16:26
rkukurairenab: Cool16:26
irenabmanishg: rate limiting16:26
*** SridharRamaswamy has joined #openstack-meeting-alt16:26
yamahatairenab: rate limiting by nic hw?16:27
irenabyamahata: yes16:27
*** niclem has joined #openstack-meeting-alt16:27
manishgirenab: then maybe better to just call it that.  qos brings in other implications and people will claim spec incomplete for qos.16:27
rkukurairenab: Not sure why the get_device_details would call into the extension drivers - these just manage the DB state - the mechanism drivers would need to enforce the extension semantics16:27
rkukuraWhich brings up the question of whether we want to work on extension semantic enforcement for Kilo?16:28
irenabrkukura: neutron agent will need to configure rate limiting, it should get the required settings16:28
rkukurairenab: Agreed, but I’d think the openvswitch mechanism driver would need to handle that.16:28
*** marun_ has joined #openstack-meeting-alt16:28
*** ptoohill has quit IRC16:28
irenabinstead of additional RPC call, it can get the details on existing call16:28
sadasuirenab: I am also interested in this spec16:29
rkukurairenab: Do you want to put this on the agenda for next week?16:29
irenabrkukura: I'll try to catch you offline to discuss, if its OK?16:29
rkukura#action Discuss rate limiting next week16:30
rkukurairenab: yes16:30
irenabrkukura: thanks16:30
rkukura#action Discuss portsecurity next week16:30
sadasuirenab: can you pls start a thread on the ML so others can participate/ get upto speed?16:30
*** nshaikh has quit IRC16:30
*** marun has quit IRC16:30
rkukurasadasu: Good idea16:30
manishgirenab: pls include me also if you start a thread.16:30
*** SridharRamaswamy has quit IRC16:31
irenabsadasu: sure, meanwhile trying to collaborate with Sean, but will send out to ML16:31
rkukurairenab: thanks16:31
shivharisML would be best, since i am interested as well16:31
sadasuirenab: thanks much16:31
rkukuraLets discuss on list, and summarize status at next weeks meeting16:31
rkukuramoving on…16:31
rkukura#topic ML2 Subream Charter16:32
*** openstack changes topic to "ML2 Subream Charter (Meeting topic: networking_ml2)"16:32
rkukuraAt the weekly Neutron IRC meeting, there was discussion of subteams16:32
*** dboik has quit IRC16:33
*** ptoohill has joined #openstack-meeting-alt16:33
rkukuraFirst, should the ML2 subteam continue?16:33
Sukhdevrkukura: I missed it because of timing - too early for me :-)16:33
*** david-lyle_afk is now known as david-lyle16:34
*** marun_ has quit IRC16:34
amotokiLayer-2 subteam rather than ML2 subteam?16:34
rkukuraThere seems to be some movement to reduce the number of subteams, but I’m not hearing any call to eliminate the ML2 subteam16:34
rkukuraamotoki: Good question16:35
amotokithough the main topic is related to ml2, some topics are not limited to ml2.16:35
*** marun_ has joined #openstack-meeting-alt16:35
sadasuI think ML2 is still evolving, so subteam is dfntly helpful16:35
rkukuraamotoki: I’d think other L2 plugins are outside our scope16:35
*** shwetaap1 has joined #openstack-meeting-alt16:35
*** EricGonczer_ has quit IRC16:36
*** EricGonczer_ has joined #openstack-meeting-alt16:36
amotokirkukura: yes to some extent.. but L2GW or other topics are related to L2. but i am not sure this is the best place to discuss.16:36
rkukuraOur main focus has been the ML2 plugin itself, its driver APIs, extensions, features, ...16:36
*** padkrish has joined #openstack-meeting-alt16:37
amotokirkukura: sounds reasonable16:37
manishgML2 is the only official core plugin. rest are vendor plugins.16:37
manishgso agree with rkukura about the scope.16:37
Sukhdevamotoki: L2GW is being proposed as a service plugin, not part of ML216:37
rkukuraWe’ve tried to make some progress on a modular L2 agent, but maybe that should be a separate effort16:37
shivharisrkukura: Additionally, ML2 has a significant traction with respect to several vendor drivers and is very valuable resource to them16:37
*** padkrish has quit IRC16:38
rkukuraShould our focus be limited to the integration point, or also include the reference control plane (L2 agents, etc.)?16:38
manishgl2 agents are independent of ML2 - agree.16:38
amotokiSukhdev: i know. I am not sure what is the best approach for l2gw.  I just raised potential topics to clarify the purpose of the subteam.16:38
rkukuraClearly the ML2 subteam should pay attention to the l2gw effort, but I’m not sure it needs to “own” it.16:39
rkukuraAnyway, if we want to continue, we need a charter16:39
irenabmanishg: not totally agree, since agents depend on data provided by plugin16:39
*** shwetaap has quit IRC16:39
manishgbut the interface should be discussed here I believe.  I think all touch points will end up needing discussion here.16:39
Sukhdevamotoki: The question is - should we limit the scope of this subcommittee to ML2 only or increase it to include all L2 related topics?16:39
manishgirenab: yes, that is the interface part.  doesn't mean the architecture depends on ML216:40
amotokiSukhdev: exactly.16:40
irenabmanishg: agree16:40
Sukhdevamotoki: I threw this question out so that we can discuss this16:40
amotokiimho it is better to focus on a single topic, so focusing ML2 looks good to me.16:41
rkukuraI’ve started a draft charter at https://etherpad.openstack.org/p/ML2_Subteam_Charter16:41
*** eddie__ has joined #openstack-meeting-alt16:41
rkukuraI’d suggest we try to incorporate wording on how the ML2 subteam would be involved in efforts like l2gw16:42
*** EricGonc_ has joined #openstack-meeting-alt16:42
*** EricGonczer_ has quit IRC16:42
Sukhdevrkukura: thanks for putting this together - this will help us focus our charter16:42
rkukuraI asked mestery about what he is looking for in these subteam charters16:42
rkukuraHe’s going to put together a wiki on this, which I think will be where the charters live.16:43
*** carl_baldwin has quit IRC16:43
rkukuraHe did say he wanted to see goals for Kilo, so I added some of the things we’ve been discussing16:43
*** padkrish has joined #openstack-meeting-alt16:43
rkukurawe don’t have a lot of time left today to complete wordsmithing this16:44
manishgrkukura: I think that makes sense and it also focuses our efforts.  Would be good define the charter (and thanks for the draft)16:44
amotokiit is very clear definition ot me and it seems worth forming a subteam.16:44
*** gyee has joined #openstack-meeting-alt16:45
*** jehb has quit IRC16:45
rkukuraI encourage others to add their ideas and comments, and improve wording as needed16:45
*** igormarnat_ is now known as igormarnat16:45
rkukuraDoes this seem like a reaonable start and a plan?16:46
banixrkukura: yes16:46
sadasurkukura: this is a great "draft"16:47
irenabrkukura: +116:47
manishgrkukura: yes16:47
amotokirkukura: of course yes16:47
*** satish_ has joined #openstack-meeting-alt16:47
Sukhdevrkukura: Absolutely16:47
shivharisrkukura: +116:47
rkukuraOK, lets try to polish this up over the next couple days so we have something for Monday’s neutron meeting16:47
*** doude has joined #openstack-meeting-alt16:48
rkukuranext topic…16:48
manishgrkukura: I think some of the efforts maybe dictated by which direction we head towards (split of api/rpc etc.)16:48
*** igormarnat is now known as igormarnat_16:48
*** EricGonc_ has quit IRC16:48
rkukuramanishg: Agreed, but that’s hopefully detail that doesn’t need to be in the charter.16:48
manishgagree.16:49
amotokimanishg: i think the first item covers it.16:49
Sukhdevmanishg: I am hoping nothing south of ML2 plugin changes -16:49
*** EricGonczer_ has joined #openstack-meeting-alt16:49
*** jcoufal has quit IRC16:49
rkukuraWe should try to make the charter as general and hight level as possible, covering both long term and some kilo specifics.16:49
rkukura#topic ML2 driver repository discussion16:50
*** timsim has joined #openstack-meeting-alt16:50
*** openstack changes topic to "ML2 driver repository discussion (Meeting topic: networking_ml2)"16:50
manishgamotoki: yes, but just saying remaining may not be completed and more stuff might come in due to the refactor.  but agree with what rkukura said - make it higher level so charter doesn't change much hopefully.16:50
*** paul_glass has joined #openstack-meeting-alt16:50
amotokirkukura: go ahead pls16:50
rkukuraI’m sure everyone is aware of the (somewhat vague) plan to move vendor drivers out of the neutron git repositroy16:50
*** satish has quit IRC16:51
rkukuraI think the initial thinking has been that each vendor would get their own (stackforge?) repo16:51
rkukuraThat seems to make sense for monolithic plugins, and could also apply to ML2 drivers16:51
Sukhdevrkukura: that makes more sense for monolithic plugins - I wonder if it makes sense for ML2 drivers16:52
SukhdevI mean individual ML2 drivers16:52
*** marun has joined #openstack-meeting-alt16:52
rkukuraBut we may want to look at alternatives for keeping the ML2 drivers together, at least for those vendors that choose to do so.16:52
rkukuraOne idea would be to have a common ml2-drivers repository, with some sort of core review team focused on ML216:53
shivharisI am assuming that unit tests will also be splt out, which begs the questions who runs the unit tests16:53
*** marun__ has joined #openstack-meeting-alt16:53
SukhdevUntil a straw-man proposal is put together, it is hard to argue one way or the other16:53
rkukuraI think the main motivation for all this is that vendor drivers don’t get enough core review attention in neutron16:54
manishgarmando already proposed a spec for the split.16:54
manishg#link: https://review.openstack.org/#/c/134680/16:54
rkukuramanishg: thanks - hadn’t seen that16:54
*** marun_ has quit IRC16:55
*** nkrinner has quit IRC16:55
manishgthe spec calls for split of ml2 drivers as well, from what I remember (read it yesterday).16:55
manishgit clearly defines the parts of the vendor drivers that will stay in repo to make things easier.16:56
Sukhdevmanishg: I have not read it yet - lets all review it and post comments on the spec itself16:56
*** dboik has joined #openstack-meeting-alt16:56
rkukuraSukhdev: +116:56
*** pballand has quit IRC16:56
*** k4n0 has quit IRC16:56
manishgrkukura: yes, that is one concern (that core reviewers won't be able to spend time on it).  But I think that is the exact reason it's proposed (because they don't have the time :( )16:57
*** Leon_ has joined #openstack-meeting-alt16:57
*** marun has quit IRC16:57
manishgI heard the main concern as -- APIs ... if they aren't clearly defined or change frequently it maybe an issue.16:57
rkukuraSo assuming this spec envisions moving each vendor driver into a vendor-specific repo, is there interest in a common ML2 driver repo with its own core review team?16:57
*** sarob has joined #openstack-meeting-alt16:58
manishgI think it would be a good idea and benefit all.16:58
sadasurkukura: +116:58
*** mugsie has joined #openstack-meeting-alt16:58
manishgat least if it is in one place other folks are more likely to review it.  and we can bring up reviews here and interested folks can review.16:58
*** pballand has joined #openstack-meeting-alt16:58
rkukuraMy personal view is that ML2 is a long way from having a stable driver API, and trying to lock it down now to guarantee compatiblity would be premature.16:58
irenabrkukura: if it makes development/deployment/testing easier, then definitly yes16:59
*** vinod has joined #openstack-meeting-alt16:59
*** SridharRamaswamy has joined #openstack-meeting-alt16:59
manishgand vendors can learn from each other.16:59
rkukuraWe are pretty much out of time16:59
*** jjmb1 has quit IRC16:59
amotokiit can but if  the number of vendor drivrs increases doesn't the same problem happen?16:59
amotokiit is open question.16:59
manishgrkukura: versioning is proposed in the spec.16:59
rkukuraLets review this spec and think about how we might go forward.16:59
*** Leonr has quit IRC16:59
irenabI guess its important to have stable API as ml2 mission17:00
manishgrkukura: I have a review for filter implementation of segments.17:00
manishgsorry... I guess no open discussion today.  will bring up next time.17:00
*** avozza is now known as zz_avozza17:00
*** mattgriffin has quit IRC17:00
*** rjrjr has joined #openstack-meeting-alt17:00
rkukuramanishg: Please make sure its in the spec tracking wili17:00
rkukurawiki17:00
*** dkusidlo_ has joined #openstack-meeting-alt17:00
*** mlavalle has joined #openstack-meeting-alt17:00
rkukurathanks everyone!17:00
manishgwill add.  thx17:00
*** mattgriffin has joined #openstack-meeting-alt17:00
manishgthanks!17:00
rkukura#endmeeting17:00
SukhdevThanks17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Nov 19 17:00:57 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
shivharisbye17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-11-19-16.03.html17:01
yamamotobye17:01
irenabthanks17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-11-19-16.03.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-11-19-16.03.log.html17:01
amotokibye. good night17:01
yamahatabye17:01
Kiall#startmeeting Designate17:01
openstackMeeting started Wed Nov 19 17:01:10 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
*** phil_h has quit IRC17:01
*** openstack changes topic to " (Meeting topic: Designate)"17:01
openstackThe meeting name has been set to 'designate'17:01
ekarlso-ello folks :)17:01
KiallHey Folks, who's about today?17:01
betsyo/17:01
yalie__bye17:01
mugsieo/17:01
*** SumitNaiksatam has quit IRC17:01
*** shivharis has quit IRC17:01
vinodo/17:01
Kiallrjrjr: about?17:01
*** romilg has quit IRC17:01
*** rcurran has joined #openstack-meeting-alt17:01
*** manishg has left #openstack-meeting-alt17:01
mugsieI saw him join a second ago17:01
*** rkukura has left #openstack-meeting-alt17:01
Kiallkk..17:01
KiallNo actions from last week, so skipping that..17:01
*** sadasu has quit IRC17:01
*** esker has joined #openstack-meeting-alt17:02
*** Leon_ has quit IRC17:02
Kiall#topic Pools - Where are we? (kiall)17:02
*** openstack changes topic to "Pools - Where are we? (kiall) (Meeting topic: Designate)"17:02
*** marun__ is now known as marun17:02
Kiallrjrjr pushed another patchset yesterday (or maybe the day before?).. I've been travelling, so haven't reviewed.. has anyone else had a chance?17:02
betsynope17:02
mugsieno major movement afaik - need to do another review day :|17:02
*** jungleboyj has left #openstack-meeting-alt17:03
rjrjrshould be finishing up the happy path by friday.  finally.17:03
vinodIt is marked as WIP. But I was looking it at now17:03
*** rcurran has quit IRC17:03
mugsierjrjr: cool17:03
mugsie:)17:03
Kiallrjrjr: excellent, I'm looking forward to getting the old stuff out :D17:03
betsyI can give an update on pool storage17:03
KiallAny blockers etc etc?17:03
*** Leonr has joined #openstack-meeting-alt17:03
timsimo/17:03
*** Longgeek has joined #openstack-meeting-alt17:03
Kiallbetsy: sure..17:03
vinodI did notice that there are some mismatches between the pool manager and minidns interfaces/calls17:04
vinodrjrjr: Do you want me to fix them up17:04
rjrjror point them out.17:04
*** shohel02 has quit IRC17:05
*** Leon_ has joined #openstack-meeting-alt17:05
*** Riddhi_ has joined #openstack-meeting-alt17:05
vinodsure rjrjr: I will work with you after this meeting17:05
Kiallbetsy: still there? ;)17:06
timsimIt looks like she's lost connection17:06
*** Riddhi has quit IRC17:06
timsimShe's putting in updates, but it's not showing up17:06
Kiallah, fair enough :)17:06
*** Leon_ has quit IRC17:07
*** gondoi is now known as zz_gondoi17:07
KiallSo.. Somewhat related to pools, we've got a "fun" bug.. https://bugs.launchpad.net/designate/+bug/139276217:07
uvirtbotLaunchpad bug 1392762 in designate "Concurrent requests can cause designate-central to lock up" [High,In progress]17:07
vinodbetsy is struggling with irc troubles17:07
vinodnetwork issues for her17:07
vinodrjrjr: Is pool manager working in the devstack tests now?17:07
*** Barker has quit IRC17:07
*** Barker_ has joined #openstack-meeting-alt17:07
Kiallit's relation to pools is that.. I believe we're best wait for all the old backend code to be removed before we fully fix it up17:07
*** betsy has quit IRC17:08
KiallSo, if you see me -1's pools reviews due to eventlet context switching.. You'll know it's that bug ;)17:08
*** betsy has joined #openstack-meeting-alt17:08
*** Leon_ has joined #openstack-meeting-alt17:08
Kiallvinod: Okay, we'll come back to betsy later.. Unless she's back on again?17:08
rjrjrvinod: yes17:08
*** pkoniszewski has quit IRC17:08
timsimShe's fighting it :P17:08
*** Longgeek has quit IRC17:08
timsimOp, she's on the other channel17:09
*** margaret__ has quit IRC17:09
betsyNow!17:09
*** nfedotov has quit IRC17:09
betsyI’m working on the server to pool_attributes table migration. And changing the v1 api to CRUD pool_attributes instead of servers while still looking like it’s doing servers. And then changing ALL the code to not use servers17:09
*** Leonr has quit IRC17:09
betsy:)17:09
*** Sukhdev has quit IRC17:09
Kiallcool - sounds like progress! :)17:09
betsyThat should be the last of the pool storage17:09
KiallExcellent - Is rjrjr held up by that work? I'm guessing not?17:10
*** Yuanying_ has joined #openstack-meeting-alt17:10
betsyNot as far as I know - rjrjr?17:10
rjrjrnot held up.17:11
KiallCool...17:11
KiallOkay, before we move on, any blockers re pools?17:11
rjrjrno17:11
rjrjrnot exactly.17:11
KiallExcellent :)17:11
Kiall#topic Mid-Cycle Dates/Locations/Topics17:11
*** openstack changes topic to "Mid-Cycle Dates/Locations/Topics (Meeting topic: Designate)"17:11
KiallHave we figured out any more info on this?17:11
rjrjryes.17:11
mugsie:D17:12
*** jtomasek has quit IRC17:12
*** irenab has quit IRC17:12
rjrjrwould the week of january 19 - 23 work for everyone?17:12
*** jmcbride has joined #openstack-meeting-alt17:13
mugsieI think so - Kiall how does that fit for you?17:13
timsimProbably so.17:13
KiallKinda.. I've got to be in CA 22nd/23rd (or 23rd/24th)17:13
rjrjrguys, i'm open on when.  trying to accommodate your schedule.17:13
rjrjrgot approval to do this.17:13
mugsiesweet17:14
mugsiehow logn do we want to put aside for it?17:14
mugsielong*17:14
mugsie2,3,4 days?17:14
timsim3 or 4 I'd think.17:14
mugsiewhich still could be ok for Kiall and CA17:14
KiallYea, that's works nicely for me17:14
mugsieMon -> Thurs in Pheonix?17:14
timsimJoe didn't seem too worried that (at least some) of us would be able to come.17:14
*** Barker_ has quit IRC17:14
rjrjrso january 19 - 22 then?17:15
*** hareeshpc has joined #openstack-meeting-alt17:15
mugsiejmcbride joined - those dates suit you Joe?17:15
*** vishwanathj has joined #openstack-meeting-alt17:15
mugsieKiall: can you confirm the 1st day you haveto be in CA?17:16
KiallYep - That should work for me, We'll want to figure out if everyone can manage 4 days.. But that can come a little later17:16
*** Yuanying_ has quit IRC17:16
Kiallmugsie: I'd love to, but nobody knows if it's the 22nd or 23rd yet17:16
mugsieah17:16
*** ayyaz_ has quit IRC17:16
mugsiei thought it was set :)17:16
*** marcoemorais has joined #openstack-meeting-alt17:16
jmcbrideI think that will work for me.17:16
Kialloriginal schedule was for Fri 23rd and Sat 24th .. Which everyone agreed to, then it was realized the 24th was a Sat.. It's kinda still up in the air17:16
*** belliott has left #openstack-meeting-alt17:17
KiallIt's the 22nd or 23rd either way17:17
*** matrohon has quit IRC17:17
mugsieso, we can agree to start on the money anyway17:17
mugsiemonday*17:17
* mugsie needs sleep17:17
mugsieand then 3 - 4 days for the duration17:17
timsimWant to set this tenatively, and come back to it next week? Jan 19-22?17:17
*** dkusidlo_ has quit IRC17:17
timsimOr maybe 21st17:18
mugsiethat sound like a good base plan? and circle around mext week, when people have checked with amnagement17:18
*** igordcard has quit IRC17:18
Kiallmugsie: ++17:18
timsimCool, sounds like fun.17:18
mugsie#action: all - check and confirm dates above17:18
KiallOkay.. Moving on! rjrjr thanks for Hosting.. :)17:19
rjrjrif it doesn't work, propose another slot.  i'm flexible as long as we nail down the dates in the next week or so.17:19
mugsie++17:19
vinodrjrjr: Is there an ebay office in Phoenix?17:19
rjrjryes.17:19
Kiall#action Pools Question - Do we want to treat nameservers differently than poolattributes, or is it just a type of poolattribute? (betsy)17:20
*** hareeshpc has quit IRC17:20
betsyI’ve just got a question as to why nameservers are treated separately than pool_attributes17:20
* mugsie *cough* #topic *cough*17:20
Kialllol17:20
*** Barker has joined #openstack-meeting-alt17:20
Kiall#ropic Pools Question - Do we want to treat nameservers differently than poolattributes, or is it just a type of poolattribute? (betsy)17:20
betsyAren’t they just a type of pool_attribute?17:20
Kiall#topic Pools Question - Do we want to treat nameservers differently than poolattributes, or is it just a type of poolattribute? (betsy)17:20
*** openstack changes topic to "Pools Question - Do we want to treat nameservers differently than poolattributes, or is it just a type of poolattribute? (betsy) (Meeting topic: Designate)"17:20
Kiall-_-17:20
betsy:)17:21
betsyWe’ve currently got a namerserver object and a pool_attribute object17:21
mugsiei think they are stored as a pool attrib, but displayed int he API separatly17:21
mugsiein the API*17:21
mugsieso, 2 objects is right17:21
mugsienameserver could inherit from pool_attrib17:22
betsyYeah, but we can still get that info from a pool_attriibute object vs a nameserver obj, can’t we?17:22
mugsieyeah, we could17:22
mugsieI am easy either way personlly17:22
betsywhat does everyone else think?17:22
KiallI'd argue we hide the pool_attributes table out of the way in the storage layer, since the _attributes tables were, from my memory, really about avoiding 1000s of small tables...17:23
Kiall(i.e. Nameserver is the object, Pool Attributes aren't)17:23
*** satish has joined #openstack-meeting-alt17:23
betsyok17:23
*** phil_h has joined #openstack-meeting-alt17:24
betsyBut we still have other pool attribute objects, right?17:24
*** satish_ has quit IRC17:24
KiallYea, when the scheduler comes along, we'll have more17:24
betsyOkay. I’ll leave it for now and see how the code goes17:24
KiallI think nameservers are the only existing use of it17:24
rjrjri think it is a pool attribute.17:24
vinodwe have scope too as a pool attribute currently17:24
timsimIt seems like a pool attribute to me, but not one that'd factor into the scheduler.17:25
mugsietimsim: ++17:25
*** giodeco has quit IRC17:25
*** arnaud__ has joined #openstack-meeting-alt17:25
Kialltimsim: agreed, scheduler hints will likely be an attribute with type=scheduler_hint value=<Something Here>17:25
timsimYep, that makes sense.17:26
betsyOk. So leave the nameserver object as is?17:26
KiallPersonally, I think so - But bearing in mind I've not read the patch yet, so "as is" could be different than I'm thinking :D17:27
betsyok. I’ll leave it for now and then y’all can review the patch17:27
mugsiecool :)17:27
*** arnaud__ has quit IRC17:27
Kiall#topic Open Discussion17:27
*** openstack changes topic to "Open Discussion (Meeting topic: Designate)"17:27
KiallAny other topics?17:27
jmcbrideyes17:27
Kiallmugsie: do you have that poll link handy?17:27
jmcbrideregarding server pools17:28
jmcbriderjrjr: You mentioned you were finishing the happy path on Friday.  Are you around next week (Thanksgiving week) for us to discuss any issues?17:28
mugsiei do17:28
rjrjryes.  i'm always on, holiday or not. 8^)17:28
mugsie#link https://www.surveymonkey.com/r/FJRBSVF17:28
Kiallrjrjr: lol17:28
timsimclear17:29
jmcbrideOK.  Getting the server pools bit finalized is an important milestone for us this year.17:29
timsimWrong window :P17:29
*** igordcard has joined #openstack-meeting-alt17:29
jmcbriderjrjr will you be at the IRC next Wednesday?17:29
rjrjryes.17:29
KiallHe's here every week :)17:29
timsimNext wednesdday is the day before a national holiday for us (Thanksgiving) so some of us may not be here.17:30
jmcbrideCool.  OK, just wanted to make sure we could reach out to you.  So I'm assuming after the happy path is posted, we all start pulling it down and testing away, identifying any issues, right?17:30
mugsie+117:30
KiallLazy b******* not coming into work, should we skip next weeks meeting? ;)17:31
timsimNah, I'm sure someone will be around.17:31
mugsieI saw go ahead17:31
*** HeOS has quit IRC17:31
betsyI’ll be here17:31
mugsiesay*17:31
vinodWe could have a quick check on server pools17:32
vinodI'll be here17:32
KiallOkay.. Quorum will be here, that'll work.17:32
jmcbrideI'd like to keep it on the calendar.17:32
ekarlso-btw, for you that would like to test, secondary zone stuff is up and v2 client :)17:32
mugsie:)17:32
jmcbridecool, ok, I'm good.  Thanks for the hard work, rjrjr.17:32
ekarlso-cloudistic.net/blog/drafts/designate-secondary-zones.html < see that for how to setup :)17:32
betsyekarlso: +117:32
rjrjrnp.  you can test now, but only zone add and delete is working.17:32
Kiall"You don't have permission to access /blog/drafts/designate-secondary-zones.html on this server." ;)17:32
ekarlso-rly17:33
timsimsame for me ^17:33
ekarlso-whaaat :p17:33
* Kiall loves how tech just randomly breaks itself ;)17:33
ekarlso-:p17:33
mugsiehas everyone filled the survey in for different meeting times?17:33
vinodi did17:33
*** marcoemorais has quit IRC17:33
mugsieto see if moving is a good idea...17:34
KiallI've not, every time I look at my calendar I get upself.17:34
Kiallupset*17:34
*** marcoemorais has joined #openstack-meeting-alt17:34
betsytry this: https://cloudistic.net/blog/drafts/designate-secondary-zones.html17:34
mugsie#link https://www.surveymonkey.com/r/FJRBSVF17:34
*** noslzzp has quit IRC17:34
ekarlso-https://www.cloudistic.net/blog/drafts/designate-secondary-zones.html < that sorry ;)17:34
ekarlso-ya ^17:34
*** marcoemorais has quit IRC17:34
nibalizeru17:35
nibalizererp ww17:35
vinodekarlso-: you now have the bar raised on documentation :-)17:35
rjrjrjust finished the survey.17:35
ekarlso-vinod: ? ;P17:35
*** emagana has quit IRC17:35
Kiallvinod: lol, just need to port it to docs.openstack.org ;)17:36
vinodi mean you have done a good job17:36
*** marcoemorais has joined #openstack-meeting-alt17:36
timsimnibalizer: wat17:36
*** emagana has joined #openstack-meeting-alt17:36
KiallYep, spec+post+code is looking good :)17:36
*** shohel02 has joined #openstack-meeting-alt17:36
KiallOkay, Any other topics or shall we call it a day?17:36
mugsieI am good17:36
vinodwhoever gets to try the same thing on server pools - it would be good to have a similar page - so that it would be helpful or others17:36
timsimI'm good.17:36
vinods/or/to17:36
*** noslzzp has joined #openstack-meeting-alt17:36
Kiallvinod: ++, any17:36
rjrjrgood.17:36
betsyvinod: +117:36
rjrjreveryone's typing has been gibberish today.17:37
ekarlso-:P17:37
ekarlso-if anyone would like, gimme feedback on the post ^ by 21:00 UTC today and i'll post it up to twitter :P17:37
Kiallekarlso-: looked good to me when I read yesterday :)17:38
*** e0ne has quit IRC17:38
KiallOkay, let's call it then.. I'm starving and dinner needs to be cooked :)17:38
*** shohel02_ has joined #openstack-meeting-alt17:38
timsimCool. See ya!17:38
KiallThanks all, esp rjrjr for the mid cycle venue and all the pools work :)17:38
*** shohel02 has quit IRC17:38
Kiall#endmeeting17:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:39
openstackMeeting ended Wed Nov 19 17:39:02 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-11-19-17.01.html17:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-11-19-17.01.txt17:39
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-11-19-17.01.log.html17:39
*** rjrjr has quit IRC17:39
*** andreykurilin_ has quit IRC17:39
*** nyechiel has quit IRC17:39
mugsieo/17:39
*** vinod has left #openstack-meeting-alt17:39
*** mugsie has left #openstack-meeting-alt17:39
*** amotoki has quit IRC17:39
*** pask81 has quit IRC17:39
*** timsim has left #openstack-meeting-alt17:40
*** emagana has quit IRC17:40
*** derekh has quit IRC17:41
*** safchain has quit IRC17:42
*** Barker has quit IRC17:42
*** absubram_ has quit IRC17:42
*** gmatefi has quit IRC17:43
*** emagana has joined #openstack-meeting-alt17:44
*** armax has quit IRC17:44
*** ptoohill has quit IRC17:44
*** ptoohill has joined #openstack-meeting-alt17:45
*** zz_avozza is now known as avozza17:46
*** zehicle has joined #openstack-meeting-alt17:47
*** annashen has joined #openstack-meeting-alt17:49
*** igordcard has quit IRC17:50
*** Riddhi_ has quit IRC17:50
*** harlowja_away is now known as harlowja17:51
*** Riddhi has joined #openstack-meeting-alt17:51
*** igormarnat_ is now known as igormarnat17:52
*** tonytan4ever has quit IRC17:52
*** nadya_ has quit IRC17:52
*** ptoohill has quit IRC17:53
*** ptoohill has joined #openstack-meeting-alt17:54
*** johnbelamaric has joined #openstack-meeting-alt17:55
*** EricGonczer_ has quit IRC17:55
*** tvoran has joined #openstack-meeting-alt17:55
*** markmcclain has quit IRC17:55
*** igormarnat is now known as igormarnat_17:55
*** rpodolyaka_work is now known as rpodolyaka_afk17:55
*** EricGonczer_ has joined #openstack-meeting-alt17:56
*** rmoe has quit IRC17:56
*** thomnico_ has quit IRC17:58
*** vishwanathj has quit IRC17:58
*** reed has quit IRC17:58
*** dboik_ has joined #openstack-meeting-alt17:58
*** SlickNik has joined #openstack-meeting-alt18:00
*** ptoohill has quit IRC18:00
SlickNik#startmeeting trove18:00
openstackMeeting started Wed Nov 19 18:00:31 2014 UTC and is due to finish in 60 minutes.  The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: trove)"18:00
openstackThe meeting name has been set to 'trove'18:00
*** dboik_ has quit IRC18:00
*** carl_baldwin has joined #openstack-meeting-alt18:00
*** dboik_ has joined #openstack-meeting-alt18:00
*** paul_glass has quit IRC18:00
*** eghobo has joined #openstack-meeting-alt18:00
SlickNikGiving folks a few minutes to trickle in18:00
*** ajo has quit IRC18:00
sgotlivo/18:00
peterstaco/18:01
amrith./18:01
*** esker has quit IRC18:01
*** marcoemorais has quit IRC18:01
SlickNikAgenda at:18:01
SlickNik#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting#Meeting_Nov_19th18:02
*** marcoemorais has joined #openstack-meeting-alt18:02
*** dboik has quit IRC18:02
*** grapex has joined #openstack-meeting-alt18:02
grapexo/18:02
*** kebray has quit IRC18:02
*** sunnyr has joined #openstack-meeting-alt18:02
*** armax has joined #openstack-meeting-alt18:03
SlickNik#topic oslo-incubator changes18:03
*** openstack changes topic to "oslo-incubator changes (Meeting topic: trove)"18:03
*** nshaikh has joined #openstack-meeting-alt18:03
amrithhello all18:04
SlickNikamrith: floor is yours18:04
dougshelley66o/18:04
amrithI'd like some reviews of these changes18:04
*** Ajay_ has joined #openstack-meeting-alt18:04
*** dboik_ has quit IRC18:04
schango/18:04
amriththanks to sergey, peterstac, mariam, denis, duk, doug so far18:04
sgotlivI will review it later today18:04
*** johnma has joined #openstack-meeting-alt18:04
amrithbut would like some others18:04
amriththe changes are now relatively small18:04
*** dboik has joined #openstack-meeting-alt18:04
amriththe hard work is in the oslo merge (to come)18:04
*** hareeshp has joined #openstack-meeting-alt18:05
amrithso depending on peoples thoughts, I'd like to get it staged to merge at the time when we think it should18:05
amrithSlickNik, i'm done18:05
*** sushilkm has joined #openstack-meeting-alt18:05
SlickNikThanks amrith — sounds good. Will take a look as well.18:06
*** ptoohill has joined #openstack-meeting-alt18:06
SlickNik#topic Better documentation for Image building18:06
sgotlivSlickNik, please, take a look on messaging patch as well18:06
*** openstack changes topic to "Better documentation for Image building (Meeting topic: trove)"18:06
amrithSlickNik, I thought I picked up the action item in Paris.18:07
SlickNiksgotliv: Yes, it's on my list as well.18:07
amrithare you looking to change it18:07
sgotlivthanks!18:07
SlickNikamrith: no, just looking for a follow up18:07
SlickNikAnd what the action item actually entails.18:07
amrithI haven't worked on it since Paris. I will brush it up and have it in the monday meeting in two weeks for review. does that work?18:08
amriththe action item currently entails telling basically how to run dib18:08
SlickNiki.e is this going in the dev docs or in the installation manual?18:08
amrithand documenting the elements we already have18:08
*** ivar-lazzaro has joined #openstack-meeting-alt18:08
*** tbarron has quit IRC18:08
amrithit should also provide a simple cookbook on how to make a new one if someone wanted to.18:08
*** eghobo has quit IRC18:09
*** ptoohill has quit IRC18:09
amrithI would expect that it goes in dev docs, not installation manual18:09
*** nyechiel has joined #openstack-meeting-alt18:09
*** tbarron has joined #openstack-meeting-alt18:09
SlickNikDo we need another section that's part of the official install guide?18:09
amriththe question is this, do we expect end users to create their own images?18:10
amrithI was assuming not18:10
sgotlivwhy not?18:10
georgelorcho/18:10
SlickNikthe current install guide says this:18:10
SlickNik"Create an image for the type of database you want to use, for example, MySQL, MongoDB, Cassandra.18:11
SlickNikThis image must have the trove guest agent installed, and it must have the trove-guestagent.conf file configured to connect to your OpenStack environment. To correctly configure the trove-guestagent.conf file, follow these steps on the guest instance you are using to build your image: …"18:11
SlickNik#link http://docs.openstack.org/juno/install-guide/install/apt/content/trove-install.html18:11
*** yamamoto has quit IRC18:11
*** reed has joined #openstack-meeting-alt18:11
*** Barker has joined #openstack-meeting-alt18:11
amrithok, let me look at that and get back to you with a better estimate next week.18:12
amrithwould that work?18:12
*** Yuanying_ has joined #openstack-meeting-alt18:12
amrithI was expecting this to be more of an operators thing18:12
amrithrather than an end user of trove18:12
*** rmoe has joined #openstack-meeting-alt18:12
*** pballand has quit IRC18:12
amrithI was expecting that an IT org or a csp would make the images and make them available18:12
amrithand that the end user would pick one.18:13
amrithnot that the end users would be making their own18:13
SlickNikamrith: is anyone collaborating with you on this?18:13
amrithI guess that's a matter of defining who the "user is".18:13
sgotlivtoday end user uploads images to Glance18:13
amrithI was working with abramley on this a while ago.18:13
amrithmore recently, I haven't done anything on it.18:13
amrithI was also working with laurel on this18:14
amrithfrom the doc perspective18:14
amritha while ago18:14
*** ptoohill has joined #openstack-meeting-alt18:14
SlickNikamrith: It is for operators, but the Install guide is also for operators — not just developers.18:15
*** Yuanying_ has quit IRC18:16
SlickNikBut sounds good. Let's chat after the meeting to see what we can do to make this happen soon (both for the dev docs and install guide — the instructions likely won't be the same).18:17
amrithok18:17
SlickNikThanks!18:17
*** armax has quit IRC18:18
SlickNik#topic Trove Mid Cycle Sprint in Seattle, WA18:18
*** openstack changes topic to "Trove Mid Cycle Sprint in Seattle, WA (Meeting topic: trove)"18:18
*** akoneru has quit IRC18:18
amrithSlickNik, I have a request18:18
*** andreykurilin_ has joined #openstack-meeting-alt18:18
amrithre: mid-cycle18:18
SlickNikamrith: yes?18:19
*** cp16net has joined #openstack-meeting-alt18:19
amrithThx, there appear to be no late night flights to the east coast.18:19
*** armax has joined #openstack-meeting-alt18:19
amriththerefore a W-F schedule means we can't leave till saturday18:19
amrithwould it be possible to do Tu-Th?18:19
amrithinstead.18:19
amrithlast flight (direct) to Boston is 2pm (as an example)18:19
amrith<eof>18:21
SlickNikHow do other folks feel about a Tu-Th instead of a Wed-Fri meetup?18:21
dougshelley66+118:21
SlickNikWell, let's back up a bit.18:21
amrithor monday to wednesday18:21
amrithI'd be happy with a late Sunday flight to seattle.18:21
SlickNikIt looks like the mid-cycle will be in February18:22
SlickNikI've set up a doodle poll to decide which week in Feb18:22
esmutethere is always the redeye flights18:22
amrithesmute, I don't see redeye to boston.18:22
amrithlast flight is 2:07pm, JB.18:22
SlickNik#link http://doodle.com/veabvxtc84czm9ep18:22
dougshelley66so is the doodle about picking a week or picking specific days in a week18:23
*** yamahata has quit IRC18:23
*** johnbelamaric has quit IRC18:23
*** johnbelamaric has joined #openstack-meeting-alt18:23
SlickNikIt's about picking the week — I wasn't able to get doodle an option to show a week in the poll instead of days.18:24
SlickNikWe can revisit the specific days once we have the week sorted out18:24
dougshelley66ah ok thx18:24
*** andreykurilin_ has quit IRC18:24
SlickNikI had thought of Wed-Fri initially, but I'm open to Mon-Wed or Tue-Thu if folks prefer that.18:24
amrithNikhil, don't use a calendar event, use a free-text event for week choices.18:25
amrithyou can make doodle a poll for anything, right now I have another doodle event to choose a restaurant (options are free text).18:25
esmuteamrith: you would think boston is a big enough of a city to have more directly flights..18:25
*** pballand has joined #openstack-meeting-alt18:25
amrithesmute, we're a small place18:25
amrithbut wait till we get the next olympics18:25
*** teran has quit IRC18:26
amrithwe'll even have an airport.18:26
*** johnthetubaguy is now known as zz_johnthetubagu18:26
*** EricGonczer_ has quit IRC18:26
*** dave-mccowan has quit IRC18:27
esmuteThe think about not ending in a friday is how productive i'll be during the weekday... i might be brain exhausted or drunk :P18:27
*** Haiying has quit IRC18:27
amrithand as exhibit (a), here we have esmute on a wednesday ;)18:28
SlickNik#link http://doodle.com/ahrvmneuddzi92kn18:28
cp16netesmute: isnt that every day?18:28
cp16net:-P18:28
SlickNik^^ Use this poll instead — to clear up some confusion18:28
SlickNikWill update the link in the page.18:28
esmutecp16net: lol18:29
cp16net:-D18:29
*** Leon_ has quit IRC18:30
SlickNikOkay, would be good if folks could take a minute today to fill out that poll, so I can have a better idea of the week for the Mid-cycle.18:30
*** Leonr has joined #openstack-meeting-alt18:30
*** achanda has joined #openstack-meeting-alt18:30
SlickNikLet me also check with a few folks who would help with organizing this on whether Mon-Wed, or Tue-Thur would be a better option.18:31
*** SumitNaiksatam has joined #openstack-meeting-alt18:31
SlickNik#action SlickNik to follow up on dates for Mid-cycle18:31
SlickNikWill get back to folks after I check on that.18:32
SlickNikAny other questions relating to this?18:32
*** ranjitha has joined #openstack-meeting-alt18:32
*** marcoemorais has quit IRC18:32
*** otherwiseguy has quit IRC18:33
*** achanda has quit IRC18:33
SlickNikOkay, let's move on then18:33
SlickNik#topic Trove Cross Project Liasons18:33
*** openstack changes topic to "Trove Cross Project Liasons (Meeting topic: trove)"18:33
*** achanda has joined #openstack-meeting-alt18:33
*** marcoemorais has joined #openstack-meeting-alt18:33
*** sarob has quit IRC18:33
*** vishwanathj has joined #openstack-meeting-alt18:33
*** ranjitha has quit IRC18:33
*** Haiying has joined #openstack-meeting-alt18:33
SlickNikSo this (Cross Project Liasons) is something that teams across openstack are trying.18:33
*** marcoemorais has quit IRC18:34
*** e0ne has joined #openstack-meeting-alt18:34
*** sgotliv has quit IRC18:34
SlickNikBasically for Cross-Project issues, the idea is that the team would have a go-to point of contact.18:34
*** marcoemorais has joined #openstack-meeting-alt18:34
SlickNikYou've probably already seen some discussion around this on the Mailing List18:34
*** marcoemorais has quit IRC18:34
SlickNik#link https://wiki.openstack.org/wiki/CrossProjectLiaisons18:34
*** achanda has quit IRC18:34
*** marcoemorais has joined #openstack-meeting-alt18:35
*** Leonr has quit IRC18:35
SlickNikThe wiki page identifies the current cross-project groups for which teams are designating liasons.18:35
amrithSlickNik, do you want us to just go and edit the page (to signify volunteering)?18:35
*** Leonr has joined #openstack-meeting-alt18:36
peterstacFrom the page: The liaison should be a core reviewer for the project, but does not need to be the PTL18:36
SlickNikpeterstac: The liason does not _need_ to be a core reviewer.18:36
*** noslzzp has quit IRC18:37
*** Leon_ has joined #openstack-meeting-alt18:37
SlickNikThe only requirement afaik is:18:37
SlickNik1. she be passionate about the cross-project area18:37
SlickNik2. she be available for a cross project meeting (IRC) during which the particular topics might be brought up.18:37
SlickNikDepending on the team they might have a few other responsibilities18:38
*** SridharRamaswamy has quit IRC18:38
SlickNiklike triaging security issues for the vulnerability mgmt one, and getting involved in releases for rel mgmt.18:38
SlickNikAlso there can be more than one person as the liason.18:39
*** noslzzp has joined #openstack-meeting-alt18:39
SlickNikamrith: Updating the wiki page as you volunteer sounds good18:39
*** achanda has joined #openstack-meeting-alt18:39
*** rtomasko has joined #openstack-meeting-alt18:39
*** banix has quit IRC18:40
*** Leonr has quit IRC18:41
*** ranjitha has joined #openstack-meeting-alt18:41
*** dave-mccowan has joined #openstack-meeting-alt18:41
SlickNikAny questions around this?18:41
*** emagana has quit IRC18:41
*** arnaud__ has joined #openstack-meeting-alt18:41
* SlickNik goes off to look at the webpage to see if we have volunteers.18:41
*** Barker has quit IRC18:42
*** emagana has joined #openstack-meeting-alt18:42
*** tonytan4ever has joined #openstack-meeting-alt18:42
peterstacbetter hurry, spots are filling up fast ;)18:42
peterstaconly Stable Branch, Vulnerability management, API Working Group left ...18:42
*** ranjitha has quit IRC18:42
*** pawel-palucki has quit IRC18:43
*** marun has quit IRC18:43
SlickNikpeterstac: There can be more than one18:43
*** radez_g0n3 is now known as radez18:44
*** dave-mccowan_ has joined #openstack-meeting-alt18:44
SlickNikOkay, I'll let folks fill that in at their convenience.18:45
SlickNikAny other questions regarding this?18:45
*** Barker has joined #openstack-meeting-alt18:45
*** dave-mccowan has quit IRC18:45
*** dave-mccowan_ is now known as dave-mccowan18:45
*** arnaud__ has quit IRC18:46
SlickNikFeel free to chat with me if you're interested in one of these roles, but are not sure what it might entail.18:46
SlickNik#topic Open Discussion18:46
*** openstack changes topic to "Open Discussion (Meeting topic: trove)"18:46
amrithI have one ...18:46
*** emagana has quit IRC18:46
amrithbut I'll wait18:46
amrithand go last18:46
cp16neti think you should fill this silence.18:47
SlickNikI'm not sure I see any other topics, so go for it.18:47
amrithThis was about the issue of datastore and flavors18:48
amrithhttps://review.openstack.org/#/c/109824/18:48
amrithI saw a mention that riddhi was going to talk about it at next trove meeting.18:48
amrithI assume that is now18:48
*** mattgriffin has quit IRC18:48
amrithso if it is, I'd like to discuss that.18:48
*** marun has joined #openstack-meeting-alt18:48
*** mattgriffin has joined #openstack-meeting-alt18:49
amrithanyone?18:49
Riddhiamrith: sgoltiv wanted to chat about it18:49
Riddhii think its night time for him though18:49
amrithhe was here earlier, and I saw the comment in the review18:49
amrithhence I bring it up18:49
amriththere was some urgency about this on monday18:49
amrithand therefore I'd like to make sure it doesn't linger18:50
amriththere appear to be two issues18:50
amrith1. whether the api is Restful18:50
Riddhiyeah..he pinged me after that comment..we would discuss about it tomorrow and i will update the patch with the details of what we discussed18:50
amrith2. whether it can be changed given that what was implemented was what was in the spec18:50
amrithso the question is this18:50
amrithif you come to the conclusion that (1) it isn't restful18:50
amrithcan it be changed.18:51
Riddhiyes..i wanted more feedback on this18:51
amrithMy understanding from Monday was that the BP would be RST'ed and then we would review it18:51
amrithis that correct?18:51
amriththis is mostly a question to grapex and SlickNik18:51
amrithdid I understand monday's meeting correctly?18:51
SlickNikamrith: There was an RST'd BP that already merged.18:51
Riddhiyeah..the rst has been approved and is now in trove -specs18:51
grapexamrith: I figured the big stuff had already been discussed18:51
SlickNikamrith: Not sure if you saw it18:51
amrithSlickNik, that went by so quick18:52
*** bradjones has quit IRC18:52
grapexBut if people had more questions we can still talk about it18:52
amrithI was assuming that review meant it would be around for a bit18:52
*** emagana has joined #openstack-meeting-alt18:52
amrithI guess I was wrong18:52
grapexamrith: Well there's still a review for the code, but the Spec BP was approved18:52
amrithalso, the process re: bp's was (I thought) that the BP would be +2'ed when the code +2'ed18:52
grapexwhich makes sense as it was already in the wiki for a long time18:52
amrithI have a bunch of BP's otu there.18:52
amriththey were discussed18:52
amriththey haven't merged.18:52
Riddhithe stuff sgotliv wanted to discuss was if /{tenant_id}/flavors/datastores/versions/{datastore_version_id} is a valid REST api18:52
*** ranjitha has joined #openstack-meeting-alt18:53
SlickNikThe BP is +2'ed when the design is agreed upon, not when the code merges.å18:53
amrithcould I get some reviews (like +2's) on my bp's18:53
Riddhigrapex: https://blueprints.launchpad.net/trove/+spec/associate-flavors-datastores18:53
amrithhave we agreed to the 'design'18:53
amrithon how to handle obsolete oslo modules?18:53
grapexSlickNik: That was my view as well18:53
grapexamrith: Sorry, I'll try to look over more of your blueprints18:53
*** tdink has quit IRC18:53
SlickNikamrith: Does that need to be a BP? It seems more of a housekeeping task to me. We're not really adding new functionality18:54
SlickNikI thought we decided to use a bug instead?18:54
*** tdruiva is now known as tdruiva|away18:54
*** armax has quit IRC18:54
amrithSlickNik, not that I know of. we reviewed the BP's at a monday meeting. I could go and check but I don't know about the decision to use a bug.18:54
amrithI'm happy to do that. just let me know which tree to go bark up.18:55
*** armax has joined #openstack-meeting-alt18:55
grapexSo- does anyone know what sgoltiv's question was?18:55
amrithyes, he had objections to the end points.18:56
amrithhe (and I agree with this) feels that the URL's should not be as in the spec18:56
amrithlet me find his exact words, one second18:56
*** rtomasko has quit IRC18:56
SlickNikamrith: IIRC I'm pretty sure other projects are using bugs, so I'd prefer doing the same.18:56
Riddhihis question was : /{tenant_id}/flavors/datastores/versions/{datastore_version_id}18:56
Riddhithe above url is not RESTful18:56
Riddhihis suggestions were:18:57
Riddhi1. How about sending datastore_version_id as a query parameter18:57
RiddhiOR18:57
*** tdink has joined #openstack-meeting-alt18:57
*** Barker has quit IRC18:57
Riddhi2. /{tenant_id}/datastores/{datastore}/versions/{id}/flavors which is even better.18:57
*** tbarron has quit IRC18:57
amrithSlickNik, ok, I'll kill the BP's.18:57
*** andreykurilin_ has joined #openstack-meeting-alt18:58
SlickNikLooks like the BP mentions the bug in it as well18:58
SlickNik#link https://bugs.launchpad.net/trove/+bug/138078918:58
uvirtbotLaunchpad bug 1380789 in trove "Do not use obsolete modules from oslo-incubator " [Undecided,In progress]18:58
grapexI'll admit, sgoltiv's option #2 seems better to me18:58
amrithdone, BP is history.18:59
grapexBut at this point I think we have devs implementing stuff based on what they think is community consensus only to find they were obeying an echo whose author has been forgotten. :p18:59
*** nshaikh has left #openstack-meeting-alt18:59
*** sarob has joined #openstack-meeting-alt18:59
amrithyes, but this was (I thought) the reason why we thought we'd review it again on Monday.18:59
grapexActually, scratch that19:00
grapexI think the query param is better- that was #1 right- I'm saying I'm ok with some change19:00
grapexbut this has been discussed since this summer19:00
*** otherwiseguy has joined #openstack-meeting-alt19:00
*** nyechiel has quit IRC19:00
SlickNikamrith: IIRC the reason we wanted the RST is to track the BPs in kilo19:01
grapexSo there isn't any urgency, I'd just like everyone to settle on these last questions since we've long since decided we're ok with the idea19:01
*** igormarnat_ is now known as igormarnat19:01
SlickNikI.e. so that we're not merging a BP in kilo without a corresponding spec19:01
*** jmontemayor has quit IRC19:01
*** dims has quit IRC19:01
grapexI've got another question- is the blueprint meeting to be used to announce new specs that are now pull requests in Gerrit, and to give a deadline to approve or deny specs from the past week?19:02
*** Barker has joined #openstack-meeting-alt19:02
grapexAs in, are we saying we want to wait a week to approve specs?19:02
amrithSlickNik, grapex ... there was much discussion about this spec on monday and I know that I said "#idea ... take existing BP and make it an RST and let people comment on it"19:03
amriththat was certainly my intent.19:03
*** marun has quit IRC19:03
*** marun_ has joined #openstack-meeting-alt19:03
amrithI know that sgotliv and others had already expressed concerns on the change19:03
amrithin areas that reflected on the spec/bp.19:03
*** marcoemorais has quit IRC19:04
amrithanyway, let's decide what we want to do procedurally with BP's.19:04
*** shwetaap1 has quit IRC19:04
amrithto grapex question, above, what's the process?19:04
Riddhii agree with grapex: although there is no urgency, we can atleast be on the same page about the implementation..this is the last nitpik with respect to the feature..i still do not see how one REST url is better than the other..19:04
*** ranjitha has quit IRC19:04
SlickNikThe design for a BP is accepted when the spec merges19:04
SlickNikwhich can happen independent of the BP meeting.19:04
*** marcoemorais has joined #openstack-meeting-alt19:04
SlickNikSo the BP meeting is to have a discussion around new specs and iron out any controversial issues that may arise.19:05
*** shwetaap has joined #openstack-meeting-alt19:05
SlickNikWe're not making any "approve" or "deny" requests as part of that meeting.19:05
SlickNikThat happens offline as part of merging the spec in gerrit19:05
*** hachao has quit IRC19:06
grapexSlickNik: Cool19:06
amrithso, a new BP/spec doesn't need to come to the monday meeting.19:06
amrithonly if there is a reason to discuss.19:06
amrithyes?19:06
SlickNikYes19:06
RiddhiSlickNik: got it:)19:06
grapexI also think we should get better about having features go on for months because of minor nitpicks in details such as REST paths19:06
amrithok, what do we do about this spec?19:07
amrithit is now merged.19:07
grapexI get that it can be ugly, but its like if someone's code could be improved in a pull request- make a comment and then hopefully it can be decided in a week or so19:07
*** tdink has quit IRC19:07
*** zz_dimtruck is now known as dimtruck19:07
grapexamrith: I think we just move on revieiwng Riddhi's implementation19:07
*** hareeshp has quit IRC19:08
grapexIf I'm correct, the only blocker is sgoltiv's opinion on what the service.py stuff needs to look like19:08
SlickNikamrith: There's nothing in the spec which prevents us from altering the implementation to change the API endpoint to be more RESTful, so why is this even an issue?19:08
amrithat this point, yes19:08
SlickNikspec is at https://review.openstack.org/#/c/135128/3/specs/kilo/associate-flavors-datastores.rst,cm19:08
amrithSlickNik, the reason I brought it up is that it was discussed in the review that we could discuss in the trove meeting.19:09
*** hareeshp has joined #openstack-meeting-alt19:09
amrithand I didn't want this to linger for too long19:09
amrithsince there was a mention of discussing in the "next trove meeting" I brought it up.19:09
RiddhiSlickNik: yeah, i will discuss this with sgotliv and keep you all in the loop about it19:10
grapexamrith: Sorry. I was really moving us for to close to some kind of agreement on Monday's meeting until SlickNik pointed out he needed the spec for Kilo book keeping, and I was like "drat! Defeated!"19:10
*** aiharos has joined #openstack-meeting-alt19:10
grapexamrith: I still want to push us to come to consenus on this19:10
*** emagana has quit IRC19:10
grapexI think Riddhi should email sgoltiv, CC the cores and will figure out what this last nitpick is19:10
amrithgrapex, I would too, hence I brought this up.19:11
*** emagana has joined #openstack-meeting-alt19:11
*** marun_ has quit IRC19:11
grapexamrith: I think we agree then.19:11
grapexI vote we give this topic a REST!19:11
* grapex rimshot19:11
SlickNikSo the only remaining item is with the last comment on the code review (the actual REST endpoint). The spec isn't an issue here.19:11
SlickNikgrapex: +119:11
*** yamamoto has joined #openstack-meeting-alt19:11
Riddhigrapex: yes..! although I do not clearly right now get the significance of the URL being RESTful or not.. will implement based on the discussion..so the end:)19:11
*** marun_ has joined #openstack-meeting-alt19:11
SlickNikRiddhi: Thanks.19:12
SlickNikPlease follow up with sgotliv.19:12
*** Yuanying_ has joined #openstack-meeting-alt19:12
grapexYou know what? I don't care if an API is RESTful. There, I said it.19:12
RiddhiSlickNik: yup..will do:) will keep you all in the loop19:12
* grapex waits to hear the audience's gasp19:13
*** sgotliv has joined #openstack-meeting-alt19:13
SlickNikAnd on that note. :)19:13
SlickNik#endmeeting19:13
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:13
openstackMeeting ended Wed Nov 19 19:13:14 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-11-19-18.00.html19:13
SlickNikThanks all19:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-11-19-18.00.txt19:13
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-11-19-18.00.log.html19:13
*** emagana_ has joined #openstack-meeting-alt19:13
*** emagana has quit IRC19:13
SlickNikSorry for running over for a bit.19:13
grapexThe bot just recorded that19:13
grapexthat is on my permanent record!19:13
grapexGuess what else... I think C++ is a good language. And at home, I use Windows. EVEN WHEN I'M CODING19:14
SlickNikhee19:14
*** dboik has quit IRC19:15
*** yamamoto has quit IRC19:16
*** marun has joined #openstack-meeting-alt19:16
*** dimtruck is now known as zz_dimtruck19:17
*** kebray has joined #openstack-meeting-alt19:17
*** andreykurilin_ has quit IRC19:17
*** Yuanying_ has quit IRC19:17
* mattgriffin changes his trove weekly meeting calendar event ... time changes, grr19:17
*** marun_ has quit IRC19:19
*** marun has quit IRC19:22
*** jannis_rake-reve has quit IRC19:23
*** HeOS has joined #openstack-meeting-alt19:25
*** armax has quit IRC19:26
SlickNikmattgriffin: I hear ya. It took me a while to get used to the UTC time thing.19:26
*** ranjitha has joined #openstack-meeting-alt19:26
*** tdruiva|away is now known as tdruiva19:26
*** tvoran has left #openstack-meeting-alt19:26
*** dboik has joined #openstack-meeting-alt19:27
*** dboik has quit IRC19:28
*** dboik has joined #openstack-meeting-alt19:28
*** armax has joined #openstack-meeting-alt19:29
*** hareeshp has quit IRC19:29
*** sballe has joined #openstack-meeting-alt19:30
*** aiharos has quit IRC19:30
*** aiharos has joined #openstack-meeting-alt19:30
*** armax has quit IRC19:30
*** markmcclain has joined #openstack-meeting-alt19:30
*** markmcclain has quit IRC19:31
*** aiharos has left #openstack-meeting-alt19:31
*** aiharos has joined #openstack-meeting-alt19:32
*** Barker has quit IRC19:32
*** aiharos has quit IRC19:33
*** julim has quit IRC19:33
*** ivar-laz_ has joined #openstack-meeting-alt19:34
*** ivar-laz_ has quit IRC19:34
*** baoli has quit IRC19:34
*** aiharos has joined #openstack-meeting-alt19:34
*** ivar-laz_ has joined #openstack-meeting-alt19:35
*** Sukhdev has joined #openstack-meeting-alt19:35
*** ddmitriev has quit IRC19:35
*** dboik has quit IRC19:35
*** armax has joined #openstack-meeting-alt19:35
*** niclem has quit IRC19:36
*** nyechiel has joined #openstack-meeting-alt19:36
*** marun has joined #openstack-meeting-alt19:37
*** ivar-lazzaro has quit IRC19:37
*** amitry has joined #openstack-meeting-alt19:37
*** zz_dimtruck is now known as dimtruck19:38
*** ivar-laz_ has quit IRC19:38
*** ivar-lazzaro has joined #openstack-meeting-alt19:39
*** carl_baldwin has quit IRC19:39
*** tdink has joined #openstack-meeting-alt19:39
*** SridharRamaswamy has joined #openstack-meeting-alt19:39
*** hachao has joined #openstack-meeting-alt19:40
*** amitry has quit IRC19:41
*** nyechiel has quit IRC19:41
*** marun_ has joined #openstack-meeting-alt19:42
*** kebray has quit IRC19:43
*** dboik has joined #openstack-meeting-alt19:44
*** marun has quit IRC19:44
*** kebray has joined #openstack-meeting-alt19:44
*** sushilkm has left #openstack-meeting-alt19:44
*** avozza is now known as zz_avozza19:44
*** sarob has quit IRC19:45
*** zz_avozza is now known as avozza19:45
*** carl_baldwin has joined #openstack-meeting-alt19:45
*** satish has quit IRC19:46
*** jmcbride has quit IRC19:46
*** Barker has joined #openstack-meeting-alt19:46
*** jtomasek has joined #openstack-meeting-alt19:47
*** marcoemorais has quit IRC19:47
*** jmcbride has joined #openstack-meeting-alt19:47
*** marcoemorais has joined #openstack-meeting-alt19:47
*** dimtruck is now known as zz_dimtruck19:47
*** marcoemorais has quit IRC19:47
*** marcoemorais has joined #openstack-meeting-alt19:48
*** mattgriffin has quit IRC19:49
*** dboik has quit IRC19:50
*** otherwiseguy has quit IRC19:50
*** noslzzp has quit IRC19:50
*** ivar-laz_ has joined #openstack-meeting-alt19:51
*** marun_ has quit IRC19:51
*** otherwiseguy has joined #openstack-meeting-alt19:52
*** marun_ has joined #openstack-meeting-alt19:52
*** noslzzp has joined #openstack-meeting-alt19:54
*** ivar-lazzaro has quit IRC19:54
*** jmontemayor has joined #openstack-meeting-alt19:55
*** johnsom has joined #openstack-meeting-alt19:55
*** mwang2 has joined #openstack-meeting-alt19:55
*** matrohon has joined #openstack-meeting-alt19:57
*** noslzzp has quit IRC19:58
*** hareeshp has joined #openstack-meeting-alt19:58
*** xgerman has joined #openstack-meeting-alt19:59
sbalukoff#startmeeting Octavia19:59
openstackMeeting started Wed Nov 19 19:59:56 2014 UTC and is due to finish in 60 minutes.  The chair is sbalukoff. Information about MeetBot at http://wiki.debian.org/MeetBot.19:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:59
*** openstack changes topic to " (Meeting topic: Octavia)"20:00
openstackThe meeting name has been set to 'octavia'20:00
sbalukoff#topic Roll Call20:00
*** openstack changes topic to "Roll Call (Meeting topic: Octavia)"20:00
johnsomo/20:00
*** jorgem has joined #openstack-meeting-alt20:00
ajmillero/20:00
*** satish has joined #openstack-meeting-alt20:00
xgermano/20:00
bediso/20:00
jorgemoi!20:00
*** TrevorV has joined #openstack-meeting-alt20:00
bloganhello!20:00
bedis\\o20:00
bediso//20:00
TrevorVo/20:00
*** jwarendt has joined #openstack-meeting-alt20:00
sbalukoffThis is our agenda today: https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda20:00
sbalukoff#link https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda20:00
sbalukoff#topic Octavia hack-a-thon in December20:01
*** openstack changes topic to "Octavia hack-a-thon in December (Meeting topic: Octavia)"20:01
xgermanwill be epic!20:01
sbalukoffSo, not a whole lot to say about this except that it's the week of Dec. 1520:01
*** ivar-laz_ has quit IRC20:01
sbalukoffIf you have not yet RSVPed yet, please do here:20:01
*** emagana_ has quit IRC20:01
sbalukoff#link Octavia hack-a-thon in December20:01
sbalukoffDangit.20:01
*** mattgriffin has joined #openstack-meeting-alt20:02
sbalukoff#link Octavia hack-a-thon in December20:02
sbalukoff...20:02
blogani can't click on that link!20:02
rm_worko/20:02
TrevorVtechnical difficulties thre sbalukoff ?20:02
jorgemI can20:02
*** emagana has joined #openstack-meeting-alt20:02
bedishttp://Octavia%20hack-a-thon%20in%20December/20:02
jorgemit just doesn't do anything :)20:02
bedis:)20:02
xgermanhttps://etherpad.openstack.org/p/octavia-kilo-meetup20:02
*** dboik has joined #openstack-meeting-alt20:02
*** dboik has quit IRC20:03
sbalukoff#link https://etherpad.openstack.org/p/octavia-kilo-meetup20:03
*** gholler has quit IRC20:03
sbalukoffYeah, that.20:03
sbalukoffOk! Anyone have questions about that at this time?20:03
*** dboik has joined #openstack-meeting-alt20:03
jorgemyes20:03
a2hillo/20:03
jorgemCan we setup a video channel of some sort?20:03
sbalukoffYes.20:03
sbalukoffThat is part of the plan, I think.20:04
jorgemI'm going to try and book a VC room for us here at Rackspace so the other devs can participate.20:04
ajmiller+1 even though I'm based in the HP Seattle office, I will be out-of-town for the first two days.  Would like to participate as best I can.20:04
a2hilli was hoping it was a google hangout that we can join/dc as needed20:04
xgermanok, we should be able to have some hangout going20:04
jorgemI've also been whiteboarding with then lately and would love to contribute :)20:04
*** irenab has joined #openstack-meeting-alt20:04
*** tonytan4ever has quit IRC20:05
sbalukoffYeah, I can definitely keep a hangout going all week, eh.20:05
*** emagana_ has joined #openstack-meeting-alt20:05
*** otherwiseguy has quit IRC20:05
a2hillPerfect!20:05
sbalukoffAny other questions about this?20:05
*** grapex has left #openstack-meeting-alt20:05
sbalukoff(I'll be working on a list of tasks to accomplish as the date draws nearer-- probably makes sense to continue what we're already doing, just in high gear, eh.)20:06
jorgemvalé20:06
sbalukoffOk, moving on...20:06
sbalukoff#topic Progress reports20:06
rm_workI think the most useful thing we could do is spend the first three days whiteboarding >_>20:06
*** openstack changes topic to "Progress reports (Meeting topic: Octavia)"20:06
*** emagana has quit IRC20:06
xgermanrm_work +120:06
sbalukoffI will destroy you, rm_work20:06
*** ptoohill has quit IRC20:06
rm_worksbalukoff: I am not kidding tho <_<20:06
xgermanlet's use the high bandwith event for high bandwith tasks20:06
sbalukoffOh, really?20:06
rm_workdestroy me with your amazing whiteboarding :P20:07
sbalukoffHaha20:07
jorgemsbalukoff: Careful he's ambidextrous20:07
jorgem:)20:07
sbalukoff#undo20:07
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x1fe3490>20:07
*** balajiiyer has joined #openstack-meeting-alt20:07
sbalukoffWhat do you want to see whiteboarded?20:07
bloganyeah we need to whiteboard a lot20:07
rm_workA lot of the flows20:07
TrevorVSeriously I might agree with rm_work here, since we should focus on nitty gritty details we've glossed over20:07
jorgemWe've been whiteboarding about agent stuff mostly20:07
sbalukoffGot it.20:07
blogannetworking frontend is a big one20:07
*** marcoemorais has quit IRC20:07
*** balajiiyer has left #openstack-meeting-alt20:07
bloganalso backend as well20:08
rm_workthere are a lot of "oh, right, we need something to deal with that" gotchas that we forget about, unless we trace flows from start to finish20:08
sbalukoffAll right. Can y'all start a list of things you'd like to see whiteboarded at the bottom of the RSVP etherpad?20:08
xgermanwell, we also might want to split the group into multiple whiteboarders20:08
jorgemThe all mighty controller layer needs to be figured out20:08
johnsomYes20:08
jorgemsure20:08
rm_workheartbeat20:08
xgermannot for 0.5?20:08
johnsomI hope to have a WIP out soon20:08
rm_workxgerman: i think we need it for 0.520:08
*** ptoohill has joined #openstack-meeting-alt20:09
*** matrohon is now known as matrohon_20:09
*** Ajay_ has quit IRC20:09
*** noslzzp has joined #openstack-meeting-alt20:09
blogansure can20:09
*** ivar-lazzaro has joined #openstack-meeting-alt20:09
rm_workit ends up being pretty central to the way the amphorae work20:09
jorgem0.5 is just a milestone but we should whiteboard for 1.0 and then figure out how to split it up into 0.5 and 1.0 work20:09
sbalukoff#action Everyone here who wants flows whiteboarded should start a list of the same on RSVP etherpad.20:09
rm_workwhich becomes clear when you whiteboard an amphora's lifecycle20:09
*** marun_ has quit IRC20:09
*** matrohon_ is now known as matrohon20:09
*** banix has joined #openstack-meeting-alt20:09
*** ranjitha has quit IRC20:09
blogani think we shouldn't try to implement 1.0 right now but we should definitely keep 1.0 in mind in that we make it easy to implement 1.020:10
*** david-lyle is now known as david-lyle_afk20:10
sbalukoffWell, yes, and I'd like to see those flows documented in the project much the same way blogan has already started with the amphora lifecycle. :)20:10
sbalukoffBut we can do that after whiteboarding them.20:10
*** jprovazn_afk has quit IRC20:10
rm_workI think a lot of things fall into the category of "ok, this isn't THAT much more complex, and it would save us a rewrite later" bucket20:10
jorgemyes minimal tech debt please20:10
rm_workerr, bucket was a bit redundant there20:10
bloganyeah we need a clear concrete path on how even the small details we glossed over are going to be implemented20:10
xgermanlet's hope so20:10
sbalukoffOk.20:11
*** markmcclain has joined #openstack-meeting-alt20:11
rm_workI am not sure there will be a clear line between 0.5 and 1.020:11
rm_workin reality20:11
sbalukoffAnd here I thought y'all were getting sick of seeing more design documents20:11
sbalukoff*shrug*20:11
rm_workwell, the whiteboarding is about the conversations that happen around it :P20:11
*** ranjitha has joined #openstack-meeting-alt20:12
sbalukoffThere's also no reason we can't start this early (again, referencing blogan's work on the amphora life cycle thus far)20:12
jorgemsbalukoff: Just yours :) eh! jk20:12
sbalukoffHeh!20:12
rm_workanyway, I think we're in agreement, lots of whiteboarding, we can go to your next point I think :)20:12
blogansbalukoff: yeah the amphora lifecycle needs discussions as well as the newtorking driver interfaec, which probably needs its own design doc20:12
sbalukoffblogan: Agreed.20:12
*** cbouch has quit IRC20:12
rm_workblogan: put it in the etherpad :)20:12
sbalukoffYes, please do!20:12
jorgemgood stuff20:13
*** ptoohill-oo has joined #openstack-meeting-alt20:13
sbalukoffOk! Anything else about the hack-a-thon right now?20:13
*** crc32 has joined #openstack-meeting-alt20:13
bloganill make a new etherpad for each one20:13
bloganj/k20:13
xgermanplease link from main etherpad though20:13
*** Yuanying_ has joined #openstack-meeting-alt20:13
sbalukoff#topic Progress reports20:14
*** openstack changes topic to "Progress reports (Meeting topic: Octavia)"20:14
sbalukoffblogan! Please update us on the operator-api20:14
bloganits ready for massive amounts of time from everyone to review, though i need to rebase20:14
sbalukoff4500 lines...20:14
rm_workdid you make those TLS updates?20:15
sbalukoffBut a lot of that is tests.20:15
bloganrm_work: yes20:15
crc32Any one talking or am I netsplit?20:16
rm_workcrc32: we are talking20:16
blogancrc32: i see you20:16
sbalukoff#action blogan to rebase, and then we need people to review: https://review.openstack.org/#/c/121233/20:16
*** adrian_otto has quit IRC20:16
*** dims has joined #openstack-meeting-alt20:16
sbalukoffblogan: How about the network driver interface?20:17
a2hillI progress in reverse20:17
*** otherwiseguy has joined #openstack-meeting-alt20:17
blogani just started research on that this week, put up a very early WIP last night, it needs a LOT of feedback from everyone20:17
sbalukoffa2hill: Er... what?20:17
a2hillheh, ignore me20:17
*** Yuanying_ has quit IRC20:17
a2hillbeen on 'internal' things20:18
sbalukoffaah.20:18
bloganbecause i don't really know much about nova-networks and there's a lot of unanswered questions about neutron as well, and this all needs to work for everyone20:18
xgermanok, we will check it out. Link?20:18
sbalukoffblogan: Sounds good. Do you have a review link?20:18
blogan#link https://review.openstack.org/#/c/130352/20:19
sbalukoffOk, cool.20:19
bloganshit thats' trevors reveiw20:19
TrevorV:D20:19
crc32+120:19
TrevorVPS.  Review mine too20:19
sbalukoffHaha20:19
blogan#link https://review.openstack.org/#/c/135495/20:19
blogani was wondering why it got a +120:19
*** PeterS has joined #openstack-meeting-alt20:20
*** marun has joined #openstack-meeting-alt20:20
sbalukoffOk, on the amphora API:  Well, I just got back from vacation, so I've been playing catch-up. However, I should have a final-ish draft of the spec out in the next day or so, then davidlenwell is going to help me code it (read: He'll totally be the one doing 99% of the work on it.)20:20
sbalukoff;)20:20
bloganlol20:20
davidlenwell:)20:21
sbalukoffAnyway, spec is here:20:21
sbalukoff#link https://review.openstack.org/#/c/126801/20:21
sbalukoffjohnsom: Can you update us on the base-image creation stuff?20:21
johnsomYes.20:22
johnsom#link https://review.openstack.org/#/c/13290420:22
*** PeterSchwaller has quit IRC20:22
johnsomIt's been out there in WIP for a few weeks and now is out for review.20:22
sbalukoffNice!20:22
*** cp16net has left #openstack-meeting-alt20:22
sbalukoffOk, folks, we need eyes on that!20:22
xgerman+120:22
johnsomI would like to discuss some of your comments sbalukoff20:22
sbalukoff#action y'all should review https://review.openstack.org/#/c/13290420:22
johnsomI have built and tested Ubuntu, fedora, and centos VMs.20:23
sbalukoffjohnsom: Live, or in the gerrit comment system?20:23
johnsomThere is tox that tests some stuff in the default ubuntu image using libguestfs20:23
sbalukoffOk, cool.20:23
johnsomLive would be cool, but we could do so in the comments system if everyone will chime in.20:24
*** edhall_ has left #openstack-meeting-alt20:24
johnsomI was happy to see most of your comments were about parts I borrowed from other projects.  grin20:24
sbalukoffLet's actually see if we can get through the rest of the agenda and then hit this topic during open discussion. If we don't have time to talk then, we can continue afterward.20:24
johnsomSounds good20:24
sbalukoffjohnsom: Yeah, I suspected there was copy-pasta going on. Because you actually type with good grammar. ;)20:25
mwang2is that possible that we wrap up a document which lists all of the review standards there20:25
*** nyechiel has joined #openstack-meeting-alt20:25
sbalukoffmwang2: Yes, we can totally do this. We've got a start in the HACKING.rst, but we can formalize other things as well. (like my bias against .md files. ;) )20:25
*** ivar-lazzaro has quit IRC20:26
johnsom.md files borrowed from other Openstack projects...  grin20:26
sbalukoffAnyway, please folks, have a look at johnsom's review above, eh!20:26
mwang2that will be great20:26
blogani should take a look at it today sometime20:26
*** marcoemorais has joined #openstack-meeting-alt20:26
xgermanmaybe sbalukoff can write some converter :-)20:26
sbalukoffmwang2: Would you like to take an initial stab at writing that review standards doc and/or amending what we've got in HACKING.rst?20:27
sbalukoffxgerman: Heh! Well, for the .md files in johnsom's review, the converter would be "cp"20:28
sbalukoffOr 'mv'20:28
*** ptoohill-oo has quit IRC20:28
*** satish_ has joined #openstack-meeting-alt20:28
bloganor rm20:28
sbalukoffXD20:28
*** marcoemorais has quit IRC20:28
johnsomI like rm20:28
xgerman+120:28
sbalukoffYeah, one-line doc files aren't all that useful, in most cases.20:28
*** marcoemorais has joined #openstack-meeting-alt20:28
* bedis propose a match rm -f 20:28
sbalukoffAnyway, mwang2: Do you mind if I assign that review standards doc to you? I'd be happy to work with you on it.20:29
sbalukoff(Did she disappear?)20:30
sbalukoffOk, let's keep going...20:30
bloganaction it, she can't decline it then!20:30
mwang2ok20:30
sbalukoffHaha!20:30
sbalukoff#action mwang2 to take initial stab at review standards doc. sbalukoff to work with her on this.20:30
bloganmwang2: if there are standards you are unsure of just list thsoe out as well20:30
mwang2ok20:30
sbalukoffrm_work: Can you give us an update on the TLS security stuff you've been working on?20:31
*** sarob has joined #openstack-meeting-alt20:31
rm_worksbalukoff: most of the initial stuff has been checked in, fixing up the Barbican impl right now20:31
*** nyechiel has quit IRC20:31
sbalukoffGreat!20:31
rm_workbut still need more eyes on the main TLS architecture spec20:31
sbalukoffCool. Link?20:31
rm_workspecifically, eyes that have security experience20:31
rm_workerr20:32
rm_workweeeeelll it might have merged20:32
*** johnma has left #openstack-meeting-alt20:32
sbalukoffYeah, I totally merged it.20:32
sbalukoffI'm pretty sure.20:32
rm_workyep :P20:32
rm_workhttps://review.openstack.org/#/c/130659/20:32
rm_workwell, we can always patch it20:32
*** jmcbride has quit IRC20:32
sbalukoffWhat kind of feedback are you looking for?20:32
sbalukoffYes we can.20:32
rm_workJust making sure I didn't miss anything20:32
rm_workwe're talking about security here20:32
*** satish has quit IRC20:32
xgermanbash had holes for years... so20:33
rm_workand this is detailing the workflow for TLS end-to-end for amphorae lifecycle and customer TLS data20:33
sbalukoffWell, you almost certainly missed something. Otherwise it wouldn't be security, eh. ;) But I get your point.20:33
bloganim pretty sure we'll have everything secure on the first go round20:33
rm_workyeah, definitely. 100% unbreakable20:33
bloganwe should announce that on twitter20:33
davidlenwellfamous last words20:33
sbalukoffHaha20:33
xgermanthat will get us some free pen tests20:34
bloganexactly20:34
sbalukoffOk, so anyone with security chops people on their team should point them at that spec.20:34
davidlenwellsbalukoff: get dustin and deva to look at it20:34
sbalukoff#action Octavia team members with access to security people should have them look at:  https://review.openstack.org/#/c/130659/20:34
sbalukoffdavidlenwell: I will.20:34
sbalukoffOk! amiller and / or TrevorV: update on the compute driver interface?20:35
TrevorVI've got a few reviews up and waiting for some vision on them20:35
sbalukoffGreat!20:35
sbalukoffPlease hit us with the links.20:35
bloganit'd be almost done if would catch everything on the first pass20:35
TrevorVI got some great feedback from sbalukoff and blogan just yesterday and am currently making changes to one of them20:35
bloganif i20:35
TrevorVI'm actually about to push a change20:36
blogan"great feedback" eh20:36
TrevorVLet me link them really quick20:36
sbalukoffHaha!20:36
TrevorV#link https://review.openstack.org/#/c/13035220:36
TrevorV#link https://review.openstack.org/#/c/13064020:36
TrevorV#link https://review.openstack.org/#/c/13310820:36
*** jmcbride has joined #openstack-meeting-alt20:36
ajmillerAs far as I am aware, my part of the spec is done.  TrevorV and I have had discussions about what should be defined where, and we think we have that worked out.20:36
TrevorVConveniently they are dependency chained together20:36
TrevorV+1 ajmiller20:37
sbalukoffExcellent, eh!20:37
*** jmcbride1 has joined #openstack-meeting-alt20:37
sbalukoff#action eyes on the above review links20:37
*** jmcbride1 has quit IRC20:37
sbalukoffLet's see...20:37
blogandoes anyone think that OCtavia will need to get amphorae by name?20:37
*** jmcbride1 has joined #openstack-meeting-alt20:37
bloganif you do, then go comment on the review20:38
*** padkrish has quit IRC20:38
sbalukoff*crickets*20:38
*** jmcbride has quit IRC20:38
a2hillit is a convenient way for a user to query for it20:38
*** zz_gondoi is now known as gondoi20:38
a2hilluuid is hard to remember20:38
sbalukoffa2hill: But... will a user ever actually being querying for it?20:38
TrevorVa2hill they user isn't ever going to know about an "amphora" though20:38
TrevorVthe**20:38
sbalukoffhostnames are going to be auto-generated too, eh.20:38
*** julim has joined #openstack-meeting-alt20:38
johnsomRight, I *hope* the user has no concept of amphora20:38
sbalukoffYep.20:38
*** sunnyr has quit IRC20:39
*** ajo has joined #openstack-meeting-alt20:39
sbalukoffOnly the operator can see behind the curtain.20:39
sbalukoff(Or at least, that's how it should be.)20:39
xgermanwell, there is always the operator side of it20:39
a2hilli suppose not, that was cleared up20:39
*** julim has quit IRC20:39
a2hillbait car!20:39
TrevorVxgerman the operator wouldn't have need of a name either, since everything should be known by the operator, right?20:39
sbalukoffxgerman: blogan's point was that we'll always know the UUID whenever we know the name.20:39
sbalukoffTrevorV: That was my thought too.20:40
TrevorVI hope the operator would have full insight ha ha20:40
*** amcrn has joined #openstack-meeting-alt20:40
xgermanyou would hope...20:40
sbalukoffAnyway, if you think we'll need to look up by name, please read through and comment on the review!20:40
sbalukoffOk!20:40
sbalukoffSo, controller update!20:40
johnsomWe don't want to name our amphora because we don't want to get too attached to them....  grin20:40
sbalukoffjohnsom: Are you working on this already (blueprint is assigned to you)20:40
johnsomYes20:40
sbalukoffOk, cool, can you give us an update?20:41
bloganqueue rm_work's "they're cattle"20:41
rm_worktechnically dougwig coined that20:41
xgermanlol20:41
johnsomI have started working on it, but stopped to address the burning need with the base-image.  I am back on it now20:41
sbalukoffamphorae are so cattle.20:41
bloganrm_work: technically there were many sessions on it at the summit20:41
johnsomHope to have some WIP stuff posted soon20:41
*** julim has joined #openstack-meeting-alt20:41
sbalukoffjohnsom: Excellent!20:41
rm_workah20:41
a2hillYea, a few were actually titled that20:41
bloganjohnsom: is there a spec out or is that what you're working on?20:42
rm_workjohnsom: you are working on "the controller"?20:42
johnsomI am working on "the controller spec"20:42
rm_workwe were doing a lot of controller-related whiteboarding here yesterday, and it's looking like whatever we are calling "the controller" is really just a collection of agents20:42
bloganexcellent20:42
johnsomYes, which aligns with my thinking too20:42
rm_workthis is the #1 thing we'll need to whiteboard I think20:43
xgermanagreed20:43
johnsomAgreed20:43
blogan#1a20:43
rm_workI wouldn't expect that spec to be finalized before the meetup20:43
blogan#1b is networking20:43
rm_workwell, I think most of the other stuff on the list falls out of the controller discussion20:43
sbalukoffHeh!20:43
johnsomHahaha, funny man.  I expect a lot of discussion20:43
xgermanyeah, if you guys have whiteboards I am wondering if you cna take pictures and forward20:43
rm_workthe HP offices have LOTS of whiteboards, right?20:44
sbalukoffOk, so: johnsom, it would be great if you could commit a WIP review as soon as you're able, with the understanding it'll probably take several weeks and at least one good whiteboarding session at the hack-a-thon to finalize it.20:44
rm_workWe will need approximale 1000 sqft of whiteboard20:44
rm_work*approximately20:44
xgermanwe have ways to erase whiteboards20:44
johnsomYes, that is the plan20:44
bloganwe will also need some boxing gloves20:44
sbalukoffSweet.20:44
rm_workxgerman: erase whiteboards? blasphemy20:44
sbalukoffHaha20:45
sbalukoffOk!20:45
sbalukoffmoving on...20:45
sbalukoff#topic Other reviews Needing Attention ( https://review.openstack.org/#/q/stackforge/octavia+status:open,n,z )20:45
*** openstack changes topic to "Other reviews Needing Attention ( https://review.openstack.org/#/q/stackforge/octavia+status:open,n,z ) (Meeting topic: Octavia)"20:45
sbalukoffDoes anyone else here want to point out a review that's not yet been mentioned that needs eyes?20:45
rm_workthe Barbican impl is up now20:45
bloganspare amphora lifecycle management20:45
blogan#link https://review.openstack.org/#/c/130424/20:45
blogandon't think that actually got a call out to reveiw20:45
rm_work#link https://review.openstack.org/#/c/132580/20:45
rm_workjust fixed the merge conflict, should be good now20:46
sbalukoffNice!20:46
*** jtomasek has quit IRC20:46
*** achanda has quit IRC20:46
sbalukoffIt's great to see all the progress on this, y'all!20:46
sbalukoffFeel like we've got good momentum going, so let's keep at it, eh!20:46
*** padkrish has joined #openstack-meeting-alt20:46
sbalukoffAny other reviews needing attention?20:47
sbalukoff#topic Open Discussion20:47
*** openstack changes topic to "Open Discussion (Meeting topic: Octavia)"20:48
*** hareeshp has quit IRC20:48
sbalukoffjohnsom: Ok, let's talk about the base-image review20:48
johnsomCool.  So, your comment about dropping the RedHat tribe... Fedora and CentOS where in the spec and we get most of that free from upstream.20:49
sbalukoffOk, that's fine. Do we have a way to test the code via CI?20:49
johnsomI would like to keep them as options, but make it clear they are experimental.20:49
johnsomYeah, we could enable the tox to also build and look at those if we feel the need20:49
sbalukoffI'm OK with that, I suppose, though I'd be happier if they weren't experimental (and testable via CI).20:49
sbalukoffRight.20:50
xgermanwell, I would assume rohara would have enough interest in those OS20:50
sbalukoffI honestly don't expect many people to use an amphora image other than the one  that is under primary support.20:50
sbalukoffUnless they happen to work for RedHat or something. XD20:50
johnsomI can add them to the tox if you would like.  It will just make it take three times as long20:50
johnsomOr we can do that later...20:51
xgermanI am for later20:51
sbalukoffLet's worry about it later.20:51
johnsomExcellent answer20:51
johnsomgrin20:51
* rm_work kicks the rock down the road a bit20:51
johnsomNext up, the init scripts.  I put them in to have something that supports reboots, etc.20:51
johnsomI expected that when the code lands that manages all of those haproxy instances would update/remove20:52
sbalukoffRight, let's not do them for now. The scripts davidlenwell and I will be writing will control the haproxy instances, including after reboot.20:52
sbalukoffLet's not even put the init scripts in there right now. They're not going to be useful at all. :/20:52
davidlenwellagreed20:53
johnsomOk, so, remove them from the commit or disable?20:53
sbalukoffRemove them.20:53
davidlenwell+120:53
johnsomOk.  The upstart I wrote has respawn working for haproxy.  You might want to borrow that for your scripts, etc.20:53
sbalukoffThanks for the heads up!20:54
*** DuaneDeC7 has quit IRC20:54
sbalukoffAnything else you'd like to discuss about this review live?20:54
johnsomREADME.md these came from another project.  Nuke 'em, or do you really want me to convert those?  I pulled them forward because they seemed to still apply20:55
*** achanda has joined #openstack-meeting-alt20:55
*** mattgriffin has quit IRC20:55
sbalukoffSo, if we're going to have document files at all, I want them to be .rst.20:55
*** DuaneDeC7 has joined #openstack-meeting-alt20:55
*** emagana_ has quit IRC20:55
johnsomSame thing with the nonlocal_bind, that came from the upstream tripleo haproxy configs.20:55
sbalukoffAnd if the documentation in there is still useful, let's convert them.20:55
*** hareeshp has joined #openstack-meeting-alt20:55
sbalukoffBut they are only 1 line (of poorly written English)20:55
sbalukoffSo I'm not sure they're actually useful.20:55
xgermandid we ever vote on rst vs. md20:55
xgerman?20:56
johnsomAgreed, they do not have good grammar20:56
bloganthat was your grammar don't lie20:56
sbalukoffxgerman: I'd rather just use one standard, and everything else with more complication is using .rst in this project.20:56
sbalukoffSo, let's just keep going with .rst20:56
johnsomHaha, go look at that sahara project files.... grin20:56
sbalukoffI don't see a compelling reason to support .md20:56
bloganlol20:56
xgermanwell, I don't liek converting for the sake of converting20:57
johnsomYeah, it seems like every project has a mix in OpenStack land20:57
sbalukoffSure, but we're talking about 3 1-line files which will probably be removed anyway.20:57
*** ajo has quit IRC20:57
sbalukoffLet's not do that. XD20:57
*** ivar-lazzaro has joined #openstack-meeting-alt20:57
bloganwe need to make an Openstack Document Format Working Group20:58
*** ajo has joined #openstack-meeting-alt20:58
xgerman+120:58
sbalukoffblogan: I'm willing to bet there already is one, probably in the docs project, but I'll bet they get ignored a lot.20:58
xgermanwe can state a strong preference but I don't want to force people borrowing stuff to convert every change the donating project does20:58
sbalukoff(Especially if in some projects "the code is the documentation" is the prevailing attitude.)20:58
sbalukoffxgerman: I'm OK with that.20:59
sbalukoffBut realize I'm probably going to complain whenever I see a .md file.20:59
sbalukoff:)20:59
sbalukoffOk! 20 seconds left!20:59
*** emagana_ has joined #openstack-meeting-alt20:59
sbalukoff#endmeeting20:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:59
openstackMeeting ended Wed Nov 19 20:59:55 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/octavia/2014/octavia.2014-11-19-19.59.html20:59
*** irenab has quit IRC20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/octavia/2014/octavia.2014-11-19-19.59.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/octavia/2014/octavia.2014-11-19-19.59.log.html21:00
sbalukoffThanks folks!21:00
jorgemthanks21:00
*** DuaneDeC7 has quit IRC21:00
*** SridharRamaswamy has quit IRC21:00
johnsomThanks sbalukoff21:00
*** e0ne has quit IRC21:00
xgermanthanks21:00
bloganthanks everyone21:00
bedisthanks :)21:00
sbalukoffbedis: Ready for a call?21:00
*** xgerman has left #openstack-meeting-alt21:00
bedisyes21:01
bedisbut we need a conf call bridge21:01
bedisI can setup one21:01
bedisor we can chat on a dedicated channel on freenode21:01
*** ranjitha has quit IRC21:01
*** emagana_ has quit IRC21:01
*** emagana has joined #openstack-meeting-alt21:02
sbalukoffbedis: Whatever you would prefer.21:02
sbalukoffI'm happy to chat via text if that's easier.21:02
bedislet me setup a conf call bridge :)21:02
sbalukoffOk!21:02
aiharosbedis: PM the call info21:03
*** hareeshp has quit IRC21:03
bedisyep21:04
*** Yuanying_ has joined #openstack-meeting-alt21:04
*** johnbelamaric_ has joined #openstack-meeting-alt21:04
*** johnbelamaric has quit IRC21:04
*** julim has quit IRC21:04
sbalukoffFWIW, I could get a phone conference bridge going right now too, if you'd like!21:07
*** julim has joined #openstack-meeting-alt21:07
*** mattgriffin has joined #openstack-meeting-alt21:08
*** Yuanying_ has quit IRC21:08
*** noslzzp has quit IRC21:09
*** niclem has joined #openstack-meeting-alt21:09
*** achanda_ has joined #openstack-meeting-alt21:09
*** andreykurilin_ has joined #openstack-meeting-alt21:09
*** otherwiseguy has quit IRC21:09
*** ivar-lazzaro has quit IRC21:10
*** ivar-lazzaro has joined #openstack-meeting-alt21:10
*** otherwiseguy has joined #openstack-meeting-alt21:10
*** noslzzp has joined #openstack-meeting-alt21:11
*** shakamunyi_ has joined #openstack-meeting-alt21:12
*** achanda has quit IRC21:12
*** nyechiel has joined #openstack-meeting-alt21:13
*** yamamoto has joined #openstack-meeting-alt21:14
*** johnbelamaric_ has quit IRC21:15
*** ivar-lazzaro has quit IRC21:15
*** johnbelamaric_ has joined #openstack-meeting-alt21:15
*** sunnyr has joined #openstack-meeting-alt21:16
*** achanda_ has quit IRC21:17
*** achanda has joined #openstack-meeting-alt21:17
*** yamamoto has quit IRC21:18
*** jwarendt has quit IRC21:18
*** avozza is now known as zz_avozza21:20
*** zz_avozza is now known as avozza21:20
*** tdink has quit IRC21:23
*** phil_h has quit IRC21:23
*** armax has quit IRC21:25
*** tdink has joined #openstack-meeting-alt21:25
*** gyee has quit IRC21:26
*** sigmavirus24 is now known as sigmavirus24_awa21:26
*** achanda has quit IRC21:27
*** emagana has quit IRC21:27
*** emagana has joined #openstack-meeting-alt21:28
*** amrith is now known as _amrith_21:29
*** gyee has joined #openstack-meeting-alt21:30
*** armax has joined #openstack-meeting-alt21:31
*** achanda has joined #openstack-meeting-alt21:31
*** gyee has quit IRC21:31
*** emagana has quit IRC21:33
*** baoli has joined #openstack-meeting-alt21:33
*** sunnyr has quit IRC21:34
*** nyechiel has quit IRC21:34
*** sarob has quit IRC21:34
*** Sukhdev has quit IRC21:34
*** tdruiva has quit IRC21:37
*** jorgem has quit IRC21:38
*** tdruiva has joined #openstack-meeting-alt21:38
*** ptoohill has quit IRC21:41
*** BrianB_ has quit IRC21:41
*** mfedosin_ has joined #openstack-meeting-alt21:42
*** salv-orlando_ has joined #openstack-meeting-alt21:44
*** salv-orlando has quit IRC21:44
*** salv-orlando_ is now known as salv-orlando21:44
*** ptoohill has joined #openstack-meeting-alt21:45
*** emagana has joined #openstack-meeting-alt21:46
*** sunnyr has joined #openstack-meeting-alt21:47
*** vishwanathj has quit IRC21:48
*** carl_baldwin has quit IRC21:51
*** zehicle has quit IRC21:54
*** carl_baldwin has joined #openstack-meeting-alt21:54
*** emagana has quit IRC21:56
*** emagana has joined #openstack-meeting-alt21:56
*** ptoohill has quit IRC21:56
*** jorgem has joined #openstack-meeting-alt21:56
*** ptoohill has joined #openstack-meeting-alt21:57
*** jorgem has left #openstack-meeting-alt21:58
*** padkrish has quit IRC21:58
*** shakamunyi_ has quit IRC21:59
*** ptoohill has quit IRC21:59
*** esker has joined #openstack-meeting-alt21:59
*** ptoohill has joined #openstack-meeting-alt21:59
*** padkrish has joined #openstack-meeting-alt22:00
*** SridharRamaswamy has joined #openstack-meeting-alt22:01
*** emagana has quit IRC22:02
*** TrevorV has left #openstack-meeting-alt22:02
*** emagana has joined #openstack-meeting-alt22:03
*** emagana has quit IRC22:07
*** andreykurilin_ has quit IRC22:08
*** ivar-lazzaro has joined #openstack-meeting-alt22:08
*** andreykurilin_ has joined #openstack-meeting-alt22:08
*** Sukhdev has joined #openstack-meeting-alt22:08
*** sergef has quit IRC22:09
*** banix has quit IRC22:09
*** shwetaap has quit IRC22:10
*** mwagner_lap has quit IRC22:10
*** ajo has quit IRC22:12
*** johnbelamaric_ has quit IRC22:13
*** Haiying has quit IRC22:13
*** emagana has joined #openstack-meeting-alt22:16
*** nyechiel has joined #openstack-meeting-alt22:16
*** jmcbride1 has quit IRC22:17
*** johnbelamaric_ has joined #openstack-meeting-alt22:18
*** matrohon has quit IRC22:18
*** johnbelamaric_ has quit IRC22:18
*** sigmavirus24_awa is now known as sigmavirus2422:18
*** pnavarro has quit IRC22:18
*** ptoohill has quit IRC22:20
*** nyechiel has quit IRC22:21
*** nyechiel has joined #openstack-meeting-alt22:22
*** ptoohill has joined #openstack-meeting-alt22:25
*** radez is now known as radez_g0n322:27
*** kevinbenton has joined #openstack-meeting-alt22:27
*** dprince has quit IRC22:28
*** baoli_ has joined #openstack-meeting-alt22:28
*** ptoohill has quit IRC22:28
*** jmcbride has joined #openstack-meeting-alt22:28
*** jmcbride has quit IRC22:28
*** jmcbride has joined #openstack-meeting-alt22:28
*** baoli has quit IRC22:29
*** marun has quit IRC22:29
*** tedross has quit IRC22:30
*** ptoohill has joined #openstack-meeting-alt22:30
*** ptoohill has quit IRC22:30
*** DuaneDeC_ has joined #openstack-meeting-alt22:33
*** emagana has quit IRC22:34
*** emagana has joined #openstack-meeting-alt22:35
*** shohel02_ has quit IRC22:37
*** esker has quit IRC22:38
*** baoli_ has quit IRC22:39
*** baoli has joined #openstack-meeting-alt22:39
*** emagana has quit IRC22:39
*** nyechiel has quit IRC22:40
*** nyechiel has joined #openstack-meeting-alt22:40
*** marun has joined #openstack-meeting-alt22:42
*** _amrith_ is now known as amrith22:47
*** marun_ has joined #openstack-meeting-alt22:49
*** teran has joined #openstack-meeting-alt22:49
*** dboik has quit IRC22:49
*** mattgriffin has quit IRC22:50
*** DuaneDeC_ has quit IRC22:50
*** david-lyle_afk is now known as david-lyle22:50
*** marun has quit IRC22:50
*** tdink has quit IRC22:51
*** tdink has joined #openstack-meeting-alt22:53
*** gyee has joined #openstack-meeting-alt22:55
*** emagana has joined #openstack-meeting-alt22:55
*** jmcbride has quit IRC22:55
*** gyee has quit IRC22:55
*** betsy has quit IRC22:56
*** hockeynut_ has joined #openstack-meeting-alt22:56
*** mattgriffin has joined #openstack-meeting-alt22:57
*** tdruiva has quit IRC22:58
*** nyechiel has quit IRC23:00
*** hockeynut_ has quit IRC23:01
*** satish_ has quit IRC23:02
*** mwagner_lap has joined #openstack-meeting-alt23:02
*** tdink has quit IRC23:02
*** otherwiseguy has quit IRC23:04
*** avozza is now known as zz_avozza23:05
*** ivar-laz_ has joined #openstack-meeting-alt23:05
*** ivar-laz_ has quit IRC23:06
*** armax has quit IRC23:06
*** ivar-laz_ has joined #openstack-meeting-alt23:07
*** shohel02 has joined #openstack-meeting-alt23:08
*** zz_avozza is now known as avozza23:08
*** ivar-lazzaro has quit IRC23:08
*** gondoi is now known as zz_gondoi23:10
*** Barker has quit IRC23:10
*** markmcclain has quit IRC23:11
*** shohel02 has quit IRC23:12
*** hareeshp has joined #openstack-meeting-alt23:14
*** dalgaaf__ has quit IRC23:17
*** jmcbride has joined #openstack-meeting-alt23:17
*** avozza is now known as zz_avozza23:17
*** gyee has joined #openstack-meeting-alt23:18
*** zz_avozza is now known as avozza23:18
*** hareeshp has quit IRC23:19
*** carl_baldwin has quit IRC23:19
*** jmcbride has quit IRC23:20
*** mlavalle has quit IRC23:21
*** shohel02 has joined #openstack-meeting-alt23:22
*** aiharos has quit IRC23:22
*** shohel02 has quit IRC23:26
*** EricGonczer_ has joined #openstack-meeting-alt23:26
*** EricGonczer_ has quit IRC23:30
*** ivar-laz_ has quit IRC23:30
*** jmontemayor has quit IRC23:31
*** juzuluag has quit IRC23:32
*** sgordon_ has quit IRC23:33
*** marun_ has quit IRC23:34
*** tdink_ has joined #openstack-meeting-alt23:35
*** AJK__ has quit IRC23:35
*** sigmavirus24 is now known as sigmavirus24_awa23:37
*** Leon_ has quit IRC23:38
*** kebray has quit IRC23:39
*** kebray has joined #openstack-meeting-alt23:39
*** julim has quit IRC23:39
*** padkrish has quit IRC23:40
*** padkrish has joined #openstack-meeting-alt23:41
*** Adri2000 has quit IRC23:42
*** ycombinator_ has joined #openstack-meeting-alt23:43
*** tdink_ has quit IRC23:46
*** noslzzp has quit IRC23:46
*** sarob has joined #openstack-meeting-alt23:46
*** Riddhi has quit IRC23:48
*** Adri2000 has joined #openstack-meeting-alt23:49
*** Adri2000 has quit IRC23:49
*** Adri2000 has joined #openstack-meeting-alt23:49
*** richm has quit IRC23:50
*** shohel02 has joined #openstack-meeting-alt23:50
*** tdink_ has joined #openstack-meeting-alt23:51
*** ptoohill has joined #openstack-meeting-alt23:51
*** esker has joined #openstack-meeting-alt23:54
*** andreykurilin_ has quit IRC23:55
*** shohel02 has quit IRC23:55
*** atiwari has quit IRC23:55
*** pballand has quit IRC23:57
*** ycombinator_ has quit IRC23:58
*** mattgriffin has quit IRC23:59

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