17:00:37 <sergmelikyan> #startmeeting Murano
17:00:37 <openstack> Meeting started Tue Dec 17 17:00:37 2013 UTC and is due to finish in 60 minutes.  The chair is sergmelikyan. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:38 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:41 <openstack> The meeting name has been set to 'murano'
17:01:22 <sergmelikyan> Welcome to Murano Community Meeting :)
17:01:39 <sergmelikyan> Agenda:
17:01:56 <sergmelikyan> 1) Action Items Review
17:02:03 <sergmelikyan> 2) Status of release 0.4
17:02:13 <sergmelikyan> 3) Plans for release 0.4.1
17:02:18 <sergmelikyan> 4) Plans for release 0.5
17:02:30 <sergmelikyan> 5) Metadata Service
17:02:47 <sergmelikyan> #topic Review AIs
17:03:18 <sergmelikyan> First action item is assigned to ATivelkov
17:03:30 <sergmelikyan> > Update the blueprint on advanced networking
17:03:50 <ATivelkov> not done yet
17:04:06 <ATivelkov> too much activities on other tasks
17:04:31 <sergmelikyan> Ok, but I believe that you had finished https://wiki.openstack.org/wiki/Murano/Specifications/Network_Management
17:04:44 <ATivelkov> will try to do it on next week as time allows
17:05:29 <sergmelikyan> We have two more AI, and second one also is assigned to ATivelkov
17:05:32 <sergmelikyan> > send a bug-scrub invitation
17:05:32 <ATivelkov> its old, needs to be updated
17:06:10 <ATivelkov> this will be done adter 0.4 is finally released
17:06:23 <sergmelikyan> Ok :)
17:06:59 <sergmelikyan> I believe third one is also will be done after finishing with 0.4:
17:07:04 <sergmelikyan> > ensure that allowed_ip_addresses limitation gets its way into release notes of 0.4
17:07:38 <sergmelikyan> Looks like there are no more AI's. Moving to the next topic...
17:07:48 <sergmelikyan> #topic Status of release 0.4
17:08:06 <sergmelikyan> tsufiev_, can you share release status?
17:09:14 <katyafervent> I can tell some news)
17:09:47 <katyafervent> We have code freeze now and preparing a release
17:10:19 <katyafervent> And we created new release-0.4 branches
17:10:46 <tsufiev> sorry guys, forgot about meeting
17:11:08 <tsufiev> so far we have fixed all critical bugs
17:11:12 <katyafervent> tsufiev, Hi! We are discussing release-0.4
17:11:37 <tsufiev> there is currenlty 2 known issues i'm aware of:
17:12:26 <tsufiev> 1. web farms don't deploy because of they use Neutron LBaaS, which we haven't on our labs
17:13:01 <tsufiev> 2. We had to open all tcp & udp ports in range 1024-65535 for MS SQL Cluster to deploy properly
17:13:11 <sergmelikyan> >which we haven't on our labs
17:13:42 <sergmelikyan> How it is a known issue? Or we assuming that feature does not work, if it was not tested on labs?
17:14:30 <gokrokve> Why we can't use LB from Heat?
17:14:30 <tsufiev> sergmelikyan, afaik, we don't know whether it deploys or not
17:14:31 <tnurlygayanov> yes, it is not tested and we will describe it in known issues
17:15:37 <tnurlygayanov> We con not use simple LB from Heat because we can not maanage neutron networks for it
17:15:38 <sergmelikyan> tsufiev, we does tested with DevStack :)
17:15:57 <tsufiev> sergmelikyan, you mean, it actually works?
17:16:22 <sergmelikyan> gokrokve, actually it is LB from Heat, but based on Neutron, raise then AWS::LoadBalancing::LoadBalancer
17:16:28 <tnurlygayanov> default Heat LB does not work properly with different neutron configurations
17:16:38 <gokrokve> make sense
17:16:50 <gokrokve> so it should be properly documented
17:17:13 <tsufiev> gokrokve, yes, guess should document it more thoroughly
17:17:15 <sergmelikyan> tsufiev, was working when I was testing :) But may be it is wise to mark as Known Issue if features was not tested thoughtfully
17:17:39 <katyafervent> yes, let's keep it for 0.4.1
17:17:49 <sergmelikyan> tsufiev, thx for details
17:17:55 <tsufiev> sergmelikyan, yes it is safer to say it won't work and it works than say it does and it doesn't :)
17:18:15 <tsufiev> so, this is all about known issues
17:18:37 <tsufiev> we're postponed a bit release date
17:18:42 <tsufiev> to 20th December
17:19:26 <tsufiev> to ensure everything is ok (besides known issues)
17:20:20 <tsufiev> am i supposed to say something more :)?
17:20:47 <katyafervent> What's next?
17:21:08 <sergmelikyan> tsufiev, thx for status update
17:21:17 <tsufiev> sergmelikyan, np :)
17:21:19 <sergmelikyan> #topic Plans for 0.4.1
17:21:42 <sergmelikyan> We have plans to release next bug-fix version right after 0.4
17:22:18 <tnurlygayanov> yes, also we plan to implement basic RBAC in this release
17:22:33 <sergmelikyan> Currently we doen't have dedicated release owner for 0.4.1, but I believe tsufiev can share some thoughts about what we postponed for 0.4.1
17:22:38 <katyafervent> And what about estimation&
17:22:50 <katyafervent> Is it end of January?
17:22:57 <tnurlygayanov> yes, Jun, 2013.
17:23:32 <katyafervent> Great
17:23:49 <tnurlygayanov> *January  ))
17:24:17 <sergmelikyan> We are talking about estimates for RBAC implementation or release date? )
17:24:26 <katyafervent> And we already work on release 0.5
17:24:32 <tsufiev> sergmelikyan, we plan to fix at least those 2 known issues in 0.4.1
17:25:43 <sergmelikyan> Great!
17:25:57 <tsufiev> also there is a bunch of minor improvements in murano-repository which don't fix any critical issue, but improve overall UX
17:26:06 <sergmelikyan> #topic Plans for release 0.5
17:26:12 <tsufiev> various (more concise) error messages etc
17:26:34 <sergmelikyan> sorry, i thought we finished with 0.4.1 %)
17:26:44 <sergmelikyan> Any other news about 0.4.1?
17:27:02 <tsufiev> np, i've finished already with 0.4.1
17:27:42 <sergmelikyan> Let's move to the release 0.5
17:28:34 <sergmelikyan> We designing new Metadata Service for release 0.5, working on both storage and processing.
17:28:34 <tsufiev> i can share my part of knowledge about 0.5, it is UI-related
17:29:11 <sergmelikyan> tsufiev, a bit later, if you don't mind? :) I will try to share about implementation details :)
17:29:24 <tsufiev> sergmelikyan, ok
17:29:36 <sergmelikyan> We have very ambitious plans for Metadata Service in release 0.5 )
17:29:46 <katyafervent> That's true!
17:30:42 <katyafervent> So will we have special git repository for a new metadata?
17:31:05 <sergmelikyan> We plan to separate storage related part of our Metadata Service and move it to Glance. We working on https://etherpad.openstack.org/p/MetadataRepository-API this alongside with Glance team.
17:31:08 <stanlagun> metadata or metadata service?
17:31:10 <sergmelikyan> git repository?!
17:31:23 <tsufiev> katyafervent, omg, another one?!
17:31:27 <tnurlygayanov> one more repo please ))) I belive no )
17:31:45 <stanlagun> Heat has repo for template examples
17:32:26 <sergmelikyan> I don't think we need a new git repository. We don't create a new service ) We plan to improve Glance.
17:32:31 <stanlagun> Comunity-provided applications for catalog deserve to have own repository
17:33:00 <stanlagun> repo for metadata, not the service
17:33:16 <sergmelikyan> More details about implementation, some rough thought you can find by the link above.
17:34:08 <sergmelikyan> stanlagun, I don't think that we need repository metadata now, and certainly don't need for service
17:34:19 <sergmelikyan> *repository for metadata
17:34:48 <sergmelikyan> If someone will find it's useful simple github repository will be enough.
17:35:27 <stanlagun> github might be ok for repository. But no doubt repo is needed somewhere
17:36:00 <sergmelikyan> Returning to the our Metadata Service, we plan to introduce new Metadata description language and processing engine. Stan could you share some details?
17:37:02 <stanlagun> I'm finishing protoryping of this. This is PoC-quality yet but ut demonstrates the idea, the language and runtime
17:37:38 <stanlagun> During next week I thing we will create main classes that do actual deployment so that we can compose apps from them
17:37:55 <sergmelikyan> Some etherpads about description language
17:37:58 <sergmelikyan> ?
17:38:18 * sergmelikyan lost links to that etherpad
17:38:23 <stanlagun> https://etherpad.openstack.org/p/MuranoMetadata
17:39:12 <stanlagun> It is slightly outdated. We will update it soon to match actual vision. Anyway it is close to what I'm doing
17:39:46 <katyafervent> So are you finished with prototyping?
17:40:49 <stanlagun> Almost finished. I'd like to share this PoC with other Murano guye tomorrow so that we can discuss the rest of 0.5 plans
17:42:14 <gokrokve> cool
17:42:21 <sergmelikyan> Looks like we covered our next meeting agenda  )
17:42:22 <gokrokve> we can finish earlier
17:42:44 * sergmelikyan will skip switching topic to 5. Metadata Service
17:44:16 <tsufiev> also we agreed on UI in 0.5
17:44:21 <sergmelikyan> tsufiev, can you share details about ui?
17:44:23 <sergmelikyan> :)
17:44:29 <tsufiev> sure
17:44:51 <tsufiev> we've filed a blueprint today https://blueprints.launchpad.net/murano/+spec/new-web-ui-prototype
17:46:27 <tsufiev> in two words: UI won't change much in 0.5 compared to 0.4, it will have one distinction, more important from the service definition side: fully qualified service names, like com.mirantis.windows.ActiveDirectory will serve as field types
17:46:44 <tsufiev> actually, a little more than 2 words :)
17:47:37 <tsufiev> where such field type is encountered, user will be able either select service of given type already created in given environment
17:47:43 <tsufiev> or create a new service
17:48:25 <tsufiev> it will require some efforts on the dynamic UI's part, but no major changes in visual experience
17:48:42 <tsufiev> that's all i had to share
17:49:47 <ativelkov> This new objects being created can be shared with the rest environment on the top level - or may be defined right in place
17:50:59 <tsufiev> seems that is all about UI in 0.5
17:51:14 <ativelkov> Are we done?
17:52:07 <gokrokve> sure
17:52:14 <gokrokve> lets end this meeting
17:52:29 <gokrokve> we need to prepare to the meeting in #openstack-glance channel
17:52:49 <sergmelikyan> Thx!
17:52:49 <sergmelikyan> #endmeeting