Alexander, do you plan to update the https://review.openstack.org/#/c/140402/
versioning spec? We can possibly try to make it a joint effort, if you like.
--
Kirill Zaitsev
Murano team
Software Engineer
Mirantis, Inc
On 14 Jul 2015 at 11:34:56, Alexander Tivelkov (ativel...@mirantis.com) wrote
Gosha,
Could you please elaborate what do you mean by extra blocks? Glance V3
comes with Glance out-of-the box, no extra deployment is needed. The only
thing one will have to install is Murano Package Type plugin - but it will
be installed at the same time with Murano.
--
Regards,
Alexander Tivel
On Mon, Jul 13, 2015 at 2:19 AM, Alexander Tivelkov
wrote:
> Hi Gosha,
>
> Supporting versioning in existing backend will require us to re-implement
> the significant part of Artifact Repository in Murano API: we'll need to
> add versions and dependencies concepts into our model (which is already
Hi Gosha,
Supporting versioning in existing backend will require us to re-implement
the significant part of Artifact Repository in Murano API: we'll need to
add versions and dependencies concepts into our model (which is already
complicated and dirty enough), extend appropriate API calls etc. And
Hi Alex,
Thank you for the great summary.
I have a concern about item #8. Can we add an option to Murano to use
previous storage engine rather then Glance v3? We need to make sure that v3
API in Glance is set by default before we do a hard dependency on it in
Murano.
Thanks
Gosha
On Fri, Jul 10
Hi folks,
Ability to manage multiple versions of application packages and their
dependencies was always an important item in Murano roadmap, however we
still don't have a clear spec for this feature.
Yesterday we hosted a small design session to come up with a plan on what
can be done in Liberty t