Wednesday, 2015-03-11

*** Riddhi has quit IRC00:01
*** jogo has left #openstack-meeting-alt00:05
*** SridharRamaswam1 has quit IRC00:05
*** e0ne has quit IRC00:06
*** dteselkin has quit IRC00:08
*** meow-nofer_ has quit IRC00:08
*** katyafervent has quit IRC00:08
*** IgorYozhikov has quit IRC00:08
*** pashkin has quit IRC00:08
*** marun has quit IRC00:09
*** katyafervent has joined #openstack-meeting-alt00:10
*** pashkin has joined #openstack-meeting-alt00:13
*** IgorYozhikov has joined #openstack-meeting-alt00:15
*** meow-nofer_ has joined #openstack-meeting-alt00:16
*** dteselkin has joined #openstack-meeting-alt00:17
*** meow-nofer_ has quit IRC00:17
*** IgorYozhikov has quit IRC00:17
*** pashkin has quit IRC00:17
*** dteselkin has quit IRC00:17
*** katyafervent has quit IRC00:17
*** katyafervent has joined #openstack-meeting-alt00:18
*** tsekiyama has quit IRC00:18
*** achanda has quit IRC00:18
*** achanda has joined #openstack-meeting-alt00:18
*** sdake_ has joined #openstack-meeting-alt00:19
*** zehicle_ has joined #openstack-meeting-alt00:20
*** dims_ has joined #openstack-meeting-alt00:20
*** kozhukalov has quit IRC00:20
*** rmoe has quit IRC00:21
*** mtanino has quit IRC00:21
*** xgerman_ has quit IRC00:22
*** pashkin has joined #openstack-meeting-alt00:22
*** dims has quit IRC00:22
*** dims_ has quit IRC00:22
*** meow-nofer_ has joined #openstack-meeting-alt00:23
*** dims has joined #openstack-meeting-alt00:23
*** achanda has quit IRC00:23
*** dteselkin has joined #openstack-meeting-alt00:24
*** gokrokve has quit IRC00:24
*** katyafervent has quit IRC00:24
*** dteselkin has quit IRC00:24
*** pashkin has quit IRC00:24
*** meow-nofer_ has quit IRC00:24
*** IgorYozhikov has joined #openstack-meeting-alt00:25
*** ivar-lazzaro has quit IRC00:25
*** annashen has quit IRC00:26
*** katyafervent has joined #openstack-meeting-alt00:27
*** Tango has quit IRC00:29
*** dteselkin has joined #openstack-meeting-alt00:30
*** Riddhi has joined #openstack-meeting-alt00:31
*** pashkin has joined #openstack-meeting-alt00:31
*** meow-nofer_ has joined #openstack-meeting-alt00:32
*** kzaitsev has quit IRC00:33
*** david-lyle_afk has quit IRC00:34
*** hongbin has left #openstack-meeting-alt00:34
*** egallen has quit IRC00:34
*** rmoe has joined #openstack-meeting-alt00:40
*** spzala has joined #openstack-meeting-alt00:43
*** shwetaap has joined #openstack-meeting-alt00:44
*** sarob has joined #openstack-meeting-alt00:45
*** yamamoto has quit IRC00:47
*** eghobo has quit IRC00:51
*** ivar-lazzaro has joined #openstack-meeting-alt01:09
*** eghobo has joined #openstack-meeting-alt01:10
*** ChuckC has quit IRC01:10
*** yamamoto has joined #openstack-meeting-alt01:15
*** zz_dimtruck is now known as dimtruck01:18
*** suro_ has quit IRC01:19
*** crc32 has joined #openstack-meeting-alt01:20
*** crc32 has quit IRC01:20
*** david-lyle_afk has joined #openstack-meeting-alt01:21
*** crc32 has joined #openstack-meeting-alt01:22
*** echoingumesh has quit IRC01:24
*** echoingumesh has joined #openstack-meeting-alt01:25
*** ivar-lazzaro has quit IRC01:25
*** annashen has joined #openstack-meeting-alt01:26
*** kebray has quit IRC01:28
*** dims has quit IRC01:28
*** dims has joined #openstack-meeting-alt01:29
*** noslzzp has joined #openstack-meeting-alt01:30
*** echoingumesh has quit IRC01:30
*** salv-orlando has quit IRC01:30
*** zehicle_ has quit IRC01:30
*** devlaps has joined #openstack-meeting-alt01:31
*** annashen has quit IRC01:31
*** dims has quit IRC01:34
*** banix has quit IRC01:36
*** slagun has joined #openstack-meeting-alt01:39
*** SumitNaiksatam has quit IRC01:39
*** dims has joined #openstack-meeting-alt01:40
*** stan_lagun has quit IRC01:42
*** ChuckC has joined #openstack-meeting-alt01:42
*** pmalik has quit IRC01:43
*** ChuckC has quit IRC01:46
*** ChuckC has joined #openstack-meeting-alt01:47
*** devlaps has quit IRC01:51
*** rwsu is now known as rwsu-afk01:52
*** suro_ has joined #openstack-meeting-alt01:54
*** dims_ has joined #openstack-meeting-alt01:55
*** dims has quit IRC01:58
*** Riddhi has quit IRC01:59
*** Riddhi has joined #openstack-meeting-alt01:59
*** woodster_ has quit IRC02:00
*** noslzzp has quit IRC02:00
*** adrian_otto has joined #openstack-meeting-alt02:02
*** sdake_ has quit IRC02:04
*** sdake_ has joined #openstack-meeting-alt02:05
*** eghobo has quit IRC02:05
*** EricGonczer_ has joined #openstack-meeting-alt02:06
*** harlowja_ is now known as harlowja_away02:09
*** yamahata has quit IRC02:13
*** sankarshan_away is now known as sankarshan02:16
*** suro_ has quit IRC02:18
*** sdake_ has quit IRC02:20
*** vishwana_ has quit IRC02:24
*** gokrokve has joined #openstack-meeting-alt02:26
*** EricGonczer_ has quit IRC02:28
*** coolsvap has joined #openstack-meeting-alt02:29
*** erkules_ has joined #openstack-meeting-alt02:29
*** salv-orlando has joined #openstack-meeting-alt02:31
*** erkules has quit IRC02:32
*** Riddhi has quit IRC02:33
*** nelsnelson has joined #openstack-meeting-alt02:33
*** david-lyle_afk has quit IRC02:36
*** salv-orlando has quit IRC02:38
*** kfarr has quit IRC02:40
*** sdake_ has joined #openstack-meeting-alt02:41
*** sdake_ has quit IRC02:45
*** shwetaap has quit IRC02:48
*** jckasper has joined #openstack-meeting-alt02:51
*** spzala has quit IRC02:54
*** carl_baldwin has joined #openstack-meeting-alt02:56
*** salv-orlando has joined #openstack-meeting-alt02:57
*** kebray has joined #openstack-meeting-alt02:58
*** achanda has joined #openstack-meeting-alt02:58
*** banix has joined #openstack-meeting-alt03:01
*** dims_ has quit IRC03:02
*** shwetaap has joined #openstack-meeting-alt03:06
*** armax has quit IRC03:09
*** salv-orlando has quit IRC03:10
*** achanda has quit IRC03:10
*** zhhuabj has quit IRC03:11
*** echoingumesh has joined #openstack-meeting-alt03:11
*** jckasper has quit IRC03:15
*** coolsvap is now known as coolsvap|afk03:15
*** tdruiva has joined #openstack-meeting-alt03:15
*** ijw has quit IRC03:17
*** armax has joined #openstack-meeting-alt03:17
*** david-lyle_afk has joined #openstack-meeting-alt03:17
*** resker has joined #openstack-meeting-alt03:18
*** sballe__ has quit IRC03:18
*** gokrokve has quit IRC03:18
*** fnaval has quit IRC03:19
*** eghobo has joined #openstack-meeting-alt03:20
*** mattgriffin has joined #openstack-meeting-alt03:20
*** ashleighfarnham has joined #openstack-meeting-alt03:20
*** armax has quit IRC03:20
*** esker has quit IRC03:21
*** eghobo has quit IRC03:21
*** EricGonczer_ has joined #openstack-meeting-alt03:22
*** coolsvap|afk is now known as coolsvap03:22
*** fnaval has joined #openstack-meeting-alt03:27
*** zhhuabj has joined #openstack-meeting-alt03:27
*** EricGonczer_ has quit IRC03:28
*** mattgriffin has quit IRC03:33
*** stevemar has quit IRC03:34
*** armax has joined #openstack-meeting-alt03:35
*** mattgriffin has joined #openstack-meeting-alt03:36
*** armax has quit IRC03:40
*** jgrimm is now known as zz_jgrimm03:40
*** echoingumesh has quit IRC03:45
*** echoingumesh has joined #openstack-meeting-alt03:46
*** zz_jgrimm is now known as jgrimm03:47
*** echoingumesh has quit IRC03:47
*** echoingumesh has joined #openstack-meeting-alt03:48
*** zehicle_ has joined #openstack-meeting-alt03:49
*** echoingumesh has quit IRC03:52
*** dims has joined #openstack-meeting-alt04:03
*** juggler_ has joined #openstack-meeting-alt04:05
*** eghobo has joined #openstack-meeting-alt04:06
*** achanda has joined #openstack-meeting-alt04:07
*** juggler has quit IRC04:08
*** adrian_otto has left #openstack-meeting-alt04:10
*** dims has quit IRC04:10
*** dimtruck is now known as zz_dimtruck04:10
*** miqui has quit IRC04:14
*** Haiying has joined #openstack-meeting-alt04:18
*** yalie has quit IRC04:31
*** Haiying has quit IRC04:34
*** absubram has joined #openstack-meeting-alt04:35
*** amotoki has joined #openstack-meeting-alt04:36
*** crc32 has quit IRC04:39
*** tdruiva has quit IRC04:40
*** tdruiva has joined #openstack-meeting-alt04:45
*** tdruiva has quit IRC04:46
*** banix has quit IRC04:48
*** nelsnelson has quit IRC04:52
*** salv-orlando has joined #openstack-meeting-alt04:57
*** rushiagr_away is now known as rushiagr04:58
*** carl_baldwin has quit IRC05:01
*** xyang1 has quit IRC05:02
*** kozhukalov has joined #openstack-meeting-alt05:06
*** salv-orlando has quit IRC05:10
*** salv-orlando has joined #openstack-meeting-alt05:12
*** salv-orlando has quit IRC05:16
*** deepakcs has joined #openstack-meeting-alt05:18
*** shwetaap has quit IRC05:21
*** salv-orlando has joined #openstack-meeting-alt05:29
*** achanda has quit IRC05:31
*** salv-orlando has quit IRC05:34
*** achanda has joined #openstack-meeting-alt05:34
*** salv-orlando has joined #openstack-meeting-alt05:35
*** salv-orlando has quit IRC05:35
*** salv-orlando has joined #openstack-meeting-alt05:41
*** mrmartin has joined #openstack-meeting-alt05:41
*** numan has joined #openstack-meeting-alt05:42
*** salv-orlando has quit IRC05:45
*** zehicle_ has quit IRC05:45
*** achanda has quit IRC05:48
*** netapp has quit IRC05:49
*** bnemec has quit IRC05:49
*** netapp has joined #openstack-meeting-alt05:49
*** vishwanathj has joined #openstack-meeting-alt05:50
*** bnemec has joined #openstack-meeting-alt05:52
*** achanda has joined #openstack-meeting-alt05:52
*** hblixt has quit IRC05:58
*** achanda has quit IRC05:58
*** irenab has joined #openstack-meeting-alt05:59
*** zehicle_ has joined #openstack-meeting-alt06:00
*** achanda has joined #openstack-meeting-alt06:01
*** netapp has quit IRC06:02
*** mattgriffin has quit IRC06:02
*** ajo has joined #openstack-meeting-alt06:03
*** salv-orlando has joined #openstack-meeting-alt06:04
*** ashleighfarnham has quit IRC06:06
*** eghobo has quit IRC06:06
*** salv-orlando has quit IRC06:08
*** mrmartin has quit IRC06:08
*** netapp has joined #openstack-meeting-alt06:08
*** Sukhdev has joined #openstack-meeting-alt06:12
*** achanda has quit IRC06:14
*** salv-orlando has joined #openstack-meeting-alt06:15
*** eghobo has joined #openstack-meeting-alt06:18
*** salv-orlando has quit IRC06:20
*** GLaupre has joined #openstack-meeting-alt06:21
*** salv-orlando has joined #openstack-meeting-alt06:21
*** salv-orlando has quit IRC06:26
*** salv-orlando has joined #openstack-meeting-alt06:27
*** kebray has quit IRC06:27
*** andreykurilin_ has joined #openstack-meeting-alt06:28
*** ozstacker has quit IRC06:28
*** annashen has joined #openstack-meeting-alt06:31
*** sreshetn1 has joined #openstack-meeting-alt06:32
*** salv-orlando has quit IRC06:32
*** Sukhdev has quit IRC06:33
*** egallen has joined #openstack-meeting-alt06:35
*** tdruiva has joined #openstack-meeting-alt06:35
*** annashen has quit IRC06:36
*** salv-orlando has joined #openstack-meeting-alt06:38
*** salv-orlando has quit IRC06:43
*** tdruiva has quit IRC06:44
*** SridharG has joined #openstack-meeting-alt06:45
*** resker has quit IRC06:49
*** esker has joined #openstack-meeting-alt06:50
*** ozstacker has joined #openstack-meeting-alt06:52
*** egallen has quit IRC06:53
*** akuznetsov has joined #openstack-meeting-alt06:55
*** andreykurilin_ has quit IRC06:57
*** kevinbenton has quit IRC06:59
*** HeOS has quit IRC07:00
*** bobmel has joined #openstack-meeting-alt07:05
*** bobmel has quit IRC07:06
*** bobmel has joined #openstack-meeting-alt07:07
*** anand1 has joined #openstack-meeting-alt07:09
*** eghobo has quit IRC07:13
*** egallen has joined #openstack-meeting-alt07:13
*** fnaval has quit IRC07:16
*** i-m-in has joined #openstack-meeting-alt07:18
*** egallen has quit IRC07:18
*** ajo has quit IRC07:19
*** sarob has quit IRC07:22
*** ajo has joined #openstack-meeting-alt07:23
*** jprovazn has joined #openstack-meeting-alt07:25
*** i-m-in has quit IRC07:25
*** scheuran has joined #openstack-meeting-alt07:25
*** stamak has joined #openstack-meeting-alt07:26
*** i-m-in has joined #openstack-meeting-alt07:33
*** i-m-in has quit IRC07:34
*** pkoniszewski has joined #openstack-meeting-alt07:34
*** stamak has quit IRC07:40
*** sergef has joined #openstack-meeting-alt07:40
*** tdruiva has joined #openstack-meeting-alt07:41
*** sreshetn1 has quit IRC07:45
*** tdruiva has quit IRC07:45
*** pnavarro has joined #openstack-meeting-alt07:50
*** coolsvap is now known as coolsvap|brb07:54
*** erkules_ is now known as erkules07:56
*** erkules has quit IRC07:56
*** erkules has joined #openstack-meeting-alt07:56
*** jcoufal has joined #openstack-meeting-alt08:04
*** salv-orlando has joined #openstack-meeting-alt08:05
*** e0ne has joined #openstack-meeting-alt08:11
*** mwang2__ has joined #openstack-meeting-alt08:13
*** vishwanathj has quit IRC08:14
*** matrohon has joined #openstack-meeting-alt08:15
*** salv-orlando has quit IRC08:15
*** mwang2_ has quit IRC08:17
*** sarob has joined #openstack-meeting-alt08:22
*** HeOS has joined #openstack-meeting-alt08:23
*** salv-orlando has joined #openstack-meeting-alt08:25
*** salv-orlando has quit IRC08:25
*** coolsvap|brb is now known as coolsvap08:26
*** Poornima has joined #openstack-meeting-alt08:27
*** sarob has quit IRC08:27
*** jungleboyj has quit IRC08:28
*** mrmartin has joined #openstack-meeting-alt08:28
*** mrmartin has quit IRC08:29
*** wojdev has joined #openstack-meeting-alt08:31
*** jungleboyj has joined #openstack-meeting-alt08:32
*** jtomasek has joined #openstack-meeting-alt08:32
*** shadower has joined #openstack-meeting-alt08:35
*** dizquierdo has joined #openstack-meeting-alt08:45
*** ajo has quit IRC08:46
*** safchain has joined #openstack-meeting-alt08:46
*** ndipanov has joined #openstack-meeting-alt08:47
*** fzdarsky has joined #openstack-meeting-alt08:47
*** ajo has joined #openstack-meeting-alt08:47
*** sreshetn1 has joined #openstack-meeting-alt08:55
*** marios has joined #openstack-meeting-alt08:57
*** mrmartin has joined #openstack-meeting-alt09:05
*** irenab has quit IRC09:15
*** irenab has joined #openstack-meeting-alt09:16
*** irenab has quit IRC09:17
*** Poornima_K has joined #openstack-meeting-alt09:19
*** Poornima_K has quit IRC09:19
*** Poornima_K has joined #openstack-meeting-alt09:19
*** Poornima has quit IRC09:19
*** irenab has joined #openstack-meeting-alt09:21
*** irenab has quit IRC09:24
*** irenab has joined #openstack-meeting-alt09:24
*** e0ne has quit IRC09:27
*** kevinbenton has joined #openstack-meeting-alt09:27
*** wojdev has quit IRC09:28
*** tdruiva has joined #openstack-meeting-alt09:29
*** teran has quit IRC09:30
*** annashen has joined #openstack-meeting-alt09:34
*** tdruiva has quit IRC09:34
*** zz_johnthetubagu is now known as johnthetubaguy09:35
*** numan has quit IRC09:39
*** annashen has quit IRC09:39
*** salv-orlando has joined #openstack-meeting-alt09:44
*** anand1 has quit IRC09:45
*** anand has joined #openstack-meeting-alt09:46
*** teran has joined #openstack-meeting-alt09:46
*** salv-orlando has quit IRC09:46
*** teran has quit IRC09:51
*** yamamoto has quit IRC09:54
*** numan has joined #openstack-meeting-alt09:55
*** nshaikh has joined #openstack-meeting-alt09:56
*** dizquierdo has quit IRC09:59
*** andriikolesnikov has joined #openstack-meeting-alt10:00
*** deepakcs has quit IRC10:04
*** salv-orlando has joined #openstack-meeting-alt10:10
*** _nadya_ has joined #openstack-meeting-alt10:11
*** sreshetn1 has quit IRC10:13
*** azemlyanov has joined #openstack-meeting-alt10:13
*** salv-orlando has quit IRC10:14
*** salv-orl_ has joined #openstack-meeting-alt10:15
*** salv-orl_ has quit IRC10:15
*** e0ne has joined #openstack-meeting-alt10:16
*** wojdev has joined #openstack-meeting-alt10:17
*** dims has joined #openstack-meeting-alt10:18
*** yamamoto has joined #openstack-meeting-alt10:19
*** thomnico has joined #openstack-meeting-alt10:23
*** [1]JonasB has quit IRC10:23
*** sarob has joined #openstack-meeting-alt10:24
*** sarob has quit IRC10:30
*** _nadya_ has quit IRC10:31
*** teran has joined #openstack-meeting-alt10:37
*** teran has quit IRC10:42
*** wojdev has quit IRC10:44
*** wojdev has joined #openstack-meeting-alt10:44
*** kevinbenton has quit IRC10:45
*** teran has joined #openstack-meeting-alt10:46
*** salv-orlando has joined #openstack-meeting-alt10:48
*** thomnico has quit IRC10:52
*** mrmartin has quit IRC10:57
*** marrusl has quit IRC11:01
*** marrusl has joined #openstack-meeting-alt11:03
*** juggler_ has quit IRC11:05
*** dizquierdo has joined #openstack-meeting-alt11:05
*** _amrith_ is now known as amrith11:08
*** yamamoto has quit IRC11:08
*** Poornima_K has quit IRC11:10
*** akuznetsov has quit IRC11:16
*** tdruiva has joined #openstack-meeting-alt11:18
*** e0ne is now known as e0ne_11:21
*** tdruiva has quit IRC11:23
*** sarob has joined #openstack-meeting-alt11:25
*** e0ne_ is now known as e0ne11:26
*** [1]JonasB has joined #openstack-meeting-alt11:26
*** vgridnev has quit IRC11:26
*** yamamoto has joined #openstack-meeting-alt11:29
*** wojdev has quit IRC11:30
*** sarob has quit IRC11:31
*** wbrothers has joined #openstack-meeting-alt11:33
*** wojdev has joined #openstack-meeting-alt11:38
*** noslzzp has joined #openstack-meeting-alt11:38
*** dizquierdo has quit IRC11:39
*** thomasem has quit IRC11:43
*** sergef has quit IRC11:43
*** yamamoto has quit IRC11:46
*** EricGonczer_ has joined #openstack-meeting-alt11:47
*** amrith is now known as _amrith_11:47
*** EricGonczer_ has quit IRC11:49
*** e0ne is now known as e0ne_11:51
*** zehicle_ has quit IRC11:52
*** pnavarro is now known as pnavarro|lunch11:52
*** esker has quit IRC11:55
*** thomasem has joined #openstack-meeting-alt11:55
*** dizquierdo has joined #openstack-meeting-alt11:56
*** e0ne_ has quit IRC11:56
*** thomasem has quit IRC11:56
*** thomasem has joined #openstack-meeting-alt11:57
*** EricGonczer_ has joined #openstack-meeting-alt12:06
*** johnthetubaguy is now known as zz_johnthetubagu12:11
*** eyald has joined #openstack-meeting-alt12:11
*** markvoelker has joined #openstack-meeting-alt12:14
*** wojdev has quit IRC12:15
*** e0ne has joined #openstack-meeting-alt12:18
*** tdruiva has joined #openstack-meeting-alt12:19
*** dprince has joined #openstack-meeting-alt12:20
*** wojdev has joined #openstack-meeting-alt12:21
*** eyald has quit IRC12:21
*** sreshetn1 has joined #openstack-meeting-alt12:22
*** tdruiva has quit IRC12:24
*** sarob has joined #openstack-meeting-alt12:27
*** _amrith_ is now known as amrith12:29
*** sarob has quit IRC12:31
*** dims has quit IRC12:33
*** dims has joined #openstack-meeting-alt12:34
*** funzo has quit IRC12:35
*** annashen has joined #openstack-meeting-alt12:36
*** miqui has joined #openstack-meeting-alt12:38
*** zz_johnthetubagu is now known as johnthetubaguy12:39
*** dave-mccowan has joined #openstack-meeting-alt12:40
*** annashen has quit IRC12:41
*** esker has joined #openstack-meeting-alt12:44
*** rushiagr is now known as rushiagr_away12:46
*** esker has quit IRC12:47
*** baoli has joined #openstack-meeting-alt12:47
*** esker has joined #openstack-meeting-alt12:50
*** esker has quit IRC12:51
*** yamamoto has joined #openstack-meeting-alt12:51
*** baoli has quit IRC12:52
*** baoli has joined #openstack-meeting-alt12:53
*** anand has quit IRC12:55
*** pnavarro|lunch is now known as pnavarro12:56
*** mattfarina has joined #openstack-meeting-alt13:04
*** banix has joined #openstack-meeting-alt13:04
*** rushiagr_away is now known as rushiagr13:05
*** jckasper has joined #openstack-meeting-alt13:05
*** banix has quit IRC13:05
*** dave-mccowan has quit IRC13:06
*** dave-mccowan has joined #openstack-meeting-alt13:07
*** amotoki has quit IRC13:08
*** DaSchab has joined #openstack-meeting-alt13:09
*** esker has joined #openstack-meeting-alt13:10
*** rtomasko has joined #openstack-meeting-alt13:11
*** jecarey has joined #openstack-meeting-alt13:12
*** banix has joined #openstack-meeting-alt13:12
*** amotoki has joined #openstack-meeting-alt13:15
*** rellerreller has joined #openstack-meeting-alt13:15
*** sdake_ has joined #openstack-meeting-alt13:15
*** Longgeek has joined #openstack-meeting-alt13:19
*** tdruiva has joined #openstack-meeting-alt13:20
*** rushiagr is now known as rushiagr_away13:20
*** dave-mccowan has quit IRC13:20
*** EricGonczer_ has quit IRC13:20
*** wojdev has quit IRC13:22
*** banix has quit IRC13:22
*** tdruiva has quit IRC13:24
*** amrith is now known as _amrith_13:24
*** wojdev has joined #openstack-meeting-alt13:25
*** DaSchab has quit IRC13:26
*** sarob has joined #openstack-meeting-alt13:27
*** banix has joined #openstack-meeting-alt13:29
*** _nadya_ has joined #openstack-meeting-alt13:29
*** jcoufal has quit IRC13:31
*** jcoufal has joined #openstack-meeting-alt13:32
*** banix has quit IRC13:32
*** dave-mccowan has joined #openstack-meeting-alt13:32
*** sarob has quit IRC13:33
*** jungleboyj has quit IRC13:33
*** akuznetsov has joined #openstack-meeting-alt13:38
*** rellerreller has quit IRC13:40
*** Longgeek has quit IRC13:43
*** fnaval has joined #openstack-meeting-alt13:49
*** thangp has joined #openstack-meeting-alt13:50
*** rprakash has joined #openstack-meeting-alt13:53
*** Longgeek has joined #openstack-meeting-alt13:55
*** e0ne has quit IRC13:57
*** gongysh has joined #openstack-meeting-alt13:57
*** e0ne has joined #openstack-meeting-alt13:57
*** bertys has joined #openstack-meeting-alt13:59
*** pc_m has joined #openstack-meeting-alt13:59
*** jgrimm is now known as zz_jgrimm14:00
*** vks has joined #openstack-meeting-alt14:00
*** tellesnobrega_ has joined #openstack-meeting-alt14:00
*** cloudon has joined #openstack-meeting-alt14:01
sgordon#startmeeting telcowg14:01
openstackMeeting started Wed Mar 11 14:01:19 2015 UTC and is due to finish in 60 minutes.  The chair is sgordon. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: telcowg)"14:01
openstackThe meeting name has been set to 'telcowg'14:01
sgordon#link https://etherpad.openstack.org/p/nfv-meeting-agenda14:01
mkodererhi14:01
sgordon#topic roll call14:01
*** openstack changes topic to "roll call (Meeting topic: telcowg)"14:01
vkshi14:01
gongyshhi14:01
cloudonhi14:01
* beagles waves, panting from running from other room14:01
sgordon#topic action items from last week14:02
*** openstack changes topic to "action items from last week (Meeting topic: telcowg)"14:02
*** dave-mccowan has quit IRC14:02
sgordon#info aveiga's basic use case template was merged14:02
*** zehicle_ has joined #openstack-meeting-alt14:02
sgordon#link http://git.openstack.org/cgit/stackforge/telcowg-usecases/tree/template.rst14:02
sgordon#info sgordon submitted cloudon's vIMS use case for review - needs some further updates to meet template14:03
mkoderersgordon: the basic template seems not to work for the doc build :(14:03
sgordon#link https://review.openstack.org/15899714:03
sgordon#info daschab submitted security segregation use case for review14:03
sgordon#link https://review.openstack.org/16339914:03
*** dkusidlo has joined #openstack-meeting-alt14:03
sgordon#info mkoderer notes that the basic template seems not to work for the doc build14:04
*** sreshetn1 has quit IRC14:04
sgordonmkoderer, do you have a link to the fail14:04
mkoderersgordon: https://review.openstack.org/#/c/163399/14:04
sgordonwell that is a friendly error isnt it14:04
*** akuznetsov has quit IRC14:04
mkoderersphinx is failing with "WARNING: Literal block expected; none found"14:04
mkoderersgordon: I need to check what goes wrong there14:05
*** yamamoto has quit IRC14:05
sgordonso in the original review where we merged the template it did build: https://review.openstack.org/#/c/158028/14:05
*** yamamoto has joined #openstack-meeting-alt14:05
sgordonso it must be something specific to the changes in that submission - i guess?14:05
*** rushiagr_away is now known as rushiagr14:06
*** shwetaap has joined #openstack-meeting-alt14:06
mkoderersgordon: I guess the template won't be used for the spinx build14:06
*** adrian-hoban has joined #openstack-meeting-alt14:06
*** nelsnelson has joined #openstack-meeting-alt14:06
mkoderersgordon: and the IMS one run through because you used the wrong directory ;)14:06
sgordonmkoderer, let's try work on that after the meeting14:06
mkodererhttps://review.openstack.org/#/c/158997/14:06
sgordonhahaha14:06
rprakash#help to corelate mNO/MVNO use case with IPv6 OPNFV when  time permits - Thanks14:06
mkoderersgordon: ok14:06
sgordonyeah i havent rebased it yet14:06
sgordonsooo14:07
sgordon#topic operators mid-cycle14:07
*** openstack changes topic to "operators mid-cycle (Meeting topic: telcowg)"14:07
sgordonwe had a telco working session at the operators mid-cycle yesterday14:07
*** smazziotta has joined #openstack-meeting-alt14:07
sgordon#link https://etherpad.openstack.org/p/PHL-ops-telco14:07
sgordonminutes are recorded in the above etherpad14:08
sgordonwe had a mix of people who have been in these meetings and some who were coming at it for the first time14:08
sgordonand i think it's fair to say that the main topic of conversation was interaction with OPNFV and how the two groups fit together14:08
*** mdbooth has quit IRC14:09
sgordonthere was also an OPNFV call on the topic of working with openstack earlier in the day14:09
gongyshwhat are 'the two groups'?14:09
sgordongongysh, OPNFV and OpenStack Telco Working group14:09
gongyshthanks14:09
sgordonwe are in a bit of an odd place because we created the latter as a place to collaborate on NFV and telco use cases and their openstack requirements before OPNFV existed14:10
rprakash#info I am working in OPNFV and as well in teclowg since last year but missed lot here14:10
*** iccha has joined #openstack-meeting-alt14:10
sgordonthe main action item that came out of that was for me to re-connect with chris price on the OPNFV side and start some more cross-threads to discuss further14:11
sgordonwe did also walk through the way we are handling use case submission and review at the moment14:11
adrian-hobanLots of OpenStack requirements going to be developed in both OPNFV and ETSI-NFV phase 214:11
rprakash#info The Community page ion OPNFV has Openstack listed and is working and we can co-ordiate with it14:12
sgordonwell this is really the issue14:12
vkshow?14:12
sgordon- ETSI, OPNFV, and this group, all currently define/update use cases14:12
*** kobis has joined #openstack-meeting-alt14:12
*** iccha has quit IRC14:12
sgordon- some are members of one but not the others14:12
sgordon- how to avoid duplication14:13
*** gokrokve has joined #openstack-meeting-alt14:13
rprakash#link https://wiki.opnfv.org/community/openstack14:13
*** iccha has joined #openstack-meeting-alt14:13
vksif we share common discussion14:13
vksat least for defining use cases14:13
*** balajiiyer has joined #openstack-meeting-alt14:14
adrian-hobanRe ETSI-NFV Phase 2, I suspect most of the OpenStack related item will come out of the IFA stream.14:14
sgordon#link https://wiki.opnfv.org/community/openstack14:14
*** balajiiyer has left #openstack-meeting-alt14:14
*** mdbooth has joined #openstack-meeting-alt14:14
*** dneary has joined #openstack-meeting-alt14:14
vksadrian-hoban, IFA?14:14
*** ian_ott has joined #openstack-meeting-alt14:14
mkodererWe need to define the scope for all these groups...14:15
sgordonif i am being brutally honest i am more concerned about the OPNFV interaction versus ETSI, unless we are expecting significantly more timely publication of the next round of ETSI outputs14:15
*** adrian-hoban_ has joined #openstack-meeting-alt14:15
sgordonOPNFV are defining and pushing out use cases, gaps, requirements for us to interact with now14:15
vkssgordon, do u mean to collabrate with any one?14:15
adrian-hoban_vks: IFA = Interfaces and Architecture Working Group14:16
rprakash#info Sean Rob from EMC/Vmware and visited OPNFV and had indicated the use case can be co-ordinaged by product team too14:16
sgordonvks, the ETSI-NFV collaboration with this group thus far has been "here is a PDF of things and you already did half of them because we took so long"14:16
sgordon;)14:16
adrian-hoban_:-)14:16
dnearyCan I #link?14:16
vks;)14:16
rprakash#info we can do agap analysis between projects listed in link I showed earlier (requirement) projects with openstack modules14:17
dneary#link https://wiki.opnfv.org/community/openstack14:17
sgordondneary, http://lists.openstack.org/pipermail/openstack-dev/2014-October/048021.html14:17
sgordondneary, we already linked that page14:17
dnearysgordon, Great, thanks14:18
sgordonso what i am getting at is i see more immediate overlap with OPNFV activities than ETSI-NFV ones14:18
*** adrian-hoban has quit IRC14:18
dnearyYes. Although the ETSI NFV Open Source WI is also focussing on OpenStack interactions14:19
rprakash#info But this is as of October 2014 , is it current?14:19
*** zehicle_ has quit IRC14:19
vkssgordon, i think we are in better position now14:19
vkswe have few use cases with us14:19
dnearyI don't know if there is a specific mailing list, or SPOC, for that work item though14:19
sgordonrprakash, this is the thing14:19
rprakash#info I though we are talking of gap between OPNFV requirments project and Openstack Modules14:19
sgordonas far as i know no newer version has been published14:19
sgordonrprakash, can you stop trying to info things that are just your commentary?14:20
sgordonthanks14:20
adrian-hoban_sgordon: I think that's a fair assessment. There's a but... If we collectively don't influence the ETSI-NFV specs, there are requirements coming down the pipe that will be difficult to implement...14:20
sgordonsure, but how much of that influence is co-ordinated via this effort today?14:20
sgordoni think a lot of participants dont have the visibility14:21
mkodererIMHO we are currently only keeping our self busy :)14:21
rprakash#info I will try get that for IFA 005-006 for NB Interfaces and that may be say next week14:22
rprakash#info VIM NB Interfaces14:22
rprakashOK I need some help  in irc practices will do14:22
dnearyrprakash, Even in OPNFV the discussion has moved past that, I think - we're breaking down requirements projects into individual feature requests - and in the future that will be Gerrit patch submissions and bug reports14:22
*** tdruiva has joined #openstack-meeting-alt14:22
*** anand1 has joined #openstack-meeting-alt14:22
mkodererat the end nobody will get the needed changes implemented14:22
sgordonmkoderer, indeed and that is really the key14:22
*** salv-orlando has quit IRC14:23
sgordonidentifying where the body of the participants actually willing to do the work are connected to each other14:23
adrian-hoban_sgordon: Working with the OPNFV community makes sense and will have more developer representation14:23
*** anand1 has left #openstack-meeting-alt14:24
vksadrian-hoban_, +114:24
*** absubram has quit IRC14:24
mkodereradrian-hoban_: but how...14:24
sgordonthat is my suspicion, also it looks like dneary fearlessly volunteered to maintain a wiki of the changes they are submitting14:24
sgordonHOWEVER14:24
*** bknudson has joined #openstack-meeting-alt14:24
dnearysgordon, Yes, I am that sucker14:25
sgordonthe concern raised with this was it excludes NFV and telco users, including some who are members of this group, that are not members of OPNFV14:25
sgordon...concern raised at the mid-cycle session yesterday that is14:25
dnearysgordon, I hope that the only metadata we'll have there which won't be upstream is the OPNFV project name it came from14:25
sgordonthis comes back to how we create some loose framework for collaboration here14:25
sgordonversus the current situation where OPNFV members submit their use cases to both groups, for example14:26
dnearysgordon, rprakash was asking me what belongs in OPNFV and what belongs in OpenStack - would it be useful to clarify that (from the OPNFV point of view)?14:26
sgordonthis is not a problem i expect to solve today but what i took the AI to try and get at14:26
*** esker has quit IRC14:26
sgordondneary, sure - but is there a common OPNFV POV on this?14:27
dnearysgordon, Getting towards it...14:27
*** sigmavirus24_awa is now known as sigmavirus2414:27
*** jungleboyj has joined #openstack-meeting-alt14:27
dnearyOPNFV - take telco use-cases defined in telco language, and convert them into requirements expressed in non-telco-readable language; from that break high level requirements into actionable feature requests for upstream projects (including OpenStack)14:28
sgordon#info Clarification needed to establish interaction/overlap of ETSI-NFV, OPNFV, and OpenStack Telco Working group14:28
rprakashIs it recommended to use new template listed to be used for use cases rather than one we used earlier as nfv group?414:28
dnearyOpenStack: OPNFV members submit blueprints, and track those blueprints through review, code creation, code review and merge14:28
*** sarob has joined #openstack-meeting-alt14:29
*** akuznetsov has joined #openstack-meeting-alt14:29
dnearyFor the moment, OPNFV is essentially taking the product of ETSI NFV ISG as the higher level telco use-case inputs14:29
mkodererdneary: seems like an overlap to this group14:29
*** kobis has quit IRC14:29
sgordondneary, really this asks more questions than it answers14:29
sgordonmkoderer, +114:29
dnearySo, for ETSI members, there are 2 opportunities to collaborate:14:29
sgordon"The working group aims to define the use cases and identify and prioritise the requirements which are needed to deploy, manage, and run telecommunication services on top of OpenStack. This work includes identifying functional gaps, creating blueprints, submitting and reviewing patches to the relevant OpenStack projects and tracking their completion in support of telecommunication services."14:30
dneary1. Breaking down the high level requests inside OPNFV (you don't need to be a member to participate in a specific project)14:30
rprakash#ilink http://git.openstack.org/cgit/stackforge/telcowg-usecases/tree/template.rst14:30
dneary2. Participating in the review & refinement of blueprints14:30
rprakashI mean this template14:30
sgordonrprakash, im not really clear on the question - at this time if you were to submit to our repo we would expect you to use our template, otherwise we wouldnt merge it14:31
*** salv-orlando has joined #openstack-meeting-alt14:31
sgordonwhat we're talking about though is whether we're just spinning our wheels here and that use case definition belongs in opnfv14:31
dnearysgordon, Yes, IMHO, there is overlap with this group. Ensuring that people in this group are ensuring that OPNFV's product is useful to OpenStack, and ensuring that OPNFV people are participating here, is a key goal.14:31
rprakashOK thta was my question , is this new template and are we doing away with old one in telcowg14:31
sgordonwhat we need to see though is that the use case definitions are in fact in non-telco speak14:31
dnearyThe delta is where OPNFV includes in scope projects other than OpenStack14:32
sgordonand are coming through with the blueprints and specs14:32
sgordonwhich at the moment based on the proposals i am seeing in the opnfv list is not necessarily the case14:32
dnearysgordon, Agreed14:32
dnearysgordon, That's been a challenge up to this point14:32
*** Poornima has joined #openstack-meeting-alt14:32
*** e0ne is now known as e0ne_14:32
fzdarskysgordon, maybe adding that ETSI NFV has activity to support with creating use cases in non-telco language along the lines of their requirements14:32
dnearyProject reviews and blueprints have not been getting enough eyeballs. We're making progress in some cases, but there are a lot of OPNFV projects now14:33
*** gokrokve_ has joined #openstack-meeting-alt14:33
*** banix has joined #openstack-meeting-alt14:33
*** sarob has quit IRC14:33
*** e0ne_ is now known as e0ne14:33
adrian-hoban_fzdarsky: I don't think you'll get that from ETSI-NFV in a form that will be usable here.14:34
sgordonfzdarsky, honestly i would again prefer to focus on OPNFV14:34
sgordonif something comes out of ETSI-NFV that is directly understandable by someone coming at it from a non-telco case then i will be the first to take notice14:34
rprakashlet me ask you I have specific MNO-MVNO use case in telco-wg under prep work how do I deal this wrt telcowg and opnfv, help me build this14:34
sgordonbut need to see evidence of that actually happening before i will believe it14:35
fzdarskyadrian-hoban_, I think doing that in ETSI NFV is the only way to ensure full coverage14:35
dnearyrprakash, What is MNO-MVNO?14:35
dneary(actually, that's kind of the point)14:35
adrian-hoban_The ETSI-NFV normative work has to stay technology neutron, so there is a level of abstraction between what is developed there, and what shows up here in blueprints14:35
sgordondneary, yes we covered this in a previous meeting also14:35
rprakashMobile Network Operator & Mobile Virtual Network Operator14:35
sgordonthe use case proposal was very acronym heavy without necessarily explaining itself14:36
*** radez_g0n3 is now known as radez14:36
fzdarskyadrian-hoban_, that is exactly why ETSI NFV created the work item for interfacing with open-source14:36
fzdarskyadrian-hoban_, so that IFA WG et al can stay technology neutral14:36
*** gokrokve has quit IRC14:36
*** numan has quit IRC14:36
rprakash#info ETSI NIFV IFA and other groups publish and only published reports we can use14:36
*** mtanino has joined #openstack-meeting-alt14:36
sgordon#info OPNFV aims overlap significantly with telco working group aims14:37
adrian-hoban_fzdarsky: I suspect that for this context, it will end up being a close collaboration with OPNFV, which brings us back to sgordon's initial point14:37
sgordon#info ETSI-NFV Open Source work item may overlap but not as clear at this point14:37
rprakashI thought that helps co-ordiate activities as we can use synergy in both forums14:37
vksin my opinion working close with OPNFV now will be gud for now14:38
sgordon#info sgordon and dneary agree OPNFV project reviews and blueprints need more eyeballs - aim being combination of both understandable/clear use case and implementation proposal make it through to OpenStack specification14:38
*** annashen has joined #openstack-meeting-alt14:38
*** esker has joined #openstack-meeting-alt14:38
*** jprovazn has quit IRC14:38
sgordonvks, +114:38
*** pmalik has joined #openstack-meeting-alt14:38
*** jungleboyj has quit IRC14:38
sgordoni think this is where there is the most obvious overlap *today*14:39
dnearySo - how can I help enable that work together?14:39
rprakashcan we then agree that let requirements come form OPNFV but use case be built here in telcowg?14:39
sgordondneary, so what is the process in opnfv land for submitting/reviewing a use case14:39
dnearyI can identify the 3-4 most important meetings for OpenStack people to be present?14:39
mkodererrprakash: I don't agree14:39
sgordonrprakash, i dont think we can14:39
vkssgordon, first by segregating use cases at single repo14:39
sgordonfor starters opnfv would have to agree14:39
sgordonsince that appears to be part of their mandate too14:40
sgordon(use cases)14:40
*** SridharG has left #openstack-meeting-alt14:40
sgordonand as dneary said they are tracking at a slightly broader level14:40
mkodererdon't forget that there are policical things ongonig :)14:40
sgordonin that the use case may cover multiple projects that include openstack14:40
mkodererWe won't join OPNFV in it's current state...14:40
sgordonmkoderer, lol - oh yes14:40
dnearysgordon, OPNFV has requirements projects, the idea is to express the high level requirements that a use-case places on the platform (some examples: multi-site, IPv6, fault management, resource reservation)14:40
vkssgordon, i meant to say blueprints whatever we have now14:40
sgordonmkoderer, right and this comes back to my biggest concern14:40
sgordonwhat is the process for people who arent OPNFV members and dont want to be14:41
sgordonbecause aveiga and amitry are also not currently14:41
dnearyEach requirements project comes up with a project definition that should say what the work result of the project will be, the upstream projects affected, and the people committed to working on the project14:41
sgordonso that's basically 4-5 of our regular contributors who arent in OPNFV at all14:41
mkodererBeing a OpenStack foundation memeber should be sufficent to file use cases :)14:41
sgordonvks, ack14:42
dnearyOnce the project is approved by the OPNFV TSC (approval process mostly rotates around clarifying project definition and deliverables, no attention is given to implementation details in my experience)14:42
*** ddovbii has left #openstack-meeting-alt14:42
sgordon#info mkoderer notes not everyone is an OPNFV member, not necessarily open to becoming one at this time14:42
sgordon#undo14:42
openstackRemoving item from minutes: <ircmeeting.items.Info object at 0x97b9690>14:42
dnearyonce approved, project participants break the higher use case into blueprints, feature requests, project proposals in upstream projects14:42
sgordon#info mkoderer notes not everyone is an OPNFV member, nor necessarily open to becoming one at this time14:42
*** marcusvrn has joined #openstack-meeting-alt14:43
*** annashen has quit IRC14:43
dnearyAnd those should go through internal review in the project, plus submission as WIP in specs repos upstream for upstream revision & review14:43
*** mrmartin has joined #openstack-meeting-alt14:43
vkssgordon, ?14:43
matrohonmkoderer : Openstack may fail at that because Telco use cases don't get enough attention in core projects14:43
dnearyThat's the ideal14:43
*** vishwanathj has joined #openstack-meeting-alt14:43
*** ChuckC_ has joined #openstack-meeting-alt14:43
cloudondneary: agree - in OPNFV you simply propose a project, and if you fill in the forms right and convince the technical steering committee it's in scope and not conflicting with other OPNFV projects then you are a go14:43
*** ChuckC has quit IRC14:44
rprakash#info any linux foundation account holder can participate in OPNFV as volunteer14:44
adrian-hoban_dneary: I think we need any requirements coming from OPNFV to pass through this WG first. If we don't get this in place we will end up in the same place we were in a year ago14:44
mkoderermatrohon: that's correct.. but OPNFV will fail too if they don't listen to their customers :)14:44
fzdarskymkoderer, sgordon , the only place where all stakeholders are represented and where normative req's are created is in ETSI. Therefore, we need a process to ensure OPNFV can take the ETSI req's and use cases and map them to upstream req's and blueprints14:44
*** Rajeev has joined #openstack-meeting-alt14:44
cloudondon't see anything in OPNFV processes yet which sets out how to interact with OpenStack community14:45
matrohonadrian-hoban : +114:45
dnearyadrian-hoban_, In terms of project requirements, or blueprints?14:45
*** gongysh has quit IRC14:45
*** marcusvrn1 has quit IRC14:45
rprakash#info ETSI use cses were for ETSI PoC and now for nfv pase 2 and not for OPNFV or Openstack14:45
*** vishwana_ has joined #openstack-meeting-alt14:45
dnearyadrian-hoban_, To date, no requirements project has "completed" - that is, tested code, merged upstream14:46
sgordondneary, yeah but blueprints have been submitted14:46
sgordonin a similar state to those we were getting 1+ years ago14:46
vks:)14:46
sgordonso i can see where adrian-hoban_ is going with that line of thought14:46
*** uschreiber has joined #openstack-meeting-alt14:46
*** tonytan4ever has joined #openstack-meeting-alt14:46
*** adrian-hoban has joined #openstack-meeting-alt14:46
sgordonnow sure "we can fix that" but it would have been better to do it before submission14:46
dnearysgordon, What happened (as you know) is that the OPNFV project got busy when under the impression that Nova blueprints needed to be submitted in early March, after the Liberty branch was opened14:47
adrian-hobanfzdarsky: I think the flow is IFA --> TST --> OPNFV --> Telco WG --> OpenStack Projects14:47
fzdarskyadrian-hoban, +114:47
mkodereradrian-hoban: that's a monster14:47
adrian-hobandneary: I got disconnected and missed your question14:47
rprakashOK lets agree that Blue Prints coming from OPNFV requiremnts be whetted by teclowg14:47
fzdarskymkoderer, but that is probably necessary, if you want full representation14:47
*** vishwanathj has quit IRC14:47
*** sankarshan is now known as sankarshan_away14:47
*** Riddhi has joined #openstack-meeting-alt14:47
mkodereradrian-hoban: we won't to build an environment in 2015 and not in 2030 :)14:48
dnearysgordon, We're now post-processing those to ensure they're useful to OpenStack14:48
adrian-hobanThere are some short-cuts14:48
rprakashThe telcowg then manage the passage of BP to approval in openstack14:48
*** adrian-hoban_ has quit IRC14:48
adrian-hobanMany of us have folks in all these projects14:48
dnearyadrian-hoban, Indeed14:48
dnearyMuch redundancy, many repeated conversations14:48
*** ChuckC_ has quit IRC14:49
fzdarskyadrian-hoban, yes, but from experience, those people do not communicate well in all companies14:49
sgordonwell/at all14:49
*** nelsnelson has quit IRC14:49
rprakashA BP in openstack does it have a hold status so that telcowg can weekly clear or correct what OPNFV comes up with?14:49
sgordonuntil someone actually approves it14:49
sgordonit's in a hold status by default ;)14:49
*** nelsnelson has joined #openstack-meeting-alt14:50
rprakashSo we ask OPNFV to start a BP with Hold staus14:50
sgordonwhat i want to get back to is mkoderer's question though14:50
vksi thought we are trying to collaborate with OPNFV, but seems going in other drection14:50
sgordonabout where use cases are tracked particularly if you are not part of OPNFV14:50
sgordonvks, how so?14:50
rprakashAnd let telcowg rework it to meet the openstack module requirments?14:51
rprakashPlus there are cases where cross module BPs are required and that is not the capability of OPNFV let teclowg suggest how to handle that14:52
*** carl_baldwin has joined #openstack-meeting-alt14:52
vkssgordon, so going by above conversation this group participation in BP's will be zero14:52
rprakashWhich group? you mean telcowg ? Not at all14:52
vksyes14:53
sgordonvks, i dont see where you got that from14:53
*** funzo has joined #openstack-meeting-alt14:53
matrohonsgordon : the Use case repo makes sense for people like mkoderer : OPNFV teams can still review them or even register new Use cases in it14:53
*** SridharRamaswamy has joined #openstack-meeting-alt14:54
sgordoni think what we keep coming around on in this conversation is that the use case definition is the primary overlap between opnfv and this group14:54
adrian-hobanOne of the reasons we set up this Telco WG was a request from various PTLs and core devs for the Telco community to collaborate and agree on an approach before broadening the review requests. I don't think that fundamental has changed14:54
rprakashSee let each requirement project come to this meeting from OPNFV to telcowg, present gt advice from telcowg before they initiate even BP14:54
sgordonblueprints although discussed in groups are ultimately owned by an individual14:54
*** iccha has left #openstack-meeting-alt14:54
*** akuznetsov has quit IRC14:54
sgordonwe can collaborate on making sure they are likely to succeed and meet everyone's needs though14:54
vksmatrohon, +114:54
sgordon#info "One of the reasons we set up this Telco WG was a request from various PTLs and core devs for the Telco community to collaborate and agree on an approach before broadening the review requests. I don't think that fundamental has changed"14:54
sgordonadrian-hoban, big +1 - and though i see opnfv as a possible step towards handling this it's clearly not there yet14:55
rprakashYes agreed but there needs be communication or join meet between the two in Openstack telcowg to help that happen14:55
*** kebray has joined #openstack-meeting-alt14:55
sgordonrprakash, isnt that how i started the meeting?14:55
*** fnaval has quit IRC14:55
sgordoni was also on the opnfv call on this topic y'day14:55
*** zz_jgrimm is now known as jgrimm14:55
*** cbouch has joined #openstack-meeting-alt14:55
*** gongysh has joined #openstack-meeting-alt14:56
*** fnaval has joined #openstack-meeting-alt14:56
sgordonwhat we need to get to is a little clearer division of responsibilities though14:56
*** marcusvrn1 has joined #openstack-meeting-alt14:56
adrian-hobansgordon: +114:56
rprakashMay be I missed that but then we must get dneary who has been leading OPNFV side to work with you on that14:56
*** kobis has joined #openstack-meeting-alt14:56
vkssgordon, +114:57
*** dkusidlo has quit IRC14:57
dnearysgordon, re: Where are use cases tracked, seems like OPNFV is the current best place.14:57
sgordondneary, unless your not in OPNFV14:57
dnearyI understand the "not everyone is in OPNFV" argument14:58
sgordonim still concerned i am seeing no answer to that14:58
*** marcusvrn has quit IRC14:58
smazziottasgordon, +1 . kind od RACI table. with owner and deadline...14:58
dnearyBut people who are not paying members can still participate (unlike ETSI NFV)14:58
dnearyAnd it's sufficiently telco focussed that we have a decent chance that use-cases as defined will be useful to that audience14:58
sgordontechnically yes, but is that politically realistic14:58
*** shivharis has joined #openstack-meeting-alt14:58
dnearysgordon, Depends14:58
fzdarskydneary, you don't have to pay to participate in ETSI NFV :)14:58
rprakashOK let us ask each requirments project in OPNFV to present their cases to telcowg, and then jointly plan what BPs are required in which module to make that happen14:59
mkodererdneary: OPNFV is seen as vendor drivern maybe?14:59
*** EricGonczer_ has joined #openstack-meeting-alt14:59
sgordon#action sgordon to kick off thread of conversation to try and define a clearer framework for who does what (OPNFV versus telcowg)14:59
mkodererIMHO the best place for telco usecases is our review process :)14:59
mkodererit's a tranperant process and I don't need any commitee agreement14:59
dnearysgordon, If there is an impression that requirements are being "done wrong" by OPNFV, to the detriment of non-OPNFV participants, the incentive to get involved and "fix" them grows - especially if the requirements coming from OPNFV result in code14:59
*** gongysh has quit IRC15:00
*** yamamoto has quit IRC15:00
sgordondneary, i think the incentive at the moment is low because they are done wrong enough that they and code associated with them wont be accepted15:00
dnearyAt the end of the day, if neither OPNFV or ETSI NFV results in code being written and merged into OpenStack, it doesn't matter which we talk to15:00
*** rcurran has joined #openstack-meeting-alt15:00
rprakashLets ask how can telcowg help OPNFV requirment folks to translate their requirments to BP, can some one propose a process15:00
mkodererdneary: +115:00
mkoderermeeting time ends :)15:00
* dneary has to drop for another meeting15:00
*** ian_ott has quit IRC15:00
*** fnaval has quit IRC15:01
sgordonmkoderer, right - if we did do something with OPNFV for use cases i would like to see them at least move to similar technology/tooling for the reviewing15:01
sgordonnot clear now15:01
sgordonwe have hit our hard stop15:01
sgordonlet's continue in #openstack-nfv or on the mailing list15:01
sgordonthanks all - like i said this was the hot topic in the room yesterday15:01
sgordonwanted to bring everyone up to date15:01
*** kebray has quit IRC15:01
*** mattgriffin has joined #openstack-meeting-alt15:01
sgordon#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings"15:01
openstackMeeting ended Wed Mar 11 15:01:40 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/telcowg/2015/telcowg.2015-03-11-14.01.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/telcowg/2015/telcowg.2015-03-11-14.01.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/telcowg/2015/telcowg.2015-03-11-14.01.log.html15:01
*** stevemar has joined #openstack-meeting-alt15:02
*** marcusvrn1 has quit IRC15:03
*** sadasu has joined #openstack-meeting-alt15:04
*** jcoufal has quit IRC15:05
*** jcoufal has joined #openstack-meeting-alt15:05
*** daniel3_ has joined #openstack-meeting-alt15:07
*** banix has quit IRC15:07
*** tellesnobrega_ has quit IRC15:07
*** armax has joined #openstack-meeting-alt15:07
*** tdruiva has quit IRC15:08
*** irenab has quit IRC15:08
*** fnaval has joined #openstack-meeting-alt15:09
*** tdruiva has joined #openstack-meeting-alt15:09
*** marcusvrn has joined #openstack-meeting-alt15:09
*** bertys has quit IRC15:09
*** muralia has left #openstack-meeting-alt15:09
*** kobis has quit IRC15:09
*** shivharis has quit IRC15:10
*** Rajeev has quit IRC15:11
*** banix has joined #openstack-meeting-alt15:12
*** manishg has joined #openstack-meeting-alt15:13
*** adrian-hoban has quit IRC15:13
*** dizquierdo has quit IRC15:13
*** manishg has left #openstack-meeting-alt15:13
*** marcusvrn has quit IRC15:14
*** sew has left #openstack-meeting-alt15:14
*** rtomasko has quit IRC15:16
*** ChuckC_ has joined #openstack-meeting-alt15:16
*** banix has quit IRC15:16
*** banix has joined #openstack-meeting-alt15:17
*** carl_baldwin has quit IRC15:18
*** rprakash has quit IRC15:19
*** teran has quit IRC15:20
*** teran has joined #openstack-meeting-alt15:20
*** shwetaap has quit IRC15:21
*** shwetaap has joined #openstack-meeting-alt15:22
*** akuznetsov has joined #openstack-meeting-alt15:23
*** shivharis has joined #openstack-meeting-alt15:24
*** zz_dimtruck is now known as dimtruck15:24
*** dizquierdo has joined #openstack-meeting-alt15:25
*** EricGonczer_ has quit IRC15:25
*** jprovazn has joined #openstack-meeting-alt15:27
*** gokrokve_ has quit IRC15:27
*** hogepodge has quit IRC15:28
*** kobis has joined #openstack-meeting-alt15:28
*** david-lyle_afk is now known as david-lyle15:28
*** sarob has joined #openstack-meeting-alt15:30
*** mtanino is now known as mtanino_away15:30
*** BrianB_ has joined #openstack-meeting-alt15:31
*** mattgriffin has quit IRC15:32
*** sreshetn1 has joined #openstack-meeting-alt15:32
*** kobis has quit IRC15:32
*** kobis has joined #openstack-meeting-alt15:32
*** ian_ott has joined #openstack-meeting-alt15:34
*** ian_ott has quit IRC15:35
*** sarob has quit IRC15:36
*** uschreiber has quit IRC15:36
*** Sukhdev has joined #openstack-meeting-alt15:37
*** jungleboyj has joined #openstack-meeting-alt15:38
*** dkusidlo has joined #openstack-meeting-alt15:39
*** EricGonczer_ has joined #openstack-meeting-alt15:39
*** carl_baldwin has joined #openstack-meeting-alt15:40
*** deepakcs has joined #openstack-meeting-alt15:41
*** nuritv has joined #openstack-meeting-alt15:41
*** SridharRamaswamy has quit IRC15:41
*** ashleighfarnham has joined #openstack-meeting-alt15:42
*** Longgeek has quit IRC15:45
*** marcusvrn has joined #openstack-meeting-alt15:45
*** mattgriffin has joined #openstack-meeting-alt15:46
*** marcusvrn1 has joined #openstack-meeting-alt15:47
*** vishwana_ has quit IRC15:49
*** vishwanathj has joined #openstack-meeting-alt15:49
*** marcusvrn has quit IRC15:49
*** wojdev has quit IRC15:51
*** marcusvrn has joined #openstack-meeting-alt15:52
*** marcusvrn1 has quit IRC15:54
*** coolsvap is now known as coolsvap|afk15:54
*** jbratton has joined #openstack-meeting-alt15:54
*** rwsu-afk is now known as rwsu15:55
*** armax has quit IRC15:55
*** armax has joined #openstack-meeting-alt15:55
*** diemt has joined #openstack-meeting-alt15:56
*** tellesnobrega has quit IRC15:58
*** rkukura has joined #openstack-meeting-alt15:58
*** tellesnobrega has joined #openstack-meeting-alt15:59
*** wojdev has joined #openstack-meeting-alt15:59
*** Leonr has joined #openstack-meeting-alt15:59
*** deepakcs has left #openstack-meeting-alt16:00
*** katyafervent is now known as katyafervent_awa16:00
*** yamahata has joined #openstack-meeting-alt16:00
*** elarson has joined #openstack-meeting-alt16:00
rkukurahi ML2ers16:00
*** ashleighfarnham has quit IRC16:00
GLauprehello16:01
shivharishi16:01
Sukhdevhello16:01
yamahatahi16:01
nuritvHi16:01
*** tdruiva has quit IRC16:01
rkukuralooks like we’ve got quorum16:02
* HenryG lurks16:02
rkukura#startmeeting networking_ml216:02
openstackMeeting started Wed Mar 11 16:02:56 2015 UTC and is due to finish in 60 minutes.  The chair is rkukura. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: networking_ml2)"16:02
openstackThe meeting name has been set to 'networking_ml2'16:03
*** sarob has joined #openstack-meeting-alt16:03
rkukura#topic Agenda16:03
*** openstack changes topic to "Agenda (Meeting topic: networking_ml2)"16:03
SukhdevHenryG: welcome16:03
rkukura#link https://wiki.openstack.org/wiki/Meetings/ML216:03
*** jbratton has left #openstack-meeting-alt16:03
rkukuraAnything specific to add to the agenda?16:03
*** nlahouti has joined #openstack-meeting-alt16:04
*** katyafervent_awa is now known as katyafervent16:04
shivharisk3 in Mar 1916:04
rkukura#topic Announcements16:04
*** openstack changes topic to "Announcements (Meeting topic: networking_ml2)"16:04
rkukuraFrom the neutron meeting:16:04
shivhariss/in/is/16:04
rkukuraFeature, String, and Dependency Freeze: March 1916:04
rkukuraRCs: April 9-2316:05
rkukuraKilo release: April 3016:05
*** zehicle_ has joined #openstack-meeting-alt16:05
*** cloudon has left #openstack-meeting-alt16:05
rkukuraAny other announcements?16:05
*** dkusidlo has quit IRC16:06
rkukura#topic ML2 Drivers decomposition discussion16:06
*** openstack changes topic to "ML2 Drivers decomposition discussion (Meeting topic: networking_ml2)"16:06
rkukuraAny updates, issues or questions on this?16:06
SukhdevI notice - great progress is being made on this effort16:07
shivharisrkukura: what was it about pinning neutron for mds/plugins in neuton meeting16:07
rkukurashivharis: good question16:07
*** bobmel has quit IRC16:08
rkukuraI didn’t exactly follow the argument why pinning was needed16:08
shivharisrkukura: seemingly breaks plugins that have already passed due to changes in neutron16:08
*** bobmel has joined #openstack-meeting-alt16:08
*** rushil has joined #openstack-meeting-alt16:08
Sukhdevshivharis: I missed the meeting - please provide more context16:09
shivharisarmax: if you are around can you please clarify for ML2'ers16:09
rkukurashivharis: Are you saying that the neutron changes actually break the driver CI? If so, don’t we want to know that?16:09
*** marun has joined #openstack-meeting-alt16:09
armaxshivharis: what exactly?16:09
shivharismarun, armax: need clarification on neutron pinning discussed in neutron meeting16:10
rkukuraarmax: Can you explain the rationale for pinning neutron versions in driver CI as discussed in the neutron meeting?16:10
armaxok16:10
*** enikanorov__ has joined #openstack-meeting-alt16:10
*** enikanorov has quit IRC16:10
*** jecarey has quit IRC16:10
*** EricGonczer_ has quit IRC16:10
armaxthe question is: at the moment both the drivers/plugins and aas services chase neutron’s tip of master16:10
*** jecarey has joined #openstack-meeting-alt16:11
*** kobis has quit IRC16:11
armaxarmax: however, this doesn’t have to be the only option16:11
*** wojdev has quit IRC16:11
*** ashleighfarnham has joined #openstack-meeting-alt16:11
*** pkoniszewski has quit IRC16:11
armaxservices, as well as drivers, may want to target a specific hash for neutron, which is deemed stable and working from an integration perspective16:12
*** manishg has joined #openstack-meeting-alt16:12
*** tdink has quit IRC16:12
*** rossella_s has quit IRC16:12
*** bryan_att_ has joined #openstack-meeting-alt16:12
rkukuraarmax: If the neutron hash is pinned, what is the point of triggering the CI on neutron changes? Am I missing something?16:13
shivharisarmax: so changes in neutron can break drivers even though at some point it passed CI etc, but what would be a good version, leave it to the developer of ml2drivers?16:13
*** bryan_att has quit IRC16:13
*** nkrinner has quit IRC16:13
*** jvrbanac has quit IRC16:13
*** codekobe has quit IRC16:13
*** briancurtin has quit IRC16:13
*** bryan_att_ is now known as bryan_att16:13
*** hemanth has joined #openstack-meeting-alt16:13
*** sdake__ has joined #openstack-meeting-alt16:13
*** venkatesh_ has joined #openstack-meeting-alt16:13
*** esheffield__ has joined #openstack-meeting-alt16:13
armaxthe need of having CI checking master is so that one can verify whether the pin can be bumpted16:13
armaxbumped16:14
*** matt__ has joined #openstack-meeting-alt16:14
*** wendar_ has joined #openstack-meeting-alt16:14
*** marcusvrn has quit IRC16:14
*** smazziotta has quit IRC16:14
*** sbalukoff has quit IRC16:14
*** venkatesh has quit IRC16:14
*** esheffield_ has quit IRC16:14
*** Guest73152 has quit IRC16:14
*** ttx has quit IRC16:14
*** stevebaker has quit IRC16:14
*** timsim has quit IRC16:14
*** jroll has quit IRC16:14
*** marcusvrn has joined #openstack-meeting-alt16:14
*** aglarendil has quit IRC16:14
*** zehicle has quit IRC16:14
*** cyeoh has quit IRC16:14
*** wendar has quit IRC16:14
*** mattoliverau has quit IRC16:14
*** russellb has quit IRC16:14
*** zigo_ has quit IRC16:14
*** smazziotta has joined #openstack-meeting-alt16:14
*** zigo_ has joined #openstack-meeting-alt16:14
*** mwang2__ has quit IRC16:15
*** timsim has joined #openstack-meeting-alt16:15
*** russellb has joined #openstack-meeting-alt16:15
*** tdink has joined #openstack-meeting-alt16:15
*** jroll has joined #openstack-meeting-alt16:15
Sukhdevarmax: I am confused - folks have stable versions (of neutron) and master - are you talking about pining some version of master itself?16:15
*** mwang2__ has joined #openstack-meeting-alt16:15
*** zehicle has joined #openstack-meeting-alt16:15
*** bdpayne has joined #openstack-meeting-alt16:15
armaxthat was simply a proposal at the moment16:16
*** stevebaker has joined #openstack-meeting-alt16:16
*** ttx has joined #openstack-meeting-alt16:16
*** scheuran has quit IRC16:16
*** jvrbanac has joined #openstack-meeting-alt16:16
*** jroll has quit IRC16:16
*** jroll has joined #openstack-meeting-alt16:16
*** cyeoh has joined #openstack-meeting-alt16:16
*** sbalukoff has joined #openstack-meeting-alt16:16
*** aglarendil has joined #openstack-meeting-alt16:16
*** rossella_s has joined #openstack-meeting-alt16:16
*** nkrinner has joined #openstack-meeting-alt16:17
*** rmoe has quit IRC16:17
*** sdake_ has quit IRC16:17
shivharisarmax: i guess we should wait till this is finalized, we can get clarification at a later time16:17
rkukuraSeems like ML2 driver owners should track this, but no immediate change is required/recommended, right?16:17
armaxrkukura: correct16:18
sadasuarmax: is this something that is going to be flushed out in Kilo, or is it something you are exploring for Liberty16:18
*** [1]JonasB has quit IRC16:18
armaxlbaas is going to experiemnt with this16:18
shivharisarmax: thanks16:18
armaxI wouldn’t recommend taking any action at the moment16:18
armaxbut it’s important to be aware that the option of pinning is there,16:18
rkukuraWhile armax is here, are there any other questions for him regarding decomosition?16:18
armaxif one does pin, then yes, the CI tracking master is only there to validate whether the pin can be moved forward16:18
sadasuI have one16:18
armaxmakes sense?16:19
*** briancurtin has joined #openstack-meeting-alt16:19
HenryGThe biggest hump the vendor repos have to get over right now is to switch away from oslo-incubator usage16:19
rkukurasadasu: go adead…16:20
Sukhdevarmax: In general, it makes sense - but, the devil is in the details :-)16:20
*** codekobe has joined #openstack-meeting-alt16:20
shivharisarmax: run CI twice to see if we can move the pin?16:20
*** sarob has quit IRC16:21
sadasuarmax: might have to give this more thought....do you really want to add dependency on vendor CI for pinning? We want to decouple correct?16:21
*** EricGonczer_ has joined #openstack-meeting-alt16:21
armaxshivharis: you run the CI once per project, how many configurations you’re testing it’s up to you16:21
sadasuvendors should be picking a pin based on how they see their CIs behaving, but those are very initial thoughts16:21
armaxsadasu: the end goal is to minimize the depedency yes16:22
sadasumy question was regarding UTs on Neutron side16:22
armaxsadasu: what about them?16:22
sadasuwith the Neutron shim being very thin, and UTs not being able to import modules from stackforge repos16:22
*** marcusvrn1 has joined #openstack-meeting-alt16:22
*** kobis has joined #openstack-meeting-alt16:22
*** sarob has joined #openstack-meeting-alt16:22
*** marcusvrn has quit IRC16:23
sadasuUTs on the Neutron side end up mocking so much that there doesnot seem much value in it16:23
sadasuso is there a hard requirement for having UTs on the Neutron side?16:24
armaxsadasu: no16:24
rcurransadasu, all cisco_nexus md UTs have been moved to stackforge16:24
GLaupreUTs?16:25
*** gokrokve has joined #openstack-meeting-alt16:25
rkukurasadasu: I think whether UTs are needed on the neutron side really depends on how thin vs. thick the specific shim is. If the shim for example includes port binding logic, that probably should be tested in neutron using mocked versions of underlying calls.16:25
sadasurcurran: correct, but the mech driver is a pass through16:25
*** marcusvrn has joined #openstack-meeting-alt16:25
sadasunot all mech drivers are split that way16:25
rcurransadasu, it'a an option. just fyi16:25
Sukhdevrkukura: yes, you are correct16:26
*** nshaikh has left #openstack-meeting-alt16:26
armaxsadasu: correct…it’s not about running UTs here or there16:26
*** esker has quit IRC16:26
*** MarkAtwood has joined #openstack-meeting-alt16:26
*** SumitNaiksatam has joined #openstack-meeting-alt16:27
*** marcusvrn1 has quit IRC16:27
SukhdevI guess the critical question to be answered is - if anything changes on the neutron side (the API, for example), how and where do you want to catch it?16:27
*** gokrokve has quit IRC16:27
armaxsadasu: so long as you ensure effective coverage, unit or otherwise it doesn’t matter where it leaves but how to run it16:28
sadasurkukura: point taken, but a very small set of UTs...we can run a full detailed set of UTs on stackforge..so why not do everything there16:28
armaxs/leaves/lives/16:28
*** jehb has quit IRC16:28
*** emagana has quit IRC16:28
sadasuarmax: yes, my question was about where it lives...we are definitely ensuring good coverage16:28
rkukurasadasu: I think there is flexibility16:28
*** emagana has joined #openstack-meeting-alt16:28
armaxeven if it existed in your own trees and you have external dependencies16:29
*** ijw has joined #openstack-meeting-alt16:29
armaxthen it’s the ‘trigger’ that counts16:29
sadasuthanks for all responses/inputs16:29
shivharisunit tests should exists where the code exists (repo'wise)16:29
sadasuarmax: didn't get that one16:29
rkukurashivharis: Don’t want to reduce neutron’s code coverage metrics16:30
sadasushivharis: agreed in theory..but UTs have an issue that if you import a module in Neutron that in turn imports from stackforge, UTs implode16:31
*** gokrokve_ has joined #openstack-meeting-alt16:31
sadasusolution for that would be to mock16:32
Sukhdevsadasu: you mean circular dependancy16:32
*** mtanino_away has quit IRC16:32
sadasuSukhdev: correct16:32
armaxsadasu: that’s one option, the other option is to move that type of coverage elsehwere16:32
*** emagana has quit IRC16:33
armaxsadasu: and execute it based on what changes may impact the code under coverage16:33
*** sdake_ has joined #openstack-meeting-alt16:33
sadasuarmax: yes, that can be tested well on the stackforge side since we don't have the import restriction16:33
rkukuralets try to wrap up the decomposition discussion in the next couple minutes so we have time for the rest of the agenda16:34
*** rcurran_ has joined #openstack-meeting-alt16:34
SukhdevHenryG: care to elaborate on oslo-incubator issue?16:34
*** tonytan4ever has quit IRC16:34
shivharisarmax: thanks16:35
armaxSukhdev: there may be breaking changes due to the handling/transition from openstack/common to oslo graduated libraries16:35
HenryGSukhdev: neutron is switching most of the oslo stuff to incubated oslo packages16:35
sadasuarmax: thanks...I think I have my questions answered.16:35
*** rmoe has joined #openstack-meeting-alt16:36
armaxihar will be compiling a wiki page, a journal if you will, where these issues are documented16:36
HenryGSukhdev: https://wiki.openstack.org/wiki/Neutron/VendorSplitPackaging16:36
armaxfor instance this one: https://review.openstack.org/#/c/159638/ it’s going to break all the projects16:36
sadasushould we be looking out for a specific commit that will bring these changes?16:36
*** wojdev has joined #openstack-meeting-alt16:37
armaxthat depedent on Neutron and use openstack/common/log16:37
SukhdevHenryG, armax : Thanks for the heads up - will go and read this16:37
*** rcurran has quit IRC16:37
*** sdake__ has quit IRC16:37
sadasuthanks for the links16:37
*** pkoniszewski has joined #openstack-meeting-alt16:38
rkukuraare we ready to move onto the next agenda item?16:38
rkukuraguess so…16:39
Sukhdevrkukura: yes16:39
rkukura#topic ML2 Sync and error handling (Task Flow)16:39
*** openstack changes topic to "ML2 Sync and error handling (Task Flow) (Meeting topic: networking_ml2)"16:39
rkukuramanishg: You around?16:39
shivharismanishg: hi16:39
*** annashen has joined #openstack-meeting-alt16:40
rkukuraI’d at least like to remind people to review and comment on https://review.openstack.org/#/c/154333/16:40
rkukuraI added one comment this AM.16:40
shivharisi had some questions, i guess i will insert in rhe review16:41
*** dizquierdo has quit IRC16:41
rkukuraOK, anything else on this today?16:41
*** kebray has joined #openstack-meeting-alt16:41
rkukuraif not…16:42
*** carl_baldwin has quit IRC16:42
rkukura#topic Bugs16:42
*** openstack changes topic to "Bugs (Meeting topic: networking_ml2)"16:42
shivharisbugs, we are looking good, i am hoping the high priority ones will be taken care of by K3 (Mar 19) - otherwise it will be very hard16:42
manishgrkukura: around.  sorry was distracted!  will wait until after bugs16:43
shivharisif anyone needs any help - reviews for bugs - now is the time to ask16:43
shivharisnot much to add further..16:44
rkukurashivharis: On https://bugs.launchpad.net/neutron/+bug/1367391, I was making progress, but am just getting back to it now. Hopefuily will have patch in review by 3/1616:44
openstackLaunchpad bug 1367391 in neutron "ML2 DVR port binding implementation unnecessarily duplicates schema and logic" [High,In progress] - Assigned to Robert Kukura (rkukura)16:44
shivharisrkukura: this is high pri bug, k3 then?16:44
*** annashen has quit IRC16:45
rkukurashivharis: yes16:45
shivharisrkukura: thanks16:45
*** Longgeek has joined #openstack-meeting-alt16:45
shivharislets move on ..16:45
rkukurano other bugs to discuss?16:46
shivharisi am worried about one - really:16:46
shivharishttps://bugs.launchpad.net/neutron/+bug/137873216:46
openstackLaunchpad bug 1378732 in neutron "migrate_to_ml2 script doesn't work for Juno release" [High,New] - Assigned to Mark McClain (markmcclain)16:46
shivharisi have pinged, will ping again, we need some resolution - i ping on this again16:47
shivharisi will ping on this again16:47
shivhariswill seek mestery on this16:48
rkukurashivharis: Thanks.16:48
rkukuraAny other bugs to discuss?16:48
shivharisthis one is in limbo16:48
*** carl_baldwin has joined #openstack-meeting-alt16:48
*** annashen has joined #openstack-meeting-alt16:48
shivharisi meant the previous one16:48
rkukura#topic: ML2 Sync and error handling (Task Flow) - revisited16:49
*** openstack changes topic to ": ML2 Sync and error handling (Task Flow) - revisited (Meeting topic: networking_ml2)"16:49
rkukuramanishg: Did you have an update on this?16:49
manishgrkukura: I'll look at your comment.  No other comments there.  one question16:49
rkukuraok16:49
rkukurago ahead manishg …16:49
manishgSukhdev wanted to talk about changing the state back to 'Creating'16:49
manishgafter it was created.16:50
manishgI'm not sure how that would work?  The device would have to generate an event through neutron REST API16:50
Sukhdevmanishg: I wanted to discuss the issue that I raised last week -16:50
*** zehicle_ has quit IRC16:50
rkukuraback to creating? Or start in creating, and change to active once complete?16:50
manishgrkukura:  normal flow  Null -> creating -> active (once all drivers are happy)16:50
rkukuraright16:51
manishgSukhdev wanted : Null-> creating -> Active -> creating (in case one of the devices is unhappy later)16:51
Sukhdevwell, it can be changed to any state other than active - so that no action is taken while the back-end is going through recreating the state16:51
*** andreykurilin_ has joined #openstack-meeting-alt16:51
manishgSukhdev: are you proposing that once we add state to the resource attributes, the REST API should allow 'updating' the internal state?16:52
Sukhdevmanishg, possibly - or any other way for the back-end to tell the front end to hold off until I tell you to go again16:53
shivharismanishg: will this lead the system to hang waiting for some completion16:53
manishgrkukura: other pending item in my plate is to write something about accumulating and queueing while it's not ACTIVE yet.16:53
rkukuraI think we need to think hard about how we want these states to effect the client workflow. We could allow all REST APIs all the time, or reject or block them in certain states. I lean towards allowing them, and treating the backends as “eventually consistent”.16:53
*** MarkAtwood has quit IRC16:53
*** openstack has joined #openstack-meeting-alt16:54
*** ChanServ sets mode: +o openstack16:54
SukhdevWe have two cases;16:54
manishgrkukura: it will also require pruning to avoid useless work.  update (a --> 1), update (a-->2).... if these are independent only latest prevails, etc.16:55
rkukuramanishg: We could avoid queuing if we could make updates sync to the current state, rather than treat each update as an event.16:55
SukhdevOne is to make sure that top-> bottom operations are sync'ed correctly16:55
*** paul_glass has joined #openstack-meeting-alt16:55
Sukhdevyou are all discussing this case16:55
manishgshivharis: yes, that's what we are discussing.  state-diagram (allow only certain events) or all of them at all times.16:56
Sukhdevthe second case is - assume you have 10K ports that have sucessfully been created - the word is happy and the back-end resets16:56
*** andreykurilin_ has quit IRC16:56
rkukuraSukhdev: In your 2nd case, I’d like the fact the back-end is out-of-sync to be visible in the API, but not to effect the workflow if possible.16:57
*** vinod1 has joined #openstack-meeting-alt16:57
Sukhdevrkukura: that is why I suggested we can have some kind of global notification/state, if needed16:58
manishgSukhdev: in the end , whatever we do needs to fit inside neutron framework.  Should ML2 or other plugins be modifying the db state from within without really a standard RPC event or REST API event?16:58
rkukuraWe’ve got 2 minutes left - if anyone has anything they’d really like to mention in Open Discussion, let me know.16:58
Sukhdevbut, the idea will be when the back-end is syncing, we would not want the resources states be changing - otherwise you have a never ending loop16:58
manishgso Null -> Active is understandable (since it's in middle of completing the action)16:58
*** n0ano has joined #openstack-meeting-alt16:58
Sukhdevespecially in a large scale depoyments16:58
manishgbut the other stuff doesn't seem to fit in the framework - regardless of what solution we use.16:59
*** i-m-in has joined #openstack-meeting-alt16:59
*** tdruiva has joined #openstack-meeting-alt16:59
SukhdevWe can take this offline - but, think scale :-):-)16:59
*** mugsie has joined #openstack-meeting-alt16:59
*** sergef has joined #openstack-meeting-alt16:59
matrohonI would appreciate  ML2ers review on that : https://review.openstack.org/#/c/163178/16:59
manishgthinking scale.16:59
manishgbut need to also think framework.16:59
rkukuramatrohon: thanks17:00
*** nshah has joined #openstack-meeting-alt17:00
Sukhdevmanishg:-)17:00
rkukuramanishg: Lets continue this discussion in gerrit17:00
manishgthis issue of active-> creating is independent of scale though :)17:00
rkukuraOur time is up17:00
rkukurathanks everyone!17:00
manishgok, next time!17:00
manishgthanks.17:00
Sukhdevbye17:00
rkukura#endmeeting17:00
rkukurabye17:00
manishgbye17:00
GLauprebye17:01
banixbye17:01
yamahataby17:01
sadasuthanks!17:01
KiallJust me, or is the meeting bot broke?17:01
shivharisbye17:01
Kiall#startmeeting Designate17:01
openstackMeeting started Wed Mar 11 17:01:26 2015 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
*** openstack changes topic to " (Meeting topic: Designate)"17:01
openstackThe meeting name has been set to 'designate'17:01
*** nuritv has left #openstack-meeting-alt17:01
*** nlahouti has left #openstack-meeting-alt17:01
mugsieo/17:01
KiallWeird - It missed the end of the ML2 meeting17:01
elarsono/17:01
KiallAnyway.. Who's about?17:01
rkukuraKiall: noticed that17:01
*** sadasu has quit IRC17:01
vinod1o/17:02
elarsonKiall: I noticed the ~openstack bot quit and rejoined in the middle of the last meeting17:02
timsimo?17:02
Kiall#topic Action Items from last week17:02
*** openstack changes topic to "Action Items from last week (Meeting topic: Designate)"17:02
*** kobis has quit IRC17:02
*** manishg has left #openstack-meeting-alt17:02
KiallSo - We skipped last week, and I had 2 actions from the week both. Both of which I fogot about :/17:02
*** Longgeek has quit IRC17:02
*** mwagner_lap has quit IRC17:03
KiallBoth were to do with old-style backends, I'll block off a few hours tomorrow to make that happen.17:03
KiallApologies :(17:03
*** jbratton has joined #openstack-meeting-alt17:03
Kiall#topic Kilo Release Status (kiall - recurring)17:03
*** openstack changes topic to "Kilo Release Status (kiall - recurring) (Meeting topic: Designate)"17:03
Kiall#link https://launchpad.net/designate/+milestone/kilo-317:03
Kiallk3 (aka feature freeze) is Mar 19th.. 8 days17:03
*** salv-orlando has quit IRC17:03
KiallWe have a bunch of stuff in progress  - TSIG, Validation, Secondaries and Pools API stuff17:04
Kialls/stuff/features/17:04
timsimWe want all that merged by then, yeah?17:04
KiallWe'll need to try get all these in before 19th, and switch to find/fix after..17:04
mugsieyeah17:05
*** tonytan4ever has joined #openstack-meeting-alt17:05
*** rkukura has left #openstack-meeting-alt17:05
mugsieyou may have noticed a ton of validation stuff going up, that needs review soon - there is a ton of work left on it17:05
*** radez is now known as radez_g0n317:05
*** kebray has quit IRC17:06
timsimCool. Review all the things then.17:06
KiallTSIG stuff has some -1's, I'll address those today.17:06
KiallValidation Stuff - Parts are ready I think, but Graham is still working on them.17:06
KiallSecondaries - Mostly there, some known things we'll want to fix (using attributes like we decided was a bad idea for pools - but that's a fix we can do later)17:06
KiallPools - I've been on/off this over the last week - nearly there, will be up and working before 19th.17:06
vinod1Is secondary zones targeted for k3?17:06
KiallI think all the other reviews are minor features (e.g. the "Guru Meditation Reports") or bugfixes..17:06
*** annashen has quit IRC17:07
*** tosky has joined #openstack-meeting-alt17:07
*** pkoniszewski has quit IRC17:07
*** annashen has joined #openstack-meeting-alt17:07
Kiallvinod1: it seems to be working well enough - at least with a few more fixes - I think we can try merge in k317:07
*** GLaupre has quit IRC17:07
*** shivharis has left #openstack-meeting-alt17:07
timsimekarlso might riot if we don't ;)17:07
mugsie:)17:07
*** johnma has joined #openstack-meeting-alt17:08
*** suro_ has joined #openstack-meeting-alt17:08
*** sergef has quit IRC17:08
KiallAt HP - mugsie / ekarlso are working 100% on upstream stuff right now, while I'm split between an internal project and upstream.. So we should have time to get things solid enough to merge.17:08
*** SridharRamaswamy has joined #openstack-meeting-alt17:08
*** esker has joined #openstack-meeting-alt17:08
KiallAnyway - re bugs - are we aware of any show stoppers?17:09
*** SumitNaiksatam has quit IRC17:09
mugsieis bug 1424621 still open?17:09
openstackbug 1424621 in Designate "eventlet 0.17.0 has broke dns.reversename.from_address() " [Critical,In progress] https://launchpad.net/bugs/1424621 - Assigned to Kiall Mac Innes (kiall)17:09
*** tonytan4ever has quit IRC17:10
mugsieand I would like 1338256 to be before k3, but it may not make iut17:10
*** ivar-lazzaro has joined #openstack-meeting-alt17:10
mugsieit*17:10
mugsiebug 1338256 *17:10
openstackbug 1338256 in Designate "There's no record validation in v2" [Critical,Triaged] https://launchpad.net/bugs/1338256 - Assigned to Slawek Kaplonski (slawek-t)17:10
KiallEhh - I think that can be closed. It's still broke with 0.17.0, but 0.17.1 or 0.17.2 fix it17:10
*** ivar-lazzaro has quit IRC17:11
Kiallthat's what your working on ;) I guess I call that a feature rather than bug ;)17:11
*** rcurran_ has quit IRC17:11
*** ivar-lazzaro has joined #openstack-meeting-alt17:11
timsimThat bug fix in eventlet broke things for us :P I've got https://github.com/eventlet/eventlet/pull/212 going17:11
*** azemlyanov has quit IRC17:11
*** ivar-lazzaro has quit IRC17:12
*** suro_ has left #openstack-meeting-alt17:12
Kialltimsim: glad you found the source of that!17:12
*** kobis has joined #openstack-meeting-alt17:12
KiallAny others?17:12
*** tonytan4ever has joined #openstack-meeting-alt17:12
timsimhttps://bugs.launchpad.net/designate/+bug/1427411  maybe?17:12
openstackLaunchpad bug 1427411 in Designate "Recordset updates remain PENDING until periodic sync" [Undecided,New]17:12
*** ivar-lazzaro has joined #openstack-meeting-alt17:13
mugsiehumm17:13
mugsieyes17:13
timsimI think vinod1 might be working on this17:13
KiallHumm, I hadn't seen that one. vinod1's making changes around that code?17:13
vinod1I am investigating that one currently17:14
ekarlsoello :p17:14
*** harlowja_away is now known as harlowja_17:14
*** dimtruck is now known as zz_dimtruck17:14
Kiallvinod1: cool, I'll mark as k3 .. If it doesn't land, it's a bugfix and can land in rc phase...17:14
KiallOkay - So, before we move on, if we can all (myself included ;)) make some time to review the features that need to land by thu of next week :)17:15
timsimSounds good.17:15
vinod1will do17:15
KiallIf there's non-critical bugs in them, and it's nearing mid-next week, +2 and file a critical/blocker for rc1 IMO.17:16
*** kobis has quit IRC17:16
timsimFair enough.17:16
KiallYea, we have a month of feature freeze after k3, but before kilo releases, so I think that makes sense :)17:17
KiallOkay, let's move on..17:17
*** zz_dimtruck is now known as dimtruck17:17
Kiall#topic Remove the APIv2 wrapping object (mugsie)17:17
*** openstack changes topic to "Remove the APIv2 wrapping object (mugsie) (Meeting topic: Designate)"17:17
Kiall#link https://etherpad.openstack.org/p/designate-apiv2-wrapping-object17:18
*** matrohon has quit IRC17:18
mugsieso -  this has been annoying the hell out of me recently17:18
Kiallmugsie - all yours..17:18
*** sarob has quit IRC17:18
*** e0ne is now known as e0ne_17:18
mugsieI don't think we need it, it adds complexity allover the place, and should just go away17:18
mugsieor, does anyone disagree?17:19
mugsieor even care ;) ?17:19
timsimI agree.17:19
vinod1i was just thinking of this last week - so I agree17:19
KiallBack when we did the V2 - It was for consistency with other OS APIs.. but they all went different directions in the end anyway.. So.. Yea.17:19
timsimHah.17:19
mugsiecool. I will call this consensus17:19
vinod1would the change apply to all of v2?17:20
mugsieI can remove it as part of the views changes17:20
mugsieyeah17:20
* Kiall feels like saying no, just to wind mugsie up17:20
*** resker has joined #openstack-meeting-alt17:20
timsimOh please do.17:20
mugsieany request that returns a single resource17:20
mugsiewould no longer have the resource name17:20
KiallWell - listings still have it, resources do not...17:20
vinod1how about posts?17:21
mugsiesame - gone17:21
KiallI've updated the etherpad with a little more..17:21
mugsieand patches ;)17:21
*** sarob has joined #openstack-meeting-alt17:21
*** pc_m has left #openstack-meeting-alt17:22
*** kobis has joined #openstack-meeting-alt17:22
mugsieand I fixed them ;)17:22
KiallI think I've confused myself with the etherpad changes.. lol17:22
Kiallmugsie: all correct now? So still a "yep" for evertyone?17:23
Kialleveryone*17:23
mugsielooks right17:23
timsimYup, sounds good17:23
mugsiesorry ekarlso - v2 bindings will have to change again ;)17:23
ekarlsowhat does that mean ?17:23
*** esker has quit IRC17:24
vinod1looks good to me17:24
elarson+17:24
mugsiethe output of the API is going to be different17:24
elarson+1 even17:24
KiallOkay.. Calling it settled so. Anything else before we move on?17:24
* mugsie is now happy17:24
*** kobis has quit IRC17:25
timsimI'm good17:25
mugsiegood? thats pushing it a bit :D17:26
timsimI'm ok17:26
KiallNext topic will be.. short.. Since I failed to do my actions :(17:26
Kiall#topic "Old Style" Backend - Status/What's TODO? (kiall)17:26
KiallI had said I'd get a POC of this done, but totally forgot. I'll block a few hours tomorrow to Just Do It? (Wonder if I need a little "TM of Nike" after that? ;))17:26
*** openstack changes topic to ""Old Style" Backend - Status/What's TODO? (kiall) (Meeting topic: Designate)"17:26
mugsiethaty better timsim17:26
*** kobis has joined #openstack-meeting-alt17:26
*** Poornima has quit IRC17:26
*** sarob has quit IRC17:26
KiallSo - I'm not sure we have anything new here to discuss till I get that done.. Thoughts?17:26
mugsienope - we need to have a POC i think17:27
timsimDon't think so.17:27
*** MarkAtwood has joined #openstack-meeting-alt17:27
KiallOkay.. Let's move onto timsim so ;)17:27
Kiall#topic Bug triage (timsim-recurring)17:27
*** openstack changes topic to "Bug triage (timsim-recurring) (Meeting topic: Designate)"17:27
Kiall#link https://bugs.launchpad.net/designate/+bugs?search=Search&field.status=New17:27
*** dimtruck is now known as zz_dimtruck17:27
timsimThree untriaged bugs17:28
timsimhttps://bugs.launchpad.net/designate/+bug/142741117:28
openstackLaunchpad bug 1427411 in Designate "Recordset updates remain PENDING until periodic sync" [High,New]17:28
timsimThat's already k3 high, so I'm just going to triage that one?17:28
*** wendar_ is now known as wendar17:28
mugsieyup17:28
Kialltimsim: please do :) I thought I did that earlier along with the for k3 change17:28
timsimk17:28
timsimhttps://bugs.launchpad.net/designate/+bug/142566817:28
openstackLaunchpad bug 1425668 in Designate "Poor error message when using same database for designate and the pool manager cache" [Undecided,New]17:29
*** e0ne_ has quit IRC17:29
timsimProbably a nice-to-have type thing?17:29
mugsieyeah17:29
KiallI think that will likely land post k3, but the LP milestone doesn't exist yet17:29
mugsienot a show stopper, and somehting that could be rc117:29
KiallI can ask Thierry to create that tomorrow..17:29
*** kobis has quit IRC17:29
timsimAlright, I'll leave it the way it is so that we remember to put it there next week17:30
*** kobis has joined #openstack-meeting-alt17:30
mugsie+117:30
Kiallperfect17:30
timsimhttps://bugs.launchpad.net/designate/+bug/142511717:30
openstackLaunchpad bug 1425117 in Designate "Designate does not work with postgres" [High,New]17:30
mugsieyeah17:30
mugsiethis is .... interesting17:30
*** e0ne has joined #openstack-meeting-alt17:30
mugsiehow do we want to mark this17:30
timsimWould we have to like...go back and edit db migrations to fix that?17:31
KiallWe (technically) support Postgres.. So it's certainly a bug.. I would mark for rc1, it's just not going to happen before then I think17:31
mugsietimsim: yes17:32
*** sarob has joined #openstack-meeting-alt17:32
Kialltimsim: yea, we've done it before for postgres! The trick is to make sure you don't change anything which would affect mysql/sqlite :/17:32
*** SumitNaiksatam has joined #openstack-meeting-alt17:32
KiallWhich is sadly harder than it should be for some changes..17:32
KiallI wonder if, once this is fixed, we move the bind9 gate to Postgres.. (PowerDNS prefers MySQL!)17:33
*** zehicle_ has joined #openstack-meeting-alt17:33
Kiall(I don't think it even actually supports psql..)17:33
timsimSounds like a good idea.17:33
timsimSo we don't have a rc1 milestone, so same story as the last one?17:34
mugsieyeah, testing postgres would be a good first step ;)17:34
KiallOh .. It does support it.. Either way, moving one of the gates over (or adding another) would help17:34
Kialltimsim: yea, I've got a sync up with Thierry tommorrw - he creates all those for the projects :)17:34
timsimSounds good. :) We're done then17:35
vinod1I see a couple of bugs that are not triaged and do not show up on the list17:35
vinod1https://bugs.launchpad.net/designate/+bug/142742517:35
openstackLaunchpad bug 1427425 in Designate "Zones remain in ERROR indefinitely with the noop pool manager cache" [Undecided,In progress] - Assigned to Vinod Mangalpally (vinod-mang)17:35
KiallI'll ask him to create rc117:35
vinod1https://bugs.launchpad.net/designate/+bug/142743317:35
openstackLaunchpad bug 1427433 in Designate "Pool Manager Recovery Code Needs to Update Status in Central" [Undecided,In progress] - Assigned to Vinod Mangalpally (vinod-mang)17:35
timsimYeah I think those just need importance?17:36
vinod1Fix is in code review for both of those - https://review.openstack.org/#/c/162754/17:36
Kiallhttp://paste.openstack.org/show/191653/ is the "untriaged-bot" that spams our room twice a day...17:36
KiallMaybe it's wrong? or the agenda link doesn't get everything? Not 100% sure :)17:36
mugsieagenda link is wrong i think17:37
timsimYeah, L27 looks for importance17:37
timsimGood catch vinod1, high for both of those?17:37
*** Sukhdev has quit IRC17:37
KiallI robbed it from tripleo - I'm betting they did 2 searches for a reason..17:37
*** nshah has left #openstack-meeting-alt17:38
vinod1timsim: I am ok with that17:38
Kialltimsim: I think so, both seem like it17:38
*** andriikolesnikov has quit IRC17:38
timsimCool.17:38
vinod1There is one other bug too - without the importance field marked - https://review.openstack.org/#/c/162754/17:39
vinod1wrong link17:39
vinod1https://bugs.launchpad.net/designate/+bug/141633717:39
Kiallwrong link?17:39
openstackLaunchpad bug 1416337 in Designate "Designate server create with concurrent request is not listing all servers even after successful creation." [Undecided,Incomplete]17:39
timsimYeah, that one is waiting for more info from the reporter.17:39
mugsiewe are still waiting for that reporter to come back17:39
KiallThat probably shouldn't be showing up - Incomplete since someone here (can't remember who) tried + failed to reproduce17:39
timsimIt's just that importance field that's catching it. Maybe just put it at a Low, and if they come back, change it?17:40
*** zz_dimtruck is now known as dimtruck17:40
timsimProbably close it out at the end of Kilo otherwise17:40
*** annashen has quit IRC17:41
KiallWell the bot code attempts to filter those out, clearly it's failing though :)17:41
*** vks has quit IRC17:41
*** e0ne has quit IRC17:41
*** annashen has joined #openstack-meeting-alt17:41
KiallAnyway, I'd agree with timsim - Low - It's not an end user or commonly called API17:42
*** igordcard_ has joined #openstack-meeting-alt17:42
*** devlaps has joined #openstack-meeting-alt17:42
timsimAlright, actually done ;)17:42
KiallCool :) Moving on so..17:42
Kiall#topic Open Discussion17:42
*** openstack changes topic to "Open Discussion (Meeting topic: Designate)"17:42
KiallAnything off-agenda to discuss?17:42
mugsieNot from me :)17:43
*** sreshetn1 has quit IRC17:43
*** jschwarz has quit IRC17:43
vinod1Nothing from me17:43
timsimI've noticed situations in Bind9 where we send a create/delete, and for some reason the thing actually happens, but the Pool Manager thinks it failed, and it gets in this nasty loop where it's trying to rndc addzone/delzone things that have already been done, which fail and get retried forever.17:44
KiallI've managed to spot that once with PowerDNS too - but didn't find the root cause17:44
timsimI could see this happening in other backends as well, I'm wondering if maybe we should take some stance on where to fix this, in the Pool Manager itself, or maybe in the backend (ie, Bind9 Backend checks before it deletes if something has been deleted, and if so, returns success without calling delzone)17:44
timsimI had a particularly nasty incident in Bind9 yesterday w/ the agent where it kept retrying like 100 delzones :P17:45
*** crobertsrh has joined #openstack-meeting-alt17:45
ekarlsoSo17:45
ekarlsoV2 bindings, what's bad there again ?17:45
Kialltimsim: I think it's probably somthing we need to do driver by driver17:45
KiallEach will have a differnt way of really knowing if the task suceeded17:45
timsimKiall: That was my opinion. That way it just works on a periodic recovery/sync17:46
*** crobertsrh has left #openstack-meeting-alt17:46
*** MarkAtwood has quit IRC17:46
elarsonnot sure if it could work, but if there is a validation function assigned to each operation based on the driver it could be called before retrying the action.17:47
Kialltimsim: how often have you managed to see it? I've only seen it once naturally and took 100s of requests to reproduce17:47
Kiallekarlso: 2 conversations at once in IRC - will come back after this one is done ;)17:47
Kiallekarlso: 2 conversations at once in IRC is hard - will come back after this one is done ;)*17:47
* elarson imagines something being added to the message on the queue17:47
timsimI've seen it fairly often when working with situations where network connectivity was spotty or firewalls were going up and down, or (yesterday) when delzones were taking longer than a TCP timeout for some calls.17:48
mugsievalidation might be a good one ...17:48
mugsiebut that should be donje in the backend I think17:48
*** mwagner_lap has joined #openstack-meeting-alt17:48
Kialltimsim: That might explain it for bind9 for powerdns, it's a SQL call, and when it's happend to me, everything was local on 1 VM17:48
*** matrohon has joined #openstack-meeting-alt17:49
Kiallbut for powerdns*17:49
KiallMaybe there's a more basic root cause somewhere?17:49
timsimThe other way to do it would basically be to call MiniDNS for that type of change (create delete) and see if it happened before retrying in periodic x17:49
timsimKiall: I think it can happen in a variety of different situations. Basically anywhere the message coming back to Designate after reaching out to the backend doesn't get there.17:49
KiallI'm guessing the update_status call -> central? or another call?17:50
timsimWhat I said two msgs up there is similar to what elarson is saying17:50
*** sarob has quit IRC17:51
timsimWell agent for example goes Mdns/PM->Agent -/> Mdns/PM17:51
timsimIf that connection is severed for some reason, then mdns/pm assumes failure17:51
KiallOkay - You have a better handle on this than anyone else it seems ;) Pretty sure we can trust your judgement on a fix!17:51
timsimI would think if Someone---SQL Query---> PDNS and it timed out, but the thing actually worked, same issue17:51
timsim:P I've been thinking about it a lot in the last 24 hours17:52
mugsie:)17:52
*** mtanino has joined #openstack-meeting-alt17:52
timsimI didn't really mean to hijack the meeting, just thought I'd mention it :x17:52
Kialllol :P17:52
timsimI'll file a bug and put my thoughts down there, how about that?17:53
KiallOkay .. ekarlso.. re v2 bindings, mugsie's proposed change https://etherpad.openstack.org/p/designate-apiv2-wrapping-object changes the V2 API.. I think that's what he meant17:53
*** sarob has joined #openstack-meeting-alt17:53
mugsietimsim: +117:53
*** thomnico has joined #openstack-meeting-alt17:53
mugsieekarlso: what Kiall said ^17:54
*** achanda has joined #openstack-meeting-alt17:54
Kiallekarlso seems to be AFK - I'm betting a certain new baby called him over :) Oh well! Anything else before we call it a day?17:54
*** [1]JonasB has joined #openstack-meeting-alt17:54
*** _nadya_ has quit IRC17:54
* mugsie has nothing17:55
timsimI'm ok ;)17:55
*** i-m-in has quit IRC17:55
KiallGuess that's it so! thanks all :) Will be a busy week getting stuff in before 19th.. See you in #openstack-dns :)17:55
mugsie0/17:55
Kiall#endmeeting17:56
*** openstack changes topic to ": ML2 Sync and error handling (Task Flow) - revisited (Meeting topic: networking_ml2)"17:56
openstackMeeting ended Wed Mar 11 17:56:03 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2015/designate.2015-03-11-17.01.html17:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2015/designate.2015-03-11-17.01.txt17:56
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2015/designate.2015-03-11-17.01.log.html17:56
*** vinod1 has left #openstack-meeting-alt17:56
mugsie#endmeeting17:56
*** mugsie has left #openstack-meeting-alt17:56
*** elarson has left #openstack-meeting-alt17:56
*** jbratton has left #openstack-meeting-alt17:58
*** SlickNik has joined #openstack-meeting-alt17:58
*** mwang2__ has quit IRC17:58
*** jodah has joined #openstack-meeting-alt18:00
SlickNik#startmeeting trove18:00
openstackMeeting started Wed Mar 11 18:00:27 2015 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
*** marcusvrn has quit IRC18:00
*** radez_g0n3 is now known as radez18:00
SlickNikHello there18:00
*** kebray has joined #openstack-meeting-alt18:00
peterstaco/18:01
jodaho/18:01
SlickNikGiving folks a few minutes to trickle in to the Trove meeting.18:01
SlickNikAgenda at:18:01
georgelorcho/18:01
SlickNik#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting#Trove_Meeting.2C_March_11.2C_201518:01
mattvdo/18:01
schango/18:01
dougshelley66o/18:01
*** atomic77 has joined #openstack-meeting-alt18:01
*** nshah has joined #openstack-meeting-alt18:02
*** Longgeek has joined #openstack-meeting-alt18:02
vgnbkro/18:03
SlickNikOkay, let's get started18:03
SlickNik#topic Trove pulse update18:03
*** openstack changes topic to "Trove pulse update (Meeting topic: trove)"18:03
SlickNik#link https://etherpad.openstack.org/p/trove-pulse-update18:03
*** reed has joined #openstack-meeting-alt18:03
*** reed has quit IRC18:03
*** reed has joined #openstack-meeting-alt18:03
SlickNikNice job on keeping the reviews moving!18:03
SlickNikThanks to folks who have been active with reviews.18:04
*** salv-orlando has joined #openstack-meeting-alt18:04
*** stevemar has quit IRC18:04
*** n0ano has left #openstack-meeting-alt18:04
edmondko/18:04
nshaho/18:04
esmute0/18:04
*** stevemar has joined #openstack-meeting-alt18:05
pmalik\0/18:05
*** emagana has joined #openstack-meeting-alt18:05
SlickNikFor folks wondering — I pulled the numbers this morning instead of last night — which is why we have numbers for the last 8 days (instead of 7)18:05
*** HeOS has quit IRC18:06
atomic77o/18:06
SlickNikOur average wait times (for incoming patches) have been consistently going down — which is really nice to see.18:06
*** woodster_ has joined #openstack-meeting-alt18:07
*** _amrith_ is now known as amrith18:07
amrith./18:07
edmondkYeah on Feb 18th average wait times were 14 days18:07
edmondknow they are 5 days18:07
SlickNikAny questions regarding this — if not, let's move on.18:08
*** Longgeek has quit IRC18:09
SlickNik#topic Feature Freeze Next Week (March 19)18:09
*** openstack changes topic to "Feature Freeze Next Week (March 19) (Meeting topic: trove)"18:09
*** spzala has joined #openstack-meeting-alt18:09
SlickNikSo next week is FF, which means that we won't be accepting patches for any feature work for kilo after that.18:09
SlickNik#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule18:10
*** carl_baldwin has quit IRC18:10
SlickNikWe have 2-3 weeks of stabilization time after that, where we will focus on bugfixes for the Kilo release.18:11
*** Wilfried has joined #openstack-meeting-alt18:11
SlickNikSo specifically for the kilo-3 blueprints, we have quite a few outstanding reviews.18:11
SlickNikI've created an etherpad page to aggregate the open BP's and their associated reviews here: https://etherpad.openstack.org/p/TroveKilo3Blueprints18:12
vkmco/18:12
SlickNik#link https://etherpad.openstack.org/p/TroveKilo3Blueprints18:12
*** kbyrne has quit IRC18:13
*** jtomasek has quit IRC18:13
SlickNikLet's prioritize getting these reviews looked at and merged before feature freeze next week.18:14
johnmado the patches for the new features need to be merged by March 19th?18:14
johnmajust trying to understand the process18:14
*** kbyrne has joined #openstack-meeting-alt18:14
*** salv-orlando has quit IRC18:14
*** i-m-in has joined #openstack-meeting-alt18:15
SlickNikjohnma: yes — if they are to be part of the Kilo release.18:15
*** thomnico has quit IRC18:15
johnmaok, sounds good. Thanks SlickNik18:15
SlickNikIf not, we will have to move them to Liberty.18:15
*** sputnik13 has joined #openstack-meeting-alt18:15
*** marcusvrn has joined #openstack-meeting-alt18:16
*** gyee has joined #openstack-meeting-alt18:17
SlickNikWhile compiling the list, I noticed that some of the reviews needed some TLC wrt merge conflicts.18:17
SlickNikSo I was going to do that today to ensure that they were in a good reviewable state.18:17
SlickNikThere are a couple that are still waiting on code to be pushed up — towards the bottom of that list.18:18
*** marcusvrn has quit IRC18:19
johnmayes I need to do that for the couchdb work. Will push one out today.18:19
SlickNikI'm still assuming that that's in the pipeline — any update on ETAs for those?18:19
SlickNikcool, thanks johnma!18:19
*** absubram has joined #openstack-meeting-alt18:20
SlickNikvgnbkr: Any update on the replication v2 patchset?18:20
*** pkoniszewski has joined #openstack-meeting-alt18:20
vgnbkrSlickNik, yeah, it's done except for one small piece of functionality.  I'm working on tests now.18:21
johnmaI have to push the patchset for the DB2 guest agent as well. I am just cleaning up some stuff but should have that in today as well.18:21
SlickNikvgnbkr / johnma: sounds good. Thanks!18:21
*** fzdarsky has quit IRC18:22
SlickNikAny other questions / clarifications regarding Feature Freeze or any of this?18:22
johnmaI have a question about the DIB elements for DB2 and Vertica but I can wait until Open Discussion time18:22
SlickNikjohnma: okay18:23
johnmaits not related to the feature freeze item18:23
SlickNikLet's move on then, to allow more time for Open Discussion18:23
SlickNik#topic Coming down the pike for Liberty18:23
*** openstack changes topic to "Coming down the pike for Liberty (Meeting topic: trove)"18:23
SlickNikamrith: around?18:24
*** dave-mccowan has joined #openstack-meeting-alt18:24
SlickNik(he mentioned earlier that he might be on a plane)18:25
dougshelley66he was travelling today - i don't think he has a wifi signal ATM18:26
SlickNikBasically these changes are for oslo-config-generator which will allow us to generate sample configs based on the values in code.18:26
SlickNikThis is one of the oslo changes that we can take in Liberty.18:27
SlickNikThere were a couple of questions folks had around BPs / specs for Liberty.18:27
*** amrith is now known as _amrith_18:27
SlickNikFeel free to submit a spec for liberty — just ensure that in your submission the spec.rst is in the liberty folder.18:28
SlickNik(in trove-specs)18:28
SlickNikMore info on the oslo config-generator changes: http://docs.openstack.org/developer/oslo.config/generator.html18:29
SlickNik#link http://docs.openstack.org/developer/oslo.config/generator.html18:29
*** kobis has quit IRC18:29
*** bknudson has quit IRC18:30
SlickNikLooking at the config-generator docs, I have a couple of questions related to namespacing — I'll follow up with _amrith_ on this once he's back.18:32
SlickNikAny other questions?18:32
*** carl_baldwin has joined #openstack-meeting-alt18:32
*** jcoufal has quit IRC18:32
SlickNik#action SlickNik follow up with _amrith_ on config parameter namespacing and different confs in trove (eg. taskmanager vs conductor)18:33
SlickNikOkay, let's move on then.18:33
SlickNik#topic Open Discussion18:33
*** openstack changes topic to "Open Discussion (Meeting topic: trove)"18:33
SlickNikjohnma: I know you had a question here18:34
*** jaypipes is now known as jaypipes-afk18:34
*** marcusvrn has joined #openstack-meeting-alt18:34
peterstacI have one18:35
johnmaIf I may about the DIB elements I mentioned earlier - I know this is up for review but I thought it might be good to have a consistent way of providing DIB elements for datastores that require the packages to be downloaded to a local file system or provide a private repository18:35
johnmaoh sorry Peterstac, I was just going on and on typing18:36
johnmayou may go ahead18:36
peterstacjohnma: go ahead, you were first18:36
johnmasorry, I didnt mean to interrupt. But I will just  type this out and rest my case. My only point about the DIB elements for such datastores is that we have a consistent env variable name for defining for example, the download location, etc18:37
*** andriikolesnikov has joined #openstack-meeting-alt18:38
johnmaand folks can review and leave their comments in there but just wanted to bring this up18:38
johnmaso that we dont have different datastores defining variables that have the same function18:38
johnmathats it from my side.18:39
SlickNikjohnma: That sounds like a good idea — let me take a look at the vertica review — we can hash out a consistent design with some standard ENV vars to set which the elements can use?18:39
SlickNikThen DB2 can use a similar pattern18:39
johnmathat would be great SlickNik, appreciate it. From the DB2 side, I would like to follow the method Amrith had mentioned in his doc for building guest images - to define an extra-data.d to download the packages18:40
johnmaright now its all in the install.d18:40
johnmaits a good thing we have a process18:41
peterstacjohnma: looks like that's how the Vertica patchset is doing it18:41
*** Leo_ has joined #openstack-meeting-alt18:41
*** Leonr has quit IRC18:41
*** Leonr has joined #openstack-meeting-alt18:42
peterstacalthough the variable names are Vertica-specific18:42
SlickNikpeterstac: Yes, I think the concern is that the changes to https://review.openstack.org/#/c/156149/3/scripts/functions_qemu,cm are too Vertica specific18:42
peterstacSlickNik: Yes, in https://review.openstack.org/#/c/156149/3/scripts/files/elements/ubuntu-vertica/extra-data.d/93-copy-vertica-deb,cm too18:43
SlickNikYes — I agree with that, let's take the comments to the review and continue from there.18:44
johnmaI havent spend much time doing reviews on the Vertica patchset I must admit but I thought since the process of downloading the packages for DB2 and Vertica are similar, there should be consistency between both, thats all18:44
peterstacsounds good18:44
johnmasounds good to me. Thank you SlickNik and peterstac. Appreciate it18:44
*** mattgriffin has quit IRC18:44
*** salv-orlando has joined #openstack-meeting-alt18:44
*** banix has quit IRC18:45
SlickNikOkay, peterstac — you had an item for Open Discussion as well?18:45
*** pkoniszewski has quit IRC18:45
peterstacyep18:45
*** Leo_ has quit IRC18:45
peterstacI was just going to point out that until the trove-integration patchsets for DB2 and Vertica land18:45
peterstacwe won't be able to test the datastores18:45
peterstacbut I guess that was driven home by the above discussion :)18:46
johnmathats true. I will push another patch today with the extra-data changes and will wait for other reviews on the env variables and push another one18:47
SlickNikpeterstac: Yes, that's the case. They will have to land as experimental at first — is that what you meant to clarify?18:47
*** zehicle_ has quit IRC18:48
peterstacsure, that too, but mostly that we have up to three patches to review on each datastore, and each one depends on the one before it being completed18:48
peterstacand the trove-integration ones should be done first, IMO18:49
peterstacthat's it18:50
SlickNikpeterstac: Ah, I recall sushil had a cheat-sheet on instructions in case you wanted to take the vertica patches for a spin — https://gist.githubusercontent.com/sushilkm/9206a9d61ee9a9046f89/raw/68cd427afe3b3727679f02bf5d2d745c70adb513/gistfile1.txt18:50
SlickNikagree that the trove-integration ones should merge first, since that's what's needed for the image.18:50
*** safchain has quit IRC18:51
SlickNikI'll follow up with the reviews on the trove-integration patches today so that we can get some closure on that as soon as possible.18:52
johnmaand the instructions for getting the DB2 packages are included in the element itself18:52
peterstacgreat!18:52
SlickNikjohnma: ++18:52
*** spzala has quit IRC18:53
SlickNikOkay — anything else for Open Discusssion?18:54
*** echoingumesh has joined #openstack-meeting-alt18:54
*** banix has joined #openstack-meeting-alt18:54
SlickNik.18:54
SlickNik#endmeeting18:54
*** openstack changes topic to ": ML2 Sync and error handling (Task Flow) - revisited (Meeting topic: networking_ml2)"18:54
openstackMeeting ended Wed Mar 11 18:54:50 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2015/trove.2015-03-11-18.00.html18:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2015/trove.2015-03-11-18.00.txt18:54
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2015/trove.2015-03-11-18.00.log.html18:54
SlickNikThanks all!18:54
*** Wilfried has quit IRC18:55
johnmathank you18:56
*** mtanino has quit IRC18:57
*** mtanino has joined #openstack-meeting-alt18:57
*** atomic77 has left #openstack-meeting-alt18:57
*** marcusvrn has quit IRC18:58
*** kebray has quit IRC18:58
*** e0ne has joined #openstack-meeting-alt18:58
*** jamiem has joined #openstack-meeting-alt19:00
*** marun has quit IRC19:00
*** marcusvrn has joined #openstack-meeting-alt19:01
*** paul_glass has quit IRC19:02
*** gokrokve_ has quit IRC19:04
*** wojdev has quit IRC19:05
*** bobmel_ has joined #openstack-meeting-alt19:06
*** rmoe has quit IRC19:06
*** sdake__ has joined #openstack-meeting-alt19:08
*** bobmel has quit IRC19:08
*** jamiem has left #openstack-meeting-alt19:09
*** rushiagr is now known as rushiagr_away19:10
*** mattgriffin has joined #openstack-meeting-alt19:10
*** rmoe has joined #openstack-meeting-alt19:11
*** sdake_ has quit IRC19:12
*** Aish has joined #openstack-meeting-alt19:12
*** bknudson has joined #openstack-meeting-alt19:13
*** annashen has quit IRC19:15
*** spzala has joined #openstack-meeting-alt19:16
*** tosky has quit IRC19:19
*** rushil has quit IRC19:20
*** teran has quit IRC19:20
*** sushilkm has joined #openstack-meeting-alt19:21
*** sushilkm has left #openstack-meeting-alt19:21
*** sreshetn1 has joined #openstack-meeting-alt19:22
*** i-m-in has quit IRC19:26
*** ddmitriev has quit IRC19:27
*** achanda has quit IRC19:27
*** resker has quit IRC19:27
*** ddmitriev has joined #openstack-meeting-alt19:27
*** emagana has quit IRC19:29
*** marcusvrn has quit IRC19:29
*** annashen has joined #openstack-meeting-alt19:30
*** bharath has joined #openstack-meeting-alt19:31
*** radez is now known as radez_g0n319:32
*** esker has joined #openstack-meeting-alt19:33
*** esker has quit IRC19:34
*** esker has joined #openstack-meeting-alt19:36
*** kebray has joined #openstack-meeting-alt19:36
*** slagun has left #openstack-meeting-alt19:36
*** achanda has joined #openstack-meeting-alt19:38
*** rushil has joined #openstack-meeting-alt19:38
*** banix has quit IRC19:40
*** tdruiva_ has joined #openstack-meeting-alt19:43
*** TrevorV has joined #openstack-meeting-alt19:45
*** jamiem has joined #openstack-meeting-alt19:45
*** HeOS has joined #openstack-meeting-alt19:45
*** johnthetubaguy is now known as zz_johnthetubagu19:45
*** sballe__ has joined #openstack-meeting-alt19:45
*** tdruiva has quit IRC19:45
*** baoli has quit IRC19:46
*** tdruiva has joined #openstack-meeting-alt19:46
*** cbouch has quit IRC19:47
*** irenab has joined #openstack-meeting-alt19:48
*** mwang2 has joined #openstack-meeting-alt19:48
*** tdruiva_ has quit IRC19:49
*** nelsnelson has quit IRC19:50
*** esker has quit IRC19:53
*** Longgeek has joined #openstack-meeting-alt19:54
*** irenab has quit IRC19:55
*** gokrokve has joined #openstack-meeting-alt19:55
*** johnsom has joined #openstack-meeting-alt19:56
*** andriikolesnikov has quit IRC19:57
*** kevinbenton has joined #openstack-meeting-alt19:57
*** xgerman has joined #openstack-meeting-alt19:58
*** ajo has quit IRC20:00
xgerman#startmeeting octavia20:00
openstackMeeting started Wed Mar 11 20:00:06 2015 UTC and is due to finish in 60 minutes.  The chair is xgerman. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: octavia)"20:00
openstackThe meeting name has been set to 'octavia'20:00
dougwigo/20:00
xgerman#chair blogan20:00
openstackCurrent chairs: blogan xgerman20:00
Aish0/20:00
bharatho/20:00
mwang2o/20:00
johnsomo/20:00
*** Longgeek has quit IRC20:00
ajmillero/20:00
xgermanAgenda: https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda#Meeting_2015-03-1120:00
xgermanlet's see if blogan is back from taco after daylight saving change20:01
*** jorgem has joined #openstack-meeting-alt20:01
jorgemo/20:01
rm_worko/20:01
fnavalo.20:01
fnavalo/20:01
ptoohillo/20:01
TrevorVo/20:01
rm_workblogan is on PTO :P20:02
*** tdruiva_ has joined #openstack-meeting-alt20:02
xgermantowed?20:02
rm_workbut who knows, he might show up20:02
dougwigrm_work: oh, you mean he's working from home?20:02
ptoohilllol20:02
TrevorVYes dougwig that's the troof20:02
rm_workyes, his last two days of PTO he did :)20:02
xgerman#topic Announcements20:02
*** openstack changes topic to "Announcements (Meeting topic: octavia)"20:02
dougwigif he's here, i can tell him that my car got towed this morning (bad starter)20:03
jorgemthat doesn't count20:03
ptoohilllol20:03
*** kobis has joined #openstack-meeting-alt20:03
xgermanlol20:03
rm_workdougwig: you didn't just fix it in your driveway? :P20:03
xgermanjorgem +120:03
rm_workstarter isn't too bed20:03
rm_work*too bad20:04
rm_workbet it's like $100 at Oreilly's20:04
xgermanok, so we had mark give us a demo of akanda rug yesterday and it looks pretty impressive20:04
xgermanbut he also promised us to give us a version to play around with... which hasn't happened...20:04
*** tdruiva has quit IRC20:04
rm_workyeah, if we decided to move to that, it would mean scrapping a huge portion of our current design for Octavia, right? basically all of the current VM interfaces?20:05
xgermanyeah, I think it will be a big refactor20:05
xgermanbut from an operator perspective I liked the tooling for listing running vms, etc,20:06
xgermananyhow, I will reserver judegment to once I had a chance to play with it :-)20:06
*** diemt has quit IRC20:06
*** mspreitz has joined #openstack-meeting-alt20:07
xgermandougwig? any lb vendor perspective?20:07
johnsomIt sounded like there was still some work to be done before everything we would need is in akanda, but it didn't sound like a lot20:07
dougwigi think we'd be nuts to rewrite all of that infrastructure ourselves.20:07
xgerman+120:08
dougwigi mean, we can have simple drivers for nova, plumbing, and amphoras for demos, but when it comes to making them production ready, an akanda driver for those three functions could get us pretty far down the road.20:08
*** thangp has quit IRC20:08
dougwigthat was my initial impression, anyway.20:08
*** tdruiva_ is now known as tdruiva20:08
ajmiller+120:09
dougwigthat is predicated on us getting bits and it all working, of course.20:09
sballe__o/ sorry for being late20:09
*** esker has joined #openstack-meeting-alt20:09
ptoohillSo, we would probably need to invest time in Akanda to get it ready for our needs, unless we expect them to do that for us?20:09
jorgemdougwig: correct, I want to get something working end to end asap20:10
xgermanyeah, I think we will need to engage with them20:10
xgermanjorgem +1 - I see akanda AFTER we have end to end20:10
sballe__dougwig: +120:10
jorgemptoohill: I hope it's the latter20:10
jorgemxgerman: +220:10
ptoohilli dont think it will be jorgem20:10
*** echoingumesh has quit IRC20:10
sballe__jorgem: +120:10
ptoohilland if it is, were at the mercy of their timeline20:10
ptoohillwhich im not sure our needs are their top priority20:11
xgerman+120:11
sballe__ptoohill: It is open source and I agree regarding the priority. We would need to see and assess its status before we deicde to go with it20:12
ptoohillagreed, im just wondering if and how much of my time well be spending getting this new framework ready for things we already have planned out20:12
sballe__based on the demo we only got to see what they wanted us to see. We need to dig deeper20:13
ptoohillor already in flux20:13
*** _amrith_ is now known as amrith20:13
xgermansballe__ +1 we need to get the code and assess20:13
*** jwarendt has joined #openstack-meeting-alt20:13
ptoohillagreed sballe__, just my initial thoughts20:13
*** radez_g0n3 is now known as radez20:13
sballe__ptoohill: I agree20:13
*** mattgrif_ has joined #openstack-meeting-alt20:14
xgermanptoohill we will be spending time getting our drivers production ready, too, so without the kanda code it's hard to assess20:14
xgermananyhow, I think we are on the same page... so moving on:20:14
xgerman#topic Brief progress reports20:14
*** openstack changes topic to "Brief progress reports (Meeting topic: octavia)"20:14
sballe__xgerman: +120:14
*** mattgriffin has quit IRC20:14
TrevorVSSH Driver should be ready to review, I just still haven't tested it locally by running the code by hand20:15
TrevorVThat's what i'll be doing today/tomorrow20:15
johnsomContinued progress on the controller worker.  I plan to post another patch set today that will add load balancer functionality20:15
xgermanAgent API server works for most functions need to add SSL and some other minor stuff20:16
ptoohillIm an Octavia slacker, all foxus has been in neutron-lbaas20:16
mwang2continue working on  add config drive to nova compute driver and change code for health manager based on review comment20:16
johnsomI was hoping blogan would be here.  I'm interested to know his timeline/plans for the network driver.20:16
sballe__I have started work on Amphora REST driver20:16
sballe__thanks for ptoohill TrevorV ajmiller for their help :-)]20:17
TrevorVjohnsom assume he's a lazy bumb until next Monday.20:17
*** wbrothers has quit IRC20:17
TrevorV( sballe__ still not sure what I did, but you're welcome :D )20:17
sballe__:-)20:17
ptoohillYour presence TrevorV20:17
xgerman#topic Discuss AmphoraDriver:20:18
*** openstack changes topic to "Discuss AmphoraDriver: (Meeting topic: octavia)"20:18
xgermanwell, with ssh being ready I guess TrevorV won the race :-)20:18
*** mrmartin has quit IRC20:18
xgerman(my intention for this topic was to highlight we are close with the REST driver and could skip ssh but since we have it...)20:19
sballe__I'll continue to work on the amphora driver we can always decide later20:20
TrevorVWell xgerman I don't think having both would be a problem anyway, since we should potentially still prioritize the REST driver for reviews and such20:21
rm_workI'm still liking the prospect of SSH driver for production deployments, after my last conversation with dougwig about it20:21
xgermanour aim was always to go with REST but we felt ssh got us to the end-to-enfd quicker20:21
rm_workso I wouldn't want to skip it regardless :P20:21
*** pkoniszewski has joined #openstack-meeting-alt20:21
sballe__rm_work: +1 I agree20:22
xgermanrm_work any reason why ssh is better than REST?20:22
rm_worka few20:22
xgermanshoot:20:22
rm_workdougwig: do you want to go through them, or should I? :P20:22
rm_work1) nothing additional running on the Amphora, so virtually zero overhead20:22
johnsomCurious on this myself.20:22
rm_work2) SSH is as provably secure as anything can be20:22
rm_work3) No logic deployed to the Amphorae, so updates would be entirely service-side (better scaling for updates)20:23
ptoohilllit the fire under rm_work :)20:23
dougwigi like it because the amphora image becomes *download cloud image from canonical*.  it's there, adding keys is common in openstack, bash is a fine DSL for configuring haproxy.20:23
dougwigno bugs in software we don't write.20:24
xgermanwell, we still need some agent to push stats/health20:24
sballe__xgerman: +120:24
rm_workwas stats a pull or a push?20:24
*** sreshetn1 has quit IRC20:24
ptoohillOther stats besides the ones maintianed by haproxy right20:24
ptoohilltheres a few types of stats i thought20:25
ptoohilllike instance stats, but think we can collect those else where?20:25
xgermaneven the ones maintained by haproxy need to get to the controller/ceilometer/...20:25
ptoohillyou can query for those20:26
dougwigscp can copy over an agent or deb.  it becomes self-updating.20:26
ptoohillits ones that are not set up to be tracked20:26
*** kobis has quit IRC20:26
rm_workdougwig speaks truth20:26
xgermanyeah, he does :-)20:26
ptoohilllike cpu stuffs20:26
xgermanwell, I know people who sell aproduct which ssh's into each host and gathers those stats20:27
TrevorVAll those informations can be derived from the SSH connection20:27
*** stockFD3S has joined #openstack-meeting-alt20:27
TrevorVthrough the SSH connection***20:27
rm_workif the stats are "haproxy stats", then yeah those can be pulled through SSH20:27
xgermanyep, but that doesn't scale very well20:27
sballe__xgerman: +120:27
ptoohillthgeres others i thought we wanted to collect20:28
rm_workI thought we'd decided to go with pull-stats too...20:28
ptoohillnot just haproxy20:28
rm_workand actually, it should scale fine -- you split up the amphorae between different workers20:28
rm_workscales pretty easily IMO?20:28
TrevorVptoohill like what?  Basic networking stats and hardware information?  That can still be retrieved through SSH connection, right?20:28
xgermanyep, I am not questioning that20:28
ptoohillsure static stats can20:28
rm_workthough there might still need to be SOME code that lives on the Amphora, like were we still planning to have a push-based heartbeat?20:29
ptoohillbut i thought we wanted to collect data of cpu usage/mem etc20:29
ptoohillbut im sure that could be done without an agent of sorts, maybe20:29
xgermanyep, we want but you cna do that though SSH, too20:29
ptoohillidk20:29
*** shwetaap has quit IRC20:29
ptoohillah, very true20:29
ptoohilljust have it poll20:29
TrevorV+1 xgerman that's what I was talking about20:29
rm_workwell, the point being if it's push based, it needs to have a daemon running ON the amphora20:29
johnsomThe code that is in the repo was for a push model.20:29
rm_workso that can do whatever20:29
*** ChuckC_ has quit IRC20:29
xgermanyeah, even UDP because TCP was too heavy :-)20:30
rm_workheh20:30
rm_workyeah, barclaac's code20:30
*** mwagner_lap has quit IRC20:30
rm_workwhich is fine to remain as-is20:30
rm_workwe're talking about the controller->amphora direction20:30
rm_worklike config updates, etc20:30
bedis(morning)20:30
rm_workand, I thought, stats pulling20:30
johnsomThe current design puts a lot of weight on the agent monitoring the haproxy instances20:30
*** _nadya_ has joined #openstack-meeting-alt20:30
dougwigi'd wager that the "health check" in 0.5 could be just keeping an ssh connection hot and noticing when it drops.20:31
xgermanmy main worry is that pushing out code with ssh, etc. makes us into some poor man's ansible/chef/etc.20:31
bedisnote: it is possible to exports stats through a TCP socket (ciphered)20:31
bedisor CSV through the stats page20:32
xgermanbedi, neat!20:32
bedishttp://demo.haproxy.org/20:32
bedisand20:32
bedishttp://demo.haproxy.org/;csv20:33
bedisjust an example20:33
bedisyou can even export stats for a single frontend or backend:20:33
bedishttp://demo.haproxy.org/;csv?scope=www20:33
xgermanI can see a short term (0.5) need for ssh but long term I would think REST is better (since we can use golden images; make sure nobody ssh i and turns it into a botnet)20:33
bedis:)20:33
rm_workwell, I assume SSH would only be bound to the management interface20:34
rm_workbut I don't know if this conversation is precisely on-topic/necessary right now20:34
rm_workwhere in the meeting were we? :P20:34
*** smazziotta has quit IRC20:35
TrevorVOne thing to note, even when considering the REST api on the amphora, its still a pull model to gather info/details about the amphora, am I wrong?20:35
ptoohillthe api client will make the request to gather that data, so yes, its still a 'pull' model20:35
xgermanTrevorV the plan is to write an gent which has a REST API and some way to push stars20:36
xgermanstars=stats20:36
xgermanbut they can be two pices20:36
ptoohillunless its planned to do something else :P20:36
*** ndipanov has quit IRC20:36
xgermanptoohill the stats argument was to defeat the assertion we can use stock ubuntu/don't need to install anything20:37
rm_workwell, depends on what is push and what is pull20:37
*** marun has joined #openstack-meeting-alt20:37
rm_workand yeah, we still need to deploy SOME agent on the amphora20:37
rm_workbut it can be much more minimal;20:37
bedisactually it depends who does it :)20:37
rm_workand it could be *deployed* via SSH, making updates much easier20:37
xgermanand that ties into how operators run their world - if it's golden images; or configured at ruuntime20:38
rm_worktrue20:38
*** SlickNik has left #openstack-meeting-alt20:38
xgerman(and I know my security people running an ssh system will only fly with waivers)20:39
rm_workwell20:39
xgermanand heavy app armor20:39
rm_workask your security people how much more comfortable they are with a custom REST-based solution you wrote20:39
*** kenhui has joined #openstack-meeting-alt20:39
TrevorVxgerman I don't remember us every automatically pushing stats from the amphora.  I knew of the heartbeat, but that's the only thing I remember as a communication out from the amphora without a request being made20:40
rm_workseems there is much more likleihood of that being insecure than SSH being insecure20:40
TrevorVever automatically***20:40
rm_workhence: <rm_work>2) SSH is as provably secure as anything can be20:40
ptoohillNot sure what were argining anymore, but sounds like we should keep/use both ssh and rest to satisfy everyones needs20:41
xgermanyep20:41
ptoohilland do a push/pull model and make it configurable ;)20:41
TrevorVThat's a given, but now I'm confused about the priorities of the amphora.20:41
xgermanTrevorV: http://octavia.io/review/master/design/version0.5/component-design.html scroll down to "Some notes on Controller <-> Amphorae communication"20:42
xgermanyeah, priorities are confusing20:42
*** ajo has joined #openstack-meeting-alt20:42
*** salv-orlando has quit IRC20:43
xgermanI think that horse is glue20:43
xgerman#topic Open Discussion20:43
*** openstack changes topic to "Open Discussion (Meeting topic: octavia)"20:43
* dougwig used to eat paste as a kid.20:44
bedisdougwig.rb !!!!20:44
rm_work"And the following would happen over TCP: * haproxy / tls certificate configuration changes"20:45
rm_workthat is not aphora->controller20:45
rm_workthat's the other way around20:45
rm_workso no, it wouldn't have anything to do with a REST API controller-side20:45
*** amrith is now known as _amrith_20:45
rm_workthe only things I see listed in that section that are relevant are things that would be handled by barclaac's heartbeat code, or by the controller->amphora SSH connection driver20:45
xgermanyep, I just pointed that out since TrevorV didn't recall pushing stats amphora -> Controller20:47
*** tcammann_ has joined #openstack-meeting-alt20:47
xgermanbut both ssh and REST are covered by the spec20:47
xgermanso as ptoohill said different operators have different needs20:47
xgerman...20:48
rm_workOH yeah I see, the bullets got messed up20:48
* ptoohill Likes goldfishes20:48
*** sushilkm has joined #openstack-meeting-alt20:48
rm_workthis stuff is really not well worded20:49
rm_workT_T20:49
*** sushilkm has left #openstack-meeting-alt20:49
xgermanagreed20:50
rm_workTrevorV pointed out what I had forgotten -- I think a lot of this stuff is supposed to be sent over *as part of* the heartbeats from barclaac's daemon20:50
rm_workover UDP20:50
*** irenab has joined #openstack-meeting-alt20:50
*** jprovazn has quit IRC20:51
rm_workat least, specifically, “edge” alert notifications (change in status) from the amphora to the controller20:51
rm_workwhich i assume means "member node UP/DOWN notifications", since haproxy is tracking those20:51
*** sdake__ has quit IRC20:51
rm_workand that's how I assume we'd be notified20:51
TrevorVWhich makes his code much more intimately connected to the API driver or SSH driver or whatever to get those "agents" set up appropriately.20:51
xgermanyeah, that's what we use the health manager for20:51
xgerman(recieving those upodates)20:52
xgermanTrevorV +120:52
TrevorVrm_work brought up that the base image will have the agent that sends those UDP connections defined.20:52
rm_workthe health-manager listens for UDP messages?20:53
TrevorVUDP informations***20:53
rm_workI guess that makes sense, but i hadn't seen that code yet20:53
*** sdake_ has joined #openstack-meeting-alt20:53
xgermanno, driver does; health manager has logic to persist it into DB20:53
rm_workah20:53
rm_workwhich driver does?20:53
rm_workthe Amphora Driver?20:53
xgermanamphora_driver20:53
rm_workif so, that'd be shared code between both the REST driver and the SSH driver20:53
xgermanyep20:53
xgermanthey will be pretty similar the REST server doesn't do muh but some with open to move files and subprocess to start/stop things20:55
*** tcammann_ has quit IRC20:55
rm_workyeah I'd hope the listening on UDP part would be above the SSH/REST layer20:55
*** achanda has quit IRC20:55
xgermanrm_work, will be an extra thread...20:55
rm_workah right20:55
rm_workso it's not really part of the Amphora Driver, it seems20:56
rm_workat least, as we have it20:56
xgermanit is20:56
*** kebray has quit IRC20:56
rm_workbecause the amphora_driver is a specification for an interface to talk TO the amphora20:56
rm_workand is not a thread20:56
*** mtanino has quit IRC20:56
rm_workit's just code that is run when there are updates to be sent20:56
xgerman+ it also fires up a thread to lisetn for the stats20:56
rm_workthere needs to be a different class like amphora_listener to actually have an open socket for that, i'd imagine20:57
rm_workerr20:57
*** thomasem has quit IRC20:57
rm_workexcept it fires up a thread when?20:57
rm_worknot per-update20:57
rm_workit doesn't really make sense for a class that is instantiated/used as a result of queue actions20:57
xgermanno, I think we will amend the spec so you cna say start_thread()20:57
rm_workto spin up a long-term listening thread20:57
xgermansince that thread needs to run as part of the health_manager BUT NOT the deploy worker20:58
*** hogepodge has joined #openstack-meeting-alt20:58
rm_workI mean, technically that would work, but it seems like a bad design decision to just shove it in with the rest of the outbound amphora communication stuff20:58
rm_worksince that thread and the rest of the amp driver will never share any code or call each other20:58
*** kenhui has quit IRC20:58
xgermanwell, I would hate to need TWO drivers to talk with Amphoras20:58
rm_workit'll only be calling health-manager persistence methods20:58
rm_workerr, no20:59
rm_workyou'd need one class that is responsible for opening a socket and acting as a long-term listener20:59
xgermanok, got it two classes; one driver20:59
rm_workand one class that is part of a lib that is run for on-queue-action updates20:59
rm_workwell, it also kind of makes sense to split it out, since it's not relevant whether the driver is SSH or REST20:59
johnsomYeah, the point of having it in the driver was for non-amphora deployments.20:59
rm_workunless it lives at a layer ABOVE that part21:00
rm_workso if it lives in the Amphora Driver code, we need to have an extra layer21:00
rm_workbecause we don't want to be duplicating that code between the SSH and REST implementations21:00
*** _nadya_ has quit IRC21:00
rm_workthat should be easy enough to figure out though, since hopefully that makes sense?21:00
*** mspreitz has quit IRC21:00
xgermanyep, we also can share the code which makes haproxy.cfg files21:01
rm_workyeah probably21:01
xgermananyhow, time's out21:01
xgerman#endmeeting21:01
*** openstack changes topic to ": ML2 Sync and error handling (Task Flow) - revisited (Meeting topic: networking_ml2)"21:01
openstackMeeting ended Wed Mar 11 21:01:50 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/octavia/2015/octavia.2015-03-11-20.00.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/octavia/2015/octavia.2015-03-11-20.00.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/octavia/2015/octavia.2015-03-11-20.00.log.html21:01
*** dprince has quit IRC21:02
*** esker has quit IRC21:02
*** thomasem has joined #openstack-meeting-alt21:03
*** TrevorV has left #openstack-meeting-alt21:04
*** thomasem_ has joined #openstack-meeting-alt21:05
*** irenab has quit IRC21:07
*** Leon has joined #openstack-meeting-alt21:07
*** Leon is now known as Guest2198421:07
*** johnsom has left #openstack-meeting-alt21:08
*** thomasem has quit IRC21:08
*** stockFD3S has quit IRC21:09
*** tellesnobrega_ has joined #openstack-meeting-alt21:09
*** Leonr has quit IRC21:10
*** akuznetsov has quit IRC21:10
*** mwang2 has quit IRC21:10
*** tellesnobrega_ has quit IRC21:11
*** Guest21984 has quit IRC21:12
*** jckasper has quit IRC21:12
*** ozamiatin has quit IRC21:13
*** a_teem has quit IRC21:13
*** jckasper has joined #openstack-meeting-alt21:14
*** ozamiatin has joined #openstack-meeting-alt21:14
*** mattgrif_ has quit IRC21:14
*** teran has joined #openstack-meeting-alt21:15
*** mattgriffin has joined #openstack-meeting-alt21:15
*** mattfarina is now known as mfer21:15
*** mfer has quit IRC21:16
*** a_teem has joined #openstack-meeting-alt21:16
*** matrohon has quit IRC21:16
*** dimtruck is now known as zz_dimtruck21:19
*** sreshetn1 has joined #openstack-meeting-alt21:21
*** esker has joined #openstack-meeting-alt21:21
*** jwarendt has quit IRC21:24
*** matt__ is now known as mattoliverau21:25
*** miqui has quit IRC21:25
*** sreshetn1 has quit IRC21:25
*** achanda has joined #openstack-meeting-alt21:28
*** salv-orlando has joined #openstack-meeting-alt21:28
*** mattgriffin has quit IRC21:29
*** movielovers has joined #openstack-meeting-alt21:31
*** annashen has quit IRC21:32
*** ijw has quit IRC21:34
*** i-m-in has joined #openstack-meeting-alt21:36
*** rushil_ has joined #openstack-meeting-alt21:38
*** annashen has joined #openstack-meeting-alt21:39
*** rushil has quit IRC21:39
*** radez is now known as radez_g0n321:40
*** baoli has joined #openstack-meeting-alt21:42
*** nshah has left #openstack-meeting-alt21:42
*** HeOS has quit IRC21:42
*** i-m-in has quit IRC21:43
*** tonytan4ever has quit IRC21:43
*** baoli has quit IRC21:44
*** baoli has joined #openstack-meeting-alt21:45
*** zehicle_ has joined #openstack-meeting-alt21:45
*** zz_dimtruck is now known as dimtruck21:46
*** sdake_ has quit IRC21:46
*** sdake_ has joined #openstack-meeting-alt21:48
*** sdake_ has joined #openstack-meeting-alt21:48
*** jckasper has quit IRC21:48
*** EricGonczer_ has quit IRC21:48
*** amotoki has quit IRC21:50
*** banix has joined #openstack-meeting-alt21:51
*** dimtruck is now known as zz_dimtruck21:51
*** zz_dimtruck is now known as dimtruck21:52
*** esker has quit IRC21:55
*** HeOS has joined #openstack-meeting-alt21:56
*** mattgriffin has joined #openstack-meeting-alt21:58
*** tdruiva is now known as banana_21:59
*** banana_ is now known as tdruiva22:00
*** sdake_ has quit IRC22:00
*** marun has quit IRC22:01
*** SridharRamaswamy has quit IRC22:05
*** baoli has quit IRC22:08
*** jungleboyj has quit IRC22:09
*** Leonr has joined #openstack-meeting-alt22:11
*** dims has quit IRC22:11
*** Leon has joined #openstack-meeting-alt22:12
*** Leon is now known as Guest3809022:12
*** baoli has joined #openstack-meeting-alt22:13
*** wojdev has joined #openstack-meeting-alt22:14
*** tdruiva has quit IRC22:14
*** ijw has joined #openstack-meeting-alt22:15
*** ijw has quit IRC22:15
*** Leonr has quit IRC22:16
*** carl_baldwin has quit IRC22:16
*** kenhui has joined #openstack-meeting-alt22:17
*** ijw has joined #openstack-meeting-alt22:17
*** sreshetn1 has joined #openstack-meeting-alt22:22
*** movielovers has left #openstack-meeting-alt22:22
*** hogepodge has quit IRC22:24
*** sreshetn1 has quit IRC22:26
*** pmalik has quit IRC22:27
*** annashen has quit IRC22:30
*** annashen has joined #openstack-meeting-alt22:30
*** jaypipes-afk is now known as jaypipes22:31
*** jgrimm is now known as zz_jgrimm22:36
*** BrianB_ has quit IRC22:37
*** tellesnobrega_ has joined #openstack-meeting-alt22:40
*** pkoniszewski has quit IRC22:41
*** tellesnobrega_ has quit IRC22:41
*** banix has quit IRC22:41
*** nikhil_k is now known as _pope22:41
*** _pope is now known as nikhil_k22:43
*** Longgeek has joined #openstack-meeting-alt22:45
*** dims_ has joined #openstack-meeting-alt22:46
*** pnavarro has quit IRC22:48
*** jckasper has joined #openstack-meeting-alt22:48
*** amotoki has joined #openstack-meeting-alt22:50
*** jecarey has quit IRC22:51
*** annashen has quit IRC22:52
*** banix has joined #openstack-meeting-alt22:52
*** banix has quit IRC22:53
*** jckasper has quit IRC22:53
*** Longgeek has quit IRC22:55
*** SridharRamaswamy has joined #openstack-meeting-alt22:55
*** sdake_ has joined #openstack-meeting-alt22:55
*** amotoki has quit IRC22:56
*** qwebirc42969 has joined #openstack-meeting-alt22:57
*** sdake__ has joined #openstack-meeting-alt22:57
*** bharath_ has joined #openstack-meeting-alt22:58
*** daniel3_ has quit IRC22:58
*** baoli has quit IRC22:59
*** EricGonczer_ has joined #openstack-meeting-alt23:00
*** sdake_ has quit IRC23:00
*** bharath has quit IRC23:01
*** SridharRamaswam1 has joined #openstack-meeting-alt23:01
*** bharath_ has quit IRC23:02
*** mattgriffin has quit IRC23:02
*** bharath has joined #openstack-meeting-alt23:02
*** SridharRamaswamy has quit IRC23:03
*** e0ne is now known as e0ne_23:04
*** qwebirc42969 has quit IRC23:05
*** sdake__ has quit IRC23:06
*** kenhui has quit IRC23:08
*** claired has joined #openstack-meeting-alt23:09
*** sdake_ has joined #openstack-meeting-alt23:09
*** jorgem has quit IRC23:09
*** kenhui has joined #openstack-meeting-alt23:09
*** kenhui has quit IRC23:12
*** annashen has joined #openstack-meeting-alt23:12
*** dave-mccowan has quit IRC23:14
*** sdake_ has quit IRC23:14
*** dneary has quit IRC23:19
*** woodster_ has quit IRC23:20
*** EricGonczer_ has quit IRC23:20
*** jckasper has joined #openstack-meeting-alt23:20
*** bharath_ has joined #openstack-meeting-alt23:20
*** bharath has quit IRC23:23
*** annashen has quit IRC23:24
*** jckasper has quit IRC23:25
*** shivharis has joined #openstack-meeting-alt23:25
*** sdake_ has joined #openstack-meeting-alt23:26
*** jecarey has joined #openstack-meeting-alt23:28
*** bknudson has quit IRC23:31
*** jckasper has joined #openstack-meeting-alt23:38
*** EricGonczer_ has joined #openstack-meeting-alt23:39
*** pmalik has joined #openstack-meeting-alt23:40
*** kozhukalov has quit IRC23:40
*** jckasper has quit IRC23:44
*** absubram has quit IRC23:44
*** pmalik has quit IRC23:47
*** e0ne_ has quit IRC23:50
*** ajmiller has quit IRC23:51
*** mtanino has joined #openstack-meeting-alt23:52
*** bknudson has joined #openstack-meeting-alt23:52
*** funzo has quit IRC23:52
*** zehicle_ has quit IRC23:53
*** SridharRamaswam1 has quit IRC23:56
*** jckasper has joined #openstack-meeting-alt23:57

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