Hi Daniel,

I think they're different.

What MSB care about is providing a registration/discovery mechanism to 
facilitate the communication of Microservices, in particular, the 
Registration/discovery of MSB focus on the access end points of service 
providers.

What ESR provides is the central registry of External Systems, such as VNFM, 
VIM, SDNC and EMS. So the relevant component of ONAP can use it in the process 
of orchestration. For example, the Orchestrator may need to know available 
VNFMs instances and choose one according to VNF type and location when create a 
VNF.




Thanks,

Huabing



Original Mail



Sender:  <[email protected]>
To: lizi00164331 <[email protected]> <[email protected]>
Date: 2017/05/15 22:09
Subject: Re: [onap-discuss] [onap-tsc] Project Proposal: External SystemRegister







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


·  Register/query/update/delete function of EMS.


 


Can you say how they are different?


 


Daniel Rose


ECOMP / ONAP


com.att.ecomp


732-420-7308


 


From: [email protected] [mailto:[email protected]] 
On Behalf Of [email protected]
 Sent: Sunday, May 14, 2017 10:32 PM
 To: [email protected] [email protected]
 Subject: [onap-tsc] Project Proposal: External System Register


 

 


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 deploy a VNF. So they should get the information 
of available external systems from a registry before call the Interfaces of 
these external systems.  ESR provides a service to centralized management of 
the information (name, vendor, version, acess end point,  etc.) of external 
systems. So the ONAP components can get the system information with unified API 
from a logical single point.


 


The proposal wiki page, which includes details of the project description 
(including sub projects), project scopes, and proposed repo names, can be found 
at: https://wiki.onap.org/display/DW/External+System+Register 


 


Thanks,


 


LiZi

 

 

 


 


李滋 lizi


 


IT开发工程师 IT Development Engineer
 网管及服务开发二部/中心研究院/系统产品 Network Management & Service Development Dept. II/Central 
R&D  Institute/System Product


 






 成都市高新区天府大道中段800号中兴通大厦
 ZTE Corporation Building, No. 800 Middle Section Tianfu Avenue, 
 Chengdu, P..R.China, 610041 
 M: +86 15583405168 
 E: [email protected] 
 www.zte.com.cn
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc

Reply via email to