Include the URL of your launchpad blueprint:
We would like to develop a plugin to install Calamari in the next release of Fuel (7.0). Calamari is a management and monitoring service for Ceph. Calamari is composed by monitoring agents, a server-side and a client-side components.
In more depth Calamari consists of three major components:
In this section we describe the main steps that a user should perform for installing Calamari. We suppose that:
We would like develop a new Fuel plugin in order to install Calamari . Our proposal considers the following aspects:
The default admin user name and password for the web interface will be configured in the setting tab of the Fuel UI.
In the Fuel UI will be possible to allow the deploy of the REST API and web application on the public network.
There will be a deployment successful message displaying the text pointing to the URL of the web application.
We can also add some info to the Post Deployment Dashboard once it is implemented.
In the source tree of calamari there are Vagrantfile and scripts to build the packages for Ubuntu 14.04, Centos and RHEL.
There is a guide on building packages.
The agent impact on Ceph servers and on the network should be negligible.
Task description: write a puppet module in order to install Calamari server and configure properly all nodes to monitor.
Assignees: Alessandro Martellone, Daniele Pizzolli.
Task description: include in the plugin repositories the required packages.
Assignees: Dmytro Iurchenko, Alessandro Martellone, Daniele Pizzolli.
Nice to have, but not essential:
- Diamond  and salt-minion services are installed and running on all OSD and Controller nodes.
- Salt-master is installed and running on the node named ‘calamari’ and salt-keys command lists all OSD and Controller node hosts in ‘Accepted Keys’ section.
- Calamari REST API is available on the node named ‘calamari’ .
- User can authenticate via REST API .
- The cluster description provided by Calamari REST API  is correct.
- Calamari UI is available on ‘calamari’ node on HTTP default port.
None. It will be a Fuel plugin with its own documentation.