[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=59312#comment-59312 ] 

Mike Norman commented on CAMP-183:
----------------------------------

I think you are right that there's nothing to stop you sharing a plans resource in another platform, or (I think) sharing the individual plan_links.

Our notion of a Plan Repository is that isn't a Platform, and doesn't do all the other things a Platform does.  Which intuitively seems right.  We envisage a small number of Plan Repositories (probably one) and multiple Platforms. A given plan belongs to a Plan Repository which acts as its reference source and we are looking to run the same Plan on multiple Platforms, so that we have traceability to the same artifact set and plan.  So we could restrict the API on a Platform to use it as a central Plan Repository, but that seems intuitively wrong.  It seems like a different thing. 

Also, your proposal introduces a many-to-many relation (a Plan belongs to multiple Platforms  a Platform has many Plans) and mine explictly forces a one-to-many relation between a Plan Repository and a Plan (a Plan belongs to one Platform Repository and  a Platform Repository has many Plans). In general I am struggling in the GUI with many-to-many relations in the model because the URIs are context free and if the GUI gets one without additional context you need to establish parentage somehow.  It may be I can get around this, but if not, once I've got my head around it I will raise another Jira.  

> 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
>            Reporter: Mike Norman
>
> 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)