pxelocal.template and $pxe_menu_items
by Pablo Iranzo Gómez
Hi
I would like to achieve something similar to pxedefault.template but with the custom options of pxelocal.template after a system has been provisoned.
The idea is to offer the full range of profiles to each system as an aditional option.
What I did was to put $pxe_menu_items stanza on the pxelocal.template as I did with pxedefault.template, but no matter what I do, it doesn't get rendered.
After looking at the code at pxegen.py, I can see the metadata["pxe_menu_items"] in "make_actual_pxe_menu" (which outputs pxelinux.cfg/default) but not on the function referencing pxelocal.template ("write_pxe_file"), so my guess is that this is not implemented.
¿any hint?
Thanks in advance
Pablo
--
Pablo Iranzo Gómez (Pablo.Iranzo(a)redhat.com)
Senior Global Profesional Services Consultant (RHCA, RHCSS, RHCDS, RHCVA, RHCE, RHCSP) #804006196923216
Phone: +34 645 01 01 49 (CET/CEST)
GnuPG KeyID: 0xFAD3CF0D
13 years
disabling second nic and HP firmware cd...
by Corey Kovacs
Folks,
Is there a built in 'correct' way to ensure that my second nics are
not configured during build and left alone when using the network
config snippets delivered with cobbler?
RIght now, when the nodes finish building, the undefined second nic
tries to dhcp even though I've not given it a config.
I am getting around this by making the appropriate changes to
ifcfg-eth1 via two 'sed' lines but if there is a 'better' way I'd
rather do that than rely on a post config.
Also,
are people using the livecd boot method for booting HP firmware disks?
How about the SSTK?
Thanks
Corey
13 years, 3 months
Ideas around auto registration
by Jean-Francois Nadeau
Hi,
I'm looking at cobbler to replace our actual home brewed kickstart system to ease 'off truck' scenarios.
We currently rely on the servers BMC (Ilo's XMLRPC interface) to initiate our kickstarts and map a boot media. In this way it is easy to match the bare metal hardware with a system profile but I would like to have a solution independent of the BMC.
Going forward with Cobbler and PXE based installs, I see a challenge with managing mac-adresses and linking them with a system profile as we have a lots of different server models with 2/4 nics and various network configuration where not all NICs can reach a cobbler server.
I really like the auto-registration feature and I was thinking of using it the following way and get around the MAC address challenge:
1. Use a default system profile all 'off truck' servers will network boot to.
The boot image is a custom CentOS 5 livecd with the following onboard:
* Needed binaries to identify the hardware (dmidecode etc.)
* Koan client
* Func client
* Utilities to create vendor RAID arrays and firmware updates
* Utilities to configure BMC if still in vanilla state (IPMI tools / Hponcfg).
* Fancy perl module used as a Cisco CDP querier
2. The image finds the server model, firmware, serial number and all possible NIC details
3. Cobbler-register creates the server's system entry using the server model and serial number since we have no idea of its hostname right now.
4. Func connects to its master and wait for commands.
>From the func master being also the cobbler server, I know which servers are ready to be kickstarted and can rename/assign their profiles easier, translating serial numbers into hostnames. I can also push firmware updates, create RAID arrays and perform some inventory tasks.
All is left is trigger a remote koan --replace-self with func to fire the install. b.t.w... I really like the hidden --kexec switch :-)
Do you think I'm going a too complicated way or does this make sense to some of you ? I remember Michael had some thoughts about extending the auto-registration feature to include other fields but I have not seen much interest on the list.
Happy new year,
Jean-Francois Nadeau
13 years, 3 months
buildiso in 2.0.10
by Urwin, Paul
Hello,
Is anyone aware of a bug in 2.0.10 that causes buildiso to fail as follows?:
# cobbler buildiso
task started: 2010-12-30_103034_buildiso
task started (id=Build Iso, time=Thu Dec 30 10:30:34 2010)
Exception occured: exceptions.TypeError
Exception value: __init__() got an unexpected keyword argument 'logger'
Exception Info:
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 95, in run
rc = self._run(self)
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 155, in runner
self.logger
File "/usr/lib/python2.4/site-packages/cobbler/api.py", line 755, in build_iso
builder = action_buildiso.BuildIso(self._config, logger=logger)
!!! TASK FAILED !!!
# cobbler buildiso --profiles="test" --iso=/var/tmp/test.iso
task started: 2010-12-30_103012_buildiso
task started (id=Build Iso, time=Thu Dec 30 10:30:12 2010)
Exception occured: exceptions.TypeError
Exception value: __init__() got an unexpected keyword argument 'logger'
Exception Info:
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 95, in run
rc = self._run(self)
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 155, in runner
self.logger
File "/usr/lib/python2.4/site-packages/cobbler/api.py", line 755, in build_iso
builder = action_buildiso.BuildIso(self._config, logger=logger)
!!! TASK FAILED !!!
Thanks,
Paul
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.
13 years, 3 months
images created with date instead of name
by Tim Dunphy
my cobbler server is working very well. except one small annoyance is
that when I create images with it, they have the date as the name of
the conf file instead of the intended file name.
If I enter:
koan --virt --server=cobbler --profile=centos55-xen-x86_64 --virt
name=vm17 --virt-path=/mnt/store/xen --nogfx
What I get is a console session and conf file named after the date / time
use virt-manager or reconnect with virsh console Sun_Dec_26_22_10_04_2010
How do i correct this so that xen will use the name of the file that I
indicate in the koan command line instead of the date? This is sort of
annoying as far as problems go...
thanks!
--
GPG me!!
gpg --keyserver pgp.mit.edu --recv-keys F186197B
13 years, 4 months
New templating language and support for EL4
by Scott Henson
I'm considering a move off of Cheetah as the templating language for
Cobbler. I am personally leaning towards django or jinja(1 or 2
depending on the EL4 discussion). I would like to know opinions people
have on if we should move and what we should move to.
Additionally, I'm considering if we should continue to explicitly
support EL4 for running Cobbler on. This would be due to the fact that
many of the really nice templating languages are just not supported on
the version of python that EL4 runs. We would continue to support
running koan on EL4 (in fact I think we will still run all the way back
to AS2.1). Are there people that are still running Cobbler on EL4?
Thanks.
--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME
13 years, 4 months
Call for talks for the Configuration Management DevRoom at fosdem 2011
by James Turnbull
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
**Call for talks for the Configuration Management DevRoom at fosdem 2011**
FOSDEM 2011 - http://fosdem.org/2011/
6 February 2011, 09:00 to 17:00, Brussels, Belgium
Contact: fosdem2011(a)puppetlabs.com
We will be holding a Configuration Management DevRoom at fosdem 2011 and
are requesting abstracts for structured presentations now.
Important information, dates:
? Submission deadline for abstracts: 2011-01-08
? Notification of accepted speakers: 2011-01-10
? Final schedule: 2011-01-11
**About this DevRoom**
Configuration Management is exciting! It is. Really. There is huge
interest in automation, configuration management and especially PAAS,
SAAS, IAAS and the cloud generally. We're seeking people who are
working the field, interested in the field, or just interested in
learning more about how to make their lives easier with automation and
configuration management.
We invite you to submit talks on these topics:
* Configuration Management theory principles
* Configuration Management tools - real world use cases
* Tools, techniques and case studies
* Configuration Management and the Cloud
* Configuration Management, Compliance and Security
NOTE: Puppet Labs is helping organise this room but we're looking for
talks on more than Puppet! We're looking for CFengine, Chef, bcfg2,
AutomateIT, and the myriad of other tools out there.
** Your submission must include:**
* Your name
* The title of your talk
* A short abstract of one to two paragraphs (150 words, max.)
* A short biography
* Links to related websites/blogs etc.
Send the abstracts to:
fosdem2011(a)puppetlabs.com
Presentations are to be formal and not longer than 30 minutes, plus 15
extra for questions (45 in total). Panels with more than one speaker are
something we're also seeking, a "My configuration management tools is
the awesomest and I'll debate that!" is possible, as are shorter
presentations of 20 minutes. We're also exploring some un-conference
style presentations too.
The deadline for submissions is January 8th 2011. If your
proposal has been accepted, you will be informed by email by January
10th 2011.
Please feel free to forward this call for abstracts and papers to
relevant lists, people and sites. We're looking forward to seeing lots
of interested folks, have lots of spirited presentations, debates,
discussion and ... quite possibly drinking.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEVAwUBTQ/ObiFa/lDkFHAyAQL/JAf9EJQexmBYS8VGcRiCwmOkOyaiCMTNC7DA
+khVdgCBNZgz5fz7lrXIw+oEYfj8MuIMW0jd2Fxpdc628y6hSG8PC1Y5/umKyYQI
JYxN9AYYu81rd1Gn7W54qN3ihNibqvJQWpi2jT00uLY/DqFnb6WGWbK00bmLh2lY
VnrtDRx8IoPKIVc0qoPfnKwmg2cw4RWQHqOrz8XwpPLyA2kjhvLmZV1MkYVu/h58
/Cxbai4IiqhurgHoYVb+AUvvenY/45oAXfKWx8+ZsKppTO/YhRu/SIpG3GQSmKGT
uMdgmuQHFwvcdUWDMiR6ylGt14PIhmy4pXpAMVv4DtaRx48C7vwsPA==
=oM7D
-----END PGP SIGNATURE-----
13 years, 4 months
Using dhcp_tag to manage different DHCP servers
by Greg Chavez
I have three subnets, separated by a high-speed p2p connection. I
can't use ip-helper to forward DHCP, so we need to run a DHCP instance
in each subnet. My plan is as follows:
(1) Run a master cobbler in Subnet A, on which everything from distros
to systems is created for all three subnets.
(2) Cobbler A will control DNS and DHCP for its IP space.
(3) Cobbler will run in Subnets B and C without the cobbler_web
component. It will control a local DHCP server but not DNS.
(4) Systems in Subnets B and C will be deployed by running cobbler
replicate and then kicking with koan or PXE.
My assumption is that I'll be able to use dhcp_tags to cause each
cobbler instance to only create entries via the dhcp.template for the
IP space controlled by its subnet. However, it's unclear to me how
this is implemented. Is it simply a matter of editing the Cheetah
language each cobbler's dhcp.template? My Cheetah knowledge is
limited at this point to what's documented via cobbler's Web site.
Can someone offer me guidance on this? Thanks.
--
--Greg Chavez
--
13 years, 4 months
Import *.json data into mysql database?
by Sean Carolan
Hello all:
As you know, Cobbler stores its data in *.json files. I would like to
be able to import system data into a MySQL database. I've been able
to pull the json data into a dictionary using the simplejson module,
like so:
import simplejson as json
mydata = json.load(open('testbox1.json'))
print mydata
{'comment': '', 'kickstart': '<<inherit>>', 'name_servers_search': [],
'ks_meta': {}, 'kernel_options_post': {}, 'image': '',
'redhat_management_key': '<<inherit>>', 'power_type': 'ipmitool',
'power_user': '', 'kernel_options': {}, 'virt_file_size':
'<<inherit>>', 'mtime': 1291922300.5639579, 'template_files': {},
'gateway': '', 'uid': 'MTI5MTkyNjMwPC41NjkyMDkwOTEuNjYxODc',
'virt_auto_boot': '<<inherit>>', 'virt_cpus': '<<inherit>>',
'hostname': '', 'virt_type': '<<inherit>>', 'mgmt_classes': [],
'power_pass': '', 'netboot_enabled': True, 'ipv6_autoconfiguration':
False, 'profile': 'workstation', 'virt_path': '<<inherit>>',
'interfaces': {'eth0': {'dhcp_tag': '', 'subnet': '', 'ipv6_address':
'', 'virt_bridge': '', 'static_routes': [], 'ipv6_mtu': '',
'ipv6_static_routes': [], 'dns_name': '', 'mtu': '', 'bonding': '',
'static': False, 'bonding_opts': '', 'mac_address':
'08:00:27:2B:65:11', 'ipv6_secondaries': [], 'bonding_master': '',
'ip_address': '', 'ipv6_default_gateway': ''}}, 'power_address': '',
'template_remote_kickstarts': 0, 'name_servers': [],
'ipv6_default_device': '', 'name': 'testbox1', 'owners': ['admin'],
'ctime': 1291922300.5639579, 'virt_ram': '<<inherit>>', 'power_id':
'', 'server': '<<inherit>>', 'redhat_management_server':
'<<inherit>>', 'depth': 2}
So far so good...where I'm stuck is importing all this data into the
MySQL database. I've tried massaging the data in various ways but am
unable to get cursor.execute(sql) to work without errors. I think
it's due to the embedded lists and dictionaries in the data set. I
know this is not strictly related to everyday cobbler usage, but you
are python experts who probably could do this in your sleep... Any
ideas?
thanks
Sean
13 years, 4 months
