[OASIS Issue Tracker] (CAMP-183) Decouple the Plan Repository from the Platform

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/CAMP-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65590#comment-65590 ] 

Michael Norman commented on CAMP-183:
-------------------------------------

It appears that the resolution here is related to the problem of coalescing the platform with the assembly (reflecting, for example,  the fact that you can run Marathon on Marathon in DCOS). In which case there can be other subclasses of assembly (e.g. repositories) that carry plans, but do not necessarily act as platforms.

> Decouple the Plan Repository from the Platform
> ----------------------------------------------
>
>                 Key: CAMP-183
>                 URL: https://issues.oasis-open.org/browse/CAMP-183
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>    Affects Versions: 1.2
>            Reporter: Michael Norman
>            Assignee: Michael Norman
>            Priority: Trivial
>
> At the moment a Platform has many Plans, and a Plan belongs to a Platform.  We would like to decouple the notion of a Plan Repository from a Platform. So a top-level entity (which we refer to as an Enterprise) would have zero or many Platforms, and also have zero or many Plan Repositories.  A Plan Repository would have zero or many Plans (and so on through the child entities of a Plan).  An Assembly would instantiate a Plan (loosely, a Plan would have zero or more Assemblies in zero or more Platforms).  Then everything is back to the existing domain model.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)