Go to file
dharmendra c71ca9a01e replace the class path uuid based stack names with vnf names
Tacker uses the class path+file name+uuid as stack names to
uniquely identify the stacks for vnf create and vnf respawn workflow.
Tacker now mandates VNF names to be provided in API layer and will be
made unique. It is useful to base stack names based on vnf names for
debugging purposes. This affects the naming of nova instances as well.

Change-Id: If043ad8c6c356f3fa1d2f5648d3d861ff5006602
Closes-Bug: #1590215
2018-01-23 08:35:01 +00:00
2017-11-04 22:09:42 +11:00
2017-11-04 22:09:42 +11:00
2016-04-21 06:08:06 +00:00
2017-08-17 00:09:33 +08:00
2015-10-17 22:40:44 +00:00
2017-06-13 06:53:07 +00:00
2017-08-03 15:32:57 +08:00
2017-03-08 05:28:05 +00:00
2017-02-23 16:11:52 +07:00
2017-11-04 22:09:42 +11:00

Team and repository tags

image

Welcome!

Tacker is an OpenStack based NFV Orchestrator service with built-in 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.

Installation:

Installation instructions: https://wiki.openstack.org/wiki/Tacker/Installation

Tacker code base now supports OpenStack master and kilo releases. Please follow the instructions in the above wiki for a successful installation of corresponding release.

Code:

Tacker code is available in following repositories:

Bugs:

Please report bugs at: https://bugs.launchpad.net/tacker

External Resources:

Tacker Wiki: https://wiki.openstack.org/wiki/Tacker

For help on usage and hacking of Tacker, please send mail to <mailto:openstack-dev@lists.openstack.org> with [Tacker] tag.

Description
Tacker: ETSI MANO NFV Orchestrator / VNF Manager. See https://wiki.openstack.org/wiki/Tacker
Readme 148 MiB
Languages
Python 99.2%
Shell 0.7%