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? > > @Vishanth: A good thought! Our intention is to avoid parameterizing deploy.sh and provide one for each pattern. On Fri, Sep 2, 2016 at 6:43 PM, Chamila De Alwis <[email protected]> wrote: > 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 > > @Chamila: In each pattern, product profile might contain different configuration values. Therefore for each pattern, profile we may need to have a container image. Then profile yaml files may contain pattern, profile specific values. If so we may need to parameterize the profile yaml files with this suggestion. By considering the number of yaml files each pattern would have, I think duplicating them might not bring much overhead. Don't you agree? Thanks > >> 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>* >> > > -- *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
