[cobbler] Re: Cobbler release 2.6.11

[Harry Hoffman]

Thanks for all of the work you guys continue to put into Cobbler!

Cheers,
Harry

On Jan 23, 2016 9:18 AM, Jörgen Maas  wrote:
>
> Hey all,
>
> We've just released Cobbler version 2.6.11. This release adds support for a 
> few current distros and also fixes some bugs (most importantly the github.com 
> -> github.io issue).
>
> - Release notes: 
> http://cobbler.github.io/manuals/2.6.0/1/1_-_Release_Notes.html
> - Downloads: http://cobbler.github.io/downloads/2.6.x.html
> - Distribution support: 
> http://cobbler.github.io/manuals/2.6.0/1/2_-_Distribution_Support.html
>
> Cheers!
>
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/cobbler@lists.fedorahosted.org

[cobbler] Buildiso doesn't seem to be bootable

[Harry Hoffman]

Hi All,

Running 2.6.9 on top of CentOS 7.x

I've got distros for Centos and RHEL (6.x, 7.x - x86-64).

Running buildiso and then taking generated.iso and dd'ing it to a USB stick via:
dd if=./generated.iso of=/dev/sdc

This method works for isos included in the RHEL DVDs but not for the cobbler 
generated iso.

Am I missing some key step here or is cobbler not actually building a bootable 
image?

Cheers,
Harry
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] Unamble to install nodes with Cobbler

[Harry Hoffman]

Hi Robin,

Are you sure the tftp-server is listening and there's not a firewall (host or 
network based that's blocking communication to that tftp port)?

Does the client system get a dhcp address from the server?

Cheers,
Harry

On Apr 27, 2015 3:20 AM, Robin Casset robin.cas...@atos.net wrote:

 Hello,

 My name is Robin, I'm an apprentice engineer  at Bull SAS.
 I recently install cobbler on a server to make some few test of it. I have 
 been able to import an iso, create a repo and set up profiles. The pxe file 
 is generated and seems to be good but when the node boot on the network I 
 have a message unable to find files

 here are my node and image profiles :

 Name   : dep12
 TFTP Boot Files    : {}
 Comment    : 
 Enable gPXE?   : False
 Fetchable Files    : {}
 Gateway    : 192.168.1.0
 Hostname   : dep12
 Image  : 
 IPv6 Autoconfiguration : False
 IPv6 Default Device    : 
 Kernel Options : {}
 Kernel Options (Post Install)  : {}
 Kickstart  : /var/lib/cobbler/kickstarts/dep12.ks
 Kickstart Metadata : {}
 LDAP Enabled   : False
 LDAP Management Type   : authconfig
 Management Classes : []
 Management Parameters  : inherit
 Monit Enabled  : False
 Name Servers   : ['192.168.1.1']
 Name Servers Search Path   : []
 Netboot Enabled    : True
 Owners : ['root']
 Power Management Address   : 192.168.1.13
 Power Management ID    : 
 Power Management Password  : administrator-
 Power Management Type  : apc
 Power Management Username  : administrator
 Profile    : Centos7-x86_64
 Internal proxy : inherit
 Red Hat Management Key : inherit
 Red Hat Management Server  : inherit
 Repos Enabled  : False
 Server Override    : inherit
 Status : production
 Template Files : {}
 Virt Auto Boot : 0
 Virt CPUs  : inherit
 Virt Disk Driver Type  : inherit
 Virt File Size(GB) : inherit
 Virt Path  : inherit
 Virt PXE Boot  : 0
 Virt RAM (MB)  : inherit
 Virt Type  : xenpv
 Interface =    : eth0
 Bonding Opts   : 
 Bridge Opts    : 
 CNAMES : []
 DHCP Tag   : default
 DNS Name   : 
 Per-Interface Gateway  : 192.168.1.0
 Master Interface   : 
 Interface Type : 
 IP Address : 192.168.1.12
 IPv6 Address   : 
 IPv6 Default Gateway   : 
 IPv6 MTU   : 
 IPv6 Prefix    : 
 IPv6 Secondaries   : []
 IPv6 Static Routes : []
 MAC Address    : 00:30:48:7a:3c:bc
 Management Interface   : True
 MTU    : 
 Subnet Mask    : 255.255.255.0
 Static : True
 Static Routes  : []
 Virt Bridge    : xenbr0

 profiles:
 ==
 Name   : Centos7-x86_64
 TFTP Boot Files    : {}
 Comment    : 
 DHCP Tag   : linux
 Distribution   : Centos7-x86_64
 Enable gPXE?   : False
 Enable PXE Menu?   : True
 Fetchable Files    : {}
 Kernel Options : {}
 Kernel Options (Post Install)  : {}
 Kickstart  : /var/lib/cobbler/kickstarts/dep12.ks
 Kickstart Metadata : {}
 Management Classes : []
 Management Parameters  : inherit
 Name Servers   : []
 Name Servers Search Path   : []
 Owners : ['root']
 Parent Profile : 
 Internal proxy : 
 Red Hat Management Key : inherit
 Red Hat Management Server  : inherit
 Repos  : ['Centos7']
 Server Override    : inherit
 Template Files : {}
 Virt Auto Boot : 1
 Virt Bridge    : xenbr0
 Virt CPUs  : 1
 Virt Disk Driver Type  : raw
 Virt File Size(GB) : 5
 Virt Path  : 
 Virt RAM (MB)  : 512
 Virt Type  : kvm

 And here the pxe file:

 default linux
 prompt 0
 timeout 1
 label linux
     kernel /images/Centos7-x86_64/vmlinuz
     ipappend 2
     append initrd=/images/Centos7-x86_64/initrd.img ksdevice=bootif lang= 
  kssendmac text  ks=http://192.168.1.1/cblr/svc/op/ks/system/dep12

 I can't see 

Re: [cobbler] Cobbler login

[Harry Hoffman]

Do you have SELINUX enabled? If so, you'll want to modify your policy
and restart cobblerd.

Cheers,
Harry


On 02/26/2015 07:09 PM, Scott Mattan wrote:
 I don't have specifics on why or what was done before this happened...
 as I typically use the command line anyway.  However it seems that the
 web interface for Cobbler has stopped authenticating.  It always
 responds with invalid password and or username.  I have tried
 re-installing the interface, recreating the user among other things
 exhausting my options. The only error that I can seem to come across is
 this:
 
 Fri Feb 27 17:56:36 2015 - INFO | Exception occured: type
 'exceptions.AttributeError'
 Fri Feb 27 17:56:36 2015 - INFO | Exception value: BootAPI instance has
 no attribute 'authn'
 Fri Feb 27 17:56:36 2015 - INFO | Exception Info:
   File /usr/lib/python2.6/site-packages/cobbler/remote.py, line 2087,
 in _dispatch
 return method_handle(*params)
File /usr/lib/python2.6/site-packages/cobbler/remote.py, line 1886,
 in login
 if self.__validate_user(login_user,login_password):
File /usr/lib/python2.6/site-packages/cobbler/remote.py, line 1783,
 in __validate_user
 return self.api.authenticate(input_user,input_password)
