If you look at the SLI-API tutorial for VoLTE on the wiki you can get a sense 
of how this is accomplished. Here a set node is used but all the value’s could 
references to context memory variables.

Device.* schema is defined by the adaptor (in this case the DC Gateway vendor’s 
API)

<parameter name='device.evpn_irts' value='1:5000'/>
<parameter name='device.evpn_erts' value='1:5000'/>
<parameter name='device.local_subnet' 
value='\"8a41319d-87cf-4cd6-8957-00000000000A\"'/>
<parameter name='device.id' value='CDD702C3-7719-4FE6-A5AD-3A9C9E265309' />
<parameter name='device.name' value='PODX-routerY' />
<parameter name='device.description' value='VPC A connect VPC B' />
<parameter name='device.router_id' value='CBB702C3-6789-1234-A5AD-00000000000A' 
/>

As an example (final parameter-name have not been selected) we might get this 
input


        {

            "parameter-name": "volte-wan-activate.dca_name",

            "string-value": "dcA-east"

        },

        {

            "parameter-name": "volte-wan-activate.dcb_name",

            "string-value": "dcB-west"

        },


The DG would lookup dcA-east and determine that the ip address of the 
controller was 10.0.1.0 and dcB-east was 10.0.2.0 (or FQDNs etc) and that the 
dcA router ID was:
'CBB702C3-6789-1234-A5AD-00000000000A’

The DG would assign a WAN VNI from resource assignment, assign import and 
export route targets from resource assignment , calculate names from 
source/destination data like the device.description, etc.

Input variables from the call from SO would also be mapped.

Then the paramters to the adaptor could be

<parameter name='device.evpn_irts' 
value='`$dc_connection.import_route_targets`'/>
<parameter name='device.evpn_erts' 
value=`$dc_connection.export_route_targets`'/>
<parameter name='device.local_subnet' 
value='$service_data_input.dc_connection.neutron_subnet_id`'/>
<parameter name='device.id' value=`$dc_connection.device_id`' />
<parameter name='device.name' value='PODdcA-east-routerdcB-west' />
<parameter name='device.description' value='VPC dcA-east connect VPC dcB-west' 
/>
<parameter name='device.router_id' value=’`$dc_connection.a_end_router_id`' />

To be clear device.* comes from the adaptor and probably would be something 
more specific than device but the leaf names would likely match the parameters 
in the API call to the 3rd party controller.

Dc_connection.* and service_data.* are from the northbound service model and 
network data model in context memory.

Using the SLI-API and an emulator we can build and test the adaptor and the DG 
in advance of having the rest of the assets available.

The actual parameter names need to be specified so that SO can provide the 
correct rpc into SDNC but that is not dependent on the actual names used in the 
adaptor node – the DG maps from the service model parameters into those adaptor 
specific (device) parameters.

Brian


From: FREEMAN, BRIAN D
Sent: Tuesday, August 08, 2017 8:35 AM
To: huang.zhuo...@zte.com.cn
Cc: SHADMI, DAVID <ds2...@att.com>; TIMONEY, DAN <dt5...@att.com>; 
seshu.kuma...@huawei.com; KAPELUTO, ZAHI <zk0...@intl.att.com>; 
onap-disc...@lists.onap.org; ROZIN, EDEN <er4...@intl.att.com>; 
onap-tsc@lists.onap.org
Subject: RE: Re: [onap-tsc]答复: Re: ONAP VoLTE SDC call

The adaptor should define its inputs as parameters in the adaptor node.

The schema for those paramters can be defined by the adaptor/vendor.

The directed graph will map from the WAN model into the vendor specific mode in 
the adaptor.

We are going to recomend using a model called the GENERIC-RESOURCE-API that has 
a name/value pair list of the parameters and we will pull the paramters of 
interface from that API to populate the inputs to the adaptor node.

Brian


