[
https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510913#comment-13510913
]
Jie Feng commented on CLOUDSTACK-576:
-------------------------------------
Here is my take on Alex's questions:
(1) I recommend something lightweight based on CloudStack concepts. We can use
AWS CloudFormation's JS format as a reference starting point and make changes
where needed.
(2) For v1.0, at minimum, the ability to launch a set of VMs. The "blueprint"
should capture VM deployment properties like template ID/network, startup
order.
(3) Scripts, Chef and Puppet can be used to install software and configure VMs
after they are launched. You can already do this today within a running VM. In
my opinion, deeper integration should be optional.
This feature should be able to use CloudStack's credential and integrate into
the CloudStack UI (through UI plugin or other means).
Jie
> 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
