17:02:59 <ruhe> #startmeeting murano
17:03:00 <openstack> Meeting started Tue May  6 17:02:59 2014 UTC and is due to finish in 60 minutes.  The chair is ruhe. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:03:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:03:04 <openstack> The meeting name has been set to 'murano'
17:03:13 <ativelkov> o/
17:03:15 <ruhe> #link https://wiki.openstack.org/wiki/Meetings/MuranoAgenda#Agenda
17:03:26 <gokrokve> Georgy Okrokvertskhov
17:03:32 <ativelkov> Alexander Tivelkov
17:03:40 <sjmc7> Steve McLellan
17:03:43 <ankurrr> Ankur RIshi
17:03:46 <btully> Brian Tully
17:04:15 <dteselkin_> Dmitry Teselkin
17:04:16 <ruhe> i wonder where's tsufiev, sergemenlikyan, katyafervent ?
17:04:42 <ruhe> ok, let's proceed
17:04:50 <ruhe> #topic Action Items Review
17:05:12 <ruhe> there was an AI for me: ruhe to create release-0.5 branches
17:05:40 <ruhe> murano-api and murano-dashboard have a branch release-0.5
17:05:47 <ruhe> #info murano-api and murano-dashboard have a branch release-0.5
17:06:22 <ruhe> tags are not cut yet because all the latest critical bug fixes landed today
17:06:35 <ruhe> will discuss release in the next topic
17:06:43 <ruhe> #topic Release status
17:06:51 <ruhe> #link https://launchpad.net/murano/+milestone/0.5
17:07:05 <ruhe> #info all the blueprints are implemented
17:07:26 <ruhe> #info critical/high priority bugs are fixed
17:08:05 <ruhe> i'd like to allocate one more day for QA procedures and if everything's ok release Murano v0.5 tomorrow
17:08:13 <sjmc7> woo!
17:08:19 <tsufiev> hi
17:08:56 <ruhe> what do you folks think about releasing 0.5 tomorrow? any concerns?
17:09:31 <ruhe> tsufiev: hi! better later than never ;)
17:09:55 <tsufiev> sorry, problems with provider, had to switch to the mobile one
17:10:13 <gokrokve> I think it is ok to have a release tomorrow
17:10:29 <gokrokve> QA team, please do another round of testing
17:10:53 <gokrokve> Please check that existing converted apps are deployable
17:10:53 <ruhe> not only QA, but everyone is encouraged to test the release :)
17:10:58 <gokrokve> Sure
17:11:11 <ruhe> #info Murano 0.5 to be released on May 7th, 2014
17:11:47 <ruhe> #topic Review roadmap
17:11:54 <ruhe> #link https://wiki.openstack.org/wiki/Murano/Roadmap
17:12:11 <ruhe> sjmc7: i've added your items to the roadmap
17:12:16 <sjmc7> thanks ruhe
17:12:46 <gokrokve> I have two more items to add
17:13:17 <sjmc7> and ruhe - you said priorities will be set during the openstack summit?
17:13:21 <gokrokve> Autoscaling support in Murano (HOT template with autoscaling, integration with Ceilometer)
17:13:33 <gokrokve> Boot from Volume support
17:13:52 <gokrokve> I think yes, we need to sit down and discuss the priorities
17:14:01 <gokrokve> We can do this on summit
17:14:10 <gokrokve> I hope we will have a room for that
17:14:36 <ruhe> sjmc7: i think that all the features you listed are valid and need in the next release. details of the technical implementation might be altered by our design sessions
17:14:48 <sjmc7> great
17:14:59 <ruhe> gokrokve: could you please add those to the roadmap?
17:15:16 <gokrokve> Sure. I think we have blueprint for these features
17:15:22 <gokrokve> Its about events
17:16:01 <ruhe> sjmc7: we don't have an official place for our design sessions, but i hope ttx will help stackforge projects to find such a place
17:16:16 <sjmc7> ok. i'll keep an ear to the ground
17:17:23 <ruhe> but, before we all get together on the summut, it'll be good to review each item from the roadmap and ask questions to submitter (if needed) to save precious time on summit
17:19:18 <gokrokve> Sure. We can start discussion on roadmap items in ML
17:19:22 <ruhe> just to make sure that everyone is familiar with the procedure. page with the roadmap is open of edit to everyone. the only requirement - is to notify the team about changes you've made (or intent to) on the weekly meeting
17:19:31 <gokrokve> To have broader audience.
17:20:08 <ruhe> so, we shifted to the next topic
17:20:17 <ruhe> #topic Plans for the design summit in Atlanta, GA
17:20:32 <ruhe> #link http://junodesignsummit.sched.org/
17:20:52 <ruhe> we have to must-attend sessions :)
17:21:05 <ruhe> #link http://junodesignsummit.sched.org/event/b7f067ff055ff7db9c92867f3febe1d9
17:21:13 <ruhe> #link http://junodesignsummit.sched.org/event/556d10915a1a0a2f1aee3ba286826b60
17:22:13 <ruhe> ah, there's one more
17:22:25 <ruhe> ativelkov: can you please give a link for your design session?
17:22:35 <ativelkov> moment
17:22:58 <ativelkov> #link http://junodesignsummit.sched.org/event/b0e1f0cbefffa942e276f1add9f85d03#.U2kaa16nDWU
17:23:28 <ruhe> ativelkov: and the link to your design document, please
17:24:30 <ativelkov> #link https://docs.google.com/document/d/1tOTsIytVWtXGUaT2Ia4V5PWq4CiTfZPDn6rpRm5In7U/edit?usp=sharing
17:25:23 <ruhe> meanwhile, we can follow established procedure and prepare an etherpad with our discussion plans for the summit
17:25:40 <ruhe> here is an etherpad, please add items for the summit:
17:25:45 <ruhe> #link https://etherpad.openstack.org/p/murano-juno-design-summit
17:26:29 <ruhe> would someone propose some topics right now?
17:27:36 <ruhe> i'll send a link to ML to invite those, who are not present at the moment
17:27:51 <igormarnat_> May I propose number 2, 3, and 4 from out roadmap?
17:27:57 <igormarnat_> Align with Heat
17:28:02 <igormarnat_> Ceilometer integration
17:28:07 <igormarnat_> Use TOSCA (to be discussed)
17:28:14 <ruhe> igormarnat_: sure, please add those to the etherpad
17:28:21 <sjmc7> yes, the heat software deployment stuff is of interest to me as well
17:29:44 <ruhe> sjmc7: when do you guys arrive to Atlanta? it'll be nice to gather together on Monday
17:30:02 <sjmc7> it's just me, unfortunately - i arrive monday morning around 9
17:31:27 <ruhe> sjmc7: good. than we can exchange our contacts later to catch at some place. actually, only gokrokve has a US number :)
17:31:48 <sjmc7> :)  email works too, but yeah, we'll figure something out
17:32:27 <ruhe> any other sessions which could be useful for murano team to attend?
17:34:31 <ruhe> ah
17:34:36 <ruhe> almost forgot it
17:35:10 <ruhe> next murano meeting falls on 1PM at Atlanta. it's time when we'll have our cross-project sessions
17:35:25 <ruhe> so i propose to cancel meeting on the next week
17:35:50 <ruhe> please +1/-1
17:35:59 <ativelkov> +1
17:36:01 <sjmc7> +1
17:36:02 <igormarnat_> +1
17:36:17 <sjmc7> http://junodesignsummit.sched.org/event/3fd9d276d9dd059c54cde3007c178a06#.U2kdQ_ldV4s might be interesting, about heat software orchestration
17:37:12 <ruhe> #info weekly meeting on May, 13th is cancelled
17:38:32 <ruhe> #topic Open discussion
17:39:16 <ruhe> it might be a good time to discuss one of blueprints :)
17:40:15 <sjmc7> do you have one in mind, ruhe?
17:41:23 <ativelkov> I would like to announce a little change in engine which may simplify the debugability
17:42:03 <ativelkov> #link https://review.openstack.org/#/c/92358/
17:42:24 <ativelkov> This is a bugfix for some concurrency issue, but it adds two important logging messages
17:42:45 <sjmc7> more logging is definitely good
17:43:42 <ativelkov> The log will now contain the lines looking like this: %green_thread_id%: Begin execution %method_name%
17:43:56 <ativelkov> and %green_thread_id%: End execution %method_name%
17:44:02 <sjmc7> i've been adding logging here and there as well as we have found issues
17:44:29 <ativelkov> So, this will allow to understand which MuranoPL methods are being executed
17:45:17 <tsufiev_> ativelkov: have you already told about our today idea?
17:45:39 <ativelkov> Also, tsufiev_ and me got a very promising idea about buidling a full-fledged debugger for MuranoPL
17:45:43 <sjmc7> oo!
17:46:29 <tsufiev_> it is still in draft state :)
17:46:38 <tsufiev_> but looks at least doable
17:46:46 <sjmc7> in some places i think improving the way exceptions are raised would be a big help, to have more information about what's being executed
17:47:03 <sjmc7> currently it's very generic
17:47:16 <ativelkov> This may require quite a lot of work (mostly related to stopping/pausing the execution, step-in/step-over, breakpoints etc), but some serious improvements can be made even now
17:47:54 <ativelkov> For example, when reporting an exception, we may return the line number for the expression being executed
17:48:02 <ativelkov> line - in MuranoPL code
17:48:14 <sjmc7> yeah, that kind of thing would be easy to do now
17:48:20 <sjmc7> well, easy-ish
17:48:35 <ruhe> ativelkov: tsufiev_ : will there be a plugin for pycharm? ;)
17:49:03 <tsufiev_> ruhe: perhaps after juno ;)
17:49:12 <ativelkov> ruhe: we think of a web-based debugger, right in browser
17:49:33 <ativelkov> but it will require tons of work just to build its APIs and UI
17:50:21 <tsufiev_> actually, more on API side
17:50:51 <tsufiev_> on UI a couple of ajax-functions here and there would be sufficient
17:52:04 <tsufiev_> it will be just a proxy passing commands to API and receiving results back... but if we are to implement stack frames inspection, watching some variables, it will of course much harder...
17:52:58 <tsufiev_> anyway, even web-based gdb will be a huge step forward :)
17:54:49 <ruhe> the only concern i have about all this - is the amount of work you guys will need to do. and how it compares with other items from the roadmap in terms of priority
17:55:49 <tsufiev_> yeah, i have also a moderate-sized list of cool things to change in dynamic UI
17:55:55 <ativelkov> This is definetly not the highest priority
17:56:13 <ativelkov> What I want to do is to design this thing in details
17:56:19 <ativelkov> and leave the design as blueprint
17:56:26 <ativelkov> Somebody may pick it later
17:56:41 <ruhe> ativelkov: that's a nice start
17:57:46 <ruhe> 3 minutes left, anything else?
17:57:52 <tsufiev_> https://blueprints.launchpad.net/murano/+spec/muranopl-stacktrace we can start with this blueprint
17:58:55 <ruhe> tsufiev_: this one i would definitely support
17:59:43 <tsufiev_> ruhe: i think we can add file:line info to exceptions in the nearest future, and other big debugging features a bit later
17:59:57 <ativelkov> +1
18:00:29 <ativelkov> we are out of time folks
18:00:40 <ruhe> all, right. we need to wrap up :)
18:00:45 <ruhe> thanks everyone!
18:00:48 <ativelkov> thanks
18:00:52 <tsufiev_> :)
18:00:57 <ruhe> #endmeeting