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] Commented: (CAMP-38) resourceState attribute needs clarification


    [ http://tools.oasis-open.org/issues/browse/CAMP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32073#action_32073 ] 

Michael Behrens commented on CAMP-38:
-------------------------------------

I'm raising the question about the stages toward being ready or delete, etc.  Is there a need to track transitional states?  It might take a while for "ready" to indicate that it is fully configured.  Perhaps just getting the status could also provide an optional message, i.e. Configuring.

> resourceState attribute needs clarification
> -------------------------------------------
>
>                 Key: CAMP-38
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-38
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>            Reporter: Gilbert Pilz
>            Assignee: Gilbert Pilz
>
> The CAMP spec currently defines a "ResourceState" type and defines a "resourceState" attribute of this type for some, but not all, resources. There are several problems with this:
> 1.) There is some confusion between the information communicated by this attribute and the state of the application within the application lifecycle. We need to make it clear that "resourceState" is about that particular resource and not the (more abstract) application which is represented by the resource.
> 2.) The values and semantics of the "ResourceState" type are only listed as exampled (through use of "e.g."). We need to define a enumeration of specific values with specific semantics.
> 3.) The "resourceState" attribute is only defined for some resources and not others. We either need to define "resourceState" as a common attribute, or explain the criteria for its application to a particular resource type.

-- 
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]