File /usr/lib/python2.6/site-packages/cobbler/api.py, line 1025, in
 authenticate
 rc = self.authn.authenticate(self,user,password)
 
 
 As it seems to be an issue directly with python code... (although I
 can't imagine why it would suddenly change) I am honestly not sure what
 to do.
 
 Any help is greatly appreciated.
 
 Thanks 
 
 Scott
 
 
 
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

[cobbler] SELINUX denials cobbler-2.6.7-1

[Harry Hoffman]

Hi All,

It seems that the selinux policy for cobbler needs some updates:

#= cobblerd_t ==
allow cobblerd_t cert_t:dir search;
allow cobblerd_t cert_t:file { read getattr open };
allow cobblerd_t cert_t:lnk_file read;
allow cobblerd_t etc_t:file write;
allow cobblerd_t slapd_cert_t:dir { getattr search };
allow cobblerd_t slapd_cert_t:file { read getattr open };
allow cobblerd_t tftpdir_rw_t:dir rmdir;
allow cobblerd_t tftpdir_rw_t:file { getattr unlink };


The cert and slapd is for ldap authentication and is optional but should
probably be part of the policy. The tftpdir stuff I think should've been
included as a default, no?

Here's the audit2why output
[root@cobbler ~]# audit2why -li /var/log/audit/audit.log
type=AVC msg=audit(1422644949.550:25): avc:  denied  { getattr } for
pid=1431 comm=cobblerd path=/etc/openldap/certs dev=dm-0 ino=786670
scontext=system_u:system_r:cobblerd_t:s0
tcontext=system_u:object_r:slapd_cert_t:s0 tclass=dir

Was caused by:
Missing type enforcement (TE) allow rule.

You can use audit2allow to generate a loadable module to allow 
this
access.

type=AVC msg=audit(1422644949.587:26): avc:  denied  { search } for
pid=1431 comm=cobblerd name=pki dev=dm-0 ino=786478
scontext=system_u:system_r:cobblerd_t:s0
tcontext=system_u:object_r:cert_t:s0 tclass=dir

Was caused by:
Missing type enforcement (TE) allow rule.

You can use audit2allow to generate a loadable module to allow 
this
access.

type=AVC msg=audit(1422644949.587:27): avc:  denied  { getattr } for
pid=1431 comm=cobblerd path=/etc/openldap/certs dev=dm-0 ino=786670
scontext=system_u:system_r:cobblerd_t:s0
tcontext=system_u:object_r:slapd_cert_t:s0 tclass=dir

Was caused by:
Missing type enforcement (TE) allow rule.

You can use audit2allow to generate a loadable module to allow 
this
access.

type=AVC msg=audit(1422644949.587:28): avc:  denied  { getattr } for
pid=1431 comm=cobblerd path=/etc/openldap/certs dev=dm-0 ino=786670
scontext=system_u:system_r:cobblerd_t:s0
tcontext=system_u:object_r:slapd_cert_t:s0 tclass=dir

Was caused by:
Missing type enforcement (TE) allow rule.

You can use audit2allow to generate a loadable module to allow 
this
access.

type=AVC msg=audit(1422645107.788:30): avc:  denied  { getattr } for
pid=1492 comm=cobblerd path=/etc/openldap/certs dev=dm-0 ino=786670
scontext=unconfined_u:system_r:cobblerd_t:s0
tcontext=system_u:object_r:slapd_cert_t:s0 tclass=dir

Was caused by:
Missing type enforcement (TE) allow rule.

You can use audit2allow to generate a loadable module to allow 
this
access.

type=AVC msg=audit(1422645107.793:31): avc:  denied  { search } for
pid=1492 comm=cobblerd name=certs dev=dm-0 ino=786670
scontext=unconfined_u:system_r:cobblerd_t:s0
tcontext=system_u:object_r:slapd_cert_t:s0 tclass=dir

Was caused by:
Missing type enforcement (TE) allow rule.

You can use audit2allow to generate a loadable module to allow 
this
access.

type=AVC msg=audit(1422645107.793:31): avc:  denied  { getattr } for
pid=1492 comm=cobblerd path=/etc/openldap/certs/secmod.db dev=dm-0
ino=786673 scontext=unconfined_u:system_r:cobblerd_t:s0
tcontext=system_u:object_r:slapd_cert_t:s0 tclass=file

Was caused by:
Missing type enforcement (TE) allow rule.

You can use audit2allow to generate a loadable module to allow 
this
access.

type=AVC msg=audit(1422645107.794:32): avc:  denied  { read } for
pid=1492 comm=cobblerd name=secmod.db dev=dm-0 ino=786673
scontext=unconfined_u:system_r:cobblerd_t:s0
tcontext=system_u:object_r:slapd_cert_t:s0 tclass=file

Was caused by:
Missing type enforcement (TE) allow rule.

You can use audit2allow to generate a loadable module to allow 
this
access.

type=AVC msg=audit(1422645107.794:32): avc:  denied  { open } for
pid=1492 comm=cobblerd name=secmod.db dev=dm-0 ino=786673
scontext=unconfined_u:system_r:cobblerd_t:s0
tcontext=system_u:object_r:slapd_cert_t:s0 tclass=file

Was caused by:
Missing type enforcement (TE) allow rule.

You can use audit2allow to generate a loadable module to allow 
this
access.

type=AVC msg=audit(1422645107.833:33): avc:  denied  { search } for
pid=1492 comm=cobblerd name=pki dev=dm-0 ino=786478
scontext=unconfined_u:system_r:cobblerd_t:s0
tcontext=system_u:object_r:cert_t:s0 tclass=dir

Was caused by:
Missing type enforcement (TE) allow rule.

You can use audit2allow to generate a loadable module to allow 
this
access.

type=AVC msg=audit(1422645107.833:33): avc:  denied  { read } for
pid=1492 comm=cobblerd name=cert.pem dev=dm-0 ino=786546
scontext=unconfined_u:system_r:cobblerd_t:s0
tcontext=system_u:object_r:cert_t:s0 

Re: [cobbler] sub profiles in 2.6.7-1

[Harry Hoffman]

Hi Alan,

Sorry about that. This was a long standing issue where subprofiles
didn't properly inherit values from their parent profile.

I've been out of cobbler for a little bit and didn't see a bugfix listed
when I checked. I'll setup a few subprofiles and test. If there's a
problem I'll report back.

Cheers,
Harry



On 1/30/15 9:35 AM, Alan Evangelista wrote:
 On 01/27/2015 08:46 PM, Harry Hoffman wrote:
 I'm trying to find out if sub profiles have been fixed in 2.6.7-1
 
 No. Reference:
 http://www.cobblerd.org/manuals/2.6.0/1/1_-_Release_Notes.html
 
 What exactly is the problem? Is there an issue in Cobbler issue tracker
 about it?
 
 
 Regards,
 Alan Evangelista
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

[cobbler] Integrating virsh with cobbler

[Harry Hoffman]

Hi All,

Wondering if anyone's done any integration with cobbler and virsh?

I'm thinking about writing some triggers to create virtual systems based
off a new system creation in cobbler.

Anyone already gone down this path?

Cheers,
Harry
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

[cobbler] sub profiles in 2.6.7-1

[Harry Hoffman]

Hi All,

I'm trying to find out if sub profiles have been fixed in 2.6.7-1

Cheers,
Harry
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] cobbler_web does not support sub profiles fully?

[Harry Hoffman]

I would use them and have used them in the past, even filing a bug report when 
they first broke.
Some sort of inheritance would be great for profiles.

Cheers,
Harry

On Jul 17, 2014 4:37 AM, =?ISO-8859-1?Q?J=F6rgen_Maas?= jorgen.m...@gmail.com 
wrote:

 Hi,

 I was just wondering who would use subprofiles ;-).
 We have another issue with them, even from the cli (see: 
 https://github.com/cobbler/cobbler/issues/1030)

 But to answer your question: i'm pretty sure there's no such setting to 
 enable the selection of distros from cobbler-web
 I assume the distro can't be changed because that is fetched from the parent 
 profile.

 I will take a look...


 On Thu, Jul 17, 2014 at 10:24 AM, alast...@alastair-munro.com wrote:

 Hi

 cobbler and cobbler-web at 2.6.1-7.1.

 Sub profiles cannot select distros from the drop down on the web page. Is 
 there a setting as to whether sub profiles can be edited or not? I thought 
 they were just like profiles and take values from the parent if a value is 
 not set? I created the sub profile from the web page. I had problems 
 selecting other options and had to set them from the command line.

 Reason I want a parent profile is I want to put all my templated files in 
 there, have a generic el6 parent and then use sub profiles to select 
 different distros (rh/centos/si-linux varying versions of el6, minor 
 release, etc) and pass a ksmeta flag to select different builds (we like to 
 reduce the number of kickstarts to maintain and just have one that does 
 everything).

 Functionality from the command line is fine.

 Let me know if a new version is coming soon :)

 Thanks in advance

 Alastair
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler




 -- 
 Grtz,
 Jörgen Maas
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] Cobbler check

[Harry Hoffman]

Typo maybe? Cobbler support ISC dhcp/named or ... (Crap, blanking on the name 
of the other one).

Cheers,
Harry

On Jul 16, 2014 7:05 AM, Newman, Stuart J. (GSFC-444.0)[HONEYWELL TECHNOLOGY 
SOLUTIONS INC]  stuart.j.new...@nasa.gov wrote:

 Cobbler 2.6.1 RHEL 6.5

  

 When running cobbler check, I get

  

 [root@fiat ~]# cobbler check

 The following are potential configuration items that you may want to fix:

  

 1 : SELinux is enabled. Please review the following wiki page for details on 
 ensuring cobbler works correctly in your SELinux environment:

     https://github.com/cobbler/cobbler/wiki/Selinux

 2 : Unknown distribution type, cannot check for running service dhcpd

 3 : Unknown distribution type, cannot check for running service cobblerd

 4 : Apache (httpd) is not installed and/or in path

 5 : debmirror package is not installed, it will be required to manage debian 
 deployments and repositories

 6 : fencing tools were not found, and are required to use the (optional) 
 power management features. install cman or fence-agents to use them

  

 Restart cobblerd and then run 'cobbler sync' to apply changes.

  

 I do not understand messages 2 and 3.

  

 See attached files for more info.

  

 

 Stuart J. Newman
 Engineer 4; Systems

 Solar Dynamics Observatory (SDO)

  

 Honeywell Technology Solutions Inc

 NASA/Goddard Space Flight Center

 Building 14, Room E222

 Mail Stop 428.2

 Greenbelt, MD 20771

  

 Office: (301) 286-5145

 Mobile: (443) 878-0280

 E-Mail: stuart.j.new...@nasa.gov

  

 
  
 NOTICE: This communication, including any attachment, contains information 
 that may be confidential or privileged, and is intended solely for the entity 
 or individual to whom it is addressed.  If you are not the intended 
 recipient, please notify the sender at once, and you should delete this 
 message and are hereby notified that any disclosure, copying, or distribution 
 of this message is strictly prohibited.  Nothing in this email, including any 
 attachment, is intended to be a legally binding signature.

  
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] How does Files work?