From: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn> 
[mailto:huang.zhuo...@zte.com.cn]
Sent: Tuesday, August 08, 2017 7:30 AM
To: FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>
Cc: SHADMI, DAVID <ds2...@att.com<mailto:ds2...@att.com>>; TIMONEY, DAN 
<dt5...@att.com<mailto:dt5...@att.com>>; 
seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>; KAPELUTO, ZAHI 
<zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; ROZIN, EDEN 
<er4...@intl.att.com<mailto:er4...@intl.att.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: 答复: Re: [onap-tsc]答复: Re: ONAP VoLTE SDC call


Hi, Brian

    Maybe here is the old question. Is there a common model for WAN description 
in SDN-C? If no, where should SDN-C get the input of adapter?

Thank you!











黄卓垚    huangzhuoyao



职位    position
承载网管开发部/有线研究院/有线产品经营部    Strategy & IT-IT Dept.


[cid:image001.gif@01D31024.C456DB50]

[cid:image002.gif@01D31024.C456DB50]
深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R&D Building, ZTE Corporation Hi-tech Road South,
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057
T: +86 755 xxxxxxxx       F: +86 755 xxxxxxxx
M: +86 xxxxxxxxxxx
E: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
www.zte.com.cn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.zte.com.cn_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=HOWZLahe1mXKqDImjc3B5fipcPdDraflmcdTzJ3nQjU&s=8zUbLA_YesMd1uo2vKgT-1smH1jDAHKSGQPIqz6Dc3Y&e=>


原始邮件
发件人: <bf1...@att.com<mailto:bf1...@att.com>>;
收件人:黄卓垚10112215; <ds2...@att.com<mailto:ds2...@att.com>>; 
<dt5...@att.com<mailto:dt5...@att.com>>; 
<seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>;
抄送人: <zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>; 
<er4...@intl.att.com<mailto:er4...@intl.att.com>>; 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>;
日 期 :2017年08月07日 23:09
主 题 :Re: [onap-tsc]答复: Re:  ONAP VoLTE SDC call


“be placed manually according to specific apdator”

The 3rd party adaptor needs the yang model as part of its development so it 
isnt needed from SDC its needed as part of the adaptor development.


I dont know if there is value in providing the yang model in the CSAR since its 
already going to be available on the controller as part of the adaptor that 
would be more Dan Timoney’s call and he probably has a better view of the 
overall  SDC to SDNC flow anyway.

Brian


From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of 
huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
Sent: Monday, August 07, 2017 7:12 AM
To: SHADMI, DAVID <ds2...@att.com<mailto:ds2...@att.com>>; TIMONEY, DAN 
<dt5...@att.com<mailto:dt5...@att.com>>; 
seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; KAPELUTO, 
ZAHI <zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; ROZIN, EDEN 
<er4...@intl.att.com<mailto:er4...@intl.att.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] 答复: Re: ONAP VoLTE SDC call


Hi,  David, Dan and seshu



   Some questions about how WAN service descriptor works with SO and SDN-C:

  1.  How does SDN-C import the YANG file describing NBI of 3rd controller? By 
Json from SO? Or be placed manually according to specific apdator? Or by other 
ways?
  2.  What kind of infomation should be contained in the interface between SO 
and SDN-C? YANG describing NBI of 3rd controller? CSAR of WAN descriptor? 
Information sending to 3rd controller? Or something else?
  3.  SDN-C receive CSAR from SDC?
  4.  SO is responsible for abstracting YANG from CSAR which is discribing the 
NBI of 3rd controller?
  5.  How to import the YANG describing NBI of 3rd controller into CSAR?



I suggest that we should discuss this topic outside the SDC call on Monday.  Do 
you have any good idea about suitable time for the discussion?



Thank you all!









黄卓垚    huangzhuoyao



职位    position
承载网管开发部/有线研究院/有线产品经营部    Strategy  & IT-IT Dept.


[cid:image001.gif@01D31024.C456DB50]

