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
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
