Monday, 2015-04-13

*** achanda has quit IRC00:05
*** jamielennox|away is now known as jamielennox00:06
*** salv-orlando has quit IRC00:26
*** sdake has joined #openstack-oslo00:30
*** sdake_ has quit IRC00:34
*** sdake_ has joined #openstack-oslo00:46
*** sdake has quit IRC00:49
*** sdake has joined #openstack-oslo00:52
openstackgerritMerged openstack/oslo.utils: timeutils: avoid passing leap second to datetime  https://review.openstack.org/17246800:54
*** sdake_ has quit IRC00:56
*** yamahata has joined #openstack-oslo01:17
*** dimsum_ has quit IRC01:19
*** achanda has joined #openstack-oslo01:21
*** liusheng has quit IRC01:24
*** amotoki has joined #openstack-oslo01:25
*** liusheng has joined #openstack-oslo01:28
*** dimsum_ has joined #openstack-oslo01:28
*** mriedem has quit IRC01:30
*** mriedem has joined #openstack-oslo01:31
*** dimsum_ has quit IRC01:35
*** mriedem has quit IRC01:58
*** takedakn has joined #openstack-oslo01:59
*** sdake_ has joined #openstack-oslo02:11
*** sdake has quit IRC02:14
*** salv-orlando has joined #openstack-oslo02:15
*** takedakn1 has joined #openstack-oslo02:16
*** takedakn has quit IRC02:17
*** salv-orl_ has joined #openstack-oslo02:18
*** yamahata has quit IRC02:20
*** salv-orlando has quit IRC02:20
*** takedakn1 has quit IRC02:29
*** takedakn has joined #openstack-oslo02:29
*** dimsum_ has joined #openstack-oslo02:35
*** takedakn has quit IRC02:37
*** dimsum_ has quit IRC02:41
*** achanda has quit IRC02:44
*** achanda has joined #openstack-oslo02:48
*** salv-orl_ has quit IRC02:49
*** achanda has quit IRC02:59
*** subscope_ has joined #openstack-oslo03:12
*** dkehn has joined #openstack-oslo03:18
*** dkehn has quit IRC03:25
*** sdake_ has quit IRC03:25
*** salv-orlando has joined #openstack-oslo03:39
*** crc32 has joined #openstack-oslo03:54
*** crc32 has quit IRC03:58
*** achanda has joined #openstack-oslo03:59
*** mdbooth has quit IRC04:01
*** salv-orlando has quit IRC04:02
*** achanda has quit IRC04:05
*** mdbooth has joined #openstack-oslo04:08
*** subscope_ has quit IRC04:43
*** arnaud___ has joined #openstack-oslo04:48
*** rushiagr_away is now known as rushiagr05:04
*** arnaud___ has quit IRC05:06
*** liusheng has quit IRC05:06
*** liusheng has joined #openstack-oslo05:06
*** dulek has joined #openstack-oslo05:25
*** rushiagr is now known as rushiagr_away05:34
*** sreshetn1 has joined #openstack-oslo05:42
*** achanda has joined #openstack-oslo05:53
openstackgerritJoshua Harlow proposed openstack/taskflow: Expose r/o listener callback + details filter callback  https://review.openstack.org/17279505:56
openstackgerritJoshua Harlow proposed openstack/taskflow: Expose r/o listener callback + details filter callback  https://review.openstack.org/17279505:58
*** rushiagr_away is now known as rushiagr06:03
*** sreshetn1 has quit IRC06:15
*** sreshetn1 has joined #openstack-oslo06:24
*** e0ne has joined #openstack-oslo06:41
*** yamahata has joined #openstack-oslo06:42
*** e0ne has quit IRC06:42
*** sreshetn1 has quit IRC06:45
*** jaosorior has joined #openstack-oslo07:02
*** mfedosin has quit IRC07:06
*** tsufiev has quit IRC07:06
*** mfedosin has joined #openstack-oslo07:07
*** tsufiev has joined #openstack-oslo07:07
*** jamielennox is now known as jamielennox|away07:11
*** achanda has quit IRC07:21
*** ihrachyshka has joined #openstack-oslo07:22
*** achanda has joined #openstack-oslo07:22
*** yamahata has quit IRC07:24
*** sreshetn1 has joined #openstack-oslo07:26
*** ihrachyshka has quit IRC07:28
*** ihrachyshka has joined #openstack-oslo07:30
*** sreshetn1 has quit IRC07:34
*** sreshetn1 has joined #openstack-oslo07:37
*** sreshetn1 has quit IRC07:49
*** haypo has joined #openstack-oslo07:55
*** e0ne has joined #openstack-oslo08:08
*** e0ne has quit IRC08:10
*** andreykurilin has joined #openstack-oslo08:11
*** e0ne has joined #openstack-oslo08:14
*** pblaho has joined #openstack-oslo08:14
*** ihrachyshka has quit IRC08:15
*** e0ne has quit IRC08:19
*** achanda has quit IRC08:22
*** ujjain has joined #openstack-oslo08:28
*** ujjain has quit IRC08:28
*** ndipanov has joined #openstack-oslo08:28
haypohi. good news, almost all oslo libraries are python 3 compatible: https://wiki.openstack.org/wiki/Python3#Common_Libraries_.28Oslo_Projects.2908:29
haypofor oslo concurrency, i have a remaining change, can anyone review it? jd__ already voted +2, a need a second reviewer :-) https://review.openstack.org/#/c/146984/08:30
hayposometimes i want to review and approve my own patches :-p08:30
haypooh, another very simple change for python 3: just enable tests which already pass on python 3, https://review.openstack.org/#/c/172356/08:32
haypojd__, sileht: hi. by the way, are you aware of an unstable test in tooz? https://review.openstack.org/#/c/171403/  "test_get_lock_concurrency_locking2(memcached)"08:33
silehthaypo, I have already seen this08:37
hayposileht, it's probably a race condition. i didn't investigate it08:38
haypodhellmann, oh, i wanted to propose a python3 session at the summit, but i see that you already proposed a session. great!08:39
*** sreshetn1 has joined #openstack-oslo08:45
*** haigang has joined #openstack-oslo08:46
*** dguitarbite has quit IRC08:56
*** jamielennox|away is now known as jamielennox09:02
*** dguitarbite has joined #openstack-oslo09:03
*** salv-orlando has joined #openstack-oslo09:04
*** salv-orlando has quit IRC09:07
*** ihrachyshka has joined #openstack-oslo09:07
*** sreshetn1 has quit IRC09:11
*** haigang has quit IRC09:13
*** sreshetn1 has joined #openstack-oslo09:15
*** haigang has joined #openstack-oslo09:15
*** andymaier has joined #openstack-oslo09:17
*** sreshetn1 has quit IRC09:22
*** haigang has quit IRC09:27
*** haigang has joined #openstack-oslo09:28
*** sreshetn1 has joined #openstack-oslo09:30
jd__haypo: yeah I saw but didn't have time to check for it yet :09:40
haypojd__, ok09:51
*** haigang has quit IRC09:54
*** e0ne has joined #openstack-oslo09:55
*** haigang has joined #openstack-oslo09:55
*** e0ne has quit IRC09:56
*** haigang has quit IRC10:00
*** dulek_ has joined #openstack-oslo10:09
*** sdake has joined #openstack-oslo10:09
*** dulek has quit IRC10:11
*** e0ne has joined #openstack-oslo10:17
*** cdent has joined #openstack-oslo10:18
*** sdake_ has joined #openstack-oslo10:28
*** sdake has quit IRC10:31
*** e0ne has quit IRC10:35
*** salv-orlando has joined #openstack-oslo10:35
*** e0ne has joined #openstack-oslo10:37
*** dimsum_ has joined #openstack-oslo10:39
*** e0ne has quit IRC10:41
*** andreykurilin has quit IRC10:43
*** gtt116_ has joined #openstack-oslo10:45
*** gtt116 has quit IRC10:49
*** sdake_ has quit IRC10:53
*** gtt116__ has joined #openstack-oslo10:54
*** gtt116_ has quit IRC10:57
*** dulek_ has quit IRC11:00
*** sreshetn1 has quit IRC11:07
*** dulek_ has joined #openstack-oslo11:12
*** gtt116_ has joined #openstack-oslo11:24
*** gtt116__ has quit IRC11:24
*** ujjain has joined #openstack-oslo11:34
*** tedross has joined #openstack-oslo11:35
*** gtt116__ has joined #openstack-oslo11:38
*** gtt116_ has quit IRC11:41
*** liusheng has quit IRC11:44
*** amotoki has quit IRC11:45
*** ttx has quit IRC11:48
*** ttx has joined #openstack-oslo11:48
*** ttx has quit IRC11:49
*** ttx has joined #openstack-oslo11:49
*** sreshetn1 has joined #openstack-oslo11:49
*** rushiagr is now known as rushiagr_away11:52
*** dimsum_ has quit IRC11:52
*** andreykurilin has joined #openstack-oslo11:58
*** andreykurilin has quit IRC11:59
*** sdake has joined #openstack-oslo12:00
*** andreykurilin has joined #openstack-oslo12:00
*** kgiusti has joined #openstack-oslo12:00
*** sdake_ has joined #openstack-oslo12:01
*** sdake has quit IRC12:04
*** sreshetn1 has quit IRC12:05
*** dulek_ has quit IRC12:08
*** dulek_ has joined #openstack-oslo12:08
*** jamielennox is now known as jamielennox|away12:12
*** jecarey has quit IRC12:13
*** EmilienM|afk is now known as EmilienM12:19
*** salv-orl_ has joined #openstack-oslo12:20
*** zz_jgrimm has quit IRC12:22
*** zz_jgrimm has joined #openstack-oslo12:24
*** salv-orlando has quit IRC12:24
*** sdake_ has quit IRC12:25
*** sdake has joined #openstack-oslo12:25
*** rushiagr_away is now known as rushiagr12:27
*** sdake_ has joined #openstack-oslo12:27
*** sdake has quit IRC12:31
dhellmannamaurymedeiros: my best guess is that your version of requests is "old" and is expecting support for something that has been removed from python as a security measure. Are you using the latest version of the requests package?12:35
dhellmannhaypo: we should definitely collaborate -- is the wiki page on python 3 status up to date?12:35
*** andreykurilin has quit IRC12:39
haypodhellmann, hi. i updated the wiki page friday12:41
haypodhellmann, i didn't check exactly each line12:42
dhellmannhaypo: ok, great (I was at pycon so I'm just catching up on what happened in the real world last week)12:42
haypodhellmann, i mostly use this page as a todo list :) to check which projects must be ported first12:42
haypodhellmann, you may review https://review.openstack.org/#/c/146984/ & https://review.openstack.org/#/c/172356/ for python 3 ;)12:42
dhellmannhaypo: I'll read the current version to update myself - I'm working on a spec to describe a process we could use to allow applications to start porting one at a time to python 312:42
haypodhellmann, i proposed a python 3 session in the nova project too, colleagues told me that it's better to discuss python 3 in a nova specific session too12:43
amaurymedeirosdhellmann, i tried to reinstall it using apt-get install --reinstall ... also tried to pip install requests. when I get home, i'll explore more options12:43
haypodhellmann, i already drafted a "plan" for nova: https://etherpad.openstack.org/p/liberty-nova-summit-ideas12:44
dhellmannhaypo: ok, good, I'll keep an eye out for that on the schedule12:44
haypodhellmann, my plan is quite simple: write patches, get them merged :-D12:44
dhellmannhaypo: ok, I was considering things like how devstack installs the project and making sure we are testing apps in the gate under the right version of python.12:44
dhellmannamaurymedeiros: you might have to install it via pip12:45
*** ttx has quit IRC12:45
*** ttx has joined #openstack-oslo12:45
haypodhellmann, ah? are you aware of python3 issues in devstack?12:45
dhellmannhaypo: well, devstack runs "python" and "pip" and doesn't install anything with python 3 yet12:46
dhellmannso in order to run integration tests on python 3, we need to change that12:46
*** ttx has quit IRC12:46
*** ttx has joined #openstack-oslo12:46
haypodhellmann, i don't know how gates work. for the py34 gate, does it run "tox -e py34"? because tox requires python 3.4 no?12:47
dhellmannhaypo: only for the unit tests. devstack installs code into the global site-packages right now12:47
haypodhellmann, "python" can be "python3" depending on your PATH :) recently, i noticed that tox now uses python3 by default! since tox 1.9.212:47
dhellmannthen it starts the services and runs tempest12:47
jd__hi dhellmann12:48
dhellmannhaypo: right, "can be" - we need to be explicit about which version of python is used for each application12:48
dhellmannhi, jd__12:48
haypodhellmann, i only checked nova. it's very easy to find things to do in nova, currently there are import errors when running tox -e py34 :)12:49
haypodhellmann, but there are maybe many traps with python3 in the infra, in packaging, in unexpected places, etc.12:49
dhellmannhaypo: right, I'm trying to think about what we need to do aside from fixing the code in projects to make it possible to test the results of "fixing the code in projects" :-)12:50
haypodhellmann, you can use the python3 page to list tasks if you want12:50
*** jroll has quit IRC12:50
*** jroll has joined #openstack-oslo12:50
dhellmannhaypo: ok, I'll see about updating that -- I'm also working on a spec, and I will probably pull things from that patch to include. Can I list you as a contributor?12:51
*** bknudson has quit IRC12:51
*** gordc has joined #openstack-oslo12:51
*** sreshetn1 has joined #openstack-oslo12:51
haypo"I will probably pull things from that patch to include" sorry, which patch? do you mean page?12:53
haypodhellmann, if you use the wiki page, you must cite cyril roelandt, he wrote 50% of the page or more :)12:53
*** dimsum_ has joined #openstack-oslo12:53
haypodhellmann, he's my colleague, he ported a lot of libraries!12:53
dhellmannhaypo: sorry, s/patch/page/12:54
dhellmannhaypo: ok, I'll cite cyril :-)12:54
*** Steap has joined #openstack-oslo12:55
haypodhellmann, here is cyril, Steap12:55
Steaphey12:55
haypoSteap, dhellmann wants to start porting *applications* during the Liberty Cycle, I agree, we almost ported all dependencies12:58
Steapyeah, sure12:58
*** dimsum_ has quit IRC12:58
SteapI think we need to pick a project with 2 core devs willing to do these kind of reviews12:59
Steapand then flood the poor devs with patches :)12:59
SteapThat worked well with the Python client.12:59
Steap+s12:59
ihrachyshkahaypo, can it be evolutionary? porting by pieces, as it was done in oslo-incubator13:00
haypoihrachyshka, it must be incremental13:00
*** openstackgerrit has quit IRC13:00
haypoihrachyshka, it's just not possible to review a single patch porting a whole application to python 3 :)13:00
Steapstill, it would be great to do this as quickly as possible13:00
Steapso that we can enable the gate and make sure there are no regressions13:01
ihrachyshkaI am interested in neutron moving to py3, and I'm a core, so you can count on me as a reviewer. it may be better to come up with a spec that would highlight how we achieve the switch though.13:01
haypodhellmann, the classical way is to group changes by common patterns. like: fix usage of print (add parenthesis), dict.iteritems => six.iteritems(dict), fix integer syntax (drop L from 1L), etc.13:01
ihrachyshkaSteap, that's what I meant, having gating while in the middle of the process, for the pieces that we assume ported13:01
haypoihrachyshka, i'm not sure that a spec is very useful13:02
haypoihrachyshka, the basic work is to fix python3 issues, so send patches. what do you expect from a spec?13:02
dhellmannhaypo: that makes sense. As I said, I want to make sure we have a plan to switch on integration testing for python 3 for an app when we think it's ready13:02
ihrachyshkahaypo, that's neutron, we don't do work without a spec, even if very brief :D13:02
ihrachyshkahaypo, well, the gating strategy for the start13:02
*** tedross has left #openstack-oslo13:02
Steapihrachyshka: https://caniusepython3.com/check/ba7f2a23-8a1b-4ec9-9d85-08c7d3b0523013:02
haypodhellmann, the end of the basic plan is: ..., (999) fix last test to make tests with python3, (1000) make py34 gate voting13:03
Steaphere are the blocking deps for neutron13:03
*** openstackgerrit has joined #openstack-oslo13:03
Steapso, these have to be fixed first13:03
ihrachyshkajsonrpclib is vendor specific and can actually be removed now that arista is out, I guess13:03
Steapok13:03
Steapwhat about the oslo.* ?13:03
ihrachyshkaoslo?.. come on, I expected it's covered13:03
haypoihrachyshka, *right now*, oslo messaging doesn't work on python3 :) it's just a matter of time, i will be at the beginning of the liberty cycle13:04
ihrachyshkaack13:04
haypo(then we should convince mike bayer is that PyMySQL slowdown is not a real matter :-D)13:04
haypo(nobody uses MySQL in production, right? :-))13:04
haypo^^ jd__ ;)13:05
ihrachyshkaoslo.context thing is surprising. there should be little to support there, should be easy13:05
dhellmannhaypo: the py34 *unit test* gate is only one of many things we need to update, though. We need the devstack-gate job to run the application under python 313:05
ihrachyshkadhellmann, speaking of neutron, we could run some kind of mixed env, when e.g. server is running py2 while some agents are py313:06
haypodhellmann, since it took almost one year to port a few lines of code (Oslo), I don't expect nova to work fully on python 3 after a single cycle :)13:06
ihrachyshkathat would allow us to gate AND be evolutionary13:06
Steapdhellmann: well, how hard is that ?13:06
dhellmannihrachyshka: I'm not sure I want to support that13:06
haypodhellmann, so i prefer to not start to think too far13:06
ihrachyshkadhellmann, gate != support13:06
haypoihrachyshka, if the code base works on python 2 & 3, you are free to choose your python version ;)13:06
Steapyeah, these are 2 different tasks13:07
ihrachyshkain any case, mixed env would be needed if we consider upgrade13:07
ihrachyshkahaypo, I don't expect it to be as easy as change-print patches13:07
Steapihrachyshka: wanna write that blueprint in an Etherpad now ?13:07
Steaphaypo: ^13:07
dhellmannihrachyshka: I'll have to look at how neutron is installed in devstack. I was going to have devstack look at the trove classifiers for a project to pick the version of python to use for installing it. Are the parts of neutron in different repos so we could set the trove classifiers differently?13:07
haypoihrachyshka, "jsonrpclib is vendor specific" is one example of use case to stay with python 2 :)13:07
dhellmannhaypo: I do not want to support applications on 2 versions of python13:07
haypodhellmann, what do you mean?13:08
haypodhellmann, do you want to drop support for python 2 at the end of the cycle?13:08
ihrachyshkadhellmann, nah, most stuff is in the same repo. but we can execute agents by being explicit about which python interpreter we want13:08
dhellmannhaypo: I want us to move each application to python 3, and then not work on it under python 2 any more13:08
Steapoh13:08
dhellmannhaypo: I'm not talking about time frames yet, just the path to take13:08
Steapwow, that's... ballsy13:08
Steapdhellmann: are you willing to drop Python 2 support at some point ?13:09
ihrachyshkahaypo, I mean, neutron is pluggable. if a vendor plugin is not py3 aware, so be it, we don't have to cope with it ourselves13:09
dhellmannihrachyshka: ok, that would require customizations that I wasn't planning to deal with. I'll have to think about it more.13:09
haypodhellmann, you really need to be prepared to keep python 2 for a very long time13:09
dhellmannSteap: yes, but not for a long time13:09
dhellmannhaypo: why?13:09
Steapdhellmann: I don't get it13:09
haypodhellmann, i would prefer to drop python 2 support as fast as possible, but it's just not possible13:09
ihrachyshkahaypo, specifically why13:09
dhellmannnone of this work is going to be completed in liberty, so stop worrying about timing13:09
ihrachyshkaagreed on the fact that we are not there to consider any drops13:10
haypoone example, RHEL7 has no python3 by default :-p13:10
dhellmannhaypo: you have *a* python 3 package, though, right?13:10
ihrachyshkahaypo, so RHEL-OSP/RDO would install it into their repo! ;)13:10
ihrachyshkaif it's a matter of a dep, no issue here13:11
haypodhellmann, it's possible to install python 3.3 on RHEL, it's just not as easy as keeping python 2.713:11
* ihrachyshka admits he hasn't actually checked what's the py3 story for rhel713:11
haypoand i'm not sure that devops will like you if you force them to install python3 :)13:11
dhellmannhaypo: ok, we're targeting 3.4 at least at this point13:11
haypodhellmann, debian stable has python 3.2 :-D13:11
dhellmannhaypo: it's just another package13:12
ihrachyshkahaypo, ops already install lots of stuff we fetch as deps13:12
dhellmannhaypo: we are not supporting 3.213:12
dhellmannwe decided *that* ages ago13:12
ihrachyshkaI heard glance requires elasticsearch that fetches Qt (sic!) stuff...13:13
haypoihrachyshka, installing a new python major version is not as easy as installing an application. you have to build a new tree for libraries in /usr/lib64/python3.3/..., install pip3, etc.13:13
dhellmanntime for breakfast, bbiab13:13
ihrachyshkahaypo, sure. but if py3 is in its repos, then all libs should be there, just not installed13:14
haypodhellmann, i would prefer a smooth transition. wait until we have enough users running python3 and then decide to deprecate python 213:14
*** bknudson has joined #openstack-oslo13:14
dhellmannusers shouldn't have to make that decision13:14
haypoihrachyshka, this is the theory :) recently, it tried to install PyQt4, it's not available for Python 3 in fedora 21. i don't understand why. fedora 21 is somehow "bleeding edge"13:15
ihrachyshkafedora 21 is so 90s!13:15
ihrachyshkarawhide, that's bleeding13:15
haypoihrachyshka, lol13:15
*** sreshetn1 has quit IRC13:24
*** sreshetn1 has joined #openstack-oslo13:24
*** prad has joined #openstack-oslo13:28
*** andreykurilin has joined #openstack-oslo13:30
*** sreshetn1 has quit IRC13:31
*** stpierre has joined #openstack-oslo13:31
*** jungleboyj has quit IRC13:34
*** kgiusti has quit IRC13:35
*** jecarey has joined #openstack-oslo13:38
jd__dhellmann: still planning releases today?13:41
*** ihrachyshka has quit IRC13:42
*** rushiagr is now known as rushiagr_away13:42
*** dulek_ has quit IRC13:43
*** rushiagr_away is now known as rushiagr13:45
*** ajo has joined #openstack-oslo13:45
*** ihrachyshka has joined #openstack-oslo13:47
Steapihrachyshka: https://etherpad.openstack.org/p/neutron-py3 WDYT ?13:51
*** _amrith_ is now known as amrith13:54
*** sdake has joined #openstack-oslo13:59
ihrachyshkaSteap, I've updated, please take a look13:59
Steapihrachyshka: about your first comment,  this Etherpad is a draft for the spec14:00
ihrachyshkaok14:01
Steapso yeah, the first comment is only about this14:01
SteapI agree with the second one, we can enable the gate, and enable the tests one by one14:01
Steapas for the last comment, well, yeah, but it's hard to know whether it really works on python 3 or not14:02
*** superdan is now known as dansmith14:02
*** sdake_ has quit IRC14:02
SteapIf all the tests pass, maybe issues with Python 3 should just be seen as regular bugs14:02
ihrachyshkaSteap, so 'phase 1', if unit test port is the goal, then it's more or less realistic for L14:03
Steapwell that would already be quite good14:03
Steapchanging the way devstack works (using Python3 instead of Python2) is not excactly a Neutron concenr14:04
ihrachyshkaSteap, it will depend on how major are the issues in py3 env. if it's not broken bad, then maybe bugs are enough14:04
Steapconcern*14:04
Steapyeah14:04
Steapwe cant really know yet14:04
ihrachyshkabut something we should check and fix before we buy the initiative14:04
SteapI don't think we can know how broken it is before actually diving into the code14:06
Steaphaypo: ^ wdyt ?14:06
ihrachyshkawell, that's fair. also, if phase 1 is about unit tests, then devstack is irrelevant14:06
ihrachyshkaand I think unit tests are more than enough14:07
ihrachyshkafor a cycle14:07
ihrachyshkaif not too much14:07
ihrachyshkathough now that neutron was shrinked significantly due to vendor decomposition, it may be a bit easier14:07
ihrachyshkaalso, another thing to note, is that neutron is now managed in four repos14:07
haypoSteap, i think that you should spend 1 or 2 hours to try to run "tox -e py34" and fix most obvious issues, just to check how many code is broken :) maybe run 2to3 before, just to focus on interesting bugs14:08
ihrachyshkaneutron + neutron-[vpn|lb|fw]aas14:08
haypoSteap, i mean, maybe we missed important issues14:08
haypoSteap, for example, "tox -e py34" may fail when installing dependencies for example :-p14:08
haypo-for example14:08
Steaphaypo: currently, it will14:09
Steap:)14:09
Steapihrachyshka: any "small" repo ?14:09
haypoihrachyshka, "neutron was shrinked significantly due to vendor decomposition" oh, i wasn't aware of that. great news!14:09
Steaplike, what is the smallest14:09
ihrachyshkahaypo, yeah, lots of vendor plugins were moved into separate repos in stackforge14:09
ihrachyshkahaypo, now tests take ~15 mins14:10
ihrachyshkain comparison to 40 mins before14:10
*** dimsum_ has joined #openstack-oslo14:10
ihrachyshkaSteap, among neutron repos?14:10
Steapyes14:10
ihrachyshkaSteap, the problem is that *aas repos depend on neutron one14:10
Steapoh ok14:10
ihrachyshkaSteap, so to achieve anything, you start from neutron14:10
SteapI see14:10
SteapI'll add that to the bp14:10
ihrachyshkathe point is that neutron is not the only thing to fix to claim victory14:10
haypoihrachyshka, so let's focus on "neutron"14:10
ihrachyshka(though if you clearly describe that it's not a goal to port *aas in L, then it's also fine)14:11
haypoihrachyshka, we need milestones ;) porting "neutron" would already be a big win14:11
Steapyes14:11
ihrachyshkahaypo, roger that, just sayin'14:11
Steapand at some point, we need to do it :)14:11
*** rushiagr is now known as rushiagr_away14:12
ihrachyshkaif neutron will get unit tests with py3 in 6 months, I will owe Steap a tank of beer14:12
haypoa spec "please port openstack to python3" is pointless14:12
Steapa tank you say ?14:12
* Steap rolls up his sleeves14:12
haypoihrachyshka, FYI Steap prefers guiness14:12
ihrachyshkaSteap, http://images.mocpages.com/user_images/34757/1383317853m_SPLASH.jpg14:13
haypoSteap, "currently, it will" so did you see issues with other dependencies?14:15
Steapnah, jsute the ones I talked about14:16
haypoSteap, ok14:16
SteapI might give it a try14:16
*** sdake_ has joined #openstack-oslo14:18
ihrachyshkaSteap, ok, so neutron ptl is generally for the effort, but we will definitely need a spec14:19
*** sdake has quit IRC14:21
*** eezhova has quit IRC14:22
*** jungleboyj has joined #openstack-oslo14:22
Steapihrachyshka: let's write that in the ehterpad :)14:24
ihrachyshkanot sure we can consider casual talk an official statement :)14:24
Steapwhat exactly defines a spec in nutron ?14:25
ihrachyshkaSteap, so there is https://github.com/openstack/neutron-specs14:26
ihrachyshkaand template is https://github.com/openstack/neutron-specs/blob/master/specs/template.rst14:26
ihrachyshkasome kilo examples: https://github.com/openstack/neutron-specs/tree/master/specs/kilo14:26
Steapoh yeah I see14:27
Steapso, do you want to write the spec, or should I do it ? :p14:28
*** amrith is now known as _amrith_14:28
*** achanda has joined #openstack-oslo14:31
ihrachyshkaSteap, I'm the lazy one, so14:33
Steaphahaha14:33
ihrachyshkaSteap, also, I'm willing to review but not sure I will have lots of cycles to actually work on it14:33
Steapsure, np14:33
Steapa review is already a lot14:33
Steapsometimes I cry a little when people review my patches14:33
*** rushiagr_away is now known as rushiagr14:35
haypoaaaah mais en fait l'alias compile pour python2 et python3... j'suis con14:36
hayposuds ne parle pas python 314:36
dimsum_dhellmann: around?14:39
*** dimsum_ is now known as dims14:39
*** achanda has quit IRC14:41
*** sdake has joined #openstack-oslo14:47
*** sdake_ has quit IRC14:50
*** mriedem has joined #openstack-oslo14:55
*** mriedem has quit IRC14:59
*** mriedem has joined #openstack-oslo15:03
*** stevemar has joined #openstack-oslo15:07
*** sdake_ has joined #openstack-oslo15:07
*** zzzeek has joined #openstack-oslo15:08
dhellmannjd__: yes, I do plan to release some things today15:12
jd__awesome15:12
*** harlowja_at_home has joined #openstack-oslo15:12
dhellmanndims: hi15:13
*** sdake has quit IRC15:13
dhellmannjd__: it might just be tooz? should I go with master there?15:14
*** _amrith_ is now known as amrith15:14
jd__dhellmann: stable/kilo needs a release too15:14
jd__dhellmann: and I would love a new oslo.db from master15:15
dimsdhellmann: harlowja_at_home started putting together a list of highlights for oslo in kilo on friday. if you get a chance please look - https://etherpad.openstack.org/p/kilo-oslo-highlights15:15
dimsjd__: ^^15:15
harlowja_at_homeyo yo15:15
* harlowja_at_home waking up :-P15:15
*** zz_jgrimm is now known as jgrimm15:15
jd__dims: yeah I filled some lines15:15
dhellmannjd__: ok, I think we talked about oslo.db but I don't remember if viktor or rpodolyaka gave the go-ahead15:15
harlowja_at_homeneed my coffeee, lol15:15
jd__hi harlowja_at_home15:15
harlowja_at_homeyo dawg15:15
dimshaha15:15
dhellmanndims: hey, thanks! I was going to start a list like that this week :-)15:15
dhellmannjd__: tooz master is 0.14?15:16
jd__dhellmann: 0.14.0 yeah15:17
*** kgiusti has joined #openstack-oslo15:18
harlowja_at_homejd__,  let's see if neutron people want to get onto the tooz boat15:22
harlowja_at_homeif u say that ML stuffs15:22
*** sreshetn1 has joined #openstack-oslo15:22
harlowja_at_homehttp://lists.openstack.org/pipermail/openstack-dev/2015-April/061268.html ...15:22
harlowja_at_homehttp://lists.openstack.org/pipermail/openstack-dev/2015-April/061292.html i think shows that people are somewhat confused when it comes to features and capabilities of distributed systems...15:23
harlowja_at_home^ not really that unexpected of a result, ha15:23
harlowja_at_homebut perhaps should write more about in tooz itself...15:23
jd__yup15:24
harlowja_at_homejd__,  although jump on https://review.openstack.org/#/c/168921 please; looks like that is recommending making there own group membership abstraction (arggggg)15:27
*** stevemar has quit IRC15:30
*** yamahata has joined #openstack-oslo15:30
*** stevemar has joined #openstack-oslo15:30
*** russellb has quit IRC15:30
dhellmannjd__: does this list look right? https://launchpad.net/python-tooz/+milestone/0.13.215:32
*** mtanino has joined #openstack-oslo15:32
*** russellb has joined #openstack-oslo15:33
dhellmannjd__: the second one about ceilometer partitioning looks like it might be a liberty fix?15:34
jd__dhellmann: now it was an issue in the Redis driver of tooz that I've backported to kilo too15:34
jd__I don't think it needs a fix in Ceilometer at all actually15:35
dhellmannjd__: ok, cool, I just wanted to make sure I had that right before I marked that milestone as closed15:35
jd__dhellmann: do we support the bug as being marked fixed in 2 releases? I think LP supports that15:35
dhellmannjd__: yeah, I have to figure out how to do it again but we can. I figured as long as it was in the earlier release that didn't matter15:36
*** sreshetn1 has quit IRC15:37
jd__I can do it manually otherwise don't bother15:37
dhellmannjd__: both releases are done15:39
jd__dhellmann: ok so I cannot mark the bug fixed in both my bad15:43
* jd__ sad face15:43
openstackgerritJoshua Harlow proposed openstack/tooz: Use rst inline code structure + link to sentinel  https://review.openstack.org/17296515:44
openstackgerritJoshua Harlow proposed openstack/tooz: Use rst inline code structure + link to sentinel  https://review.openstack.org/17296515:45
dhellmannjd__: where did that bug go, it's not on the 0.13.2 page any more?15:46
jd__dhellmann: I've moved it to 0.14.0 while testing, do you want me to put it back to 0.13.2 ?15:47
jd__it's fixed in both so…15:47
dhellmannjd__: yes, it should go in the earlier version. I'll see if I can get it into the newer version, too.15:47
jd__ok let me move it back then :)15:47
*** sreshetn1 has joined #openstack-oslo15:47
jd__dhellmann: done15:48
jd__ah using branches, I see you :)15:48
*** yamahata has quit IRC15:49
*** tsekiyama has joined #openstack-oslo15:50
openstackgerritJoshua Harlow proposed openstack/debtcollector: Ensure that the incoming 'new_class' is actually a class  https://review.openstack.org/17261315:51
dhellmannjd__: I have it targeted to both releases now, but because that milestone is closed I can't set that field15:53
* dhellmann hates launchpad more every day15:53
jd__dhellmann: yeah you need to re-set it to active just the time to use it15:53
jd__that's what I did15:53
dhellmannjd__: ok, done15:54
jd__awesome15:55
*** daniel3_ has joined #openstack-oslo15:55
*** ttx has quit IRC15:57
*** ttx has joined #openstack-oslo15:57
*** gtt116_ has joined #openstack-oslo15:59
openstackgerritJoshua Harlow proposed openstack/oslo.utils: Add missing reflection + uuidutils docs  https://review.openstack.org/17297416:01
*** gtt116__ has quit IRC16:02
*** stevemar has quit IRC16:03
*** haypo has left #openstack-oslo16:04
*** stevemar has joined #openstack-oslo16:04
*** ttx has quit IRC16:05
*** ttx has joined #openstack-oslo16:05
*** sreshetn1 has quit IRC16:05
*** amrith is now known as _amrith_16:16
openstackgerritMerged openstack/oslo-specs: graduate-oslo-versionutils  https://review.openstack.org/16773716:20
*** pblaho has quit IRC16:33
*** dougwig has quit IRC16:35
*** hogepodge has quit IRC16:35
*** dougwig has joined #openstack-oslo16:35
*** sputnik13 has joined #openstack-oslo16:40
*** bknudson has quit IRC16:40
*** subscope_ has joined #openstack-oslo16:41
harlowja_at_homebb, heading in16:46
*** harlowja_at_home has quit IRC16:46
*** kgiusti has quit IRC16:47
*** ujjain has quit IRC16:51
*** yamahata has joined #openstack-oslo16:57
*** ihrachyshka has quit IRC17:00
dhellmanndims: we should talk about the best way to merge the versionutils patches that we're importing. Now that the spec is approved, I can just fast-approve them and leave the ones that actually add the module to the library. Or we could wait for the final patches to be approved and then merge them all at once. Thoughts?17:01
*** sreshetn1 has joined #openstack-oslo17:01
*** flaper87 has quit IRC17:03
dimsdhellmann: +1 to fast approve them17:05
dhellmanndims: ok, I'll go ahead and do that today or tomorrow then17:05
dimsthanks dhellmann17:05
*** andymaier has quit IRC17:06
*** sreshetn1 has quit IRC17:06
*** subscope_ has quit IRC17:08
*** sputnik13 has quit IRC17:08
*** flaper87 has joined #openstack-oslo17:16
*** achanda has joined #openstack-oslo17:18
*** fesp has joined #openstack-oslo17:18
amaurymedeirosdhellmann, it turns out the problem was my version of pip. i downloaded a new one using get-pip.py and it fixed it. i sent the patch and added you as a reviewer as you asked: https://review.openstack.org/#/c/172993/17:19
*** fesp has quit IRC17:21
*** hogepodge has joined #openstack-oslo17:23
*** harlowja_away is now known as harlowja17:37
*** bknudson has joined #openstack-oslo17:48
openstackgerritJoshua Harlow proposed openstack/oslo.utils: Add missing reflection + uuidutils docs  https://review.openstack.org/17297417:49
*** sreshetn1 has joined #openstack-oslo18:03
*** sreshetn1 has quit IRC18:07
*** sputnik13 has joined #openstack-oslo18:19
*** cdent has quit IRC18:20
*** rpodolyaka has quit IRC18:22
*** kgiusti has joined #openstack-oslo18:23
openstackgerritJoshua Harlow proposed openstack/tooz: Silence logs + errors when stopping and group membership lost  https://review.openstack.org/17303018:29
*** SlickNik has quit IRC18:31
*** SlickNik has joined #openstack-oslo18:32
dhellmannamaurymedeiros: I'm glad you figured it out. I'll add your new patch to my review queue. Thanks!18:37
amaurymedeirosdhellmann, thank you18:49
openstackgerritJoshua Harlow proposed openstack/tooz: Handle errors that come out of pymemcache better  https://review.openstack.org/17303818:54
*** hockeynut_ has quit IRC18:57
*** hockeynut has joined #openstack-oslo18:58
*** _amrith_ is now known as amrith19:02
*** sreshetn1 has joined #openstack-oslo19:03
*** e0ne has joined #openstack-oslo19:04
*** sreshetn1 has quit IRC19:08
*** e0ne has quit IRC19:14
*** e0ne has joined #openstack-oslo19:17
*** amrith is now known as _amrith_19:19
openstackgerritJoshua Harlow proposed openstack/tooz: Handle errors that come out of pymemcache better  https://review.openstack.org/17303819:24
*** daniel3_ has quit IRC19:26
*** daniel3_ has joined #openstack-oslo19:27
dhellmannjd__: oslo.db 1.8.0 released19:31
openstackgerritJoshua Harlow proposed openstack/tooz: Handle errors that come out of pymemcache better  https://review.openstack.org/17303819:31
openstackgerritJoshua Harlow proposed openstack/tooz: Handle errors that come out of pymemcache better  https://review.openstack.org/17303819:34
*** haypo has joined #openstack-oslo19:35
*** rushiagr is now known as rushiagr_away19:36
openstackgerritJoshua Harlow proposed openstack/tooz: Handle errors that come out of pymemcache better  https://review.openstack.org/17303819:38
openstackgerritJoshua Harlow proposed openstack/tooz: Handle errors that come out of pymemcache better  https://review.openstack.org/17303819:40
*** flashgordon has quit IRC19:42
*** rushiagr_away is now known as rushiagr19:45
*** sreshetn1 has joined #openstack-oslo19:47
*** cdent has joined #openstack-oslo19:48
dhellmannsileht: how do you feel about turning on py 3.4 unit tests for oslo.messaging? https://review.openstack.org/#/c/173056/119:48
openstackgerritMerged openstack/tooz: Use rst inline code structure + link to sentinel  https://review.openstack.org/17296519:51
*** sdake has joined #openstack-oslo19:53
openstackgerritJoshua Harlow proposed openstack/tooz: Use oslo.serialization msgpackutils  https://review.openstack.org/17305819:54
*** sdake_ has quit IRC19:56
*** achanda has quit IRC19:57
haypodhellmann, maybe it will make more sense after my change https://review.openstack.org/172135  is accepted for oslo messaging20:00
haypo?20:00
haypodhellmann, to run oslo messaging tests with eventlet20:00
dhellmannhaypo: ah, ok. I ran the tests and they passed on my system so I thought it was already working?20:00
haypodhellmann, tests using eventlet are skipped. but oslo messaging without eventlet means using the blocking executor, whereas almost all projects use the eventlet executor20:02
haypodhellmann, (maybe gnocchi or keystone can use the blocking executor?)20:02
haypodhellmann, (even aioeventlet executor is skipped on python3! ;-) it requires eventlet as well)20:02
*** tsekiyam_ has joined #openstack-oslo20:03
haypodhellmann, we should wait some weeks until eventlet can be bumped20:03
*** cdent has quit IRC20:03
dhellmannhaypo: we have to start somewhere, so I'm ok with turning the tests on and then updating them to use eventlet20:03
*** tsekiyama has quit IRC20:05
haypodhellmann, oh wait20:06
haypodhellmann, i already proposed the same change :-D https://review.openstack.org/#/c/172221/20:06
haypodhellmann, sorry, i forgot my own patch :-D it already got a +220:06
haypodhellmann, and mehdi voted +120:06
*** e0ne has quit IRC20:08
haypodhellmann, when i wrote this patch, everything exploded on my PC! with tox 1.9.2, i got various python 3 issues in project-conflit itself, but also jenkins-job-builder. i sent patches too ;)20:08
haypodhellmann, (FYI: https://review.openstack.org/#/c/172239/ (merged) & https://review.openstack.org/#/c/172238/ (jenkins-job-builder))20:08
dhellmannhaypo: hahaha, ok20:13
*** rpodolyaka has joined #openstack-oslo20:13
haypodhellmann, python3 is like a can of worms. it's hard to stay focus on a single project20:14
krotscheckdhellmann: I hear there's a project to replace launchpad :/20:14
dhellmannkrotscheck: yeah :-(20:14
*** achanda has joined #openstack-oslo20:25
*** jungleboyj has quit IRC20:32
*** jgrimm is now known as zz_jgrimm20:33
*** HenryG has quit IRC20:33
*** HenryG has joined #openstack-oslo20:37
*** tsekiyam_ has quit IRC20:41
*** e0ne has joined #openstack-oslo20:41
*** tsekiyama has joined #openstack-oslo20:43
*** ajo has quit IRC20:51
*** sdake_ has joined #openstack-oslo20:53
*** andreykurilin has quit IRC20:55
*** haypo has quit IRC20:56
*** sdake has quit IRC20:57
*** rjaiswal_ has joined #openstack-oslo20:59
rjaiswal_Hi Folks, can anyone take a look at this - https://answers.launchpad.net/pbr/+question/26513720:59
krotscheckIs there a planned release for oslo.middleware (liberty) anytime soon?21:00
dhellmanngordc: are you ready for an oslo.middlware release? ^^21:01
dhellmannrjaiswal_: that question is filed against pbr but seems to be about tooz21:02
gordcdhellmann: fine with me. i think only change was CORS patch.21:02
dhellmannrjaiswal_: I refiled it for you to ensure the owners of that lib see it21:02
dhellmanngordc: ok - krotscheck  tomorrow morning?21:03
rjaiswal_thanks @dhellman21:03
krotscheckdhellmann, gordc: Hrm, if I had an option, I'd want an oslo.config release so I can tweak the tests in that CORS patch, but I can do that in a subsequent release.21:04
dhellmannkrotscheck: I can probably do both21:04
gordcdhellmann: thanks :)21:04
krotscheckdhellmann: Ok, maybe do config first, then give me 24 hours or so to get the tests updated and landed?21:04
krotscheckOh wait, I have to get global-requiremetns updated :/21:05
krotscheckBetter make that 48 hours :D21:05
dhellmannkrotscheck: ok21:05
krotscheckdhellmann: Thanks :D21:05
krotscheckoslo_db is the correct namespace, yes?21:07
dhellmannkrotscheck: yes21:07
gordcdhellmann: do you know who i should ask to give permission to add stable/* branch to python-ceilometerclient?21:07
dhellmanngordc: let me look21:08
gordcdhellmann: cool cool21:09
dhellmanngordc: if I'm reading the acls right anyone in ceilometer-core should be able to create stable branches21:09
dhellmanngordc: if that's not the case, fungi should be able to help figure out why21:09
*** cdent has joined #openstack-oslo21:09
*** rushiagr is now known as rushiagr_away21:10
gordcdhellmann: oh... we're probably doing it wrong then. eglynn tried to git push something last week and he didn't have permission.21:10
gordci'll check with fungi.21:10
dhellmanngordc: I just use gerrit to make branches21:11
dhellmannI'm not sure if you can push a branch creation21:11
gordcdhellmann: ah i see. /me doesn't see any buttons/forms in branches subtab so i'm guessing i can't do it.21:12
dhellmanngordc: https://review.openstack.org/#/admin/projects/openstack/python-ceilometerclient,branches21:12
*** stevemar has quit IRC21:13
openstackgerritJoshua Harlow proposed openstack/tooz: Handle errors that come out of pymemcache better  https://review.openstack.org/17303821:13
gordcdhellmann: i just see static table "branch name" and "revision"... and then 3 entries21:14
dhellmanngordc: ah, ok. I may see the form because I'm in stable-maint-core21:14
dhellmanngordc: the acl file for ceilometerclient looks different from what we have for oslo, so I'd ask someone in infra to help straighten it out21:14
dhellmanngordc: that said, if you want me to create a branch in the mean time just tell me the sha21:15
gordcdhellmann: ah cool cool. i'll check with fungi21:15
gordcdhellmann: i think we'd just want to tag against 1.0.12... will grab the link21:15
gordcdhellmann: icehouse and juno reqs are capped against this: https://github.com/openstack/python-ceilometerclient/releases/tag/1.0.1221:16
*** sreshetn1 has quit IRC21:17
dhellmanngordc: so you want stable/icehouse and stable/juno branches created from that same point?21:18
dhellmanngordc: why is the cap set to include the patch level there?21:18
*** andreykurilin has joined #openstack-oslo21:20
gordc... why are requirements capped at 1.0.12? i believe there was an oslo lib we pulled in that was not compatibilty with icehouse/juno requirements.21:20
dhellmanngordc: ah, right, the 1.0.13 release should have been 1.121:20
*** stpierre has quit IRC21:21
dhellmanngordc: we should make the cap <=1.1.0,!=1.0.13 eventually to allow you to release new patch releases21:21
gordcdhellmann: right. i'm not exactly sure tbh, i vaguely remember something about SEMVER but i haven't really been following releases (since i couldn't do it until now)21:21
dhellmanngordc: ok21:22
dhellmanngordc: so stable/icehouse and stable/juno should both start from https://github.com/openstack/python-ceilometerclient/commit/7316dd16b8850270db27c1298dcf5a2223f2f1e1 I think. Can you confirm?21:22
dhellmanngordc: and maybe we should move to #ceilometer :-)21:22
gordcdhellmann: sounds good21:22
openstackgerritJoshua Harlow proposed openstack/oslo.serialization: Add docstring to handler registry  https://review.openstack.org/17308921:31
*** jungleboyj has joined #openstack-oslo21:32
dhellmannSpamapS: it would be good to have your input on https://review.openstack.org/#/c/171131 if you have time21:34
*** frickler_ has joined #openstack-oslo21:36
*** frickler has quit IRC21:38
dhellmanndims: let me know if you think we need a spec for https://blueprints.launchpad.net/oslo-incubator/+spec/remove-namespace-packages -- I was viewing it as completing the work started this cycle, so I was going to track it with a bp but hadn't planned on a spec21:39
dimsagree dhellmann, no need for a spec21:40
dhellmanndims: do you want to go ahead and approve it?21:40
dimsdhellmann: done. thanks21:41
dhellmanndims: ty21:41
*** kgiusti has left #openstack-oslo21:42
dimsdhellmann: i'll need some time of yours to go over ptl-y stuff after i get back :)21:42
*** mriedem is now known as mriedem_away21:42
dhellmanndims: yeah, I have a note to start a list for you :-)21:42
* dhellmann is glad to have an extra week to do that21:42
dimsthanks!! :)21:42
dhellmannand of course you know you can just hit me up as needed21:42
dhellmannbut I'll try to do some proper documentation, too21:43
openstackgerritJoshua Harlow proposed openstack/oslo.serialization: More docstring cleanups/tweaks  https://review.openstack.org/17309521:43
dimsmuch appreciated dhellmann!21:43
*** e0ne has quit IRC21:43
*** gordc has quit IRC21:45
openstackgerritJoshua Harlow proposed openstack/oslo.serialization: Add docstring(s) to handler registry  https://review.openstack.org/17308921:46
openstackgerritJoshua Harlow proposed openstack/oslo.serialization: More docstring cleanups/tweaks  https://review.openstack.org/17309521:46
SpamapSdhellmann: I have time. :)21:46
dhellmannSpamapS: excellent, thanks21:47
SpamapSwow, this is interesting... http://zeromq.org/tutorials:dealer-and-router  ... basically it describes SMTP, but calls it ROUTER.. ;-)22:03
*** andreykurilin has quit IRC22:05
krotscheckI love version kickoff week. All my builds go to the top of the queue :)22:06
krotscheckWhoops, wrong channel22:06
openstackgerritJoshua Harlow proposed openstack/tooz: Make and use a thread safe pymemcache client subclass  https://review.openstack.org/17310122:09
openstackgerritJoshua Harlow proposed openstack/tooz: Make and use a thread safe pymemcache client subclass  https://review.openstack.org/17310122:14
openstackgerritJoshua Harlow proposed openstack/tooz: Make and use a thread safe pymemcache client subclass  https://review.openstack.org/17310122:33
SpamapSdhellmann: I tried really hard not to -1 it. I really did.22:34
*** jecarey has quit IRC22:41
*** mtanino has quit IRC22:51
*** bknudson has quit IRC23:02
*** dims_ has joined #openstack-oslo23:03
*** cdent has quit IRC23:03
*** dims has quit IRC23:04
*** mtanino has joined #openstack-oslo23:04
*** jungleboyj has quit IRC23:06
openstackgerritMerged openstack/cliff: Updated from global requirements  https://review.openstack.org/16642823:06
*** jamielennox|away is now known as jamielennox23:22
*** jaosorior has quit IRC23:32
*** SergeyLukjanov has quit IRC23:39
*** SergeyLukjanov has joined #openstack-oslo23:40
*** zzzeek has quit IRC23:43
*** salv-orl_ has quit IRC23:57

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