Wednesday, 2017-03-15

*** ricolin has joined #openstack-meeting-501:54
*** markvoelker has quit IRC03:06
*** markvoelker has joined #openstack-meeting-504:07
*** markvoelker has quit IRC04:13
*** markvoelker has joined #openstack-meeting-506:09
*** markvoelker has quit IRC06:13
*** matrohon has joined #openstack-meeting-507:55
*** matrohon has quit IRC08:02
*** markvoelker has joined #openstack-meeting-508:10
*** markvoelker has quit IRC08:14
*** rarcea has joined #openstack-meeting-508:43
*** matrohon has joined #openstack-meeting-508:50
*** ralonsoh has joined #openstack-meeting-508:55
*** skazi has quit IRC09:42
*** dmellado has quit IRC09:54
*** skazi has joined #openstack-meeting-509:56
*** dmellado has joined #openstack-meeting-510:02
*** markvoelker has joined #openstack-meeting-510:10
*** markvoelker has quit IRC10:15
*** ralonsoh has quit IRC11:32
*** markvoelker has joined #openstack-meeting-512:11
*** markvoelker has quit IRC12:16
*** markvoelker has joined #openstack-meeting-512:38
*** tongli has joined #openstack-meeting-513:23
*** mafei has joined #openstack-meeting-513:24
*** Thor_ has joined #openstack-meeting-513:24
*** mafei has quit IRC13:26
*** feima has joined #openstack-meeting-513:27
*** kbaikov has joined #openstack-meeting-513:29
*** markvoelker_ has joined #openstack-meeting-513:54
*** vkmc has joined #openstack-meeting-513:55
*** markvoelker has quit IRC13:55
*** cschwede has joined #openstack-meeting-513:56
*** zhipeng has joined #openstack-meeting-513:56
*** tiantian has joined #openstack-meeting-513:57
*** tdasilva has joined #openstack-meeting-513:57
tonglihello.14:00
feimahello14:01
vkmchi14:01
tongliPing dmellado tongli gema zhipengh markvoelker daniela_ebert skazi luzC gcb hodgepodge yaohelan eeiden kgarlofftongl14:01
Thor_Hi14:01
vkmcI'm joining in place of dmellado today :)14:01
tongli#startmeeting interop_challenge14:01
openstackMeeting started Wed Mar 15 14:01:49 2017 UTC and is due to finish in 60 minutes.  The chair is tongli. 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: interop_challenge)"14:01
openstackThe meeting name has been set to 'interop_challenge'14:01
zhipengi thought the meeting is one hour later14:02
markvoelker_o/14:02
skazio/14:02
tongliHi, everyone, who is here for the interop challenge meeting today?14:02
feimaHi everyone, I am Fei Ma, from China OpenSource Cloud Alliance for industry (OSCAR)14:02
tongliwelcome @feima.14:02
feimaThis is my first time to here.14:02
feimathank you, tongli14:02
tongliBrad has a conflict today , he asked me to chair this meeting.14:03
feimaok14:03
Thor_Hi everyone, this is Thor from inwinSTACK and this is also my first time to join this meeting14:03
tongliwelcome @Thor_14:03
* topol brad about to hop on a plane. THANKS tongli for leading today!!14:03
tongliYes, I saw your email, glad that you are here.14:04
*** linux_ has joined #openstack-meeting-514:04
tongli@topol, thanks14:04
Thor_good to see you and everybody too14:04
tongliok, we are 5 minutes past the hour, let's start.14:05
tongli#topic Review last meeting action items14:05
*** openstack changes topic to "Review last meeting action items (Meeting topic: interop_challenge)"14:05
tonglihttp://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-08-14.00.html14:05
*** Daisy has joined #openstack-meeting-514:05
tongliwe had a short meeting last time. the only action was to schedule Alex from coreos community and Mark to participate in this meeting.14:06
tongliI had few emails exchanges with Alex from coreos.14:06
tonglion the k8s workload.14:06
tonglihe suggested us to use a tool that coreos uses to stand up k8s cluster.14:07
tongliThe tool is called Tectonic.14:07
Thor_https://coreos.com/tectonic/14:08
tongliThe issue is that Tectonic is a tool sold by coreos.com, it is not an open source software.14:09
tonglihowever, 10 nodes or less is free.14:09
tongliso I assume we are not interested in switching to that tool.14:09
tongliany one object to that, please speak up.14:09
markvoelker_I suppose we *could*...given the time constraint we're probably not going to spin up more than 10 nodes anyway...but I'm not sure there's any real impetus to do so.14:10
linux_Well, using it might be a strong endorsement of this tool -- it's not clear to me whether we would want to do this, especially if it's a commercial tool.14:11
tongli@markvoelker, I had made a lot of improvement to our ansible based k8s workload.14:11
*** linux_ is now known as garloff14:11
tonglinow provisioning VM on openstack is done parallel.14:11
tonglithat is where we spent most of time,14:11
tongliwith that improvement, my 8 VM nodes k8s clusters entire run finishes within 8 minutes.14:12
vkmcI wouldn't use a tool that is not open source for an effort of an open source community14:12
garlofftongli: We have like 10 -- 12 mins again for the showcase?14:12
tongliI think we may go 15 minutes, but that will be the most time we have.14:13
garloffvkmc: exactly, that would be my default approach as well to this question14:13
markvoelker_tongli: fair point.  Even so though, sentiment seems to be there's not really much incentive to use Tectonic here.14:13
tongliI think we may go with 8 nodes since Mark hinted that 3 nodes is too small.14:13
tonglido not think Tectonic can stand up k8s cluster against ubuntu, but I am not sure about that.14:14
tongliI will give it some time next week to see how it works. and will report back.14:15
tonglifor now, I think we are sticking with Ansible scripts, everyone agrees with that?14:15
markvoelker_++14:15
garlofftongli: sure, that's a proven approach14:16
tonglianyone else?14:16
tongliif no, I think #decision, we stick with Ansible script for k8s workload.14:16
tonglithis week I am in Milan for openstack operator midcycle meetup.14:17
tonglithere are quite few session on containers.14:18
vkmc++14:18
tongliseems to me that OpenStack operators have very little experiences running k8s on openstack.14:18
tonglithis is the area very hot but not many people have actually been running k8s to serve their customers.14:19
garlofftongli: Containers are a challenge for operators b/c of a new (and sometimes not well defined) share of responsibility b/w Devs and Ops14:19
tonglibut there are vendors actively trying to do things with k8s14:19
tongli@garloff, agreed.14:20
tonglistill a lot of learnings to do.14:20
tonglifrom developers to operators.14:20
tongliso this group IMHO is doing something quite exciting. I mean both k8s workload and NFV workload.14:21
tongliok, let's move on to our Agenda.14:21
tonglihttps://review.openstack.org/#/q/status:open+project:openstack/interop-workloads,n,z14:21
tongli#topic review patch sets14:22
*** openstack changes topic to "review patch sets (Meeting topic: interop_challenge)"14:22
tongliwe have 4, one is very minor, on  the readme doc at the root.14:22
tonglisomeone please take a quick look https://review.openstack.org/#/c/440027/14:23
tongliit is like one word change.14:23
tonglithen we have two nfv patch sets. we need to review these patches.14:24
tongliand of course the k8s workload, sits at patch #2914:24
tongliit is getting very big now. 1712 lines.14:25
tonglibut since we are deploying k8s dashboard, dns, and cockroachdb pods, we need to general k8s spec yaml files.14:26
tonglithese files normally are pretty big, we have 3 this type of files sized around 500 lines.14:26
tongliso we do not have many lines of code if we take away these spec files and template files.14:26
tongliplease review the code and run the workload.14:27
zhipengI think helen could give a update about the nfv workload ?14:27
tongliit will be really nice if we can get it merged soon.14:27
tongli@zhipeng, sure, let me finish the k8s workload.14:28
zhipengtongli okey :)14:28
tonglithere was one review comment regarding the license headers .14:28
tonglimy take is that we already have apache2 license file at the root of the project.14:28
tonglido we need license header on each individual file?14:28
tonglisomeone suggested to add to the README.rst file, but most openstack project do not place license headers on README.rst file.14:29
tongliso I do not think we should do that. what do you guys think?14:29
dmelladoo/14:29
tongli@dmellado, good timing.14:30
dmelladohey tongli, I don't really have a strong opinion on that, so disregard that change if you want to14:30
tongliwe started talking about the license thing.14:30
dmelladothat said, luzC did you want to add that license to all yaml files?14:30
dmelladoIMHO it could be a li'l overkill14:30
tongliI do not think we have LuzC today.14:30
markvoelker_tongli: https://wiki.openstack.org/wiki/LegalIssuesFAQ#Copyright_Headers14:30
dmelladomarkvoelker_: tongli I guess that we're just fine with that14:31
markvoelker_"In general, ..... Always keep the license in the header"14:31
markvoelker_So probably best practice to do so (most other projects do this too IIRC)14:32
markvoelker_See also: https://docs.openstack.org/developer/hacking/#openstack-licensing14:32
dmelladohey markvoelker_ yep14:32
markvoelker_"All source files should have the following header"14:32
dmelladothat's waht luzC and we were speaking about14:32
dmelladoso TODO: add Apache license to source files ;)14:33
dmelladowould that be fine for you tongli?14:33
dmelladonot that is urgent in any case, but we should address that14:34
tongli@dmellado,@markvoelker_, can someone go through this and add copyright headers to source files?14:34
markvoelker_Sure, I'll take a look this week14:34
dmelladotongli: sure, I'll try to automate that as much as possible, so I'll be sending some patches14:35
tongligreat. I am trying to let our guys review the patch and get it through, then we fix the copyright thing.14:35
dmellado+114:35
tongliotherwise, this patch set gets even bigger, and harder to review.14:35
garloff+114:35
*** skazi_ has joined #openstack-meeting-514:36
tongliplease review https://review.openstack.org/#/c/433874/14:36
markvoelker_works for me14:36
tongliplease review and let's get this going. it is not easy for guys wanting to run the workload as a patch.14:37
tongliok. please review all the four patch sets we have outstanding.14:37
tongli#action mark will look into the copy right and submit a patch to fix this requirement.14:38
tongli@zhipeng, @hellenyao, can you update on the NFV workload?14:38
HelenYaoSure. The deployment for OPEN-O and clearwater is done. I am working on test scripts to verify the deployment and it will be done shortly. It is able to support both Keystone v2 and v3. I would suggest to start to run the workload on cloud to explore the potential limitation14:39
HelenYaoI will also fix the copyright header14:39
zhipengso in short we are able to deploy the nfv workload using ansible now14:39
zhipengwe are working on the functional testing part14:40
tongli@HelenYan, I looked at the patch and just wonder if it is all possible to use the configuration file instead of using env viriables.14:40
HelenYaotongli: I saw ur comment. I will try to make use of config file14:41
tongliall other workload we develoepd use configuration files , that is the place you have your cloud info, any variables.14:41
tongliwhen you run it, you do not really care if you are in a different console or if you have set the variables.14:41
tongliit also sets up an example to others.14:42
tongliif it is all possible, I would like to have it.14:42
garloffexcept for passwords, which you might not normally have in a config file ...14:42
tongli@garoff, except password, well that should be specified as a password field.14:42
tongliif you really really want to put in that file, you can, if not, command line.14:42
garloffgood, just making sure ...14:43
HelenYaogarloff, tongli: got it. It makes sense to make the code work in a consistent way14:43
zhipengand another question for the interop-challenge team is that14:43
tonglithe problem with command line is that when we do demos, I would rather put the password in the conf file.14:43
zhipengif we were to demo it14:43
tonglisince everyone will see my command line.14:43
tonglithe idea is that you can put either in the conf file or command line.14:44
garlofftongli: I would pass $OS_PASSWORD there, noone will see it :-)14:44
tonglicorrect, so we should have options in any case.14:44
tonglijust little thing.14:44
zhipengshould we demo the interoperability between different OpenStack versions which the NFV workload deploys on14:44
tongli@HelenYao @zhipenghuang, I will try the workload next week and provide feedback.14:45
HelenYaotongli: great14:45
dmelladowe could as well support os-client-config14:45
dmelladoshouldn't be that much work14:45
dmelladohttps://docs.openstack.org/developer/os-client-config/14:45
dmelladobut yeah, we do have several options ;)14:45
zhipengdo we have an answer for my previous question ?14:46
zhipengtongli okey wait for you tryouts14:47
tongli@zhipeng, in terms of different releases of the openstack, in the past we have made sure that the workload runs on past 3 recent releases.14:47
zhipengtongli the "make sure" is part of the interop testing ?14:47
zhipengor a precondition ?14:47
dmelladozhipeng: basically it all depends on the shade library14:47
dmelladoand also on tempest14:47
tongliI am not sure if NFV requires any new features from more recent release.14:47
tongliok, we need to leave some time for @feima to update14:48
dmelladoHelenYao: which version is the cloud that you're running this against?14:48
HelenYaomitaka and newton14:49
dmelladoack, thanks14:49
HelenYaoboth are tested14:49
tongliI have mitaka and newton, I will run against these two.14:49
tongliany other things before we give the floor to @feima?14:49
feimathank you, tongli. i am alive:-)14:50
tongliok. it is all yours now, please proceed. @feima.14:50
feimaok14:50
tongli#topic Mafei from Interop Challenge China chapter14:51
feimaChina OpenSource Cloud Alliance for industry (OSCAR) will hold the Global Cloud Computing summit in Beijing April 19 to 20, and we have invited Mike Perez and Tong Li to attend the summit.14:51
*** openstack changes topic to "Mafei from Interop Challenge China chapter (Meeting topic: interop_challenge)"14:51
feimaIn the summit, we will have a InterOp show similar to Barcelona.14:51
feimaUnder the guidance of OSCAR, there are eight Chinese companies have finished the LAMP and docerswarm testing, and they have submit some bugs and patches to the community.14:51
feimaWe are testing the k8s workload now, at the same time, we will encourage everyone to go into the community.14:51
feimaWe plan to choose one workload to show, and how do you think?14:52
feimaLAMP, dockerswarm or k8s?14:52
feimathat`s all14:52
dmelladofeima: cool, looking forward to meet you at Boston ;) IIRC, the chosen workload for the keynote would be k8s14:53
dmelladowasn't it, tongli ?14:53
tongliconsider k8s has not been shown by the foundation.14:53
tongli@dmellado, yes, foundation has committed to show k8s workload.14:53
feimai will go to Boston,dmellado14:53
tongliand foundation has very specific requirements how the workload should be done. such as what image to use and what apps to show14:54
tongliat present, it will be k8s on coreos image to show cockroachdb cluster with cockroachdb UI.14:54
*** therve has joined #openstack-meeting-514:54
tongliso it may not be very nice to steal foundation's thunder.14:55
feimaI wonder if it is good to show a same demo as the Boston summit14:55
tonglishowing off the lampstack may be good especially the lampstack workload showed in Barcelona was a plain wordpress site.14:55
tonglithe latest lampstack workload shows OpenStack superuser site.14:56
tongliall the themes and artifacts came from foundation.14:56
feimaand, there is only 1 month left before the Beijing open source summit. I don't know if the time is enough to get K8s ready.14:56
tongliso the content will be a bit different comparing to the one in Barcelona.14:56
tongli@feima, good point,  k8s workload is not complete, but lampstack is.14:57
zhipenglampstack would be a good choice14:57
* luzC luzC enter and sit at the back14:57
feimaDo you think if it's better to show a China specific website other than OpenStack superuser site ? @tongli14:57
dmelladotongli: that said, I don't think that we'll have time to show more than 1 demo14:57
dmelladojust recall at BCN, we were kinda short on time ;)14:57
tongli@feima, if want to do that, then we need to deploy a different wordpress app on the lampstack.14:57
feimai agree @zhipeng14:57
feimayes,@tongli14:58
tongli@dmellado, yes, just one workload. not two or more.14:58
dmelladofeima: zhipeng the idea is that, way before the summit the k8s workload would be totally operational14:58
dmellado;)14:58
garloffwe need to ensure this, yeah14:59
feimaso we show lampstack in Beijing, but need a different app?14:59
tongliand many companies have completed the successful runs many times.14:59
tonglithat is not the current state of k8s workload.14:59
tongliguys, we ran out time.15:00
feimaok15:00
feimathank you very much15:00
feimaall of you15:00
ricolinthx:)15:00
tongli#decision, global summit uses lampstack workload.15:00
feimaok15:00
dmelladotongli: didn't we just agree on k8s15:01
dmelladoor are you speaking about the beijing one15:01
dmellado?15:01
tongligreat. thanks everyone. sorry for cutting this short but we run out time.15:01
tongli@dmellado, that decision is for april beijing summit.15:01
dmelladotongli: ack then ;)15:01
tonglifor boston summit, we run k8s workload.15:01
tonglithat is also part of the reason why beijing summit should not use the k8s workload since it has not been used by the foundation.15:02
tongliall right, guys, thanks so much and please review patches and run the workload.15:03
ricolin:)15:03
tongliif your company has not signed up for the boston on stage keystone demo, you should do that before the spots run out.15:03
feimathx15:03
tongli#endmeeting15:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:03
openstackMeeting ended Wed Mar 15 15:03:54 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-15-14.01.html15:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-15-14.01.txt15:03
openstackLog:            http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-15-14.01.log.html15:04
ricolin#startmeeting heat15:04
openstackMeeting started Wed Mar 15 15:04:08 2017 UTC and is due to finish in 60 minutes.  The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:04
*** openstack changes topic to " (Meeting topic: heat)"15:04
openstackThe meeting name has been set to 'heat'15:04
ricolin#topic roll call15:04
*** openstack changes topic to "roll call (Meeting topic: heat)"15:04
zanebo/15:04
*** skraynev has joined #openstack-meeting-515:04
ricolinhi15:04
skraynevщ.15:04
tiantiano/15:04
skraynevo/15:04
zanebskraynev: lol15:05
ricolinщ.!?15:05
skraynevwrong keyboard layout  :)15:05
skraynevit the same as o/15:05
skraynev:)15:05
feimao/15:05
*** Daisy has quit IRC15:06
*** feima has quit IRC15:06
ricolinskraynev I will remember that!15:06
ricolin#topic adding items to agenda15:07
*** openstack changes topic to "adding items to agenda (Meeting topic: heat)"15:07
ricolin#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-03-15_1500_UTC.2915:07
*** mohankumar has joined #openstack-meeting-515:09
ricolin#topic BOS Brainstorming15:09
*** openstack changes topic to "BOS Brainstorming (Meeting topic: heat)"15:09
ricolin#link https://etherpad.openstack.org/p/BOS-Heat-brainstorming15:10
ricolinRight now is the brainstroming period15:10
*** Thor_ has quit IRC15:10
ricolinfeel free to put any ideas in etherpad15:11
ricolinalso if you will attend Boston summit, would be great if you put your name in attendee list:)15:12
zanebI added an idea15:13
*** tongli has quit IRC15:13
ricolincool!15:13
zanebI can probably attend but nothing is confirmed yet15:13
ricolinpotentially we will require both developer and user to be there as a `Forum`15:15
ricolinwill try to make some discussion in mailing list for all ideas in etherpad:)15:15
ricolin#link https://wiki.openstack.org/wiki/Forum/Boston201715:16
ricolinhere is all other etherpad for Forum, so feel free to check on any cross projects15:16
ricolinmove on15:17
ricolin#topic amqp gate15:17
*** openstack changes topic to "amqp gate (Meeting topic: heat)"15:17
therveIt works, but it's slow15:17
therveOriginally the driver only supported centos, so I went with it, but ubuntu seems to work now15:18
therveI may be faster, so I think I'll try that15:18
ricolin+115:19
therveThat'll be 3 different convergence gate though15:19
therveI wonder if we could consolidate it with the non apache one15:19
ricolinwe have suffer with amqp this week, we really need some speed up IMO15:20
therveSuffer with amqp? How so?15:20
ricolinJust sense the last gate issue might have something todo with it15:21
therveI'm talking about the non-voting gate, so I doubt it :)15:22
ricolinsure15:22
therveAnyway, that's all I had15:23
ricolinnice:)15:24
ricolin#topic Py3 gate suffering with devstack15:25
*** openstack changes topic to "Py3 gate suffering with devstack (Meeting topic: heat)"15:25
ricolintherve yours too:)15:25
therveSo yeah15:25
therveThe advice we got at the PTG to rely on classifier was outdated15:26
therveSo when we enabled swift, it tried to install with python315:26
therveI made a patch to make it uses python215:26
therveAnd now swift fails with an import error15:26
thervehttps://review.openstack.org/444775 is where I am right now15:26
therve(And python3 effort on swift seems non-existent, but hey)15:28
therveThat's it15:28
ricolinso like therve said, our py35 gate is block by devstack right now15:29
zaneb"slightly gross but gets the job done"15:29
thervezaneb, You can put that on my tombstone15:31
therveAlso, probably devstack motto15:31
zanebtherve: I was just thinking the exact same thing :D15:31
ricolin`#action ..`15:32
ricolin#topic Open discussion15:32
*** openstack changes topic to "Open discussion (Meeting topic: heat)"15:32
zanebreview my patches!15:32
zanebthat is all.15:33
ricolinwe have some backport that will be great to get in15:33
thervezaneb, I made a stupid comment on https://review.openstack.org/43516415:33
therveShould we ignore it? :)15:33
ricolin#link https://review.openstack.org/#/c/445355/15:33
zanebtherve: my plan was to ignore it :)15:34
therveOK :)15:34
ricolinI have backport therve's patch, which might fix ocata's gate?15:34
therve"fix" as makes things green yeah15:34
zanebtherve: you removed the -1 so I took that to mean you were on board :)15:35
thervezaneb, kindaaaa15:35
therveBut yeah sure15:35
ricolinanyway, would be great if guys can help to approve more backports:)15:36
ricolinthat's all I have15:37
therveYeah, wouldn't that be fantastic?15:37
therveLike, if more people could do it? I wonder why it's not the case...15:37
zanebrofl15:38
ricolinI'm +1 only, so that will be fantastic:)!15:38
zanebI'd be happy if we could just get the gate to work so that the ones that have been approved will merge15:39
ricolinskrayne counting on you!15:39
*** garloff has left #openstack-meeting-515:40
ricolinskraynev15:40
ricolinAny other topic to discuss:)?15:40
therveJust, please try to all focus a bit on gate issues15:41
therveRandomly rechecking stuff isn't a solution to anything15:41
therveWe didn't merge a patch for a week, that's pretty terrible15:41
skraynevm?15:42
*** persia has quit IRC15:42
zanebskraynev: https://review.openstack.org/#/c/445355/15:42
ricolinskraynev we need backport landing master15:42
skraynevow. I like to sleep :015:43
skraynev:)15:43
skraynevApproved15:43
zanebwoohoo, thanks skraynev15:43
ricolinzaneb BTW nice talk in `The future of the App Catalog`15:43
zanebheh, yeah that turned into a fun thread15:43
ricolinyeah, long15:44
ricolinbut fun:)15:44
* zaneb is gonna blame that thread for not having time to look at the gate issues15:44
*** persia has joined #openstack-meeting-515:45
ricolinthat thread just keep going:)15:45
ricolinShall we close meeting and move back to heat?:)15:46
zanebyes, let's15:46
ricolinokey, thanks all!15:46
ricolin#endmeeting15:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:46
openstackMeeting ended Wed Mar 15 15:46:45 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-03-15-15.04.html15:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-03-15-15.04.txt15:46
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-03-15-15.04.log.html15:46
*** therve has left #openstack-meeting-515:47
*** kbaikov has left #openstack-meeting-516:08
*** ricolin has quit IRC16:24
*** robputt_ has quit IRC16:28
*** robputt has joined #openstack-meeting-516:30
*** zhipeng has quit IRC16:54
*** matrohon has quit IRC17:28
*** beisner has joined #openstack-meeting-518:20
*** skraynev has quit IRC18:48
*** rarcea has quit IRC19:35
*** rarcea has joined #openstack-meeting-519:41
*** shasha_t- has quit IRC19:45
*** rarcea has quit IRC19:57
*** matrohon has joined #openstack-meeting-520:00
*** matrohon has quit IRC20:31
*** stream10 has joined #openstack-meeting-520:40
*** stream10 has quit IRC21:06
*** joanna has joined #openstack-meeting-523:58

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