OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (CAMP-184) Entity Immutability

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

David Laurance commented on CAMP-184:

1. A Plan must be identifiable by a URI.  (As all Camp Resources must.)
2. A Plan must remain immutable upon Assembly instantiation.
3. Plans must be writable in the repository even during Assembly instantiation.
4. An Assembly must be able to interrogate its Plan to determine whether that Plan has been superseded.

Requirements 1-3 might be met with a versioning scheme (as in Git or Subversion) or with a provenance / lineage solution.  
Requirement 4 does not follow from 1-3. 

> Entity Immutability
> -------------------
>                 Key: CAMP-184
>                 URL: https://issues.oasis-open.org/browse/CAMP-184
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>    Affects Versions: 1.2
>            Reporter: Michael Norman
>            Assignee: Gilbert Pilz
>            Priority: Minor
> For audit purposes we would like to ensure the Plan from which an Assembly is initiated is immutable.  In general it may be best to ensure that all entities within the domain model are "copy-on-write", and we can have a generic way of accessing versions of entities through the API.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]