[Harry Hoffman]

Hi,
Straight from the manual...

http://www.cobblerd.org/manuals/2.4.0/5/3/1_-_Built-In_Configuration_Management.html

Cheers,
Harry

On Jun 30, 2014 7:54 AM, Michael Tiernan mtier...@mit.edu wrote:

 There's a gui  cli option for files.

 What's it supposed to do?
 How does this work?
 It asks for a template, what's it want there?

 While we're on it, how does one create (and then get) a fetchable file?

 I have the need to put a set of specific files on a system and I'd
 rather let cobbler handle moving them instead of my scripting some
 strange approach to fixing it.

 Thanks for everyone's time.
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] How does Files work?

[Harry Hoffman]

Hi Mike,

So, are you just unsure of how to template or how to setup the templates?

You can use the cheetah templating within each template and have one template 
cover multiple hosts. So, if you had a template located on the cobbler server 
at /srv/templates/etc_resolv_conf you can use cobbler templates do designate 
different DNS servers per host/group/etc.

#set $dns1 = $getVar(‘$dns1’, 127.0.0.1)
#if $hostname == “SomeHost”
nameserver $dns1
#else
nameserver 8.8.8.8
#end if

So, if you set this as 
cobbler profile edit --name=foo 
--template-files=/srv/templates/etc_resolv_conf=/etc/resolv.conf
Cobbler will set that file for you.

Does this help? It’s a very basic example.

HTH.

Cheers,
Harry

On Jun 30, 2014, at 8:07 AM, Michael Tiernan mtier...@mit.edu wrote:

 On 6/30/14 7:59 AM, Harry Hoffman wrote:
 Hi,
 Straight from the manual...
 Grr... :)
 
 Okay, let me reread this and see what I can learn.
 
 Thanks for letting me know.
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler

___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] How does Files work?

[Harry Hoffman]

Yep, that’s correct. You can have it anywhere you want (that the cobbler user 
can access via normal permissions) and it is user created. I store mine under 
/var/lib/cobbler just for sanity’s sake.

Hope this helps!

Cheers,
Harry

On Jun 30, 2014, at 10:02 AM, Michael Tiernan mtier...@mit.edu wrote:

 On 6/30/14 9:02 AM, Harry Hoffman wrote:
 So, if you had a template located on the cobbler server at 
 /srv/templates/etc_resolv_conf you can use cobbler templates do designate 
 First off, thank you very much for your help and advice.
 
 I just want to clear up something obvious to make sure I don't assume
 anything.
 
 The base of the prefix you used /srv/templates (i.e. templates) is
 user created and not already there normally right? (Nor does it have to
 be that name.)
 
 I'm just making sure I am covering all my bases.
 
 Thanks.
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler

___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] An introduction from an engineer who will be intergrating Cobbler + Nexenta

[Harry Hoffman]

Wow, that's awesome news.

I was just looking into OpenSolaris integration with Cobbler.

I'd be interested in how you make out.

Cheers,
Harry

On 01/08/2014 11:22 AM, piousbox-admin wrote:
 Hello all,
 
 I'm Victor, working at Nexenta and my current task is to enable Nexenta to be
 booted via Cobbler. My supervisor suggested that I send an email to this
 maillist and introduce myself, which is what I am doing.
 
 Nexenta is a Solaris-based storage solution that utilizes the ZFS technology
 (http://en.wikipedia.org/wiki/ZFS).
 I'm sure later on I will have specific questions about the task. Presently, I
 just wanted to say hello and announce that this project is under way.
 
 Cheers! ^__^
 
 --
 Victor Pudeyev
 ad...@piousbox.com mailto:ad...@piousbox.com
 http://piousbox.com/users/show/piousbox
 
 
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

[cobbler] contributing snippets

[Harry Hoffman]

Hi All,

I've written a bunch of snippets to harden RH based distro so that they
conform to NIST/CIS benchmarks for system hardening.

Is there a central place to contribute these (assuming they are wanted)
or should I just find a place to host and then send a link?

Cheers,
Harry
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] centos 6 distro importing fails

[Harry Hoffman]

In the first instance you are trying to import the updates and not the
distro.

In the second case I don't know if the minimal distro is supported.

This is the proper base for importing the latest (6.4):
http://mirror.centos.org/centos-6/6.4/os/

If you want just 64bit then choose x86_64

Cheers,
Harry



On 09/09/2013 09:30 AM, Joost Ringoot wrote:
 Hello,
 
 I am trying to set up cobbler for deploying centos6 machines (later on
 maybe ubuntu)
 
 I have problems when I try to import a repository:
 
 This apparently copies the rpms, but then brutally fails:
 [root@geppetto cobbler]# cobbler import --path=rsync://
 ftp.belnet.be/centos/6/updates/x86_64/Packages --name=centos-server-6.4
 task started: 2013-09-09_143420_import
 task started (id=Media import, time=Mon Sep  9 14:34:20 2013)
 No signature matched in /var/www/cobbler/ks_mirror/centos-server-6.4
 !!! TASK FAILED !!!
 [root@geppetto cobbler]#
 
 I retried after updating the signature file, (like described here, in both
 ways, by copying the file and manually in python:
 https://github.com/cobbler/cobbler/issues/423) after restarting cobblerd
 still the same result.
 
 Then I tried importing an iso file, looks better, it found valid signatures
 but ends even more cryptic:
 
 [root@geppetto tmp]# md5sum /data/isos/CentOS-6.4-x86_64-minimal.iso
 4a5fa01c81cc300f4729136e28ebe600  /data/isos/CentOS-6.4-x86_64-minimal.iso
 [root@geppetto tmp]# umount /data/isos/CentOS-6.4-x86_64-minimal.iso
 [root@geppetto tmp]# md5sum /data/isos/CentOS-6.4-x86_64-minimal.iso
 4a5fa01c81cc300f4729136e28ebe600  /data/isos/CentOS-6.4-x86_64-minimal.iso
 [root@geppetto tmp]# mount -o loop
 /data/isos/CentOS-6.4-x86_64-minimal.iso  /mnt/CentOS-6.4-x86_64-minimal
 [root@geppetto tmp]# ls -al /mnt/CentOS-6.4-x86_64-minimal
 total 87
 dr-xr-xr-x. 7 root root  4096 Mar  5  2013 .
 drwxr-xr-x. 3 root root  4096 Sep  9 14:51 ..
 -r--r--r--. 1 root root14 Mar  5  2013 CentOS_BuildTag
 -r--r--r--. 1 root root33 Mar  5  2013 .discinfo
 dr-xr-xr-x. 3 root root  2048 Mar  5  2013 EFI
 -r--r--r--. 1 root root   212 Mar  2  2013 EULA
 -r--r--r--. 1 root root 18009 Mar  2  2013 GPL
 dr-xr-xr-x. 2 root root  2048 Mar  5  2013 images
 dr-xr-xr-x. 2 root root  2048 Mar  5  2013 isolinux
 dr-xr-xr-x. 2 root root 36864 Mar  5  2013 Packages
 -r--r--r--. 1 root root  1354 Mar  2  2013 RELEASE-NOTES-en-US.html
 dr-xr-xr-x. 2 root root  4096 Mar  5  2013 repodata
 -r--r--r--. 1 root root  1706 Mar  2  2013 RPM-GPG-KEY-CentOS-6
 -r--r--r--. 1 root root  1730 Mar  2  2013 RPM-GPG-KEY-CentOS-Debug-6
 -r--r--r--. 1 root root  1730 Mar  2  2013 RPM-GPG-KEY-CentOS-Security-6
 -r--r--r--. 1 root root  1734 Mar  2  2013 RPM-GPG-KEY-CentOS-Testing-6
 -r--r--r--. 1 root root  3380 Mar  5  2013 TRANS.TBL
 -r--r--r--. 1 root root   276 Mar  5  2013 .treeinfo
 [root@geppetto tmp]# cobbler import --path=/mnt/CentOS-6.4-x86_64-minimal
 --name=Centos-6.4-x86_64
 task started: 2013-09-09_145520_import
 task started (id=Media import, time=Mon Sep  9 14:55:20 2013)
 Found a candidate signature: breed=redhat, version=rhel6
 Found a matching signature: breed=redhat, version=rhel6
 Adding distros from path /var/www/cobbler/ks_mirror/Centos-6.4-x86_64:
 No distros imported, bailing out
 !!! TASK FAILED !!!
 [root@geppetto tmp]#
 
 Is there something specific I should look for in the cobbler log?
 [root@geppetto cobbler]# tail -n 20 /var/log/cobbler/cobbler.log
 repodata/ce2d698b9fb1413b668443e88835a0642cea8f387c7f25cc946f56dd93f109bb-c6-minimal-x86_64.xml.gz
 1405 100%6.38kB/s0:00:00 (xfer#266, to-check=1/274)
 repodata/repomd.xml
 3736 100%   16.89kB/s0:00:00 (xfer#267, to-check=0/274)
 
 sent 358281326 bytes  received 5112 bytes  55120990.46 bytes/sec
 total size is 358215622  speedup is 1.00
 
 Mon Sep  9 14:52:31 2013 - DEBUG | received on stderr:
 Mon Sep  9 14:55:20 2013 - DEBUG | REMOTE CLI Authorized; user(?)
 Mon Sep  9 14:55:20 2013 - INFO | REMOTE start_task(Media import);
 event_id(2013-09-09_145520_import); user(?)
 Mon Sep  9 14:55:21 2013 - INFO | import_tree;
 ['/mnt/CentOS-6.4-x86_64-minimal', 'Centos-6.4-x86_64', None, None, None]
 Mon Sep  9 14:55:21 2013 - INFO | importing from a network location,
 running rsync to fetch the files first
 Mon Sep  9 14:55:21 2013 - INFO | running: rsync -a
 '/mnt/CentOS-6.4-x86_64-minimal/'
 /var/www/cobbler/ks_mirror/Centos-6.4-x86_64 --progress
 Mon Sep  9 14:55:21 2013 - INFO | received on stdout: sending incremental
 file list
 
 sent 10978 bytes  received 18 bytes  21992.00 bytes/sec
 total size is 358215622  speedup is 32576.90
 
 Mon Sep  9 14:55:21 2013 - DEBUG | received on stderr:
 [root@geppetto cobbler]#
 
 
 BTW: I would love to get it working wit selinux, but I want to get it just
 working right now, so this is my current selinux status:
 [root@geppetto audit]# getenforce
 Permissive
 [root@geppetto audit]#
 
 
 Thanks,
 
 Joost
 
 
 
 ___
 cobbler mailing list
 

Re: [cobbler] help with import

[Harry Hoffman]

Can you post the command and args you used to do the import?

On 05/14/2013 01:26 PM, David Birdsong wrote:
 ping?
 
 anybody know where should focus to troubleshoot this or whether i'm just
 doing something incorrectly?
 
 
 On Fri, May 10, 2013 at 7:00 PM, David Birdsong 
 david.birds...@gmail.comwrote:
 
 Oh, forgot to give the deets:

 server: Centos6.4

 cobbler version delivered via epel repo: cobbler-2.2.3-2.el6.noarch




 On Fri, May 10, 2013 at 6:55 PM, David Birdsong 
 david.birds...@gmail.comwrote:

 IRC was quiet,  re-posting...


 I could use some help on importing my yum repo. i'm doing an rsync style,
 debug log shows rsync completes, but the command line returns 'TASK FAILED'.

 cobbler.log shows: INFO | No import managers found a valid signature at
 the location specified among other non-interesting log lines.

 My packages are signed, the local rpm db has the public keys imported. Is
 there a way to import the keys to cobbler separately?



 
 
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] Cobbler 2.4

[Harry Hoffman]

Hi Stuart,

RPMs for 2.4 beta X can be had via the EPEL repository. If you select
epel-test via

yum --enablerepo=epel-test install cobbler cobbler_web

you'll get the latest (beta5, I believe).

Not sure about the upgrade, I did a fresh install. Just backup
/etc/cobbler and /var/lib/cobbler/{kickstarts,snippets}

Cheers,
Harry

On 05/02/2013 08:14 AM, Newman, Stuart J. (GSFC-444.0)[HONEYWELL
TECHNOLOGY SOLUTIONS INC] wrote:
 I have several questions concerning Cobbler 2.4
 
 
  1.
 Approximately when will thwe production version of Cobbler 2.4 be released?
  2.
 How does one get the rpm's for 2.4 beta 3?
  3.
 What precautions need to be taken when upgrading from 2.2.3 to 2.4?
  4.
 Should 2.4 be able to do an automated install of ESXi 5.1?
 
 Stuart J. Newman
 Engineer 4; Systems
 Solar Dynamics Observatory (SDO)
 
 Honeywell Technology Solutions Inc
 
 NASA/Goddard Space Flight Center
 Building 14, Room E222
 Mail Stop 428.2
 Greenbelt, MD 20771
 
 Office: (301) 286-5145
 EMail: stuart.j.new...@nasa.govmailto:stuart.j.new...@nasa.gov
 
 
 
 NOTICE: This communication, including any attachment, contains information 
 that may be confidential or privileged, and is intended solely for the entity 
 or individual to whom it is addressed.  If you are not the intended 
 recipient, please notify the sender at once, and you should delete this 
 message and are hereby notified that any disclosure, copying, or distribution 
 of this message is strictly prohibited.  Nothing in this email, including any 
 attachment, is intended to be a legally binding signature.
 
 
 
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] Finding snippet errors

[Harry Hoffman]

Jimmi,

Will this fix be pushed out to the 2.4 version that in epel-testing?

Cheers,
Harry

On 03/22/2013 09:46 AM, James Cammarata wrote:
 On Fri, Mar 22, 2013 at 7:05 AM, Robert Jacobson robert.c.jacob...@nasa.gov
 wrote:
 
  On 3/22/2013 7:30 AM, Harry Hoffman wrote:

 Have you run cobbler validateks on the kickstart file that includes
 the snippet?


 Thanks, I didn't know about this -- However, for my particular example of
 a broken snippet, it doesn't help.  It just stops working with a
 non-helpful error message when it gets to the kickstart with the problem:

 Exception occured: type 'exceptions.NameError'
 [etc]


  Also, there's the ErrorCatcher class in cheetah (albeit not built into
 cobbler) that can help with this.


 Thanks again!   This will probably help for some things.  Still, it
 doesn't appear to help with my example broken snippet.  At least, not when
 I did this:
 #errorCatcher Echo
 #if $break_me == 1
 #  no #end if...

 I did notice that if  you have an undefined variable, it changes the
 behavior completely.  Without errorCatcher, the kickstart would just have:
 $SNIPPET('snippet_with_error')
 but with errorCatcher, the kickstart is printed with the undefined
 variable in it.  Maybe this isn't a good thing, because there's no error
 message anywhere I can find.  i.e. all the errorCatcher does in this case
 is make the error silent!  At least when $SNIPPET is present I know
 there's an error in it :)

 
 Cobbler injects the error catching class silently before parsing, so that's
 why that won't work. You could modify templar.py if you wanted, here's the
 patch that I added for 2.4.0:
 
 https://github.com/cobbler/cobbler/commit/60d5f0131ea2ec0fe8e109f1dab4ac8419ddb502
 
 
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] iterating of a list stored in ksmeta

[Harry Hoffman]

Thanks guys,

The typo was just in my email. But that code didn't work.

What did was the following:
#set uname = $users.split(,)
#for $name in $uname
user --name=$name
#end for


Cheers,
Harry

On 03/04/2013 07:11 AM, James Cammarata wrote:


 I'm trying to iterate over the list of users to be able to create users
 in my kickstart file.

 I was trying to do something like:
 #for $uname = $users.split(',')
 user --name=$user
 #end for


 You might have issues here as well since you're assigning the values to
 $uname in the for loop but then using the variable $user when attempting to
 print out the user.

 
 Right, it should be:
 
 #for $uname in $users.split(',')
 user --name=$uname
 #end for
 
 
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] iterating of a list stored in ksmeta

[Harry Hoffman]

Oh, great! That looks a little bit cleaner.

Thanks, Jimi.

Cheers,
Harry

On 03/04/2013 10:01 AM, James Cammarata wrote:
 On Mon, Mar 4, 2013 at 7:09 AM, Harry Hoffman 
 hhoff...@ip-solutions.netwrote:
 
 Thanks guys,

 The typo was just in my email. But that code didn't work.

 What did was the following:
 #set uname = $users.split(,)
 #for $name in $uname
 user --name=$name
 #end for

 
 In that case, you may want to use:
 
 #set $uname = $getVar(users,).split(,)
 #for $name in $uname
 user --name=$name
 #end for
 
 I've tested this as follows:
 
 $ cobbler system edit --name=test2 --ksmeta=users=test1,test2,test3
 $ cobbler system getks --name=test2 | grep name=test
 user --name=test1
 user --name=test2
 user --name=test3
 
 
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

[cobbler] iterating of a list stored in ksmeta

[Harry Hoffman]

Hi All,

I've got a value (actually several) stored in ksmeta for a list of 
users.


Kickstart Metadata: {'users': 'user1,user2,user3', 'rootmail': 
'u...@fq.dn'}


I'm trying to iterate over the list of users to be able to create users 
in my kickstart file.


I was trying to do something like:
#for $uname = $users.split(',')
user --name=$user
#end for

But that doesn't seem to work.

Anyone know how to do this?

Cheers,
Harry

___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] cobblerd 2.4.0 beta3 on centos 6.0 seg faulting

[Harry Hoffman]

Yeah, that's what I was saying. In permissive mode everything works.

Bob Cochran bcochra...@verizon.net wrote:

I'm on CentOS 6.3 x86_64 but it is not running as a virtual machine. I 
run selinux in permissive mode:

[bobbyc@cobbler1 ~]$ sestatus
SELinux status: enabled
SELinuxfs mount:/selinux
Current mode:   permissive
Mode from config file:  permissive
Policy version: 24
Policy from config file:targeted


