Wednesday, 2017-04-12

*** ntpttr has quit IRC00:00
*** ntpttr has joined #openstack-meeting-400:01
*** woodard has quit IRC00:01
*** bobh has joined #openstack-meeting-400:02
*** woodard has joined #openstack-meeting-400:05
*** ntpttr has quit IRC00:05
*** lamt has quit IRC00:06
*** ntpttr has joined #openstack-meeting-400:06
*** lamt has joined #openstack-meeting-400:09
*** thorst has quit IRC00:09
*** lamt has quit IRC00:10
*** ntpttr has quit IRC00:11
*** ntpttr has joined #openstack-meeting-400:13
*** ntpttr has quit IRC00:17
*** yfauser has joined #openstack-meeting-400:17
*** woodard has quit IRC00:18
*** ntpttr has joined #openstack-meeting-400:19
*** yfauser has quit IRC00:22
*** ntpttr has quit IRC00:25
*** ntpttr has joined #openstack-meeting-400:27
*** rfolco has joined #openstack-meeting-400:30
*** ntpttr has quit IRC00:31
*** ntpttr has joined #openstack-meeting-400:32
*** pshedimb_ has joined #openstack-meeting-400:34
*** thorst has joined #openstack-meeting-400:35
*** zhurong has joined #openstack-meeting-400:39
*** ntpttr has quit IRC00:39
*** ntpttr has joined #openstack-meeting-400:40
*** ntpttr has quit IRC00:44
*** ntpttr has joined #openstack-meeting-400:46
*** thorst has quit IRC00:46
*** ntpttr has quit IRC00:50
*** ntpttr has joined #openstack-meeting-400:53
*** tovin07_ has joined #openstack-meeting-400:56
*** ntpttr has quit IRC00:57
*** ntpttr has joined #openstack-meeting-400:59
*** cjloader_ has joined #openstack-meeting-400:59
*** ntpttr has quit IRC01:03
*** ntpttr has joined #openstack-meeting-401:05
*** cathrich_ has joined #openstack-meeting-401:08
*** s3wong has quit IRC01:08
*** ntpttr has quit IRC01:09
*** ntpttr has joined #openstack-meeting-401:11
*** ntpttr has quit IRC01:15
*** thorst has joined #openstack-meeting-401:17
*** ntpttr has joined #openstack-meeting-401:17
*** yfauser has joined #openstack-meeting-401:18
*** yfauser has quit IRC01:23
*** ntpttr has quit IRC01:24
*** thorst has quit IRC01:24
*** ntpttr has joined #openstack-meeting-401:25
*** cjloader_ has quit IRC01:27
*** cjloader_ has joined #openstack-meeting-401:27
*** woodard has joined #openstack-meeting-401:27
*** ntpttr has quit IRC01:29
*** ntpttr has joined #openstack-meeting-401:31
*** cjloader_ has quit IRC01:32
*** dixiaoli has joined #openstack-meeting-401:33
*** ntpttr has quit IRC01:35
*** SerenaFeng has joined #openstack-meeting-401:37
*** ntpttr has joined #openstack-meeting-401:37
*** woodard has quit IRC01:39
*** avishnoi has quit IRC01:40
*** ntpttr has quit IRC01:44
*** ntpttr has joined #openstack-meeting-401:45
*** Sukhdev has quit IRC01:47
*** ntpttr has quit IRC01:49
*** ntpttr has joined #openstack-meeting-401:50
*** ntpttr has quit IRC01:54
*** ntpttr has joined #openstack-meeting-401:56
*** lei-zh has joined #openstack-meeting-402:00
*** ntpttr has quit IRC02:00
*** ntpttr has joined #openstack-meeting-402:01
*** bobmel has quit IRC02:04
*** ntpttr has quit IRC02:05
*** ntpttr has joined #openstack-meeting-402:07
*** rfolco has quit IRC02:08
*** gongysh has joined #openstack-meeting-402:09
*** ntpttr has quit IRC02:11
*** ntpttr has joined #openstack-meeting-402:13
*** ntpttr has quit IRC02:20
*** ntpttr has joined #openstack-meeting-402:21
*** thorst has joined #openstack-meeting-402:21
*** Julien-zte has joined #openstack-meeting-402:26
*** yfauser has joined #openstack-meeting-402:33
*** unicell has quit IRC02:35
*** ntpttr has quit IRC02:35
*** ntpttr has joined #openstack-meeting-402:37
*** reedip_ has quit IRC02:38
*** yfauser has quit IRC02:38
*** thorst has quit IRC02:41
*** Julien-zte has quit IRC02:43
*** Julien-zte has joined #openstack-meeting-402:43
*** erikmwilson has joined #openstack-meeting-402:47
*** erikmwil_ has quit IRC02:47
*** Julien-zte has quit IRC02:47
*** Julien-zte has joined #openstack-meeting-402:47
*** reedip_ has joined #openstack-meeting-402:51
*** Kevin_Zheng has joined #openstack-meeting-402:54
*** woodard has joined #openstack-meeting-402:55
*** Julien-zte has quit IRC02:56
*** Julien-zte has joined #openstack-meeting-402:56
*** ntpttr has quit IRC03:05
*** ntpttr has joined #openstack-meeting-403:06
*** Julien-zte has quit IRC03:07
*** woodard has quit IRC03:07
*** Julien-zte has joined #openstack-meeting-403:08
*** woodard has joined #openstack-meeting-403:08
*** bobh has quit IRC03:11
*** woodard has quit IRC03:12
*** lamt has joined #openstack-meeting-403:14
*** Julien-zte has quit IRC03:17
*** lyan has joined #openstack-meeting-403:17
*** Julien-zte has joined #openstack-meeting-403:18
*** gongysh has quit IRC03:21
*** Julien-zte has quit IRC03:26
*** Julien-zte has joined #openstack-meeting-403:27
*** Julien-zte has quit IRC03:31
*** Julien-zte has joined #openstack-meeting-403:31
*** yfauser has joined #openstack-meeting-403:34
*** gongysh has joined #openstack-meeting-403:35
*** yfauser has quit IRC03:39
*** lamt has quit IRC03:43
*** iyamahat has quit IRC03:44
*** Julien-zte has quit IRC03:44
*** Julien-zte has joined #openstack-meeting-403:45
*** krtaylor has quit IRC03:45
*** yfauser has joined #openstack-meeting-403:48
*** Julien-zte has quit IRC03:51
*** Julien-zte has joined #openstack-meeting-403:52
*** yfauser has quit IRC03:53
*** baoli has quit IRC03:53
*** lamt has joined #openstack-meeting-403:56
*** dave-mccowan has joined #openstack-meeting-403:57
*** Julien-zte has quit IRC03:58
*** Julien-zte has joined #openstack-meeting-403:59
*** links has joined #openstack-meeting-404:03
*** zhurong has quit IRC04:06
*** lei-zh has quit IRC04:07
*** lamt has quit IRC04:08
*** lamt has joined #openstack-meeting-404:09
*** reedip_ has quit IRC04:13
*** Julien-zte has quit IRC04:13
*** Julien-zte has joined #openstack-meeting-404:13
*** Julien-zte has quit IRC04:14
*** Julien-zte has joined #openstack-meeting-404:14
*** dave-mccowan has quit IRC04:16
*** dave-mccowan has joined #openstack-meeting-404:16
*** trinaths has joined #openstack-meeting-404:18
*** ntpttr has quit IRC04:18
*** ntpttr has joined #openstack-meeting-404:19
*** lamt has quit IRC04:19
*** lyan has quit IRC04:21
*** ntpttr has quit IRC04:24
*** ntpttr has joined #openstack-meeting-404:25
*** iyamahat has joined #openstack-meeting-404:25
*** iyamahat has quit IRC04:26
*** ntpttr has quit IRC04:30
*** ntpttr has joined #openstack-meeting-404:31
*** zhurong has joined #openstack-meeting-404:34
*** psachin has joined #openstack-meeting-404:36
*** Julien-zte has quit IRC04:36
*** thorst has joined #openstack-meeting-404:37
*** yamamoto has quit IRC04:38
*** ntpttr has quit IRC04:38
*** ntpttr has joined #openstack-meeting-404:39
*** Julien-zte has joined #openstack-meeting-404:39
*** yamamoto has joined #openstack-meeting-404:41
*** thorst has quit IRC04:42
*** lamt has joined #openstack-meeting-404:43
*** ntpttr has quit IRC04:44
*** ntpttr has joined #openstack-meeting-404:45
*** Julien-zte has quit IRC04:47
*** Julien-zte has joined #openstack-meeting-404:49
*** yfauser has joined #openstack-meeting-404:49
*** dave-mccowan has quit IRC04:50
*** lamt has quit IRC04:52
*** Julien-zte has quit IRC04:53
*** lamt has joined #openstack-meeting-404:54
*** yfauser has quit IRC04:54
*** Julien-zte has joined #openstack-meeting-404:56
*** adisky_ has joined #openstack-meeting-404:57
*** pshedimb_ has quit IRC05:03
*** lamt has quit IRC05:08
*** woodard has joined #openstack-meeting-405:09
*** ntpttr has quit IRC05:10
*** ntpttr has joined #openstack-meeting-405:11
*** Julien-zte has quit IRC05:12
*** Julien-zte has joined #openstack-meeting-405:15
*** ntpttr has quit IRC05:16
*** ntpttr has joined #openstack-meeting-405:17
*** Sukhdev has joined #openstack-meeting-405:20
*** ntpttr has quit IRC05:24
*** ntpttr has joined #openstack-meeting-405:25
*** SerenaFeng has quit IRC05:30
*** Julien-zte has quit IRC05:30
*** Julien-zte has joined #openstack-meeting-405:31
*** pshedimb_ has joined #openstack-meeting-405:31
*** janki has joined #openstack-meeting-405:32
*** lei-zh has joined #openstack-meeting-405:36
*** ntpttr has quit IRC05:38
*** thorst has joined #openstack-meeting-405:39
*** ntpttr has joined #openstack-meeting-405:39
*** aavraham has joined #openstack-meeting-405:40
*** thorst has quit IRC05:43
*** ntpttr has quit IRC05:44
*** ntpttr has joined #openstack-meeting-405:45
*** Julien-zte has quit IRC05:46
*** zenirc369 has joined #openstack-meeting-405:46
*** Julien-zte has joined #openstack-meeting-405:47
*** lamt has joined #openstack-meeting-405:49
*** ntpttr has quit IRC05:50
*** yfauser has joined #openstack-meeting-405:50
*** ntpttr has joined #openstack-meeting-405:51
*** yfauser has quit IRC05:55
*** unicell has joined #openstack-meeting-405:55
*** SerenaFeng has joined #openstack-meeting-405:56
*** Julien-zte has quit IRC05:57
*** Julien-zte has joined #openstack-meeting-405:57
*** lamt has quit IRC05:58
*** Sukhdev has quit IRC05:58
*** ntpttr has quit IRC06:01
*** ntpttr has joined #openstack-meeting-406:01
*** yfauser has joined #openstack-meeting-406:04
*** Julien-zte has quit IRC06:06
*** Julien-zte has joined #openstack-meeting-406:07
*** yfauser has quit IRC06:09
*** kzaitsev_ws has joined #openstack-meeting-406:09
*** ntpttr has quit IRC06:10
*** ntpttr has joined #openstack-meeting-406:11
*** Julien-zte has quit IRC06:11
*** Julien-zte has joined #openstack-meeting-406:12
*** anilvenkata has joined #openstack-meeting-406:13
*** Julien-zte has quit IRC06:15
*** Julien-zte has joined #openstack-meeting-406:16
*** yfauser has joined #openstack-meeting-406:17
*** ntpttr has quit IRC06:18
*** ntpttr has joined #openstack-meeting-406:19
*** Julien-zte has quit IRC06:20
*** iyamahat has joined #openstack-meeting-406:21
*** Julien-zte has joined #openstack-meeting-406:21
*** hieulq has joined #openstack-meeting-406:24
*** hieulq has quit IRC06:26
*** iyamahat has quit IRC06:27
*** pcaruana has joined #openstack-meeting-406:30
*** Julien-zte has quit IRC06:31
*** Julien-zte has joined #openstack-meeting-406:32
*** ntpttr has quit IRC06:32
*** ntpttr has joined #openstack-meeting-406:33
*** Julien-zte has quit IRC06:34
*** Julien-zte has joined #openstack-meeting-406:34
*** SerenaFe_ has joined #openstack-meeting-406:37
*** SerenaFeng has quit IRC06:39
*** ntpttr has quit IRC06:42
*** ntpttr has joined #openstack-meeting-406:43
*** bogdando has joined #openstack-meeting-406:44
*** ntpttr has quit IRC06:48
*** pbourke has quit IRC06:49
*** belmoreira has joined #openstack-meeting-406:49
*** ntpttr has joined #openstack-meeting-406:49
*** lei-zh has quit IRC06:50
*** lei-zh has joined #openstack-meeting-406:50
*** pbourke has joined #openstack-meeting-406:51
*** yfauser has quit IRC06:52
*** yfauser has joined #openstack-meeting-406:52
*** julim_ has joined #openstack-meeting-406:54
*** Julien-zte has quit IRC06:54
*** ntpttr has quit IRC06:54
*** pcarver has quit IRC06:54
*** adreznec has quit IRC06:55
*** degorenko has quit IRC06:55
*** julim has quit IRC06:55
*** ntpttr has joined #openstack-meeting-406:55
*** dtardivel has joined #openstack-meeting-406:56
*** degorenko has joined #openstack-meeting-406:56
*** adreznec has joined #openstack-meeting-406:56
*** Julien-zte has joined #openstack-meeting-406:56
*** jamemcc has quit IRC06:59
*** ntpttr has quit IRC07:00
*** pcarver has joined #openstack-meeting-407:00
*** hieulq has joined #openstack-meeting-407:01
*** jamemcc has joined #openstack-meeting-407:01
*** ntpttr has joined #openstack-meeting-407:01
*** d0ugal has joined #openstack-meeting-407:03
*** d0ugal has quit IRC07:03
*** d0ugal has joined #openstack-meeting-407:03
*** pshedimb_ has quit IRC07:03
*** lei-zh has quit IRC07:05
*** Julien-zte has quit IRC07:06
*** cjloader_ has joined #openstack-meeting-407:07
*** Julien-zte has joined #openstack-meeting-407:07
*** ntpttr has quit IRC07:11
*** ntpttr has joined #openstack-meeting-407:11
*** ntpttr has quit IRC07:16
*** ntpttr has joined #openstack-meeting-407:17
*** Julien-zte has quit IRC07:18
*** Julien-zte has joined #openstack-meeting-407:19
*** cjloader_ has quit IRC07:23
*** Julien-zte has quit IRC07:38
*** Julien-zte has joined #openstack-meeting-407:38
*** thorst has joined #openstack-meeting-407:40
*** ntpttr has quit IRC07:40
*** ntpttr has joined #openstack-meeting-407:41
*** thorst has quit IRC07:45
*** Julien-zte has quit IRC07:45
*** Julien-zte has joined #openstack-meeting-407:45
*** ntpttr has quit IRC07:46
*** trinaths has left #openstack-meeting-407:47
*** ntpttr has joined #openstack-meeting-407:47
*** Julien-zte has quit IRC07:50
*** Julien-zte has joined #openstack-meeting-407:50
*** ntpttr has quit IRC07:52
*** ntpttr has joined #openstack-meeting-407:53
*** zenirc369 has quit IRC07:55
*** ntpttr has quit IRC07:58
*** ntpttr has joined #openstack-meeting-407:59
*** ralonsoh has joined #openstack-meeting-408:02
*** ntpttr has quit IRC08:04
*** ntpttr has joined #openstack-meeting-408:05
*** reedip has quit IRC08:07
*** Julien-zte has quit IRC08:07
*** Julien-zte has joined #openstack-meeting-408:08
*** woodard has quit IRC08:09
*** ntpttr has quit IRC08:10
*** ntpttr has joined #openstack-meeting-408:11
*** Julien-zte has quit IRC08:12
*** Julien-zte has joined #openstack-meeting-408:12
*** Julien-zte has quit IRC08:15
*** Julien-zte has joined #openstack-meeting-408:16
*** ntpttr has quit IRC08:16
*** alexchadin has joined #openstack-meeting-408:16
*** lei-zh has joined #openstack-meeting-408:16
*** ntpttr has joined #openstack-meeting-408:17
*** Julien-zte has quit IRC08:19
*** Julien-zte has joined #openstack-meeting-408:20
*** reedip has joined #openstack-meeting-408:21
*** dmellado has joined #openstack-meeting-408:23
*** aarefiev_afk is now known as aarefiev08:24
*** Julien-zte has quit IRC08:26
*** ntpttr has quit IRC08:26
*** Julien-zte has joined #openstack-meeting-408:26
*** ntpttr has joined #openstack-meeting-408:28
*** Julien-zte has quit IRC08:31
*** Julien-zte has joined #openstack-meeting-408:31
*** ntpttr has quit IRC08:32
*** ntpttr has joined #openstack-meeting-408:33
*** zenirc369 has joined #openstack-meeting-408:34
*** links has quit IRC08:35
*** trinaths1 has joined #openstack-meeting-408:37
*** ntpttr has quit IRC08:38
*** ntpttr has joined #openstack-meeting-408:40
*** thorst has joined #openstack-meeting-408:41
*** neiljerram has joined #openstack-meeting-408:42
*** Julien-zte has quit IRC08:44
*** Julien-zte has joined #openstack-meeting-408:45
*** ntpttr has quit IRC08:46
*** Julien-zte has quit IRC08:47
*** ntpttr has joined #openstack-meeting-408:48
*** Julien-zte has joined #openstack-meeting-408:48
*** Julien-zte has quit IRC08:51
*** yamahata has quit IRC08:51
*** Julien-zte has joined #openstack-meeting-408:51
*** links has joined #openstack-meeting-408:52
*** ntpttr has quit IRC08:52
*** reedip has quit IRC08:53
*** reedip has joined #openstack-meeting-408:53
*** ntpttr has joined #openstack-meeting-408:54
*** ntpttr has quit IRC08:58
*** ntpttr has joined #openstack-meeting-409:00
*** thorst has quit IRC09:00
*** Julien-zte has quit IRC09:05
*** Julien-zte has joined #openstack-meeting-409:05
*** Julien-zte has quit IRC09:07
*** Julien-zte has joined #openstack-meeting-409:08
*** jchhatbar has joined #openstack-meeting-409:14
*** janki has quit IRC09:14
*** vcn[m] has joined #openstack-meeting-409:14
*** neiljerram has quit IRC09:17
*** neiljerram has joined #openstack-meeting-409:18
*** ntpttr has quit IRC09:19
*** Julien-zte has quit IRC09:19
*** ntpttr has joined #openstack-meeting-409:20
*** Julien-zte has joined #openstack-meeting-409:20
*** links has quit IRC09:20
*** numans has quit IRC09:21
*** lkoranda has quit IRC09:23
*** Julien-zte has quit IRC09:24
*** Julien-zte has joined #openstack-meeting-409:24
*** iyamahat has joined #openstack-meeting-409:25
*** Julien-zte has quit IRC09:26
*** ntpttr has quit IRC09:26
*** Julien-zte has joined #openstack-meeting-409:26
*** trinaths1 has left #openstack-meeting-409:26
*** ntpttr has joined #openstack-meeting-409:27
*** Julien-zte has quit IRC09:28
*** Julien-zte has joined #openstack-meeting-409:28
*** iyamahat has quit IRC09:30
*** ntpttr has quit IRC09:32
*** numans has joined #openstack-meeting-409:32
*** links has joined #openstack-meeting-409:33
*** Julien-zte has quit IRC09:33
*** xingchao has joined #openstack-meeting-409:34
*** ntpttr has joined #openstack-meeting-409:34
*** ntpttr has quit IRC09:40
*** ntpttr has joined #openstack-meeting-409:41
*** neiljerram has quit IRC09:48
*** ntpttr has quit IRC09:49
*** ntpttr has joined #openstack-meeting-409:50
*** neiljerram has joined #openstack-meeting-409:51
*** SerenaFe_ has quit IRC09:51
*** sambetts|afk is now known as sambetts09:52
*** ntpttr has quit IRC09:56
*** thorst has joined #openstack-meeting-409:57
*** ntpttr has joined #openstack-meeting-409:58
*** tovin07_ has quit IRC09:59
*** thorst has quit IRC10:01
*** salmankhan has joined #openstack-meeting-410:03
*** ntpttr has quit IRC10:10
*** ntpttr has joined #openstack-meeting-410:12
*** lei-zh has quit IRC10:12
*** janki has joined #openstack-meeting-410:15
*** jchhatbar has quit IRC10:16
*** ntpttr has quit IRC10:16
*** ntpttr has joined #openstack-meeting-410:17
*** sdague has joined #openstack-meeting-410:22
*** bobmel has joined #openstack-meeting-410:25
*** bobmel has quit IRC10:25
*** ntpttr has quit IRC10:27
*** ntpttr has joined #openstack-meeting-410:28
*** bobmel has joined #openstack-meeting-410:30
*** ntpttr has quit IRC10:32
*** ntpttr has joined #openstack-meeting-410:34
*** neiljerram has quit IRC10:34
*** neiljerram has joined #openstack-meeting-410:35
*** ntpttr has quit IRC10:41
*** ntpttr has joined #openstack-meeting-410:44
*** trinaths has joined #openstack-meeting-410:44
*** ntpttr has quit IRC10:48
*** ntpttr has joined #openstack-meeting-410:50
*** ntpttr has quit IRC10:54
*** ntpttr has joined #openstack-meeting-410:55
*** ntpttr has quit IRC10:59
*** alexchadin has quit IRC11:00
*** trinaths has left #openstack-meeting-411:01
*** ntpttr has joined #openstack-meeting-411:02
*** alexchadin has joined #openstack-meeting-411:04
*** jchhatbar has joined #openstack-meeting-411:05
*** dixiaoli has quit IRC11:06
*** janki has quit IRC11:08
*** ntpttr has quit IRC11:10
*** ntpttr has joined #openstack-meeting-411:12
*** rfolco has joined #openstack-meeting-411:15
*** ntpttr has quit IRC11:18
*** ntpttr has joined #openstack-meeting-411:20
*** zhurong has quit IRC11:26
*** ntpttr has quit IRC11:26
*** rwallner has joined #openstack-meeting-411:26
*** ntpttr has joined #openstack-meeting-411:28
*** rwallner has quit IRC11:30
*** ntpttr has quit IRC11:32
*** ntpttr has joined #openstack-meeting-411:34
*** rwallner has joined #openstack-meeting-411:34
*** salmankhan has quit IRC11:36
*** ntpttr has quit IRC11:40
*** thorst has joined #openstack-meeting-411:41
*** ntpttr has joined #openstack-meeting-411:42
*** ntpttr has quit IRC11:46
*** ntpttr has joined #openstack-meeting-411:48
*** baoli has joined #openstack-meeting-411:49
*** psachin has quit IRC11:51
*** ntpttr has quit IRC11:55
*** ntpttr has joined #openstack-meeting-411:57
*** ntpttr has quit IRC12:04
*** klamath has joined #openstack-meeting-412:04
*** klamath has quit IRC12:04
*** klamath has joined #openstack-meeting-412:05
*** ntpttr has joined #openstack-meeting-412:06
*** psachin has joined #openstack-meeting-412:08
*** ntpttr has quit IRC12:10
*** woodard has joined #openstack-meeting-412:10
*** krtaylor has joined #openstack-meeting-412:11
*** ntpttr has joined #openstack-meeting-412:11
*** daidv has joined #openstack-meeting-412:11
*** woodard has quit IRC12:14
*** woodard has joined #openstack-meeting-412:15
*** gongysh has quit IRC12:15
*** gongysh has joined #openstack-meeting-412:17
*** ntpttr has quit IRC12:21
*** ntpttr has joined #openstack-meeting-412:24
*** daidv has quit IRC12:26
*** cathrich_ has quit IRC12:27
*** ntpttr has quit IRC12:28
*** ntpttr has joined #openstack-meeting-412:29
*** ntpttr has quit IRC12:33
*** ntpttr has joined #openstack-meeting-412:36
*** markvoelker has joined #openstack-meeting-412:37
*** baoli has quit IRC12:39
*** ntpttr has quit IRC12:40
*** ntpttr has joined #openstack-meeting-412:41
*** lamt has joined #openstack-meeting-412:47
*** lamt has quit IRC12:48
*** ntpttr has quit IRC12:51
*** ntpttr has joined #openstack-meeting-412:53
*** mbruzek has joined #openstack-meeting-412:53
*** lamt has joined #openstack-meeting-412:57
*** ntpttr has quit IRC12:57
*** mriedem has joined #openstack-meeting-412:57
*** zenirc369 has quit IRC12:58
*** haleyb has joined #openstack-meeting-412:59
*** xingchao has quit IRC12:59
*** ntpttr has joined #openstack-meeting-412:59
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Apr 12 13:00:02 2017 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
mriedemo/13:00
alex_xuwho is here today>13:00
gmanno/13:00
alex_xus/>/?/13:00
macszO/13:00
sdagueo/13:01
johnthetubaguyo/13:01
alex_xulet us start the meeting13:01
alex_xugmann: thanks for running the meeting last week first13:01
alex_xu#topic priorities13:01
*** openstack changes topic to "priorities (Meeting topic: nova api)"13:01
*** baoli has joined #openstack-meeting-413:02
alex_xu#link https://review.openstack.org/43303713:02
mriedemi'll go through ^ today, i plan on reviewing the remaining specs for most of the day13:02
alex_xunot sure whether everyone understand the spec about remove scope check now :)13:03
alex_xumriedem: cool13:03
*** trinaths has joined #openstack-meeting-413:03
mriedemi haven't looked at it since the updates were made13:03
mriedembut i never understood the original problem :)13:03
*** lyan has joined #openstack-meeting-413:03
alex_xuhah13:03
alex_xuthe part of separate scope check is hard13:04
alex_xubut I think I got the point13:04
alex_xujohnthetubaguy: anything more worth to talk? or just wait for review?13:05
johnthetubaguyI think just waiting for the review really13:05
alex_xuok, cool13:05
*** ntpttr has quit IRC13:05
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/policy-docs13:06
alex_xuthe doc one is very progress13:06
johnthetubaguythe follow on spec I am not really targeting any more13:06
*** pmesserli has joined #openstack-meeting-413:06
alex_xujohnthetubaguy: yea, agree13:06
*** psachin has quit IRC13:06
alex_xuI think that is all for priorities, let us go to the open13:07
alex_xu#topic open13:07
*** openstack changes topic to "open (Meeting topic: nova api)"13:07
alex_xuwe have a lot of deprecation API proposal now :)13:07
johnthetubaguyso I have a spec that maybe should have been a priority13:07
*** lamt has quit IRC13:07
johnthetubaguybut its really later13:07
johnthetubaguys/later/late/13:08
johnthetubaguylets do that after deprecations13:08
*** ntpttr has joined #openstack-meeting-413:08
alex_xujohnthetubaguy: ok13:08
alex_xu#link https://review.openstack.org/38426113:08
alex_xusdague: that needs one more +2 ^13:08
alex_xu#link https://review.openstack.org/45589613:08
alex_xuand one more for deprecated os-hosts API13:09
mriedemalso,13:09
mriedemsort of,13:09
sdagueyeh, I'll take a look post meeting13:09
mriedemmacsz updated https://review.openstack.org/#/c/454332/ to include os-cloudpipe13:09
mriedemafter a discussion with sdague and i about that one,13:09
alex_xusdague: thanks13:09
mriedemto remove nova-cert, which os-cloudpipe depends on13:09
mriedemso it makes sense to also just deal with os-cloudpipe in that same change13:09
alex_xu+1 for os-cloudpipe13:10
mriedemas in +1 you love it? :)13:10
alex_xualso +1 for nova-cert :)13:10
gmanndeprecated  os-cloudpipe right ?13:11
gmann*deprecating13:11
*** Julien-zte has joined #openstack-meeting-413:11
alex_xuwait, mriedem you mean deprecate the os-cloudpipe API?13:11
johnthetubaguyah, yeah, killing htem both makes sense13:11
mriedemalex_xu: actual removal13:11
johnthetubaguyalex_xu: +1 its nova-network only13:11
johnthetubaguyoh, right my mistake13:12
mriedemand it relies on nova-cert13:12
johnthetubaguythis is removal13:12
mriedemnova-cert is going to be removed13:12
*** cathrichardson has joined #openstack-meeting-413:12
mriedemos-certificates will fail13:12
mriedemos-cloudpipe uses nova-cert, so it's going to also be busted, so we might as well remove13:12
mriedemit's kind of an odd situation13:12
johnthetubaguyhmm, thats probably the right call13:12
johnthetubaguyI feel bad not being louder about the cloud-pipe deprecation, but its deprecated as part of nova-network anyways13:13
gmannyea it deprecated #link https://developer.openstack.org/api-ref/compute/#cloudpipe-os-cloudpipe-deprecated13:13
johnthetubaguyyeah, my bad13:14
mriedemjohnthetubaguy: i feel the same13:14
mriedemwe never formally deprecated with a microversion13:14
mriedembut it's going to be busted anyway13:14
mriedemhell, it's not tested, so it might already be broken13:14
gmanntrue13:14
*** ntpttr has quit IRC13:14
johnthetubaguynot sure I ever got that thing working 4/5 years go13:14
alex_xudo we need a microversion to adverties that?13:14
johnthetubaguyalex_xu: so we are using a different return code to 40413:15
johnthetubaguynormally we would have to raise the min_version of the API13:15
*** ntpttr has joined #openstack-meeting-413:15
alex_xuadvert a remove13:15
mriedemi'd just use the same thing for os-certificates, which is a 40113:15
mriedem*41013:15
mriedemin that spec13:15
johnthetubaguyyeah13:16
*** lamt has joined #openstack-meeting-413:16
mriedemmacsz: might want a slight tweek in the spec there13:16
mriedemi left a comment13:16
johnthetubaguyalex_xu: its a good point though, we could signal the removal, I am curious on sdague's thoughts on that, I remember he talked me away from that ledge before13:16
mriedemsdague was pro removal when we talked about this the other day, which resulted in the spec update13:16
* mriedem assumes power of attorney for sean13:17
*** links has quit IRC13:17
sdagueyeh, I'm pro removal13:17
alex_xu:)13:17
johnthetubaguybut what about a signal for the removal?13:17
johnthetubaguyso you can detect a cloud that has it removed13:17
sdaguejohnthetubaguy: other than the 410?13:17
johnthetubaguyI guess we have enough API changes that we will get a signal soon enough13:17
johnthetubaguysdague: yeah13:18
johnthetubaguysdague: like if higher than 2.42 it must be removed13:18
sdaguesure, if you want to also mv signal, that's probably fine13:18
sdagueit's probably easier to explain in the API docs as well13:18
johnthetubaguyalthough the next API change we land after the removal will give us a signal for free I guess13:19
mriedemso we're doing 404 for deprecation or 410 for cloudpipe is gone?13:19
johnthetubaguy41013:19
mriedemand that's on the new microversion, or all?13:19
johnthetubaguynot sure?13:20
alex_xunew microversion for cloudpiple and os-certificates return 410?13:20
johnthetubaguythat works for me13:21
mriedemso i think for os-certs we are doing 410 for all microversions13:21
mriedembecause the backing nova-cert service is going to be gone13:21
johnthetubaguyalthough after that microversion, we maybe want to return 404, but return 410 before that microversion13:21
*** Julien-zte has quit IRC13:21
mriedemjohnthetubaguy: you're confusing me13:21
alex_xuyes, new microversion for 410 in all version13:21
johnthetubaguyso if move min about that microversion, we would delete the handler code?13:21
gmannhummm13:22
johnthetubaguymriedem: confusing my self too13:22
mriedemalex_xu: you're also confusing me13:22
gmanncurrently is it 410?13:22
johnthetubaguysay its 2.4213:22
alex_xu:)13:22
johnthetubaguyif you request 2.41 we return 40413:22
sdaguejohnthetubaguy: it has to be true for all versions13:22
mriedem2.42 is the max in ocata13:22
sdagueotherwise we can't delete the service13:22
mriedemos-certs is going to return 410 for ALL versions13:22
johnthetubaguyhang on, I screwed up that text13:22
mriedemthere is no new microversion13:22
mriedemthat's why it's not in the spec13:22
johnthetubaguymriedem: I think I just changed my mind13:23
johnthetubaguyso we remove it, we return 41013:23
johnthetubaguythats fine13:23
johnthetubaguynow we could signal that with a new microversion13:23
mriedemjohnthetubaguy: so you agree with my statement?13:23
gmannand with 410 in all version we can basically delete the code right13:23
johnthetubaguyso you know if its removed13:23
johnthetubaguy... but if we did that...13:23
mriedemjohnthetubaguy: but a new microversion implies 2.1 would work13:23
mriedemand it won't13:23
johnthetubaguywe could return 404 after that microversion13:24
mriedemthe 410 tells you it's gone13:24
johnthetubaguysuch that if we raised the minimum ever, we could drop the code that returns 41013:24
*** Julien-zte has joined #openstack-meeting-413:24
mriedemi think we're splitting hairs here,13:24
johnthetubaguymriedem: right 410 is needed for below where we remove it from the API13:24
mriedemi don't see the need for a new microversion of this13:24
johnthetubaguyso I was thinking, say is 2.50 we remove it in13:24
alex_xuwe needn't return 404 after that microversion, when min verison raise, it will be 404 in the future13:24
johnthetubaguy2.42 return 41013:24
johnthetubaguy2.50 returns 40413:24
johnthetubaguyits just an idea, so we can delete more code later13:25
mriedemas alex_xu said, if we raise and it's gone, then it's just gone and it's 40413:25
mriedemi'm more interested in what we're saying for os-cloudpipe,13:25
mriedemeven though we just merged the spec13:25
johnthetubaguyOK13:25
alex_xuah I think I got johnthetubaguy point13:26
gmannso we maintain some code to return 410 basically13:26
*** mattmceuen has joined #openstack-meeting-413:26
gmannand if we completely remove its going to be 40413:27
mriedemyeah we're already doing that. when we originally talked about this spec, we suggested just deleting it which would be automatic 40413:27
johnthetubaguygmann: yep, thats my thinking13:27
gmannjohnthetubaguy: that's your point right?13:27
*** psachin has joined #openstack-meeting-413:27
gmannyea13:27
*** cathrichardson has left #openstack-meeting-413:27
mriedemso you're saying any microversion between 2.1 and 2.43+ would be a 410?13:27
johnthetubaguymriedem: thats my suggestion, yes13:28
mriedem2.43 is the first one for pike13:28
johnthetubaguywell, which ever version we do the change in13:28
*** neiljerram has quit IRC13:28
sdagueso, honestly no, please no13:28
johnthetubaguyoh way, that the wrong way around13:28
mriedemi don't see the point13:28
mriedemwith the microversion that is13:28
sdagueif we want to use 410 to signal that a thing was once here, and now will never be again13:28
johnthetubaguy2.1 to 2.43 is 410, its 404 after 2.4313:28
sdaguethat's fine13:28
mriedemwe return 410 for all microversions for os-certs, if you ever delete the code, then we get 404 for free13:28
sdaguebut just use it forever with a stub13:29
johnthetubaguysdague: OK, I was just trying to avoid the stub longer term, but thats overkill maybe13:29
sdaguebut using 410 and changing to 404 is just more pain13:29
sdaguejohnthetubaguy: the stub is going to be pretty small13:29
johnthetubaguyit was more for the users, its logically no longer part of the API after a certain point13:30
alex_xuwhy we use 410, that is for another signal?13:30
johnthetubaguyso 410 is to tell people the thing they thought was there is gone13:30
johnthetubaguyif we did 404 they might think they typoed the URL13:30
alex_xunew microversion is also for that13:30
*** neiljerram has joined #openstack-meeting-413:30
gmannsdague: with 410 we do need ti maintain api doc etc saying its gone13:30
johnthetubaguyalex_xu: 410 is for all old microversions too13:30
johnthetubaguy... so lets back up13:31
johnthetubaguydrop the microversion signal and drop the 404 nonsesne13:31
johnthetubaguywe can do the 410 thing now13:31
johnthetubaguyand we can decide about 404 later, if the 410 turns out to be a pain13:31
mriedemyes, that was the plan13:31
mriedemplan = "we can do the 410 thing now"13:31
johnthetubaguymriedem: yeah +113:31
mriedemso we just talked in a big circle right?13:31
sdagueyes13:32
johnthetubaguyyeah13:32
johnthetubaguymy bad13:32
alex_xuI think the user should check the API doc about what happened in the new microversion first, not raise the request version in his client code first13:32
mriedemok, that's fine13:32
mriedemgood to be on the same page13:32
mriedemso,13:32
mriedemgetting back to os-cloudpipe,13:32
*** lkoranda has joined #openstack-meeting-413:32
mriedemwere we going to do the same with 410 for all microversions?13:32
mriedemor deprecate with a 404 in a new microversion?13:32
johnthetubaguyalex_xu: this is about the user that has their old code suddenly starting to fail, or just doesn't read the docs13:32
johnthetubaguyI think lets do 410 for all microversions, for now13:32
johnthetubaguythats simplest13:33
alex_xujohnthetubaguy: ah, right13:33
mriedemjohnthetubaguy: their old code would start failing anyway,13:33
mriedembecause nova-cert is gone13:33
johnthetubaguythis is just describing why its failing13:33
alex_xuok, I got it, +1 for 41013:33
mriedemjohnthetubaguy: "I think lets do 410 for all microversions, for now" for os-cloudpipe too you mean?13:33
johnthetubaguyyou didn't get the URL wrong, the API is dead13:33
johnthetubaguymriedem: yes13:33
gmann yes for 410 for all13:33
mriedemjohnthetubaguy: ok yeah i agree13:33
mriedemwhew :)13:33
sdagueyeh, this seems like it should be consistent13:33
johnthetubaguysdague: +113:33
mriedemmacsz: please update the spec to also point out that we'll return 410 for all microversions for os-cloudpipe like with os-certificates13:34
johnthetubaguythey are both in the same situation13:34
johnthetubaguythat might be my action now :(13:34
mriedemmacsz: maybe also say something in there that we aren't going to be adding a new microversion for this13:34
mriedemto be clear13:34
alex_xunew microversion is for someone begin take care that in their client code?13:34
mriedemor johnthetubaguy :)13:34
macszmriedem: will do, sorry for not being too talkative, driving to the office13:34
mriedemnp13:35
mriedemprobably shouldn't be in an irc meeting while driving...13:35
* johnthetubaguy assumes macsz has an IRC to speech app13:36
sdagueanyway...13:36
macszstuck at railroad crossing atm :P13:36
mriedemalex_xu: what's next?13:37
alex_xuok...13:37
*** markvoelker has quit IRC13:37
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/api-no-more-extensions-pike13:37
alex_xuI will update the patches soon13:38
alex_xu#link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114736.html13:38
alex_xu^ and I have note for remove some URL mapping, but no response, I guess people agree that13:38
alex_xuI think people notice that in the commit message also, just double check13:38
mriedemi dont think i understood it13:38
gmannagree. i think you mentioned in patch also13:38
mriedemi don't know what the atom publish protocol is13:39
johnthetubaguymriedem: +1 I think thats where I was lost13:39
mriedemPOST /servers.:(format) GET /servers/detail.:(format)13:39
*** jchhatbar has quit IRC13:39
johnthetubaguywhats the ":(format)" bit really look like?13:39
mriedemi have to assume it's ok to remove support for that13:39
alex_xuok, the double check is right :)13:39
mriedemwe have never tested it13:39
alex_xuPOST /servers.json13:39
alex_xuPOST /servers.xml13:39
alex_xubut we didn't have xml now13:40
johnthetubaguyoh...13:40
johnthetubaguybummer13:40
alex_xuand we have strange 'GET /servers/:(id)/edit'13:40
*** markvoelker has joined #openstack-meeting-413:40
*** Julien-zte has quit IRC13:40
alex_xuand '/servers/:(id)/tags/new' make the tag name as 'new' doesn't work, as I remember13:41
alex_xu#link https://bugs.launchpad.net/nova/+bug/161547513:41
openstackLaunchpad bug 1615475 in OpenStack Compute (nova) "Unable to fetch the details of a keypair with name "new"." [Medium,Confirmed] - Assigned to manoj6030 (manoj2002)13:41
alex_xu^ ah, that bug is for keypair with name 'new'13:41
*** Julien-zte has joined #openstack-meeting-413:42
mriedemok i'll ack the removal in the ML13:42
alex_xumriedem: thanks13:42
mriedemdone13:43
mriedemyw13:43
alex_xumriedem: cool13:43
alex_xuthat is all I have, anything more?13:43
*** mriedem has quit IRC13:44
*** woodard has quit IRC13:44
*** mriedem has joined #openstack-meeting-413:44
johnthetubaguyoh, I had a thing13:44
johnthetubaguywhat was it...13:44
alex_xujohnthetubaguy: ah, right, sorry13:45
mriedemsomething something policy13:45
johnthetubaguy#link https://review.openstack.org/45479213:45
johnthetubaguy#link https://review.openstack.org/45562913:45
johnthetubaguyso I think tonyb has been swamped, so I started the capabiltiies discussion back up13:45
*** kzaitsev_ws has quit IRC13:45
*** Julien-zte has quit IRC13:45
mriedemon https://review.openstack.org/#/c/455629/ i had expected to see amrith chiming in there13:45
*** bogdando has quit IRC13:45
johnthetubaguywe kinda agreed on progress at the PTG, but it stalled13:45
sdaguejohnthetubaguy: is there time set asside in boston for this?13:45
mriedembut amrith has been busy13:45
johnthetubaguysdague: unsure, I know the keystone PTL has lost travel funding13:46
*** Julien-zte has joined #openstack-meeting-413:46
sdaguejohnthetubaguy: I thought at the PTG we just said we'd do 3 things for horizon?13:46
johnthetubaguysdague: thats the spec13:46
mriedemjohnthetubaguy: see my email to the ML from yesterday about discovering if we can do volume extend - that would probably be a decent test for the capabilities one,13:46
*** bogdando has joined #openstack-meeting-413:46
mriedemor live resize since that was the original thing we said we'd hold up for capabilities13:46
johnthetubaguysdague: the 454792 one13:46
*** zhurong has joined #openstack-meeting-413:47
sdaguejohnthetubaguy: ok... so I was reading this the other day - http://blog.novatec-gmbh.de/the-problems-with-swagger/13:47
sdagueand kind of wondered why we aren't doing this with hypermedia13:47
*** mattmceuen has quit IRC13:48
*** Julien-zte has quit IRC13:48
johnthetubaguyI have no idea what hypermedia is I guess, I should do more reading around that13:48
sdaguebascially using the links: [] more effectively13:48
mriedemit certainly sounds exciting13:48
sdaguethe operations that a thing supports are listed as links13:48
sdaguewith rel="$action_name"13:48
mriedemdidn't mordred tell us yesterday that he hated links?13:48
johnthetubaguysdague: oh, right, I see now. back to the you only need the base URL, no URLs should be built thingy13:48
sdaguemriedem: he did13:49
mriedemhmm, also,13:49
johnthetubaguymriedem: I think he hates them, because they get broken too easily13:49
mriedemhow do we do an action link when our actions are the same link, with a different request body?13:49
*** Julien-zte has joined #openstack-meeting-413:49
*** lamt has quit IRC13:49
mriedemrather than POST /servers/{id}/createImage13:49
mriedemor whatever13:49
sdaguemriedem: rel="reboot", href="...."13:49
mriedemoh, hrm13:50
johnthetubaguyoh...13:50
sdaguethe rel field is effectively the capability13:50
mriedembut you still need to know the body right?13:50
*** kzaitsev_ws has joined #openstack-meeting-413:50
sdaguemriedem: sure13:50
mriedemso does the link help you?13:50
mriedembesides just telling you the capabilities story for that server13:50
sdaguegiven the actions post interface, it's definitely a bit minimal13:51
sdaguebut... I think the real question is establishing the next pattern of interfaces13:51
sdaguebecause if we had less silly actions interface, it would go a longer way13:51
mriedemjohnthetubaguy: so for https://review.openstack.org/#/c/454792/ do we actually plan on sorting this out in 24 hours?13:51
mriedemjohnthetubaguy: or do we make it a backlog spec?13:51
johnthetubaguywell, depends if we think that represents what we agreed at the PTG or not13:52
alex_xusdague: will people construct the url request by the links in the client? or the links just for human reading?13:52
mriedemper my ML thread from yesterday, i feel like things could be nicer if we just stored capabilities for a compute node in the db for the api to lookup for fast fails, but it seems we've rejected that in the past13:52
sdaguemriedem: I really want fast fail13:53
*** lamt has joined #openstack-meeting-413:53
sdagueI'm also not sure why we wouldn't propagate them up to the db there13:53
mriedemsdague: well i think there is an easy way to do that, but it might be a temporary hack13:53
mriedemwhich db? api db?13:53
mriedemcompute_nodes are in the cell db13:53
sdagueah13:53
johnthetubaguyI was assuming it goes in the instance record, as they are per instance, not per compute node13:54
mriedemthe specific case is this volume extend thing,13:54
*** amotoki has joined #openstack-meeting-413:54
*** Julien-zte has quit IRC13:54
mriedemthe compute can either support volume extend or it can't,13:54
mriedemwe have the compute driver capabilities dict already13:54
sdagueso, I'm going to be honest, I think that with limits and policy changes in flight, capabilities seems like too much churn13:54
johnthetubaguyso for the crazier stuff, it gets affected by virt emulator choices13:54
mriedemi was thinking it'd be easy in the api to get the compute that the instance is running on, check it's capabilities dict to see if it can do volume extend, and if not just fail fast13:54
*** Julien-zte has joined #openstack-meeting-413:55
mriedemjohnthetubaguy: right there are wrinkles, i'm just thinking bare bones, like is there 0% chance this works13:55
mriedemif there is 0%, the api fails fast13:55
mriedemsdague: that's why i asked if this was backlog13:55
johnthetubaguymriedem: I am agreeing with you, I was just doing that in the instance record13:55
johnthetubaguyyeah, I think at this point it should move to queens or backlog13:56
*** erikmwilson has quit IRC13:56
johnthetubaguythere are too many questions here13:56
alex_xureminds that 4 mins left13:56
*** erikmwil_ has joined #openstack-meeting-413:56
mriedema good goal for pike might just be getting general agreement on the spec,13:56
mriedemwith no code13:56
mriedemi have a feeling though,13:56
johnthetubaguyyeah, that would be a good goal13:56
mriedemat some point with the capabilities stuff we're just going to have to do what we think works for nova - even though it sucks to say that13:56
mriedembut we've been talking about this since at least mitaka13:57
mriedemi think at the ptg, ironic said they would try some things and report back if they worked13:57
mriedemor if people hated them13:57
*** ntpttr has quit IRC13:57
mriedemalthough i might be thinking about the min microversion bump thing13:57
mriedemironic is going to trailblaze everything13:57
johnthetubaguyyeah, thats were I thought we were with this too13:57
sdagueso... related - some actual API proposal for the limits in keystone https://review.openstack.org/#/c/455709/13:57
johnthetubaguysdague: sweet13:58
sdagueso now we get people to hate on it there, but I need some feedback to start evolving it to an agreed thing13:58
johnthetubaguyso the middleware and policy discussion just highlighed to me how out of sync we all are with the delgation story13:58
mriedemok, remind me after the spec freeze if i haven't looked13:58
sdaguejohnthetubaguy: I also still don't really understand the volume type limit problem, so if you've got that in your head, that would be great13:59
mriedem1 minute13:59
johnthetubaguysdague: think per flavor limits, its basically the same thing, but we should talk about that13:59
mriedemi can feel alex_xu stressing13:59
alex_xuyea13:59
* johnthetubaguy nods13:59
johnthetubaguylets call it13:59
sdaguejohnthetubaguy: can we get on a hangout in a couple of minutes and talk about that13:59
alex_xuI can't read the English and watch the clock sametime13:59
mriedemhaha13:59
*** zhurong_ has joined #openstack-meeting-414:00
alex_xu#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Apr 12 14:00:07 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-04-12-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-04-12-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-04-12-13.00.log.html14:00
*** ntpttr has joined #openstack-meeting-414:00
*** mriedem has left #openstack-meeting-414:00
*** zhurong has quit IRC14:01
*** cjloader_ has joined #openstack-meeting-414:02
*** alexchadin has quit IRC14:02
*** bobh has joined #openstack-meeting-414:04
*** ntpttr has quit IRC14:04
*** janki has joined #openstack-meeting-414:05
*** ntpttr has joined #openstack-meeting-414:06
*** aavraham has left #openstack-meeting-414:07
*** bobh has quit IRC14:08
*** bobh has joined #openstack-meeting-414:08
*** bogdando has quit IRC14:12
*** bogdando has joined #openstack-meeting-414:12
*** ntpttr has quit IRC14:12
*** ntpttr has joined #openstack-meeting-414:14
*** david-lyle has quit IRC14:15
*** bogdando has quit IRC14:16
*** bogdando has joined #openstack-meeting-414:16
*** bogdando has quit IRC14:18
*** premsankar has joined #openstack-meeting-414:18
*** ntpttr has quit IRC14:18
*** cjloader_ has quit IRC14:19
*** cjloader_ has joined #openstack-meeting-414:19
*** ntpttr has joined #openstack-meeting-414:20
*** lamt has quit IRC14:21
*** cjloader_ has quit IRC14:24
*** Julien-zte has quit IRC14:27
*** egonzalez has joined #openstack-meeting-414:27
*** rwallner has quit IRC14:28
*** rwallner has joined #openstack-meeting-414:28
*** ntpttr has quit IRC14:29
*** rwallner has quit IRC14:29
*** iyamahat has joined #openstack-meeting-414:29
*** ntpttr has joined #openstack-meeting-414:30
*** Julien-zte has joined #openstack-meeting-414:30
*** links has joined #openstack-meeting-414:33
*** links has quit IRC14:36
*** ntpttr has quit IRC14:36
*** ntpttr has joined #openstack-meeting-414:38
*** lamt has joined #openstack-meeting-414:42
*** ntpttr has quit IRC14:45
*** yamahata has joined #openstack-meeting-414:45
*** sbezverk has joined #openstack-meeting-414:45
*** ntpttr has joined #openstack-meeting-414:46
*** Julien-zte has quit IRC14:46
*** Julien-zte has joined #openstack-meeting-414:47
*** wxy| has joined #openstack-meeting-414:47
*** janki has quit IRC14:50
*** hongbin has joined #openstack-meeting-414:50
*** ntpttr has quit IRC14:50
*** Julien-zte has quit IRC14:51
*** ntpttr has joined #openstack-meeting-414:52
*** Julien-zte has joined #openstack-meeting-414:53
*** rwallner has joined #openstack-meeting-414:53
*** Julien-zte has quit IRC14:55
*** ntpttr__ has joined #openstack-meeting-414:55
*** ntpttr has quit IRC14:56
*** Julien-zte has joined #openstack-meeting-414:56
*** zhurong_ has quit IRC14:57
*** ntpttr has joined #openstack-meeting-414:58
*** pshedimb_ has joined #openstack-meeting-414:58
*** bklei has joined #openstack-meeting-414:59
*** Julien-zte has quit IRC15:00
*** xingchao has joined #openstack-meeting-415:01
*** marst has joined #openstack-meeting-415:01
*** ntpttr__ is now known as ntpttr_laptop15:01
*** Julien-zte has joined #openstack-meeting-415:01
*** ntpttr has quit IRC15:02
*** ntpttr has joined #openstack-meeting-415:04
*** Julien-zte has quit IRC15:06
*** Julien-zte has joined #openstack-meeting-415:07
*** ntpttr__ has joined #openstack-meeting-415:07
*** ntpttr_laptop has quit IRC15:08
*** ntpttr has quit IRC15:08
*** Julien-zte has quit IRC15:10
*** ntpttr has joined #openstack-meeting-415:10
*** cjloader_ has joined #openstack-meeting-415:11
*** Julien-zte has joined #openstack-meeting-415:12
*** ntpttr has quit IRC15:14
*** ntpttr has joined #openstack-meeting-415:16
*** lamt has quit IRC15:20
*** ntpttr has quit IRC15:22
*** ntpttr has joined #openstack-meeting-415:24
*** bklei has quit IRC15:24
*** lamt has joined #openstack-meeting-415:27
*** Julien-zte has quit IRC15:28
*** ntpttr has quit IRC15:28
*** Sukhdev has joined #openstack-meeting-415:28
*** Julien-zte has joined #openstack-meeting-415:28
*** baoli has quit IRC15:28
*** baoli has joined #openstack-meeting-415:29
*** ntpttr has joined #openstack-meeting-415:30
*** d0ugal has quit IRC15:30
*** d0ugal has joined #openstack-meeting-415:30
*** d0ugal has quit IRC15:30
*** d0ugal has joined #openstack-meeting-415:30
*** d0ugal has quit IRC15:31
*** d0ugal has joined #openstack-meeting-415:31
*** d0ugal has quit IRC15:31
*** d0ugal has joined #openstack-meeting-415:31
*** belmoreira has quit IRC15:32
*** Julien-zte has quit IRC15:33
*** ntpttr has quit IRC15:34
*** Julien-zte has joined #openstack-meeting-415:34
*** ntpttr has joined #openstack-meeting-415:36
*** Julien-zte has quit IRC15:37
*** cathrichardson has joined #openstack-meeting-415:37
*** Julien-zte has joined #openstack-meeting-415:39
*** trinaths has left #openstack-meeting-415:40
*** ntpttr has quit IRC15:40
*** Rockyg has joined #openstack-meeting-415:42
*** ntpttr has joined #openstack-meeting-415:42
*** anilvenkata has quit IRC15:43
*** caboucha has joined #openstack-meeting-415:45
*** ntpttr has quit IRC15:46
*** ntpttr has joined #openstack-meeting-415:48
*** chyka has joined #openstack-meeting-415:48
*** Julien-zte has quit IRC15:49
*** reedip_ has joined #openstack-meeting-415:49
*** Julien-zte has joined #openstack-meeting-415:51
*** woodard has joined #openstack-meeting-415:51
*** duonghq has joined #openstack-meeting-415:52
*** ntpttr has quit IRC15:52
*** daidv has joined #openstack-meeting-415:52
*** lamt has quit IRC15:53
*** ntpttr has joined #openstack-meeting-415:53
*** Sukhdev_ has joined #openstack-meeting-415:55
*** kzaitsev_ws has quit IRC15:55
*** mnaser has joined #openstack-meeting-415:56
*** ntpttr has quit IRC15:58
*** rbak_ has joined #openstack-meeting-415:58
*** hrw has joined #openstack-meeting-415:58
hrwo/15:58
spsurya_hrw: will get start noti15:59
inc0#startmeeting kolla15:59
openstackMeeting started Wed Apr 12 15:59:20 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
*** openstack changes topic to " (Meeting topic: kolla)"15:59
openstackThe meeting name has been set to 'kolla'15:59
*** ralonsoh_ has joined #openstack-meeting-415:59
*** mandre has joined #openstack-meeting-415:59
inc0#topic w00t for Kolla15:59
*** openstack changes topic to "w00t for Kolla (Meeting topic: kolla)"15:59
berendtO/15:59
duonghqo/15:59
inc0o/15:59
spsurya_woot15:59
egonzalezw00t o/15:59
sdakeo/16:00
*** vhosakot has joined #openstack-meeting-416:00
spsurya_oOo/16:00
daidvo/16:00
*** ntpttr has joined #openstack-meeting-416:00
sbezverko/16:00
vhosakoto/16:00
*** tovin07 has joined #openstack-meeting-416:00
*** rbak has quit IRC16:00
*** Julien-zte has quit IRC16:01
*** jascott1_ has joined #openstack-meeting-416:01
mandreo/16:01
kfox1111o/16:01
jascott1_o/16:01
Jeffrey4lo/16:01
*** ralonsoh has quit IRC16:01
mnasero/16:01
inc0since we have busy schedule I'll move on16:01
inc0#topic announcements16:02
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:02
inc0I have one "help your project" request16:02
*** Julien-zte has joined #openstack-meeting-416:02
inc0we'll hold hands on workshop for deploying kolla-ansible in Boston16:02
inc0and we'll need mentors in room to help workshopers deal with issues16:03
*** cathrichardson has quit IRC16:03
inc0so if anyone is interested in helping, please let me know after meeting16:03
sdakeinc0 who is leading?16:03
inc0I do16:03
*** marst_ has joined #openstack-meeting-416:03
*** dharinic has quit IRC16:03
sdakeyour leading the workshop?16:03
inc0yes16:03
*** marst has quit IRC16:03
sdakeis it the 2 hour lab thing?16:03
inc0yes16:03
sdakecool count me in iif my schedule doesn't conflict16:03
inc0thanks16:03
*** hieulq_ has joined #openstack-meeting-416:04
inc0ok moving on16:04
*** Julien-zte has quit IRC16:04
mnaserim in as well16:04
mnaserbarring schedule conflicts16:04
inc0#topic protocore (an onramp to core reviewer) (pbourke)16:04
*** openstack changes topic to "protocore (an onramp to core reviewer) (pbourke) (Meeting topic: kolla)"16:04
inc0agg16:04
inc0sorry one more announcement16:04
inc0very important to me16:04
inc0recently it came to my attention that some of us have issues with visa entry to US for summit/ptg16:05
inc0if you are affected, please let me knw on email16:05
inc0inc007@gmail com16:05
spsurya_+116:05
inc0I'm trying to asses scale of this issue to make sure we're not locking out anyone from discussion16:06
inc0ok, let's get back to meeting16:06
*** aarefiev is now known as aarefiev_afk16:06
inc0so protocore, pbourke sdake you have the floor16:06
*** Julien-zte has joined #openstack-meeting-416:06
pbourkeso, sdake had asked me to cover this, but it seems like he's around?16:06
*** ntpttr has quit IRC16:06
sdakepbourke go ahead an dcover it - i'm in training sort of16:06
pbourkeok16:07
pbourkeso sdake just brought this up earlier today, we dont have all the details but,16:07
inc0I can do it if you guys want16:07
qwango/16:07
inc0and sdake you can correct me16:07
*** baoli has quit IRC16:07
*** Julien-zte has quit IRC16:08
pbourkethe idea came about of having an onboarding program for new core reviewers16:08
*** ntpttr has joined #openstack-meeting-416:08
pbourkeso we wanted to see if people think this is a good or bad idea16:08
berendtGood one.16:08
sdakepbourke i dont know that everyone has heard the idea ;)16:08
spsurya_+1 for idea16:08
inc0so I think it's wonderful idea, question I'm still strugglign with is how exactly will that look like16:09
*** Julien-zte has joined #openstack-meeting-416:09
pbourkesummary is people who would like to be core reviewers will be added to a group. During a certain period a +1 from members of this group will count as a +216:09
pbourkeif a trial core +1's and a current core disagrees, it is the responsibility of the core to explain why in additional detail16:10
mnaseri agree with it16:10
kfox1111I think the idea is they count as 1 of the +2's needed to wf. but can't be both.16:10
sdakekfox1111 right16:10
sdakekfox1111 also trials don't have capability to +2 or +w a review16:10
sdakethey are in "training"16:10
pbourkeapparently nova are currently doing this, so it would be good to get some detail from them16:10
inc0my question for this would be - if core seconds with +2 do we merge with single +2? I'm on the fence with this16:11
berendtI think we should not remove the second +2.16:11
sdakeinc0 yup it is a reasonable concern because it places more responsibility on core reviewers then theey already have16:11
pbourkepersonally, I'm not sure this is actually necessary. That said, I think it could be a nice entry path for people, as kolla and kolla-ansible in particular are short on cores lately imo16:11
sbezverk+1 not remove second +216:11
sbezverkat least at the beginning16:12
mnaseri think it would be best to have an "agreement" on those protocores that they do not do +w16:12
mnaserbut they can do +216:12
kfox1111even if it doesn't remove the second +2, it might alow existing cores to prioritize those reviews,16:12
kfox1111getting them in faster, and building up the protocore's knowlege to the point where more cores are grown faster.16:12
sdakenova doesn't permit protocores to +w or +2 a review16:12
mnaserso a protocore +2 + core +2 can only be wf'd by that 2nd core (or a 3rd core)16:12
inc0yes, in this case that's totally fine, we keep 2*+2 and just put more pressure on explaining why we didn't +216:12
sdakethey just arne't in the gerrit g roup16:12
*** Julien-zte has quit IRC16:12
berendtIs it not possible to have a group that can give +2 without being able to approve a review?16:12
pbourkehave we seen a case were a new core reviewer performed sub standardly? I would say no...16:12
sdakeberendt I am not sure if that is possible but it may be16:13
inc0no, but that's because we have high standards for cores16:13
sdakeberendt that would be a great solution to the 2 +2 problem :)16:13
*** Kevin_Zheng has quit IRC16:13
inc0so I have 2 different approaches to this, one is already being in nova for some time16:13
kfox1111pbourke: the bar has been high for cores in the past, so few mistakes are made.16:13
inc0that being = mentorship16:13
pbourkeok makes sense16:13
sdakekfox1111 the thing is protocores aren't voted on16:13
sbezverksdake: I think the main idea is not looking for a short cut to 2x+2 issue but to motivate people to be more active16:14
sdakekfox1111 however we expect people to learn how to become a  core reviewer without training them16:14
sdakethis magic incantation stage - is very  diffficult16:14
*** Julien-zte has joined #openstack-meeting-416:14
inc0hence mentorship16:14
inc0every core can become a mentor for non-core, or protocore16:14
Jeffrey4lsbezverk, +116:14
kfox1111sdake: yeah. this is a way to help train reviewers to be cores. it makes sense to me.16:14
sdakeyup - and the wayt o be mentored is to be excited that your review actually matters16:14
*** ntpttr has quit IRC16:14
kfox1111so...16:15
inc0sdake: but I'm not ready to remove need for 2*+216:15
sdakementorship is a two way street :)  and requires interest form both aprties16:15
kfox1111shoudl each protocore be assigned to 1+ core officially?16:15
sbezverkinc0: +1 for not removing it16:15
sdakewe could offer protocorss +2 but not +w16:15
inc0then this mentor core can just +2 his mantees change16:15
sdakeprotocores rather16:15
kfox1111inc0: yeah, I think we have enough cores now ,that a core can ask another core for a priority review to deal with the +2.16:15
sdakethe nultimately teh responsiblity of the core reviewer is preserved16:16
inc0and mantee will have trusted core to either ask for review and get +2 or ask for feedback16:16
*** ntpttr has joined #openstack-meeting-416:16
*** baoli has joined #openstack-meeting-416:16
sdakelets ask the quesiton16:16
sdakewho would be interested in participating as a protocore16:16
kfox1111protocors with +2 but not wf sounds very much like what google does.16:16
sdakecan we get a liset?16:16
kfox1111they have cores, and approvers.16:16
inc0sdake: let me ask this clearly - are you suggesting merging changes with just single +2 and +1 from protocore?16:17
kfox1111cores make sure the code is up to snuff. aprovers make sure the code fits in the overall archetecture properly.16:17
sdakeno, I'm suggesting adding +2 ability to a protocore, and merging based upon 2 +2s and a +w from a  core reviewer16:17
inc0so it doesn't changing anything really, we still merge with 2*+2 from cores16:17
sdakein fact ithink berendt suggested that :)16:18
sbezverksdake: but if you give +2 protocore it is not the same as 2x+2 from cores16:18
*** Julien-zte has quit IRC16:18
sbezverkso you relaxing quality checks16:18
kfox1111sbezverk: right.16:18
kfox1111that is the risk in it.16:18
sbezverkkfox1111: I do not think it is right16:18
sdakesbezverk i think the tradeoff is worth it to train the next gen of core reviewers16:18
jascott1_can two protocores +2 a single issue?16:18
sdakejascott1_ nada16:19
*** bogdando has joined #openstack-meeting-416:19
sdakejascott1_ they could but always takes a core reviweer to +w any change16:19
kfox1111sbezverk: yeah, I get the risk. the risk in not having enough cores is also a problem.16:19
jascott1_sdake the system prevents it?16:19
inc0ok...so thing we want to solve is training16:19
*** hieulq_ has quit IRC16:19
kfox1111it seems like the short term solution and long term solution may be different.16:19
jascott1_ah ok16:19
inc0and I'd suggest more official mentorship program for that16:19
inc0at least for start to see if that's work16:19
sdakethis is that inc016:19
*** adisky_ has quit IRC16:19
inc0no sdake, not exactly16:19
sdakenova is anal anal retentive about reviews16:20
inc0by mentorship I mean  each protocore will have mentor (known by name)16:20
*** cathrichardson has joined #openstack-meeting-416:20
sdakeyet they permit a protocore to count as a +216:20
sdakeare we more anal then nova about reviewing?16:20
*** ntpttr has quit IRC16:20
inc0sdake: we are different project and we deal with our policies differently16:20
sdakeinc0 i get that16:20
sdakeinc0 we generally have pretty lax policies in comparison to other projects16:20
sdakenot more stringent16:20
inc0what I *do not* want to do is to rush issue that could potentially lower our quality16:21
kfox1111the one issue I see is,16:21
*** l4yerffeJ has joined #openstack-meeting-416:21
*** janki has joined #openstack-meeting-416:21
kfox1111nova's pretty stable at this point. not so many breaking architectural changes.16:21
sbezverksdake: maybe because nova is not ivolving that rapidly as we, they can afford it16:21
inc0I'm not saying it's bad idea, I'm saying let's spend some time exploring and thinking about problem16:21
kfox1111kolla-kubernetes is changing a lot.16:21
kfox1111so the risk of paches going in that break things are higher.16:21
kfox1111yeah16:21
jascott1_so do cores tap protocores that they see potential in or do protocores sit in the snow outside temple for period of time?16:21
*** Julien-zte has joined #openstack-meeting-416:21
inc0kolla-ansible is somewhere in between16:22
sdakewe have until september to shake out kolla-kubernetes kfox111116:22
sbezverkkfox1111: +2 that is why we need to be extra cautios16:22
*** Julien-zte has quit IRC16:22
inc0since nova still have hard spec process16:22
inc0which means changes have lots of context, we don't follow specs16:22
*** ntpttr has joined #openstack-meeting-416:22
duonghqI think kolla-images is quite stable in arch16:22
inc0so our volitality is higher for new changes16:22
*** Julien-zte has joined #openstack-meeting-416:22
*** trinaths1 has joined #openstack-meeting-416:22
sdakelets have a summary of where we agree and disagree16:22
sdakeinc0 can you do that plz?16:22
*** Julien-zte has quit IRC16:22
inc0not yet, I feel we didn't explore different ideas to solve the problem16:23
inc0can we start ML thread?16:23
*** l4yerffeJ has quit IRC16:23
sdakeindeed16:23
inc0thanks16:23
inc0I'm not saying it's bad idea16:23
inc0in fact I totally support idea in general16:24
*** baoli has quit IRC16:24
kfox1111yeah. that would give other projects that may be struggling the ability to discuss too.16:24
inc0it's details of implementation that I want to get sorted out before we agree/disagree16:24
sdakeyour focused on implemetnation - I have one quesiton16:24
sdakedo we agree to the following16:24
sdake1) we have folks that want to be core reviewers16:24
sdake2) they dont know how to become core reviewers16:25
kfox1111yeah.16:25
inc0totally16:25
sdake3) the core reviewers will mentor these protocores on how to become core reviewers16:25
inc0yup16:25
sdake4) they should be incentivized in some  wya to know that  their voice matters16:25
sdake(vs a drive by reviewer)16:25
inc0soooo here's where I want to stop (4)16:25
sbezverksdake: incentive should not impact the quality16:26
inc0*everyones* voice matters16:26
sdakei am actuallly done16:26
sdake:)16:26
*** rwellum has joined #openstack-meeting-416:26
sdakesup rwallner16:26
sdakerwellum  that is :)16:26
inc0not just core or protocore16:26
*** ntpttr has quit IRC16:26
sdakesbezverk the incentive is to learn how  to become a core reviewer16:26
inc0I want to break this perception that you need to be core for your voie to matter16:27
sdakepart of that is taking the responsibility of reviewing properly16:27
*** dharinic has joined #openstack-meeting-416:27
inc0and adding new layer of "priviledged" will not help imho16:27
sdakesbezverk the incentive isn't the ability to +2 a review16:27
inc0but again, let's have ML discussion16:27
sbezverksdake: I think the way to become core is to be more active16:27
*** lamt has joined #openstack-meeting-416:27
inc0I'm in full support of having cleared path to core16:27
rwellumhi sdake sorry about my lateness, it's at the wrong time on my calendar16:27
sbezverkif you do not want to be active then, you just not ready for the core16:27
sdakesbezverk we need to WRITE DOWN how to beomce a core reviewer16:28
sdakethere are people that actively want it yet dont know how to obtain it16:28
*** zenirc369 has joined #openstack-meeting-416:28
sbezverksdake: easy more reviews and more contribution :)16:28
sdakerwellum DST  FTL :)16:28
jascott1_sdake agree. documenting expectations would be nice as well16:28
*** ntpttr has joined #openstack-meeting-416:28
sdakesbezverk how do you do a good review?16:28
kfox1111sdake: I think the main disconnect is,16:28
kfox1111people need to revew stuff,16:28
sdakekfox1111 right - and they dont know *how*16:28
kfox1111and cores need to be able to notice enough quality reviews from a person are happening to suggest promotion.16:29
inc0sdake: I tihnk it's less about how and more about "voice matters"16:29
kfox1111sdake: frequency helps with that.16:29
inc0ok, I'll cut us here16:29
kfox1111if they reveiw something, and say +1, and then a core -1's it, there's a learning opertunity.16:29
inc0this is important and we need discussion across community16:29
kfox1111eventually the reviewers learn what to look for.16:29
inc0so please, let's start ML thread16:29
kfox1111inc0: yeah.16:29
sdakeyes although we are squandering it by not teaching the new potential core reviweeer16:29
*** gongysh has quit IRC16:29
sdakeml it is16:30
kfox1111sdake: I don't disagree.16:30
inc0thank you16:30
inc0moving on16:30
inc0#topic kolla devstack (pbourke) https://review.openstack.org/#/c/454690/16:30
*** openstack changes topic to "kolla devstack (pbourke) https://review.openstack.org/#/c/454690/ (Meeting topic: kolla)"16:30
sdakekfox1111 if you  dont disagree, you could say ou agree ;)16:30
pbourkeso, just wanted a brief discussion on this16:30
inc0sdake: at this point it's not that we agree or not, it's how we implement it16:30
kfox1111sdake: assumed boolean. ;)16:30
*** baoli has joined #openstack-meeting-416:31
kfox1111right.16:31
sdakethanks pbourke  :)16:31
*** Sukhdev_ has quit IRC16:31
pbourkeit came up quite a while ago that people would like to see kolla as a viable replacement for devstack16:31
inc0ahh, we're here at last16:31
inc0it was lingering idea around16:31
kfox1111an interesting idea.16:31
pbourkeI've put up a patch for a possible implementation, but would like to get some ideas on whats needed and whether this can even work16:31
inc0there is few immmediate benefits for that16:31
inc01. multinode is assumed from start so will allow people to do better testing of multinode code16:32
*** ntpttr has quit IRC16:32
inc02. you'll be able to run upgrades from latest master to your codebase to ensure upgrades aren't breaking16:32
pbourke#link https://review.openstack.org/#/c/454690/16:32
kfox1111I can think of 1 major benifit and 1 major drawback right away from the idea.16:32
pbourkekfox1111: the benefit is you dont have to use devstack :p16:33
kfox1111the beinifit is its closer to what operators would want to use, so devs will see operator problems sooner.16:33
kfox1111the drawback is, it will potentially be more work for devs to do quick dev changes repeatedly to work on a ps.16:33
inc0kfox1111: second one is fixable16:34
inc0by making it easy16:34
pbourkeI've been using the above patch the past day or two to work on a heat change and its quite easy to work with16:34
kfox1111inc0: yeah. its solvable. but non trivial.16:34
pbourkeyou make a change and restart the container, same as you'd restart a process16:34
inc0will require code and good ideas16:34
Jeffrey4lthere one issue in this implementation. what if the end-user changed the database schema, or add a new python dependency?16:34
inc0and I think this is what this change is about16:34
inc0Jeffrey4l: rebuild of container should be way to go16:35
Jeffrey4lothers LGTM16:35
pbourkeinc0: you dont need to rebuild16:35
pbourkeinc0: in most cases16:35
kfox1111pbourke: can you put in a document describing how that flow works into the ps?16:35
kfox1111I think that might help a lot.16:35
pbourkekfox1111: sounds good16:35
inc0also, this will require a lot of howtos16:35
inc0and some code in or codebase16:35
kfox1111it may be easy. its just not obvious to me.16:36
sbezverkdevstack for the time of its existance, produced lots of useful scripts developers got used. absense of these scripts on kolla side might delay adoption it as devstack replacement..16:36
inc0I starred this review, will throw some ideas I've been playing with over the time16:36
inc0sbezverk: but also has a lot of baggage16:37
inc0for example it's not easy to test upgrades16:37
pbourkei haven't used devstack in a long time so if people are used to it I'd be interested in what parts of the workflow they need the most16:37
inc0and it will take over your node16:37
inc0where kolla can be quickly removed16:37
sbezverkinc0: right but when you do not have a spare t-shirt it is not very conveneient ;)16:37
inc0devstack can't16:37
*** pmesserli has quit IRC16:37
pbourkeright now I can guarantee there are people execing into containers and making changes16:37
pbourkeso anything is better than that16:37
Jeffrey4las a certain project developer, for example horizon, who can use kolla to set up whole stack quickly.16:38
inc0and tear it down quickly16:38
Jeffrey4lbetter than devstack.16:38
Jeffrey4lyep.16:38
*** reedip_ has quit IRC16:38
inc0and deploy it prod-like16:38
Jeffrey4lthis direct is meaningful ;)16:39
inc0#action check pbourke's review and throw ideas to the basket16:39
pbourkethanks inc0 sounds good16:39
pbourkethats it from me16:40
inc0thank you Paul for taking this work, it's been whispered around for few years already;)16:40
inc0ok moving on16:40
*** pmesserl_ has joined #openstack-meeting-416:40
inc0#topic tagging of images for automatic pushes to dockerhub (inc0)16:40
*** openstack changes topic to "tagging of images for automatic pushes to dockerhub (inc0) (Meeting topic: kolla)"16:40
inc0soo..we are close to create auto publisher of images16:40
inc0after merge image will be pushed to dockerhub16:40
inc0issue is tagging these images16:41
inc0today we tag with github tag16:41
inc0and I think this is good and proper behavior16:41
inc0so 4.0.0 image tag corresponds with 4.0.0 git tag16:41
inc0but having images from HEAD of each stable branch+master will not follow this tagging16:42
inc0should not at least16:42
inc0so I see few options here, none of which are perfect16:42
berendtWe could simply use the first part of the git hash.16:43
inc01. we create whole new set of tags, for example nova-api:ocata16:43
inc0berendt: negative, if someone would like to keep upgrading their env to HEAD of stable, which is good use case16:43
inc0that would be horrible experience16:43
pbourkeplus you'd end up with thousands of tags very soon16:44
Jeffrey4lberendt, git hash will generate lots of useless images.16:44
mnaseron a semi-related note, i had an interesting discussion with dmsimard a while back about this about tagging and he mentioned that it would be interesting to look at the image tag to be a version that corresponds to the version of the software in the container (e.x: nova-api:14.0.0) rather than nova-api:4.0.0 (which is the kolla version)16:44
berendtUsing hashs in CI currently, there it is working pretty good.16:44
pbourkemnaser: how do you then map that to the appropriate kolla version though16:44
inc0mnaser: so if we use release codename that would be quite easy to figure out16:44
*** david-lyle has joined #openstack-meeting-416:45
inc0berendt: because nobody needs to upgrade their globals.yml every time hash changes;)16:45
Jeffrey4lmnaser, for current implementation in kolla, this is hard ( kolla build all images rather one of images)16:45
mnaseryeah, release codename is really easy too, i agree inc0 .. pbourke, interesting issue but the idea was: kolla 4.0.0 bits were used to generate nova-api 14.0.016:45
mnaserso the bits themselves are those of nova-api 14.0.0, the code used to build it was 4.0.016:46
pbourkewhy cant we use the branch name again?16:46
inc0problem with release name would be automatic tagging detection aka pbr16:46
kfox1111I think the 4.0.0 thing is not quite right.16:46
berendtUsing the release number of Nova does not currently work because we only define one version in the globals file.16:46
kfox1111I think it should tag based on updates.16:46
Jeffrey4li do not think use the nova-api:14.0.0 is better. it cause another issue that which cinder version should i use?16:46
inc0on the bright side...globals.yml openstack_release will point to actual release;)16:46
kfox1111so, 4.0.0-1, 4.0.0-2, 4.0.1-1, etc.16:46
mnaserJeffrey4l the appropriate cinder version for that release.  but branch names works for me except i think that will generate a huge churn16:46
kfox1111aliases can be made for 4.0.0-2 to 4.0.0 in case people don't want to care about atomic updates.16:47
mnaseri.e.: is nova-compute:ocata really stable/ocata?  will we rebuild on every merge of every project?16:47
inc0kfox1111: 4.0.0-2 would mean second commit after tag?16:47
inc0mnaser: no, dailt16:47
kfox1111inc0: I'm talking about stable not trunk.16:47
inc0daily16:47
Jeffrey4lwhat issue are we talking and solving ;(16:47
kfox1111tags would be for unversioned changes.16:47
mnaseri think i've created a different conversation, sorry16:48
kfox1111so I guess for trunk, yeah, it would be incrementing the release, not the version.16:48
*** wxy| has quit IRC16:48
mnasergoing back to topic, nightly builds tagged with branch name for kolla seem reasonable16:48
kfox1111but for stable, anything that causes any changes to the container that arn't a version change need to bump revision.16:48
inc0kfox1111: well we still keep tagged images16:48
*** ntpttr__ has quit IRC16:48
inc0as in once we tag, we push16:48
Jeffrey4lmnaser, yep, for branch image is useful.16:48
kfox1111so, for example, shared libraries needing to update.16:48
kfox1111inc0: versions are for bunches of patches "released".16:49
kfox1111so, kolla 4.0.1 is a bug fix release to 4.0.0.16:49
mnasernow what if a change was introduced in stable/<branch> that needed something in $your_fav_kolla_deployment_tool ?16:49
inc0kfox1111: but we also rebuild at that time16:49
mnasernow you deploy from the tagged branch but things break16:49
*** psachin has quit IRC16:49
kfox1111but 4.0.1 built at 4/12/2017 is different then 4.0.1 built at 5/12/2017.16:49
kfox1111due to security updates of base packages.16:50
inc0kfox1111: agree, but we can't solve this in kolla16:50
inc0in dockerhub at least16:50
kfox1111so, the first should be 4.0.1-1 and the second 4.0.1-2.16:50
kfox1111in dockerhub.16:50
Jeffrey4lkfox1111, this is not big issue, too.16:50
mnaser^ i think that is the more fundamental issue which will help us answer the part for inc0's question16:50
kfox1111Jeffrey4l: it is a big issue to folks wanting security updates.16:50
inc0well, it's going to be big issue if we want to have same experience while pulling from dockerhub and building locally16:50
Jeffrey4lif you want security updates, just update all your containers.16:51
kfox1111not being able to tag revisions means its hard to know whats updated and whats not.16:51
kfox1111Jeffrey4l: thats a very costly thing to do with openstack. :/16:51
mnaseri disagree, as an operator, if there was some sort of really big change that happened from 14.0.1 to 14.0.2 in nova and 4.0.0 happens to change on that deploy16:51
kfox1111I want the ability to update only the stuff needed, when needed.16:51
mnaser$bad_stuff16:51
inc0I agree with kfox1111 ops need to be able to selectively pick and chose containers16:51
Jeffrey4lotherwise, how to get the updates?16:51
Jeffrey4lkfox1111, it is hard to define *which* stuff need to be update.16:52
inc0what I don't agree with you kfox1111 really is that ops that wants this type of control would use dockerhub...16:52
kfox1111comparing whats running on your system, vs whats in the repo's is step 1 to solving it.16:52
inc0I'd rather suggest keeping local registry and control your builds16:52
kfox1111if the names are the same, you have no idea whats going on.16:52
Jeffrey4lif you wanna just update nova-api from 4.0.1 to 4.0.2, then just update nova_api_tag: variable16:52
kfox1111if you see 4.0.0-1 is on your sytem, but 4.0.0-2 is released, now hyou know things.16:52
*** unicell has quit IRC16:53
kfox1111and can start digging into why the change was made, and why you may or may not want to apply it.16:53
Jeffrey4lhrm are u talking daily build for kolla tag?16:53
pbourkekfox1111: that could maybe solved with labels16:53
inc0also I don't want us to become effectively repository mgmt team for openstack16:53
kfox1111Jeffrey4l: kind of. security updates.16:53
pbourkeno other projects on dockerhub use that kind of tagging16:53
Jeffrey4lshouldn't the operator use self-build images? use hub.docker.com is danger.16:53
inc0waaay beyond our capability16:53
Jeffrey4lat least, i will not do this..16:53
kfox1111pbourke: and many projects on docker hub are riddled with seciruty problmes. :/16:53
kfox1111inc0: its an autobuild thing. its not hard.16:54
pbourkekfox1111: im mainly talking about the official images16:54
pbourkekfox1111: which should serve as a reference16:54
kfox1111pbourke: I am too.16:54
kfox1111the reference images shoudl be secure.16:54
inc0ok...so I suggest something different for now16:54
kfox1111should not need to build the images themselves.16:54
inc0we need to have both conversations16:54
inc0but short term, let's figure out autobuild not-fully versioned16:55
inc0and have discussion on version mgmt in general16:55
kfox1111the revision's not hard to do. you just have to know what version was built last,16:55
kfox1111and increment it by one before pushing.16:55
kfox1111the infra for pushing is the hard bit.16:55
*** ntpttr has joined #openstack-meeting-416:55
inc0I agree, but doing this on buildtime locally will be fun code to write16:56
inc0and we need to do this on build time locally to have similar experience on local registry and dockerhub16:56
inc0which for me is important16:56
kfox1111+1.16:56
kfox1111for folks that want to ci/cd it themselves,16:56
inc0because again, we really suggest to build your own images16:56
kfox1111they will need the same functionality.16:56
kfox1111and again, will need revisions.16:56
inc0this is how I'd run my prod anyway16:57
kfox1111just driven by jenkins or whatever.16:57
inc0ok, we're running out of time16:57
inc0I'll start ML thread about both issues - 1. autotagging for HEAD for daily pushes to dockerhub16:57
inc0and 2. general revisiion mgmgt16:57
inc0mgmt16:57
inc0or rather, do we agree with nova-api:ocata approach?16:58
inc0for HEAD builds?16:58
kfox1111for stable or just trunk?16:58
inc0both16:58
Jeffrey4lre  nova-api:ocata, agree, but need tell the end-user, this is not stable.16:58
inc0it's stable16:58
Jeffrey4land not recommended to use directly.16:58
inc0anyway, we're out of time16:58
kfox1111why not just nova-api:trunk?16:58
inc0thank you all, let's move it to #openstack-kolla16:59
inc0#endmeeting kolla16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Wed Apr 12 16:59:06 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-04-12-15.59.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-04-12-15.59.txt16:59
Jeffrey4lit is stable branch, but the image is not stable. because it is a daily build16:59
kfox1111Jeffrey4l: we've been doing that already. and it has turned away users I think.16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-04-12-15.59.log.html16:59
*** vks1 has joined #openstack-meeting-417:00
*** jascott1_ has left #openstack-meeting-417:00
*** hrw has left #openstack-meeting-417:00
*** bogdando has quit IRC17:03
*** tovin07 has quit IRC17:03
*** psachin has joined #openstack-meeting-417:06
*** ntpttr__ has joined #openstack-meeting-417:07
*** ntpttr has quit IRC17:07
*** pshedimb_ has quit IRC17:10
*** psachin_ has joined #openstack-meeting-417:11
*** woodard has quit IRC17:11
*** woodard has joined #openstack-meeting-417:12
*** reedip_ has joined #openstack-meeting-417:12
*** psachin_ has quit IRC17:14
*** lamt has quit IRC17:17
*** neiljerram has quit IRC17:17
*** neiljerram has joined #openstack-meeting-417:19
*** psachin_ has joined #openstack-meeting-417:19
*** psachin_ has quit IRC17:21
*** duonghq has quit IRC17:22
*** psachin_ has joined #openstack-meeting-417:22
*** unicell has joined #openstack-meeting-417:23
*** psachin_ has quit IRC17:23
*** daidv has quit IRC17:26
*** egonzalez has quit IRC17:29
*** cathrichardson has left #openstack-meeting-417:29
*** dtardivel has quit IRC17:30
*** psachin has quit IRC17:34
*** rwellum has left #openstack-meeting-417:34
*** cathrichardson has joined #openstack-meeting-417:36
*** ralonsoh_ has quit IRC17:36
*** cathrichardson has left #openstack-meeting-417:36
*** sambetts is now known as sambetts|afk17:36
*** vishnoianil has joined #openstack-meeting-417:45
*** pshedimb_ has joined #openstack-meeting-417:46
*** Sukhdev has quit IRC17:46
*** ntpttr__ has quit IRC17:56
*** neiljerram has quit IRC17:58
*** ntpttr has joined #openstack-meeting-417:59
*** mattmceuen has joined #openstack-meeting-418:02
*** baoli has quit IRC18:03
*** baoli has joined #openstack-meeting-418:04
*** krtaylor has quit IRC18:05
*** s3wong has joined #openstack-meeting-418:06
*** dharinic has quit IRC18:10
*** lamt has joined #openstack-meeting-418:14
*** vks1 has quit IRC18:29
*** ntpttr has quit IRC18:30
*** cathrichardson has joined #openstack-meeting-418:40
*** yfauser_ has joined #openstack-meeting-418:40
*** aavraham has joined #openstack-meeting-418:41
*** yfauser has quit IRC18:43
*** Sukhdev has joined #openstack-meeting-418:44
*** vks1 has joined #openstack-meeting-418:44
*** aavraham has left #openstack-meeting-418:48
*** krtaylor has joined #openstack-meeting-418:49
*** vks1 has quit IRC18:49
*** baoli has quit IRC18:54
*** baoli has joined #openstack-meeting-418:54
*** Sukhdev_ has joined #openstack-meeting-418:56
*** dharinic has joined #openstack-meeting-418:58
*** Sukhdev_ has quit IRC18:59
*** Sukhdev_ has joined #openstack-meeting-419:00
*** vks1 has joined #openstack-meeting-419:04
*** Sukhdev_ has quit IRC19:09
*** ntpttr has joined #openstack-meeting-419:16
*** zenirc369 has quit IRC19:17
*** ntpttr has quit IRC19:18
*** ntpttr has joined #openstack-meeting-419:18
*** lamt has quit IRC19:22
*** baoli has quit IRC19:23
*** baoli has joined #openstack-meeting-419:23
*** Sukhdev_ has joined #openstack-meeting-419:26
*** Sukhdev_ has quit IRC19:26
*** janki has quit IRC19:27
*** pshedimb_ has quit IRC19:35
*** trinaths1 has quit IRC19:35
*** yfauser_ has quit IRC19:47
*** vhosakot has quit IRC19:48
*** yfauser has joined #openstack-meeting-419:49
*** lamt has joined #openstack-meeting-419:54
*** lamt has quit IRC19:54
*** lamt has joined #openstack-meeting-420:02
*** cathrichardson has quit IRC20:15
*** caboucha has quit IRC20:16
*** cathrichardson has joined #openstack-meeting-420:16
*** vks1 has quit IRC20:18
*** jose-phillips has joined #openstack-meeting-420:18
*** vks1 has joined #openstack-meeting-420:20
*** dharinic has quit IRC20:26
*** vks1 has quit IRC20:29
*** yfauser has quit IRC20:37
*** marst_ has quit IRC20:48
*** marst_ has joined #openstack-meeting-420:49
*** Sukhdev has quit IRC20:56
*** thorst has quit IRC21:01
*** thorst has joined #openstack-meeting-421:02
*** pshedimb_ has joined #openstack-meeting-421:04
*** epcim has joined #openstack-meeting-421:04
*** dharinic has joined #openstack-meeting-421:04
*** thorst has quit IRC21:06
*** sdague has quit IRC21:07
*** ntpttr has quit IRC21:08
*** ntpttr has joined #openstack-meeting-421:08
*** haleyb has quit IRC21:08
*** bkero has quit IRC21:13
*** Sukhdev has joined #openstack-meeting-421:14
*** bkero has joined #openstack-meeting-421:25
*** bkero has quit IRC21:25
*** bkero has joined #openstack-meeting-421:25
*** neiljerram has joined #openstack-meeting-421:28
*** krtaylor has quit IRC21:32
*** cjloade__ has joined #openstack-meeting-421:33
*** cathrichardson has quit IRC21:35
*** cjloader_ has quit IRC21:36
*** cjloade__ has quit IRC21:37
*** marst_ has quit IRC21:38
*** neiljerram has quit IRC21:43
*** marst_ has joined #openstack-meeting-421:44
*** baoli has quit IRC21:50
*** pcaruana has quit IRC21:51
*** rwallner has quit IRC21:54
*** ntpttr has quit IRC21:55
*** galstrom is now known as galstrom_zzz21:57
*** lamt has quit IRC21:59
*** rwallner has joined #openstack-meeting-422:01
*** ntpttr has joined #openstack-meeting-422:02
*** lamt has joined #openstack-meeting-422:04
*** mgkwill has joined #openstack-meeting-422:04
*** rwallner has quit IRC22:05
*** klamath has quit IRC22:09
*** lyan has quit IRC22:10
*** inc0 has quit IRC22:12
*** rbak_ has quit IRC22:34
*** lyan has joined #openstack-meeting-422:37
*** mbruzek has quit IRC22:42
*** marst_ has quit IRC22:43
*** baoli has joined #openstack-meeting-422:45
*** lamt has quit IRC22:47
*** baoli has quit IRC22:50
*** bobh has quit IRC22:57
*** lamt has joined #openstack-meeting-422:59
*** Sukhdev has quit IRC23:04
*** trinaths has joined #openstack-meeting-423:07
*** rwallner has joined #openstack-meeting-423:07
*** lamt has quit IRC23:08
*** ntpttr has quit IRC23:08
*** ntpttr__ has joined #openstack-meeting-423:08
*** rwallner has quit IRC23:11
*** lamt has joined #openstack-meeting-423:12
*** lamt has quit IRC23:12
*** lamt has joined #openstack-meeting-423:13
*** lamt has quit IRC23:13
*** lamt has joined #openstack-meeting-423:14
*** lamt has quit IRC23:15
*** pshedimb_ has quit IRC23:15
*** pmesserl_ has quit IRC23:16
*** epcim has quit IRC23:18
*** thorst has joined #openstack-meeting-423:20
*** pshedimb_ has joined #openstack-meeting-423:20
*** baoli has joined #openstack-meeting-423:20
*** baoli has quit IRC23:21
*** thorst has quit IRC23:21
*** baoli has joined #openstack-meeting-423:22
*** trinaths has left #openstack-meeting-423:26
*** chyka has quit IRC23:30
*** chyka has joined #openstack-meeting-423:31
*** chyka has quit IRC23:35
*** hippiepete has joined #openstack-meeting-423:38
*** hippiepete has quit IRC23:38
*** gongysh has joined #openstack-meeting-423:40
*** pshedimb_ has quit IRC23:44
*** bobh has joined #openstack-meeting-423:46

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