OpenStack Tacker Liberty Mid-Cycle

Aug 2015

Agenda• Welcome / Intro / Agenda bashing • Health Monitoring• Break• TOSCA / VNFD / NSD data-model• Lunch• Tacker's Service Chaining strategy• Tacker governance - spec, approval process, etc.• Wrap up

VNF Health Monitoring

Health Monitoring• Tacker server – monitoring framework interface

• custom boot-wait• vdu_mon_start / stop• vdu_mon_event_notification

• Driver: icmp, event: icmp-unreachable• Driver: http-alive, event: alive-check-failed• Driver: alu-vepc-2015, event: max-foo-reached

• Monitoring drivers• icmp-ping• http-alive• custom driver

• Co-existing with Heat / Ceilometer monitoring• Monasca Integration

Monasca architecture

TOSCA / VNFD / NSD

TOSCA – Heat Translator Update• Heat-translator is splitting into two libraries• Heat-translator parser + generator• Plan is to use heat-translator parser as a dependent library • Extract objects consumed by Tacker crucial to differentiate Tacker from Heat

• mgmt_driver - configuration• monitoring_parameter

• Remaining objects goes to heat-translator for HOT template generation

• TBD – define Tacker VNF state-machine !

MANO Descriptors

© ETSI 2014. All rights reserved

NSD

Id

Vendor

Version

vnfd

Vnffgd

Vld

Lifecycle_event

Vnf_depedency

Monitoring_parameters

Deployment_flavour

Auto_scale_policy

CP

pnfd

VNFDvendor

descriptor_versionversion

vduvirtual_link

connection_pointlifecycle_event

dependencymonitoring_parameter

deployment_flavourauto_scale_policy

manifest_filemanifest_file_security

VDUid

vm_imagecomputation_requirement

virtual_memory_resource_elementvirtual_network_bandwidth_resource

lifecycle_eventconstraint

high_availabilityscale_in_out

vnfcmonitoring_parameter

idvm_image

vnfcid

connection_point

VNFFGDId

VendorDescriptor_version

VersionConstituent_vnf

CpNfp

Depedent_virtual_linkNumber _of_endpointsnumber_of_virtual_link

VLDId

VendorVersion

Root_requirementsLeaf_requirements

Qosconnection

Connectivity_typeTest_access

NFPId

policyconnection

MANO information elements describe features for all MANO constructs

NS Instantiation Flow

© ETSI 2014. All rights reserved

OSS

NFVO processes the NS LCM

request

NFVO creates connectivity for

the NS

NFVO instantiate needed VNFs using the Instantiate VNF

flow

NFVO connects VNFs

to the connectivity

network

NFVO requests Network

Manager(s) to connect PNFs

VNF related resource management

© ETSI 2014. All rights reservedSimplified flow, focusing only on Resource Management

NFVO, EM, VNFM itself

Any VNF LCM request

VNFM processes the VNF LCM

request

VNFM gets permission from NFVO

(Details under specification)

VNFM invokes directly RM

operations towards the VIM

Additional processing skipped for simplicity

Resource Management

operations handled by

the VIM

ETSI MANO IFA WG Work ItemsNFV Orchestrator

(NFVO)

Virtualized Infrastructure Manager

(VIM)

NFV-MANO

Os-Ma-nfvo

Or-Vnfm

Vi-Vnfm

Or-Vi

Nf-Vi

Ve-Vnfm-em

Ve-Vnfm-vnfIFA005

IFA006

IFA007

IFA008

IFA012

IFA013OSS

EM

NFVI

Vn-Nf

VNF

IFA009: MANO architectural options IFA010: MANO Functional RequirementsIFA011: VNF Package/VNFDIFA014: NSD

VNF Manager(VNFM)

Governance

Moving to the tent !• Stackforge is being retired [1]• Automatically migrated to openstack/ namespace• Tentative dates : Oct 17th or Nov 7th

Reviews• +1 / -1s are very, very important• Goal -> two +2s for merge• Mandatory min days before merging • Min = 1 day ?• Exception for critical, blocking issues

Transparency• Logging #tacker IRC logs• For e.g: http://eavesdrop.openstack.org/irclogs/%23heat/• Any veto ?

Ease of development• Optimal tacker-spec process • Launchpad RFE bug – what is the community sign off process ? • Blueprint – is this really required ? What is the value of this ?• Write up in tacker-specs repo – is the template simple enough ?• DevRef – should we adopt this ?

• Avoid process for process sake

Upcoming activities &

Roadmap

Key upcoming activities• Switch to master• pull stable/kilo branch• merge master oslo_xyz changes

• MANO API changes• API docs• Initial unit tests

• Parameter / get_input support in TOSCA template

Roadmap• mgmt_drivers – horizontal (ssh, netconf) and vertical (vyatta, tail-f,

arista, hp-vsr, …)• basic auto-scaling• ODL SFC integration

Tokyo Demo

Tokyo Demo Plans

• The talk will be followed by a demonstration of OpenStack Tacker doing:• ● Complex VNF instantiation with multiple VDUs• ● VNF Auto-Configuration using Tacker plugins• ● VNF Self-Healing• ● VNF Auto-Scaling• The demo will showcase Tacker Orchestrating various VNFs like vRouter,

vFirewall,• vEPC from multiple vendors.

Backup

NVFO VNFM (IFA 7)• VNF Package Management

• metadata, vendor, release-date, image, VNFD

• VNF Lifecycle Management• Instantiate• Terminate• Show • Scaling

• VNF Change Notification• Changes to VNFC (VDU?)• Changes to Networks, Ports, etc• Start – End notifications

NVFO VIM (IFA 5)• AddImageRequest• Side note: There is an effort to enhance glance to be used as a ‘uber’

repository – even to store NSD & VNFD templates

• AllocateNetworkRequest• Compute & Storage Interfaces• FaultManagement Interface• PerformanceManagement Interface

NSD – NVFO VIM (IFA 5)• AddImageRequest• Upload image to glance• Do we need to treat these images different from other glance images ?

• Side note: There is an effort to enhance glance to be used as a ‘uber’ repository – even to store NSD & VNFD templates• AllocateNetworkRequest• create-network ?