Open APIs

Hi

My UC: User punches in Device Name and a Port Name as part of the REST request and need to perform activate/de-activate of the port.

Queries:
1/ I see there are generic states defined as per TR255 in TMF639 spec - but there is no mention how we could use these states when doing a PATCH on a physical resource.
2/ In the examples there is a mention of having lifecycle state being patched as "Reserved" - but Reserved is not the sub-state of any of the state machine diagram described in the spec pg14.
3/ For my UC i was thinking to base state=operating & sub-state=Adminstrative updated as Activated/Deactivated. But not sure how that can be put in the PATCH request.

Thanks in advance for your help

Thanks
Vikas

------------------------------
Vikas Kumar
Ciena Corporation
------------------------------

​Vikas
My recollection from speaking to author of TR 255 a ew months back was that the state model was taken from our previous interface work on MTOSI

https://www.tmforum.org/resources/suite/mtosi-4-0/

I'll need to check back as It is quite a while since I reviewed these documents however this did have an operational and administrative state model which originated in earlier ITU -T work in the X.700 series maybe X.731?

Other's may be more up to date on this than I

------------------------------
Dave Milham
TM Forum Chief Architect, TM Forum
------------------------------

Original Message:
Sent: Oct 03, 2018 19:57
From: Vikas Kumar
Subject: TMF639 States of a Physical Resource

Hi

My UC: User punches in Device Name and a Port Name as part of the REST request and need to perform activate/de-activate of the port.

Queries:
1/ I see there are generic states defined as per TR255 in TMF639 spec - but there is no mention how we could use these states when doing a PATCH on a physical resource.
2/ In the examples there is a mention of having lifecycle state being patched as "Reserved" - but Reserved is not the sub-state of any of the state machine diagram described in the spec pg14.
3/ For my UC i was thinking to base state=operating & sub-state=Adminstrative updated as Activated/Deactivated. But not sure how that can be put in the PATCH request.

Thanks in advance for your help

Thanks
Vikas

------------------------------
Vikas Kumar
Ciena Corporation
------------------------------

​Spoke to original editor for MTOSI work Steve Fratini and he tells me the state model is in
Network Resource Basic DDP as a supporting document SD2-17  which should be in the MTOSI 4.0 package

------------------------------
Dave Milham
TM Forum Chief Architect, TM Forum
------------------------------

Original Message:
Sent: Oct 04, 2018 06:30
From: Dave Milham
Subject: TMF639 States of a Physical Resource

​Vikas
My recollection from speaking to author of TR 255 a ew months back was that the state model was taken from our previous interface work on MTOSI

https://www.tmforum.org/resources/suite/mtosi-4-0/

I'll need to check back as It is quite a while since I reviewed these documents however this did have an operational and administrative state model which originated in earlier ITU -T work in the X.700 series maybe X.731?

Other's may be more up to date on this than I

------------------------------
Dave Milham
TM Forum Chief Architect, TM Forum

Original Message:
Sent: Oct 03, 2018 19:57
From: Vikas Kumar
Subject: TMF639 States of a Physical Resource

Hi

My UC: User punches in Device Name and a Port Name as part of the REST request and need to perform activate/de-activate of the port.

Queries:
1/ I see there are generic states defined as per TR255 in TMF639 spec - but there is no mention how we could use these states when doing a PATCH on a physical resource.
2/ In the examples there is a mention of having lifecycle state being patched as "Reserved" - but Reserved is not the sub-state of any of the state machine diagram described in the spec pg14.
3/ For my UC i was thinking to base state=operating & sub-state=Adminstrative updated as Activated/Deactivated. But not sure how that can be put in the PATCH request.

Thanks in advance for your help

Thanks
Vikas

------------------------------
Vikas Kumar
Ciena Corporation
------------------------------

​I spoke to the  MTOSI 4.0 Editor Steve Fratini  and he telss me the state model is in:

the Network Resource Basic DDP as a supporting document SD2-17
name is SD2-17_EnhancedResourceStates.pdf


------------------------------
Dave Milham
TM Forum Chief Architect, TM Forum
------------------------------

Original Message:
Sent: Oct 03, 2018 19:57
From: Vikas Kumar
Subject: TMF639 States of a Physical Resource

Hi

My UC: User punches in Device Name and a Port Name as part of the REST request and need to perform activate/de-activate of the port.

