Hide Forgot
Description of problem: Calamari-lite runs on ceph Monitor nodes to provide a REST API for ceph Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
API is documented here https://github.com/ceph/mariner-installer/#calamari
Is this the same calamari that will handle registering nodes with USM during bootstrapping? I believe there was a requirement to have an agent installed on newly provisioned nodes that would register them with USM.
*** Bug 1213082 has been marked as a duplicate of this bug. ***
I believe this is something we'll need to add to ceph-ansible. Are there docs somewhere for installing calamari-lite? Where will we get packages for calamari-lite? Do we need to configure calamari-lite in any way to get it to talk with USM?
Greg, in order to continue with this one we need a bit more of information. "calamari-lite" (now known as the "agent") needs to be installed in the target nodes but: * what are those packages named? both for Ubuntu and RHEL * are the requirements for configuration the same as `ceph-deploy calamari connect` ? If so, the installer needs to know where is the master * if the configuration for the agent is any different from `ceph-deploy calamari connect` we need to know what parts are so we can address them
the rhscon-agent will be configured as calamari was in ceph-deploy assume that the ceph-installer and USM will be hosted on the same FQDN for now
Pull Request that implements the API endpoint: https://github.com/ceph/ceph-installer/pull/42
Pull request in ceph-ansible that allows installing and initializing calamari-server on a monitor: https://github.com/ceph/ceph-ansible/pull/614
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions
Checked with ceph-installer-1.0.11-1.el7scon.noarch and it works. Calamari runs only on one monitor. ->Verifed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2016:1754