Jennifer,
You are specifying that on a system already registered in cobbler that
you want to be able to switch the BIOS setting for boot source? As Alvin
mentioned, at the moment this is not possible, as an alternative you could
script it yourself... I am however, curious to understand the reason for
your needing this functionality provided that you can tell me.
I am not a developer working on cobbler... not yet anyway, however,
since I am a heavy user of cobbler and follow this list very closely I was
curious about your post...
The reason why I am curious is mainly due to the fact that once your
server is set to boot from PXE you shouldn't need to have it changed.
Unless you are pre-defining your servers in cobbler and then using it to
deploy each one?
My set up uses the default system settings to install a base operating
system, automatically register the system to cobbler, determine the system
type (virtual or physical) , reinstall the correct OS/Profile, and then
configure it automatically. This allows me to get my servers from the
factory preset to PXE, press the power button and go.
I would like to see various functionality like this integrated into the
cobbler framework however... of particular interest is turning on and off
CPU components i.e. hyperthreading or virtualization at the BIOS level.
Scott
On Wed, Aug 5, 2015 at 8:44 PM, Jennifer Patrick <[email protected]> wrote:
> Howow would you suggest going about that...
>
> Aside from somehow inserting some manual bit into the python code to do
> this? And even then, what and where?
>
> And why doesn't the CLI work for things like this...?
>
> cobbler system edit --name=test123 --netboot-enabled=true
>
> cobbler system reboot --name=test123
>
> Does not produce a netboot. But ipmitool wiil.
>
> When I do try it that way, I don't even get anything valuable in the logs
> if it's failing to try to set a netboot.
>
>
> Seems like this has been solved or documented by someone somewhere.
>
> On Wed, Aug 5, 2015 at 7:39 AM, Alvin Starr <[email protected]> wrote:
>
>> It was my impression that fence is just to shut a machine down as part of
>> the HA/clustering toolset.
>> All the other features are just added extras that are not needed as part
>> of the primary function.
>>
>> The features from man include on,off,reboot,status,diag,list,monitor.
>>
>> There is no "set to boot from PXE".
>> I believe that you will need to do this manually.
>>
>>
>>
>> On 08/05/2015 05:36 AM, Jennifer Patrick wrote:
>>
>> Just having some woes with making fence_ipmilan work with some Supermicro
>> servers (Don't say use the supermicro IPMI Tool, we're trying to get around
>> that.)
>>
>> The problem is, using fence_ipmilan, we can initiate a boot (off then on)
>> from the web GUI, or from the CLI via...
>>
>>
>> *# cobbler system reboot --name=test123*
>> *task started: 2015-08-05_092815_power*
>> *task started (id=Power management (reboot), time=Wed Aug 5 09:28:15
>> 2015)*
>> *cobbler power configuration is:*
>> * type : ipmilan*
>> * address: 192.168.1.5*
>> * user : user*
>> * id :*
>> *running: /usr/sbin/fence_ipmilan*
>> *running: /usr/sbin/fence_ipmilan*
>> *received on stdout: Powering off machine @ IPMI:**192.168.1.5*
>> *...Failed*
>>
>> *received on stderr:*
>> *running: /usr/sbin/fence_ipmilan*
>> *received on stdout: Powering off machine @ IPMI:**192.168.1.5**...Done*
>>
>> *received on stderr:*
>> *cobbler power configuration is:*
>> * type : ipmilan*
>> * address: **192.168.1.5*
>> * user : user*
>> * id :*
>> *running: /usr/sbin/fence_ipmilan*
>> *received on stdout: Powering on machine @ IPMI:**192.168.1.5**...Failed*
>>
>> *received on stderr: ipmilan: Power still off*
>>
>> *running: /usr/sbin/fence_ipmilan*
>> *received on stdout: Powering on machine @ IPMI:192.168.1.5...Done*
>>
>> *received on stderr:*
>> **** TASK COMPLETE ****
>>
>> So that's great. My real question comes from the fact that I can't make
>> cobbler set these machines to reboot via the Web GUI to Netboot/PXE. It
>> just seems to never issue the right command via fence_ipmilan (which
>> actually uses IPMITOOL)
>>
>> I can do it fine in IPMITOOL:
>>
>> * ipmitool -H 192.168.1.5 -U user -I lanplus -P password chassis bootdev
>> pxe ipmitool -H 192.168.1.5 -U user -I lanplus -P password chassis power
>> reset *
>>
>> And the system reboots into PXE boot mode.
>>
>> So is there something I have to mangle in
>> /etc/cobbler/fence_ipmilan.template?
>>
>> Something Else?
>>
>> All help is appreciated.
>>
>> Thanks.
>>
>> JLP
>>
>>
>> _______________________________________________
>> cobbler mailing
>> [email protected]https://lists.fedorahosted.org/mailman/listinfo/cobbler
>>
>>
>>
>> --
>> Alvin Starr || voice: (905)513-7688
>> Netvel Inc. || Cell: (416)[email protected]
>> ||
>>
>>
>> _______________________________________________
>> cobbler mailing list
>> [email protected]
>> https://lists.fedorahosted.org/mailman/listinfo/cobbler
>>
>>
>
>
> --
>
> [image: Dyn logo, Dyn.com] <http://dyn.com/>
> <http://twitter.com/dyn> <http://twitter.com/dyninc>[image: Dyn
> facebook account] <http://facebook.com/dyn>
> <http://twitter.com/dyninc>[image:
> Dyn LinkedIn account] <http://linkedin.com/company/dyn>
>
> Jennifer Patrick / Sr. Systems Engineer
> 617-335-6284
>
> _______________________________________________
> cobbler mailing list
> [email protected]
> https://lists.fedorahosted.org/mailman/listinfo/cobbler
>
>
_______________________________________________
cobbler mailing list
[email protected]
https://lists.fedorahosted.org/mailman/listinfo/cobbler
