Gayan, Do we have a sample for this metadataservice.xml? Is it mandatory to have it when we are using the meta data service?
On Tue, Aug 12, 2014 at 4:47 PM, Gayan Gunarathne <[email protected]> wrote: > Hi Sajith, > > Please find the inline comments. > > Thanks, > Gayan > > > On Tue, Aug 12, 2014 at 3:58 PM, Sajith Kariyawasam <[email protected]> > wrote: > >> Hi Gayan, >> >> I have few things to get clarified in the initial design. >> >> Are you maintaining the data structure template per tenant? How do you >> maintain the password in the cartridge instance? >> > > > We maintain the data structure template per application. > Following is the sample data structure template in the G-Reg and we > maintain the instance password as a property. > (It also describe under* "*Data Structure Template" in section 3 of the > initial design) > > Application 1 > > - cartridge 1 > > -property 1(key/value) > > -property 2 > > - cartridge 2 > > -property 1 > > -property 2 > > Application 2 > > - cartridge 1 > > -property 1 > > -property 2 > > - cartridge 2 > > -property 1 > -property 2 > > >> Does the communication between metadata-service and Greg happen in tenant >> mode or super-tenant mode? >> > > This will be currently in configuration level(metadataservice.xml). We can > set the communication user in the configuration file. > >> >> >> Thanks, >> Saijth >> >> >> On Tue, Aug 12, 2014 at 3:15 PM, Gayan Gunarathne <[email protected]> >> wrote: >> >>> Further clarification of point 1 , >>> In current meta data service once you call the retrieve meta data >>> service with cartridge specified, it will return whole set of meta data >>> related to that cartridge. So in the client side you need to filter the >>> information you needed from that response JSON object. >>> >>> Thanks, >>> Gayan >>> >>> >>> On Tue, Aug 12, 2014 at 3:00 PM, Gayan Gunarathne <[email protected]> >>> wrote: >>> >>>> Hi Isuru, >>>> >>>> Please find my inline comments in blue. >>>> >>>> 1. In addition to getting all the meta data at one time, is it possible >>>> to specifically get the value for one meta data property? >>>> >>>> Currently it is not support for get a value of one meta data. Currently >>>> it will return all the meta data related to the cartridge.Thanks for point >>>> out this. I think if we can provide the another REST service for getting >>>> the value of one meta data at a time will be a good addition for the >>>> current meta data service. >>>> >>>> 2. Are the current rest operations (store and retrieve metadata) >>>> restricted to super tenant? >>>> No. It won't restrict to the super tenant admin only. >>>> >>>> >>>> Thanks, >>>> Gayan >>>> >>>> >>>> On Tue, Aug 12, 2014 at 2:29 PM, Isuru Haththotuwa <[email protected]> >>>> wrote: >>>> >>>>> Hi Gayan, >>>>> >>>>> Great work with the initial version of the meta data service! >>>>> >>>>> I have a couple of questions regarding the current implementation. >>>>> >>>>> 1. In addition to getting all the meta data at one time, is it >>>>> possible to specifically get the value for one meta data property? >>>>> 2. Are the current rest operations (store and retrieve metadata) >>>>> restricted to super tenant? >>>>> >>>>> >>>>> On Wed, Jul 30, 2014 at 6:32 PM, Gayan Gunarathne <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Imesh, >>>>>> >>>>>> Thanks for pointed out this.I will update the URLs in the document. >>>>>> >>>>>> Thanks, >>>>>> Gayan >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Jul 30, 2014 at 6:25 PM, Imesh Gunaratne <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hi Gayan, >>>>>>> >>>>>>> The initial design of the metadata service looks good. I have few >>>>>>> comments: >>>>>>> >>>>>>> - I could see the following URLs designed for posting and retrieving >>>>>>> meta-data information: >>>>>>> POST: admin/cartridge/metadatasubcription >>>>>>> GET: >>>>>>> admin/cartridge/metadataretrieve/<application-name>/<cartridge-type> >>>>>>> >>>>>>> IMO this design does not adhere to RESTful resource naming standards >>>>>>> [1]. Ideally both POST and GET should have the same URL. Shall we >>>>>>> redesign >>>>>>> them to something like following: >>>>>>> POST: admin/cartridge/<cartridge-type>/<application-name>/metadata/ >>>>>>> GET: admin/cartridge/<cartridge-type>/<application-name>/metadata/ >>>>>>> >>>>>>> [1] >>>>>>> http://www.restapitutorial.com/lessons/restfulresourcenaming.html >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Jul 30, 2014 at 5:16 AM, Gayan Gunarathne <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> To publish the meta data with this REST API, I am thinking of >>>>>>>> adding the meta data service publish REST API request from the >>>>>>>> "instance-started" extension of the cartridge agent.I guess we can get >>>>>>>> the >>>>>>>> relevant meta data from the Factors.Meta data will be different from >>>>>>>> cartridge to cartridge.IMO we can use the addone(erb files) for the >>>>>>>> different cartridges to support this. >>>>>>>> >>>>>>>> Any thoughts or suggestions about this? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Gayan >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ---------- Forwarded message ---------- >>>>>>>> From: Gayan Gunarathne <[email protected]> >>>>>>>> Date: Thu, Jul 24, 2014 at 4:27 PM >>>>>>>> Subject: Stratos meta data service - Initial Design >>>>>>>> To: [email protected], Lakmal Warusawithana <[email protected]> >>>>>>>> >>>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> Based on the discussions[1][2], I have drafted the initial design >>>>>>>> for the Stratos meta data service. >>>>>>>> >>>>>>>> MetaDataService-Design >>>>>>>> <https://docs.google.com/a/wso2.com/document/d/1RkmBv290mleaUIsYYebMKZ8TTTyMrqWfqOY_nXgGLdw/edit?usp=drive_web> >>>>>>>> >>>>>>>> >>>>>>>> Your inputs and suggestions regarding this is highly appreciated. >>>>>>>> >>>>>>>> >>>>>>>> [1]. [Discuss] Grouping of services (cartridges) >>>>>>>> [2]. [Discuss] Grouping of services with dependency cartridges >>>>>>>> >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Gayan >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> >>>>>>>> Gayan Gunarathne >>>>>>>> Technical Lead >>>>>>>> WSO2 Inc. (http://wso2.com) >>>>>>>> email : [email protected] | mobile : +94 766819985 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Best Regards, >>>>>>>> >>>>>>>> Gayan Gunarathne >>>>>>>> Technical Lead >>>>>>>> WSO2 Inc. (http://wso2.com) >>>>>>>> email : [email protected] | mobile : +94 766819985 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Imesh Gunaratne >>>>>>> >>>>>>> Technical Lead, WSO2 >>>>>>> Committer & PPMC Member, Apache Stratos >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best Regards, >>>>>> >>>>>> Gayan Gunarathne >>>>>> Technical Lead >>>>>> WSO2 Inc. (http://wso2.com) >>>>>> email : [email protected] | mobile : +94 766819985 >>>>>> >>>>>> -- >>>>>> <%2B94%20766819985> >>>>>> Thanks and Regards, >>>>>> >>>>>> Isuru H. >>>>>> <%2B94%20766819985> >>>>>> +94 716 358 048 <%2B94%20766819985>* <http://wso2.com/>* >>>>>> >>>>>> >>>>>> * <http://wso2.com/>* >>>>>> >>>>>> >>>>>> >>>> >>>> >>>> -- >>>> Best Regards, >>>> >>>> Gayan Gunarathne >>>> Technical Lead >>>> WSO2 Inc. (http://wso2.com) >>>> email : [email protected] | mobile : +94 766819985 >>>> >>>> >>> >>> >>> >>> -- >>> Best Regards, >>> >>> Gayan Gunarathne >>> Technical Lead >>> WSO2 Inc. (http://wso2.com) >>> email : [email protected] | mobile : +94 766819985 >>> >>> >> >> >> >> -- >> *--* >> *Sajith Kariyawasam* >> *Mobile: +94772269575 <%2B94772269575>* >> > > > > -- > Best Regards, > > Gayan Gunarathne > Technical Lead > WSO2 Inc. (http://wso2.com) > email : [email protected] | mobile : +94 766819985 > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* <http://wso2.com/>* > > > * <http://wso2.com/>* > > >
