On Fri, Nov 4, 2011 at 6:21 PM, Greg Swift <gregswift@gmail.com> wrote:


On Fri, Nov 4, 2011 at 12:47, Gerhardus Geldenhuis <gerhardus.geldenhuis@gmail.com> wrote:
Hi

As of version 2.0, BootAPI is not the recommended way of interfacing with Cobbler. It directly modifies the config store in a way that may not be safe. Furthermore the modifications made will not be visible to cobblerd. The CobblerXmlrpc interface should instead be used until at least version 2.2.

Is this still true? Or can we use BootAPI now?

This is still true.

Damm, I was hoping this had changed.
 
 
Is there anyway to get error messages back when using xmlrpc? The https://fedorahosted.org/cobbler/wiki/CobblerXmlrpc page references https://fedorahosted.org/cobbler/wiki/CobblerExceptions but it does not exist any more. I want to know if actions were successful or not. I suspect error checking is better done with the api hence my question.

I'm not sure personally.  I want to say I saw errors that I could deal with when using the xmlrpc, I just don't recall the format.  I just pulled a small snippet that is the only error checking I did against the xmlrpc.  here it is:

           try:
                cobbler.modify_system(sysid, 'modify_interface', int, token)
            except xmlrpclib.Fault, e:
                print "system %s errored trying to add %s interface"  % (system, interface)
                print e

not great, but hopefully it helps.

No, that is awesome thanks I will give it a go and see if I can get the error to trigger. So far it is either successful in adding a server or it just does nothing.

 
 
One last novice question, does the api only run on the same server as cobbler or can I use the api to access a remote cobbler server?

The API should be remotely accessible.


That is useful but since the API is not the recommended way I am going to steer clear for now and make do with xmlrpc.

Best Regards
 
--
Gerhardus Geldenhuis