As a workaround, I ended up outputting system specific logs on an NFS share on cobbler server and wrote a perl daemon to check for newly created entries and add systems based on the info found there. It does the job know. Still it would be nicer to be able to do it from the target systems directly.

On 26 April 2011 23:58, Scott Henson <shenson@redhat.com> wrote:

On Mon, 25 Apr 2011 18:47:11 +0000 (UTC), Levente Lajko <levente.lajko@gmail.com> wrote:
> Hello Guys,
>
> I am working on a cobbler powered deployment environment to prepare hardware
> for a specific deployment. Here is the scenario:
> 1. Multitude of bare-metal "off the truck" servers
> 2. Loading HP Scripting Toolkit image with some custom scripting via Cobbler
> to update firmware, set iLO, configure RAID.
> 3. For this I use the default system with the Scripting Toolkit's profile
>
> What I'm missing at this point is the ability to prevent pxe boot for the
> default profile after the first boot + auto registration of the servers
> using the Scripting Toolkit's profile.
>
> My understanding is that these options are available only when deploying
> RedHat/Fedora/Centos based images.
>
> Any help would be appreciated.

If you can do a standard HTTP GET, you can hit
/cblr/svc/op/trig/mode/post/system/$SYSTEMNAME on your cobbler
server. This plus enabling PXE_JUST_ONCE in your settings file should
result in your system getting set to boot local. You can do other
interesting things with triggers as well. Even doing auto registration
without koan/python installed. It would be a little difficult, but I'm
pretty sure it is possible.

--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME