I would suggest this discussion would be best continued as comment on the live team discussions.
As Dmytro mentioned at Accelerate there was agreement to introduce a new component called Resource configurator similar to the Product Configurator. Rationale was that the profile and configuration templates need to be under the control of Network departments to meet emerging regulations on securing critical infrastructure.
Anastasios will be creating an ODA Component specification for this new component.
Original Message:
Sent: Feb 20, 2024 02:43
From: Dan d'Albuquerque
Subject: Resource order management vs resource activation
Confused, Koen is suggesting a separate component (ODA-C) for the TMF702 Resource Activation & Configuration provider (which I agree with), yet others are still suggesting that resource provisioning is part of the ROM. Should the ROM ODA-C then be renamed Resource Provisioning and the SOM ODA-C renamed Service Orchestration (to incorporate both SOM and SA-TMF640)?
------------------------------
Dan d'Albuquerque
Individual
Original Message:
Sent: Feb 19, 2024 09:53
From: Dmytro Gassanov
Subject: Resource order management vs resource activation
Hello,
The demand for having ROM and Resource Configuration/ Activation components separately was discussed in the previous Accelerate . We considered the traditional use cases with physical network elements. One of the motivations for having ROM and Resource Configuration components separately is regulator requirements in some countries. The current list of available ROM APIs is presented in TMFC011:Resource Order Management
UC008 was created before this proposal and doesn't have yet this component, so will be updated. TMF NaaS architecture implies having TMF ODA E2E Service Management Domain and different ODMs which was depicted in IG1224 noted by Dave.
Thank you for your comments.
------------------------------
Dmytro Gassanov
TM Forum
Original Message:
Sent: Feb 19, 2024 09:27
From: Koen Peeters
Subject: Resource order management vs resource activation
Hi,
The discussion regarding ROM and Resource Activation & Configuration dates from this month. Documentation of ig1228 UC to reflect this is work in progress.
Thanks for pointing out the sequence diagram that requires correction.
Regards
------------------------------
Koen Peeters
OryxGateway FZ LLC
Original Message:
Sent: Feb 19, 2024 09:20
From: Myagaa Nm
Subject: Resource order management vs resource activation
Hi,
According to ig1228 v16 uc008, the ROM calls a non TMF API "SM-DP+". You wrote that ROM doesn't interact in any non TMF protocol. Select/get actions are allowed?
------------------------------
Myagaa Nm
Mobicom Corporation
Original Message:
Sent: Feb 19, 2024 07:23
From: Koen Peeters
Subject: Resource order management vs resource activation
Hi,
We recently had a similar discussion in the ODA component group. As a conclusion Resource order management is defined as an component that orchestrates dependencies and updates resource inventories. ROM doesn't interact in any non TMF protocols. It calls a resource activation component that translates TMF formated activation in a protocol/API managed by another SDO (Standards Developing Organisation) (Netconf, SNMP, ...)
I hope that clarifies the separation.
Regards
------------------------------
Koen Peeters
OryxGateway FZ LLC
Original Message:
Sent: Feb 16, 2024 01:52
From: Myagaa Nm
Subject: Resource order management vs resource activation
Hello,
Resource order management (ROM) receives resource order request that contains multiple resource order items. Each resource order item contains one resource (an instance of resource specification). Resource activation (RA) receives a resource as request. Both of them receives resource structure. According to ig1228 uc008, ROM receives request from SOM. Then it passes the request to RA. In my opinion, one of them is enough to fulfill resource request. Why did the use case implement both?
------------------------------
Myagaa Nm
Mobicom Corporation
------------------------------