Red Hat Bugzilla – Bug 488137
change spacewalk to use cobbler_xmlrpc instead of cobbler_xmlrpc_rw
Last modified: 2009-09-17 03:10:48 EDT
This release contains numerous XMLRPC performance enhancements that will be very beneficial to spacewalk. XMLRPC now suffers no penalty for large configurations other than at cobblerd startup, in particular, and cobblerd is now one process instead of four. Anyway, I think I've mentioned this before, but Spacewalk /must/ be coded to know that the following XMLRPC endpoint is going away:
The correct process to connect to any version of cobbler is
connect first to http://cobbler.example.org/cobbler_xmlrpc
If the version call yields >=1.5, go ahead and login against the above URL
If that version is <1.5, log in to cobbler_xmlrpc_rw
(Please do not modify the Apache configuration to keep cobbler_xmlrpc_rw pointing to the old URL, and also do not connect to an XMLRPC port number directly as the users can change these ports)
Changing spacewalk code now to anticipate this release is recommended.
(There are no API changes, this only effects the endpoint)
Future versions of Spacewalk can just require Cobbler >= 1.6 and not have the code to look for the correct endpoint.
As far as I've been able to determine, spacewalk has been talking to cobbler via this url pattern:
"http://" + cobblerServer + ":" + cobblerServerPort + "/cobbler_api_rw";
I'm unsure if this is just some configuration thing we're doing when we set up cobbler or if you've mistyped the url in the bug specification - can you (or Paji) clarify?
Should be resolved in the next revision of cobbler
if cobbler_version > 1.6 => use cobbler_api , else use cobbler_api_rw
The following diff looks odd to me:
- return "http://" + cobblerServer + ":" + cobblerServerPort + "/cobbler_api_rw";
+ return "http://" + cobblerServer + ":" + cobblerServerPort;
Here you are no longer using the API endpoint, which you should be using.
Also, why not https:// ?
Moving to ON_QA
Spacewalk 0.5 released.
Spacewalk 0.5 has been released for long time ago.