17:00:49 #startmeeting cinder-nova-api-changes 17:00:50 Meeting started Mon Aug 1 17:00:49 2016 UTC and is due to finish in 60 minutes. The chair is ildikov. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:53 The meeting name has been set to 'cinder_nova_api_changes' 17:01:17 scottda DuncanT ameade cFouts johnthetubaguy jaypipes takashin alaski e0ne jgriffith tbarron andrearosa hemna erlon mriedem gouthamr ebalduf patrickeast smcginnis diablo_rojo gsilvis 17:01:30 0/ 17:01:33 hi 17:01:45 hi :) 17:03:01 hey 17:03:19 o/ 17:03:53 ok let's start 17:04:18 jgriffith: I saw updates on the Cinder patches for the new attach/detach calls 17:04:39 jgriffith: can you update us a bit with where we are regarding those? 17:04:42 ildikov: yep, fixed up the merge conflicts and a couple little things like adding a functional test 17:05:03 ildikov: got stuck trying to get Cinders functional framework to allow admin api calls 17:05:25 ildikov: creating the admin-api seemed easy, but didn't quite work 17:05:37 ildikov: Then moved back over the Nova side. 17:06:11 jgriffith: I thought to extend the already existing API tests here: https://review.openstack.org/#/c/339692/ 17:06:16 btw, my devstack change to test all of this isn't configured correctly, i think the docs for LIBS_FROM_GIT are old, but i'm failing here https://review.openstack.org/#/c/340517/ 17:06:29 I'm not sure how useful those are though... :S 17:06:33 mriedem: looking 17:07:01 probably just need to corner someone in -qa to ask what i'm missing 17:08:10 mriedem: that *looks* correct 17:08:32 basically what I used in my local.conf 17:09:09 d-g checks the PROJECTS list or something 17:09:10 and pukes on that 17:09:20 ildikov: I kinda take issue with stuffing everything under a generic volume test again 17:09:25 http://logs.openstack.org/17/340517/3/check/gate-tempest-dsvm-full/3cf66c7/logs/devstacklog.txt.gz#_2016-07-27_19_42_38_923 17:09:31 i'll bug someone in -qa 17:09:33 ildikov: we made that sort of mistake in our unit tests and it's sort of a mess 17:10:10 ildikov: https://review.openstack.org/#/c/327408/10/cinder/tests/functional/test_attach.py 17:10:12 jgriffith: the currently existing functional tests are using stuff from the unit test folder, which got me delayed a bit as I didn't look for things there... 17:10:25 jgriffith: yeap, I will check it 17:10:27 ildikov: :) I merged a change for a few of those BTW 17:10:34 ildikov: moved them up into the tests root 17:10:56 mriedem: Ohh 17:11:06 jgriffith: it's really a mess, so thanks for all clean up work 17:11:08 mriedem: the new/old thing... so it's cloning into /opt/stack I'll bet 17:11:29 mriedem: I don't use new/old locally so that is likely something to do with it 17:11:34 jgriffith: I didn't want to change them as I wasn't sure whether anyone is working on it 17:11:50 mriedem: ildikov other than that, the main thing I'm working out now is the shelve tests 17:12:20 mriedem: ildikov they do the old initialize_connection and terminate calls directly still and it sort of screws things up 17:12:55 mriedem: ildikov so I'll get those fixed up and then we probably need to start talking about how we all would like to see the detection of the API's and things work 17:13:01 jgriffith: you mean shelve now, right? 17:13:22 whether that's microversions etc and how we detect/check on the Nova side 17:13:42 ildikov: I'm referring to the tempest/gate dsvm tests 17:15:33 jgriffith: ah, ok 17:16:33 #action mriedem to move https://review.openstack.org/#/c/340517/ to devstack-gate 17:16:47 jgriffith: I'm sure there will be a few issues with the VM actions which are kind of hacked currently 17:20:03 jgriffith: are we planning to microversion the API now? 17:20:43 ildikov: that's up to mriedem and others 17:21:03 ildikov: I believe in past discussions that's what mriedem and johnthetubaguy had suggested, but I could be wrong 17:21:31 a new api in cinder should probably be microversioned no? 17:21:32 ildikov: I can just add an API call to nova/volume/cinder that checks and sets that on init and be done as well 17:22:27 mriedem: I can set it up however people would like. Personally I don't know that new calls need to be, but I'm fine if we want that 17:22:50 mriedem: I'm just putting off dealing with them as long as I can knowing that it's inevitable :) 17:24:47 jgriffith: so until a microversion, 17:25:01 you were going to call the new api and set a flag if it works or not so we can know in nova if we can use it? 17:25:32 mriedem: yeah, or just hack it somehow for a POC knowing that we don't plan to merge this on the Nova side until the next release 17:26:06 mriedem: well... yes, that *is* the hack 17:27:03 that would be easier for now 17:27:15 so you don't land a microversion'ed api in cinder that just needs changes 17:27:24 i guess the question is if cinder is going to land the api change in newton 17:27:28 mriedem: ok, great. I fully realize that whatever I push is going to be just WIP and temporary 17:27:40 i think you'd definitely want it microversioned when it lands in cinder 17:28:02 mriedem: yeah, I'll check in with the folks running micro-versions in Cinder and see where we're at 17:28:20 mriedem: I think we're pretty close so it should be a thing in Newton for sure 17:28:22 scottda should be able to help with that 17:28:30 I mean the microversion stuff 17:28:55 ildikov: yeah... I got ya :) 17:29:08 and as we need to keep Nova be able to talk to older Cinder as well cannot avoid using this 17:30:31 jgriffith: I remember correctly that we will not have feature branches for this, right? 17:30:51 ildikov: that's correct 17:31:18 jgriffith: cool, tnx 17:33:19 jgriffith: mriedem: I think if we can get the Cinder side merged and make the pure attach call work with the new Cinder API as a POC in Newton that would be a great starting point 17:34:53 jgriffith: back to testing a bit, should I abandon my patch on top of yours in Cinder and try to help out on the direction you're working at the moment? 17:36:01 ildikov: that's completely up to you, I would prefer we don't have every volume related action under the sun in a single test but that's just my opinion 17:36:36 jgriffith: sure, that was just a test to try to make it work :) 17:36:49 ildikov: test_volume is technically just fine, I'm just being picky :) 17:37:05 jgriffith: I was wondering more how the Cinder team and you would like to see functional tests in the future 17:37:37 ildikov: well my opinion has been that an API feature should have it's own test file/module 17:38:05 jgriffith: that sounds reasonable 17:38:43 jgriffith: are the fake drivers and other helper methods going to stay but maybe re-organized a bit? 17:39:29 mriedem: one thing, I saw that hemnafk's patch to start to remove check_attach got merged 17:40:04 ildikov: the fake_driver is already in cinder/tests not quite sure what you mean? 17:40:05 mriedem: can you check this one, which tries to clean it up fully: https://review.openstack.org/#/c/335358/ ? 17:40:52 ildikov: yeah, probably not today though, i think had some concerns about the boot from volume scenario and that 17:41:01 jgriffith: I had to add modifications to the one that's used with the current tests: https://review.openstack.org/#/c/339692/5/cinder/tests/fake_driver.py 17:41:01 like race issues 17:41:47 mriedem: so in case of BFV, when you attach an already existing volume at boot time reserve_volume was not called at all 17:42:19 mriedem: so there's an extra reserve_volume call in that flow now, but I'm not 100% sure it's at the right place TBH 17:43:10 mriedem: there's also a grenade test that's quite constantly failing with that patch, I need to take a look at that one as well 17:43:35 mriedem: I appreciate if you can check that patch some time this week :) 17:44:28 jgriffith: so by adding the modifications I got a little bit unsure I'm using the right thing :) 17:44:47 ildikov: i think the thing was with boot from volume, we didn't reserve the volume in the api today, we reserved it in the compute 17:45:24 at least i thought we did 17:45:26 but i'm not seeing that 17:46:36 mriedem: I mistyped some stuff during trying to debug it in reserve_volume and attaching a volume during BFV still worked like a charm, so I'm sure it's not called at all 17:47:06 mriedem: when I detached the volume and tried to attach it again reserve failed as expected 17:47:20 i guess i'm not sure why we don't reserve the volume during BFV today 17:47:35 not the nicest way to see what's happening, but was quite quick and effective 17:47:47 anyway, we can take it offline 17:47:57 I couldn't come up with any scenario either besides it got forgotten 17:47:58 i have about 10 things going on at once today 17:48:25 sure, I hate Mondays too 17:48:40 mriedem: I don't know of a reason other than oversight either 17:48:41 so I'm happy to take it on the review 17:50:40 is there anything else for today? 17:52:03 ok, I take it as a no 17:52:20 nope 17:52:25 thanks guys for joining and have a nice rest of the day! 17:52:41 #endmeeting