Open APIs

Hi,

     I am implementing TMF641 and use service catalog to find CFS to RFS dependencies. However when I call disconnect order, then actions on resources are almost opposite of what we do for Add order e.g. For Add order, you reserve the inventory first (Resource Spec) and then go to switch to activate it (RFS). However for disconnect, you de-activate on switch first (RFS) and then go to release inventory. I can take different action for each order within the Resource orders but calling these resource order sequence is based on CFS to RFS mapping and same for all order types (Move, Add, Change and Disconnect).  How to change that?

Howdy Somesh,

I may be missing something but in most build up and tear down scenarios the steps are reversed. For example, you cannot put the item back into inventory until all of the dependencies that are downstream in fulfillment have been reversed and removed. In this case, one has to deactivate (RFS) before releasing the inventory (Resource Spec). Does that make sense?

Cheers,

Wade 

Hi Wade,

   Thanks for responding.  My challenge is that the RFS/RS sequence of disconnect is not exactly opposite of add. In that case, how do we manage the dependencies between RFS as dependencies are not defined for order type but are generic for all types of orders.

Regards,
Somesh