[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (CAMP-183) Decouple the Plan Repository from the Platform
[ https://issues.oasis-open.org/browse/CAMP-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60850#comment-60850 ] Anish Karmarkar edited comment on CAMP-183 at 9/29/15 4:39 AM: --------------------------------------------------------------- Decided to on the 2015-09-09 telcon to let David/Mike think about this more. This issue won't be discussed till David/Mike come back with addition information/proposal. There is still an outstanding issue of what to call "Thing1" (Yaml file). The two options are: plan manifest OR app manifest was (Author: akarmark): Decided to let David/Mike think about this more. This issue won't be discussed till David/Mike come back with addition information/proposal. > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]