[+ Suho & Anjana] On Wed, Oct 7, 2015 at 10:37 PM, Gayan Gunarathne <gay...@wso2.com> wrote:
> Yeah. We need to consider external CEP/DAS. > > Installer will ask whether user need to setup CEP/DAS as a separate > service? If user input as it needs to be external service, installer will > configure the CEP/DAS as external services. > > Thanks, > Gayan > > > On Wed, Oct 7, 2015 at 2:26 AM, Lasindu Charith <lasi...@wso2.com> wrote: > >> Hi Imesh, >> >> On Mon, Oct 5, 2015 at 11:03 PM, Imesh Gunaratne <im...@wso2.com> wrote: >> >>> On Tue, Oct 6, 2015 at 12:09 AM, Gayan Gunarathne <gay...@wso2.com> >>> wrote: >>>> >>>> >>>> PPaaS installer will setup the private paas. Main responsibility of >>>> that installer will be setup the db, ActiveMQ and Private PaaS and start >>>> the Private PaaS server. >>>> >>> >>> We may also need to configure CEP and DAS. >>> >> >> Yes, there should be an option to have CEP/DAS separately. From the >> installer do we only ask to point the external CEP/DAS ip addresses or will >> the installer take care of the configuration of CEP/DAS as well? (similar >> to configuring puppet master) >> >> >>> Thanks >>> >>> On Tue, Oct 6, 2015 at 12:09 AM, Gayan Gunarathne <gay...@wso2.com> >>> wrote: >>> >>>> >>>> Hi All, >>>> >>>> We are planing to have two installers with the PPaaS 4.1.0. Our idea >>>> behind that is to make the PPaaS setup and the cartridge deployment to be >>>> loosely coupled. >>>> >>>> +1 >> >>> PPaaS installer will setup the private paas. Main responsibility of that >>>> installer will be setup the db, ActiveMQ and Private PaaS and start the >>>> Private PaaS server. >>>> >>> >> I think this is for PPaaS running in a single instance. Since we may not >> recommend to use installer in production, we need not to support >> distributed deployment of PPaaS in the installer. But as Imesh has >> mentioned, we would need to support CEP/DAS running externally. >> >> >>> >>>> PPaaS cartridges installer will be to deploy the Private PaaS >>>> cartridges.Main responsibility of this will be deploy the cartridges.Mainly >>>> It will carry out the following tasks, >>>> >>>> - Obtain the user input on deployment product and environment >>>> - If it is vm, >>>> set up the puppet master ,set up the packs , template module and >>>> plugins to right location >>>> - If it is kubenetes cluster, >>>> pull the docker images for nodes/or build the docker image >>>> locally and transfer to the Kubernetes cluster nodes based on the user >>>> input >>>> - Execute configurator to configure the samples >>>> - Update the deployment artifacts based on the user inputs and >>>> initialized the deployment process through Rest API. >>>> >>>> We will maintain and release those two installers separately. >>>> >>>> Please share your thoughts and suggestions on this. >>>> >>>> Thanks, >>>> Gayan >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Gayan Gunarathne >>>> Technical Lead, WSO2 Inc. (http://wso2.com) >>>> Committer & PMC Member, Apache Stratos >>>> email : gay...@wso2.com | mobile : +94 775030545 <%2B94%20766819985> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> *Imesh Gunaratne* >>> Senior Technical Lead >>> WSO2 Inc: http://wso2.com >>> T: +94 11 214 5345 M: +94 77 374 2057 >>> W: http://imesh.gunaratne.org >>> Lean . Enterprise . Middleware >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> Thanks, >> -- >> *Lasindu Charith* >> Software Engineer, WSO2 Inc. >> Committer & PMC Member, Apache Stratos >> Mobile: +94714427192 | Web: blog.lasindu.com >> > > > > -- > > Gayan Gunarathne > Technical Lead, WSO2 Inc. (http://wso2.com) > Committer & PMC Member, Apache Stratos > email : gay...@wso2.com | mobile : +94 775030545 <%2B94%20766819985> > > > -- *Imesh Gunaratne* Senior Technical Lead WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: http://imesh.gunaratne.org Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
