Daryl Pierce indicated to me today that rubygem-cobbler is unmaintained and is not going to be keeping up with the new Cobbler versions as ovirt is not needing the new features.
As a result, I think there are several options (A) eliminate it altogether and those using it can use the XMLRPC APIs directly. (B) code-generate bindings from the source (I have started some work to do this for java, but results are TBD) (C) use something like Thrift for everything, and insert this between the XMLRPC layers and cobblerd (so the XMLRPC fork of cobblerd essentially just re-exposes what is available over Thrift, as a form of proxy-client to cobblerd). (D) find a new community owner for the package who wants to make it 2.0 compatible. In doing this, it should surface all cobbler objects and methods. I would generally think B and C might be better options in this case, but are non-trivial. I'm not going to be around to see this through, but thought it important to notify users of rubygem-cobbler, as it does appear in the listings when you do yum search. If we decide to eliminate this package, we should follow the Fedora process for orphaning and create the dead.package file and so forth. --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