...no problems with my cobbler 2.4.0 implementation, which is built from 
sourcecode.

Bob


On 12/12/12 7:06 PM, Harry Hoffman wrote:
 Ok, this seems to be a selinux issue. setenforce 0 allows cobbler to 
 start:

 #= cobblerd_t ==
 allow cobblerd_t cobbler_tmp_t:file execute;
 allow cobblerd_t devlog_t:sock_file write;
 allow cobblerd_t syslogd_t:unix_dgram_socket sendto;
 allow cobblerd_t tmpfs_t:dir search;

 Cheers,
 Harry


 On Wed, 12 Dec 2012 19:02:16 -0500, Harry Hoffman wrote:
 Hi All,

 Hopefully the subject says it all.

 Just installed cobbler 2.4.0-beta3 on a centos 6 vm system (virtual
 box x86_64):

 [root@localhost ~]# service cobblerd start
 Starting cobbler daemon: /bin/bash: line 1:  1626 Segmentation fault
   (core dumped) cobblerd --daemonize
 [FAILED]
 From: /var/log/messages
 Dec 13 00:00:25 localhost kernel: cobblerd[1661] general protection
 ip:3369e8616e sp:7fff20597d80 error:0 in
 libpython2.6.so.1.0[3369e0+171000]
 Dec 13 00:00:25 localhost abrtd: Directory
 'ccpp-2012-12-13-00:00:25-1661' creation detected
 Dec 13 00:00:25 localhost abrt[1662]: Saved core dump of pid 1661
 (/usr/bin/python) to /var/spool/abrt/ccpp-2012-12-13-00:00:25-1661
 (11132928 bytes)
 Dec 13 00:00:25 localhost abrtd: Package 'cobbler' isn't signed with
 proper key
 Dec 13 00:00:25 localhost abrtd: 'post-create' on
 '/var/spool/abrt/ccpp-2012-12-13-00:00:25-1661' exited with 1
 Dec 13 00:00:25 localhost abrtd: Corrupted or bad directory
 /var/spool/abrt/ccpp-2012-12-13-00:00:25-1661, deleting

 Let me know if you need more info.

 Cheers,
 Harry
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler

 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler


___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] Puppet configuration

[Harry Hoffman]

You probably want to add EPEL via the repo list. That way the packages
in EPEL are available as part of the install.

If you google for kickstart documentation or goto redhat's site you'll
see the options.

Then you can specify puppet and use a %post script to configure it.

Cheers,
Harry

On 08/20/2012 10:41 AM, Bai Shen wrote:
 Interesting.  I didn't realize you could do things like that with %post.
 
 How do you add the epel and puppet?  When I try to run puppet manually,
 the command isn't found.  And yum tries to connect to the internet
 instead of the cobbler repo.
 
 The sample template I'm using includes puppet snippets, but they don't
 seem to do anything.  Is that because I don't have the epel added to
 cobbler?
 
 Thanks.
 
 On Mon, Aug 20, 2012 at 10:27 AM, Scot Floess sflo...@redhat.com
 mailto:sflo...@redhat.com wrote:
 
 Bai,
 
 One of the things I do is have my own custom kickstart file.  Part
 of that kickstart is including puppet...
 
 https://github.com/FlossWare/cobbler/blob/development/system.ks
 
 The aforementioned link is the kick start I use with cobbler.  All
 you really need to do is define ksmeta having packages=puppet and
 that will ensure puppet gets installed...  Well that and you'll also
 need to include epel yum repo...
 
 HTH,
 
 Flossy
 
 
 
 *From: *Bai Shen baishen.li...@gmail.com
 mailto:baishen.li...@gmail.com
 *To: *cobbler mailing list cobbler@lists.fedorahosted.org
 mailto:cobbler@lists.fedorahosted.org
 *Sent: *Monday, August 20, 2012 10:16:48 AM
 *Subject: *[cobbler] Puppet configuration
 
 
 So I'm able to get my machine built using cobbler.  However, it
 doesn't seem to have installed and set up puppet.
 
 Does anyone know of any good tutorials or documentation that I
 can look at?  Most of the stuff I'm finding assumes you're just
 installing puppet, not continuing on from a cobbler kickstart.
 
 Thanks.
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 mailto:cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
 
 
 
 -- 
 Make It So Number One
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org mailto:cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
 
 
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] Puppet configuration

[Harry Hoffman]

How will the client talk to the puppetmaster, after the install, if they
are on networks that can't communicate?

Cheers,
Harry

On 08/20/2012 12:26 PM, Bai Shen wrote:
 The sample kickstart file already has the puppet setup as far as I can
 tell.  The part I appear to be missing is the first step.
 
 Part of my complication is that this install is on a separate switch
 with no internet access.  So everything I do has to come from the
 cobbler/puppet machine.  However, once the install is done, the machine
 will be connected to the network and not have access to the
 cobbler/puppet machine anymore.
 
 On Mon, Aug 20, 2012 at 11:30 AM, Shake Chen shake.c...@gmail.com
 mailto:shake.c...@gmail.com wrote:
 
 if is centos, it is simple
 
 1: add epel to profile, let can find the puppet
 
 2: edit /etc/cobbler/setting, enable puppet.
 
 that would install puppet agent for the node.
 
 
 
 On Mon, Aug 20, 2012 at 10:16 PM, Bai Shen baishen.li...@gmail.com
 mailto:baishen.li...@gmail.com wrote:
 
 So I'm able to get my machine built using cobbler.  However, it
 doesn't seem to have installed and set up puppet.
 
 Does anyone know of any good tutorials or documentation that I
 can look at?  Most of the stuff I'm finding assumes you're just
 installing puppet, not continuing on from a cobbler kickstart.
 
 Thanks.
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 mailto:cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
 
 
 
 -- 
 Shake Chen
 
 
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org mailto:cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
 
 
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://lists.fedorahosted.org/mailman/listinfo/cobbler
 
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Re: [cobbler] Necessity For Using Kickstart

[Harry Hoffman]

I guess you should just pxeboot the netboot.iso?  Original Message  From: Bob Cochran  Sent: Sat, Jun 23, 2012 09:51 PM To: cobbler-list  CC:  Subject: [cobbler] Necessity For Using KickstartHi,

I am still setting up my Cobbler server (version 2.3.1, and I installed 
and updated from the Github source). I have added a bunch of distros 
such as CentOS and Fedora 17. Now I want to put a new hard drive in my 
laptop and install Fedora 17 to the laptop with Cobbler.

I am wondering if I absolutely must use a kickstart file? Suppose I 
don't asssociate a profile with a kickstart, and then pxeboot my laptop, 
will I be able to install Fedora 17 "as if" I had put an installation 
DVD in the DVD drive, and be walked through the entire installation by 
Anaconda? That is what I would like to do.

I do have two kickstart files I used for installing Fedora 14. Perhaps I 
used these with an older version of cobbler. I'm not sure I remember the 
passwords embedded in them. Nor am I sure the package names used in 
Fedora 17 are the same as those in Fedora 14.

Thanks

Bob Cochran

___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Re: A How-to Question: Capturing a server configuration in command line form

[Harry Hoffman]

While maybe not clonable when building a brand new cobbler server I 
use root's .bash_history to guide me through what I've done.

For every config file I edit I always issue the command cp $file 
$file-`date -I` so I have the original to diff against to know exactly 
what changes were made.

Once done building the new cobbler server I take the history file, 
remove all of the things that are uneccesary (ls; pwd; etc) and put full 
paths on file and commands I've used the write all of this out to our wiki.

It works pretty well even when you don't get to document for days or 
weeks after you've finished the build.

Cheers,
Harry

On 10/19/2011 09:00 AM, Dan White wrote:
 I agree, replicate is a great way to clone the existing server, but I am 
 tasked to record the steps it took to create the server such that someone 
 else could do it.

 Such info could be used to make a separate server for a different group for a 
 different project by tweaking parameters.

 “Sometimes I think the surest sign that intelligent life exists elsewhere in 
 the universe is that none of it has tried to contact us.”
 Bill Waterson (Calvin  Hobbes)

 - James Cammarataj...@sngx.net  wrote:

 Cobbler replicate is definitely the way to go, or if you use some kind
 of SAN replication like SRDF you can store all of your data on a
 replicated LUN.
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Re: A How-to Question: Capturing a server configuration in command line form

[Harry Hoffman]

Sure, I use cfengine... but it's a chicken and egg game and you have to 
start somewhere.

The setup I describe is when there are no other machines and I'm walking 
in to build something from the ground up.

Cheers,
Harry

On 10/19/2011 09:28 AM, James Cammarata wrote:
 On Wed, Oct 19, 2011 at 8:21 AM, Harry Hoffman
 hhoff...@ip-solutions.net  wrote:
 While maybe not clonable when building a brand new cobbler server I
 use root's .bash_history to guide me through what I've done.

 For every config file I edit I always issue the command cp $file
 $file-`date -I` so I have the original to diff against to know exactly
 what changes were made.

 Once done building the new cobbler server I take the history file,
 remove all of the things that are uneccesary (ls; pwd; etc) and put full
 paths on file and commands I've used the write all of this out to our wiki.

 It works pretty well even when you don't get to document for days or
 weeks after you've finished the build.

 I'd recommend looking into a configuration management system like
 puppet. You can lay down a consistent configuration very quickly using
 that.
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler

___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Re: A How-to Question: Capturing a server configuration in command line form

[Harry Hoffman]

Sure, you can get all of that from the history command.

On 10/19/2011 10:34 AM, Dan White wrote:
 All my config files are in Subversion, but I want to capture the commands to 
 set up the distros, repos, profiles, and systems

 “Sometimes I think the surest sign that intelligent life exists elsewhere in 
 the universe is that none of it has tried to contact us.”
 Bill Waterson (Calvin  Hobbes)

 - Harry Hoffmanhhoff...@ip-solutions.net  wrote:
 While maybe not clonable when building a brand new cobbler server I
 use root's .bash_history to guide me through what I've done.

 For every config file I edit I always issue the command cp $file
 $file-`date -I` so I have the original to diff against to know exactly
 what changes were made.

 Once done building the new cobbler server I take the history file,
 remove all of the things that are uneccesary (ls; pwd; etc) and put full
 paths on file and commands I've used the write all of this out to our wiki.

 It works pretty well even when you don't get to document for days or
 weeks after you've finished the build.

 Cheers,
 Harry

 On 10/19/2011 09:00 AM, Dan White wrote:
 I agree, replicate is a great way to clone the existing server, but I am 
 tasked to record the steps it took to create the server such that someone 
 else could do it.

 Such info could be used to make a separate server for a different group for 
 a different project by tweaking parameters.

 “Sometimes I think the surest sign that intelligent life exists elsewhere 
 in the universe is that none of it has tried to contact us.”
 Bill Waterson (Calvin   Hobbes)

 - James Cammarataj...@sngx.net   wrote:

 Cobbler replicate is definitely the way to go, or if you use some kind
 of SAN replication like SRDF you can store all of your data on a
 replicated LUN.
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler

 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Re: A How-to Question: Capturing a server configuration in command line form

[Harry Hoffman]

Oh, either I missed that part or you failed to mention it, LOL.

On 10/19/2011 10:59 AM, Dan White wrote:
 Yes, provided that I did it from the command line.
 Silly me, I used the web interface for some of it and THAT's the part I am 
 trying to recapture.

 I may have to just try on a scratch machine.

 I appreciate all the responses I am getting on this.

 “Sometimes I think the surest sign that intelligent life exists elsewhere in 
 the universe is that none of it has tried to contact us.”
 Bill Waterson (Calvin  Hobbes)

 - Harry Hoffmanhhoff...@ip-solutions.net  wrote:
 Sure, you can get all of that from the history command.

 On 10/19/2011 10:34 AM, Dan White wrote:
 All my config files are in Subversion, but I want to capture the commands 
 to set up the distros, repos, profiles, and systems

 “Sometimes I think the surest sign that intelligent life exists elsewhere 
 in the universe is that none of it has tried to contact us.”
 Bill Waterson (Calvin   Hobbes)

 - Harry Hoffmanhhoff...@ip-solutions.net   wrote:
 While maybe not clonable when building a brand new cobbler server I
 use root's .bash_history to guide me through what I've done.

 For every config file I edit I always issue the command cp $file
 $file-`date -I` so I have the original to diff against to know exactly
 what changes were made.

 Once done building the new cobbler server I take the history file,
 remove all of the things that are uneccesary (ls; pwd; etc) and put full
 paths on file and commands I've used the write all of this out to our wiki.

 It works pretty well even when you don't get to document for days or
 weeks after you've finished the build.

 Cheers,
 Harry

 On 10/19/2011 09:00 AM, Dan White wrote:
 I agree, replicate is a great way to clone the existing server, but I 
 am tasked to record the steps it took to create the server such that 
 someone else could do it.

 Such info could be used to make a separate server for a different group 
 for a different project by tweaking parameters.

 “Sometimes I think the surest sign that intelligent life exists elsewhere 
 in the universe is that none of it has tried to contact us.”
 Bill Waterson (CalvinHobbes)

 - James Cammarataj...@sngx.netwrote:

 Cobbler replicate is definitely the way to go, or if you use some kind
 of SAN replication like SRDF you can store all of your data on a
 replicated LUN.
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler

 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler

 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Re: install url trouble

[Harry Hoffman]

You have a underscore instead of a hyphen in the kickstart output, no? 

Tim Tassinari tpt...@yahoo.com wrote:

Tim,

When I've seen this in the past it is usually because the network for the 
machine being kickstarted is either not setup or incorrect.  

I'd verify that the network information is correct and utilizing it without 
any routes that you can get to these media locations.

-tim

On Jun 14, 2011, at 11:33 PM, Tim Dunphy bluethu...@jokefire.com wrote:

 hello list!
 
 I am having trouble with the install url portion of the kickstart file. The 
 ks was working in the recent past and honestly I'm not sure what may have 
 changed to break the darn thing. 
 
 First is the mirror url I am attempting to use:
 
 ## use mirror to install
 url --url http://mirror.trouble-free.net/centos/5.6/os/x86_64/
 
 Now if you pump that url into your browser you should see a viable installer 
 location. But this is what happens in the installer:
 
 Welcome to CentOS

 
 
  +-+ HTTP Setup +--+ 
   
  | | 
   
  | Please enter the following information: | 
   
  | | 
   
  | o the name or IP number of your Web server  | 
   
  | o the directory on that server containing   | 
   
  |   CentOS for your architecture  | 
   
  | | 
   
  |   Web site name:mirror.trouble-free.net_| 
   
  |   CentOS directory: /centos/5.6/os/x86_64/__| 
   
  | | 
   
  | ++ +--+ | 
   
  | | OK | | Back | | 
   
  | ++ +--+ | 
   
  | | 
   
  | | 
   
  +-+ 
   
 
 
 
  Tab/Alt-Tab between elements  | Space selects | F12 next screen 
  
 
 
 Next I tried the NFS media I have used in the past without kickstart.
 
 # Use NFS installation media
 nfs --server=192.168.1.250 --dir=/mnt/DVD
 
 
 Now with this I can type the appropriate command on the command line and 
 have it mount:
 
 [root@LCENT03:~] #mount 192.168.1.250:/mnt/DVD /mnt/DVD
 [root@LCENT03:~] #cd /mnt/DVD
 [root@LCENT03:/mnt/DVD] #ls
 CentOSRELEASE-NOTES-cs   RELEASE-NOTES-en_US   RELEASE-NOTES-ja  
 RELEASE-NOTES-ro
 EULA  RELEASE-NOTES-cs.html  RELEASE-NOTES-en_US.html  
 RELEASE-NOTES-ja.html RELEASE-NOTES-ro.html
 GPL   RELEASE-NOTES-de   RELEASE-NOTES-es  RELEASE-NOTES-nl  
 repodata
 imagesRELEASE-NOTES-de.html  RELEASE-NOTES-es.html 
 RELEASE-NOTES-nl.html RPM-GPG-KEY-beta
 isolinux  RELEASE-NOTES-en   RELEASE-NOTES-fr  
 RELEASE-NOTES-pt_BR   RPM-GPG-KEY-CentOS-5
 NOTES RELEASE-NOTES-en.html  RELEASE-NOTES-fr.html 
 RELEASE-NOTES-pt_BR.html  TRANS.TBL
 
 
 But in the installer this is what happens:
 
 Welcome to CentOS

 
  +--+ NFS Setup +--+ 
   
  | | 
   
  | Please enter the following information: | 
   
  | | 
   
  | o the name or IP number of your NFS server  | 
   
  | o the directory on that server containing   | 
   
  |   CentOS for your architecture  | 
   
  | o optionally, parameters for the NFS mount  | 
   
  | | 
   
  | NFS server name:  192.168.1.250___  | 
   
  | CentOS directory: /mnt/DVD  | 
   
  | NFS mount options (optional):   | 
   
  | | 
   
  |  ++ +--+| 
   
  |  | OK | | Back || 
   
  |  ++ +--+| 
   
  |  

RE: cobbler/module_loader.py

[Harry Hoffman]

Hi Bryon,

regarding your 1st point you should check out func/certmaster as they
integrate very nicely with cobbler and do exactly what you describe.

Cheers,
Harry

On Fri, 2010-08-13 at 16:30 -0400, Byron Pezan wrote:
 i'm not a dev, just a user, but in my experience so far, triggers definitely 
 do run on the cobbler server.  i have a couple that i use now, one of which 
 is just a simple shell script to iterate through the various locations that 
 cobbler keeps important files (/etc/cobbler, /var/lib/cobbler, and even 
 /usr/lib/python/site-packages/cobbler) and add them to my SVN repo.  i also 
 have a more complex python script that maintains selective/arbitrary state 
 info b/w by prod cobbler server and my development cobbler server.  and to 
 mark's point i also drop a custom rc.local file onto all provisioned systems 
 to deal with things like vmware tools, custom RHN/Satellite registration and 
 various other junk that i was too lazy to deal with in a more elegant manner 
 (puppet).

