Bug 741898
Summary: | RFE: Ability to see active as well as proposed configuration | |||
---|---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Matthew Farrellee <matt> | |
Component: | condor-wallaby-tools | Assignee: | grid-maint-list <grid-maint-list> | |
Status: | CLOSED WONTFIX | QA Contact: | MRG Quality Engineering <mrgqe-bugs> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | medium | |||
Version: | Development | CC: | ltoscano, matt, mkudlej, rrati, tstclair, willb | |
Target Milestone: | --- | Keywords: | FutureFeature | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Enhancement | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 874939 874946 (view as bug list) | Environment: | ||
Last Closed: | 2016-05-26 19:13:15 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 802510 | |||
Bug Blocks: | 850563, 874939, 874946 |
Description
Matthew Farrellee
2011-09-28 12:03:07 UTC
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. |