Have a use case that maybe unique to us as were not unfortunately using
DHCP or all our vlans. We automate on demand VMware guests by using a
workflow engine to; create the guest images, cobbler system record, request
cobbler buildiso, attach iso and boot guest, detach iso. Our issue is
the
On Fri, Dec 30, 2011 at 1:10 PM, wrote:
>
>
> Have a use case that maybe unique to us as were not unfortunately using DHCP
> or all our vlans. We automate on demand VMware guests by using a workflow
> engine to; create the guest images, cobbler system record, request cobbler
> buildiso, attach i
On Fri 30/12/11 12:27 PM , Jörgen Maas wrote:On Fri, Dec 30, 2011 at 1:10
PM, wrote:
>
>
> Have a use case that maybe unique to us as were not unfortunately using
DHCP
> or all our vlans. We automate on demand VMware guests by using a
workflow
> engine to; create the guest images, cobble
This feature already exists.Create a system named "default":
cobbler system add --name=default --profile=foo
PXE also works by IP, so it at least used to work that you could create a
system ip in CIDR notation to get the same thing for just a part of your
network:
cobbler system add --name
Ah, you said ontimeout? Try editing the templates in /etc/cobbler… the
"local" part is in that template, not the cobbler source, so you can change it.
-- Michael
On Friday, December 30, 2011 at 11:20 AM, Michael DeHaan wrote:
> This feature already exists.Create a system named "default":
Right you can change the bootiso template but the ontimeout value needs to
match the System or Profile name your requesting, in this use case its always a
system since were creating single system iso's passing the ip details on the
boot line, call it a very poor replacement for dhcp. We can no
"Right you can change the bootiso template but the ontimeout value needs to
match the System or Profile name your requesting,"
If you know what it's going to timeout to, you should just set the IP/MAC so it
boots directly and not use the menu, otherwise you won't know what you are
supposed to d
Thats not an option as the action_buildiso code is inserting syslinux menu
commands, also I only need this for virtual for physical I would want default
Local in place e.g. hence supplying an option to buildiso would be nice.
I think this is probably just a use case for this particular env, I
On Tue, Jan 3, 2012 at 4:30 PM, Simon Woolsgrove wrote:
>
> I think this is probably just a use case for this particular env, I will
> take a look at a patch and see if it makes sense.
>
I think this is very much true ;-)
--
Grtz,
Jörgen Maas
___
co
