On 11/6/24 11:04, Frédéric Nass wrote:
...
You could enumerate all hosts one by one or use a pattern like 'ceph0[1-2]'
You may also use regex patterns depending on the version of Ceph that you're using. Check [1].
Regex patterns should be available in next minor Quincy release 17.2.8.
[1] https://github.com/ceph/ceph/pull/53803
[2] https://github.com/ceph/ceph/pull/56222
This simple wildcard scheme is called "globbing" and it's what is
typically used by Unix-style command shells.
It's convenient, but limited. For more subtlety you'd need a regex.
More generally, is there a higher level document that talks about Ceph spec
files and the orchestrator - something that deals with the general concepts?
I've submitted an outline on the issue tracker for a comprehensive and
coherent document on the creation and maintenance of OSDs.
Spec files, as I mentioned earlier, are YAML-format declarations of the
specifications to be applied to create or update one or more resources.
You can define spec files not only for OSDs, but for other Ceph
resources as well and I *think* a unified spec file for multiple
resource types.
By convention, any orchestrator command that can get its options from a
spec file will do so via the "-i {filename}" command line option. If
you put options on both the spec file and the orchestrator command line,
presumably the command line will take precedence, as that's the general
convention for such things. It may or may not warn you that it's doing
so, though.
Tim
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
