Open APIs

Hi,

We are in the middle of implementing open API "Service Ordering Management API", as we were trying to implement this for one specific use case we came across to the challenge on how to receive actual resources using this API (eg. IP, adresss, Port, Shelf, Slot, etc) as we see it on the API you can only receive Service Characteristics but we can find a place where to put resources.

Maybe we can model everything as Services Characteristics even though they are resources.

Example.

"serviceCharacteristics": [
{
"name": "bandwidth",
"value": "100"
},
{
"name": "region",
"value": "US-NORTH"
},
{
"name": "Subnet",
"value": "10.44.14.61/30"
},
{
"name": "oltName",
"value": "OLT01"
},
{
"name": "routerName",
"value": "ROUTER01"
}
]

------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

​I think your APIs should reflect your Data Model.
If you have modelled Service and resources separately then you could create one API for ordering the service (Post) and offer set of Patch Options to order resources on top of the already ordered Service.

------------------------------
Neeraj Kumar
Swisscom AG
------------------------------

Original Message:
Sent: 11-21-2017 14:25
From: Christopher Gonzalez
Subject: Receiving Resources using: Service Ordering Management API

Hi,

We are in the middle of implementing open API "Service Ordering Management API", as we were trying to implement this for one specific use case we came across to the challenge on how to receive actual resources using this API (eg. IP, adresss, Port, Shelf, Slot, etc) as we see it on the API you can only receive Service Characteristics but we can find a place where to put resources.

Maybe we can model everything as Services Characteristics even though they are resources.

Example.

"serviceCharacteristics": [
{
"name": "bandwidth",
"value": "100"
},
{
"name": "region",
"value": "US-NORTH"
},
{
"name": "Subnet",
"value": "10.44.14.61/30"
},
{
"name": "oltName",
"value": "OLT01"
},
{
"name": "routerName",
"value": "ROUTER01"
}
]

------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

Thanks Neeraj,

Have you ever tried to implement this API o seen one like it?

KR

------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------

Original Message:
Sent: 11-22-2017 03:27
From: Neeraj Kumar
Subject: Receiving Resources using: Service Ordering Management API

​I think your APIs should reflect your Data Model.
If you have modelled Service and resources separately then you could create one API for ordering the service (Post) and offer set of Patch Options to order resources on top of the already ordered Service.

------------------------------
Neeraj Kumar
Swisscom AG

Original Message:
Sent: 11-21-2017 14:25
From: Christopher Gonzalez
Subject: Receiving Resources using: Service Ordering Management API

Hi,

We are in the middle of implementing open API "Service Ordering Management API", as we were trying to implement this for one specific use case we came across to the challenge on how to receive actual resources using this API (eg. IP, adresss, Port, Shelf, Slot, etc) as we see it on the API you can only receive Service Characteristics but we can find a place where to put resources.

Maybe we can model everything as Services Characteristics even though they are resources.

Example.

"serviceCharacteristics": [
{
"name": "bandwidth",
"value": "100"
},
{
"name": "region",
"value": "US-NORTH"
},
{
"name": "Subnet",
"value": "10.44.14.61/30"
},
{
"name": "oltName",
"value": "OLT01"
},
{
"name": "routerName",
"value": "ROUTER01"
}
]

------------------------------
Christopher Gonzalez
Intraway Corp
------------------------------