Alain Barthe wrote:
xmlrpclib.Fault: <Fault 1: "cobbler.cexceptions.CX:'object has no
method: ks_meta'">
'ksmeta' is what you want.
With respect to questions about the XMLRPC interface, the best reference
you can possibly use is the code to CobblerWeb itself, which uses /only/
that interface. So whatever it does has to be correct :)
The driving source code is cobbler/webui/CobblerWeb.py
Perhaps it would be a good idea to define those names in only one
place
Sure. I understand. I wanted the XMLRPC calls to resemble the
command line options, not the internal storage, though this does cause
confusion when the results from the "get" calls return things like the
internal storage. However, preserving backwards compatibility and an
upgrade path is very important, so we won't be changing the YAML and the
existing XMLRPC calls need to continue to work as is.
Making the remote "edit" methods accept a few more variants on the
naming and making them a bit introspective is probably a good idea and
is something we can look into.
The Ruby XMLRPC module makes a layer on top of things to make it more
like a local API, which is a nice thing to do, so what we may do instead
is just create a similar layer in Python and let folks use that instead.
The Spacewalk developers I /think/ are also developing a Java-based API
wrapper.
--Michael