Wednesday, 2018-10-31

*** salmankhan has quit IRC00:11
*** markvoelker has quit IRC00:49
*** markvoelker has joined #openstack-meeting-400:50
*** seajay has joined #openstack-meeting-400:52
*** markvoelker has quit IRC00:55
*** yamahata has quit IRC01:36
*** iyamahat has quit IRC01:36
*** seajay has quit IRC01:43
*** iyamahat has joined #openstack-meeting-401:52
*** lei-zh has joined #openstack-meeting-401:52
*** hongbin has joined #openstack-meeting-402:02
*** diablo_rojo has quit IRC02:02
*** seajay has joined #openstack-meeting-402:05
*** yamahata has joined #openstack-meeting-402:10
*** mhen has quit IRC02:13
*** mhen has joined #openstack-meeting-402:16
*** seajay has quit IRC02:49
*** markvoelker has joined #openstack-meeting-402:51
*** psachin has joined #openstack-meeting-402:53
*** markvoelker has quit IRC03:24
*** seajay has joined #openstack-meeting-403:29
*** seajay has quit IRC03:30
*** janki has joined #openstack-meeting-403:47
*** hongbin has quit IRC04:01
*** seajay has joined #openstack-meeting-404:03
*** seajay has quit IRC04:04
*** markvoelker has joined #openstack-meeting-404:21
*** yamahata has quit IRC04:35
*** yamahata has joined #openstack-meeting-404:35
*** markvoelker has quit IRC04:54
*** lei-zh has quit IRC05:03
*** pcaruana|elisa| has joined #openstack-meeting-405:29
*** pcaruana|elisa| has quit IRC05:37
*** lei-zh has joined #openstack-meeting-405:39
*** janki has quit IRC05:46
*** janki has joined #openstack-meeting-405:49
*** markvoelker has joined #openstack-meeting-405:51
*** e0ne has joined #openstack-meeting-406:16
*** e0ne has quit IRC06:18
*** janki has quit IRC06:18
*** markvoelker has quit IRC06:26
*** janki has joined #openstack-meeting-406:37
*** markvoelker has joined #openstack-meeting-407:24
*** pcaruana|elisa| has joined #openstack-meeting-407:45
*** gkadam has joined #openstack-meeting-407:54
*** ifat_afek has joined #openstack-meeting-407:55
*** idan_hefetz has joined #openstack-meeting-407:55
*** markvoelker has quit IRC07:57
*** lei-zh1 has joined #openstack-meeting-407:59
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Oct 31 08:00:52 2018 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
*** lei-zh has quit IRC08:01
*** LiangFang has quit IRC08:01
*** eyalb1 has joined #openstack-meeting-408:01
ifat_afekHi :-)08:01
eyalb1\o/08:01
idan_hefetzHi!08:02
*** Liang__ has joined #openstack-meeting-408:04
ifat_afek#topic Status and updates08:04
*** openstack changes topic to "Status and updates (Meeting topic: vitrage)"08:04
ifat_afekLast week we released the first Stein version of python-vitrageclient 2.4.008:04
ifat_afek. I did not release vitrage and vitrage-dashboard, because I’m still waiting for two bug fixes08:04
ifat_afekSince we are working by the cycle-with-intermediary model we don’t have to release by specific dates08:04
ifat_afekBesides that, I spent most of my time preparing a demo for Berlin, so I didn’t progress with Nova versioned notifications08:05
ifat_afekThat’s it for me08:05
idan_hefetzMy update08:05
eyalb1I am finishing up the hands on lab in berlin08:05
eyalb1thats it08:06
idan_hefetz:)08:06
idan_hefetzTo reduce memory consumption of vitrage-graph service, there is a process for handling template api's evaluations (TemplateWorker).08:06
idan_hefetzThis process can be removed by moving it's logic to the evaluator workers.08:06
idan_hefetzAlso,08:07
idan_hefetzAlso, I'm investigating this issue:08:07
idan_hefetz#link https://storyboard.openstack.org/#!/story/177039008:08
*** lei-zh1 has quit IRC08:08
*** yboaron has joined #openstack-meeting-408:11
ifat_afekThanks08:11
*** e0ne has joined #openstack-meeting-408:12
*** liuyulong has quit IRC08:12
ifat_afekAnyone else wants to update? we are very few today…08:12
e0nehi08:13
e0nea really short update from me08:13
ifat_afeke0ne: Hi08:13
e0neI'm working on xstatic-* packages for vitrage-dashboard08:13
ifat_afekGreat08:13
e0neI've got some js errors08:13
e0neso I'll ask some help later today or tomorrow08:14
ifat_afekOk, you should probably talk with Alon08:14
ifat_afekHe’s not on IRC now, but I’ll tell him you need his help08:14
e0neI don't have an environment by the hand, so I can't say now what actually goes wrong08:14
e0neifat_afek: thanks!08:14
*** mnajjar has joined #openstack-meeting-408:14
mnajjarhi08:14
ifat_afekmnajjar: Hi08:15
mnajjari'll update that i'm working on Vitrage lab along side eyalb108:15
mnajjarbuilding image, fixing scenario and custom changes to Vitrage08:16
mnajjarthat's from my side :D08:17
ifat_afekThanks08:17
ifat_afekI guess we are done, unless someone wants to talk about another issue08:17
e0neaccording to the nodejs-npm-run-test job for vitrage-dashboard - I'll propose a patch today to fix it08:17
e0nethat's all from my side for today08:18
ifat_afeke0ne: but does that fix all of the problems, or do you still need Alon’s help?08:18
e0neifat_afek: it's a different issue:(08:18
ifat_afeke0ne: ok, sorry, you got me conused :-)08:19
e0neifat_afek: np08:19
ifat_afekLet’s close the meeting. See you next week!08:20
eyalb1bye08:21
*** eyalb1 has left #openstack-meeting-408:21
ifat_afek#endmeeting08:21
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:21
openstackMeeting ended Wed Oct 31 08:21:31 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2018/vitrage.2018-10-31-08.00.html08:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2018/vitrage.2018-10-31-08.00.txt08:21
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2018/vitrage.2018-10-31-08.00.log.html08:21
*** ktibi has joined #openstack-meeting-408:32
*** mnajjar has quit IRC08:51
*** celebdor has quit IRC08:53
*** markvoelker has joined #openstack-meeting-408:54
*** pcaruana|elisa| has quit IRC09:13
*** Liang__ has quit IRC09:14
*** pcaruana|elisa| has joined #openstack-meeting-409:15
*** e0ne has quit IRC09:16
*** Liang__ has joined #openstack-meeting-409:18
*** e0ne has joined #openstack-meeting-409:25
*** ktibi has quit IRC09:26
*** markvoelker has quit IRC09:27
*** idan_hefetz has quit IRC10:03
*** salmankhan has joined #openstack-meeting-410:05
*** ktibi has joined #openstack-meeting-410:06
*** celebdor has joined #openstack-meeting-410:07
*** markvoelker has joined #openstack-meeting-410:24
*** aperevalov has left #openstack-meeting-410:31
*** yamamoto has quit IRC10:34
*** yamamoto has joined #openstack-meeting-410:34
*** Liang__ has quit IRC10:37
*** yamamoto has quit IRC10:39
*** yamamoto has joined #openstack-meeting-410:40
*** yamamoto has quit IRC10:41
*** markvoelker has quit IRC10:58
*** ktibi has quit IRC10:58
*** ktibi has joined #openstack-meeting-411:13
*** e0ne has quit IRC11:15
*** e0ne has joined #openstack-meeting-411:15
*** e0ne has quit IRC11:27
*** yamamoto has joined #openstack-meeting-411:28
*** yamamoto has quit IRC11:35
*** yamamoto has joined #openstack-meeting-411:35
*** yboaron has quit IRC11:42
*** seajay has joined #openstack-meeting-411:46
*** markvoelker has joined #openstack-meeting-411:54
*** seajay has quit IRC11:56
*** pbourke has quit IRC12:09
*** pbourke has joined #openstack-meeting-412:10
*** markvoelker has quit IRC12:13
*** markvoelker has joined #openstack-meeting-412:13
*** markvoelker has quit IRC12:15
*** jchhatbar has joined #openstack-meeting-412:28
*** jchhatbar has quit IRC12:28
*** janki has quit IRC12:29
*** janki has joined #openstack-meeting-412:29
*** celebdor has quit IRC12:44
*** yamamoto has quit IRC12:44
*** yboaron has joined #openstack-meeting-412:56
*** ifat_afek has quit IRC12:56
*** gkadam has quit IRC12:57
*** ktibi has quit IRC13:00
*** celebdor has joined #openstack-meeting-413:01
*** gkadam has joined #openstack-meeting-413:03
*** yamamoto has joined #openstack-meeting-413:04
*** e0ne has joined #openstack-meeting-413:06
*** liuyulong has joined #openstack-meeting-413:19
*** janki has quit IRC13:22
*** janki has joined #openstack-meeting-413:23
*** sambetts|afk is now known as sambetts13:28
*** slaweq has quit IRC13:29
*** yamamoto has quit IRC13:37
*** yamamoto has joined #openstack-meeting-413:38
*** yamamoto has quit IRC13:38
*** ifat_afek has joined #openstack-meeting-413:52
*** ifat_afek has left #openstack-meeting-413:57
*** yamamoto has joined #openstack-meeting-414:00
*** JamesBenson has joined #openstack-meeting-414:09
*** ktibi has joined #openstack-meeting-414:12
*** JamesBenson has quit IRC14:13
*** hongbin has joined #openstack-meeting-414:14
*** e0ne has quit IRC14:19
*** JamesBenson has joined #openstack-meeting-414:26
*** e0ne has joined #openstack-meeting-414:26
*** e0ne has quit IRC14:41
*** slaweq has joined #openstack-meeting-414:41
*** e0ne has joined #openstack-meeting-414:44
*** ktibi has quit IRC14:50
*** hrw has joined #openstack-meeting-414:50
*** mpiwowarczy has joined #openstack-meeting-414:58
*** mgoddard has joined #openstack-meeting-415:01
*** slaweq has quit IRC15:01
egonzalez#startmeeting kolla15:02
openstackMeeting started Wed Oct 31 15:02:47 2018 UTC and is due to finish in 60 minutes.  The chair is egonzalez. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: kolla)"15:02
openstackThe meeting name has been set to 'kolla'15:02
egonzalez#topic rollcall15:02
*** openstack changes topic to "rollcall (Meeting topic: kolla)"15:02
mgoddard\o15:03
spsurya\o15:03
chasono/15:03
hrwo/15:03
egonzalez#topic agenda15:04
*** openstack changes topic to "agenda (Meeting topic: kolla)"15:04
egonzalez* Roll-call15:04
egonzalez* Announcements15:04
egonzalez* Fast Forward Upgrade15:04
egonzalez* open discussion15:04
egonzalez* placement API split from nova15:05
egonzalezmissed last item15:05
egonzalez#topic Announcements15:05
*** openstack changes topic to "Announcements (Meeting topic: kolla)"15:05
egonzalezhi, thanks for comming the meeting, i dont have any announcement for today15:05
egonzalezanyone have any update?15:05
pbourkeo/15:06
spsuryaegonzalez:  yes15:06
egonzalezspsurya go ahead15:06
spsuryaI presented session in Open Source India Days15:06
spsuryait was related to migration wit Kolla15:06
spsuryavery much people were interested in Kolla15:07
egonzaleznice, good work spsurya15:07
egonzalezhave a link to slides or video?15:07
*** jmccarthy has joined #openstack-meeting-415:07
spsuryaOpen Source India Days is largest open source event in Asia15:08
spsuryaegonzalez:  i will share, video is not live15:08
egonzaleznice15:08
spsuryaalso available only to attendees15:08
*** dkrol has joined #openstack-meeting-415:09
egonzalezspsurya thanks for the update15:09
spsuryaso overall Kolla is in demand with respect to other OpenStack deployment tool15:09
egonzalezanything else?15:09
spsuryaegonzalez: all from my side for announcement15:10
egonzalezthats good, thanks spsurya15:11
egonzalezlets move to next topic15:11
egonzalez#topic Fast Forward Upgrade15:11
*** openstack changes topic to "Fast Forward Upgrade (Meeting topic: kolla)"15:11
egonzalez#link https://blueprints.launchpad.net/kolla-ansible/+spec/fast-forward-upgrades-support15:11
egonzalez#link https://review.openstack.org/#/c/548101/15:11
egonzalez#link https://review.openstack.org/#/c/556568/15:11
egonzalezspsurya you added the items to the agenda, wanna hold this topic?15:12
spsuryaegonzalez: yes15:12
spsuryaegonzalez: i wanted to bring this to agenda15:12
spsuryaif i can give hand into it15:12
spsuryaplease let me know15:12
*** donghm_ has joined #openstack-meeting-415:12
spsuryalike testing perspective as well as implementation15:13
pbourkeis this patchset oversimplifying thigns a little?15:13
pbourkeoften there's more steps required when moving between releases than db migrations15:13
egonzalezpbourke no is different upgrade path15:13
egonzalezfor those who are not familiar with fast forward upgrades (FFU) here is the description from the FFU-SIG15:14
egonzalezA fast-forward upgrade is an offline upgrade which effectively runs the upgrade processes for all versions of openstack components from your originating version to your desired final version.15:14
egonzalez#link https://wiki.openstack.org/wiki/Fast_forward_upgrades15:14
spsuryapbourke: please review those patchsets15:14
egonzalezas short resume, stop the whole control plane to jump from version to version faster15:15
spsuryawould be a great help like what else needed otherthan db migration15:15
spsuryaegonzalez: pbourke  i have pushed spec for FFU with Kolla-ansible in WIP https://review.openstack.org/#/c/614508/15:16
egonzalezthis  means, only upgrade db schemas for each service in one node, and in last iteration bring all services to the desired version15:16
*** donghm_ has quit IRC15:16
pbourkea good example is the introduction of the nova cell stuff15:16
pbourkehow would that be handled in this situation15:16
mgoddardpbourke: isn't that all done via nova-manage?15:17
egonzalezpbourke yep, thats the main issues in that situation, hopefully that release has passed and we already have cells_v2 ;)15:17
mgoddardI guess it does wait for things to be registered though15:17
pbourkeegonzalez: not if I want to fast forward through that release ;)15:17
mgoddardhave we defined which releases are supported?15:18
egonzalezshould we backport the ffu feature?15:18
mgoddardi.e. from how far back can you FFU?15:18
pbourkethat's an extreme example though15:18
pbourkebut there's other stupid sh*t15:18
mgoddardFFU support is only required in the target release, right?15:18
egonzalezin the case of cells_v2, only thing required to bring up would be nova-api, conductor, placement and one compute15:19
spsuryamgoddard: yes, FFU is for higher release15:19
*** dave-mccowan has joined #openstack-meeting-415:19
pbourkeunless there's been advancements since I last looked at this the only reliable way to FFU was to manually install and upgrade each release15:19
mgoddardspsurya: higher release?15:19
mgoddardoh, I see15:20
spsuryamgoddard: means newton--> rokcy           newton-->stein   etc15:20
mgoddardI think we need to pick specific examples and define what "stupid sh*t" is required :)15:20
spsuryamgoddard: egonzalez https://review.openstack.org/#/c/614508/15:21
mgoddarde.g. initially work on queens -> stein15:21
egonzalezbe aware that the config files for the upgrade should be compatible with all the releases15:21
spsuryai will update in problem description15:21
spsuryamgoddard:15:21
egonzalezfor example nova's stein config is not compatible on some option in rocky, so using latest code to jump through various version wont be easy15:22
spsuryawe need bring the spec in final shape to do target implementation IIUC15:22
mgoddardegonzalez: surely only the latest config is used?15:23
mgoddardi.e. latest nova-manage and updated nova.conf are used to upgrade the DB15:23
egonzalezmgoddard latest code, or only support ffu from stein (if implemented) to newers15:23
egonzalezthats not possible, db schemas doesnt allow version skip15:24
egonzalezIMHO, we should only support FFU from the version implemented in master to newers15:24
mgoddardthe DB manage just syncs the DB to the latest supported by the version of nova-manage, right?15:25
*** dave-mccowan has quit IRC15:25
mgoddardegonzalez: I disagree - I don't see why the source version matters15:25
mgoddardto upgrade, the first thing you do is to upgrade kolla-ansible15:26
mgoddardso whatever is in the old version doesn't matter15:26
egonzalezyes, if only want to upgrade one release15:26
mgoddardunless we need to change patterns to make things compatible15:26
spsuryamgoddard: egonzalez version should not be the case in FFU while migrating db....me be i have check more15:26
egonzalezin case of +2 upgrades, will need to jump through each release15:26
mgoddardok, so we would not actually skip versions, but perform multiple upgrades while offline?15:28
egonzalezyes, skip version is not supported by the projects15:28
mgoddardhmm, so really this feature is 'offline upgrades'15:28
egonzalezIIRC nova said in 2017 denver summit that they wont support version skip15:28
egonzalezmgoddard yes, thats how FFU works now15:29
spsuryamgoddard: egonzalez IIRC i have seen someone from the community wrote the scripts for FFU while going through each releases, as per my dublin PTG update15:29
egonzalezbut trying to minimize downtime by only upgrading one api node, do db syncs and then upgrade all other's nodes15:29
mgoddardok, so we could support an offline upgrade to stein15:29
*** slaweq has joined #openstack-meeting-415:29
egonzalezyes, a FFU would be more like two offline upgrades15:30
mgoddardand in T we could support an FFU15:30
egonzalezyes15:30
mgoddardgot it. sorry for being slow :)15:31
egonzalezthats why in the ansible code is not called FFU, is offline upgrade to make things clear15:31
spsuryaegonzalez: +115:32
egonzalezFFU is like a dark definition of a offline upgrade through various releases without bringing all control plane up15:33
egonzalezwe can discuss this more in the spec15:33
egonzalezonce more data is added we should add ffu-sig ML to be aware of it15:33
spsuryayes15:35
egonzalezcould we move this discussion into the spec review? we have other item in the agenda to talk about15:35
mgoddard+115:35
egonzalezwe're finally bussy in a meeting :)15:35
egonzalez#topic placement API split from nova15:35
*** openstack changes topic to "placement API split from nova (Meeting topic: kolla)"15:35
egonzalez#link https://review.openstack.org/#/c/613629/15:36
egonzalez#link https://review.openstack.org/#/c/613589/15:36
egonzalezas you will probably aware, placement api is finally being splitted into its own project15:36
egonzalezthey will finish the work for this cycle15:36
egonzalezfor now, they've migrated the api code, main thing missing is the placement-manage which is not implemented yet15:37
egonzalezthe links in the topic are the starting point of splitting the API from nova roles/images15:38
egonzalezplease feel free to review and take over work on it15:38
egonzalezthey need some project to finish the migration so they make sure nothing gets broken in existing evironments15:39
spsuryaegonzalez: thanks for update15:39
mgoddardthanks for starting that work egonzalez. are you saying you don't have time to finish it?15:39
egonzalezi have, but if we are working more on it, faster will get done15:39
spsuryaegonzalez: +115:39
mgoddardcool15:40
egonzalezanyway we're blocked until placement-manage is not implemented15:40
spsuryayes it should be finished nova side15:40
egonzalezwe could use dev mode to fetch the placement-manage change15:40
egonzalezhere's the ML thread15:41
egonzalez#link http://lists.openstack.org/pipermail/openstack-dev/2018-October/136075.html15:41
egonzalezthere you have more information and links to reviews15:41
egonzalezany question about this topic or something to add?15:43
egonzalezguess not, lets move to open discussion15:44
egonzalez#topic open discussion15:44
*** openstack changes topic to "open discussion (Meeting topic: kolla)"15:44
egonzalezanything else to discuss on todays meeting?15:45
spsuryahow many kolla cores are going to Berlin Summit ?15:45
mgoddardo/15:45
egonzalezI am15:45
spsuryamy travel is pending as of now.....waiting for green flag from Org ;)15:46
egonzalezbest luck spsurya15:46
egonzalezpbourke you going?15:46
spsuryathanks egonzalez :)15:47
egonzalezin berlin i think we will be more than in denver (even not being that much from the core)15:48
egonzalezbut many contributors15:48
pbourkeegonzalez: no plans currently15:48
spsuryaseems so egonzalez15:48
egonzalez:(15:48
egonzalezanyway, any topic for the meeting or we can move to #openstack-kolla ?15:49
egonzalezthank you all for attending the meeting, have a nice day :)15:51
spsuryathanks egonzalez mgoddard pbourke for FFU discussion15:51
egonzalez#endmeeting15:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:51
spsuryathanks all15:51
openstackMeeting ended Wed Oct 31 15:51:32 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2018/kolla.2018-10-31-15.02.html15:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2018/kolla.2018-10-31-15.02.txt15:51
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2018/kolla.2018-10-31-15.02.log.html15:51
*** mgoddard has left #openstack-meeting-415:51
*** markvoelker has joined #openstack-meeting-415:51
*** celebdor has quit IRC16:01
*** ktibi has joined #openstack-meeting-416:03
*** janki has quit IRC16:13
*** gkadam has quit IRC16:20
*** seajay has joined #openstack-meeting-416:21
*** seajay has quit IRC16:22
*** JamesBenson has quit IRC16:24
*** hrw has left #openstack-meeting-416:33
*** pcaruana|elisa| has quit IRC16:37
*** JamesBenson has joined #openstack-meeting-416:43
*** JamesBenson has quit IRC16:52
*** JamesBen_ has joined #openstack-meeting-416:52
*** celebdor has joined #openstack-meeting-416:54
*** celebdor has quit IRC16:54
*** celebdor has joined #openstack-meeting-416:55
*** diablo_rojo has joined #openstack-meeting-416:56
*** jmccarthy has left #openstack-meeting-416:59
*** e0ne has quit IRC17:08
*** ktibi has quit IRC17:15
*** iyamahat has quit IRC17:42
*** yamahata has quit IRC17:44
*** sambetts is now known as sambetts|afk17:46
*** iyamahat has joined #openstack-meeting-417:59
*** yamahata has joined #openstack-meeting-418:19
*** yboaron has quit IRC18:25
*** celebdor has quit IRC18:28
*** e0ne has joined #openstack-meeting-418:31
*** e0ne has quit IRC18:32
*** celebdor has joined #openstack-meeting-418:32
*** psachin has quit IRC18:36
*** celebdor has quit IRC18:56
*** iyamahat has quit IRC19:02
*** iyamahat has joined #openstack-meeting-419:03
*** salmankhan has quit IRC19:07
*** iyamahat_ has joined #openstack-meeting-419:07
*** iyamahat has quit IRC19:08
*** iyamahat_ has quit IRC19:18
*** diablo_rojo has quit IRC19:26
*** yboaron has joined #openstack-meeting-419:29
*** celebdor has joined #openstack-meeting-419:40
*** e0ne has joined #openstack-meeting-419:44
*** e0ne has quit IRC19:45
*** diablo_rojo has joined #openstack-meeting-419:45
*** celebdor has quit IRC19:59
*** iyamahat_ has joined #openstack-meeting-420:02
*** liuyulong has quit IRC20:18
*** e0ne has joined #openstack-meeting-420:30
*** salmankhan has joined #openstack-meeting-420:45
*** e0ne has quit IRC20:50
*** salmankhan has quit IRC20:50
*** yboaron has quit IRC21:04
*** spiette has quit IRC21:06
*** dkrol has quit IRC21:27
*** mhen has quit IRC21:28
*** mhen has joined #openstack-meeting-421:33
*** spiette has joined #openstack-meeting-421:51
*** JamesBen_ has quit IRC22:05
*** diablo_rojo has quit IRC22:18
*** salmankhan has joined #openstack-meeting-422:18
*** salmankhan has quit IRC22:25
*** diablo_rojo has joined #openstack-meeting-422:50
*** hongbin has quit IRC23:06
*** JamesBenson has joined #openstack-meeting-423:22
*** JamesBenson has quit IRC23:26
*** diablo_rojo has quit IRC23:45

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