[
https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509883#comment-13509883
]
Alex Heneveld commented on CLOUDSTACK-576:
------------------------------------------
John,
+1 && thanks for the idea.
I'm a big fan of OpenShift. I think that should definitely be a
supported deployment tech. We've done similar (lightweight isolation)
with LXC at one of our customers.
So the question is whether things like this should be a native option?
Or do we aim to be general enough so cartridges/recipes/etc can all
easily be leveraged? I'm thinking the latter, then with a library of
examples for using OpenShift, Puppet, etc etc, which people can copy and
tweak.
--A
> 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
