Re: [onap-discuss] [SO][SDNC] About underlay vpn deployment

2017-11-03 Thread Ramu n
Hi Chenchuanyu,

For the Edge Rule between “service-instance” object and “configuration” object, 
relationship-data can’t contain configuration-type as shown in the below mail 
because configuration-type is not a key.
Can SO get the “configuration” object using “related-link” and check the 
“configuration-type” value to decide whether it is underlay or overlay 
configuration object.

Please check issue AAI-51 for more details.

Thanks,
Ramu N


***
 This e-mail and attachments contain confidential information from 
HUAWEI, which is intended only for the person or entity whose address is listed 
above. Any use of the information contained herein in any way (including, but 
not limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient's) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!

From: Ramu n
Sent: Friday, October 13, 2017 1:05 PM
To: dt5...@att.com; Chenchuanyu
Cc: huang.zhuo...@zte.com.cn; onap-discuss@lists.onap.org; 
onap-s...@lists.onap.org; Yang Xu (Yang, Fixed Network)
Subject: RE: [onap-discuss] [SO][SDNC] About underlay vpn deployment

Hi All,

After discussion with SO team(Chenchuanyu) SDNC can add the underlay/overlay 
network-instance record in AAI and bind(update relationship-data) with VoLTE 
E2E service-instance record.
During VoLTE service delete, UUI give service-instance-id to SO and SO can get 
the network-instance-ids form AAI(service instance’s relationship-data) and 
pass these service-instance-id & network-instance-id in the 
GENERIC-RESOURCE-API request’s service-information & network-information 
respectively.

NOTE: SDNC store underlay/overlay information in “Configuration” node in AAI. 
The relationship-data with service instance will be as shown below..

{
  "service-instance-id": "service-c",
  "service-instance-name": "example-service-instance-name-val-54177",
  "resource-version": "1507628208146",
  "relationship-list": {
"relationship": [
  {
"related-to": "configuration",
"related-link": "/network/configurations/configuration",
"relationship-data": [
  {
"relationship-key": "configurationId",
"relationship-value": "1"
  },
  {
"relationship-key": "configurationType",
"relationship-value": "overlay"
  }
]
  },
  {
"related-to": "configuration",
"related-link": "/network/configurations/configuration",
"relationship-data": [
  {
"relationship-key": "configurationId",
"relationship-value": "1"
  },
  {
"relationship-key": "configurationType",
"relationship-value": "underlay"
  }
]
  }
]
  }
}

Thanks,
Ramu N

***
 This e-mail and attachments contain confidential information from 
HUAWEI, which is intended only for the person or entity whose address is listed 
above. Any use of the information contained herein in any way (including, but 
not limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient's) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramu n
Sent: Thursday, October 12, 2017 1:34 PM
To: dt5...@att.com<mailto:dt5...@att.com>
Cc: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
onap-s...@lists.onap.org<mailto:onap-s...@lists.onap.org>
Subject: Re: [onap-discuss] [SO][SDNC] About underlay vpn deployment

Hi Dan,

Regarding the “network-object-path” or “service-object-path” returned by SDNC 
to SO, currently in most cases SDNC returns the network-data/service-data 
instance path from MDSAL data-store.
SO team wants SDNC add the network instance record in AAI and return the AAI 
resource path in the GENERIC-RESOURCE-API response. So that SO can bind the 
network instance with service instance.

Can you help me understand why current SDNC implementation return MDSAL 
data-store path to SO in the GENERIC-

Re: [onap-discuss] [SO][SDNC] About underlay vpn deployment

2017-10-13 Thread Ramu n
Hi All,

After discussion with SO team(Chenchuanyu) SDNC can add the underlay/overlay 
network-instance record in AAI and bind(update relationship-data) with VoLTE 
E2E service-instance record.
During VoLTE service delete, UUI give service-instance-id to SO and SO can get 
the network-instance-ids form AAI(service instance’s relationship-data) and 
pass these service-instance-id & network-instance-id in the 
GENERIC-RESOURCE-API request’s service-information & network-information 
respectively.

NOTE: SDNC store underlay/overlay information in “Configuration” node in AAI. 
The relationship-data with service instance will be as shown below..

{
  "service-instance-id": "service-c",
  "service-instance-name": "example-service-instance-name-val-54177",
  "resource-version": "1507628208146",
  "relationship-list": {
"relationship": [
  {
"related-to": "configuration",
"related-link": "/network/configurations/configuration",
"relationship-data": [
  {
"relationship-key": "configurationId",
"relationship-value": "1"
  },
  {
"relationship-key": "configurationType",
"relationship-value": "overlay"
  }
]
  },
  {
"related-to": "configuration",
"related-link": "/network/configurations/configuration",
"relationship-data": [
  {
"relationship-key": "configurationId",
"relationship-value": "1"
  },
  {
"relationship-key": "configurationType",
"relationship-value": "underlay"
  }
]
  }
]
  }
}

Thanks,
Ramu N

***
 This e-mail and attachments contain confidential information from 
HUAWEI, which is intended only for the person or entity whose address is listed 
above. Any use of the information contained herein in any way (including, but 
not limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient's) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramu n
Sent: Thursday, October 12, 2017 1:34 PM
To: dt5...@att.com
Cc: huang.zhuo...@zte.com.cn; onap-discuss@lists.onap.org; 
onap-s...@lists.onap.org
Subject: Re: [onap-discuss] [SO][SDNC] About underlay vpn deployment

Hi Dan,

Regarding the “network-object-path” or “service-object-path” returned by SDNC 
to SO, currently in most cases SDNC returns the network-data/service-data 
instance path from MDSAL data-store.
SO team wants SDNC add the network instance record in AAI and return the AAI 
resource path in the GENERIC-RESOURCE-API response. So that SO can bind the 
network instance with service instance.

Can you help me understand why current SDNC implementation return MDSAL 
data-store path to SO in the GENERIC-RESOURCE-API response and how it will be 
useful to SO ?

"GENERIC-RESOURCE-API:network-response-information": {
  "GENERIC-RESOURCE-API:instance-reference": {
"GENERIC-RESOURCE-API:instance-id": "",// 
underlay network-instance record id(created by SDNC)
"GENERIC-RESOURCE-API:object-path": "",   // 
restconf retrieval path to this particular object
  },
},
"GENERIC-RESOURCE-API:service-response-information": {
  "GENERIC-RESOURCE-API:instance-reference": {
"GENERIC-RESOURCE-API:instance-id": "",// same 
as service-instanceid passed by SO in the request, is it ok ?// hzy: ok!
"GENERIC-RESOURCE-API:object-path": "",   // can be 
empty ? //hzy: It seems ok by now.
  },
},


Thanks,
Ramu N

***
 This e-mail and attachments contain confidential information from 
HUAWEI, which is intended only for the person or entity whose address is listed 
above. Any use of the information contained herein in any way (including, but 
not limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient's) is prohibited. If you receive this 
e-mail in error, please notify the sender

Re: [onap-discuss] [SO][SDNC] About underlay vpn deployment

2017-10-12 Thread Ramu n
Hi Dan,

Regarding the “network-object-path” or “service-object-path” returned by SDNC 
to SO, currently in most cases SDNC returns the network-data/service-data 
instance path from MDSAL data-store.
SO team wants SDNC add the network instance record in AAI and return the AAI 
resource path in the GENERIC-RESOURCE-API response. So that SO can bind the 
network instance with service instance.

Can you help me understand why current SDNC implementation return MDSAL 
data-store path to SO in the GENERIC-RESOURCE-API response and how it will be 
useful to SO ?

"GENERIC-RESOURCE-API:network-response-information": {
  "GENERIC-RESOURCE-API:instance-reference": {
"GENERIC-RESOURCE-API:instance-id": "",// 
underlay network-instance record id(created by SDNC)
"GENERIC-RESOURCE-API:object-path": "",   // 
restconf retrieval path to this particular object
  },
},
"GENERIC-RESOURCE-API:service-response-information": {
  "GENERIC-RESOURCE-API:instance-reference": {
"GENERIC-RESOURCE-API:instance-id": "",// same 
as service-instanceid passed by SO in the request, is it ok ?// hzy: ok!
"GENERIC-RESOURCE-API:object-path": "",   // can be 
empty ? //hzy: It seems ok by now.
  },
},


Thanks,
Ramu N

***
 This e-mail and attachments contain confidential information from 
HUAWEI, which is intended only for the person or entity whose address is listed 
above. Any use of the information contained herein in any way (including, but 
not limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient's) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!

From: huang.zhuo...@zte.com.cn [mailto:huang.zhuo...@zte.com.cn]
Sent: Friday, September 29, 2017 6:04 PM
To: Ramu n
Cc: dt5...@att.com; onap-discuss@lists.onap.org; onap-s...@lists.onap.org
Subject: 答复: [onap-discuss] [SO][SDNC] About underlay vpn deployment


Hi Ramun,



My replay is in green, thank you!



Best regards!











黄卓垚huangzhuoyao



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


[cid:image001.gif@01D3435D.4BF73CB0]

[cid:image002.gif@01D3435D.4BF73CB0]
深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R Building, ZTE Corporation Hi-tech Road South,
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057
T: +86 755    F: +86 755 
M: +86 xxx
E: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
www.zte.com.cn<http://www.zte.com.cn/>


原始邮件
发件人: <ram...@huawei.com<mailto:ram...@huawei.com>>;
收件人:黄卓垚10112215; <dt5...@att.com<mailto:dt5...@att.com>>;
抄送人: <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; 
<onap-s...@lists.onap.org<mailto:onap-s...@lists.onap.org>>;
日 期 :2017年09月29日 15:21
主 题 :[onap-discuss] [SO][SDNC] About underlay vpn deployment


Hi Zhuoyao,

For the underlay “create” GENERIC-RESOURCE-API request from SO, the response 
from SDNC will be like below..

"GENERIC-RESOURCE-API:output": {
"GENERIC-RESOURCE-API:topology-response-common": {
  "GENERIC-RESOURCE-API:svc-request-id": "", // the request id from 
the request message
  "GENERIC-RESOURCE-API:response-code": "", // a success code or an 
defined error code
  "GENERIC-RESOURCE-API:response-message": ""  // message included for 
error code
  "GENERIC-RESOURCE-API:ack-final-indicator": ""  // Expected to be Y or N
},
"GENERIC-RESOURCE-API:network-response-information": {
  "GENERIC-RESOURCE-API:instance-reference": {
"GENERIC-RESOURCE-API:instance-id": "",// 
underlay network-instance record id(created by SDNC)
"GENERIC-RESOURCE-API:object-path": "",   // 
restconf retrieval path to this particular object
  },
},
"GENERIC-RESOURCE-API:service-response-information": {
  "GENERIC-RESOURCE-API:instance-reference": {
"GENERIC-RESOURCE-API:instance-id": "",// same 
as service-instanceid passed by SO in the request, is it ok ?// hzy: ok!
"GENERIC-RESOURCE-API:object-path": "",   // can be 
empty ? //hzy: It seems ok by now.
  },
},
  }

For “underlay” delete request, I think SO need to send this network-id. Please 
find the same r

[onap-discuss] [SO][SDNC] About underlay vpn deployment

2017-09-29 Thread Ramu n
Hi Zhuoyao,

For the underlay “create” GENERIC-RESOURCE-API request from SO, the response 
from SDNC will be like below..

"GENERIC-RESOURCE-API:output": {
"GENERIC-RESOURCE-API:topology-response-common": {
  "GENERIC-RESOURCE-API:svc-request-id": "", // the request id from 
the request message
  "GENERIC-RESOURCE-API:response-code": "", // a success code or an 
defined error code
  "GENERIC-RESOURCE-API:response-message": ""  // message included for 
error code
  "GENERIC-RESOURCE-API:ack-final-indicator": ""  // Expected to be Y or N
},
"GENERIC-RESOURCE-API:network-response-information": {
  "GENERIC-RESOURCE-API:instance-reference": {
"GENERIC-RESOURCE-API:instance-id": "",// 
underlay network-instance record id(created by SDNC)
"GENERIC-RESOURCE-API:object-path": "",   // 
restconf retrieval path to this particular object
  },
},
"GENERIC-RESOURCE-API:service-response-information": {
  "GENERIC-RESOURCE-API:instance-reference": {
"GENERIC-RESOURCE-API:instance-id": "",// same 
as service-instanceid passed by SO in the request, is it ok ?
"GENERIC-RESOURCE-API:object-path": "",   // can be 
empty ?
  },
},
  }

For “underlay” delete request, I think SO need to send this network-id. Please 
find the same request for below..

{
  "GENERIC-RESOURCE-API:input": {
"GENERIC-RESOURCE-API:sdnc-request-header": {
  "GENERIC-RESOURCE-API:svc-request-id": "",  // Uniquely 
generated by calling system
  "GENERIC-RESOURCE-API:svc-action": "",   // delete
  "GENERIC-RESOURCE-API:svc-notification-url": ""
},
"GENERIC-RESOURCE-API:request-information": {
  "GENERIC-RESOURCE-API:request-action": "",  // DeleteNetworkInstance
  "GENERIC-RESOURCE-API:notification-url": "",
  "GENERIC-RESOURCE-API:order-version": "",
  "GENERIC-RESOURCE-API:request-id": "",  // Uniquely generated by calling 
system
  "GENERIC-RESOURCE-API:order-number": "",
  "GENERIC-RESOURCE-API:source": "so"
},
"GENERIC-RESOURCE-API:service-information": {
  "GENERIC-RESOURCE-API:global-customer-id": "", // need for put of 
data to AnAI (SO provides)
  "GENERIC-RESOURCE-API:subscription-service-type": "",   // reference to 
a subscription-service-type
  "GENERIC-RESOURCE-API:service-id": "",
   // servive-instance-id from SO
  "GENERIC-RESOURCE-API:service-instance-id": "", // 
reference to a service-instance-id
  "GENERIC-RESOURCE-API:ecomp-model-information": {
"GENERIC-RESOURCE-API:model-customization-uuid": "",
"GENERIC-RESOURCE-API:model-invariant-uuid": "",
"GENERIC-RESOURCE-API:model-name": "",
"GENERIC-RESOURCE-API:model-uuid": "",
"GENERIC-RESOURCE-API:model-version": ""
  },
  "GENERIC-RESOURCE-API:subscriber-name": ""
},
"GENERIC-RESOURCE-API:network-information": {
  "GENERIC-RESOURCE-API:network-id": "",  // network-instance 
id provided by SDNC in “create” response
  "GENERIC-RESOURCE-API:network-type": "",
  "GENERIC-RESOURCE-API:ecomp-model-information": {
"GENERIC-RESOURCE-API:model-customization-uuid": "",
"GENERIC-RESOURCE-API:model-invariant-uuid": "",
"GENERIC-RESOURCE-API:model-name": "",
"GENERIC-RESOURCE-API:model-uuid": "",
"GENERIC-RESOURCE-API:model-version": ""
  },
},
"GENERIC-RESOURCE-API:network-request-input": {
  "GENERIC-RESOURCE-API:network-name": "",
  "GENERIC-RESOURCE-API:region-identifier": {
"GENERIC-RESOURCE-API:tenant": "",
"GENERIC-RESOURCE-API:aic-cloud-region": "",
"GENERIC-RESOURCE-API:aic-clli": "",
  },
  "GENERIC-RESOURCE-API:network-input-parameters": {// Does User 
provide any input for “delete” operation ?
"GENERIC-RESOURCE-API:param": [
  {
  }
   ]
 }
}

Can you provide more details on highlighted parameters.

Thanks,
Ramu N

***
 This e-mail and attachments contain confidential information from 
HUAWEI, which is intended only for the person or entity whose address is listed 
above. Any use of the information contained herein in any way (including, but 
not limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient's) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss