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

Transcription

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

2 Traditional network management Day 0 Day 1 Day 2 BSS OSS OSS EMS EMS EMS EMS PNF installation Initial configuration to make PNF reachable (user, pwd, network, etc.) License activation Injection of configuration Neighbor configuration Network configuration Service provisioning Business provisioning

3 NFV management Day 0 Day 1 Day 2 deployment NS deployment (complex topology) OSS EMS Network Service MANO OSS EMS Network Service BSS MANO License activation configuration Neighbor configuration Service provisioning Business provisioning

4 s operational procedures are embedded in the Package package D artifacts Additional metadata? Capacity aspects 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)

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

6 operational procedures are encapsulated in charms, which are controlled by VCA Packages Mgmt Procedures Resource Description NS Package Mgmt Procedures Topology INFORMATION MODEL OSM s NBI SO VCA s RO VIM/SDN Connectors NFVI VIM s NBI VIM 2 NS#1 1 3 Deployment

7 Juju charms in layman s terms ETSI

8 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)

9 What is a charm? design hooks layers red blue green config action actions

10 What is a charm? build

11 From charms to primitives ETSI

12 Controller descriptors map charm actions to primitives, thus providing a full set of enablers for NFV management UI initialconfigprimitive serviceprimitive pre/post scaling primitives OSS SO OSM NB API: - Create new NS instance - Get NS instance record - Get metrics - Call NS primitive - Scale in/out NS instance action VCA RO D: - Basic configuration (SSH keys, hostname, user-data scripts, etc.) - Initial config primitive - Config primitive - s Actions - s Metrics action metric Injection of basic configuration NSD: - Initial config primitive - Service primitive - Scaling groups - Pre and post scaling primitives - Scripts

13 Controller Day-0 configuration (at instantiation time) UI OSS OSM NB API: - Create new NS instance SO VCA RO D: - Basic configuration (SSH keys, hostname, user-data scripts, etc.) Injection of basic configuration

14 Controller Day-1 configuration (at instantiation time) UI OSS OSM NB API: - Create new NS instance initial-config-primitive SO VCA RO D: - Initial-config-primitive - s -> Actions action action Injection of basic configuration NSD: - Initial config primitive - Scripts

15 Controller Day-2 configuration config-primitive service-primitive UI OSS OSM NB API: - Get NS instance record SO - Call NS or primitive action VCA D: - Config primitive - s -> Actions action NSD: - Service primitive - Scripts

16 Controller Day-2 elasticity (scaling) UI OSS OSM NB API: - Get NS instance record - Scale in/out NS instance pre/post-scalingprimitive SO action VCA RO D: - Basic configuration (SSH keys, hostname, cloud-init scripts, etc.) - s Actions action Injection of basic configuration NSD: - Scaling groups - Pre and post scaling primitives

17 Find us at: osm.etsi.org osm.etsi.org/wikipub