Hi Chuanyu, See my comments inline.
Thanks, David From: Chenchuanyu [mailto:[email protected]] Sent: Tuesday, September 05, 2017 10:57 PM To: SHADMI, DAVID <[email protected]>; [email protected] Cc: LEVY, DONALD E <[email protected]>; [email protected]; [email protected] Subject: 答复: [onap-discuss] Invitation: SDC & VFC integration meeting @ Fri2017-09-01 9pm - Sat 2017-09-02 12am (CST) ([email protected]) Hi，David, Yuanxing, I have questions as below, can you give me any support:. 1. Import and certify the underlayvpn.yml as VL Q:How can I import the underlayvpn.yml as a VL? I have not found that entry, only import VFC found. [David] Use Import VFC and select the Virtual Link category from the list. [cid:[email protected]] 2. Create vIMS_NS VF as new AllottedResources (Network Service subcategory) Q:I can not find a VF category type of AllottedResources yet ,is it a new supported type? Or I need to create new Resource Category and subcategory using Admin user? [David] You need to create the “Network Service” as subcategory of AllottedResource. This can be done using SDC Admin workspace. [cid:[email protected]] 3. Define all properties as inputs (had to do that for the properties to be visible when generating the VoLTE service TOSCA) Q: I think for providing_service_uuid and providing_service_invariant_uuid, these two properties could not be defined as inputs for voLTE, User who deploy voLTE will not concern the uuid/invariant_uuid of vIMS/vEPC service. What will be better: when we design the VFC, we can set the default value for providing_service_uuid and providing_service_invariant_uuid, This is design time. Desinger who design voLTE service could bind the uuid information , but not user who deploy the voLTE service . Let me know if any suggestions. [David] Providing the vIMS/vEPC UUIDs information happen during the vIMS_NS and vEPC_NS design. Thanks Chuanyu Chen. 发件人: [email protected]<mailto:[email protected]> [mailto:[email protected]] 代表 SHADMI, DAVID 发送时间: 2017年9月6日 2:52 收件人: [email protected]<mailto:[email protected]> 抄送: LEVY, DONALD E; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> 主题: Re: [onap-discuss] Invitation: SDC & VFC integration meeting @ Fri2017-09-01 9pm - Sat 2017-09-02 12am (CST) ([email protected]<mailto:[email protected]>) Hi, I manually added the two categories using SDC Admin role. My suggestion is to use “Network Service” and “E2E Service”, as it generic and would allow SO to implement a generic support for these two type of services. If there is an agreement on these two categories, we would include them in the predefined list of service categories. Thanks, David From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: Monday, September 04, 2017 9:32 PM To: SHADMI, DAVID <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; LEVY, DONALD E <[email protected]<mailto:[email protected]>>; LANDO, MICHAEL <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: 答复: Re: [onap-discuss] Invitation: SDC & VFC integration meeting @ Fri2017-09-01 9pm - Sat 2017-09-02 12am (CST) ([email protected]<mailto:[email protected]>) Hi David, Thanks for your presentation which was really helpful. I imported your nsd.yml and underlayvpn.yml in my sdc portal and it works. After that I succeed to create two VFs(vIMS and vEPC). Unfortunately, I can't find two category types(Network Service and E2E Service). I use VolteNS instead. Does it make difference? BTW, my sdc version is:1.1-STAGING-latest． BR Feng yuanxing 原始邮件 发件人： <[email protected]<mailto:[email protected]>>; 收件人： <[email protected]<mailto:[email protected]>>; <[email protected]<mailto:[email protected]>>; <[email protected]<mailto:[email protected]>>; <[email protected]<mailto:[email protected]>>;张茂鹏10030173; <[email protected]<mailto:[email protected]>>; <[email protected]<mailto:[email protected]>>; <[email protected]<mailto:[email protected]>>; 日 期 ：2017年09月02日 07:31 主 题 ：Re: [onap-discuss] Invitation: SDC & VFC integration meeting @ Fri2017-09-01 9pm - Sat 2017-09-02 12am (CST) ([email protected]<mailto:[email protected]>) Hello All, Here is the summary of the call we had today: 1. CSAR format – I update the slide we discussed on Monday based on today’s call 2. VoLTE E2E service a. Enclosed please find the NSD and underlayvpn node type definition I used in the call. b. Use the following steps to create the VoLTE E2E service: i. Import and certify the NSD.yml as VFC ii. Import and certify the underlayvpn.yml as VL iii. Create vIMS and vEPC services to get the uuid and invariantUUID information needed for the vIMS and vEPC NSs iv. Create vIMS_NS VF as new AllottedResources (Network Service subcategory) 1. Add the NSD VFC and populate the properties 2. Define all properties as inputs (had to do that for the properties to be visible when generating the VoLTE service TOSCA) v. Create vEPC_NS VF – same steps as in #4 vi. Create the VoLTE E2E service with vIMS, vEPC, and underlayvpn Thanks, David -----Original Appointment----- From: ONAP [mailto:[email protected]] Sent: Monday, August 28, 2017 9:25 PM To: ONAP; LEVY, DONALD E; LANDO, MICHAEL; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: [onap-discuss] Invitation: SDC & VFC integration meeting @ Fri 2017-09-01 9pm - Sat 2017-09-02 12am (CST) ([email protected]<mailto:[email protected]>) When: Friday, September 01, 2017 8:00 AM-11:00 AM (UTC-06:00) Central Time (US & Canada). Where: https://zoom.us/j/648493837<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_648493837&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=L_AEkSgBxO3aiW8qFSg739m8Guz__acKeI710MOLmOM&s=DUQJ2lzkhomDVFq0himDg53r5S9fyjEBESeN2wYr7cM&e=> more details »<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_event-3Faction-3DVIEW-26eid-3DNGNlZ2VraXVjdnZ2NzRyMWc5c2Q1c3Y0azMgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn-26tok-3DNTIjZjI2dHU2dHFlcW91MWxpOThuN3V2cTY2ZDBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbWUxNjE5OTg2ZDU0YmJiZmQzYTIwMDYyOTY3ZjU2ZjY0MmY3MTQ2Mjc-26ctz-3DAsia_Shanghai-26hl-3Den&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=iHXJbxD69wMgySs8O7RASXE7XUQc3IemR_F9OhvWG08&s=jQhKZdmVPyFLbbxujlnzW2MLA-7P57ODTLp7fZaiMfs&e=> SDC & VFC integration meeting When Fri 2017-09-01 9pm – Sat 2017-09-02 12am China Time - Beijing Where https://zoom.us/j/648493837<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_648493837&d=DwQFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=iHXJbxD69wMgySs8O7RASXE7XUQc3IemR_F9OhvWG08&s=CgeDN7aOoxCxkNiqVlisJQ2JlU-zmCw5VZH43j2Xsag&e=> (map<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fj-252F648493837-26sa-3DD-26usd-3D2-26usg-3DAFQjCNGZzqQxKWK1Xr7EgQkjrmclAXF42w&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=iHXJbxD69wMgySs8O7RASXE7XUQc3IemR_F9OhvWG08&s=1aC1B3mAxgw8zmKJvphx4gW8MzGm4tPJ-I3Yv-aX6Rw&e=>) Calendar [email protected]<mailto:[email protected]> Who • Huabing Zhao - creator • [email protected]<mailto:[email protected]> • [email protected]<mailto:[email protected]> • [email protected]<mailto:[email protected]> • [email protected]<mailto:[email protected]> • [email protected]<mailto:[email protected]> • [email protected]<mailto:[email protected]> • [email protected]<mailto:[email protected]> Hi there, ZTE Open Source is inviting you to a scheduled Zoom meeting. Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/648493837<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fj-252F648493837-26sa-3DD-26usd-3D2-26usg-3DAFQjCNGZzqQxKWK1Xr7EgQkjrmclAXF42w&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=iHXJbxD69wMgySs8O7RASXE7XUQc3IemR_F9OhvWG08&s=1aC1B3mAxgw8zmKJvphx4gW8MzGm4tPJ-I3Yv-aX6Rw&e=> Or iPhone one-tap : US: +14086380968,,648493837# or +16468769923,,648493837# Or Telephone： Dial(for higher quality, dial a number based on your current location)： US: +1 408 638 0968 or +1 646 876 9923 Meeting ID: 648 493 837 International numbers available: https://zoom.us/zoomconference?m=1O70GAs-yNBBPJICgPTuoy42OL0_AxkM<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fzoomconference-253Fm-253D1O70GAs-2DyNBBPJICgPTuoy42OL0-5FAxkM-26sa-3DD-26usd-3D2-26usg-3DAFQjCNG7uI4V3XxV7x3T22cgAC2rYPGdFA&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=iHXJbxD69wMgySs8O7RASXE7XUQc3IemR_F9OhvWG08&s=a1msciRhJM2zlu4dLUFo19nvIyf28U2dhHwYMS-O2YU&e=> Going? Yes<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_event-3Faction-3DRESPOND-26eid-3DNGNlZ2VraXVjdnZ2NzRyMWc5c2Q1c3Y0azMgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn-26rst-3D1-26tok-3DNTIjZjI2dHU2dHFlcW91MWxpOThuN3V2cTY2ZDBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbWUxNjE5OTg2ZDU0YmJiZmQzYTIwMDYyOTY3ZjU2ZjY0MmY3MTQ2Mjc-26ctz-3DAsia_Shanghai-26hl-3Den&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=iHXJbxD69wMgySs8O7RASXE7XUQc3IemR_F9OhvWG08&s=vtEGQMgGkKjmwuJO7dih3jXxwpN808wdEjLXzN9QNfQ&e=> - Maybe<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_event-3Faction-3DRESPOND-26eid-3DNGNlZ2VraXVjdnZ2NzRyMWc5c2Q1c3Y0azMgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn-26rst-3D3-26tok-3DNTIjZjI2dHU2dHFlcW91MWxpOThuN3V2cTY2ZDBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbWUxNjE5OTg2ZDU0YmJiZmQzYTIwMDYyOTY3ZjU2ZjY0MmY3MTQ2Mjc-26ctz-3DAsia_Shanghai-26hl-3Den&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=iHXJbxD69wMgySs8O7RASXE7XUQc3IemR_F9OhvWG08&s=T7WiOswpa3zwkpbK_XBgGbBQOpVL-JzJ-f3Z_wdTRH8&e=> - No<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_event-3Faction-3DRESPOND-26eid-3DNGNlZ2VraXVjdnZ2NzRyMWc5c2Q1c3Y0azMgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn-26rst-3D2-26tok-3DNTIjZjI2dHU2dHFlcW91MWxpOThuN3V2cTY2ZDBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbWUxNjE5OTg2ZDU0YmJiZmQzYTIwMDYyOTY3ZjU2ZjY0MmY3MTQ2Mjc-26ctz-3DAsia_Shanghai-26hl-3Den&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=iHXJbxD69wMgySs8O7RASXE7XUQc3IemR_F9OhvWG08&s=rK4yvWQwzwDkqBRPtKLmrNieVv9idrcTQa9lttRAsUA&e=> more options »<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_event-3Faction-3DVIEW-26eid-3DNGNlZ2VraXVjdnZ2NzRyMWc5c2Q1c3Y0azMgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn-26tok-3DNTIjZjI2dHU2dHFlcW91MWxpOThuN3V2cTY2ZDBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbWUxNjE5OTg2ZDU0YmJiZmQzYTIwMDYyOTY3ZjU2ZjY0MmY3MTQ2Mjc-26ctz-3DAsia_Shanghai-26hl-3Den&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=iHXJbxD69wMgySs8O7RASXE7XUQc3IemR_F9OhvWG08&s=jQhKZdmVPyFLbbxujlnzW2MLA-7P57ODTLp7fZaiMfs&e=> Invitation from Google Calendar<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=iHXJbxD69wMgySs8O7RASXE7XUQc3IemR_F9OhvWG08&s=VKYgv68M8_Ed_iaB8JvlwLAwkkdfFTe2ZmbYl4GdYbA&e=> You are receiving this courtesy email at the account [email protected]<mailto:[email protected]> because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_&d=DwQFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=iHXJbxD69wMgySs8O7RASXE7XUQc3IemR_F9OhvWG08&s=VKYgv68M8_Ed_iaB8JvlwLAwkkdfFTe2ZmbYl4GdYbA&e=> and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn More<https://urldefense.proofpoint.com/v2/url?u=https-3A__support.google.com_calendar_answer_37135-23forwarding&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=iHXJbxD69wMgySs8O7RASXE7XUQc3IemR_F9OhvWG08&s=InTjsqSo8wc2Y0jX3fc2tX-2WazcXf6is4-u5hD1Ups&e=>. << File: invite.ics >> << File: ATT00001.txt >>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
