On Fri, Apr 8, 2016 at 5:12 PM, Imesh Gunaratne <[email protected]> wrote:
> Hi Devs,
>
> IMO we need to handle $subject without affecting other deployments. At the
> moment we have updated default.yaml with K8S specific configurations and
> manager and worker yaml files also have clustering configurations enabled
> for K8S.
>
+1. As per the offline discussion, one possible method of doing this is to
have a separation under the product level of hieradata to indicate whether
the configuration is relevant to vm, docker, kubernetes, mesos, etc based
scenarios. So the hieradata structure should change as below:
hieradata
|--- dev
|--- wso2
|---- <product_name>
|--- <product_version>
|-- *vm*
|-- default.yaml
|-- manager.yaml
|-- worker.yaml
|--* docker*
|-- default.yaml
|-- manager.yaml
|-- worker.yaml
|-- *kubernetes*
|-- default.yaml
|-- manager.yaml
|-- worker.yaml
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.io
> Lean . Enterprise . Middleware
>
>
--
Thanks and Regards,
Isuru H.
+94 716 358 048* <http://wso2.com/>*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev