17:00:34 #startmeeting murano 17:00:34 Meeting started Tue Dec 10 17:00:34 2013 UTC and is due to finish in 60 minutes. The chair is ativelkov. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:37 The meeting name has been set to 'murano' 17:01:06 Hi Muranoers! 17:01:15 Anybody here today? 17:01:15 hi! 17:01:37 Hi ! 17:01:54 \o 17:02:09 Let's start then 17:02:15 hi 17:02:41 Let's start with AI review, as usual 17:02:48 #topic AI review 17:03:13 ativelkov to fix the security groups cidd assignment 17:03:31 This is done, the fix has been reviewed and merged to master branch already 17:03:50 ativelkov to update the blueprint on advanced networking 17:04:18 This is not done yet: too many tasks are pending on other documentation, so I could not find time to do it 17:04:28 will do next week, I hope 17:04:31 #action ativelkov to update the blueprint on advanced networking 17:04:44 Next, katyafervent to transfer api spec to docbook 17:04:47 Hi 17:05:25 currently she is away, but afaik she did it 17:05:43 Ok, that' good 17:05:55 The remaining are on you, Timur: 17:06:08 tsufiev to create launchpad issues to track bugs with security group cords and MS SQL cluster IP 17:07:13 done 17:07:27 tsufiev to implement the subnet detection routing in the dashboard 17:07:49 Is this done as well? 17:07:53 also done, finally implemented it today 17:07:58 Good! 17:08:14 Ok, let's discuss the upcoming 0.4 then 17:08:20 #topic release 0.4 17:08:42 tsufiev, please share an update 17:09:00 we have fixed all bugs in Metadata Repository (that are known) 17:09:21 we have a code freeze today, also 17:09:45 Is it already active? 17:09:51 so right now we trying to ensure that nothing broken in 0.4 remains 17:10:22 we're currently testing MS SQL Cluster deployment - it seems, that some port were open previously by default 17:10:26 I mean, is the stable 0.4 branch is created? 17:10:33 and now we need to specify them manually 17:10:43 not yet, i'l do it in an hour or so 17:11:07 Ok 17:11:29 #info code freeze for 0.4 scheduled for today, will occur in about 10 am PST 17:11:51 tnurlygayanov_: can you comment on the bugs known in 0.4 by far? 17:12:26 so, we hova no critical issues in the release 0.4 17:12:59 #info No critical issues in 0.4 discovered yet 17:13:00 and we plan to fix some major features during the next few days 17:13:26 what do you mean by major features? Is something not implemented yet - or you mean bugs? 17:13:26 tnurlygayanov_: are they related to fuel? 17:13:40 all automated tests, which we executed on our test lab are passed for this release 17:13:57 or? sorry, major bugs ) 17:14:31 Ok. We need to decide if we really want to fix them or document as known issues and proceed. 17:14:36 tnurlygayanov_: do you mean major bugs in murano itself or fuel integration issues? 17:14:55 Usually code freeze means that check-ins are allowed only for critical bugs 17:15:06 So, I would suggest 17:15:12 in Murano, yes. Need to fix and merge commti for key pair, for example 17:15:28 to either escalate the status of the bugs to "critical" - or to postpone the fix till 0.4.1 17:15:32 it does not work now ) 17:16:20 ok, we will review bugs descriptions and will change priorities and mailstones for all bugs 17:16:28 #info some major bugs remain. Some of them may be escalated and fixed before the release, others will remain as known issue 17:16:40 afair, key pairs wasn't specified as 0.4 deliverables... 17:17:23 is it a critical feature? 17:17:38 yup. Also, the linux images which we use for this Apps usually allow root login via the horizon console 17:17:50 So, I don't think that they are really crtitical 17:18:06 But it is up to you to decide, as you are the owner of the release 17:18:38 it is small non critical feature, but implementation of linux services without this feature is incomple 17:18:44 i'd prefer to postpone them until 0.4.1 17:18:57 Anyway, we need to schedule a service release 0.4.1 which will fix these known issues and will add role-based access control to Simplified Metadata Repository 17:19:04 ok, no problem, let's move it to 0.4.1 17:19:23 good :) 17:19:35 #agreed to postpone kypair fix till 0.4.1 17:19:48 joel_c: when do we expect 0.4.1 to land? approximately? 17:20:31 Depends on the feature set. If this is just bug fixes + RBAC, then about mid january 17:21:02 May be earlier, but long holiday seasons tend to consume time 17:21:13 ativelkov: sounds good. 17:22:23 Is that all what we have for 0.4, tsufiev? 17:23:12 ativelkov: almost forgotten. Also all needed heat patches were ported to havana - to make ms sql cluster work 17:23:37 now i think that's all 17:23:47 I thought that allowed address pairs is not ported to havanna 17:24:08 At least yesterday I saw it in their master, but not in stable/havana 17:24:33 i rebased patches made from master onto stable/havana 17:24:53 dteselkin applied it today on our lab, it works 17:25:03 Ah, I see 17:25:30 but the official Heat does not have it in their Havanna release 17:26:18 This means that our implementation of MS SQL Cluster will work either on the latest trunk of the Heat - or on patched deployment of Havana 17:26:32 but not on the out-of-the-box Havana 17:26:46 yes, exactly 17:26:59 This is fine, but we need to track such limitations carefully 17:27:15 tsufiev, this should get into the release notes of 0.4 17:27:47 ativelkov: ok, will add it 17:27:53 #action tsufiev to ensure that allowed_ip_addresses limitation gets its way into release notes of 0.4 17:28:08 Ok, let's move on 17:28:20 #topic release 0.5 planning 17:29:09 So, we have completed vision for DSL design 17:29:29 some of it are summarised in ether pad at https://etherpad.openstack.org/p/MuranoMetadata 17:30:02 We are going to complete the pad this week and move the final definition to wiki 17:30:25 And then create a series of blueprint to implement the minimal feature set of this spec in the 0.5 17:31:21 Afaik, stanlagun is doing some PoC with the engine for the new DSL right now 17:31:30 stanlagun, can you share some update on this topic 17:31:38 ? 17:32:14 Well it is going not so fast as I hoped 17:32:22 because of many meatings we have 17:32:42 but I expect it to be completed by next comunity meeting 17:33:12 What set of functionality may we expect? 17:34:12 #info new-DSL engine is being prototyped. ETA - next tuesday 17:34:14 Currently I'm trying to implement some workflow engine prototype that can handle simultenious task execution. The goal is also to implement classes for underlying type system. That is a DOM model for the DSL 17:34:56 #info prototype will have a DOM model with parser and a simple workflow engine 17:35:16 stanlagun what about Mistral? Are we going to use it for the workflows? 17:35:18 As a result it will be possible to declare and implement workflow for some Hello-World class 17:36:26 No. Mistral is yet far from our minimal requirements. But it is moving fast and I'm present on all of their meetings to be sure it is going in good direction. I expect that we can start using Mistral by 0.6-0.7 timeframe 17:36:47 Thanks 17:37:11 #info PoC of the new workflow engine is not going to use Mistral. We will migrate to Mistral at later stages of the product 17:37:51 Also, there was a long discussion in mailing list about HeatR 17:38:23 It turned out that there is a strong community demand for a generic unified Metadata Repository 17:38:45 which will be able to store various kinds of cataloged metadata 17:39:18 The consensus in the list was reached that Glance should become such a reporsitory 17:39:42 Is it final? 17:39:50 Of course not 17:40:14 But we should expect that it may come true 17:41:03 So, Murano should 1) be prepared for such changes and make a good use of the new repository if it emerges, 2) contribute our own ideas and experience 17:41:29 In general, this would be really beneficial for all the projects in the community 17:42:19 Anyway, until the final solution is made, we should demonstrate our own achievements in this area to the community 17:42:43 It is suggested to present our simplified metadata repository 17:43:09 tsufiev has recorded a short video demo, gokrokve_ will send it to a mailing list 17:45:09 Ok, that's all we have for 0.5 for now 17:45:20 #topic Open Questions 17:45:33 Does anybody have any questions? 17:46:38 Ok, then I have a proposal 17:47:14 As release 0.4 is moving to the delivery, I'd like to clean up the remaining bugs which we have at launchpad 17:47:31 Some of them are outdated, some need to be re-estimated 17:47:44 So, I suggest to have a standard bug-scrub procedure 17:49:14 I suggest to send an invitation to a mailing list - so all may participate in this procedure 17:50:01 We will then schedule a convenient timeslot and all do a bug scrub in #murano channel 17:50:16 Sounds good 17:50:57 currently we have 69 open bugs, so it should not take too long 17:51:38 lots of them are in "fix committed" state, so they are likely to be closed with the release of 0.4 17:51:53 Any objections? 17:52:23 #agreed have a bug-scrub procedure to clean-up the launchpad issues after the release 0.4 goes public 17:52:41 #action ativelkov to send a bug-scrub invitation 17:52:54 Ok, that's all I had. Any other questions? 17:54:10 Then let's finish the meeting 17:54:15 #endmeeting