[cid:image002.gif@01D31024.C456DB50]
深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R&D Building, ZTE Corporation Hi-tech Road South,
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057
T: +86 755 xxxxxxxx       F: +86  755 xxxxxxxx
M: +86 xxxxxxxxxxx
E: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
www.zte.com.cn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.zte.com.cn_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=FUaOnuThGoi7rszuMjB5A44hZAWX0ak0as-MAyXrNNw&s=fE5ujy53EYv0-ASEIaLvHBom0jzRvgi4ocNdpKeIErk&e=>


原始邮件
发件人:黄卓垚10112215
收件人: <ds2...@att.com<mailto:ds2...@att.com>>; 
<dtimo...@att.com<mailto:dtimo...@att.com>>; 
<seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>;
抄送人:袁越10008526; <er4...@intl.att.com<mailto:er4...@intl.att.com>>;  
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>; 
<zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>;
日 期 :2017年08月05日 16:45
主 题 :答复: Re: [onap-tsc] ONAP VoLTE SDC call



There are some issues about how WAN service descriptor works with SO and SDN-C 
might need to be clarified. I suggest should we have a discussion on Monday 
8:00 PM UTC on these issues first? If this time is not suitable for everyone, 
please choose a better  time for discussion.



Thank you all!











黄卓垚    huangzhuoyao



职位    position
承载网管开发部/有线研究院/有线产品经营部    Strategy  & IT-IT Dept.


[cid:image001.gif@01D31024.C456DB50]

[cid:image002.gif@01D31024.C456DB50]
深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R&D Building, ZTE Corporation Hi-tech Road South,
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057
T: +86 755 xxxxxxxx       F: +86  755 xxxxxxxx
M: +86 xxxxxxxxxxx
E: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
www.zte.com.cn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.zte.com.cn_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=FUaOnuThGoi7rszuMjB5A44hZAWX0ak0as-MAyXrNNw&s=fE5ujy53EYv0-ASEIaLvHBom0jzRvgi4ocNdpKeIErk&e=>






发件人: <ds2...@att.com<mailto:ds2...@att.com>>;
收件人:袁越10008526;黄卓垚10112215;
抄送人: <er4...@intl.att.com<mailto:er4...@intl.att.com>>; 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>;  
<zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>;
日 期 :2017年08月05日 01:27
主 题 :Re: [onap-tsc] ONAP VoLTE SDC call


Can we use the SDC call on Monday 8am PDT to discuss the WAN service descriptor?

Thanks,
David

From: yuan....@zte.com.cn<mailto:yuan....@zte.com.cn> 
[mailto:yuan....@zte.com.cn]
Sent: Thursday, August 03, 2017 10:49 PM
To: SHADMI, DAVID <ds2...@att.com<mailto:ds2...@att.com>>; 
huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
Cc: denghu...@huawei.com<mailto:denghu...@huawei.com>; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; KAPELUTO, ZAHI 
<zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; ROZIN, EDEN 
<er4...@intl.att.com<mailto:er4...@intl.att.com>>
Subject: 答复: Re: [onap-tsc] ONAP VoLTE SDC call


Congratulations! Great progress for ONAP R1.

@David:  SO, SDNC, SDC team and WAN provider of Volte usecase(ZTE and CMCC) 
might have further work on defining of WAN service descriptor which is not as 
clear as NS descriptor.

@Zhuoyao Huang: please prepare and arrange discussion with related teams.

Thank you all!



Yuan Yue





袁越 yuanyue

资深战略规划师   Senior Strategy Planner

技术规划部/技术规划部/系统产品 Technology Planning Dept./Technology Planning Dept./System 
Product


[cid:image001.gif@01D31024.C456DB50]

[cid:image002.gif@01D31024.C456DB50]
南京市雨花区软件大道50号中兴通讯3号楼
1/F,Building 3, ZTE Nanjing R&D Center II, No.50, Software Avenue,YuHua 
District,Nanjing,P.R.China 210012

T: +025 88013478
M: +86 13851446442
E: yuan....@zte.com.cn<mailto:yuan....@zte.com.cn>
www.zte.com.cn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.zte.com.cn_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=xTG_RQ0qpMCVf07qx4XAH9v0FiXvV4kjNleRuNzQYSM&s=CiFknwpdQ5kvXS9vbAIA9YJ1Zk6-dOs4mVAokPeKU-c&e=>

