Device and Service manager
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
OpenDev Sysadmins 0eccb6c497 OpenDev Migration Patch 1 month ago
doc/source Initial Cookiecutter Commit. 3 years ago
etc config file update 3 years ago
namos re-factored the processor 3 years ago
.coveragerc Initial Cookiecutter Commit. 3 years ago
.gitignore Initial Cookiecutter Commit. 3 years ago
.gitreview OpenDev Migration Patch 1 month ago
.mailmap Initial Cookiecutter Commit. 3 years ago
.testr.conf Initial Cookiecutter Commit. 3 years ago
CONTRIBUTING.rst Initial Cookiecutter Commit. 3 years ago
HACKING.rst Initial Cookiecutter Commit. 3 years ago
LICENSE Initial Cookiecutter Commit. 3 years ago
MANIFEST.in Initial Cookiecutter Commit. 3 years ago
README.rst Correct the namos-api port number 3 years ago
babel.cfg Initial Cookiecutter Commit. 3 years ago
config-generator.conf deployment node type 3 years ago
requirements.txt rpc layer 3 years ago
setup.cfg re-factored the processor 3 years ago
setup.py Initial Cookiecutter Commit. 3 years ago
test-requirements.txt Initial Cookiecutter Commit. 3 years ago
tox.ini Cleanup tox.ini: Remove obsolete constraints 2 years ago

README.rst

namos - OpenStack manager

Features

  • Automatic discovery of OpenStack deployment architecture

How to setup db

  • create the 'namos' db using below command

    create database namos

  • update database.connection in /etc/namos/namos.conf with db username and password
  • Run the below command to sync the namos schema

    namos-manage create_schema

How to setup namos

  • Assume, namos is cloned at /opt/stack/namos, then run below command to install namos from this directory.

    sudo python setup.py install

How to run namos

  • namos-api - Namos API starts to listen on port 9999. Now it does have support for keystone authendication

    namos-api

  • namos-manager - Namos backend service, to configured the number of workers, update os_manager->workers

namos-manager --config-file=/etc/namos/namos.conf

NOTE: Before running the namos-manager, please add os-namos agent in the console scripts of respective service components.

To find the 360 view of OpenStack deployment

Run http://localhost:9999/v1/view_360

It provides 360 degree view under region->service_node in the response. In addition, gives the current live status of each servicec components.

To find the status of components

Run the below command

namos-manage status

NOTE: This command supports to query status based on given node name, node type , service and component. To find more details run this command with --help