A typical Cobbler install looks something as follows. Note that in general Cobbler manages its own directories. Editing templates and configuration files is intended. Deleting directories will result in very loud alarms. Please do not ask for help if you decide to delete core directories or move them around.
See Relocating Your Installation if you have space problems.
All Cobbler logs go here. Cobbler does not dump to /var/log/messages, though other system services relating to netbooting do.
This is a Cobbler owned and managed directory for serving up various content that we need to serve up via http. Further selected details are below. As tempting as it is to self-garden this directory, do not do so. Manage it using the "cobbler" command or the Cobbler web app.
Here is where the mod_python web interface and supporting service scripts live for Cobbler pre 2.0
Here is where content for the (pre 2.0) webapp lives that is not a template. Web templates for all versions live in /usr/share/cobbler.
This is used to serve up certain scripts to anaconda, such as anamon (See Anaconda Monitoring for more information on anamon).
This is where the mod_wsgi script for Cobbler lives.
Kernel and initrd files are copied/symlinked here for usage by koan.
Install trees are copied here.
Cobbler repo objects (i.e. yum, apt-mirror) are copied here.
This is the main data directory for Cobbler. See individual descriptions of subdirectories below.
Here Cobbler stores configuration files that it creates when you make or edit Cobbler objects. If you are using serializer_catalog in modules.conf, these will exist in various ".d" directories under this main directory.
This is a backup of the config directory created on RPM upgrades. The configuration format is intended to be forward compatible (i.e. upgrades without user intervention are supported) though this file is kept around in case something goes wrong during an install (though it never should, it never hurts to be safe).
This is where Cobbler's shipped kickstart templates are stored. You may also keep yours here if you like. If you want to edit kickstarts in the web application this is the recommended place for them. Though other distributions may have templates that are not explicitly 'kickstarts', we also keep them here.
This is where Cobbler keeps snippet files, which are pieces of text that can be reused between multiple kickstarts.
Various user-scripts to extend Cobbler to perform certain actions can be dropped into subdirectories of this directory. See the Triggers section for more information.
This is where the cobbler-web package (for Cobbler 2.0 and later) lives. It is a Django app.
Here we keep the templates for the various power management modules Cobbler supports. Please refer to the Power Management section for more details on configuring power management features.
Various templates related to netboot installation, not neccessarily "pxe".
If the chosen DNS management module for DNS is BIND, this directory is where templates for each zone file live. dnsmasq does not use this directory.
Templates for various reporting related functions of Cobbler, most notably the new system email feature in Cobbler 1.5 and later.
The source code to Cobbler lives here. If you have multiple versions of python installed, make sure Cobbler is in the site-packages directory for the correct python version (you can use symlinks to make it available to multiple versions).
This is a directory where modules can be dropped to extend Cobbler without modifying the core. See Modules for more information.