Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-06 Thread Lasindu Charith
Hi Akila/Imesh, Any reason why we moved common samples (network partitions, autoscale policies, deployment policies, application policies) inside each cartridge? If those artifacts are similar, what if we keep them in a common place? (say inside common/samples/..). Once we introduce more

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-06 Thread Rajkumar Rajaratnam
On Wed, Oct 7, 2015 at 9:38 AM, Lasindu Charith wrote: > Hi Akila/Imesh, > > Any reason why we moved common samples (network partitions, autoscale > policies, deployment policies, application policies) inside each cartridge? > > If those artifacts are similar, what if we keep

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-06 Thread Akila Ravihansa Perera
Hi, We are planning to create a single set of templates for samples using Jinja templating language. Once it is done we can remove individual sample artifacts. Thanks. On Wednesday, 7 October 2015, Imesh Gunaratne wrote: > On Wed, Oct 7, 2015 at 2:08 AM, Lasindu Charith

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-06 Thread Imesh Gunaratne
On Wed, Oct 7, 2015 at 2:08 AM, Lasindu Charith wrote: > Hi Akila/Imesh, > > Any reason why we moved common samples (network partitions, autoscale > policies, deployment policies, application policies) inside each cartridge? > > If those artifacts are similar, what if we keep

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-04 Thread Imesh Gunaratne
On Fri, Oct 2, 2015 at 2:25 PM, Thanuja Uruththirakodeeswaran < thanu...@wso2.com> wrote: > Hi All, > > We have folder for base-image and inside that we have a folder called > 'docker' for docker base image. In the VM scenario, we are using > init-scripts to create the vm base image. So what if

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-04 Thread Imesh Gunaratne
On Thu, Oct 1, 2015 at 6:06 PM, Reka Thirunavukkarasu wrote: > Hi > > Shall we maintain an installer as well (specially for VM cartridges) in > this repository to quickly create specific cartridges in puppet? > +1 On Thu, Oct 1, 2015 at 6:14 PM, Akila Ravihansa Perera

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-04 Thread Imesh Gunaratne
It looks good Akila! On Mon, Oct 5, 2015 at 12:01 AM, Akila Ravihansa Perera wrote: > Hi, > > I've restructured the repo considering what we discussed here. I've also > added a distribution for VM related files. > > Final directory structure as follows; > > ├── common > │

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-04 Thread Akila Ravihansa Perera
Hi, I've restructured the repo considering what we discussed here. I've also added a distribution for VM related files. Final directory structure as follows; ├── common │ ├── configurator │ │ ├── live-test │ │ │ ├── src │ │ ├── src │ │ │ ├── assembly │ │ │ └── main │

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-02 Thread Thanuja Uruththirakodeeswaran
Hi All, We have folder for base-image and inside that we have a folder called 'docker' for docker base image. In the VM scenario, we are using init-scripts to create the vm base image. So what if we move the init-scripts folder inside /common/base-image/vm/ path? ├── common │ ├── base-image │

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-01 Thread Imesh Gunaratne
On Thu, Oct 1, 2015 at 12:52 PM, Akila Ravihansa Perera wrote: > > Wouldn't it be easier to navigate if we move those common folders to root > folder? > > The problem is that then the cartridges would mix up with the common ones. On Thu, Oct 1, 2015 at 12:52 PM, Akila

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-01 Thread Gayan Gunarathne
On Thu, Oct 1, 2015 at 6:06 PM, Reka Thirunavukkarasu wrote: > Hi > > Shall we maintain an installer as well(specially for VM cartridges) in > this repository to quickly create specific cartridges in puppet? What this > installer could do is, > > User has to provide the packs and

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-01 Thread Reka Thirunavukkarasu
Hi Gayan On Thu, Oct 1, 2015 at 6:16 PM, Gayan Gunarathne wrote: > > > On Thu, Oct 1, 2015 at 6:06 PM, Reka Thirunavukkarasu > wrote: > >> Hi >> >> Shall we maintain an installer as well(specially for VM cartridges) in >> this repository to quickly create

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-01 Thread Akila Ravihansa Perera
> > > > Shall we maintain an installer as well(specially for VM cartridges) in > this repository to quickly create specific cartridges in puppet? What this > installer could do is, > > User has to provide the packs and set of values for the environment > variables. > > - Install puppet master > -

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-01 Thread Reka Thirunavukkarasu
Hi Shall we maintain an installer as well(specially for VM cartridges) in this repository to quickly create specific cartridges in puppet? What this installer could do is, User has to provide the packs and set of values for the environment variables. - Install puppet master - Locate the

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-10-01 Thread Akila Ravihansa Perera
Hi Gayan, Wouldn't it be easier to navigate if we move those common folders to root folder? We can create a common folder under /plugins/ folder to keep common PCA plugins and util files. Just a thought...wdyt? Thanks. On Thu, Oct 1, 2015 at 10:29 AM, Gayan Gunarathne wrote:

Re: [Dev] [PPaaS] private-paas-cartridges repository structure

2015-09-30 Thread Gayan Gunarathne
Adding to the Dev list On Thu, Oct 1, 2015 at 7:05 AM, Imesh Gunaratne wrote: > Shall we move this discussion to Dev? > > Thanks > > On Wed, Sep 30, 2015 at 11:02 PM, Gayan Gunarathne > wrote: > >> As puppet,init-scripts,base image are common for all the