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
Team and repository tags
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:
- Tacker server: https://git.openstack.org/cgit/openstack/tacker
- Tacker Python client: https://git.openstack.org/cgit/openstack/python-tackerclient
- Tacker Horizon UI: https://git.openstack.org/cgit/openstack/tacker-horizon
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.