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: major batch refactor #34740
Conversation
|
jenkins test docs |
cbbd9f8
to
7f0f8c0
Compare
7f0f8c0
to
e523d64
Compare
f79fabc
to
63b0e8a
Compare
63b0e8a
to
a1b8cac
Compare
Signed-off-by: Joshua Schmid <jschmid@suse.de>
b7855f0
to
de8f034
Compare
e86004a
to
6d746d6
Compare
f6ce9f9
to
6ba8195
Compare
|
jenkins test ceph-volume tox |
|
jenkins test ceph-volume all |
38d109c
to
9920e6f
Compare
yes, in that case maybe it's not really relevant, I was more speaking about how I think it should be from a more general point of view. |
Signed-off-by: Jan Fajerski <jfajerski@suse.com>
Some device we never want to pass to the batch subcommand. For now this includes devices that have a partition or are mounted on the machine. One goal is to filter the root device, so it is not included on a batch command and thus would contribute to its implicit sizing calculation. Signed-off-by: Jan Fajerski <jfajerski@suse.com>
This enables user to pass sizes like "10G", which batch now understands. Signed-off-by: Jan Fajerski <jfajerski@suse.com>
Signed-off-by: Jan Fajerski <jfajerski@suse.com>
Signed-off-by: Jan Fajerski <jfajerski@suse.com>
5b347b3
to
8178d5c
Compare
|
Alright, I added the missing output in the doc. One last round of tests and unless someone has objections I'll merge this. |
|
jenkins test ceph-volume all |
|
jenkins test ceph-volume tox |
With ceph#34740 ceph-volume is now idempotent. We now assemble the device set based on the drivegroups in mgr/cephadm (regardless of their availability) and pass it to c-v. This is the missing piece to actually do this. related changes: ceph@7d168ad Signed-off-by: Joshua Schmid <jschmid@suse.de>
With ceph#34740 ceph-volume is now idempotent. We now assemble the device set based on the drivegroups in mgr/cephadm (regardless of their availability) and pass it to c-v. This is the missing piece to actually do this. related changes: ceph@7d168ad Signed-off-by: Joshua Schmid <jschmid@suse.de>
The ceph-volume lvm batch --auto introduced by [1] breaks the backward compatibility when using non rotational devices only (SSD and/or NVMe). Those devices are reaffected as bluestore db or filestore journal devices while we want them as data devices. Fixes: https://tracker.ceph.com/issues/48106 [1] ceph#34740 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
The ceph-volume lvm batch --auto introduced by [1] breaks the backward compatibility when using non rotational devices only (SSD and/or NVMe). Those devices are reaffected as bluestore db or filestore journal devices while we want them as data devices. Fixes: https://tracker.ceph.com/issues/48106 [1] ceph#34740 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
The ceph-volume lvm batch --auto introduced by [1] breaks the backward compatibility when using non rotational devices only (SSD and/or NVMe). Those devices are reaffected as bluestore db or filestore journal devices while we want them as data devices. Fixes: https://tracker.ceph.com/issues/48106 [1] ceph#34740 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
The ceph-volume lvm batch --auto introduced by [1] breaks the backward compatibility when using non rotational devices only (SSD and/or NVMe). Those devices are reaffected as bluestore db or filestore journal devices while we want them as data devices. Fixes: https://tracker.ceph.com/issues/48106 [1] ceph#34740 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
The ceph-volume lvm batch --auto introduced by [1] breaks the backward compatibility when using non rotational devices only (SSD and/or NVMe). Those devices are reaffected as bluestore db or filestore journal devices while we want them as data devices. Fixes: https://tracker.ceph.com/issues/48106 [1] ceph#34740 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com> (cherry picked from commit 2a854ca)
The ceph-volume lvm batch --auto introduced by [1] breaks the backward compatibility when using non rotational devices only (SSD and/or NVMe). Those devices are reaffected as bluestore db or filestore journal devices while we want them as data devices. Fixes: https://tracker.ceph.com/issues/48106 [1] ceph#34740 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com> (cherry picked from commit 2a854ca)
The ceph-volume lvm batch --auto introduced by [1] breaks the backward compatibility when using non rotational devices only (SSD and/or NVMe). Those devices are reaffected as bluestore db or filestore journal devices while we want them as data devices. Fixes: https://tracker.ceph.com/issues/48106 [1] ceph#34740 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com> (cherry picked from commit 2a854ca)
The ceph-volume lvm batch --auto introduced by [1] breaks the backward compatibility when using non rotational devices only (SSD and/or NVMe). Those devices are reaffected as bluestore db or filestore journal devices while we want them as data devices. Fixes: https://tracker.ceph.com/issues/48106 [1] ceph#34740 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com> (cherry picked from commit 2a854ca)
The ceph-volume lvm batch --auto introduced by [1] breaks the backward compatibility when using non rotational devices only (SSD and/or NVMe). Those devices are reaffected as bluestore db or filestore journal devices while we want them as data devices. Fixes: https://tracker.ceph.com/issues/48106 [1] ceph#34740 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com> (cherry picked from commit 2a854ca)
The ceph-volume lvm batch --auto introduced by [1] breaks the backward compatibility when using non rotational devices only (SSD and/or NVMe). Those devices are reaffected as bluestore db or filestore journal devices while we want them as data devices. Fixes: https://tracker.ceph.com/issues/48106 [1] ceph#34740 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
|
I just experienced the following error with |
@haslersn could you paste the exact command you tried to run? |
This is a major rewrite of batch in order to use the create/prepare code path and significantly simplify this subcommands code. Simultaneously this adds support for vg re-use, idempotency, use of LVs with batch and additional implicit sizing arguments.
This also closes a number of bugs and unblocks other work in cephadm and rook.
Fixes: https://tracker.ceph.com/issues/24969
Fixes: https://tracker.ceph.com/issues/36242
Fixes: https://tracker.ceph.com/issues/36283
Fixes: https://tracker.ceph.com/issues/37502
Fixes: https://tracker.ceph.com/issues/37590
Fixes: https://tracker.ceph.com/issues/38168
Fixes: https://tracker.ceph.com/issues/42412
Fixes: https://tracker.ceph.com/issues/43899
Fixes: https://tracker.ceph.com/issues/44749
Fixes: https://tracker.ceph.com/issues/44783
Fixes: https://tracker.ceph.com/issues/44951
Fixes: https://tracker.ceph.com/issues/46031
Fixes: https://tracker.ceph.com/issues/46033
Signed-off-by: Jan Fajerski jfajerski@suse.com
Some things are still TODO