17:00:43 #startmeeting murano 17:00:44 Meeting started Tue Apr 5 17:00:43 2016 UTC and is due to finish in 60 minutes. The chair is kzaitsev_mb. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:48 The meeting name has been set to 'murano' 17:01:01 #topic rollcall 17:01:04 o/ 17:01:07 Madhuri Kumari 17:01:17 * twm2016 is lurking 17:01:25 o/ 17:01:27 * jaugustine also lurking 17:01:41 as usual todays agenda is here https://wiki.openstack.org/wiki/Meetings/MuranoAgenda 17:01:46 o/ 17:02:26 o/ 17:02:45 o/ 17:03:03 o/ 17:04:04 o/ 17:04:07 o/ 17:04:12 o/ 17:05:08 ok I don't think we had any AI's from the previous meeting, so I'll skip right to status updates 17:05:13 #topic Status Updates 17:05:40 last week we've tagged RC2 for all our repos and RC3 for murano 17:06:04 this week, I believe on Thursday 2.0.0 is going to be released =) 17:06:37 cheers and congrats to everyone on all the work we've done to make this release happen! 17:07:36 Any chances for RC4? :) 17:07:43 Since we won't be able to publish any RC's anymore — all the bugs we find/fix at this point are going to 2.0.1 17:07:53 ah 17:08:16 ativelkov: nope =) I can dig up a letter from release team, saying that only release critical things can get merged at this point. 17:08:22 and they promised to be super picky 17:08:40 I see 17:08:49 kzaitsev_mb: meaning that we are not merging to 2.0.0 https://bugs.launchpad.net/bugs/1565577 ? 17:08:51 Launchpad bug 1565577 in Magnum UI "murano-dashboard uses wrong horizon requirement" [High,In progress] - Assigned to aimee.ukasick (aimeeu) 17:10:12 sergmelikyan: we're merging it into stable/mitaka. It just won't make it into 2.0.0 17:11:47 #link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html 17:12:28 here's the letter from Doug about the release procedure at this point 17:13:09 sergmelikyan: And it seems no one has responded to your letter about this bug. 17:13:10 I believe that they're going to tag 2.0.0 themselves, actually. Gotta ask around in #openstack-release though 17:14:21 Also — release team is going to remove tagging rights from us and during newton release procedure would be fully automatic and handeled throught openstack/releases repo 17:15:24 #link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090737.html 17:15:37 #link https://review.openstack.org/#/c/298866/ 17:16:07 don't think this would affect us in some bad way, just want to make sure, that you guys are aware of this change 17:16:19 ok. I don't think I have any more news/updates 17:16:42 It's actually super cool :) I got too many new gray hair after few isssues during releasing Murano ) 17:18:01 yep, I hope this would prevent us from ever having a pythonclient release of 200 or smth ) 17:19:20 ok, moving on 17:19:24 #topic Triaging bugs for stable branches 17:19:39 last time we agreed to have bi-weekly meetings for that 17:20:34 I've looked throught murano and murano-dashboard commits for past 3-5 weeks and have made a small list of bugs that we've fixed, that I belive are eligible for stable/liberty at least 17:20:48 #link https://etherpad.openstack.org/p/murano-stable-backports 17:21:23 here's an e-pad for those 17:22:00 +1 to each item 17:22:01 So I'll give you folks a couple of minutes to look through it =) 17:22:15 have only small concern regarding #1512710 17:22:33 is this really counts as a bug? 17:22:47 sergmelikyan: https://review.openstack.org/#/c/286363/ here is the fix 17:23:05 #link https://review.openstack.org/#/c/286363/ 17:23:15 read through description - yeah... this is a bug 17:23:50 looks like an incorrect handling of icmp there. And a rather safe thing to backport. 17:24:33 So unless there are any objections (which you can sound now or in the e-pad =)) I'm going to backport those to stable-liberty around tomorrow. 17:25:37 If any of you folks, has anything to add — feel free to add those to the etherpad. I plan to use and expand it for further meetings. 17:27:08 kzaitsev_mb: I have one. I will add it tomorrow 17:27:30 madhuri: sure! please do =) 17:28:50 One more thing — I haven't yet looked through the client and agent patches. Would probably do this for the next meeting in 2 weeks. 17:30:22 ok, looks like there are no objections for these backports and no suggestions for new ones yet. Let's move on 17:30:34 #topic Open Discussion 17:30:36 by the way which version of client will be used in Murano 17:30:51 in Mitaka? =) 17:31:25 0.8.4 is that latest 17:31:30 #link http://releases.openstack.org/mitaka/index.html 17:32:18 search for 'python-muranoclient' there. it lists 0.8.0 and 0.8.4 versions as 1st and latest 17:32:43 I actually have one more topic for open discussion 17:33:17 StanLagun and I considered moving murano-agent to independent release model 17:33:25 (much like python-muranoclient) 17:34:06 makes sense 17:34:12 +1 17:34:14 I also have to discuss something 17:34:21 the reason behind this is that 1) we always keep backward compatibility (at least expect to do it) and 2) cloud-init/DIB always installs the latest agent anyway 17:34:24 Please let me know when I can start 17:35:49 I'd say that there are no reasons to not move agent to independent model =) 17:37:12 I'll leave this under idea tag and will make a commit to governance repos early in newton to change this and would raise the question one more time to allow everyone to chime in there ) 17:37:34 #idea It seems a good idea to move murano-agent to independent release model 17:37:37 sorry, for being late, guys :( 17:37:53 madhuri: please go on with whatever questions you had ) 17:38:29 Thanks! Ok so I am adding MagnumDockerHost to deploy container on Magnum cluster 17:38:41 #link https://review.openstack.org/#/c/300825/ 17:39:05 So my question is can I add this application to magnum-app repo? 17:39:57 Sorry murano-app repo 17:40:04 that's a good question indeed ) 17:42:12 I'd probably say yes, but I'm not 100% sure =) 17:42:41 StanLagun: sergmelikyan: your thoughts ^^ 17:42:43 Can we teams' opinion on it? 17:42:50 *have 17:43:56 madhuri: seems that most guys floated away )) 17:44:09 madhuri: if you are planning to support it in th future, why not? 17:44:10 madhuri: the safe idea would be to upload it to murano-apps anyway 17:44:13 If the app is in murano-apps repo then murano team is free to make changes to it 17:44:52 Yes I will be supporting it 17:45:09 And will also discuss with Magnum team about it 17:45:18 at worst you're going to get downvoted =) 17:45:38 One thing do we have any test to test this apps? 17:45:59 I mean that anybody can submit a patch and once it it there you lose control over it 17:46:00 madhuri kzaitsev_mb So, IMHO, if this app is plugin-dependent, I would like to leave it as is. If this app is doesn't depend on plugin, it should be moved to murano-apps repo. 17:46:11 So that we can be sure that some random Magnum change is not breaking it 17:46:34 madhuri: We haven't any gate in murano-apps repo, unfortunately. 17:47:01 the plan is to have test gate at some point, we have murano-test-runner and unit tests for that. But I'm not sure when we're going to build it 17:47:02 freerunner: This app is plugin dependent 17:47:55 madhuri: tbh I doubt we're going to have that difficultintegration jobs 17:48:22 freerunner: even if the app is plugin dependant — murano-apps seems like a better place for well 17:48:26 murano apps =) 17:49:11 kzaitsev_mb: Hm. But we have some different plugins with the apps, that stores in plugin dir. 17:49:18 madhuri: to make sure that random change in magnum would not break anything in your app — you would need to test after smth is merged to magnum, not after smth is merged to murano/murano-apps 17:49:29 *stored 17:50:18 Yes but I suppose there should be test for some cross project apps 17:50:34 freerunner: having plugins in murano code-base is correct. Having example apps close to those plugins is ok. Having production-grade apps in murano code-base is not a good idea 17:51:09 madhuri: I don't think, that at this point it's time to setup such jobs, tbh ) 17:51:19 Yes agree 17:51:38 And just for one app that is not good idea to add gate job 17:52:17 Ok I will be tracking Magnum changes to make sure our app doesn't break 17:53:02 So I guess team has agreed to have this app in murano-apps. Right? 17:53:03 madhuri: I'd say that if you feel, that the app becomes big/complex enough to be moved away from murano code (and to murano-apps) — you should move it there. 17:53:04 kzaitsev_mb: So, then we need to add a corresponding README file for the app. 17:53:36 freerunner: sure, we can point to the docs of the plugin and how to install and everything ) 17:53:58 Yes I can add that 17:54:34 madhuri: I'd say, yes. I don't like the idea to have a 500-1000 LOC app in /contrib/ in murano-code 17:55:15 Ok thanks team for this discussion:) 17:55:25 I will do that soon 17:59:09 ok! Thanks everyone for the meeting and see you in #murano 17:59:21 #endmeeting