Wednesday, 2016-11-30

*** Swami_ has quit IRC00:00
*** galstrom_zzz is now known as galstrom00:05
*** sambetts|afk has quit IRC00:08
*** sambetts_ has joined #openstack-meeting-400:09
*** spotz is now known as spotz_zzz00:13
*** hongbin has quit IRC00:20
*** thorst_ has joined #openstack-meeting-400:21
*** thorst_ has quit IRC00:22
*** thorst_ has joined #openstack-meeting-400:23
*** thorst_ has quit IRC00:31
*** Swami has joined #openstack-meeting-400:32
*** Julien-zte has joined #openstack-meeting-400:35
*** Julien-zte has quit IRC00:35
*** Julien-zte has joined #openstack-meeting-400:35
*** haleyb__ has joined #openstack-meeting-400:36
*** edleafe- has joined #openstack-meeting-400:36
*** edleafe has quit IRC00:36
*** numans has quit IRC00:37
*** limao has joined #openstack-meeting-400:37
*** haleyb__ has quit IRC00:41
*** unicell has quit IRC00:48
*** Julien-zte has quit IRC00:49
*** Julien-zte has joined #openstack-meeting-400:50
*** Julien-zte has quit IRC00:56
*** Julien-zte has joined #openstack-meeting-400:57
*** bpokorny has quit IRC00:59
*** thorst_ has joined #openstack-meeting-401:06
*** uck has quit IRC01:06
*** chigang has joined #openstack-meeting-401:07
*** dave-mccowan has joined #openstack-meeting-401:07
*** Julien-zte has quit IRC01:11
*** uck has joined #openstack-meeting-401:12
*** reedip_ has joined #openstack-meeting-401:12
*** thorst_ has quit IRC01:13
*** zhurong has joined #openstack-meeting-401:14
*** tovin07_ has quit IRC01:16
*** uck has quit IRC01:17
*** Julien-zte has joined #openstack-meeting-401:17
*** baoli has joined #openstack-meeting-401:18
*** Julien-zte has quit IRC01:19
*** baoli has quit IRC01:19
*** baoli has joined #openstack-meeting-401:19
*** Swami_ has joined #openstack-meeting-401:22
*** Swami has quit IRC01:22
*** galstrom is now known as galstrom_zzz01:24
*** Syed has quit IRC01:26
*** spzala has quit IRC01:27
*** ricolin has joined #openstack-meeting-401:32
*** Zer0Byte__ has quit IRC01:35
*** haleyb__ has joined #openstack-meeting-401:37
*** bobmel has joined #openstack-meeting-401:38
*** Swami_ has quit IRC01:40
*** haleyb__ has quit IRC01:42
*** apuimedo is now known as apuimedo|away01:42
*** bobmel has quit IRC01:42
*** bpokorny has joined #openstack-meeting-401:51
*** bpokorny has quit IRC01:51
*** bpokorny has joined #openstack-meeting-401:52
*** thorst_ has joined #openstack-meeting-401:55
*** bpokorny has quit IRC01:58
*** bpokorny has joined #openstack-meeting-402:02
*** chem has quit IRC02:02
*** thorst_ has quit IRC02:02
*** chem has joined #openstack-meeting-402:03
*** sdake has quit IRC02:07
*** bpokorny_ has joined #openstack-meeting-402:15
*** sdake has joined #openstack-meeting-402:15
*** tovin07 has joined #openstack-meeting-402:16
*** tovin07_ has joined #openstack-meeting-402:18
*** rbak has quit IRC02:18
*** bpokorny has quit IRC02:18
*** bpokorny_ has quit IRC02:20
*** hongbin has joined #openstack-meeting-402:21
*** hongbin has quit IRC02:32
*** haleyb__ has joined #openstack-meeting-402:38
*** thorst_ has joined #openstack-meeting-402:39
*** thorst_ has quit IRC02:40
*** baoli has quit IRC02:41
*** haleyb__ has quit IRC02:42
*** sdake_ has joined #openstack-meeting-402:49
*** reedip_ has quit IRC02:52
*** sdake has quit IRC02:52
*** zhurong_ has joined #openstack-meeting-402:53
*** bobmel has joined #openstack-meeting-402:53
*** zhurong has quit IRC02:55
*** chandanc has joined #openstack-meeting-402:56
*** s3wong has quit IRC02:56
*** bobmel has quit IRC02:58
*** links has joined #openstack-meeting-403:28
*** vishnoianil has quit IRC03:31
*** haleyb__ has joined #openstack-meeting-403:39
*** Julien-zte has joined #openstack-meeting-403:40
*** haleyb__ has quit IRC03:43
*** tlbr has quit IRC03:44
*** thorst_ has joined #openstack-meeting-403:45
*** tlbr has joined #openstack-meeting-403:45
*** Julien-zte has quit IRC03:49
*** Julien-zte has joined #openstack-meeting-403:49
*** thorst_ has quit IRC03:52
*** psachin has joined #openstack-meeting-404:01
*** Julien-zte has quit IRC04:01
*** numans has joined #openstack-meeting-404:06
*** Marcellin__ has quit IRC04:08
*** dave-mccowan has quit IRC04:14
*** hieulq_ has joined #openstack-meeting-404:17
*** hieulq_ has quit IRC04:21
*** yamamoto_ has quit IRC04:24
*** hongbin has joined #openstack-meeting-404:30
*** hongbin has quit IRC04:30
*** prateek has joined #openstack-meeting-404:31
*** baoli has joined #openstack-meeting-404:32
*** yamahata has quit IRC04:35
*** bobh has quit IRC04:36
*** Jeffrey4l has quit IRC04:46
*** unicell has joined #openstack-meeting-404:52
*** prateek has quit IRC04:53
*** prateek has joined #openstack-meeting-404:54
*** bobmel has joined #openstack-meeting-404:54
*** unicell1 has joined #openstack-meeting-404:56
*** unicell has quit IRC04:57
*** bobmel has quit IRC04:59
*** Jeffrey4l has joined #openstack-meeting-404:59
*** sdake_ has quit IRC05:00
*** yamamoto_ has joined #openstack-meeting-405:08
*** thorst_ has joined #openstack-meeting-405:11
*** thorst_ has quit IRC05:20
*** Julien-zte has joined #openstack-meeting-405:29
*** anilvenkata has joined #openstack-meeting-405:33
*** bobh has joined #openstack-meeting-405:36
*** Julien-zte has quit IRC05:37
*** Julien-zte has joined #openstack-meeting-405:38
*** haleyb__ has joined #openstack-meeting-405:41
*** bobh has quit IRC05:41
*** haleyb__ has quit IRC05:46
*** Julien-zte has quit IRC05:54
*** Julien-zte has joined #openstack-meeting-405:54
*** revon has quit IRC06:02
*** zhihui has joined #openstack-meeting-406:14
*** trinaths has joined #openstack-meeting-406:17
*** thorst_ has joined #openstack-meeting-406:18
*** Julien-zte has quit IRC06:19
*** Julien-zte has joined #openstack-meeting-406:20
*** Julien-zte has quit IRC06:21
*** Julien-zte has joined #openstack-meeting-406:22
*** thorst_ has quit IRC06:25
*** yamahata has joined #openstack-meeting-406:26
*** armax has quit IRC06:27
*** Julien-zte has quit IRC06:28
*** Julien-zte has joined #openstack-meeting-406:29
*** Julien-zte has quit IRC06:38
*** Julien-z_ has joined #openstack-meeting-406:38
*** anilvenkata has quit IRC06:39
*** haleyb__ has joined #openstack-meeting-406:42
*** psachin_ has joined #openstack-meeting-406:42
*** psachin has quit IRC06:45
*** haleyb__ has quit IRC06:47
*** Julien-z_ has quit IRC06:47
*** Julien-zte has joined #openstack-meeting-406:48
*** Julien-zte has quit IRC06:49
*** Julien-zte has joined #openstack-meeting-406:50
*** Julien-zte has quit IRC06:50
*** Julien-zte has joined #openstack-meeting-406:51
*** Julien-zte has quit IRC06:53
*** chem has quit IRC06:53
*** Julien-zte has joined #openstack-meeting-406:55
*** zenoway has joined #openstack-meeting-407:00
*** zenoway has quit IRC07:00
*** zenoway has joined #openstack-meeting-407:00
*** Julien-zte has quit IRC07:00
*** Julien-zte has joined #openstack-meeting-407:01
*** Julien-zte has quit IRC07:01
*** Julien-zte has joined #openstack-meeting-407:02
*** Julien-zte has quit IRC07:05
*** Julien-zte has joined #openstack-meeting-407:07
*** gongysh has joined #openstack-meeting-407:10
*** irenab has joined #openstack-meeting-407:20
*** thorst_ has joined #openstack-meeting-407:24
*** thorst_ has quit IRC07:29
*** Julien-zte has quit IRC07:31
*** Julien-zte has joined #openstack-meeting-407:32
*** hieulq_ has joined #openstack-meeting-407:32
*** zhihui has quit IRC07:36
*** bobh has joined #openstack-meeting-407:38
*** bobh has quit IRC07:42
*** haleyb__ has joined #openstack-meeting-407:43
*** Julien-zte has quit IRC07:43
*** Julien-zte has joined #openstack-meeting-407:44
*** haleyb__ has quit IRC07:48
*** zhihui has joined #openstack-meeting-407:49
*** matrohon has joined #openstack-meeting-407:50
*** Julien-zte has quit IRC07:51
*** Julien-zte has joined #openstack-meeting-407:52
*** iyamahat has joined #openstack-meeting-407:52
*** apuimedo|away is now known as apuimedo07:55
*** dwj has joined #openstack-meeting-407:56
*** trinaths has quit IRC07:58
*** ifat_afek has joined #openstack-meeting-407:59
*** zhihui has quit IRC07:59
*** eyalb has joined #openstack-meeting-407:59
*** Julien-zte has quit IRC08:00
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Nov 30 08:00:14 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: vitrage)"08:00
openstackThe meeting name has been set to 'vitrage'08:00
ifat_afekHi everyone :-)08:00
*** alexey_weyl has joined #openstack-meeting-408:00
*** Julien-zte has joined #openstack-meeting-408:00
eyalbhi08:00
alexey_weylHello there08:01
*** elisha_r has joined #openstack-meeting-408:02
*** ifat_afek has left #openstack-meeting-408:02
*** ifat_afek has joined #openstack-meeting-408:03
*** yujunz has joined #openstack-meeting-408:03
*** limao has quit IRC08:03
elisha_rhi08:03
*** nofarsch has joined #openstack-meeting-408:03
*** iyamahat has quit IRC08:03
ifat_afek#topic plans for Ocata08:03
*** openstack changes topic to "plans for Ocata (Meeting topic: vitrage)"08:03
ifat_afeklet’s start by talking about Ocata. I have some suggestions, will be happy to hear yours08:04
*** zhurong_ has quit IRC08:04
nofarschhi guys!08:04
ifat_afekTop priority: We should finish the integration with RedHat, so we will have vitrage rpms ready08:04
*** zhurong has joined #openstack-meeting-408:04
*** trofoti has joined #openstack-meeting-408:05
trofotiHi guys08:05
*** Julien-zte has quit IRC08:05
ifat_afekIntegrations with other proejcts are also very important. Aodh for example - we want to be able to show Vitrage alarms in Aodh08:05
ifat_afekAnother integration is with collectd and DPDK08:05
*** Julien-zte has joined #openstack-meeting-408:06
*** links has quit IRC08:06
ifat_afekWe must complete our commitments to OPNFV Doctor project. We should install Vitrage as part of OPNFV installers (Apex should be the first one), and add Vitrage test scripts to OPNFV testing environment08:06
*** shizhihui_ has joined #openstack-meeting-408:07
*** trinaths has joined #openstack-meeting-408:07
ifat_afekWe should improve Vitrage UI, mainly the entity graph08:07
ifat_afekAnd support multi-tenancy in the UI. It is partially supported already, but we need to add for example Vitrage menu to Admin08:08
*** Julien-zte has quit IRC08:08
ifat_afekAnd obviously - we should add more use cases to Vitrage. We can explore existing Zabbix alarms, and think of ways to add deduced alarms and RCA on top08:08
*** idan_hefetz has joined #openstack-meeting-408:08
*** amotoki has joined #openstack-meeting-408:08
*** amotoki has quit IRC08:08
*** Julien-zte has joined #openstack-meeting-408:09
*** yfauser has joined #openstack-meeting-408:09
ifat_afekAnother important goal is to add a persistent graph database, in favor of HA support and alarm history. As this requires a lot of work and Ocata is a very short cycle, I’m not sure we’ll be able to complete this.08:09
*** Julien-zte has quit IRC08:09
*** shizhihui_ has quit IRC08:09
ifat_afekYour comments? other ideas?08:09
elisha_rifat_afek: sounds good08:09
*** yfauser has quit IRC08:09
alexey_weylGreat success!08:10
*** Julien-zte has joined #openstack-meeting-408:10
elisha_rI think making vitrage more compatible with all these projects is critical, to help vitrage become more embedded in the community. The DPDK is also very good when thinking about OPNFV context.08:11
ifat_afekelisha_r: I agree08:11
trinathselisha_r: +108:12
alexey_weylmulti tenancy already supported in Vitrage, but08:13
alexey_weylin the horizon at the moment we need to add in the system tab to be able to show all the alarms of all the tennats, and all the whole entity_graph of all the tenants08:14
ifat_afekalexey_weyl: right. thanks for the clarification08:15
alexey_weylbasically our main goals are to add a persistent graph and history on top of this graph.08:15
*** Julien-zte has quit IRC08:16
eyalbwhat about supporting sensu ?08:16
alexey_weylalso to add database that will store the templates08:16
*** dtardivel has joined #openstack-meeting-408:16
ifat_afekeyalb: is there a request for that?08:16
eyalbredhat guys suggested it08:16
ifat_afekeyalb: ok. I guess adding another datasource is not a lot of work08:17
alexey_weyland also to handle the new vitrage_id that will more like a UUID and not what we have today08:17
ifat_afekthe new vitrage_id is very important indeed08:17
alexey_weyleyalb: the only problem to add such a datasource is to find out how exactly it works, and what we can extract from it08:18
*** links has joined #openstack-meeting-408:19
eyalbits a monitoring tool #link https://sensuapp.org/08:19
*** Julien-zte has joined #openstack-meeting-408:19
*** Julien-zte has quit IRC08:19
trofoti@danoffek is currently working on Vitrage ID08:19
*** ralonsoh has joined #openstack-meeting-408:19
*** limao has joined #openstack-meeting-408:19
eyalbit is designed to replace nagios and zabbix08:19
*** Julien-zte has joined #openstack-meeting-408:19
*** Julien-zte has quit IRC08:20
eyalbfrom their site: Sensu allows you to reuse monitoring checks and plugins from legacy monitoring tools like Nagios, Icinga, Zabbix, and many more. Sensu was designed from day one as a replacement for an aging Nagios installation, and to this day monitoring plugin compatibility remains as one of Sensu's most compelling features08:20
*** Julien-zte has joined #openstack-meeting-408:20
ifat_afekeyalb: sounds great08:21
ifat_afeklet’s consider it then08:21
ifat_afek#topic Status and Updates08:22
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:22
ifat_afekI’m working on a bug with the evaluator08:22
ifat_afek#link https://bugs.launchpad.net/vitrage/+bug/164565908:22
openstackLaunchpad bug 1645659 in Vitrage "template actions override one another" [High,In progress] - Assigned to Ifat Afek (ifat-afek)08:22
ifat_afekturns out that if a scenario has both set-state and mark-down actions, the second one “wins” and the changes of the first one are overwritten. I’m trying to figure out why it happens08:22
*** Jeffrey4l has quit IRC08:22
ifat_afekThat’s it on my side08:22
alexey_weylI will update08:23
*** Jeffrey4l has joined #openstack-meeting-408:23
alexey_weylI have done some name changes in the constants file.08:23
*** Julien-zte has quit IRC08:23
alexey_weylwe have changed the sync_type to datasource_action08:24
alexey_weylsync_mode to graph_action08:24
*** Julien-zte has joined #openstack-meeting-408:24
alexey_weylso it will be more clear and understandable what each one of them means08:24
ifat_afekalexey_weyl: I think it significantly improved the code readability08:25
*** Julien-zte has quit IRC08:25
alexey_weylI am glad :)08:25
eyalbI will update08:25
eyalbI added a support for osc in the vitrage client08:25
*** Julien-zte has joined #openstack-meeting-408:26
eyalbI fixed the devstack installation of the vitrage dashboard08:26
*** thorst_ has joined #openstack-meeting-408:26
eyalband updated the bash completion file of the vitrage client08:26
ifat_afekeyalb: osc is openstack client?08:26
eyalbthats all08:26
eyalbyes08:27
ifat_afekgreat08:27
alexey_weylAbout the persistent graph which is going to be in Ocata, I think that we should use neo4j for that.08:27
*** Julien-zte has quit IRC08:27
alexey_weylNeo4j has a community and many companies use it.08:27
ifat_afekneo4j is probably a good option. we should check what it means to use it in openstack, since I don’t think it is there yet08:27
*** Julien-zte has joined #openstack-meeting-408:28
alexey_weylIt also has very nice python plugins08:28
alexey_weylIt isn't in Openstack, and need to see how we push it in08:28
ifat_afekright, we should make sure there is no license issue08:29
ifat_afekanyone else has updates?08:29
dwjI'll update08:29
dwjI finished the code about getting aodh alarm notification, ongoing add the test case.08:29
dwjStill have a issue to improve: may lost notification messaging. How to remedy it, synchronize with snapshot peroidly or something else?  It's a little probability. We can improve it after supporting the function08:29
*** Julien-zte has joined #openstack-meeting-408:30
ifat_afekdwj: thanks for the first change, I think it improved the code08:30
ifat_afekas for the second issue - can you ellaborate?08:30
*** makowals_ has joined #openstack-meeting-408:30
*** makowals_ has quit IRC08:31
dwjfor example, if we lost alarm.creation notification, the receive another notification about the alrm08:31
ifat_afekso you mean we will not know the details of the alarm, if we missed its creation?08:32
dwjwe can't get all the alarm info for update  the vertex08:32
ifat_afekthat’s a problem, I agree08:32
*** nbloom has joined #openstack-meeting-408:32
dwjyes08:32
ifat_afekget_all will fix it, but it happens only once in about 10 minutes I think08:32
*** makowals has quit IRC08:33
ifat_afekfrom your experience, does it happen that notifications get lost? because if we start with get_all, and then listen to all notifications, it should be ok, right?08:33
dwjNo,it doesn't happen,but it is still a issue to consider08:34
*** thorst_ has quit IRC08:34
ifat_afekbut if you never seen it happen, then why consider it? I agree that it can be a bug, but if it is a rare occasion then maybe it will be good enough to fix it by the next get_all after a few minutes08:35
ifat_afekI’m just trying to understand if you have a specific use case you are worried about. You are right for being worried, but I am trying to understand how often we should expect it to happen08:37
dwjListenerService should synchronize with snapshotService for get_all, the update the cached alarms08:38
ifat_afekyou suggest this as a solution?08:38
*** gongysh has quit IRC08:39
*** Julien-zte has quit IRC08:39
*** Julien-zte has joined #openstack-meeting-408:40
dwjyes, it can be a solution, or when we can't find the alarm in cache,we can query to aodh08:40
ifat_afekok, I think it may work08:41
ifat_afekgetting notification from Aodh is very important, thanks for taking care of it :-)08:42
dwjno problem. :)08:42
ifat_afekany other issues?08:43
*** Julien-zte has quit IRC08:43
*** haleyb__ has joined #openstack-meeting-408:44
dwjNo08:44
*** makowals has joined #openstack-meeting-408:44
ifat_afekanyone else would like to update?08:44
*** Julien-zte has joined #openstack-meeting-408:44
*** Julien-zte has quit IRC08:46
*** diga has joined #openstack-meeting-408:46
*** Julien-zte has joined #openstack-meeting-408:46
ifat_afekgoodbye then, see you next week08:46
ifat_afek#endmeeting08:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:47
openstackMeeting ended Wed Nov 30 08:47:02 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-11-30-08.00.html08:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-11-30-08.00.txt08:47
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-11-30-08.00.log.html08:47
*** numans has quit IRC08:47
*** nofarsch has quit IRC08:47
*** Julien-zte has quit IRC08:49
*** haleyb__ has quit IRC08:49
*** Julien-zte has joined #openstack-meeting-408:49
*** Julien-zte has quit IRC08:51
*** Julien-zte has joined #openstack-meeting-408:51
*** Julien-zte has quit IRC08:54
*** Julien-zte has joined #openstack-meeting-408:55
*** bobmel has joined #openstack-meeting-408:56
*** Julien-zte has quit IRC08:58
diga#openstack-kuryr08:59
*** Julien-zte has joined #openstack-meeting-408:59
*** numans has joined #openstack-meeting-409:00
*** bobmel has quit IRC09:00
*** Julien-zte has quit IRC09:03
*** zxen has joined #openstack-meeting-409:03
*** Julien-zte has joined #openstack-meeting-409:04
*** numans has quit IRC09:04
*** Julien-zte has quit IRC09:04
*** Julien-zte has joined #openstack-meeting-409:05
*** oshidoshi has joined #openstack-meeting-409:06
*** Julien-zte has quit IRC09:07
*** Julien-zte has joined #openstack-meeting-409:07
*** yamahata has quit IRC09:09
*** dwj has quit IRC09:12
*** Julien-zte has quit IRC09:13
*** Julien-zte has joined #openstack-meeting-409:13
*** yujunz has quit IRC09:15
*** alexey_weyl has quit IRC09:15
*** Julien-zte has quit IRC09:17
*** Julien-zte has joined #openstack-meeting-409:18
*** Julien-zte has quit IRC09:20
*** Julien-zte has joined #openstack-meeting-409:21
*** hieulq_ has quit IRC09:21
*** hieulq_ has joined #openstack-meeting-409:24
*** Julien-zte has quit IRC09:24
*** hieulq_ has quit IRC09:26
*** hieulq_ has joined #openstack-meeting-409:28
*** baoli_ has joined #openstack-meeting-409:31
*** thorst_ has joined #openstack-meeting-409:33
*** baoli has quit IRC09:33
*** 14WAANMV5 has joined #openstack-meeting-409:35
*** notmyname has quit IRC09:38
*** thorst_ has quit IRC09:39
*** nbloom has quit IRC09:39
*** notmyname has joined #openstack-meeting-409:40
*** bobh has joined #openstack-meeting-409:40
*** 14WAANMV5 is now known as asettle09:41
*** ifat_afek has quit IRC09:42
*** bobh has quit IRC09:44
*** ifat_afek has joined #openstack-meeting-409:44
*** ifat_afek has left #openstack-meeting-409:44
*** zxen has quit IRC09:51
*** zenoway has quit IRC09:54
*** chem has joined #openstack-meeting-409:57
*** derekjhyang has joined #openstack-meeting-409:59
*** tovin07_ has quit IRC10:02
*** zhurong has quit IRC10:02
*** links has quit IRC10:05
*** janki has joined #openstack-meeting-410:07
*** britthouser2 has joined #openstack-meeting-410:15
*** hieulq_ has quit IRC10:16
*** baoli has joined #openstack-meeting-410:16
*** ricolin has quit IRC10:16
*** shizhihui_ has joined #openstack-meeting-410:17
*** shizhihui_ is now known as zhihui10:18
*** pbourke_ has joined #openstack-meeting-410:18
*** fkautz has quit IRC10:19
*** logan- has quit IRC10:19
*** anteaya has quit IRC10:19
*** notmyname has quit IRC10:19
*** baoli_ has quit IRC10:19
*** betherly has quit IRC10:19
*** britthouser has quit IRC10:19
*** pcarver has quit IRC10:19
*** sambetts_ has quit IRC10:19
*** bnemec has quit IRC10:19
*** pbourke has quit IRC10:19
*** hughhalf has quit IRC10:19
*** briancurtin has quit IRC10:19
*** Adri2000 has quit IRC10:19
*** darrenc has quit IRC10:19
*** jschwarz has quit IRC10:19
*** mfisch has quit IRC10:19
*** palendae has quit IRC10:19
*** dhellmann has quit IRC10:19
*** morgabra has quit IRC10:19
*** sp_ has quit IRC10:19
*** darrenc has joined #openstack-meeting-410:20
*** logan- has joined #openstack-meeting-410:20
*** pcarver has joined #openstack-meeting-410:20
*** bnemec has joined #openstack-meeting-410:21
*** fkautz has joined #openstack-meeting-410:21
*** links has joined #openstack-meeting-410:22
*** mfisch has joined #openstack-meeting-410:22
*** mfisch has quit IRC10:23
*** mfisch has joined #openstack-meeting-410:23
*** janonymous_ has joined #openstack-meeting-410:23
*** dhellmann has joined #openstack-meeting-410:23
*** briancurtin has joined #openstack-meeting-410:24
*** meteorfox_ has joined #openstack-meeting-410:24
*** eyalb has left #openstack-meeting-410:24
*** limao_ has joined #openstack-meeting-410:25
*** alanmeadows_ has joined #openstack-meeting-410:25
*** markmcclain has quit IRC10:25
*** alanmeadows has quit IRC10:25
*** meteorfox has quit IRC10:25
*** vkmc has quit IRC10:25
*** janonymous has quit IRC10:25
*** Daviey has quit IRC10:25
*** spotz_zzz has quit IRC10:25
*** sgordon has quit IRC10:25
*** alex_xu has quit IRC10:25
*** makowals has quit IRC10:25
*** limao has quit IRC10:25
*** sambetts_ has joined #openstack-meeting-410:25
*** notmyname has joined #openstack-meeting-410:25
*** janonymous_ is now known as janonymous10:25
*** meteorfox_ is now known as meteorfox10:25
*** alanmeadows_ is now known as alanmeadows10:26
*** hughhalf has joined #openstack-meeting-410:26
*** makowals has joined #openstack-meeting-410:26
*** spotz_zzz has joined #openstack-meeting-410:26
*** markmcclain has joined #openstack-meeting-410:26
*** sambetts_ is now known as sambetts10:26
*** sgordon has joined #openstack-meeting-410:26
*** jschwarz has joined #openstack-meeting-410:26
*** limao_ has quit IRC10:27
*** alex_xu has joined #openstack-meeting-410:27
*** palendae has joined #openstack-meeting-410:27
*** palendae is now known as Guest4629910:27
*** vkmc has joined #openstack-meeting-410:27
*** diga has quit IRC10:28
*** Adri2000 has joined #openstack-meeting-410:28
*** morgabra has joined #openstack-meeting-410:29
*** anteaya has joined #openstack-meeting-410:31
*** pcaruana has joined #openstack-meeting-410:35
*** Daviey has joined #openstack-meeting-410:36
*** betherly has joined #openstack-meeting-410:36
*** betherly has quit IRC10:36
*** betherly has joined #openstack-meeting-410:36
*** thorst_ has joined #openstack-meeting-410:36
*** psachin_ has quit IRC10:40
*** psachin has joined #openstack-meeting-410:40
*** thorst_ has quit IRC10:45
*** haleyb__ has joined #openstack-meeting-410:46
*** psachin_ has joined #openstack-meeting-410:47
*** psachin has quit IRC10:48
*** chandanc has quit IRC10:49
*** haleyb__ has quit IRC10:51
*** alexchadin has joined #openstack-meeting-410:52
*** irenab has quit IRC10:58
*** janki has quit IRC11:05
*** links has quit IRC11:07
*** links has joined #openstack-meeting-411:08
*** alexchadin has quit IRC11:14
*** alexchadin has joined #openstack-meeting-411:14
*** bobmel has joined #openstack-meeting-411:15
*** bobmel has quit IRC11:20
*** bobmel has joined #openstack-meeting-411:20
*** alexchadin has quit IRC11:22
*** mchiappero has left #openstack-meeting-411:24
*** idan_hefetz has left #openstack-meeting-411:32
*** trofoti has left #openstack-meeting-411:32
*** irenab has joined #openstack-meeting-411:35
*** dave-mccowan has joined #openstack-meeting-411:37
*** zxen has joined #openstack-meeting-411:37
*** psachin_ has quit IRC11:39
*** zxen has quit IRC11:42
*** bobmel has quit IRC11:42
*** thorst_ has joined #openstack-meeting-411:43
*** zxen has joined #openstack-meeting-411:43
*** bobmel has joined #openstack-meeting-411:43
*** psachin has joined #openstack-meeting-411:43
*** haleyb__ has joined #openstack-meeting-411:47
*** elisha_r has quit IRC11:48
*** thorst_ has quit IRC11:49
*** rtheis has joined #openstack-meeting-411:49
*** zxen has quit IRC11:50
*** eil397 has joined #openstack-meeting-411:52
*** haleyb__ has quit IRC11:52
*** tinwood has quit IRC12:04
*** tinwood has joined #openstack-meeting-412:05
*** thorst_ has joined #openstack-meeting-412:07
*** sdake has joined #openstack-meeting-412:07
*** chigang has quit IRC12:11
*** thorst_ has quit IRC12:11
*** baoli_ has joined #openstack-meeting-412:20
*** baoli has quit IRC12:22
*** limao has joined #openstack-meeting-412:24
*** trinaths has quit IRC12:27
*** prateek has quit IRC12:28
*** makowals_ has joined #openstack-meeting-412:31
*** links has quit IRC12:34
*** makowals has quit IRC12:34
*** makowals has joined #openstack-meeting-412:43
*** makowals_ has quit IRC12:45
*** jichen has joined #openstack-meeting-412:46
*** haleyb__ has joined #openstack-meeting-412:48
*** haleyb__ has quit IRC12:53
*** thorst_ has joined #openstack-meeting-412:53
*** kylek3h has quit IRC12:54
*** claudiub|2 has joined #openstack-meeting-412:56
*** yamamoto_ has quit IRC12:59
*** cdent has joined #openstack-meeting-413:00
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Nov 30 13:00:12 2016 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: nova api)"13:00
openstackThe meeting name has been set to 'nova_api'13:00
alex_xuwho is here today?13:00
cdento/13:00
alex_xuI guess johnthetubaguy is going to lunch13:01
*** claudiub|2 is now known as claudiub13:01
alex_xuwait few more minutes13:01
jicheno/13:01
johnthetubaguysorry, yeah, back online13:02
alex_xucool13:02
alex_xudaylight saving changed again, so I guess the meeting is right on your lunch time13:03
johnthetubaguyyeah, its 1pm, which is right at the end of my usual lunch13:03
alex_xuheh13:03
johnthetubaguyI should remember to actually have lunch on time on a wednesday, my bad13:04
alex_xuso the only topic I have for now is the spec https://review.openstack.org/39320513:04
alex_xujohnthetubaguy: no worries13:04
johnthetubaguyits way better time than for most folks, so I certainly can't complain!13:04
*** bobmel has quit IRC13:04
alex_xujohnthetubaguy: but you should lunch on time for health13:04
johnthetubaguythats true :)13:05
*** bobmel has joined #openstack-meeting-413:05
johnthetubaguyI skip some things for work, food is not one of those13:05
alex_xu:)13:05
alex_xufor the spec, currently found that the sort can't get any help from db index13:05
* cdent has not yet had breakfast or lunch :(13:06
alex_xucdent: !13:06
cdentI got distracted :)13:06
* cdent blames johnthetubaguy 13:06
cdent(but not really)13:06
johnthetubaguyheh13:06
alex_xuheh13:06
jichen:)13:06
alex_xuI got feedback from jay, keep focus on the filters with index. just good luck for sort13:07
alex_xuso two choices: 1. keep all the sort whatever they can't get help from index. 2. continue to remove those sort with rarely use-case13:08
alex_xuor any better choice13:09
johnthetubaguyI am still thinking it through13:10
johnthetubaguywhat do we do today, add lots of different sorts, whatever the user says?13:11
alex_xui don't know13:12
*** bobmel has quit IRC13:12
*** bobmel has joined #openstack-meeting-413:13
johnthetubaguyhttps://github.com/openstack/nova/blob/master/nova/api/openstack/compute/servers.py#L110313:13
alex_xujohnthetubaguy: those are filters13:14
*** caowei has joined #openstack-meeting-413:15
johnthetubaguyyeah, sorry13:15
johnthetubaguyhttps://github.com/openstack/nova/blob/master/nova/api/openstack/compute/servers.py#L33013:15
alex_xujohnthetubaguy: you mean?13:16
johnthetubaguyhttps://github.com/openstack/nova/blob/master/nova/api/openstack/common.py#L14513:16
johnthetubaguyso I guess we allow *anything* for sort params right now13:16
johnthetubaguyand we allow mulitple13:16
alex_xuyes13:17
johnthetubaguywould it be simpler to just have the same list for filtering and sorting?13:17
alex_xuthere is no different for allow one or multiple, they can't get benefit from index anyway13:18
johnthetubaguyoh, OK, it does just the one sort run I guess13:18
alex_xujohnthetubaguy: yea,it can be similar list. But filter with uuid is useful. sort with uuid is useless.13:18
johnthetubaguywhy?13:19
johnthetubaguyI mean why is sorting with uuid useless? its a choice I guess13:19
*** Julien-zte has joined #openstack-meeting-413:20
alex_xusort on random generated uuid, sounds like useless13:20
johnthetubaguywhat I mean really is, someone could be doing that today, and we probably shouldn't break them13:20
alex_xuif the rule is 'don't break them', that confuse me also :)13:21
johnthetubaguywell I want to only break them, if we are protecting people from something bad13:21
alex_xujohnthetubaguy: all the sort is bad13:21
johnthetubaguysorting on something thats not returned in the API with the same key, is silly13:22
alex_xunone of them can get benefit from index13:22
alex_xuah, +1 for that point, yea13:22
*** kylek3h has joined #openstack-meeting-413:22
johnthetubaguyso we protect them form accidentally being tied to the DB model rather than the API, thats a good step forward here13:22
alex_xuwe don't have mapping for display_name=>name, that is another bad thing.13:23
johnthetubaguyyeah, that should be fixed13:23
johnthetubaguywell allowing both13:23
alex_xufix in the spec or later?13:23
alex_xuok13:23
johnthetubaguyalthough that needs a microversion, in theory, so maybe leave that for later13:24
johnthetubaguyyuck, I hate how complicated our past is making all this13:24
johnthetubaguyanyways... baby steps forward here13:24
alex_xui hate also :)13:25
johnthetubaguylonger term, we can add discoverable policy around sort, and encourage folks to use searchlight instead I guess13:25
alex_xuyea13:25
johnthetubaguybut for now, folks really seem to rely on sorting, so its here to stay13:25
johnthetubaguyI think restricting sort and filtering to the same set seems like a minimal level of protection, thats better than the current free for all, but shouldn't break everyone?13:26
alex_xujohnthetubaguy: just one question, so for small size deployment, to use searchlight looks like overhead, so just keep nova native sort for them in the future?13:26
alex_xureally not sure 'break', we can't ensure what people use13:27
johnthetubaguyscratch that last one13:27
johnthetubaguywe should just call searchlight I guess13:27
johnthetubaguyeventually13:27
alex_xuok, leave the burden to the deployment tools, hope deployment tools can ease the pain of people :)13:29
*** karthiks has quit IRC13:29
johnthetubaguywell, I guess I mean the small deployments can just use the DB13:30
johnthetubaguyelasticsearch is great, but you do need to feed it memory, from what I remember13:30
johnthetubaguyanyways, we got a bit distracted13:31
alex_xujohnthetubaguy: ok,then I'm little prefer to keep sort key which can mapping to the API13:31
johnthetubaguyI think people rely on us doing sort right now, so we can't remove that13:31
alex_xuwe can control that with policy in the future13:31
johnthetubaguyyeah13:31
johnthetubaguypossibly13:31
*** woodard has joined #openstack-meeting-413:33
alex_xujohnthetubaguy: yea, that what i thought, we just remove the bad thing. the sort can't get benefit from index, so enable one sort key or enable ten sort keys is same13:33
*** woodard has quit IRC13:33
*** woodard has joined #openstack-meeting-413:34
johnthetubaguyI was thinking that would mean sorting the list several times, but I assume mysql doesn't do it that way13:34
alex_xumaybe I can do a test later, to see is there any different for one sort key and multiple sort key13:35
johnthetubaguyits worth a quick check I guess13:36
johnthetubaguyparticularly on the longer string fields13:36
*** links has joined #openstack-meeting-413:36
*** links has quit IRC13:36
alex_xujohnthetubaguy: just done, very close with one key and mutiple keys13:37
johnthetubaguycool, lets just not worry about that13:38
alex_xuok13:38
alex_xuso the plan is the filter list probably is same with current proposal13:39
alex_xuremove the sort which didn't mapping to the API.13:39
*** kylek3h has quit IRC13:39
*** lamt has joined #openstack-meeting-413:40
alex_xuadd mapping for display_name => name13:41
alex_xuI need to check another mapping13:41
alex_xus/another/any other/13:41
alex_xudoes that sounds cool?13:41
johnthetubaguyso filter and sort being the same list?13:42
johnthetubaguyor is that list too small?13:42
alex_xuI guess filter list is small13:42
alex_xuspecial for non-admin filter list13:43
johnthetubaguywell non-admins should be able to sort on project_id, but I guess it doesn't matter as its a no op sort13:44
johnthetubaguyI mean should not be able13:44
*** karthiks has joined #openstack-meeting-413:45
alex_xuyea13:45
*** yamamoto has joined #openstack-meeting-413:45
alex_xulook at the API response, looks like they are close13:46
johnthetubaguyanyways, sounds like we are closer to agreement13:46
alex_xuyea13:47
*** baoli has joined #openstack-meeting-413:48
alex_xuat least agreement on the direction. i will work out the final list. I guess that won't be too much different than your expect13:48
*** haleyb__ has joined #openstack-meeting-413:49
*** kylek3h has joined #openstack-meeting-413:50
alex_xuemm...I need to check the client also13:50
*** baoli_ has quit IRC13:50
alex_xuensure there isn't anything we break13:50
johnthetubaguytrue, it would be bad to break what we advertise in the client13:52
alex_xujohnthetubaguy: emm...we wil remove some filters which support in the client. so I think we can't remove them13:52
johnthetubaguyah, what are the examples?13:52
alex_xulike --ip, --ip6, --image, --flavor13:52
johnthetubaguyimage and flavor seem worth keeping13:53
alex_xuok13:53
*** julim has joined #openstack-meeting-413:53
johnthetubaguyI guess we should keep ip/ip6 if thats in the client, but I can't say I like that :(13:53
alex_xuyea13:53
alex_xuand --name13:54
*** haleyb__ has quit IRC13:54
*** baoli_ has joined #openstack-meeting-413:54
*** julim has quit IRC13:54
alex_xuprobably the client just adverties the filters for non-admin and few admin-only13:55
johnthetubaguy--name has to stay13:55
johnthetubaguyI know those don't have an index, but I think thats intentional, becuase the index is more expensive than the gain we get by having it13:56
alex_xuhttps://github.com/openstack/nova/blob/f8a81807e016c17e6c45d318d5c92ba0cc758b01/nova/api/openstack/compute/servers.py#L110313:56
alex_xuheh, ^ probably we just keep this list13:56
*** baoli has quit IRC13:56
alex_xuyea, name is pattern matching, index won't help13:57
*** seanmurphy has joined #openstack-meeting-413:57
alex_xu3 mins left13:57
*** brunograz has joined #openstack-meeting-413:58
alex_xujohnthetubaguy: so i guess that is the plan, anything more you hope me to notice?13:58
johnthetubaguyalex_xu: so IP filter happens in code btw: https://github.com/openstack/nova/blob/3cd2005523dc83b1cadc956c4f86385766aaf679/nova/compute/api.py#L243313:58
alex_xujohnthetubaguy: yea13:58
johnthetubaguyalex_xu: thats in some ways worse, as it means we have to turn off paging13:58
johnthetubaguyalex_xu: anyways, don't need to worry about an index for that one13:59
alex_xujohnthetubaguy: how that works in paging for now?13:59
alex_xuI need to check13:59
alex_xuit's time to close13:59
johnthetubaguywell, I think the expectation is there will only be a very small number of matches13:59
alex_xujohnthetubaguy: ok, got it14:00
*** licanwei 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 Nov 30 14:00:05 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-11-30-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-11-30-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-11-30-13.00.log.html14:00
*** numans has joined #openstack-meeting-414:00
dtardivel #startmeeting watcher14:00
dtardivelhi14:01
*** julim has joined #openstack-meeting-414:01
hvprash_hi14:01
seanmurphyhi guys14:01
sballe_hi14:01
dtardivel#startmeeting watcher14:01
openstackMeeting started Wed Nov 30 14:01:39 2016 UTC and is due to finish in 60 minutes.  The chair is dtardivel. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: watcher)"14:01
openstackThe meeting name has been set to 'watcher'14:01
*** diga has joined #openstack-meeting-414:01
digao/14:01
*** karthiks has quit IRC14:02
licanweihi14:02
pshedimbhi14:02
brunograzo/14:02
dtardivelagenda for today: https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#11.2F30.2F201614:02
dtardivel#topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:03
*** cdent has left #openstack-meeting-414:03
dtardivelacabot is currently introducing Watcher at Cloud Expo Europe, Paris14:03
seanmurphycool!14:04
sballe_+214:04
dtardivelso, he asked me to lead this meeting today ;)14:04
hvprash_nice !14:04
dtardivel#link http://www.cloudexpoeurope.fr/english/about-cloud-expo-europe-paris14:04
*** jwcroppe has joined #openstack-meeting-414:05
dtardivelThis is meanly a summit for french cloud experts14:05
sballe_you mean 'mainly" right ;-)14:05
dtardivelHe is on stage now for 30mn :)14:05
sballe_very cool!14:05
dtardivelmainly yep14:05
dtardivelanother point: If you have a look on github project, we have now a flag 'project/official' on README page14:06
sballe_very cool!14:06
dtardivel#link: https://github.com/openstack/python-watcherclient#team-and-repository-tags14:06
jwcroppenice, that's great to see14:07
dtardivelsballe_: can you merge this patch for watcher-specs project please #link https://review.openstack.org/#/c/402979/14:07
sballe_hey jwcroppe! your are back! great to see you again14:07
jwcroppetangential question - is reviwew.openstack.org slow for anyone today?14:07
dtardiveljwcroppe: it is ok from France14:08
sballe_dtardivel: done14:08
jwcroppesballe_: hey there - yes, thanks - finally all moved and things settled down a bit.  I've been trying to get the new house all organized in my 'spare time'  :)14:08
dtardivelOther announcements from you side ?14:09
sballe_no not from me14:10
jwcroppewill review https://review.openstack.org/#/c/402979/ after the meeting14:10
dtardiveljwcroppe: sballe has just set W+1 :)14:11
dtardivel#topic Review Action Items14:11
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:11
dtardivel Watcher specs14:11
sballe_I figured it looked straight forward14:11
jwcroppeyep, looked good14:12
dtardivelDefine grammar for workload characterization need a new PS14:12
dtardivel#link https://review.openstack.org/#/c/377100/14:12
hvprash_yes dtardivel, i will add a new PS14:12
hvprash_seanmurphy, thanks for the review and comments. I will take a look on your comments and a new PS.14:12
seanmurphyhvprash_: np - hope it was useful14:12
sballe_hvprash_: we can work on it together I have thougth about some of the comments14:12
sballe_seanmurphy: it was14:12
hvprash_frankly, i haven't had a chance to look into your comments. Its been a big week for us due to thanks giving retail etc..14:13
sballe_100% understand...14:13
hvprash_i am going to spend sometime this week14:13
sballe_I am glad you guys are doing well14:13
hvprash_thanks sballe_ :)14:13
dtardivel#action hvprash_, seanmurphy complete  https://review.openstack.org/#/c/377100/14:14
dtardivelDefine when an action plan is stale/invalid needs reviews14:14
dtardivel#link https://review.openstack.org/#/c/386293/14:14
dtardivelsballe_: or jwcroppe : as core reviewer, could you have a look on this one ?14:15
sballe_yes I will do it14:15
hvprash_will do14:15
jwcroppeyep14:15
dtardivelthx14:15
dtardivel#action sballe_, jwcroppe, hvprash_ review https://review.openstack.org/#/c/386293/14:16
dtardivelAudit tag in VM Metadata needs reviews as well14:16
dtardivel#link https://review.openstack.org/#/c/391374/14:16
sballe_yes I thought I had reviwed it but I guess not14:16
sballe_it is my plan to look at it14:16
hvprash_yes, thanks to vincent for thoise comments.14:16
hvprash_I need to review that14:16
dtardivel#action sballe_ dtardivel will review https://review.openstack.org/#/c/391374/14:17
dtardivelAdd improvements to the planner and workflow mechanisms needs reviews as well :)14:17
dtardivel#link https://review.openstack.org/#/c/385871/14:17
*** hemanth|away is now known as hemanth14:18
dtardivelalexchain is not online.14:18
*** karthiks has joined #openstack-meeting-414:19
dtardivelI think we have now a complete description of what we should implement. Core reviews is now required :)14:19
dtardivel#action acabot will review https://review.openstack.org/#/c/385871/14:20
sballe_ok. I would like some +1s here from non core members as well14:20
dtardivelsballe_: ok14:20
dtardivel#action dtardivel will review last update on https://review.openstack.org/#/c/385871/14:20
sballe_this is an important specs so I would like some more eyes on it and then we +2 it14:20
licanwei+114:21
dtardivellicanwei: do you want review it ?14:21
licanweiyes14:21
dtardivellicanwei: thx14:22
dtardivel#action licanwei will review https://review.openstack.org/#/c/385871/14:22
dtardivelSupport Description For Dynamic Action needs reviews14:22
dtardivel#link https://review.openstack.org/#/c/401111/14:22
dtardivelI reviewed it this morning. We can ask to hanrong a new update first14:23
sballe_yes just saw that14:23
dtardivel#action hanrong will update https://review.openstack.org/#/c/401111/14:24
dtardivelOther specs in your mind ?14:24
*** tonytan4ever has joined #openstack-meeting-414:25
sballe_just as an FYI I will start working on: https://review.openstack.org/#/c/398162/14:25
sballe_pshedimb:  will be co-author as well14:25
dtardivelsballe_: ok. is it something you would like for ocata ?14:26
sballe_yes I believe we have it for ocata-314:26
dtardivelsballe_: ok14:26
dtardivelLet's review actions for watcher project14:27
dtardivelcentralise-config-opts needs reviews14:27
dtardivel#link https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/centralise-config-opts14:27
pshedimbi'm working on your comments dtardivel14:27
sballe_pshedimb: did you have questions on the dbmanage one?14:28
pshedimbYeah I did14:28
dtardivelpshedimb: yes I reviewed one changeset this morning.14:28
sballe_pshedimb:  did you get them answered?14:29
pshedimbNot yet14:29
pshedimbCan I ask it here?14:29
sballe_sure if it is quick14:29
dtardivelpshedimb: please ask on openstack-watcher, just after the meeting14:29
sballe_ok :-)14:29
dtardivelpshedimb: you have just 1mn :)14:29
pshedimbwatcher/cmd/dbmanage.py14:30
pshedimbwhich opt group does this come under?14:30
dtardivelpshedimb: ok on openstack-watcher later :) I have not the answer14:30
pshedimbDefault?14:30
pshedimbokay.14:30
dtardivelpshedimb: please ring me later14:31
dtardivelcheck the state of action plan needs discussions14:31
dtardivel#link https://review.openstack.org/#/c/391383/14:31
sballe_dtardivel: so pshedimb can chat with you rigth after the meeting?14:31
dtardivellicanwei: What is the status ?14:32
dtardivelsballe_: yep14:32
pshedimbokay dtardivel14:32
licanweidtardivel: I'll add a new PS14:33
dtardivel#action licanwei will add a new PS on https://review.openstack.org/#/c/391383/14:33
dtardivelAdd auto_trigger support to watcher needs reviews ?14:34
dtardivel#link https://review.openstack.org/#/c/403718/14:34
dtardivelalexchain is not online. This changeset is tagged [WIP]. Let move to the next ...14:35
dtardivelSpecific exception for stale cluster state was added needs reviews14:35
dtardivel#link https://review.openstack.org/#/c/399202/14:35
dtardivelno update ?14:36
dtardivelno update ... :) I will ask to acabot to contact Anton to get news14:37
hvprash_dtardivel, i will try to find from anton14:37
hvprash_he was working on it14:37
dtardivelhvprash_: what is the Anton's nickname ?14:38
hvprash_eil39714:38
dtardivelhvprash_: yes of course, :)14:38
hvprash_sure :)14:38
dtardiveleil397: ^^^^14:39
dtardiveltrying ....14:39
dtardivelAdd auto_trigger in audit API needs a status14:39
dtardivel#link https://review.openstack.org/#/c/398044/14:40
dtardiveldiga: any update ?14:40
*** irenab has quit IRC14:40
dtardivel#action diga please update your changeset to fix failure jobs14:41
dtardivelFix rally gate test has been merged this morning14:41
dtardivel#link https://review.openstack.org/#/c/398180/14:41
dtardivelSince last week, I merged several little patches improving our source code. Thx a lot everybody :)14:43
dtardivellet's move to actions on watcherclient project14:43
dtardivelAdd auto_trigger support needs reviews ?14:43
dtardivel#link https://review.openstack.org/#/c/403716/14:43
dtardivelwho want to review it ?14:44
dtardiveloups sorry it is tagged [WIP] as well14:44
dtardivel#action alexchadin please update status on https://review.openstack.org/#/c/403716/14:45
dtardivelAdd functional tests to watcherclient needs reviews14:45
dtardivel#link https://review.openstack.org/#/c/389181/14:45
*** Swami has joined #openstack-meeting-414:46
dtardivelI asked to alexchain a new section in README doc. But more reviewer is welcome on this changeset14:46
dtardivelnobody want to know how Tempest works for cli ? :)14:48
sballe_lol14:48
dtardivelchanges to make consistent with other openstack component needs reviews14:49
dtardivel#link https://review.openstack.org/#/c/403434/14:49
dtardivelok I reviewed it this morning. I waiting for an update from Lucky14:49
*** spzala has joined #openstack-meeting-414:50
dtardivel10 mn left .... quick quick quick14:50
dtardivel#topic Blueprint/Bug Review and Discussion14:50
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:50
*** haleyb__ has joined #openstack-meeting-414:50
dtardivelsballe_: your strategy documentation has been merged14:51
sballe_yes thank you14:51
sballe_thx for all the reviews, comments, and +1s14:51
sballe_I will work on the next two docs now14:51
sballe_dtardivel: and off course your +214:52
dtardivelsballe_: what about nishi's strategy doc (airflow) ?14:52
sballe_I will do all the intel docs14:52
dtardivelsballe_: cool14:52
*** reedip_ has joined #openstack-meeting-414:52
dtardivelAny comments on BP ?14:52
sballe_I just wanted this one completed first so I didn;t have 3 in flux with the same comments14:52
dtardivel#topic Open discussions14:54
*** openstack changes topic to "Open discussions (Meeting topic: watcher)"14:54
sballe_I would like to understand if I have to pay $100 to attend the cross project meet up in Feb.14:54
*** danpawlik has joined #openstack-meeting-414:54
sballe_I tried to register abd evenbrite wanted $10014:54
sballe_acabot: was suppose to ask ttx but I haven't heard back from him14:54
dtardivelsballe_: I really don't know14:54
sballe_ok has anybody signed up for the meetup?14:55
dtardivelsballe_: I will discuss with acabot tomorrow if you want14:55
sballe_yes please14:55
*** unicell1 has quit IRC14:55
*** unicell has joined #openstack-meeting-414:55
*** haleyb__ has quit IRC14:55
*** GeraldK has joined #openstack-meeting-414:55
dtardivel#action dtardivel query acabot about $100 tax from eventbrite for cross project meet up14:56
sballe_also atuly is trying to figure out who to talk to to get a letter for his visa14:56
*** diga has quit IRC14:56
hvprash_sballe_ do you have the eventbrite link ?14:56
sballe_i refered himto acabot14:56
sballe_hvprash_: yes one sec14:56
sballe_https://www.eventbrite.com/e/project-teams-gathering-tickets-27549298694#tickets14:57
hvprash_thanks14:57
sballe_http://www.openstack.org/ptg14:57
dtardivelsballe_: thx14:58
dtardivelOther points (in 2mn)14:58
*** betherly has quit IRC14:59
sballe_nope I am done :-)14:59
*** prateek has joined #openstack-meeting-414:59
*** Rockyg has joined #openstack-meeting-414:59
dtardivelno, so have a good day, afternoon, night everyone14:59
*** dmsimard has left #openstack-meeting-414:59
*** bklei has joined #openstack-meeting-415:00
dtardivelplease see you again next week15:00
dtardivel#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Nov 30 15:00:17 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-11-30-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-11-30-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-11-30-14.01.log.html15:00
*** yamamoto has quit IRC15:00
*** licanwei has left #openstack-meeting-415:00
jwcroppethanks - reviewing specs now :)15:00
*** jwcroppe has left #openstack-meeting-415:00
*** ad_rien_ has joined #openstack-meeting-415:01
serverascode#startmeeting operators_telco_nfv15:01
openstackMeeting started Wed Nov 30 15:01:46 2016 UTC and is due to finish in 60 minutes.  The chair is serverascode. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
*** bobh has joined #openstack-meeting-415:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: operators_telco_nfv)"15:01
openstackThe meeting name has been set to 'operators_telco_nfv'15:01
serverascode#topic roll call15:02
ad_rien_o/15:02
*** openstack changes topic to "roll call (Meeting topic: operators_telco_nfv)"15:02
ad_rien_hi all15:02
serverascodehi ad_rien_15:02
GeraldKhi15:02
GeraldKbtw, what does "o/" mean?15:02
*** brunograz has left #openstack-meeting-415:02
serverascodeit's meant to be like a person putting their hand up15:03
serverascodesaying "I'm here" :)15:03
GeraldKserverascode: yes, I saw it was used in this context. thanks for the explanation of "hands up"15:03
serverascodeanyone else here for the ops telecom/nfv meeting or just us three?15:04
GeraldKsome public holiday today in some countries?!?15:05
serverascodeok so far just the three of us :)15:05
serverascodeI know one person said they were not able to make it today15:05
ad_rien_I didn't see your email15:05
ad_rien_BTW serverascode so maybe this can explain that15:05
*** yamamoto has joined #openstack-meeting-415:06
*** bobh has quit IRC15:06
serverascodead_rien_ yes good point. I have only been emailing the openstack-operators list, I think perhaps I should gather everyone's email to sent out notices15:06
*** Julien-zte has quit IRC15:06
*** Julien-zte has joined #openstack-meeting-415:07
serverascode#link http://lists.openstack.org/pipermail/openstack-operators/2016-November/012213.html15:07
*** Julien-zte has quit IRC15:07
*** Julien-zte has joined #openstack-meeting-415:07
ad_rien_serverascode:  thanks for the link15:07
*** Julien-zte has quit IRC15:08
*** caowei has quit IRC15:08
*** Julien-zte has joined #openstack-meeting-415:08
serverascode#action serverascode to put a contact section in the agenda etherpad15:08
*** Julien-zte has quit IRC15:08
serverascodeI think I will gather contact emails and send out to more than just the ops list15:08
*** Julien-zte has joined #openstack-meeting-415:09
serverascodeok, so otherwise, the only thing I had on the agenda was continuing our conversation on NFVi/multi-site etc15:09
serverascodeanyone have anything else to add to the agenda?15:09
*** Julien-zte has quit IRC15:09
*** eil397 has quit IRC15:09
serverascodeif so just go ahead and add it15:10
*** Julien-zte has joined #openstack-meeting-415:10
serverascode#link https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda15:10
*** Julien-zte has quit IRC15:10
serverascode#topic mid to long term project around NFVi15:10
*** openstack changes topic to "mid to long term project around NFVi (Meeting topic: operators_telco_nfv)"15:10
*** prateek has quit IRC15:10
*** rbak has joined #openstack-meeting-415:10
*** spotz_zzz is now known as spotz15:11
serverascodeso last meeting we had a good discussion about NFVi and also we tried to figure out if multi-site/region/cloud was also part of that15:11
serverascodeI noticed that OPNFV has a multi-site project15:11
serverascode#link https://wiki.opnfv.org/display/multisite/Multisite+Deployment+Environment15:11
serverascodeanyone have any further thoughts on that?15:11
jamemccHi - Jamey McCabe here now also.15:12
serverascodeif we do think that multi-site is important to us, then it might make sense to work with that OPNFV project15:12
serverascodehi jamecc :)15:12
* ad_rien_ is giving a look to the OPNFV link15:12
serverascodethere is also some kind of related project called kingbird15:13
serverascode#link https://wiki.openstack.org/wiki/Kingbird15:13
serverascodenot sure how that relates to multi-site or the tricircle project...15:13
ad_rien_yyes15:13
ad_rien_tricricle is now only focusing on the network part15:14
ad_rien_kingbird seems to address everything15:14
ad_rien_(i.e. like the initial goal of Tricircle)15:15
GeraldKas a proposal: there had been some confusion last meeting around what is a "NFVI reference architecture". we seem to mean something like OpenStack + neutron-sfc, right? From ETSI point of view, OpenStack is the VIM and runs on top of the NFVI, so maybe be choosing a different name for the intended reference architecture could solve our confusions. what do you think?15:15
serverascodeGeraldK right my mistake, I keep saying NFVi15:16
GeraldKe.g. use "minimal benchmarking reference architecture"?15:16
ad_rien_I'm still confused about what will be the minimal benchmarking reference.15:16
ad_rien_several independant openstack instances? only one?15:17
GeraldKserverascode: np. just that we use NFVI now already in several places e.g. the Etherpad15:17
serverascodead_rien_ yes this is where we got stuck last meeting :)15:17
*** edleafe- is now known as edleafe15:17
*** armax has joined #openstack-meeting-415:17
GeraldKlet's talk first about the test/benchmarks we want to initially work on. then, we can see what benchmark reference architecture we need15:17
serverascodeGeraldK I agree15:18
jamemccI agree15:18
ad_rien_I'm not working for a telco so please feel free to start the discussion ;)15:18
ad_rien_As I mentioned, I just want to see whether there can be common actions with the massively distributed WG15:19
serverascodemy thinking has been that service function chaining (SFC) is a key feature for minimal benchmarking reference15:19
*** spotz is now known as spotz_zzz15:19
serverascodeso an openstack VIM which has the ability to do SFC, probably via networking-sfc15:20
serverascodebut that's just me15:20
*** galstrom_zzz is now known as galstrom15:20
serverascodeanyone have any thoughts on that?15:21
GeraldKi did not propose this benchmarking topic :)15:21
GeraldKnot sure what the people proposing it had in mind when proposing it15:22
ad_rien_If I'm right the idea was to identify limitations/missing features15:22
*** spotz_zzz is now known as spotz15:22
ad_rien_of the Openstack vanilla code w-r-t the NFV use-cses15:22
ad_rien_By conducting such experiments it will be possible to present strong arguments to the different openstack projects15:23
serverascodethat was my impression, where also the simple creation of a reference architecture is also valuable15:23
serverascodejust doing that would be of some use, and then testing it from both a functional and performance view would also be beneficial15:24
jamemccI didn't either - but it made sense to me.  I interpreted Benchmarking as a performance topic.  Performance being response time and throughput.  So minimal benchmarking could be measuring something like response time and throughput within and across openstack instances.15:24
serverascodeand would likely allow us to work with various groups like OPNFV, OpenStack Performance group, etc15:24
serverascodeI think the word "benchmarking" might have also been used in such a way that it also meant functional testing15:25
serverascodeso not just performance, but actually ensuring the features we need are there and are working15:25
serverascodeBut, I am typing a lot, and what this group does is up to the group, which means we need to solve the problems we are actually encountering15:26
ad_rien_+115:26
*** bobh has joined #openstack-meeting-415:26
jamemccI thought of it as having a baseline/minimal architecture that provided a recognized throughput and from that you could have a few persuits.  1. Imporve (or at least maintain) performance release over release.  Have a better measure on which vendors or specialized projects could claim great imporvements.15:26
ad_rien_jamemcc:  +1  serverascode:  can you elaborate the use-case you envision15:27
ad_rien_please?15:27
*** limao has quit IRC15:27
*** icey has joined #openstack-meeting-415:28
serverascodeI haven't though too much about the use case, but my thinking was mostly around networking-sfc15:28
serverascode#link http://docs.openstack.org/developer/networking-sfc/15:28
*** icey is now known as Guest2816815:28
serverascodeI am not a telecom expert by any stretch, but it seems to me like SFC is pretty important to most use-cases15:28
ad_rien_ok15:29
*** duonghq_ has joined #openstack-meeting-415:29
ad_rien_do you think we can find a key thread that will guide us in our action15:29
ad_rien_i.e. a concrete use-case that can illustrate the networking-sfc you mention15:30
ad_rien_i.e. what are the software components that should be deployed? and where (i.e; how these services should be consolidated through the different VMs)15:30
serverascodethe most common thing I see with SFC is "virtual customer premise equipment" (vCPE)15:30
ad_rien_ok15:30
serverascodebut I'm not too sure how valuable that actually is?15:31
ad_rien_so the idea can be to identify what is the minimal infrastructure15:31
ad_rien_for being able to provide vCPE? and I guess that the VM that host the vCPE should be deployed as close as possible to15:31
ad_rien_the customer location?15:31
*** duonghq_ is now known as duonghq15:32
jamemccJust following the line of thinking of a functional benchmark.  Bascially could define a number of somewhat simple and straightforward NFV use cases: e.g. Firewall, Load Balancer, Audio / Video Conferencing or maybe the benchmark would be an arrangement of a few of those that sets up the "chain"15:32
GeraldKjamemcc +115:32
serverascodeyeah that'd be great :)15:32
*** Guest28168 has quit IRC15:33
ad_rien_ok but we should chose one, shouldn't we?15:33
ad_rien_at least for moving forward15:33
serverascodeprobably one to start then add more use-cases as we see fit15:33
ad_rien_ok15:34
serverascodethoughts? concerns about using a vCPE an SFC use case for our minimal reference architecture?15:35
GeraldKif I remember right, we had choosen in total 3 or 4 mid to long term projects. should we also spend some meeting time on those?15:35
serverascodeok, how about I write up a basic vCPE + SFC use-case and we discuss next meeting, and we move on to other potential projects?15:35
GeraldKserverascode: sounds good to me15:35
ad_rien_+&15:36
ad_rien_+115:36
ad_rien_sorry15:36
serverascode#action serverascode write up basic vCPE + SFC use case to discuss next meeting15:36
*** icey_ has joined #openstack-meeting-415:36
serverascode#topic Other mid-to-long term projects to consider working on15:36
*** openstack changes topic to "Other mid-to-long term projects to consider working on (Meeting topic: operators_telco_nfv)"15:36
*** oshidoshi has quit IRC15:36
serverascodeok GeraldK did you have some other project ideas?15:37
*** yuli_s has quit IRC15:37
*** oshidoshi has joined #openstack-meeting-415:37
*** yuli_s has joined #openstack-meeting-415:37
GeraldKfrom the meeting we also had Rolling/live upgrades/updates and VNF onboarding with many votes15:37
*** rhallisey has joined #openstack-meeting-415:38
GeraldKI am interested in the rolling/live upgrades15:38
GeraldKfor an operator, each upgrade comes at high cost (for integration, testing, ..) and high risk15:38
serverascodeyeah and in a telecom environment it could be even harder15:39
serverascodeare you most concerned about the openstack control plane, or the virtual machine data plane?15:39
GeraldKso, currently, operators tend to even skip some releases and just upgrade when an important new function/feature/improvement is available15:39
serverascodeand I don't think you can skip versions any more15:40
GeraldKwhereas the goal could be to reduce the efforts and risks such that telcos are more willing to upgrade more often15:41
*** darrenc has quit IRC15:41
*** darrenc has joined #openstack-meeting-415:42
serverascodeI do think that is an important topic and would be worth spending time on15:42
GeraldKas far as I know, if we as a Telco get a new version from our integrator, this will skip a few OS releases. but of course that means extra (proprietary) efforts on the integrator side15:42
ad_rien_with the adoption of OpenStack on top of containers, such upgrades should become easier15:42
ad_rien_but I agree the distributed context of telcos makes the story more complex15:42
*** hongbin has joined #openstack-meeting-415:42
GeraldKTelcos are very conservative on this regards. in the past with the legacy HW upgrades had been very rare.15:43
serverascodeGeraldK are you interested in this from a high-level, like how to approach upgrading? or the actual technical details?15:43
*** jmorgan1 has joined #openstack-meeting-415:44
serverascodeand do you care about the openstack API uptime or just that your virtual machines stay up and running and don't lose any packets?15:44
GeraldKmore high-level I would say. what are requirements from operators/telcos, how can those be realized by openstack and where do we see gaps that we could then trigger to be addressed15:45
GeraldKI care about the Telco service staying up and running and not loosing any calls / connections during the upgrade15:45
serverascodeok15:46
*** Sukhdev has joined #openstack-meeting-415:46
GeraldKas well as reducing the complexity and efforts to test the new versions15:46
serverascodegood point on testing, that is hard to do15:46
serverascodeI think it would be worthwhile putting together an upgrading document of some kind, something that discusses these requirements and issues15:47
*** icey_ has quit IRC15:47
*** hieulq_ has joined #openstack-meeting-415:48
GeraldKduring the upgrade phase you might even have entities running different versions in parallel15:48
serverascodedo you want to put together maybe a paragraph or so on this project idea and we can discuss it more next meeting?15:49
*** yamamoto has quit IRC15:49
GeraldK+1 to start a document. it can also collect ongoing activites around upgrading15:49
*** galstrom is now known as galstrom_zzz15:49
GeraldKokay. I can give it a start.15:49
serverascode#action GeraldK write up a paragraph or so on the upgrading project idea to discuss next meeting15:50
serverascodeok about 10 min left, anything we are missing today?15:50
*** icey_ has joined #openstack-meeting-415:50
*** rhallisey has quit IRC15:51
serverascodead_rien_ jamemcc any additional thoughts?15:51
jamemccIn our LCOO workign group we also have raised the issue and pretty much agreed we share the concern and situation and approach as stated by GeraldK.  We want this topic to get more attention - basically upgradeability.  We found though as we started to dig a little deeper that we couldn't easily identify user stories and that our being behind 2-4 releases made it really our own issue - nothing we could point out for an upcoming release.15:51
jamemccBut I can try to generate interest / help for this from the LCOO members.15:51
*** icey_ has quit IRC15:51
ad_rien_not on my side.. (sorry a few busy and so not so reactive today)15:51
*** Syed_ has joined #openstack-meeting-415:51
serverascodead_rien_ no worries :)15:51
GeraldKjamemcc, can you point me to some docs / discussion on this?15:52
serverascodejamecc is the LCOO mostly starting to work on user stories to start?15:52
*** icey_ has joined #openstack-meeting-415:53
*** egonzalez90 has joined #openstack-meeting-415:53
jamemccKind of a mixed bag - we are pushing joint user stories - but we also have involvement in current projects so are trying to also generate more cooperation around projects the various members are already workign on.15:53
*** rhallisey has joined #openstack-meeting-415:53
jamemccYeah GeraldK - I'll try to pull from some of our early meeting notes15:53
GeraldKthanks jamemcc15:54
*** sbezverk has joined #openstack-meeting-415:54
*** apuimedo is now known as apuimedo|away15:54
*** inc0 has joined #openstack-meeting-415:54
serverascodeok, well that was a good meeting, we certainly have some direction to go in now :)15:54
serverascodeanyone have any last comments?15:55
serverascodeif you want me to send you an email before each meeting, feel free to put your email in the agenda page15:56
serverascodeunder "contact emails"15:56
serverascodeotherwise I usually email the openstack operators list the day before as well15:56
jamemccThanks Curtis - good job15:56
serverascodethanks jamemcc :)15:57
serverascodeI'll end the meeting and we'll talk in a couple weeks15:57
serverascode#endmeeting15:57
*** portdirect has joined #openstack-meeting-415:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:57
GeraldKbye15:57
openstackMeeting ended Wed Nov 30 15:57:22 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-11-30-15.01.html15:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-11-30-15.01.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_telco_nfv/2016/operators_telco_nfv.2016-11-30-15.01.log.html15:57
*** zhubingbing_ has joined #openstack-meeting-415:58
*** psachin has quit IRC15:59
*** Sukhdev_ has joined #openstack-meeting-415:59
inc0#startmeeting kolla15:59
openstackMeeting started Wed Nov 30 15:59:07 2016 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
*** wirehead_ has joined #openstack-meeting-415:59
inc0#topic rollcall, w00t please!15:59
*** openstack changes topic to "rollcall, w00t please! (Meeting topic: kolla)"15:59
duonghqw00t!!! o/15:59
wirehead_meow15:59
rhalliseymeow meow15:59
duonghqwirehead_, meo,,,,,15:59
inc0lol15:59
*** mgiles has joined #openstack-meeting-415:59
Jeffrey4lwoot16:00
*** cathrichardson has joined #openstack-meeting-416:00
sbezverko/16:00
*** bklei_ has joined #openstack-meeting-416:00
*** sayantani01_ has joined #openstack-meeting-416:00
*** jascott1 has joined #openstack-meeting-416:00
zhubingbing_o/16:00
duonghqI forgot or we have new kollish?16:00
sbezverksorry wirehead_ I am dog guy ;-)16:00
pbourke_o/16:01
inc0^._.^16:01
berendto/16:01
jascott1o/16:01
pbourke_finally remembered the correct time16:01
*** thorst_ has quit IRC16:01
berendtpbourke_: dito :)16:01
inc0yes, pbourke_ that would be hard for someone as far away from GMT as you are;)16:01
sayantani01_w00t16:01
duonghqnice to see both of you pbourke_, berendt16:01
portdirecto/16:01
pbourke_inc0: :P16:02
sdakeWOOT16:02
*** bklei has quit IRC16:02
duonghqsdake, WOOT finally?16:02
sdakeyou got it16:02
inc0#topic announcements16:02
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:02
sdakeone time only :)16:02
*** oshidoshi has quit IRC16:03
inc0I have one. I'm going for PTO + moving across country from 6th Dec till pretty much holiday. I won't be around (will try to join in every now and then but can't promise)16:03
inc0Jeffrey4l graciously agreed to help me and cover for me during this time16:04
sdakeJeffrey4l ++16:04
zhubingbing_++16:04
Jeffrey4lmay need some help from sdake  ;)16:04
inc0so, if there is anything needing immediate attention, he's your guys. I'll also can be reached by email or just wait till I'm back16:04
*** ad_rien_ has left #openstack-meeting-416:04
*** GeraldK has quit IRC16:05
inc0anyway, that being said, let's kick this off by handing this meeting to Jeffrey4l16:05
*** seanmurphy has quit IRC16:05
inc0#chair Jeffrey4l16:05
openstackCurrent chairs: Jeffrey4l inc016:05
inc0you're up:)16:05
*** piet_ has joined #openstack-meeting-416:05
sdakeJeffrey4l you got it16:05
Jeffrey4lour agenda is not updated recently.16:05
inc0yeah, that's not news;016:05
inc0so I can throw first topic16:06
Jeffrey4lother annoucement from community?16:06
inc0our voting of splitting core teams ends today and so far we seems to be in agreement16:06
sdakeon Jeffrey4l 's point - i think it would be helpful for everyone to update the agenda16:06
*** yamamoto has joined #openstack-meeting-416:06
sdakerather then relying on one person to do the job16:06
berendtuh. looks like i missed this mail.16:07
portdirectwill do :)16:07
Jeffrey4lre agenda: update the wiki page https://wiki.openstack.org/wiki/Meetings/Kolla before meeting please :)16:07
*** galstrom_zzz is now known as galstrom16:07
inc0well not splitting cores16:07
inc0that cores form kolla-ansible woudl vote for kolla-ansible cores and so on16:07
inc0that's effectively team split16:07
Jeffrey4lok. next topic?16:08
*** Sukhdev_ has quit IRC16:09
Jeffrey4l#topic heka alternative16:09
*** openstack changes topic to "heka alternative (Meeting topic: kolla)"16:09
Jeffrey4lthis is talked in http://lists.openstack.org/pipermail/openstack-dev/2016-November/108011.html16:09
Jeffrey4lrecently.16:09
wirehead_One might say we've discussed it a heka lot of times.16:10
sdakewirehead_ lol16:10
Jeffrey4li think we need make the choice right now.16:10
Jeffrey4lyep.16:10
*** iyamahat has joined #openstack-meeting-416:10
Jeffrey4li think the fluentd win finally.16:10
*** bklei_ has quit IRC16:10
sdakeJeffrey4l right now or kick it to pike16:10
Jeffrey4lany idea on this?16:10
sdakei have a bit of concern about the short schedule we have in ocata16:11
Jeffrey4lok. yes.16:11
sdakeand not cratering kolla in the process16:11
berendti would prefer to work on it right now16:11
portdirect+1 to Fluentd, simply beause a lot of k8s support is there16:11
sbezverkhurray for fluentd ;-)16:11
sdakeok - again just an opion16:11
berendtfluentd works for me, i do not have a strong behavior..16:11
inc0yeah fluentd is cool as it's cncf project now16:12
sdakei'd recommend we work on a stack of patches rather then merging16:12
inc0my reservations for fluentd were because of billing model afair16:12
berendtsdake: +116:12
Jeffrey4lsdake, +116:12
sdakepurupose of that is to hedge, in case the implementation doesn't work16:12
inc0but as its cncf project now, that's done16:12
inc0so for Snap credit, it will allow us to have similar functionality to heka in a month or so, as far as I know from team managing it16:13
inc0but I understand, maturity16:13
berendti think we should try to make fluentd swapable16:13
sdakewe also have a general rule inc0 we adapt to our upstreams and don't wait for them to publish features16:13
berendtthat it is not a big deal to replace it in the future16:13
berendtmaybe we have the same issue with fluentd in a few months16:13
sdakeberendt no doubt about it ;)16:14
inc0so yeah, I think that thing is swappable on it's own16:14
Jeffrey4l#action migrate from heka fluentd with a stack of patches. merged until it works.16:14
sdakenot merged ?16:14
berendtJeffrey4l: will you send out an update to openstack-dev?16:14
sdakeJeffrey4l you can use #undo to undo an action16:14
Jeffrey4l#undo16:15
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x7fbb93d96790>16:15
Jeffrey4l#action migrate from heka fluentd with a stack of patches. not merged until it works.16:15
sdakeJeffrey4l and then do the action again - merged until works doesn't mean what I think you meant it  to :)16:15
sdakesweet :)16:15
portdirectJeffrey4l: s/untill/when16:15
Jeffrey4lsdake, thanks.16:15
sdakeportdirect its gefn :)16:15
Jeffrey4lwhy openstack-dev?16:16
Jeffrey4lberendt, ^16:16
berendtJeffrey4l: we discussed it there and i think we should note that we decided to use fluentd16:16
sdakeJeffrey4l so people know the action16:16
zhubingbing_+116:17
Jeffrey4lshould we send mail to openstack-ops, right?16:17
inc0Jeffrey4l, let's send email when we merge stuff16:17
inc0to ops16:17
berendtinc0: +116:17
Jeffrey4lOK.16:17
Jeffrey4li will send the mail.16:17
inc0as we might end up having some sort of strange technical issues16:17
inc0never know16:17
Jeffrey4lnext topic is? i have no right now16:17
inc0I wanted to talk about changes in core polict16:18
inc0#topic core team policy change16:18
*** openstack changes topic to "core team policy change (Meeting topic: kolla)"16:18
inc0#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107457.html16:18
*** jmorgan1 has left #openstack-meeting-416:18
inc0voting ends today eod, but so far it's unanimous +1 so I expect it to pass16:18
inc0that effectively means that we will have separate core teams for all 3 deliverables16:19
inc0kolla, kolla-k8s and kolla-ansible16:19
berendtdoes this also mean that we split the meetings?16:19
inc0no, meetings, irc channel, community is the same16:19
inc0it's just for logistics of reviews16:20
portdirectsounds good16:20
qwangshould we merge kolla and kolla-kubernetes?16:20
inc0we work to clean up kolla-kubernetes core team to better show who really cares about project;)16:20
duonghqqwang, no....16:20
inc0qwang, no, both of them are separate16:21
*** danpawlik has quit IRC16:21
inc0same as ansible16:21
inc0now16:21
sdakeinc0 the cleanup stuff is intenral core business - and shouldn't be discussed in the meeting fwiw :)16:21
inc0well, fair enough;)16:22
inc0anyway, most importantly core teams now will have ability to nominate and vote for their own memeber16:23
inc0s16:23
portdirectsdake / sbezverk: wanna talk about the progress on kolla-kubernetes helm?16:24
duonghq+1 portdirect16:24
*** Guest46299 is now known as palendae16:24
inc0heh, I guess we exhausted this topic?;) ok, let's move on16:24
Jeffrey4l#topic kolla-kubernetes helm16:24
*** openstack changes topic to "kolla-kubernetes helm (Meeting topic: kolla)"16:24
*** revon has joined #openstack-meeting-416:24
sbezverkfinally we got into the agreement how helm temaplating will look like16:24
portdirect+216:25
duonghqthank sbezverk, kfox1111  on it16:25
sbezverkso with merging a couple of PS people will be able to replicate merged solution and start adding templates16:25
*** yamahata has joined #openstack-meeting-416:26
sbezverkwe have a white board with planned services/microservices please pick the one you like and go ....16:26
sdakesbezverk i think the whiteboard is not filled out16:26
sdakesbezverk i'll do that after this meeting assuming i don't have another ;)16:26
sbezverkhttps://blueprints.launchpad.net/kolla-kubernetes/+spec/helm-microservices16:26
Jeffrey4ldo we have any example on how to do this? which will be helpful for others to join.16:27
sdakeya no work items16:27
sdakeJeffrey4l indeed that is what the whiteboard patchsets are16:27
*** vishnoianil has joined #openstack-meeting-416:27
sbezverksdake: oh so we did not move from helm-packages BP the whiteborad we had there?16:27
sdakeJeffrey4l mind adding an action for me to fill out the work items16:27
sdakesbezverk not whiteboard, the work items16:27
sdakethe whiteboared is for status udpates16:27
sdakethe work items are for organizing the work16:27
sbezverksdake: right16:28
Jeffrey4l#action sdake add work item for bp helm-microservices16:28
Jeffrey4l#link https://blueprints.launchpad.net/kolla-kubernetes/+spec/helm-microservices16:28
portdirectI've also been working on a dev env, based on halycon-k8s, that I've started to docs for - so once kfox's work is merged in, i'll try and get that doc'd as well and we should be able to get a real head of steam up :)16:28
sdakeportdirect ++16:28
sdakeportdirect so your dev env, i'm using it16:29
sdakewhat else is needed?16:29
Jeffrey4lfeel free to take some item from this bp. we'd better finish this before m2.16:29
sbezverkgood job portdirect, I saw the results of your doc in sdake testbed, looks good16:29
portdirectnot much really - though I'm gonna retire my halycon-k8s fork (hopfully today)16:30
portdirectand document getting kubectl and helm clients installed on the localhost16:30
Jeffrey4lanything else on this topic?16:30
portdirectfrom there the workflow should be really easy for a developer to use16:30
jascott1do we also need a setup_dev.sh ?16:30
wirehead_yay. :)16:30
portdirectjascott1: on it :)16:31
sdakeportdirect thats a great idea - kubectl and helm clients on lcoal host16:31
sdakejascott1 defien setup_dev.sh for us :)16:31
*** hieulq_ has quit IRC16:31
portdirectand destroy_dev.sh...16:32
jascott1things from setup_gate.sh but for local dev16:32
portdirect^^16:32
sdakeone thing i'd like to ensure is we dont muck up developer systems with  a bunch of crap16:32
sdakereference: devstack16:32
sdakepeople run devstack in vms for a reason16:32
jascott1there are these things called containers...16:32
sdakei want to run kolla-kubernetes on my bare metal16:33
wirehead_Yeah, making kollak-k8s not be like devstack was a very large motivator. :)16:33
sdakerahter i want to do dev of kolla-kubernetes on bare metal16:33
inc0I have an idea, let's deploy it with kolla and it will be all great16:33
sdakeif that means its in a vagrant box on my localhost16:33
portdirectsdake: thats very close :)16:33
sdakethats cool16:33
rhalliseythis is what I used: https://github.com/kubernetes/kube-deploy/tree/master/docker-multinode16:33
*** cathrichardson has quit IRC16:34
sdakeportdirect what you got now is good for devs16:34
rhalliseyonly issue for multinode is you need a 2nd bm machine or a vm16:34
sdakeportdirect setup_dev.sh may be good too - have to see in review :)16:34
portdirectthe vagrant is just setting up come vm's to then run ansible on - I'll document running on baremetal...16:34
sdakeportdirect nah thats not what i meant16:34
sdakeportdirect your docs are perfect from my pov +/- some deltas16:35
duonghqrhallisey, it's a good option16:35
sdakeportdirect devs dont want their systems destroyed by the development environment16:35
rhalliseyif you have 1 vagrant box setup to run https://github.com/kubernetes/kube-deploy/blob/master/docker-multinode/worker.sh16:36
sdakewhich in essence, is what devstack does16:36
rhallisey& run on your host: https://github.com/kubernetes/kube-deploy/blob/master/docker-multinode/master.sh16:36
portdirectsdake: +116:36
sdakeportdirect so keep at it, my only recommendaiton there is to keep setup_dev.sh whtaever that is, constrained to not installing a bajillion things :)16:36
sdakeportdirect i think your docs are pretty close to mergeable now as is but we can sort that out in gerrit16:37
sdakeportdirect if you do a setup_dev.sh would you do it in a followup?16:37
sdakewhenever i see setup_dev.sh I think "setup_devSTACK.sh" :)16:37
portdirectsdake: yeah - it wont do anything other than setup kubectl and helm clients16:38
Jeffrey4l#link https://github.com/kubernetes/kube-deploy/tree/master/docker-multinode16:38
*** hieulq_ has joined #openstack-meeting-416:38
sdakerhallisey v1k0d3n and crew have produced a nice development environment that we are using as an upstream16:38
rhalliseycool16:38
sdakei really like it alot16:39
jascott1me too16:39
Jeffrey4llet's move on?16:39
sdakeruns on one node - simualtes multiple nodes, fast to setup, fast to teardwon16:39
portdirectrhallisey: kube-deploy is better for production  (ATM at least in my opnion) - but this is just for getting a quick and dirty mutinode env up and running16:39
sdakehits all the checkboxes ;)16:40
*** cathrichardson has joined #openstack-meeting-416:40
portdirectJeffrey4l: yeah16:40
sdakeJeffrey4l sure16:40
rhalliseynice16:40
Jeffrey4l#open discussion16:40
sdakeoh wait one moment jeffrey4l16:40
sdakemaybe i wasn't paying attention16:40
sdakedid we have the kolla-kubernetes topic?16:41
Jeffrey4lsdake, we are just now.16:41
*** srwilkers_ has joined #openstack-meeting-416:41
sdakeok in open discussion - wfm :)16:41
Jeffrey4lbut it is marked as `kolla-kubernetes helm`16:41
srwilkers_o/16:41
sdakeoh i see.16:41
sdakeok, well i'll do a general update here in open discussion16:41
* srwilkers_ is very late16:41
sdakesup srwilkers_16:41
portdirectsrwilkers_: o/16:41
sdakesrwilkers_ its ok - volunteer effort :)16:42
Jeffrey4lanyone want talk?16:42
sdakebasically the plan is to crank out the microservices16:42
sdakeafter the microservices are done16:42
sdakewe will move up a layer to thte service layer16:42
sdakehow that works is to be defined16:42
*** caboucha has joined #openstack-meeting-416:42
duonghqcan we set the topic back to helm?16:43
sdakethats all I have duonghq :)16:43
portdirectso - I have a topic that may be controversial re ceph16:43
duonghqsdake,  I think we should refer to rhallisey specs16:43
sdakeduonghq agree - there  is no spec for this part of the system16:43
duonghqin rhallisey's specs, we have 4 option, seem that we nearly have consensus no option 4 (iirc)16:44
sdakeduonghq moment let me read the spec16:45
portdirectshould we continue to maintain kolla-k8s ceph - or make use of the work that the ceph team are doing upstream? - Not a strong opioninion either way but seems like we are replicating effort.16:45
duonghq#link https://review.openstack.org/#/c/392257/16:45
Jeffrey4l#link https://review.openstack.org/#/c/392257/16:45
sdakeportdirect on the containers aspect, we must use our containers16:46
sdakeportdirect the ceph containers themselves don't do ubuntu for example16:46
rhalliseydid want to mention one thing real quick16:46
Jeffrey4lportdirect, does ceph fro upstream runs on k8s?16:46
portdirectJeffrey4l: yes and they have a good set of templates16:47
*** vhosakot has joined #openstack-meeting-416:47
rhalliseydealing with some internal stuff so i'll be around here and there16:47
*** caboucha_ has joined #openstack-meeting-416:47
vhosakotsorry I joined late16:47
rhalliseyjust wanted everyone to know where I've been16:47
duonghqvhosakot, o/16:48
sdakeportdirect got a link16:48
vhosakoto/16:48
portdirectbut sdake's point clarifyted the policy I was unsure of - so I'll keep on it16:48
rhalliseysdake, had kindly agreed to take the helm16:48
jascott1snare drum crash16:48
Jeffrey4lrhallisey, nice ;)16:48
*** caboucha has quit IRC16:48
portdirectsdake: https://github.com/ceph/ceph-docker/tree/master/examples/kubernetes16:48
sdakeportdirect thanks16:48
sdakei'll check it out16:48
Jeffrey4l#link https://github.com/ceph/ceph-docker/tree/master/examples/kubernetes16:49
rhalliseywirehead_, did you see that pun ^16:49
sdakewe dont want to duplicate work that is happening upstream, no16:49
rhalliseywhere's the applause?16:49
sdakealthough if the work happening upstream conflcts with our rchitecture, we are forced into it16:49
portdirectrhallisey: are you here all week :D16:49
rhalliseyhehe16:49
duonghqrhallisey, awesome16:49
sdakerhallisey applause :)16:49
srwilkers_rhallisey, oh i see what you did there16:50
sdakeok duonghq when I said move up a lyaer, I wasn't talking about moving up the layer to operators16:51
sdakeI was talking about moving up a "sub-layer" in layer-316:51
portdirectsdake: it would be very eay to take what we needed and put them in our containers though - I've been working on that16:51
sdakeduonghq as in services next - all part of the helm layer - layer 316:51
duonghqsdake, got it16:52
*** hieulq_ has quit IRC16:52
sdakeportdirect there are CLA problems with that16:52
sdakethe work submitted to the repo must be original work of your own, not someone elses16:52
duonghqso the rhallisey's operators in review queues need waiting little more time?16:53
sdakethat is unless they have also signed the cla :)16:53
portdirectsdake: roger16:53
sdakeduonghq i think that operators can be worked in parallel16:53
rhalliseyduonghq, it's in decent shape16:53
sdakeduonghq if people want to get on that, wfm :)16:53
rhalliseyit was meant to be a foundation16:53
*** bpokorny has joined #openstack-meeting-416:54
duonghqsdake, rhallisey we have some diverse in sort out operator and helm stuff in bp organization?16:54
sdakeduonghq that didn't parse16:54
sdakespecifically diverse16:54
duonghqsdake, I mean for the operators, we have 1bp/operator, but for helm stuff, we have 1bp/layer16:55
sdakedo you mean that the launchpad needs better organiation?16:55
rhalliseythe bps for each operator hasn't been made16:55
*** hieulq_ has joined #openstack-meeting-416:55
*** Zer0Byte__ has joined #openstack-meeting-416:55
sbezverkduonghq: confused a bit, what we do with helm now is perfectly fits with operator concept16:55
rhalliseyshould do a bp per operator service16:55
rhalliseysince that work will be split up16:55
sdakedisagree16:56
sbezverkwhere operator would call helm install microservice to deploy what ever it needs16:56
sdakethe best way to handle that is work items16:56
sdakeone master blueprint16:56
*** thorst_ has joined #openstack-meeting-416:56
rhalliseywhatever works16:56
sdakewell its the openstack way :)16:56
duonghqsbezverk, we are talking about "layer" in rhallisey's spec16:56
rhalliseyI roll my own way :)16:57
duonghqsdake, okay16:57
Jeffrey4ltime almost up  2 min16:57
sdakeduonghq happy to have further conversation with you to clear things up after meeting since we are short on time16:58
sdakein #openstack-kolla16:58
rhalliseyalso16:58
duonghqsdake, sure16:58
rhalliseygot a new name for operators16:59
rhalliseyvessels16:59
rhalliseymariadb vessel16:59
sdakemake it harder ;)16:59
duonghqrhallisey, didn't got your idea16:59
duonghq*get16:59
*** uck has joined #openstack-meeting-416:59
rhalliseysdake, operator is hard enough16:59
rhalliseyit means 2 things16:59
Jeffrey4lok. time is up17:00
Jeffrey4lthanks people for coming17:00
*** wirehead_ has left #openstack-meeting-417:00
Jeffrey4l#endmeeting17:00
*** sbezverk has left #openstack-meeting-417:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Nov 30 17:00:34 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
sdakethanks Jeffrey4l  :)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-11-30-15.59.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-11-30-15.59.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-11-30-15.59.log.html17:00
*** rhallisey has left #openstack-meeting-417:00
portdirectJeffrey4l: thanks for chairing17:00
sdakeJeffrey4l ++17:00
sdakeinc0++17:01
sdakeok dudes, i got work to do :)17:01
*** egonzalez90 has left #openstack-meeting-417:01
*** mgiles has left #openstack-meeting-417:02
*** zhubingbing_ has quit IRC17:05
*** jichen has quit IRC17:05
*** icey_ is now known as icey17:06
*** icey has quit IRC17:06
*** icey has joined #openstack-meeting-417:06
*** matrohon has quit IRC17:07
*** slaweq_ has joined #openstack-meeting-417:11
*** bpokorny has quit IRC17:11
*** cwolferh has left #openstack-meeting-417:11
*** icey has quit IRC17:12
*** icey has joined #openstack-meeting-417:14
*** yamamoto has quit IRC17:14
*** Kevin_Zheng has quit IRC17:15
*** yamamoto has joined #openstack-meeting-417:15
*** Kevin_Zheng has joined #openstack-meeting-417:17
*** yamamoto has quit IRC17:17
*** numans has quit IRC17:17
*** yamamoto has joined #openstack-meeting-417:18
*** hieulq_ has quit IRC17:21
*** pcaruana has quit IRC17:23
*** duonghq has quit IRC17:23
*** slaweq_ has quit IRC17:23
*** woodard has quit IRC17:24
*** bpokorny has joined #openstack-meeting-417:24
*** slaweq_ has joined #openstack-meeting-417:24
*** spzala has quit IRC17:25
*** woodster_ has joined #openstack-meeting-417:33
*** yamamoto has quit IRC17:34
*** slaweq_ has quit IRC17:36
*** inc0 has quit IRC17:37
*** sdake_ has joined #openstack-meeting-417:40
*** sdake_ has quit IRC17:40
*** sdake_ has joined #openstack-meeting-417:40
*** sdake has quit IRC17:44
*** jascott1 has quit IRC17:44
*** yamamoto has joined #openstack-meeting-417:46
*** cathrichardson has quit IRC17:50
*** unicell has quit IRC17:50
*** yamamoto has quit IRC17:51
*** yamahata has quit IRC17:51
*** matrohon has joined #openstack-meeting-417:52
*** vhosakot has left #openstack-meeting-417:53
*** iyamahat has quit IRC17:55
*** spzala has joined #openstack-meeting-417:59
*** bobmel has quit IRC18:00
*** spzala has quit IRC18:03
*** numans has joined #openstack-meeting-418:04
*** ralonsoh has quit IRC18:04
*** cathrichardson has joined #openstack-meeting-418:07
*** galstrom is now known as galstrom_zzz18:08
*** Sukhdev has quit IRC18:11
*** eil397 has joined #openstack-meeting-418:11
*** inc0 has joined #openstack-meeting-418:11
*** inc0 has quit IRC18:11
*** iyamahat has joined #openstack-meeting-418:16
*** bobh has quit IRC18:19
*** tonytan4ever has quit IRC18:19
*** tonytan4ever has joined #openstack-meeting-418:20
*** sdake_ has quit IRC18:22
*** sdake has joined #openstack-meeting-418:22
*** dave-mcc_ has joined #openstack-meeting-418:23
*** galstrom_zzz has quit IRC18:24
*** unicell has joined #openstack-meeting-418:24
*** dave-mccowan has quit IRC18:26
*** tonytan4ever has quit IRC18:27
*** galstrom_zzz has joined #openstack-meeting-418:27
*** tonytan4ever has joined #openstack-meeting-418:28
*** kylek3h has quit IRC18:28
*** yamahata has joined #openstack-meeting-418:35
*** kbyrne has quit IRC18:35
*** Swami has quit IRC18:36
*** Swami has joined #openstack-meeting-418:37
*** kbyrne has joined #openstack-meeting-418:38
*** kylek3h has joined #openstack-meeting-418:41
*** spzala has joined #openstack-meeting-418:43
*** dharinic is now known as dharinic|lunch18:47
*** spzala has quit IRC18:47
*** spzala has joined #openstack-meeting-418:47
*** woodard has joined #openstack-meeting-418:52
*** vishnoianil has quit IRC18:52
*** bpokorny has quit IRC18:55
*** klindgren has joined #openstack-meeting-418:56
*** tonytan4ever has quit IRC19:02
*** reedip_ has quit IRC19:04
*** bobh has joined #openstack-meeting-419:08
*** bpokorny has joined #openstack-meeting-419:08
*** sambetts is now known as sambetts|afk19:10
*** Swami has quit IRC19:11
*** asettle has quit IRC19:13
*** unicell has quit IRC19:14
*** unicell has joined #openstack-meeting-419:17
*** unicell has quit IRC19:22
*** unicell has joined #openstack-meeting-419:24
*** Sukhdev has joined #openstack-meeting-419:24
*** tonytan4ever has joined #openstack-meeting-419:25
*** hemanth is now known as hemanth|lunch19:25
*** dharinic|lunch is now known as dharinic19:28
*** cathrichardson has quit IRC19:29
*** betherly has joined #openstack-meeting-419:35
*** cathrichardson has joined #openstack-meeting-419:37
*** woodard has quit IRC19:39
*** woodard has joined #openstack-meeting-419:39
*** claudiub has quit IRC19:43
*** bpokorny has quit IRC19:51
*** kylek3h_ has joined #openstack-meeting-419:51
*** bpokorny has joined #openstack-meeting-419:51
*** vishnoianil has joined #openstack-meeting-419:52
*** kylek3h has quit IRC19:54
*** bpokorny has quit IRC19:57
*** bpokorny has joined #openstack-meeting-419:58
*** MeganR has joined #openstack-meeting-420:00
*** bpokorny has quit IRC20:02
*** asettle has joined #openstack-meeting-420:14
*** uck has quit IRC20:19
*** matrohon has quit IRC20:19
*** bobmel has joined #openstack-meeting-420:22
*** asettle has quit IRC20:22
*** matrohon has joined #openstack-meeting-420:25
*** srwilkers_ has quit IRC20:26
*** galstrom_zzz is now known as galstrom20:27
*** basilAB has quit IRC20:29
*** basilAB has joined #openstack-meeting-420:29
*** Zer0Byte__ has quit IRC20:34
*** galstrom is now known as galstrom_zzz20:36
*** Zer0Byte__ has joined #openstack-meeting-420:39
*** icey has quit IRC20:41
*** dtardivel has quit IRC20:44
*** Swami has joined #openstack-meeting-420:48
*** spzala has quit IRC20:54
*** MeganR has quit IRC20:56
*** haleyb_ has joined #openstack-meeting-420:57
*** bpokorny has joined #openstack-meeting-420:58
*** bobh has quit IRC20:59
*** haleyb_ has quit IRC21:01
*** Zer0Byte__ has quit IRC21:05
*** Zer0Byte__ has joined #openstack-meeting-421:06
*** Marcellin__ has joined #openstack-meeting-421:08
*** rtheis has quit IRC21:10
*** caboucha_ has quit IRC21:17
*** uck has joined #openstack-meeting-421:19
*** claudiub has joined #openstack-meeting-421:22
*** uck has quit IRC21:24
*** Zer0Byte__ has quit IRC21:24
*** Zer0Byte__ has joined #openstack-meeting-421:25
*** Jeffrey4l_ has joined #openstack-meeting-421:34
*** Jeffrey4l has quit IRC21:35
*** Zer0Byte__ has quit IRC21:43
*** tonytan4ever has quit IRC21:43
*** Zer0Byte__ has joined #openstack-meeting-421:48
*** julim has quit IRC21:49
*** matrohon has quit IRC21:51
*** haleyb_ has joined #openstack-meeting-421:58
*** bobh has joined #openstack-meeting-421:59
*** hongbin has quit IRC22:01
*** Zer0Byte__ has quit IRC22:01
*** haleyb_ has quit IRC22:03
*** cathrichardson has quit IRC22:03
*** bobh has quit IRC22:04
*** claudiub|2 has joined #openstack-meeting-422:09
*** bpokorny has quit IRC22:11
*** slaweq_ has joined #openstack-meeting-422:11
*** claudiub has quit IRC22:13
*** bpokorny has joined #openstack-meeting-422:13
*** kylek3h_ has quit IRC22:17
*** woodard has quit IRC22:19
*** uck has joined #openstack-meeting-422:21
*** sdake_ has joined #openstack-meeting-422:25
*** uck has quit IRC22:25
*** sdake has quit IRC22:28
*** uck has joined #openstack-meeting-422:38
*** bobmel has quit IRC22:39
*** bobmel has joined #openstack-meeting-422:40
*** bobh has joined #openstack-meeting-422:42
*** slaweq_ has quit IRC22:44
*** slaweq_ has joined #openstack-meeting-422:46
*** kylek3h has joined #openstack-meeting-422:47
*** dave-mcc_ has quit IRC22:53
*** haleyb_ has joined #openstack-meeting-422:59
*** pbourke_ has quit IRC23:03
*** haleyb_ has quit IRC23:04
*** uck has quit IRC23:07
*** thorst_ is now known as thorst_afk23:08
*** bpokorny has quit IRC23:10
*** bpokorny has joined #openstack-meeting-423:11
*** Sukhdev has quit IRC23:12
*** unicell has quit IRC23:15
*** bpokorny has quit IRC23:15
*** bpokorny has joined #openstack-meeting-423:18
*** spotz is now known as spotz_zzz23:18
*** pbourke_ has joined #openstack-meeting-423:20
*** unicell has joined #openstack-meeting-423:20
*** spzala has joined #openstack-meeting-423:21
*** asettle has joined #openstack-meeting-423:25
*** spzala has quit IRC23:26
*** pbourke_ has quit IRC23:29
*** asettle has quit IRC23:30
*** spzala has joined #openstack-meeting-423:36
*** claudiub|2 has quit IRC23:37
*** bobh has quit IRC23:39
*** bobh has joined #openstack-meeting-423:39
*** revon has quit IRC23:42
*** bobh has quit IRC23:44
*** lamt has quit IRC23:44
*** hemanth|lunch is now known as hemanth|away23:47
*** rbak has quit IRC23:52
*** Zer0Byte__ has joined #openstack-meeting-423:53
*** eil397 has quit IRC23:56
*** bpokorny has quit IRC23:58
*** bpokorny has joined #openstack-meeting-423:58

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