On Sat, Sep 3, 2016 at 12:39 PM, Pubudu Gunatilaka <[email protected]> wrote:
> Hi, > > +1 for the approach and it is more simpler in this way. We need to > consider the puppet side as well as we use puppet provision for docker > images. At the moment we only support single JVM and fully distributed > pattern. IMO we need to introduce patterns for puppet as well to go forward > with this effort. Otherwise, users will have to write their own patterns by > changing hiera data. > +1 Yes Pubudu! Will introduce support for managing paterns in puppet first. Thanks > > Thank you! > > On Fri, Sep 2, 2016 at 8:33 PM, Chamila De Alwis <[email protected]> > wrote: > >> >> On Fri, Sep 2, 2016 at 9:28 AM, Imesh Gunaratne <[email protected]> wrote: >> >>> 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? >>> >> >> Yes, I didn't think of that. In that case, artifact duplication is a >> better, simpler approach. +1 >> >> >> Regards, >> Chamila de Alwis >> Committer and PMC Member - Apache Stratos >> Senior Software Engineer | WSO2 >> Blog: https://medium.com/@chamilad >> >> >> > > > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > -- *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
