Instantiation Level, Scaling Aspect, Scale Info

Slides:



Advertisements
Similar presentations
XML Schema Heewon Lee. Contents 1. Introduction 2. Concepts 3. Example 4. Conclusion.
Advertisements

1 Web Data Management XML Schema. 2 In this lecture XML Schemas Elements v. Types Regular expressions Expressive power Resources W3C Draft:
Analytical Methods in CS (CIS 505)
Systems Analysis Requirements structuring Process Modeling Logic Modeling Data Modeling  Represents the contents and structure of the DFD’s data flows.
Introduction to XLink Transparency No. 1 XML Information Set W3C Recommendation 24 October 2001 (1stEdition) 4 February 2004 (2ndEdition) Cheng-Chia Chen.
XML Schemas Lecture 10, 07/10/02. Acknowledgements A great portion of this presentation has been borrowed from Roger Costello’s excellent presentation.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
Document Content Description for XML, Version 1.0 By Tim Bray, Charles Frankston and Ashok Malhotra EECS 684 Presentation by Calvin Ang.
OLD Organization Book Chapter Title Group Number, Group Member names New Organization
CSE314 Database Systems Data Modeling Using the Entity- Relationship (ER) Model Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson Ed Slide Set.
1 XML Schemas. 2 Useful Links Schema tutorial links:
BPJ444: Business Programming Using Java Classes and Objects Tim McKenna
Entity Relationship Diagrams Objectives s Learn the Elements of the E-R model (entities, attributes, and relationships) s Show how to apply the E-R model.
A Z Approach in Validating ORA-SS Data Models Scott Uk-Jin Lee Jing Sun Gillian Dobbie Yuan Fang Li.
Database Management System Lecture 4 The Relational Database Model- Introduction, Relational Database Concepts.
Standard Algorithms –search for an item in an array –count items in an array –find the largest (or smallest) item in an array.
NETWORK CONNECTIVITY USE CASES AT CARRIER / SERVICE PROVIDERS CloudBand June 2014.
Arrays An array is a data structure that consists of an ordered collection of similar items (where “similar items” means items of the same type.) An array.
LDK R Logics for Data and Knowledge Representation PL of Classes.
Chapter 10 Defining Classes. The Internal Structure of Classes and Objects Object – collection of data and operations, in which the data can be accessed.
Mathematical Preliminaries
CSE314 Database Systems Lecture 3 The Relational Data Model and Relational Database Constraints Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson.
Chapter 16 UML Class Diagrams 1CS6359 Fall 2012 John Cole.
Fundamentals, Design, and Implementation, 9/e Appendix B The Semantic Object Model.
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”
Interpreting the Object Constraint Presented by: Ed Kausmeyer.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix H: The Semantic Object Model.
1 CS 430 Database Theory Winter 2005 Lecture 3: A Fifty Minute Introduction to Data Modeling.
“It is impossible to define every concept.” For example a “set” can not be defined. But Here are a list of things we shall simply assume about sets. A.
CSE 373, Copyright S. Tanimoto, 2002 Abstract Data Types - 1 Abstract Data Types Motivation Abstract Data Types Example Using math. functions to describe.
Update for tosca-nfv-profile
ER Diagrams and Relational Model CS 174a (Winter 2015)
Data Modeling Using the Entity- Relationship (ER) Model
Entity/Relationship Modelling
Mapping between NFV model and TOSCA
Lesson 2.1 Basic Set Concepts.
Chapter 9 Domain Models.
OPEN-O Modeling Directions (DRAFT 0.6)
Requirements Become the E-R Data Model
ECOMP Information Model
Entity-Relationship Modeling
VNFD and NSD modeling: Rel2 Thinh Nguyenphu, Nokia thinh
Workflow-Instance Model Interaction
Deployment Flavour as VNF Capability: Alt1_r3
DF design as a node type.
Deployment Flavor Model – Challenges and Emerging trends for ONAP adaptation Priya TG, NetCracker Technology.
NSD modeling: Rel2 Nagesha Subramanya nagesha.
TOSCA Matching Or how the orchestrator provides implementation for abstract nodes or dangling requirements.
DF design as a node type (output by Chris and shitao)
DF design as a node type (output by Chris and shitao)
Lixiang,YaoguangWang, ChangMing Bai,
البرمجة بلغة فيجول بيسك ستوديو
SwImageDesc Shitao li.
Remain issues
Enhancements for Property function Tosca Simple Profile in YAML v1.2
Semantic Objects.
IFA007: VNF LCM The Or-Vnfm reference point is used for exchanges between Network Functions Virtualization Orchestrator (NFVO) and Virtualized Network.
ONAP modeling report shitao.
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
Mathematical Background 1
Mathematical Background 1
Which sets are equal? Which sets are equivalent?
Open Source Projects Collaborations with ONAP
NFV adhoc Shitao li.
Creating and Using Classes
NSD model in ONAP service descriptors (draft7)
DataTypes Nigel Davis
Presentation transcript:

Instantiation Level, Scaling Aspect, Scale Info October 2017 Removed “A High Level Discussion about” to reduce clutter from the title slide

InstantiationLevel Information Element ETSI IFA 011 http://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/011/02.03.01_60/gs_NFV-IFA011v020301p.pdf Describes given level of resources to be instantiated within a DF in term of the number of VNFC instances to be created from each VDU. All the VDUs referenced in the level shall be part of the corresponding DF and their number shall be within the range (min/max) for this DF. Attribute Qualifier Cardinality Content Description levelId M 1 Identifier Uniquely identifies a level with the DF. description String Human readable description of the level. vduLevel 1..N VduLevel Indicates the number of instance of this VDU to deploy for this level. scaleInfo 0..N ScaleInfo Represents for each aspect the scale level that corresponds to this instantiation level. scaleInfo shall be present if the VNF supports scaling. Curious why I’m not listed in SDO/OSSP as I work with ONF, MEF, BBF, CableLabs, and OANP, OSM & NSM. I don't need to see my name listed, but think it would reinforce that more than two people are working this. Attribute Qualifier Cardinality Content Description vduId M 1 Identifier (Reference to Vdu) Uniquely identifies a VDU. numberOf Instances Integer Number of instances of VNFC based on this VDU to deploy for this level.

Instantiation Level + Deployment Flavor VNF VDU 1 VDU 3 VDU 5 VDU 2 VDU 4 VDU 6 Deployment topology in Deployment Flavor 1, Instantiation Level =1 Deployment topology in Deployment Flavor 2, Instantiation Level = 1 VDU1 VDU3 VDU1 VDU3 VDU5 VDU2 VDU4 VDU2 VDU4 VDU6 Deployment topology in Deployment Flavor 1, Instantiation Level =2, vduLevel for VDU 3 =1 , vduLevel for all other VDUs = 2 VDU 1 VDU 2 VDU 4 VDU 1 VDU 2 VDU 3 VDU 4 Note: The diagram illustrates ETSI’s concept of deployment flavor and instantiation level

ScaleInfo Information Element ETSI IFA 011 Represents the scale level for a particular scaling aspect Scaling is applied for elements defined in a group (in Scaling Aspect IE) Attribute Qualifier Cardinality Content Description aspectId M 1 Identifier Identifier of the scaling aspect. scaleLevel Integer The scale level, greater than or equal to 0. NOTE: Vertical scaling (scale up, scale down) is not supported currently A scaling step is the smallest increment by which a VNF can be scaled for a particular aspect. Scaling by a single step does not imply that only one VNFC instance is created or removed. It means that one or more VNFC instances are created from the same VDU or from different VDUs, or that a more complex setup occurs.

ScalingAspect Information Element ETSI IFA 011 Attribute Qualifier Cardinality Content Description Id M 1 Identifier Unique identifier of this aspect in the VNFD. Name String Human readable name of the aspect. Human readable description of the aspect. associatedGroup 0..1 Identifier (Reference to VnfdElementGroup) Reference to the group of Vnfd elements defining this aspect. If present, scaling for this aspect is limited to the elements of the group, but there is no assumption that all the elements of the groups will be increased at each step. maxScaleLevel PositiveInteger The maximum scaleLevel for total number of scaling steps that can be applied w.r.t. this aspect. The value of this attribute corresponds to the number of scaling steps can be applied to this aspect when scaling it from the minimum scale level (i.e. 0) to the maximum scale level defined by this attribute.

Instantiation Level as Policy tosca.policies.nfv.instantiationlevel: derived_from: tosca.policies.Root properties: description: type: string required: false isDefault: type: boolean default: false vduLevels: type: map entry_schema: type: tosca.datatypes.nfv.vduLevel scaleInfo: type: tosca.datatypes.nfv.scaleInfo  

Scaling Aspect as Policy tosca.policies.nfv.scalingAspect: derived_from: tosca.policies.Root properties: name: type: string description: required: false maxScaleLevel: type: integer required: true

VDU Level and Scale Info Data types tosca.datatypes.nfv.vduLevel: derived_from: tosca.datatypes.Root properties: numberOfInstances: type: integer required: true tosca.datatypes.nfv.scaleInfo: scaleLevel:

VnfdElementGroup Group type group_types: tosca.groups.nfv.VnfdElementGroup: derived_from: tosca.groups.Root

Instantiation Level - Example # Instantiation Levels:     - InstantiationLevel1:         type: tosca.policies.nfv.instantiationlevel         properties:           description: Instantiation Level 1 isDefault: true           vduLevels:                      bono:            numberOfInstances: 1          ralf: homer:               numberOfInstances: 1           scaleInfo:                        bonoScaleAspect:             scaleLevel: 1           ralfScaleAspect:             scaleLevel: 0 homerScaleAspect:   Instantiation level as a policy.           VDU Level: VDU Id and Number of instances   Scale Info : Scale Aspect and Scale level  

Scaling Aspect and Scaling Group - Example - bonoScaleAspect:        type: tosca.policies.nfv.scalingAspect         properties:             name:              description:           maxScaleLevel: 5   targets: [bonoScalingGroup]         homerScalingGroup:       type: tosca.groups.nfv.VnfdElementGroup       description:       members: [ bono]    Scaling Aspect as a policy, consists of max scale level and scaling group Scaling Group