brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <j...@apache.org>
Subject [jira] [Created] (BROOKLYN-13) OSGi for blueprint versioning, and catalog updates/revamp
Date Mon, 30 Jun 2014 14:15:25 GMT
Aled Sage created BROOKLYN-13:
---------------------------------

             Summary: OSGi for blueprint versioning, and catalog updates/revamp
                 Key: BROOKLYN-13
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-13
             Project: Brooklyn
          Issue Type: New Feature
            Reporter: Aled Sage
             Fix For: 0.7.0


Several users have requested features around maintaining versions of blueprints and composing
YAML blueprints.  Although these seem distinct, we propose that the best way to implement
these is through an overhaul of the existing catalog mechanism.  At a high level we propose
the following set of user stories:

1) Register new blueprints to the catalog with code isolation, including at runtime
2) Allow references to these registered blueprints respecting their classpaths
3) Allow catalog changes to be persisted and shared among HA servers
4) Support versioning of items in the catalog
5) Allow managing the catalog via the GUI

This proposal outlines how these features could be supported.

See the full proposal at: https://docs.google.com/document/d/1wWySDhfn5LBHfsNfj0cW0e2lSo-6T9_Ox3mHbKX1Hm8

See the original e-mail thread at http://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201406.mbox/%3C53A01604.5050607%40cloudsoftcorp.com%3E



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message