Wednesday, 2017-05-31

*** galstrom_zzz is now known as galstrom00:02
*** dave-mccowan has joined #openstack-meeting-400:03
*** markvoelker has quit IRC00:04
*** thorst has joined #openstack-meeting-400:14
*** salv-orlando has joined #openstack-meeting-400:15
*** thorst has quit IRC00:15
*** thorst has joined #openstack-meeting-400:17
*** thorst has quit IRC00:19
*** salv-orlando has quit IRC00:19
*** yifei has joined #openstack-meeting-400:19
*** neiljerram has quit IRC00:27
*** slaweq has joined #openstack-meeting-400:29
*** iyamahat has quit IRC00:32
*** yamahata has quit IRC00:33
*** slaweq has quit IRC00:35
*** Julien-zte has joined #openstack-meeting-400:46
*** markvoelker has joined #openstack-meeting-400:47
*** Julien-zte has quit IRC00:49
*** emagana has quit IRC00:49
*** emagana has joined #openstack-meeting-400:50
*** Julien-zte has joined #openstack-meeting-400:51
*** emagana has quit IRC00:54
*** galstrom is now known as galstrom_zzz01:09
*** markvoelker_ has joined #openstack-meeting-401:16
*** markvoelker has quit IRC01:17
*** cathrich_ has joined #openstack-meeting-401:19
*** cathrichardson has quit IRC01:19
*** thorst has joined #openstack-meeting-401:19
*** jose-phillips has quit IRC01:20
*** markvoelker_ has quit IRC01:21
*** jose-phillips has joined #openstack-meeting-401:21
*** markvoelker has joined #openstack-meeting-401:23
*** yamahata has joined #openstack-meeting-401:24
*** thorst has quit IRC01:24
*** leo_wang has joined #openstack-meeting-401:26
*** slaweq has joined #openstack-meeting-401:30
*** slaweq has quit IRC01:35
*** tovin07_ has joined #openstack-meeting-401:39
*** baoli_ has quit IRC01:40
*** rwellum has quit IRC01:41
*** hongbin has quit IRC01:51
*** lei-zh has joined #openstack-meeting-402:06
*** unicell has quit IRC02:06
*** iyamahat has joined #openstack-meeting-402:12
*** thorst has joined #openstack-meeting-402:13
*** thorst has quit IRC02:13
*** salv-orlando has joined #openstack-meeting-402:15
*** dave-mccowan has quit IRC02:15
*** rfolco has quit IRC02:17
*** vishnoianil has quit IRC02:19
*** jrist has quit IRC02:20
*** salv-orlando has quit IRC02:20
*** SerenaFeng has joined #openstack-meeting-402:30
*** slaweq has joined #openstack-meeting-402:31
*** jrist has joined #openstack-meeting-402:33
*** slaweq has quit IRC02:36
*** thorst has joined #openstack-meeting-402:37
*** thorst has quit IRC02:38
*** Julien-zte has quit IRC03:00
*** Julien-zte has joined #openstack-meeting-403:03
*** thorst has joined #openstack-meeting-403:09
*** Julien-zte has quit IRC03:10
*** Julien-zte has joined #openstack-meeting-403:11
*** Julien-zte has quit IRC03:19
*** Julien-zte has joined #openstack-meeting-403:20
*** Julien-zte has quit IRC03:23
*** Julien-zte has joined #openstack-meeting-403:24
*** thorst has quit IRC03:26
*** SerenaFeng has quit IRC03:26
*** Julien-zte has quit IRC03:27
*** Julien-zte has joined #openstack-meeting-403:28
*** psachin has quit IRC03:29
*** slaweq has joined #openstack-meeting-403:32
*** vks1 has joined #openstack-meeting-403:33
*** anilvenkata has joined #openstack-meeting-403:34
*** SerenaFeng has joined #openstack-meeting-403:34
*** david-lyle has joined #openstack-meeting-403:35
*** Julien-z_ has joined #openstack-meeting-403:35
*** janki has joined #openstack-meeting-403:37
*** slaweq has quit IRC03:37
*** Julien-zte has quit IRC03:37
*** Julien-z_ has quit IRC03:45
*** links has joined #openstack-meeting-403:45
*** rfolco has joined #openstack-meeting-403:45
*** rfolco has quit IRC03:45
*** unicell has joined #openstack-meeting-403:46
*** Julien-zte has joined #openstack-meeting-403:46
*** psachin has joined #openstack-meeting-403:47
*** Julien-zte has quit IRC03:50
*** salv-orlando has joined #openstack-meeting-403:50
*** Julien-zte has joined #openstack-meeting-403:51
*** Julien-zte has quit IRC03:53
*** salv-orlando has quit IRC03:54
*** Julien-zte has joined #openstack-meeting-403:56
*** lei-zh has quit IRC04:03
*** yamamoto has joined #openstack-meeting-404:13
*** zenirc369 has joined #openstack-meeting-404:15
*** zhurong has joined #openstack-meeting-404:16
*** SerenaFeng has quit IRC04:16
*** zhurong has quit IRC04:19
*** hongbin has joined #openstack-meeting-404:21
*** slaweq has joined #openstack-meeting-404:33
*** slaweq has quit IRC04:37
*** salv-orlando has joined #openstack-meeting-404:39
*** vks1 has quit IRC04:46
*** emagana has joined #openstack-meeting-404:52
*** Julien-zte has quit IRC04:52
*** Julien-zte has joined #openstack-meeting-404:55
*** hongbin has quit IRC04:57
*** adisky__ has joined #openstack-meeting-405:03
*** lei-zh has joined #openstack-meeting-405:05
*** vks1 has joined #openstack-meeting-405:05
*** karthiks has joined #openstack-meeting-405:23
*** thorst has joined #openstack-meeting-405:23
*** slaweq has joined #openstack-meeting-405:24
*** thorst has quit IRC05:28
*** slaweq has quit IRC05:31
*** SerenaFeng has joined #openstack-meeting-405:38
*** unicell1 has joined #openstack-meeting-405:44
*** unicell has quit IRC05:45
*** yfauser has quit IRC05:47
*** yfauser has joined #openstack-meeting-405:48
*** karthiks has quit IRC05:49
*** yfauser has quit IRC05:52
*** Julien-zte has quit IRC05:52
*** karthiks has joined #openstack-meeting-406:02
*** SerenaFeng has quit IRC06:06
*** emagana has quit IRC06:10
*** yamahata has quit IRC06:11
*** vishnoianil has joined #openstack-meeting-406:21
*** SerenaFeng has joined #openstack-meeting-406:22
*** thorst has joined #openstack-meeting-406:24
*** thorst has quit IRC06:29
*** yamamoto has quit IRC06:30
*** slaweq has joined #openstack-meeting-406:32
*** matrohon has quit IRC06:35
*** slaweq has quit IRC06:37
*** julim has quit IRC06:38
*** ltomasbo|away is now known as ltomasbo06:41
*** julim has joined #openstack-meeting-406:42
*** basilAB has quit IRC06:42
*** basilAB has joined #openstack-meeting-406:44
*** yfauser has joined #openstack-meeting-406:48
*** yfauser has quit IRC06:53
*** matrohon has joined #openstack-meeting-406:54
*** bogdando has joined #openstack-meeting-407:00
*** yfauser has joined #openstack-meeting-407:01
*** kbyrne has quit IRC07:05
*** kbyrne has joined #openstack-meeting-407:06
*** unicell has joined #openstack-meeting-407:08
*** dimak_ has joined #openstack-meeting-407:09
*** unicell1 has quit IRC07:09
*** yamamoto has joined #openstack-meeting-407:13
*** neiljerram has joined #openstack-meeting-407:22
*** unicell1 has joined #openstack-meeting-407:24
*** unicell has quit IRC07:25
*** pcaruana has joined #openstack-meeting-407:26
*** salv-orl_ has joined #openstack-meeting-407:27
*** iyamahat has quit IRC07:29
*** salv-orlando has quit IRC07:30
*** zenirc369 has quit IRC07:32
*** slaweq has joined #openstack-meeting-407:33
*** slaweq has quit IRC07:38
*** SerenaFeng has quit IRC07:38
*** dimak_ has quit IRC07:40
*** egonzalez has joined #openstack-meeting-407:44
*** thorst has joined #openstack-meeting-407:46
*** ralonsoh has joined #openstack-meeting-407:50
*** thorst has quit IRC07:50
*** aarefiev_afk is now known as aarefiev07:54
*** ralonsoh_ has joined #openstack-meeting-407:54
*** ralonsoh has quit IRC07:56
*** kzaitsev_ws has joined #openstack-meeting-408:02
*** alexchadin has joined #openstack-meeting-408:09
*** ralonsoh_ is now known as ralonsoh08:12
*** kbyrne has quit IRC08:14
*** kbyrne has joined #openstack-meeting-408:17
*** emagana has joined #openstack-meeting-408:27
*** zenirc369 has joined #openstack-meeting-408:27
*** emagana has quit IRC08:31
*** slaweq has joined #openstack-meeting-408:34
*** pbourke has quit IRC08:35
*** pbourke has joined #openstack-meeting-408:36
*** slaweq has quit IRC08:39
*** thorst has joined #openstack-meeting-408:47
*** pbourke_ has joined #openstack-meeting-408:53
*** jose-phi_ has joined #openstack-meeting-408:53
*** wxy_ has joined #openstack-meeting-408:53
*** dasanind_ has joined #openstack-meeting-408:54
*** ediardo_ has joined #openstack-meeting-408:54
*** chigang__ has joined #openstack-meeting-408:54
*** sulo_ has joined #openstack-meeting-408:55
*** hwoarang_ has joined #openstack-meeting-408:55
*** numans_ has joined #openstack-meeting-409:00
*** mmedvede_ has joined #openstack-meeting-409:00
*** johnthetubaguy_ has joined #openstack-meeting-409:00
*** dmellado_ has joined #openstack-meeting-409:00
*** pbourke has quit IRC09:01
*** links has quit IRC09:01
*** jose-phillips has quit IRC09:01
*** numans has quit IRC09:01
*** hwoarang has quit IRC09:01
*** ediardo has quit IRC09:01
*** sulo has quit IRC09:01
*** chigang_ has quit IRC09:01
*** dasanind has quit IRC09:01
*** mmedvede has quit IRC09:01
*** wxy has quit IRC09:01
*** dmellado has quit IRC09:01
*** mhayden has quit IRC09:01
*** johnthetubaguy has quit IRC09:01
*** mmedvede_ is now known as mmedvede09:01
*** ediardo_ is now known as ediardo09:01
*** dasanind_ is now known as dasanind09:01
*** wxy_ is now known as wxy09:01
*** SerenaFeng has joined #openstack-meeting-409:01
*** beagles has quit IRC09:03
*** limao has joined #openstack-meeting-409:03
*** adreznec has quit IRC09:04
*** adreznec has joined #openstack-meeting-409:05
*** b3nt_pin has joined #openstack-meeting-409:06
*** b3nt_pin is now known as Guest4632509:06
*** thorst has quit IRC09:06
*** links has joined #openstack-meeting-409:07
*** mhayden has joined #openstack-meeting-409:07
*** david-lyle has quit IRC09:11
*** david-lyle has joined #openstack-meeting-409:12
*** salmankhan has joined #openstack-meeting-409:13
*** limao has quit IRC09:29
*** slaweq has joined #openstack-meeting-409:35
*** trinaths has joined #openstack-meeting-409:35
*** vks1 has quit IRC09:38
*** slaweq has quit IRC09:39
*** sambetts|afk is now known as sambetts09:44
*** dmellado_ is now known as dmellado09:46
*** alexchadin has quit IRC09:46
*** vks1 has joined #openstack-meeting-409:49
*** tovin07_ has quit IRC09:55
*** lei-zh has quit IRC09:55
*** salmankhan has quit IRC10:07
*** Julien-zte has joined #openstack-meeting-410:10
*** Julien-zte has quit IRC10:12
*** Julien-zte has joined #openstack-meeting-410:12
*** links has quit IRC10:16
*** salmankhan has joined #openstack-meeting-410:22
*** Julien-zte has quit IRC10:23
*** Julien-zte has joined #openstack-meeting-410:24
*** Julien-zte has quit IRC10:25
*** Julien-zte has joined #openstack-meeting-410:26
*** Julien-zte has quit IRC10:26
*** mfedosin has joined #openstack-meeting-410:28
*** Julien-zte has joined #openstack-meeting-410:28
*** aavraham has joined #openstack-meeting-410:29
*** slaweq has joined #openstack-meeting-410:35
*** links has joined #openstack-meeting-410:36
*** Julien-zte has quit IRC10:39
*** Julien-zte has joined #openstack-meeting-410:40
*** slaweq has quit IRC10:40
*** Julien-zte has quit IRC10:44
*** Julien-zte has joined #openstack-meeting-410:45
*** trinaths has left #openstack-meeting-410:56
*** salv-orl_ has quit IRC10:59
*** yamamoto has quit IRC11:02
*** Julien-zte has quit IRC11:03
*** thorst has joined #openstack-meeting-411:04
*** Julien-zte has joined #openstack-meeting-411:05
*** Julien-zte has quit IRC11:07
*** Julien-zte has joined #openstack-meeting-411:08
*** thorst has quit IRC11:08
*** dave-mccowan has joined #openstack-meeting-411:12
*** Julien-zte has quit IRC11:15
*** kbyrne has quit IRC11:23
*** SerenaFeng has quit IRC11:23
*** aavraham has quit IRC11:23
*** rwallner has joined #openstack-meeting-411:23
*** rfolco has joined #openstack-meeting-411:30
*** thorst has joined #openstack-meeting-411:30
*** rfolco has quit IRC11:30
*** slaweq has joined #openstack-meeting-411:36
*** salmankhan has quit IRC11:39
*** rwallner has quit IRC11:40
*** slaweq has quit IRC11:40
*** rwallner has joined #openstack-meeting-411:41
*** Guest46325 is now known as beagles11:41
*** yamamoto has joined #openstack-meeting-411:43
*** rwallner has quit IRC11:46
*** rwallner has joined #openstack-meeting-411:47
*** salmankhan has joined #openstack-meeting-411:47
*** psachin has quit IRC11:49
*** psachin has joined #openstack-meeting-411:49
*** cathrich_ has quit IRC11:55
*** rfolco has joined #openstack-meeting-412:02
*** psachin has quit IRC12:07
*** kbyrne has joined #openstack-meeting-412:08
*** yfauser_ has joined #openstack-meeting-412:09
*** links has quit IRC12:11
*** yfauser has quit IRC12:11
*** vks1 has quit IRC12:18
*** anilvenkata has quit IRC12:19
*** janki has quit IRC12:26
*** rwallner has quit IRC12:30
*** rwallner has joined #openstack-meeting-412:31
*** slaweq has joined #openstack-meeting-412:37
*** rwellum has joined #openstack-meeting-412:42
*** slaweq has quit IRC12:42
*** Julien-zte has joined #openstack-meeting-412:43
*** yfauser_ has quit IRC12:46
*** yfauser has joined #openstack-meeting-412:46
*** Julien-zte has quit IRC12:48
*** Julien-zte has joined #openstack-meeting-412:48
*** iyamahat has joined #openstack-meeting-412:50
*** yfauser has quit IRC12:51
*** zenirc369 has quit IRC12:56
*** cathrichardson has joined #openstack-meeting-412:56
*** lyan has joined #openstack-meeting-412:57
alex_xu#startmeeting nova api12:59
openstackMeeting started Wed May 31 12:59:59 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
*** cdent has joined #openstack-meeting-413:00
alex_xuwho is here today?13:00
Kevin_Zhengo/13:00
cdento/13:00
*** bobmel has quit IRC13:01
*** Julien-zte has quit IRC13:01
alex_xuok, let us start the meeting13:01
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/policy-docs13:02
alex_xulooks like all the patches are approved13:02
*** Julien-zte has joined #openstack-meeting-413:02
alex_xuI think we are done all of those work, maybe I should do a double check later13:02
alex_xu#link https://review.openstack.org/46861913:03
alex_xuthe next thing is the quota-class bug, which bring up by gmann last week13:03
alex_xuthe spec is already submitted13:03
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bug/169316813:04
alex_xugmann also have patch for it13:04
alex_xuthere also one question doesn't get answer yet, which is about the legacy v213:04
alex_xunot sure whether we should fix legacy v2 API13:05
*** woodard has joined #openstack-meeting-413:06
sfinucano/13:06
*** woodard has quit IRC13:06
*** woodard has joined #openstack-meeting-413:07
alex_xumaybe the easiest way is adding a reno which notice the user to set the server-group-quota extension as undiscoverable in the legacy v2 API.13:07
alex_xuthat may makes the API user's code work correctly.13:07
alex_xuanyway, I will go through all the options in the spec13:08
*** psachin has joined #openstack-meeting-413:09
*** baoli has joined #openstack-meeting-413:09
*** pmesserli has joined #openstack-meeting-413:09
alex_xu#link https://etherpad.openstack.org/p/pike-nova-priorities-tracking13:09
alex_xualso I list all the API related patches in the etherpad13:09
*** yamahata has joined #openstack-meeting-413:10
alex_xu#link https://review.openstack.org/#/q/topic:bp/restore-vm-diagnostics13:10
*** baoli has quit IRC13:10
alex_xurestore-vm-diagnostics one is most close one13:10
alex_xualso thanks sfinucan review the patches13:11
sfinucan(y)13:11
alex_xuthat is all I have today13:11
alex_xuany other thing people want to bring up?13:11
alex_xutoday is very quiet :)13:12
sfinucanI guess most of the US guys are still away13:13
sfinucanI don't have anything pressing, personally :)13:13
alex_xusfinucan: yea, I heard that there is holiday in the US13:13
cdentI got nothing13:14
alex_xuok, let us end the meeting today, back to work or ready to sleep :)13:14
alex_xuthanks all13:14
sfinucan(y) ta13:14
alex_xu#endmeeting13:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:14
openstackMeeting ended Wed May 31 13:14:25 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-05-31-12.59.html13:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-05-31-12.59.txt13:14
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-05-31-12.59.log.html13:14
cdento/13:15
*** cdent has left #openstack-meeting-413:15
*** superdan is now known as dansmith13:26
*** mugsie has quit IRC13:27
*** rwallner has quit IRC13:28
*** vks1 has joined #openstack-meeting-413:31
*** klamath has joined #openstack-meeting-413:33
*** klamath has quit IRC13:33
*** bobh has joined #openstack-meeting-413:33
*** baoli has joined #openstack-meeting-413:33
*** klamath has joined #openstack-meeting-413:34
*** baoli has quit IRC13:35
*** cleong has joined #openstack-meeting-413:37
*** baoli has joined #openstack-meeting-413:37
*** slaweq has joined #openstack-meeting-413:38
*** zhurong has joined #openstack-meeting-413:42
*** slaweq has quit IRC13:43
*** vks1 has quit IRC13:45
*** krtaylor has quit IRC13:46
*** yfauser has joined #openstack-meeting-413:47
*** trinaths has joined #openstack-meeting-413:49
*** alexchadin has joined #openstack-meeting-413:51
*** yfauser has quit IRC13:52
*** rwallner has joined #openstack-meeting-413:52
*** psachin has quit IRC13:53
*** krtaylor has joined #openstack-meeting-413:54
*** krtaylor has quit IRC13:55
*** vks1 has joined #openstack-meeting-413:59
*** yfauser has joined #openstack-meeting-413:59
alexchadin#startmeeting watcher14:00
openstackMeeting started Wed May 31 14:00:23 2017 UTC and is due to finish in 60 minutes.  The chair is alexchadin. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: watcher)"14:00
openstackThe meeting name has been set to 'watcher'14:00
*** Yumeng__ has joined #openstack-meeting-414:00
alexchadinHello!14:00
Yumeng__Hi14:00
sballe_morning14:00
alexchadinToday we have the following agenda: https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#05.2F31.2F201714:01
alexchadin#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:01
alexchadin#info One week left till pike-2 release14:02
*** draynium has quit IRC14:02
alexchadinplease, spend your time on high priority BPs during your review process14:03
*** lakerzhou has joined #openstack-meeting-414:03
*** vincentfrancoise has joined #openstack-meeting-414:03
vincentfrancoiseo/14:03
alexchadin#info OpenStack Foundation proposed to use Storyboard instead of Launchpad14:03
alexchadin#link https://storyboard.openstack.org/14:03
alexchadinFoundation tests new service named storyboard14:03
lakerzhoulakerzhou14:04
*** yfauser has quit IRC14:04
sballe_alexchadin: when will we be switching?14:04
*** licanwei has joined #openstack-meeting-414:04
alexchadinit uses auth of launchpad, but stores BP and bugs in different things14:04
alexchadinsballe_: I want Watcher team to play around with this site and we will decide whether we move to storyboard or not by next Wednesday14:05
*** emagana has joined #openstack-meeting-414:05
alexchadin#link https://storyboard-dev.openstack.org/14:05
vincentfrancoisealexchadin: that's a big change if it gets accepted14:05
alexchadinhere is test version to crush :D14:06
alexchadinvincentfrancoise: yes, so we need time to look at it14:06
alexchadinand to make right choice14:06
alexchadin#link https://storyboard-blog.io/14:07
alexchadinhere is description of storyboard and why Foundation wants to migrate to it14:07
alexchadinplease, read above links once you have some free time14:08
alexchadinas vincentfrancoise said, it is really big change and we need to compare all pros and contras14:09
*** iyamahat has quit IRC14:09
*** emagana has quit IRC14:10
vincentfrancoisealexchadin: +114:10
alexchadinwell, any other announcements from you?14:10
*** salv-orlando has joined #openstack-meeting-414:10
alexchadingreat, let's move on14:11
alexchadin#topic Review Action Items14:11
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:11
alexchadinWatcher specs14:11
alexchadinAdd spec for Supporting HA for background jobs in Watcher needs final core from Susanne #link https://review.openstack.org/#/c/447996/14:12
*** emagana has joined #openstack-meeting-414:12
sballe_done14:12
alexchadinsballe_: if you +2 it, could you please send it to workflow?14:12
sballe_done14:13
alexchadinsballe_: thanks!14:13
alexchadinNoisy Neighbor Strategy needs reviews (Hidekazu's comment is still valid) #link https://review.openstack.org/#/c/398162/14:13
*** yamahata has quit IRC14:13
sballe_psdhemdi is moving but he will be back next week and will upload a new spec14:14
* sballe_ meant pshedimbi14:14
alexchadinsballe_: sure14:14
alexchadin#action pshedimbi submit new PS on https://review.openstack.org/#/c/398162/14:14
alexchadinSupport workload fingerprinting needs reviews #link https://review.openstack.org/#/c/448396/14:15
sballe_I ran out of time regarding review but will try this week14:16
alexchadin#action sballe_ review https://review.openstack.org/#/c/448396/14:17
alexchadinAdd spec for services-versioned-notifications-api bp needs final core review #link https://review.openstack.org/#/c/445817/14:17
alexchadinsballe_: it would be good if you review it too14:18
sballe_ok will do14:18
*** cathrichardson has quit IRC14:18
alexchadinsballe_: it is already accepted by me, vincentfrancoise, hidekazu and licanwei14:18
*** yfauser has joined #openstack-meeting-414:19
*** yfauser has quit IRC14:19
*** yfauser has joined #openstack-meeting-414:19
sballe_alexchadin:14:19
sballe_done14:19
alexchadinsballe_: since it has the same structure as other notification-related specs, it won't take a lot of time to review it14:19
alexchadinAdd Volume migrate action spec needs reviews #link https://review.openstack.org/#/c/468817/14:20
alexchadinhidekazu has submitted it recently, it is part of cinder related commits14:21
sballe_nice!14:22
alexchadinvincentfrancoise: could you please review it?14:22
vincentfrancoisealexchadin: add me on it, I'll do my best :)14:23
vincentfrancoisealexchadin: I wanted to do some more reviews before the meeting but a meeting I wasn't aware took the time slot away from me...14:24
alexchadinvincentfrancoise: no worries14:24
alexchadin#action vincentfrancoise review https://review.openstack.org/#/c/468817/14:24
*** cathrichardson has joined #openstack-meeting-414:25
alexchadinBuild baremetal data model in watcher needs new PS #link https://review.openstack.org/#/c/448016/14:25
*** hongbin has joined #openstack-meeting-414:25
alexchadinYumeng__: have you seen Bin Zhou's comments?14:25
Yumeng__Yep, I have seen them14:26
Yumeng__I will update tomorrow14:26
Yumeng__Since I just come back from holiday14:26
alexchadinYumeng__: great!14:26
alexchadin#action Yumeng__ submit new PS on https://review.openstack.org/#/c/448016/14:27
alexchadinAdd new actions "power on" and "power off" in Watcher needs new PS #link https://review.openstack.org/#/c/435436/14:27
alexchadinYumeng__: here is the same :)14:28
Yumeng__Ok14:28
alexchadin#action Yumeng__ submit new PS on https://review.openstack.org/#/c/435436/14:30
alexchadinWatcher14:31
vincentfrancoisealexchadin: Yumeng__: I just added a comment on https://review.openstack.org/#/c/448016/ to explain how we use notifications to build CDMs so that lakerzhou can see they are not really mandatory although highly encouraged14:31
alexchadinvincentfrancoise: thank you14:32
alexchadinCancel Action Plan needs reviews #link https://review.openstack.org/#/c/458492/14:33
alexchadinI will try to review it14:34
alexchadin#action alexchadin review https://review.openstack.org/#/c/458492/14:34
alexchadinWatcher Install guide needs reviews #link https://review.openstack.org/#/c/463281/14:34
*** woodard has quit IRC14:34
*** zhurong has quit IRC14:35
alexchadinsballe_: could you please review it14:35
alexchadin?14:35
Yumeng__vincentfrancoise: thanks!14:35
sballe_alexchadin: I am running out of time. I need to make sure I answers Bin Zhou's comments in our patch on noisy neighbor14:36
sballe_I really want it merged as soon as possible14:36
alexchadinsballe_: okay :)14:37
vincentfrancoisealexchadin: quick question about the lack of specs core reviewers since acabot is not here anymore, shouldn't we have all/most watcher core-reviewers as specs core-reviewers too so we end up with 1 core from each represented company?14:37
alexchadinvincentfrancoise: I plan to have talks with everyone from watcher core-reviewers this week14:38
vincentfrancoisealexchadin: oh ok then :)14:39
*** slaweq has joined #openstack-meeting-414:39
alexchadinvincentfrancoise: I was talking about it during last meeting :)14:39
vincentfrancoisealexchadin: yeah I saw the subject popped up although I didn't read it all14:39
alexchadinYumeng__: do you have time to review install guide?14:39
lakerzhoualexchadin, I will review the install guide14:40
alexchadinlakerzhou: thank you!14:41
Yumeng__Yes, I can make time to do.14:41
alexchadin#action Yumeng__ lakerzhou review https://review.openstack.org/#/c/463281/14:41
*** cathrichardson has left #openstack-meeting-414:41
alexchadinNoisy Neighbor Strategy needs reviews #link https://review.openstack.org/#/c/454359/14:41
sballe_alexchadin: just answered Bin Zhou14:42
sballe_I think the issue here is that not all noisy neighbor algorithm will server everybody14:42
sballe_This algorithm is helping Intel in several ways.14:42
sballe_It solves our issue and help illustrate how ll3 metric can be used14:43
sballe_I agree that the code needs to be divided up in subroutines, etc.14:43
sballe_but I am not sure I agree on questions around the algorithm14:43
*** slaweq has quit IRC14:43
lakerzhouMy main concern is around the decision of the dest_server14:43
sballe_lakerzhou: I saw that. we are chosing the server with the least amount of cache occupancy which is what the algorithm focuses on14:44
vincentfrancoisesballe_: Maybe a solution would be to add a description in which case it works and the assumptions it makes following the templating we used for other strategies like workload_balance.py14:44
lakerzhouother than that, it is just code format, and code comments14:44
sballe_so we migrate the aggressor to the server with the least amount of last level cache occupancy14:45
sballe_vincentfrancoise: let me look at thta14:45
sballe_vincentfrancoise: I added this as a comment to the code and pshembi will address it14:47
alexchadinlakerzhou: sballe_ vincentfrancoise nice work :D14:48
*** vincentfrancoise has quit IRC14:48
alexchadinvincentfrancoise: I agree about description14:49
*** vincentfrancoise has joined #openstack-meeting-414:49
lakerzhou+114:49
* sballe_ :-)14:50
sballe_+114:50
*** iyamahat has joined #openstack-meeting-414:50
alexchadinlakerzhou: every strategy (which is initiated by company) solves the issues which company faces14:50
*** marst has joined #openstack-meeting-414:50
sballe_alexchadin: +114:51
alexchadinlakerzhou: it may be not acceptable for other companies, but we are trying to provide wide-range strategies14:51
vincentfrancoiselakerzhou: alexchadin: this is also why you have the distinction between goals and strategies: the former is generic the latter is more tied to the context of a company14:52
sballe_+114:52
*** baoli has quit IRC14:52
alexchadinright14:53
lakerzhoualexchadin, it is not realistic for one solution to fix all problems. Where should a user find the context of the solution?14:53
lakerzhouA user need to know the risk if he/she wants to take the solution14:53
*** kgiusti has joined #openstack-meeting-414:54
sballe_lakerzhou: Whihc is why the description suggested by vincentfrancoise  is a great idea14:54
alexchadinlakerzhou: user should find the goal that should be solved and look for goal's strategies, their descriptions and algorithm details14:54
lakerzhouI am totally onboard with the description suggestion14:55
alexchadinlakerzhou: we already have description section for strategies14:55
alexchadinlet me find a link...14:55
alexchadinlakerzhou: https://github.com/openstack/watcher/tree/master/doc/source/strategies14:56
lakerzhouthanks, alex14:56
*** trinaths has left #openstack-meeting-414:56
*** ansmith has joined #openstack-meeting-414:56
*** simon-AS559 has joined #openstack-meeting-414:56
alexchadinlakerzhou: you can find a link to strategy specification inside of its documentation, section Algorithm14:57
alexchadinExcuse me, but I need to go14:57
*** iyamahat has quit IRC14:57
vincentfrancoisealexchadin: time's almost over anyway ;)14:57
alexchadinwe have 3 minutes left so I propose to end up this meeting14:57
*** shintaro has joined #openstack-meeting-414:58
lakerzhouI don't see one for noisy neighbor, so will we have one there?14:58
sballe_ok make sense14:58
sballe_bye and have a great day14:58
alexchadinlakerzhou: you are welcome on openstack-watcher channel :)14:58
vincentfrancoiselakerzhou: yes, the answer to your question will be to write one of those ;)14:58
lakerzhousure, thanks all14:58
vincentfrancoisebye14:58
alexchadinthank you for your attention14:58
alexchadingood luck and have a nice day14:59
alexchadinbye14:59
*** vincentfrancoise has left #openstack-meeting-414:59
alexchadin#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Wed May 31 14:59:16 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-05-31-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-05-31-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2017/watcher.2017-05-31-14.00.log.html14:59
*** lakerzhou has left #openstack-meeting-414:59
*** alexchadin has quit IRC14:59
serverascode#startmeeting operators_telco_nfv15:00
*** ad_rien_ has joined #openstack-meeting-415:00
openstackMeeting started Wed May 31 15:00:35 2017 UTC and is due to finish in 60 minutes.  The chair is serverascode. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: operators_telco_nfv)"15:00
openstackThe meeting name has been set to 'operators_telco_nfv'15:00
ad_rien_o/15:00
ad_rien_Hi all15:00
serverascode#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: operators_telco_nfv)"15:00
serverascodehi ad_rien_15:00
serverascode#link https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda15:01
serverascodeanybody else here for the ops telecom/nfv meeting? :)15:01
kgiustio/15:01
serverascodehi kgiusti :)15:02
kgiustihi there!15:02
ad_rien_Hi guys15:02
*** baoli has joined #openstack-meeting-415:02
serverascodeok so far 3 of us...15:02
serverascodeanybody else lurking?15:02
serverascodekgiusti is this your first time attending?15:03
serverascodeif so you could introduce yourself :)15:03
kgiustiSure thing - I'm a developer on the oslo.messaging project and work for redhat.  Very interested in highly distributed messaging stuff.15:04
serverascodeah ok cool15:04
serverascodewell thanks for coming :)15:04
*** qwebirc30842 has joined #openstack-meeting-415:04
serverascodeunless there are some other people arriving late I'm not sure there is much we can do today15:04
kgiustimy pleasure - hope I can help out if there's any oslo.messaging stuff15:05
shintarohi15:05
ad_rien_Hi Shintaro15:05
serverascodehi shintaro :)15:05
shintaroI was in wrong channel :(15:05
serverascodeI think we are in the right channel, I always have to double check15:05
*** lyan has quit IRC15:05
*** licanwei has quit IRC15:05
*** wxy| has joined #openstack-meeting-415:05
serverascodeok I guess with four we can continue on with the meeting :)15:05
*** lyan has joined #openstack-meeting-415:06
serverascode#topic actions from last meeting15:06
*** openstack changes topic to "actions from last meeting (Meeting topic: operators_telco_nfv)"15:06
serverascodelet me just lookup the last meeting15:06
ansmitho/15:06
ad_rien_:-)15:06
serverascodehi ansmith :)15:07
ad_rien_Hi ansmith15:07
serverascodeok actions from last meeting15:07
ansmithhi15:07
serverascodeACTION: : keep in mind progress regarding monthly WG chairs meeting. (serverascode, 15:13:56)15:07
serverascodeACTION: : gianpietro gather a list of potential NFV deployment examples (serverascode, 15:18:40)15:07
serverascodeACTION: : serverascode to respond to WG chairs collaboration session email thread (serverascode, 15:21:43)15:07
serverascodegianpietro is not here15:07
serverascodeI didn't respond to that particular email thread, but I did send a different message on the same topic15:08
serverascodeso I think we are good there15:08
shintaroany progress on WG chairs meeting?15:08
ad_rien_+1 ?15:08
serverascodenot that I'm aware of15:08
shintaroI may need to poll Edger about this. or Ildiko15:08
ad_rien_Yes15:09
ad_rien_I'm not sure all WG chairs got the message15:09
serverascodeif I remember correctly the last thing was an email suggesting just using the wg meeting15:09
shintarobut UC meeting timeslot is not good for me...15:09
jamemccHi15:09
serverascodehi jamemcc :)15:10
shintaroah now we have 3 WG chairs!15:10
ad_rien_:-)15:10
ad_rien_s/NFV/WG chair meeting ;)15:10
serverascodeyeah my memory is just from a thread between ildiko, jamey, adrien, me, and edgar15:10
serverascodebut I don't know any more than that15:10
jamemccThats my understanding as well - UC meeting is Edgars suggestion.15:11
ad_rien_The initial thread is that one: Re: WG Chairs Collaboration session (May 8th @ 12:05PM)15:11
* ad_rien_ is looking for the linj15:11
ad_rien_cannot find it but the list of the persons was larger15:12
jamemccIRC that way - basically what's been suggested since early this year - but we never got the WG chairs to the UC meeting and it didnt' happen many weeks as well.15:12
jamemccI think if the 3 of us would attend that would create the start though.15:12
ad_rien_JAMEY A MCCABE "JAMEY A MCCABE" <jm6819@att.com>; Edgar Magana "Edgar Magana" <emagana@gmail.com>; Melvin Hillsman "Melvin Hillsman" <mrhillsman@gmail.com>; Shilla Saebi "Shilla Saebi" <shilla.saebi@gmail.com>; Jon Proulx "Jon Proulx" <jon@jonproulx.com>; Shamail Tahir "Shamail Tahir" <itzshamail@gmail.com>; Patricia Montenegro "Patricia Montenegro" <patricia.montenegro@intel.com>; Christopher Aedo "Christopher Aedo" <doc@ae15:12
ad_rien_do.net>; Yih Leong Sun "Yih Leong Sun" <yih.leong.sun@intel.com>; nematollah.bidokhti@huawei.com "nematollah.bidokhti@huawei.com" <Nematollah.Bidokhti@huawei.com>; Rochelle Grober "Rochelle Grober" <rockyg@gmail.com>; Matt VanWinkle "Matt VanWinkle" <mvanwink@rackspace.com>; Tom Fifield "Tom Fifield" <tom@openstack.org>; Curtis Collicutt "Curtis Collicutt" <curtis@interdynamix.com>; Stig Telfer15:12
*** limao has joined #openstack-meeting-415:12
ad_rien_all that persons were in the initial mail.15:13
ad_rien_but unfortunately no follow up15:13
ad_rien_It can make sense to reactivate that thread15:13
serverascodeyeah I didn't respond to that one15:13
ad_rien_and see whether it leads us somewhere15:13
jamemccI agree a better time is needed, I think perhaps 1200 or 1300 UTC might work.15:13
ad_rien_Maybe Shinator your were not in this loop.15:13
ad_rien_sorry s/Shinator/Shintaro15:14
shintarono. I would prefer this thread take in some ML. maybe UC ML?15:14
ad_rien_if you want15:14
serverascodeyeah they are hard to follow when not on a mailing list15:14
ad_rien_Maybe I can forward this thread to the different ML ?15:14
ad_rien_yes I agree15:14
ad_rien_so let's forward it to the MLs ?15:14
emaganaI am around15:15
emaganacan someone let me know what's up?15:15
ad_rien_Coo. Hi  emagana15:15
shintarohi emagana15:15
serverascodehi emagana :)15:15
emaganaI got the notification from my chat but I haven't read the whole meeting minutes15:15
ad_rien_We discussed a few times of how we can improve collaborations between WGs15:15
emaganahi ad_rien_ shintaro serverascode15:15
shintarowe were talking about WG charis meeting and NFV collaboration discussion15:16
ad_rien_We exchanged a couple of emails between several folks but we did not converge toward a final decision.15:16
emaganaOh, you may refer to the email about having a dedicated time during the UC IRC meeting for all WGs15:16
emaganais that the topic?15:16
*** Yumeng__ has left #openstack-meeting-415:16
*** limao_ has joined #openstack-meeting-415:16
serverascodeexactly the topic15:16
ad_rien_yes… can be the solution15:16
serverascodethe time is not great for shintaro15:17
ad_rien_The idea was to give the floor two minutes for each WG to present what they did during the last month and what the WG plans to do for the next one.15:17
*** limao has quit IRC15:17
ad_rien_I don't know whether this should be done on a month basis or two weeks (less seems not reasonable at least for the FEMDC WG)15:18
serverascodewe might have lost shintaro15:18
shintaroIf we can invite OPNFV and ETSI or any relevant external project there to have their update, we can find overlapping activities which we can collaborate on15:19
ad_rien_and I don't know how this should be organized.15:19
serverascodeI like the idea of hearing from OPNFV and others15:19
emaganain my mind I always wanted to have one or two members of the WGs attending the UC IRC meeting and share the progress and/or impediments15:19
shintaroI'm still here serverascode :)15:19
*** woodard has joined #openstack-meeting-415:20
*** woodard has quit IRC15:20
serverascodeok great that you are still online :)15:20
emaganaI was even planing to make it some kind of "requirement" to keep going on the WG15:20
*** woodard has joined #openstack-meeting-415:20
emaganabut it is hard to attend for some members in a different time zone, for instance shintaro15:20
ad_rien_emagana:  all: I think there are two aspects: 1./ Collaborations between OpenStack WGs in general (Performance, Large scale team, FEMDC, NFV, LCCO,…) and 2./ Collaborations between any WG that deals with NFV related challenges15:21
emaganaCorrect, the one that I want to tackle is the number 1) with the UC IRC meetings15:21
ad_rien_for 1./ I think we should define one IRC meeting per month (because I don't think it would be possible for each WG to attend every UC meetings)15:21
emaganaThe 2) should be mostly from this WG15:21
ad_rien_for 2./ I think we should create a new thread on the ML and add in the loop OpenNFV and ESTI folks15:22
emaganaad_rien_: That's also a good idea, we can have a dedicated meeting every three or four weeks.15:22
shintaro+1 and ask them which thread is good for them15:22
emaganawe can even change the timing for that meetings in order to be sure that we guarantee that max attendence15:22
ad_rien_yes15:22
ad_rien_I think this would be valuable15:23
emaganawhat about running a poll about the timing with all WGs15:23
emaganato find out that time?15:23
ad_rien_and I think it should target all WGs (UC and TC)15:23
emaganaI don't think we should include the TC initially15:23
ad_rien_Large Scale Team, Performance Team … we are all addressing interesting challenges/questions with a lot of overlaps15:23
jamemccI guess it's the start of getting chairs to show up is to get them to say when they could show up15:23
ad_rien_+115:24
emaganalet's identify requirements or very well define request and then we can engage with TC15:24
ad_rien_jamemcc15:24
*** woodard has quit IRC15:24
ad_rien_ad_rien_:  from our side (FEMDC) I think we are more a TC WG than a UC one.15:24
*** woodard has joined #openstack-meeting-415:24
ad_rien_As we are investigating technical questions and we provide technical contributions15:24
ad_rien_(this is an example)15:25
ad_rien_Large Deployment team is a TC or UC WG?  What's about Performance? What's about NFV?15:25
ad_rien_to be honest it is difficult for me to see where is the frontier.15:25
serverascodehmm, I'm not sure there is such a thing as a TC working group15:26
shintaroso we need a place like the Forum, right?15:26
*** TxGirlGeek has joined #openstack-meeting-415:26
ad_rien_shintaro:  yes I think that the issue we have with all NFV WGs is something more general.15:26
*** kzaitsev_ws has quit IRC15:27
ad_rien_I do not want to steal the time of the meeting today15:27
ad_rien_but I really think we should find means/methods/strategies to be able to be more fruitful15:27
jamemccBut really there are only 2 semi-acceptabel times to have a meeting if you have to cover the whole world and not be in the Midnight to 6AM. 1300 or 1400 UTC and 0400 UTC - though I think even that one is difficult for Europe. I guess those are the ones I would start with to poll. Let me start one now.15:27
serverascodewe are good for time, we only have a couple things on the agenda15:27
shintaroI can reach out Ildiko and OPNFV folks for 2) topic15:27
ad_rien_jamemcc:  we can alternate15:28
*** kzaitsev_ws has joined #openstack-meeting-415:28
*** simon-AS559 has quit IRC15:28
ad_rien_one month we favor one part of the world and the other month...15:28
serverascodeso the poll would be a for a UC meeting time once per month where other WGs can come and report what they have been doing?15:29
ad_rien_+1 from my side.15:29
ad_rien_I think we should be able to identify synergies between WGs/actions15:29
serverascodeok, and it sounds like jamemcc is willing to create that poll :)15:29
ad_rien_otherwise, my feeling is that we are going to give up at the end :(15:30
*** krtaylor has joined #openstack-meeting-415:30
serverascode#action jamemcc create a poll for a monthly UC meeting time where other WGs could come and report on their activities15:30
serverascodeand it sounds like shintaro is willing to coordinate with OPNFV?15:30
shintaroyes15:30
serverascode#action shintaro coordination with OPNFV regarding the once per month UC meeting time in which other WGs and communities can report their activities15:31
shintarooption is to join the UC monthly meeting or have them here in this IRC15:31
serverascodeok15:31
serverascodethat seems like some good actions :)15:31
serverascodeanything else on this topic?15:32
shintaronone from me15:33
serverascodeok, we'll move on15:33
ad_rien_jamemcc:  could you please send the mail on dev-ML ops-ML and the general one so we can ensure to attract as much as WG chairs.15:33
ad_rien_serverascode:  no thanks15:33
serverascodeansmith are you still here? :)15:33
*** vishnoianil has quit IRC15:33
jamemccWIll do15:34
ad_rien_thanks15:34
serverascodedarn maybe we lost ansmith15:34
jamemccTry this pol - see if it's clear to your timezone15:34
jamemcc#URL https://beta.doodle.com/poll/6k36zgre9ttciwqz#table15:34
*** aarefiev is now known as aarefiev_afk15:34
mrhillsmanyou raaaaang15:34
ansmithsorry, had walked away for a sec15:34
ad_rien_ok from my side15:34
jamemccYou are the best to certify - thanks15:35
emaganaplease, email me anything needed from my side. I will be in PTO from 6/1 to 6/815:35
serverascodeansmith oh no worries, if you want to do a quick introduction that'd be great15:35
* ildikov got caught up in another thread, sorry :(15:35
ansmithyes, work along with kgiusti on messaging15:35
serverascodemrhillsman we were just discussing a UC meeting for WGs to discuss their activities15:36
serverascodebut I think we have some steps figured out15:36
serverascodeansmith ah ok15:36
mrhillsmanOk cool15:36
serverascodethanks for dropping in though :)15:36
mrhillsmanI see emagana so all in is order :)15:36
emaganaups!15:36
ildikovI was waiting to agree on re-using or not the UC meeting, maybe adding a permanent agenda item, etc, but I'll double check that thread now :)15:37
emaganaI have been multitasking (my bad) but I think we are good with some action items with  shintaro and jamemcc15:37
ildikovI can help out with channelling in the ETSI folks15:37
ildikovand with shintaro we will also get OPNFV in15:37
serverascodeildikov that's great!15:37
shintarothanks ildikov!15:37
*** vks1 has quit IRC15:38
emaganaildikov: Yes, I missed to asnwer your last email but it seems that in this meeting we are deciding to besides giving time during the UC IRC meeting, we will have a specific one for the WGs cross collaboration15:38
ad_rien_Once per month will be great (to start at least)15:39
*** slaweq has joined #openstack-meeting-415:39
ildikovemagana: sounds good, I need to read back the logs as I was late due to some firefighting on another thing...15:40
ildikovemagana: business as usual :)15:40
ildikovemagana: thanks for your help!15:40
shintaroildikov: so for OPNFV/ETSI folks, they have two options. to join the monthly IRC or join this ops-nfv IRC15:40
ildikovad_rien_: +115:40
ad_rien_jamemcc:  maybe it should be underlined that we expect to have one representative for each WG15:41
ildikovshintaro: I would go for the monthly one to get a dedicated forum for the updates15:41
emaganaildikov: sounds good!15:41
ad_rien_(if the WG chair cannot attend we should find a substitute)15:41
*** Rockyg has joined #openstack-meeting-415:41
ildikovshintaro: so people know what they can expect and what's expected from them15:41
shintarook15:41
ad_rien_otherwise, it would be rather impossible to converge on a doodle15:41
ildikovshintaro: if you agree15:41
shintaroI agree15:42
shintarowe can use this channel for more specific discussions.15:42
shintaroif they want15:42
ildikovad_rien_: I think we could have liaisons from the groups too15:42
*** rwallner has quit IRC15:42
ad_rien_ildikov:  you mean ?15:43
*** rwallner has joined #openstack-meeting-415:43
jamemcc+1 to Shintaro's suggestion - Monthy UC which is more of a status and this meeting (every 2 weeks) for the more detailed NFV topics15:43
ildikovad_rien_: I was just reflecting to your substitute comment15:43
ad_rien_ok15:43
ildikovshintaro: yep, we should not go down in too deep details with the monthly meeting but find where to discuss items in details, like this channel15:44
*** slaweq has quit IRC15:44
*** matrohon has quit IRC15:44
ildikovjamemcc: +1 :)15:44
serverascodejamemcc: +1 as well15:44
*** pmesserli has quit IRC15:45
shintarook great15:45
*** pmesserli has joined #openstack-meeting-415:45
ildikovI think we're getting there now :)15:45
ildikovthank you All for your support on this!15:45
*** caboucha has joined #openstack-meeting-415:45
serverascodeyeah this is great15:45
*** emagana_ has joined #openstack-meeting-415:45
shintarothank you ildikov for stopping by :)15:46
serverascodedo we want to have a quick look at the poll jamemcc created?15:46
ildikovshintaro: I planned to do that already at the beginning of the meeting, but don't have an alert set in my calendar so I missed it... :/15:46
ad_rien_Actually I don't know whether we should open a doodle15:47
ad_rien_or simply define the first slot15:47
*** bogdando has quit IRC15:47
serverascodeanyone have an opinion on that?15:47
ad_rien_emagana:  could you please tell us whe  is scheduled the next UC meeting? or what can be the next UC meeting we can use to make this first try ?15:48
ad_rien_s/whe is/when is15:48
*** emagana has quit IRC15:49
serverascodenot sure if this is right http://eavesdrop.openstack.org/#User_Committee_Meeting15:49
serverascodebut it says weekly, monday, 18:00 UTC15:50
jamemccThis is where I have been going to try to add tot he agenda and confirm date and time15:50
jamemcc#link https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee15:50
ad_rien_ok so not sure whether emagana_ wants to schedule a specific meeting (but they it can become a nightmare to get a slot across the different IRC channels) or if we want to leverage the UC slot.15:50
jamemccI believe it needs to be changed to June 515:51
ildikovad_rien_: I think we should have enough meeting channels15:51
emagana_The wiki is right15:51
emagana_Those are our weekly UC IRC meetings15:51
ildikovad_rien_: but we can agree on the next step on the next UC meeting15:51
emagana_eveybody is welcome to attend15:51
ad_rien_hmmm15:51
ildikovemagana_: I planned this Monday and then I realized it's a US holiday, when I saw it's canceled :)15:52
ad_rien_I think the goal is to 1./ contact everyone on the MLs to invite all WG chairs to join a specific meeting.15:52
emagana_I wont be able to attend next Monday meeting but please, coordinate with either mrhillsman shamail shilla or jon15:52
ad_rien_so my question is what can be the date? jamemcc opened a doodle (thanks jamemcc)15:52
ad_rien_but the slots, which have been proposed, do not correspond to the UC meetings.15:53
ad_rien_so I'm a bit lost :-P15:53
ad_rien_sorry15:53
serverascodemy impression of what we discussed so far was that it would be a "special meeting" and we would have to figure out a time15:54
serverascodebut I don't know how we would figure out a time/date15:54
ad_rien_time/date/IRC channel15:54
jamemccI think sending out the doodle to gather times (and people) is a good move.  And at the same time we should rbing this to the next UC meeting as it's more the propoer place for the discussion.15:54
shintaroUC weekly is not Asia friendly, but jamemcc proposed slot that may fit for all US/Europe/Asia15:54
ildikovI usually create a Doodle including all one hour slots for a week in UTC and see whether we have at least one lucky one where most of the people are around15:55
ad_rien_ok so let's keep an eye on jamemcc's doodle15:55
jamemccAfter we see results of the doodle for a few days and have the UC discusion tehn we can settle on a new time for UC if desired - perhaps only for the monthy as well as a new time for the Operators Telco NFV.15:55
ildikovall those three are hard to cover with one slot15:55
*** duonghq has joined #openstack-meeting-415:55
ildikovI'm personally flexible with weird hours, but we will see how things go15:55
*** inc0 has joined #openstack-meeting-415:55
ad_rien_serverascode:  17:56 ?15:56
serverascodeyeah 4 min left :)15:56
serverascodeok anyone strongly opposed to what jamemcc metioned above? put out the poll as is, see how it goes, attend next UC meeting to discuss?15:57
emagana_So, in summary the idea is to find a time for everybody every three or four weeks to discuss cross functional activities. Because the meeting may end up in a not so friendly time for some of us, it should be still fine because it is just once every month15:57
ad_rien_emagana_:  +115:57
shintaro+115:57
serverascodeyup15:58
ildikovserverascode: +115:58
ildikovemagana_: +115:58
emagana_looking forward to see the results from the poll jamemcc15:58
emagana_take care folks, moving on to my next meeting15:58
serverascodethanks emagana15:58
*** jascott1 has joined #openstack-meeting-415:58
ad_rien_same here.15:58
shintarohave a good vacation emagana15:58
ad_rien_thanks serverascode15:58
emagana_And again, everybody is welcome to the UC IRC meeting on Mondays!15:58
serverascodeok, well, I think that conlcludes our meeting today :)15:58
ad_rien_for chairing the discussion15:58
emagana_shintaro: Thanks!15:59
serverascodewe will push the two things we had onto the next meeting15:59
*** baoli has quit IRC15:59
serverascodethanks everyone!15:59
shintarothank you15:59
*** spsurya_ has joined #openstack-meeting-415:59
serverascode#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Wed May 31 15:59:31 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-05-31-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-05-31-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2017/operators_telco_nfv.2017-05-31-15.00.log.html15:59
inc0#startmeeting kolla15:59
openstackMeeting started Wed May 31 15:59:54 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
sdakeo/16:00
inc0#topic w00t for Kolla!16:00
*** openstack changes topic to "w00t for Kolla! (Meeting topic: kolla)"16:00
spsurya_o/16:00
berendto/16:00
rwellumw00t16:00
jascott1o/16:00
spsurya_w00t16:00
berendtWoot16:00
inc0we need to make video in one of summits where everyone in community will shout w00t;)16:00
inc0(yes, with zeros)16:00
krtayloro/16:00
berendtGreat idea.16:00
duonghqwo0t o/16:00
*** baoli has joined #openstack-meeting-416:01
egonzalezwoot!16:01
inc0lets give few more minutes16:01
Jeffrey4lo/16:02
inc0ok let's get to business16:03
TxGirlGeekw00t!!16:03
inc0#topic announcements16:03
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:03
inc01. new resolution from TC was proposed that will directly affect us16:03
inc0https://review.openstack.org/#/c/469265/ this resolution will provide guidelines for publishing images to dockerhub/quay.io16:03
inc0I encourage everyone to read it carefully and provide feedback16:04
*** shintaro has quit IRC16:04
* krtaylor looks16:04
*** baoli has quit IRC16:04
berendt#link https://review.openstack.org/#/c/46926516:04
inc0thanks Christian16:04
inc0so, on that note we'll kick off this whole project of publishing, so if anyone wants to contribute, I'd appreciate help16:05
inc0there is a lot of cool code to be written;)16:05
*** marst has quit IRC16:05
*** marst has joined #openstack-meeting-416:06
inc02. I haven't done this last week (since I was out), but I would like to congratulate Bertrand and welcome him to core team:)16:06
*** david-lyle has quit IRC16:06
sdakegrats!16:06
inc0any community announcements?16:06
sdakequestion - is the ptg eventprint page up?16:06
inc0I haven't heard anything yet16:07
sdakethanks16:07
inc0ok, let's move on16:07
sdakeneed to book travel before the checkwriters change their minds :)16:07
sdakecan you ask around inc0?16:07
*** limao_ has quit IRC16:07
inc0check with ttx, he was one who gave me link last time;)16:08
inc0or I can do it16:08
inc0anyway, let's move on16:08
inc0#topic bp/ansible-specific-task-become (duonghq)16:08
*** openstack changes topic to "bp/ansible-specific-task-become (duonghq) (Meeting topic: kolla)"16:08
inc0duonghq: go ahead16:08
duonghqinc0, thanks, but I don't remember that I register this topic for this meeting, but, I still need more suggestion for the bp16:09
duonghqonly 3ps16:10
duonghqhttps://review.openstack.org/#/c/398682/16:10
duonghqhttps://review.openstack.org/#/c/398684/16:10
*** marst has quit IRC16:10
duonghqhttps://review.openstack.org/#/c/398685/16:10
*** ad_rien_ has left #openstack-meeting-416:10
duonghqinc0, I saw you comment on 2nd ps, can you re-review that?16:11
inc0sure16:11
duonghqespecially about gate in 2nd ps16:11
inc0I'll wait for neutron to get fixed tho16:11
inc0it's critical that this ps gets gate coverage16:11
duonghqsorry, I don't get your point16:12
inc0duonghq: neutron bug makes our gates red'16:12
duonghqyou mean the rolling update one?16:12
duonghqgot it16:12
*** yfauser has quit IRC16:13
inc0ok, anything else Duong on this topic?16:13
*** baoli has joined #openstack-meeting-416:13
duonghqI'm done, thank you16:13
inc0#topic nova cell instabilities (rwellum)16:13
*** openstack changes topic to "nova cell instabilities (rwellum) (Meeting topic: kolla)"16:13
inc0rwellum: you have the floor16:13
rwellumYes thanks -  just a question: These micro-services were added to a service recently: nova-cell0-create-db-job and nova-api-create-simple-cell-job. For me nova seems unstable - takes a lot longer in kubernetes for the pods to stabilize. Curious if anyone else is seeing this, and if I should write a bug?16:13
inc0rwellum: ocata nova requires cell0 setup16:14
inc0and this is whole new database and such16:14
*** david-lyle has joined #openstack-meeting-416:14
rwellumYes but I was adding them as micro-services - and it worked fine.16:15
rwellumAs long as the order was correct etc.16:15
inc0kfox1111 around?16:15
rwellumI think sdake mentioned he was suspicious about the change.16:16
sdakerwellum i think that change is broken16:16
rwellumah16:16
*** simon-AS559 has joined #openstack-meeting-416:16
inc0I guess we need to un-break it then;)16:16
sdakeinc0 i dont know how16:16
sdakeinc0 its a circular dependency issue16:16
sdakeit works in the gate because the gate spams the operations16:16
inc0mhm16:16
sdakewhen done manually it will not work reliably16:17
inc0I see16:17
sdakemy best recommendation would be to revert the change16:17
inc0ok, publish a bug, mark it critical and let's work to fix it?16:17
rwellumsdake: even for kolla-ansible?16:17
sdakerwellum i dont follow for kolla-ansible16:17
sdakekolla-ansible syncronizees in the correct order16:17
rwellumgot it16:17
sdakekolla-kubernetes has no such synchronization16:17
inc0rwellum: kolla ansible doesn't have this issue16:17
inc0sdake: change dependency order in entrypoint?16:18
sdakecell0 must be registered after the placement api16:18
sdakeinc0 unfortunately i think that wont work either16:18
inc0why16:18
sdakeas cell0 is optinoal16:18
inc0?16:18
*** simon-AS5591 has joined #openstack-meeting-416:18
sdakeand entrypoint doesn't support optionals16:18
inc0oh joy16:19
sdakesorry conditonal16:19
sdake(the stuff jascott1 added)16:19
sdakethe bestsolution i have is to make another service chart specifically for cell registration16:19
inc0it's ugly16:19
sdakethis is why the dream of helm install kolla-kubernetes is just a dream atm :)16:19
inc0ok, let's discuss it with Kevin and Serguey when they're back16:20
sdakesoundsgood16:20
sdakei've brought it up prior16:20
sdake"it works in the gate, nothign wrong"16:20
sdakehard to argue against...16:20
inc0maybe it's good time to ditch entrypoint and write it ourselves16:20
jascott1:)16:20
*** simon-AS559 has quit IRC16:20
sdake+10016:20
rwellumsdake: meantime a bug as inc0 suggested?16:20
inc0yeah16:21
sdakerwellum i guess - although kolla-kubernetes not really using bugs atm16:21
sdakealthough sould be16:21
inc0good time to start16:21
sdakeimplementation is mature enough for it16:21
sdakewould be nice to have sbezverk and kofx here for that discusison16:21
inc0entrypoint shouldn't be too hard to write (if we do it in python that is)16:21
sdakeagreed and we would have more control over the changes16:22
rwellumI'll hunt them down and get them involved.16:22
sdakeit seems to me that the entyrpoint upstream is dead16:22
sdake(i could be wrong, this is just my perception)16:22
inc0it is16:22
sdakewe shouldn't base any deps on a dead upstream imo16:22
sdakeno security, no mainteannce, no enhancements, etc16:23
inc0ok, let's get cracking on our new entrypoint...and for f* sake call it something else;)16:23
jascott1haha16:23
inc0k8s dep resolver or whatever16:23
sdakeneed someone to write the code16:23
rwellumcovfefe?16:24
inc0covfefe +116:24
sdakei am maxed out on capacity16:24
sdakeso i cna't do it :)16:24
inc0jascott1? you and me?16:24
jascott1sure16:24
sdakepersonally I htink the approach we should use for the short term is to get a deploy workign with microcharts16:24
inc0I could use some python programming for a change;)16:24
sdakeinc0 that sounds good to me :)16:24
sdakehowever a microchart approach has a short runway16:25
inc0we still need proper dep resolution16:25
sdakewe can do that in an ansible workflow wrapped in a container based on  microcharts16:25
inc0so make it work ugly asap and we'll get crackin' on covfefe-resolver16:25
sdakeand then improve it to service charts next16:25
rwelluminc0: +1 :)16:26
sdakei am also not convinced about entrypoint's ordering16:26
sdakeas you know inc0 many openstack services require upgrade in a specific order16:26
sdakeentrypoint - who knows what happens ;)16:26
inc0sdake: all ordering can be managed by proper dependency modelling16:26
sdakewhereas a microchart approach - ordering is forced16:26
*** baoli has quit IRC16:27
inc0I wanted to rewrite heat to use this algorithm16:27
inc0microchart has no ordering whatsoever unless manually16:27
sdakethere would need to be two orderings -one for deploy and one for upgrade16:27
sdakei think they are different - but not certain16:27
inc0covfefe-resolver is microchart orchiestration tool16:27
*** baoli has joined #openstack-meeting-416:27
inc0jascott1 another idea, don't you think that would make awesome addition to tiller?16:28
jascott1interesting idea16:28
inc0since it already manages dependency, just doing this naively16:28
inc0let's grab technosophos later and discuss that16:28
sdakenot familiar wtih the helm code - don't know how long that effort would take16:28
*** simon-AS5591 has quit IRC16:29
sdakei'd like to get to the point poeple can deploy in the next 3-4 weeks :)16:29
rwellumIt deploys - those pods just flap around like crazy a few times :)16:29
sdakerwellum by deploy - i mean error-free16:30
rwellumAha16:30
rwellumOk well that was it from me - glad that sdake sees it too.16:31
sdakerwellum yup i knew when that went it it wouldn't work :)16:31
rwellumDid you +1 then?16:31
sdakegate was green.16:31
inc0#action inc0 and jascott1 to figure it out;)16:31
sdakeshows the gate is imperfect16:31
rwellumI missed the review unfortunately16:32
inc0it's never perfect16:32
inc0ok anything else?16:32
sdakerwellum can you submit a revert patch for that change plz16:32
*** ltomasbo is now known as ltomasbo|away16:32
rwellumsdake: sure16:32
sdakerwellum thx :)16:32
inc0ok moving on:)16:33
sdakeone last thing16:33
inc0go ahead16:33
sdake(oh its related to mariadb)16:33
sdakedont' have agenda open - we can tackle it at end16:33
inc0yeah, it's open discussion now16:34
sdakeok16:34
inc0#topic open discussion16:34
*** openstack changes topic to "open discussion (Meeting topic: kolla)"16:34
sdakehere is plan for mariadb16:34
sdake1. backport sean's pin of mariadb ot stable/ocata16:34
sdakes we don't want  to upgrade mariadb in stable branches16:34
sdake2. use mariadb from rdo (which includes galera and xtrabackup-v2)16:35
sdakethis allows us to eject the percona and mariadb repos for centos16:35
inc0just to be clear, we're only talking about centos right?16:35
sdakeand gets us on a well maintained version of mariadb16:35
sdakeyes just centos16:35
sdakei don't know what ot do about ubuntu as i dont have it installed16:35
inc0pinning versions will only work if we make security updates work16:35
sdake1 is already done16:35
sdakeya everytime I see a pin I die a little inside16:36
inc0you must be pretty dead inside sdake then16:36
egonzalezbtw, just checked and mariadb included missing packages for 10.016:36
sdakeinc0 souless :(16:36
sdakeegonzalez for which distro?16:36
egonzalezcentos16:36
egonzalezhttps://yum.mariadb.org/10.0.30/centos7-amd64/rpms/16:37
inc0ah so they fixed their repo upstream?16:37
sdakeinc0 no, there is no security updates on 10.0.30 that i know of16:37
rwellumsdake: what are they symptoms of the mariadb issue?16:37
sdakeinc0 although thatis pure speculation16:37
sdakerwellum stable/ocata wasn't building16:37
rwellumah ok ty16:37
inc0well, I'm saying is 10.0.* not 10.0.3016:37
sdakeegonzalez 10.0 doesn't work right?16:38
egonzalez-w the backport pin change16:38
inc0https://yum.mariadb.org/10.0/centos/7.3/x86_64/rpms/ we have packages for 10.0.3116:38
*** rwallner has quit IRC16:38
egonzalezsdake, shoudl work now16:39
sdakecool so we can unpin?16:39
egonzalezyep16:39
inc0also if it's fix, let's unpin master16:39
inc0fixed16:39
sdakeinc0 agreed16:39
inc0cool, I'm glad16:39
sdakeinc0 although stable/ocata wasn't building16:39
sdakeand it was unpinned16:39
inc0sdake: let's try now16:39
sdakeand i rechecked 30 minutes ago16:39
inc0right16:40
egonzalezi rechecked a change now, lets see..16:40
sdakeegonzalez the 10.0.30 pin went into stable/ocata16:40
*** slaweq has joined #openstack-meeting-416:40
egonzalezwas not merged, -workflow  the change16:41
sdakei think the course of action that make sense is to revert the pin that sean produced, and see if the  gate blows up on master16:41
sdakeand then replace it later with rdo mariadb16:41
*** sambetts is now known as sambetts|afk16:42
sdakesounds like new coure of action is16:42
sdake1) unpin master16:42
sdake2) backport unpin if it works16:42
sdake3) replace master mariadb with rdo version16:42
sdakealso could use some mariadb nerds to help wti hthe rdo transition16:44
sdakethe extend_start.sh script is busted in master16:44
sdakeit never wroked16:44
sdakecould be why ubuntu packaging doesn't work as well16:45
sdakeanyway thats it - need help with mariadb plz :)16:45
*** slaweq has quit IRC16:45
inc0right16:45
inc0can we wrap up?16:45
duonghqo/16:46
duonghqhttps://blueprints.launchpad.net/kolla-ansible/+spec/enable-osprofiler16:46
inc0thank you all for coming!16:46
inc0ah16:46
inc0sorry16:46
inc0I thought you were waving goodbye;)16:46
duonghq:P, my fault16:46
duonghqwill we make the bp in P?16:47
duonghqI think it's not a complicated bp, but interesting one16:47
inc0do we want to make it default yes?16:47
duonghqegonzalez's one16:47
inc0is there anything bad that could happen from enabling it?16:47
duonghqyeah, it's resource hungry16:48
duonghqso it should be turned off by default16:48
inc0ok16:48
duonghqbut easy to turn on16:48
egonzalezi would say this change makes more sense for devs with pbourke_'s devstack change16:48
egonzalezmaybe for gates to have a better view of how resources work16:48
duonghqtracing is quite hot topic nowaday, not only for dev :)16:49
*** bobmel has joined #openstack-meeting-416:49
duonghqbut osprofiler has some interesting features in its design, we should choose some for implement or try to implement all of this?16:50
duonghqi.e. different hmac_key for different "trace path"16:50
inc0btw if it's resource hungry, that's actually good candidate to be rewritten in golang16:50
*** pcaruana has quit IRC16:50
inc0golang would totally shine in this use case16:51
egonzalezis resource hungry because need elasticsearch or all metering services to store traces16:51
*** emagana_ has quit IRC16:51
duonghqyep16:52
duonghqbut the main point I want to discuss is will we implement all of its nice option, or just some for beginning then improve latter16:52
duonghqany ideas?16:53
*** emagana has joined #openstack-meeting-416:53
inc0I'd split it into multiple patchsets if that's what you're asking16:53
inc0easier to merge/review16:53
egonzalezwhat you mean of nice option?16:53
duonghqi.e. HMAC_KEY16:53
duonghqegonzalez, in your implementation, you use only one HMAC_KEY,16:53
duonghqbut osprofiler let we ultilize HMAC_KEY as kind of path chooser16:54
duonghqI mean the path which osprofiler will trace in whole request processing sequence16:54
*** rwallner has joined #openstack-meeting-416:55
duonghqalso, we have some caveat for consider,16:55
duonghqcannot recall right now16:55
*** salv-orlando has quit IRC16:55
duonghqbut, summerize: they have option to let user configure tracing quite flexible16:56
duonghqanw, our time is running out?16:56
inc0yeah16:56
inc0I'll wrap it up:)16:56
inc0thank you all for coming!16:56
inc0#endmeeting kolla16:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:56
openstackMeeting ended Wed May 31 16:56:57 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-05-31-15.59.html16:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-05-31-15.59.txt16:57
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-05-31-15.59.log.html16:57
*** emagana has quit IRC16:57
*** rwallner has quit IRC16:58
*** hieulq_ has joined #openstack-meeting-416:59
*** wxy| has quit IRC16:59
*** unicell1 has quit IRC16:59
*** ralonsoh has quit IRC17:01
*** rwallner has joined #openstack-meeting-417:02
*** duonghq has quit IRC17:04
*** hieulq__ has joined #openstack-meeting-417:04
*** emagana has joined #openstack-meeting-417:06
*** caboucha has quit IRC17:07
*** baoli has quit IRC17:07
*** hieulq_ has quit IRC17:08
*** baoli has joined #openstack-meeting-417:08
*** egonzalez has quit IRC17:09
*** vishnoianil has joined #openstack-meeting-417:12
*** baoli has quit IRC17:13
*** baoli has joined #openstack-meeting-417:13
*** salmankhan has quit IRC17:15
*** Julien-zte has quit IRC17:23
*** Julien-zte has joined #openstack-meeting-417:24
*** karthiks has quit IRC17:24
*** unicell has joined #openstack-meeting-417:26
*** anilvenkata has joined #openstack-meeting-417:28
*** anilvenkata has quit IRC17:33
*** simon-AS559 has joined #openstack-meeting-417:35
*** simon-AS5591 has joined #openstack-meeting-417:38
*** hieulq__ has quit IRC17:39
*** simon-AS559 has quit IRC17:40
*** slaweq has joined #openstack-meeting-417:41
*** slaweq has quit IRC17:45
*** simon-AS5591 has quit IRC17:53
*** galstrom_zzz is now known as galstrom18:02
*** emagana has quit IRC18:08
*** Rockyg has quit IRC18:08
*** reedip_ has joined #openstack-meeting-418:17
*** iyamahat has joined #openstack-meeting-418:19
*** emagana has joined #openstack-meeting-418:20
*** emagana has quit IRC18:21
*** emagana has joined #openstack-meeting-418:21
*** slaweq has joined #openstack-meeting-418:42
*** krtaylor has quit IRC18:44
*** slaweq has quit IRC18:48
*** iyamahat_ has joined #openstack-meeting-418:59
*** qwebirc30842 has quit IRC19:00
*** adisky__ has quit IRC19:01
*** iyamahat has quit IRC19:01
*** dimak_ has joined #openstack-meeting-419:01
*** reedip_ has quit IRC19:02
*** iyamahat_ has quit IRC19:04
*** bobh has quit IRC19:07
*** rwallner has quit IRC19:12
*** rwallner has joined #openstack-meeting-419:16
*** rwallner_ has joined #openstack-meeting-419:17
*** rwallner has quit IRC19:21
*** yamamoto has quit IRC19:33
*** salmankhan has joined #openstack-meeting-419:35
*** krtaylor has joined #openstack-meeting-419:37
*** dimak_ has quit IRC19:37
*** egonzalez has joined #openstack-meeting-419:45
*** pcaruana has joined #openstack-meeting-419:45
*** rwallner_ has quit IRC19:53
*** mfedosin has quit IRC19:54
*** woodard_ has joined #openstack-meeting-419:58
*** salv-orlando has joined #openstack-meeting-420:00
*** jascott1 has quit IRC20:01
*** TxGirlGeek has quit IRC20:01
*** woodard has quit IRC20:02
*** pcaruana has quit IRC20:02
*** woodard_ has quit IRC20:02
*** salmankhan has quit IRC20:05
*** vishnoianil has quit IRC20:07
*** TxGirlGeek has joined #openstack-meeting-420:09
*** salv-orlando has quit IRC20:09
*** salv-orlando has joined #openstack-meeting-420:11
*** simon-AS559 has joined #openstack-meeting-420:12
*** TxGirlGeek has quit IRC20:13
*** TxGirlGeek has joined #openstack-meeting-420:15
*** simon-AS559 has quit IRC20:16
*** simon-AS559 has joined #openstack-meeting-420:17
*** TxGirlGeek has quit IRC20:18
*** yfauser has joined #openstack-meeting-420:21
*** yfauser has quit IRC20:21
*** yfauser has joined #openstack-meeting-420:22
*** cleong has quit IRC20:30
*** yamamoto has joined #openstack-meeting-420:33
*** TxGirlGeek has joined #openstack-meeting-420:34
*** iyamahat_ has joined #openstack-meeting-420:36
*** woodard has joined #openstack-meeting-420:37
*** ansmith has quit IRC20:39
*** woodard has quit IRC20:40
*** galstrom is now known as galstrom_zzz20:40
*** woodard has joined #openstack-meeting-420:40
*** salmankhan has joined #openstack-meeting-420:43
*** yamamoto has quit IRC20:43
*** slaweq has joined #openstack-meeting-420:45
*** slaweq has quit IRC20:50
*** rfolco has quit IRC20:53
*** galstrom_zzz is now known as galstrom20:55
*** TxGirlGeek has quit IRC21:06
*** TxGirlGeek has joined #openstack-meeting-421:07
*** bobh has joined #openstack-meeting-421:10
*** pcaruana has joined #openstack-meeting-421:12
*** rwallner has joined #openstack-meeting-421:14
*** TxGirlGeek has quit IRC21:14
*** TxGirlGeek has joined #openstack-meeting-421:15
*** salv-orlando has quit IRC21:16
*** thorst has quit IRC21:17
*** TxGirlGeek has quit IRC21:18
*** rwallner has quit IRC21:18
*** TxGirlGeek has joined #openstack-meeting-421:19
*** bobh has quit IRC21:21
*** vishnoianil has joined #openstack-meeting-421:21
*** harlowja has quit IRC21:21
*** TxGirlGeek has quit IRC21:28
*** yfauser has quit IRC21:28
*** yfauser has joined #openstack-meeting-421:29
*** pcaruana has quit IRC21:29
*** TxGirlGeek has joined #openstack-meeting-421:30
*** TxGirlGeek has quit IRC21:31
*** yfauser_ has joined #openstack-meeting-421:32
*** TxGirlGeek has joined #openstack-meeting-421:33
*** yfauser has quit IRC21:34
*** vishnoianil has quit IRC21:34
*** TxGirlGeek has quit IRC21:35
*** vishnoianil has joined #openstack-meeting-421:37
*** TxGirlGeek has joined #openstack-meeting-421:39
*** TxGirlGeek has quit IRC21:42
*** yfauser_ has quit IRC21:44
*** yfauser has joined #openstack-meeting-421:44
*** slaweq has joined #openstack-meeting-421:46
*** yfauser has quit IRC21:49
*** slaweq has quit IRC21:50
*** thorst has joined #openstack-meeting-421:56
*** salmankhan has quit IRC21:57
*** iyamahat_ has quit IRC22:04
*** harlowja has joined #openstack-meeting-422:06
*** neiljerram has quit IRC22:09
*** rockyg has joined #openstack-meeting-422:12
*** simon-AS559 has quit IRC22:17
*** klamath has quit IRC22:18
*** egonzalez has quit IRC22:21
*** TxGirlGeek has joined #openstack-meeting-422:22
*** rwellum has quit IRC22:31
*** iyamahat has joined #openstack-meeting-422:32
*** baoli has quit IRC22:34
*** yfauser has joined #openstack-meeting-422:34
*** galstrom is now known as galstrom_zzz22:35
*** baoli has joined #openstack-meeting-422:35
*** iyamahat has quit IRC22:37
*** limao has joined #openstack-meeting-422:39
*** yfauser has quit IRC22:39
*** baoli has quit IRC22:39
*** limao_ has joined #openstack-meeting-422:42
*** jose-phi_ has quit IRC22:42
*** lyan has quit IRC22:44
*** limao has quit IRC22:44
*** krtaylor has quit IRC22:46
*** slaweq has joined #openstack-meeting-422:47
*** jose-phillips has joined #openstack-meeting-422:50
*** slaweq has quit IRC22:51
*** Sukhdev has joined #openstack-meeting-422:52
*** yfauser has joined #openstack-meeting-422:59
*** rockyg has quit IRC22:59
*** yfauser has quit IRC23:04
*** thorst has quit IRC23:09
*** pmesserli has quit IRC23:12
*** thorst has joined #openstack-meeting-423:20
*** baoli has joined #openstack-meeting-423:32
*** iyamahat has joined #openstack-meeting-423:34
*** baoli_ has joined #openstack-meeting-423:34
*** baoli has quit IRC23:37
*** Julien-zte has quit IRC23:37
*** TxGirlGeek has quit IRC23:39
*** limao_ has quit IRC23:40
*** iyamahat has quit IRC23:41
*** limao has joined #openstack-meeting-423:44
*** slaweq has joined #openstack-meeting-423:47
*** limao has quit IRC23:50
*** slaweq has quit IRC23:52
*** emagana has quit IRC23:54

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