Revision as of 19:29, 19 May 2015

Title: Tacker

Aim: To develop a fully functional ETSI MANO based general purpose VNF Manager for OpenStack

Repo: http://git.openstack.org/cgit/stackforge/tacker/

IRC Channel: #tacker

Meetings: Wednesdays 1700 UTC [On-Demand] @ #openstack-meeting-4

Tags: [NFV] [Tacker]

Mission & Scope

Tacker is an OpenStack based VNF Manager service and a framework used 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

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

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.

Repos

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

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 Tacker Talk	Sched Link
Juno Design Summit	Tacker/JunoSummit
Team	Team Members

@@ Line 3: / Line 3: @@
 '''Title:''' Tacker <br />
-'''Aim:''' <tt style="color: blue">To develop a fully functional ETSI MANO based VNF Manager for OpenStack</tt><br />
+'''Aim:''' <tt style="color: blue">To develop a fully functional ETSI MANO based general purpose VNF Manager for OpenStack</tt><br />
 '''Repo:''' http://git.openstack.org/cgit/stackforge/tacker/<br />
@@ Line 39: / Line 39: @@
 = Use Cases =
-{| class="wikitable"
+== vCE ==
-|-
-! No. !! Name !! Description !! User !! Priority !! Target Release !! Status
+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
-|-
-| 1 || Define ServiceVM || Ability to define a ServiceVM template using (a) instance image (2) device specification (to run the image)  || Operator || High || Kilo ||
+== vCPE ==
-|-
-| 2 || ServiceVM CRUD API ||  API for basic life-cycle management of ServiceVMs (a) acquire a service-vm instance (b) release a service-vm instance  || Plugin|| High || Kilo ||
+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.
-|-
-| 3 || ServiceVM Neutron plugging driver  || Neutron port attributes to plug in ServiceVM to appropriate networks (a) Tenant L2 network  || Plugin|| High || Kilo ||
+== vPE ==
-|-
-| 4 || Resource Pools of ServiceVMs || Operator should be able to configure a pool of ServiceVMs to be in standby for immediate allocation (to avoid bootup latency) || Operator || Medium || L ||
+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.
-|-
-| 5 || Service allocation using partial ServiceVM || Allocate a portion of ServiceVM for specific service. Reason: Overhead cost of spinning another VM instance is high. If a ServiceVM supports multi-tenancy (for eg VRF for network services) a single ServiceVM can be segregated to support multiple tenant services. Note, there should be 100% tenant isolation while providing this scheme  || Operator, Plugin || Medium || L ||
-|-
-| 6 || Scheduling Scheme for ServiceVM allocation across a pool of VMs.  || Ability to schedule ServiceVMs based on different filters (Gnaat integration). For e.g. Tenant-A might have a higher application throughput needs. It would need a "high-end" FW ServiceVM with SR-IOV nics. Tacker scheduler need to get the "hint" from the plugin and allocate "appropriate" FW ServiceVM from the pool.  || Operator, Plugin || Low || M ||
-|-
-| 7 || Capacity management of ServiceVM  || Ability to report and use "remaining-capacity" data within a ServiceVM to host the next service request  || Plugin || Low || L ||
-|-
-| 8 || Docker Container Hosted Services  || Ability to host a ServiceVM in a Docker Container  || Operator || Low || M ||
-|-
-| 9 || Physical Appliance Hosted Services  || Ability to host a Service-Instance in a physical appliance  || Operator || Low|| M ||
-|}

Difference between revisions of "Tacker"