原始邮件
发件人: <ds2...@att.com<mailto:ds2...@att.com>>;
收件人: <denghu...@huawei.com<mailto:denghu...@huawei.com>>; 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>;   
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>;
抄送人: <zk0...@intl.att.com<mailto:zk0...@intl.att.com>>; 
<er4...@intl.att.com<mailto:er4...@intl.att.com>>;
日 期 :2017年08月04日 01:52
主 题 :Re: [onap-tsc] ONAP VoLTE SDC call


All,

SDC can support SO suggestion for VoLTE service design presented in th call.

With that, I believe we concluded the discussion about the different options, 
and we are moving forward with Option A.

1.       SDC supports onboarding the vIMS and vEPC validated (VNF SDK) VNFs.

2.       vIMS, vEPC, and WAN services design in SDC.

3.       VoLTE service design in SDC.

4.       Distribution of the 4 services to SO, SDNC, VF-C, A&AI.

Regards,
David

-----Original Appointment-----
 From: LANDO, MICHAEL On Behalf Of denghui (L)
 Sent: Thursday, August 03, 2017 5:09 AM
 To: denghui (L); KAPELUTO, ZAHI; SHADMI, DAVID; ROZIN, EDEN; 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc; 
Lando,Michael
 Subject: FW: ONAP VoLTE SDC call
 When: Thursday, August 03, 2017 9:00 PM-10:00 PM (UTC+08:00) Beijing, 
Chongqing, Hong Kong, Urumqi.
 Where: 
https://zoom.us/j/137904496<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_137904496&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=xTG_RQ0qpMCVf07qx4XAH9v0FiXvV4kjNleRuNzQYSM&s=KM5n-s_9vMSKwAcr5SJzfAdE3a4ckANdYuvoUyYKGNk&e=>

-----Original Appointment-----
 From: denghui (L) [mailto:denghu...@huawei.com]
 Sent: Thursday, August 03, 2017 9:20 AM
 To: denghui (L); 
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc; 
Lando,Michael
 Subject: ONAP VoLTE SDC call
 When: Thursday, August 03, 2017 9:00 PM-10:00 PM (UTC+08:00) Beijing, 
Chongqing, Hong Kong, Urumqi.
 Where: 
https://zoom.us/j/137904496<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_137904496&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=xTG_RQ0qpMCVf07qx4XAH9v0FiXvV4kjNleRuNzQYSM&s=KM5n-s_9vMSKwAcr5SJzfAdE3a4ckANdYuvoUyYKGNk&e=>

Hello all

This is for discussion ONAP VoLTE SDC call.
ONAP Meeting 5 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/137904496<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fj-252F137904496-26sa-3DD-26usd-3D2-26usg-3DAFQjCNHWLm-2DMNCNZh9JQ8TByZ7QBGA-5FnzQ&d=DwMFoQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY&m=dpXmFKa0QNbRyfMs1HSGB0g9k2po9_kyNEKoiBjciK4&s=ANIpcEWNUouIZ5UhxTtZwOWD9vQyzh_27KaxClpkiUI&e=>
Or iPhone one-tap (US Toll): +14086380968,137904496# or +16465588656,137904496#
Or Telephone:
 Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
 Meeting ID: 137 904 496
 International numbers available: 
https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fzoomconference-253Fm-253Dmi-2Dad1sMLWlXByAKLio5vDnd9JYqUR-5Fa-26sa-3DD-26usd-3D2-26usg-3DAFQjCNGUpQlMWM7Hx42afMT3U-2DkpQiPOMA&d=DwMFoQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY&m=dpXmFKa0QNbRyfMs1HSGB0g9k2po9_kyNEKoiBjciK4&s=BtclOBi4y-PNYyG2p-L3aOUkayC3MZYe2-MIRp51h7M&e=>

Thanks a lot

DENG Hui













_______________________________________________
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Reply via email to