Hi, Subhash
The vim-id in esr-vnfm is composed by {cloud-owner}_{cloud-region-id}, it
should be input by ESR portal user. For Amsterdam Release, we didn't add the
edge between the vim-id in esr-vnfm with anyother things. The id in
cloud-region/esr-system-info is a automatically gennerated uuid.
If you want to get the VIM infomation through esr-vnfm. First, you need query
the esr-vnfm to get the vim-id, and parse it into cloud-owner and
cloud-region-id. Second, query the cloud-region
/aai/v11/cloud-regions/cloud-region/<cloud-owner>/<cloud-region-id>. Note here,
at least in Amsterdam release, you should not try to query the esr-system-info
only.
Thanks,
LiZi
原始邮件
发件人： <subhash.kumar.si...@huawei.com>;
收件人：李滋00164331; <jf2...@att.com>;
抄送人： <onap-discuss@lists.onap.org>; <kanagaraj.manic...@huawei.com>;
<victor....@huawei.com>;
日 期 ：2017年10月11日 13:43
主 题 ：RE: Not able to create relationship between esr-vnfmandesr-system-info
Hello Lizi,
If I understand correctly then vim id will be used to refer esr-system-info
(VIM) stored at
/aai/v11/cloud-regions/cloud-region/<cloud-owner>/<cloud-id>/esr-system-info-list/esr-system-info/<vim-id>.
I think it would be a good approach, if we create relationship from esr-vnfm to
esr-system-info instead of having vim-id as attribute.
Please let me know your thoughts.
--
Regards,
Subhash Kumar Singh
***************************************************************************************
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**************************************************************************************
***************************************************************************************
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whoseaddress 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, pleasenotify the sender by phone or email immediately and
delete it!
***************************************************************************************
From: li.z...@zte.com.cn [mailto:li.z...@zte.com.cn]
Sent: Wednesday, October 11, 2017 7:10 AM
To: jf2...@att.com
Cc: Subhash Kumar Singh <subhash.kumar.si...@huawei.com>;
onap-discuss@lists.onap.org; Kanagaraj Manickam <kanagaraj.manic...@huawei.com>
Subject: RE: Not able to create relationship between esr-vnfm
andesr-system-info
Hi Subhash, Jimmy:
Yes, for cloud-region and external system item, esr-system-info is wrapped in
cloud-region/esr-vnfm/esr-ems .etc. Usually, I put esr-vnfm together with
esr-system-info, and not need to create the relationship. And also
esr-system-info should not exist alone. Here is an example to PUT esr-vnfm.
PUT
https://ip:8443/aai/v11/external-system/esr-vnfm-list/esr-vnfm/e6445387-faa3-4996-8ddc-250c808a86
BODY:
{
"vnfm-id": "e6445387-faa3-4996-8ddc-250c808a86",
"vim-id": "dfadfafda",
"certificate-url": "aaaa",
"esr-system-info-list": {
"esr-system-info": [
{
"esr-system-info-id": "2e3a1a6f-a1a5-406a-a86a-4788506f47",
"system-name": "vnfmtest1",
"type": "Tacker",
"vendor": "ZTE",
"version": "v2",
"service-url": "http://10.10.10.11";,
"user-name": "admin",
"password": "admin",
"system-type": "VNFM"
}
]
}
}
原始邮件
发件人： <jf2...@att.com>;
收件人： <subhash.kumar.si...@huawei.com>; <onap-discuss@lists.onap.org>;
抄送人： <kanagaraj.manic...@huawei.com>;李滋00164331;
日 期 ：2017年10月10日 22:38
主 题 ：RE: Not able to create relationship between esr-vnfm andesr-system-info
Hi, Subhash,
Please notice that both cloud-region and esr-vnfm can contain the
esr-system-info-list.
Maybe LiZi can comment on why it’s necessary to contain them this way, I don’t
fully understand it – possibly the esr-system-info can exist without a cloud
region? So, if you want to relate esr-system-info to esr-vnfm, you need to
add the esr-system-info as a child of the esr-vnfm.
Thanks,
jimmy
From: Subhash Kumar Singh [mailto:subhash.kumar.si...@huawei.com]
Sent: Tuesday, October 10, 2017 10:05 AM
To: FORSYTH, JAMES <jf2...@att.com>; onap-discuss <onap-discuss@lists.onap.org>
Cc: Kanagaraj Manickam <kanagaraj.manic...@huawei.com>
Subject: Not able to create relationship between esr-vnfm and esr-system-info
Hello Jimmy,
I am trying to create a relationship between esr-vnfm and esr-system-info node,
but it throws error message on adding this relationship entry.
Following are the request details:
Request :
PUT:
https://<ip>:8443/aai/v11/external-system/esr-vnfm-list/esr-vnfm/htipl12-VnfmId-val-699
{
"vnfm-id": "htipl12-VnfmId-val-699",
"resource-version": "1507274845927",
"relationship-list": {
"relationship": [
{
"related-to": "esr-system-info",
"relationship-data": [
{
"relationship-key": "cloud-region.cloud-owner",
"relationship-value": "htipl103-cloud-owner-val-18494"
},
{
"relationship-key": "cloud-region.cloud-region-id",
"relationship-value":
"htipl103-cloud-region-id-val-8824"
},
{
"relationship-key":
"esr-system-info.esr-system-info-id",
"relationship-value":
"example-esr-system-info-id-val-35409"
}
]
}
]
}
}
Response:
{
"requestError": {
"serviceException": {
"messageId": "SVC3000",
"text": "Invalid input performing %1 on %2 (msg=%3) (ec=%4)",
"variables": [
"PUT",
"external-system/esr-vnfm-list/esr-vnfm/htipl12-VnfmId-val-699",
"Cannot create a nested/containment edge via relationship",
"ERR.5.4.6145"
]
}
}
}
Could you please let me know how to draw this relationship correctly.
--
Regards,
Subhash Kumar Singh
***************************************************************************************
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**************************************************************************************
***************************************************************************************
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whoseaddress 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, pleasenotify 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
