cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Burwell (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints
Date Tue, 04 Dec 2012 17:43:58 GMT


John Burwell commented on CLOUDSTACK-576:


My thought is a PaaS would be implemented in a manner akin to BareMetal whereby an SPI would
be provided to direct the allocation of resources (compute, storage, and network) to one or
more PaaS instances.  CloudStack would provide a common authentication and authorization layer
allowing providers to provide a single set of credentials that would operate across IaaS and
PaaS offerings, normalized monitoring and metrics collection, and some level UI embedding/theming
to provide a consistent user experience between the two management console.  The actual configuration
of the PaaS for administrators and users would be delegated to the PaaS and associated system
tools (e.g. Puppet, Chef, etc).  In my opinion, attempting any deeper integration would create
undue maintenance burden for the CloudStack project while compromising flexibility for operators
-- without providing any additional value for either.


> PaaS Enablement: Composite Application Blueprints
> -------------------------------------------------
>                 Key: CLOUDSTACK-576
>                 URL:
>             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:

View raw message