Saturday, 2015-10-10

*** sdake has joined #kolla00:04
*** cloudnautique has quit IRC00:11
*** nihilifer has quit IRC00:13
*** Kennan2 has joined #kolla00:37
*** Kennan has quit IRC00:38
*** tummy has joined #kolla00:46
*** tummy has quit IRC00:51
*** achanda has joined #kolla00:57
*** unicell has quit IRC01:07
*** erkules_ has joined #kolla01:16
*** erkules has quit IRC01:19
*** achanda has quit IRC01:28
*** dimsum__ has joined #kolla01:38
*** diogogmt has joined #kolla01:39
*** bmace_ has joined #kolla01:54
*** bmace has quit IRC01:58
*** bmace__ has joined #kolla02:06
*** diogogmt has quit IRC02:07
*** bmace_ has quit IRC02:10
*** dimsum__ has quit IRC02:11
*** mbound has quit IRC02:13
*** dimsum__ has joined #kolla02:24
*** vinkman1 has joined #kolla02:36
*** vinkman has quit IRC02:38
*** sdake has quit IRC02:40
*** thumpba has joined #kolla02:42
*** thumpba_ has joined #kolla02:48
*** thumpba has quit IRC02:48
*** achanda has joined #kolla02:59
*** achanda has quit IRC03:03
*** dimsum__ has quit IRC03:33
*** thumpba_ has quit IRC03:49
*** vinkman1 has quit IRC03:50
*** vinkman has joined #kolla03:51
*** achanda has joined #kolla05:02
*** achanda has quit IRC05:07
*** unicell has joined #kolla05:39
*** unicell1 has joined #kolla05:51
*** unicell has quit IRC05:52
*** achanda has joined #kolla06:04
*** achanda has quit IRC06:10
*** achanda has joined #kolla06:36
SamYaplemorning06:36
openstackgerritSam Yaple proposed openstack/kolla: DO NOT MERGE - Gate things  https://review.openstack.org/23188107:38
openstackgerritSam Yaple proposed openstack/kolla: DO NOT MERGE - Gate things  https://review.openstack.org/23188107:47
openstackgerritSam Yaple proposed openstack/kolla: DO NOT MERGE - Gate things  https://review.openstack.org/23188107:49
*** jainman has joined #kolla07:57
openstackgerritSam Yaple proposed openstack/kolla: DO NOT MERGE - Gate things  https://review.openstack.org/23188107:57
jainman[Bug 1502633] Re: Not able to Launch Instances07:58
openstackbug 1502633 in kolla "connecting to rabbitmq returns ECONNREFUSED" [Critical,Triaged] https://launchpad.net/bugs/150263307:58
jainmanIs there a workaround08:00
SamYaplejainman: im not sure what issue you are having. I see you posted some images failed to build but did not post any logs related to why they failed to build08:01
SamYapleas far as rabbitmq goes, there are also no logs showing why that is not running08:01
SamYaplewe cant do anything without logs08:01
openstackgerritSam Yaple proposed openstack/kolla: DO NOT MERGE - Gate things  https://review.openstack.org/23188108:02
jainmanI can post all the build logs about this08:02
jainmanI am building in debug mode08:02
openstackgerritSam Yaple proposed openstack/kolla: DO NOT MERGE - Gate things  https://review.openstack.org/23188108:06
*** Slower_ has quit IRC08:12
openstackgerritSam Yaple proposed openstack/kolla: DO NOT MERGE - Gate things  https://review.openstack.org/23188108:12
*** Slower has joined #kolla08:12
jainmansudo tools/build.py -n localhost:5000/kollaglue  --push 2>&1 | tee KollaBuild.txt08:18
*** vinkman has quit IRC08:18
jainmanAll  build logs are in KollaBuild.txt08:18
jainmanDo I have to collect other logs08:18
*** achanda has quit IRC08:19
openstackgerritSam Yaple proposed openstack/kolla: DO NOT MERGE - Gate things  https://review.openstack.org/23188108:22
SamYaplethat should be fine08:22
openstackgerritSam Yaple proposed openstack/kolla: DO NOT MERGE - Gate things  https://review.openstack.org/23188108:26
openstackgerritSam Yaple proposed openstack/kolla: DO NOT MERGE - Gate things  https://review.openstack.org/23188108:32
openstackgerritSam Yaple proposed openstack/kolla: DO NOT MERGE - Gate things  https://review.openstack.org/23188108:37
jainmanUploaded logs on lauchpad08:37
*** nihilifer has joined #kolla08:38
jainmanhttps://bugs.launchpad.net/kolla/+bug/150263308:40
openstackLaunchpad bug 1502633 in kolla "connecting to rabbitmq returns ECONNREFUSED" [Critical,Triaged]08:40
*** exploreshaifali has joined #kolla08:53
*** sdake has joined #kolla08:53
*** sdake has quit IRC08:56
*** sdake has joined #kolla08:57
*** sdake has quit IRC08:57
*** exploreshaifali has quit IRC09:01
jainmanI aslso see following error in logs09:02
jainmanERROR:__main__:Put http://localhost:5010/v1/repositories/kollaglue/centos-source-base/: read tcp 127.0.0.1:5010: connection reset by peer ERROR:__main__:Put http://localhost:5010/v1/repositories/kollaglue/centos-source-ceilometer-alarm/: read tcp 127.0.0.1:5010: connection reset by peer09:02
jainmanrepository URL is somewhat different here09:04
*** sdake has joined #kolla09:08
*** jainman has quit IRC09:12
*** sdake has quit IRC09:12
*** jainman has joined #kolla09:28
*** sdake has joined #kolla09:35
*** jainman has quit IRC10:02
jmccarthyo/ Anyone about ? I've got some questions about novnc + ha :)10:43
*** inc0 has joined #kolla11:02
inc0hello11:02
*** Kennan2 has quit IRC11:03
jmccarthyo/ Hiya !11:04
jmccarthyHow are you w/novnc hapt inc0 ;)11:04
*** Kennan has joined #kolla11:05
inc0I'm afraid I didn't understood you jmccarthy :(11:05
jmccarthyOh sorry - I mean stuff to do with novnc_console + haproxy11:06
jmccarthyI seem to have something odd going on with it, so I'm not sure if it's just my setup11:07
inc0hmm, dunno, I didn't test it11:07
jmccarthyOk just wondering :)11:07
inc0hold on let me check if we even did endpoint11:08
jmccarthyI seem to have an issue where I get a console to an instance 50% of the time, as if haproxy is causing an issue11:08
inc0hmm11:08
inc0that's odd, check if you have novnc proxy container running on all controller nodes11:09
jmccarthyI'll double check11:09
inc0maybe it just failed to deploy for some reason11:09
inc0or restarting or something..11:09
jmccarthyThey both seem to be running ok11:10
jmccarthyHow do they decide which compute node to connect to ?11:10
inc0honestly? I don't know, I raretly used vncproxy11:11
jmccarthyMaybe that's it - as of course the instance is only on one of them - ok I'll go poke around logs some more no probs :)11:11
inc0yeah, if you won't find anything conclusive, pop a but on launchpad plz11:12
inc0bug11:12
jmccarthySure ! It seems like misconfig tho somehow not sure, ok11:12
inc0possibly11:13
*** sdake has quit IRC11:17
*** jainman has joined #kolla11:18
jainmanhttps://bugs.launchpad.net/kolla/+bug/150263311:19
openstackLaunchpad bug 1502633 in kolla "connecting to rabbitmq returns ECONNREFUSED" [Critical,Triaged]11:19
inc0is your rabbit running?11:26
inc0docker ps on controller node plz11:27
inc0and check if rabbit is running and correct11:27
inc0also, what is your host system>11:27
jainmanI have  rebuild the the souce as there were error in the end11:28
jainmanHost system is CentOS11:29
jainmanbuild has errors11:29
jainmanAttached logs in the build11:29
nihiliferbuild of docker images or what?11:29
jainmandocker images11:29
*** erkules_ is now known as erkules11:32
*** erkules has joined #kolla11:32
jainmandoker images of kolla11:33
jainmanpush to local registry11:33
jainmansudo tools/build.py -n localhost:5010/kollaglue --base centos --type source --push --debug 2>&1 | tee KollaBuild.txt11:34
inc0and what are the errors?11:37
jainmanERROR:__main__:designate-sink  Failed with status: error ERROR:__main__:murano-base  Failed with status: error ERROR:__main__:nova-base  Failed with status: error ERROR:__main__:galera  Failed with status: error ERROR:__main__:heat-api-cfn  Failed with status: error ERROR:__main__:designate-poolmanager  Failed with status: error ERROR:__main__:cinder-base  Failed with status: error ERROR:__main__:neutron-openvswi11:38
jainmanand many more like this11:38
jainmanBut I can see several kolla images in docker11:38
inc0well, you need to check full logs11:38
inc0that's not very helpful...11:39
jainmanINFO:__main__:swift-object-auditor:Successfully built c8852d963201 INFO:__main__:swift-object-auditor:Built DEBUG:__main__:swift-object-auditor:Processed ERROR:__main__:Put http://localhost:5010/v1/repositories/kollaglue/centos-source-base/: read tcp 127.0.0.1:5010: connection reset by peer ERROR:__main__:Put http://localhost:5010/v1/repositories/kollaglue/centos-source-ceilometer-alarm/: read tcp 127.0.0.1:5010: connection reset by11:40
jainmanand several others similar11:40
jainmanFull log updated in Bug11:41
jainmanhttps://bugs.launchpad.net/kolla/+bug/150263311:41
openstackLaunchpad bug 1502633 in kolla "connecting to rabbitmq returns ECONNREFUSED" [Critical,Triaged]11:41
jainmanDocker images dump11:42
jainmanREPOSITORY                                                         TAG                 IMAGE ID            CREATED             VIRTUAL SIZE localhost:5010/kollaglue/centos-source-swift-object-auditor        latest              c8852d963201        3 hours ago         498 MB localhost:5010/kollaglue/centos-source-swift-object-server         latest              a742354ae220        3 hours ago         498 MB localhost:5010/kollaglue/cent11:42
inc0404 on repo11:44
inc0run build with --no-cache11:44
jainmanIt took 5 hrs before11:47
inc0well, I don't think you can build it without this now11:48
jainmanstarted with --no-cache11:48
inc0anyway, it takes 20min for me to build whole image set so you might want to check what's taking so long for you11:48
jainmanLet me see  it this time11:52
jainmanAs such it keep builing - Pull images but few ianges are I get error11:52
jainmanWhich also cause openstack deployement fail or launch correctly11:53
inc0well, you need most images to deploy openstack11:55
inc0there are few that arent ansibled yet, but most of them are11:55
*** sdake has joined #kolla12:00
jainmanok12:03
jainmanShd I deploy openstack12:03
jainmanI was waiting before doing that12:04
jainmanI  am rebilding with --no-cache, It may take few minutes12:10
*** sdake has quit IRC12:13
*** jainman has quit IRC12:25
*** bkosick_ has joined #kolla12:38
*** bkosick_ has quit IRC12:56
*** exploreshaifali has joined #kolla12:59
*** jainman has joined #kolla13:02
jainmanhttps://bugs.launchpad.net/kolla/+bug/150263313:03
openstackLaunchpad bug 1502633 in kolla "connecting to rabbitmq returns ECONNREFUSED" [Critical,Triaged]13:03
*** jmccarthy has quit IRC13:08
jainmanHi13:12
*** jmccarthy has joined #kolla13:26
openstackgerritMichal Rostecki proposed openstack/kolla: Update Vagrant docs  https://review.openstack.org/23337113:31
*** exploreshaifali has quit IRC13:34
*** dimsum__ has joined #kolla13:36
inc0nihilifer, in vagrant you use registry by default (I didn't deploy vagrant;))13:39
inc0?13:39
inc0because otherwise you don't need to add --push option to build, rather than that you change pull_policy to "missing" and it will use local images13:40
*** diogogmt has joined #kolla13:45
openstackgerritMichal Rostecki proposed openstack/kolla: Fix path of synced_folder in Vagrantfile  https://review.openstack.org/23337413:54
jainmanhttps://bugs.launchpad.net/kolla/+bug/150263313:58
openstackLaunchpad bug 1502633 in kolla "connecting to rabbitmq returns ECONNREFUSED" [Critical,Triaged]13:58
jainmanBuild failed with error ERROR:__main__:designate-sink^M                  Failed with status: error ERROR:__main__:murano-base^M                     Failed with status: error ERROR:__main__:nova-base^M                       Failed with status: error ERROR:__main__:galera^M                  Failed with status: error ERROR:__main__:heat-api-cfn^M                    Failed with status: error13:59
*** diogogmt has quit IRC13:59
inc0jainman, please show actual logs...13:59
inc0we can't work on just error reports13:59
inc0use paste.openstack.org or something14:00
nihiliferinc0: yes, by default vagrant uses registry14:00
inc0ok, thanks, I'll have to test it someday...14:01
jainmaninc0 how to show actual logs on IRC14:01
inc0use paste.openstack.org or something14:01
nihiliferjainman: as far as I understand, you have problems with images building, right?14:02
nihiliferjainman: if yes, then description of your bug is hmm... outdates? inaccurate?14:03
nihiliferoutdated*14:03
inc0nihilifer, not necessarly14:04
inc0jainman, tries to repeat his problem14:04
nihiliferinc0: ah, ok14:04
nihilifersorry jainman14:04
inc0however I have gut feeling that it was indeed some build problem14:05
inc0and if he successfully rebuild whole env, it won't be repeated14:05
inc0but we have to confirm that14:05
jainmanI have today build it trice, everytime same issue14:05
inc0jainman, but with fresh images?14:06
jainmanI am new to IRC -  need help how to paste here14:06
nihiliferjainman: use paste.openstack.org14:06
nihiliferantd then send a link there14:06
nihiliferand*14:07
jainmanhttp://paste.openstack.org/show/475965/14:07
*** mbound has joined #kolla14:08
inc0jainman, this looks like your local registry problem14:08
inc0have you tried to build images without registry?14:08
nihiliferjainman: or is your docker registry running on the same host?14:09
inc0however, please add full log, not just few lines14:09
jainmansudo docker run -d -p 5010:5010 --restart=always --name registry registry:214:10
inc0jainman, now...there is issue14:10
jainmanMy registry is running at 501014:10
jainmanThere are several  kolla images14:10
inc0yeah, but it's not listening on 5010 inside your container14:11
jainmanbut the images with namespace /v1/repositories/ have problem14:11
nihiliferregistry inside containet is listening on 5000, not 501014:12
nihiliferplease do14:12
nihilifersudo docker run -d -p 5010:5000 --restart=always --name registry registry:214:12
jainmanBut that port conflict with keyston admin port14:12
inc0no, it's not, you'll still have it on 501014:12
nihiliferyes, on host you'll have 501014:12
inc0docker will forward 5010 from host to 5000 inside container14:13
nihilifer<host_port>:<contrainer_port>14:13
inc0and I strongly advice using registry v114:13
nihiliferthat's the syntax :)14:13
inc0sudo docker run -d -p 5010:5000 --restart=always --name registry registry14:13
inc0registry v2 have...issues14:13
jainmanOh ok,  Do I have to cleanup before restarting registry14:14
inc0just do docker rm -f registry14:14
inc0it will remove your current registry14:14
inc0try to do fresh image install afterwards14:14
inc0with --no-cache and stuff14:14
inc0unless you already built them14:15
inc0docker images -a14:15
jainmanlocalhost:5010/kollaglue/centos-source-nova-compute                latest              699e40ca66e9        30 minutes ago      653.7 M14:18
inc0then you need to rebuild all of it14:20
inc0try without --push14:21
inc0you can push images later14:21
jainmanDoc says I need to push images in local registry14:22
inc0ehh...trust me on this plz14:22
jainmanmy steps are run  local registry   - sudo docker run -d -p 5010:5000 --restart=always --name registry registry:214:23
jainmanthan build image - sudo tools/build.py -n localhost:5010/kollaglue --base centos  --type source --push --debug 2>&1 | tee KollaBuild.txt14:23
jainmanhow I should change it?14:24
jainmanI am using insecure-registry14:24
inc0remove --push option14:24
inc0you first need to build images, then you can think about pushing them14:24
inc0and it seems to me you can't even build them properly14:24
inc0so let's not add to complexity and try to fix building14:25
inc0sudo tools/build.py -n localhost:5010/kollaglue --base centos  --type source --debug please14:26
jainmanOk understood, But for deployment, is it necessary to push them in registry14:26
inc0are you doing all-in-one on localhost?14:26
jainmanYes14:26
inc0then no, you don't need them pushed14:26
jainmanOk I am starting with new  cmd14:27
inc0sudo tools/build.py -n localhost:5010/kollaglue --base centos  --type source --debug --no-cache14:27
inc0(forgot about --no-cache)14:27
inc0use this command14:27
jainmanI have cleaned all images  - docker images  | awk '{print $1}' | xargs sudo docker rmi -f14:27
inc0cool14:27
jainmanI am trying following deployment14:32
jainmanFirst do allinone on localhost14:32
jainmanonce things works -  Modify it to bare metal provisioning on  remote node14:34
nihiliferok, so you're doing it on VM?14:34
jainmanfollwed by real hardware with compute cluster14:34
jainmanno physical mc centos14:35
nihiliferok14:35
jainmanI have two physical centos - My plan is to  use one for Kolla docker images and management and other for deployment14:35
inc0jainman, use both for deployment14:36
inc0and either setup registry on one or just build images on both14:37
inc0there is no need for losing one node just to keep images on it14:37
jainmanHow I will test baremetal provision in such setup14:37
inc0well, one thing - kolla will not deploy baremetal14:38
inc0you need OS on both nodes14:38
inc0then you configure your ansible/inventory/multinode with both hosts14:38
nihiliferbut jainman said that he has centos installed on both nodes14:39
nihilifernvm14:39
nihiliferlet's see whether images will build at all ;)14:40
inc0+1 nihilifer14:40
jainmanstarted clean build as suggested14:43
jainmanI am little confused14:44
jainmanI have pods with compute and storage cluster14:45
jainmanI and to deploy openstack on it14:45
jainmanSo do I have to install OS on all of them14:46
inc0pods as in kubernates?14:47
inc0and yes, for using kolla you need to deploy OS on every node14:47
inc0https://github.com/openstack/kolla/blob/master/doc/ansible-deployment.rst14:48
inc0look at prerequsites14:48
*** jainman_ has joined #kolla14:49
*** jainman has quit IRC14:50
jainman_Hi14:52
jainman_Pods in datacenter are  Rack mounted  servers14:52
inc0so servers, ok14:53
inc0yes, you need to have OS on them before you use kolla14:53
jainman_But that could be real scale challenge - Can that step be automated e.g boot from doker image14:55
inc0there are solutions for that, docker is not one of them14:56
inc0still, that is out of scope of kolla as for now, but we have session about that in tokyo so we probably will create howto at very least14:56
jainman_I just  see on one doc "A bare metal system takes three minutes to deploy AIO"15:00
inc0ehh...you misunderstood this sentence15:01
inc0baremetal as server with nothing but operating system15:01
inc0and not a vm15:01
jainman_Oh Ok.... Not good in english15:02
inc0it could be better phrased, I agree15:02
inc0still, installing OS is something you need to do yourself, by using Foreman or something, but it's out of scope of kolla15:03
jainman_Does JUJU  or equiv can be used in parallel15:03
nihiliferno, juju has its own way to deploy openstack15:03
inc0I don't know juju well enough to answer that15:03
inc0still, there are several bare metal provisioning tools you can use15:04
jainman_Ok,15:04
jmccarthyI found it: I ran into this, https://bugs.launchpad.net/nova/+bug/98933715:05
openstackLaunchpad bug 989337 in OpenStack Compute (nova) "multiple nova-consoleauth instances cause issues with novncproxy" [Undecided,Fix released] - Assigned to Vish Ishaya (vishvananda)15:05
nihilifera tool from canonical for bare metal provisioning is maas, but I don't know this tool15:05
inc0jmccarthy, fix released in folsom? strange...15:07
inc0anyway, did you solve it?15:08
jmccarthyI haven't as of yet, other than only run one nova_consoleauth which gets around it ..15:09
inc0hmm...you'd need to change haproxy confs to remove other vips15:10
jmccarthyIt might not be that bad to stick in memcache, which seems to be a suggested workaround as well15:10
jmccarthyinc0: remove other vips ?15:11
inc0I meant virtual servers15:11
inc0but memcache would work as well15:11
inc0care to submit a bug for that?15:11
jmccarthyNot sure I follow about removing virtual servers from haproxy ? Sure I can add a bug in no probs15:12
jainman_So, what will be Kolla   differntiator in terms of MaaS - Is it Openstack as microservice15:13
inc0jmccarthy, even better, just change your inventory https://github.com/openstack/kolla/blob/master/ansible/inventory/multinode#L10015:13
inc0instead of group you can add single server there15:14
inc0that will be immediate help15:14
inc0and file a bug so we can change ansible templates to use memcache15:14
inc0https://github.com/openstack/kolla/blob/master/README.rst jainman_ there is a mission statement15:15
nihiliferjainman_: I don't know, I have no knowledge about MaaS. I'm just saying that MaaS could be more relevand than Juju here15:15
nihiliferin general, we have no official way of provisioning nodes (it means - installing OS and Ansible), it's oout of Kolla's scope, as inc0 said15:16
nihiliferrelevant*15:17
nihiliferout*15:17
jmccarthyinc0: There is memcache for swift in meta/main.yml - I should shuffle the inventory how ? I don't quite see how that gets me out of it15:17
inc0jmccarthy, if you provide just one node in this group in inventory15:19
inc0ansible will provision only single instance of it15:19
inc0and haproxy will have just one server in this group15:19
inc0better solution is to use memchache, but that's more work15:20
jmccarthyOh ok I see what your getting at, I'm not sure there is that granularity for just the nova_consoleauth container/portion of nova on the control nodes ?15:22
inc0it is15:22
jmccarthyOh it is there !15:23
inc0https://github.com/openstack/kolla/blob/master/ansible/inventory/multinode#L9615:23
inc0ansible is pretty cool eh?:)15:23
jmccarthyThat is a great work around =)15:24
jmccarthyinc0: Where to raise this bug again ?15:25
inc0https://bugs.launchpad.net/kolla jmccarthy15:25
inc0please include link to original nova bug15:25
jmccarthyinc0: Will do !15:26
inc0thanks a lot15:26
jmccarthyinc0: Thank you ! =)15:27
inc0any time15:28
jmccarthyinc0: Just a quick description I stuck in - https://bugs.launchpad.net/kolla/+bug/150480015:35
openstackLaunchpad bug 1504800 in kolla "kolla issue with multiple nova_consoleauth and HA" [Undecided,New]15:35
jmccarthyHopefully it is enough info15:35
inc0yeah, should be enough15:37
inc0going off, cya guys15:47
*** inc0 has quit IRC15:48
*** diogogmt has joined #kolla15:48
*** unicell has joined #kolla15:50
*** unicell1 has quit IRC15:51
jmccarthyo/15:52
*** jmccarthy has quit IRC16:11
*** jmccarthy has joined #kolla16:12
*** vinkman has joined #kolla17:38
*** exploreshaifali has joined #kolla17:39
*** exploreshaifali has quit IRC17:47
*** jainman_ has quit IRC17:55
*** vinkman has joined #kolla17:59
*** jainman has joined #kolla18:03
jainmanhttps://bugs.launchpad.net/kolla/+bug/150263318:04
openstackLaunchpad bug 1502633 in kolla "connecting to rabbitmq returns ECONNREFUSED" [Critical,Triaged]18:04
jainmanKolla OpenStack AIO build and deploy successful18:06
jainmanBut not able to lauch any instance as no image found18:07
jainmanWhat should I do to resolve it18:07
*** jmccarthy1 has joined #kolla18:10
*** jmccarthy has quit IRC18:10
*** sdake has joined #kolla18:14
*** jainman has quit IRC18:18
*** sdake has quit IRC18:21
*** sdake has joined #kolla18:27
*** sdake has quit IRC18:49
*** cloudnautique has joined #kolla18:50
*** achanda has joined #kolla19:32
*** sdake has joined #kolla19:34
*** sdake has quit IRC19:39
*** sdake has joined #kolla19:44
*** sdake has quit IRC19:55
*** achanda has quit IRC20:03
*** sdake has joined #kolla20:05
*** jmccarthy1 has quit IRC20:11
*** jmccarthy has joined #kolla20:18
*** sdake has quit IRC20:35
*** sdake has joined #kolla20:56
*** jmccarthy has quit IRC20:58
*** achanda has joined #kolla21:08
*** achanda has quit IRC21:12
*** sdake has quit IRC21:13
*** jmccarthy has joined #kolla21:15
*** kragniz has quit IRC21:32
*** kragniz has joined #kolla21:33
*** masterbound has joined #kolla21:33
*** masterbound has quit IRC21:37
*** masterbound has joined #kolla21:40
*** mbound has quit IRC21:43
*** siwos_ has quit IRC21:43
*** Windir has quit IRC21:43
*** SamYaple has quit IRC21:43
*** siwos has joined #kolla21:43
*** SamYaple has joined #kolla21:45
*** Windir has joined #kolla21:47
*** achanda has joined #kolla22:01
*** sdake has joined #kolla22:05
*** achanda has quit IRC22:05
*** Slower has quit IRC22:05
*** sdake has quit IRC22:10
*** sdake has joined #kolla22:10
*** achanda has joined #kolla22:10
*** dimsum__ has quit IRC22:14
*** sdake has quit IRC22:17
*** sdake has joined #kolla22:26
*** achanda has quit IRC22:28
*** sdake has quit IRC22:49
*** jmccarthy has quit IRC23:11
*** jmccarthy1 has joined #kolla23:11
*** dimsum__ has joined #kolla23:14
*** sdake has joined #kolla23:18
sdakeevening folks23:18
*** dimsum__ has quit IRC23:21
jmccarthy1o/23:29
*** dimsum__ has joined #kolla23:35

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