openstack/tacker
Code Issues Proposed changes

Fix Tacker architecture image

Browse Source 
Current images do not keep up with the latest architectures.
I fixed architecture image in FM/PM.

Change-Id: If5ca63294ea2bdf6e8a08d6a88c64b8190f2bf6b
This commit is contained in:
Kenta Fukaya 2023-10-20 19:10:28 +09:00
parent 73b41001a5
commit bf292d5175
2 changed files with 1633 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1618
doc/source/_images/tacker-design.svg Executable file
View File

File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 164 KiB

27
doc/source/user/architecture.rst
View File

@ -4,32 +4,35 @@ Tacker Architecture
Tacker design can be described by the following diagram:
.. figure:: ../_images/tacker-design.png
.. figure:: ../_images/tacker-design.svg
:figwidth: 700 px
:align: left
:scale: 80 %
Packages:
* **python-tackerclient** - is the package for CLI and *REST API* calling.
* **tacker** - is the main package for Tacker project.
Components:
* **tacker-client** - provides CLI and communication with Tacker via
*REST API*.
* **server** - provides *REST API* and calls conductor via RPC.
* **conductor** - implements all logics to operate VNF and call required
* **tacker-conductor** - implements all logics to operate VNF and call required
drivers providing interface to NFV infrastructures.
* **infra-driver** - is responsible for exact actions to operate OpenStack or
Kubernetes resources.
* **VnfPm/VnfFmController** - is responsible for exact actions
to configure of PM/FM.
* **VnfLcmController** - is responsible for exact actions to
configure of LCM.
* **PrometheusPlugin** - is responsible for exact actions to
configure Prometheus.
* **vim-driver** - is responsible for registration of VIM.
* **mgmt-driver** - is responsible for exact actions to configure VNFs.
* **monitor-driver** - is responsible for exact actions to monitor VNFs.
* **policy-driver** - is responsible for policy based VNF operations.
* **VnfPm/VnfFmDriver** - is responsible for send notification to NFVO.
* **VnfLcmDriver** - is responsible for exact action to
mgmt driver or infra driver.
* **MgmtDriver** - is responsible for exact actions to configure VNFs.
* **InfraDriver** - is responsible for exact actions to operate OpenStack or
Kubernates.
Tacker Service
--------------