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] Created: (CAMP-67) resource model lacks explicit information about the state of dependencies

resource model lacks explicit information about the state of dependencies

                 Key: CAMP-67
                 URL: http://tools.oasis-open.org/issues/browse/CAMP-67
             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
          Issue Type: Bug
          Components: Spec
            Reporter: Gilbert Pilz
            Assignee: Gilbert Pilz

Section 2.1.2 of WD10 contains the following language:

"An Application Component Template cannot be instantiated unless all of its dependencies are satisfied. An Application Component Template shall be referenced by a single Assembly Template. An Assembly Template shall not be instantiated until all of its Application Component Templates are successfully instantiated."

However, nowhere in the spec does it say how either the platform or the client are supposed to determine whether or not an ApplicationComponentTemplate (ACT) has had all its dependencies satisfied. Leaving other application components out of the picture for now, an ACT can have links to both PlatformComponentRequirements (PCRs) and PlatformComponentTemplates (PCTs). The semantics of the PCR links are "I have these requirements". The semantics of the PCT links are "I use the service described by this PCT".

1.) Can we mandate that every PCR is satisfied by a single PCT link or is it possible for a single PCR to require two or more PCT links?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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