Re: [Dev] [Dockerfiles] Managing Data Sources & JDBC Driver in Distributed Deployments

On Sat, Apr 23, 2016 at 8:43 PM, Imesh Gunaratne wrote: > > > +1 Yes but I think we need to make API-M yaml files consistent with other > products. I will update those and commit soon. > I have now updated API-M hiera files to be consistent with the other products [3]. However

Re: [Dev] [Dockerfiles] Managing Data Sources & JDBC Driver in Distributed Deployments

On Sat, Apr 23, 2016 at 7:14 PM, Isuru Haththotuwa wrote: > Hi Imesh, > > On Sat, Apr 23, 2016 at 8:25 AM, Imesh Gunaratne wrote: > >> Hi Devs, >> >> How do we manage $subject in Puppet provisioning for Kubernetes? >> > >> I can see that in API-M we have defined

Re: [Dev] [Dockerfiles] Managing Data Sources & JDBC Driver in Distributed Deployments

Hi Imesh, On Sat, Apr 23, 2016 at 8:25 AM, Imesh Gunaratne wrote: > Hi Devs, > > How do we manage $subject in Puppet provisioning for Kubernetes? > > I can see that in API-M we have defined MySQL connector JAR [1] and data > sources but not in others. We have also hard coded

Re: [Dev] [Dockerfiles] Managing Data Sources & JDBC Driver in Distributed Deployments

I think we need to consider other Databases (Oracle,PostgreSQL etc) also. Default[1] set up also we have hard corded to the h2 database. Better if we support the other set of databases here also.Based on the database we used we can set the appropriate DB driver with hiera. [1]

[Dev] [Dockerfiles] Managing Data Sources & JDBC Driver in Distributed Deployments

Hi Devs, How do we manage $subject in Puppet provisioning for Kubernetes? I can see that in API-M we have defined MySQL connector JAR [1] and data sources but not in others. We have also hard coded MySQL host IP [2] in API-M profile yaml files. [1]