/snip

___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Cobbler and func filetracker

[Harry Hoffman]

Hi,

I seem to remember someone talking about setting up filetracking via 
func at install time.

I can't remember if it's built into cobbler or if someone was just using 
  snippets.

Anyone know?

Cheers,
Harry
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Re: installing koan on new system

[Harry Hoffman]

Hi Larry,

You can add the repo during install with the repo keyword in the 
kickstart file.

repo --name=repoid [--baseurl=url| --mirrorlist=url]


HTH,
Harry


Larry Matter wrote:
 I am using cobbler to install CentOS 5.3 on a new system which will be a
 Xen host.  I then want to install koan on that system so that I can
 remotely create VMs on it.
 
 The stupid question is, what's the recommended way to automatically
 install koan on the new Xen host?
 
 I'm sure this is a FAQ, but searching on koan kickstart returns just
 about every page in the wiki.  After an hour of serious googling, I've
 learned a lot, but not the answer to this question.
 
 I did add EPEL as a repository to the new system, hoping then I could just
 add koan as a package in the kickstart, but it seems the new repository
 isn't available during install, only afterwards.
 
 Any help appreciated!
 
 Thanks,
 Larry Matter
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
 
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Re: OT - patch management

[Harry Hoffman]

We use this rather simplistic method:

#!/bin/bash
for i in `/usr/bin/func * list_minions`
do 
  /usr/bin/func $i call yumcmd check_update  /var/tmp/updates-`date
-I`
done

cat /var/tmp/updates-`date -I` |mail -s System Updates Available root
rm -f /var/tmp/updates-`date -I`



We're using a for loop because running the check_update with func *
seems to time out too often.

Cheers,
Harry



