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

[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 cartridges, we will
have to add them again and if there's a new change we'll have to change it
everywhere(maintainability?)

WDYT?
If the priority/concern was regarding modularity, this approach is totally
fine for me.

Thanks,

On Sun, Oct 4, 2015 at 1:33 PM, Imesh Gunaratne  wrote:

> It looks good Akila!
>
> On Mon, Oct 5, 2015 at 12:01 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> 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
>> │   ├── configurator
>> │   │   ├── live-test
>> │   │   │   ├── src
>> │   │   ├── src
>> │   │   │   ├── assembly
>> │   │   │   └── main
>> │   ├── docker
>> │   │   ├── base-image
>> │   │   │   ├── packages
>> │   │   │   └── scripts
>> │   │   └── scripts
>> │   ├── plugins
>> │   └── vm
>> │   ├── assembly
>> │   ├── init-scripts
>> │   │   ├── ec2
>> │   │   ├── gce
>> │   │   ├── openstack
>> │   │   └── vcloud
>> │   ├── puppet
>> │   │   ├── manifests
>> │   │   └── modules
>> ├── wso2am
>> │   ├── 1.9.0
>> │   │   ├── assembly
>> │   │   ├── docker
>> │   │   │   ├── packages
>> │   │   │   ├── plugins
>> │   │   │   └── scripts
>> │   │   ├── plugins
>> │   │   ├── samples
>> │   │   │   ├── application-policies
>> │   │   │   ├── applications
>> │   │   │   ├── autoscaling-policies
>> │   │   │   ├── cartridge-groups
>> │   │   │   ├── cartridges
>> │   │   │   ├── deployment-policies
>> │   │   │   ├── kubernetes-clusters
>> │   │   │   ├── network-partitions
>> │   │   │   └── template-modules
>> │   │   └── template-module
>> │   │   ├── files
>> │   │   ├── src
>> │   │   └── templates
>> ├── wso2as
>> │   ├── 5.2.1
>> │   │   ├── assembly
>> │   │   ├── docker
>> │   │   │   ├── packages
>> │   │   │   ├── plugins
>> │   │   │   └── scripts
>> │   │   ├── plugins
>> │   │   ├── samples
>> │   │   │   ├── application-policies
>> │   │   │   ├── applications
>> │   │   │   ├── autoscaling-policies
>> │   │   │   ├── cartridge-groups
>> │   │   │   ├── cartridges
>> │   │   │   ├── deployment-policies
>> │   │   │   ├── kubernetes-clusters
>> │   │   │   ├── network-partitions
>> │   │   │   ├── signups
>> │   │   │   └── template-modules
>> │   │   └── template-module
>> │   │   ├── files
>> │   │   ├── src
>> │   │   └── templates
>> ├── wso2esb
>> │   ├── 4.8.1
>> │   │   ├── assembly
>> │   │   ├── docker
>> │   │   │   ├── packages
>> │   │   │   ├── plugins
>> │   │   │   └── scripts
>> │   │   ├── plugins
>> │   │   ├── samples
>> │   │   │   ├── application-policies
>> │   │   │   ├── applications
>> │   │   │   ├── autoscaling-policies
>> │   │   │   ├── cartridge-groups
>> │   │   │   ├── cartridges
>> │   │   │   ├── deployment-policies
>> │   │   │   ├── kubernetes-clusters
>> │   │   │   ├── network-partitions
>> │   │   │   ├── signups
>> │   │   │   └── template-modules
>> │   │   │   ├── archive-tmp
>> │   │   │   └── maven-shared-archive-resources
>> │   │   └── template-module
>> │   │   ├── files
>> │   │   ├── src
>> │   │   └── templates
>> └── wso2is
>> ├── 5.0.0
>> │   ├── assembly
>> │   ├── docker
>> │   │   ├── packages
>> │   │   ├── plugins
>> │   │   └── scripts
>> │   ├── plugins
>> │   ├── samples
>> │   │   ├── application-policies
>> │   │   ├── applications
>> │   │   ├── autoscaling-policies
>> │   │   ├── cartridge-groups
>> │   │   ├── cartridges
>> │   │   ├── deployment-policies
>> │   │   ├── kubernetes-clusters
>> │   │   ├── network-partitions
>> │   │   ├── signups
>> │   │   └── template-modules
>> │   └── template-module
>> │   ├── files
>> │   ├── src
>> │   └── templates
>>
>>
>> On Sun, Oct 4, 2015 at 10:04 PM, Imesh Gunaratne  wrote:
>>
>>> 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 we move the
 init-scripts folder inside /common/base-image/vm/ path?

>>>
>>> Yes, a good point! May be we can do the necessary changes.
>>>
>>> Thanks
>>>
>>> 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 

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

[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 them in a common place?
> (say inside common/samples/..). Once we introduce more cartridges, we will
> have to add them again and if there's a new change we'll have to change it
> everywhere(maintainability?)
>

​+1 to keep them in a common place. Why we are duplicating these common
artifacts across all the cartridges?
​


>
> WDYT?
> If the priority/concern was regarding modularity, this approach is totally
> fine for me.
>
> Thanks,
>
> On Sun, Oct 4, 2015 at 1:33 PM, Imesh Gunaratne  wrote:
>
>> It looks good Akila!
>>
>> On Mon, Oct 5, 2015 at 12:01 AM, Akila Ravihansa Perera <
>> raviha...@wso2.com> 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
>>> │   ├── configurator
>>> │   │   ├── live-test
>>> │   │   │   ├── src
>>> │   │   ├── src
>>> │   │   │   ├── assembly
>>> │   │   │   └── main
>>> │   ├── docker
>>> │   │   ├── base-image
>>> │   │   │   ├── packages
>>> │   │   │   └── scripts
>>> │   │   └── scripts
>>> │   ├── plugins
>>> │   └── vm
>>> │   ├── assembly
>>> │   ├── init-scripts
>>> │   │   ├── ec2
>>> │   │   ├── gce
>>> │   │   ├── openstack
>>> │   │   └── vcloud
>>> │   ├── puppet
>>> │   │   ├── manifests
>>> │   │   └── modules
>>> ├── wso2am
>>> │   ├── 1.9.0
>>> │   │   ├── assembly
>>> │   │   ├── docker
>>> │   │   │   ├── packages
>>> │   │   │   ├── plugins
>>> │   │   │   └── scripts
>>> │   │   ├── plugins
>>> │   │   ├── samples
>>> │   │   │   ├── application-policies
>>> │   │   │   ├── applications
>>> │   │   │   ├── autoscaling-policies
>>> │   │   │   ├── cartridge-groups
>>> │   │   │   ├── cartridges
>>> │   │   │   ├── deployment-policies
>>> │   │   │   ├── kubernetes-clusters
>>> │   │   │   ├── network-partitions
>>> │   │   │   └── template-modules
>>> │   │   └── template-module
>>> │   │   ├── files
>>> │   │   ├── src
>>> │   │   └── templates
>>> ├── wso2as
>>> │   ├── 5.2.1
>>> │   │   ├── assembly
>>> │   │   ├── docker
>>> │   │   │   ├── packages
>>> │   │   │   ├── plugins
>>> │   │   │   └── scripts
>>> │   │   ├── plugins
>>> │   │   ├── samples
>>> │   │   │   ├── application-policies
>>> │   │   │   ├── applications
>>> │   │   │   ├── autoscaling-policies
>>> │   │   │   ├── cartridge-groups
>>> │   │   │   ├── cartridges
>>> │   │   │   ├── deployment-policies
>>> │   │   │   ├── kubernetes-clusters
>>> │   │   │   ├── network-partitions
>>> │   │   │   ├── signups
>>> │   │   │   └── template-modules
>>> │   │   └── template-module
>>> │   │   ├── files
>>> │   │   ├── src
>>> │   │   └── templates
>>> ├── wso2esb
>>> │   ├── 4.8.1
>>> │   │   ├── assembly
>>> │   │   ├── docker
>>> │   │   │   ├── packages
>>> │   │   │   ├── plugins
>>> │   │   │   └── scripts
>>> │   │   ├── plugins
>>> │   │   ├── samples
>>> │   │   │   ├── application-policies
>>> │   │   │   ├── applications
>>> │   │   │   ├── autoscaling-policies
>>> │   │   │   ├── cartridge-groups
>>> │   │   │   ├── cartridges
>>> │   │   │   ├── deployment-policies
>>> │   │   │   ├── kubernetes-clusters
>>> │   │   │   ├── network-partitions
>>> │   │   │   ├── signups
>>> │   │   │   └── template-modules
>>> │   │   │   ├── archive-tmp
>>> │   │   │   └── maven-shared-archive-resources
>>> │   │   └── template-module
>>> │   │   ├── files
>>> │   │   ├── src
>>> │   │   └── templates
>>> └── wso2is
>>> ├── 5.0.0
>>> │   ├── assembly
>>> │   ├── docker
>>> │   │   ├── packages
>>> │   │   ├── plugins
>>> │   │   └── scripts
>>> │   ├── plugins
>>> │   ├── samples
>>> │   │   ├── application-policies
>>> │   │   ├── applications
>>> │   │   ├── autoscaling-policies
>>> │   │   ├── cartridge-groups
>>> │   │   ├── cartridges
>>> │   │   ├── deployment-policies
>>> │   │   ├── kubernetes-clusters
>>> │   │   ├── network-partitions
>>> │   │   ├── signups
>>> │   │   └── template-modules
>>> │   └── template-module
>>> │   ├── files
>>> │   ├── src
>>> │   └── templates
>>>
>>>
>>> On Sun, Oct 4, 2015 at 10:04 PM, Imesh Gunaratne  wrote:
>>>
 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 we move the
> init-scripts folder inside 

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

[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  > 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 them in a common place?
>> (say inside common/samples/..).
>>
>
> +1 A good suggestion! Yes we could move above artifacts to common/samples
> folder. However when we are creating the cartridge distribution we may need
> to copy them to the cartridge/samples folder similar to common/plugins.
>
> Thanks
>
> On Wed, Oct 7, 2015 at 2:50 AM, Rajkumar Rajaratnam  > wrote:
>
>>
>>
>> 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 them in a common place?
>>> (say inside common/samples/..). Once we introduce more cartridges, we will
>>> have to add them again and if there's a new change we'll have to change it
>>> everywhere(maintainability?)
>>>
>>
>> ​+1 to keep them in a common place. Why we are duplicating these common
>> artifacts across all the cartridges?
>> ​
>>
>>
>>>
>>> WDYT?
>>> If the priority/concern was regarding modularity, this approach is
>>> totally fine for me.
>>>
>>> Thanks,
>>>
>>> On Sun, Oct 4, 2015 at 1:33 PM, Imesh Gunaratne >> > wrote:
>>>
 It looks good Akila!

 On Mon, Oct 5, 2015 at 12:01 AM, Akila Ravihansa Perera <
 raviha...@wso2.com 
 > 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
> │   ├── configurator
> │   │   ├── live-test
> │   │   │   ├── src
> │   │   ├── src
> │   │   │   ├── assembly
> │   │   │   └── main
> │   ├── docker
> │   │   ├── base-image
> │   │   │   ├── packages
> │   │   │   └── scripts
> │   │   └── scripts
> │   ├── plugins
> │   └── vm
> │   ├── assembly
> │   ├── init-scripts
> │   │   ├── ec2
> │   │   ├── gce
> │   │   ├── openstack
> │   │   └── vcloud
> │   ├── puppet
> │   │   ├── manifests
> │   │   └── modules
> ├── wso2am
> │   ├── 1.9.0
> │   │   ├── assembly
> │   │   ├── docker
> │   │   │   ├── packages
> │   │   │   ├── plugins
> │   │   │   └── scripts
> │   │   ├── plugins
> │   │   ├── samples
> │   │   │   ├── application-policies
> │   │   │   ├── applications
> │   │   │   ├── autoscaling-policies
> │   │   │   ├── cartridge-groups
> │   │   │   ├── cartridges
> │   │   │   ├── deployment-policies
> │   │   │   ├── kubernetes-clusters
> │   │   │   ├── network-partitions
> │   │   │   └── template-modules
> │   │   └── template-module
> │   │   ├── files
> │   │   ├── src
> │   │   └── templates
> ├── wso2as
> │   ├── 5.2.1
> │   │   ├── assembly
> │   │   ├── docker
> │   │   │   ├── packages
> │   │   │   ├── plugins
> │   │   │   └── scripts
> │   │   ├── plugins
> │   │   ├── samples
> │   │   │   ├── application-policies
> │   │   │   ├── applications
> │   │   │   ├── autoscaling-policies
> │   │   │   ├── cartridge-groups
> │   │   │   ├── cartridges
> │   │   │   ├── deployment-policies
> │   │   │   ├── kubernetes-clusters
> │   │   │   ├── network-partitions
> │   │   │   ├── signups
> │   │   │   └── template-modules
> │   │   └── template-module
> │   │   ├── files
> │   │   ├── src
> │   │   └── templates
> ├── wso2esb
> │   ├── 4.8.1
> │   │   ├── assembly
> │   │   ├── docker
> │   │   │   ├── packages
> │   │   │   ├── plugins
> │   │   │   └── scripts
> │   │   ├── plugins
> │   │   ├── samples
> │   │   │   ├── application-policies
> │   │   │   ├── applications
> │   │   │   ├── autoscaling-policies
> │   │   │   ├── cartridge-groups
> │   │   │   ├── cartridges
> │   │   │   ├── deployment-policies
> │   │   │   ├── kubernetes-clusters
> │  

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

[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 them in a common place?
> (say inside common/samples/..).
>

+1 A good suggestion! Yes we could move above artifacts to common/samples
folder. However when we are creating the cartridge distribution we may need
to copy them to the cartridge/samples folder similar to common/plugins.

Thanks

On Wed, Oct 7, 2015 at 2:50 AM, Rajkumar Rajaratnam 
wrote:

>
>
> 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 them in a common place?
>> (say inside common/samples/..). Once we introduce more cartridges, we will
>> have to add them again and if there's a new change we'll have to change it
>> everywhere(maintainability?)
>>
>
> ​+1 to keep them in a common place. Why we are duplicating these common
> artifacts across all the cartridges?
> ​
>
>
>>
>> WDYT?
>> If the priority/concern was regarding modularity, this approach is
>> totally fine for me.
>>
>> Thanks,
>>
>> On Sun, Oct 4, 2015 at 1:33 PM, Imesh Gunaratne  wrote:
>>
>>> It looks good Akila!
>>>
>>> On Mon, Oct 5, 2015 at 12:01 AM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> 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
 │   ├── configurator
 │   │   ├── live-test
 │   │   │   ├── src
 │   │   ├── src
 │   │   │   ├── assembly
 │   │   │   └── main
 │   ├── docker
 │   │   ├── base-image
 │   │   │   ├── packages
 │   │   │   └── scripts
 │   │   └── scripts
 │   ├── plugins
 │   └── vm
 │   ├── assembly
 │   ├── init-scripts
 │   │   ├── ec2
 │   │   ├── gce
 │   │   ├── openstack
 │   │   └── vcloud
 │   ├── puppet
 │   │   ├── manifests
 │   │   └── modules
 ├── wso2am
 │   ├── 1.9.0
 │   │   ├── assembly
 │   │   ├── docker
 │   │   │   ├── packages
 │   │   │   ├── plugins
 │   │   │   └── scripts
 │   │   ├── plugins
 │   │   ├── samples
 │   │   │   ├── application-policies
 │   │   │   ├── applications
 │   │   │   ├── autoscaling-policies
 │   │   │   ├── cartridge-groups
 │   │   │   ├── cartridges
 │   │   │   ├── deployment-policies
 │   │   │   ├── kubernetes-clusters
 │   │   │   ├── network-partitions
 │   │   │   └── template-modules
 │   │   └── template-module
 │   │   ├── files
 │   │   ├── src
 │   │   └── templates
 ├── wso2as
 │   ├── 5.2.1
 │   │   ├── assembly
 │   │   ├── docker
 │   │   │   ├── packages
 │   │   │   ├── plugins
 │   │   │   └── scripts
 │   │   ├── plugins
 │   │   ├── samples
 │   │   │   ├── application-policies
 │   │   │   ├── applications
 │   │   │   ├── autoscaling-policies
 │   │   │   ├── cartridge-groups
 │   │   │   ├── cartridges
 │   │   │   ├── deployment-policies
 │   │   │   ├── kubernetes-clusters
 │   │   │   ├── network-partitions
 │   │   │   ├── signups
 │   │   │   └── template-modules
 │   │   └── template-module
 │   │   ├── files
 │   │   ├── src
 │   │   └── templates
 ├── wso2esb
 │   ├── 4.8.1
 │   │   ├── assembly
 │   │   ├── docker
 │   │   │   ├── packages
 │   │   │   ├── plugins
 │   │   │   └── scripts
 │   │   ├── plugins
 │   │   ├── samples
 │   │   │   ├── application-policies
 │   │   │   ├── applications
 │   │   │   ├── autoscaling-policies
 │   │   │   ├── cartridge-groups
 │   │   │   ├── cartridges
 │   │   │   ├── deployment-policies
 │   │   │   ├── kubernetes-clusters
 │   │   │   ├── network-partitions
 │   │   │   ├── signups
 │   │   │   └── template-modules
 │   │   │   ├── archive-tmp
 │   │   │   └── maven-shared-archive-resources
 │   │   └── template-module
 │   │   ├── files
 │   │   ├── src
 │   │   └── templates
 └── wso2is
 ├── 5.0.0
 │   ├── assembly
 │   ├── docker
 │   │   ├── packages
 │   │   ├── plugins
 │   │   └── scripts
 │   ├── plugins
 │   ├── samples
 │   │   ├── application-policies
 │   │   ├── applications
 │   │   ├── autoscaling-policies
 │   │   ├── 

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

[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 we move the
> init-scripts folder inside /common/base-image/vm/ path?
>

Yes, a good point! May be we can do the necessary changes.

Thanks

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 we move the
> init-scripts folder inside /common/base-image/vm/ path?
>
> ├── common
> │   ├── base-image
> │   │   └── docker
> │   ├── common-plugins
> │   │   ├── wso2-cleanup-handler.py
> │   │   └── wso2-cleanup-handler.yapsy-plugin
> │   ├── configurator
> │   │   ├── live-test
> │   │   ├── org.wso2.ppaas.cartridges.common.configurator.iml
> │   │   ├── pom.xml
> │   │   ├── README.md
> │   │   ├── src
> │   │   └── target
> │   ├── init-scripts
> │   │   ├── ec2
> │   │   ├── gce
> │   │   ├── openstack
> │   │   ├── README.md
> │   │   └── vcloud
>
> Thanks.
>
> On Thu, Oct 1, 2015 at 6:32 PM, Reka Thirunavukkarasu 
> wrote:
>
>> 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 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 relevant cartridges puppet modules
 - Place the packs, template modules and plugins to right location
 - Export all the user given environment variables
 - Execute configurator to configure the samples

 WDYT?

>>>
>>> Good thought reka. As our offline chat , we can plan to have two
>>> installers for ppaas and ppaas cartridges.We can have the ppaas installer
>>> to set up the ppaas related stuff while ppaas cartridge installer to set up
>>> the cartridge specific installations.
>>>
>> +1. We can check whether we can modify the stratos-installer and use it
>> as a ppaas-installer rather writing it from the scratch.
>>
>> Thanks,
>> Reka
>>
>>>
 Thanks,
 Reka

 On Thu, Oct 1, 2015 at 2:01 PM, Gayan Gunarathne 
 wrote:

> Hi Akila,
>
> Common folder has all the common stuff related to the cartridges.So if
> someone can navigate to the common folder and get the stuff shared among
> the cartridges.
>
> I think it is meaningful to have those common stuff at a one place,
> then someone new to this repository also have a feeling those stuff will 
> be
> common for all the cartridges.Common PCA plugins and utils also we can 
> have
> inside the common folder
>
> Thanks,
> Gayan
>
> On Thu, Oct 1, 2015 at 12:52 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> 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:
>>
>>> 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
> cartridges,shall we group them under common?
> Also what about the configurator?I can see two options
> One option will be move the configurator to the private-paas
> repository and release it with the private paas.Other option will be 
> we can
> do the separate release for the configurator.Seems it is better to 
> have a
> separate release for the configurator. WDYT?
>
> Thanks,
> Gayan
>
> On Wed, Sep 30, 2015 at 10:44 PM, Gayan Gunarathne <
> gay...@wso2.com> wrote:
>
>> Hi,
>>
>> On Wed, Sep 30, 2015 at 9:48 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> +1 for having a simple folder structure. I think we can move the
>>> contents in /common/ 

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

[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 
 wrote:
>
>
> I'm looking into creating a single set of templates using Jinja template
> language to cater for all IaaS requirements. We can maintain separate set
> of module.ini files to create artifacts for different IaaS's.
>

+1 My initial thought was to make the existing set of files in the samples
folder, Jinja2 templates. If so we don't need to maintain another set of
the same file set as the templates.

On Thu, Oct 1, 2015 at 6:16 PM, Gayan Gunarathne  wrote:
>
>
> Good thought reka. As our offline chat , we can plan to have two
> installers for ppaas and ppaas cartridges.We can have the ppaas installer
> to set up the ppaas related stuff while ppaas cartridge installer to set up
> the cartridge specific installations.
>

Would it be difficult to handle this using a single installer? IMO having
two installers would confuse the users and add more overhead to the
installation process.

May be we can introduce a separate installer for the cartridges (assuming
that there could be cartridge specific requirements to be added to the
installer) and integrate it with the private paas installer. This would
nicely decouple cartridge installation steps from the private paas
installer and at the same time give a better user experience. WDYT?

Thanks

-- 
*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

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

[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
> │   ├── configurator
> │   │   ├── live-test
> │   │   │   ├── src
> │   │   ├── src
> │   │   │   ├── assembly
> │   │   │   └── main
> │   ├── docker
> │   │   ├── base-image
> │   │   │   ├── packages
> │   │   │   └── scripts
> │   │   └── scripts
> │   ├── plugins
> │   └── vm
> │   ├── assembly
> │   ├── init-scripts
> │   │   ├── ec2
> │   │   ├── gce
> │   │   ├── openstack
> │   │   └── vcloud
> │   ├── puppet
> │   │   ├── manifests
> │   │   └── modules
> ├── wso2am
> │   ├── 1.9.0
> │   │   ├── assembly
> │   │   ├── docker
> │   │   │   ├── packages
> │   │   │   ├── plugins
> │   │   │   └── scripts
> │   │   ├── plugins
> │   │   ├── samples
> │   │   │   ├── application-policies
> │   │   │   ├── applications
> │   │   │   ├── autoscaling-policies
> │   │   │   ├── cartridge-groups
> │   │   │   ├── cartridges
> │   │   │   ├── deployment-policies
> │   │   │   ├── kubernetes-clusters
> │   │   │   ├── network-partitions
> │   │   │   └── template-modules
> │   │   └── template-module
> │   │   ├── files
> │   │   ├── src
> │   │   └── templates
> ├── wso2as
> │   ├── 5.2.1
> │   │   ├── assembly
> │   │   ├── docker
> │   │   │   ├── packages
> │   │   │   ├── plugins
> │   │   │   └── scripts
> │   │   ├── plugins
> │   │   ├── samples
> │   │   │   ├── application-policies
> │   │   │   ├── applications
> │   │   │   ├── autoscaling-policies
> │   │   │   ├── cartridge-groups
> │   │   │   ├── cartridges
> │   │   │   ├── deployment-policies
> │   │   │   ├── kubernetes-clusters
> │   │   │   ├── network-partitions
> │   │   │   ├── signups
> │   │   │   └── template-modules
> │   │   └── template-module
> │   │   ├── files
> │   │   ├── src
> │   │   └── templates
> ├── wso2esb
> │   ├── 4.8.1
> │   │   ├── assembly
> │   │   ├── docker
> │   │   │   ├── packages
> │   │   │   ├── plugins
> │   │   │   └── scripts
> │   │   ├── plugins
> │   │   ├── samples
> │   │   │   ├── application-policies
> │   │   │   ├── applications
> │   │   │   ├── autoscaling-policies
> │   │   │   ├── cartridge-groups
> │   │   │   ├── cartridges
> │   │   │   ├── deployment-policies
> │   │   │   ├── kubernetes-clusters
> │   │   │   ├── network-partitions
> │   │   │   ├── signups
> │   │   │   └── template-modules
> │   │   │   ├── archive-tmp
> │   │   │   └── maven-shared-archive-resources
> │   │   └── template-module
> │   │   ├── files
> │   │   ├── src
> │   │   └── templates
> └── wso2is
> ├── 5.0.0
> │   ├── assembly
> │   ├── docker
> │   │   ├── packages
> │   │   ├── plugins
> │   │   └── scripts
> │   ├── plugins
> │   ├── samples
> │   │   ├── application-policies
> │   │   ├── applications
> │   │   ├── autoscaling-policies
> │   │   ├── cartridge-groups
> │   │   ├── cartridges
> │   │   ├── deployment-policies
> │   │   ├── kubernetes-clusters
> │   │   ├── network-partitions
> │   │   ├── signups
> │   │   └── template-modules
> │   └── template-module
> │   ├── files
> │   ├── src
> │   └── templates
>
>
> On Sun, Oct 4, 2015 at 10:04 PM, Imesh Gunaratne  wrote:
>
>> 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 we move the
>>> init-scripts folder inside /common/base-image/vm/ path?
>>>
>>
>> Yes, a good point! May be we can do the necessary changes.
>>
>> Thanks
>>
>> 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 we move the
>>> init-scripts folder inside /common/base-image/vm/ path?
>>>
>>> ├── common
>>> │   ├── base-image
>>> │   │   └── docker
>>> │   ├── common-plugins
>>> │   │   ├── wso2-cleanup-handler.py
>>> │   │   └── wso2-cleanup-handler.yapsy-plugin
>>> │   ├── configurator
>>> │   │   ├── live-test
>>> │   │   ├── org.wso2.ppaas.cartridges.common.configurator.iml
>>> │   │   ├── pom.xml
>>> │   │   ├── README.md
>>> │   │   ├── src
>>> │   │   └── target
>>> │   ├── init-scripts
>>> │   │   ├── ec2
>>> │   │   ├── gce
>>> │   │   ├── openstack
>>> │   │   ├── README.md
>>> │   │   └── vcloud
>>>
>>> Thanks.
>>>
>>> On Thu, Oct 1, 2015 at 6:32 PM, Reka Thirunavukkarasu 

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

[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
│   ├── docker
│   │   ├── base-image
│   │   │   ├── packages
│   │   │   └── scripts
│   │   └── scripts
│   ├── plugins
│   └── vm
│   ├── assembly
│   ├── init-scripts
│   │   ├── ec2
│   │   ├── gce
│   │   ├── openstack
│   │   └── vcloud
│   ├── puppet
│   │   ├── manifests
│   │   └── modules
├── wso2am
│   ├── 1.9.0
│   │   ├── assembly
│   │   ├── docker
│   │   │   ├── packages
│   │   │   ├── plugins
│   │   │   └── scripts
│   │   ├── plugins
│   │   ├── samples
│   │   │   ├── application-policies
│   │   │   ├── applications
│   │   │   ├── autoscaling-policies
│   │   │   ├── cartridge-groups
│   │   │   ├── cartridges
│   │   │   ├── deployment-policies
│   │   │   ├── kubernetes-clusters
│   │   │   ├── network-partitions
│   │   │   └── template-modules
│   │   └── template-module
│   │   ├── files
│   │   ├── src
│   │   └── templates
├── wso2as
│   ├── 5.2.1
│   │   ├── assembly
│   │   ├── docker
│   │   │   ├── packages
│   │   │   ├── plugins
│   │   │   └── scripts
│   │   ├── plugins
│   │   ├── samples
│   │   │   ├── application-policies
│   │   │   ├── applications
│   │   │   ├── autoscaling-policies
│   │   │   ├── cartridge-groups
│   │   │   ├── cartridges
│   │   │   ├── deployment-policies
│   │   │   ├── kubernetes-clusters
│   │   │   ├── network-partitions
│   │   │   ├── signups
│   │   │   └── template-modules
│   │   └── template-module
│   │   ├── files
│   │   ├── src
│   │   └── templates
├── wso2esb
│   ├── 4.8.1
│   │   ├── assembly
│   │   ├── docker
│   │   │   ├── packages
│   │   │   ├── plugins
│   │   │   └── scripts
│   │   ├── plugins
│   │   ├── samples
│   │   │   ├── application-policies
│   │   │   ├── applications
│   │   │   ├── autoscaling-policies
│   │   │   ├── cartridge-groups
│   │   │   ├── cartridges
│   │   │   ├── deployment-policies
│   │   │   ├── kubernetes-clusters
│   │   │   ├── network-partitions
│   │   │   ├── signups
│   │   │   └── template-modules
│   │   │   ├── archive-tmp
│   │   │   └── maven-shared-archive-resources
│   │   └── template-module
│   │   ├── files
│   │   ├── src
│   │   └── templates
└── wso2is
├── 5.0.0
│   ├── assembly
│   ├── docker
│   │   ├── packages
│   │   ├── plugins
│   │   └── scripts
│   ├── plugins
│   ├── samples
│   │   ├── application-policies
│   │   ├── applications
│   │   ├── autoscaling-policies
│   │   ├── cartridge-groups
│   │   ├── cartridges
│   │   ├── deployment-policies
│   │   ├── kubernetes-clusters
│   │   ├── network-partitions
│   │   ├── signups
│   │   └── template-modules
│   └── template-module
│   ├── files
│   ├── src
│   └── templates


On Sun, Oct 4, 2015 at 10:04 PM, Imesh Gunaratne  wrote:

> 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 we move the
>> init-scripts folder inside /common/base-image/vm/ path?
>>
>
> Yes, a good point! May be we can do the necessary changes.
>
> Thanks
>
> 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 we move the
>> init-scripts folder inside /common/base-image/vm/ path?
>>
>> ├── common
>> │   ├── base-image
>> │   │   └── docker
>> │   ├── common-plugins
>> │   │   ├── wso2-cleanup-handler.py
>> │   │   └── wso2-cleanup-handler.yapsy-plugin
>> │   ├── configurator
>> │   │   ├── live-test
>> │   │   ├── org.wso2.ppaas.cartridges.common.configurator.iml
>> │   │   ├── pom.xml
>> │   │   ├── README.md
>> │   │   ├── src
>> │   │   └── target
>> │   ├── init-scripts
>> │   │   ├── ec2
>> │   │   ├── gce
>> │   │   ├── openstack
>> │   │   ├── README.md
>> │   │   └── vcloud
>>
>> Thanks.
>>
>> On Thu, Oct 1, 2015 at 6:32 PM, Reka Thirunavukkarasu 
>> wrote:
>>
>>> 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 specific cartridges in puppet? What this

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

[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
│   │   └── docker
│   ├── common-plugins
│   │   ├── wso2-cleanup-handler.py
│   │   └── wso2-cleanup-handler.yapsy-plugin
│   ├── configurator
│   │   ├── live-test
│   │   ├── org.wso2.ppaas.cartridges.common.configurator.iml
│   │   ├── pom.xml
│   │   ├── README.md
│   │   ├── src
│   │   └── target
│   ├── init-scripts
│   │   ├── ec2
│   │   ├── gce
│   │   ├── openstack
│   │   ├── README.md
│   │   └── vcloud

Thanks.

On Thu, Oct 1, 2015 at 6:32 PM, Reka Thirunavukkarasu  wrote:

> 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 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 relevant cartridges puppet modules
>>> - Place the packs, template modules and plugins to right location
>>> - Export all the user given environment variables
>>> - Execute configurator to configure the samples
>>>
>>> WDYT?
>>>
>>
>> Good thought reka. As our offline chat , we can plan to have two
>> installers for ppaas and ppaas cartridges.We can have the ppaas installer
>> to set up the ppaas related stuff while ppaas cartridge installer to set up
>> the cartridge specific installations.
>>
> +1. We can check whether we can modify the stratos-installer and use it as
> a ppaas-installer rather writing it from the scratch.
>
> Thanks,
> Reka
>
>>
>>> Thanks,
>>> Reka
>>>
>>> On Thu, Oct 1, 2015 at 2:01 PM, Gayan Gunarathne 
>>> wrote:
>>>
 Hi Akila,

 Common folder has all the common stuff related to the cartridges.So if
 someone can navigate to the common folder and get the stuff shared among
 the cartridges.

 I think it is meaningful to have those common stuff at a one place,
 then someone new to this repository also have a feeling those stuff will be
 common for all the cartridges.Common PCA plugins and utils also we can have
 inside the common folder

 Thanks,
 Gayan

 On Thu, Oct 1, 2015 at 12:52 PM, Akila Ravihansa Perera <
 raviha...@wso2.com> wrote:

> 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:
>
>> 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
 cartridges,shall we group them under common?
 Also what about the configurator?I can see two options
 One option will be move the configurator to the private-paas
 repository and release it with the private paas.Other option will be 
 we can
 do the separate release for the configurator.Seems it is better to 
 have a
 separate release for the configurator. WDYT?

 Thanks,
 Gayan

 On Wed, Sep 30, 2015 at 10:44 PM, Gayan Gunarathne  wrote:

> Hi,
>
> On Wed, Sep 30, 2015 at 9:48 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> +1 for having a simple folder structure. I think we can move the
>> contents in /common/ folder to root folder. One can easily identify 
>> the
>> important files available and easy to navigate as well.
>>
>> What should be the Maven groupId for this repo? How about
>> "org.wso2.ppaas.cartridges" or "org.wso2.cartridges" ?
>>
> We can use org.wso2.ppaas.cartridges as groupId
>
> Thanks,
> Gayan
>
>
>>
>
>> On Wed, Sep 30, 2015 at 9:24 PM, Imesh Gunaratne 
>> wrote:
>>
>>>  I would like to reduce the complexity of the folder structure
>>> and make it much simple. Shall we have some thing like below:
>>>
>>> 

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

[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 Ravihansa Perera 
wrote:

> 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:
>
>> 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
 cartridges,shall we group them under common?
 Also what about the configurator?I can see two options
 One option will be move the configurator to the private-paas repository
 and release it with the private paas.Other option will be we can do the
 separate release for the configurator.Seems it is better to have a separate
 release for the configurator. WDYT?

 Thanks,
 Gayan

 On Wed, Sep 30, 2015 at 10:44 PM, Gayan Gunarathne 
 wrote:

> Hi,
>
> On Wed, Sep 30, 2015 at 9:48 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> +1 for having a simple folder structure. I think we can move the
>> contents in /common/ folder to root folder. One can easily identify the
>> important files available and easy to navigate as well.
>>
>> What should be the Maven groupId for this repo? How about
>> "org.wso2.ppaas.cartridges" or "org.wso2.cartridges" ?
>>
> We can use org.wso2.ppaas.cartridges as groupId
>
> Thanks,
> Gayan
>
>
>>
>
>> On Wed, Sep 30, 2015 at 9:24 PM, Imesh Gunaratne 
>> wrote:
>>
>>>  I would like to reduce the complexity of the folder structure and
>>> make it much simple. Shall we have some thing like below:
>>>
>>> private-paas-cartridges/
>>> |--/common/
>>>|--/configurator/
>>>|--/puppet/
>>>   |--/wso2-installer/
>>>|--/scripts/
>>>   |---/ec2/init.sh
>>>   |---/openstack/init.sh
>>>
>>> |--/wso2esb/4.9.0/
>>>|-/template-module/
>>>|-/cartridge-agent-plugins/
>>>|-/application/
>>>|-/docker/
>>>
>>> Thanks
>>>
>>> On Wed, Sep 30, 2015 at 9:13 PM, Imesh Gunaratne 
>>> wrote:
>>>
 May be we can have this discussion in Dev, I cannot see any reason
 to take this private.

 Thanks

 On Wed, Sep 30, 2015 at 6:26 PM, Gayan Gunarathne 
 wrote:

> Adding Engineering group
>
>
> -- Forwarded message --
> From: Gayan Gunarathne 
> Date: Wed, Sep 30, 2015 at 6:26 PM
> Subject: [PPaaS] private-paas-cartridges repository structure
> To: Imesh Gunaratne , Reka Thirunavukkarasu <
> r...@wso2.com>, Udara Liyanage , Lahiru
> Sandaruwan , Rajkumar Rajaratnam <
> rajkum...@wso2.com>, Sajith Kariyawasam , Isuru
> Haththotuwa , Lasindu Charith ,
> Akila Ravihansa Perera , Chamila De Alwis <
> chami...@wso2.com>, Vishanth Balasubramaniam ,
> Dinithi De Silva , Anuruddha Liyanarachchi <
> anurudd...@wso2.com>, Pubudu Gunatilaka ,
> Thanuja Uruththirakodeeswaran 
>
>
> Hi All,
>
> Shall we have the following structure with
> the private-paas-cartridges[1] repository
>
> 1. Maintain the separate directory for each cartridge
>
> Suggested directory structure as following
>
> .
>
> ├── base-image
>
> │   └── docker
>
> │   └── scripts
>
> │   └── start-agent.sh
>
> ├── vm
>
> │   ├── init-scripts
>
> │   │
>
> │   ├── puppet
>
> │   │

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

[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 set of values for the environment
> variables.
>
> - Install puppet master
> - Locate the relevant cartridges puppet modules
> - Place the packs, template modules and plugins to right location
> - Export all the user given environment variables
> - Execute configurator to configure the samples
>
> WDYT?
>

Good thought reka. As our offline chat , we can plan to have two installers
for ppaas and ppaas cartridges.We can have the ppaas installer to set up
the ppaas related stuff while ppaas cartridge installer to set up the
cartridge specific installations.

>
> Thanks,
> Reka
>
> On Thu, Oct 1, 2015 at 2:01 PM, Gayan Gunarathne  wrote:
>
>> Hi Akila,
>>
>> Common folder has all the common stuff related to the cartridges.So if
>> someone can navigate to the common folder and get the stuff shared among
>> the cartridges.
>>
>> I think it is meaningful to have those common stuff at a one place, then
>> someone new to this repository also have a feeling those stuff will be
>> common for all the cartridges.Common PCA plugins and utils also we can have
>> inside the common folder
>>
>> Thanks,
>> Gayan
>>
>> On Thu, Oct 1, 2015 at 12:52 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> 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:
>>>
 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
>> cartridges,shall we group them under common?
>> Also what about the configurator?I can see two options
>> One option will be move the configurator to the private-paas
>> repository and release it with the private paas.Other option will be we 
>> can
>> do the separate release for the configurator.Seems it is better to have a
>> separate release for the configurator. WDYT?
>>
>> Thanks,
>> Gayan
>>
>> On Wed, Sep 30, 2015 at 10:44 PM, Gayan Gunarathne 
>> wrote:
>>
>>> Hi,
>>>
>>> On Wed, Sep 30, 2015 at 9:48 PM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 +1 for having a simple folder structure. I think we can move the
 contents in /common/ folder to root folder. One can easily identify the
 important files available and easy to navigate as well.

 What should be the Maven groupId for this repo? How about
 "org.wso2.ppaas.cartridges" or "org.wso2.cartridges" ?

>>> We can use org.wso2.ppaas.cartridges as groupId
>>>
>>> Thanks,
>>> Gayan
>>>
>>>

>>>
 On Wed, Sep 30, 2015 at 9:24 PM, Imesh Gunaratne 
 wrote:

>  I would like to reduce the complexity of the folder structure and
> make it much simple. Shall we have some thing like below:
>
> private-paas-cartridges/
> |--/common/
>|--/configurator/
>|--/puppet/
>   |--/wso2-installer/
>|--/scripts/
>   |---/ec2/init.sh
>   |---/openstack/init.sh
>
> |--/wso2esb/4.9.0/
>|-/template-module/
>|-/cartridge-agent-plugins/
>|-/application/
>|-/docker/
>
> Thanks
>
> On Wed, Sep 30, 2015 at 9:13 PM, Imesh Gunaratne 
> wrote:
>
>> May be we can have this discussion in Dev, I cannot see any
>> reason to take this private.
>>
>> Thanks
>>
>> On Wed, Sep 30, 2015 at 6:26 PM, Gayan Gunarathne <
>> gay...@wso2.com> wrote:
>>
>>> Adding Engineering group
>>>
>>>
>>> -- Forwarded message --
>>> From: Gayan Gunarathne 
>>> Date: Wed, Sep 30, 2015 at 6:26 

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

[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 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 relevant cartridges puppet modules
>> - Place the packs, template modules and plugins to right location
>> - Export all the user given environment variables
>> - Execute configurator to configure the samples
>>
>> WDYT?
>>
>
> Good thought reka. As our offline chat , we can plan to have two
> installers for ppaas and ppaas cartridges.We can have the ppaas installer
> to set up the ppaas related stuff while ppaas cartridge installer to set up
> the cartridge specific installations.
>
+1. We can check whether we can modify the stratos-installer and use it as
a ppaas-installer rather writing it from the scratch.

Thanks,
Reka

>
>> Thanks,
>> Reka
>>
>> On Thu, Oct 1, 2015 at 2:01 PM, Gayan Gunarathne  wrote:
>>
>>> Hi Akila,
>>>
>>> Common folder has all the common stuff related to the cartridges.So if
>>> someone can navigate to the common folder and get the stuff shared among
>>> the cartridges.
>>>
>>> I think it is meaningful to have those common stuff at a one place, then
>>> someone new to this repository also have a feeling those stuff will be
>>> common for all the cartridges.Common PCA plugins and utils also we can have
>>> inside the common folder
>>>
>>> Thanks,
>>> Gayan
>>>
>>> On Thu, Oct 1, 2015 at 12:52 PM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 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:

> 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
>>> cartridges,shall we group them under common?
>>> Also what about the configurator?I can see two options
>>> One option will be move the configurator to the private-paas
>>> repository and release it with the private paas.Other option will be we 
>>> can
>>> do the separate release for the configurator.Seems it is better to have 
>>> a
>>> separate release for the configurator. WDYT?
>>>
>>> Thanks,
>>> Gayan
>>>
>>> On Wed, Sep 30, 2015 at 10:44 PM, Gayan Gunarathne 
>>> wrote:
>>>
 Hi,

 On Wed, Sep 30, 2015 at 9:48 PM, Akila Ravihansa Perera <
 raviha...@wso2.com> wrote:

> +1 for having a simple folder structure. I think we can move the
> contents in /common/ folder to root folder. One can easily identify 
> the
> important files available and easy to navigate as well.
>
> What should be the Maven groupId for this repo? How about
> "org.wso2.ppaas.cartridges" or "org.wso2.cartridges" ?
>
 We can use org.wso2.ppaas.cartridges as groupId

 Thanks,
 Gayan


>

> On Wed, Sep 30, 2015 at 9:24 PM, Imesh Gunaratne 
> wrote:
>
>>  I would like to reduce the complexity of the folder structure
>> and make it much simple. Shall we have some thing like below:
>>
>> private-paas-cartridges/
>> |--/common/
>>|--/configurator/
>>|--/puppet/
>>   |--/wso2-installer/
>>|--/scripts/
>>   |---/ec2/init.sh
>>   |---/openstack/init.sh
>>
>> |--/wso2esb/4.9.0/
>>|-/template-module/
>>|-/cartridge-agent-plugins/
>>|-/application/
>>|-/docker/
>>
>> Thanks
>>
>> On Wed, Sep 30, 2015 at 9:13 PM, Imesh Gunaratne 
>> wrote:
>>
>>> May be we can have this discussion in Dev, I cannot see 

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

[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
> - Locate the relevant cartridges puppet modules
> - Place the packs, template modules and plugins to right location
> - Export all the user given environment variables
> - Execute configurator to configure the samples
>
> WDYT?
>
> Thanks,
> Reka
>


Big +1

I'm looking into creating a single set of templates using Jinja template
language to cater for all IaaS requirements. We can maintain separate set
of module.ini files to create artifacts for different IaaS's. This we can
reduce the complexity in current sample folder structure.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[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 relevant cartridges puppet modules
- Place the packs, template modules and plugins to right location
- Export all the user given environment variables
- Execute configurator to configure the samples

WDYT?

Thanks,
Reka

On Thu, Oct 1, 2015 at 2:01 PM, Gayan Gunarathne  wrote:

> Hi Akila,
>
> Common folder has all the common stuff related to the cartridges.So if
> someone can navigate to the common folder and get the stuff shared among
> the cartridges.
>
> I think it is meaningful to have those common stuff at a one place, then
> someone new to this repository also have a feeling those stuff will be
> common for all the cartridges.Common PCA plugins and utils also we can have
> inside the common folder
>
> Thanks,
> Gayan
>
> On Thu, Oct 1, 2015 at 12:52 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> 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:
>>
>>> 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
> cartridges,shall we group them under common?
> Also what about the configurator?I can see two options
> One option will be move the configurator to the private-paas
> repository and release it with the private paas.Other option will be we 
> can
> do the separate release for the configurator.Seems it is better to have a
> separate release for the configurator. WDYT?
>
> Thanks,
> Gayan
>
> On Wed, Sep 30, 2015 at 10:44 PM, Gayan Gunarathne 
> wrote:
>
>> Hi,
>>
>> On Wed, Sep 30, 2015 at 9:48 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> +1 for having a simple folder structure. I think we can move the
>>> contents in /common/ folder to root folder. One can easily identify the
>>> important files available and easy to navigate as well.
>>>
>>> What should be the Maven groupId for this repo? How about
>>> "org.wso2.ppaas.cartridges" or "org.wso2.cartridges" ?
>>>
>> We can use org.wso2.ppaas.cartridges as groupId
>>
>> Thanks,
>> Gayan
>>
>>
>>>
>>
>>> On Wed, Sep 30, 2015 at 9:24 PM, Imesh Gunaratne 
>>> wrote:
>>>
  I would like to reduce the complexity of the folder structure and
 make it much simple. Shall we have some thing like below:

 private-paas-cartridges/
 |--/common/
|--/configurator/
|--/puppet/
   |--/wso2-installer/
|--/scripts/
   |---/ec2/init.sh
   |---/openstack/init.sh

 |--/wso2esb/4.9.0/
|-/template-module/
|-/cartridge-agent-plugins/
|-/application/
|-/docker/

 Thanks

 On Wed, Sep 30, 2015 at 9:13 PM, Imesh Gunaratne 
 wrote:

> May be we can have this discussion in Dev, I cannot see any reason
> to take this private.
>
> Thanks
>
> On Wed, Sep 30, 2015 at 6:26 PM, Gayan Gunarathne  > wrote:
>
>> Adding Engineering group
>>
>>
>> -- Forwarded message --
>> From: Gayan Gunarathne 
>> Date: Wed, Sep 30, 2015 at 6:26 PM
>> Subject: [PPaaS] private-paas-cartridges repository structure
>> To: Imesh Gunaratne , Reka Thirunavukkarasu <
>> r...@wso2.com>, Udara Liyanage , Lahiru
>> Sandaruwan , Rajkumar Rajaratnam <
>> rajkum...@wso2.com>, Sajith Kariyawasam , Isuru
>> Haththotuwa , Lasindu Charith ,
>> Akila Ravihansa Perera , 

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

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

> 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
>>> cartridges,shall we group them under common?
>>> Also what about the configurator?I can see two options
>>> One option will be move the configurator to the private-paas repository
>>> and release it with the private paas.Other option will be we can do the
>>> separate release for the configurator.Seems it is better to have a separate
>>> release for the configurator. WDYT?
>>>
>>> Thanks,
>>> Gayan
>>>
>>> On Wed, Sep 30, 2015 at 10:44 PM, Gayan Gunarathne 
>>> wrote:
>>>
 Hi,

 On Wed, Sep 30, 2015 at 9:48 PM, Akila Ravihansa Perera <
 raviha...@wso2.com> wrote:

> +1 for having a simple folder structure. I think we can move the
> contents in /common/ folder to root folder. One can easily identify the
> important files available and easy to navigate as well.
>
> What should be the Maven groupId for this repo? How about
> "org.wso2.ppaas.cartridges" or "org.wso2.cartridges" ?
>
 We can use org.wso2.ppaas.cartridges as groupId

 Thanks,
 Gayan


>

> On Wed, Sep 30, 2015 at 9:24 PM, Imesh Gunaratne 
> wrote:
>
>>  I would like to reduce the complexity of the folder structure and
>> make it much simple. Shall we have some thing like below:
>>
>> private-paas-cartridges/
>> |--/common/
>>|--/configurator/
>>|--/puppet/
>>   |--/wso2-installer/
>>|--/scripts/
>>   |---/ec2/init.sh
>>   |---/openstack/init.sh
>>
>> |--/wso2esb/4.9.0/
>>|-/template-module/
>>|-/cartridge-agent-plugins/
>>|-/application/
>>|-/docker/
>>
>> Thanks
>>
>> On Wed, Sep 30, 2015 at 9:13 PM, Imesh Gunaratne 
>> wrote:
>>
>>> May be we can have this discussion in Dev, I cannot see any reason
>>> to take this private.
>>>
>>> Thanks
>>>
>>> On Wed, Sep 30, 2015 at 6:26 PM, Gayan Gunarathne 
>>> wrote:
>>>
 Adding Engineering group


 -- Forwarded message --
 From: Gayan Gunarathne 
 Date: Wed, Sep 30, 2015 at 6:26 PM
 Subject: [PPaaS] private-paas-cartridges repository structure
 To: Imesh Gunaratne , Reka Thirunavukkarasu <
 r...@wso2.com>, Udara Liyanage , Lahiru Sandaruwan
 , Rajkumar Rajaratnam ,
 Sajith Kariyawasam , Isuru Haththotuwa <
 isu...@wso2.com>, Lasindu Charith , Akila
 Ravihansa Perera , Chamila De Alwis <
 chami...@wso2.com>, Vishanth Balasubramaniam ,
 Dinithi De Silva , Anuruddha Liyanarachchi <
 anurudd...@wso2.com>, Pubudu Gunatilaka ,
 Thanuja Uruththirakodeeswaran 


 Hi All,

 Shall we have the following structure with
 the private-paas-cartridges[1] repository

 1. Maintain the separate directory for each cartridge

 Suggested directory structure as following

 .

 ├── base-image

 │   └── docker

 │   └── scripts

 │   └── start-agent.sh

 ├── vm

 │   ├── init-scripts

 │   │

 │   ├── puppet

 │   │

 │   └── README.md

 ├── wso2_product

   ├──  Version

 │   ├── docker

 │   │

 │   ├── plugins

 │   │

 │   ├── templates-modules

 │   │

 │   ├── Samples

 │   └── README.md



 Also we can move the samples to the related product folder. Then as
 a best practice we 

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

[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 cartridges,shall
>> we group them under common?
>> Also what about the configurator?I can see two options
>> One option will be move the configurator to the private-paas repository
>> and release it with the private paas.Other option will be we can do the
>> separate release for the configurator.Seems it is better to have a separate
>> release for the configurator. WDYT?
>>
>> Thanks,
>> Gayan
>>
>> On Wed, Sep 30, 2015 at 10:44 PM, Gayan Gunarathne 
>> wrote:
>>
>>> Hi,
>>>
>>> On Wed, Sep 30, 2015 at 9:48 PM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 +1 for having a simple folder structure. I think we can move the
 contents in /common/ folder to root folder. One can easily identify the
 important files available and easy to navigate as well.

 What should be the Maven groupId for this repo? How about
 "org.wso2.ppaas.cartridges" or "org.wso2.cartridges" ?

>>> We can use org.wso2.ppaas.cartridges as groupId
>>>
>>> Thanks,
>>> Gayan
>>>
>>>

>>>
 On Wed, Sep 30, 2015 at 9:24 PM, Imesh Gunaratne 
 wrote:

>  I would like to reduce the complexity of the folder structure and
> make it much simple. Shall we have some thing like below:
>
> private-paas-cartridges/
> |--/common/
>|--/configurator/
>|--/puppet/
>   |--/wso2-installer/
>|--/scripts/
>   |---/ec2/init.sh
>   |---/openstack/init.sh
>
> |--/wso2esb/4.9.0/
>|-/template-module/
>|-/cartridge-agent-plugins/
>|-/application/
>|-/docker/
>
> Thanks
>
> On Wed, Sep 30, 2015 at 9:13 PM, Imesh Gunaratne 
> wrote:
>
>> May be we can have this discussion in Dev, I cannot see any reason to
>> take this private.
>>
>> Thanks
>>
>> On Wed, Sep 30, 2015 at 6:26 PM, Gayan Gunarathne 
>> wrote:
>>
>>> Adding Engineering group
>>>
>>>
>>> -- Forwarded message --
>>> From: Gayan Gunarathne 
>>> Date: Wed, Sep 30, 2015 at 6:26 PM
>>> Subject: [PPaaS] private-paas-cartridges repository structure
>>> To: Imesh Gunaratne , Reka Thirunavukkarasu <
>>> r...@wso2.com>, Udara Liyanage , Lahiru Sandaruwan <
>>> lahi...@wso2.com>, Rajkumar Rajaratnam , Sajith
>>> Kariyawasam , Isuru Haththotuwa ,
>>> Lasindu Charith , Akila Ravihansa Perera <
>>> raviha...@wso2.com>, Chamila De Alwis , Vishanth
>>> Balasubramaniam , Dinithi De Silva <
>>> dinit...@wso2.com>, Anuruddha Liyanarachchi ,
>>> Pubudu Gunatilaka , Thanuja Uruththirakodeeswaran
>>> 
>>>
>>>
>>> Hi All,
>>>
>>> Shall we have the following structure with
>>> the private-paas-cartridges[1] repository
>>>
>>> 1. Maintain the separate directory for each cartridge
>>>
>>> Suggested directory structure as following
>>>
>>> .
>>>
>>> ├── base-image
>>>
>>> │   └── docker
>>>
>>> │   └── scripts
>>>
>>> │   └── start-agent.sh
>>>
>>> ├── vm
>>>
>>> │   ├── init-scripts
>>>
>>> │   │
>>>
>>> │   ├── puppet
>>>
>>> │   │
>>>
>>> │   └── README.md
>>>
>>> ├── wso2_product
>>>
>>>   ├──  Version
>>>
>>> │   ├── docker
>>>
>>> │   │
>>>
>>> │   ├── plugins
>>>
>>> │   │
>>>
>>> │   ├── templates-modules
>>>
>>> │   │
>>>
>>> │   ├── Samples
>>>
>>> │   └── README.md
>>>
>>>
>>>
>>> Also we can move the samples to the related product folder. Then as
>>> a best practice we need to have a separate sample for each cartridge.
>>>
>>> Advantage of this structure is we will be able to release the
>>> cartridges separately. We don't need to wait for a PPaaS cartridges
>>> repository release for release the cartridge.
>>>
>>> 2. Move the configurator to the private-paas repo or other repo as
>>> the responsibility of the configurator is to generate the products
>>> configurations based on the