Description of problem:
One of the necessary parameters in needed to configure the Ceph backend is missing from the hostgroup parameters:
As described in the page http://ceph.com/docs/next/rbd/rbd-openstack/ the cinder backup need to use the cinder-backup client keyring file, located in /etc/ceph/ .
Version-Release number of selected component (if applicable):
There's a parameter for ceph password
Right now, staypuft/astapor does not configure *anything* under /etc/ceph (like keyrings). There are RFE's filed for puppet management of that directory and its contents. Additionally, staypuft/astapor does not configure the cinder-backup service.
Closing based on the above. ceph configuration is external to staypuft at the current time
I've been asked to check staypuft's cinder and glance with Ceph backend.
Ceph option added on current release great but still missing Ceph parameters. Hence can't check staypuft's configuration of Ceph for Cinder\Glance, adding blocker.
All ceph parameters for cinder and glance are defaulted and available in the advanced configuration. There are not required parameters to be exposed in the standard wizard.
As stated in comment 1, cinder-backup is not configured/supported at this time.
Can we get doc_text for the present use of ceph-deploy to populate config values?
I'm not sure how to do this. Passing on the needinfo to Neil.
When I added a compute node (which is not a ceph mon node), I used "ceph deploy install" to install the needed packages (we won't need to do this anymore when the astapor puppet manifests install the packages; the PR for that is already merged). Then, I copied/rsync'ed the entirety of the /etc/ceph/ dir from one of the existing ceph cluster nodes. I couldn't see from the documentation of ceph-deploy how to copy over the needed config files to be sure that /etc/ceph/ceph.conf, ceph.client.images.keyring, and ceph.client.volumes.keyring were created on the compute node.
Mike, I disagree, the Ceph basic configurations for Glance and Cinder require these parameters. Administrators would need to know what they need to provide them in order to work with Ceph, without additional post installation configurations.
(In reply to Yogev Rabl from comment #8)
> Mike, I disagree, the Ceph basic configurations for Glance and Cinder
> require these parameters. Administrators would need to know what they need
> to provide them in order to work with Ceph, without additional post
> installation configurations.
Ceph configuration supported in this release is very limited. All other configuration that is needed outside of what is available in advanced configuration must be done separate from RHEL-OSP Installer.
Just saw that this is still open.
As Puppet is creating the client keyrings and ceph.conf, the assupmtion was that Puppet would be responsible for copying these to the compute nodes as well as the controller. Can you confirm this is what has been implemented for A2?
Crag, can you confirm this is all set in A2?
Confirmed that puppet creates the client images and volumes keyring files on the controller and compute nodes. Note this has nothing to do the with the subject of this BZ, cinder-backup, which we are not configuring.
Closing list of bugs for RHEL OSP Installer since its support cycle has already ended . If there is some bug closed by mistake, feel free to re-open.
For new deployments, please, use RHOSP director (starting with version 7).
-- Jaromir Coufal
-- Sr. Product Manager
-- Red Hat OpenStack Platform