Monday, 2016-06-13

*** markvoelker has quit IRC00:01
*** tyr has joined #openstack-meeting-cp00:10
*** tyr has quit IRC00:15
*** tyr has joined #openstack-meeting-cp01:54
*** markvoelker has joined #openstack-meeting-cp01:58
*** tyr has quit IRC01:59
*** markvoelker has quit IRC02:02
*** coolsvap has joined #openstack-meeting-cp03:20
*** tyr has joined #openstack-meeting-cp03:38
*** tyr has quit IRC03:42
*** markvoelker has joined #openstack-meeting-cp03:59
*** markvoelker has quit IRC04:03
*** tyr has joined #openstack-meeting-cp05:26
*** tyr has quit IRC05:31
*** markvoelker has joined #openstack-meeting-cp05:59
*** markvoelker has quit IRC06:04
*** tyr has joined #openstack-meeting-cp07:14
*** tyr has quit IRC07:19
*** markvoelker has joined #openstack-meeting-cp08:00
*** markvoelker has quit IRC08:05
*** tyr has joined #openstack-meeting-cp09:02
*** tyr has quit IRC09:06
*** tyr_ has joined #openstack-meeting-cp10:50
*** tyr_ has quit IRC10:55
*** sdague has joined #openstack-meeting-cp11:49
*** markvoelker has joined #openstack-meeting-cp12:01
*** markvoelker has quit IRC12:06
*** flaper87 has quit IRC12:09
*** flaper87 has joined #openstack-meeting-cp12:15
*** flaper87 has quit IRC12:15
*** flaper87 has joined #openstack-meeting-cp12:15
*** sdague has quit IRC12:16
*** sdague has joined #openstack-meeting-cp12:16
*** coolsvap has quit IRC12:25
*** markvoelker has joined #openstack-meeting-cp12:25
*** scottda has joined #openstack-meeting-cp12:32
*** tyr_ has joined #openstack-meeting-cp12:38
*** tyr_ has quit IRC12:43
*** xyang1 has joined #openstack-meeting-cp12:55
*** sheel has joined #openstack-meeting-cp13:05
*** xyang1 has quit IRC14:22
*** xyang1 has joined #openstack-meeting-cp14:25
*** tyr_ has joined #openstack-meeting-cp14:25
*** tyr_ has quit IRC14:30
*** sigmavirus24_awa is now known as sigmavirus2414:32
*** coolsvap has joined #openstack-meeting-cp15:05
*** tyr_ has joined #openstack-meeting-cp15:08
*** tyr_ has quit IRC15:12
*** piet has joined #openstack-meeting-cp15:14
*** piet has quit IRC15:52
*** piet has joined #openstack-meeting-cp15:52
*** tyr_ has joined #openstack-meeting-cp15:59
*** smcginnis has quit IRC16:58
*** smcginnis has joined #openstack-meeting-cp16:58
*** mriedem has joined #openstack-meeting-cp16:58
ildikov#startmeeting cinder-nova-api-changes17:00
openstackMeeting started Mon Jun 13 17:00:04 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: cinder-nova-api-changes)"17:00
openstackThe meeting name has been set to 'cinder_nova_api_changes'17:00
scottdahi17:00
ildikovscottda ildikov DuncanT ameade cFouts johnthetubaguy jaypipes takashin alaski e0ne jgriffith tbarron andrearosa hemna erlon mriedem gouthamr ebalduf patrickeast smcginnis diablo_rojo gsilvis17:00
ildikovhi :)17:00
mriedemo/17:00
* alaski lurks17:00
* johnthetubaguy lurks17:00
ildikovetherpad: #link https://etherpad.openstack.org/p/cinder-nova-api-changes17:00
patrickeasthey17:01
ildikovsorry for skipping last week17:01
ildikovI thought two items for today, which are the refactoring and its impacts that jgriffith is working on and the other would be the migration test, I think scottda has updates on that one17:03
scottdaI've a migrations-with-BFV patch up: https://review.openstack.org/#/c/32668117:03
scottdaIT needs a devstack change (devstack-gate) which I need to put up and list as a dependency.17:04
scottdaBut is ready for testing if anyone is interested.17:04
scottdaOnce that is in, we'd want another test with multi-attach and cinder migrate.17:04
scottdaBut we said we wouldn't support multi-attach with BFV, so that'd be slightly different. But not more complicated.17:05
ildikovthat looks good17:05
ildikovI think we will not support booting from a multi-attach volume17:05
ildikovbut we will support attaching a multi-attach volume at boot time17:06
* amrith lurks17:06
ildikovso we have a negative test and a positive as well with the non-bootable one17:06
ildikovscottda: those few jobs are failing due to the missing dependency?17:06
hemnahey guys, I'm working on the grenade failures with os-brick right now17:07
scottdaildikov: Actually, one failure was a requirements issue for something that looked unrelated....17:07
jgriffitho/17:07
jgriffithsorry I'm a bit tardy17:07
ildikovhemna: ok17:08
scottdaildikov: The other seemed obscure as well. I did a rebase just to see if it was something fixed in tempest itself.17:08
jgriffithildikov: scottda wait... not support multi-attach BFV?17:08
ildikovscottda: ok, got it17:08
scottdaildikov: Frankly, I'm learning as I go with regards to getting a Tempest test merged. Anyone with more expertise, let me know if you're available to bother with questions.17:09
jgriffithildikov: scottda I though one of the primary use cases you wanted multi-attach for was to help live-migration of volume backed instances?17:09
ildikovjgriffith: we agreed to skip boot from multi-attach volume with mriedem and johnthetubaguy I think during Mitaka17:10
scottdajgriffith: At least for the first pass at multi-attach.17:10
ildikovscottda: I'm not a big expert either, but I'll try to take a look and be helpful17:11
mriedemi honestly don't exactly remember the reason why anymore17:11
ildikovmriedem: TBH I think it simply felt odd17:11
scottdaI think we just didn't like the complexity, and were unsure of the corner cases.17:11
mriedemnova won't create a multiattach volume when booting, that would require API changes in nova17:12
mriedemi'm not sure what bringing a multiattach volume to attach at boot time would do17:12
johnthetubaguy+117:12
mriedemexcept maybe not landing on a host that could attach that kind of volume, i.e. mitaka node at this point17:12
ildikovI think simply attaching it, but not booting from it should be perfectly fine17:13
ildikovwell, placement is an issue in other cases as well17:14
johnthetubaguyso I should check something here17:15
johnthetubaguyis that booting from an already created multi-attach17:15
johnthetubaguyor creating a multi-attach from an image during the boot process17:15
johnthetubaguyor both17:15
mriedem"or creating a multi-attach from an image during the boot process" - we're not doing thta17:15
mriedemyou'd have to tell nova in the BDM dict to create multiattach=True which is more proxy17:15
ildikovright17:16
mriedemproviding an existing multiattach volume to attach at boot time should be fine17:16
mriedemit's the same as attaching it to an existing instance17:16
mriedemmost of this is covered in http://specs.openstack.org/openstack/nova-specs/specs/newton/approved/multi-attach-volume.html#rest-api-impact17:16
ildikovand I think I still have the code for failing when we're trying to boot from an existing multi-attach volume17:16
mriedemi think we can get around the placement issues if we just block in the nova-api that you can't do anything with multiattach volumes until all of the computes in the deployment are new enough to handle it17:17
ildikovsource and dest is volume and bootindex is 017:17
mriedemildikov: yup, that's in the spec17:17
ildikovyeap, checking that will help and then placement will only have to check whether we have libvirt or not17:18
mriedemwell,17:18
mriedemunless we extend the compute capabilities filter or add a new scheduler filter, i'm not sure that's going to happen17:18
mriedemi have a feeling that non-kvm deployments of openstack will just block this via policy17:19
mriedemjohnthetubaguy: is that what rax is/would do?17:19
mriedemprobably on the cinder side so you can't create the multiattach volume to begin with17:19
ildikovthat would be the easiest17:19
ildikovI think17:20
mriedemanyway, we're kind of getting off in the weeds on things that have already been discussed and are for the most part in the spec17:20
ildikovalthough we need to get there to have the Cinder changes in place to get to enable multi-attach17:20
ildikovjgriffith: can you give us an update on how the refactoring work goes?17:21
jgriffithildikov: sure17:21
jgriffithildikov: was hoping to get feedback on the code17:21
ildikovI added the links to the etherpad for the already uploaded patches17:21
jgriffithildikov: I'm working on the detach side of things in Nova now17:21
jgriffithattach is working as expected, haven't cleaned out some of the things like calling initialize to get connection info17:22
jgriffithbut I think that would be good follow up work17:22
jgriffithwant to focus on the base attach/detach cases for now17:23
ildikovyou mean you initialize_connection twice on Cinder side with the new code?17:23
jgriffithildikov: NO17:23
jgriffithildikov: I mean there's a few places where Nova uses initialize_connection calls to Cinder to re-establish connection info17:23
ildikovyeah, I agree it would be good to have the basic scenarios work before jumping on the more difficult ones17:23
jgriffithildikov: with no intent of performing an attach17:23
ildikovjgriffith: ah, ok, I wasn't sure what you meant by missing clean up17:24
jgriffithildikov: ie the volume is already attached, but they want to "refresh" the info17:24
mriedemis there going to be a problem with nova calling os-initialize_connection in non-attach cases?17:25
jgriffithildikov: FWIW these changes will just support multi-attach for the most part without Nova really having to be involved (except for the libvirt setting)17:25
ildikovjgriffith: right, got it, I think there will be a few cases where we need to figure out what to do based on the instance actions johnthetubaguy described us a few meetings ago17:25
jgriffithmriedem: no... but I'd like to eventually make that go away17:25
mriedemjgriffith: with a new cinder api to get connection info?17:25
jgriffithmriedem: I wrote the code currently in such a way that all of the *old* calls work exactly as they did before17:25
ildikovjgriffith: yeah, I expected that to happen as we want to remove the handling of the volume state machine from Nova17:26
jgriffithmriedem: https://review.openstack.org/#/c/327408/17:26
jgriffithmriedem: I'm just using wrappers of things for now17:26
* johnthetubaguy shakes fist at his internet connection17:26
jgriffithmriedem: that way it's relatively seemless, and we can continue progressing all the various implementation details over time17:27
johnthetubaguymriedem: yeah, +1 on both counts, we just block until all compute nodes are upgraded17:27
jgriffithmriedem: rather than a single "big bang" wanted a phased approach that just got us over the API hump17:27
jgriffithmriedem: note the (outdated) gist of the nova changes that go with that patch17:28
jgriffithmriedem: I should have something at least suitable to post as a WIP to Nova shortly and link the cinder, cinderclient patches to it17:28
ildikovjgriffith: you already have the snippets up for attach, right?17:31
mriedemjgriffith: ok, posted a comment in your change17:31
jgriffithildikov: yes17:31
mriedemjgriffith: would nova-api be calling create_attachment now?17:31
jgriffithmriedem: looking17:31
mriedemrather than the compute?17:31
mriedemit'd have to be compute i guess17:31
mriedemto pass the connector dict17:31
ildikovjgriffith: cool, I planed to play with it a bit in devstack17:31
jgriffithmriedem: yeah... so your points are part of what led me to this wrapper approach17:32
jgriffithmriedem: https://gist.github.com/j-griffith/ded4a08c488f0d90e90fff53afb2d7f117:32
jgriffithso for now, I only address things in the base attach case17:32
jgriffithmriedem: this way I don't change anything like swap_volume or the case with Cells etc17:33
jgriffithmriedem: my thought would be start with the base attach/detach cases.  Get that merged, then do follow up patches to start hitting all the individual *special* cases17:34
jgriffithmriedem: I mostly want to keep the patch sizes manageable17:34
mriedemjgriffith: with https://gist.github.com/j-griffith/ded4a08c488f0d90e90fff53afb2d7f1 we'd still be reserving the volume in nova-api17:34
jgriffithmriedem: then deprecate the old calls, and mark them for removal next cycle17:34
mriedemwould that make create_attachment fail?17:34
jgriffithmriedem: nope, it'll still work because I removed that step :)17:35
ildikovjgriffith: I would assume if we have more info stored on Cinder side along with the way more simpler API then things should work out for those *special* cases as well, but agreed on adressing them one-by-one17:35
jgriffithmriedem: That's something I should clean up a bit thought TBH17:35
jgriffithmriedem: I considered removing it from the nova-api and baking it in here, but instead just left it alone and instead "use" it17:36
ildikovmriedem: I think the aim is to replace reserve, initialize and attach with the single create_attachment call17:36
jgriffithmriedem: I still think there's value in reserve to avoid some possible race conditions17:36
ildikovmriedem: and by having only one call kill the race conditions as well17:37
mriedemyeah i only bring it up because you can have mitaka computes that aren't using create_attachment17:37
jgriffithildikov: perhaps eventually.  for now I'm just replacing initialize_connection and attach17:37
jgriffithmriedem: +117:37
jgriffithmriedem: that's why it ended up that way17:37
mriedembut again, nova can check the min compute service version in the deployment and make decisions based on that17:37
ildikovjgriffith: ok, then I'm a step ahead it seems :)17:37
jgriffithmriedem: I suppose ya'll will want something to deal with the nova-newton, cinder-mitaka... I didn't include that in my gist, but will look at making it happen17:39
mriedemyeah, microversion on the cinder side17:40
mriedemnova will need to know if cinder is new enough to call create_attachment17:40
jgriffithmriedem: ok, honestly I wanted to do this without using those, but no reason not to use them17:41
jgriffithmriedem: will just mean I have to finally figure them out and how they really work17:41
jgriffith:)17:41
ildikovjgriffith: are there any items any of us can help with?17:42
jgriffithildikov: comment on the code that's there, add notes on what you might propose for micro-versions17:42
jgriffithildikov: once I get the nova WIP posted test17:42
ildikovjgriffith: I'm not saying I'm friends with microversions, but I'm happy to give it a try :)17:43
ildikovjgriffith: ok, cool, will do17:43
jgriffithildikov: and at that point honestly anybody that wants to joint-contribute on the nova side inparticular that would be great17:43
mriedemthere is obviously a cinderclient change that's needed also17:43
mriedemhttps://gist.github.com/j-griffith/ded4a08c488f0d90e90fff53afb2d7f1#file-gistfile1-txt-L9817:44
scottdajgriffith: I'll add some notes for microversions. We are friends.17:44
ildikovjgriffith: sounds good, tnx!17:44
jgriffithmriedem: posted https://review.openstack.org/#/c/327409/17:44
ildikovscottda: :)17:44
jgriffithmriedem: FWIW those two reviews and the gist applied to Nova give a working attach change17:45
jgriffithmriedem: it doesn't include error-recovery, but I've got that and it will be in the Nova WIP when I get it posted17:45
jgriffithand of course no microvresioning etc17:45
jgriffithgeeshh... *micro versioning*17:45
mriedemi'm trying to think through the nova-api changes when we get a multiattach volume17:48
mriedembecause nova-api is still calling reserve, and the patch in mitaka needed to check if it's a multiattach volume17:48
ildikovI would assume check_attach is out of the game as well17:49
ildikovor at least it should be17:49
ildikovand that checked mutliattach17:49
*** piet has quit IRC17:49
mriedemb/c hemna is removing the calls to os-reserve?17:49
ildikovother than that there is the code for the BFV case17:49
ildikovmriedem: hemna has a patch up for removing check_attach as those checks are in os-reserve as well17:50
mriedemyeah https://review.openstack.org/#/c/315789/17:50
hemnaI've been absent from this meeting...sorry guys17:51
ildikovmriedem: so both Nova and Cinder performs the same checks17:51
hemnagrenade issues.17:51
ildikovhemna: no worries, if you can take a look at jgriffith's patches that would be good, we talked about those mostly17:51
hemnaok I'll re-read the meeting after I'm done17:52
ildikovmriedem: so if jgriffith did not remove reserve for now it still does its job for checking the volume status17:52
ildikovI mean volume state, like 'attached', etc. and it's prepared for multiattach as well17:53
ildikovhemna: tnx17:53
mriedemok 5 minutes left17:54
ildikovright, so as a summary we need reviews for jgriffith's patches, and also comment on the microversioning to have the simpler API calls for attach and then detach, we can move on to the more difficult cases after figuring out the basics17:55
*** coolsvap has quit IRC17:56
ildikovwe also need an eye on hemna's remove check_attach patch as that would be another great cleanup item17:56
mriedemthere are some comments in that one already17:56
ildikovwe also talked about the Cinder migrate tests scottda is working on17:56
*** coolsvap has joined #openstack-meeting-cp17:56
ildikovmriedem: yeap I saw, I'll check on the details later17:57
ildikovis there anything for the today's meeting we would need to discuss?17:57
mriedemend it17:59
ildikovok, I'll take it as a no :)17:59
scottdabye17:59
ildikovthanks everyone!!!17:59
ildikov#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Mon Jun 13 17:59:45 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder_nova_api_changes/2016/cinder_nova_api_changes.2016-06-13-17.00.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder_nova_api_changes/2016/cinder_nova_api_changes.2016-06-13-17.00.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder_nova_api_changes/2016/cinder_nova_api_changes.2016-06-13-17.00.log.html17:59
*** mriedem has left #openstack-meeting-cp18:00
*** tyr_ has quit IRC18:00
*** ebalduf has quit IRC18:06
*** coolsvap has quit IRC18:13
*** sdake_ has joined #openstack-meeting-cp18:23
*** sheel has quit IRC19:35
*** cebreidian has quit IRC19:59
*** sdake_ is now known as sdake20:06
*** ericksonsantos has quit IRC20:59
*** rockyg has joined #openstack-meeting-cp21:04
*** rockyg has quit IRC21:47
*** beekhof has quit IRC22:59
*** sheeprine has quit IRC23:03
*** hemna is now known as hemnafk23:04
*** xyang1 has quit IRC23:05
*** sheeprine has joined #openstack-meeting-cp23:06
*** beekhof has joined #openstack-meeting-cp23:07
*** sdague has quit IRC23:38

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