Issue 53 in ogf-nsi-project: confirmation messages for all state tranistions?
Status: New Owner: ---- Labels: Type-Review Priority-Medium FoundInVersion-1.0 FixedInVersion-1.1 New issue 53 by guy.robe...@gmail.com: confirmation messages for all state tranistions? http://code.google.com/p/ogf-nsi-project/issues/detail?id=53 Description of Issue: Henrik: do we need a universal confirmation from PA to RA for all state transitions? Discussion of Issue: TK: could add a large burden of unnecessary messages? Resolution of Issue: The implications of the change needs to be reviewed.
Updates: Status: Accepted Owner: tkudoh...@gmail.com Labels: -FixedInVersion-1.1 FixedInVersion-2.0 Comment #1 on issue 53 by guy.robe...@gmail.com: confirmation messages for all state tranistions? http://code.google.com/p/ogf-nsi-project/issues/detail?id=53 GR: I have assigned this to Tomohiroh Kudoh-san for consideration as he is one of the main authors of the current state-machine. This will not be changed before version 2.0 at the earliest.
Comment #2 on issue 53 by thost...@gmail.com: confirmation messages for all state tranistions? http://code.google.com/p/ogf-nsi-project/issues/detail?id=53 Just an update for this. I'm currently refactoring OpenNSA quite a bit and I am running into all sort of odd corners for aggregation. If an aggregate state is supposed to only switch into a state once all sub-connection have switched into this state it is impossible for the aggregated state to move into auto-provision as there is no confirmation message for moving into that state. Of course we could use the reserve reply message for this indication (i.e., the initial reply in the same http stream, NOT the provisionConfimed callback ). However there is no well-defined meaning that reply so this isn't really an option either. I am not buying the whole burden of unnessary/ineffiency. If you want a fast, optimized protocol, we should have picked something else than SOAP+WSDL, and avoid the callback structure and switch to message based system, where we could have message for each state update, but with less messages in total.
Comment #3 on issue 53 by tkudoh...@gmail.com: confirmation messages for all state tranistions? http://code.google.com/p/ogf-nsi-project/issues/detail?id=53 As stated in the state machine, transition from Reserved to Auto-Provision happens when a provision request is received before the start_time. The transition happens without confirmation of transitions of children. I believe the specification of current state machine is clear enough to show this. It is designed to have no implicit state transition, regardless of whether it is used for an aggregator or ultimate provider.
participants (1)
-
ogf-nsi-project@googlecode.com