Can we then say, Network Controller is some sort of VIM and App Controller is 
sort of VNF-m.

thanks & regards,
Dhananjay Pavgi
Mobile : +91 98220 22264
[cid:image002.png at 01CE7323.F2727500]               [ONAP_logo_Sig]
www.techmahindra.com<http://www.techmahindra.com/>                 Platinum 
Member. Visit : http://www.onap.org<http://www.onap.org/>

From: onap-tsc-bounces at lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
Sent: Tuesday, April 18, 2017 9:33 PM
To: HU, BIN <bh526r at att.com>; onap-tsc at lists.onap.org; discuss at 
lists.onap.org
Subject: Re: [onap-tsc] Some questions regarding Controllers in ONAP 
Architecture

-              SDN Agent: [1] was a proposal and not how it is implemented 
today so I will leave the discussion of that to someone else but my 
understanding is it would be in the open-o repo (if it exists at all today)
-              Infrastructure Controller: right now its openstack (not just 
nova) but I know we are adding more. MSO would have the multicloud logic (maybe 
via cloudify or something) to handle that. The code you should be looking for 
is the po adapters in MSO 
(https://gerrit.onap.org/r/gitweb?p=mso/libs.git;a=tree;h=refs/heads/release-1.0.0;hb=refs/heads/release-1.0.0).
-              Network Controller: SDN-GC is the network controller and is odl 
based. Check out https://wiki.onap.org/display/DW/Architecture for the 
architecture of each part. The extra logic we have like sli is a separate 
docker which is then called by odl at certain points.
-              App Controller: Has the same architecture as SDN-GC (ie is odl + 
sli based). It's basically different karaf plugins and you could run them on 
either platform - it is an architecture distinction more at this point I believe

For either controller Brian freeman can go into more detail.

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at 
lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of HU, BIN
Sent: Tuesday, April 18, 2017 11:53 AM
To: onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>; discuss at 
lists.onap.org<mailto:discuss at lists.onap.org>
Subject: [onap-tsc] Some questions regarding Controllers in ONAP Architecture

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Hello community,

Reading current ONAP architecture [1] and tutorial of setting up the base ONAP 
stack [2], I have a few questions regarding those controllers:

-          SDN Agent:

o   What is the role, features and functions of SDN Agent? How is it different 
from Network Controller?

o   I couldn't find any code of SDN Agent in ONAP repo [3]. Does anyone know 
where it is?

-          Infrastructure Controller:

o   Is it OpenStack Nova? Or is it agnostic of any VIM and OpenStack is just 
one of the VIM?

o   If the intention is to be agnostic of VIM, and support other VIMs, where is 
a plugin/adaptor from architecture point of view?

o   I couldn't find code either in ONAP [3]. Does anyone know where it is?

-          Network Controller:

o   Is it OpenStack Neutron or ODL? Or Neutron with ODL as backend?

o   I found the code in [3], but it seems it only installs ODL there (correct 
me if I am wrong).

o   What is the primary role, features and functions of Network Controller 
other than those in ODL?

-          App Controller:

o   Are we using ODL too as App Controller?

o   Or Is it a container orchestrator or something else?

Appreciate if someone can explain some details, or give the pointer to more 
detailed documentation.

Thanks
Bin

[1] https://wiki.onap.org/display/DW/ONAP at 
ONS2017?preview=/3245268/3245303/ONAP%20Architecture%20Overview%20_Final-1.pdf<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_ONAP-40ONS2017-3Fpreview-3D_3245268_3245303_ONAP-2520Architecture-2520Overview-2520-5FFinal-2D1.pdf&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=3_AC6BGbT6uU35Nl7J2S5u7jo61YQjIHG11hEPv62EA&s=jRBZsDc2CyioeVWjhCRKHkPCIWewvBN-ob1eR-vvr1A&e=>
[2] 
https://wiki.onap.org/display/DW/Tutorial%3A+Configuring+and+Starting+Up+the+Base+ONAP+Stack<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Tutorial-253A-2BConfiguring-2Band-2BStarting-2BUp-2Bthe-2BBase-2BONAP-2BStack&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=3_AC6BGbT6uU35Nl7J2S5u7jo61YQjIHG11hEPv62EA&s=2ECLYmyNHjMuNAksMX82uMlGnsn1yZWHQ2z1K80oUB8&e=>
[3] 
https://git.onap.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=3_AC6BGbT6uU35Nl7J2S5u7jo61YQjIHG11hEPv62EA&s=xyj30pXIgxQyZunOXabVRS2Br7nc9M9jbO8-N7wrLi4&e=>

============================================================================================================================

Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html 
<http://www.techmahindra.com/Disclaimer.html> externally 
http://tim.techmahindra.com/tim/disclaimer.html 
<http://tim.techmahindra.com/tim/disclaimer.html> internally within 
TechMahindra.

============================================================================================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/fbc27bef/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 4909 bytes
Desc: image001.png
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/fbc27bef/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 7337 bytes
Desc: image002.jpg
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/fbc27bef/attachment-0001.jpg>

Reply via email to