Monday, 2014-06-09

*** yamahata has quit IRC00:04
*** markmcclain1 has quit IRC00:14
*** yamahata has joined #openstack-oslo01:23
*** amotoki has joined #openstack-oslo01:36
*** yamahata has quit IRC01:54
*** yamahata has joined #openstack-oslo01:54
*** mriedem has left #openstack-oslo02:03
*** mriedem has quit IRC02:03
*** mgagne1 is now known as mgagne02:30
*** zhiyan_ is now known as zhiyan02:35
*** gtt116 has joined #openstack-oslo03:03
gtt116any body online?03:03
*** jecarey has quit IRC03:03
*** lbragstad has joined #openstack-oslo03:07
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Increase usefulness of the retry component compile errors  https://review.openstack.org/9868103:57
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Switch to a restructuredtext README file  https://review.openstack.org/9862303:57
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Denote that other projects can use this library  https://review.openstack.org/9862403:59
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Increase usefulness of the retry component compile errors  https://review.openstack.org/9868104:06
*** praneshp has quit IRC04:42
*** praneshp has joined #openstack-oslo04:42
*** lbragstad has quit IRC05:01
*** zhiyan is now known as zhiyan_05:04
*** flashgordon is now known as jogo05:46
*** gtt116 has quit IRC05:49
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Address concurrent mutation of sqlalchemy backend  https://review.openstack.org/9868905:53
*** zhiyan_ is now known as zhiyan06:08
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Clarify locked decorator is for instance methods  https://review.openstack.org/9869106:10
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Sync our version interprocess lock  https://review.openstack.org/9869606:40
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Sync our version of the interprocess lock  https://review.openstack.org/9869606:45
openstackgerritlifeless proposed a change to openstack/oslo-specs: Semantic version support for pbr  https://review.openstack.org/9660806:46
*** jaosorior has joined #openstack-oslo07:14
*** ihrachyshka has joined #openstack-oslo07:27
*** tkelsey has joined #openstack-oslo07:34
*** markmc has joined #openstack-oslo07:53
*** flaper87|afk is now known as flaper8708:01
*** russell_h has quit IRC08:01
*** russell_h has joined #openstack-oslo08:02
*** openstackgerrit has quit IRC08:02
*** gilliard_ has quit IRC08:04
*** openstackgerrit has joined #openstack-oslo08:07
*** praneshp has quit IRC08:09
*** anteaya has quit IRC08:10
openstackgerritChristian Berendt proposed a change to openstack/oslo.vmware: replace iterator.next() with next(iterator)  https://review.openstack.org/9871008:11
*** russell_h has quit IRC08:13
*** russell_h has joined #openstack-oslo08:16
*** russell_h has quit IRC08:21
*** russell_h has joined #openstack-oslo08:24
openstackgerritIlya Pekelny proposed a change to openstack/oslo.db: oslo.db.api module documentation  https://review.openstack.org/9343408:28
*** russell_h has quit IRC08:31
*** russell_h has joined #openstack-oslo08:33
*** russell_h has quit IRC08:38
*** yamahata has quit IRC08:41
*** russell_h has joined #openstack-oslo08:42
openstackgerritIlya Pekelny proposed a change to openstack/oslo.db: oslo.db.options module documentation  https://review.openstack.org/9343608:47
haypodhellmann: hi. i hesitate to vote -1 or even -2 for https://review.openstack.org/#/c/98429/08:55
haypodhellmann: i don't like long lines using *tricks* like "var = var or ..."08:56
haypodhellmann: and i prefer an explicit loop instead of a lambda function with a call to list.extend(...)08:56
haypoi don't think that it adds any value, some changes make the code less readable IMO08:56
*** russell_h has quit IRC08:58
*** russell_h has joined #openstack-oslo08:59
*** russell_h has quit IRC09:02
*** stannie has joined #openstack-oslo09:03
*** russell_h has joined #openstack-oslo09:04
*** russell_h has quit IRC09:14
*** russell_h has joined #openstack-oslo09:14
*** russell_h has quit IRC09:18
*** russell_h has joined #openstack-oslo09:20
openstackgerritMark McLoughlin proposed a change to openstack/oslo.config: Add cfgfilter.ConfigFilter  https://review.openstack.org/9723309:24
*** russell_h has quit IRC09:26
*** erecio has quit IRC09:42
*** erecio has joined #openstack-oslo09:43
silehtmarkmc, Can you review https://review.openstack.org/#/c/75365 ? (I see your progress on the config filter, I hope ceilometer have been fixed before your works on the filter is finished :p)09:49
markmcsileht, will do09:50
silehtmarkmc, thx09:53
haypohum, i should try to review oslo messaging patches09:54
jaosoriorhaypo, is there a specific reason you don't like the "var = var or..." notation? I add more of that stuff in this patch that depends on dhellmann 's patches, here: https://review.openstack.org/#/c/98429/09:59
jaosoriorand replaced some explicit loops with generators09:59
haypojaosorior: i prefer an explicit if09:59
jaosoriorI think the "var = var or ..." is quite readable, so I don't see why it would be a problem :/10:00
haypojaosorior: the "localdir = localedir" instruction is not very useful :)10:00
*** russell_h has joined #openstack-oslo10:01
haypojaosorior: i don't know how to argue why an explicit if is better10:01
jaosoriorThere is not much difference really, my only argument is that it makes the code a bit more compact, and is still quite readable10:02
haypojaosorior: that's why i didn't touch the patch (i didn't leave a comment and i didn't vote)10:02
haypojaosorior: my general rule is one instruction per line, or at least reduce the number of instructions per line10:03
haypojaosorior: "var = ... or ..." is 2 instructions for example, assign and the "or" trick10:03
haypojaosorior: you also replaced "if domain is None:" with "domain or ...", it's not the same, you don't check "is None"10:04
jaosoriorwell, an empty domain is also invalid10:05
haypojaosorior: in my opinion, python code must not be compact :) compact means harder to parser, harder to maintain, harder to debug, etc.10:05
jaosoriorat least the way it was used10:05
jaosoriorso now that's checked also10:06
jaosoriorand I would say the compact argument is subjective10:07
haypojaosorior: i'm fine with "translator = lang.gettext if six.PY3 else lang.ugettext", because here you have two different expressions depending on the test10:07
haypojaosorior: "var = var or ..." looks inefficient to me10:07
jaosoriorI'm flexible to changing the patch, that's no big deal10:08
haypojaosorior: no coding style is "correct", we just have to agree on a coding style. that's why i would like to discuss it here ;)10:09
jaosorioruhm... maybe a little benchmark would be a good idea10:09
haypojaosorior: a micro-benchmark is useless :) the code is probably only called once10:09
jaosoriorand to hear what people's preferences are10:09
haypoi don't really care of performances here ;)10:09
jaosoriorwhat's your timezone?10:10
*** anteaya has joined #openstack-oslo10:10
jaosoriormaybe it would be good to wait until more people are online and discuss these style questions10:11
haypojaosorior: i live in france10:11
jaosorioroh, ok, so I guess two hours less than here10:12
jaosoriorI live in Finland10:12
jaosoriordo you have a particular opinion about the generator bits in the patch I did?10:13
haypojaosorior: good https://review.openstack.org/#/c/98429/2/oslo/i18n/_translate.py,cm10:14
haypojaosorior: bad https://review.openstack.org/#/c/98429/2/oslo/i18n/gettextutils.py,cm -- i don't like lambda10:14
haypofor this one, IMO the current code is more readable and easier to understand10:15
*** zhiyan is now known as zhiyan_10:17
jaosoriorhaypo, I'm not very fond of explicit loops appending to lists, since we have generators available. Would you prefer if I would define a function explicitly instead of using a lambda?10:17
haypojaosorior: it would be better but i still prefer an explicit loop10:18
haypoi don't like to abuse generators10:18
haypoif you are motivated, you should discuss the coding style on the openstack-dev mailing list ;)10:19
haypofor example, "if var: var = ..." vs "var = var or ...", for ...: if ...: list.append(...) vs list.extend(it for it in ... if ...), etc.10:20
jaosoriorsure, that sounds democratic enough10:20
haypobe careful, all coding style discuss starts a troll/flamewar :)10:21
jaosorioryeah, that's what I was fearing10:21
hayposince as i wrote, there is no "good" coding style10:21
jaosoriorwell, I could get rid of the lambda, and of the other one, for that matter, since there are two in that function10:22
jaosoriorbut keep using those generators, at least that's some middle ground10:22
openstackgerritJuan Antonio Osorio Robles proposed a change to openstack/oslo.i18n: Trivial refactors for gettextutils  https://review.openstack.org/9842910:37
openstackgerritMark McLoughlin proposed a change to openstack/oslo.config: Add cfgfilter.ConfigFilter  https://review.openstack.org/9723311:14
*** DuncanT has quit IRC11:41
ihrachyshkamarkmc: hey! around?12:02
ihrachyshkamarkmc: I have a question re your kombu (and amqp) driver in oslo.messaging12:03
ihrachyshkamarkmc: https://review.openstack.org/#/c/38339/1/oslo/messaging/_drivers/impl_rabbit.py , line 1128. why's that?12:03
ihrachyshkadhellmann: you may also have insight into why that's needed ^^12:04
*** stannie has quit IRC12:05
markmcihrachyshka, hey12:07
markmcihrachyshka, somewhere in the driver code we call to_dict()12:07
*** erecio has quit IRC12:08
*** stannie has joined #openstack-oslo12:08
markmcihrachyshka, that can be refactored though - remove the call to to_dict() and remove the wrapper Context object12:08
markmcihrachyshka, as far as oslo.messaging is concerned, context is just a free-form dict12:08
ihrachyshkamarkmc: I'm currently porting neutron to oslo.messaging, and I have a Context class to store all the relevant data, and it has .to_dict() method. The problem is that this hack enforces me to add .iteritems() method to the class, even though if there wouldn't be such a hack, existing .to_dict() would work12:09
ihrachyshkamarkmc: does it mean I should translate Context to a generic dict somewhere in serialiser?12:10
markmcihrachyshka, yes, exactly12:10
markmcihrachyshka, look in nova.rpc at the request context serializer12:10
silehtihrachyshka, http://git.openstack.org/cgit/openstack/ceilometer/tree/ceilometer/messaging.py#n3612:11
markmcyeah, that one :)12:11
ihrachyshkathanks guys!12:11
markmcnp12:11
ihrachyshkaI've almost attempted to fix the issue the wrong way, adding another layer of hackery ;)12:11
markmcno problem that another layer of hackery can't solve :)12:12
ihrachyshkaexactly!12:12
ihrachyshkait's like 'hmmm, it fails because .iteritems() is missing? ok, let's add one! great, it passes further! moving to the next failure' :)12:13
openstackgerritMark McLoughlin proposed a change to openstack/oslo-incubator: cfgfilter: fix some docstring issues  https://review.openstack.org/9877112:27
openstackgerritMark McLoughlin proposed a change to openstack/oslo-incubator: cfgfilter: don't re-register options  https://review.openstack.org/9877212:27
*** erecio has joined #openstack-oslo12:35
*** stannie has quit IRC12:43
openstackgerritMark McLoughlin proposed a change to openstack/oslo.messaging: Use cfgfilter to hide transport opts from API  https://review.openstack.org/9877912:56
dhellmannhaypo: you can leave that comment on the patch, it's easier to discuss there -- some of the changes seem OK, some I was indifferent about13:12
dhellmannhaypo, jaosorior: I'm still catching up on the scrollback, but it looks like good discussion on style. :-)13:13
*** mriedem has joined #openstack-oslo13:14
haypodhellmann: hi13:16
dhellmannhaypo: hi!13:26
*** pafuent has joined #openstack-oslo13:39
jaosoriorhaypo, dhellman, well, now that the timezone is more adequate for everyone, do you have any insights on what was discussed?13:40
pafuentHi. I want to update generate_sample.sh/check_uptodate.sh in the Blazar repository. Should I get the files from the repo and update Blazar manually? or There is another way to do it?13:42
*** jecarey has joined #openstack-oslo13:44
dhellmannjaosorior: I don't mind "var = var or default" in the case where a default is being ensured, esp. when using a mutable value as a default. I do worry in some cases that removing explicit if statements makes test coverage harder to calculate accurately, though I think the tools are getting better at supporting branch coverage.13:46
dhellmannpafuent: you might find these instructions helpful: https://wiki.openstack.org/wiki/Oslo#Syncing_Code_from_Incubator13:46
dhellmannpafuent: we have a tool to help copy modules and scripts from the incubator, since part of copying involves rewriting some defaults in the code to use the project name instead of "oslo"13:47
pafuentdhellmann: Thanks. I'll check that link13:48
dhellmannpafuent: let us know if you run into trouble13:48
pafuentdhellmann: OK13:48
ihrachyshkadhellmann: hey, can we consider latest jsonutils changes in incubator to add support for simplejson for stable back port?14:01
jaosoriordhellman, haypo, well, I see your point, but isn't that case covered by the coverage tool setting a "partially covered" flag on that line?14:01
*** beekneemech is now known as bnemec14:02
*** tsekiyama has joined #openstack-oslo14:02
dhellmannihrachyshka: I'm not sure if that counts as a "feature" or not14:03
dhellmannjaosorior: does the tool say which part of the line is covered? My knowledge of that aspect of coverage.py is thin.14:03
boris-42dhellmann one step closer https://github.com/stackforge/osprofiler14:04
boris-42dhellmann going to make huge read me14:04
ihrachyshkadhellmann: no API changes, just internal performance improvement. I think we should consider it in the same way as any other performance improvements that do not change visible behaviour.14:04
jaosoriordhellman, no, it doesn't say, as far as I've noticed14:04
dhellmannjaosorior: so that would make it more difficult to get useful information from coverage in that case14:05
jaosoriorOK, that makes sense14:05
jaosoriorshould I then revert all the occurrences of the "var = var or ..."?14:05
dhellmannjaosorior: another case where "var = something or somethingelse" can go wrong is with exceptions raised in the expressions something or somethingelse -- depending on how close the expressions are, it's not always clear which one is causing the error (I don't think that came up in your changes, I'm just pointing it out)14:06
jaosorioralright14:07
jaosoriorI'll revert those in some hours (gotta head home now)14:07
dhellmannjaosorior: I don't mind using those for ensuring a valid default, but I would have to look at your patch again to know if there are any cases I would prefer you to remove14:07
jaosoriorcan you point it out as comments on the patch?14:07
dhellmannjaosorior: thanks, I appreciate the work you're doing on this14:07
dhellmannjaosorior: sure, I'll try to get back to it today or tomorrow14:08
*** ildikov has joined #openstack-oslo14:11
*** zzzeek has joined #openstack-oslo14:29
*** dims has joined #openstack-oslo14:36
*** erecio has quit IRC14:48
*** erecio has joined #openstack-oslo14:49
*** erecio has quit IRC14:49
*** ihrachyshka_ has joined #openstack-oslo14:54
*** ihrachyshka_ has quit IRC14:54
*** lbragstad has joined #openstack-oslo14:54
*** ihrachyshka has quit IRC14:57
bnemecArgh: https://bugs.launchpad.net/oslo/+bug/132794615:00
*** mriedem has quit IRC15:07
*** mriedem has joined #openstack-oslo15:11
*** erecio has joined #openstack-oslo15:12
*** arnaud__ has joined #openstack-oslo15:15
*** morganfainberg_Z is now known as morganfainberg15:18
*** arnaud__ has quit IRC15:20
zzzeekdhellmann: what’s the typical process by which we can upgrade SQLAlchemy versions?  by which I mean how much can I refer to SQLAlchemy 0.9 features for oslo.db improvements, as it seems like we’re still on 0.8 (or 0.7?  I see both in the setup )?15:29
dhellmannzzzeek: https://wiki.openstack.org/wiki/Requirements describes, somewhat, the requirements management process15:31
dhellmannbecause of our backwards-compatibility requirements it may take some time to be able to update to a new version15:32
dhellmannknowing what the distros actually ship in their packages would help, too15:32
*** russell_h has quit IRC15:32
*** russell_h has joined #openstack-oslo15:32
zzzeekdhellmann: basically, all of this wrap DB exception stuff at the ORM level / explicilt everywhere makes me sad15:34
dhellmannzzzeek: looking across all projects, I see mostly >=0.7.8,<=0.9.99 -- http://paste.openstack.org/show/83418/15:34
zzzeekdhellmann: and this should be internalized into SQLAlhcemy hooks15:35
dhellmannzzzeek: I'm not sure what you mean15:35
zzzeekfor example https://bugs.launchpad.net/oslo/+bug/121434115:35
dhellmannso there's a way to make sqlalchemy convert exceptions for us?15:35
zzzeekthere are some hooks right now, they would need some improvement to support15:36
dhellmannnice15:36
dhellmannwe might want different exceptions for the same error on different ables -- NoSuchInstance vs. NoSuchNetwork or something like that15:37
dhellmannzzzeek: I suggest you start a wiki page or etherpad or something with notes about these sorts of changes. Some are going to be long-term, and we'll need to enlist people to help with them. Some will be easier, and can be isolated in oslo.db.15:38
openstackgerritBrad Pokorny proposed a change to openstack/oslo-incubator: Mask passwords included without quotes at the ends of commands  https://review.openstack.org/9730515:39
dhellmannzzzeek: eventually the notes can become specs with more details so we can split up the work and you don't end up having to do it all :-)15:40
zzzeekwell there’s really just an assortment of patterns I’d add to oslo.db that I think improve upon what is there, it’s not that much work to put them in oslo.db codewise, the work is getting everything to work in all cases, deal with backwards compat, migration paths etc.15:41
dhellmannright15:42
dhellmannhaving them in oslo.db doesn't ensure adoption, either15:42
zzzeekwell that’s somehting else15:43
dhellmannmaking pattern changes across all of the projects tends to take a lot of education and patience15:43
zzzeekif a project has their own SQLAclhemy code out of nowhere, that’s sort of their own problem15:43
zzzeekbut within oslo.db I’d like to make it such that a projecvt that uses it doesn’t have to make many decisions as far as DB integration, there will be a few well-understood paths for things and that’s it15:44
zzzeekoslo.db is framework code, it needs to show the way for those who are using it15:44
dhellmanntrue, I meant more things like setting up the exception translation where it would be project-specific15:44
zzzeekOK, well there might be multi-levels to that.  at the core level I’d like to have more of an oslo.db specific set of rules that add whatever information is possible.  project-specific rules would then have a hook within oslo.db15:45
zzzeekthat is, only oslo.db deals with the SQLA hooks15:45
dhellmannI like that approach15:46
zzzeekhttps://github.com/openstack/oslo.db is the main repo?   you folks don’t use tags or anything?15:50
* zzzeek reads https://wiki.openstack.org/wiki/BranchModel15:51
zzzeekah http://tarballs.openstack.org/oslo.db/ , we have no tags!15:54
*** mrodden has quit IRC15:54
dhellmannzzzeek: http://git.openstack.org/cgit/openstack/oslo.db and there won't be any tags until we have a release15:58
openstackgerritGordon Sim proposed a change to openstack/oslo-specs: Added spec for proposed AMQP 1.0 driver  https://review.openstack.org/9672916:00
zzzeekdhellmann: dumb question, what is the relationship between git.openstack.org and github.com/openstack?16:03
*** mrodden has joined #openstack-oslo16:07
*** ildikov_ has joined #openstack-oslo16:08
*** yamahata has joined #openstack-oslo16:10
*** ildikov has quit IRC16:10
*** markmcclain has joined #openstack-oslo16:21
*** yamahata has quit IRC16:22
*** yamahata has joined #openstack-oslo16:22
*** praneshp has joined #openstack-oslo16:26
*** yamahata has quit IRC16:35
*** yamahata has joined #openstack-oslo16:35
dhellmannzzzeek: the github repos are mirrors of git.openstack.org16:56
zzzeekok16:56
dhellmannzzzeek: the CI system pushes merges up there, and automatically closes pull requests with instructions for how to submit through gerrit16:56
zzzeekCI pushes … from git.openstack to github ?17:04
zzzeeke.g. an approved changeset on gerrit goes to git.openstack first17:05
*** harlowja_away is now known as harlowja17:09
dhellmannzzzeek: yes, that's right (sorry for the lag, was in a meeting)17:15
*** tkelsey has quit IRC17:15
openstackgerritBen Nemec proposed a change to openstack/oslo-specs: Graduate oslo.serialization  https://review.openstack.org/9731517:22
*** markmcclain has quit IRC17:30
*** markmcclain has joined #openstack-oslo17:33
*** russell_h has quit IRC17:36
*** pafuent has left #openstack-oslo17:37
*** russell_h has joined #openstack-oslo17:39
*** russell_h has quit IRC17:41
*** russell_h has joined #openstack-oslo17:41
*** mkoderer has quit IRC18:02
*** stannie has joined #openstack-oslo18:08
*** stannie has quit IRC18:08
*** mrodden has left #openstack-oslo18:16
*** erecio has quit IRC18:19
*** erecio has joined #openstack-oslo18:19
*** dims has quit IRC18:25
*** dims has joined #openstack-oslo18:25
*** ildikov has joined #openstack-oslo18:27
*** ildikov has quit IRC18:29
*** markmcclain has quit IRC18:30
*** ildikov_ has quit IRC18:30
*** markmcclain has joined #openstack-oslo18:30
*** markmcclain has quit IRC18:31
*** markmcclain has joined #openstack-oslo18:31
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Make intentions a tuple (to denote immutability)  https://review.openstack.org/9885118:39
openstackgerritJuan Antonio Osorio Robles proposed a change to openstack/oslo.i18n: Trivial refactors for gettextutils  https://review.openstack.org/9842918:45
*** ildikov|2 has joined #openstack-oslo18:45
*** ildikov|2 is now known as ildikov18:54
*** markmcclain has quit IRC19:00
*** erecio has quit IRC19:04
*** erecio has joined #openstack-oslo19:04
zzzeekhey dhellmann can I use http://paste.openstack.org/show/83418/ as a guide to all projects that are currently on SQLA?  e.g. to look for patterns used anywhere ?19:05
*** markmcclain has joined #openstack-oslo19:07
*** praneshp has quit IRC19:08
openstackgerritDoug Hellmann proposed a change to openstack/oslotest: Add API documentation  https://review.openstack.org/9886119:15
*** ihrachyshka has joined #openstack-oslo19:15
dhellmannzzzeek: those are just the integrated projects, but it should give you all of those19:16
zzzeekok...19:17
dhellmannzzzeek: here's a thing for cloning all of the git repos: http://lists.openstack.org/pipermail/openstack-dev/2013-October/017532.html19:18
zzzeekah thanks19:18
*** markmcclain1 has joined #openstack-oslo19:19
dhellmannzzzeek: my copy takes about 8 GB, but I may have some extra stuff in there19:19
zzzeekive checked them all out manually19:19
*** markmcclain1 has quit IRC19:20
*** markmcclain1 has joined #openstack-oslo19:20
dhellmannok, that script will give you *ALL* of them, including the attic and stackforge19:20
zzzeekit does19:23
*** markmcclain has quit IRC19:23
zzzeekso I am surprised that these reqs all state 0.7.8 - 0.9.9, that is very wide open ?19:23
dhellmannwe're trying to take into account what the different distros include, I believe19:23
zzzeekI’m trying to find where tests are being run to see what versions are really used, im not seeing quite on jenkins.openstack.org where things are ?19:23
zzzeekI see19:23
dhellmannyou should probably do some digging in the openstack-dev archives; I know there were some discussions about sqlalchemy versions in the last year19:24
dhellmannyeah, tests are weird19:24
dhellmannzuul manages the test jobs, and passes them out to one of several jenkins servers to run19:24
zzzeekso how do I get a sense of that, 0.7.8 is very old, there’s more than a few pretty awful connection pool bugs in early 0.8 versions19:25
dhellmannI believe we're running on precise right now, although we do have some centos servers for python 2.6 I think19:25
zzzeekand here I am looking to things that will work best with new features I want to add in 0.9.519:25
dhellmannyou know, I *believe* we actually install sqla via pip, so we should get the most current version available in our tests19:25
zzzeekyeah19:25
zzzeekim looking at RH and it seems to be 0.8.4 based on the current RPM that redhat 6 has19:26
dhellmannthe folks in #openstack-infra would be able to give you a more definitive answer, but I think the tests use pip but we want to support the distro version of the package19:26
zzzeekOK so then…what distros do we support and when ? :)   sorry am i just leaning on you too hard here19:26
zzzeekthis is a lot to ask19:27
dhellmannnah, this is all good bootstrapping19:27
dhellmannwe support long term releases, so whatever RHEL is at now and the LTS from Canonical (12.04, moving to 14.04 (I think))19:27
dhellmannI'm not sure what the deal is with debian or suse19:28
dhellmanneither ttx or the folks in infra should be able to help you find the people who are our interfaces for the distros19:28
zzzeekshoudlnt this be in the main openstack docs19:29
dhellmannI think we leave it up to the distros to claim whatever *they* support, since we don't actually do the support ourselves19:29
dhellmannand there is probably a release document somewhere that says some of this19:29
zzzeekyeah i am poking around...19:29
zzzeekum well what do you think of the notion of new sqlalhcemy features that oslo.db can use when version > 0.9.X is detected, then fallback to known semi-public API technique for existing versions ?19:30
dhellmannthat seems like a reasonable approach19:30
zzzeekOK, so folks are OK with a little bit of sqla._underscore here and there if I pin it to released versions19:31
*** praneshp has joined #openstack-oslo19:31
dhellmannit also seems like something to make sure we release note, so deployers know their options19:31
zzzeekOK so,  i like this wiki idea19:31
dhellmannI would rather not rely on private APIs19:31
dhellmannbut if we only have it in oslo.db, and it comes with a big warning comment, it might be ok19:32
zzzeekright but the reason we don’t like to do that is beacuse, they are unstable.  my proposal is, we rely on those APIs only for existing, released versions of SQLA - new versions will offer public API that oslo.db will be set up to accommodate at the same time19:32
dhellmannthat makes sense19:32
zzzeekim not sure of the CI environemnt yet but in theory we shoudl ahve oslo.db tested against multiple SQLA versions19:33
zzzeekunsure meaning, I don’t know where I can see CI logs of actual oslo.db test runs...19:33
zzzeekgeuss it’s not these https://jenkins.openstack.org/view/Devstack%20Nodes/search/?q=oslo.db19:34
dhellmannlinks to the logs are saved in gerrit on the patch that triggered the build, so you could look at an existing patch19:34
zzzeekgood idea19:34
dhellmannthere's also the logstash UI, but I don't know if that's public yet19:34
dhellmannthat's really more for looking for patterns across builds anyway19:34
dhellmannhmm, internal issues coming up, I need to step away for a bit19:35
zzzeekok19:35
*** yfujioka has joined #openstack-oslo19:40
*** markmcclain1 has quit IRC19:42
*** yfujioka has quit IRC19:51
openstackgerritBertrand Lallau proposed a change to openstack/oslo-incubator: Improve amqp rpc logging format for debug purpose  https://review.openstack.org/9887319:58
*** jecarey has quit IRC20:05
*** morganfainberg is now known as morganfainberg_Z20:06
*** boris-42 has quit IRC20:08
openstackgerritTomoki Sekiyama proposed a change to openstack/oslo-specs: Add ChainingRegExpFilter into rootwrap  https://review.openstack.org/9853620:11
*** boris-42 has joined #openstack-oslo20:11
*** jecarey has joined #openstack-oslo20:19
*** arnaud__ has joined #openstack-oslo20:30
*** markmcclain has joined #openstack-oslo20:34
bnemeczzzeek: There's a pip-freeze file that gets created for some of the test jobs: http://logs.openstack.org/67/96467/14/check/check-tempest-dsvm-full/310a9b5/logs/pip-freeze.txt.gz20:52
openstackgerritlifeless proposed a change to openstack/oslo-specs: Semantic version support for pbr  https://review.openstack.org/9660820:52
*** morganfainberg_Z is now known as morganfainberg21:10
*** praneshp has quit IRC21:11
*** arnaud__ has quit IRC21:14
*** arnaud__ has joined #openstack-oslo21:26
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Clarify locked decorator is for instance methods  https://review.openstack.org/9869121:27
*** mrda-longweekend is now known as mrda21:30
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Rename additional to general/higher-level  https://review.openstack.org/9861721:31
*** tsekiyama has quit IRC21:32
*** arnaud__ has quit IRC21:37
*** mriedem has quit IRC21:45
*** praneshp has joined #openstack-oslo21:50
*** mestery has joined #openstack-oslo21:57
mesterydhellmann: FYI, we have an approved spec for the oslo.messaging port to neutron, and we've started landed patches to that effect: https://blueprints.launchpad.net/neutron/+spec/oslo-messaging21:58
*** dims_ has joined #openstack-oslo22:00
*** markmcclain has quit IRC22:01
*** dims has quit IRC22:02
*** ihrachyshka has quit IRC22:10
openstackgerritJoshua Harlow proposed a change to openstack/taskflow: Address concurrent mutation of sqlalchemy backend  https://review.openstack.org/9868922:17
*** flaper87 is now known as flaper87|afk22:23
*** krotscheck has joined #openstack-oslo22:25
krotscheckDoes anyone out there have simple ‘getting started’ example code for Oslo.Messaging?22:26
*** zzzeek has quit IRC22:55
*** zzzeek has joined #openstack-oslo23:01
*** morganfainberg is now known as morganfainberg_Z23:25
*** jaosorior has quit IRC23:32
*** morganfainberg_Z is now known as morganfainberg23:42

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