Change Details

In much the same way that `pacemaker-schedulerd metadata` shows cluster options, we should have a command-line method of showing all possible meta-attributes with descriptions and value types. Meta-attributes are accepted for alert, primitive, group, clone, bundle, operation, rsc_defaults, and op_defaults. `crm_resource` would be a reasonable place to put the new option, maybe `--list-meta [context]`. Currently, we do not collect this information anywhere (though //Pacemaker Explained// is the closest to being definitive, other than the source code). * [[https://bugzilla.redhat.com/show_bug.cgi?id=2163699 | RHBZ#2163699]]

The controller and scheduler both take a `metadata` command-line argument to output OCF-like metadata for the cluster options that they use. This has a few problems: both have to be run to see all options, options that they both use are in both sets of metadata, and a couple options are used only by the CIB manager (which doesn't have a metadata argument; see `cib_opts`) and so aren't listed in either. Pacemaker currently doesn't even have that much information for the environment variables or meta-attributes that it supports. `etc/sysconfig/pacemaker` documents most but not all of the environment variables, and isn't available in a convenient OCF-like form from the command-line. Pacemaker accepts meta-attributes for alert, primitive, group, clone, bundle, operation, rsc_defaults, and op_defaults. //Pacemaker Explained// documents most but not all of them, and again isn't available in a parseable form. `crm_attribute` would be a reasonable place to put new command-line options for this, maybe `--list-options`, `--list-environment`, and `--list-meta [context]`, or maybe a single `--list-options [type]` argument. They should support both text and XML output, with the XML being OCF-like. Feel free to separate out subtasks for this * [[https://bugzilla.redhat.com/show_bug.cgi?id=2163699 | RHBZ#2163699]] * [[https://bugzilla.redhat.com/show_bug.cgi?id=2182383 | RHBZ#2182383]]

In much the same way that `pacemaker-schedulerd metadata` shows cluster options,The controller and scheduler both take a `metadata` command-line argument to output OCF-like metadata for the cluster options that they use. This has a few problems: both have to be run to see all options, options that they both use are in both sets of metadata, and a couple options are used only by the CIB manager (which doesn't have a metadata argument; we should have a command-line method of showing all possible meta-attributes with descriptions and value typessee `cib_opts`) and so aren't listed in either. Meta-attributes are accepted for alert, primitive, group, clone, bundle, operation, rsc_defaults, and op_defaults. `crm_resource` would be a reasonable place to put the new option, maybe `--list-meta [context]`Pacemaker currently doesn't even have that much information for the environment variables or meta-attributes that it supports. Currently,`etc/sysconfig/pacemaker` documents most but not all of the environment variables, and isn't available in a convenient OCF-like form from the command-line. Pacemaker accepts meta-attributes for alert, primitive, group, clone, bundle, operation, rsc_defaults, and op_defaults. //Pacemaker Explained// documents most but not all of them, and again isn't available in a parseable form. `crm_attribute` would be a reasonable place to put new command-line options for this, maybe `--list-options`, `--list-environment`, and `--list-meta [context]`, or maybe a single `--list-options [type]` argument. we do not collect this information anywhere (though //Pacemaker Explained// is the closest to being definitiveThey should support both text and XML output, other than the source code).with the XML being OCF-like. Feel free to separate out subtasks for this * [[https://bugzilla.redhat.com/show_bug.cgi?id=2163699 | RHBZ#2163699]] * [[https://bugzilla.redhat.com/show_bug.cgi?id=2182383 | RHBZ#2182383]]