Wednesday, 2015-06-17

openstackgerritJoshua Harlow proposed openstack/tooz: Use `encodeutils.exception_to_unicode` for exception -> string function  https://review.openstack.org/19245200:02
*** crc32 has quit IRC00:02
*** ozialien has quit IRC00:04
*** enikanorov has quit IRC00:10
*** takedakn has joined #openstack-oslo00:11
*** takedakn has quit IRC00:16
*** amrith is now known as _amrith_00:19
*** mtanino has quit IRC00:22
*** sdake has quit IRC00:24
vipul:q00:29
*** sputnik13 has joined #openstack-oslo00:36
openstackgerritTony Breeds proposed openstack/oslo.concurrency: Add 2 callbacks to processutils.execute()  https://review.openstack.org/19047200:40
openstackgerritOpenStack Proposal Bot proposed openstack/oslo-incubator: Updated from global requirements  https://review.openstack.org/19238100:41
*** kgiusti1 has quit IRC00:44
*** sdake has joined #openstack-oslo00:48
*** sputnik13 has quit IRC00:54
*** crc32 has joined #openstack-oslo00:58
*** sdake_ has joined #openstack-oslo00:58
*** sdake has quit IRC01:01
openstackgerritJeremy Stanley proposed openstack-dev/cookiecutter: Ignore .eggs cruft  https://review.openstack.org/19248001:02
*** tobe has joined #openstack-oslo01:05
*** zz_jgrimm is now known as jgrimm01:06
*** jgrimm is now known as zz_jgrimm01:07
*** bknudson has joined #openstack-oslo01:11
openstackgerritJoshua Harlow proposed openstack/taskflow: Use `encodeutils.exception_to_unicode` for exception -> string function  https://review.openstack.org/19245801:19
*** gordc has joined #openstack-oslo01:32
openstackgerritMerged openstack/oslo-specs: service: Adds Windows Oslo Service Workers spec  https://review.openstack.org/19116801:50
openstackgerritMerged openstack/oslo-incubator: Updated from global requirements  https://review.openstack.org/19238101:52
openstackgerritMerged openstack/oslosphinx: Updated from global requirements  https://review.openstack.org/19231601:54
openstackgerritMerged openstack/oslo.cache: Updated from global requirements  https://review.openstack.org/19230301:54
openstackgerritMerged openstack/oslotest: Updated from global requirements  https://review.openstack.org/19231701:55
*** vilobhmm has joined #openstack-oslo02:02
*** dims has quit IRC02:04
*** vilobhmm has quit IRC02:07
*** dims has joined #openstack-oslo02:08
*** dims has quit IRC02:19
openstackgerritMerged openstack/oslo.db: Updated from global requirements  https://review.openstack.org/19230602:35
openstackgerritMerged openstack/oslo.policy: Updated from global requirements  https://review.openstack.org/19231002:36
openstackgerritMerged openstack/oslo.i18n: Updated from global requirements  https://review.openstack.org/19230702:37
openstackgerritMerged openstack/oslo.log: Updated from global requirements  https://review.openstack.org/19230802:40
openstackgerritMerged openstack/oslo.context: Updated from global requirements  https://review.openstack.org/19230502:45
openstackgerritMerged openstack/oslo.middleware: Updated from global requirements  https://review.openstack.org/19230902:45
openstackgerritMerged openstack/oslo.serialization: Updated from global requirements  https://review.openstack.org/19231102:45
openstackgerritMerged openstack/oslo.service: Updated from global requirements  https://review.openstack.org/19231202:45
openstackgerritMerged openstack/oslo.versionedobjects: Updated from global requirements  https://review.openstack.org/19231402:45
openstackgerritMerged openstack/oslo.concurrency: Updated from global requirements  https://review.openstack.org/19230402:47
openstackgerritMerged openstack/oslo.utils: Updated from global requirements  https://review.openstack.org/19231302:50
openstackgerritMerged openstack/oslo.vmware: Updated from global requirements  https://review.openstack.org/19231502:52
*** sdake_ is now known as sdake03:00
*** ViswaV has quit IRC03:36
*** stevemar has quit IRC03:47
*** stevemar has joined #openstack-oslo03:48
*** vilobhmm has joined #openstack-oslo03:53
*** ozialien has joined #openstack-oslo04:03
*** jamespage has quit IRC04:06
*** jamespage has joined #openstack-oslo04:06
*** rushiagr_away is now known as rushiagr04:10
*** rjaiswal has quit IRC04:14
*** amotoki has joined #openstack-oslo04:19
*** achanda has joined #openstack-oslo04:23
*** r0j4z0 has joined #openstack-oslo04:25
*** gordc has quit IRC04:25
*** achanda has quit IRC04:32
*** rpodolyaka1 has joined #openstack-oslo04:54
*** ozialien has quit IRC05:01
*** achanda has joined #openstack-oslo05:02
*** rpodolyaka1 has quit IRC05:07
*** rpodolyaka1 has joined #openstack-oslo05:11
*** stevemar has quit IRC05:14
*** Kennan has quit IRC05:14
*** browne has quit IRC05:16
*** Kennan has joined #openstack-oslo05:20
*** nkrinner has joined #openstack-oslo05:31
*** achanda has quit IRC05:31
openstackgerritJoshua Harlow proposed openstack/taskflow: Use `encodeutils.exception_to_unicode` for exception -> string function  https://review.openstack.org/19245805:31
*** tobe has quit IRC05:39
*** arnaud___ has joined #openstack-oslo05:41
*** rpodolyaka1 has quit IRC05:54
*** rpodolyaka1 has joined #openstack-oslo05:58
*** crc32 has quit IRC06:01
*** browne has joined #openstack-oslo06:03
*** browne has quit IRC06:14
*** rpodolyaka1 has quit IRC06:16
*** exploreshaifali has joined #openstack-oslo06:19
*** tobe has joined #openstack-oslo06:20
*** dulek has joined #openstack-oslo06:22
*** dulek has quit IRC06:25
*** browne has joined #openstack-oslo06:32
*** rjaiswal has joined #openstack-oslo06:33
*** salv-orl_ has joined #openstack-oslo06:41
*** boris-42 has quit IRC06:42
*** rpodolyaka1 has joined #openstack-oslo06:44
*** salv-orlando has quit IRC06:44
*** dulek has joined #openstack-oslo06:49
*** browne has quit IRC06:49
*** arnaud___ has quit IRC06:52
*** vilobhmm has quit IRC06:58
*** r0j4z0 has quit IRC07:05
*** sputnik13 has joined #openstack-oslo07:11
*** sdake has quit IRC07:20
*** haypo has joined #openstack-oslo07:28
*** ihrachyshka has joined #openstack-oslo07:29
*** jamespage_ has joined #openstack-oslo07:37
*** jamespage_ has quit IRC07:40
*** sputnik13 has quit IRC07:48
*** rpodolyaka1 has quit IRC07:51
*** sputnik13 has joined #openstack-oslo07:53
*** sputnik13 has quit IRC07:58
*** jaosorior has joined #openstack-oslo07:58
*** r0j4z0 has joined #openstack-oslo08:06
*** yassine has joined #openstack-oslo08:24
openstackgerritJames Polley proposed openstack-dev/pbr: Fix everything by requiring setuptools>=16.  https://review.openstack.org/18784608:25
*** rpodolyaka1 has joined #openstack-oslo08:32
*** dguitarbite has quit IRC08:38
openstackgerritMerged openstack/oslo.service: Use monotonic.monotonic and stopwatches instead of time.time  https://review.openstack.org/19037208:42
*** mdbooth has quit IRC08:42
*** mdbooth has joined #openstack-oslo08:45
*** cdent has joined #openstack-oslo08:53
*** tobe has quit IRC08:58
*** tobe has joined #openstack-oslo08:59
*** cdent has quit IRC09:00
*** cdent has joined #openstack-oslo09:00
*** tobe_ has joined #openstack-oslo09:01
*** tobe_ has quit IRC09:01
*** tobe has quit IRC09:03
*** ozamiatin has joined #openstack-oslo09:09
openstackgerritMerged openstack/oslo.concurrency: Add 2 callbacks to processutils.execute()  https://review.openstack.org/19047209:13
*** ndipanov has joined #openstack-oslo09:21
*** rpodolyaka1 has quit IRC09:23
*** tobe has joined #openstack-oslo09:23
*** rjaiswal has quit IRC09:24
*** rpodolyaka1 has joined #openstack-oslo09:25
*** e0ne has joined #openstack-oslo09:36
openstackgerritMerged openstack/tooz: Use `encodeutils.exception_to_unicode` for exception -> string function  https://review.openstack.org/19245209:37
openstackgerritMerged openstack/tooz: Use the `excutils.raise_with_cause` after doing our type check  https://review.openstack.org/19245009:37
openstackgerritMerged openstack/tooz: Use the 'driver_lock' around read operations  https://review.openstack.org/19235709:37
*** e0ne is now known as e0ne_09:43
*** e0ne_ is now known as e0ne09:47
*** ozamiatin has quit IRC09:49
*** arnaud___ has joined #openstack-oslo09:53
*** arnaud___ has quit IRC09:57
*** dguitarbite has joined #openstack-oslo10:06
*** davidlenwell has quit IRC10:12
*** davidlenwell has joined #openstack-oslo10:12
*** ozamiatin has joined #openstack-oslo10:14
*** dims has joined #openstack-oslo10:17
*** tobe has quit IRC10:17
*** dims has quit IRC10:17
*** dims has joined #openstack-oslo10:18
*** ativelkov has joined #openstack-oslo10:18
*** rpodolyaka1 has quit IRC10:19
ativelkovHi folks, may anybody answer a couple of questions on oslo.versioned_objects?10:19
*** rpodolyaka1 has joined #openstack-oslo10:30
*** claudiub has joined #openstack-oslo10:31
*** rpodolyaka1 has quit IRC10:36
*** e0ne is now known as e0ne_10:49
*** e0ne_ has quit IRC10:54
*** e0ne has joined #openstack-oslo10:56
eezhovadims, ping11:04
dimshi eezhova11:05
openstackgerritMehdi Abaakouk (sileht) proposed openstack/oslo.messaging: Ensure consumer app don't use wait before stop  https://review.openstack.org/19243711:05
eezhovadims, can we try to make a release now?11:05
dimsativelkov: dansmith is not here yet. you can ask the question anyway and he'll respond when he gets in (west coast time)11:05
dimseezhova: i'd like to get the other 4 reviews in11:05
dimsjd__: flaper87: can you please take a look at the 4 oslo.service reviews when you get a chance? https://review.openstack.org/#/q/status:open+project:openstack/oslo.service+branch:master,n,z11:06
ativelkovthanks dims11:06
dimssileht: dhellmann ^^11:06
dimsif you are around, please do as well, so we can try to get a test oslo.service release out11:06
silehtdims, I take a look11:07
eezhovadims, what has to be done to make a release? does the section "Tagging a Release" from https://wiki.openstack.org/wiki/Oslo/CreatingANewLibrary#Prepare_an_Initial_Release describe all steps?11:09
ativelkovdansmith: I'm looking at versioned_objects and it seems like CompoundFields do not coerce the values of their elements when the values are modified either by index access or by some method. I.e. the following is possible: http://paste.openstack.org/show/298141/11:12
ativelkovSo, the question is if this is intentional or not. If not, I may file a bug and submit a patch to fix this11:14
*** rushiagr is now known as rushiagr_away11:24
dimsativelkov: i'd file a bug for this one11:29
*** e0ne is now known as e0ne_11:29
ativelkovdims, ok, I will11:30
ativelkovAnother one (similar, but a bit different): if a compound field is "readonly", should we allow to modify the contents of the collection (e.g. pop elements from list or replace the, by index)?11:30
toabctlpypi says hacking 's latest version is 0.9.6 but seems that it's 0.10.2 ...11:34
*** e0ne_ has quit IRC11:34
*** sdake has joined #openstack-oslo11:41
*** prad has quit IRC11:42
*** rpodolyaka1 has joined #openstack-oslo11:44
*** ganso_ has joined #openstack-oslo11:45
*** rpodolyaka1 has quit IRC11:46
openstackgerritMehdi Abaakouk (sileht) proposed openstack/oslo.messaging: Ensure consumer app don't use wait before stop  https://review.openstack.org/19243711:48
*** rpodolyaka1 has joined #openstack-oslo11:48
openstackgerritMehdi Abaakouk (sileht) proposed openstack/oslo.messaging: Ensures that some assumptions are true.  https://review.openstack.org/19243711:50
silehtdhellmann, dims what do you think of https://review.openstack.org/192437 to ensure people don't run in some pitfalls (like Ritz hits yesterday)11:52
openstackgerritIlya Shakhat proposed openstack/oslo.config: Fix sorting of optional arguments  https://review.openstack.org/19263011:53
*** dulek_ has joined #openstack-oslo11:57
*** dulek has quit IRC12:01
*** kgiusti has joined #openstack-oslo12:04
dimssileht: thanks!12:04
dimssileht: LOOKING12:04
*** sdake has quit IRC12:04
dimsoops! capslock12:04
dimssorry12:04
dimseezhova: watch the zuul page for the 4 oslo.service changes to merge - http://status.openstack.org/zuul/ - we can cut a release when those lang12:05
eezhovadims, okay, but according to zuul it seems there will be a merge conflict for https://review.openstack.org/#/c/190175/12:07
dimseezhova: y, we can wait to see what merges and then run recheck or rebase12:07
eezhovadims, ack, I checked, it's gonna be a trivial conflict12:10
dimseezhova: k, rebase it and i'll fast approve it12:10
dims(please! :)12:10
*** rushiagr_away is now known as rushiagr12:11
*** jlvillal has quit IRC12:11
dimssileht: i see some changes in tests from blocking to eventlet..do we lose some test coverage because of that?12:12
silehtdims, the test itself is to test the dispatcher code so we can use any executor12:13
silehtdims, I have used the eventlet one, because blocking is the only executor that block on stop12:14
silehts/on stop/on start12:14
*** r0j4z0 has quit IRC12:19
*** e0ne has joined #openstack-oslo12:19
eezhovadims, I can't rebase it now because it will involve rebasing a change it depends on and that one is already in a check queue and has no conflicts. Me or Marian can rebase when that one merges12:20
dimsack thanks12:20
*** jlvillal has joined #openstack-oslo12:23
*** exploreshaifali has quit IRC12:27
sdaguedims: just kicking this in - https://review.openstack.org/#/c/189118/1212:33
*** dulek_ is now known as dulek12:34
*** dims has quit IRC12:36
*** dims has joined #openstack-oslo12:36
dimssdague: nice thanx sean12:37
sdaguewe just needed the g-r sync so we didn't break any CD folks, but kevin landed that last night12:37
dimsyes, i was tracking that12:38
*** dulek has quit IRC12:39
*** dulek has joined #openstack-oslo12:40
*** bknudson has quit IRC12:41
dimsdhellmann: around?12:43
dimsdhellmann: so fungi mentioned that gerrit admins can create a feature branch from external repo provided they shared the same commit in their history. i checked the ACL(s) of oslo.messaging and oslo.cache. since they looked similar i am guessing you may have karma to pull this off? please let me know. i have a git repo with the keystone stuff pulled in on top of oslo.cache ready to go12:45
*** kgiusti has left #openstack-oslo12:45
*** exploreshaifali has joined #openstack-oslo12:46
*** e0ne is now known as e0ne_12:55
*** e0ne_ is now known as e0ne12:57
openstackgerritMerged openstack/oslo.service: Add documentation for the service module  https://review.openstack.org/19176813:01
*** bknudson has joined #openstack-oslo13:08
*** jamielennox is now known as jamielennox|away13:13
*** jecarey has joined #openstack-oslo13:13
*** amotoki_ has joined #openstack-oslo13:14
*** bknudson has quit IRC13:14
*** ozamiatin has quit IRC13:16
*** jamielennox|away is now known as jamielennox13:21
*** stpierre has joined #openstack-oslo13:26
*** rpodolyaka1 has quit IRC13:26
*** bknudson has joined #openstack-oslo13:27
*** stevemar has joined #openstack-oslo13:30
*** jamielennox is now known as jamielennox|away13:33
dansmithativelkov: yep13:35
ativelkovdansmith: I've submitted https://bugs.launchpad.net/oslo.versionedobjects/+bug/146605713:36
openstackLaunchpad bug 1466057 in oslo.versionedobjects "Compound fields do not coerce values of their elements when modified" [Undecided,New]13:36
dansmithativelkov: do you have a fix?13:37
ativelkovworking on it right now13:37
dansmithokay13:37
ativelkovwhat about readonly attribute?13:37
ativelkovAnother one (similar, but a bit different): if a compound field is "readonly", should we allow to modify the contents of the collection (e.g. pop elements from list or replace the, by index)?13:38
*** rpodolyaka1 has joined #openstack-oslo13:39
dansmithif you have an easy way to prevent it then sure, but I've never seen a readonly list attribute in practice :)13:39
*** prad has joined #openstack-oslo13:40
ativelkovwe have them in Glance Artifacts13:41
dansmithokay13:42
*** jamielennox|away is now known as jamielennox13:42
*** mriedem_away is now known as mriedem13:42
*** kbyrne has quit IRC13:46
openstackgerritMerged openstack/oslo.service: Eventlet service fixed  https://review.openstack.org/19223913:50
* dhellmann notes a long backlog13:51
dhellmannsileht: I like the general idea of enforcing those constraints; I'll put that in my review queue13:52
dhellmanndims: I see some jenkins -1 on those service patches, are those just the merge conflicts?13:52
*** sigmavirus24_awa is now known as sigmavirus2413:58
dimsdhellmann: right.14:05
dhellmannok14:05
dimseezhova: 2 of the reviews need rebases14:06
dimsdhellmann: so fungi mentioned that gerrit admins can create a feature branch from external repo provided they shared the same commit in their history. i checked the ACL(s) of oslo.messaging and oslo.cache. since they looked similar i am guessing you may have karma to pull this off? please let me know. i have a git repo with the keystone stuff pulled in on top of oslo.cache ready to go14:06
dimsdhellmann: https://github.com/dims/oslo.cache14:07
fungichances are we'll need to update the acl to allow pushing a merge commit for review14:10
*** kbyrne has joined #openstack-oslo14:15
dhellmanndims: I'm going to need to spend some time figuring out how to do that14:15
*** zzzeek has joined #openstack-oslo14:15
dhellmanndims : I think I'm not a gerrit admin, so we probably need fungi or someone else from infra to assist14:16
fungiyeah, i can take care of the particulars, but be forewarned whatever gets pushed up is going to have to pass the currently configured jobs before it will be able to merge14:17
dhellmannfungi: wouldn't we just do "git merge" and then "git review" locally? or are merge commits different somehow in gerrit?14:17
dhellmannfungi: yep, we wouldn't want it any other way14:18
dhellmanndims: does the api for that code need to go through the incubator process?14:18
fungiright, i'd create a feature branch by pushing dims's custom fork into gerrit, then one of us (easiest if it's me since i'll already have my privs elevated for the branch push) will propose a merge commit of that feature branch to master for review, and that will get tests run on it14:20
dimsfungi: yes, will work on it in the feature branch and finally merge when ready for jobs14:20
dhellmannfungi: it appears that dims' branch places the new files in a directory that isn't in the test path, so we'll end up testing things as we move the code into the right place to be picked up for packaging14:20
fungithough if the feature branch is going to need a while to bake in gerrit before merging to master, then we'll want to update the acl to allow one of you to propose a merge commit once you're ready14:20
dimsdhellmann: that was the bare minimum import from keystone14:20
dhellmanndims: right, and I think that's a reasonable approach -- that lets us merge now, and then shuffle things around as normal commits14:21
dimscool14:21
dhellmannOTOH, do we need to do this in the incubator instead of oslo.cache?14:21
dimsdhellmann: any advantages?14:22
dhellmanndims: if we expect lots of changes to the api, it's easier to test them in keystone if we're syncing code from the incubator14:22
dhellmannthat ensures no backwards compatibility issues for keystone, without a lot of unstable releases of the lib14:23
*** nkrinner has quit IRC14:23
dimsdhellmann: i think i have a way to do that dhellmann once we get past jobs into the master14:23
dhellmannok14:23
dimsdhellmann: we are testing oslo.service against nova, neutron, cinder for example14:23
*** exploreshaifali has quit IRC14:24
dhellmanndims: ok, if you have a way to do it that isn't too painful14:24
dimsyes, we should not release the library until we know keystone would work14:24
dimsy, should be ok14:24
*** mdbooth has quit IRC14:27
*** ozamiatin has joined #openstack-oslo14:27
dimsfungi: thanks. is there another project that has the acl for merge commit i can copy from?14:28
fungidims: swift, keystone...14:28
dimsfungi: ack looking14:29
* stevemar starts reading14:30
*** zz_jgrimm is now known as jgrimm14:30
stevemardims, which library should you not release until you know keystone would work?14:31
dimsstevemar: oslo.cache14:31
stevemaris it available as a 0.1 now?14:32
dimsstevemar: we are just getting the ball rolling with the initial import14:32
stevemari'm happily push a patch for keystone that is trying to use oslo.cache 0.114:33
stevemari'll*14:33
stevemari guess i could do it from an external git repo too14:34
dimsstevemar: thanks!14:39
*** kgiusti has joined #openstack-oslo14:43
*** exploreshaifali has joined #openstack-oslo14:48
*** sdake_ has joined #openstack-oslo14:53
*** dulek has quit IRC14:53
*** Kevin_Bishop has joined #openstack-oslo14:54
*** browne has joined #openstack-oslo15:01
openstackgerritMarian Horban proposed openstack/oslo.service: Graceful shutdown WSGI/RPC server  https://review.openstack.org/19017515:03
*** openstackgerrit has quit IRC15:05
*** openstackgerrit has joined #openstack-oslo15:05
*** amotoki_ has quit IRC15:06
*** amotoki_ has joined #openstack-oslo15:08
*** rpodolyaka1 has quit IRC15:08
Kevin_BishopHello, could someone give me an approximate timeline for the oslo_service development? Thanks.15:12
*** haypo has left #openstack-oslo15:12
dhellmannKevin_Bishop: we're working on it this cycle; are you waiting to be able to use it?15:13
Kevin_Bishopdhellmann, yeah we're trying to switch over some of our incubator code.15:14
dhellmannKevin_Bishop: ok, dims probably has a better handle on dates, but the goal is to have a new lib this cycle15:15
dhellmannKevin_Bishop: you're already using the incubated version?15:15
Kevin_Bishopdhellmann: that's great! Is there's anything we can do to help out?15:16
dhellmannKevin_Bishop: I'll have to defer to dims on that, but I'm sure they would appreciate help developing/testing the adoption docs since there are those API changes15:16
dimsKevin_Bishop: which project?15:18
Kevin_Bishopdhellmann: Great. Yes, we are currently using the incubated version. We've been trying to move most of our incubated code to graduated modules.15:18
Kevin_BishopBarbican15:18
*** mtanino has joined #openstack-oslo15:18
dhellmannKevin_Bishop: that's good news, I'm really glad to hear it. The service stuff is pretty close.15:19
dimsKevin_Bishop: we are running some initial code against nova, neutron. we may have a pre-alpha/test release in a week or so.15:19
dimsonce we get it stable and we are happy with the API, we'll propose a global requirements change15:20
Kevin_Bishopdhellmann, dims: That's great to hear!15:20
dimsKevin_Bishop: redrobot is your liaison per https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo - so if one of you are in the oslo meetings, you can follow along15:22
dimswe'd love for you to try the initial releases and give us feedback if you are ok that we may break stuff15:23
Kevin_Bishopdims: Yeah, I'll be sure to let him know.15:23
dimsKevin_Bishop: thank you sir15:26
*** yamahata has joined #openstack-oslo15:31
*** yamahata has quit IRC15:32
*** yamahata has joined #openstack-oslo15:32
*** ozamiatin has quit IRC15:35
*** jamielennox is now known as jamielennox|away15:38
*** harlowja_at_home has joined #openstack-oslo15:42
ativelkovdansmith: I've found another one which looks like a bug to me: https://bugs.launchpad.net/oslo.versionedobjects/+bug/146614115:44
openstackLaunchpad bug 1466141 in oslo.versionedobjects "Type inheritance is ignored when coercing object fields" [Undecided,New]15:44
dansmithativelkov: well, the existing behavior is what we intended15:45
dansmithativelkov: but if you want to allow inheritance, we probably need a different field, or a flag15:45
*** viktors is now known as viktors|afk15:45
ativelkovah, I see15:45
dansmithativelkov: the point of that field is sort of an interface definition... like "an object that implements the FixedIP model is placed here"15:46
dansmithwhich we wanted so that we could have alternate implementations of a given object15:46
ativelkovI actually found it in one of the tests which began to fail as soon as I fixed compound coercing15:46
dansmithwe could have done it with inheritance, but we look them up via name in the registry15:46
dansmithokay15:46
openstackgerritJoshua Harlow proposed openstack/taskflow: Use `encodeutils.exception_to_unicode` for exception -> string function  https://review.openstack.org/19245815:47
*** jamielennox|away is now known as jamielennox15:47
dansmithativelkov: I think maybe a different field that takes a class instead of a name would be good,15:47
dansmithand then we can make sure that what they provide has the defined class in its mro ancestry15:48
ativelkovhttps://github.com/openstack/oslo.versionedobjects/blob/master/oslo_versionedobjects/tests/test_objects.py#L285 - this fails, as MyList (which is actually ab ObjectListBase) expects its items to be VersionedObject, but in this tests they are MyObj - nad they always will be some subclass of VersionedObject15:49
dansmithativelkov: yeah, just an oversight I think.. good catch, glad you caught that :D15:50
*** ashleighfarnham has joined #openstack-oslo15:50
*** stevemar has quit IRC15:50
ativelkovClasses are bad in this case, as you won't be able to define a class which reference themselves15:50
ativelkove.g. http://paste.openstack.org/show/298801/ is impossible to interpret15:51
dansmithreally?15:52
*** stevemar has joined #openstack-oslo15:52
dansmithI guess because it's run at parse time15:52
ativelkovyup15:52
dansmithobject path/15:52
dansmith?15:52
dansmithnova.objects.Baz ?15:52
*** jecarey has quit IRC15:53
*** exploreshaifali has quit IRC15:53
ativelkovchecking..15:54
ativelkovNo, seems like you cannot reference it - you'll have to import nova.objects from within nova.objects, which is obviously impossible15:57
dansmithativelkov: no, I meant pass it a string15:57
dansmithativelkov: and look up the ancestor class during coerce15:57
*** jamielennox is now known as jamielennox|away15:58
ativelkovah, got it15:58
*** tsekiyama has joined #openstack-oslo15:58
*** rpodolyaka1 has joined #openstack-oslo15:58
ativelkovso, may be use the same obj_name instead, but - if some field (say, 'include_ancestors') is present - check obj_names of the bases as well?15:59
dansmithwell, the problem with that is that we may have two objects with the same "name" that don't inherit from a common base15:59
*** haypo has joined #openstack-oslo16:00
ativelkov'cause I like the concept of obj_name which allows to override the pythonic name, and it would be great to utilize it for inheritance lookups as well16:00
dansmithhow about we just imply that the thing has to be a descendant of the name, if the name includes dots and is interpreted as a common ancestor class?16:00
dansmithand if no dots, we just match the obj_name() ?16:01
ativelkovprobably I don't understand something16:01
dansmithhang on16:02
ativelkovSo, in current implementation you may assign a field with any object which have the specified name, regardless of its inheritance hierarchy, right?16:03
*** exploreshaifali has joined #openstack-oslo16:03
dansmithativelkov: https://github.com/openstack/nova/blob/master/nova/tests/unit/objects/test_objects.py#L125-13616:04
dansmithwe intentionally make that compatible with MyObj, but not sharing a common ancestor16:04
ativelkovI got it, yes16:05
openstackgerritJoshua Harlow proposed openstack/tooz: Delay interpolating the LOG string  https://review.openstack.org/19274916:05
*** jamielennox|away is now known as jamielennox16:06
*** arnaud___ has joined #openstack-oslo16:06
*** vilobhmm has joined #openstack-oslo16:06
dhellmannkgiusti, dims, sileht : I'm getting an error installing qpid because it can't find uuid/uuid.h -- do you know what ubuntu package I need for that?16:07
ativelkovBut still, if you create a class which inherits from this MyObj2 and make an instance of it, it should be coercible to MyObj in the same way - even if it has some different obj_name16:07
dhellmannthat's actually in the oslo.messaging unit tests16:07
*** ihrachyshka has quit IRC16:07
*** rpodolyaka1 has quit IRC16:08
dimsdansmith:  uuid-dev and swig was mentioned in https://review.openstack.org/#/c/191107/16:09
dhellmanndims: thanks16:09
*** rpodolyaka1 has joined #openstack-oslo16:09
dansmithativelkov: well, I dunno16:10
* dansmith thinks16:10
*** ozamiatin has joined #openstack-oslo16:10
*** dims_ has joined #openstack-oslo16:11
dansmithativelkov: so you're thinking that coercion would take the thing you have, check its MRO and just make sure that something in the chain has an obj_name() equal to the one set on the field?16:11
ativelkovdansmith: yes, at least optionally if there is appropriate flaf16:11
dansmithativelkov: yeah, okay, I think that will be okay.. it's not how I've been thinking about it so it takes me a minute to wrap my head around it16:12
dansmithativelkov: but I think that'll be okay, especially if it's a flag16:12
ativelkovotherwise I don't know what to do with ObjectListBase - it's going to store its "objects" as a List of VersionedObject16:12
*** achanda has joined #openstack-oslo16:12
dansmithativelkov: we define each of our lists specifically16:12
ativelkovwhich is an abstract class anyway16:12
ativelkovah, I see.16:12
dansmithativelkov: so we use that as the base, but we redefine the objects field as "a list of $these"16:13
dansmithbut, we probably have a case coming up where allowing that to be more generic will be helpful actually16:13
*** dims has quit IRC16:13
*** jecarey has joined #openstack-oslo16:13
ativelkovgot it16:13
ativelkovYes, in Artifacts we'll need generic Artifact references which may get some specific artifact as its value16:14
dansmithyeah16:14
ativelkovSo, I'll add a flag for that16:14
*** ashleighfarnham has quit IRC16:18
*** ashleighfarnham has joined #openstack-oslo16:18
dansmithcool, sounds good16:18
openstackgerritJoshua Harlow proposed openstack/tooz: Remove file-driver special no-async abilities  https://review.openstack.org/19275816:21
*** achanda_ has joined #openstack-oslo16:21
*** harlowja_at_home has quit IRC16:22
silehtdhellmann, uuid-dev16:23
silehtdhellmann,and swig is needed too16:23
silehthum I'm late16:24
*** achanda has quit IRC16:24
*** sdake_ is now known as sdake16:25
kgiustisileht: dhellmann: yes - on ubuntu it's uuid-dev, fedora/rhel is libuuid-devel.  swig should be the same on both.16:27
kgiustisileht: dhellmann: flaper87 has submitted a patch to proton that will remove these requirements, but we won't see that until its next release16:28
*** vilobhmm has quit IRC16:28
*** achanda_ has quit IRC16:31
*** openstackgerrit has quit IRC16:33
*** openstackgerrit has joined #openstack-oslo16:34
*** jamielennox is now known as jamielennox|away16:35
*** arnaud___ has quit IRC16:38
*** ozamiatin has quit IRC16:40
*** cdent_ has joined #openstack-oslo16:43
*** mtanino has quit IRC16:45
*** cdent has quit IRC16:45
*** cdent_ is now known as cdent16:45
*** mtanino has joined #openstack-oslo16:49
*** jamielennox|away is now known as jamielennox16:49
*** timsim has left #openstack-oslo16:51
*** alexpilotti has joined #openstack-oslo16:51
*** exploreshaifali has quit IRC16:52
*** yamahata has quit IRC16:54
*** yamahata has joined #openstack-oslo16:55
*** achanda has joined #openstack-oslo16:57
*** _amrith_ is now known as amrith16:58
*** vilobhmm has joined #openstack-oslo16:58
*** haypo has quit IRC16:59
*** e0ne has quit IRC17:00
dhellmannkgiusti, sileht : thanks, it's working again17:01
*** achanda has quit IRC17:02
*** exploreshaifali has joined #openstack-oslo17:03
*** rushiagr is now known as rushiagr_away17:04
openstackgerritDavanum Srinivas (dims) proposed openstack/oslo.service: Test for instantaneous shutdown fixed  https://review.openstack.org/19242717:04
openstackgerritMerged openstack/oslo.service: Graceful shutdown WSGI/RPC server  https://review.openstack.org/19017517:05
*** achanda has joined #openstack-oslo17:05
*** yamahata has quit IRC17:08
*** achanda has quit IRC17:11
*** ndipanov has quit IRC17:12
*** jamielennox is now known as jamielennox|away17:13
*** rpodolyaka1 has quit IRC17:14
*** dims_ has quit IRC17:16
*** rpodolyaka1 has joined #openstack-oslo17:16
*** dims has joined #openstack-oslo17:17
*** achanda has joined #openstack-oslo17:18
*** achanda_ has joined #openstack-oslo17:22
*** ViswaV has joined #openstack-oslo17:24
*** achanda has quit IRC17:25
*** ViswaV has quit IRC17:28
*** ViswaV has joined #openstack-oslo17:29
*** sdake_ has joined #openstack-oslo17:30
*** achanda_ has quit IRC17:33
*** sdake has quit IRC17:34
*** rpodolyaka1 has quit IRC17:34
*** rpodolyaka1 has joined #openstack-oslo17:37
*** yassine has quit IRC17:39
*** rpodolyaka1 has quit IRC17:41
*** amotoki_ has quit IRC17:43
openstackgerritJoshua Harlow proposed openstack/taskflow: Use `encodeutils.exception_to_unicode` for exception -> string function  https://review.openstack.org/19245817:49
*** e0ne has joined #openstack-oslo17:51
*** achanda has joined #openstack-oslo17:54
*** sdake has joined #openstack-oslo17:58
ativelkovdansmith: there is one more issue with obj_name() and inheritance18:00
*** browne has quit IRC18:01
*** sdake_ has quit IRC18:01
dansmithativelkov: okay18:03
ativelkovimagine there is a 'Base' class which overrides its obj_name to some value. What will happen to all its descendant "Derived"? It will have to override its obj_name's back, or it will be considered to be "Base" as well (i.e. there will be no way to create a field which coerces to  "Derived")18:03
*** browne has joined #openstack-oslo18:03
dansmithativelkov: well, that's kinda what I didn't do this in the first place, because if you change your obj_name() then you're "different"18:05
ativelkovyup18:05
ativelkovin Artifacts we do it slightly different18:06
ativelkovwe do not inherit this name at all18:06
ativelkovit is always set to classname if it is not explicitly overridden at that particular class18:06
ativelkovSay, if "Base" overrides its name to "MyBase", then its descendant Derived will still be "Derived" unless explicitly renamed to something else18:08
ativelkovthe renames are not inherited (yet the inheritance chain may be traced, so "Derived" may be used where "MyBase" is required)18:09
*** sdake_ has joined #openstack-oslo18:10
*** sdake has quit IRC18:14
ativelkovI'll try to think about it a bit more and come up with some solution.18:14
*** achanda has quit IRC18:17
krotscheckI'm pondering making a change to oslo config. The automatic configuration detection that I'm doing in the cors middleware requires a call to list_all_sections, which basically means that I can't really support duck typing. My question is: Is it feasible to make the config iteration work for non-registered groups, too? (and/or should we?)18:20
*** cdent has quit IRC18:21
krotscheckRelevant code:18:21
krotscheckhttps://review.openstack.org/#/c/191238/2/oslo_middleware/cors.py18:22
krotscheckAlso, dhellmann - I modified that patch as you requested. https://review.openstack.org/#/c/190753/318:22
dhellmannkrotscheck: you're already calling methods of the configopts class, why do you want to check the type?18:23
krotscheckdhellmann: Usability, mostly.18:23
krotscheckdhellmann: I know that as an engineer, I always appreciate having a sane error message.18:23
dhellmannkrotscheck: we don't really do that anywhere else, though, do we?18:24
krotscheckdhellmann: ... I don't really accept "We don't do it anywhere else" as a reason not to improve usability, even in a small way.18:26
*** isq_ has quit IRC18:27
dhellmannkrotscheck: python programmers do not do type checks, though, it's just not something we do18:27
lifelessdhellmann: https://review.openstack.org/#/c/192019/ and https://review.openstack.org/#/c/192024/ are both shallow and green if you have a few minutes18:28
lifelessdhellmann: the one above them requires integration work in other repos that I'm working through now18:28
krotscheckdhellmann: Didn't you just ask me to implement a type check to support backwards compatibility in https://review.openstack.org/#/c/190753/3 ?18:29
dhellmannlifeless: I've put them in my queue, but I'm monitoring release tags this afternoon so it may be a little while18:29
dhellmannkrotscheck: I suggested 2 ways to solve that. Create a different base class, or look at what you're calling to see if it expects all of the arguments. That's not the same thing as saying "this argument must subclass from a specific class"18:29
lifelessdhellmann: ack18:29
krotscheckdhellmann: Fair point.18:30
lifelessdhellmann: opinion solicited: do we want our setup.py's to be executable ?18:31
krotscheckdhellmann: Actually, no. Just because one of the things you suggested is different, it doesn't negate the fact that the other one - inspecting a callable - is basically type checking. But then, it's all semantics.18:31
dhellmannlifeless: I don't usually expect them to be. Does it matter?18:31
lifelessdhellmann: or do we not care, since we're not ever telling people to just run them (its always in the context of pip, or a venv, where 'python setup.py' is the go)18:31
lifelessdhellmann: one of the side effects of moving from in-place file rewrites to atomic ones is that projects with +x on their setup.py are losing them in the next requirements sync18:32
krotscheck(Note: I don't really have an argument about removing the type checking)18:32
*** mriedem has quit IRC18:32
dhellmannkrotscheck: I'm proposing a way to enforce an API, not look at the type. Someone could subclass ConfigOpts and override a method in a way that would not work with your code.18:32
lifelessdhellmann: I think a strong case can be made for consistency; and then its much more ambiguous about whether we want them to be +x or -x18:32
krotscheckOr a disagreement for that matter.18:32
dhellmannlifeless: I think -x18:33
dimslifeless: default "-x"18:33
lifelessdims: since its a sync job, its not really a 'default' thing - its going to be 'the thing'18:33
krotscheckdhellmann: Subclass Configopts? That's crazytalk!18:33
krotscheckWho would EVER do that.18:33
* krotscheck is pointedly not pointing at himself.18:33
lifelessI'll raise it on the dev list as the way we want it and see if there are screams18:33
dimslifeless: ++18:33
openstackgerritJon Grimm proposed openstack/oslotest: Allow ``OS_DEBUG`` environment variable to specify log level.  https://review.openstack.org/19205518:34
openstackgerritMichael Krotscheck proposed openstack/oslo.middleware: Support PasteDeploy  https://review.openstack.org/19123818:34
dhellmannkrotscheck: yeah, I don't feel that strongly about that one line of code, but as a general rule I don't bother with type checking because it doesn't actually enforce an API and it makes passing fakes into the thing for testing harder.18:34
*** ozamiatin has joined #openstack-oslo18:36
openstackgerritJon Grimm proposed openstack/oslotest: Allow ``OS_DEBUG`` environment variable to specify log level.  https://review.openstack.org/19205518:36
openstackgerritJon Grimm proposed openstack/oslotest: Allow ``OS_DEBUG`` environment variable to specify log level.  https://review.openstack.org/19205518:43
*** rpodolyaka1 has joined #openstack-oslo18:50
*** mriedem has joined #openstack-oslo18:54
openstackgerritMerged openstack/oslo.service: Test for instantaneous shutdown fixed  https://review.openstack.org/19242718:59
*** amrith is now known as _amrith_19:01
sdagueso... I noticed in looking at fungi's patch - https://review.openstack.org/#/c/184387/ and looking at the test results closely, that the oslo.db test code for opportunitistic db testing doesn't work if the url is mysql+pymysql19:03
sdagueanyone addressing that on the oslo.db side?19:03
fungizzzeek: ^ you had figured out the test fixes on that (thanks again, btw!)19:04
zzzeekfungi: np19:04
*** ozamiatin has quit IRC19:05
sdaguezzzeek: cool, how far away from release are those fixes?19:05
*** jaosorior has quit IRC19:05
fungii'm also looking now to see if i can suss out how that opportunistic detection works19:06
sdaguebecause we definitely need them before landing https://review.openstack.org/#/c/184387/19:06
fungibut i'm pretty new to that codebase, so more seasoned eyes are welcome19:06
zzzeeksdague: in…oslo.db ?   um.  looks like the patch is still bouncing around https://review.openstack.org/#/c/184392/19:07
fungii wonder if we need a depends-on in 184387 (and similar) to 18439219:09
fungioh! though i bet we need more than just landing 18439219:09
fungiwe probably also need to tag a new oslo.db release with that?19:10
sdaguefungi: yeh, we'll need a new release19:10
fungidims: dhellmann: might make sense to up the priority on 184392 since we need it landed _and_ released before we can sanely move forward on pymysql for a lot of the leaf projects (at least the ones using oslo.db opportunistic database detection in their tests)19:12
openstackgerritGreg Hellings proposed openstack-dev/pbr: Add support for local versioning schemes  https://review.openstack.org/19284219:14
*** openstackgerrit has quit IRC19:16
*** openstackgerrit has joined #openstack-oslo19:16
dhellmannfungi: looks like it needs a rebase?19:18
dimsdhellmann: when you get a chance, we can cut a test version of oslo.service now from HEAD now, all the changes are in.19:21
dhellmanndims: 0.1.0?19:22
dimsdhellmann: sure19:23
dimsthanks!19:23
dhellmanndims: done19:24
*** jungleboyj has joined #openstack-oslo19:24
dhellmanndims: as a note, the release notes script doesn't work quite right for the first release, so you have to edit the output before sending the announcement.19:25
*** jungleboyj has quit IRC19:32
*** arnaud___ has joined #openstack-oslo19:39
*** ViswaV has quit IRC19:41
*** arnaud___ has quit IRC19:43
*** nkrinner has joined #openstack-oslo19:46
*** jungleboyj has joined #openstack-oslo19:50
*** rpodolyaka1 has quit IRC19:51
fungidhellmann: oh, probably. it was fine a few days ago but i will admit to having not had time to check back in on it19:52
*** ozamiatin has joined #openstack-oslo19:53
jungleboyjdims: I am here now.  Sorry my connection timed out.19:54
jungleboyjI have jecarey lurking to help as he was going to look at fixing this.19:54
jecareyjungleboyj, there is a patch to oslo-incubator already: https://review.openstack.org/#/c/186533/19:55
jungleboyjSo, the issue is that we want to get the fix for this problem into stable/kilo as it is kidn-of a bad thing:19:55
jungleboyjjecarey: Oh,19:55
jecareydims you -1'd it ... should we just skip it and make the change directly to stable/kilo if cinder needs it?19:56
jecareydhellmann, ^^19:56
jungleboyjjecarey: That is good.  So, we need to convince dims we need it.  :-)19:56
dhellmannjungleboyj, jecarey, dims : it should be ok to backport fixes to supported stable branches, even in the incubator19:56
*** exploreshaifali has quit IRC19:57
*** Rockyg has joined #openstack-oslo19:57
dhellmannjungleboyj, jecarey, dims: if the code is being removed from the master incubator, we could skip that step and go straight to the stable branch19:57
*** Rockyg has quit IRC19:57
*** _amrith_ is now known as amrith19:57
jungleboyjdhellmann: Ok ...19:58
*** Rockyg has joined #openstack-oslo19:59
*** stevemar has quit IRC20:00
dhellmannjungleboyj: we did that with one or two patches during kilo, I think20:02
*** rpodolyaka1 has joined #openstack-oslo20:03
jecareydhellmann, patch is already ready for oslo-incubator https://review.openstack.org/#/c/186533/20:04
jecareyseems cleaner in this case to get that in and then cherry pick it back to stable/kilo.20:04
mtaninojecarey: final version of that fix is here. https://review.openstack.org/#/c/190175/  186533 needs a little update I think20:06
*** kgiusti has quit IRC20:06
mtaninoand then cherry pick into stable/kilo right?20:07
jecareymtanino, that's what I was thinking, but it shoulds like you could skip it and go straight to stable/kilo20:08
mtaninojecarey: you mean go straight to backport 190175 to stable/kilo, right?20:09
dhellmannjecarey: that patch is against master, for a module we're deleting from master20:15
jecareydhellmann, ok ... so mtanino should just go staight to backport 190175 to stable/kilo.20:16
mtaninojecarey: It's make sense for me.20:17
*** rpodolyaka1 has quit IRC20:17
*** ozamiatin has quit IRC20:18
*** rpodolyaka1 has joined #openstack-oslo20:19
*** achanda has joined #openstack-oslo20:19
*** achanda_ has joined #openstack-oslo20:23
dhellmannjecarey, mtanino : that's my view, but we should get dims to confirm before you spend a bunch more effort on it. I would expect (a) a patch to oslo.service if there isn't one, (b) a patch to stable/kilo (c) patches to any other stable branches where this is a problem you want to fix20:23
mtaninodhellmann: I understand.20:24
*** achanda has quit IRC20:26
*** ViswaV has joined #openstack-oslo20:32
*** e0ne has quit IRC20:32
*** e0ne has joined #openstack-oslo20:33
*** achanda_ has quit IRC20:38
*** e0ne has quit IRC20:41
openstackgerritGreg Hellings proposed openstack-dev/pbr: Add support for local versioning schemes  https://review.openstack.org/19284220:46
dimsjecarey: i want to be sure that the change in 186533 exactly is the same that is in oslo.service first. then we can debate master oslo-incubator vs stable/kilo oslo-incubator20:47
*** yamahata has joined #openstack-oslo20:54
*** haypo has joined #openstack-oslo20:54
*** nkrinner has quit IRC20:58
*** rpodolyaka1 has quit IRC20:59
*** jungleboyj has quit IRC21:02
*** ViswaV has quit IRC21:17
*** ViswaV has joined #openstack-oslo21:20
*** openstackgerrit has quit IRC21:24
*** openstackgerrit has joined #openstack-oslo21:24
*** ViswaV has quit IRC21:24
*** sdake_ is now known as sdake21:25
*** ViswaV has joined #openstack-oslo21:27
openstackgerritJeremy Stanley proposed openstack/oslo.db: Switch from MySQL-python to PyMySQL  https://review.openstack.org/18439221:27
fungidhellmann: dims: zzzeek: sdague: ^ rebased (minor conflict on one line of oslo_db/tests/sqlalchemy/test_sqlalchemy.py)21:28
*** Kevin_Bishop has quit IRC21:30
Rockygdhellmann: I'll be back in about half an hour if you'll be around.  Otherwise I'll look for you here tomorrow21:33
haypofungi, hey. i'm porting openstack to python 3, and your patches helped me :)21:33
fungiviktors|afk: i'll let you and zzzeek debate the benefits of an additional tox env for legacy mysql-python testing in https://review.openstack.org/18439221:34
haypofungi, i now need your patch for glance, my latest patch https://review.openstack.org/#/c/192904/ (to fix tox -e py34) requires https://review.openstack.org/#/c/184373/ (PyMySQL for Glance)21:34
haypofungi, Sabari wrote "DB migration tests are getting skipped for MySQL database with this patch"21:34
fungihaypo: great! i mostly just pushed them with a mass-proposal script. sdague pointed out the same on the nova change21:35
*** jungleboyj has joined #openstack-oslo21:35
* jungleboyj is having a bad computer day.21:35
fungihaypo: i _think_ a new oslo.db release with 184392 in it will correct that21:35
haypofungi, for nova, i picked ironic tox.ini which uses PyMySQL on python 3, and MySQL-python on Python 221:35
fungihaypo: but it's still a bit voodoo and black magic for me21:36
haypofungi, the "until we drop MySQL-python support" part is unclear to me :-p21:36
*** achanda has joined #openstack-oslo21:36
fungihaypo: right, i assume that's "so soon that there's no point in a second env to keep testing it"21:36
*** ashleighfarnham has quit IRC21:36
fungibut it's not my call21:37
haypofungi, did you try to add a separated venv to test mysql-python?21:37
*** bknudson has quit IRC21:37
funginope21:37
*** yamahata has quit IRC21:37
jecareymtanino, note comment from dims above ... update 186533.21:37
*** Rockyg has quit IRC21:38
haypofungi, i missed the session where pymysql was discussed. i'm allowed to vote +2, but i don't feel able to take a strong decision in favor of dropping mysql-python support21:38
*** ashleighfarnham has joined #openstack-oslo21:39
haypofungi, i would feel safer if you put a new venv to continue to test mysql-python. it puts less pressure on having to make a choice21:39
haypoi guess that a new gate will be needed to run this new venv, but it's usually fast and easy to get it21:40
fungihaypo: the upshot of the session was "it should be quick to just rip it out and replace it so let's not go for a long parallel support and deprecation period"21:40
haypofungi, it's ok for applications, not for the specific case of oslo.db21:40
fungihaypo: i'm happy for someone else to take it over if the consensus shifts that direction, but it's not something i have time to implement21:40
*** ViswaV has quit IRC21:40
haypofor the other venv, it's something like 4 lines in tox. i just don't remember the syntax for connectors21:41
dhellmannRockyg: I'm going offline for the evening in a bit, so maybe tomorrow21:41
fungialso, time for me to go pick up groceries, but i'll let the interested parties (i'm not an especially interested party, just didn't want it to stall for lack of volunteers) hash out the particulars21:42
dhellmannfungi: +2 on the patch, and if we need another tox env that can come in another patch21:42
*** achanda has quit IRC21:42
fungidhellmann: sounds good. hopefully once this makes it into an oslo.db release we can more safely move forward on the corresponding changes in leaf projects21:44
haypodhellmann, do you know the syntax to get the mysql-python connector? is it just "mysql://..." ? (it's "mysql+pymysql://..." for PyMySQL)21:44
haypodhellmann, i'm not sure that a different patch is a good choice, fungi removes mysql-python dep21:45
fungihaypo: well, the mysql-python dep would stay removed, you would just tweak the tox env definition to explicitly install it along with the requirements list files21:46
fungiso that it only gets installed if you're invoking the env which would test mysql-python21:46
haypofungi, i would prefer to keep mysql-python in .txt, it's updated by global requirements21:47
haypothe requirements script is not smart enough (yet?) to handle tox21:47
fungibut i'll leave it to the oslo.db cores to debate how many mysql libraries they want to support21:47
haypoit's better to make baby step. switching from mysql-python to pymysql by default for mysql is already a giant step :)21:48
fungiit just sounds like the scope will quickly escape what we discussed at the summit if we're going to let anyone use whatever mysql lib they like21:48
dhellmannfungi: if we land it this week, we can release monday21:48
fungianyway, <- afk for a while21:48
mtaninojecarey: dims I compared between 186533(incubator) and 190175(oslo.service). There is little bit difference between these at service.py.21:52
*** stpierre has quit IRC21:52
haypodhellmann, i have a local patch which is fungi's patch + "tox -e mysql-python" which uses "OS_TEST_DBAPI_ADMIN_CONNECTION=mysql://...". my patch keeps test-requirements-py2/py3, it only adds PyMySQL to py221:52
haypodhellmann, is it ok to reuse the same change id for such variant of his patch?21:53
haypoah. tox -e mysql-python fails :-p21:53
haypocool, only one failure21:53
dhellmannhaypo: I don't think we want to support both libraries, but I'll defer to dims and the oslo.db leads.21:55
dhellmann(rpodolyaka and viktors|afk)21:56
*** mriedem has quit IRC21:58
dims+1 to ask the leads first21:58
haypodhellmann, viktors|afk already replied: "are we really going to drop ANY MySQL-python support from openstack?"22:01
haypohe replied with a question... :)22:01
haypodhellmann, zzzeek looks to support the patch. he's a reference in the db world, no?22:02
zzzeekwhat is the question22:02
haypozzzeek, hey! would you be ok to support mysql-python support in oslo.db, at least in tests?22:03
zzzeeksure22:03
dhellmannhaypo: why do you want this?22:03
zzzeekive been telling ppl for  a few days now, the provising system should likely be fixed to support multiple drivers22:04
zzzeekwhich right now can only be done with this very awkward hack i gave to neutron22:04
haypozzzeek, do you see any reason why a specific application would prefer to keep mysql-python?22:04
haypodhellmann, sorry, wanting what?22:04
zzzeekhaypo: because they are hitting race conditions wiht pymysql.  again, neutron22:04
haypozzzeek, wait. i'm very tired and i'm no more able to use a computer...22:04
haypozzzeek, my question was: would you be ok to *drop* mysql-python support22:05
dhellmannhaypo: I'm trying to understand why you care about oslo.db having support for more than one mysql driver22:05
zzzeekhaypo: fine by me22:05
zzzeekhaypo: that’s what the patch does , i thought22:05
haypodhellmann, *i* have no opinion. as i wrote, i don't feel able to take a decision :)22:05
dhellmannok. I think we're all probably reaching the end of our day, so it might not be the best time to talk about it22:06
haypozzzeek, i was checking if you wrote the patch or not, i read "Michael Bayer: Uploaded patch set 3."22:06
dhellmannin general, I would rather we be consistent with what we support so we see consistent behavior in consuming projects22:06
zzzeekhaypo: i only fixed it to make the tests work22:06
dhellmannbe limited in what we support, that is22:06
zzzeekhaypo: id like oslo.db to be open towards multiple drivers in general, but that’s not critical at the moemnt22:07
haypozzzeek, just to make sure that i understand: with the patch, mysql-python is no more *tested*, but it still works, right?22:07
*** jgrimm is now known as zz_jgrimm22:07
zzzeekhaypo: sure22:07
haypozzzeek, ok22:07
dhellmannif we're not testing it, we shouldn't claim to support it22:07
*** sigmavirus24 is now known as sigmavirus24_awa22:08
haypodhellmann, "why you care about oslo.db having support for more than one mysql driver" it looks like any minor change in oslo* breaks all openstack22:08
haypodhellmann, that's why i'm looking for more information to understand the risk :)22:09
*** jungleboyj has quit IRC22:09
dhellmannhaypo: ok, that's fair. I think it might be confusing to distros if we aren't clear about what we really want them to be using, though.22:10
haypozzzeek, neutron already uses PyMySQL: fungi's patch was merged, https://review.openstack.org/#/c/184383/22:10
haypoglance will use PyMySQL too: https://review.openstack.org/#/c/184373/ (already a +2)22:12
haypoas glance, nova is waiting for oslo.db to change to PyMySQL: https://review.openstack.org/#/c/184387/22:12
haypocinder also switched to PyMySQL22:13
haypodhellmann, for me, there is no more reason against switching to PyMySQL22:13
dhellmannhaypo: I can't tell which side of which argument you're on any more :-)22:14
haypodhellmann, i'm in favor of simply approving the patch as it is22:14
dhellmannhaypo: which patch?22:15
haypodhellmann, https://review.openstack.org/#/c/184392/ fungi's patch to switch to PyMySQL by default22:15
haypoin oslo.db22:15
haypoi will unblock glance & nova to do the same change22:15
dhellmannhaypo: ok. I recommend voting +2 now, and leaving the W+1 until we can coordinate with rpodolyaka and viktors|afk just to be safe.22:16
*** prad has quit IRC22:23
haypodhellmann, i voted +2, tried to summarize the discussion and i pinged viktors|afk & rpodolyaka22:24
haypogood night ;)22:24
*** haypo has quit IRC22:24
*** dims has quit IRC22:26
*** jecarey has quit IRC22:30
*** zzzeek has quit IRC22:44
*** sigmavirus24_awa is now known as sigmavirus2422:55
*** sigmavirus24 is now known as sigmavirus24_awa22:56
*** ganso_ has quit IRC22:58
*** yamahata has joined #openstack-oslo23:15
*** dims has joined #openstack-oslo23:24
*** zzzeek has joined #openstack-oslo23:25
*** dims has quit IRC23:28
*** dims has joined #openstack-oslo23:28
*** dims has quit IRC23:33
*** claudiub has quit IRC23:34
*** yamahata has quit IRC23:40
*** mriedem has joined #openstack-oslo23:42
*** mriedem1 has joined #openstack-oslo23:45
*** mriedem has quit IRC23:47
*** sdake_ has joined #openstack-oslo23:59

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