Tacker

= Tacker - OpenStack NFV Orchestration =

Tacker is an official OpenStack project building a Generic VNF Manager (VNFM) and an NFV Orchestrator (NFVO) to deploy and operate Network Services and Virtual Network Functions (VNFs) on an NFV infrastructure platform like OpenStack. It is based on ETSI MANO Architectural Framework and provides a functional stack to Orchestrate Network Services end-to-end using VNFs.



= High-Level Architecture =

NFV Catalog

 * 1) VNF Descriptors
 * 2) Network Services Descriptors
 * 3) VNF Forwarding Graph Descriptors

VNFM

 * 1) Basic life-cycle of VNF (create/update/delete)
 * 2) Enhanced platform-aware (EPA) placement of high-performance NFV workloads
 * 3) Health monitoring of deployed VNFs
 * 4) Auto Healing / Auto Scaling VNFs based on Policy
 * 5) Facilitate initial configuration of VNF

NFVO

 * 1) Templatized end-to-end Network Service deployment using decomposed VNFs
 * 2) VNF placement policy – ensure efficient placement of VNFs
 * 3) VNFs connected using an SFC - described in a VNF Forwarding Graph Descriptor
 * 4) VIM Resource Checks and Resource Allocation
 * 5) Ability to orchestrate VNFs across Multiple VIMs and Multiple Sites (POPs)

= Documentation =

https://docs.openstack.org/tacker/

Install Guide
https://docs.openstack.org/tacker/latest/install/index.html

= Use Cases =

vCE
Tacker API can be used by SP's OSS / BSS or an NFV Orchestrator to deploy VNFs in SP's network to deliver agile network services for remote Customer networks

vCPE
Tacker API can be used by SP's OSS / BSS or an NFV Orchestrator to manage OpenStack enabled remote CPE devices to deploy VNFs to provide locally network services at the customer site.

vPE
Tacker API can be used by SP's OSS / BSS or an NFV Orchestrator to deploy VNFs within SP's network to virtualize existing network services into a Virtual Function.

Telecom operator's expectations
What Tacker solves ?

= ETSI NFV SPECS = ETSI NFV SPECS

= TOSCA for NFV =

Tacker uses TOSCA for VNF meta-data definition. Within TOSCA Tacker used NFV profile schema.
 * TOSCA YAML
 * YAML Simple Profile: http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/csprd02/TOSCA-Simple-Profile-YAML-v1.1-csprd02.html
 * TOSCA NFV Profile:
 * Latest spec is available here: https://www.oasis-open.org/committees/document.php?document_id=56577&wg_abbrev=tosca
 * Current latest (as of Oct 2015) is: https://www.oasis-open.org/committees/download.php/56577/tosca-nfv-v1.0-wd02-rev03.doc

= Tacker + SFC (Service Function Chaining)  =

The proposal to enable SFC for Tacker is captured in these slides,

https://docs.google.com/presentation/d/18AGaiysVgHOd_fIHVpObMO7zUkMjJGOQ98CUwkxU1xo/edit?usp=sharing

= Weekly Meetings and Mailing List =

IRC Channel:

Meetings: Tuesday 08:00 UTC [Weekly] @

Tags: [NFV] [Tacker]

= Meeting Minutes =

http://eavesdrop.openstack.org/meetings/tacker/

= Repos =

= Reviews =

Tacker Code and Spec Reviews

Tacker Open Code and Spec Reviews

= Bugs =

https://bugs.launchpad.net/tacker

Unassigned Bugs = Points of contact =


 * Launchpad project page: https://launchpad.net/tacker
 * IRC meeting information: https://wiki.openstack.org/wiki/Meetings/Tacker
 * IRC channel on OFTC:

= Quick Links =

= Wiki Pages =