Friday, 2014-09-12

*** tsekiyama has quit IRC00:02
*** mtanino has quit IRC00:03
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: Add a memory based shared cache  https://review.openstack.org/11629700:04
*** praneshp has quit IRC00:05
*** oomichi_ has joined #openstack-oslo00:05
*** praneshp has joined #openstack-oslo00:05
*** oomichi has quit IRC00:08
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Adjust the WBE log levels  https://review.openstack.org/12094600:15
*** dims__ has quit IRC00:17
*** amrith is now known as _amrith_00:34
openstackgerritSean Dague proposed a change to openstack/oslo.db: Fixup Fixtures Use in db test classes.  https://review.openstack.org/12092300:41
*** mriedem has joined #openstack-oslo00:44
openstackgerritKen Giusti proposed a change to openstack/oslo.messaging: Add documentation explaining how to use the AMQP 1.0 driver  https://review.openstack.org/12086000:50
*** yamahata has joined #openstack-oslo01:05
*** takedakn has quit IRC01:07
*** praneshp has quit IRC01:07
*** takedakn has joined #openstack-oslo01:10
*** noelbk has quit IRC01:11
*** shakamunyi has joined #openstack-oslo01:16
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Increase robustness of WBE message and request processing  https://review.openstack.org/12096001:21
*** shakamunyi has quit IRC01:24
*** dims_ has joined #openstack-oslo01:28
*** shakamunyi has joined #openstack-oslo01:31
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Increase robustness of WBE message and request processing  https://review.openstack.org/12096001:31
*** dims_ has quit IRC01:31
*** dims_ has joined #openstack-oslo01:32
*** dims_ has quit IRC01:39
*** jogo has quit IRC01:40
*** dims_ has joined #openstack-oslo01:40
*** dims__ has joined #openstack-oslo01:44
*** dims_ has quit IRC01:44
*** _amrith_ is now known as amrith01:49
*** dims__ has quit IRC01:51
*** dims_ has joined #openstack-oslo01:52
openstackgerritRichard Jones proposed a change to openstack/oslo.middleware: Add CORS middleware for OpenStack APIs to use.  https://review.openstack.org/12096401:54
openstackgerritRichard Jones proposed a change to openstack/oslo.middleware: Add CORS middleware for OpenStack APIs to use.  https://review.openstack.org/12096401:57
*** dims_ has quit IRC01:57
*** alexpilotti has quit IRC02:11
*** mriedem has left #openstack-oslo02:15
*** mriedem has quit IRC02:15
openstackgerritRichard Jones proposed a change to openstack/oslo.middleware: Add CORS middleware for OpenStack APIs to use.  https://review.openstack.org/12096402:15
*** praneshp has joined #openstack-oslo02:21
*** sunrenjie6 has joined #openstack-oslo02:26
*** takedakn has quit IRC02:42
*** praneshp has quit IRC02:44
*** harlowja is now known as harlowja_away02:56
*** praneshp has joined #openstack-oslo03:12
*** shakamunyi has quit IRC03:22
*** praneshp_ has joined #openstack-oslo03:22
*** praneshp has quit IRC03:26
*** praneshp_ is now known as praneshp03:26
*** praneshp has quit IRC03:36
*** praneshp has joined #openstack-oslo03:38
*** praneshp_ has joined #openstack-oslo03:41
*** praneshp has quit IRC03:42
*** praneshp_ is now known as praneshp03:42
*** zz_jgrimm is now known as jgrimm03:51
*** amotoki has joined #openstack-oslo03:55
*** takedakn has joined #openstack-oslo04:01
openstackgerritRichard Jones proposed a change to openstack/oslo.middleware: Add CORS middleware for OpenStack APIs to use.  https://review.openstack.org/12096404:08
*** jogo has joined #openstack-oslo04:14
*** jogo has quit IRC04:23
*** takedakn has quit IRC04:24
*** takedakn has joined #openstack-oslo04:25
*** HenryG is now known as HenryG_afk04:55
*** harlowja_at_home has joined #openstack-oslo04:57
*** tsufiev has quit IRC04:58
*** tsufiev_ has joined #openstack-oslo04:58
*** jaosorior has joined #openstack-oslo05:01
*** HenryG_afk has quit IRC05:04
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Increase robustness of WBE message and request processing  https://review.openstack.org/12096005:13
openstackgerritA change was merged to openstack/oslo-incubator: Add contributing page to docs  https://review.openstack.org/11935905:15
openstackgerritA change was merged to openstack/oslo-incubator: warn against sorting requirements  https://review.openstack.org/11873605:15
*** noelbk has joined #openstack-oslo05:22
*** HenryG has joined #openstack-oslo05:23
*** HenryG is now known as HenryG_afk05:24
*** harlowja_at_home has quit IRC05:25
openstackgerritA change was merged to openstack/taskflow: Reduce unused tox environments  https://review.openstack.org/11894105:26
openstackgerritA change was merged to openstack/oslo.middleware: Updated from global requirements  https://review.openstack.org/11406405:28
openstackgerritA change was merged to openstack/oslo.messaging: Work toward Python 3.4 support and testing  https://review.openstack.org/11879005:29
*** morganfainberg is now known as stevemar305:50
*** stevemar3 is now known as morganfainberg05:51
openstackgerritOpenStack Proposal Bot proposed a change to openstack/oslo.db: Imported Translations from Transifex  https://review.openstack.org/11853906:00
*** jgrimm is now known as zz_jgrimm06:03
*** sunrenjie6 has quit IRC06:04
openstackgerritOpenStack Proposal Bot proposed a change to openstack/oslo.messaging: Imported Translations from Transifex  https://review.openstack.org/12070006:06
*** ajo has joined #openstack-oslo06:14
openstackgerritZhongyue Luo proposed a change to openstack/oslo-incubator: Use immutable arg rather mutable arg  https://review.openstack.org/10369806:18
*** flaper87|afk is now known as flaper8706:18
openstackgerritZhongyue Luo proposed a change to openstack/oslo-incubator: Use immutable arg rather mutable arg  https://review.openstack.org/10369806:20
*** tkelsey has joined #openstack-oslo06:23
openstackgerritA change was merged to openstack/oslo.i18n: Add missing six dependency  https://review.openstack.org/12043606:31
*** takedakn has quit IRC06:39
*** k4n0 has joined #openstack-oslo06:45
openstackgerritA change was merged to openstack-dev/hacking: Updated from global requirements  https://review.openstack.org/12062807:00
*** ildikov has joined #openstack-oslo07:03
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Work toward Python 3.4 support and testing  https://review.openstack.org/11881307:06
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Increase/adjust the logging of the WBE response/send activities  https://review.openstack.org/10295907:11
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Use oslotest to provide our base test case class  https://review.openstack.org/12029407:16
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Use the features that the oslotest mock base class provides  https://review.openstack.org/12062007:16
*** dtantsur|afk is now known as dtantsur07:20
*** praneshp has quit IRC07:24
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Tidy up the WBE cache (now WBE types) module  https://review.openstack.org/10324507:32
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Tidy up the WBE cache (now WBE types) module  https://review.openstack.org/10324507:33
*** tkelsey has quit IRC07:41
*** amotoki has quit IRC07:51
*** ihrachyshka has joined #openstack-oslo08:03
*** yassine has joined #openstack-oslo08:04
*** noelbk has quit IRC08:07
*** oomichi has joined #openstack-oslo08:12
*** oomichi has quit IRC08:12
*** YorikSar_ has joined #openstack-oslo08:13
*** dtantsur is now known as dtantsur|bbl08:15
*** oomichi_ has quit IRC08:16
*** YorikSar has quit IRC08:17
*** andreykurilin has joined #openstack-oslo08:19
*** tkelsey has joined #openstack-oslo08:21
*** yamahata__ has quit IRC08:22
*** yamahata__ has joined #openstack-oslo08:22
*** yamahata has quit IRC08:26
jd__viktors: any ETA on a new oslo.db release?08:26
*** tkelsey has quit IRC08:28
*** markmc has joined #openstack-oslo09:26
*** YorikSar_ has quit IRC09:45
*** YorikSar has joined #openstack-oslo09:45
*** amotoki has joined #openstack-oslo09:49
*** yamahata has joined #openstack-oslo09:50
*** dims_ has joined #openstack-oslo10:11
*** pcm_ has joined #openstack-oslo10:13
*** dims_ has quit IRC10:16
*** dims_ has joined #openstack-oslo10:16
*** alexpilotti has joined #openstack-oslo10:18
*** AAzza_afk is now known as AAzza10:19
*** dims_ has quit IRC10:20
*** andreykurilin has quit IRC10:21
*** YorikSar has quit IRC10:28
*** YorikSar has joined #openstack-oslo10:30
*** tkelsey has joined #openstack-oslo10:37
*** ajo has quit IRC10:45
viktorsjd__: hi! At the moment release is blocked by bug https://bugs.launchpad.net/oslo.db/+bug/1367354 :(10:55
jd__erf :(10:56
*** dims_ has joined #openstack-oslo11:00
*** ihrachyshka has quit IRC11:22
*** ihrachyshka has joined #openstack-oslo11:22
*** ihrachyshka has quit IRC11:24
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: VMware: Enable vCenter SSL certificate validation  https://review.openstack.org/12018311:25
*** dtantsur|bbl is now known as dtantsur11:35
*** ajo has joined #openstack-oslo11:37
*** kgiusti has joined #openstack-oslo11:59
openstackgerritA change was merged to openstack/oslosphinx: Remove empty file  https://review.openstack.org/12071712:10
*** tedross has joined #openstack-oslo12:10
openstackgerritA change was merged to openstack/oslo-incubator: Do not incur the cost of a second method call  https://review.openstack.org/12093212:14
*** kgiusti has quit IRC12:14
openstackgerritA change was merged to openstack/oslo-incubator: Use immutable arg rather mutable arg  https://review.openstack.org/10369812:14
*** kgiusti has joined #openstack-oslo12:16
*** andreykurilin has joined #openstack-oslo12:19
*** dims_ has quit IRC12:21
*** dims_ has joined #openstack-oslo12:22
*** russellb has joined #openstack-oslo12:27
*** kgiusti has quit IRC12:27
*** kgiusti has joined #openstack-oslo12:28
*** kgiusti has left #openstack-oslo12:28
openstackgerritA change was merged to openstack/oslo.config: Looks for variable subtitution in the same group  https://review.openstack.org/12044512:30
*** kgiusti has joined #openstack-oslo12:31
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.messaging: Don't write python bytecode while testing  https://review.openstack.org/12107412:33
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.middleware: Don't write python bytecode while testing  https://review.openstack.org/12107512:33
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.rootwrap: Don't write python bytecode while testing  https://review.openstack.org/12107612:33
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.serialization: Don't write python bytecode while testing  https://review.openstack.org/12107712:33
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.utils: Don't write python bytecode while testing  https://review.openstack.org/12107812:33
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.version: Don't write python bytecode while testing  https://review.openstack.org/12107912:33
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslosphinx: Don't write python bytecode while testing  https://review.openstack.org/12108012:33
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslotest: Don't write python bytecode while testing  https://review.openstack.org/12108112:33
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.vmware: Don't write python bytecode while testing  https://review.openstack.org/12108412:37
*** ihrachyshka has joined #openstack-oslo12:37
jd__dims_: I'm not sure about that change12:39
jd__is it pbr that write the bytecode when it's run?12:39
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo-incubator: Don't write python bytecode while testing  https://review.openstack.org/12108612:40
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.concurrency: Don't write python bytecode while testing  https://review.openstack.org/12108712:40
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.config: Don't write python bytecode while testing  https://review.openstack.org/12108812:40
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.db: Don't write python bytecode while testing  https://review.openstack.org/12108912:40
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.i18n: Don't write python bytecode while testing  https://review.openstack.org/12109012:40
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo.log: Don't write python bytecode while testing  https://review.openstack.org/12109112:40
dims_jd__: it's documented here - https://docs.python.org/2/using/cmdline.html12:41
jd__dims_: oh I don't doubt it's working, I wonder why/if we need that12:42
dims_jd__: you mean for small projects we won't face that issue that much?12:42
dims_easy to abandon :)12:42
jd__I don't think I ever encountered the issue actually12:43
jd__if you run tox -e py27 nothing should write .pyc files in your source tree12:43
dims_i saw these in my directories12:46
dims_http://paste.openstack.org/show/110631/12:46
openstackgerritA change was merged to openstack/oslo.concurrency: Imported Translations from Transifex  https://review.openstack.org/12069812:48
*** HenryG_afk is now known as HenryG12:51
*** gordc has joined #openstack-oslo12:52
openstackgerritMike Heald proposed a change to openstack-dev/pbr: Retry the integration setup on connection error  https://review.openstack.org/12109312:53
jd__dims_: I do too, I'm just wondering why12:55
jd__but now I get it's the testr run that generates them in the end12:56
dims_jd__: did you see sean's email? http://markmail.org/message/rkuwjzv5gcitmhxw12:56
jd__dims_: I'm just wondering if we couldn't "fix" that in testrepository or the like rather than copy/pasting code everywhere12:58
dims_jd__: works for me if we can find another way12:58
dims_jd__: honestly i have not looked for the source of the problem yet12:59
jd__hehe12:59
jd__well it's just testtools that __import__ everything to discover the tests12:59
jd__so maybe we should teach it to tell Python to import without generating pyc in _this_ case12:59
*** kgiusti has quit IRC13:11
*** kgiusti has joined #openstack-oslo13:13
*** tkelsey has quit IRC13:17
*** dims_ has quit IRC13:23
*** dims_ has joined #openstack-oslo13:23
*** mriedem has joined #openstack-oslo13:24
*** dims__ has joined #openstack-oslo13:28
*** dims_ has quit IRC13:29
*** sigmavirus24_awa is now known as sigmavirus2413:35
mriedemkgiusti: hey, do you know when qpid 0.30 is going to be releaesd?13:37
mriedemkgiusti: noticed at least 2 blocking qpid issues with multiple workers in neutron13:37
mriedemon 0.26 that is13:37
mriedemnot fixed in 0.2813:37
openstackgerritTerry Howe proposed a change to openstack/cliff: Get testenv docs working  https://review.openstack.org/12091813:37
kgiustiI believe the first rc was spun up today.  No hard release date, but usually it's a week or so from RC to release.13:38
*** bknudson has joined #openstack-oslo13:39
kgiustimriedem: I'll ping the project lead and get his 'gut feel' in any case.13:39
mriedemkgiusti: ok thanks, just fyi these are the 2 issues i'm aware of: https://issues.apache.org/jira/browse/QPID-563713:40
mriedemhttps://issues.apache.org/jira/browse/QPID-555713:40
mriedemwe had a performance test team here saying they couldn't scale neutron w/o increasing api_workers but when they did with qpid 0.26 it would hang w/o those patches - we're seeing the same in tempest runs13:41
kgiustimriedem: looks like the release vote will happen on Tuesday, barring any last minute gotchas.13:41
mriedemcool, thanks13:41
kgiustimriedem: if you can give the RC a whirl, there's still a chance we can fix any other issues you folks find: https://dist.apache.org/repos/dist/dev/qpid/0.30-rc/13:42
*** jecarey has joined #openstack-oslo13:43
*** zzzeek has joined #openstack-oslo13:50
*** ihrachyshka has quit IRC13:56
*** zzzeek_ has joined #openstack-oslo14:02
*** ihrachyshka has joined #openstack-oslo14:02
*** zzzeek has quit IRC14:04
*** zzzeek_ is now known as zzzeek14:04
*** dims has joined #openstack-oslo14:05
ihrachyshkadhellmann: ping me when you're around please14:07
*** yassine has quit IRC14:10
*** Guest14516 is now known as hartsocks14:10
*** bnemec is now known as beekneemech14:13
*** dims has quit IRC14:18
*** dims has joined #openstack-oslo14:18
*** mtanino has joined #openstack-oslo14:19
*** dims has quit IRC14:22
*** dims__ is now known as dimsum14:22
*** dimsum is now known as dimsum_14:22
amrithbnemec ... ping14:30
amrithbeekneemech, ping14:30
*** zz_jgrimm is now known as jgrimm14:31
amrithYorikSar, do you have a second.14:34
beekneemechamrith: In a meeting.  Will ping you when I get done.14:34
amriththanks14:34
amrithre: you rcomment in https://review.openstack.org/#/c/110933/ ... you ask that I rebase that change on 109469 which is still not merged. Am I correct in this understanding?14:35
amrithYorikSar, ^^14:35
YorikSaramrith: Hi. We got this change merged after logging change in oslo.concurrency (and you had to change your CR a bit after that). So I suggest to land them in the same order in incubator to have consistent code.14:37
amrithok14:38
amriththx14:39
amrithYorikSar, would it make sense for me to abandon my change (potentially) and treat this as a merge from oslo.concurrency?14:42
YorikSaramrith: Why do you want to abandon it?14:43
amrithin case there are other changes14:43
amrithI don't know for sure14:43
amrithbut in case there are other changes, it would be easy to just smash it all into one "merge from o.c"14:43
amrithI don't know that this is the case (yet)14:43
dhellmannihrachyshka: hi14:43
amrithbut I will check14:43
YorikSaramrith: No, I don't think we should do it like this.14:43
openstackgerritMike Heald proposed a change to openstack-dev/pbr: Retry the integration setup on connection error  https://review.openstack.org/12109314:44
amrithOK, good, that's what I was looking for.14:44
amritha quick up/down on the approach14:44
ihrachyshkadhellmann: hey. lots of mess from my spec, right? :|14:44
openstackgerritA change was merged to openstack/oslo.vmware: Add API to enable calling module to register an exception  https://review.openstack.org/11801314:44
openstackgerritA change was merged to openstack/oslo.concurrency: Add code/api documentation  https://review.openstack.org/11893314:44
dhellmannihrachyshka: well, I think just that one patch was broken, but at this stage in the cycle it caused an unusual amount of trouble14:44
ihrachyshkadhellmann: but I think we're settled now on that it's not going to happen in juno, so another unrelated question.14:44
ihrachyshkadhellmann: there is a review for icehouse: https://review.openstack.org/11484514:45
YorikSaramrith: I've just comparet diffs from your change in lib and in incubator. Found red-green blob in that except: clause - code in your patchset to incubator is not the same as in lib.14:45
ihrachyshkathey attempt to add oslo.utils to keystone deps just because keystoneclient master (will?) use it, and it's installed by devstack without deps (git clone)14:45
amrithYorikSar, let me find out why14:45
ihrachyshkaI wonder whether it should be instead fixed by the backport: https://review.openstack.org/12112814:46
ihrachyshkawhat are your thoughts?14:46
dhellmannihrachyshka: we usually just add things to the requirements list, and not to devstack itself14:46
openstackgerritA change was merged to openstack/oslo.serialization: Updated from global requirements  https://review.openstack.org/11914514:46
dhellmannihrachyshka: you raise an interesting question, though14:46
ihrachyshkadhellmann: my understanding is that the guilty here is devstack that fails to install deps14:47
dhellmannihrachyshka: in this case, the client should probably be installed using the released version of the lib14:47
ihrachyshkaif it falls back to avoiding requirements files, it should make sure that deps are somehow provided14:47
*** AAzza is now known as AAzza_afk14:47
dhellmannihrachyshka: is that what causes it? I thought something failed to upgrade correctly because of the change in dependencies14:48
ihrachyshkadhellmann: but it's installed from git unconditionally, so pip won't install anything14:48
dhellmannihrachyshka: I thought there was a grenade dependency check or something14:48
dhellmanninstalling from source using pip does install the dependencies14:48
dhellmannunless devstack is explicitly turning that off?14:48
*** tsekiyama has joined #openstack-oslo14:49
*** jaypipes is now known as leakypipes\14:50
*** leakypipes\ is now known as leakypipes14:50
ihrachyshkahm, I somehow thought that devstack avoids it, let me check14:51
*** morganfainberg is now known as morgan14:53
ihrachyshkahm, indeed, pip is called inside setup_develop()14:53
ihrachyshkathen I wonder why that guy needed his patch in the first place14:53
ihrachyshkaas per code, keystoneclient should be cloned, then pip is called (=oslo.utils is installed), so it's available when keystoneclient is used. hm.14:54
ihrachyshkadhellmann: ^^14:54
ihrachyshkait's probably that patch that made me think that oslo.utils is not intended to be installed. it is.14:55
dhellmannihrachyshka: I'm not sure. I know that grenade checks dependencies to verify that they "overlap" for upgrades, and that causes problems when we add new ones, but I would have to see a job that failed to understand why they think they need to add a second-level dependency to allow the upgrade14:56
ihrachyshkathere is a link: http://logs.openstack.org/20/113820/3/check/check-grenade-dsvm-icehouse/3fb23cb/logs/grenade.sh.txt.gz14:56
openstackgerritKen Giusti proposed a change to openstack/oslo.messaging: Add documentation explaining how to use the AMQP 1.0 driver  https://review.openstack.org/12086014:59
ihrachyshkahm, there is some _sync_requirements_file step...14:59
*** mtanino has quit IRC15:01
dhellmannihrachyshka: ah, yeah, that would do it15:02
ihrachyshkawhere does it come from?15:02
dhellmannihrachyshka: the new keystone client depends on oslo.foo, but that isn't in the global requirements list, so I wonder if the sync is removing it15:02
dhellmannihrachyshka: devstack does that to ensure that all projects are using the same requirements at the time they are installed15:02
ihrachyshkaaha. does it mean that we should just add that oslo.utils to global reqs?15:03
dhellmannihrachyshka: yes, adding the new requirement to the stable branch is usually how we fix this15:03
ihrachyshkabut global reqs only?.. why adding it to keystone too?15:04
dhellmannI don't know about that15:04
ihrachyshkaok, at least that's some kind of an explanation of what's going on there.15:04
ihrachyshkathanks!15:04
*** zzzeek_ has joined #openstack-oslo15:06
*** zzzeek has quit IRC15:06
*** zzzeek_ is now known as zzzeek15:06
*** AAzzal has joined #openstack-oslo15:06
*** AAzzal is now known as AAzza15:07
*** kgiusti has quit IRC15:08
*** rpodolyaka has joined #openstack-oslo15:08
*** ajo has quit IRC15:08
*** AAzzal has joined #openstack-oslo15:08
*** AAzza_afk has quit IRC15:09
*** AAzza has quit IRC15:11
*** AAzzal is now known as AAzza15:11
*** kgiusti has joined #openstack-oslo15:12
*** kgiusti has joined #openstack-oslo15:13
*** kgiusti has quit IRC15:21
*** kgiusti has joined #openstack-oslo15:24
*** zzzeek has quit IRC15:28
*** zzzeek has joined #openstack-oslo15:30
*** ildikov has quit IRC15:31
*** mriedem has quit IRC15:35
*** tsekiyama has quit IRC15:38
*** tsekiyama has joined #openstack-oslo15:39
*** dtantsur is now known as dtantsur|afk15:40
*** tedross has quit IRC15:42
*** tedross_ has joined #openstack-oslo15:42
*** flashgordon has joined #openstack-oslo15:43
flashgordonbeekneemech:  wow logging is hard https://bugs.launchpad.net/nova/+bug/136794115:44
beekneemechflashgordon: Maybe we should just remove all of those logging messages.  At least that way we wouldn't have any inaccurate log information. ;-)15:46
flashgordonbeekneemech: hehe15:46
*** cfriesen has joined #openstack-oslo15:49
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Organize provisioning to use testresources  https://review.openstack.org/12087015:51
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Reorganize DbTestCase to use provisioning completely  https://review.openstack.org/11017015:51
*** mriedem has joined #openstack-oslo15:53
*** harlowja_at_home has joined #openstack-oslo15:53
*** harlowja_home has joined #openstack-oslo15:53
openstackgerritDavanum Srinivas (dims) proposed a change to openstack/oslo-incubator: EXPERIMENT for lockutils  https://review.openstack.org/12115415:53
*** mriedem1 has joined #openstack-oslo15:54
cfriesenHi, I'm trying to find someone to talk to about design intent in RPC/amqp messaging and what should happen on rabbitmq server switchover.  Can someone point me to the right person/people?15:54
*** harlowja_home has quit IRC15:54
openstackgerritJoshua Harlow proposed a change to openstack/oslo-incubator: Always log the releasing, even under failure  https://review.openstack.org/12115615:54
harlowja_at_homebeekneemech, ^15:55
*** mriedem has quit IRC15:57
*** noelbk has joined #openstack-oslo15:57
beekneemechharlowja_away: Nice15:58
*** zzzeek_ has joined #openstack-oslo15:59
harlowja_at_homeshould of notice that yesterday, my fault :-P15:59
harlowja_at_home*noticed that15:59
*** zzzeek has quit IRC16:00
*** zzzeek_ is now known as zzzeek16:00
beekneemechharlowja_away: Just one comment on the review - we should get this proposed to oslo.concurrency before it merges to incubator so we don't forget.16:00
dhellmannmeeting time16:01
*** morgan is now known as morganfainberg16:02
openstackgerritJoshua Harlow proposed a change to openstack/oslo.concurrency: Always log the releasing, even under failure  https://review.openstack.org/12116016:03
harlowja_at_homebeekneemech, done16:04
dhellmannharlowja_at_home: if you have time to join us in #openstack-meeting-alt, that would be good16:04
harlowja_at_homesuree16:04
openstackgerritKen Giusti proposed a change to openstack/oslo.messaging: Add documentation explaining how to use the AMQP 1.0 driver  https://review.openstack.org/12086016:04
beekneemechharlowja_away: Great, thanks!16:05
*** mriedem has joined #openstack-oslo16:06
*** mriedem1 has quit IRC16:06
harlowja_at_homenp16:07
*** ajo has joined #openstack-oslo16:12
*** ajo has quit IRC16:12
*** ajo has joined #openstack-oslo16:13
*** kgiusti has left #openstack-oslo16:13
*** kgiusti has joined #openstack-oslo16:13
*** markmcclain has joined #openstack-oslo16:19
*** markmcclain has quit IRC16:20
*** markmcclain has joined #openstack-oslo16:20
*** kgiusti has left #openstack-oslo16:22
*** kgiusti has joined #openstack-oslo16:22
*** kgiusti has quit IRC16:22
*** kgiusti has joined #openstack-oslo16:23
cfriesenkgiusti: looks like you know something about rpc/amqp....wonder if you could help me.  I'm seeing a case where the compute node issues an rpc call and then the rabbitmq server fails over.  Some connections on the compute node get reconnected, but the rpc call waits the full 60 seconds before reconnecting to the server.  It seems like it would make more sense to either have all outstanding RPC requests retry or else throw an16:28
cfriesenexception right away--or are there cases where they could still get a response?16:28
kgiusticfriesen: I'm no expert in rabbit, but I do believe there's no way to confirm that a response may _not_ come back.16:30
kgiusticfriesen: in other words, if the rpc request was queued, and the queue fails over to the new broker, the request could still get to the server.16:31
kgiusticfriesen: assuming queue redundancy/clustering.16:31
cfriesenif the request gets to the server, but the client connection was destroyed, is it even possible for the RPC response to be delivered to the client?  If not, perhaps the rpc call should error out immediately rather than waiting for the RPC timeout period.16:37
*** k4n0 has quit IRC16:40
*** harlowja_at_home has quit IRC16:50
*** zzzeek has quit IRC16:50
*** viktors is now known as viktors|afk16:51
kgiusticfriesen: yes, I see your point - if the client's reply queue is destroyed (autodelete) when the connection fails, then the reply will probably be dropped.16:54
cfriesenlooking at impl_kombu.py, it appears that DirectConsumer (used for rpc response) does not use a durable exchange/queue, so it would get lost on rabbitmq server restart16:57
kgiusticfriesen: stepping back, I'm concerned that a fast failure may not be the 'right' thing to do in all cases.  It's really based on the quality of service desired by the RPC user.17:03
kgiusticfriesen: eg. there may be those RPC calls which can retry until timeout, and the app is ok with that.17:03
kgiusticfriesen: on the other hand, I don't _think_ oslo.messaging actually retries sending a message, since it doesn't handle explicit acknowledgments.17:04
cfriesenkgiusti: Do we actually retry sending the message if we don't get a response?  Looking at the code it seemed like we did not, but I might have missed a loop somewhere.   On a different note...I'm seeing multiple AMPQ connections between nova-compute and the AMQP server...do you know why we have multiple connections?  The AMQP docs seem to suggest using a single connection with multiple channels.17:04
kgiusticfriesen: ^^^ I don't believe msg are explicitly re sent, no.17:05
cfriesenkgiusti:  message overlap. :)17:05
kgiusticfriesen: :)17:06
kgiusticfriesen: rabbit uses 0-9 version of the protocol (I think), I'm not sure how that works re: sub-channels.  I think olso.messaging maintains a connection pool, so it could be that multiple connections are created over time.17:07
*** ihrachyshka has quit IRC17:07
*** takedakn has joined #openstack-oslo17:08
kgiusticfriesen: if olso.messaging was to re-send, we'd have to also have it de-duplicate on the receiving side.17:08
cfriesenkgiusti: yes, and then properly handle "connection reset by peer" errors when we try to re-send.17:09
cfriesenkgiusti: simpler to just error out early once the rpc core knows that it cannot possibly get a response to an outstanding rpc call...but then I suppose the question arises what error should be raised since raising the timeout might conceivably cause problems.17:11
kgiusticfriesen: ya - that's seems to be what the 'retry' logic does - block long enough to see if the connection attempt fails, and if it does immediately throw a MessageDeliveryFailure (if retry==1, that is)17:13
cfriesenkgiusti: looks like currently rpc.common.Timeout is the only exception being handled in openstack.common.rpc.proxy.RpcProxy.call17:13
cfriesenbah....I'm looking at havana code, but it should be roughly equivalent17:15
kgiusticfriesen: take a look at trunk - the new retry logic is there.17:15
cfriesenwhich file?17:16
*** praneshp has joined #openstack-oslo17:17
kgiusticfriesen: see oslo/messaging/_drivers/impl_rabbit.py - look at the reconnect(retry) method.17:17
kgiusticfriesen: it's documented in olso/messaging/rpc/client.py17:18
cfriesenkgiusti: what if the original message send succeeds, then the connection gets shut down by the server?17:21
cfriesen(looking at the code now)17:21
*** dtantsur|afk has quit IRC17:22
kgiusticfriesen: so the client's connection to the broker is still up?17:22
kgiusticfriesen: sorry, I'm a bit confused: I'm imagining two connections:  client---broker, and broker---rpc-server17:24
kgiusticfriesen: either can fail independently17:24
cfriesenkgiusti: Right.  I'm viewing rabbitmq as the server, and everyone else as the client.  In my case it seems that nova-compute sends the rpc request successfully to the rabbit-mq server, but then rabbitmq does a controlled switchover (shutting down all the connections in the process)17:25
kgiusticfriesen: ah, you're asking what happens on local connection failure after send!17:25
kgiusticfriesen: gotcha.  IIRC, the client doesn't get an indication of the connection failure while it's waiting for the response.17:26
kgiusticfriesen: I haven't been down that codepath in awhile.17:26
kgiusticfriesen: but I seem to recall a "wait for reply" that simply sits on a queue waiting for messages to arrive (or not).  I don't think it directly monitors the connection's status.17:27
kgiusticfriesen: but it's been awhile since I've looked at that code (above the driver interface).17:28
*** takedakn has quit IRC17:29
cfriesenkgiusti: yes, that seems to be the case.  So I was wondering if the low-level code that actually receives the "connection reset by peer" error on the socket should somehow propagate that upwards so that we could terminate any outstanding RPC waiters early rather than waiting for the timeout17:29
cfriesenThe particular case that I ran into was the service status update which by default does an rpc call() to nova-conductor every 10 seconds.  On rabbitmq switchover the rpc call can take up to 60 seconds to time out, which is long enough for that compute node to be detected as "down" for the purposes of scheduling, live migration, etc.17:31
cfriesenkgiusti: in that particular case I may submit a change to reduce the rpc timeout to less than the status update interval, but I'm sure there are other similar cases that would benefit from early error reporting.17:32
*** takedakn has joined #openstack-oslo17:33
*** harlowja_away is now known as harlowja17:34
*** noelbk has quit IRC17:39
kgiusticfriesen: yes - in general, if oslo.messaging can be sure of message loss than those waiters should fail faster I agree.17:40
*** noelbk has joined #openstack-oslo17:40
openstackgerritA change was merged to openstack/oslo.vmware: Add 'details' property to VMwareDriverException  https://review.openstack.org/12076817:41
openstackgerritA change was merged to openstack/oslo.vmware: Add DuplicateName exception  https://review.openstack.org/12076917:41
*** tristanC has joined #openstack-oslo17:42
*** mtanino has joined #openstack-oslo17:42
*** ajo has quit IRC17:42
tristanCHello folks, I'm trying to run unit tests on stable/icehouse and it fails with: "ImportError: No module named openstack.common.db" from ./openstack/common/db/sqlalchemy/provision.py ... I tried to pull the sqlalchemy-migrate pinout of !=0.9.2  but without any luck... Does someone know what is going on here ?17:43
cfriesenkgiusti: thanks for the discussion, it's been helpful.  If I'm lucky I might be able to get some time to work it...will have to see about priorities.17:43
kgiusticfriesen: that would be great!17:45
openstackgerritamrith proposed a change to openstack/oslo-incubator: Log stdout, stderr and command on execute() error  https://review.openstack.org/10946917:46
amrithbeekneemech, ping!17:54
*** amotoki has quit IRC17:59
*** zzzeek has joined #openstack-oslo18:00
openstackgerritamrith proposed a change to openstack/oslo-incubator: Merge changes from oslo.concurrency into oslo-incubator  https://review.openstack.org/10946918:03
amrithYorikSar, ping. I think git did something I didn't expect it to do. In fact, it did just what I didn't want it to do.18:10
amrithdamn!18:11
beekneemechamrith: ack18:16
amrithhi beekneemech18:16
amrithwanted to check with you on the bug for oslo-incubator18:16
amrithbut in the meanwhile I think I managed to get git all confused18:17
amrithand squashed two changes into one commit18:17
amrithnot my intent18:17
amrithbut they are both in oslo.concurrency now18:17
beekneemechamrith: git reflog is your friend :-)18:17
amrithI thought git was my friend. It has proved that to be a bad assumption.18:18
amrithI'll see what reflog can do for me.18:18
*** mtanino has quit IRC18:18
beekneemechamrith: Basically git reflog should be able to reset you to pre-squashed state without manually untangling the changes.18:18
amrithI'll take a look at it.18:18
amrithbut for oslo-incubator, given taht there are only two changes outstanding from o.c, the merged patch may be ok? put differently the net effect would be the same.18:19
beekneemechamrith: I'd prefer them separate.  It would be a lot easier for an accidental difference to slip in if they're merged and we can't compare the changes 1:1.18:24
*** yamahata has quit IRC18:25
dhellmannbeekneemech: ooo, I'd love to have more detail about using reflog to fix that18:32
beekneemechdhellmann: Basically run git reflog, find the last entry before the squash, and git checkout that HEAD@{#} thing.18:36
dhellmannbeekneemech: that seems far too simple, are you sure that's it? :-)18:37
beekneemechdhellmann: It just worked for me locally (I wanted to make sure I wasn't crazy :-).18:37
beekneemechgit reflog is git's undo button :-)18:37
*** bjornar_ has joined #openstack-oslo18:39
beekneemechamrith: ^FYI, in case you're still looking for git reflog info.18:43
*** jaosorior has quit IRC19:02
*** mtanino has joined #openstack-oslo19:05
openstackgerritA change was merged to openstack/pycadf: Updated from global requirements  https://review.openstack.org/12064919:08
zzzeeklifeless: this optimisingtestsuite is kicking my ass so far19:16
zzzeekjust to get it to find load_tests() is very difficult19:16
zzzeekthen it either hangs, or reports a test as being “duplicated” which is not…still digging19:16
* zzzeek finds print statements inside of testresources/__init__.py is helping19:20
*** kgiusti has quit IRC19:39
*** jecarey has quit IRC19:40
*** mriedem has quit IRC19:43
*** mriedem has joined #openstack-oslo19:43
*** kgiusti has joined #openstack-oslo19:44
*** mriedem1 has joined #openstack-oslo19:47
*** mriedem has quit IRC19:48
*** mtanino has quit IRC19:55
openstackgerritA change was merged to openstack/oslo-incubator: Always log the releasing, even under failure  https://review.openstack.org/12115619:57
*** alexpilotti has quit IRC19:58
openstackgerritDoug Hellmann proposed a change to openstack/oslo-incubator: Add a script for checking out all OpenStack repos  https://review.openstack.org/12121420:00
openstackgerritDoug Hellmann proposed a change to openstack/oslo-incubator: Script to print a list of the official oslo repos  https://review.openstack.org/12121520:00
openstackgerritDoug Hellmann proposed a change to openstack/oslo-incubator: Script to list unreleased changes in all oslo projects  https://review.openstack.org/12121620:00
*** alexpilotti has joined #openstack-oslo20:02
*** andreykurilin_ has joined #openstack-oslo20:05
*** zzzeek has quit IRC20:07
*** kgiusti has quit IRC20:08
*** zzzeek has joined #openstack-oslo20:11
*** kgiusti has joined #openstack-oslo20:11
*** tedross_ has quit IRC20:27
*** AAzza is now known as AAzza_afk20:27
*** kgiusti has left #openstack-oslo20:31
*** vigneshvar has joined #openstack-oslo20:31
vigneshvarHi guys. Kindly review this patch . need some clarification20:32
vigneshvarhttps://review.openstack.org/#/c/103186/20:32
*** ajo has joined #openstack-oslo20:33
dhellmannhi, vigneshvar: we're really really close to cutting off oslo.messaging for juno, is this a critical bug?20:33
*** leakypipes has quit IRC20:34
flashgordondhellmann: https://github.com/jogo/mustached-bear20:35
flashgordonre: https://review.openstack.org/#/c/121214/1/tools/clone_openstack.sh20:35
vigneshvardhellmann: oh am sorry . It is not a critical bug. This bug is becoming a blocker for few other blueprints. So when would be the good time to bring this again20:35
dhellmannflashgordon: yeah, I20:37
dhellmannoops20:37
dhellmannflashgordon: I'm not surprised to find another tool. I wanted to throw that one into the incubator, because it sets up the environment for the tools that come after it in the patch series20:37
flashgordondhellmann: that makes sense, but a few comments about yours20:37
flashgordonbash meh. but mainly the ssh API20:37
dhellmannvigneshvar: after the juno release is announced and kilo opens for developmernt -- you can leave the patch up for review, I just wanted to make sure we both understood its priority and how/when it might be reviewed20:38
dhellmannflashgordon: I'm not scared of a little bash. :-)20:39
dhellmannyou're using an https endpoing to get the list of projects?20:39
dhellmannflashgordon: oh, you have a nicer way to get the current branch, I like that20:40
flashgordondhellmann: I am :)20:40
vigneshvardhellmann: sure. Thanks will get back to you during kilo dev20:40
flashgordondhellmann: yeah I use the rest API to list things20:41
dhellmannflashgordon: if I was doing this in python, I'd want to do that, I think20:41
flashgordondhellmann: that REST API doesn't need any authentication which means you can run it on a machine without ssh keys etc20:42
dhellmannflashgordon: yeah, this is really intended to set up a dev box, where not having ssh access (not keys) is going to just cause issues later on20:44
dhellmannwell, that's how I've been using it, anyway20:44
dhellmannI guess it would be possible for the other scripts in that patch series to work without ssh keys20:45
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Organize provisioning to use testresources  https://review.openstack.org/12087020:45
flashgordondhellmann: anyone another comment in line: I don't do git pulls when local changes on git master20:46
flashgordonif I am on master20:46
dhellmannyeah, that's reasonable20:46
dhellmannI think there's code in devstack to figure that out20:46
dhellmannflashgordon: what's the difference between "git remote update" and "git fetch"?20:47
dhellmannI think "git remote update" is the same as "git fetch --all" and I'm doing a remote update a couple of lines above where I skip a pull if not on master20:47
*** ajo_ has joined #openstack-oslo20:48
amrithbeekneemech, yes, I saw the instructions you provided above. It would be awesome if git reflog provided timestamps.20:48
openstackgerritAndreas Jaeger proposed a change to openstack/oslo.messaging: Stop using intersphinx  https://review.openstack.org/12122920:49
flashgordondhellmann: yeah you are right, they are the same enough in this context20:50
*** tsufiev_ is now known as tsufiev20:50
flashgordondhellmann: maybe down the road we should have a openstack-dev repo for odds and ends like this20:51
openstackgerritamrith proposed a change to openstack/oslo-incubator: Log stdout, stderr and command on execute() error  https://review.openstack.org/10946920:51
dhellmannflashgordon: good idea20:51
flashgordondhellmann: as I run this script before getting on a plane etc20:52
amrithbeekneemech, it turns out that git review -d <change #>,<patch #> is a lot easier20:52
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Organize provisioning to use testresources  https://review.openstack.org/12087020:53
dhellmannflashgordon: yeah, I use the branch check to protect my local changes, but I see your point20:53
openstackgerritDoug Hellmann proposed a change to openstack/oslo-incubator: Script to print a list of the official oslo repos  https://review.openstack.org/12121520:57
openstackgerritDoug Hellmann proposed a change to openstack/oslo-incubator: Script to list unreleased changes in all oslo projects  https://review.openstack.org/12121620:57
openstackgerritDoug Hellmann proposed a change to openstack/oslo-incubator: Add a script for checking out all OpenStack repos  https://review.openstack.org/12121420:57
dhellmannflashgordon: ^^20:58
flashgordondhellmann: what about stackforge?21:00
dhellmannflashgordon: what about it?21:00
flashgordonthis will download of all of it by default21:01
dhellmannyes21:01
flashgordonis that what you want?21:01
dhellmannthat's how I use it, yes21:01
flashgordonthen looks good21:02
flashgordonI run git pull/git fetch on stackforge repos I have already cloned but don't clone new ones21:02
openstackgerritDoug Hellmann proposed a change to openstack/oslo-incubator: Script to print a list of the official oslo repos  https://review.openstack.org/12121521:02
openstackgerritDoug Hellmann proposed a change to openstack/oslo-incubator: Script to list unreleased changes in all oslo projects  https://review.openstack.org/12121621:02
flashgordonbut that is just me21:02
dhellmannflashgordon: yeah, I could see adding a mode to turn that off21:03
flashgordondhellmann: anyway just an idea but as a first pass it looks good now21:04
dhellmannflashgordon: yeah, I'm working on an option to disable stackforge now21:04
*** pcm_ has quit IRC21:07
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Organize provisioning to use testresources  https://review.openstack.org/12087021:10
*** vigneshvar has quit IRC21:14
*** tongli has joined #openstack-oslo21:15
*** tongli has quit IRC21:15
openstackgerritMichael Bayer proposed a change to openstack/oslo.db: Organize provisioning to use testresources  https://review.openstack.org/12087021:16
zzzeekOK im out21:19
*** zzzeek has quit IRC21:20
openstackgerritDoug Hellmann proposed a change to openstack/oslo-incubator: Change clone_openstack.sh to ignore stackforge by default  https://review.openstack.org/12124421:21
dhellmannflashgordon: ^^21:21
dhellmannI'm going to call it a night, too21:21
*** dhellmann is now known as dhellmann_21:22
flashgordondhellmann_: o/21:23
*** andreykurilin_ has quit IRC21:26
*** vigneshvar has joined #openstack-oslo21:26
*** flaper87 is now known as flaper87|afk21:36
*** dimsum_ has quit IRC21:36
*** dimsum_ has joined #openstack-oslo21:36
*** dimsum_ has quit IRC21:40
*** jokke_ has quit IRC21:42
*** jokke_ has joined #openstack-oslo21:42
*** bjornar_ has quit IRC21:43
*** bjornar_ has joined #openstack-oslo21:44
*** mriedem1 has left #openstack-oslo21:47
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Increase robustness of WBE message and request processing  https://review.openstack.org/12096021:52
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Remove the dependency on prettytable  https://review.openstack.org/11762921:58
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Add existing types to generated documentation  https://review.openstack.org/10693021:59
flashgordondhellmann_: FYI https://review.openstack.org/#/c/121250/ for oslo graduation checklist22:01
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Add a mandelbrot parallel calculation WBE example  https://review.openstack.org/10621622:03
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Example which shows how to move values from one task to another  https://review.openstack.org/12051522:03
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Mention issue with more than one thread and reduce workers  https://review.openstack.org/11772922:04
*** gordc has quit IRC22:05
harlowjadhellmann_ alright, think i updated most bugs and other stuff for next-juno (or whatever that becomes) for taskflow, reviews tagged if they weren't and such...22:08
harlowjabeekneemech are u going to resync https://review.openstack.org/#/c/121156/ to nova (or shall i or others?)22:11
*** jgrimm_ has joined #openstack-oslo22:13
*** sigmavirus24 is now known as sigmavirus24_awa22:15
*** jgrimm_ is now known as zz_jgrimm_22:15
*** tsufiev_ has joined #openstack-oslo22:15
*** tsufiev has quit IRC22:15
*** jraim___ has joined #openstack-oslo22:16
*** electrichead has joined #openstack-oslo22:17
*** takedakn has quit IRC22:18
*** yamahata__ has quit IRC22:18
*** jgrimm has quit IRC22:18
*** dhellmann_ has quit IRC22:18
*** jraim__ has quit IRC22:18
*** jraim___ is now known as jraim__22:20
*** boris-42_ has joined #openstack-oslo22:22
*** yamahata__ has joined #openstack-oslo22:26
*** ajo__ has joined #openstack-oslo22:27
*** andreykurilin has quit IRC22:27
*** openstack has joined #openstack-oslo23:37
*** sendak.freenode.net sets mode: +ns 23:37
*** sendak.freenode.net sets mode: -o openstack23:42
-sendak.freenode.net- *** Notice -- TS for #openstack-oslo changed from 1410565045 to 139343354523:42
*** sendak.freenode.net sets mode: +ct-s 23:42
*** YorikSar has joined #openstack-oslo23:42
*** tristanC has joined #openstack-oslo23:42
*** dimsum_ has joined #openstack-oslo23:42
*** ajo_ has joined #openstack-oslo23:42
*** ekarlso- has joined #openstack-oslo23:42
*** dhellmann has joined #openstack-oslo23:42
*** openstackgerrit has joined #openstack-oslo23:42
*** krotscheck has joined #openstack-oslo23:42
*** AAzza has joined #openstack-oslo23:42
*** dteselkin has joined #openstack-oslo23:42
*** sigmavirus24_awa has joined #openstack-oslo23:42
*** HenryG has joined #openstack-oslo23:42
*** russellb has joined #openstack-oslo23:42
*** andreykurilin has joined #openstack-oslo23:42
*** gus has joined #openstack-oslo23:42
*** rpodolyaka has joined #openstack-oslo23:42
*** markmc has joined #openstack-oslo23:42
*** Guest74618 has joined #openstack-oslo23:42
*** lbragstad has joined #openstack-oslo23:42
*** jroll has joined #openstack-oslo23:42
*** boris-42 has joined #openstack-oslo23:42
*** hartbot has joined #openstack-oslo23:42
*** r1chardj0n3s_afk has joined #openstack-oslo23:42
*** cfriesen_ has joined #openstack-oslo23:42
*** kevinbenton has joined #openstack-oslo23:42
*** harlowja_ has joined #openstack-oslo23:42
*** ajo__ has joined #openstack-oslo23:42
*** electrichead has joined #openstack-oslo23:42
*** jraim__ has joined #openstack-oslo23:42
*** tsufiev_ has joined #openstack-oslo23:42
*** zz_jgrimm_ has joined #openstack-oslo23:42
*** bjornar_ has joined #openstack-oslo23:42
*** jokke_ has joined #openstack-oslo23:42
*** vigneshvar has joined #openstack-oslo23:42
*** praneshp has joined #openstack-oslo23:42
*** markmcclain has joined #openstack-oslo23:42
*** flashgordon has joined #openstack-oslo23:42
*** tsekiyama has joined #openstack-oslo23:42
*** sileht has joined #openstack-oslo23:42
*** wendar has joined #openstack-oslo23:42
*** ttx has joined #openstack-oslo23:42
*** flaper87|afk has joined #openstack-oslo23:42
*** bogdando has joined #openstack-oslo23:42
*** toabctl has joined #openstack-oslo23:42
*** GheRivero_pto has joined #openstack-oslo23:42
*** palendae has joined #openstack-oslo23:42
*** morgan has joined #openstack-oslo23:42
*** jeckersb_gone has joined #openstack-oslo23:42
*** mrda-vacation has joined #openstack-oslo23:42
*** dmitryme has joined #openstack-oslo23:42
*** therve has joined #openstack-oslo23:42
*** vishy has joined #openstack-oslo23:42
*** ujjain has joined #openstack-oslo23:42
*** lifeless has joined #openstack-oslo23:42
*** Kiall has joined #openstack-oslo23:42
*** viktors|afk has joined #openstack-oslo23:42
*** hyakuhei has joined #openstack-oslo23:42
*** zhiyan has joined #openstack-oslo23:42
*** amrith has joined #openstack-oslo23:42
*** JoshNang has joined #openstack-oslo23:42
*** cburgess has joined #openstack-oslo23:42
*** SergeyLukjanov has joined #openstack-oslo23:42
*** kragniz has joined #openstack-oslo23:42
*** mugsie has joined #openstack-oslo23:42
*** gmurphy has joined #openstack-oslo23:42
*** jd__ has joined #openstack-oslo23:42
*** ruhe has joined #openstack-oslo23:42
*** clarkb has joined #openstack-oslo23:42
*** mtreinish has joined #openstack-oslo23:42
*** tcammann_ has joined #openstack-oslo23:42
*** anteaya has joined #openstack-oslo23:42
*** SlickNik has joined #openstack-oslo23:42
*** d0ugal has joined #openstack-oslo23:42
*** dstanek has joined #openstack-oslo23:42
*** sendak.freenode.net changes topic to "#openstack-oslo"23:42
*** dimsum_ has quit IRC23:43
*** AAzza_afk has joined #openstack-oslo23:44
*** harlowja has joined #openstack-oslo23:44
*** AAzza_afk has quit IRC23:44
*** harlowja has quit IRC23:44
*** tsekiyama has quit IRC23:48
*** dimsum_ has joined #openstack-oslo23:54
*** bnemec has joined #openstack-oslo23:54
*** dimsum_ has quit IRC23:54
*** dimsum_ has joined #openstack-oslo23:55
*** bjornar_ has quit IRC23:56
*** flaper87|afk has quit IRC23:56
*** flaper87|afk has joined #openstack-oslo23:56
*** zz_jgrimm_ has quit IRC23:58
*** zz_jgrimm_ has joined #openstack-oslo23:58
*** jraim__ has quit IRC23:58
*** jraim__ has joined #openstack-oslo23:58
*** harlowja_ has quit IRC23:58
*** harlowja_ has joined #openstack-oslo23:58

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