Difference between revisions of "Tacker"
(→TOSCA for NFV) |
|||
Line 68: | Line 68: | ||
Tacker uses TOSCA for VNF meda-data definition. Within TOSCA Tacker used NFV profile schema, | Tacker uses TOSCA for VNF meda-data definition. Within TOSCA Tacker used NFV profile schema, | ||
− | * 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 | ||
+ | ** 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) = | = Tacker + SFC (Service Function Chaining) = |
Revision as of 02:58, 12 October 2015
Title: Tacker
Aim: To develop a fully functional ETSI MANO / IFA based general purpose NFV Orchestrator + VNF Manager for OpenStack
Repo: http://git.openstack.org/cgit/stackforge/tacker/
IRC Channel: #tacker
Meetings: Thursdays 1600 UTC [Weekly] @ #openstack-meeting
Tags: [NFV] [Tacker]
Contents
Mission & Scope
Tacker is building an OpenStack based NFV Orchestrator with in-built general purpose VNF Manager to deploy and operate Virtual Network Functions (VNFs) on an OpenStack based NFV Platform. It is based on ETSI MANO Architectural Framework and provides full functional stack to Orchestrate VNFs end-to-end.
High Level Functionality
VNFM
- VNF Catalog
- Basic life-cycle of VNF (define/start/stop/undefine)
- Performance and 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 a SFC - described in a VNF Forwarding Graph Descriptor
- VIM Resource Checks and Resource Allocation
- Ability to orchestrate VNFs across Multiple VIMs
Relation to Nova, Glance, Heat :
Tacker makes use of Nova and Glance for VM and image management. Tacker makes use of Heat as a subsystem to manage virtual devices.
Use Cases
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
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.
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.
Installation
TOSCA for NFV
Tacker uses TOSCA for VNF meda-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
Meeting Minutes
http://eavesdrop.openstack.org/meetings/tacker/
Repos
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 |