OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC

 View Only

RE: [Sent to NSN.COM] RE: [tosca] Groups - TOSCA-NFV-Profile v1.0 ToC proposal.zip uploaded

  • 1.  RE: [Sent to NSN.COM] RE: [tosca] Groups - TOSCA-NFV-Profile v1.0 ToC proposal.zip uploaded

    Posted 06-30-2016 22:29




    Forwarding the email to the Tosca list since Thinh believes there may be email issues with the nsn.com domain.
     
    Chris
     


    From: Nguyenphu, Thinh (Nokia - US/Irving) [mailto:thinh.nguyenphu@nokia.com]

    Sent: Thursday, June 30, 2016 1:42 PM
    To: John Crandall <jcrandal@Brocade.COM>; Chris Lauwers <lauwers@ubicity.com>; tosca@lists.oasis-open.org
    Subject: RE: [Sent to NSN.COM] RE: [tosca] Groups - TOSCA-NFV-Profile v1.0 ToC proposal.zip uploaded


     
    Hi Chris and John,
     
    I am responding to Chris and John in one email.
     
    @Chris’ email:
    I do like your “Hello World” example and build from basic example.  Section 3 and section 5 are very much related to give the reader the understanding of TOSCA NFV Profile would layout and works. Perhaps, section
    5 should move up before going into normative part of profile Simple YAML in Section 4. Section 4 (TOSCA Modeling Principle and Data Model) is important to begin profile the Simple YAML for NFV.  This section is important foundation for defining VNFD and NSD. 

     
    @John’s email:
    The proposal is not to re-write the document. The proposal is to re-factor the document to fulfill the gap such as section 4, and a separation of NSD and VNFD. For the missing items, they are VnfDeploymentFlavour,
    VnfElementGroup, Vnfindicator, VduCpd, VnfExternalCpd, VnfVld, NsDeploymentFlavour, etc.
     
    Thinh
     
     


    From: John Crandall [ mailto:jcrandal@Brocade.COM ]

    Sent: Thursday, June 30, 2016 10:21 AM
    To: Chris Lauwers < lauwers@ubicity.com >; Nguyenphu, Thinh (Nokia - US/Irving) < thinh.nguyenphu@nokia.com >;
    tosca@lists.oasis-open.org
    Subject: [Sent to NSN.COM] RE: [tosca] Groups - TOSCA-NFV-Profile v1.0 ToC proposal.zip uploaded


     
    Hi all,
     
    I am generally okay reorganizing the sections and providing more info, though I think this will be more work and take more time than some expect.
     
    But I am concerned that we might be starting completely over on technical content that has already been implemented. I would like to see a more pragmatic approach where the changes are more iterative on content that already exists (and has been implemented).
    For content that is completely new (green field), we should try to introduce it as quickly as possible.
     
    John
     
     


    From: Chris Lauwers
    Sent: Monday, June 27, 2016 6:47 PM
    To: Thinh Nguyenphu;tosca@lists.oasis-open.org
    Subject: RE: [tosca] Groups - TOSCA-NFV-Profile v1.0 ToC proposal.zip uploaded

     
     
    I very much like the direction of this new outline. It takes a big step towards making the document more readable, and it also does a great job in better aligning the Tosca NFV Profile with the abstractions defined
    by ETSI NFV.
     
    As a potential additional improvement, I would recommend that we go even further and adopt an approach similar to what was done in the Simple Profile for YAML spec. As you know, in that document we built up Tosca
    concepts by starting from a simple “Hello World” example and gradually adding additional functionality. I believe the NFV Profile document could benefit from a similar build-up.

     
    Specifically, I believe we could use Section 5 in Thinh’s outline for this purpose:
     
    -          
    We would first introduce network service concepts:

    o   
    Starting with a very simple example consisting of a single VNF with two external connection points

    o   
    Then add a second VNF with a virtual link (and internal connection points) connecting these VNFs

    o   
    Potentially adding physical network functions

    o   
    Adding forwarding graph(s)

    o   
    And any other concepts that might need to be introduced
    -          
    Then we could move towards VNF descriptor templates:

    o   
    Mapping a VNF onto just one single VDU

    o   
    Adding additional VDUs with an internal virtual link

    o   
    Specifying how these VDUs use virtual compute and virtual storage

    o   
    Etc.
     
    This would make Section 5 the “meat” of the document where most if not all of the NFV concepts are explained and described using TOSCA.
     
    Sections 6 and 7 would then introduce the normative type definitions specified by the document (as shown in Thinh’s outline).

     
    Chris
     
     
    From: tosca@lists.oasis-open.org [ mailto:tosca@lists.oasis-open.org ]
    On Behalf Of Thinh Nguyenphu
    Sent: Monday, June 27, 2016 6:37 AM
    To: tosca@lists.oasis-open.org
    Subject: [tosca] Groups - TOSCA-NFV-Profile v1.0 ToC proposal.zip uploaded
     
    Submitter's message
    I uploaded an input contribution as a proposal change to the TOSCA-NFV-Profile v1.0 csd03 ToC.


    This contribution is targeted for today, June 27 NFV/SDN adhoc call, agenda item 1 & 2.

    Regards,
    Thinh Nguyenphu
    -- Thinh Nguyenphu




    Document Name :

    TOSCA-NFV-Profile v1.0 ToC proposal.zip




    Description
    Proposal change ToC of TOSCA-NFV-Profile v1.0 csd03.
    Download
    Latest Revision
    Public
    Download Link




    Submitter : Thinh Nguyenphu
    Group : OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
    Folder : Working Documents
    Date submitted : 2016-06-27 06:36:49