New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ceph-volume: ensure correct --filestore/--bluestore behavior #18518
Conversation
Signed-off-by: Alfredo Deza <adeza@redhat.com>
Signed-off-by: Alfredo Deza <adeza@redhat.com>
Signed-off-by: Alfredo Deza <adeza@redhat.com>
Signed-off-by: Alfredo Deza <adeza@redhat.com>
…or block and data Signed-off-by: Alfredo Deza <adeza@redhat.com>
Signed-off-by: Alfredo Deza <adeza@redhat.com>
Signed-off-by: Alfredo Deza <adeza@redhat.com>
…ot osd dir paths Signed-off-by: Alfredo Deza <adeza@redhat.com>
Signed-off-by: Alfredo Deza <adeza@redhat.com>
Signed-off-by: Alfredo Deza <adeza@redhat.com>
Catching more issues :( Latest problem (hopefully the last one) is that custom cluster names were causing OSDs not to start because they were looking for |
Signed-off-by: Alfredo Deza <adeza@redhat.com>
Signed-off-by: Alfredo Deza <adeza@redhat.com>
This is now good to be merged. I am adding the workarounds for ceph-bluestore-tool because the fixes for that tool aren't in master yet and I prefer to have this working and then consume the fixes later. @andrewschoen if you find anything else in here you want changed, let me know, otherwise this is good to move forward. |
jenkins test ceph-volume tox |
This fix makes it so that when
--filestore
is used, it is respected. Before it would always use--bluestore
which is not correct.Tags were also being polluted when using a journal (in filestore) and db or block in bluestore, keeping the last device set, which would cause the 'data' device being reported as 'db' or 'wal'.
Finally, the
prepare
api was using the old function signature for checking mounts which changed to require the caller to specify if checking for a path or a device.