Red Hat Bugzilla – Bug 741898
RFE: Ability to see active as well as proposed configuration
Last modified: 2016-05-26 15:13:15 EDT
Two important states in the wallaby database are the active configuration (currently deployed and running) and the proposed configuration (config being built, not yet activated).
The condor_configure_* tools only report the proposed configuration. For instance, condor_configure_pool -l -n node0 will display the configuration that would be active after the next --activate, not what is currently deployed on node0.
RFE is to add the ability to see the active configuration.
The most recently activated configuration (i.e. a set of name-value pairs) for each node is available via the API, but the tools will probably need special API support if we're interested in getting more detailed information (e.g. group memberships and feature applications for the active configuration).
Is this for wallaby do-foo commands and also for condor_configure_pool -something?
Will the initial implementation be only for node configuration or also the "more detailed information" (#1)?
We can get some, but not all, of the "more detailed information" right now. (That is, we can get group memberships for active configurations, but not feature applications for these groups.) We also have API access to the list of entities that have been modified since the last successful activation. So we could fairly trivially have a tool that shows the active configuration. We could also have a tool that shows, for each modified node, how the low-level configuration has changed between the active and proposed configurations.
I believe that the best way to proceed is to have a wallaby shell command that handles these cases and not to build additional machinery into CCS/CCP, but Rob may have thoughts about this as well.
I agree with will here. There may be some additional flags that might be required in the ccs/ccp relm, but wallaby shell commands to complete the task is the route to take.
MRG-G is in maintenance only and only customer escalations will be addressed from this point forward. This issue can be re-opened if a customer escalation associated with this issue occurs.