[
https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13528868#comment-13528868
]
Alex Heneveld commented on CLOUDSTACK-576:
------------------------------------------
Thanks all. Great comments Jie. Seems like we're in general agreement that we
want something lightweight, based around Cloudstack concepts, and supporting
the main vApp/cloudformation functionality. It *must* support the ability to:
* launch a set of VM's
* specify template ID and order/dependencies
* specify user/pass/keys on VM's where supported
* specify network configuration
Additionally we've learned from how people use the earlier approaches and this
*should* be designed so that:
* popular config tools can be used -- including bash, chef, puppet, package
managers (eg rpm), paas (eg openshift cartridges) -- but without depending on
these or coding to them
* hooks for runtime management/automation are available -- e.g. scaling, HA/DR
-- again through optional and flexible mechanisms
* these blueprints and instantiations are integrated with the UI and the
ecosystem (e.g. marketplace?)
I'm happy with this. Anything I've missed or we should add at this point?
What's the recommended next step? Is there a standard requirements or feature
spec document to put forward? (We have a stab at this above but is there an
official format?)
Personally I'd like to get some mock-up proposals for {X,YA}ML syntax and GUI
to discuss. Ideas welcome ... I'll start working on the same.
Best
Alex
> PaaS Enablement: Composite Application Blueprints
> -------------------------------------------------
>
> Key: CLOUDSTACK-576
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-576
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, AWSAPI
> Reporter: Duncan Johnston-Watt
>
> Given the level of interest in CloudStack as a platform for private, hybrid
> and public cloud one of the gaps is support for composite/multi-tier
> application blueprints comparable to VMware vApp and CloudFormation templates
> without necessarily slavishly following either of them. This is almost
> certainly a new component. One that will leverage/enhance the API/AWSAPI
> components amongst others.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
