The APIs tend to fall into one of a set of common patterns including
Catalog,
Inventory and
Activation. If your intent is to cause the instantiation of a
Physical or
Logical Resource entity than TMF702 would be appropriate. If your intent is to cause the instantiation of a
Resource Function entity that it's TMF664 which also includes
Task Resources for Day 2 operations such as
Scale,
Heal and
Migrate which are specific to
Resource Function. Afterwards you may want to record the instantiated details in a
Resource Inventory with TMF639.
If you're looking for overlap, here's a little game for you, try and find a difference between TMF702 and TMF639. :)
------------------------------
Vance Shipley
SigScale
------------------------------
Original Message:
Sent: Jul 13, 2022 00:35
From: Srinivasa Vellanki
Subject: TMF702 vs TMF664
Is there any material providing guidance on when to use TMF702 vs TMF664.
Didn't do proper analysis but at a high level TMF664 appears to be over-lapping with TMF702 & TMF640.
------------------------------
Srinivasa Vellanki
Reliance Jio Infocomm Ltd
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of my employer or TM Forum.
------------------------------