17:01:02 #startmeeting murano 17:01:03 Meeting started Tue Mar 31 17:01:02 2015 UTC and is due to finish in 60 minutes. The chair is serg_melikyan. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:08 The meeting name has been set to 'murano' 17:01:16 * serg_melikyan is quite inaccurate 17:01:53 Hi o/ 17:02:03 hi 17:02:04 o/ 17:02:13 hi 17:02:30 Hi ^^ 17:03:12 o/ 17:04:44 #topic Action Items Review 17:05:08 hi 17:05:14 #1, sergmelikyan, send e-mail describing roadmap planning procedure 17:05:32 We have only one item for this AI Review on me :) 17:05:34 It's done :) 17:05:43 Folks, any questions regarding process? 17:06:06 henar: I believe you had some questions? I was no able to responds earlier 17:06:09 yes, it is not clear for me how to add new features.. 17:06:20 in lanchpad, by mail..? 17:07:54 henar: Step #1 - file blueprint with core of your idea in launchpad 17:08:15 yes 17:08:24 Step #2 - validate idea on nearest community meeting 17:08:47 ok, perfect I will do it so that we can discuss in next community meeting 17:08:56 Step #3 - Initiate discussions in IRC/E-mail if idea is valid, but people had number of questions regarding this feature 17:09:16 serg_melikyan: I would say that the spec review is the best place for such discussions 17:09:44 Step #4 - Start writing specification for this feature and discuss this feature in Review 17:10:28 ok 17:10:35 ativelkov, henar, agree - maybe it's better to have discussion in Spec itself 17:11:56 leaving out e-mail for technical discussions 17:12:06 And I'd say that you don't need to wait for the whole week for the community meeting just to validate the idea: ping any of us in IRC at any moment, and if the idea seems valid, just start drafting the spec. All the discussions may (and should) happen in the review of the spec. It's better to keep them in one place 17:12:37 Once more time - agree :) 17:12:54 thanks 17:13:37 What about bug scrub day? Did we get some result? 17:13:51 It's time to assign bugs and fix them! 17:14:04 katyafervent I think I fixed one bug =) 17:15:16 katyafervent: I would say it went pretty quite unfortunately - as bug liaison - do you feel that we had great bug-scrub day? 17:16:15 We definitely need to cover all High and Critical bugs in RC1 (April 9). 17:18:08 henar: I think at least merging Configuration Language implementation is going well, except CI issues :( 17:19:19 #topic CI Issues 17:19:20 CI job doesn't work, does it? 17:19:50 henar: today Horizon broke all DSVM jobs in whole OpenStack including ours 17:19:58 serg_melikyan, no, but we should have concrete aim before bug-scrub bug :) 17:19:58 henar, there is one more thing that need to be done for configuration languages: increment version in execution plans 17:19:59 ok 17:20:17 so now since it's feature freeze, we have time on bug fixing 17:20:33 katyafervent: like? 17:20:46 https://bugs.launchpad.net/horizon/+bug/1438543 17:20:47 Launchpad bug 1438543 in OpenStack Dashboard (Horizon) "wrong package name 'XStatic-Angular-Irdragndrop' in horizon/requirements.txt" [Critical,In progress] - Assigned to Rob Cresswell (robcresswell) 17:20:52 https://review.openstack.org/#/c/169132/ 17:20:52 https://review.openstack.org/#/c/169133/ 17:21:06 This is bug and two proposed fixes for issue with DSVM jobs 17:21:12 henar: ^ 17:21:23 We also have issue with Horizon and Django 1.7 17:21:33 like find first 10 bugs that should be fixed and investigating one or another areas for bugs 17:21:38 In few days before release - Horizon decided to switch to Django 1.7 :( 17:21:49 And this is also causing CI issues 17:22:17 dsvm jobs have been unlocked for a couple of hours already. 17:22:28 katyafervent: we have more than 70 bugs to be fixed in launchpad - you think we should create another list with bugs? 17:22:48 kzaitsev: awesome! 17:22:52 The wrongly-named package have been restored, and we reverified all the packages, that failed because of it I think 17:23:02 or almost all. 17:25:02 But we still have some wierd CI issues with ci jobs not being run. We have a commit, that supposedly should fix django 1.7 (it ended up being a very small change) but it is not checked by the ci =/ 17:25:13 hope we'll be able to fix the issues soon 17:25:16 serg_melikyan, no, but we need to pick and prioritize them 17:25:30 it's can be done on real-time in irc 17:25:56 I think we should do this regularly without specific date for that 17:26:13 we should pick couple of hours, go online and concentrate all our attention 17:26:14 kzaitsev: you are talking about integration jobs on Murano CI? 17:26:32 serg_melikyan: exactly them. 17:27:12 freerunner: ^ 17:28:19 serg_melikyan: ageryugin is working on this 17:29:04 katyafervent lets do it on a random day throughout the week than! =) like let's do it tomorrow for example =) I've commented on a couple of bugs during bug scrub day, that seem unreproducable. 17:29:05 serg_melikyan: As I know, the CI should already working. 17:29:17 freerunner yay! =) 17:29:56 That means we'll most likely fix all our issues soon enough. =) 17:30:16 kzaitsev: Sure! =) 17:32:14 #topic Open Discussion 17:33:07 What other questions we have to discuss today? 17:36:49 Thank you for todays meeting! 17:36:51 #endmeeting