Thanks Lakmal, yes I think we can reuse cluster min/max for Kubernetes replica min/max.
On Fri, Dec 19, 2014 at 12:50 AM, Lakmal Warusawithana <[email protected]> wrote: > > > > On Fri, Dec 19, 2014 at 12:21 AM, Imesh Gunaratne <[email protected]> > wrote: >> >> Hi Devs, >> >> Currently we define Docker/Kubernetes configuration in the cartridge >> definition using a property called deployerType. >> >> This properly can only have the value "kubernetes". I think it would be >> better if we could reuse the IaasProvider section for this. WDYT? >> >> A sample cartridge definition: >> { >> "*type*":"tomcat", >> "*category*":"framework", >> ... >> "*iaasProvider*":[ >> { >> "*type*":"kubernetes", >> "*imageId*":"apache-tomcat/v7", >> "*maxInstanceLimit*":"2", >> "*property*":[ >> { >> "*name*":"KUBERNETES_CLUSTER_ID", >> "*value*":"kubernetes-cluster-1" >> }, >> { >> "*name*":"KUBERNETES_REPLICAS_MIN", >> "*value*":"3" >> }, >> { >> "*name*":"KUBERNETES_REPLICAS_MAX", >> "*value*":"20" >> > > Min and max does not comes with cartridge definitions. It should come with > application definition. > > > >> } >> ] >> } >> ] >> } >> >> Thanks >> >> >> -- >> Imesh Gunaratne >> >> Technical Lead, WSO2 >> Committer & PMC Member, Apache Stratos >> > > > -- > Lakmal Warusawithana > Vice President, Apache Stratos > Director - Cloud Architecture; WSO2 Inc. > Mobile : +94714289692 > Blog : http://lakmalsview.blogspot.com/ > > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
