← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] Updated: (CAMP-27) Should CAMP surface the names of the application states?

From
OASIS Issues Tracker <>
Date
2013-11-11T17:56:24+00:00
ID
975972127.2771384192669837.JavaMail.tomcat@customer-jira
Thread
[OASIS Issue Tracker] Updated: (CAMP-27) Should CAMP surface the names of the application states?
[ http://tools.oasis-open.org/issues/browse/CAMP-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Chapman  updated CAMP-27:
--------------------------------

    Proposal: close no action as we have no standard operation names. re-visit after some interop experience  (was: Define a normative set of application states and their names.)

> Should CAMP surface the names of the application states?
> --------------------------------------------------------
>
>                 Key: CAMP-27
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-27
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Martin Chapman 
>            Assignee: Gilbert Pilz
>            Priority: Minor
>
> The application lifecycle model uses names like deployed, stopped, etc should these be normative?
> This was discussed at the Nov 12 F2F where we agreed on the new issue and to open it.

-- 
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
← Prev in month ← Prev in thread
Next in thread → Next in month →