Hi Alan, In short; i agree with all your points and would be VERY happy to merge your changes.
I have been discussing exactly these kind of changes with some SuSE people. They use Cobbler in the SuSE Manager product, whereas Red Hat has dropped Cobbler in their latest version of Satellite Server product. It makes a lot of sense to re-position Cobbler as a generic deployment tool and drop all Red Hat'isms. The master branch is the place (which will be 3.0) to do it, also you don't have to worry about breaking compatibility too much (it just needs to be documented in the changelog). Thanks! On Mon, Sep 8, 2014 at 12:18 AM, Alan Evangelista <ala...@linux.vnet.ibm.com > wrote: > I see some terms used in Cobbler which were probably created a long time > ago and are > currently outdated. I'd like to suggest renamings which would make names > reflect better > current code. Examples: > > - "kickstart" is commonly used in Cobbler to refer to the file which is > used by Linux installers > to automate Linux installation and configuration. Cobbler supports Debian, > Suse and Red Hat based > distros. However, "kickstart" term is exclusive to Red Hat based distros, > Suse based distros use > "autoyast" and Debian based distros use "preseed". A generic term (eg > auto-installation file) > would prevent confusion. > > - BootAPI and BootCLI are not intuitive names. It seems Cobbler is limited > to managing network > boot. I think CobblerAPI and CobblerCLI are better names. > > - I'd expect that PXEGen class would handle all PXE (DHCP + TFTP) files. > However, it builds mainly > boot loader configuration files and files which will be copied to TFTP > server in a Cobbler server, > it does not build DHCP conf file. Also, Cobbler currently support archs > which do not use PXE, > such as Power. I'd rename this to TFTPGen. > > - Config class manages collections of Cobbler objects (system, profile, > distro, etc.). Config is > already used in several different contexts in Cobbler, such as Cobbler > config file, DHCP config file, > boot loader config file, etc. It takes a while to figure out that > system/profile/distro data created > by user is maintained by this class. I think that CollectionManager or > something similar would be more > intuitive. > > - cobbler/modules/serializer_catalog.py serializes/deserializes objects > to/from files. Catalog is a > generic term which does not add much. Renaming to serializer_file would > make this much easier to understand. > > I have already implemented most of these changes in my customized Cobbler. > If the ideas are welcome, > I could apply them in upstream code and submit patches. > > > Regards, > Alan Evangelista > > _______________________________________________ > cobbler-devel mailing list > cobbler-devel@lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/cobbler-devel > -- Grtz, Jörgen Maas
_______________________________________________ cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler-devel
