discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>;
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] Project Proposal: External System
Register
Hi Jacopo,
Thanks for your quick response. The business logic can be information
Hi,
I would agree with Steve about the need to limit overlap between subprojects
Jacopo
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
On Behalf Of Stephen Terrill
Sent: Monday, May 15, 2017 10:10 AM
To: li.z...@zte.com.cn; onap-...@lists.onap.org;
Hi,
While I agree with the need of the external elements to be registered, is there
a reason for why we need a separate register in addition to A? (note: I saw
that Catherine had a comment with a similar lines). It may also relate to
catalogue - LiZi, have you had a chance to chat with the A
Dear ONAP TSC,
We would like to formally propose the External System Register project for ONAP.
ONAP components need to talk with external systems such as VIM/VNFM/SDNC/EMS to
orchestrate a network service, for example, SO/VF-C need to talk with VIM to
allocate resource and VNFM to
Hi LiZi,
How would you compare this project with the MSB project?
MSB lists
Service discovery - Server side discovery
and you list
• Register/query/update/delete function of VIM
• Register/query/update/delete function of VNFM
• Register/query/update/delete function of SDN Controller
•
