Issue 54 in ogf-nsi-project: Make it possible to go from auto-provision to scheduled
Status: Accepted Owner: ---- Labels: Type-Enhancement Priority-Medium FoundInVersion-1.0 FixedInVersion-1.1 New issue 54 by thost...@gmail.com: Make it possible to go from auto-provision to scheduled http://code.google.com/p/ogf-nsi-project/issues/detail?id=54 It is not possible to go from auto-provision to scheduled in the current state machine. In case of a failed provision call, it is impossible to "release" the other connections, making it impossible to keep the state between connections consistent. As some will be in auto-provisioned and other will be in scheduled. Ignore failures, it should also be possible for a connection to go into scheduled mode from auto-provision to say that the connection shouldn't be provisioned, but the resources should still be reserved. Resolution of Issue: Allow transistion from auto-provision to scheduled and have a release request move a connection from auto-provision to scheduled.
Updates: Owner: tkudoh...@gmail.com Comment #1 on issue 54 by guy.robe...@gmail.com: Make it possible to go from auto-provision to scheduled http://code.google.com/p/ogf-nsi-project/issues/detail?id=54 Kudoh-san will propose a new state machine to solve this issue.
Updates: Labels: -FixedInVersion-1.1 FixedInVersion-2.0 Comment #2 on issue 54 by guy.robe...@gmail.com: Make it possible to go from auto-provision to scheduled http://code.google.com/p/ogf-nsi-project/issues/detail?id=54 (No comment was entered for this change.)
Updates: Status: Fixed Comment #3 on issue 54 by jmacau...@gmail.com: Make it possible to go from auto-provision to scheduled http://code.google.com/p/ogf-nsi-project/issues/detail?id=54 Fixed with revision 34.
participants (1)
-
ogf-nsi-project@googlecode.com