Hi Brian,




Sorry for confusing. The SDNC in "related external system" column means vendor 
SDN controller, the SDN-C in "Project" column refers to the ONAP SDNC. 


ESR will not be located and responsible for the communication between 
controllers. But just supplies a way to tell the other components where the 
vendor SDN controllers are, and also the basic information which will be used 
while contact with the vendor controller. 






The vendor sdn controler which is managed by VIM do not fit for ESR. But I am 
wondering whether there is any vendor SDN controller was managed by ONAP SDNC. 
In my opinion those vendor sdnc which managed by ONAP SDNC may be valid for ESR.


 


Thanks,


LiZi

















原始邮件



发件人: <[email protected]>
收件人:李滋00164331 <[email protected]> <[email protected]> <[email protected]> 
<[email protected]> <[email protected]> <[email protected]> 
<[email protected]> <[email protected]> <[email protected]> 
<[email protected]> <[email protected]> <[email protected]> 
<[email protected]> <[email protected]> <[email protected]>
抄送人: <[email protected]>
日 期 :2017年06月13日 15:43
主 题 :RE: [onap-tsc]  Call for feedback about interaction with ExternalRegister 
System







This table is confusing since it is using the term SDN-C for both the ONAP SDNC 
and VIM sdn local controllers.


Its not clear to me that the sdn controllers are valid ESR end points since in 
fact we could be using BGP and non-rest api interfaces for some of the 
communication between controllers depending on the network function being used.


 


When the network function is associated with non-real time provisioning we also 
likely would not have a direct SDNC to local controller interface but rather 
use the HEAT /ARM template interfaces to communicate the information needed to  
the local controller on required networking (OS::Neutron for instance in HEAT)


 


Brian


 


 


From: [email protected] [mailto:[email protected]] 
On Behalf Of [email protected]
 Sent: Sunday, June 11, 2017 10:11 PM
 To: AGGARWAL, MANISHA <[email protected]> KLEIN, REUBEN <[email protected]> BURNS, 
COLIN <[email protected]> [email protected] TIMONEY, DAN <[email protected]> 
[email protected] [email protected] [email protected] SMOKOWSKI, 
STEVEN <[email protected]>  [email protected] [email protected] 
[email protected] [email protected] HEMLI, AMICHAI <[email protected]> 
WEST, EARLE <[email protected]>
 Cc: [email protected]
 Subject: [onap-tsc] Call for feedback about interaction with External Register 
System


 


Hi There,


 


After discussion about the ESR in the subgroup in the F2F meeting in Beijin. We 
got a consquence that ESR is necessary. But since we do not clear about the 
business detail of other projects, such as VID/Multi-VIM/VF-C/SO/SDN-C  etc. So 
we may do not clear that which projects will interact with ESR or whether the 
project has seed code of the function which ESR supplies. This is why I am 
reaching out.


 


Here, I would like to emphasize about the scope of ESR again, and do some 
clarification about some points. 

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.


For the project description and the scope of ESR, you may visit 
https://wiki.onap.org/pages/viewpage.action?pageId=5734948 


 


The sequence diagram bellow shows what we think about the interaction between 
ESR and other components in high level. But we still need to confirm it with 
VID/A&AI/Multi-VIM/SO/VF-C/APP-C/SDN-C team in the detail business scenario.





 


Here I listed a table about the ONAP project and its related external systems 
(if I am wrong please correct me). 


 

Project


Related external system


 Will interact with ESR(Yes/No)


VID


VIM/VNFM/EMS/SDNC


Yes


Multi-VIM


VIM


Yes


SDN-C


Vendor SDN controller


Yes


VF-C


VIM/VNFM/EMS/SDNC


Yes


SO


VIM/VNFM/EMS/SDNC


Yes


APP-C


EMS


Yes


 


Briefly, according to the comments about ESR in the F2F meeting in Beijin. I 
need you guys give a feedback about whether your components will interact with 
ESR about the external systems OR how the function  of ESR is realized in your 
component( if you do have the function of ESR). 


 


Thanks a lot.


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