Open Stack

Hello,

As far as I see it now here is what will be required:

1. Ability to integrate support for Murano guest VM agent (probably as a
component type plugin).
2. Ability to control configuration actions order by explicitly specifying
pre-requirements for each component
3. All configuration actions that has all pre-requirements met need to be
executed simultaneously (green threads are ok). So that we can do
mass-configuration things like install XX on 100 machines (using 100
components in generated template)
4. Components need to have metadata and agent plugin implementation need to
have access to it so that the values could be passed to Murano Agent.
Standard HOT value referencing  syntax must be supported here as well.
5. Configuration actions performed by component may produce output values
that need to be accessible to other components later in dependency chain.
This may be in form of explicit output attributes (as in HOT template
itself) or by altering own metadata values in runtime
6. Ability to stop orchestration and/or rollback stack on configuration
failures
7. Ability to modify component graph for deployed stack and thus execute
some additional configuration actions on VMs created earlier.


Does this fit your vision of Heat orchestration?


On Fri, Nov 15, 2013 at 1:11 AM, Steve Baker <sbaker at redhat.com> wrote:

>  On 11/15/2013 08:30 AM, Alexander Tivelkov wrote:
>
>  Hey Stackers,
>
>  During HK summit  we’ve been discussing an approach to implement app
> catalog for Openstack. We’ve seen certain interest in the topic and heard
> from few people that they are working on similar concepts outside of
> community.
>
>  Apparently Openstack is now mature enough to have a need for an
> application catalog which will fulfil several needs of cloud admins and
> users on platform level:
>
> - an integration point for applications and services running on top of OS
>
> - the level of management of lifecycle of applications, distribution
> channels and billing
>
> - self-service provisioning for applications
>
>  Few weeks ago we proposed to extend the mission of Murano to be an
> Application Catalog for Openstack, simultaneously we decided to contribute
> several parts of the project to other OpenStack projects, mainly Heat and
> Mistral.
>
>  Our intention is to make the mission and scope of the project as lean as
> possible, at the same time leveraging as much of the existing Openstack
> services as possible.
>
>  As many others we’re excited about Solum project and looking forward to
> integrate with Solum and contribute there.
>
>  Now the most exciting part - we are looking for contributors! Use cases,
> architecture, blueprints, code - anything would be helpful.
>
>  Right now is the best time to start, as we are just started figuring out
> definition of Application Catalog, getting the requirements, considering
> use cases and design concepts.
>
>  The project from day one is run on OpenStack infrastructure, following
> all standard OpenStack processes and practices and we’re really making an
> effort to make it very open.
>
>  We believe that this is an initiative which can bring a lot of value to
> the community, let’s try to obtain synergy working on this all together.
> The earlier you express your interest explicitly, the more impact you’re
> going to have on the roadmap.
>
>  The high-level overview of the proposal can be found at our wiki:
> https://wiki.openstack.org/wiki/Murano/ApplicationCatalog
>
> This is a work-in-progress document, and it is going to be changed - so
> your feedback is very welcome right now.
>
>  We’ve created several etherpads to collaborate and gather the
> requirements together. Feel free to add anything which seems important for
> you:
>
> https://etherpad.openstack.org/p/AppCatalogUI - requirements for UI
>
> https://etherpad.openstack.org/p/AppCatalogRoadmap - roadmap with
> features and milestones
>
> https://etherpad.openstack.org/p/AppCatalogUseCases - some use-cases,
> giving examples of how different users interact with the Application Catalog
>
>  Feel free to add anything to these etherpads - and share any ideas you
> might have with all the community.
>
> Looking forward for your participation!
>
>
>
>   Can you outline what might need to be added to Heat to support Murano?
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Sincerely yours
Stanislav (Stan) Lagun
Senior Developer
Mirantis
35b/3, Vorontsovskaya St.
Moscow, Russia
Skype: stanlagun
www.mirantis.com
slagun at mirantis.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131115/7c3e13ba/attachment.html>