Open APIs

Hi there,

A resource flavor represents a master node and worker nodes in my resource catalog. Both the nodes consist of CPU, mem, storage.  resourceSpecCharacteristic definition in the API specs allows only String or Integer. Therefore it cannot be represented. I was thinking of the following: 

1. Define the node as a custom object and represent it in the resourceSpecCharacteristic.  However, the resourceSpecCharacteristic should be extended to accept an array of objects.

2. Master node and worker node represents two resources in the catalog. CPU, mem, storage will be presented in resourceSpecCharacteristic. Stitch these two together as a composite resource (flavor). Alternatively, we can put these together as  service in the service catalog.

I'd really appreciate any direction in this. 

Thank you.

------------------------------
Mohamed Nahfees
SingTel Optus
------------------------------

In version 4 of the Open APIs, characteristics (including Resource Spec Characteristics in TMF 634, see the entry for the API on the beta publication page here  ) are modeled with Any (which is basically an empty JSON schema fragment that matches any JSON structure), so that any data type can be used for a characteristic value. This would allow you to define complex characteristics.

However, since this Any pattern has caused issues in some code generations, we will be moving in version 5 to a strongly-typed characteristic pattern, which still will allow you to define complex data types (including arrays) for characteristic values.

Hope it helps

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------

Thank you very much.

------------------------------
Mohamed Nahfees
SingTel Optus
------------------------------

Original Message:
Sent: May 10, 2020 01:15
From: Jonathan Goldberg
Subject: TMF634 - infra resource provisioning

In version 4 of the Open APIs, characteristics (including Resource Spec Characteristics in TMF 634, see the entry for the API on the beta publication page here  ) are modeled with Any (which is basically an empty JSON schema fragment that matches any JSON structure), so that any data type can be used for a characteristic value. This would allow you to define complex characteristics.

However, since this Any pattern has caused issues in some code generations, we will be moving in version 5 to a strongly-typed characteristic pattern, which still will allow you to define complex data types (including arrays) for characteristic values.

Hope it helps

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------