Capability issues 2018.4 Shitao li.

Slides:



Advertisements
Similar presentations
Restructuring Proposal for TOSCA Files 1. Goals Separation of concerns: only expose what is needed to different roles in the creation of TOSCA templates.
Advertisements

6.1 – Graphing Systems of Equations
Min Chen School of Computer Science and Engineering Seoul National University Data Structure: Chapter 7.
computer
7.4 – Roots of Real Numbers. Real vs. Imaginary Roots – opposite of exponents!
Restructuring Proposal for TOSCA Files 1. Goals Separation of concerns: only expose what is needed to different roles in the creation of TOSCA templates.
Simplifying Radical Expressions Simplifying Radicals Radicals with variables.
Grammars CS 130: Theory of Computation HMU textbook, Chap 5.
Evaluate container lifecycle support in TOSCA TOSCA – 174 Adhoc TC.
How TOSCA Adds Value in NFV world

TOSCA v1.0 Figures. Definition of building blocks for services … along with the implementation artifacts for manageability operations … and the definition.
Evaluate container lifecycle support in TOSCA TOSCA – 174 Adhoc TC.
Update for tosca-nfv-profile
Mapping between NFV model and TOSCA
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
VNF Package CSAR for ONAP Release 2 – adding Telco grade features Andrei Kojukhov, PhD, Amdocs Oct 6, 2017.
Change Log VNF Package Model Business Compute Req.
VoLTE VNF Descriptor gaps
Domino Release D Planning
ONAP Information Model and Data Model
VNFD and NSD modeling: Rel2 Thinh Nguyenphu, Nokia thinh
Deployment Flavour as VNF Capability: Alt1_r3
ETSI NSD Overview & TOSCA model Thinh Nguyenphu, Nokia thinh
OASIS TOSCA Report for December ONAP Event
Section 8.1 Trees.
TOSCA Namespaces for tosca-nfv-profile
Critical issues with TOSCA NFV profile direction
Balanced and Unbalanced Forces.
OASIS TOSCA Report for December ONAP Modeling Workshop
NSD modeling: Rel2 Nagesha Subramanya nagesha.
OASIS TOSCA Report for December ONAP Event
DF design as a node type (output by Chris and shitao)
TOSCA NFV profile: short vs long-term approach
Evaluate the integral by making the given substitution: {image}
DF design as a node type (output by Chris and shitao)
NFV & SDN adhoc Progress
Artifact Properties Use cases and Examples to demonstrate the need of artifact properties July 2018.
Which of the following graphs is the graph of the derivative of the function {image} . 1. {applet}
SwImageDesc Shitao li.
TOSCA Namespaces for tosca-nfv-profile
Question Suppose exists, find the limit: (1) (2) Sol. (1) (2)
Defining ONAP VNF Package Model
VNF Package Model Per ETSI NFV SOL001, SOL004, SOL005
VDU proposal comparison
Vocabulary Trees Complete the tree by adding your vocabulary word to the trunk, definitions to the roots, and fill the branches with at least 8 related.
VNFD Overview & TOSCA model Thinh Nguyenphu, Nokia thinh
New VDU model proposal.
TOSCA v1.0 Figures.
Further Sequences and Series
DF design as a node type (output by Chris and shitao)
Deployment Flavour as VNF Capability: Alt1_r2
Discussion of Publishing CSD03 version of NFV Profile
The Discriminant CA 22.0, 23.0.
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.
13.9 Day 2 Least Squares Regression
VDU proposal comparison
TOSCA Simple Profile for YAML: Changes proposed for 1.3 release
Trial and Improvement Cube root.
Open Source Projects Collaborations with ONAP
NFV adhoc Shitao li.
NFV adhoc Shitao li.
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
Squares and Square Roots
All sales information is derived from the Whistler Listing Service and is believed correct. E&EO
Generating Function and Applications
NSD model in ONAP service descriptors (draft7)
B-Trees B-trees are characterized in the following way:
Presentation transcript:

Capability issues 2018.4 Shitao li

Design issues Issues 1, tosca.capabilities.Node VS tosca.capabilities.root 2, tosca.capabilities.Compute

What is the difference between tosca. capabilities. Node and tosca What is the difference between tosca.capabilities.Node and tosca.capabilities.root? The Node capability indicates the base capabilities of a TOSCA Node Type When a new capability has been defined, whether it should be derived from the Root capability or the Node capability? We face this issue in the NFV application model (ETSI NFV SOL001)

tosca.capabilities.Compute Definition of tosca.capabilities.Compute It is used as the compute capability of a compute node Are those two definitions correct? Should tosca.capabilities.container be used instead?