18:05:43 #startmeeting savanna 18:05:44 Meeting started Thu Oct 3 18:05:43 2013 UTC and is due to finish in 60 minutes. The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:05:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:05:48 The meeting name has been set to 'savanna' 18:05:55 #topic Agenda 18:05:55 #info Action items from the last meeting 18:05:55 #info Feature freeze 18:05:55 #info News / updates 18:05:55 #info Roadmap cleanup / update 18:05:56 #info Design track sessions 18:05:56 #info General discussion 18:06:06 #topic Action items from the last meeting 18:06:14 #info http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-09-26-18.03.html 18:06:51 there was two action items from the last meeting about moving monitoring and next-gen arch to the next release 18:06:55 both done 18:07:09 #topic Feature freeze 18:07:25 #link http://lists.openstack.org/pipermail/openstack-dev/2013-September/015800.html 18:07:35 it's today 18:07:49 so, I'll push rc1 tag in several hours 18:08:16 a have a question about it: do we plan to stop implement new features right now? And what will be with the CRs n the review? 18:08:22 and it's time to test everything 18:08:48 most of the reviews are not new features 18:08:58 we have one more week before code freeze 18:09:11 ok, that's good 18:09:19 and feature freeze exceptions could be request 18:09:24 Regardin data locality feature, does FF means that it will not be included to 0.3? 18:09:42 I hope it'll be 18:10:07 alazarev, let's discuss it when it'll be finished and ready for review 18:10:19 SergeyLukjanov, ok 18:10:43 ok, let's move on 18:10:51 #topic News / updates 18:10:58 folks, please 18:11:28 #info multi-tenancy resurrected after applying conductor 18:11:39 We're working on integrating service still making good progress on the HDP side. Hoping to be done early next week 18:12:17 #info Savanna Dashboard is now using python-savannaclient 18:12:23 We're also looking in detail at Neutron support and what the current gap is. 18:12:24 no code duplication left there 18:12:35 I think that the EDP UI is close to finished. Currently 1 outstanding review and a couple of bugs. I'm currently trying to do some end-to-end testing. I'll add any bugs that I find. 18:13:07 great, looks like EDP is near to be done 18:13:16 I mean 0.3 scope 18:13:16 this week I was working on EDP, triyed to find some bugs, and there were found :) also had adisscussions with our qa, They started implementing integration tests 18:13:55 crobertsrh, today I'm was not able to delete job object from the UI 18:14:08 were there any job executions that were based on that job? 18:14:12 I will investigate. 18:14:17 aignatov_, let's discuss it in general discussion section 18:14:22 any news/updates? 18:14:24 hmm, it seems yes 18:14:36 we 18:14:46 Data locality is nearly done, it was working yesterday and I spent today on resolving conflicts after rebase (mostly with concurrent ssh) 18:14:47 I got what you mean, crobertsrh :) 18:14:55 We're glad to see the multi-tenancy support get resolved. 18:15:06 ErikB, yeah, me too :) 18:15:39 When can we discuss Neutron state / support? 18:15:58 general discussions sections I think 18:16:03 I'll add point to agenda before general discussion for it 18:16:11 thanks 18:16:12 for today I mean :) 18:16:22 any more news? 18:16:34 #topic Roadmap cleanup / update 18:16:42 should we update roadmap? 18:16:58 any thoughts from my side 18:17:06 #link https://wiki.openstack.org/wiki/Savanna/Roadmap 18:17:35 ok 18:17:38 #topic Design track sessions 18:18:03 as you all know, we are now in Incubator 18:18:12 +1 18:18:15 and so we have 4 time slots at design summit 18:18:38 Friday (November 8) 18:19:23 November 8 (for clients that like smiles) 18:19:28 #link http://summit.openstack.org 18:19:44 ^^ here you can propose sessions for design summit 18:19:56 with topic "savanna" for us 18:20:11 and then we should decide which talks will be there, right? 18:20:24 there -> in the summit 18:20:27 we'll merge sessions in 4 slots at the end of the next week I think 18:20:36 ok 18:21:03 here is some info about design track 18:21:18 #link https://wiki.openstack.org/wiki/Summit 18:21:44 so, I'm looking for your suggestions 18:22:07 any questions? 18:22:43 Suggestion for design track is to how to best spawn a large cluster 18:23:03 I've already added scalable savanna session 18:23:10 great. 18:23:13 please, comment on it to add details 18:23:18 ok 18:23:40 #link http://summit.openstack.org/cfp/details/145 18:24:55 #topic Neutron support 18:25:30 We are actively looking at Neutron support for a customer. 18:25:33 Nikita, please, write the current status of Neutron support 18:26:04 What we can do know with Neutron is tell nova to assign a specific network 18:26:22 ErikB, yep, do you read the Ruslan's answer in ML? 18:26:23 the requirement, as one would expect is to leverage Neutron without requiring floating/public ip addresses. 18:26:37 SergeyLukjanov - yes 18:27:11 ErikB, as Ruslan said it will not work in case of HA or at least will be hard to implement 18:27:25 I've replied to Jon today. There might be issues in HA mode deployment 18:27:55 Yes, agreed - although I don't understand the details yet. HA is a separate topic I think and providing basic Neutron support is top of mind for us. 18:27:55 it's ok to add a flag 'use-netns' to use network namespaces in case of non-HA installations 18:27:56 the actual difficulty is there in no access to private network of vms 18:28:19 Nikita - there is through netns 18:28:56 using a paramiko proxy you can ssh to the instance on their private network through the controller (where Savanna will presumably be deployed). 18:29:16 netns will work only when savanna is on the same host with quantum router 18:29:45 ruhe - yes, that is the only viable option to deploy Savanna with Neutron right? 18:30:08 ErikB: except using floating IPs for provisioning 18:30:23 Yes, but that negates Neutron completely. 18:30:40 The reason someone is using Neutron is for security - at least in large part. 18:30:48 afaik the router is tenant specific, but networks might be not 18:30:49 yep, and for HA installation netns usage will break even floating IPs, so, it could be implemented only as option 18:31:32 Nikita - yes you are correct routers are tenant specific I believe as well. 18:32:16 Regardless, we will be implementing this in the short term and if we can get it into 0.3 - even if it is not the final version of Neutron support, it would be a good start. 18:32:40 routers can be tenant or non-tenant specific 18:32:58 but tenant routers make sense in most scnearios 18:33:20 it's a good solution. I just want to make it clear -it'll require advanced ha configuration 18:33:45 Sergey - is HA on the agenda for design summit? 18:34:02 ErikB, if you'll be able to push this patch early next week than we can merge it (should be wrapped with flag) 18:34:15 ErikB, the same topic - scalable savanna 18:34:19 regarding neutron, do we know exactly how to choose namespace for netns? 18:34:27 we should discuss new architecture 18:34:37 scalable, distributed and HA-friendly 18:34:38 Sergey - we will look at what we can accomplish in the short term for this. 18:34:51 and Neutron and Heat and etc. -friendly too :) 18:35:06 yeah, great 18:35:07 alazarev - we'll have to explore that issue. there should be a way to map from network to router (we hope ;) ) 18:35:20 and from router to namespace 18:35:36 (the latter part is much easier :) ) 18:37:01 jmaron, will see, it could be rather nono-trivial 18:37:06 ok, netns enabling flag for Neutron support could be merged into the 0.3 18:37:36 any things to discuss on this topic? 18:37:41 alazarev -true. we just have to explore and see 18:38:02 in the short term we may be able to simply configure 18:38:32 it'll be great to have this patch in0.3 18:38:41 yep, absolutely 18:39:03 let's move to the general discusion 18:39:15 #topic General discussion 18:39:27 folks, please 18:40:56 we're nearing the release date. it's time to work on documentation, especially forEDP. who's willing to participate? 18:40:58 nothing to discuss today?^) 18:41:22 we need volunteers from all sub teams :) 18:41:32 I can create docs for REST API samples 18:42:46 trevor, could you help aignatov with writing EDP docs? 18:42:58 I can help with any UI documentation required 18:43:34 crobertsrh, great, I think it'll be good to add some descriptions for EDP-related workflows on UI 18:43:42 for end-users 18:43:54 lets create a bp with work items 18:44:10 ruhe, yeah, good point 18:44:38 Is there a particular format or template to conform to? 18:44:39 probably should make sure to look at docs across the board to make sure there are no gaps 18:44:43 tmckay, howdy :) 18:44:52 sorry, I forgot completely 18:44:54 also we should have a clear description what EDP is 18:45:18 tmckay, meeting logs http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-10-03-18.05.log.txt 18:45:29 * tmckay looks 18:45:39 tmckay, could you please help aignatov with writing EDP-related docs? 18:45:46 sure 18:45:51 we're discussing state of docs and gaps in them 18:45:59 tmckay, great! 18:46:09 thx, tmckay, will work together 18:46:34 so, aigantov and tmckay will cover EDP docs for backend part, crobertsrh for UI part 18:46:55 are there anything more that should be done for 0.3 docs? 18:47:24 crobertsrh: we don't have established formats. I think that the general rule should be that all docs should be consistent 18:47:51 I think it could be the action item to the next week: "find the gaps in docs for 0.3 and fix that" 18:47:57 yep, no templates 18:48:24 there's a guide how-to write docs 18:48:49 #action all to find and fix gaps in the docs for 0.3 release 18:49:39 who would like to help coordinate doc activity? 18:50:00 me 18:50:18 Looks like savanna-dashboard has no existing "docs" Is that correct? 18:50:22 ruhe, great thank you 18:50:31 crobertsrh, only installation and dev guides 18:50:38 fyi, aignatov_, I am PTO tomorrow but will be back on Monday 18:50:43 re docs 18:50:46 crobertsrh:nope, just user's guide giving general guildelines 18:51:16 tmckay, no problem, docs activiti could be started on the next week 18:51:31 Ok. Should I add my new doc to the savanna/doc/source/horizon tree, or should something be added to the savanna-dashboard project itself? 18:51:39 additionally, it'll be great to add unit tests :) 18:51:47 this discussion can just take place in #savanna, no need to figure it all out here 18:51:53 crobertsrh, to the savanna repo 18:51:59 SergeyLukjanov, also, I would remind anyone who hasn't to check blueprints too as part of the doc effort 18:52:17 yeah, tmckay, good point 18:52:36 #action all to check their blueprints and update their descriptions and statuses 18:53:42 anything more to discuss? 18:54:27 #action ruhe to create root documentation blueprint and add work items to it 18:56:18 ok, one more minute 18:56:28 #info JFYI you can always use openstack-dev@lists.openstack.org mailing lists and #savanna irc channel to find us and ask your questions 18:57:31 ok, thank you all! 18:57:36 #endmeeting