Tuesday, 2019-01-15

*** yamamoto has quit IRC00:03
*** yamamoto has joined #openstack-meeting-400:05
*** seajay has quit IRC00:05
*** markvoelker has quit IRC00:06
*** yamamoto has quit IRC00:07
*** yamamoto has joined #openstack-meeting-400:11
*** yamamoto has quit IRC00:13
*** yamamoto has joined #openstack-meeting-400:14
*** yamamoto has quit IRC00:16
*** macza has quit IRC00:18
*** yamamoto has joined #openstack-meeting-400:27
*** yamamoto has quit IRC00:31
*** yamamoto has joined #openstack-meeting-401:15
*** yamamoto has quit IRC01:21
*** Liang__ has joined #openstack-meeting-401:28
*** markvoelker has joined #openstack-meeting-401:35
*** markvoelker has quit IRC01:40
*** hongbin has joined #openstack-meeting-401:57
*** markvoelker has joined #openstack-meeting-401:59
*** hongbin has quit IRC01:59
*** hongbin has joined #openstack-meeting-402:04
*** macza has joined #openstack-meeting-402:06
*** markvoelker has quit IRC02:07
*** macza has quit IRC02:11
*** TxGirlGeek has quit IRC02:23
*** yamamoto has joined #openstack-meeting-402:32
*** Liang__ has quit IRC02:36
*** yamamoto has quit IRC02:37
*** Liang__ has joined #openstack-meeting-402:39
*** iyamahat_ has quit IRC02:44
*** yamahata has quit IRC02:45
*** TxGirlGeek has joined #openstack-meeting-403:18
*** premsankar has quit IRC03:28
*** yamamoto has joined #openstack-meeting-403:30
*** diablo_rojo has quit IRC03:45
*** TxGirlGeek has quit IRC03:51
*** dave-mccowan has quit IRC04:11
*** hongbin has quit IRC04:25
*** radeks has joined #openstack-meeting-404:33
*** yamamoto has quit IRC04:34
*** markvoelker has joined #openstack-meeting-405:05
*** iyamahat has joined #openstack-meeting-405:29
*** yamamoto has joined #openstack-meeting-405:42
*** markvoelker has quit IRC05:47
*** markvoelker has joined #openstack-meeting-405:48
*** yamamoto has quit IRC05:49
*** markvoelker has quit IRC05:59
*** yboaron has joined #openstack-meeting-406:21
*** gcheresh_ has joined #openstack-meeting-406:25
*** yamahata has joined #openstack-meeting-406:36
*** diablo_rojo has joined #openstack-meeting-406:46
*** yamamoto has joined #openstack-meeting-407:08
*** yamamoto has quit IRC07:13
*** iyamahat has quit IRC07:20
*** e0ne has joined #openstack-meeting-407:30
*** e0ne has quit IRC08:04
*** radeks has quit IRC08:08
*** ralonsoh has joined #openstack-meeting-408:36
*** yamamoto has joined #openstack-meeting-408:39
*** iyamahat has joined #openstack-meeting-408:42
*** yamamoto has quit IRC08:44
*** Liang__ has quit IRC09:09
*** Liang__ has joined #openstack-meeting-409:13
*** diablo_rojo has quit IRC09:26
*** pcaruana has joined #openstack-meeting-409:30
*** Liang__ has quit IRC09:37
*** e0ne has joined #openstack-meeting-409:38
*** yboaron has quit IRC09:55
*** yboaron_ has joined #openstack-meeting-409:55
*** yamamoto has joined #openstack-meeting-410:09
*** yamamoto has quit IRC10:12
*** yamamoto has joined #openstack-meeting-410:12
*** k_mouza has joined #openstack-meeting-410:23
*** salmankhan has joined #openstack-meeting-410:33
*** salmankhan has quit IRC10:42
*** salmankhan has joined #openstack-meeting-410:42
*** salmankhan has quit IRC10:46
*** macza has joined #openstack-meeting-410:50
*** salmankhan has joined #openstack-meeting-410:53
*** macza has quit IRC10:54
*** k_mouza has quit IRC11:30
*** k_mouza has joined #openstack-meeting-411:38
*** k_mouza has quit IRC11:43
*** radeks has joined #openstack-meeting-412:31
*** Luzi has joined #openstack-meeting-412:41
*** radeks has quit IRC13:00
*** radeks has joined #openstack-meeting-413:01
*** seajay has joined #openstack-meeting-413:06
*** mhen has joined #openstack-meeting-413:14
*** k_mouza has joined #openstack-meeting-413:15
*** dave-mccowan has joined #openstack-meeting-413:28
*** radeks has quit IRC13:29
*** mhen has left #openstack-meeting-413:49
*** Liang__ has joined #openstack-meeting-414:07
*** psachin has joined #openstack-meeting-414:16
*** portdirect has joined #openstack-meeting-414:42
*** jayahn has joined #openstack-meeting-414:43
*** dwalt has joined #openstack-meeting-414:51
*** powerds0111 has joined #openstack-meeting-414:55
*** megheisler has joined #openstack-meeting-414:58
*** howell has joined #openstack-meeting-414:58
*** k_mouza has quit IRC14:59
*** nick_kar has joined #openstack-meeting-415:00
jayahnis it right channel?15:00
*** mattmceuen has joined #openstack-meeting-415:02
*** yongiman has joined #openstack-meeting-415:02
portdirectyes - sorry running 2 mins late today15:02
*** evgenyl has joined #openstack-meeting-415:02
jayahno/15:02
portdirect#startmeeting openstack-helm15:02
openstackMeeting started Tue Jan 15 15:02:45 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
powerds0111o/15:02
portdirect#link Agenda https://etherpad.openstack.org/p/openstack-helm-meeting-2019-01-1515:03
*** srwilkers has joined #openstack-meeting-415:03
portdirectlets give it a few lins for people to arrive who happen to be even later than i :)15:03
srwilkersgot the room wrong15:03
*** georgk has joined #openstack-meeting-415:03
mattmceueno/15:03
georgko/15:03
mattmceuenthis channel feels so much more... 4-like than it used to.  totally different vibe here.15:04
jayahnfantastic-4....15:04
portdirectcan i be thing?15:04
portdirectanyway - lets begin15:04
portdirect#topic Support cinder multi rbd backends15:05
*** openstack changes topic to "Support cinder multi rbd backends (Meeting topic: openstack-helm)"15:05
portdirectjayahn: think this is yours?15:05
jayahnpowerds011115:05
jayahndan will talk about it15:05
powerds0111cinder & libvirt charts cannot support multiple rbd backends but some sites need the feature. so i described what issues in charts and made tasks on the story https://storyboard.openstack.org/#!/story/200477715:05
powerds0111first task is implemented on https://review.openstack.org/#/c/630810/ and others are  on going15:06
portdirectthe timing of this is somewhat great - now we have support for multiple ceph clusters (and gating for them) with the ceph chart.15:06
yongimano/15:07
powerds0111you mean it is implemented already?15:07
portdirectpowerds0111: could you explain the rationalle with `ceph configuration generation chart for supporting multiple cluster` that you link to above?15:07
*** alanmeadows has joined #openstack-meeting-415:08
portdirectpowerds0111: not the consumption of them by libvirt - but that the ceph chart now supports multiple deployments within a single cluster - so we can simply test the work you are undertaking15:08
powerds0111multi rbd backends need multiple ceph.conf so the PS make cepf.conf files in ceph-etc configmap15:09
portdirectperhaps - rather than a ceph specific chart for this use case, a generic: configmap chart would make sense?15:10
portdirectalternativly you could just turn all manifests other than the configmap off for any other ceph chart15:11
portdirecti'm not fully aligned with supamatts line of thinking15:11
portdirectbut am on the other side concerned that if we end up with many 'pico' charts then we will quickly end up in a mess15:11
portdirectthe work you did for the 'bring your own service' chart was great here15:12
portdirectas its equally applicable for ceph, as it is for mariadb15:12
powerds0111could you explain more about the idea to support multiple ceph.conf?15:15
portdirecti dont have any ideas there yet :)15:15
portdirectthe point im making though is that having a chart dedicated to rendering a ceph.conf is a very heavyweight solution for a single task15:16
jayahnportdirect: you are suggesting to think a bit more about if there is any possible case to make it more generic feature?15:16
jayahnhowever, dose not have any concrete suggestion yet. ;) am i understanding correctly?15:17
portdirectwhen the same end result could be achived by turning all of the lines here to 'false' https://github.com/openstack/openstack-helm-infra/blob/master/ceph-client/values.yaml#L438-L450 with the expetion of 44115:17
portdirectjayahn: pretty much - i think if we go down the 'chart to produce configmap' approach, then it would be nice to see it able to produce *any* configmap that htk supports15:17
*** yboaron_ has quit IRC15:18
portdirectrather than one for each15:18
mattmceuenah, agree - because the only thing ceph-specific about the chart is the values themselves, which could be overridden for all kinds of handy non-ceph things15:18
portdirectyes - as it stand the chart is a 'helm-toolkit.utils.to_ini' chart with prepopulated values for ceph15:20
powerds0111:) i agree i need to check 1) how to fix ceph-client to support multiple cepf configs 2) make new chart to generate general configmap15:20
portdirectawesome - thanks powerds0111, really looking forward to seeing this shape up15:21
mattmceuen++ good stuff powerds011115:21
portdirectalso - lets sync sooner rather than later on getting gating for this in place15:22
portdirectas it should be a simple addition to the tenant ceph job that was added recently15:22
*** roman_g has joined #openstack-meeting-415:22
portdirectok to move on?15:22
powerds0111okay15:22
portdirect#topic: referencing work outside of openstack-helm repo15:23
*** openstack changes topic to ": referencing work outside of openstack-helm repo (Meeting topic: openstack-helm)"15:23
portdirectjayahn: this one is yours i think?15:23
jayahnit was a simple question, all of your today's comment on https://review.openstack.org/#/c/630810/  are great!15:23
*** Liang__ has quit IRC15:23
jayahnbut on the comment with "-1", i see someone actually put things happening outside of openstack-helm repo (attdev), then gave -1.15:24
portdirecti think i can take this one and draw some lines in the sand (hopefully)15:24
jayahnokay. thanks,. :)15:24
portdirectI strongly disagree with the -1, not least of which is that the work referenced there is not happening in openstack hosted infra (which is the important point here)15:25
portdirectI do fortuantly have some insight into the project that supamatt is refering to15:26
portdirectATT has been operationalizing airship based osh clusters - which is great for us as a community as it really exposes the gaps we have15:27
portdirectatt-comdevs porthole is a great example of this15:27
*** hongbin has joined #openstack-meeting-415:28
portdirectI think its got tot the stage where it would be a great thing for the community at large to benefit from15:28
jayahnokay, porthole. i need to learn this word first.15:28
portdirectits the round windoes on the side of a boat15:28
portdirect*windows15:28
portdirectthe idea being they let an operations team look inside a cluster without having to be in the cluster itself15:29
mattmceuenhooray for clever names15:29
portdirect(att does spend a long time coming up with names for things it seems)15:29
*** k_mouza has joined #openstack-meeting-415:30
portdirectthis week I'm going to work with mattmceuen and alanmeadows to try and free porthole from its current home15:30
portdirectso it can set sail out into the world15:30
*** TxGirlGeek has joined #openstack-meeting-415:30
jayahnah, okay, now i am getting what you are talking about.15:30
* portdirect i'll run out of these soon...15:30
jayahntook sometime to understand... :)15:30
portdirectmost likley i think it would have a good home in airship - whihc would let us leverage it a lot easier within osh if there is desire to do so15:31
portdirectbut . thats something we would need to propose to the airship community15:31
jayahnI am just opposing a practice to give -1 with outside of osh work. that is all. but absolutely support brining porthole into the world.15:31
portdirectjayahn: i could not agree with your more on the -1 in this instance15:32
portdirectsometimes though - it may make sense - eg there is no point re-inventing a wheel that already exists ;)15:32
jayahnfor the porthole thing, if you need any supporting words, I will do it.15:33
portdirectbut in this instance - thankfully it helps rip a scab off that was frustrating a lot of people.15:33
jayahnyeap. that is true. it was just -1.. not message contents itself.15:33
portdirectjayahn: that would be really appreciated - I'll add it to the meeting for airship next week.15:33
jayahnsure, I will be in airship meeting next week then15:33
*** k_mouza has quit IRC15:34
portdirect#topic New charts: pod security policy15:34
*** openstack changes topic to "New charts: pod security policy (Meeting topic: openstack-helm)"15:34
portdirectmattmceuen added a chart for pod security policy recently - and it was one of the topics in this weeks airship meeting15:35
portdirectmattmceuen: you oke go give a breif over-view of your work here for those that were not there?15:35
mattmceuenSure!15:36
mattmceuenin a nutshell - the podsecuritypolicy chart adds k8s RBAC-based policy that restricts what particular roles are allowed to do with pod specifications15:36
mattmceuene.g. restricting whether pods are allowed to have elevated permissions, host-level access, etc15:37
jayahnthat would be really great one to have15:37
mattmceuenI will be lazy and cut and paste :)15:37
mattmceuenSo you may or may not be familiar with k8s PodSecurityPolicies15:37
mattmceuen8:04 AM If you configure your k8s to use them, then the k8s api server will only allow you an actor to schedule pods that meet certain criteria/policy15:37
mattmceuen8:04 AM Based on k8s RBAC15:37
mattmceuen8:05 AM This is a security feature we wanted to add into airship, but in a way that doesn't break all the privileged actions that are taken across airship and openstack-helm15:37
mattmceuen8:05 AM This helm chart was added to openstack-helm-infra: https://github.com/openstack/openstack-helm-infra/tree/master/podsecuritypolicy15:37
mattmceuen8:06 AM It specifies by default an incredibly (100%) permissive podsecuritypolity, and sets it up as a default for the cluster15:37
mattmceuen8:06 AM It was also added into the Treasuremap reference yamls: https://review.openstack.org/#/c/629686/15:37
mattmceuen8:07 AM You can do a couple things through the chart:15:37
mattmceuenYou can use the chart to:15:38
mattmceuen8:08 AM 1) add whatever additional podsecuritypolicies you want for your cluster, programmatically, letting helm manage lifecycle15:38
mattmceuen8:08 AM 2) change the default(s)15:38
mattmceuen8:09 AM Over time, we want to tune the defaults in the chart to be a reasonable non-fully-open set of policy, as much as possible.  However, the intent is also that operators fully customize it for their workloads,15:38
mattmceuenYou can set up defaults in the chart individually for serviceacounts, authenticated users, and unauthenticated users via the chart, and/or associate the PSPs to other roles outside of the chart itself15:38
mattmceuenGive folks a minute to read that - let me know if any questions!15:38
srwilkersi think this could add value down the road once things are fleshed out.  my only request would be to have this run in some sort of job just to validate that `helm install foo ./podsecuritypolicy` results in a successful installation15:40
portdirectpersonally i love it, though i am biased15:40
srwilkersthen the post run jobs can help sanity check this as we move to provide a reference policy that makes sense15:40
portdirectsrwilkers: good point15:40
portdirectmattmceuen: what does the default psp permit/deny?15:40
mattmceuensrwilkers - will do!15:41
mattmceuenportdirect:  the default psp in the values allows everything!  basically the most permissive settings for each factor.  By default the psp is bound to all serviceaccounts and all authenticated users (but nothing is bound by default to unauthenticated users)15:41
mattmceuenalthough we can and should definitely tune those defaults down over time15:42
portdirectmattmceuen: nice, in that case a simple gate test could be as easy as deploying a simple pod in host nework, deploying the chart with this flipped https://github.com/openstack/openstack-helm-infra/blob/master/podsecuritypolicy/values.yaml#L38, and trying to deploy another15:43
portdirectif the 2nd fails on psp - then take it as a win?15:43
mattmceuenI like it15:43
mattmceuenwill do15:43
*** mjturek has joined #openstack-meeting-415:44
portdirectwoot - would also be great over time to add docs around this15:44
portdirectas it highlights some areas were we could maybe improve our posture15:44
*** Luzi has quit IRC15:44
mattmceuenagree, will add to the todo list :)15:44
portdirectcan you apply psps to only select workloads in a namespace, or is it a blanket?15:44
*** salmankhan has quit IRC15:45
portdirectif the latter - should longer term we start to consider splitting the control plane away from the data plane?15:46
portdirectas apis'/engines' we could really lock down, though agents (eg nova compute) will require much more permissive rules15:46
mattmceuenit's all done through roles / rolebindings15:47
mattmceuenso we can RBAC it however we want15:47
mattmceuenthe PSPs themselves are defined at the cluster level only15:48
mattmceuenoh I think I misunderstood you15:48
portdirectoh i'll need to read up more then - as we dynamicly generate service accounts/roles/bindings for each pod we may need some accounting mechanism15:48
mattmceuenyes, let me chew on this as well15:49
portdirectnice - thanks for the intro mattmceuen15:49
portdirectwe also have another addition to the fold this week:15:50
portdirect#topic New charts/images: mini-mirror15:50
*** openstack changes topic to "New charts/images: mini-mirror (Meeting topic: openstack-helm)"15:50
portdirectdwalt: can you give a similar breif into for this work?15:51
dwalto/15:51
dwaltGladly!15:51
dwaltOne of the challenges Airship was facing in larger scale deployments was the coordination of packages on the host -- i.e. package versions changed between the time that we ran test deployment pipelines t to the time of the actual deployment.15:51
dwaltMini-mirror exists as a way to combat that. By mirroring Debian/Ubuntu package repositories and deploying them into the cluster, we can control what packages exist on the host for a deployment.15:52
dwaltCurrently, you can utilize your own mini-mirror by building an image and specifying the sources/packages you would like to mirror.15:53
dwalt#link https://github.com/openstack/openstack-helm-images/blob/master/mini-mirror/README.rst15:53
dwalt#link https://github.com/openstack/openstack-helm-addons/tree/master/mini-mirror15:53
*** yongiman has quit IRC15:53
portdirectnot just an airship problem, but a 'hey i need to manage an airgapped set of hosts' problem - so really nice to see this work in osh-addons/images15:53
dwaltportdirect: definitely15:53
dwaltAlso, as discussed in the #airshipit meeting earlier, this can easily be expanded to include other types of repos (e.g. rpm)15:53
jayahnrpm! :)15:54
powerds0111sounds good :) do you have a plan to support yum and pip?15:54
jayahnthat would be a good addition, i agree!15:54
portdirect++15:54
portdirectthat should be simple to add dwalt ?15:55
portdirectwould just be a case of a new image?15:55
dwaltportdirect: indeed! There isn't a fleshed out design for it yet, but it would be as simple as copying the existing Dockerfile and modifying it to use a tool to mirror the specific type of repository. OSH images already supports multiple distributions15:56
portdirectnice - jayahn / powerds0111 if you have the bandwidth it would be awesome to see this reliased15:57
*** radeks has joined #openstack-meeting-415:57
portdirectI suspect evrardjp would also have interest as well15:57
portdirects/reliased/implemented15:57
portdirectwould also be great to see some basic gating around this if possible15:58
jayahnyeah, will surely discuss internally, we really need this. thanks dwalt15:58
*** gcheresh_ has quit IRC15:59
jayahndwalt: thanks for a good work :)15:59
portdirectok - out of time :(16:00
portdirectlets move over to the osh channel - though next week id really like to discuss the work that has been going on in docs - lets get it 1st thing on the schedule16:01
jayahnokay16:01
portdirectand thanks for all the work everyones been putting in over the last few weeks - really nice to see things ramping back up again :D16:01
portdirect#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:01
openstackMeeting ended Tue Jan 15 16:01:55 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-01-15-15.02.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-01-15-15.02.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-01-15-15.02.log.html16:02
*** megheisler has quit IRC16:03
*** radeks has quit IRC16:04
*** salmankhan has joined #openstack-meeting-416:04
*** dwalt has left #openstack-meeting-416:06
*** e0ne has quit IRC16:11
*** k_mouza has joined #openstack-meeting-416:20
*** k_mouza_ has joined #openstack-meeting-416:23
*** k_mouza has quit IRC16:24
*** nick_kar has left #openstack-meeting-416:25
*** k_mouza_ has quit IRC16:27
*** howell has quit IRC16:32
*** k_mouza has joined #openstack-meeting-416:34
*** dklyle has joined #openstack-meeting-416:35
*** iyamahat has quit IRC16:47
*** yamahata has quit IRC16:49
*** georgk has quit IRC16:49
*** salmankhan has quit IRC16:50
*** salmankhan has joined #openstack-meeting-416:50
*** yamamoto has quit IRC16:55
*** iyamahat has joined #openstack-meeting-417:06
*** roman_g has quit IRC17:07
*** macza has joined #openstack-meeting-417:08
*** macza_ has joined #openstack-meeting-417:13
*** e0ne has joined #openstack-meeting-417:13
*** macza has quit IRC17:14
*** yamahata has joined #openstack-meeting-417:24
*** e0ne has quit IRC17:28
*** gcheresh_ has joined #openstack-meeting-417:44
*** yamamoto has joined #openstack-meeting-417:45
*** yamamoto has quit IRC17:48
*** yamamoto has joined #openstack-meeting-417:48
*** yamamoto has quit IRC17:48
*** yamamoto has joined #openstack-meeting-417:53
*** pcaruana has quit IRC18:01
*** yamamoto has quit IRC18:01
*** psachin has quit IRC18:03
*** salmankhan1 has joined #openstack-meeting-418:04
*** TxGirlGeek has quit IRC18:04
*** TxGirlGeek has joined #openstack-meeting-418:05
*** gcheresh_ has quit IRC18:06
*** salmankhan has quit IRC18:07
*** yamamoto has joined #openstack-meeting-418:07
*** k_mouza has quit IRC18:07
*** salmankhan1 has quit IRC18:08
*** diablo_rojo has joined #openstack-meeting-418:12
*** yamamoto has quit IRC18:19
*** yamamoto has joined #openstack-meeting-418:23
*** yamamoto has quit IRC18:32
*** yamamoto has joined #openstack-meeting-418:33
*** k_mouza has joined #openstack-meeting-418:34
*** k_mouza has quit IRC18:34
*** yamamoto has quit IRC18:36
*** yamamoto has joined #openstack-meeting-418:37
*** ralonsoh has quit IRC18:38
*** yamamoto has quit IRC18:45
*** yamamoto has joined #openstack-meeting-418:45
*** yamamoto has quit IRC18:59
*** yamamoto has joined #openstack-meeting-419:05
*** e0ne has joined #openstack-meeting-419:07
*** yamamoto has quit IRC19:09
*** yamamoto has joined #openstack-meeting-419:16
*** gcheresh_ has joined #openstack-meeting-419:18
*** yamamoto has quit IRC19:42
*** yamamoto has joined #openstack-meeting-419:42
*** gcheresh_ has quit IRC19:55
*** njohnston has joined #openstack-meeting-420:27
*** yamamoto has quit IRC20:28
*** yamamoto has joined #openstack-meeting-420:49
*** georgk has joined #openstack-meeting-420:59
*** yamamoto has quit IRC21:02
*** yamamoto has joined #openstack-meeting-421:17
*** yamamoto has quit IRC21:20
*** salmankhan has joined #openstack-meeting-421:23
*** roman_g has joined #openstack-meeting-421:36
*** yamamoto has joined #openstack-meeting-421:52
*** yamamoto has quit IRC21:52
*** yamamoto has joined #openstack-meeting-422:05
*** yamamoto has quit IRC22:14
*** yamamoto has joined #openstack-meeting-422:23
*** yamamoto has quit IRC22:40
*** yamamoto has joined #openstack-meeting-422:41
*** yamamoto has quit IRC22:44
*** hongbin has quit IRC23:01
*** yamamoto has joined #openstack-meeting-423:08
*** yamamoto has quit IRC23:08
*** e0ne has quit IRC23:24
*** georgk has quit IRC23:28
*** yamamoto has joined #openstack-meeting-423:51
*** georgk has joined #openstack-meeting-423:52
*** seajay has quit IRC23:54
*** salmankhan has quit IRC23:56
*** yamamoto has quit IRC23:58

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