On Thu, Sep 18, 2014 at 5:21 PM, Isuru Haththotuwa <isu...@apache.org> wrote:
> Hi Akila, > > I'm not aware if there is a generic carbon component for this. But, I > totally agree with the second point; we can implement a generic rest > client. Currently we have one in the CLI, and now we are going to have the > same for Kubernetes and Meta Data service clients. We can put all the > required functionality in a single component and re-use. > +1 for a generic rest client. I also need to have a rest client for invoking Jenkins docker image build operations. > > > On Thu, Sep 18, 2014 at 4:55 PM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Hi Isuru, >> >> Thanks for the explanation. >> >> Don't we have a Carbon platform component to achieve this? Just making >> sure we are not replicating the functionality. >> > >> Can we create a generic REST client that can be used for communicating >> with other REST services too? For eg - we need to have a REST client >> to communicate with the Kubernetes API for Docker integration. >> > > >> >> Any thoughts? >> >> On Thu, Sep 18, 2014 at 4:10 PM, Isuru Haththotuwa <isu...@apache.org> >> wrote: >> > Hi Akila, >> > >> > On Thu, Sep 18, 2014 at 2:09 PM, Akila Ravihansa Perera < >> raviha...@wso2.com> >> > wrote: >> >> >> >> +1 >> >> >> >> Meta-data service is going to be vital when implementing clustering >> >> support for application services as well. I think it's better to have >> >> it as a separate component. >> >> >> >> Could you please explain what components will have dependencies to the >> >> meta-data service client? This is going to be a REST client right? >> > >> > Yes, what I thought is to make it a rest client. At the moment, it does >> not >> > have any dependencies on other components. >> >> >> >> >> >> Also we might want to think about security permissions for meta-data >> >> service too. We can integrate this with the new user management model >> >> that is being developed. >> > >> > Yes. For the initial version, I will not be focusing on the >> > authentication/authorization aspects much. +1 for using the new >> permission >> > model if its viable. >> >> >> >> >> >> Thanks. >> >> >> >> On Wed, Sep 17, 2014 at 3:12 PM, Isuru Haththotuwa <isu...@apache.org> >> >> wrote: >> >> > Hi Devs, >> >> > >> >> > In Service Grouping, we would heavily need to use the meta data >> service >> >> > to >> >> > put and get data. Therefore, shall we implement a $subject? Then it >> can >> >> > be >> >> > re-used wherever required across Stratos. WDYT? >> >> > >> >> > >> >> > -- >> >> > Thanks and Regards, >> >> > >> >> > Isuru H. >> >> > +94 716 358 048 >> >> > >> >> > >> >> >> >> >> >> >> >> -- >> >> Akila Ravihansa Perera >> >> Software Engineer, WSO2 >> >> >> >> Blog: http://ravihansa3000.blogspot.com >> >> >> >> -- >> >> Thanks and Regards, >> >> >> >> Isuru H. >> >> +94 716 358 048 >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> -- >> Akila Ravihansa Perera >> Software Engineer, WSO2 >> >> Blog: http://ravihansa3000.blogspot.com >> >> -- >> <http://ravihansa3000.blogspot.com> >> Thanks and Regards, >> >> Isuru H. >> <http://ravihansa3000.blogspot.com> >> +94 716 358 048 <http://ravihansa3000.blogspot.com>* <http://wso2.com/>* >> >> >> * <http://wso2.com/>* >> >> >> -- *Sajith Kariyawasam* *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com <http://wso2.com>AMIE (SL)Mobile: +94772269575*
