Jump to: navigation, search

Difference between revisions of "Tacker"

(→‎TOSCA for NFV)
(16 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
−
 
−
Tacker is OpenStack project building an Open NFV Orchestrator with in-built general purpose VNF Manager to deploy and operate Virtual Network Functions (VNFs) on an NFV Platform. It is based on ETSI MANO Architectural Framework and provides full functional stack to Orchestrate VNFs end-to-end.
 
  
−
[[File:ETSI_MANO_TackerPhase1.JPG]]
+
= 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.
  
−
'''IRC Channel:''' <code><nowiki>#tacker</nowiki></code>
+
[[File:Tacker_Architecture.png]]
  
−
'''Meetings:''' Thursdays 1600 UTC [Weekly]  @ <code><nowiki>#openstack-meeting</nowiki></code>
+
= High Level Architecture =
  
−
'''Tags:'''  [NFV] [Tacker]<br />
 
  
−
__TOC__
+
== NFV Catalog ==
  
−
 
+
# VNF Descriptors 
−
= High Level Functionality =
+
# Network Services Decriptors
 +
# VNF Forwarding Graph Descriptors
  
 
== VNFM ==
 
== VNFM ==
  
−
# VNF Catalog
+
# Basic life-cycle of VNF (create/update/delete)
−
# Basic life-cycle of VNF (define/start/stop/undefine)
+
# Enhanced platform-aware (EPA) placement of high-performance NFV workloads
−
# Performance and Health monitoring of deployed VNFs
+
# Health monitoring of deployed VNFs
−
# Auto Healing VNFs based on Policy
+
# Auto Healing / Auto Scaling VNFs based on Policy
 
# Facilitate initial configuration of VNF
 
# Facilitate initial configuration of VNF
  
Line 29: Line 28:
 
# Templatized end-to-end Network Service deployment using decomposed VNFs
 
# Templatized end-to-end Network Service deployment using decomposed VNFs
 
# VNF placement policy – ensure efficient placement of VNFs  
 
# VNF placement policy – ensure efficient placement of VNFs  
−
# VNFs connected using a SFC - described in a VNF Forwarding Graph Descriptor
+
# VNFs connected using an SFC - described in a VNF Forwarding Graph Descriptor
 
# VIM Resource Checks and Resource Allocation
 
# VIM Resource Checks and Resource Allocation
−
# Ability to orchestrate VNFs across Multiple VIMs  
+
# Ability to orchestrate VNFs across Multiple VIMs and Multiple Sites (POPs)
  
−
= Installation =
+
[[File:Tacker-Architecture.jpg]]
  
−
[[ Tacker/Installation ]]
+
 
 +
= Documentation =
 +
 
 +
http://docs.openstack.org/developer/tacker/
 +
 
 +
== Install Guide ==
 +
 
 +
http://docs.openstack.org/developer/tacker/#installation
  
 
= Use Cases =
 
= Use Cases =
Line 41: Line 47:
 
=== vCE ===
 
=== vCE ===
  
−
Tacker API can be used by SP's OSS / BSS or a 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 deploy VNFs in SP's network to deliver agile network services for remote Customer networks
  
 
=== vCPE ===
 
=== vCPE ===
  
−
Tacker API can be used by SP's OSS / BSS or a NFV Orchestrator to manage OpenStack enabled remote CPE devices to deploy VNFs to locally provide network services at customer site.
+
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 ===
 
=== vPE ===
  
−
Tacker API can be used by SP's OSS / BSS or a NFV Orchestrator to deploy VNFs within SP's network to virtualize existing network services into a Virtual Function.
+
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.
  
 +
= ETSI NFV SPECS =
 +
[http://www.etsi.org/standards-search#page=1&search=&title=1&etsiNumber=1&content=0&version=0&onApproval=1&published=1&historical=0&startDate=1988-01-15&endDate=2017-02-03&harmonized=0&keyword=&TB=789,,832,,831,,795,,796,,800,,798,,799,,797&stdType=&frequency=&mandate=&sort=1 ETSI NFV SPECS]
  
 
= TOSCA for NFV =
 
= TOSCA for NFV =
  
−
Tacker uses TOSCA for VNF meda-data definition. Within TOSCA Tacker used NFV profile schema,
+
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:
 
* TOSCA NFV Profile:
 
** Latest spec is available here: https://www.oasis-open.org/committees/document.php?document_id=56577&wg_abbrev=tosca
 
** Latest spec is available here: https://www.oasis-open.org/committees/document.php?document_id=56577&wg_abbrev=tosca
Line 65: Line 74:
  
 
https://docs.google.com/presentation/d/18AGaiysVgHOd_fIHVpObMO7zUkMjJGOQ98CUwkxU1xo/edit?usp=sharing
 
https://docs.google.com/presentation/d/18AGaiysVgHOd_fIHVpObMO7zUkMjJGOQ98CUwkxU1xo/edit?usp=sharing
 +
 +
=  Weekly Meetings and Mailing List =
 +
 +
 +
'''IRC Channel:''' <code><nowiki>#tacker</nowiki></code>
 +
 +
'''Meetings:''' Wednesday 0530 UTC [Weekly]  @ <code><nowiki>#openstack-meeting</nowiki></code>
 +
 +
'''Tags:'''  [NFV] [Tacker]<br />
  
 
=  Meeting Minutes =
 
=  Meeting Minutes =
Line 77: Line 95:
 
| Tacker || http://git.openstack.org/cgit/openstack/tacker/
 
| Tacker || http://git.openstack.org/cgit/openstack/tacker/
 
|-
 
|-
−
| Tacker Specs || http://git.openstack.org/cgit/openstack/tacker-specs/
+
| Tacker Specs || http://specs.openstack.org/openstack/tacker-specs/
 
|-
 
|-
 
| Tacker Python Client  || http://git.openstack.org/cgit/openstack/python-tackerclient/
 
| Tacker Python Client  || http://git.openstack.org/cgit/openstack/python-tackerclient/
Line 129: Line 147:
 
|-
 
|-
 
|  Team  ||  [https://wiki.openstack.org/wiki/Tacker/Incubation#Team_Members Team Members ]
 
|  Team  ||  [https://wiki.openstack.org/wiki/Tacker/Incubation#Team_Members Team Members ]
 +
|-
 +
|  Tacker API doc  ||  http://developer.openstack.org/api-ref/nfv-orchestration/
 +
|-
 +
|  Tacker Client doc  ||  http://docs.openstack.org/cli-reference/tacker.html
 
|}
 
|}
−
 
  
 
= Wiki Pages =
 
= Wiki Pages =
 
{{Special:PrefixIndex/ServiceVM}}
 
{{Special:PrefixIndex/ServiceVM}}

Revision as of 03:26, 15 February 2017


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

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)

Tacker-Architecture.jpg


Documentation

http://docs.openstack.org/developer/tacker/

Install Guide

http://docs.openstack.org/developer/tacker/#installation

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.

ETSI NFV SPECS

ETSI NFV SPECS

TOSCA for NFV

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,

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

Weekly Meetings and Mailing List

IRC Channel: #tacker

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

Tags: [NFV] [Tacker]

Meeting Minutes

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

Repos

Git
Tacker http://git.openstack.org/cgit/openstack/tacker/
Tacker Specs http://specs.openstack.org/openstack/tacker-specs/
Tacker Python Client http://git.openstack.org/cgit/openstack/python-tackerclient/
Gerrit
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

Reviews

Tacker Code and Spec Reviews

Tacker Open Code and Spec Reviews

Bugs

https://bugs.launchpad.net/tacker

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
Tacker API doc http://developer.openstack.org/api-ref/nfv-orchestration/
Tacker Client doc http://docs.openstack.org/cli-reference/tacker.html

Wiki Pages

Retrieved from "https://wiki.openstack.org/w/index.php?title=Tacker&oldid=151157"