brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Downer <>
Subject Re: Persisting catalogues
Date Tue, 02 Sep 2014 13:29:10 GMT
Hi Sam,

Is there any way to merge the persisted catalog with the defined
catalog? So that if the user adds new entries to the catalog through
another mechanism (catalog.xml being the obvious one) they will be
added to Brooklyn even if there is persisted state.

Perhaps only late-added catalog entries - using the mechanism you
suggest - should be persisted? Everything loaded through catalog.xml
does not get persisted?

Ideally in the future I'd like to see the catalog get populated
automatically through introspection, so that dropping e.g. the Clocker
jar into dropins would be all that's needed to get it into the
catalog. So I'm keen that your solution here wouldn't conflict with
that. OTOH, code talks, and I don't have any code yet :-)


On 1 September 2014 11:10, Sam Corbett <> wrote:
> Hi all,
> Another feature proposal and request for comments.
> Brooklyn maintains a catalogue of applications, entities and policies. This
> catalogue can be updated programatically:
>     managementContext.getCatalog().addItem(..)
> Or restfully by VERBing /v1/catalog.
> At the moment this catalogue is not persisted when you stop Brooklyn. Any
> modifications made after start-up are lost forever. I would like to change
> that.
> I think the only point of contention is what is loaded from where and when.
> I propose that when the server starts:
> * If persistence if disabled load the default catalogue;
> * If persistence is enabled but there is no persisted catalogue (i.e. the
> server is running for the first time) then load the default catalogue;
> * Otherwise load the persisted catalogue. Do _not_ load the default
> catalogue.
> Any comments?
> Thanks,
> Sam

View raw message