summaryrefslogtreecommitdiffstats
path: root/docs/development/overview/containerized_compass.rst
blob: 1df570d7489a6fa4373f9d58810168f6dfc95e16 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) by Justin Chi (HUAWEI) and Yifei Xue (HUAWEI)

Introduction of Containerized Compass
=====================================

Containerized Compass uses five compass containers instead of a single VM.

Each container stands for a micro service and compass-core function separates into these five micro services:

        - Compass-deck : RESTful API and DB Handlers for Compass
        - Compass-tasks : Registered tasks and MQ modules for Compass
        - Compass-cobbler : Cobbler container for Compass
        - Compass-db : Database for Compass
        - Compass-mq : Message Queue for Compass

Compass4nfv has several containers to satisfy OPNFV requirements:

        - Compass-tasks-osa : compass-task's adapter for deployment OpenStack via OpenStack-ansible
        - Compass-tasks-k8s : compass-task's adapter for deployment Kubernetes
        - Compass-repo-osa-ubuntu : optional container to support OPNFV offfline installation via OpenStack-ansible
        - Compass-repo-osa-centos : optional container to support OPNFV offfline installation via OpenStack-ansible

Picture below shows the new architecture of compass4nfv:

.. figure:: images/compass_arch.png
    :alt: New Archietecture of Compass4nfv
    :figclass: align-center

    Fig 1. New Archietecture of Compass4nfv