1 / 23

Mapping between NFV model and TOSCA

Mapping between NFV model and TOSCA. Shitao li (huawei) Matt Rutkowski (IBM) John Crandall (Brocade). NFV model. Definition of VDU in NFV003. The NFV model of VDU and VNFD are fully aligned with TOSCA composition concept. Vdu concept. From the infrastructure point of view. VDU. VM.

countsm
Download Presentation

Mapping between NFV model and TOSCA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mapping between NFV model and TOSCA Shitao li (huawei) Matt Rutkowski (IBM) John Crandall (Brocade)

  2. NFV model Definition of VDU in NFV003 The NFV model of VDU and VNFD are fully aligned with TOSCA composition concept.

  3. Vdu concept From the infrastructure point of view VDU VM Virtual storage = CP +image +image CP

  4. Vdu concept In IFA model In tosca VDU VM Virtual storage CP +image +image CP In UML model, this means aggregation (VduCpd, VirtualConputeDesc and VirtualStorageDesc belong to VDU) In TOSCA, node templates are the components of a service template. This is a usual way in TOSCA to describe composition.

  5. TOSCA normative node definition Virtual container (VM) Virtual storage • AttachesTo ConnectsTo Compute Node ObjectStorage BlockStorage tosca.capabilities.compute.Container: derived_from:tosca.capabilities.Compute size volume_id snapshot_id name size maxsize num_cpus cpu_frequency disk_size mem_size capabilities: attachment: type: tosca.capabilities.Attachment capabilities: storage_endpoint: type: tosca.capabilities.Endpoint

  6. VDU mapping option 1 VM aggregation • AttachesTo or X ConnectsTo Virtual Storage

  7. VDU mapping option 2 (suggested way to go) VM • VDU contains: • 1 or more internal connection points • Reference to 1 virtual compute descriptor • Reference to 0 or more virtual storage descriptors • Zero or 1 SW image descriptor • One set of VNFC configurable properties virtualComputeDescId requestAdditionalCapabilities virtualMemory virtualCpu Virtual Storage VDU • AttachesTo or ConnectsTo

  8. Proposal virtualStorage Descriptor.Block VDU internalCpd virtualCompute Description VduCpd VirtualStorageDescriptor property req VirtualComputeDescriptor req property cap VirtualLinkable cap AttachesTo Attachment property req Nfv_compute input property VirtualBindable input req VirtualBindsTo virtualStorage Descriptor.Object Attachment Connect VirtualStorageDescriptor cap req Substitution mappings VirtualBindable ConnectsTo artifact cap cap swImageDescriptor Connect

  9. Attributes of the VNFD information element Attributes of the Vdu information element reference reference

  10. Mapping between VNFD model defined in NFV and TOSCA

  11. Mapping between VDU model defined in NFV and TOSCA

  12. The definition of VirtualComputeDesc in NFV much more align with tosca.capabilities.Compute tosca.capabilities.Compute

  13. Combining three tables for VirtualComputeDesc together

  14. Defining a new capability tosca.capabilities.nfv.Compute.Container

  15. VirtualComputeDescriptor note type

  16. VirtualStorageDescriptor note type

  17. VDU service template and node type example

  18. Suggestion 1，using a service template to describe a VDU, and using the substitution mapping feature to abstract the VDU to be a new VDU node type. 2, Defining virtualComputeDesc and virtualStorageDesc in the DSL_definitions section in a VNFD service template, so multiple VDUs can reference the same virtualComputeDesc or virtualStorageDesc. 3, Defining swImageDesc as a artifact in a VDU.

  19. Thank you!

  20. If substitution mapping is not used VL InternalCpd InternalCpd VDU2 VDU1 VirtualComputeDesc VirtualComputeDesc attachsTo attachsTo attachsTo VirtualStorageDesc VirtualStorageDesc VirtualStorageDesc

  21. In NFV, VDU is the smallest unit of VNF, for VNF lifecycle management, it has to based on VDU level, all the lifecycle management operation can not directly target to virtualComputeDesc or virtualStorageDesc. E.g. Scaling should based on VDU, adding or delete VDU instances (VNFCs).

  22. Remaining issues Issue: In TOSCA, only compute node can contain an artifact. We don’t have the mechanism to describe how to store a software image into a virtual storage. Proposal: Option 1: allow virtual storage to have an artifact.

More Related