On Thu, 2009-02-19 at 12:39 -0500, Michael DeHaan wrote:
 Rainer Duffner wrote:
  Am 19.02.2009 um 17:32 schrieb Jeff Schroeder:
 

  Like anything systems related the proper way is with a dedicated
  testing environment and a configuration management tool. Some pretty
  big companies use puppet. Some other really big companies (one of
  which I formerly worked for) use Spine
  (http://code.ticketmaster.com/index.php?page=spine)
  
 
 
 
  OK, we will be using puppet in the future.
 
  But it doesn't answer the question of:
- what's the revision of package X on my hosts
- which any CVE's apply?
- and similar questions
 
 
  We would have little problems patching sshd on most of our hosts - but  
  patching apache or tomcat would need some testing.
 
  So, the question is not wether we can automate the patch-process  
  itself, but rather the getting an overview-phase.
 
  We are an ISP with a rather large managed hosting infrastructure - we  
  don't have 500 hosts running all the same version of apache + php.
  We want to be able to make an informed decision as to which hosts  
  actually need patching, based on various criteria.
 
  Pakiti looked good - but it seems that either CERN has stopped  
  development or doesn't publish the code anymore.
  Hm. The author still seems to work at CERN - I might just as well ask  
  him.
 
 
 
  Rainer
  ___
  cobbler mailing list
  cobbler@lists.fedorahosted.org
  https://fedorahosted.org/mailman/listinfo/cobbler

 
 I still think Func would be ideally suited to generating some quick and 
 dirty reports about what systems would need updates. It already has yum 
 and RPM modules for this, and you could use things like the exploding 
 laptop finder and func-inventory for examples on how to write some 
 simple reports to do just that.
 
 If shiny enough, we could probably package them as 
 /usr/bin/func-package-report as we do with func-inventory today.
 
 --Michael
 
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler

___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Re: slightly OT - preserving ssh keys

[Harry Hoffman]

we pass them out via our configuration mgmt system.

Cheers,
Harry


On Thu, 2009-01-29 at 16:18 +, Tom Brown wrote:
 Hi
 
 We use cobbler to build a pretty stateless farm that can be rebuilt 
 pretty fluidly pretty much all the time as you'd expect. I have however 
 never really come up with a great way to preserve ssh keys so that the 
 id does not change when the box gets rebuilt.
 
 Does anyone have any ideas on how to achieve this?
 
 thanks
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler

___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

yum upgrade to 1.2.6-1.el5

[Harry Hoffman]

Just upgraded to the latest cobbler from epel-testing... the 
post-install script fails :-(

Updating  : cobbler  ### [ 5/10]
profile CentOS-5.2-x86_64 not found, inheritance not possible

Stopping cobbler daemon: [  OK  ]
Starting cobbler daemon: Traceback (most recent call last):
   File /usr/bin/cobblerd, line 32, in ?
 api = bootapi.BootAPI()
   File /usr/lib/python2.4/site-packages/cobbler/api.py, line 90, in 
__init__
 self.deserialize()
   File /usr/lib/python2.4/site-packages/cobbler/api.py, line 448, in 
deserialize
 return self._config.deserialize()
   File /usr/lib/python2.4/site-packages/cobbler/config.py, line 186, 
in deserialize
 serializer.deserialize(self._profiles)
   File /usr/lib/python2.4/site-packages/cobbler/serializer.py, line 
125, in deserialize
 rc = storage_module.deserialize(obj,topological)
   File 
/usr/lib/python2.4/site-packages/cobbler/modules/serializer_yaml.py, 
line 136, in deserialize
 obj.from_datastruct(datastruct)
   File /usr/lib/python2.4/site-packages/cobbler/collection.py, line 
144, in from_datastruct
 item = self.factory_produce(self.config,seed_data)
   File 
/usr/lib/python2.4/site-packages/cobbler/collection_profiles.py, line 
41, in factory_produce
 return profile.Profile(config).from_datastruct(seed_data)
   File /usr/lib/python2.4/site-packages/cobbler/item_profile.py, line 
87, in from_datastruct
 self.set_parent(self.parent)
   File /usr/lib/python2.4/site-packages/cobbler/item_profile.py, line 
131, in set_parent
 raise CX(_(profile %s not found, inheritance not possible) % 
parent_name)
cobbler.cexceptions.CX: 'profile CentOS-5.2-x86_64 not found, 
inheritance not possible'
[FAILED]
error: %post(cobbler-1.2.6-1.el5.noarch) scriptlet failed, exit status 1

Any ideas?

Cheers,
Harry
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Re: yum upgrade to 1.2.6-1.el5

[Harry Hoffman]

According to func-inventory (yay!) I was running 'cobbler 0 1.2.5 1.el5 
noarch'

I've synced regularly over the past few days as we've been installing a 
few systems.

I'm using serializers_yaml and can see the profile listed in 
/var/lib/cobbler/profiles:

I can see the profiles in there.

Should I erase and re-install cobbler? b/c I don't think that I'll be 
able to just do a rpm -Uvh if the versions are the same.

Cheers,
Harry

Michael DeHaan wrote:
 Harry Hoffman wrote:
 Just upgraded to the latest cobbler from epel-testing... the 
 post-install script fails :-(

 Updating  : cobbler  ### [ 5/10]
 profile CentOS-5.2-x86_64 not found, inheritance not possible

 Stopping cobbler daemon: [  OK  ]
 Starting cobbler daemon: Traceback (most recent call last):
File /usr/bin/cobblerd, line 32, in ?
  api = bootapi.BootAPI()
File /usr/lib/python2.4/site-packages/cobbler/api.py, line 90, in 
 __init__
  self.deserialize()
File /usr/lib/python2.4/site-packages/cobbler/api.py, line 448, in 
 deserialize
  return self._config.deserialize()
File /usr/lib/python2.4/site-packages/cobbler/config.py, line 186, 
 in deserialize
  serializer.deserialize(self._profiles)
File /usr/lib/python2.4/site-packages/cobbler/serializer.py, line 
 125, in deserialize
  rc = storage_module.deserialize(obj,topological)
File 
 /usr/lib/python2.4/site-packages/cobbler/modules/serializer_yaml.py, 
 line 136, in deserialize
  obj.from_datastruct(datastruct)
File /usr/lib/python2.4/site-packages/cobbler/collection.py, line 
 144, in from_datastruct
  item = self.factory_produce(self.config,seed_data)
File 
 /usr/lib/python2.4/site-packages/cobbler/collection_profiles.py, line 
 41, in factory_produce
  return profile.Profile(config).from_datastruct(seed_data)
File /usr/lib/python2.4/site-packages/cobbler/item_profile.py, line 
 87, in from_datastruct
  self.set_parent(self.parent)
File /usr/lib/python2.4/site-packages/cobbler/item_profile.py, line 
 131, in set_parent
  raise CX(_(profile %s not found, inheritance not possible) % 
 parent_name)
 cobbler.cexceptions.CX: 'profile CentOS-5.2-x86_64 not found, 
 inheritance not possible'
 [FAILED]
 error: %post(cobbler-1.2.6-1.el5.noarch) scriptlet failed, exit status 1

 Any ideas?

 Cheers,
 Harry
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
   
 
 What version were you running previously? Could it be that the profile 
 just didn't exist before and now the problem with the subprofile lacking 
 a parent was caught?
 
 Since cobbler no longer requires cobbler sync to be run frequently, that 
 kind of error detection might not occur until an event that requires the 
 object to be re-processed. Removal of the parent object should not be 
 possible without the API getting in the way, though it might have been 
 removed manually.
 
 You can do a rpm -Uvh --noscripts to skip the call to cobbler 
 reserialize and /sbin/services cobblerd restart in the bottom. This may 
 help you look at the problem.
 
 Depending on whether you are using serializers_yaml or 
 serializer_catalog in /etc/cobbler/modules.conf, check 
 /var/lib/cobbler/profiles or /var/lib/cobbler/config/profiles.d and see 
 what you have in there.
 
 --Michael
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Re: Tighter func integration

[Harry Hoffman]

Yep! that's exactly what I had in mind. This could extend out to other 
services that would be configured at install time and ppl could chose 
whether or not to enable the firewall rules via snippets :-)

Cheers,
Harry



Michael DeHaan wrote:
 Harry Hoffman wrote:
 This is awesome!

 Can you integrate iptables into the %post snippet or should that just be 
 left as a exercise per deployment?
   
 
 My first thought was that it should be a per-deployment thing.   
 However, it may encourage best practices if we do something about this
 with regard to the sample templates.   Interesting idea.
 
 If it's as simple as cobbler profile edit --name=foo 
 --iptables-rules=/etc/iptables.template (default nothing) that's not 
 too intrusive at all.
 
 We could then have SNIPPET::enable_iptables_if_configured and 
 SNIPPET::install_assigned_iptables_rules as special snippets.
 
 And we could ship some good starter rules/templates so people could use 
 them, ones that were set up to auto-allow Func and Cobbler and other
 similar services.
 
 Naturally the default for this should be no assignment and folks who 
 didn't want to use this feature could still do things their own way.
 
 I kind of like this what did you have in mind?Does that sound 
 similar?
 
 Cheers,
 harry



 Michael DeHaan wrote:
   
 I'm working on some features on the development branch (Cobbler 1.3 and 
 later) that will make it very easy for admins to set up new 
 machines/nodes so that they are running Func out of the box.   I think 
 this is a very powerful way to deploy things so that they are 
 controllable later and should hopefully introduce more people to Func 
 (http://fedorahosted.org/func). 
 You can read more about what I'm doing here:

 https://fedorahosted.org/cobbler/wiki/FuncIntegration

 On a related note, I still need some help testing the Puppet external 
 nodes integration feature on the devel branch ... 
 https://fedorahosted.org/cobbler/wiki/UsingCobblerWithConfigManagementSystem

 In conjunction these become nicely powerful in that you have a config 
 management system and also a system (Func!) for one-off tasks, misc 
 scripting, and do this now! type activity.   Coupled with a deployment 
 system (Cobbler) this becomes especially nice.

 Read an outside view on this in terms of Francesco Crippa's presentation 
 to Linux TAG this year:

 http://people.byte-code.com/fcrippa/wp-content/uploads/2008/06/fcrippa_large-scale-env.pdf

 --Michael






 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
   
 
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Re: [ANNOUNCE] Cobbler 1.2.2

[Harry Hoffman]

Hmm, not quite there... running cobbler sync after the upgrade (and 
moving the new settings file into place):

[EMAIL PROTECTED] cobbler]# cobbler sync

local variable 'elilo' referenced before assignment
   File /usr/lib/python2.4/site-packages/cobbler/cobbler.py, line 77, 
in main
 rc = BootCLI().run(sys.argv)

   File /usr/lib/python2.4/site-packages/cobbler/cobbler.py, line 57, 
in run
 return self.loader.run(args)

   File /usr/lib/python2.4/site-packages/cobbler/commands.py, line 
116, in run
 return fn.run()

   File /usr/lib/python2.4/site-packages/cobbler/modules/cli_misc.py, 
line 223, in run
 return self.api.sync()

   File /usr/lib/python2.4/site-packages/cobbler/api.py, line 381, in sync
 return sync.run()

   File /usr/lib/python2.4/site-packages/cobbler/action_sync.py, line 
101, in run
 self.dhcp.write_dhcp_file()

   File 
/usr/lib/python2.4/site-packages/cobbler/modules/manage_isc.py, line 
233, in write_dhcp_file
 metadata = {

Cheers,
Harry


Harry Hoffman wrote:
 w00t! that's awesome as it fixes two things that bit me.
 
 Thanks for all of the hard work!
 
 Cheers,
 Harry
 
 Michael DeHaan wrote:
 Cobbler 1.2.2 contains bugfixes from 1.2.1, and is a continuation of the 
 previous releases in support of the 1.2.0 stable branch.  We will 
 continue to address bugfixes in 1.2.X until we get close to releasing 1.4

 You can find source RPMs and tarballs here:

 http://people.fedoraproject.org/~mdehaan/files/cobbler/

 In addition, this has been submitted to the Fedora mirrors (F9, F8) and 
 EPEL (EL5, EL4) mirrors as usual.

 The change list is very short.  This fixes 3 relatively minor bugs:   It 
 no longer loads the elilo location from the settings file, fixing users 
 who don't have that setting stored there (and who are also using DHCP 
 management).   It now loads the netboot_enabled field in the WebUI 
 correctly.   Finally, it adds named_conf, which is a configuration 
 parameter to specify where BIND is located if using DNS management with 
 BIND, to the config file.  Finally it also packages a few directories 
 that were previously not owned by cobbler.

 You will also notice I've just made http://cobbler.et.redhat.com/ a 
 simple redirect to http://fedorahosted.org/cobbler.  It's pretty clear 
 that's the center of cobbler documentation land now, and now this allows 
 anyone to fix the documentation anywhere it lives on the site.  

 --Michael
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Re: [ANNOUNCE] Cobbler 1.2.2

[Harry Hoffman]

which 1.2 is this? I believe that particular error was fixed in 1.2.2 
(but still existed in 1.2.1).

Cheers,
Harry


Demetri Mouratis wrote:
 On Sat, Sep 6, 2008 at 5:16 AM, Harry Hoffman [EMAIL PROTECTED] wrote:
 Hmm, not quite there... running cobbler sync after the upgrade (and
 moving the new settings file into place):

 [EMAIL PROTECTED] cobbler]# cobbler sync

 local variable 'elilo' referenced before assignment
   File /usr/lib/python2.4/site-packages/cobbler/cobbler.py, line 77,
 in main
 rc = BootCLI().run(sys.argv)

   File /usr/lib/python2.4/site-packages/cobbler/cobbler.py, line 57,
 in run
 return self.loader.run(args)

   File /usr/lib/python2.4/site-packages/cobbler/commands.py, line
 116, in run
 return fn.run()

   File /usr/lib/python2.4/site-packages/cobbler/modules/cli_misc.py,
 line 223, in run
 return self.api.sync()

   File /usr/lib/python2.4/site-packages/cobbler/api.py, line 381, in sync
 return sync.run()

   File /usr/lib/python2.4/site-packages/cobbler/action_sync.py, line
 101, in run
 self.dhcp.write_dhcp_file()

   File
 /usr/lib/python2.4/site-packages/cobbler/modules/manage_isc.py, line
 233, in write_dhcp_file
 metadata = {

 Cheers,
 Harry
 
 Hi,
 
 Similar error here.  This is 1.2 running on CentOS 4:
 
 [EMAIL PROTECTED] ~]# cobbler sync
 
 bootloaders
   File /usr/lib/python2.3/site-packages/cobbler/cobbler.py, line 77, in main
 rc = BootCLI().run(sys.argv)
 
   File /usr/lib/python2.3/site-packages/cobbler/cobbler.py, line 57, in run
 return self.loader.run(args)
 
   File /usr/lib/python2.3/site-packages/cobbler/commands.py, line 113, in 
 run
 return fn.run()
 
   File /usr/lib/python2.3/site-packages/cobbler/modules/cli_misc.py,
 line 223, in run
 return self.api.sync()
 
   File /usr/lib/python2.3/site-packages/cobbler/api.py, line 381, in sync
 return sync.run()
 
   File /usr/lib/python2.3/site-packages/cobbler/action_sync.py, line
 101, in run
 self.dhcp.write_dhcp_file()
 
   File /usr/lib/python2.3/site-packages/cobbler/modules/manage_isc.py,
 line 157, in write_dhcp_file
 elilo = os.path.basename(self.settings.bootloaders[ia64])
 
   File /usr/lib/python2.3/site-packages/cobbler/settings.py, line
 149, in __getattr__
 raise AttributeError, name
 
 Also, it seems cobbler check is referring to the old config file in a
 status message:
 
 [EMAIL PROTECTED] ~]# cobbler check
 No setup problems found
 Manual review and editing of /var/lib/cobbler/settings is recommended
 to tailor cobbler to your particular configuration.
 Good luck.
 
 Thanks.
 
 -D
 ___
 cobbler mailing list
 cobbler@lists.fedorahosted.org
 https://fedorahosted.org/mailman/listinfo/cobbler
___
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler