SwImageDesc Shitao li.

Slides:



Advertisements
Similar presentations
Modeling Deployment Content and Metadata
Advertisements

Docker Container Modeling Goals Goals (not requirements) Not proliferate Node Types for “Docker” 1.Consider modeling “Docker” as an (explicit) runtime.
DigiTool METS Profile DigiTool Version 3.0. DigiTool METS Profile 2 What is METS? A Digital Library Federation initiative built upon the work of MOA2.
Software Component (Container + Containee) Software Component (Container + Containee) WebServer HostedOn Compute (Container) Compute (Container) Exploring.
Software Component (Container + Containee) Software Component (Container + Containee) WebServer HostedOn Compute (Container) Compute (Container) Exploring.
TOSCA Workloads with OpenStack Heat-Translator
File Systems (1). Readings r Reading: Disks, disk scheduling (3.7 of textbook; “How Stuff Works”) r Reading: File System Implementation ( of textbook)
Software Component (Container + Containee) Software Component (Container + Containee) WebServer HostedOn Compute (Container) Compute (Container) Exploring.
Kind: “Pod” (i.e. Type) kind: “Pod” (i.e. Type) Kubernetes Analysis: 2 types of containers “Dumb” (no HA, no Autoscale) = Pod Template kind: “ReplicationController”
IMS Content Packaging Overview Dec 5, IMS Content Packaging scope Source: IMS Info Model document Fig. 2.1.
Ontology Resource Discussion
Kind: “Pod” (i.e. Type) kind: “Pod” (i.e. Type) Kubernetes Analysis: 2 types of containers “Dumb” (no HA, no Autoscale) = Pod Template kind: “ReplicationController”
How TOSCA Adds Value in NFV world
Fedora Digital Object in a Nutshell Sandy Payette, Executive Director UK Fedora Training London January 22-23, 2009.
TOSCA v1.0 Figures. Definition of building blocks for services … along with the implementation artifacts for manageability operations … and the definition.
Update for tosca-nfv-profile
Day 28 File System.
SDN-O LCM for Mercury Release Key Points and Overview
Mapping between NFV model and TOSCA
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
ONAP SDC VoLTE Model Support
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
VNF Package Integrity and Authenticity – Public key based
VNF Package CSAR for ONAP Release 2 – adding Telco grade features Andrei Kojukhov, PhD, Amdocs Oct 6, 2017.
VoLTE VNF Descriptor gaps
Kubernetes Analysis: 2 types of containers
VNFD and NSD modeling: Rel2 Thinh Nguyenphu, Nokia thinh
Deployment Flavour as VNF Capability: Alt1_r3
Instantiation Level, Scaling Aspect, Scale Info
Approach to finalize the TOSCA NFV profile
OASIS TOSCA Report for December ONAP Event
Clarification of CSAR format Thinh Nguyenphu, Nokia thinh
TOSCA Namespaces for tosca-nfv-profile
DF design as a node type.
Deployment Flavor Model – Challenges and Emerging trends for ONAP adaptation Priya TG, NetCracker Technology.
OASIS TOSCA Report for December ONAP Modeling Workshop
TOSCA Namespaces Explained
Capability issues Shitao li.
DF design as a node type (output by Chris and shitao)
TOSCA NFV profile: short vs long-term approach
TOSCA-Metadata (directory )
DF design as a node type (output by Chris and shitao)
Enhancements for Simple YAML Profile v1.2
Artifact Properties Use cases and Examples to demonstrate the need of artifact properties July 2018.
TOSCA Namespaces Explained
Remain issues
TOSCA Namespaces for tosca-nfv-profile
Instance Model Structure
Tivoli Common Reporting v1.2 Overview
TOSCA-Metadata (directory )
Defining ONAP VNF Package Model
VNF Package Model Per ETSI NFV SOL001, SOL004, SOL005
VDU proposal comparison
VNFD Overview & TOSCA model Thinh Nguyenphu, Nokia thinh
New VDU model proposal.
DF design as a node type (output by Chris and shitao)
Deployment Flavour as VNF Capability: Alt1_r2
Session 2: Metadata and Catalogues
JAR Desc CSAR Notes A package file format typically used to aggregate many Java class files and associated metadata and resources (text, images, etc.)
NFV adhoc Shitao li.
Metadata The metadata contains
VDU proposal comparison
The new RDA: resource description in libraries and beyond
TOSCA v1.3 Enhancements February 21, 2019.
Global Types – Open-O spec versus TOSCA NVF Profile
TOSCA v1.3 Deprecated Features and Non-Backward-Compatible Changes
NFV adhoc Shitao li.
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
Task 55 Scope – TOSCA Profile
NSD model in ONAP service descriptors (draft7)
Presentation transcript:

