Based On tosca-nfv-profile-wd05-rev03.

Download : https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/62125/tosca-nfv-v1.0-wd05-rev03.doc

Based on SOL001 v0.6.0

Download: https://docbox.etsi.org/ISG/NFV/Open/Drafts/SOL001_TOSCA_desc/NFV-SOL001v060.zip

  • No labels

13 Comments

  1. Alexander Vul

    VIctor,


    I believe the intent is to use the SOL001 spec to align the model, not TOSCA NFV Profile. Thoughts?


    Alex Vul

  2. shitao li

    Alex


    yes. The intention should be tosca-nfv-profile + SOL001, some of the type definitions as used in SOL001 are referenced from tosca-nfv-profile. 

  3. Alexander Vul

    Shitao, 

    We need to merge in the HPA changes as well. I have  a set of candidate changes or the NFV Profile spec. Should we use these, or update the information directly on the Wiki...


    Thanks,


    Alex


  4. shitao li

    Alex

    Sure, HPA changes are needed.

  5. Andrei Kojukhov

    So the intent is to use the SOL001 as superset of NFV profile that already includes the HPA feature.

  6. Jessie S Jewitt

    I don't understand why we are not using the SOL001 mapping to DM as defined here, instead of TOSCA NFV Profile:

    Mapping IM (clean version) to SOL001 (data model).

    It is more comprehensive→

    • Includes HPA
    • Contains attributes that aren't in TOSCA NFV Profile (especially for the Vnf, VirtualCompute, Cpd...)
    • Contains the datatypes that are mentioned in TOSCA mappings in this section, but are missing in OASIS spec and data type artifacts, such as VduProfile, LogicalNodeData, etc. SOL001 has a richer set of datatypes.

  7. Andrei Kojukhov

    Interfaces should be added as well.

  8. Thinh Nguyenphu

    I will add the tosca.intefacesnfv.nfv.lifecycle.Nfv types.

  9. Jessie S Jewitt

    I see that somebody added on this page that the DM definitions are now also "based on SOL001". Does that mean we are using both specs, and not just the OASIS spec?

  10. Alexander Vul

    Added HPA changes and fixed grammar mistakes...

  11. Weitao Gao

    I think our DM should also also algin with ONAP R2 IM,at least,DM should be the superset of IM.

    ONAP R2 IM Clean Page:Design Time Model Clean Version

  12. Andrei Kojukhov

    ONAP R2 IM that is in general based on IFA011,however has some extensions that were communicated to ETSI NFV and currently being considered.

    For the mean time I would not implement these extensions before ETSI decision and we as a community agree on them.

  13. yuanxing feng

    I see all those types are now based on SOL001 V0.6.0. Does that mean ONAP R2 will follow SOL001 with 1:1 mapping?  

    Actually we have discussed and agreed on some extensions and modifications in IM. Meanwhile, I think we ought to think about use cases to be implemented in R2 as well.