Tuesday, 2019-01-22

*** macza has joined #openstack-meeting-400:00
*** bobh has joined #openstack-meeting-400:06
*** k_mouza has joined #openstack-meeting-400:14
*** k_mouza has quit IRC00:18
*** igordc has joined #openstack-meeting-400:22
*** macza has quit IRC00:24
*** Liang__ has joined #openstack-meeting-400:44
*** salmankhan has quit IRC00:49
*** igordc has quit IRC01:05
*** markvoelker has quit IRC01:08
*** slaweq has joined #openstack-meeting-401:11
*** slaweq has quit IRC01:15
*** roman_g has quit IRC01:18
*** bobh has quit IRC01:40
*** markvoelker has joined #openstack-meeting-402:09
*** hongbin has joined #openstack-meeting-402:24
*** psachin has joined #openstack-meeting-402:42
*** markvoelker has quit IRC02:43
*** bobh has joined #openstack-meeting-402:44
*** hongbin has quit IRC02:58
*** hongbin has joined #openstack-meeting-403:01
*** slaweq has joined #openstack-meeting-403:11
*** slaweq has quit IRC03:15
*** hongbin has quit IRC03:16
*** hongbin has joined #openstack-meeting-403:17
*** hongbin has quit IRC03:17
*** hongbin has joined #openstack-meeting-403:17
*** gkadam has joined #openstack-meeting-403:19
*** hongbin has quit IRC03:20
*** hongbin has joined #openstack-meeting-403:20
*** bobh has quit IRC03:21
*** hongbin has quit IRC03:21
*** hongbin has joined #openstack-meeting-403:21
*** hongbin has quit IRC03:22
*** hongbin has joined #openstack-meeting-403:22
*** markvoelker has joined #openstack-meeting-403:41
*** bobh has joined #openstack-meeting-404:09
*** markvoelker has quit IRC04:13
*** bobh has quit IRC04:14
*** gkadam has quit IRC04:21
*** hongbin has quit IRC05:10
*** markvoelker has joined #openstack-meeting-405:10
*** slaweq has joined #openstack-meeting-405:11
*** slaweq has quit IRC05:15
*** macza has joined #openstack-meeting-405:24
*** macza has quit IRC05:29
*** slaweq has joined #openstack-meeting-405:35
*** markvoelker has quit IRC05:43
*** igordc has joined #openstack-meeting-405:45
*** radeks has joined #openstack-meeting-405:51
*** e0ne has joined #openstack-meeting-405:52
*** e0ne has quit IRC05:53
*** gcheresh has joined #openstack-meeting-406:08
*** spsurya has joined #openstack-meeting-406:21
*** yboaron_ has joined #openstack-meeting-406:25
*** yboaron_ has quit IRC06:33
*** markvoelker has joined #openstack-meeting-406:40
*** Luzi has joined #openstack-meeting-406:49
*** lpetrut has joined #openstack-meeting-407:12
*** markvoelker has quit IRC07:14
*** igordc has quit IRC07:27
*** bobh has joined #openstack-meeting-407:29
*** Liang__ has quit IRC07:34
*** bobh has quit IRC07:35
*** Liang__ has joined #openstack-meeting-407:36
*** pcaruana has joined #openstack-meeting-407:41
*** gkadam has joined #openstack-meeting-407:51
*** macza has joined #openstack-meeting-408:05
*** macza has quit IRC08:09
*** markvoelker has joined #openstack-meeting-408:10
*** roman_g has joined #openstack-meeting-408:21
*** ralonsoh has joined #openstack-meeting-408:30
*** yboaron has joined #openstack-meeting-408:32
*** celebdor has joined #openstack-meeting-408:34
*** yboaron_ has joined #openstack-meeting-408:36
*** yboaron has quit IRC08:39
*** markvoelker has quit IRC08:43
*** yboaron_ has quit IRC09:07
*** yboaron_ has joined #openstack-meeting-409:07
*** iyamahat_ has quit IRC09:40
*** markvoelker has joined #openstack-meeting-409:40
*** Liang__ has quit IRC09:42
*** iyamahat has joined #openstack-meeting-410:01
*** markvoelker has quit IRC10:13
*** e0ne has joined #openstack-meeting-410:24
*** salmankhan has joined #openstack-meeting-410:26
*** salmankhan1 has joined #openstack-meeting-410:37
*** salmankhan has quit IRC10:37
*** salmankhan1 is now known as salmankhan10:37
*** markvoelker has joined #openstack-meeting-411:10
*** k_mouza has joined #openstack-meeting-411:14
*** k_mouza has quit IRC11:39
*** markvoelker has quit IRC11:44
*** radeks_ has joined #openstack-meeting-411:52
*** radeks has quit IRC11:55
*** dave-mccowan has joined #openstack-meeting-411:56
*** k_mouza has joined #openstack-meeting-412:00
*** bobh has joined #openstack-meeting-412:03
*** k_mouza has quit IRC12:04
*** bobh has quit IRC12:08
*** k_mouza has joined #openstack-meeting-412:21
*** macza has joined #openstack-meeting-412:21
*** k_mouza has quit IRC12:25
*** e0ne has quit IRC12:25
*** macza has quit IRC12:26
*** e0ne has joined #openstack-meeting-412:30
*** GregWaines has joined #openstack-meeting-412:36
*** k_mouza has joined #openstack-meeting-412:38
*** k_mouza_ has joined #openstack-meeting-412:39
*** markvoelker has joined #openstack-meeting-412:41
*** k_mouza has quit IRC12:42
*** radeks_ has quit IRC13:06
*** radeks_ has joined #openstack-meeting-413:06
*** seajay has joined #openstack-meeting-413:08
*** markvoelker has quit IRC13:09
*** psachin has quit IRC13:16
*** lpetrut has quit IRC13:20
*** lpetrut has joined #openstack-meeting-413:28
*** oanson has quit IRC13:31
*** mjturek has joined #openstack-meeting-413:42
*** e0ne has quit IRC14:05
*** e0ne has joined #openstack-meeting-414:08
*** njohnston has joined #openstack-meeting-414:15
*** TxGirlGeek has joined #openstack-meeting-414:18
*** howell has joined #openstack-meeting-414:19
*** TxGirlGeek has quit IRC14:39
*** sgrasley has joined #openstack-meeting-414:42
*** dwalt has joined #openstack-meeting-414:57
*** nick_kar has joined #openstack-meeting-415:00
*** georgk has joined #openstack-meeting-415:00
portdirect#startmeeting openstack-helm15:02
openstackMeeting started Tue Jan 22 15:02:41 2019 UTC and is due to finish in 60 minutes.  The chair is portdirect. 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: openstack-helm)"15:02
openstackThe meeting name has been set to 'openstack_helm'15:02
portdirectlets give it a few mins for people to join15:02
mattmceueno/ GM15:02
howello/15:03
portdirectAgenda here: https://etherpad.openstack.org/p/openstack-helm-meeting-2019-01-22, add away :D15:03
*** dimitris_ has joined #openstack-meeting-415:03
georgko/15:04
dimitris_o/15:04
dwalto/15:04
nick_karo/15:05
portdirectok - lets kick off15:05
portdirect#topic docs-repo15:06
*** openstack changes topic to "docs-repo (Meeting topic: openstack-helm)"15:06
portdirectso theres been some great work tring to the the docs repo up and running - though im wondering if we are trying to run, before we walk15:06
portdirectI have given this a -2 https://review.openstack.org/#/c/625853/515:06
portdirectthough am prepared to be told thats not appropriate15:07
portdirecti thought we would do this in a phased approach 1) bring over exisiting docs un altered, 2) restructure15:07
*** yboaron_ has quit IRC15:07
portdirectthough this attempts to do both in one pass15:07
portdirectwhich makes it very hard (at least for me) to see whats changed etc15:08
portdirectso more process than intent ;)15:08
*** yboaron_ has joined #openstack-meeting-415:08
portdirectnot sure if any of the people working on that are here, so i may just be shouting incoherently atm :D15:08
mattmceuen+1 for splitting to two steps - that makes sense to me too15:09
*** hongbin has joined #openstack-meeting-415:09
portdirectok - lets move on unless anyone else has anything to add - seems bad to discuss to much without Jaesang Lee around - whos put a lot of effort into this15:10
*** Luzi has quit IRC15:10
portdirect#topic Helm 315:10
*** openstack changes topic to "Helm 3 (Meeting topic: openstack-helm)"15:10
portdirectso howell has been doing some poc work with helm 315:10
portdirectand doing cool things like deploying memcached with it15:11
evrardjpportdirect: mmm15:11
portdirecthowell: you able to give a update on where helm3 is? eg lua etc15:11
howellSure15:11
howelllast i checked, it's stil quite a ways down the road15:12
evrardjpon previous topic I believe it's easier to do the things right in the proper place first, then increase the amount of content to match the proper structure15:12
evrardjpbut ok15:12
howellthe lua library API is still being developed, so lua hooks aren't working at all yet15:12
howellhttps://github.com/helm/helm/issues/508415:12
*** liuyulong has joined #openstack-meeting-415:13
jayahno/15:13
howellfurther, there isn't much of a timeline on when things will start to be useable :/15:13
mattmceuenthat's interesting howell - does that mean helm 3 is not usable at all now, or just usable in more simple use cases?15:14
mattmceueno/ jayahn!15:14
howellit's usable. it is pretty limited though15:14
portdirecthowell: at this point is the same (or greater) sprig version supperted as helm2?15:15
portdirect*supported15:15
howelli beleive so, but i'd have to double check15:16
portdirecti think that would be awesome - then once a alpha binary starts being published we could explore again15:16
mattmceuenevrardjp: given the state of helm 3, sounds like doing this POC-style is the right way/ right place to do this, if it's not ready to introduce into OSH.  Do you disagree?15:16
portdirectthough I think you are planning on getting much more involved upstream there? ;)15:16
howellplanning on it :)15:17
evrardjpmattmcemaI was talking about previous topic, I can't judge on that helm3 part. Did you really want to ping me there? :)15:18
evrardjpmattmceuen: *15:18
portdirecti think we can circle back to that (docs) at the end of the meeting if jayahn is around?15:18
evrardjpportdirect: lgtm15:18
jayahni will be around15:19
portdirectnice - all done on helm3 - aka the future of OSH15:19
evrardjpmattmceuen: helm-tng interests me though :)15:19
mattmceuenAh - I gotcha now evrardjp.  Mis-parsed ya :)15:19
portdirectso onwards to the next topic - this meeting should perhaps be renamed the howell show this week15:20
evrardjp:)15:20
howellhaha :)15:20
portdirect#topic kubernetes-entrypoint - whats going on there?15:20
*** openstack changes topic to "kubernetes-entrypoint - whats going on there? (Meeting topic: openstack-helm)"15:20
howellso I've been making some updates to kubernetes-entrypoint15:20
portdirecthowell: i think you have been doing some k8s-entrypoint work recently?15:20
howellFirstly, the tool now supports Custom Resource Dependencies.  Custom Resource Depedendencies use arbitrary key and "desired" value pairs.15:20
howellSecondly, I've added an option to print all unresolved dependendencies as machine-readable JSON.15:21
portdirectok - so lets peel that back a bit15:21
portdirectCRD support, what and why?15:22
evrardjphowell: "the tool" is not easy to understand for people without context, but that's maybe because I am new to this project15:22
howellright. getting ahead of myself15:22
srwilkerso/15:22
srwilkerssorry im late15:22
portdirecthowell: i think evrardjp has a good point15:22
portdirectwe have been in osh so long - we forget the very basic concepts15:22
portdirectlets start with what is k8s-entrypoint15:22
portdirectand how do we use it today in osh15:22
howellso kubernetes-entrypoint is used to wait on dependencies15:23
*** bobh has joined #openstack-meeting-415:23
*** meg has joined #openstack-meeting-415:23
howellthat is, if a pod A is dependendent on pod B, kubernetes-entrypoint will prevent A from starting until B is finished15:23
portdirectwe use this concept to orchestrate everything in osh15:24
portdirectdriven by the dependences section and a helm toolkit function15:24
portdirectlets take a simple service - eg keystone15:24
portdirecthttps://github.com/openstack/openstack-helm/blob/master/keystone/values.yaml#L104-L11415:24
evrardjpyup I've seen it around, but I think the important part is that it's our own thing, and that we have to maintain things forward. If deployers need to be aware of changes,we need to notify those in meetings, which is what's happening here15:24
evrardjpcorrect?15:25
portdirectevrardjp: its not our own thing15:25
portdirectits intels15:25
evrardjpok15:25
srwilkersit's been around awhile, we just take advantage of it and provide updates along the way15:25
evrardjpthanks for the clarification!15:25
portdirectwe, stackentes, and kolla-k8s all uses it as the foundation for openstack on k8s15:25
howellup until recently, the tool has supported pods, services, daemonsets, and a handful of other kubernetes builtins15:25
portdirectanyway back to the 10115:25
portdirectin the link i put above, you see the deps for the keystone api service15:26
*** bobh has quit IRC15:26
portdirectit needs: a migrated db, and a lod of other things done - which we do via k8s jobs15:26
*** gcheresh has quit IRC15:26
portdirectand also some services to be up and ready - which are, suprise sprise, services in a k8s15:27
portdirectworld15:27
portdirectthe container runs as in init container in each osh pod15:27
portdirectand waits for the jobs to be complete, and services to be up before exiting15:27
portdirectthus orchestrating across the cluster15:27
portdirectback to you howell15:28
evrardjpthanks for that :)15:28
howellanyway, i've recently added support for CRDs15:28
howellthat is, "wait until some arbitrary key has some arbitrary value"15:29
howell*of a crd15:29
portdirectfor those that may not know - what produces/works with crds in k8s?15:29
* portdirect buzzword incomming15:30
howelloperators15:30
howellso it will work with operators such as rook15:30
evrardjp:)15:30
portdirectand anything else ;D15:30
* mattmceuen imagines movie preview voice saying "operators"15:30
georgkone quick question in this regard:15:30
evrardjphowell: good job there15:31
georgkdoes this not overlap with Armada in some functionaly?15:31
georgkalso: noob question15:31
jayahnhowell: that would be helpful!15:31
howellit'll also work nicely with creatign DAGs with argo15:31
howellthanks :)15:31
portdirectand howell is planning to prototype that for openstack service management :D15:31
evrardjphowell: I will ask a lesson on argo in the #openstack-helm channel, I took enough time already.15:32
portdirectso it will be pretty exciting to see that progess, and if it has legs15:32
evrardjpsorry to ask one more question there howell: What is the idea behind bringing that? I mean it's obviously a very positive change, but there is probably something you have on your mind that I cannot see on the roadmap15:33
howellit's not on the roadmap, because we aren't sure if it's a good idea or not yet15:34
evrardjpok, for the moment it's just opening possible doors15:34
portdirectexactly15:34
howellyes15:34
evrardjpshould that change, I think it's worth mentioning in a meeting15:35
portdirectoh - 100% it would be a big change15:35
portdirectbut also - untill we try it - have no idea if it will be any good15:35
portdirectso very early days - and i think best to do these things fully in the open15:35
evrardjpagreed15:36
portdirectso we can collectivly evaluate approaches15:36
portdirectk8s is still young, and evolving fast15:36
jayahnwe are talking about trying argo? (just want to followup)15:36
portdirecttalkign about a very simple poc15:37
portdirecti think 'pre-trying' at this stage15:37
jayahnokay, :)15:37
portdirectone thing that has come out of this though that we clearly need to do a better job on15:37
portdirect#action anyone document k8s-entrypoint15:37
howelli can work on documentation if needed15:38
portdirecthowell: i think you would be a great person to do that15:38
portdirectalon with evrardjp, as he gets openstack requirements like very few people i know15:39
portdirect*along15:39
evrardjpI am fine with helping on that side with you howell15:39
portdirectgeorgk: not forgotten your question15:39
georgkportdirect: that´s fine, we can take it later15:40
portdirectnone of this really overlaps with armada15:40
portdirectas they have two different objectives, k8s entrypoint deals with deps etc within a chart, while armada orchestrates charts themselves15:40
portdirectits this loose coupling, that allows osh (and those that came before it) to both be very resilient and self contained at a service level15:41
georgkportdirect: ok, got it. Thanks15:42
portdirectwhile armada allows the deployment and configuration of these serices to be tied together in a chohertent fasion15:42
evrardjpvery good patterns15:42
portdirect(and once you are there, the rabbit hole opens - deckhand alows the config to be managed etc...)15:42
jayahnyeah.15:43
portdirecthowell: one last thing - you also added machine readable output to k8s entrypoint15:43
howellyes. k8s-entrypoint currently has some human-readable logging output on stdout15:43
portdirectthe hope here is that tooling - eg lma will be able to tap into this and give faster/simpler insight into the state of the cluster15:44
evrardjpthat's interesting15:44
portdirectso operators can at a glance see why a service, such as say glance, is not working15:45
srwilkersi see what you did there15:45
* portdirect is here all week15:45
howellbooo15:46
*** lpetrut has quit IRC15:46
portdirectok to move on?15:46
georgk:q15:47
*** yboaron_ has quit IRC15:47
portdirect#topic Reminder: Open Infra Summit talk  submissions due 11:59 PT tomorrow!15:47
*** openstack changes topic to "Reminder: Open Infra Summit talk submissions due 11:59 PT tomorrow! (Meeting topic: openstack-helm)"15:47
mattmceuen^^15:47
portdirectthanks mattmceuen for reminding us15:47
jayahnyeah, thank for the reminder.15:47
evrardjpthere should be forum sessions to organise after the call for summit presentations, right?15:48
evrardjpthen ofc the ptg sessions15:48
jayahnusually, i remember15:48
srwilkersyeah15:48
jayahn6 days..15:48
portdirectevrardjp: yup15:48
portdirectreally happy to see the events back to back15:49
srwilkersme too15:49
portdirectalmost like the forum15:49
portdirectthough i better not say that out loud15:49
srwilkershush hush15:49
portdirecti'm planning on submitting a workshop with alanmeadows15:50
*** yboaron_ has joined #openstack-meeting-415:50
jayahnfirst week of May.. really worst timing ever for Korean...15:50
portdirectwhere we use some airship components along with osh to bring up and a small cloud15:50
portdirectjayahn: how come?15:50
evrardjpI guess holidays?15:51
jayahnfirst week of May involves labor day (holiday) and children's day (also holiday)15:51
evrardjpwe have labor day too here. We can complain together there jayahn15:51
jayahnusually k-12 gives short vacation for the children15:51
portdirectjayahn: bring them15:51
evrardjpI will give you a beverage of your choice to forget it15:51
*** TxGirlGeek has joined #openstack-meeting-415:52
jayahnlol15:52
portdirectanyway - should we revisit docs for a bit?15:52
srwilkersi'm looking forward to the timing -- i thought about passing on flying out there and riding a motorcycle out there instead15:52
srwilkersand taking a few days to ride around the rockies15:52
jayahndocs15:52
portdirect#topic docs round 215:52
*** openstack changes topic to "docs round 2 (Meeting topic: openstack-helm)"15:52
jayahni thought restructuring was an important priority on doc-repo.15:53
*** dklyle has joined #openstack-meeting-415:53
portdirectso - the original plan i thought was to work on struture, then bring content over from the existing repo,a nd the great stuff skt has done15:53
jayahnand, somewhat agree on evrardjp15:53
portdirectit looks like thigs have jumped right in15:53
portdirectso this morning i proposed that if the desire is to get a large body of content in - this should be done as it15:54
portdirect*as is15:54
portdirectand then resutureing in a follow on ps15:54
portdirectan alternative approach would be to have a ps laying out the struture, and then populating with content once we have that down15:54
portdirectim just worried that as it stands today - theres too many parts moving at once to sanly review15:55
portdirect*sanely15:55
*** TxGirlGe_ has joined #openstack-meeting-415:55
jayahnokay, that probably true. (theres too many parts moving at once to sanly review)15:55
portdirectso - are you ok with getting a ps up to simply define the desired layout15:56
evrardjpso what I did when I refactored large chunks of content in the docs of a project, I pretty much did the structure with no document in it, then quickly add, topic by topic, in the right place15:56
portdirectand once we have that - start filling it with content?15:56
portdirectevrardjp: i think that approach makes most sense15:56
jayahnokay, i do agree on that15:56
jayahnhaving ps up to define the desired layout first15:57
*** TxGirlGeek has quit IRC15:57
evrardjpon top of that all your downstream content would be easily importable patch per patch...15:57
evrardjpjayahn: you want me to push that structure up?15:57
jayahnevrardjp: yeap, that would be great :)15:58
*** lemko has joined #openstack-meeting-415:58
evrardjpI'd rather let you do it:p15:58
evrardjpoh ok15:58
evrardjpI guess I am volunteer then15:58
jayahnah.. we can do it as well,15:58
jayahnbut i guess anyone available to do it can do it.15:59
evrardjplet's sync on the chan then15:59
portdirecthey - about to run out of time15:59
portdirectsee you all in the channel16:00
portdirect#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Tue Jan 22 16:00:08 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-01-22-15.02.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-01-22-15.02.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-01-22-15.02.log.html16:00
*** nick_kar has left #openstack-meeting-416:00
*** meg has quit IRC16:00
*** TxGirlGe_ has quit IRC16:01
evrardjpthanks everyone16:04
*** TxGirlGeek has joined #openstack-meeting-416:09
*** dims has quit IRC16:15
*** dimitris_ has quit IRC16:18
*** dims has joined #openstack-meeting-416:20
*** yboaron_ has quit IRC16:28
*** GregWaines has quit IRC16:28
*** e0ne has quit IRC16:38
*** e0ne has joined #openstack-meeting-416:39
*** roman_g has quit IRC16:58
*** pcaruana has quit IRC17:02
*** macza has joined #openstack-meeting-417:02
*** e0ne has quit IRC17:02
*** macza_ has joined #openstack-meeting-417:06
*** macza has quit IRC17:07
*** radeks__ has joined #openstack-meeting-417:08
*** radeks_ has quit IRC17:10
*** k_mouza_ has quit IRC17:11
*** k_mouza has joined #openstack-meeting-417:11
*** k_mouza has quit IRC17:16
*** dwalt has left #openstack-meeting-417:19
*** igordc has joined #openstack-meeting-417:28
*** radeks__ has quit IRC17:33
*** igordc has quit IRC17:39
*** georgk has quit IRC17:46
*** radeks has joined #openstack-meeting-417:47
*** radeks has quit IRC17:50
*** pcaruana has joined #openstack-meeting-418:01
*** lemko has quit IRC18:04
*** yamahata has quit IRC18:22
*** iyamahat has quit IRC18:22
*** pcaruana has quit IRC18:23
*** k_mouza has joined #openstack-meeting-418:25
*** gkadam has quit IRC18:26
*** georgk has joined #openstack-meeting-418:30
*** k_mouza has quit IRC18:31
*** georgk has quit IRC18:35
*** iyamahat has joined #openstack-meeting-418:36
*** TxGirlGeek has quit IRC18:48
*** yamahata has joined #openstack-meeting-418:55
*** TxGirlGeek has joined #openstack-meeting-418:59
*** salmankhan has quit IRC19:03
*** iyamahat has quit IRC19:06
*** iyamahat has joined #openstack-meeting-419:06
*** e0ne has joined #openstack-meeting-419:07
*** TxGirlGeek has quit IRC19:11
*** k_mouza has joined #openstack-meeting-419:12
*** TxGirlGeek has joined #openstack-meeting-419:14
*** k_mouza has quit IRC19:17
*** e0ne has quit IRC19:42
*** iyamahat_ has joined #openstack-meeting-419:43
*** TxGirlGeek has quit IRC19:46
*** iyamahat has quit IRC19:46
*** iyamahat__ has joined #openstack-meeting-419:48
*** pcaruana has joined #openstack-meeting-419:50
*** iyamahat_ has quit IRC19:51
*** ralonsoh has quit IRC19:53
*** diablo_rojo has joined #openstack-meeting-419:56
*** TxGirlGeek has joined #openstack-meeting-419:58
*** diablo_rojo has quit IRC20:05
*** pcaruana has quit IRC20:11
*** yboaron_ has joined #openstack-meeting-420:19
*** mjturek has quit IRC20:24
*** pcaruana has joined #openstack-meeting-420:24
*** dims has quit IRC20:40
*** dims has joined #openstack-meeting-420:42
*** dave-mccowan has quit IRC20:48
*** dims has quit IRC20:50
*** isq has joined #openstack-meeting-420:52
*** dims has joined #openstack-meeting-420:52
*** celebdor has quit IRC20:53
*** pcaruana has quit IRC21:19
*** dklyle has quit IRC21:39
*** yboaron_ has quit IRC22:05
*** slaweq has quit IRC22:12
*** TxGirlGeek has quit IRC22:24
*** TxGirlGe_ has joined #openstack-meeting-422:24
*** slaweq has joined #openstack-meeting-422:29
*** seajay has quit IRC22:29
*** seajay has joined #openstack-meeting-422:31
*** TxGirlGe_ has quit IRC22:31
*** slaweq has quit IRC22:33
*** TxGirlGeek has joined #openstack-meeting-422:40
*** howell has quit IRC22:41
*** TxGirlGeek has quit IRC22:59
*** slaweq has joined #openstack-meeting-423:00
*** TxGirlGeek has joined #openstack-meeting-423:03
*** slaweq has quit IRC23:05
*** seajay has quit IRC23:19
*** TxGirlGeek has quit IRC23:35
*** lamt has joined #openstack-meeting-423:55

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