17:03:38 #startmeeting training-guides 17:03:39 Meeting started Mon Jun 8 17:03:38 2015 UTC and is due to finish in 60 minutes. The chair is sayalilunkad. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:03:40 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:03:42 The meeting name has been set to 'training_guides' 17:04:16 so, no agenda. shouldn't take too long :-). 17:04:42 what's up, sayalilunkad? 17:04:43 I guess not :) 17:05:39 ntm, Just out of ER :/ Got a bad sun burn on the beach 17:06:19 you need to get out of that country, you don't seem to be a good fit. 17:06:35 how did you survive that many years? 17:06:45 I am in Austin atm 17:07:05 hello 17:07:06 get out of that country, too, then :-). 17:07:17 hi dguerri 17:07:21 hi dguitarbite 17:07:25 Yeah! I need to migrate to the cold regions ;) 17:07:43 sayalilunkad: or at least less hot. 17:08:04 rluethi: yeah 17:08:45 so, plans for labs-scripts? 17:08:54 how's the python port coming along? 17:09:04 rluethi: I am waiting for sayalilunkad 17:09:14 shes supposed to finish some parts 17:09:31 sayalilunkad: do you have any progress 17:09:34 hello Guest57520 17:09:51 nope, haven't been able to do much 17:10:09 what are you working on? 17:10:14 Will try to work on it the coming few weeks 17:10:48 well I need to do some exception handling and code re factoring 17:11:36 so the code is roughly feature-complete? 17:12:09 sorry something wrong with my IRC client today 17:13:03 Well it is functional as of now but the excetiopns are not handled so chances of failure is high 17:13:47 I should take a look one of these days. 17:14:00 is it still on that github repo? 17:14:20 yep it's there 17:14:32 rluethi: its still there but I would suggest you to wait before you spend your time on it 17:14:53 I would predict around two months before its worth takin ga look 17:15:37 if it's feature-complete it should be worth a look now. 17:15:59 rluethi: its not feature complete 17:16:06 some parts still need a lot of work 17:17:25 It works well to deploy a multi node cluster 17:17:44 so which repo should I watch, StackTrain or libvirtPOC? 17:17:56 libvirtPOC 17:18:15 k 17:18:43 so if it works well to deploy a multi node cluster, what does it not do? 17:18:59 that's pretty much all osbash does, too. 17:19:05 it does not handle exceptions like any of the libvirt exceptions 17:19:44 so if you have duplicate vms or network name already exists it will just skip that or break 17:20:02 so it isn't robust yet and the code lacks modularity 17:20:04 there are many open ends 17:20:12 I see. 17:22:10 but i will fix it soon 17:22:16 then you can try it out 17:22:30 okay. looking forward to it. 17:23:29 :) 17:23:41 :) 17:24:26 anything else you want to discuss? you know I won't be around this weekend. 17:24:55 does osbash need any attention as of now? 17:25:29 nothing from my side 17:25:54 KVM support would still be nice, but cleaning that up takes more time than I currently have. 17:27:25 what about kilo branch for osbash? 17:27:48 good point. at some point we need a kilo port. 17:27:58 dbyte? 17:29:11 wrong question? 17:30:21 I think he got disconnected 17:30:46 unpossible. he said he has the best Internet connection in the world. 17:31:05 Ikr! 17:31:56 have there been any decisions regarding kilo updates for the scripts in vancouver? 17:32:36 * sayalilunkad looking for the etherpad link 17:32:53 apologies again 17:33:51 its my web IRC client 17:34:15 which keeps on crashing 17:34:35 dbiyte: what's the plan for kilo updates for the lab-scripts? 17:35:26 you gotta be kidding me. 17:35:31 Hi 17:35:53 now I should not DC again! Apologies, its my IRC client, keeps on crashing on my old laptop 17:36:05 dbit: do you have the link for the liberty etherpad? 17:36:33 https://etherpad.openstack.org/p/liberty-training-guides-design 17:36:34 So for Kilo updates we need to start asap 17:36:45 but I would rather say that we need to fix metadata for Juno and then we are set for kilo 17:37:08 what's the deal with metadata again? it used to work. 17:37:09 ah thanks rluethi 17:37:46 its not working for Juno as of now, or atleast the last time I tried there were some issues with it 17:39:04 oh 17:39:09 IIRC, the metadata issues in icehouse were mostly due to a race in the neutron setup. 17:40:20 can you send some bug info so I can replicate the metadata problem (or recognize it when I see it) ? 17:40:46 Yes I'm sure its a small race because I have been deploying Juno since a year now and it used to work since a long time back 17:41:07 its just that when I rebuild the cluster, there is a metadata failure in the logs 17:41:17 the 'SUM' logs 17:41:23 or something is missing in there? 17:41:46 pretty sure that's new, it used to work without error. 17:41:56 is that just from current master? 17:42:16 yes 17:43:00 hmmm. okay. 17:44:09 I will confirm the bug if its metadata issue or not by tomorrow morning CEST and then we fix it by the end of this week and start working on Kilo scripts? 17:44:35 *How about starting the work on Kilo scripts by the end of next week? 17:45:11 I'd rather not commit to anything for this week, I need to take care of a few things before I fly out Friday morning. 17:45:34 but I'd like to get this thing fixed soon. 17:46:12 I am ok with end of next week 17:46:32 I would also like to take a stab at our hardware project :-). 17:47:59 rluethi: Yes for sure :D But I will be low on budget to buy some for the next couple of months 17:48:25 perfect. it's supposed to be a low-budget project anyway :-) 17:48:37 what project? 17:48:43 sayalilunkad will help, of course. 17:49:05 rluethi: yeah, she should be able to pitch in too ;) 17:49:36 what is all this excitement about? 17:49:43 sayalilunkad: we'll tell you in good time :) 17:49:57 we could have a demo "federated cloud" with multi keystone regions and a master keystone! 17:50:01 I am a part od a project I haven't heard of :D 17:50:10 ok :D 17:50:19 dbit: geez, hold your horses. 17:51:45 sayalilunkad: the project would be great fun, but it will take time which some of us may be lacking. 17:52:44 rluethi: yes, yes 17:52:53 Sounds like fun. I hope to hear about it soon :) 17:53:11 sayalilunkad: I hope to see it soon. 17:54:00 would be cool! 17:54:18 indeed. 17:54:46 though I don't know what it is ;) 17:55:18 ok anything else we need to discuss? 17:55:20 sayalilunkad: in time :) 17:55:20 hey, gotta build up the excitement. it's called marketing. 17:55:41 I'm good. Call it a day, Miss Chair? 17:55:42 nothing much on my plate 17:56:09 yep let's call it a day :) 17:56:42 bye guys, it's been a pleasure. 17:56:44 bye, talk to you'll soon! 17:56:48 :) 17:56:59 bye have a nice week 17:57:01 #endmeeting