(Somewhat OT) -- Introducing my new remote control framework
by Michael DeHaan
I figure there's enough of a user base crossover between Cobbler, Puppet/Chef, and Func-land to make this interesting.
This is the project I've been working on for the last, well, couple of nights: Ansible.
Introductory blog post
http://michaeldehaan.net/post/18160683912/introducing-ansible-minimal-dis...
Github (source, pull requests, issue tracker)
https://github.com/mpdehaan/ansible
Mailing list (thoughts, ideas, questions?)
http://groups.google.com/group/ansible-project
Please help spread the word, it is really early yet but I think there are a lot of places it can go.
I've been working on the "playbook" a lot, which is more or less like a puppet module tree, or chef runbook, only 10x simpler. But I really think that it's actually enough for *most* people, assuming modules flesh out more over the next few weeks.
There are reasons why you'd pick X over Y, this is just for those who want "Y", so I'm not really interested in pulling a Charlie Sheen on any other projects. But I know there's just times when I need something set up *yesterday* and I want something that's really simple and never going to give me trouble,
that I can explain to someone in 5 minutes. This is that.
There are a lot of features I probably *won't* accept because the whole goal is to keep it extremely simple. Modules, yes, we'll build up a community of those, but there are going to be certain requirements for what ship in the core, like what attributes they return and how they check errors.
Shouldn't be too complicated. Fair warning, code review may be harsh as I have some goals for keeping this _really_ small and easy to understand.
Since this isn't about Cobbler really, this will be the last post on Ansible. Keep replies to me or the ansible-project list please. Again, really early, but wanted to give folks a chance to get in at the ground floor.
Thanks!
--Michael
12 years, 2 months
Cobbler used in 'cloud provisioning solutions'?
by Dale Reagan
Greetings All,
I'm exploring some 'cloud solutions' and finding Cobbler in use (or as an
add-on) for several tool sets including 1) Orchestra (Ubuntu) and 2)
openQRM. I'm just looking to become familiar with the landscape a bit -
are there others that I should look at?
BTW - I'm tinkering in the HP Cloud beta so naturally I thought of using
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
Documentation for RHEL
by Gerhardus Geldenhuis
Hi
I have been going through the process of setting up a cobbler server from
scratch recently... up until now I was relying on legacy config files that
I kept copying over. Although the documentation on the wiki is useful there
was no step by step guide. I also experienced one possible bug but will
need to double check. My question is with regards to the re-org of the
documentation mentioned a while ago does such a step by step guide fit
anywhere or do you purposely not want one? I would be happy to write one
and also provide a bootstrap kickstart that anyone can use to build the
cobbler server to build the rest his/her servers.
Regards
--
Gerhardus Geldenhuis
12 years, 2 months
Incorrect links on import and rename
by Scott, Sean I
Running cobbler-2.2.1-1.el6.noarch from epel-testing
Performing an import below:
[root@el6-seanscott01 links]# cobbler import --path=/media/RHEL_5.8\ x86_64\ DVD/ --name=rhel5.8 --arch=x86_64
Creates the following directory:
[root@el6-seanscott01 links]# ls -lAh /var/www/cobbler/ks_mirror/
dr-xr-xr-x 8 apache apache 4.0K Feb 2 12:02 rhel5.8-x86_64
But produces broken symlinks:
[root@el6-seanscott01 links]# ls -lAh /var/www/cobbler/links
lrwxrwxrwx 1 root root 34 Feb 22 21:37 rhel5.8-x86_64 -> /var/www/cobbler/ks_mirror/rhel5.8
lrwxrwxrwx 1 root root 34 Feb 22 21:37 rhel5.8-xen-x86_64 -> /var/www/cobbler/ks_mirror/rhel5.8
Also when i renamed my first rhel5 distro and profiles to rhel5.7-x86_64 and rhel5.7-xen-x86_64 the symlinks in /var/www/cobbler/links that I had fixed earlier were deleted but not recreated.
Regards,
Sean
Terracon provides geotechnical, environmental, construction materials, and facilities consulting engineering services delivered with responsiveness, resourcefulness, and reliability.
________________________________
Private and confidential as detailed here (www.terracon.com/disclaimer). If you cannot access hyperlink, please e-mail sender.
12 years, 2 months
PXE TFTP Time Out
by Scott, Sean I
I just completed a (2) fresh install of cobbler for the first time. One at my home network on EL6.2 and one at work on RHEL5.7. So far the only issue I ran into was with the arguments that were being placed in the tftpd configuration for xinetd by cobbler sync on 6.2.
On the Centos 6.2 Server with atftp-server as the tftp server the -s argument that was being written was causing TFTP connections to timeout. In /var/log/messages the tftp daemon was exiting immediately with status=1
/usr/lib/python2.6/site-packages/cobbler/modules/manage_in_tftpd.py
In line 128
def write_tftpd_files(self):
metadata = {
"user" : "root",
"binary" : "/usr/sbin/in.tftpd",
--> "args" : "-v -s %s" % self.bootloc
I had to remove the "-s" from the argument list (restart and sync) before atftp would function. Would it be possible to move those arguments (except for bootloc of course) to the /etc/cobbler/tftpd.template instead of the manage_in_tftpd.py file? Or include a check for the tftp daemon running and remove the -s if the /usr/sbin/in.tftpd daemon is a symlink to atftpd?
Just starting to move my kickstart files to live within the model cobbler uses but so far a very positive experience.
Regards,
Sean
Terracon provides geotechnical, environmental, construction materials, and facilities consulting engineering services delivered with responsiveness, resourcefulness, and reliability.
________________________________
Private and confidential as detailed here (www.terracon.com/disclaimer). If you cannot access hyperlink, please e-mail sender.
12 years, 2 months
Testing cobbler install - pxe tftp open timeout
by Daniel Lollman
Hello all -
Hopefully you all can help me out. I am fairly new to Cobbler/PXE booting in general. I had an interesting issue show up this morning while doing some testing of various kickstart files that I am trying to wrap my head around.
For the past week or so I have been testing various kickstarts on two different systems by editing the kickstart, taking the system out of cobbler, and re-adding it so it is like new and it rebuilds the system via PXE. It has been working like a charm.
Until this morning.. I was working with one system (let's call it sysA) which is in a subnet 172.19.10.x. For some reason when this system boots up now it gets a DHCP address but then tftp times out and eventually boots from local disk instead of reinstalling.
I have another system (let's call it sysB) which is in subnet 172.19.34.x. It is still working fine. Both of these systems are being served from the same cobbler server which has two NICs, one on each subnet.
There were no changes to the cobbler server (besides changing kickstart templates slightly and snippets) or the network recently which is really making me confused as to why this has happened?
Any ideas on where I can look?
I have tested tftp commands from sysA (after booting from local disk) to the cobbler server which work just fine.
The only things I see in logs that are concerning are in the httpd error_logs:
[Wed Feb 22 08:55:07 2012] [error] possible cheetah template error
[Wed Feb 22 08:58:32 2012] [error] possible cheetah template error
[Wed Feb 22 14:34:03 2012] [error] /usr/lib64/python2.6/site-packages/mod_python/importer.py:32: DeprecationWarning: the md5 module is deprecated; use hashlib instead
[Wed Feb 22 14:34:03 2012] [error] import md5
However I have not been able to find much in terms of solutions to these errors.
[root@cobbler ~]# rpm -qa|grep cobbler
cobbler-web-2.0.11-2.el6.noarch
cobbler-2.0.11-2.el6.noarch
[root@cobbler ~]# cat /etc/redhat-release
CentOS release 6.2 (Final)
[root@cobbler ~]#
Any direction and any outputs needed please let me know!
Thanks in advance.
Daniel
12 years, 2 months
Read write cobbler xmlrpc API
by Kirk VanOpdorp
I am using cobbler with passthru authentication to enable Kerberos on cobbler web. I would also like remote read write access to the xmlrpc API. I have setup the proxied cobbler_api in apache such that I think it should work. My question is that the read write API requires a token which requires a user and password. What password do I use in that case if I am using the passthru authentication?
12 years, 2 months
managing cobbler with puppet / augeas
by Nick
Hi,
Further to a question I asked on the Puppet mailing list, I wonder if anyone
here has had any success managing Cobbler with Puppet which they could share?
http://groups.google.com/group/puppet-users/browse_thread/thread/31040119...
As I said there, what I'd like to do is:
- write a Puppet node definition manifest for a new machine
- include DHCP, DNS, hostname and network declarations
- commit this to Git
- deploy via Puppet
- have the Cobber server pick the config up and set up PXE, DHCP, and
DNS accordingly (Cobbler being managed via Puppet)
- shortly after, boot a new machine, and during the PXE boot either
- have its MAC address recognised, or
- select the system from a menu
- have it provisioned with the Puppet package and an appropriate hostname
- have Puppet configure it in the pre-assigned role
Ideally, I'd be able to re-deploy a new Cobbler server in exactly the same way
as another node.
Puppet modules which allow automating setting up repos, profiles, systems etc.
don't seem to exist on the public internet.
One way might be to write a Puppet type based on the Ruby library for
controlling Cobbler 2.0 (2.x?) I gather exists here:
http://www.google.com/url?sa=D&q=https://github.com/duritong/ruby-cobbler...
However, more recently I've been experimenting with Augeas (from Puppet) to
manage certain config files and I notice there are Augeas lenses (parsers) for
cobbler's settings and modules.conf files. Plus there is a generic JSON lens,
which presumably could handle everything in /var/lib/cobbler/config.
So another approach might be to use that - although this would would be
bypassing the API, of course, which comes with its own set of problems.
Cheers,
Nick
12 years, 2 months
cobbler centos kickstart with rpms from external repo
by George Pitich
i've been trying to kickstart centos 6 (pxe) with cobbler for some time but haven't been successful. namely if installation doesn't require any external repos (like epel or rpmforge) kickstart works great. however when installation needs some packages provided in external repos (epel) i don't know how to specify such a request.
I thought that:
cobbler repo add --name=EPEL-x86_64 --mirror=http://download.fedora.redhat.com/pub/epel/5/x86_64 --mirror-locally=N
would fetch dependencies during kickstart (puppet) but that simply didn't happen (did cobbler reposync), installation process would complain that puppet package didn't exist. excerpt from the ks file:
url --url http://server-ip/distros/CentOS/6.0/os/x86_64/
%packages
@base
@compat-libraries
@core
@puppet
Os and core packages are served from a local yum repo that resides on the same box as cobbler:
also:
cobbler add --name=Centos_6.0_x86_64 --kernel=/distros/CentOS/6.0/os/x86_64/images/pxeboot/vmlinuz --initrd=/distros/CentOS/6.0/os/x86_64/images/pxeboot/initrd.img
cobbler distro add --name=Centos_6.0_x86_64 --kernel=/distros/CentOS/6.0/os/x86_64/images/pxeboot/vmlinuz --initrd=/distros/CentOS/6.0/os/x86_64/images/pxeboot/initrd.img
cobbler profile add --name=Centos_6.0_x86_64_Bit --distro=Centos_6.0_x86_64 --kickstart=/distros/kickstarts/centos60.ks
I can browse the repo without any issues (repo was created from 2 centos 6 dvd iso files). At the moment i am mirroring epel through the cobbler locally. once mirror is done i'll create the profile but not sure if this is the only thing required?
i'm quite new to cobbler and would appreciate any help on this matter.
thx.
12 years, 2 months
if two external repos are added to a profile kicstart always opens network dialog
by George Pitich
I'm kickstarting Centos 5.4 with cobbler-2.0.11. if I have only one external repo in my profile, kickstart correctly applies network config for eth0 (satic IP). However, if add another external repo to my centos 5.4 profile (cobbler profile edit), kickstart always shows network config dialog even tho eth0 is configured with static IP? If I remove the lastly added external profile (only one stays) kicstart correctly assigns static IP address to eth0.
How do I make sure that regardless of the number of external repos in a profile, kickstart applies correct settings?
Thanks.
12 years, 2 months