Difference between revisions of "Tacker"
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | |||
| − | |||
| − | + | = 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. | ||
| − | + | [[File:ETSI_MANO_Tacker.JPG]] | |
| − | + | = High Level Architecture = | |
| − | + | == NFV Catalog == | |
| − | + | # VNFD Catalog | |
| − | + | # NSD Catalog (*) | |
| − | |||
| − | |||
== VNFM == | == VNFM == | ||
| − | |||
# Basic life-cycle of VNF (define/start/stop/undefine) | # Basic life-cycle of VNF (define/start/stop/undefine) | ||
| − | # | + | # Enhance platform-aware placement of high-performance NFV workloads |
| + | # Health monitoring of deployed VNFs | ||
# Auto Healing VNFs based on Policy | # Auto Healing VNFs based on Policy | ||
# Facilitate initial configuration of VNF | # Facilitate initial configuration of VNF | ||
| Line 29: | Line 26: | ||
# 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 | + | # 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 | ||
| − | = | + | = Documentation = |
| − | + | http://docs.openstack.org/developer/tacker/ | |
| − | = | + | == Install Guide == |
| − | http:// | + | http://docs.openstack.org/developer/tacker/#installation |
= Use Cases = | = Use Cases = | ||
| Line 45: | Line 42: | ||
=== vCE === | === vCE === | ||
| − | Tacker API can be used by SP's OSS / BSS or | + | 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 | + | 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 | + | 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. |
= TOSCA for NFV = | = TOSCA for NFV = | ||
| − | Tacker uses TOSCA for VNF | + | Tacker uses TOSCA for VNF meta-data definition. Within TOSCA Tacker used NFV profile schema, |
* TOSCA NFV Profile: | * TOSCA NFV Profile: | ||
| Line 69: | Line 66: | ||
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:''' Tuesday 1700 UTC [Weekly] @ <code><nowiki>#openstack-meeting-4</nowiki></code> | ||
| + | |||
| + | '''Tags:''' [NFV] [Tacker]<br /> | ||
= Meeting Minutes = | = Meeting Minutes = | ||
| Line 81: | Line 87: | ||
| Tacker || http://git.openstack.org/cgit/openstack/tacker/ | | Tacker || http://git.openstack.org/cgit/openstack/tacker/ | ||
|- | |- | ||
| − | | Tacker Specs || http:// | + | | 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/ | ||
|- | |- | ||
Revision as of 00:55, 23 April 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.
High Level Architecture
NFV Catalog
- VNFD Catalog
- NSD Catalog (*)
VNFM
- Basic life-cycle of VNF (define/start/stop/undefine)
- Enhance platform-aware placement of high-performance NFV workloads
- Health monitoring of deployed VNFs
- Auto Healing VNFs based on Policy
- Facilitate initial configuration of VNF
NFVO
- Templatized end-to-end Network Service deployment using decomposed VNFs
- VNF placement policy – ensure efficient placement of VNFs
- VNFs connected using an SFC - described in a VNF Forwarding Graph Descriptor
- VIM Resource Checks and Resource Allocation
- Ability to orchestrate VNFs across Multiple VIMs
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.
TOSCA for NFV
Tacker uses TOSCA for VNF meta-data definition. Within TOSCA Tacker used NFV profile schema,
- 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: #tacker
Meetings: Tuesday 1700 UTC [Weekly] @ #openstack-meeting-4
Tags: [NFV] [Tacker]
Meeting Minutes
http://eavesdrop.openstack.org/meetings/tacker/
Repos
| Git | |||
|---|---|---|---|
| Tacker | http://git.openstack.org/cgit/openstack/tacker/ | ||
| 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 Open Code and Spec Reviews
Bugs
https://bugs.launchpad.net/tacker
Points of contact
- Launchpad project page: https://launchpad.net/tacker
- IRC meeting information: https://wiki.openstack.org/wiki/Meetings/Tacker
- IRC channel on Freenode:
#tacker
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 |
