16:02:52 #startmeeting cinder 16:02:53 Meeting started Wed Sep 19 16:02:52 2012 UTC. The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:02:55 The meeting name has been set to 'cinder' 16:03:03 Role call? 16:03:38 Looks like short meeting :) 16:03:43 hi 16:03:43 hi 16:03:48 hey 16:03:51 * bswartz is here 16:03:51 Ohh... so close! 16:03:53 :) 16:04:36 hello 16:05:05 Alright, cool 16:05:13 #topic rc1 16:05:41 We cut RC1 yesterday and I think we got everything we had slated in 16:05:58 Thanks EVERYONE for all the work the past week 16:06:08 ESPECIALLY all the work on syncing back to Nova 16:06:12 morning 16:06:19 you guys are making great progress :) 16:07:06 jgriffith: is there a process in place to figure out if anything was missed in the cinder->nova backporting effort? 16:07:18 bswartz: Yes... testing! 16:07:51 So that's what I'd like to ask now 16:08:02 Anybody who has some cycles... I'd like to do some good testing 16:08:15 I'm going to set up an etherpad we can keep updated 16:08:23 That way we won't all test the same thing :) 16:08:35 Particularly, I'd like to test a number of things: 16:08:50 1. Migrate from nova-vol (Folsom) ---> Cinder (Folsom) 16:09:03 This would include having volumes and snapshots created 16:09:49 2. Setup/run with cinder on seperate node from compute 16:10:01 3. multiple cinder nodes 16:10:18 you get the idea... 16:10:51 If you have time: http://etherpad.openstack.org/cinder-rc1testing 16:11:04 jgriffith: where is the process of migrating documented? 16:11:08 Throw up test ideas here as well as sign up for any you might do or want to work on 16:11:20 I've never actually tried migrating from n-vol to c-vol 16:11:30 bswartz: That's the other thing we all need to work on *documentation* 16:11:50 bswartz: So right now there's a couple of methods I've added to cinder-manage 16:12:05 bswartz: One for *moving* persistent target files 16:12:08 yeah I don't want to side track the meeting, but is there a script we can run to do the migration, or follow some manual steps? 16:12:12 bswartz: The other does a DB migration 16:12:38 Those are the tools we have in place for getting the data over... 16:12:51 We need to work on a script to do the config work still 16:13:11 bswartz: That's something I'm planning to get back to working on later today *hopefully* 16:13:28 but I could sure use help on all of this stuff 16:14:05 bswartz: answer your question? 16:14:17 jgriffith: yes thank you 16:14:22 bswartz: NP 16:15:00 So if anybody can do any sort of testing this week that would be fantastic 16:15:16 The next topic is even less popular :) 16:15:21 #documentation 16:15:27 #topic documentation 16:15:57 I've been harping about documentation for the drivers but I know we've been busy just getting changes in 16:16:02 But NOW is the time 16:16:15 I'm as guilty on this as anyone 16:16:41 I have plans to document the netapp drivers 16:16:49 I realize it's ridiculously late 16:17:08 bswartz: It's never too late until after we release :) 16:17:39 where is the documentation? 16:17:53 rongze: We have to generate it :) 16:18:11 rongze: So first step seperate from the drivers is going to be here: 16:18:29 docs.openstack.org 16:18:44 We'll need to create cinder versions of the nova-volume docuemntation 16:18:51 jgriffith: do you have a link to the github repo for the docs? I'm not finding it 16:19:00 bswartz: Yeah... 16:19:29 is it https://github.com/openstack/openstack-manuals ? 16:19:30 bswartz: https://github.com/openstack/openstack-manuals 16:19:36 okay thanks 16:19:42 bswartz: Yup.... sorry for the delay there :) 16:19:53 bswartz: So it's ugly as it's all XML 16:20:14 sample : http://docs.openstack.org/essex/openstack-compute/admin/content/nexenta-driver.html ?? 16:20:22 But I think we can get help from the docs gurus if needed 16:20:36 rongze: exactly! 16:21:34 jgriffith: that is different from this right http://docs.openstack.org/developer/cinder/ 16:21:41 developer docs 16:21:42 rnirmal: Yes! 16:21:49 which is the primary focus 16:21:52 The developer docs are in the project source 16:22:05 in the docs dir and auto upload etc 16:22:23 k gotcha.... so focus is going to be on admin docs 16:22:27 My priority would be the admin docs right now yes 16:22:51 rnirmal: But if there's one that folks feel more comfortable with versus another I don't care 16:22:58 We just need to update 16:23:15 My perference is we do everything we can to make transition for users as smooth as possible 16:23:23 Which translates to *admin docs* 16:23:52 ok another question 16:24:02 updating volumes doc in openstack-compute/admin or 16:24:08 create a new one for cinder ? 16:24:29 rnirmal: So this is kinda tricky 16:25:05 rnirmal: What might work is augment compute with cinder info 16:25:36 rnirmal: I would like to break the cinder docs out but I don't think that's going to work at this point 16:26:10 hmm I don't know.. since the volumes in openstack-compute would be nova-volumes related... the docs for the drivers are going to be the same 16:26:21 but other things... there's differences 16:26:39 rnirmal: Yeah, that's where it gets a bit tricky 16:27:08 Your mean is add new driver document into openstack-compute/admin ? 16:27:21 yes 16:27:22 such as xiv/netapp? 16:27:25 would it suffice to say... update the nova-volumes docs.. add all the missing pieces then port those docs over for cinder? 16:27:43 rnirmal: Yes, I think for the drivers that's ideal 16:28:32 I want to do that, but my english is not good.. 16:28:50 rongze: It seems as good as mine :) 16:28:54 I think it need the author of the driver to do that. 16:29:10 rongze: Yes, I think the driver authors MUST do their drivers 16:29:26 So... on the other side here's a better example: 16:29:37 http://docs.openstack.org/essex/openstack-compute/admin/content/ch_volumes.html 16:30:03 We need to update the managing volumes section 16:30:10 Include cinder info and mark it as the default 16:30:51 Volume drivers, we just update appropriately (this is where myself, bswartz jdurgin etc come in) 16:31:15 We need to add sections for things we added such as: NFS, clone image etc 16:31:26 That would be a good start... 16:31:42 After that we'll want a specific migrate nova-vol--->cinder section 16:32:15 Make sense? 16:32:20 yes 16:32:36 yup 16:32:42 anybody disagree, or see a better approach/starting point? 16:32:42 yup 16:32:51 makes sense, that is 16:32:53 * bswartz agrees 16:32:54 Ok... one yes and two yups wins 16:33:08 #topic anything we know we missed already 16:33:29 So is there anything folks already know we NEED to get in for Folsom that was missed in RC1 16:34:11 I have an open bug 16:34:11 Ok... silence was what I hoped for on that one 16:34:14 DOH! 16:34:21 was planning to fix it 16:34:24 bswartz: You do? Which one? 16:34:28 sec 16:34:54 1050359 16:35:04 https://bugs.launchpad.net/bugs/1050359 16:35:07 Launchpad bug 1050359 in nova "Tests fail on 32bit machines (_get_hash_str is platform dependent)" [Medium,Confirmed] 16:35:17 bswartz: Ahhh! Yes 16:35:23 it won't be hard to fix 16:35:28 bswartz: I did see that one and knew about it 16:35:28 I just need to test and checkin 16:36:01 jgriffith: do you foresee any problems getting that fix accepted? 16:36:10 it needs to go into both cinder and nova 16:36:15 Yeah, I wasn't sure about the validity of running OS on 32 bit but it's supported so it should go in 16:36:33 bswartz: I don't think it should be an issue 16:36:53 okay well that's like #2 on my todo list 16:37:04 bswartz: But I think the Nova side is stricter on this stuff than I am :) 16:37:25 it was the nova folks that discovered it 16:37:30 bswartz: We'll raise it and see, but it seems like it should qualify 16:37:51 bswartz: Yeah, it shouldn't be a problem 16:38:05 Ok... anything else folks have? 16:38:13 #topic open discussion 16:39:04 I have a suggestion , if we first have migrate nova-vol--->cinder section in document , our testing for cinder-rc1testing will be easy. 16:39:18 rongze: good idea 16:40:07 We can note it on the ehterpad and work on it 16:40:43 Even if folks want to document migration steps on the ehterpad as a working doc we can then formalize it into a doc later 16:41:18 I'll try to get to that step 1 piece on the etherpad later (unless someone beats me to it) :) 16:42:04 It's going to be something like: install cinder, set up DB, copy targets and DB, verify transfer 16:42:37 what is the targets? 16:42:42 detach volumes from instances, stop services, reconfig, start services etc 16:42:49 rongze: iscsi targets 16:43:08 Do it need to copy? 16:43:20 targets' config ? 16:43:29 rongze: More accurately it's the persistent target files/configs 16:43:47 oh, I know 16:44:00 We don't have to recreate the targets themeselves 16:44:33 rongze: We could also leave them where they are rather than move them 16:45:26 yes 16:45:54 Ok, that part is probably only applicable in devstack env 16:46:56 Do devstack support multi cinder-volume? 16:47:15 rongze: I don't think most people use it that way 16:47:27 rongze: There is multi node support with devstack on hardware 16:47:44 rongze: that's what I was trying to set up a couple weeks ago but got distracted 16:48:30 It's kinda just *cheating* or being lazy and using devstack to install everyting for you 16:49:07 Then manually figuring out all the config file settings etc that need done 16:49:15 At least that was my approach 16:49:40 when we testing multiple cinder nodes, we need multi cinder-volume env. 16:50:03 if devstack support it, it will be easy to test. 16:50:49 devstack won't do it automatically, but it will handle all the grunt work (installing the packages, setting up DB's networking etc) 16:51:19 oh, I see 16:52:07 TBH manual install as painful as it is would be the *best* thing to do but I tend to have mixed results when I do that :) 16:52:22 It's very time consuming and I'm lazy, that's why I love devstack :) 16:53:15 I love too... 16:53:26 rongze: If you get started on it and need some help let me know 16:53:47 rongze: I'm by no means an install/config expert but I can try to help and maybe learn some more :) 16:54:15 Ok... anybody have anything else? 16:55:00 ahh 16:55:02 I think I have no time to test.. I must to write a topic. 16:55:07 ceph? 16:55:07 I have a topic in Design summit, it is about volume on local storage. 16:55:26 gatuus: yes, what about it? 16:56:19 are you planning to .. well support it in some time.. or we need to wati for the inktank guys to make the.. mm.. I dunno the tests? 16:57:07 gatuus: It is supported (RBD) at any rate, is there something specific you're looking for? 16:57:34 I need to make tests.. but dont know where to start.. sorry.. 16:57:56 I remember a blog record the test. 16:59:17 http://www.sebastien-han.fr/blog/2012/06/10/introducing-ceph-to-openstack/ 17:00:38 gatuus: That will work for the most part if you just s/nova.voume/cinder/ 17:01:36 gatuus: Does that help? 17:02:47 jgriffith: My topic is about local storage, it is like http://wiki.cloudstack.org/display/RelOps/Local+storage+for+data+volumes. 17:02:59 yes a lot thanks 17:03:24 rongze: cool, I haven't checked the submisssions page lately TBH, did you propose it? 17:03:32 jgriffith: yes 17:03:39 90% 17:03:57 rongze: Ok, I'll be sure to check later. For some reason I'm not getting email updates on that this time around 17:04:06 Ok... everyone 17:04:11 rongze: Page Not Found ?? 17:04:31 gatuus: Odd... it came up for me? 17:04:36 hehehe 17:04:38 sorry 17:04:51 but not for me =( 17:04:54 I have impl implement dependence snapshot, and it can upload snapshot to swift. 17:04:59 alright everyone, thanks for your time and all the effort so far this release cycle! 17:05:08 Need to break... 17:05:17 "The CloudStack wiki is under migration. " bblablabla 17:05:24 I'll be on IRC of course if anything comes up 17:05:29 #endmeeting cinder