[Nsi-wg] Issue 100 in ogf-nsi-project: Need no GenericErrorType to communicate INVALID_TRANSITION errors
ogf-nsi-project at googlecode.com
ogf-nsi-project at googlecode.com
Thu Aug 1 09:59:33 EDT 2013
Status: Accepted
Owner: jmacauley
Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0
New issue 100 by jmacauley: Need no GenericErrorType to communicate
INVALID_TRANSITION errors
http://code.google.com/p/ogf-nsi-project/issues/detail?id=100
Description of Issue:
For those requests like reserveAbort, provision, release, etc. there is no
GenericFailedType reply. How can errors such as INVALID_TRANSITION be
passed to the RA?
Discussion of Issue:
The specific failed messages were removed for operations such as provision
because there was a view that it would not fail, and therefore, would not
require failed transitions in the state machine. However, there are some
errors that do not cause state machine transitions. At the moment there is
no mechanism that would permit their return to the requesting agent after a
message has been accepted for processing (a service exception can be
returned instead of an ACK, but this is only during the message acceptance
phase).
Resolution of Issue:
Add a generic error message that can be returned to indicate a non-state
machine affecting error.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
More information about the nsi-wg
mailing list