Jump to: navigation, search

Difference between revisions of "Tacker"

(Tacker - OpenStack NFV Orchestration)
Line 77: Line 77:
'''IRC Channel:''' <code><nowiki>#tacker</nowiki></code>
'''IRC Channel:''' <code><nowiki>#tacker</nowiki></code>
'''Meetings:''' Tuesday 1700 UTC [Weekly]  @ <code><nowiki>#openstack-meeting-4</nowiki></code>
'''Meetings:''' Wednesday 0530 UTC [Weekly]  @ <code><nowiki>#openstack-meeting</nowiki></code>
'''Tags:'''  [NFV] [Tacker]<br />
'''Tags:'''  [NFV] [Tacker]<br />

Revision as of 05:28, 21 December 2016

Tacker - OpenStack NFV Orchestration

Tacker is an official OpenStack project building a Generic VNF Manager (VNFM) and a 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.

Tacker Architecture.png

High Level Architecture

NFV Catalog

  1. VNF Descriptors
  2. Network Services Decriptors
  3. VNF Forwarding Graph Descriptors


  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


  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)




Install Guide


Use Cases


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


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.


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.


Tacker uses TOSCA for VNF meta-data definition. Within TOSCA Tacker used NFV profile schema,

Tacker + SFC (Service Function Chaining)

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


Weekly Meetings and Mailing List

IRC Channel: #tacker

Meetings: Wednesday 0530 UTC [Weekly] @ #openstack-meeting

Tags: [NFV] [Tacker]

Meeting Minutes



Tacker http://git.openstack.org/cgit/openstack/tacker/
Tacker Specs - Tacker Python Client http://git.openstack.org/cgit/openstack/python-tackerclient/
Tacker https://review.openstack.org/#/q/status:open+project:openstack/tacker,n,z
Tacker Specs https://review.openstack.org/#/q/status:open+project:openstack/tacker-specs,n,z
Tacker Python client https://review.openstack.org/#/q/status:open+project:openstack/python-tackerclient,n,z


Tacker Code and Spec Reviews

Tacker Open Code and Spec Reviews



Unassigned Bugs

Points of contact

Quick Links

Design & Documentation Tacker/Design
Resources Tacker/Resources
Action Items Tacker/ActionItems
Dependencies & Wish List Tacker/Dependencies
Spec/Patch Tracking Spec & Patch Tracking
Liberty Summit Tacker Talk Sched Link
Juno Design Summit Tacker/JunoSummit
Team Team Members

Wiki Pages