On Thu, Apr 7, 2011 at 12:16 AM, Garrett Holmstrom <gho...@fedoraproject.org> wrote: > That sounds reasonable to me; being able to use a full-blown RDBMS would > likely cause tremendous performance and ease of maintenance > improvements. However, if Cobbler starts using a DB to store things I > would like to see it support sqlite or another really low-maintenance DB > to help keep things simple in the default case. Cobbler should be easy > to pick up and use.
Ideally, we would have multiple DB backends. One thought would be to use django's DB abstraction layer for the object storage, however that would have major implications. I don't think we could ever get rid of XMLRPC, as I'm assuming spacewalk/RHN use that as the interface to manage cobbler. > The problem with dependency bloat is that there are more things in the > stack below Cobbler that can go awry as things get updated or ported to > more distros. On the other hand, if having cobbler and cobbler-web use > separate web stacks makes things too difficult to maintain then adding > more external dependencies may be the better option. I can't really > give much of an opinion with regard to the web UI because of how little > I have used it. Things used to be split, and it was way worse - maintainability went up by an order of magnitude when we made the CLI an interface to cobblerd instead of being a standalone code base. It used to be that features were added to the CLI rapidly with the webui a complete afterthought. Now with the field list structures and generic list/edit, adding features is relatively easy. _______________________________________________ cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
