Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial...

17
© ETSI 2018 Day-0, day-1 and day-2 configuration in OSM Gerardo García (Telefónica)

Transcript of Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial...

Page 1: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

Day-0, day-1 and day-2 configuration in OSM

Gerardo García (Telefónica)

Page 2: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

Traditional network management

Day 0 Day 1 Day 2

• PNF installation

• Initial configuration to make PNF reachable (user, pwd, network, etc.)

• License activation

• Injection of configuration• Neighbor configuration• Network configuration

EMS

OSS

EMS

• Service provisioning

• Business provisioning

EMS

OSS

EMS

BSS

Page 3: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

NFV management

Day 0 Day 1 Day 2

• VNF deployment

• NS deployment(complex topology)

• Service provisioning

• Business provisioning

Network Service

MANO

OSS

BSS

VNF VNF

VNF

VNF

EMS

License activation

VNF configuration

Neighbor configuration

Network Service

MANO

OSS

VNF VNF

VNF

VNF

EMS

Page 4: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

VNF’s operational procedures are embedded in the VNF Package…

VNF package

VNFD

VNF artifacts

Additional metadata?

Capacity aspects

VNF resource orchestration info(EPA resources and internal

connectivity)

Functionality aspects

Descriptive information- metadata.yaml- config.yaml- actions.yaml

Executables- Hooks- Actions

Additional info (icon, README)

Page 5: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

... ready to be used in complex Network Services, which define their own E2E operational procedures…

Page 6: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

VNF operational procedures are encapsulated in charms, which are controlled by VCA

NFVI VIM

NS#1VNF 1

VNF 2

VNF 3

VIM’s NBI

VCACharms

ROVIM/SDN Connectors

SO

OSM’s NBI

MgmtProcedures

Resource Description

VNF Packages

MgmtProcedures

Topology

NS Package

Deployment

INFORMATION MODEL

Page 7: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2017

Juju charms in layman’s terms

7

Page 8: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

What is a charm?

• A charm is a set of actions and hooks

• Actions are programs

• Hooks are events/signals

• For commodity and reusability, those actions and hooks are grouped in layers

• A charm will always have one layer:

• That layer has some actions and hooks

• In addition, that layer can import other layers

• The resulting charm has all the actions and hooks from all the layers joined together, plus additional default actions and hooks (e.g. ‘config’ action)

Page 9: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

What is a charm?Charm design

blue

red green

layers

‘config’ action

actions

hooks

Page 10: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

What is a charm?Charm build

Page 11: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2017

From charms to VNF primitives

11

Page 12: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

VNF descriptors map charm actions to VNF primitives, thus providing a full set of enablers for NFV management

RO

Injection of basic configuration

OSM NB API:- Create new NS instance

- Get NS instance record

- Get VNF metrics

- Call NS primitive

- Scale in/out NS instance

VNFD:- Basic configuration (SSH keys,

hostname, user-data scripts, etc.)

- Initial config primitive

- Config primitive

- Charms Actions

- Charms Metrics

NSD:- Initial config primitive

- Service primitive

- Scaling groups

- Pre and post scaling primitives

- Scripts

VCA

SO

Contr

olle

r

initial-config-

primitive

Charm

Charm

Charm

Charm action

Charm action

UI OSS

service-primitive

pre/post scaling

primitives

Charm metric

Page 13: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

RO

OSM NB API:- Create new NS instance

VNFD:- Basic configuration (SSH keys,

hostname, user-data scripts, etc.)VCA

SO

Contr

olle

r

Charm

Charm

Charm

UI OSS

Injection of basic configuration

Day-0 configuration (at instantiation time)

Page 14: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

RO

OSM NB API:- Create new NS instance

VNFD:- Initial-config-primitive- Charms -> Actions

NSD:- Initial config primitive- Scripts

VCA

SO

Contr

olle

r

initial-config-primitive

Charm

Charm

Charm

Charm action

Charm action

UI OSS

Injection of basic configuration

Day-1 configuration (at instantiation time)

Page 15: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

VCA

SO

Contr

olle

r

config-primitiveservice-primitive

Charm

Charm

Charm

Charm action

Charm action

UI OSS OSM NB API:- Get NS instance record- Call NS or VNF primitive

VNFD:- Config primitive- Charms -> Actions

NSD:- Service primitive- Scripts

Day-2 configuration

Page 16: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

OSM NB API:- Get NS instance record- Scale in/out NS instance

ROVCA

SO

Contr

olle

r

pre/post-scaling-primitive

Charm

Charm

Charm

Charm action

Charm action

UI OSS

VNFD:- Basic configuration (SSH keys,

hostname, cloud-init scripts, etc.)

- Charms Actions

NSD:- Scaling groups- Pre and post scaling primitives

Injection of basic configuration

Day-2 elasticity (scaling)

Page 17: Day-0, day-1 and day-2 configuration in OSM · Day 0 Day 1 Day 2 • PNF installation • Initial configuration to make PNF reachable (user, pwd, network, etc.) • License activation

© ETSI 2018

Find us at:osm.etsi.org

osm.etsi.org/wikipub