The table bellow describes the problem and how it is or isn’t addressed today
Scenario | External system to be provisioned | Baseline approach | Reflections | Have Interface Interact With ESR | Project PTL | Feedback From |
|---|---|---|---|---|---|---|
Connection to cloud infra | Address and capabilities of VIM managers (e.g. openstack port) | Mult-VIM: will register/unregister VIM with ESR, the register VIM from ESR portal and need the health check function of VIM. | Yes | |||
| VID: manually input the VIM addresses and connection information to the portal, and sent this info to MSO which later call controllers which interact with all of these systems (VNFMS , VIM , EMS) | No | Avi from amdocs (avi.chapnic@amdocs.com) | ||||
| VF-C: get the VIM addresses from ESR. | Yes | |||||
| SO: will not interact with external system directly | No | jin xin | ||||
Connection to transport | SDN controller address’s and capabilities | vendor sdn controler which managed by VIM is not in the scope of ESR. How about the vendor sdn controller managed by ONAP SDN-C? There is a request about API used to verify that platform is available from SDN-C release plan. ONAP SDN-C: ? | no response | |||
Connecting to S-VNFM | S-VNFM and capabilites | VF-C: manage VNFM addresses from ESR | Could be part of the tosca/heat template | Yes | ||
EMS (Element Management System) | EMS address and capabilities | APP-C: will not interact with external system directly. Interfaces with other ONAP Components: AAI, Policy,, MSO, DCAE etc. | No | cl664y@att.com | ||
| Other | DCAE: DCAE will not collect the data from external system? | Lusheng Ji |
| View file | ||||
|---|---|---|---|---|
|
Stephen:
Based on the above, I understand that the Functionality that ESR provides is to enable a common means to input the addressing information required to enable ONAP to contact these external systems. That functionality does seem like a good idea. If we turn our attention to what is required, this seems to required:
- A means to input the addressing information
- A place to store the addressing information
- A means for the ONAP modules to retrieve this information.
A assume the means to input the addressing information should be using the SDC environment, I mean it isn't optimal to have another creation environment with a different look and feel.
Part of the discussion as I understand is to store this information into A&AI, actually it is kind of static inventory information - is this a decent fit - it could be better than having yet another storage to deal with.
If the above was correct, then I guess that ESR somewhat becomes a proxy for the address information, is that required or could that be directly retrieved from the storage instead, and the ESR project focusses on creating the module required in SDC to input the data and place it in the storage instead of having a proxy?
----
ESR meeting information
Time: wednesday(9 PM China, 1 PM UTC, 9 AM US/Eastern, 5th July )
...
ESR will supplies both portal and API to manage(register/query/delete/update) the external system, but will not deploy the external system. (Here external system means that the systems already exsist somewhere, but not included in ONAP, such as VIM/VNFM/EMS/vendor SDN controller)
ESR will check whether the external systems are reachable, but will not do the fault analysis.
...