You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Svetoslav Neykov (JIRA)" <ji...@apache.org> on 2017/06/19 09:24:01 UTC

[jira] [Commented] (BROOKLYN-367) Upload catalogue boms and their dependencies to the server

    [ https://issues.apache.org/jira/browse/BROOKLYN-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053693#comment-16053693 ] 

Svetoslav Neykov commented on BROOKLYN-367:
-------------------------------------------

Persisting of bundles implemented in https://github.com/apache/brooklyn-server/pull/645. But it's not the exact same feature as this one. Linked bundles in libraries are still fetched from the URL and not persisted.

> Upload catalogue boms and their dependencies to the server
> ----------------------------------------------------------
>
>                 Key: BROOKLYN-367
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-367
>             Project: Brooklyn
>          Issue Type: Sub-task
>            Reporter: Sam Corbett
>
> A catalogue's dependencies (OSGi bundles) must be hosted somewhere accessible to Brooklyn. They must be available for the entire time that the catalogue item exists. Brooklyn installs the items into the framework in {{org.apache.brooklyn.util.core.osgi.Osgis#install}}.
> Brooklyn should allow these dependencies to be uploaded. We could use TOSCA's Cloud Service Archive format [1] as an inspiration for how this would be structured.
> We would need to consider where the files are stored and if/how they are distributed across HA clusters.
> References:
> 1. http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/csprd01/TOSCA-Simple-Profile-YAML-v1.0-csprd01.html#_Toc430015789



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)