Queries:
1/ I see there are generic states defined as per TR255 in TMF639 spec - but there is no mention how we could use these states when doing a PATCH on a physical resource.
2/ In the examples there is a mention of having lifecycle state being patched as "Reserved" - but Reserved is not the sub-state of any of the state machine diagram described in the spec pg14.
3/ For my UC i was thinking to base state=operating & sub-state=Adminstrative updated as Activated/Deactivated. But not sure how that can be put in the PATCH request.

Thanks in advance for your help

Thanks
Vikas

------------------------------
Vikas Kumar
Ciena Corporation
------------------------------

Hi Kumar,

I agree the TMF 639  state diagram is incomplete in that respect.

Based on the text description I have created my own model using a further level of detail: 


On top of this I believe an additional "assignmentState" is required to manage the usage of a Resource:



------------------------------
Koenraad Peeters
Ciminko Luxembourg
------------------------------

Original Message:
Sent: Oct 03, 2018 19:57
From: Vikas Kumar
Subject: TMF639 States of a Physical Resource

Hi

My UC: User punches in Device Name and a Port Name as part of the REST request and need to perform activate/de-activate of the port.

Queries:
1/ I see there are generic states defined as per TR255 in TMF639 spec - but there is no mention how we could use these states when doing a PATCH on a physical resource.
2/ In the examples there is a mention of having lifecycle state being patched as "Reserved" - but Reserved is not the sub-state of any of the state machine diagram described in the spec pg14.
3/ For my UC i was thinking to base state=operating & sub-state=Adminstrative updated as Activated/Deactivated. But not sure how that can be put in the PATCH request.

Thanks in advance for your help

Thanks
Vikas

------------------------------
Vikas Kumar
Ciena Corporation
------------------------------

The following message has been sent to you in response to your Discussion message

Message From: Koenraad Peeters 

Hi Kumar,

I agree the TMF 639  state diagram is incomplete in that respect.

Based on the text description I have created my own model using a further level of detail: 


On top of this I believe an additional "assignmentState" is required to manage the usage of a Resource:



------------------------------
Koenraad Peeters
Ciminko Luxembourg
------------------------------

Original Message:
Sent: Oct 03, 2018 19:57
From: Vikas Kumar
Subject: TMF639 States of a Physical Resource

Hi

My UC: User punches in Device Name and a Port Name as part of the REST request and need to perform activate/de-activate of the port.

Queries:
1/ I see there are generic states defined as per TR255 in TMF639 spec - but there is no mention how we could use these states when doing a PATCH on a physical resource.
2/ In the examples there is a mention of having lifecycle state being patched as "Reserved" - but Reserved is not the sub-state of any of the state machine diagram described in the spec pg14.
3/ For my UC i was thinking to base state=operating & sub-state=Adminstrative updated as Activated/Deactivated. But not sure how that can be put in the PATCH request.

Thanks in advance for your help

Thanks
Vikas

------------------------------
Vikas Kumar
Ciena Corporation
------------------------------

Just as a general point on states and transitions in the Open API specs - we have a rule that the diagrams are illustrative, not normative. This allows specific businesses to change the states and transition logic and still maintain compliance with the API.

------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------

Original Message:
Sent: Oct 07, 2018 06:02
From: Koenraad Peeters
Subject: TMF639 States of a Physical Resource

The following message has been sent to you in response to your Discussion message

Message From: Koenraad Peeters 

Hi Kumar,

I agree the TMF 639  state diagram is incomplete in that respect.

Based on the text description I have created my own model using a further level of detail: 


On top of this I believe an additional "assignmentState" is required to manage the usage of a Resource:



------------------------------
Koenraad Peeters
Ciminko Luxembourg

Original Message:
Sent: Oct 03, 2018 19:57
From: Vikas Kumar
Subject: TMF639 States of a Physical Resource

Hi

My UC: User punches in Device Name and a Port Name as part of the REST request and need to perform activate/de-activate of the port.

Queries:
1/ I see there are generic states defined as per TR255 in TMF639 spec - but there is no mention how we could use these states when doing a PATCH on a physical resource.
2/ In the examples there is a mention of having lifecycle state being patched as "Reserved" - but Reserved is not the sub-state of any of the state machine diagram described in the spec pg14.
3/ For my UC i was thinking to base state=operating & sub-state=Adminstrative updated as Activated/Deactivated. But not sure how that can be put in the PATCH request.

Thanks in advance for your help

Thanks
Vikas

------------------------------
Vikas Kumar
Ciena Corporation
------------------------------