You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Duncan Johnston-Watt (JIRA)" <ji...@apache.org> on 2012/12/02 18:53:57 UTC

[jira] [Created] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Duncan Johnston-Watt created CLOUDSTACK-576:
-----------------------------------------------

             Summary: 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

Re: [jira] [Created] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by John Burwell <jb...@basho.com>.
Alex,

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.

Thanks,
-John

On Dec 4, 2012, at 12:30 PM, Alex Heneveld <al...@cloudsoftcorp.com> wrote:

> 
> 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
> 
> 
> On 04/12/2012 11:13, John Burwell wrote:
>> Alex,
>> 
>> You may also want to take a look at OpenShift (https://github.com/openshift).  Rather than VMs, they separate applications using SELinux controls which leads to far greater densities.  This approach has allowed them to support a number of unique features (such as SSH access for each account) that are not available on other platforms.
>> 
>> Thanks,
>> -John
>> 
> 


Re: [jira] [Created] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by Alex Heneveld <al...@cloudsoftcorp.com>.
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


On 04/12/2012 11:13, John Burwell wrote:
> Alex,
>
> You may also want to take a look at OpenShift (https://github.com/openshift).  Rather than VMs, they separate applications using SELinux controls which leads to far greater densities.  This approach has allowed them to support a number of unique features (such as SSH access for each account) that are not available on other platforms.
>
> Thanks,
> -John
>


Re: [jira] [Created] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by John Burwell <jb...@basho.com>.
Alex,

You may also want to take a look at OpenShift (https://github.com/openshift).  Rather than VMs, they separate applications using SELinux controls which leads to far greater densities.  This approach has allowed them to support a number of unique features (such as SSH access for each account) that are not available on other platforms.

Thanks,
-John

On Dec 4, 2012, at 12:05 PM, Alex Heneveld <al...@cloudsoftcorp.com> wrote:

> 
> Hi folks--
> 
> To get the ball rolling here are a few questions on design/features.  And my answers, in order to kick off the argument discussion this needs!  I'll collate and post at #576.
> 
> 
> *(1) Should we try for an AWS or vApp look-alike?  Or build something around Cloudstack concepts?*
> 
> Something new and lightweight based around Cloudstack, taking the best of the others.
> 
> Cloudstack concepts (networking, service offerings) have evolved a lot since EC2 and are more expressive.  If we try to mimic something else too much we'll end up with a poorly fitting shoe.
> 
> A migration tool to take other template types would then be an option.
> 
> 
> *(2) What functionality do people care about most?*
> 
> - ability to launch a set of VM's based on template ID or template key/value details
> - ability to define a scalable cluster of a template
> - ability to attach external (code) policies to that cluster
> - ability to specify that the collection is on a private subnet with only selected VM+ports exposed via a public IP
> 
> 
> *(3) What deployment and management tools/techniques are people using and would like to see supported here?*
> 
> - bash scripts (install and run scripts, with ability to refer to other VMs programmatically in the script)
> - deploy a puppet-master, then bring up other "stem-cell" nodes which connect to the puppet master
> - (David Nalley has already mentioned knife-cloudstack using chef)
> - whirr  ( http://whirr.apache.org )
> - brooklyn ( http://brooklyncentral.github.com ) for clusters and policies, building on the above
> 
> 
> Best,
> Alex
> 


Re: [jira] [Created] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by Alex Heneveld <al...@cloudsoftcorp.com>.
Hi folks--

To get the ball rolling here are a few questions on design/features.  
And my answers, in order to kick off the argument discussion this 
needs!  I'll collate and post at #576.


*(1) Should we try for an AWS or vApp look-alike?  Or build something 
around Cloudstack concepts?*

Something new and lightweight based around Cloudstack, taking the best 
of the others.

Cloudstack concepts (networking, service offerings) have evolved a lot 
since EC2 and are more expressive.  If we try to mimic something else 
too much we'll end up with a poorly fitting shoe.

A migration tool to take other template types would then be an option.


*(2) What functionality do people care about most?*

- ability to launch a set of VM's based on template ID or template 
key/value details
- ability to define a scalable cluster of a template
- ability to attach external (code) policies to that cluster
- ability to specify that the collection is on a private subnet with 
only selected VM+ports exposed via a public IP


*(3) What deployment and management tools/techniques are people using 
and would like to see supported here?*

- bash scripts (install and run scripts, with ability to refer to other 
VMs programmatically in the script)
- deploy a puppet-master, then bring up other "stem-cell" nodes which 
connect to the puppet master
- (David Nalley has already mentioned knife-cloudstack using chef)
- whirr  ( http://whirr.apache.org )
- brooklyn ( http://brooklyncentral.github.com ) for clusters and 
policies, building on the above


Best,
Alex


Re: [jira] [Created] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by David Nalley <da...@gnsa.us>.
On Sun, Dec 2, 2012 at 1:02 PM, Duncan Johnston Watt
<du...@cloudsoftcorp.com> wrote:
> Chip/All
>
> Just to add to this feature request provided we have the support/backing of
> the community we would be happy to lead this effort/commit resources to
> this as it is well aligned with our other efforts in the open source [1]
> and standards community [2] as well as our focus as a business.
>


I would be very interested in seeing this.
To date, we've had a number of external efforts essentially 'working
around' this gap, the earliest that I can recall is knife-cloudstack
that permitted you to define an application stack using chef and then
having knife programmatically having the ability to deploy the entire
stack with a single call. I don't know that we'd necessarily eliminate
the need for things like that, but it would be incredibly useful. Do I
infer properly that you'd be looking at using the AWS cloudformation
API to make this happen?

--David

Re: [jira] [Created] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by Duncan Johnston Watt <du...@cloudsoftcorp.com>.
Chip/All

Just to add to this feature request provided we have the support/backing of
the community we would be happy to lead this effort/commit resources to
this as it is well aligned with our other efforts in the open source [1]
and standards community [2] as well as our focus as a business.

[1] http://brooklyncentral.github.com/
[2] https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=camp

Best

Duncan

On 2 December 2012 09:53, Duncan Johnston-Watt (JIRA) <ji...@apache.org>wrote:

> Duncan Johnston-Watt created CLOUDSTACK-576:
> -----------------------------------------------
>
>              Summary: 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
>



-- 
Duncan Johnston-Watt
CEO | Cloudsoft Corporation

Twitter | @duncanjw
Mobile | +44 777 190 2653
Skype | duncan_johnstonwatt
Linkedin | www.linkedin.com/in/duncanjohnstonwatt

Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP

This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.

RE: [jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "Kelcey Damage (BBITS)" <ke...@bbits.ca>.
I also failed to properly read your original mailer where you state vApp and VMware style feature. I currently have a vCloud and yes those are very useful features.

-kd 

-----Original Message-----
From: Kelceydamage@bbits (JIRA) [mailto:jira@apache.org] 
Sent: Tuesday, December 04, 2012 8:23 PM
To: cloudstack-dev@incubator.apache.org
Subject: [jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510257#comment-13510257 ] 

Kelceydamage@bbits commented on CLOUDSTACK-576:
-----------------------------------------------

Sorry, don't get me wrong, I do think a PaaS solution for S would be awesome. 

On the other note I brought up a feature request at CCC for vApp style containers, and application collections. I Think there are a lot of features that I would enjoy seeing in CS, as it evolves. I just wanted to make sure I voiced that it would be a shame if CS lost some flexibility as the cost of enabling it as more end-user friendly system.

My comment about add-on layer, I was thinking about how CloudPortal et-al, fits onto CloudStack but yet its separate.

I summary I am in favor of more automation, and better feature-set, I hope we can be careful in its implementation.

KELCEY DAMAGE
Infrastructure Systems Architect
www.backbonetechnology.com
-------------------------------------------------------------------------
kelcey@bbits.ca 

address: 55 East 7th Ave, Vancouver, BC, V5T 1M4
tel: +1 604 713 8560 ext:114
fax: +1 604 605 0964
skype: kelcey.damage 
 


                
> 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


[jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "David Nalley (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509836#comment-13509836 ] 

David Nalley commented on CLOUDSTACK-576:
-----------------------------------------

On Sun, Dec 2, 2012 at 1:02 PM, Duncan Johnston Watt


I would be very interested in seeing this.
To date, we've had a number of external efforts essentially 'working
around' this gap, the earliest that I can recall is knife-cloudstack
that permitted you to define an application stack using chef and then
having knife programmatically having the ability to deploy the entire
stack with a single call. I don't know that we'd necessarily eliminate
the need for things like that, but it would be incredibly useful. Do I
infer properly that you'd be looking at using the AWS cloudformation
API to make this happen?

--David

                
> 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

[jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "Kelceydamage@bbits (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509903#comment-13509903 ] 

Kelceydamage@bbits commented on CLOUDSTACK-576:
-----------------------------------------------

I am in agreement with this, as a content IaaS provider, I would not want integration to go so far as to cloud or obfuscate the IaaS systems in favor of PaaS. To me they are 2 distinct and seperate methodologies. I do like PaaS, and would think it more of an opportunity for an add on system it layer.

Sent from my iPhone



                
> 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

[jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "Rajesh Battala (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510229#comment-13510229 ] 

Rajesh Battala commented on CLOUDSTACK-576:
-------------------------------------------

Is this similar to vApps support in XenServer?
                
> 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

[jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "Alex Heneveld (JIRA)" <ji...@apache.org>.
    [ 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

[jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "John Burwell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509873#comment-13509873 ] 

John Burwell commented on CLOUDSTACK-576:
-----------------------------------------

Alex,

You may also want to take a look at OpenShift (https://github.com/openshift).  Rather than VMs, they separate applications using SELinux controls which leads to far greater densities.  This approach has allowed them to support a number of unique features (such as SSH access for each account) that are not available on other platforms.

Thanks,
-John




                
> 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

[jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "Kelceydamage@bbits (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510265#comment-13510265 ] 

Kelceydamage@bbits commented on CLOUDSTACK-576:
-----------------------------------------------

I also failed to properly read your original mailer where you state vApp and VMware style feature. I currently have a vCloud and yes those are very useful features.

-kd 


                
> 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

Re: [jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by Duncan Johnston Watt <du...@cloudsoftcorp.com>.
Kelcey

The reason we presented this as PaaS enablement is that we see this as a
distinct but related activity. One that is important to end users/consumers
of cloud.

Best

Duncan

On 4 December 2012 09:58, Kelceydamage@bbits <ke...@bbits.ca> wrote:

> I am in agreement with this, as a content IaaS provider, I would not want
> integration to go so far as to cloud or obfuscate the IaaS systems in favor
> of PaaS. To me they are 2 distinct and seperate methodologies. I do like
> PaaS, and would think it more of an opportunity for an add on system it
> layer.
>
> Sent from my iPhone
>
> On Dec 4, 2012, at 9:43 AM, "John Burwell (JIRA)" <ji...@apache.org> wrote:
>
> >
> >    [
> https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509892#comment-13509892]
> >
> > John Burwell commented on CLOUDSTACK-576:
> > -----------------------------------------
> >
> > Alex,
> >
> > 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.
> >
> > Thanks,
> > -John
> >
> >
> >
> >
> >
> >> 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
>



-- 
Duncan Johnston-Watt
CEO | Cloudsoft Corporation

Twitter | @duncanjw
Mobile | +44 777 190 2653
Skype | duncan_johnstonwatt
Linkedin | www.linkedin.com/in/duncanjohnstonwatt

Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP

This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.

Re: [jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "Kelceydamage@bbits" <ke...@bbits.ca>.
I am in agreement with this, as a content IaaS provider, I would not want integration to go so far as to cloud or obfuscate the IaaS systems in favor of PaaS. To me they are 2 distinct and seperate methodologies. I do like PaaS, and would think it more of an opportunity for an add on system it layer.

Sent from my iPhone

On Dec 4, 2012, at 9:43 AM, "John Burwell (JIRA)" <ji...@apache.org> wrote:

> 
>    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509892#comment-13509892 ] 
> 
> John Burwell commented on CLOUDSTACK-576:
> -----------------------------------------
> 
> Alex,
> 
> 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.
> 
> Thanks,
> -John
> 
> 
> 
> 
> 
>> 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

[jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "John Burwell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509892#comment-13509892 ] 

John Burwell commented on CLOUDSTACK-576:
-----------------------------------------

Alex,

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.

Thanks,
-John




                
> 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

[jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "Duncan Johnston-Watt (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510243#comment-13510243 ] 

Duncan Johnston-Watt commented on CLOUDSTACK-576:
-------------------------------------------------

Kelcey

The reason we presented this as PaaS enablement is that we see this as a
distinct but related activity. One that is important to end users/consumers
of cloud.

Best

Duncan





-- 
Duncan Johnston-Watt
CEO | Cloudsoft Corporation

Twitter | @duncanjw
Mobile | +44 777 190 2653
Skype | duncan_johnstonwatt
Linkedin | www.linkedin.com/in/duncanjohnstonwatt

Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP

This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.

                
> 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

[jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "Jie Feng (JIRA)" <ji...@apache.org>.
    [ 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

[jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "Kelceydamage@bbits (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510257#comment-13510257 ] 

Kelceydamage@bbits commented on CLOUDSTACK-576:
-----------------------------------------------

Sorry, don't get me wrong, I do think a PaaS solution for S would be awesome. 

On the other note I brought up a feature request at CCC for vApp style containers, and application collections. I Think there are a lot of features that I would enjoy seeing in CS, as it evolves. I just wanted to make sure I voiced that it would be a shame if CS lost some flexibility as the cost of enabling it as more end-user friendly system.

My comment about add-on layer, I was thinking about how CloudPortal et-al, fits onto CloudStack but yet its separate.

I summary I am in favor of more automation, and better feature-set, I hope we can be careful in its implementation.

KELCEY DAMAGE 
Infrastructure Systems Architect 
www.backbonetechnology.com 
------------------------------------------------------------------------- 
kelcey@bbits.ca 

address: 55 East 7th Ave, Vancouver, BC, V5T 1M4
tel: +1 604 713 8560 ext:114    
fax: +1 604 605 0964 
skype: kelcey.damage 
 


                
> 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

[jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "Alex Heneveld (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509865#comment-13509865 ] 

Alex Heneveld commented on CLOUDSTACK-576:
------------------------------------------


Hi folks--

To get the ball rolling here are a few questions on design/features.  
And my answers, in order to kick off the argument discussion this 
needs!  I'll collate and post at #576.


*(1) Should we try for an AWS or vApp look-alike?  Or build something 
around Cloudstack concepts?*

Something new and lightweight based around Cloudstack, taking the best 
of the others.

Cloudstack concepts (networking, service offerings) have evolved a lot 
since EC2 and are more expressive.  If we try to mimic something else 
too much we'll end up with a poorly fitting shoe.

A migration tool to take other template types would then be an option.


*(2) What functionality do people care about most?*

- ability to launch a set of VM's based on template ID or template 
key/value details
- ability to define a scalable cluster of a template
- ability to attach external (code) policies to that cluster
- ability to specify that the collection is on a private subnet with 
only selected VM+ports exposed via a public IP


*(3) What deployment and management tools/techniques are people using 
and would like to see supported here?*

- bash scripts (install and run scripts, with ability to refer to other 
VMs programmatically in the script)
- deploy a puppet-master, then bring up other "stem-cell" nodes which 
connect to the puppet master
- (David Nalley has already mentioned knife-cloudstack using chef)
- whirr  ( http://whirr.apache.org )
- brooklyn ( http://brooklyncentral.github.com ) for clusters and 
policies, building on the above


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

[jira] [Commented] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "Duncan Johnston-Watt (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508308#comment-13508308 ] 

Duncan Johnston-Watt commented on CLOUDSTACK-576:
-------------------------------------------------

Chip/All

Just to add to this feature request provided we have the support/backing of
the community we would be happy to lead this effort/commit resources to
this as it is well aligned with our other efforts in the open source [1]
and standards community [2] as well as our focus as a business.

[1] http://brooklyncentral.github.com/
[2] https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=camp

Best

Duncan





-- 
Duncan Johnston-Watt
CEO | Cloudsoft Corporation

Twitter | @duncanjw
Mobile | +44 777 190 2653
Skype | duncan_johnstonwatt
Linkedin | www.linkedin.com/in/duncanjohnstonwatt

Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP

This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.

                
> 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

[jira] [Comment Edited] (CLOUDSTACK-576) PaaS Enablement: Composite Application Blueprints

Posted by "Duncan Johnston-Watt (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLOUDSTACK-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508308#comment-13508308 ] 

Duncan Johnston-Watt edited comment on CLOUDSTACK-576 at 12/4/12 9:53 PM:
--------------------------------------------------------------------------

Just to add to this feature request provided we have the support/backing of
the community we would be happy to lead this effort/commit resources to
this as it is well aligned with our other efforts in the open source [1]
and standards community [2] as well as our focus as a business.

[1] http://brooklyncentral.github.com/
[2] https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=camp

                
      was (Author: duncanjw):
    Chip/All

Just to add to this feature request provided we have the support/backing of
the community we would be happy to lead this effort/commit resources to
this as it is well aligned with our other efforts in the open source [1]
and standards community [2] as well as our focus as a business.

[1] http://brooklyncentral.github.com/
[2] https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=camp

Best

Duncan





-- 
Duncan Johnston-Watt
CEO | Cloudsoft Corporation

Twitter | @duncanjw
Mobile | +44 777 190 2653
Skype | duncan_johnstonwatt
Linkedin | www.linkedin.com/in/duncanjohnstonwatt

Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP

This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.

                  
> 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