17:02:19 <serg_melikyan> #startmeeting murano
17:02:20 <openstack> Meeting started Tue Apr 21 17:02:19 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:02:22 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:02:24 <openstack> The meeting name has been set to 'murano'
17:02:31 <katyafervent2> hi
17:02:34 <henar> hi
17:02:35 * serg_melikyan laughing )
17:02:39 <freerunner> hi there! ;)
17:02:57 <slagun> o/
17:03:03 <serg_melikyan> I started meeting in the wrong channel :) Boris was really surprised :)
17:03:12 <freerunner> lol =)
17:03:35 <slagun> :)
17:03:35 <FilipBlaha> hi
17:04:07 <serg_melikyan> And I was deadly sure that it is my meeting :) He seemed not so sure :)
17:04:23 * serg_melikyan still lauching
17:05:04 <serg_melikyan> Sorry folks, let's get started
17:05:29 <aderyugin> hi^^
17:05:58 <ruhe> o/
17:06:16 <serg_melikyan> Meeting Minutes from previous meeting: http://eavesdrop.openstack.org/meetings/murano/2015/murano.2015-04-14-17.00.html
17:06:28 <serg_melikyan> ruhe: long time no see :)
17:06:50 <ruhe> sorry, i had overlapping meetings at this time
17:07:15 <serg_melikyan> ruhe: heh, saw few commits from you recently - you are returning to us? :)
17:07:41 <ruhe> not as a full time engineer, but i hope to contribute something :)
17:07:59 <serg_melikyan> We have only one action item for today: sergmelikyan, schedule discussion for https://blueprints.launchpad.net/murano/+spec/abstract-env-template after Kilo RC1
17:08:34 <serg_melikyan> We released RC1 yesterday, and working our way to RC2, so I guess we can schedule this meeting
17:09:27 <serg_melikyan> henar: what do you think about 12:00 UTC on the next Tuesday?
17:10:11 <henar> ok
17:10:29 <serg_melikyan> ruhe: happy to hear that - every commit made by you makes me happy :)
17:10:39 <serg_melikyan> henar: excellent
17:11:35 <serg_melikyan> #info meeting about blueprint/abstract-env-template is scheduled for Tuesday, April 28 12:00 UTC in #murano
17:11:55 <serg_melikyan> I think we are going eventually move to hangout to make this meeting more productive
17:12:46 <ruhe> serg_melikyan: please make sure that everyone in community is aware of these meetings and can read through meeting minutes of these meetings
17:13:17 <serg_melikyan> Yep
17:13:49 <serg_melikyan> #topic Release Status
17:15:54 <katyafervent2> we need to concentrate on the documentation for Kilo
17:16:53 <serg_melikyan> Yesterday we've released RC1, and we are working on releasing python-muranoclient...
17:17:15 <katyafervent2> im going to prepare a list of tasks to improve it
17:17:20 <kzaitsev> YAY for RC1!
17:17:50 <serg_melikyan> btw, releasing RC1 means that we have stable/kilo branch and all fixes for kilo should go to master and stable/kilo and merged to stable/kilo first
17:18:21 <serg_melikyan> katyafervent2: we need critical fixes that we need to fix in kilo, we have freeze here
17:18:34 <serg_melikyan> but list of tasks is anyway is good
17:19:20 <ruhe> serg_melikyan: can you please rephrase that sentence about order of commits? If you want to commit something to stable/kilo, you need to merge it to master first. Is that correct?
17:20:42 <serg_melikyan> ruhe: Since stable/kilo is really close to release we need to fix bugs in stable/kilo and cherry-pick them to master (essentially to Liberty)
17:21:00 <serg_melikyan> I am still sound confusing?
17:21:19 <ruhe> so, stable/kilo first, master is second. ok
17:23:10 <serg_melikyan> And by the way I will unblock all the commits blocked until Liberty tomorrow
17:30:58 <serg_melikyan> Any other questions regarding kilo release?
17:31:32 <ruhe> nope
17:31:49 <serg_melikyan> #topic Open Discussion
17:32:20 <serg_melikyan> aderyugin: https://review.openstack.org/175933 Stan proposed alternative way to place DIB elements, what do you think?
17:32:42 <ruhe> i'd like to implement this spec in L1 https://github.com/openstack/openstack-specs/blob/master/specs/no-downward-sql-migration.rst
17:32:57 <ruhe> should i create a spec in murano for it, or just create a blueprint?
17:33:54 <henar> sorry I have to go.. I will read the minutes.
17:34:06 <FilipBlaha> Hi, regarding to discussion from previous meeting on importing packages and cli tool. did you consider downloading packages from central public repository via cli tool?
17:34:06 <FilipBlaha> Hi, regarding to discussion from previous meeting on importing packages and cli tool. did you consider downloading packages from central public repository via cli tool?
17:34:06 <FilipBlaha> Hi, regarding to discussion from previous meeting on importing packages and cli tool. did you consider downloading packages from central public repository via cli tool?
17:34:36 <serg_melikyan> ruhe: I think blueprint should be enough, if it would point to right specification.
17:34:37 <FilipBlaha> e.g. murano package site-import io.murano.apps.WordPress
17:34:37 <FilipBlaha> e.g. murano package site-import io.murano.apps.WordPress
17:34:58 <FilipBlaha> this command would download/clone package form https://github.com/murano-project/murano-app-incubator and import it to your local opanstack with murano
17:35:08 <serg_melikyan> FilipBlaha: somehow I have an echo for your messages :)
17:35:17 <aderyugin> serg_melikyan: I do not fully understand, why we should store elements inside application, but I think all other ok...
17:35:19 <FilipBlaha> sorry for that
17:35:27 <serg_melikyan> FilipBlaha: we actually already have that kind of feature
17:35:53 <serg_melikyan> FilipBlaha: http://murano-specs.readthedocs.org/en/latest/specs/kilo/muranoclient-marketplace-support.html
17:36:28 <serg_melikyan> aderyugin: there is comment in comments on this change with answer to why...
17:37:25 <kzaitsev> Filip, what do you mean? We've actually implemented a feature, very similar to the one you describe
17:37:50 <serg_melikyan> FilipBlaha: http://murano.readthedocs.org/en/stable-kilo/articles/client.html#importing-packages-in-murano
17:37:59 <kzaitsev> http://murano.readthedocs.org/en/stable-kilo/articles/repository.html and this =)
17:39:28 <velovec> serg_melikyan: If I understand correctly, we will upload application with elements to murano?
17:39:29 <FilipBlaha> ok I will read about it. But looks the same as I meant my fault
17:41:19 <serg_melikyan> FilipBlaha: it does not import from github :(
17:43:06 <aderyugin> serg_melikyan: so, I think it can be done this way for this moment, but it's better to store elements in separate repository
17:43:06 <FilipBlaha> why? some technical problem? I mean  some public with well defined structure and versioning as central point for murano apps
17:43:56 <kzaitsev> Oh I get it. You want a bit of different importing mechanism =)
17:45:50 <FilipBlaha> something like https://supermarket.chef.io/cookbooks  for chef cookbooks
17:47:32 <kzaitsev> Filip, I think, that what we've implemented is very similar to https://supermarket.chef.io/cookbooks We do not have a public web repo/endpoint yet, but the idea is very similar.
17:49:30 <FilipBlaha> kzaitsev: I think so the only differnce is that you must give url as parameter. My fault that I didn;t know about it
17:49:52 <kzaitsev> You mean --murano-repo-url?
17:49:55 <serg_melikyan> FilipBlaha: you can pass this param through env variables
17:50:14 <kzaitsev> I hope it will be replaced with a sensible default in future =)
17:50:48 <serg_melikyan> FilipBlaha: http://murano.readthedocs.org/en/stable-kilo/articles/repository.html#setting-up-your-own-repository this is how easy is bring such web-server to live
17:51:36 <FilipBlaha> yes. I agree there is nothing new in my idea
17:54:05 <serg_melikyan> I hope this feature will be adopted very soon by community and we would see public "supermarkets" for murano apps
17:58:04 <serg_melikyan> Thank you, folks! See you on the next, so long
17:58:07 <serg_melikyan> #endmeeting