Bug 1365495
| Summary: | RPC interface to dump and load BRE rules | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Romana Cadova <rcadova> |
| Component: | Internal Tools | Assignee: | Matt Tyson 🤬 <mtyson> |
| Internal Tools sub component: | Rules Engine | QA Contact: | tools-bugs <tools-bugs> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | agk, huiwang, mtyson, qgong, rcadova |
| Version: | 4.4 | ||
| Target Milestone: | 4.4 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-28 02:17:26 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: | |||
|
Description
Romana Cadova
2016-08-09 11:50:17 UTC
We discussed this problem with Ludek in a bluejeans meeting yesterday. The way to go here is to create an RPC interface that would allow you to download rules from one server and upload them to another. Your team can then write scripts against this RPC interface to keep partner and production in sync. You can create and test your rule on partner-bugzilla, and once you are satisfied with it, use the RPC interface to copy a rule from partner into production. Proposed RPC calls: - RuleEngine.list Return a list of available rules, their IDs, names, enabled state etc. - RuleEngine.create Create a new rule. - RuleEngine.update Update the definition or name of an existing rule. Also enable or disable a rule. - RuleEngine.get Fetch the definition of a rule. The output of this RPC call can then be fed into the create or update functions, allowing rules to be copied between systems. For the present I'm still envisioning rules being created through the web interface and then copied about via RPC. Manually handcrafting rules through RPC might be possible. It would require documenting the internal rule format, or creating a stable API to that format. This could be done as a future task if required. Romana, Would this solve the problems you are having? QE can't verify this bug as pass, since exist bug 1377194 1377192 > Actual results:
> xmlrpclib.Fault: <Fault 50: 'The function requires a rules argument, and that argument was not set.'>
The documentation for the RuleEngine.create function is wrong.
result = proxy.RuleEngine.update({'name':'test-qq', 'login': 'qgong', 'password': '******', 'id':262})
Actual results:
xmlrpclib.Fault: <Fault 50: 'The function requires a id argument, and that argument was not set.'>
The docs for the RuleEngine.update function is also telling lies.
Tested on QA environment(4.4.12059-2) Result: Pass Steps： 1.Could list, get, create and update rule engine by api now. This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug. |