Re: Grouping of services with dependency cartridges

Hi, On Tue, Jul 22, 2014 at 2:12 PM, Gayan Gunarathne wrote: > how do we store meta data - > IMO if we go with the registry (G-Reg) rather than a DB or other > implementation we can acquire following benefits. > 1. Activity log and monitoring support > 2. Development effect and maintaina

RE: Grouping of services with dependency cartridges

potentially very powerful thing, and would be a superset of what is being discussed here. OTOH, it could be complete overkill… ☺ From: Gayan Gunarathne [mailto:gay...@wso2.com] Sent: 22 July 2014 09:42 To: dev@stratos.apache.org Subject: Re: Grouping of services with dependency cartridges how do we

Re: Grouping of services with dependency cartridges

how do we store meta data - IMO if we go with the registry (G-Reg) rather than a DB or other implementation we can acquire following benefits. 1. Activity log and monitoring support 2. Development effect and maintainable effect will be less 3. We can use in-build notifications functiona

Re: Grouping of services with dependency cartridges

Hi, - metadata should be independent from topology. Otherwise one has to tamper topology to introduce application specific metadata. (if we go in that path, we dont need metadata service at all i guess) - so udaras' idea might not work. - we need a rest api - > means packaging type would be a weba

Re: Grouping of services with dependency cartridges

Hi Imesh, Thanks for the clarification. With this approach how we add the Cartridge meta data to the registry/web -app? AFAIK the all the meta data related to the cartridges are not available in the topology.As a example credential details of the MySQL cartridge not available in the topology. +1

Re: Grouping of services with dependency cartridges

Hi Gayan, Few weeks back I had a discussion on this with Lakmal and the idea was to use a metadata service web-app. Shall we discuss pros and cons on using the Registry vs a Web-app. Regarding Pradeep's question, IMO the metadata-service (either the registry/web-app) can listen to the topology an

Re: Grouping of services with dependency cartridges

Hi, Could n't this be achieved by using the existing topology? Add some REST APIs to SM which get necessary details from CC. Agent can get the IP by calling the API. However mysql credentials are not in topology. Touched, not typed. Erroneous words are a feature, not a typo.

Re: Grouping of services with dependency cartridges

Yes. IMO We can remove the metadata related to terminated instance from the CC and we can add meta data related to the new instance from the cartridge agent after new instance spawned. Thanks, Gayan On Mon, Jul 21, 2014 at 4:53 PM, Pradeep Fernando wrote: > how the termination info (removing t

Re: Grouping of services with dependency cartridges

how the termination info (removing the metadata related to terminated instance) get updated in the registry. Is it a task of CC bits ? thanks, --Pradeep On Mon, Jul 21, 2014 at 3:37 PM, Gayan Gunarathne wrote: > > Hi All, > > For the composite cartridge subscription[1], in the case of the cart

Grouping of services with dependency cartridges

Hi All, For the composite cartridge subscription[1], in the case of the cartridge instance is terminated and new instance create scenario, we need to share the new meta data with the dependencies cartridge.We will thinking of using the governance registry(G-Reg) with rest API for the meta data st