[openstack-dev] [Murano] Package composition

Stan Lagun slagun at mirantis.com
Tue Jun 17 19:58:12 UTC 2014


Hi Steve,

It is very simple: one application per package. If something can be
deployed on its own (can be a top level component in environment and must
be visible in app catalog) then it is application and deserves a separate
package.

The composition (in your example distribution of hosts between
applications) is done by the user in dashboard. Due to current dashboard
limitations there is no way to share instance between several applications
but this a temporary limitation. Also it would be wrong to enforce some
particular deployment topology on package level until absolutely required
because otherwise you would require to publish separate application
versions for each supported topology. Imagine how it will look like for
apps with tens of instances and hundreds of combinations of what can be
combined into single VM.

Sincerely yours,
Stan Lagun
Principal Software Engineer @ Mirantis

 <slagun at mirantis.com>


On Tue, Jun 17, 2014 at 7:36 PM, McLellan, Steven <steve.mclellan at hp.com>
wrote:

>  Hi,
>
>
>
> I’m trying to figure out what we’ll be able to support in the near/far
> term with regards to packaging applications. My understanding of the DSL is
> incomplete and I’m trying to fix that J  This isn’t so much a usage
> question as for assistance writing documentation.
>
>
>
> Taking Wordpress as the ever-present example, imagine I want to present
> one choice to a user:
>
> ·         Install it and mysql on one host
>
> ·         Install it on one host, and mysql on another host
>
>
>
> This also implies that I have two Applications defined; one which
> describes how to install Wordpress (and takes a database host/user/password
> as arguments, as well as an instance), and one describing how to install a
> database (which maybe also takes a username and password as arguments).
>
>
>
> In terms of packaging, what’s the best way to represent this? What would
> make sense to me is to have the database Application defined in a library
> somewhere, and the Wordpress Application and the logic and UI to take input
> and make decisions in their own package.
>
>
>
> This kind of composition seems very similar to the
> SQLServer/ActiveDirectory example but it’s hard working through the
> example. It was mentioned at the summit that we need some good examples of
> what can be done above Heat (and the reason this is a good example is
> because there’s a direct comparison to Thomas Spatzier’s softwareconfig
> example heat templates).
>
>
>
> I’m happy to write something up but I’d like some input first.
>
>
>
> Steve
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140617/62568b61/attachment.html>


More information about the OpenStack-dev mailing list