On Wed, May 23, 2012 at 2:00 AM, Amon Ott <a.ott@xxxxxxxxxxxx> wrote: > So I started experimenting with the new "cluster" variable, but it does not > seem to be well supported so far. mkcephfs does not even know about it and > always uses "ceph" as cluster name. Setting a value for "cluster" in global > section of ceph.conf (homeuser.conf, backup.conf, ...) does not work, it is > not even used in the same config file, instead it has the fixed value "ceph". "cluster" is not meant to be set in the config file; that's too late, the config file is read from /etc/ceph/$cluster.conf. Instead, you pass in --cluster=foo, and that is early enough to influence what config file is read. The --cluster argument will be more useful with the new-style Chef deployment. All the new daemon running infrastructure will already happily run osds and mons from multiple cluster, even though several locations still have "ceph" hardcoded, just due to time pressure. I don't think anyone is likely to fix mkcephfs to work with it -- I'm personally trying to get mkcephfs declared obsolete. It's fundamentally the wrong tool; for example, it cannot expand or reconfigure an existing cluster. -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
