Hi Ilya
On Thu, Jun 25, 2015 at 9:51 PM, ilya <ilya.mailing.li...@gmail.com> wrote: > I guess you would call this PaaS provisioning. > Agreed. > It seems like you have a good handle on process. > > Few more things to consider: > You may want to look into autoscaling options - to spin up more PaaS > slave nodes. > The templates for PaaS engine and PaaS slave nodes would make use of > metadata to auto configure. In fact, you don't have to create specific > templates for Engine/Slave if time to provision is not of essence (probably > unlikely). Entire script or pointer to install the script can be passed > through metadata. > Consider making use of groups feature to group node types > > Last but not least, you did not mention what type of cloud you are running - > private or public. I would call my current implementation Private Cloud. Would this make a difference? > > Regards, > ilya > > On 6/25/15 10:40 AM, Traiano Welcome wrote: >> >> Hi List >> >> First of all, thanks to the CloudStack developer and user community >> for an excellent piece of software! >> >> I'd like to understand the best way of implementing a PaaS layer on >> top of a CloudStack 4.5 based IaaS. >> >> The ideal (to me) is for the PaaS layer to be integrated to the point >> that PaaS can be provisioned by the end-user from the same interface >> as infrastructure is provisioned (the C.S web via), and/or for >> something like a PaaS templating syntax to be available for automated >> provisioning of PaaS on on CloudStack. >> >> Since C.S does not appear to have "native PaaS" integrated with it, >> the options would appear to be something like this: >> >> a) Implement a given PaaS with templates as a service offering >> b) Automate PaaS template deployments using cloudmonkey or the C.S API >> c) Install a PaaS management layer like OpenShift or Stackato 'on top' >> of CloudStack >> >> Are these all the current options for implementing integrated PaaS on >> CloudStack? What would be the "best" approach (i.e the most tightly >> integrated with C.S from the end-user perspective) ? >> >> Cheers, >> Traiano > >
