Bug 1309480
| Summary: | Remote API is missing ability to retrieve and revert historic plug-in and resource configuration | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Larry O'Leary <loleary> | |
| Component: | CLI | Assignee: | Michael Burman <miburman> | |
| Status: | CLOSED WONTFIX | QA Contact: | Mike Foley <mfoley> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | JON 3.1.2 | CC: | fbrychta | |
| Target Milestone: | --- | |||
| Target Release: | One-off release | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1309481 (view as bug list) | Environment: | ||
| Last Closed: | 2018-09-13 15:01:11 UTC | Type: | Bug | |
| 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: | ||||
| Bug Blocks: | 1309481 | |||
Description of problem: ConfigurationManagerRemote interface does not expose a method to apply/revert configuration from configuration history/updates. This prevents a client from using the remote API to manage configuration for a resource and its connection settings based on prior configuration updates. Version-Release number of selected component (if applicable): 3.1.2 How reproducible: Always Steps to Reproduce: 1. Import a resource. 2. Make configuration changes. 3. Use the remote API to retrieve the resource's plug-in configuration updates: > // Get all plugin configuration updates for the Resource myResource > var myConnectionHistory = myResource.getPluginConfigurationUpdates(); Actual results: myConnectionHistory contains a list of ids but there is no way to get the configuration update record showing the date/time of the update along with who applied it and its status along with the actual Configuration object so that it can be reapplied to the resource. Expected results: myConnectionHistory should contain a list of PluginConfigurationUpdate which includes all the details of the update including Configuration. Additionally, it should be possible to pass a resource ID and configuration update ID to a method of ConfigurationManager to have the server reapply the desired configuration update. This would be similar to the Rollback function provided in the configuration history pages of the UI. Additional info: It appears that some/all of this functionality is exposed in the local interface so perhaps this is just a matter of moving local methods over to the remote interface.