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-173) "service resource" is not required to advertise its characteristics

     [ https://issues.oasis-open.org/browse/CAMP-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gilbert Pilz updated CAMP-173:

Initial proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/53653/camp-spec-v1.1-wd45-173.doc

This proposal is known to have a few things wrong with the pseudo-schema and is missing some updates to the UML diagram.

High-level proposal: add an optional attribute to the "service resource" called "characteristics" which is the JSON equivalent of the YAML "characteristics" array in a ServiceSpecification.

      "characteristics": [
          "characteristic_type": String
          "characteristic": String +

The text for this attribute should make it clear that the CAMP spec is deliberately silent on the matching between information in a Plan and the information in this attribute.

Added link to first, rough-cut, proposal.

> "service resource" is not required to advertise its characteristics
> -------------------------------------------------------------------
>                 Key: CAMP-173
>                 URL: https://issues.oasis-open.org/browse/CAMP-173
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>            Reporter: Gilbert Pilz
>            Assignee: Gilbert Pilz
> The CAMP spec says that a Plan can contain a ServiceSpec that "describes a service used by the application". A ServiceSpec can contain an array of CharacteristicSpecifcations which "describe a desired characteristic or capability". Example 3 shows:
> 10           characteristics:
> 11             -
> 12               characteristic_type: com.example:Linux
> 13               com.example.linux.kernelVersion: [3.9.6]
> 14               org.iaas.bitsize: 64
> This seems clear enough, but what is lacking is any way to correlate this information with the information provided by the CAMP resource model.
> The purpose of ServiceSpecification's is to provide information to the platform so that it can select "service resources" that meet the consumers requirements. The CAMP TC has long been of the opinion that the process of matching the information in a Plan to specific "service resources" instances is, and should be, opaque to the consumer; the CAMP spec shouldn't say anything about this process. However, there is a difference between "opaque" and "a complete and utter mystery".
> At a minimum the CAMP spec should define some optional way whereby a Provider can adorn a "service resource" (or a resource that inherits from the "service resource") with enough information to give Consumers some notion of whether or not the service represented by that resource will be able to meet their requirements. Ideally this information should be analogous to the information in the CharacteristicSpecification array.

This message was sent by Atlassian JIRA

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