Issue 113 in ogf-nsi-project: Change provisionState machine to be mandatory.
Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 113 by jmacauley: Change provisionState machine to be mandatory. http://code.google.com/p/ogf-nsi-project/issues/detail?id=113 Decision was made to instantiate the provisionState when the first reserve request is received for a reservation. This makes it consistent with the other state machines. However, it should be noted that a provision request cannot be received until the first version of the reservation has been successful committed. If a provision request is received before the first version of a reserve has been created, then it must be rejected with an 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
Updates: Status: Done Comment #1 on issue 113 by jmacauley: Change provisionState machine to be mandatory. http://code.google.com/p/ogf-nsi-project/issues/detail?id=113 Change completed with revision 117. -- 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
On Fri, 10 Jan 2014, ogf-nsi-project@googlecode.com wrote:
Comment #1 on issue 113 by jmacauley: Change provisionState machine to be mandatory. http://code.google.com/p/ogf-nsi-project/issues/detail?id=113
Change completed with revision 117.
Dafuq? r116 has already been labelled as the version for 2.0. We cannot keep changing small things here and there, or we will never get anything out the door. Further this change was not discussed at last weeks meeting (or before christmas) or on the mailing list, which given the current situation, would be an absolute minimum for doing that sort of changes. Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet
This one was on oversight on my part. It was agreed to and an issue was open but I forgot to do the change. This actually lines it up with the NSI-CS document. If we discuss if we do not want to support it in deployment. This is the change that instantiates all the SM at reservation creation. On 2014-01-13, at 4:33 AM, Henrik Thostrup Jensen <htj@nordu.net> wrote:
On Fri, 10 Jan 2014, ogf-nsi-project@googlecode.com wrote:
Comment #1 on issue 113 by jmacauley: Change provisionState machine to be mandatory. http://code.google.com/p/ogf-nsi-project/issues/detail?id=113
Change completed with revision 117.
Dafuq? r116 has already been labelled as the version for 2.0. We cannot keep changing small things here and there, or we will never get anything out the door.
Further this change was not discussed at last weeks meeting (or before christmas) or on the mailing list, which given the current situation, would be an absolute minimum for doing that sort of changes.
Best regards, Henrik
Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet
_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg
On Mon, 13 Jan 2014, John MacAuley wrote:
This one was on oversight on my part. It was agreed to and an issue was open but I forgot to do the change. This actually lines it up with the NSI-CS document. If we discuss if we do not want to support it in deployment. This is the change that instantiates all the SM at reservation creation.
We all forget things from time to time. There are probably 5 or 10 more things that we intended to get in there, but somehow slipped. But we got to learn to say stop. Otherwise we will never get this thing out the door. Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet
participants (3)
-
Henrik Thostrup Jensen -
John MacAuley -
ogf-nsi-project＠googlecode.com