Wednesday, 2016-05-04

*** minwang2 has quit IRC00:01
*** shaohe_feng has quit IRC00:07
*** shaohe_feng has joined #openstack-meeting-400:07
*** Jeffrey4l has joined #openstack-meeting-400:10
*** pvaneck has quit IRC00:11
*** markvoelker has joined #openstack-meeting-400:14
*** shaohe_feng has quit IRC00:17
*** shaohe_feng has joined #openstack-meeting-400:17
*** bpokorny has quit IRC00:18
*** SimonChung has quit IRC00:18
*** ddieterly has joined #openstack-meeting-400:22
*** banix has joined #openstack-meeting-400:25
*** shaohe_feng has quit IRC00:27
*** shaohe_feng has joined #openstack-meeting-400:28
*** zenoway has joined #openstack-meeting-400:29
*** mlavalle has quit IRC00:30
*** zenoway has quit IRC00:33
*** baoli has joined #openstack-meeting-400:34
*** baoli has quit IRC00:36
*** unicell has quit IRC00:36
*** baoli has joined #openstack-meeting-400:36
*** shaohe_feng has quit IRC00:37
*** shaohe_feng has joined #openstack-meeting-400:38
*** yamahata has joined #openstack-meeting-400:39
*** mageshgv has joined #openstack-meeting-400:40
*** klamath has quit IRC00:46
*** shaohe_feng has quit IRC00:48
*** shaohe_feng has joined #openstack-meeting-400:48
*** mageshgv has quit IRC00:54
*** shaohe_feng has quit IRC00:58
*** shaohe_feng has joined #openstack-meeting-400:59
*** baoli has quit IRC00:59
*** baoli has joined #openstack-meeting-401:04
*** uck has quit IRC01:07
*** shaohe_feng has quit IRC01:08
*** shaohe_feng has joined #openstack-meeting-401:08
*** thorst has joined #openstack-meeting-401:09
*** armax_ has joined #openstack-meeting-401:11
*** armax has quit IRC01:12
*** armax_ is now known as armax01:12
*** sdake has quit IRC01:13
*** armax has quit IRC01:14
*** shaohe_feng has quit IRC01:18
*** shaohe_feng has joined #openstack-meeting-401:19
*** yamamoto has quit IRC01:21
*** fitoduarte has quit IRC01:23
*** zhurong has joined #openstack-meeting-401:23
*** armax has joined #openstack-meeting-401:26
*** baoli has quit IRC01:27
*** shaohe_feng has quit IRC01:29
*** shaohe_feng has joined #openstack-meeting-401:29
*** wxy has joined #openstack-meeting-401:33
*** yamamoto has joined #openstack-meeting-401:36
*** ddieterly is now known as ddieterly[away]01:38
*** iyamahat has quit IRC01:38
*** yamahata has quit IRC01:38
*** shaohe_feng has quit IRC01:39
*** shaohe_feng has joined #openstack-meeting-401:39
*** yamamoto has quit IRC01:41
*** yamamoto has joined #openstack-meeting-401:41
*** yamamoto has quit IRC01:42
*** vishwanathj has quit IRC01:48
*** shaohe_feng has quit IRC01:49
*** shaohe_feng has joined #openstack-meeting-401:50
*** antonyfm has joined #openstack-meeting-401:51
*** thorst has quit IRC01:57
*** thorst has joined #openstack-meeting-401:58
*** mkaushik has quit IRC01:58
*** mkaushik has joined #openstack-meeting-401:59
*** mkaushik has quit IRC01:59
*** shaohe_feng has quit IRC01:59
*** shaohe_feng has joined #openstack-meeting-402:00
*** mkaushik has joined #openstack-meeting-402:00
*** mkaushik has quit IRC02:00
*** mkaushik has joined #openstack-meeting-402:01
*** mkaushik has quit IRC02:04
*** mkaushik has joined #openstack-meeting-402:04
*** mkaushik has quit IRC02:04
*** mkaushik has joined #openstack-meeting-402:05
*** thorst has quit IRC02:06
*** shaohe_feng has quit IRC02:10
*** shaohe_feng has joined #openstack-meeting-402:10
*** ddieterly[away] has quit IRC02:11
*** yamahata has joined #openstack-meeting-402:12
*** cdelatte has quit IRC02:15
*** shaohe_feng has quit IRC02:20
*** shz has quit IRC02:22
*** shaohe_feng has joined #openstack-meeting-402:23
*** shihanzhang has joined #openstack-meeting-402:24
*** zenoway has joined #openstack-meeting-402:25
*** zenoway has quit IRC02:29
*** shaohe_feng has quit IRC02:30
*** shaohe_feng has joined #openstack-meeting-402:31
*** shaohe_feng has quit IRC02:40
*** shaohe_feng has joined #openstack-meeting-402:41
*** yamamoto has joined #openstack-meeting-402:43
*** shaohe_feng has quit IRC02:51
*** shaohe_feng has joined #openstack-meeting-402:51
*** markvoelker has quit IRC02:52
*** yamamoto has quit IRC02:54
*** shaohe_feng has quit IRC03:01
*** shaohe_feng has joined #openstack-meeting-403:02
*** banix has quit IRC03:02
*** thorst has joined #openstack-meeting-403:04
*** cwolferh has quit IRC03:05
*** xingchao has joined #openstack-meeting-403:08
*** dave-mccowan has quit IRC03:10
*** thorst has quit IRC03:11
*** shaohe_feng has quit IRC03:11
*** shaohe_feng has joined #openstack-meeting-403:12
*** Kevin_Zheng has joined #openstack-meeting-403:17
*** wanghua has joined #openstack-meeting-403:18
*** shaohe_feng has quit IRC03:23
*** shaohe_feng has joined #openstack-meeting-403:24
*** cwolferh has joined #openstack-meeting-403:28
*** xingchao has quit IRC03:29
*** baoli has joined #openstack-meeting-403:31
*** shaohe_feng has quit IRC03:35
*** shaohe_feng has joined #openstack-meeting-403:35
*** baoli has quit IRC03:37
*** fitoduarte has joined #openstack-meeting-403:38
*** shaohe_feng has quit IRC03:42
*** shaohe_feng has joined #openstack-meeting-403:43
*** antonyfm has quit IRC03:46
*** shaohe_feng has quit IRC03:52
*** markvoelker has joined #openstack-meeting-403:52
*** shaohe_feng has joined #openstack-meeting-403:55
*** yamamoto has joined #openstack-meeting-403:57
*** markvoelker has quit IRC03:57
*** shaohe_feng has quit IRC04:02
*** shaohe_feng has joined #openstack-meeting-404:03
*** yamamoto has quit IRC04:09
*** thorst has joined #openstack-meeting-404:09
*** itisha has quit IRC04:09
*** shaohe_feng has quit IRC04:13
*** shaohe_feng has joined #openstack-meeting-404:13
*** thorst has quit IRC04:16
*** shaohe_feng has quit IRC04:23
*** shaohe_feng has joined #openstack-meeting-404:23
*** yamamoto has joined #openstack-meeting-404:24
*** mageshgv has joined #openstack-meeting-404:26
*** yamamoto has quit IRC04:26
*** yamamoto has joined #openstack-meeting-404:30
*** shaohe_feng has quit IRC04:33
*** shaohe_feng has joined #openstack-meeting-404:34
*** vtech has quit IRC04:35
*** vtech has joined #openstack-meeting-404:36
*** yamamoto has quit IRC04:36
*** shaohe_feng has quit IRC04:43
*** shaohe_feng has joined #openstack-meeting-404:44
*** amit213 has quit IRC04:44
*** gangil has joined #openstack-meeting-404:50
*** shaohe_feng has quit IRC04:54
*** shaohe_feng has joined #openstack-meeting-404:54
*** mageshgv has quit IRC04:56
*** vtech has quit IRC05:03
*** shaohe_feng has quit IRC05:04
*** vtech has joined #openstack-meeting-405:05
*** shaohe_feng has joined #openstack-meeting-405:05
*** mohankumar has joined #openstack-meeting-405:06
*** mohankumar has quit IRC05:10
*** shaohe_feng has quit IRC05:14
*** thorst has joined #openstack-meeting-405:14
*** shaohe_feng has joined #openstack-meeting-405:14
*** mageshgv has joined #openstack-meeting-405:17
*** bnemec has quit IRC05:17
*** numans has joined #openstack-meeting-405:20
*** thorst has quit IRC05:21
*** gangil has quit IRC05:22
*** mohankumar has joined #openstack-meeting-405:22
*** mageshgv has quit IRC05:23
*** zenoway has joined #openstack-meeting-405:24
*** shaohe_feng has quit IRC05:24
*** shaohe_feng has joined #openstack-meeting-405:25
*** paul-carlton2 has joined #openstack-meeting-405:26
*** zenoway has quit IRC05:28
*** shaohe_feng has quit IRC05:35
*** shaohe_feng has joined #openstack-meeting-405:35
*** numans has quit IRC05:36
*** numans has joined #openstack-meeting-405:37
*** yamamoto has joined #openstack-meeting-405:37
*** yamamoto has quit IRC05:45
*** shaohe_feng has quit IRC05:45
*** mkaushik has quit IRC05:45
*** shaohe_feng has joined #openstack-meeting-405:45
*** mkaushik has joined #openstack-meeting-405:46
*** mkaushik has quit IRC05:46
*** mkaushik has joined #openstack-meeting-405:47
*** mkaushik has quit IRC05:54
*** mkaushik has joined #openstack-meeting-405:54
*** mkaushik has quit IRC05:55
*** cwolferh has quit IRC05:55
*** shaohe_feng has quit IRC05:55
*** mkaushik has joined #openstack-meeting-405:55
*** shaohe_feng has joined #openstack-meeting-405:56
*** vishnoianil has quit IRC05:58
*** vishnoianil has joined #openstack-meeting-405:58
*** david-lyle has quit IRC06:05
*** l8huang has joined #openstack-meeting-406:05
*** shaohe_feng has quit IRC06:05
*** shaohe_feng has joined #openstack-meeting-406:06
*** salv-orlando has joined #openstack-meeting-406:07
*** cartik has joined #openstack-meeting-406:09
*** javeriak has joined #openstack-meeting-406:15
*** shaohe_feng has quit IRC06:16
*** shaohe_feng has joined #openstack-meeting-406:18
*** thorst has joined #openstack-meeting-406:18
*** javeriak has quit IRC06:21
*** javeriak has joined #openstack-meeting-406:21
*** thorst has quit IRC06:26
*** shaohe_feng has quit IRC06:26
*** vishnoianil has quit IRC06:26
*** shaohe_feng has joined #openstack-meeting-406:27
*** cartik has quit IRC06:31
*** zenoway has joined #openstack-meeting-406:32
*** vtech has quit IRC06:35
*** salv-orlando has quit IRC06:36
*** zenoway has quit IRC06:36
*** shaohe_feng has quit IRC06:36
*** shaohe_feng has joined #openstack-meeting-406:37
*** zenoway has joined #openstack-meeting-406:38
*** anilvenkata has joined #openstack-meeting-406:44
*** shaohe_feng has quit IRC06:46
*** shaohe_feng has joined #openstack-meeting-406:47
*** markvoelker has joined #openstack-meeting-406:54
*** shaohe_feng has quit IRC06:57
*** shaohe_feng has joined #openstack-meeting-406:57
*** vtech has joined #openstack-meeting-406:59
*** vtech_ has joined #openstack-meeting-406:59
*** vtech has quit IRC06:59
*** markvoelker has quit IRC07:00
*** khushbu has joined #openstack-meeting-407:02
*** hdaniel has joined #openstack-meeting-407:06
*** shaohe_feng has quit IRC07:07
*** shaohe_feng has joined #openstack-meeting-407:08
*** nmadhok has joined #openstack-meeting-407:09
*** nmadhok1 has quit IRC07:09
*** vishnoianil has joined #openstack-meeting-407:13
*** matrohon has joined #openstack-meeting-407:14
*** shaohe_feng has quit IRC07:17
*** paul-carlton2 has quit IRC07:18
*** shaohe_feng has joined #openstack-meeting-407:18
*** zeih has joined #openstack-meeting-407:21
*** thorst has joined #openstack-meeting-407:24
*** shaohe_feng has quit IRC07:27
*** shaohe_feng has joined #openstack-meeting-407:28
*** thorst has quit IRC07:31
*** paul-carlton2 has joined #openstack-meeting-407:32
*** salv-orlando has joined #openstack-meeting-407:36
*** shaohe_feng has quit IRC07:38
*** shaohe_feng has joined #openstack-meeting-407:38
*** paul-carlton2 has quit IRC07:39
*** jschwarz has joined #openstack-meeting-407:41
*** salv-orlando has quit IRC07:41
*** alexchadin has joined #openstack-meeting-407:43
*** mkaushik has quit IRC07:44
*** shaohe_feng has quit IRC07:48
*** shaohe_feng has joined #openstack-meeting-407:51
*** paul-carlton2 has joined #openstack-meeting-407:52
*** shaohe_feng has quit IRC07:58
*** shaohe_feng has joined #openstack-meeting-407:59
*** javeriak has quit IRC08:06
*** shaohe_feng has quit IRC08:08
*** shaohe_feng has joined #openstack-meeting-408:09
*** yamahata has quit IRC08:11
*** mbound has joined #openstack-meeting-408:11
*** matrohon has quit IRC08:11
*** shaohe_feng has quit IRC08:19
*** shaohe_feng has joined #openstack-meeting-408:19
*** javeriak has joined #openstack-meeting-408:21
*** akijak has joined #openstack-meeting-408:22
*** paul-carlton2 has quit IRC08:23
*** paul-carlton2 has joined #openstack-meeting-408:27
*** thorst has joined #openstack-meeting-408:29
*** shaohe_feng has quit IRC08:29
*** shaohe_feng has joined #openstack-meeting-408:29
*** akijak has quit IRC08:29
*** thorst has quit IRC08:36
*** salv-orlando has joined #openstack-meeting-408:38
*** akijak has joined #openstack-meeting-408:38
*** shaohe_feng has quit IRC08:39
*** shaohe_feng has joined #openstack-meeting-408:39
*** salv-orlando has quit IRC08:42
*** zeih has quit IRC08:43
*** paul-carlton2 has quit IRC08:43
*** khushbu has quit IRC08:44
*** yamahata has joined #openstack-meeting-408:46
*** paul-carlton2 has joined #openstack-meeting-408:48
*** shaohe_feng has quit IRC08:49
*** shaohe_feng has joined #openstack-meeting-408:50
*** markvoelker has joined #openstack-meeting-408:50
*** paul-carlton2 has quit IRC08:53
*** markvoelker has quit IRC08:55
*** zeih has joined #openstack-meeting-408:55
*** shaohe_feng has quit IRC09:00
*** shaohe_feng has joined #openstack-meeting-409:00
*** mohankumar has quit IRC09:00
*** iyamahat has joined #openstack-meeting-409:03
*** javeriak has quit IRC09:03
*** paul-carlton2 has joined #openstack-meeting-409:07
*** shaohe_feng has quit IRC09:10
*** zhurong has quit IRC09:10
*** zeih has quit IRC09:12
*** mohankumar has joined #openstack-meeting-409:12
*** shaohe_feng has joined #openstack-meeting-409:13
*** zhurong has joined #openstack-meeting-409:13
*** zhurong has quit IRC09:13
*** cartik has joined #openstack-meeting-409:15
*** khushbu has joined #openstack-meeting-409:19
*** nmadhok has quit IRC09:19
*** shaohe_feng has quit IRC09:20
*** nmadhok has joined #openstack-meeting-409:21
*** shaohe_feng has joined #openstack-meeting-409:21
*** prithiv has joined #openstack-meeting-409:23
*** nmadhok has joined #openstack-meeting-409:23
*** zeih has joined #openstack-meeting-409:25
*** paul-carlton2 has quit IRC09:26
*** yamamoto has joined #openstack-meeting-409:28
*** shaohe_feng has quit IRC09:30
*** shaohe_feng has joined #openstack-meeting-409:31
*** thorst has joined #openstack-meeting-409:33
*** sdague has joined #openstack-meeting-409:33
*** yamamoto has quit IRC09:34
*** mbound has quit IRC09:35
*** zeih has quit IRC09:35
*** sshnaidm has quit IRC09:37
*** salv-orlando has joined #openstack-meeting-409:38
*** paul-carlton2 has joined #openstack-meeting-409:39
*** shaohe_feng has quit IRC09:41
*** thorst has quit IRC09:41
*** shaohe_feng has joined #openstack-meeting-409:41
*** salv-orlando has quit IRC09:43
*** yamamoto has joined #openstack-meeting-409:44
*** javeriak has joined #openstack-meeting-409:45
*** prithiv has quit IRC09:45
*** khushbu has quit IRC09:46
*** dshakhray has joined #openstack-meeting-409:48
*** yamamoto has quit IRC09:50
*** shaohe_feng has quit IRC09:51
*** mbound has joined #openstack-meeting-409:51
*** shaohe_feng has joined #openstack-meeting-409:51
*** vdrok_ is now known as vdrok09:55
*** shaohe_feng has quit IRC10:01
*** shaohe_feng has joined #openstack-meeting-410:02
*** khushbu has joined #openstack-meeting-410:04
*** prithiv has joined #openstack-meeting-410:06
*** prithiv has quit IRC10:08
*** prithiv has joined #openstack-meeting-410:09
*** prithiv has quit IRC10:10
*** prithiv has joined #openstack-meeting-410:10
*** prithiv has quit IRC10:11
*** shaohe_feng has quit IRC10:11
*** prithiv has joined #openstack-meeting-410:12
*** shaohe_feng has joined #openstack-meeting-410:12
*** zeih has joined #openstack-meeting-410:20
*** yamamoto has joined #openstack-meeting-410:21
*** shaohe_feng has quit IRC10:22
*** shaohe_feng has joined #openstack-meeting-410:22
*** sshnaidm has joined #openstack-meeting-410:24
*** shaohe_feng has quit IRC10:32
*** shaohe_feng has joined #openstack-meeting-410:33
*** thorst has joined #openstack-meeting-410:39
*** salv-orlando has joined #openstack-meeting-410:40
*** shaohe_feng has quit IRC10:42
*** shaohe_feng has joined #openstack-meeting-410:43
*** salv-orlando has quit IRC10:45
*** thorst has quit IRC10:46
*** prithiv has quit IRC10:47
*** allen_gao has quit IRC10:47
*** dave-mccowan has joined #openstack-meeting-410:51
*** allen_gao has joined #openstack-meeting-410:52
*** shaohe_feng has quit IRC10:52
*** shaohe_feng has joined #openstack-meeting-410:53
*** baoli has joined #openstack-meeting-410:57
*** baoli has quit IRC10:57
*** baoli has joined #openstack-meeting-410:57
*** david-lyle has joined #openstack-meeting-410:58
*** prithiv has joined #openstack-meeting-410:58
*** baoli has quit IRC10:58
*** prithiv has quit IRC10:59
*** rtheis has joined #openstack-meeting-411:00
*** shaohe_feng has quit IRC11:03
*** shaohe_feng has joined #openstack-meeting-411:03
*** antonyfm has joined #openstack-meeting-411:04
*** prithiv has joined #openstack-meeting-411:04
*** prithiv has quit IRC11:05
*** shaohe_feng has quit IRC11:13
*** shaohe_feng has joined #openstack-meeting-411:13
*** belmoreira has joined #openstack-meeting-411:15
*** alexchadin has quit IRC11:15
*** alexchadin has joined #openstack-meeting-411:15
*** nmadhok has quit IRC11:16
*** nmadhok has joined #openstack-meeting-411:17
*** cartik has quit IRC11:18
*** khushbu has quit IRC11:18
*** yamamoto has quit IRC11:22
*** shaohe_feng has quit IRC11:23
*** shaohe_feng has joined #openstack-meeting-411:24
*** yamamoto has joined #openstack-meeting-411:25
*** nmadhok has quit IRC11:26
*** vtech_ has quit IRC11:27
*** vtech has joined #openstack-meeting-411:28
*** alexchadin has quit IRC11:29
*** banix has joined #openstack-meeting-411:33
*** javeriak has quit IRC11:33
*** javeriak has joined #openstack-meeting-411:33
*** shaohe_feng has quit IRC11:33
*** xingchao has joined #openstack-meeting-411:34
*** shaohe_feng has joined #openstack-meeting-411:34
*** xingchao has quit IRC11:39
*** salv-orlando has joined #openstack-meeting-411:40
*** mbound has quit IRC11:42
*** shaohe_feng has quit IRC11:44
*** banix has quit IRC11:45
*** shaohe_feng has joined #openstack-meeting-411:45
*** salv-orlando has quit IRC11:46
*** antonyfm has quit IRC11:47
*** thorst has joined #openstack-meeting-411:51
*** shaohe_feng has quit IRC11:54
*** iyamahat has quit IRC11:54
*** yamahata has quit IRC11:54
*** shaohe_feng has joined #openstack-meeting-411:55
*** cdelatte has joined #openstack-meeting-412:02
*** shaohe_feng has quit IRC12:04
*** markvoelker has joined #openstack-meeting-412:04
*** shaohe_feng has joined #openstack-meeting-412:07
*** jichen has joined #openstack-meeting-412:07
*** matrohon has joined #openstack-meeting-412:10
*** prithiv has joined #openstack-meeting-412:12
*** bobh has joined #openstack-meeting-412:12
*** javeriak has quit IRC12:12
*** davidlenwell has quit IRC12:13
*** shaohe_feng has quit IRC12:14
*** davidlenwell has joined #openstack-meeting-412:15
*** mbound has joined #openstack-meeting-412:16
*** shaohe_feng has joined #openstack-meeting-412:16
*** woodard has joined #openstack-meeting-412:23
*** dave-mcc_ has joined #openstack-meeting-412:24
*** shaohe_feng has quit IRC12:25
*** bobh has quit IRC12:25
*** shaohe_feng has joined #openstack-meeting-412:26
*** dave-mccowan has quit IRC12:27
*** prithiv has quit IRC12:28
*** yamamoto has quit IRC12:30
*** prithiv has joined #openstack-meeting-412:30
*** yamamoto has joined #openstack-meeting-412:31
*** shaohe_feng has quit IRC12:35
*** shaohe_feng has joined #openstack-meeting-412:36
*** baoli has joined #openstack-meeting-412:38
*** baoli_ has joined #openstack-meeting-412:40
*** salv-orlando has joined #openstack-meeting-412:41
*** baoli has quit IRC12:43
*** pav0 has joined #openstack-meeting-412:43
*** fitoduarte has quit IRC12:45
*** shaohe_feng has quit IRC12:45
*** antonyfm has joined #openstack-meeting-412:45
*** trozet has quit IRC12:46
*** shaohe_feng has joined #openstack-meeting-412:46
*** salv-orlando has quit IRC12:46
*** julim has joined #openstack-meeting-412:47
*** shaohe_feng has quit IRC12:55
*** oomichi_ has joined #openstack-meeting-412:56
*** andymaier has joined #openstack-meeting-412:56
*** shaohe_feng has joined #openstack-meeting-412:56
*** cdent has joined #openstack-meeting-412:58
*** sfinucan has joined #openstack-meeting-413:00
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed May  4 13:00:22 2016 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: nova api)"13:00
openstackThe meeting name has been set to 'nova_api'13:00
alex_xuwho is here today?13:00
oomichi_hi13:01
jicheno/13:01
johnthetubaguyo/13:01
cdento/13:02
alex_xui guess people still in jetlag13:02
*** javeriak has joined #openstack-meeting-413:02
alex_xu#topic API Priorities13:03
*** openstack changes topic to "API Priorities (Meeting topic: nova api)"13:03
sfinucano/13:03
*** trozet has joined #openstack-meeting-413:03
*** ddieterly has joined #openstack-meeting-413:04
alex_xulet say remove legacy v2 API first?13:04
oomichi_+1 :-)13:04
jichen+113:04
alex_xuoomichi_: and i already sent out some patches13:05
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/remove-legacy-v2-api-code13:05
oomichi_not only nova, but also devstack13:05
oomichi_https://review.openstack.org/#/q/status:open+project:openstack/topic:bp/remove-legacy-v2-api-code13:06
*** shaohe_feng has quit IRC13:06
alex_xuis there any order people concerned? I'm think of removing the api-paste.ini entry first, that stop user using the legacy v2 api first. Then we remove legacy v2 code piece by piece13:06
*** shaohe_feng has joined #openstack-meeting-413:06
alex_xuoomichi_: ah, cool, also the merged one, the legacy v2 gate job, thanks for that :)13:06
oomichi_alex_xu: yeah, we can remove api-paste.ini now13:07
sdaguealex_xu: I left a comment on your patch removing the paste bits13:07
johnthetubaguyhonestly, as long as we get it done quickly, the order isn't too important13:07
johnthetubaguyyeah, +1 sdague's comment on that patch13:07
sdagueI'd like to have a unit test to understand what the user sees if they forgot to update paste.ini13:07
sdagueI also updated the api dashboard to look for this blueprint - https://review.openstack.org/#/c/312475/13:08
alex_xusdague: yea, good point on that patch, I think I should add log in pipeline_facotry method instead of removing the pipeline_factory directly.13:08
sdaguealex_xu: yeh, maybe, as long as we understand what the behavior is, and it's something that the admin will understand and be able to fix13:08
sdaguethe ec2 remove from enabled_apis was a little rougher than we would have liked13:09
*** salv-orlando has joined #openstack-meeting-413:09
alex_xusdague: ok, got it, i will update the patch.13:09
*** krotscheck_dcm is now known as krotscheck13:10
alex_xuI think we should remove paste entry before breaking the legacy v2 api code13:10
alex_xuafter that we can free to remove legacy v2 api code, just ensure the tests passed.13:10
sdagueyep13:11
johnthetubaguyI think we have to, it sounds sensible13:11
alex_xuafter legacy v2 code removed, there can be some cleanup in the wsgi stack.13:11
sdaguegetting the paste entry removed, and the failure if it's still there sensible seems like the primary step. After that we can just delete a bunch of stuff.13:11
alex_xuone more question, what kind of test we expected on v2.1 compat mode?13:12
*** pmesserli has joined #openstack-meeting-413:13
oomichi_alex_xu: meaning additionalProperties:True mode?13:13
johnthetubaguyare we not OK with all the existing testing?13:13
sdagueI think the existing testing is probably fine13:13
*** salv-orlando has quit IRC13:13
*** nmadhok has joined #openstack-meeting-413:14
alex_xuthe api sample test still run with v2.1 compat mode, the nova/tests/functional/test_servers run under compat mode, and other functional test is not.13:14
alex_xuoomichi_: yup13:14
sdaguewe've got functional testing for the APIs in tree with the samples, the only differences between it and the v2.1 code should be in that layer13:14
sdagueI'm sure there are ways to enhance it further, but it's been fine up until this point13:14
johnthetubaguyare we also removing the extensions config for v2.1, maybe I am getting ahead of the list now?13:14
sdaguejohnthetubaguy: I think we decided that's a spec13:15
sdaguefor communication as much as anything else13:15
johnthetubaguysdague: gotcha13:15
johnthetubaguyI remember that conversation now... vaguely13:15
alex_xuok, that is another question, but i got clearly now13:16
sdaguehttps://etherpad.openstack.org/p/newton-nova-api L9613:16
*** shaohe_feng has quit IRC13:16
*** mageshgv has joined #openstack-meeting-413:16
johnthetubaguyin my head that change affects the samples testing, hence the quick check13:16
*** shaohe_feng has joined #openstack-meeting-413:16
*** mriedem has joined #openstack-meeting-413:16
* mriedem joins late13:16
alex_xuyes, probably need gmann's sample test merging work first13:17
*** schwarzm has joined #openstack-meeting-413:18
alex_xuwho is going to write that spec?13:18
*** coolsvap has quit IRC13:18
johnthetubaguyif I don't write it, I can help +2 it13:18
*** prithiv has quit IRC13:18
alex_xuif no-one, let me help it.13:19
sdagueI might get to it, but it will be a couple of weeks, because we really do need to stay focussed on api-ref and policy13:19
*** armax has quit IRC13:19
alex_xuok, looks like api-ref and policy is more priority than that13:19
*** armax has joined #openstack-meeting-413:20
alex_xuso let me try first.13:21
johnthetubaguysounds like the correct call13:21
*** automagically has joined #openstack-meeting-413:21
alex_xuso looks like cool at here. let's move on13:21
alex_xuapi policy discovery13:21
alex_xu#link https://review.openstack.org/#/c/290155/13:22
alex_xuwe said only need this one in newton?13:22
mriedemlooks like alaski and dhellmann need to sort that one out13:22
mriedemotherwise i was more or less ok with it13:23
sdagueyeh, we should just keep on top of it, I think I need to take one more pass on it13:23
johnthetubaguylikewise, I like the way its going, just nits13:23
mriedemi'm not sure if dhellmann is asking that we bake a bunch of new stuff into an oslo lib13:23
alex_xustill implement in nova first, not oslo?13:23
mriedembecause it would be easier for nova to do this thing first and split it out later13:23
*** qwebirc28577 has joined #openstack-meeting-413:24
alex_xuok, got it13:24
*** hvprash has joined #openstack-meeting-413:24
sdagueok, probably a todo to sort out where that one stands13:24
sdagueto make sure we get to approval soon13:24
mriedemit needs a rev anyway13:24
*** fitoduarte has joined #openstack-meeting-413:25
mriedembut it would be good to have an agreement between alaski and dhellmann13:25
sdaguehttps://review.openstack.org/#/c/289405/6/specs/newton/approved/discoverable-policy-api.rst is a bit more problematic. I think we decided on a very different approach during the session, but I'm not sure that claudio_ was there13:25
johnthetubaguyah, yes, the nova-manage command idea13:25
sdagueright13:25
* mriedem doesn't remember exactly13:25
sdagueI can provide that group feedback into the spec today13:26
mriedemhopefully the notes are in https://etherpad.openstack.org/p/newton-nova-api13:26
sdaguehttps://etherpad.openstack.org/p/newton-nova-api L28-L4113:26
*** automagically has left #openstack-meeting-413:26
*** shaohe_feng has quit IRC13:26
mriedemyeah13:26
sdagueL35 is the most relevant13:26
mriedemnew policy language13:26
*** bobh has joined #openstack-meeting-413:26
*** tonytan4ever has joined #openstack-meeting-413:26
alex_xuat line 3513:26
sdagueDecision: no, not in Newton. Build the infra and be able to see it in nova-manage.13:26
mriedembuild it into nova-manage13:26
mriedemyup13:26
sdagueDecision: don't munge this with capabilities, this is a permission check. +113:26
mriedemi would have gotten there eventually :) i need to write the recap for the api session today13:27
sdague:)13:27
*** hvprash_ has joined #openstack-meeting-413:27
sdague#action sdague to provide session feedback to https://review.openstack.org/#/c/289405 spec13:27
cdentsdague, awesome, because I'm struggling to parse the etherpad13:28
johnthetubaguyquick question...13:28
alex_xusdague: cool, thanks13:28
*** geseib has joined #openstack-meeting-413:28
*** hvprash has quit IRC13:28
johnthetubaguyactually is dumb question, ignore me, was thinking about whats needed to unblock live-reize13:28
johnthetubaguythis is a dependency, but its not the end of the road, thats all13:28
sdaguejohnthetubaguy: right, we said, previously, it was discoverable capabilities13:28
*** trozet_ has joined #openstack-meeting-413:29
*** hvprash has joined #openstack-meeting-413:29
sdaguewhich this is all ground work for13:29
johnthetubaguyyeah, +113:29
johnthetubaguyyou could expose that via permissions, but thats messy13:29
sdaguewe specifically said we wouldn't do that13:29
*** shaohe_feng has joined #openstack-meeting-413:29
*** trozet has quit IRC13:30
sdagueDecision: don't munge this with capabilities, this is a permission check. +113:30
sdagueL3613:30
*** trozet_ is now known as trozet13:30
johnthetubaguyright, I was meaning deployers might change permissions due to known capabilities, but yeah, its not an assumption we want in the API13:30
alex_xui still confuse on the policy discovery and capabilities discovery. I found we always talk about them together, but I thought they are diffrent things.13:30
sdaguealex_xu: they are13:30
johnthetubaguydoes it work vs can i do it13:30
sdaguebut capabilities are hard to do without the policy being fully known in advance (which it is not)13:31
alex_xuok, cool, looks like i'm same page with people13:31
johnthetubaguy+1, this is a needed stop on that journey13:31
sdaguebecause the two intersect in some cases, where the cloud can in theory do X, but the admin wants to prevent it13:31
johnthetubaguyI think claudio_ was hoping this spec would un block his live-resize, hence my query13:31
johnthetubaguyjust a heads up there13:32
*** hvprash_ has quit IRC13:32
sdagueso it makes no sense to expose can:live-resize to the user, they try, then get a 40313:32
alex_xuah, i got it now, sdague thanks13:32
johnthetubaguysdague: agreed13:32
sdagueor, it can make sense, but it's mostly very frustrating13:32
johnthetubaguyack, both for the deployer and the user13:33
sdagueso if we fix permissions being fully explicit, then we can address the rest of it on top of that13:33
cdentI assume throughout this people being conscious of the fact that any one human operating a user-agent may have multiple identities with the service13:33
cdentso they need to be able to know "if you change who you are you might be able to do this"13:33
alex_xuafter we have policy discovery, that is kind of thing instead of extension?13:34
johnthetubaguycdent: we were generally talking per token, I think13:34
sdaguecdent: right, per token, which is really per tenant in the policy conversation13:34
*** vhoward has joined #openstack-meeting-413:35
cdentcool, just checkin'13:35
sdaguealex_xu: more or less, but that's all next cycle13:35
alex_xusdague: ok, want to know how people think about that, as we said no extension. but there is something make people can do something13:36
alex_xus/something/same thing/13:36
alex_xuso we can move on?13:36
sdaguealex_xu: yeh13:36
*** shaohe_feng has quit IRC13:36
alex_xuLet's talk about api ref13:37
alex_xusdague: what is next plan13:37
sdaguewell, first off, a bunch of open patches out there - https://review.openstack.org/#/q/file:api-ref+project:openstack/nova+status:open13:37
sdaguejichen is doing a bunch of great work here, very thankful of that13:37
*** shaohe_feng has joined #openstack-meeting-413:37
sdaguewe need more folks diving in though13:37
alex_xujichen: thanks!13:37
jichenalex_xu: sdague :  :)13:38
sdaguenext Mon & Wed we'll do some doc sprints to try to push through as much as possible13:38
mriedem#link api-ref review sprint dev thread http://lists.openstack.org/pipermail/openstack-dev/2016-May/093844.html13:38
*** fwdit has joined #openstack-meeting-413:38
sdagueI've got some todos once we get the content close about microversions, and changing the way we represent urls13:38
sdagueHow about I follow up to mriedem's post with the details there so people can see the longer term steps here13:39
alex_xu+113:39
mriedemmaybe separate thread if it's not about reviews?13:39
mriedemi'd only follow up with review tips to my thread13:40
sdaguemriedem: sure, sounds good13:40
mriedemthis is what to expect, this is what to chec, etc13:40
mriedem*check13:40
sdagueI'll follow up on your thread with that, I'll wait until post sprint to evaluate and say next steps13:40
sdagueI'll probably write something today to assess how many outstanding items we've got in our checklist13:41
sdagueI updated the nova-api dashboard to put API ref at the top13:41
sdagueto try to score everything there first, as it should be easy13:41
sdagueany other questions there?13:43
alex_xunothing fro me13:43
alex_xus/fro/from/13:43
mriedemlink to the dashboard?13:43
mriedemor is that in a wiki somewhere?13:43
mriedemor etherpad13:43
sdaguemriedem: it's just in the repo, I can add it to the wiki13:45
mriedemmikal thanks you already13:45
sdagueor figure out a way to get these dashboards on stable urls13:45
*** yamamoto has quit IRC13:45
mriedemthere is 14 minutes left with a few more items, so let's move on13:46
alex_xuok13:46
alex_xuDeprecated API Proxy13:46
alex_xu#link https://review.openstack.org/#/c/312209/13:46
*** d0ugal has quit IRC13:46
mriedemi plan to review that soon13:46
*** d0ugal has joined #openstack-meeting-413:47
mriedemwe have notes in the session etherpad13:47
*** shaohe_feng has quit IRC13:47
sdagueyeh, I think that mostly matches the session13:47
*** shaohe_feng has joined #openstack-meeting-413:47
alex_xuok, only thing need is review13:47
*** sdake has joined #openstack-meeting-413:48
alex_xuif no more question, then move on?13:48
sdagueyep13:48
alex_xu#topic Open13:48
*** openstack changes topic to "Open (Meeting topic: nova api)"13:48
*** sdake has quit IRC13:48
alex_xucdent: you have items for open I think13:48
cdentyeah, I am after eyes and feedback on https://review.openstack.org/#/c/305800/ and https://review.openstack.org/#/c/300077/13:49
mriedemdid you guys already go over the legacy v2 api removal?13:49
cdentthe main concern is how best to document the change and ensure that it is kosher13:49
cdentmriedem: that was first13:49
mriedemd'oh!13:49
alex_xumriedem: yea, in the beginning of the meeting13:49
mriedemok13:49
*** woodard has quit IRC13:49
*** khushbu has joined #openstack-meeting-413:50
sdagueI have on my todo list a few more specs to write up: deprecating some unused, unusable REST APIs; remove of bookmark links; update for the flavor by server spec;13:50
cdentI know that the microversion change isn't a priority, but it is a) basically done b) pretty lightweight, so may as well push it along if people have some spare cycles13:50
cdentmy implementation is probably a bit incomplete, due to my inexperience with nova api changes, so feedback will make things happen13:50
sdaguecdent: yeh, I'll put the spec up for review. I think it's mostly going to be about a usage section in api-ref on microversions13:51
sdaguestarred that spec to look later13:51
cdentthanks13:51
alex_xuah, good point, probably a lot of microversion doc need update13:52
sdaguehttps://review.openstack.org/#/c/311529/ is the metadata casing proposed fix13:52
sdaguewhich was talked about late on friday, and mriedem did a good job pointing out the bits I messed up in draft 113:52
sdaguedraft 2 should be a lot more explicit13:52
sdaguehttp://docs-draft.openstack.org/29/311529/3/check/gate-nova-specs-docs/7f935cf//doc/build/html/specs/newton/approved/lowercase-metadata-keys.html13:53
* mriedem frames that on the wall13:53
alex_xucool, another fix for mess stuff13:54
*** mbound has quit IRC13:54
*** GregoryKatsaros has joined #openstack-meeting-413:55
cdentoh, before I forget, mriedem had said something about wanting it to be easier to explore what gabbi is, so I made this: https://gist.github.com/cdent/d70015ac6fffbbd3cd80a771e197bf3613:55
alex_xuif no more question, I probably go to end the meeting early?13:55
*** mbound has joined #openstack-meeting-413:55
cdentit's a shell script that automatically starts up and automatic demo13:55
cdents/and/an/13:55
cdentin case anyone is interested or curious13:56
*** sigmavirus24_awa is now known as sigmavirus2413:56
alex_xucdent: cool13:56
sdaguecool13:56
sdaguecdent: oh, last thing, I looked at the resource pools API spec this morning13:56
sdagueand I wonder if now is the time to split the CLI as well13:56
cdentit only covers the very basics, mostly of the syntax, not of how to integrate with testing harness and fixtures13:56
sdagueso we don't have to do that late in the game13:57
cdentsdague: yeah I read that13:57
cdentI think you're probably right13:57
sdagueand take a bunch of novaclient gorp with it13:57
*** jmckind has joined #openstack-meeting-413:57
*** shaohe_feng has quit IRC13:57
*** alexchadin has joined #openstack-meeting-413:57
*** dave-mcc_ has quit IRC13:57
cdentI haven't even begun to think that about the cli yet...13:57
cdents/that//13:57
*** shaohe_feng has joined #openstack-meeting-413:57
*** trozet has quit IRC13:57
mriedemsplit the cli as in for the new placement api?13:57
sdaguemriedem: yeh13:58
mriedemand put it where? new thing or osc?13:58
*** trozet has joined #openstack-meeting-413:58
sdagueprobably a new thing entirely13:58
* alex_xu will cut the meeting on time, but now people can just free to talk13:58
*** vincentfrancoise has joined #openstack-meeting-413:58
sdagueI guess it could be an osc plugin, which would be fine13:58
*** dronshaw has joined #openstack-meeting-413:59
sdaguebut not in nova cli for sure, because that will be one more bit of split challenge13:59
alex_xu#endmeeting13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:59
openstackMeeting ended Wed May  4 13:59:22 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-05-04-13.00.html13:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-05-04-13.00.txt13:59
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-05-04-13.00.log.html13:59
alex_xuthanks all13:59
acabot#startmeeting watcher13:59
openstackMeeting started Wed May  4 13:59:38 2016 UTC and is due to finish in 60 minutes.  The chair is acabot. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
*** openstack changes topic to " (Meeting topic: watcher)"13:59
openstackThe meeting name has been set to 'watcher'13:59
acabothi guys13:59
*** cdent has left #openstack-meeting-413:59
alexchadinhi13:59
vincentfrancoiseo/13:59
*** raj_singh has left #openstack-meeting-414:00
sballe_o/14:00
*** javeriak has quit IRC14:00
jed56(0-0)14:00
acabotour heavy agenda #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#05.2F04.2F201614:00
*** vmahe has joined #openstack-meeting-414:00
*** javeriak has joined #openstack-meeting-414:00
*** klamath has joined #openstack-meeting-414:00
*** klamath has quit IRC14:00
acabot#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:01
*** woodard has joined #openstack-meeting-414:01
*** prithiv has joined #openstack-meeting-414:01
*** mriedem has left #openstack-meeting-414:01
*** klamath has joined #openstack-meeting-414:01
*** jwcroppe has joined #openstack-meeting-414:01
acabot#info openstack Summit last week in Austin, all discussions in https://etherpad.openstack.org/p/watcher-newton-design-session14:01
tpeopleso/14:01
alexchadina lot things to discuss:)14:01
jwcroppeo/14:01
*** oomichi_ has quit IRC14:02
*** itisha has joined #openstack-meeting-414:02
acabot#info Watcher talk available on YouTube and Slideshare, of course, feel free to share them across social networks14:02
acabot#info we had discussions with Monasca & Congress as we could have some overlap with these 2 projects14:03
tkaczynskihi14:04
*** iyamahat has joined #openstack-meeting-414:04
acabot#info we will add a new timeslot for our weekly meeting separating odd and even weeks14:04
acabotthis will be easier for asian people to join this meeting every 2 weeks14:05
acabot#action acabot fin a new timeslot for Watcher meeting on odd weeks14:05
sballe_acabot: How do you suggest we move forward with discussing the possible overlap with Monasca and Congress? Also do we care? Not everybody will have Monasca.14:05
sballe_I am just interested in us understanding where all the project overlap and then decide on who is doing what14:06
tkaczynskisballe_ I guess we care about mission statement etc. we might not become big tent if there is overlap or something14:06
acabot#info we agreed to propose Watcher for the big tent in May to clarify our mission14:06
sballe_and if overlap is okay or if we can work together14:06
*** sdake has joined #openstack-meeting-414:06
hvprashsballe_ from walmart we are trying to evaluate all the solutions and coral a unified solution14:07
jed56sballe_:  in my opinion we have a different approach than Congress14:07
acabotsballe_ : my point is that for now, we will let TC members decide if there is an overlap in our missions, then if we enter the big tent, we will start working with them14:07
*** shaohe_feng has quit IRC14:07
sballe_perfect14:07
tpeoplesthe TC has stated in the past that competition isn't forbidden under the big tent, haven't they?14:08
jwcroppejed56: +1 ... but there is some alerting overlap (read: triggers for optimization), but I think it's minor14:08
*** mbound has quit IRC14:08
acabotjwcroppe : does is makes sense to you ?14:08
*** shaohe_feng has joined #openstack-meeting-414:08
jwcroppetpeoples: right14:08
sballe_yes they have :)14:08
dronshawtpeoples: correct14:08
jwcroppeacabot: +114:08
acabottpeoples : yes they did it for the monitoring but it was because ceilometer didn't work14:08
jed56jwcroppe: I agree14:09
vmaheI agree with Jed. You could trigger Watcher audits with Congress whenever some conditions are met. Watcher aims at providing deeper analysis strategies.14:09
vincentfrancoisevmahe: +114:09
sballe_vmahe: I agree with you. I would like to add watcher+congress integration sooner rather than later14:09
jed56we could create policies in congress14:09
*** prithiv has quit IRC14:09
sballe_so we don;t have to have this discussion again with Congress inthe fall14:10
*** salv-orlando has joined #openstack-meeting-414:10
acabotI think everybody should read this doc from the congress team https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit#heading=h.wy2kqfa4vhs2 and give its feedback in our next meeting14:10
*** nmadhok has quit IRC14:10
jwcroppeacabot: will do14:10
jed56acabot: +214:11
acabotI really think we have a different approach in Watcher but I'd like to have everybody agree14:11
alexchadinacabot: will do14:11
*** woodard has quit IRC14:11
*** nmadhok has joined #openstack-meeting-414:11
acabot#action jwcroppe jed56 alexchadin sballe_ read https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit#heading=h.wy2kqfa4vhs2 and give feedback to the team14:11
*** hvprash has quit IRC14:11
acabot#topic Review Action Items14:12
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:12
*** hvprash has joined #openstack-meeting-414:12
*** vishnoianil has quit IRC14:12
acabotvery quick review on specs14:12
alexchadinI forgot to tell14:13
alexchadinAdd Overload standard deviation strategy spec is already megred14:13
*** rbak has joined #openstack-meeting-414:13
jed56acabot: +214:13
acabothttps://review.openstack.org/#/c/283449/ needs reviews14:13
*** zeih has quit IRC14:14
acabotwe really need reviews from core on https://review.openstack.org/301774 as the code is ready to be merged14:14
acabot#action jwcroppe acabot sballe_ review asap https://review.openstack.org/30177414:14
sballe_I will do so today ;-)14:14
*** anilvenkata has quit IRC14:14
*** salv-orlando has quit IRC14:15
*** vincentfrancoise has quit IRC14:15
acabotI also have 2 new specs submitted by Greg from Intel, Greg are you there ?14:15
GregoryKatsarosYes, Hi14:15
*** nmadhok has quit IRC14:16
acabothi Greg, so are your specs ready to be reviewed ?14:16
*** vincentfrancoise has joined #openstack-meeting-414:16
GregoryKatsarosyes are ready14:16
acabotcause today your BPs are not in top priority14:16
GregoryKatsaroswe are working on the code at the moment. Have not submitted anything14:16
sballe_I'll review them today. GregoryKatsaros they are the graph model stuff right?14:16
acabotbut its great to have specs already14:16
GregoryKatsarosare the graph model and the action plans consolidation14:17
jed56I can read the spec next week14:17
acabotgreg, do you plan to deliver the code also on this 2 BPs ?14:17
GregoryKatsarosfor the graph we plan it. we are considering for the consolidation14:17
acabot#action sballe_ jed56 review specs https://review.openstack.org/#/c/298891/ https://review.openstack.org/#/c/298871/14:17
*** shaohe_feng has quit IRC14:17
acabottkaczynski : tomasz, I think it would be great to have your feedback on https://review.openstack.org/#/c/298891/14:18
*** shaohe_feng has joined #openstack-meeting-414:18
tkaczynskiacabot: ok, I can have a look14:18
jed56sballe_: do you think that thjis  can take a look ?14:19
*** mkaushik has joined #openstack-meeting-414:19
acabot#action tkaczynski review https://review.openstack.org/#/c/298891/14:19
GregoryKatsarosThijs, has already reviewed that internally14:19
acabotok thx14:19
GregoryKatsaroswe wrote that together14:19
sballe_yes just put him on and I'll let him know he has an action item when I send out the minutes notes14:19
*** jichen has quit IRC14:19
acabotmoving to Watcher code14:20
jed56sballe_: great14:20
jed56GregoryKatsaros: okay14:20
*** yamahata has joined #openstack-meeting-414:20
sballe_GregoryKatsaros: we also want him to +1 it14:20
acabotThere are a lot of code reviews open14:20
acabotand there is bunch of it related to get-goal-from-strategy https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/get-goal-from-strategy14:21
*** bnemec has joined #openstack-meeting-414:21
acabotthis code have been reviewed by 2 cores on bcom side but we need another core reviewer14:21
tkaczynskiacabot: is known when all of this will be merged? there are a lot of changes and I think many people might be affected14:22
acabottkaczynski : this is exactly why I want to have this code merged asap14:22
jed56IMO, we will merge this implementation next week.14:22
acabotit will impact others contributors14:22
sballe_+114:22
jed56We can't keep these patchets open more time :)14:22
tkaczynskiit would be also good to communicate that this is merged, maybe on the meeting next week?14:23
sballe_+114:23
acabotso I propose to merge it next monday with 2 cores from bcom, does anyone has a problem with that ?14:23
jed56before the next meeting :)14:23
*** jwcroppe has quit IRC14:23
acabot#info get-goal-from-strategy will be merged next monday14:24
sballe_acabot: Fine with me14:24
*** salv-orlando has joined #openstack-meeting-414:24
*** nmadhok has joined #openstack-meeting-414:24
*** mkaushik has quit IRC14:24
*** vishnoianil has joined #openstack-meeting-414:24
*** raj_singh has joined #openstack-meeting-414:24
acabotwe have 2 strategies currently in review https://review.openstack.org/#/c/297590/ & https://review.openstack.org/#/c/292188/14:24
*** mkaushik has joined #openstack-meeting-414:24
*** fwdit has quit IRC14:25
acaboton Watcher client side14:25
acabota BP has been submitted to support the official unified openstack CLI14:25
acabotand code is already available for review thx vincentfrancoise https://review.openstack.org/#/q/status:open+project:openstack/python-watcherclient+branch:master+topic:bp/openstackclient-plugin14:26
alexchadinI'll review some of them14:26
acabot#action alexchedin review https://review.openstack.org/#/q/status:open+project:openstack/python-watcherclient+branch:master+topic:bp/openstackclient-plugin14:26
acabot#action alexchadin review https://review.openstack.org/#/q/status:open+project:openstack/python-watcherclient+branch:master+topic:bp/openstackclient-plugin14:26
alexchadinReview for https://review.openstack.org/#/c/297590/ is very appreciate :)14:27
acaboton Watcher dashboard, there is a review open related to get-goal-from-strategy https://review.openstack.org/#/c/301516/14:28
*** shaohe_feng has quit IRC14:28
acabot#topic Blueprint/Bug Review and Discussion14:28
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:28
*** fitoduarte has quit IRC14:28
*** shaohe_feng has joined #openstack-meeting-414:28
jed56#action jed56 review https://review.openstack.org/#/c/297590/14:28
*** salv-orlando has quit IRC14:29
*** mbound has joined #openstack-meeting-414:29
acabot#info as we will propose Watcher for the big tent, we will assign an essential BP to each contributor to Watcher for our next milestone (Newton-1)14:29
sballe_+114:29
acabot#info next milestone is Newton-1 (May 30th) https://blueprints.launchpad.net/watcher14:29
*** spotz_zzz is now known as spotz14:29
acabotalexchadin proposed to take https://blueprints.launchpad.net/watcher/+spec/continuously-optimization as the one for servionica14:30
*** vtech has quit IRC14:30
acabottpeoples : you were interested in this BP, can alexchadin work on it ?14:31
hvprashacabot question on milestone. so does that include the code to be ready for review by May 30th. I am owning one of the blueprints https://blueprints.launchpad.net/watcher/+spec/persistent-audit-parameters14:31
*** ddieterly is now known as ddieterly[away]14:31
tpeoplesyes, that is fine acabot and alexchadin. i am focusing on the other BP, so feel free14:31
sballe_cabot: this will involve listening on the Monasca/ceilomter message bus. right?14:32
acabothvprash : at least specs merged14:32
hvprashok, got it14:32
*** julim has quit IRC14:32
hvprashsorry, if it was a stupid question since this is my first one ;)14:32
alexchadintpeoples: great. thanks!14:32
acabot#action alexchadin submit specs for https://blueprints.launchpad.net/watcher/+spec/continuously-optimization14:32
*** prithiv has joined #openstack-meeting-414:32
sballe_hvprash: stupid questions do not exist14:32
*** yamamoto has joined #openstack-meeting-414:32
*** yamamoto has quit IRC14:32
acabothvprash : not at all14:33
*** Swami has joined #openstack-meeting-414:33
*** yamamoto has joined #openstack-meeting-414:33
*** zeih has joined #openstack-meeting-414:33
acabot#info we have 7 BPs targeted as essential for Newton-1 (6 partners assigned and 1 free)14:33
*** mbound has quit IRC14:34
*** julim has joined #openstack-meeting-414:34
acabot#info there is a new BP on watcher CLI to improve tempest coverage on the new openstack CLI https://blueprints.launchpad.net/python-watcherclient/+spec/tempest-cli-test14:35
acabotanyone wants to take it ?14:35
acabothvprash : you have set your BP as discussion state, any question about it ?14:35
*** zeih has quit IRC14:36
*** zeih has joined #openstack-meeting-414:36
hvprashyes, i have some questions. So i did setup a devstack working env. Trying to recreate the issue and understand14:36
*** v1k0d3n has quit IRC14:36
*** v1k0d3n has joined #openstack-meeting-414:36
*** javeriak has quit IRC14:37
hvprashi was able to create a alarm template and trying to test the p[ersistency issue we are trying to fix14:37
*** mkaushik has quit IRC14:37
*** mkaushik has joined #openstack-meeting-414:37
hvprashwe can discuss this in watcher channel too due to time limitaiton14:37
hvprashneed some inputs though14:37
acabotthe problem we have here is that when you create an audit template and then build an audit with this template, if in the future you change the original template, your audit will have a consistency issue14:38
*** irenab_ has joined #openstack-meeting-414:38
*** shaohe_feng has quit IRC14:38
acabotbut yes lets discuss it on our IRC channel in more details14:38
vincentfrancoisehvprash: FYI, I can help you on #openstack-watcher if you want14:38
*** shaohe_feng has joined #openstack-meeting-414:38
hvprashvincentfrancoise awesome, will work you then14:39
acabot#topic Open Discussion14:39
*** openstack changes topic to "Open Discussion (Meeting topic: watcher)"14:39
*** ddieterly[away] is now known as ddieterly14:39
*** woodard has joined #openstack-meeting-414:39
hvprashacabot sballe_ i am talking to ramki from dell next week on the congress + policy based scheduling14:39
acabot#info there are some interesting talks from the summit that I'd like to share https://www.openstack.org/videos/video/enforcing-application-slas-with-congress-and-monasca & https://www.youtube.com/watch?v=zxcfM9tSh7Y14:39
*** irenab has quit IRC14:40
*** irenab_ is now known as irenab14:40
hvprashif interested can send you the invites14:40
sballe_hvprash: cool! how can I/we help14:40
sballe_hvprash: yes please14:40
hvprashsballe acabot : we are trying to find where thats headed14:40
acabothvprash : did you see this email http://lists.openstack.org/pipermail/openstack-dev/2016-May/093826.html ?14:41
hvprashacabot, thx. i missed that14:41
hvprashwill go through it14:41
acabotits a quick recap from Congress PTL but there are no actions yet14:41
acabotsballe_ : I will not be able to attend the congress IRC meeting tomorrow14:42
acabotsballe_ : can you go ?14:42
hvprashacabot, as we discussed earlier there was another effort from cisco sometime back on solverscheduler.. so lot of parallel efforts14:42
acabotsballe_ : just to check if there is any action related to us ?14:42
sballe_no I have a full day of meeting. Can joe go?14:42
acabothvprash : I dont want to tell the full story again...we decided to build this project because there is no way to improve the Nova scheduler14:43
hvprash:)14:44
sballe_acabot: +114:44
acabotso we decided to build Watcher as a project that uses Nova scheduler as it is14:44
*** m1r4nt15_b0y is now known as d34dh0r5314:44
acabot#info Valet is an interesting initiative coming from AT&T to try to do resource optimization at Heat level14:45
acabotunfortunately code is not open source right now14:46
acabotand it seems to be focused on telco use cases14:46
hvprashfor NFV etc ?14:46
acabotbut we need to keep an eye on it14:46
jed56+1 , agree they seems to focus on network topologies14:46
tpeoplesacabot: are they periodically optimizing the environment or was it making more intelligent initial placement decisions?14:46
acabotyes mostly to guarantee NFV performances14:46
hvprashwill try to get some details from comcast too ;)14:47
acabottpeoples : I think so, but you should look at the presentation (20 minutes) https://www.youtube.com/watch?v=zxcfM9tSh7Y14:47
acabotsballe_ : can you share details about our next mid-cycle ?14:48
dronshawacabot: I had spoken to Joe about Valet at the summit and thought there were plans to open source soon, not positive on that14:48
*** shaohe_feng has quit IRC14:48
*** shaohe_feng has joined #openstack-meeting-414:48
acabotdronshaw  : yes, Joe said that they will test it on their infra before, my concern is that they will deliver a full stack of software and it will be hard for the community to jump in14:49
sballe_acabot sure. It will be in Hillsboro, OR and the dates are 7/19-20 and maybe a half day on the 2114:50
*** sshnaidm has quit IRC14:50
acabotsballe_ : ok can you register an event on eventbrite or you want me to do it ?14:50
sballe_yes will do14:50
sballe_If I need help I will ping you since I haven't done it before14:51
acabot#action sballe_ register mid-cycle meetup details on eventbrite14:51
acabotno pb14:51
*** mohankumar has quit IRC14:51
acabotpav0 : you want to talk about puppet recipe for Watcher ?14:51
pav0acabot: hi, yes14:51
dronshawacabot: completely understand14:52
acabotso dtardivel is our maintainer for Watcher repositories so I suggest he creates the puppet repo14:52
sballe_+114:52
*** yamahata has quit IRC14:52
acabotbut he is away until monday14:52
pav0acabot: +114:52
acabotis it ok for you to wait until next monday ?14:53
pav0acabot: no problem :)14:53
*** yamahata has joined #openstack-meeting-414:53
acabotgreat14:53
pav0acabot: I just start working on it14:53
*** pav0 has left #openstack-meeting-414:53
acabot#action dtardivel create a puppet repo for Watcher14:53
acabotanything you need to have on the CI ?14:53
*** mbound has joined #openstack-meeting-414:53
*** salv-orlando has joined #openstack-meeting-414:54
*** alexey_weyl has joined #openstack-meeting-414:54
*** pav0 has joined #openstack-meeting-414:55
acabotpav0 : dtardivel will come back to you on our IRC channel for details on Monday14:55
acabotany other discussion ?14:55
pav0acabot: should I parametrize all variables14:55
pav0available in watcher.conf file14:55
*** jmckind_ has joined #openstack-meeting-414:55
vincentfrancoisepav0: I can also help for project setup if you have questions14:55
pav0or should I parametrize only the main variables like connection etc14:55
jed56yes you should :)14:56
pav0vincentfrancoise: okey, I will write to you14:56
jed56you should parametrize all variables14:56
*** alexey_weyl has quit IRC14:56
*** vtech has joined #openstack-meeting-414:56
*** cwolferh has joined #openstack-meeting-414:57
pav0jed56: ok. Some variables in puppet-nova are not parametrize, so I wonder if I should do the same or not14:57
acabotok dtardivel has experience with puppet so he will give our needs14:57
*** a_w has joined #openstack-meeting-414:57
acabotthx pav014:58
jed56pav0:  IMHO, we have less variable than nova :)14:58
acabottime to end the meeting14:58
*** jmckind has quit IRC14:58
*** shaohe_feng has quit IRC14:58
acabotthank you guys, have a good day / night14:58
tpeoplesyou too14:59
hvprashthx, bye14:59
vincentfrancoisebye14:59
pav0jed56: not so. I reviewed watcher.conf.sample and there is a lot variables xD14:59
pav0you yoo14:59
sballe_bye14:59
jed56:)14:59
pav0you too14:59
acabot#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Wed May  4 14:59:18 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
*** salv-orlando has quit IRC14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-05-04-13.59.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-05-04-13.59.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-05-04-13.59.log.html14:59
*** shaohe_feng has joined #openstack-meeting-414:59
*** mhoppal has joined #openstack-meeting-415:00
*** mhoppal has left #openstack-meeting-415:00
*** zeih has quit IRC15:00
*** sfinucan has left #openstack-meeting-415:01
*** mkaushik has quit IRC15:03
*** emagana has joined #openstack-meeting-415:03
*** yamamoto has quit IRC15:04
*** sshnaidm has joined #openstack-meeting-415:05
*** a_w has quit IRC15:07
*** a_w has joined #openstack-meeting-415:08
*** shaohe_feng has quit IRC15:09
*** gb21 has joined #openstack-meeting-415:10
*** GregoryKatsaros has quit IRC15:11
*** shaohe_feng has joined #openstack-meeting-415:11
*** a_w has quit IRC15:12
*** raj_singh has left #openstack-meeting-415:17
*** armax has quit IRC15:17
*** gangil has joined #openstack-meeting-415:17
*** spzala has joined #openstack-meeting-415:18
*** shaohe_feng has quit IRC15:19
*** Swami_ has joined #openstack-meeting-415:19
*** vhoward has quit IRC15:19
*** shaohe_feng has joined #openstack-meeting-415:20
*** Swami has quit IRC15:22
*** bpokorny has joined #openstack-meeting-415:23
*** dronshaw has quit IRC15:27
*** armax has joined #openstack-meeting-415:27
*** fitoduarte has joined #openstack-meeting-415:28
*** vmahe has quit IRC15:29
*** cinerama has joined #openstack-meeting-415:29
*** shaohe_feng has quit IRC15:29
*** shaohe_feng has joined #openstack-meeting-415:30
*** azbiswas has joined #openstack-meeting-415:30
*** sshnaidm_ has joined #openstack-meeting-415:31
*** sshnaidm has quit IRC15:32
*** mohankumar has joined #openstack-meeting-415:34
*** belmoreira has quit IRC15:34
*** paul-carlton2 has quit IRC15:35
*** pbourke has joined #openstack-meeting-415:35
*** jinquan has joined #openstack-meeting-415:35
*** dshakhray has quit IRC15:36
*** jinquan has left #openstack-meeting-415:36
*** hvprash_ has joined #openstack-meeting-415:36
*** jinquan has joined #openstack-meeting-415:37
*** jinquan has left #openstack-meeting-415:37
*** azbiswas_ has joined #openstack-meeting-415:38
*** armax has quit IRC15:38
*** armax has joined #openstack-meeting-415:38
*** hvprash has quit IRC15:39
*** shaohe_feng has quit IRC15:39
*** shaohe_feng has joined #openstack-meeting-415:40
*** sdake_ has joined #openstack-meeting-415:40
*** azbiswas has quit IRC15:41
*** sdake has quit IRC15:43
*** jinquan has joined #openstack-meeting-415:43
*** alexchadin has quit IRC15:43
*** jmckind has joined #openstack-meeting-415:43
*** salv-orlando has joined #openstack-meeting-415:44
*** azbiswas_ has quit IRC15:45
*** azbiswas has joined #openstack-meeting-415:45
*** cbouch has joined #openstack-meeting-415:45
*** khushbu has quit IRC15:45
*** jschwarz has quit IRC15:45
*** AlanClark has joined #openstack-meeting-415:46
*** sdake_ has quit IRC15:46
*** mhoppal_ has joined #openstack-meeting-415:46
*** mhoppal_ has left #openstack-meeting-415:46
*** jmckind_ has quit IRC15:47
*** khushbu has joined #openstack-meeting-415:47
*** geseib has quit IRC15:47
*** geseib has joined #openstack-meeting-415:47
*** Sukhdev has joined #openstack-meeting-415:48
*** sshnaidm_ has quit IRC15:48
*** MarkAtwood has joined #openstack-meeting-415:49
*** matrohon has quit IRC15:49
*** shaohe_feng has quit IRC15:50
*** lakshmiS has joined #openstack-meeting-415:50
*** shaohe_feng has joined #openstack-meeting-415:51
*** vincentfrancoise has quit IRC15:51
*** andymaier has quit IRC15:52
*** banix has joined #openstack-meeting-415:57
*** mlima has joined #openstack-meeting-415:58
*** prithiv has quit IRC15:58
*** salv-orlando has quit IRC15:59
*** mohankumar has quit IRC15:59
*** prithiv has joined #openstack-meeting-416:00
*** shaohe_feng has quit IRC16:00
*** salv-orlando has joined #openstack-meeting-416:00
*** shaohe_feng has joined #openstack-meeting-416:01
*** amotoki has joined #openstack-meeting-416:02
*** salv-orlando has quit IRC16:03
*** yamamoto has joined #openstack-meeting-416:05
*** shaohe_feng has quit IRC16:10
*** uck has joined #openstack-meeting-416:11
*** shaohe_feng has joined #openstack-meeting-416:11
*** paul-carlton2 has joined #openstack-meeting-416:13
*** hdaniel has quit IRC16:14
*** gangil has quit IRC16:14
*** yamamoto has quit IRC16:14
*** SimonChung has joined #openstack-meeting-416:15
*** numans has quit IRC16:18
*** daneyon has quit IRC16:20
*** shaohe_feng has quit IRC16:20
*** pmesserli has quit IRC16:22
*** shaohe_feng has joined #openstack-meeting-416:22
*** jinquan has left #openstack-meeting-416:23
*** gangil has joined #openstack-meeting-416:23
*** gangil has quit IRC16:23
*** gangil has joined #openstack-meeting-416:23
*** mbound has quit IRC16:23
*** sdake has joined #openstack-meeting-416:24
*** sridhar_ram has joined #openstack-meeting-416:24
*** pmesserl_ has joined #openstack-meeting-416:25
*** javeriak has joined #openstack-meeting-416:26
*** inc0 has joined #openstack-meeting-416:27
*** zenoway has quit IRC16:29
*** zenoway has joined #openstack-meeting-416:29
*** britthouser has joined #openstack-meeting-416:29
*** eghobo has joined #openstack-meeting-416:29
inc0#startmeeting kolla16:30
openstackMeeting started Wed May  4 16:30:10 2016 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.16:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:30
*** openstack changes topic to " (Meeting topic: kolla)"16:30
openstackThe meeting name has been set to 'kolla'16:30
inc0#topic rollcall16:30
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:30
inc0good morning;) show of hands guys!16:30
mlimai'm here :)16:30
*** vhosakot has joined #openstack-meeting-416:30
Jeffrey4l\o/16:30
vhosakot\o\ /o/ \o\ /o/16:30
pbourkehey16:31
*** shaohe_feng has quit IRC16:31
britthouser0/16:31
*** paul-carlton2 has quit IRC16:31
eghoboo/16:31
*** paul-carlton2 has joined #openstack-meeting-416:31
inc0#topic Announcements16:31
*** openstack changes topic to "Announcements (Meeting topic: kolla)"16:31
schwarzm.16:31
*** shaohe_feng has joined #openstack-meeting-416:32
inc0summit last week took it's toll16:32
britthouser+116:32
sdakehey folks rq, inc0 is going to organize today's meeting, I have a persoanl conflict - bbi2 hours or so16:32
inc0cya sdake16:33
vhosakotwas great meeting everyone.... sorry missed meeting whoever missed the summit16:33
inc0so, kolla-kubernates is being created16:33
inc0we decided to run it in separate repo16:33
vhosakotinc0: so, the vote was to create a separate repo ?16:34
Jeffrey4lvhosakot, yes.16:34
inc0let's discuss it at topic16:34
*** huikang_ has joined #openstack-meeting-416:34
inc0as*16:34
vhosakotcool16:34
inc0so, any other announcements16:34
inc0?16:34
*** zenoway has quit IRC16:34
inc0#topic kolla-k8s16:34
*** openstack changes topic to "kolla-k8s (Meeting topic: kolla)"16:34
inc0so yes, vote is for separate repo16:34
vhosakotcool16:35
*** gb21 has quit IRC16:35
inc0we still have issues with pip's kolla-kubernates as project like that was already created16:35
inc0we can go with kolla-k8s16:35
mlimathe name will be kolla-k8s or kolla-kubernates?16:36
britthouseris kolla-kubernetes the OLD stuff (pre-ansible?)16:36
vhosakotinc0: from the emails in   http://paste.openstack.org/show/496099/    this topic includes four threads.. "k8s Core team"     "One repo vs two"     "kolla-kubernetes repository management proposal up for vote"    and   "kolla-kubernetes pm's"16:36
inc0well, we already decided that yes, we do kolla-k8s at all and it will be in another repo16:36
vhosakotyep16:36
inc0we need to discuss core-team setup16:36
vhosakotyep16:36
inc0so I'd like you guys to comment on my email16:37
*** gangil has quit IRC16:37
inc0respond*16:37
Jeffrey4lthe kolla-kubernets has nothing. https://pypi.python.org/pypi/kolla-kubernetes we can re-use it, i think.16:37
inc0Jeffrey4l, but we don't own the project in pip16:37
*** vhoward has joined #openstack-meeting-416:37
inc0any other comments on this one?16:38
*** ninag has joined #openstack-meeting-416:38
Jeffrey4lops.. could we contact the owner?16:38
inc0Jeffrey4l, already done, waiting for answer16:38
vhosakotbritthouser: kolla-kubernetes is one of the names for the repo... we can go with kolla-k8s.. we need to decide if it needs pre-ansbile stuff or not16:38
inc0Ryan will know more about it16:38
Jeffrey4lok. cool16:38
sdakeon my way out - kolla-kubernetes was created by the sap cats16:38
sdakei am taking care of getting ownership of it16:38
sdakegott aroll bye ;)16:38
inc0bye16:38
Jeffrey4lbye16:39
vhosakottc sdake16:39
inc0any other questions/comments on k8s? things are rolling, we need to figure out this stuff, but it's all in progress16:39
Jeffrey4lno.16:39
vhosakotwe covered repo creation and core team.. there is one more item16:40
vhosakotpackage manager for kolla k8s using kubespray and helm... somebody brought this up in design meeting.. http://lists.openstack.org/pipermail/openstack-dev/2016-April/093188.html16:40
*** shaohe_feng has quit IRC16:41
inc0yeah, we need to have this discussion16:41
*** shaohe_feng has joined #openstack-meeting-416:42
inc0but truth be told, I don't know first thing about this;) anyone can comment on it?16:42
schwarzmnope but sounds like premature optimization to me16:42
inc0oh schwarzm , Michael?;) nice to have you around16:43
vhosakotI think it needs to be handled by the packagaing team...16:43
schwarzmlets get stuff into the repo to be packaged before knowing how to package16:43
vhosakotschwarzm: agreed :)  there is nothing yet to package now!16:43
inc0agree, I think we should discuss that later16:43
vhosakotcool16:43
inc0also I'd love to have kfox input into this as he started this topic16:43
inc0so let's move on16:44
inc0#topic stable branches16:44
*** openstack changes topic to "stable branches (Meeting topic: kolla)"16:44
*** sshnaidm_ has joined #openstack-meeting-416:44
inc0(I'm making up ageda as I go, sorry;))16:44
inc0so, we have stable/liberty and stable/mitaka to care about16:44
inc0we got at least one critical bug in mitaka, ubuntu:latest != ubuntu:14.0416:44
vhosakotyes, both are stable and tested... inc0 I see you filed a bug about Ubuntu in summit... was that for master ?16:45
inc0as for liberty, https://review.openstack.org/#/c/308390/16:45
inc0all 3 of them really16:45
inc0I need eyes, thests and merge on patchset above as we don't have liberty right now16:46
vhosakotinc0: is the new approach after the megapatch was abandoned ?16:47
*** gb21 has joined #openstack-meeting-416:47
inc0stable/liberty is a snapshot of stable/mitaka now16:47
inc0so it is actually deploying mitaka16:47
inc0yes, this is approach we're taking16:48
*** bobh has quit IRC16:48
*** paul-carlton2 has quit IRC16:48
inc0and it's super important16:48
vhosakotinc0: got it...16:48
inc0can't stress that enough16:48
inc0any other comments on that one?16:49
*** bobh has joined #openstack-meeting-416:49
Jeffrey4lthere are other bug in the gate now.16:49
vhosakotinc0: will the new bug (ubuntu:latest != ubuntu:14.04) affect your PS ?16:49
Jeffrey4lthe rabbitmq crash in the cento deploy.16:49
inc0vhosakot, not really16:49
*** Swami_ has quit IRC16:49
vhosakotinc0: cool16:49
Jeffrey4lin the mitaka branch, ubuntu + binary is crash.16:50
vhosakotJeffrey4l: is there a bug ?16:50
Jeffrey4lif anyone have time, please fix the gate first. thanks.16:50
Jeffrey4lvhosakot, which one you mean.16:50
Jeffrey4lthere are several bug in the gate.16:50
Jeffrey4lmay be I can post a mail to list the bugs.16:51
Jeffrey4llater.16:51
huikang_jeffrey4l, that will be great16:51
*** unicell has joined #openstack-meeting-416:51
vhosakotJeffrey4l: yes please... we need bug for each gate issue16:51
Jeffrey4lOK. I will write the email after the meeting.16:51
*** shaohe_feng has quit IRC16:51
Jeffrey4lno other comment.16:51
inc0ok, let's move on16:51
inc0#topic ansible 2.016:51
*** openstack changes topic to "ansible 2.0 (Meeting topic: kolla)"16:51
inc0we didn't really have time to discuss it on summit16:52
inc0and I don't think we have quorum to discuss it really now16:52
vhosakotwe need to add work items to the bp Jeffrey4l created...16:52
*** shaohe_feng has joined #openstack-meeting-416:52
vhosakotI can look into kolla_docker... I see PS for kolla_toolbox.. what else needs to be updated for ansible 2.0 ?16:52
inc0I'm digging into it now, let me understand scope of changes and then we'll follow up on that16:52
Jeffrey4lI do not think there are much work items to do.16:53
*** zenoway has joined #openstack-meeting-416:53
inc0it should be easy to make it non-exploding16:53
inc0but to make it proper, that's a major refactoring16:53
inc0vhosakot, I already got kolla_docker working16:53
Jeffrey4lvhosakot, yep. as far as I know. only the kolla_docker need more work.16:53
vhosakotdoes moving to Ansible 2.0 affect just the deploy node or the target nodes as well (like control, compute, network, storage)16:53
inc0I hope I can propose patchset to allow deploy with 2.0 this week16:53
vhosakotinc0: cool16:53
*** javeriak_ has joined #openstack-meeting-416:54
britthousershould be just the deploy node @vhosakot, that is where ansible is installed.16:54
inc0deployed node doesn't have ansible at all16:54
Jeffrey4linc0, cool. please push it. even it is wip.16:54
britthouser?16:54
inc0just deployment16:54
britthouseroh16:54
inc0deployed nodes*16:54
britthouserI missed the -ed vs -ment16:54
*** javeriak has quit IRC16:54
vhosakotcool... britthouser inc0 that is what I thought16:54
inc0I'll post wip soon16:55
inc0any other comments on this one?16:55
*** sdake has quit IRC16:55
Jeffrey4lthanks.16:55
vhosakotJeffrey4l: is the rabbitmq crash seen on both Centos source and binary in gate ?16:55
*** ddieterly is now known as ddieterly[away]16:55
inc0#topic Open discussion16:55
*** openstack changes topic to "Open discussion (Meeting topic: kolla)"16:55
Jeffrey4lvhosakot, yep.16:55
mlimawhen we begin to support Ubuntu 16.04?16:55
vhosakotyes xenial16:55
*** emagana has quit IRC16:55
Jeffrey4lvhosakot, see this https://review.openstack.org/30420516:55
Jeffrey4lgate is lying now.16:56
inc0mlima, could you please add bp for that16:56
inc0?16:56
inc0or check if it's already there?16:56
mlimayes, i can16:56
huikang_If you core have time, I would like hear some comment on compute-kit plugin, like nova-docker and neutron OVN16:56
vhosakotmlima: does kolla master out of the box work on xenial ?16:56
inc0I'd wait a month or two really16:56
mlimavhosakot, i don't know16:57
vhosakothuikang_: I wanted to reply to your email... sdake has great views about plugins (like nova-docker,  neutron OVN, ODL, etc)16:57
mlimabut it should work16:57
*** zenoway has quit IRC16:57
Jeffrey4lseem we have multi open topic. :D.16:57
inc0huikang_, https://github.com/openstack/kolla/blob/master/doc/image-building.rst#plugin-functionality have you seen this one?16:57
huikang_vhosakot, great. please email after the meeting16:57
*** scsnow_ has joined #openstack-meeting-416:58
*** emagana has joined #openstack-meeting-416:58
huikang_inc0, thanks.16:58
vhosakothuikang_: do you have any ideas how to handle neutron plugins ? we need an approach for cinder as well.. sberzerk also has ideas for plugins16:58
Jeffrey4lcurrent plugin function only work with source installation.16:58
huikang_nova-docker and neutron ovn work perfect with source installation16:59
vhosakotshould the kolla repo carry all the plugin code ?16:59
mlimainc0, https://blueprints.launchpad.net/kolla/+spec/add-xenial-support16:59
inc0thanks mlima16:59
inc0vhosakot, unrealistic16:59
*** eghobo has left #openstack-meeting-416:59
inc0even neutron doesn't want to carry all it's plugins code any more17:00
vhosakotyes... then, where should the code exist... ? I hear stackforge is dead..17:00
vhosakotcinder carries it17:00
Jeffrey4lvhosakot, that's not possible.17:00
huikang_vhosakot, I build nova-docker and neutron-ovn image17:01
inc0we cannot possibly maintain complexity of all of it17:01
inc0all we can do is to enable others to build their containers locally17:01
pbourkethat is what we do currently17:01
huikang_inc0, these are optional, like enable_cinder17:01
vhosakotyes.. exactly what huikang_ is doing...17:01
Jeffrey4linc0, yea.  kolla need a plugin mechianism like devstack.17:01
inc0huikang_, see if link I gave you fixes your issues17:01
*** shaohe_feng has quit IRC17:01
*** gangil has joined #openstack-meeting-417:02
*** ninag has quit IRC17:02
inc0if it's not let's revisit this topic17:02
inc0we have ideas how to make it fully customizable17:02
inc0right now you can do mixture of our plugin mechanism and --include-footer17:02
*** shaohe_feng has joined #openstack-meeting-417:02
*** ninag has joined #openstack-meeting-417:02
vhosakotinc0: can code in {{ include_footer }} be merged into kolla master ?17:03
mlimainc0, which will be the default when kolla begin to support xenial?17:03
*** emagana has quit IRC17:03
huikang_inc0, since nova-docker is part of the big tent, it makes sense to provide such container, like nova-libvirt17:03
inc0vhosakot, what do you mean?17:03
*** antonyfm has quit IRC17:03
*** ddieterly[away] is now known as ddieterly17:03
inc0mlima, not sure, could you start a ML thread about that?17:04
*** emagana has joined #openstack-meeting-417:04
inc0huikang_, we could, sure, it's just a matter of logistics and who exactly will support it17:04
vhosakotinc0: I meant if 3rd party plugin code can be added as include_footer ?17:04
inc0vhosakot, yeah...why not?17:04
inc0all you need to do is to write chunk of dockerfile to install it17:05
vhosakotinc0: then, kolla ends up carrying plugin code17:05
inc0no17:05
huikang_inc0, I can support nova-docker :). The bp exists for a while https://blueprints.launchpad.net/kolla/+spec/nova-docker-container17:05
inc0becasue that's you writting dockerfile17:05
Jeffrey4lthe include_footer is customized and never be merged into kolla code. vhosakot17:05
inc0huikang_, well...commit the code then17:05
huikang_we have implemented the nova-docker container and ansible17:05
huikang_inc0, sure and will do soon17:06
vhosakotJeffrey4l: right... I think include_footer is pure non-kolla code17:06
inc0it's whatever you want it to be really;)17:06
vhosakotinc0: ecaxtly... it can be whatever the operator wants other than what kolla offers17:06
*** ninag has quit IRC17:07
huikang_vhosakot, agree17:07
vhosakothuikang_: can you please link that bp as topic in gerrit...17:07
*** prithiv has quit IRC17:07
pbourkeyou actually dont need a footer for most cases17:08
vhosakotis nova-docker a big tent project ?17:08
pbourkeif you look in the neutron-server dockerfile17:08
pbourkeit will install plugins automatically *if* they are available17:08
huikang_vhosakot, yes it is17:08
huikang_https://github.com/openstack/nova-docker17:08
*** scsnow_ has quit IRC17:08
huikang_vhosakot, nova-docker is under openstack repo17:09
inc0huikang_, but if it's big tent;)17:09
inc0well it's part of nova17:09
*** rtheis_ has joined #openstack-meeting-417:09
*** jmckind has quit IRC17:09
vhosakoti thought it was a sister project of nova... like how neutron-fwaas or neutron-vpn-aas for neutron... if it is big tent, then, yes, we dont have to treat it like a plugin17:10
inc0nah, it's jsut a compute driver vhosakot17:10
vhosakotfor docker (sorry for dumb q :))17:10
huikang_vhosakot, inc0 is right. nova-docker is a driver liek nova-libvirt17:10
vhosakotcool17:10
inc0huikang_, we can have it in kolla, no problem, just submit patches17:11
huikang_inc0, thanks. I will17:11
*** vishnoianil has quit IRC17:11
vhosakotyes, agreed.. we should have/welcome it in kolla17:11
inc0so any other topic needing attention?17:11
Jeffrey4lhttp://lists.openstack.org/pipermail/openstack-dev/2016-May/093936.html here17:11
Jeffrey4l better solution for the non-ini formatconfigure file17:12
*** rtheis has quit IRC17:12
vhosakot2 more.. "Add a gating check job for precheck"   and  threat analysis (what are we doing about this ?)17:12
*** shaohe_feng has quit IRC17:12
Jeffrey4lcomment iw welcome.17:12
Jeffrey4liw/is17:12
*** Swami has joined #openstack-meeting-417:12
*** paul-carlton2 has joined #openstack-meeting-417:12
huikang_will comment after the meeting, jeffrey4l17:12
vhosakotI like Jeffrey4l approach to add precheck for _every_ gate job17:12
Jeffrey4lhuikang_, thanks.17:12
*** salv-orlando has joined #openstack-meeting-417:12
huikang_I think precheck gate job should be part of deploy job17:13
*** shaohe_feng has joined #openstack-meeting-417:13
huikang_so we need to update that bp17:13
inc0Jeffrey4l, how does adding this functionality to out merge_config sounds to you?17:13
Jeffrey4ljust add the precheck to the deploy_aio.sh script is enough, i think.17:13
vhosakotright.. precheck should happen pre-deploy... in every gate job17:13
inc0might be tricky tho17:13
vhosakotJeffrey4l: yes17:13
huikang_will update that precheck bp after the meeting17:14
inc0in any case, it will require meddling with merge_configs.py17:14
inc0and I'd rather do that once we move to ansible 2.0 fullt17:14
inc0fully17:14
vhosakotinc0: that is a good point.. as we need to update mer_configs for 2.017:14
Jeffrey4linc0, maybe just add a extra field to mark the merge strategy?17:14
inc0either way, let's focus on migration to 2.0 and in the meantime figure out best strategy17:15
Jeffrey4lremember: overwrite is not ideal either. any better solution is welcome.17:15
inc0everyone, please consider this topic and respond to Jeffs mail17:15
*** scsnow_ has joined #openstack-meeting-417:15
vhosakotyes... http://lists.openstack.org/pipermail/openstack-dev/2016-May/093936.html17:16
inc0we can make use of some of jinja2s magics17:16
mlimainc0, thread was started in ml17:16
Jeffrey4linc0, maybe.17:16
vhosakotI think we already use jija2 to use variables in non-ini files...17:16
inc0yeah, what I mean is to go full jinja217:17
inc0I'll show you what I mean, I'll write an email about it17:17
Jeffrey4lcool17:17
vhosakotcool17:17
Jeffrey4lanother question is http://lists.openstack.org/pipermail/openstack-dev/2016-May/093799.html17:17
Jeffrey4lhttp://lists.openstack.org/pipermail/openstack-dev/2016-May/093799.html17:17
Jeffrey4l[openstack-dev] [Kolla] lock the distro version in the stable branch17:17
*** prithiv has joined #openstack-meeting-417:17
inc0Jeffrey4l, ubuntu was already merged17:18
Jeffrey4li am thinking may be we need lock the image tag in the master branch either.17:18
inc0that we did17:18
Jeffrey4linc0, but that is not ideal and confused the end-user.17:19
vhosakotJeffrey4l: do you mean this ?   -->  https://github.com/openstack/kolla/blob/master/etc/kolla/globals.yml#L2017:19
*** prithiv has quit IRC17:19
inc0https://github.com/openstack/kolla/blob/master/kolla/cmd/build.py#L34717:19
inc0Jeffrey4l, I agree17:20
Jeffrey4lmoreover. we do not support other Ubuntu release except for trusty. ( because the sources.list file)17:20
inc0we need to find better defaults17:20
*** scsnow_ has quit IRC17:20
inc0problem is default on this one is dependant on base_distro17:20
*** prithiv has joined #openstack-meeting-417:20
Jeffrey4lyep17:20
*** prithiv has quit IRC17:20
Jeffrey4lvhosakot, no.17:21
Jeffrey4lvhosakot, i mean the build image stage.17:21
vhosakotJeffrey4l: so, kolla master does not work with Ubuntu 16, we need a bug for it please17:21
Jeffrey4lvhosakot, ther base_image and base_image_tag17:21
*** shaohe_feng has quit IRC17:22
mlimavhosakot, we have a bp https://blueprints.launchpad.net/kolla/+spec/add-xenial-support17:22
vhosakotcool mlima!17:22
*** dave-mccowan has joined #openstack-meeting-417:22
Jeffrey4lI think we should depend on certain specify tag rather than the latest tag.17:23
mlimai did right now hehe17:23
*** shaohe_feng has joined #openstack-meeting-417:23
vhosakotyes, defaulting to 14.04 for base_tag == 'latest'  should not happen for xenial17:23
inc0you can specify 16.0617:23
inc0and run xenial this way17:23
vhosakotyes... to kolla-build... Jeffrey4l did you pass base_tag for kolla-build ?17:23
mlimai started this thread http://lists.openstack.org/pipermail/openstack-dev/2016-May/093956.html17:24
*** paul-carlton2 has quit IRC17:24
*** jed56 has quit IRC17:24
Jeffrey4lvhosakot, what i want is changing the default behavior.17:24
Jeffrey4li think it work when change the base_tag by using cli paramter or in the kolla-build.conf file.17:25
*** coolsvap has joined #openstack-meeting-417:25
vhosakotwell, default for 14 is different than default for 16... I think it is a matter for adding new code for 16...17:25
vhosakotcool17:25
vhosakotI think we covered all topics... everyone, please add comments if any in k8s spec.. https://review.openstack.org/#/c/304182/17:26
Jeffrey4lI do not think we should support both 14 and 16 in one branch.( for example mitaka branch)17:27
Jeffrey4lone is enough.17:27
vhosakotI think the spec must be full and solid to start any dev17:27
Jeffrey4lin this case, options is not good.17:27
inc0agree with Jeffrey4l17:27
inc0we can easily make our code unmainainable17:27
inc0lets focus on one and make it well17:27
Jeffrey4lmaybe, liberty is 14, mitaka is 14 and newton is 1617:27
huikang_I like this17:28
vhosakotinc0: yes, I like that too17:28
Jeffrey4leasy and enough. :D17:28
inc0ok, we ran out of time17:28
vhosakotinc0: kolla must gracefully exit on unsupported distro versions17:28
inc0thank you guys!17:28
Jeffrey4lvhosakot, yes.17:28
*** paul-carlton2 has joined #openstack-meeting-417:28
vhosakotthanks all!17:28
inc0part of our upgrade17:28
pbourkethanks17:28
inc0plays17:28
inc0#endmeeting kolla17:28
Jeffrey4lthanks all guys.17:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:28
openstackMeeting ended Wed May  4 17:28:55 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-05-04-16.30.html17:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-05-04-16.30.txt17:29
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-05-04-16.30.log.html17:29
*** huikang_ has left #openstack-meeting-417:29
*** vhosakot has left #openstack-meeting-417:29
*** ddieterly is now known as ddieterly[away]17:29
*** mlima has left #openstack-meeting-417:29
*** spzala has quit IRC17:30
*** spzala has joined #openstack-meeting-417:30
*** AlanClark has quit IRC17:31
*** spzala has quit IRC17:31
*** javeriak_ has quit IRC17:32
*** pcm_ has joined #openstack-meeting-417:32
*** shaohe_feng has quit IRC17:32
*** spzala has joined #openstack-meeting-417:32
*** shaohe_feng has joined #openstack-meeting-417:33
*** inc0 has quit IRC17:33
*** unicell has quit IRC17:33
*** unicell1 has joined #openstack-meeting-417:33
*** tonytan4ever has quit IRC17:34
*** mohankumar__ has joined #openstack-meeting-417:34
*** pcm_ has left #openstack-meeting-417:38
*** Sukhdev has quit IRC17:42
*** shaohe_feng has quit IRC17:42
*** shaohe_feng has joined #openstack-meeting-417:43
*** pvaneck has joined #openstack-meeting-417:44
*** ccesario has joined #openstack-meeting-417:44
*** tonytan4ever has joined #openstack-meeting-417:45
*** javeriak has joined #openstack-meeting-417:46
*** paul-carlton2 has quit IRC17:50
*** padkrish has joined #openstack-meeting-417:51
*** shaohe_feng has quit IRC17:53
*** shaohe_feng has joined #openstack-meeting-417:55
*** khushbu has quit IRC17:55
*** emagana has quit IRC17:59
*** minwang2 has joined #openstack-meeting-417:59
*** salv-orlando has quit IRC18:01
*** gangil has quit IRC18:01
*** emagana has joined #openstack-meeting-418:02
*** ninag has joined #openstack-meeting-418:02
*** shaohe_feng has quit IRC18:03
*** sambetts is now known as sambetts|afk18:03
*** shaohe_feng has joined #openstack-meeting-418:04
*** emagana has quit IRC18:07
*** mdorman has joined #openstack-meeting-418:08
*** vishnoianil has joined #openstack-meeting-418:10
*** pbourke has quit IRC18:12
*** shaohe_feng has quit IRC18:13
*** gangil has joined #openstack-meeting-418:14
*** shaohe_feng has joined #openstack-meeting-418:14
*** javeriak has quit IRC18:15
*** uck has quit IRC18:17
*** javeriak has joined #openstack-meeting-418:17
*** ninag has quit IRC18:18
*** gangil has quit IRC18:18
*** ninag has joined #openstack-meeting-418:19
*** ninag_ has joined #openstack-meeting-418:20
*** rstarmer has joined #openstack-meeting-418:23
*** sridhar_ram has left #openstack-meeting-418:23
*** shaohe_feng has quit IRC18:23
*** ninag has quit IRC18:24
*** shaohe_feng has joined #openstack-meeting-418:24
*** ninag_ has quit IRC18:25
*** s3an2 has joined #openstack-meeting-418:25
*** inc0 has joined #openstack-meeting-418:26
*** zenoway has joined #openstack-meeting-418:29
*** emagana has joined #openstack-meeting-418:30
*** bloatyfloat has joined #openstack-meeting-418:31
*** adduarte has joined #openstack-meeting-418:31
*** fitoduarte has quit IRC18:33
*** shaohe_feng has quit IRC18:34
*** Jeffrey4l has quit IRC18:34
*** ninag has joined #openstack-meeting-418:34
*** shaohe_feng has joined #openstack-meeting-418:34
*** ninag_ has joined #openstack-meeting-418:35
*** raj_singh has joined #openstack-meeting-418:35
*** raj_singh has left #openstack-meeting-418:36
*** omnipresent has joined #openstack-meeting-418:36
*** ninag__ has joined #openstack-meeting-418:36
*** khushbu has joined #openstack-meeting-418:37
*** ddieterly[away] is now known as ddieterly18:38
*** ninag has quit IRC18:38
*** ninag_ has quit IRC18:40
*** zenoway has quit IRC18:40
*** ninag__ has quit IRC18:40
*** lakshmiS has quit IRC18:42
*** sdake has joined #openstack-meeting-418:42
*** lakshmiS has joined #openstack-meeting-418:42
*** shaohe_feng has quit IRC18:44
*** automagically has joined #openstack-meeting-418:44
*** sdake has quit IRC18:44
*** shaohe_feng has joined #openstack-meeting-418:45
*** sdake has joined #openstack-meeting-418:46
*** MarkAtwood has quit IRC18:47
*** padkrish has quit IRC18:48
*** padkrish has joined #openstack-meeting-418:48
*** bpokorny_ has joined #openstack-meeting-418:50
*** vishwanathj has joined #openstack-meeting-418:50
*** bpokorny_ has quit IRC18:51
*** salv-orlando has joined #openstack-meeting-418:51
*** bpokorny_ has joined #openstack-meeting-418:51
*** ninag has joined #openstack-meeting-418:52
*** adduarte has quit IRC18:53
*** ninag has quit IRC18:54
*** bpokorny has quit IRC18:54
*** adduarte has joined #openstack-meeting-418:54
*** shaohe_feng has quit IRC18:54
*** gangil has joined #openstack-meeting-418:55
*** ninag has joined #openstack-meeting-418:55
*** salv-orlando has quit IRC18:56
*** salv-orlando has joined #openstack-meeting-418:56
*** gangil has quit IRC18:57
*** shaohe_feng has joined #openstack-meeting-418:57
*** minwang2 has quit IRC18:58
RaginBajin#startmeeting operators_ops_tools_monitoring18:59
openstackMeeting started Wed May  4 18:59:09 2016 UTC and is due to finish in 60 minutes.  The chair is RaginBajin. Information about MeetBot at http://wiki.debian.org/MeetBot.18:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:59
*** openstack changes topic to " (Meeting topic: operators_ops_tools_monitoring)"18:59
openstackThe meeting name has been set to 'operators_ops_tools_monitoring'18:59
RaginBajin#link https://etherpad.openstack.org/p/osops-irc-meeting-2016050418:59
RaginBajinThat's the agenda for today's meeting.19:00
RaginBajino/19:00
RaginBajinJust giving it a few minutes for others to join.19:02
*** emagana has quit IRC19:02
*** minwang2 has joined #openstack-meeting-419:02
mdormano/19:02
mdormanhere-ish19:03
RaginBajinđź‘Ť19:03
*** klindgren has joined #openstack-meeting-419:04
*** shaohe_feng has quit IRC19:04
mdormanok here for real now19:06
RaginBajinGreat.. Still only us at the moment.19:06
*** mriedem has joined #openstack-meeting-419:07
* mriedem joins late19:07
mdormani always worry i’ll have the UTC offset wrong and be an hour late19:07
*** javeriak_ has joined #openstack-meeting-419:07
*** salv-orlando has quit IRC19:07
RaginBajinHopefully a few more will join.  Yeah I figured out in my Outlook calendar that you can actually enter it as UTC19:07
RaginBajinand it will do the conversion for you within the calendar and update all your devices that way19:07
*** shaohe_feng has joined #openstack-meeting-419:07
RaginBajinHi mriedem.. Thanks for coming19:08
mdormancool19:08
mdormanklindgren is here too19:08
RaginBajinperfect..19:08
*** salv-orlando has joined #openstack-meeting-419:08
RaginBajinwell I guess we can just start and we'll see where it takes us.19:09
*** javeriak_ has quit IRC19:09
RaginBajin#topic Summit Recap19:09
*** openstack changes topic to "Summit Recap (Meeting topic: operators_ops_tools_monitoring)"19:09
RaginBajinThere are two big sessions we had.. https://etherpad.openstack.org/p/AUS-ops-OSOps and https://etherpad.openstack.org/p/AUS-ops-Requests-for-Enhancement-Process19:09
*** itisha has quit IRC19:09
RaginBajinBoth of them had some really good discussions going on..19:10
RaginBajinThe first half of the OSOps had close to the same discussion points as the RFE sessions.19:10
*** piet has joined #openstack-meeting-419:10
*** rockyg has joined #openstack-meeting-419:10
*** javeriak has quit IRC19:10
rockygo/19:11
*** automagically has left #openstack-meeting-419:11
RaginBajinI think the biggest action that came out of those sessions was ways that from either direction that feedback can be provided.19:11
RaginBajinIdeas around having Liason's that possible work between the groups was laid out. I think a great example of that happening right now is mriedem from the Nova team participating in our group sessions.19:12
mdormandid that idea of liasons seem to resonnate with the other projects, too?  i couldn’t come to the RFE session19:13
RaginBajinFrom what I could tell, there wasn't a lot of other projects attending..19:13
*** salv-orlando has quit IRC19:13
mdormanah i see, heh.19:13
RaginBajinSo, I think in order for it to work, we (osops) would have to find someone that is willing to participate from this side.19:13
RaginBajinand go to their meetings to start building that relationship19:14
mdormanmakes sense19:14
RaginBajinWe also heard that the OSOps group can be an advocation group for patches, tools, and features that operators would like to see.19:15
*** shaohe_feng has quit IRC19:15
mriedemfwiw, cburgess is usually always in the nova channel, and is pretty involved with ops questoins when the nova devs have them19:15
mriedemb/c he's reasonably familiar with the code19:15
mriedemnic too19:15
mriedemso we have some of that already19:15
RaginBajinOh that's good to know.. Maybe we can reach out to them to see if they would be willing to bring back what they know here as well.19:16
mriedemwhat we (nova) don't really have a lot of the time is someone from the ops side coming to us saying 'this is a major thing that all of us are dealing with and would like to see it prioritized if possible and this is why'19:16
mriedemso we don't know what we don't know19:16
*** tonytan4ever has quit IRC19:17
mriedemto the point raised in the RFE session, it doesn't mean nova is going to drop everything it's already doing, or planning to do, for anything that's brought up19:17
mriedembut it'd be good to know so it's in our heads and potential backlog19:17
RaginBajinThat to me is the feedback loop I was really interested in.. I see all the mentions in etherpads, and it's like if 20 people are saying yes to it.. Then maybe we need to figure out how to bring it up.19:17
*** uck has joined #openstack-meeting-419:17
mriedemhonestly i think if there is just a thing that bubbles up on the ops side, make sure it's mentioned in this meeting or the nova meeting or in the ML19:18
mriedemjust to get the initial communication ball rolling19:18
*** emagana has joined #openstack-meeting-419:18
*** shaohe_feng has joined #openstack-meeting-419:18
RaginBajinGotcha..19:18
mriedembtw, communication ball (tm)19:18
RaginBajinAs long as it comes in different colors.19:18
mriedemcan do19:19
RaginBajinAnother item that was mentioned was finding a task to start off with to start figuring out how to groom a list of issues..19:19
RaginBajinI think there are two great sessions that a lot of information could be pulled into and maybe summarized into particular problems...19:20
RaginBajinhttps://etherpad.openstack.org/p/AUS-ops-Liberty-upgrades and https://etherpad.openstack.org/p/AUS-ops-informal-meetup19:20
RaginBajinI'm wondering if there is anyone out there that would like to take that action on..   I can also raise it to the mailing list as well for additional help19:20
RaginBajinWe could say just take the Nova side (since we have active representation) and collect all the Nova type of issues.. Work them down into "yeah that's a config problem" to "ooooh that's really broke" and then start with that list.19:21
RaginBajinWhoa whoa.. Too many volunteers... :)19:23
mriedemi was in the liberty upgrades session and i don't really remember any kind of action items for nova come out of that19:23
*** uck has quit IRC19:23
RaginBajinYou are probably right. I just know that there was a lot of discussions around a lot of things.. Maybe another Ops session is a better option.19:24
RaginBajinEither way, I'll take the action to go ahead and put something out on the Mailiing List to see if i can wrangle up some help.19:24
RaginBajin#action raginbajin will send out an email asking for help to break down an etherpad or two to collect data to share with the group and nova about problems identified.19:24
*** shaohe_feng has quit IRC19:25
*** sdake has quit IRC19:25
*** sdake has joined #openstack-meeting-419:26
RaginBajin Does anyone else want to maybe send out an email to the list about looking for liasons to work between osops and the project teams?  Are we at that point to take on a few more, should we?19:26
*** shaohe_feng has joined #openstack-meeting-419:26
*** minwang2 has quit IRC19:26
RaginBajinOk. Well I'll take that one as well to keep things moving forward.19:27
mdormanyeah we could at least ask.  see if anyone out there is already kinda doing that, anyway, or if folks have interest in particular projects.19:28
RaginBajin#action  RaginBajin to email out to the mailing list discussing the idea of liasons working between osops and project teams.  Hopefully this will bring in some feedback.19:28
RaginBajinOk.. I think the feedback will tell us if there is any sort of interest out there at least for now.19:28
mdormanagreed19:29
*** nmadhok has quit IRC19:29
*** mbound has joined #openstack-meeting-419:29
RaginBajinThe only other actions that were from the summit was to get the Kolla project to maybe add some brief configuration files that could be used for sanity checking.. Right now you don't know what options you should be using for a working model and which ones don't19:29
*** salv-orlando has joined #openstack-meeting-419:30
RaginBajinand I need to upload a rally job that I have that creates a vm and then ssh's into it to test end to end connectivity as an example for monitoring.19:30
RaginBajinOther than that.. We are on to New business19:30
RaginBajin#topic new business19:30
*** openstack changes topic to "new business (Meeting topic: operators_ops_tools_monitoring)"19:30
RaginBajinI think you added a few things mriedem19:31
mriedemyeah19:32
*** simon-AS559 has joined #openstack-meeting-419:32
mriedem Request for operator review of nova spec https://review.openstack.org/#/c/306647/ Improve Scheduler Logging19:32
mriedemcfriesen had a thing in the ops list about this19:32
mriedembasically just looking for feedback on how ops would like to see this done/used19:32
mriedemi.e. dump debug only on NoValidHost, or always, or configurable, etc19:32
mdormani looked at that this morning, i think it’ll be a great step forward19:33
mriedem#help Request for operator review of nova spec https://review.openstack.org/#/c/306647/ Improve Scheduler Logging19:33
mriedemthe other one is19:33
*** woodard has quit IRC19:33
mriedem#help Request for operator review of nova spec https://review.openstack.org/#/c/311529/ Add spec for lower case metadata keys only19:33
*** woodard_ has joined #openstack-meeting-419:33
mriedemthis is a spec to add a microversion in the nova api to enforce that metadata keys are only lower-case,19:33
mriedembecause depending on your database, it treats the values different in the backend19:34
mriedemwhich is a long standing latent bug for things like aggregate metadata, flavor extra specs, and instance metadata19:34
mriedemso the idea here is, don't dick around with the db api gorp, and just enforce lower-case in the api after the microversion19:34
mdormanmakes sense19:34
mriedemand anyone below that microversoin has to live with the latent bug19:34
mriedemwhich we'll document in the api-ref19:34
mriedemthere would be a nova-manage command provided to fold the duplicate metadata keys19:35
mriedemso that's a thing deployers can use, but would like feedback on how that might be used19:35
*** shaohe_feng has quit IRC19:35
mriedemor if we're missing anything and doing this could cause big problems for people19:35
mdormanwas there a post to the ML about that one, too?   i can’t remember19:36
mriedemyeah19:36
mdormankk19:36
*** vhoward has quit IRC19:36
mriedemit's linked as a reference in the spec19:36
*** shaohe_feng has joined #openstack-meeting-419:36
mdormangottcha19:36
RaginBajinIs there anything in particular that we can help with on these?19:36
RaginBajin My initial thought is sending out some more reminders on the Mailing list to get more feedback.19:36
*** balajin has joined #openstack-meeting-419:36
mriedemcfriesen already did on the first one19:38
mriedemand that's the one that probably needs more feedback19:38
mriedemthe metadata keys fix is probably less of an issue,19:38
mriedemso just one or two ops being cool with that is good for me19:38
*** tonytan4ever has joined #openstack-meeting-419:38
RaginBajinGotcha.. Well lets see what we can do then..19:38
*** baoli_ has quit IRC19:39
*** geseib has quit IRC19:39
*** geseib has joined #openstack-meeting-419:39
RaginBajinOk.. Is there anything else that anyone would like to bring up.19:39
mdormanso question mriedem , when there is a new patchset posted on a spec review, do you all look for additional +1’s at that point?   or if somebody +1’d an earlier patch set as “yes this feature looks good to me and would be useful to ops”, does that sort of “count”?19:40
mdormanbasically do we need to pay attention to later patch sets and make sure to go +1 again?19:40
*** ddieterly is now known as ddieterly[away]19:40
mriedemmdorman: the former i think19:41
mriedemi don't expect ops to be babysitting these19:41
mriedemunless they really care about seeing them land19:41
mriedemthis is really a sanity check19:41
mdormankk, right right.  makes sense.19:41
mdormansounds good19:41
*** padkrish has quit IRC19:41
mriedemthe only other thing i'd say as an fyi which wasn't on the agenda,19:42
mriedemnova-network is deprecated again19:42
mriedemthere isn't a set date for removal though19:43
mriedemwe have things we have to land in newton first19:43
mriedemdetails are in http://lists.openstack.org/pipermail/openstack-dev/2016-May/093589.html19:43
RaginBajincool19:43
mdormanyeah i had heard some rumblings about that.19:43
*** gangil has joined #openstack-meeting-419:43
mriedemthose were probably just hunger pains19:44
mdormanhehehe19:44
mdormani didn’t have anything else to bring up RaginBajin19:44
*** piet has quit IRC19:44
mdormanthanks so much for the time mriedem19:45
RaginBajinYes! Thank you.19:45
mriedemsure, np19:45
mriedemi don't have anything else19:45
RaginBajinThanks everyone for coming...19:45
*** minwang2 has joined #openstack-meeting-419:45
*** shaohe_feng has quit IRC19:45
mdormanthanks RaginBajin.  also appreciate you running the sessions in austin19:46
*** simon-AS559 has left #openstack-meeting-419:46
RaginBajinno problem.. Hopefully they were and these are useful.. Time will tell.19:46
RaginBajin#endmeeting19:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:46
openstackMeeting ended Wed May  4 19:46:32 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-05-04-18.59.html19:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-05-04-18.59.txt19:46
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-05-04-18.59.log.html19:46
*** shaohe_feng has joined #openstack-meeting-419:46
*** mriedem has left #openstack-meeting-419:47
*** schwarzm has quit IRC19:47
*** piet has joined #openstack-meeting-419:49
*** mdorman has left #openstack-meeting-419:52
*** emagana has quit IRC19:54
*** shaohe_feng has quit IRC19:56
*** emagana has joined #openstack-meeting-419:56
*** shaohe_feng has joined #openstack-meeting-419:56
*** iyamahat has quit IRC19:57
*** yamahata has quit IRC19:58
*** raj_singh has joined #openstack-meeting-419:59
*** gangil has quit IRC19:59
*** daneyon has joined #openstack-meeting-419:59
*** salv-orlando has quit IRC20:00
rockygdang!  missed the meeting!  I was too early20:01
*** emagana has quit IRC20:01
rockygor not.  But, missed it, nonetheless20:01
rockygAQnyone around for log_wg?20:01
*** emagana has joined #openstack-meeting-420:02
*** mohankumar__ has quit IRC20:02
*** ddieterly[away] is now known as ddieterly20:03
*** shaohe_feng has quit IRC20:06
*** shaohe_feng has joined #openstack-meeting-420:07
*** sdague has quit IRC20:07
*** bpokorny_ has quit IRC20:07
*** gangil has joined #openstack-meeting-420:07
*** bpokorny has joined #openstack-meeting-420:07
*** woodard_ has quit IRC20:07
*** raj_singh has left #openstack-meeting-420:07
*** piet has quit IRC20:08
*** harlowja has quit IRC20:09
*** salv-orlando has joined #openstack-meeting-420:11
*** cdelatte has quit IRC20:12
*** sdague has joined #openstack-meeting-420:14
*** shaohe_feng has quit IRC20:16
*** woodard has joined #openstack-meeting-420:16
*** woodard has quit IRC20:16
*** woodard has joined #openstack-meeting-420:17
*** shaohe_feng has joined #openstack-meeting-420:17
rbradforrockyg, I'm back20:18
*** inc0 has left #openstack-meeting-420:19
rockygWelcome back!20:19
*** iyamahat has joined #openstack-meeting-420:20
rockygShould we meet and discuss summit summary?20:20
rockygor just discuss without a meet?20:20
rockygwhatever, we've got this room20:20
rbradforwhat would you like to discuss?20:21
*** gangil has quit IRC20:21
rbradforis there a followup etherpad to https://etherpad.openstack.org/p/AUS-ops-Logging for second session?20:22
*** cbouch has quit IRC20:22
*** daneyon_ has joined #openstack-meeting-420:23
rockygAll on the one.  The working session addressed most of the items orginally put on the first session, with action items, steps forward, etc.20:23
rockygItem 7:  please review.  This *might* fix, or go a long ways towards fixing the "no valid host" with no valid information in the error message problem,20:24
*** daneyon has quit IRC20:26
rbradforif this is a nova change was it part of the nova priorities. I know they have very set blueprints (or is there still a window)20:26
*** shaohe_feng has quit IRC20:26
*** fawadkhaliq has joined #openstack-meeting-420:27
rockygItem 11:  we've got etherpads started to collect never used/frequently used debug log messages.  I think there needs to to a weekly ops summary email like the general one, with lots of links and reminders to provide info in the various collection efforts20:27
rbradforI created them.20:27
*** shaohe_feng has joined #openstack-meeting-420:27
rockygAh.  Can't remember sh*t.  Thank you.  Now I just have to ping weekly :-)20:27
*** banix has quit IRC20:28
rbradforI take it operators do not have a weekly IRC chat?  There is an OSOps one.  is the mailing list the primary communication means, openstack-operators@.  That doesn't seemto have a high volume20:29
rockygalso, Item 2:  Need better documentation on the JSON formatter ... is there a config option?  Need a chunk of documentation for the ops folks.20:29
rbradforthe json formatter already exists, but it maybe only configurable with a config log file (yet to experiment).20:30
rbradforwe discussed in oslo the ability to specify the format type (e.g. log, json, color etc) as an actual new option, so I'll follow that during this cycle20:31
rockygopenstack-ops mailing list and IRC are the primary channels.  Lots of Ops don't really have time/uesful setup for IRC20:31
*** cdelatte has joined #openstack-meeting-420:31
rockyglog config:  cool.  If a spec happens, we can advertise in ops and have them comment.20:31
*** brucet has joined #openstack-meeting-420:32
rbradforI'd have to check with harlowja on the config option, it may not require a spec.20:32
*** tonytan4ever has quit IRC20:33
rockygRequest ID stuff:  The folks implementing need mentoring.  We've got the list of reviews in the etherpad.  Cleaner ways to implement would go a long ways to get those happening.  I believe Cinder nearly choked on the proposed implementation.20:33
*** gangil has joined #openstack-meeting-420:34
rbradforit seems that is needs no oslo input, it's simply appending the specific ids to a log message.  It seemed from my question that the log messages generally already exist, the just need all the stored ids outputted20:35
*** salv-orlando has quit IRC20:35
rockygItem 5.4:  gonna leave log level at debug until immplementation is complete.20:35
rockygSo, I've a question about the deprecated syslog option... I assume, you can still get syslog format, but the documentation on the opts was not clear.20:36
rbradforwhich documentation are you referring to?20:36
rockygconfig options for oslo.log...leme find20:36
*** shaohe_feng has quit IRC20:37
*** shaohe_feng has joined #openstack-meeting-420:38
rockyghttp://docs.openstack.org/developer/oslo.log/opts.html20:38
*** yamahata has joined #openstack-meeting-420:38
rockyguse_syslog20:38
rockygOh.  The message is clearer now.  cool.20:39
rbradfornever tried the option, looking at it now.20:39
rbradforI'm suspecting RFC5424 is the format now, I'll add to my list and update help text to remove deprecation if applicable.20:40
rockygSo, the last field in the 5424 header is a structured data field.  Perfect place to put the three key pairs20:40
*** woodard has quit IRC20:40
*** woodard has joined #openstack-meeting-420:41
rbradforenabling option did not do as expected, I'll need to investigate further,20:43
rockygnot a problem.  If the fields that had been missing from the header that match syslog are now in oslo.log, (the last field, struct data and the eventID field), Ops has everything we need for requestID log implementation and for eventual error codes20:44
*** salv-orlando has joined #openstack-meeting-420:44
rockygThe important point for the requestIDs is to make sure the log message have the keyed pairs in that specific syslog header field, whatever it is called in oslo.log20:45
rbradforok, so I can see syslog messages /var/log/syslog, helps if I don't duplicate use_syslog in conf file.20:46
rbradfordo you have a ready at hand reference for 5424, or should I just google it.20:46
rockygThe eventID or whatever that field is (can't remember exact name right now) is curently unused and the ops community plans to create the error code standard, discussed and I'll get the rfc20:47
*** shaohe_feng has quit IRC20:47
*** fawadk has joined #openstack-meeting-420:47
rockyghttp://www.faqs.org/rfcs/rfc5424.html20:47
*** bpokorny has quit IRC20:47
rockyg6.3 is structured data  6.2.7 is msgid20:48
*** shaohe_feng has joined #openstack-meeting-420:48
rbradforso, is there a means to view structured information, I take it /var/log/syslog is just a text representation (that's probably configurable??)20:49
*** daneyon_ has quit IRC20:49
rockygactually, looks like structured-data is actually separate from head *and* message20:49
*** raj_singh has joined #openstack-meeting-420:49
*** fawadkhaliq has quit IRC20:50
rockygso, check out 7.2.5  It's just a list of name=values20:51
*** Sukhdev has joined #openstack-meeting-420:52
*** SimonChung has quit IRC20:52
*** SimonChung1 has joined #openstack-meeting-420:52
rockygalso, the end of 9.2  A provision is made here for locally extensible names.  The IANA will20:53
rockyg   not register, and will not control names with the at-sign (ABNF %d64)20:53
rockyg   in them.20:53
rbradforI'll need to research syslog more, all I know re syslog, is the log file, and rsyslogd20:53
*** Sukhdev has quit IRC20:54
rockygNot a problem.  I'll admit that all of what I've said is predicateded on *my* understanding of the RFC.  I may be wrong.20:54
rockygBut, Ops will work on converging on a written doc that defines the standard for error codes.  There was already a request to either put place holders in for all fields, or an option that would put the placeholders in.20:55
rockygI think Doug implemented that already.  The error codes could be done by n00bies, cheap labor (interns, HS students, etc) and/or on a "while you're in there"  basis.20:56
rockygWe'll need help using the commenting code like the opts comments to generate the docs for it, but that'20:57
rockygs a ways off.20:57
*** shaohe_feng has quit IRC20:57
*** shaohe_feng has joined #openstack-meeting-420:58
rockygBut, then again, it would be commments at the call to oslo.log, wouldn't it?  Cool!  A hacking rule!  If there's a code, there needs to be a comment!20:58
rockygBut ops don't expect to see error codes this cycle.  We do hope to have the standard specified, though20:59
*** julim has quit IRC20:59
rbradforthere was no mention of this by operators at austin so perhaps the interest is in other areas.21:00
*** julim has joined #openstack-meeting-421:01
rockygThe error codes are a long running issue for ops.  We cover it most summits.  It's at the bottom of the etherpad:  L80  I think it was mentioned elsewhere in the epad, but I know we had the "usual" discussion and I said we'd create the spec for the standard in Ops groups.21:04
rockygAlso, I try to capture all the past etherpads wrt logging at the bottom of all the new etherpads.21:04
*** woodard has quit IRC21:06
*** shaohe_feng has quit IRC21:07
*** shaohe_feng has joined #openstack-meeting-421:08
*** banix has joined #openstack-meeting-421:10
rbradforI've not read all the history for logging, rather started on an outstanding blueprint21:10
*** harlowja has joined #openstack-meeting-421:10
*** uck has joined #openstack-meeting-421:12
*** ddieterly is now known as ddieterly[away]21:12
*** hvprash_ has quit IRC21:12
rockygNot a problem.  I'll be kicking off the ops discussion for a standard and we'll see where it goes.  No need to think about it, other than about getting the 5424 header fields all in oslo.log and ops will negotiate the rest among themselves.  Then bring it to dev for discussion.21:12
rbradforrockyg, ok21:13
*** brucet has quit IRC21:13
*** mbound has quit IRC21:13
rockygoh, and good to meet you, even though it was for about 15 seconds!  I had no idea you had a not American accent!21:13
*** ddieterly[away] is now known as ddieterly21:14
rockygI think we've covered enough for today.  I'm going to do a few reviews on the related specs and work on the standard.  TTFN21:14
*** l8huang has quit IRC21:17
*** shaohe_feng has quit IRC21:18
*** shaohe_feng has joined #openstack-meeting-421:19
*** Sukhdev has joined #openstack-meeting-421:19
*** piet has joined #openstack-meeting-421:21
*** bpokorny has joined #openstack-meeting-421:22
*** rstarmer has quit IRC21:23
*** daneyon has joined #openstack-meeting-421:24
*** brucet has joined #openstack-meeting-421:25
*** ddieterly is now known as ddieterly[away]21:27
*** rtheis_ has quit IRC21:28
*** shaohe_feng has quit IRC21:28
*** bobh has quit IRC21:28
*** thorst has quit IRC21:28
*** shaohe_feng has joined #openstack-meeting-421:29
*** lakshmiS has quit IRC21:32
*** thorst has joined #openstack-meeting-421:33
*** mrhillsman has joined #openstack-meeting-421:34
*** daneyon has quit IRC21:34
*** ninag has quit IRC21:35
*** thorst has quit IRC21:37
*** shaohe_feng has quit IRC21:38
*** shaohe_feng has joined #openstack-meeting-421:39
*** shaohe_feng has quit IRC21:48
*** bauzas is now known as bauzas_off21:50
*** ddieterly[away] is now known as ddieterly21:50
*** sdague has quit IRC21:51
*** shaohe_feng has joined #openstack-meeting-421:51
*** Sukhdev has quit IRC21:52
*** Sukhdev has joined #openstack-meeting-421:52
*** raj_singh has left #openstack-meeting-421:55
*** rockyg has quit IRC21:56
*** mageshgv has quit IRC21:57
*** shaohe_feng has quit IRC21:59
*** shaohe_feng has joined #openstack-meeting-422:00
*** Sukhdev has quit IRC22:04
*** pav0 has quit IRC22:04
*** rockyg has joined #openstack-meeting-422:04
*** akijak has quit IRC22:05
*** julim has quit IRC22:06
*** ddieterly is now known as ddieterly[away]22:07
*** shaohe_feng has quit IRC22:09
*** khushbu has quit IRC22:09
*** shaohe_feng has joined #openstack-meeting-422:10
*** vishwanathj has quit IRC22:10
*** nmadhok has joined #openstack-meeting-422:19
*** shaohe_feng has quit IRC22:19
*** shaohe_feng has joined #openstack-meeting-422:20
*** sigmavirus24 is now known as sigmavirus24_awa22:21
*** thorst has joined #openstack-meeting-422:22
*** baoli has joined #openstack-meeting-422:24
*** baoli_ has joined #openstack-meeting-422:25
*** thorst has quit IRC22:26
*** piet has quit IRC22:28
*** baoli has quit IRC22:29
*** shaohe_feng has quit IRC22:29
*** shaohe_feng has joined #openstack-meeting-422:30
*** khushbu has joined #openstack-meeting-422:31
*** gangil has quit IRC22:31
*** iyamahat has quit IRC22:31
*** vishnoianil has quit IRC22:33
*** ddieterly[away] is now known as ddieterly22:34
*** ddieterly has quit IRC22:35
*** gangil has joined #openstack-meeting-422:35
*** shaohe_feng has quit IRC22:40
*** shaohe_feng has joined #openstack-meeting-422:41
*** spotz is now known as spotz_zzz22:41
*** zenoway has joined #openstack-meeting-422:45
*** zenoway has quit IRC22:46
*** mbound has joined #openstack-meeting-422:46
*** omnipresent has quit IRC22:49
*** shaohe_feng has quit IRC22:50
*** gangil has quit IRC22:50
*** harlowja has quit IRC22:52
*** shaohe_feng has joined #openstack-meeting-422:52
*** harlowja has joined #openstack-meeting-422:53
*** adduarte has quit IRC22:53
*** khushbu has quit IRC22:54
*** adduarte has joined #openstack-meeting-422:54
*** banix has quit IRC22:54
*** azbiswas has quit IRC22:55
*** vishnoianil has joined #openstack-meeting-422:58
*** shaohe_feng has quit IRC23:00
*** iyamahat has joined #openstack-meeting-423:01
*** shaohe_feng has joined #openstack-meeting-423:01
*** rbak has quit IRC23:02
*** baoli_ has quit IRC23:05
*** baoli has joined #openstack-meeting-423:08
*** ddieterly has joined #openstack-meeting-423:10
*** shaohe_feng has quit IRC23:10
*** shaohe_feng has joined #openstack-meeting-423:11
*** Sukhdev has joined #openstack-meeting-423:13
*** banix has joined #openstack-meeting-423:15
*** shaohe_feng has quit IRC23:21
*** shaohe_feng has joined #openstack-meeting-423:21
*** bapalm_ has quit IRC23:30
*** shaohe_feng has quit IRC23:31
*** gangil has joined #openstack-meeting-423:33
*** shaohe_feng has joined #openstack-meeting-423:34
*** sdake has quit IRC23:37
*** gb21 has quit IRC23:39
*** salv-orlando has quit IRC23:39
*** gb21 has joined #openstack-meeting-423:40
*** ddieterly is now known as ddieterly[away]23:40
*** shaohe_feng has quit IRC23:41
*** shaohe_feng has joined #openstack-meeting-423:42
*** ddieterly[away] is now known as ddieterly23:42
*** banix has quit IRC23:44
*** gangil has quit IRC23:44
*** pmesserl_ has quit IRC23:45
*** Swami has quit IRC23:47
*** bobh has joined #openstack-meeting-423:47
*** piet has joined #openstack-meeting-423:48
*** mbound has quit IRC23:48
*** fawadkhaliq has joined #openstack-meeting-423:50
*** amit213 has joined #openstack-meeting-423:51
*** shaohe_feng has quit IRC23:51
*** fawadk has quit IRC23:52
*** shaohe_feng has joined #openstack-meeting-423:52
*** bpokorny has quit IRC23:58

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