SwImageDesc Shitao li

Artifact type, artifact definition in TOSCA Keyname Required Type Description mime_type no string The required mime type property for the Artifact Type. file_ext string[] The required file extension property for the Artifact Type. properties list of property definitions An optional list of property definitions for the Artifact Type. 3.6.7 Artifact definition Keyname Required Type Description type yes string The required artifact type for the artifact definition. file The required URI string (relative or absolute) which can be used to locate the artifact’s file. repository no The optional name of the repository definition which contains the location of the external repository that contains the artifact. The artifact is expected to be referenceable by its file URI within the repository. description The optional description for the artifact definition. deploy_path The file path the associated file would be deployed into within the target node’s container. No properties as defined currently in tosca-simple-profile-yaml v1.1 and v1.2. May need to added. The properties can only be considered as metadata information of the artifact itself. 2018/11/21

SwImageDesc Metadata of the image(could be mapped as artifact name) Attribute Qualifier Cardinality Content Description id M 1 Identifier The identifier of this software image. name String The name of this software image. version The version of this software image. checksum The checksum of the software image file. containerFormat The container format describes the container file format in which software image is provided. diskFormat The disk format of a software image is the format of the underlying disk image. minDisk Number The minimal disk size requirement for this software image. The value of the "size of storage" attribute of the VirtualStorageDesc referencing this SwImageDesc shall not be smaller than the value of minDisk. minRam 0..1 The minimal RAM requirement for this software image. The value of the "size" attribute of VirtualMemoryData of the Vdu referencing this SwImageDesc shall not be smaller than the value of minRam. Size The size of this software image. swImage Identifier (Reference to SwImage) This is a reference to the actual software image. The reference can be relative to the root of the VNF Package or can be a URL. operatingSystem Identifies the operating system used in the software image. This attribute may also identify if a 32 bit or 64 bit software image is used. supportedVirtualisationEnvironment 0..N Identifies the virtualisation environments (e.g. hypervisor) compatible with this software image. Metadata of the image, it is not required for TOSCA orchestrator (could be a property of the artifact) Could move into vnf package manifest file Type of the artifact or file_ext of the artifact type(such as, tosca.artifacts.Deployment.Image.Container.Docker, tosca.artifacts.Deployment.Image.VM.ISO) Could delete and use the value “size of the storage” in VirtualStorageDesc Could delete and use the value in VirtualMemoryData Metadata of the image, it is not required for TOSCA orchestrator (could be a property of the artifact) ‘file’ of this artifact Metadata of the image, it is not required for TOSCA orchestrator (could be a property of the artifact) Could move to Vdu.compute

Artifact type tosca.artifacts.nfv.SwImage:   derived_from: tosca.artifacts.Deployment.Image   file_ext: #diskFormat of the image properties: version: size: operationSystem:      This type can be extended to support other container format, such as docker, tosca.artifacts.nfv.SwImage.docker Node template: VDU_compute: type:tosca.nodes.nfv.Vdu.Compute properties: supportedVirtualisationEnvironment: capabilities: virtualCompute: virtual_memory: virtual_mem_size: 16384 # MB bigger than minRam of image requirement artifact: My_Image: # The identifier and name of this software image. type: tosca.artifacts.nfv.SwImage # could indicate the container format file: image_url# file_ext: qcow2 #disc format deploy_path: VDU_Storage_1 #node template name of a Vdu.VirtualStorage, in case, #it has more one VirtualStorage attached in the Vdu.Compute version: 1.0 size: 1 # G os: suse VDU_Storage_1: type:tosca.nodes.nfv.Vdu.VirtualStorage      properties: size_of_storage: 50 # G bigger than minDisk of image requirement