Hi Imesh,
Wouldn't we be duplicating (say for Kubernetes) replication controller and
service definitions across deployment patterns? If it's relatively easier
to just have a configurable description of the deployment pattern can we
follow something like the following?
*/<paas>-artifacts-<product>/*
/artifacts
/wso2<product>-<profile>-controller.yaml
/wso2<product>-<profile>-service.yaml
/<pattern-1>
/README.md - Include pattern information
/pattern.yaml - The ordered list of profiles to deploy
/deploy.sh
/<pattern-n>
/README.md - Include pattern information
/pattern.yaml - The ordered list of profiles to deploy
/deploy.sh
What we are essentially doing in the deploy.sh is to add a certain profile
to the PaaS in a certain pattern. So pattern.yaml could look like the
following.
---
deployment-order:
- profile1
- profile2
- profile3
WDYT?
Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Senior Software Engineer | WSO2
Blog: https://medium.com/@chamilad
On Fri, Sep 2, 2016 at 6:17 AM, Vishanth Balasubramaniam <[email protected]
> wrote:
> Hi,
>
> +1 to have different directories to manage deployment patterns. We can
> also have single deploy script and pass the pattern name as a parameter.
> WDYT?
>
> Regards,
> Vishanth
>
> On Fri, Sep 2, 2016 at 3:46 PM, Imesh Gunaratne <[email protected]> wrote:
>
>> Hi All,
>>
>> Currently, in K8S and Mesos Artifacts, we only have support for two
>> deployment patterns in each product. That is for single-JVM and fully
>> distributed deployments. We also have included files required for both
>> patterns inside the same directly and they are managed by the same
>> deploy.sh bash script. In this approach, it would be difficult to manage
>> multiple patterns of products as deploy.sh needs to be parameterized
>> accordingly.
>>
>> Shankar proposed to split this into separate folders and have a folder
>> per deployment pattern. I'm +1 for that approach. Please find a sample
>> folder structure designed according to this approach below:
>>
>> */<paas>-artifacts-<product>/*
>> /<pattern-1>
>> /README.md - Include pattern information
>> /<paas-artifacts> - Artifacts needed for deployment
>> automation
>> /deploy.sh
>> /<pattern-n>
>> /README.md - Include pattern information
>> /<paas-artifacts> - Artifacts needed for deployment
>> automation
>> /deploy.sh
>>
>> Please share your thoughts on this.
>>
>> Thanks
>>
>> --
>> *Imesh Gunaratne*
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: https://medium.com/@imesh TW: @imesh
>> lean. enterprise. middleware
>>
>>
>
>
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94 77 17 377 18*
> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
