Hi Michael,

Please see my inline response.

Thanks,
Huabing
Original Message
*From:* Lando,Michael;
*To:*zhaohuabing10201488;
*Cc:*SHADMI, DAVID; Kapeluto, Zahi; [email protected];
[email protected];
*Date:* 2017-07-29 19:36:34
*Subject:RE: Re:[onap-discuss] 答复: 答复: What Do You Need From The July
Developers Event?*

Hi,

We started reviewing all the date you provided and we have a couple of
questions:

1.       The CSAR you provided represent SERVICES not VF? Can you provide
us with the VF TOSCA used in creating the base blocks HSS/vMME etc?

Zhao: they're in the attachment. However, you might don't need the VNF
package to validate the VoLTE service within SDC because all the VNF TOSCA
node type definitions are included in the vIMS_NS and vEPC_NS Packages.

2.       Where was this orchestred and where is the compute nod in your
TOSCA?

Zhao: They're used in OPEN-O Mecury release. If I  understand correctly,
Copmute node in NFV is tosca.nodes.nfv.VDU

3.       In you model what is mapped to a VM?

Zhao:  My understanding is that the mapping of VNF to VM is handled by VNFM
via VDU, which is not exposed to NS and service level.

4.       How is this model mapped to open stack?

Zhao: My understanding is that the mapping of VNF to VM(Whether the VM is
Openstack or not) is handled by VNFM.

5.       Is VNF one VM?

 Zhao:My understanding is that the mapping of VNF to VM(Whether the VM is
Openstack or not) is handled by VNFM. NS Model has no restriction to that.


Regurding the GAPS:

1.       Please provide a scenario where you need:

a.       metadata setting?

b.      capability setting

c.       requirement setting

d.      attribute setting

e.      artifact setting

      zhao: The questions are can we set these parts of a TOSCA model in
SDC or not.



*BR, *



*Michael Lando*

Opensource & Frontend Team Lead, SDC

AT&T Network Application Development · NetCom

Tel Aviv | Tampa | Atlanta | New Jersey |Chicago

···········································································

*Office*: +972 (3) 5451487 <+972%203-545-1487>

*Mobile*: +972 (54) 7833603 <+972%2054-783-3603>

*e-mail*: *[email protected] <[email protected]>*





*From:* [email protected] [mailto:[email protected]]
*Sent:* Wednesday, July 26, 2017 6:01 PM
*To:* [email protected]; Lando,Michael <[email protected]>;
[email protected]
*Subject:* Re:[onap-discuss] 答复: 答复: What Do You Need From The July
Developers Event?



Hi Folks,

Attached is the slides deck I presented at today's meeting.

We'd like to identify the gaps before the functional freeze milestone, here
are the action items and date.

·          Design an example VoLTE model with SDC and export  the model as
CSAR (use OPEN-O VoLTE CSARs as reference) – this week

 Reference CSAR Packages are attached in this mail.

·          Analyze the gaps for VoLTE model design supporting – next Monday

·          Add the work items to Amsterdam Release to address all the
identified gaps.  -August 3.

Thanks,

Huabing





Original Mail

*Sender: * <[email protected]>;

*To: * <[email protected]>; <[email protected]>;

*Date: *2017/07/26 17:23

*Subject: [onap-discuss] * *答复:  **答复:  What Do You Need From The July
Developers Event?*



Hi Micheal,



TSC and the Linux Foundation suggested organizing thematic discussion on
SDC again tonight, because you didn’t participate in yesterday's virtual
meeting.

The meeting time is 1:10 PM for SDC questions topic. Hopefully, you can
participate the meeting today.



Best Regards,

Yan

*发件人**:* [email protected] [
mailto:[email protected]
<[email protected]>] *代表* 杨艳
*发送时间**:* 2017年7月21日 18:32
*收件人**:* [email protected]; [email protected];
[email protected]
*主**题**:* [onap-discuss] 答复: What Do You Need From The July Developers
Event?



Hi Micheal,



VF-C team has added a topic about the SDC questions at next week’s virtual
development event, hope your team can join the topic.

Following are the topic description and we will add more details about the
issues we want to discuss. Thanks.

Description:The output of SDC will be distributed to multiple modules, SO
,VF-C, Policy, etc. Want to know more details of SDC, such as how to
subscribe topic, how to get template or csar package, the notification
example, etc.







Best Regards,

Yan



*发件人**:* [email protected] [
mailto:[email protected]
<[email protected]>] *代表* Kenny Paul
*发送时间**:* 2017年7月18日 6:18
*收件人**:* [email protected]
*抄送**:* onap-tsc
*主**题**:* [onap-discuss] What Do You Need From The July Developers Event?



The July Virtual Developers Event is next week and your contributions are
what will drive all of these sessions.

As Phil Robb mentioned at the close of the PTL call this morning, *we are
looking to the community to suggest topics for discussion* which we
will use to build the agenda from.  Ideally these are areas where you need
a deeper understanding of in order to make progress, or deep-dive
information sharing in a particular area you wish to provide.  It is
critically important to extract a list of questions/decisions/agreements
that each project needs to close on so that they can successfully execute
their development cycle for Amsterdam.

*The following wiki page has been created for this purpose: DISCUSSION
TOPICS / QUESTIONS
<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D8232264&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=RynqW2q8pkELnIhPvHEWeQ&m=p-EFRhtWYSVpYYg0IynmhiVZ9xuRo2pFLs-tjoi1sPg&s=fziSTDdpVI6FmrHYz9m9RnmNzM2eNnasmTld-IFPH7E&e=>*

To to add a new topic please provide your project name and topic using the
template provided on the wiki page. If there is a topic that you would like
discussed, but you do not feel that you can lead it, please add the topic
and indicate that you are "Interested in Attending", then indicate TBD as
the "Topic Leader”.



For any existing topic(s) you would like to lead and/or attend simply add
your name to the list as appropriate.



The page has been populated with a few topics based upon input we have
already received.



Thank you in advance for your contributions and participation.



Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
[email protected]
510.766.5945
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to