Setting Hostname via network_config snippet
by Corey Garst
I've found this in /var/lib/cobbler/snippets/network_config:
#if $hostname != ""
#set $network_str = $network_str + " --hostname=" +
$hostname
How and where should I define $hostname in the web interface or CLI?
Thanks
-Corey Garst
14 years, 11 months
Wiki cleanup begins
by Michael DeHaan
It's time for me to go through the Wiki and scrub references to old
syntaxes, old cobbler versions, and so forth, and in general try to make
things more readable for new people.
I'm a bit blinded by some of it because I know the app too well, but for
those of you who have just picked things up recently, you are the ones
to ask this.
Think about the first times you were reading through things on the Wiki
and the mainpage, and things you found confusing and hard to find.
This is not another survey (yes, I'm due to report back on those results
from that one still), but in general I'm looking for information like...
Do we need more examples on the Wiki? (On what topics?)
Should things be more cookbook like?
Are articles on certain things actually too long and confusing, or
actually too short (specific examples?)
Should I explain some concepts that I might be taking for granted?
Is the Wiki too flat, or too nested in terms of what you are trying to find?
Is there any obsolete content we just need to take out back and shoot
(some of the snippet examples, possibly, should just link to our
snippets as examples)
What things don't have documentation and you had to ask here or in the
channel about?
Are there particular settings that we don't explain but should?
I know one thing I want to do for sure is write better examples for
pure-python triggers, and API examples, both in terms of the Python API
and XMLRPC.
Developer docs should probably also mention the importance of individual
files better and how things are inter-related, without dwelling too much
on things that will quickly go out of date.
Comments on docs both in terms of the Wiki and the mainpage are welcome.
The goal is to not only make things easier to new users, but also make
it clear what all the advanced features are, and also show people how to
adopt those features and also /if/ they should adopt those features.
We don't want any particular things buried or not well documented.
Thanks!
--Michael
14 years, 11 months
Cobbler/Koan - DRBD based Xen VMs
by Alex Davies
Hi All,
I am trying to create some DRBD based virtual machines. The correct
syntax for these in the xen configuration is:
disk = [ 'drbd:resource,xvda,w' ]
(there is a "drbd" script in /etc/xen/scripts, provided by the DRBD package).
Is there a way of telling cobbler/koan to use this?
Many thanks,
Alex
14 years, 11 months
scm_track_enabled docs?
by Dick Davies
Does anyone have any documentation on what
scm_track_enabled: 1
should do? I'm assuming cobbler creates its own git repo and starts versioning
its config, but I've no idea where it would/should be. Thanks!
14 years, 11 months
bonding 'error'
by Tom Brown
Hi
I get the following error reported on boot with a box that has miltiple
nics bonded using cobbler at provision time.
http://home.ng23.net/boot.jpg
The good thing is though that everything works just fine - So is this
error benign ?
thanks
14 years, 11 months
Nagios configuration generator
by Léon Keijser
Hi,
I've updated cobnag (nagios configuration generator for
cobbler-maintained systems) and split it into a python module, a wrapper
script and separate settings file and modified things so it works with
cobbler 1.6.x
I've included a spec file to build an RPM from it for easy deployment,
as well as a sample /etc/cobnag.conf configuration file.
Everything can be found at git://github.com/lkeijser/cobnag.git
Syntax:
$ cobnag -y mysystem.example.com -k ExampleCorp
Will then
create /etc/nagios/cobjects/customers/ExampleCorp/mysystem.example.com.cfg and update/generate /etc/nagios/cobjects/customers/ExampleCorp/hostgroup.cfg to include the system.
regards,
--
Léon
14 years, 11 months
Can't read settings file
by Chris O'Regan
NOTE: This is a custom install of Cobbler. I understand that this is
unsupported, but I am hoping that someone can point me in the right
direction.
When I run cobbler (v1.6.4 and v.1.6.5), it exits with the following
warning:
/local/data/cobbler/etc/settings is not a valid YAML file
It's the stock settings file from Cobbler. I even tried a settings file
from a working RPM version of Cobbler (v1.6.3). I have the following
installed:
cheetah-2.0.1
cobbler-1.6.5
netaddr-0.6.2
python-2.5.4
pyyaml-3.08
simplejson-2.0.9
yaml-0.1.2
Thanks,
Chris
14 years, 11 months
NameMapper error in Cobbler
by Aaron Lippold
Has anyone ever run into this?
[root@localhost ~]# cobbler check
/usr/lib/python2.4/site-packages/Cheetah/Compiler.py:1531: UserWarning:
You don't have the C version of NameMapper installed! I'm disabling
Cheetah's useStackFrames option as it is painfully slow with the
Python version of NameMapper. You should get a copy of Cheetah with
the compiled C version of NameMapper.
warnings.warn(
The following potential problems were detected:
#0: since iptables may be running, ensure 69, 80, and 25151 are unblocked
#1: fencing tools were not found, and are required to use the
(optional) power management features. install cman to use them
I can't seem to track it down.
Thanks,
Aaron
14 years, 11 months
