restoring damaged install trees and repo mirrors
by Nick
Hi,
Currently I have a Cobbler installation stored in a Git repository, including
selected parts of /var/lib/cobbler and /etc/cobbler.
/etc/cobbler/**
/var/lib/cobbler/config/**
/var/lib/cobbler/kickstarts/**
/var/lib/cobbler/snippets/**
/var/lib/cobbler/triggers/**
At some point I may have to transplant it. I know there's the replication
feature, but I'm wondering what happens if, say, my server dies and all I have
left is the git repository. For obvious reasons I didn't include the install
trees and RPM mirrors in /var/www/cobbler, although I now suspect I may need to
preserve selected parts of that too, except I'm not sure which.
I actually made an attempt at this very early on, and ran into problems because
I couldn't refresh these caches successfully. In particular the install tree -
there's a "cobbler import" command for the first time, which adds a distro,
however if the import has been done already for a given distro but the imported
data lost, can any of it be refreshed, and if so which parts?
I think I ended up starting from scratch, since initial blundering attempts to
restore the data broke cobbler (something in /var/www/cobbler/links was missing,
which broke the install process).
Next time I need to do this I want to be forearmed with a better understanding.
Can anyone help me with some pointers?
Thanks,
N
12 years, 2 months
bad filter value on profile web page
by Ed Deloye
I just upgraded cobbler and cobbler-web to 2.2. I was trying out the new filtering on the profile web page and have a bad value in there. Now when I enter the profile page I get an error page about a Fault at /profile/list. I've copied the Traceback below. Does anyone know of a way, other than deleting the Mozilla profile, to clear the data in the filter field?
Thanks,
Ed
Traceback:
Environment:
Request Method: GET
Request URL: http://rfcobbler.internal.rfmd.com/cobbler_web/profile/list
Django Version: 1.1.4
Python Version: 2.4.3
Installed Applications:
['django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'cobbler_web']
Installed Middleware:
('django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware')
Traceback:
File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py" in get_response
99. response = callback(request, *callback_args, **callback_kwargs)
File "/usr/share/cobbler/web/cobbler_web/views.py" in genlist
286. pageditems = remote.find_items_paged(what,utils.strip_none(filters),sort_field,page,limit)
File "/usr/lib64/python2.4/xmlrpclib.py" in __call__
1096. return self.__send(self.__name, args)
File "/usr/lib64/python2.4/xmlrpclib.py" in __request
1383. verbose=self.__verbose
File "/usr/lib64/python2.4/xmlrpclib.py" in request
1147. return self._parse_response(h.getfile(), sock)
File "/usr/lib64/python2.4/xmlrpclib.py" in _parse_response
1286. return u.close()
File "/usr/lib64/python2.4/xmlrpclib.py" in close
744. raise Fault(**self._stack[0])
Exception Type: Fault at /profile/list
Exception Value: <Fault 1: 'cobbler.cexceptions.CX:"find cannot compare type: <type \'NoneType\'>"'>
12 years, 2 months
Wiki port of manage docs now up / edit away!
by Michael DeHaan
For those that are interested in helping with docs, manage docs are now ported over to the Wiki, in a few parts.
https://github.com/cobbler/cobbler/wiki/Start%20Here
This is pretty much most of the manage, which I think should stay more or less together. If you split things into too many Wiki pages, it's hard to absorb things via osmosis. I would like to mix the examples in closer to the job though and incorporate more examples throughout, so if you're a new user you don't get bored/confused and wonder what commands you actually care about running.
https://github.com/cobbler/cobbler/wiki/Advanced%20Topics
For topics in Advanced Topics that already had a Wiki page, we should make sure any info there is mentioned in those pages and then just link to them, so Advanced Topics can eventually go away as a catch all. For instance, all the info about DHCP management should already be covered elsewhere, but the stuff about PXE boot loop prevention does not, so that deserves it's own page.
https://github.com/cobbler/cobbler/wiki/Koan
Koan's docs -- notice to understand the configuration management features that Kelsey Hightower wrote, you have to skip between the two manages, so there are probably some implied topics that could be created, and the existing configuration management section could probably mention it there. That's just one of many though.
Once these get hammered out a bit I'll replace the .pod files in the docs tree to more or less just link to the Wiki.
Thanks!
--Michael
12 years, 2 months
Looking for more details on Virtualization options
by Joshua J. Kugler
So, the page on cobbler virtualization options seems a bit sparse.
https://github.com/cobbler/cobbler/wiki/Installing%20Virtual%20Guests
Am I correct when I assume: The system is defined (including
virtualization options) in Cobbler. Then on the machine that will host
the VM, you run
koan --server=cobbler.example.org --virt --system=<system_name_here>'
and it will fire up, say, virsh-install with the proper options?
Any additional insights?
Thanks!
j
--
Joshua J. Kugler - Fairbanks, Alaska
Azariah Enterprises - Programming and Website Design
joshua(a)azariah.com - Jabber: pedahzur(a)gmail.com
PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A
12 years, 2 months
Re: [cobbler] Install with kernel issues
by Dale Reagan
Seth,
At 02:28 PM 2/11/2012, you wrote:
<snip>
>The problem I am having is that some kind of kernel issue is occurring
>during build and when the client reboots it won't fully come up. The
>screen shows several lines reading:
Based on my experiences with VirtualBox + Cobbler:
- test VBox build via CD/DVD install first to arrive at workable virtual
hardware settings
- create new VMs with known 'working' settings based on those 'tests'
- note that ANY update/change related to 'hardware' for either VBox or the
OS being used could 'break' your auto-installs - so you either 'settle' on
a fixed setup and/or re-visit/update every 3-6-12+ months...
- make sure to disable auto-update of Cobbler software in your 'production'
environment...
I wrote several posts in ~2008 covering Cobbler + Virtual box - since both
Cobbler/Vbox have moved along a bit the posts should be considered 'aged'
but they may also contain a nugget or
two... http://web-tech.ga-usa.com/wtags/cobbler/
:)
Dale
= = = = = = = = = = = = = = = = = = = =
Dale E. Reagan | (912) 920-9299
Photographer / Consultant | Dale(a)DaleReagan.Com
PO Box 15336, Savannah, Ga 31416 USA
http://www.dalereagan.com/
12 years, 2 months
Use bootp instead of dnsmasq/
by Javier Domingo
Hi all,
I did already ask this previously, but though I have read most part of the
user docs, I've been unable to find how to use bootpd with cobbler. I want
to use bootpd because it just has dhcp features, configuration file is
quite self explanatory, one line configs for each client and you just need
one configuration file.
I was wondering if there was any already implemented thing. If there isn't
anything implemented but the python interface with dhcp server is clean, I
could try to abstract a module for bootpd. If not, I would be glad to know
how is usually used cobbler with the dhcp server independant.
I have supposed that the DHCP server is supposed to say "take pxelinux.0
from this server" and when the request arrives, depending on the asking
MAC, returns one pxelinux.cfg and if it is in the cobbler database, it will
jump into one menu, if it isn't, you have to type menu, select your
favourite and launch it.
I have read relative to all this:
https://github.com/cobbler/cobbler/wiki/DHCP%20Management => where seemed
that cobbler didn't had bootpd support (for managing it itself)
https://github.com/cobbler/cobbler/wiki/Using%20Cobbler%20Import => here
seems to explain how it works, and it seems to be as I described, if anyone
confirms...
Have read some more, but I don't think they are quite relevant for my
question, or have just few relative words.
My idea is to use mini isos- imports, and use debian-installer files
(preseeding). If anyone knows also any graphical/template explainatory
resource that makes easier to understand preseed, it is welcomed,
Javier Domingo
12 years, 2 months
Re: [cobbler] Cobbler SCCM Integration
by Prashanth Sundaram
I was able to make some progress. Now I get the menu, where I can select the pxe boot env.
When I select SCCM from menu, I get MXE-MOF: Exiting Intel PXE ROM, Operating system not found.
-----Original Message-----
From: cobbler-bounces(a)lists.fedorahosted.org [mailto:cobbler-bounces@lists.fedorahosted.org] On Behalf Of Prashanth Sundaram
Sent: Wednesday, February 08, 2012 5:35 PM
To: cobbler mailing list
Subject: [cobbler] Cobbler SCCM Integration
Hi,
At $work, I have SCCM(Microsoft Systems Center Config Manager) for
Windows Deployment and use cobbler for Linux distros. My DHCP server is
Windows Server 2008 and the way I get cobbler to work is to manually
define the scope options just before I provision.
66 Boot Server Host name: <IP of cobbler>
67 Bootfilename: pxelinux.0
Though this works, I recently came across this doc. "Creating a PXE boot
menu item for integration with SCCM"
https://github.com/cobbler/cobbler/wiki/Microsoft-systems-center
The documentation is very vague and is difficult to follow even with the
reference links. I somehow managed to export the files to /tftpboot/ but
I don't know how to make it work.
What filename should I give for dhcp scope options, so it shows this
menu? If I don't provide a file, PXE fails with no file found. If I give
'pxelinux.0', it goes directly to linux deployment.
Has anyone successfully implemented the SCCM and cobbler?
Thanks,
Prashanth
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
12 years, 2 months
Cobbler SCCM Integration
by Prashanth Sundaram
Hi,
At $work, I have SCCM(Microsoft Systems Center Config Manager) for
Windows Deployment and use cobbler for Linux distros. My DHCP server is
Windows Server 2008 and the way I get cobbler to work is to manually
define the scope options just before I provision.
66 Boot Server Host name: <IP of cobbler>
67 Bootfilename: pxelinux.0
Though this works, I recently came across this doc. "Creating a PXE boot
menu item for integration with SCCM"
https://github.com/cobbler/cobbler/wiki/Microsoft-systems-center
The documentation is very vague and is difficult to follow even with the
reference links. I somehow managed to export the files to /tftpboot/ but
I don't know how to make it work.
What filename should I give for dhcp scope options, so it shows this
menu? If I don't provide a file, PXE fails with no file found. If I give
'pxelinux.0', it goes directly to linux deployment.
Has anyone successfully implemented the SCCM and cobbler?
Thanks,
Prashanth
12 years, 2 months
NIC naming in RHEL 6.x
by Gonzalo Servat
Hi All,
I've noticed that in RHEL 6.1, setting mac addresses in Cobbler (and, thus,
in /etc/sysconfig/network-scripts/ifcfg-* -> HWADDR) sometimes results in
interfaces being renamed. In /etc/udev/rules.d/70-persistent-net.rules, I
end up with:
# PCI device 0x8086:0x105e (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:15:17:4a:2e:91", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth1"
# PCI device 0x8086:0x105e (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:15:17:4a:2e:90", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth0"
# PCI device 0x14e4:0x164c (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:1a:64:11:a1:60", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth2"
# PCI device 0x14e4:0x164c (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:1a:64:11:a1:62", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth3"
# PCI device 0x8086:0x105e (e1000e) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:15:17:4a:2e:91", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth3"
# PCI device 0x14e4:0x164c (bnx2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:1a:64:11:a1:62", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth1"
# PCI device 0x14e4:0x164c (bnx2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:1a:64:11:a1:60", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth0"
# PCI device 0x8086:0x105e (e1000e) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:15:17:4a:2e:90", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth2"
The above is the result of specifying the 4 MAC addresses in Cobbler for
eth0/1/2/3. It ended up renaming eth0 to rename4 and eth1 to rename5!? By
removing the first 4 entries out of 70-persistent-net.rules, it brought up
eth0/1/2/3 correctly.
Any suggestions on how to manage consistent naming of NICs on RHEL 6?
Thanks in advance.
Gonzalo
12 years, 2 months