Since the default OSD is no longer created under dataDirHostPath,
the most common issue in the 1.0 release is that users don't have OSD
created in the cluster. Now the quickstart doc will guide users to
create a test cluster to get them going with a filestore OSD in
a directory, with clear guidance that this is not expected in production
Signed-off-by: travisn <tnielsen@redhat.com>
- Updated code to use deviceClass property when a pool is created for both "replicated" and "erasure code".
- Updated "ceph crush rule create-..." command to use "create-replicated" instead of "create-simple"
- Updated unit tests
- Updated (ceph-pool-crd.md) documentation to reflect the changes.
- Updated pending release notes.
Signed-off-by: Santosh Pillai <sapillai@redhat.com>
This corrects the cleanup instructions to delete operator.yaml but also
common.yaml to remove the reamining objects in one go.
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
The default mon port has changed from 6790 to 6789. With the msgr2 work in nautilus,
the mons need to be listening on the default ports. These instructions will
direct the users to failover the mons to the new default port.
Signed-off-by: travisn <tnielsen@redhat.com>
* Remove redundant hint to create namespace, role, and role bindings
(already noted before)
* Refer to node settings under cluster `nodes` setting
Signed-off-by: Timoses <timosesu@gmail.com>
The alpha, beta, and stable channels do not match the rook release process.
Each storage provider defines their own stability based on the CRDs
rather than defining it with the release process. Rook really
only has two release streams: master and the official releases.
Master is published with each merge, while releases go through
a signoff process to ensure quality. Thus, the alpha, beta,
and stable channels are removed and replaced with a
single release channel.
Signed-off-by: travisn <tnielsen@redhat.com>
Signed-off-by: Ashish Ranjan <ashishranjan738@gmail.com>
This commit removes one to one mapping of NFS provisioner and adds a dedicated provisioner for nfs.
The CephCluster CR contains settings that are needed by other
CRs to configure the Ceph daemons. When the CephCluster CR
is updated, the updates will now be passed on to each of the
CR controllers to ensure the daemons are updated properly
without requiring an operator restart.
When calling the controllers from another controller,
we ensure that only a single goroutine is handling
CRs at any given time to prevent contention across
multiple CRs of the same type.
Signed-off-by: travisn <tnielsen@redhat.com>
Adding a raw tag wrapper tells liquid to ignore this section and compile
this text without trying to interpret it. Otherwise an error is thrown
during builds
Signed-off-by: Steven Rathbauer <steven@rathpc.com>