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.
Yes, the fact that attribute names are different when you write them is very confusing, and I think that every people using the XMLRPC API fall into the trap. Maybe a big WARNING in the wiki or in the doc would save time for future users.
Thanks for your reply and for developing Cobbler.
--Michael