If we had the following commands:
cobbler system edit --name=foo --poweron-command="..." cobbler system edit --name=foo --poweroff-command="..." # we will probably also have a defaultpoweron type command in settings if we do this to avoid repeated entry
cobbler system edit --name=foo --netboot-enabled=true cobbler system power --name=foo --power=on # or maybe reboot cobbler system power --name=foo --power=off
Would that work for people?
What power management systems do you use, and if so, what are the commands you typically run (give bash examples) to power on, off, and reboot nodes?
If we have the above it would be very easy to expose in the webapp, though I'd like to get it right in the CLI first.
If you can help supply me with some background info, we can see about getting this done. I think the ability to be able to reinstall a node without having to go somewhere else to power cycle it would be very useful.
--Michael
Michael DeHaan wrote:
If we had the following commands:
cobbler system edit --name=foo --poweron-command="..." cobbler system edit --name=foo --poweroff-command="..." # we will probably also have a defaultpoweron type command in settings if we do this to avoid repeated entry
cobbler system edit --name=foo --netboot-enabled=true cobbler system power --name=foo --power=on # or maybe reboot cobbler system power --name=foo --power=off
Would that work for people?
What power management systems do you use, and if so, what are the commands you typically run (give bash examples) to power on, off, and reboot nodes?
If we have the above it would be very easy to expose in the webapp, though I'd like to get it right in the CLI first.
If you can help supply me with some background info, we can see about getting this done. I think the ability to be able to reinstall a node without having to go somewhere else to power cycle it would be very useful.
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
So I can change "reboot" above to just "off" and "on", universally?
So far it looks like we're adding the following fields to each cobbler system:
fence_address fence_user fence_password fence_type == none, ilo, drac, etc
Each filed would have a default value in settings so you wouldn't have to fill it in if your network was homogenous (or you could be clever and do it with xargs and 'cobbler find' and 'grep')
Sound good?
This way you wouldn't have to put in the full command, we could just build the command based on the type of fence command wanted, saving effort.
What else am I missing? Does someone use something other than fence?
--Michael
Michael DeHaan wrote:
Michael DeHaan wrote:
If we had the following commands:
cobbler system edit --name=foo --poweron-command="..." cobbler system edit --name=foo --poweroff-command="..." # we will probably also have a defaultpoweron type command in settings if we do this to avoid repeated entry
cobbler system edit --name=foo --netboot-enabled=true cobbler system power --name=foo --power=on # or maybe reboot cobbler system power --name=foo --power=off
Would that work for people?
What power management systems do you use, and if so, what are the commands you typically run (give bash examples) to power on, off, and reboot nodes?
If we have the above it would be very easy to expose in the webapp, though I'd like to get it right in the CLI first.
If you can help supply me with some background info, we can see about getting this done. I think the ability to be able to reinstall a node without having to go somewhere else to power cycle it would be very useful.
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
So I can change "reboot" above to just "off" and "on", universally?
So far it looks like we're adding the following fields to each cobbler system:
fence_address fence_user fence_password fence_type == none, ilo, drac, etc
Each filed would have a default value in settings so you wouldn't have to fill it in if your network was homogenous (or you could be clever and do it with xargs and 'cobbler find' and 'grep')
Sound good?
This way you wouldn't have to put in the full command, we could just build the command based on the type of fence command wanted, saving effort.
What else am I missing? Does someone use something other than fence?
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Here are the current thoughts Bill Peck and I are thinking about:
https://fedorahosted.org/cobbler/wiki/PowerManagement
We'll implement that as described unless anyone else has additional improvement ideas.
Kind of off topic, but similar functionality. It may be worth while also considering some host level integration tools such as hpbootcfg and kexec (maybe) that could be merged into koan with the command below. If you run hpbootcfg -p it will set the host to one time PXE boot on next boot up only (if you dont always pxe on every boot).
-r, --replace-self reinstall this host at next reboot
On Thu, Nov 13, 2008 at 1:23 PM, Michael DeHaan mdehaan@redhat.com wrote:
Michael DeHaan wrote:
Michael DeHaan wrote:
If we had the following commands:
cobbler system edit --name=foo --poweron-command="..." cobbler system edit --name=foo --poweroff-command="..." # we will probably also have a defaultpoweron type command in settings if we do this to avoid repeated entry
cobbler system edit --name=foo --netboot-enabled=true cobbler system power --name=foo --power=on # or maybe reboot cobbler system power --name=foo --power=off
Would that work for people?
What power management systems do you use, and if so, what are the commands you typically run (give bash examples) to power on, off, and reboot nodes?
If we have the above it would be very easy to expose in the webapp, though I'd like to get it right in the CLI first.
If you can help supply me with some background info, we can see about getting this done. I think the ability to be able to reinstall a node without having to go somewhere else to power cycle it would be very
useful.
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
So I can change "reboot" above to just "off" and "on", universally?
So far it looks like we're adding the following fields to each cobbler system:
fence_address fence_user fence_password fence_type == none, ilo, drac, etc
Each filed would have a default value in settings so you wouldn't have to fill it in if your network was homogenous (or you could be clever and do it with xargs and 'cobbler find' and 'grep')
Sound good?
This way you wouldn't have to put in the full command, we could just build the command based on the type of fence command wanted, saving
effort.
What else am I missing? Does someone use something other than fence?
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Here are the current thoughts Bill Peck and I are thinking about:
https://fedorahosted.org/cobbler/wiki/PowerManagement
We'll implement that as described unless anyone else has additional improvement ideas.
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Christopher Johnston wrote:
Kind of off topic, but similar functionality. It may be worth while also considering some host level integration tools such as hpbootcfg and kexec (maybe) that could be merged into koan with the command below. If you run hpbootcfg -p it will set the host to one time PXE boot on next boot up only (if you dont always pxe on every boot).
In case you missed it, Charles Duffy has added support for kexec (--kexec) which is a supplemental argument to --replace-self, so the system can be reinstalled via koan (where supported) without being rebooted.
I'm not sure what we get from integrating with something like hpbootcfg when it's not universally available, seems like if you had systems that used it you could get away just as well by flipping them using Func + hpcootcfg directly (or SSH, if you wanted, though Func is in some ways easier).
Also, it is nicer if you do set them up to PXE first every time, seeing cobbler has the --netboot-enabled flag and the pxe_just_once feature to help control when to reinstall them.
-r, --replace-self reinstall this host at next reboot
On Thu, Nov 13, 2008 at 1:23 PM, Michael DeHaan <mdehaan@redhat.com mailto:mdehaan@redhat.com> wrote:
Michael DeHaan wrote: > Michael DeHaan wrote: > >> If we had the following commands: >> >> cobbler system edit --name=foo --poweron-command="..." >> cobbler system edit --name=foo --poweroff-command="..." >> # we will probably also have a defaultpoweron type command in settings >> if we do this to avoid repeated entry >> >> cobbler system edit --name=foo --netboot-enabled=true >> cobbler system power --name=foo --power=on # or maybe reboot >> cobbler system power --name=foo --power=off >> >> Would that work for people? >> >> What power management systems do you use, and if so, what are the >> commands you typically run (give bash examples) to power on, off, and >> reboot nodes? >> >> If we have the above it would be very easy to expose in the webapp, >> though I'd like to get it right in the CLI first. >> >> If you can help supply me with some background info, we can see about >> getting this done. I think the ability to be able to reinstall a node >> without having to go somewhere else to power cycle it would be very useful. >> >> --Michael >> >> _______________________________________________ >> cobbler mailing list >> cobbler@lists.fedorahosted.org <mailto:cobbler@lists.fedorahosted.org> >> https://fedorahosted.org/mailman/listinfo/cobbler >> >> > > So I can change "reboot" above to just "off" and "on", universally? > > > So far it looks like we're adding the following fields to each cobbler > system: > > fence_address > fence_user > fence_password > fence_type == none, ilo, drac, etc > > Each filed would have a default value in settings so you wouldn't have > to fill it in if your network was homogenous (or you could be clever and > do it with xargs and 'cobbler find' and 'grep') > > Sound good? > > This way you wouldn't have to put in the full command, we could just > build the command based on the type of fence command wanted, saving effort. > > What else am I missing? Does someone use something other than fence? > > --Michael > > > > > > _______________________________________________ > cobbler mailing list > cobbler@lists.fedorahosted.org <mailto:cobbler@lists.fedorahosted.org> > https://fedorahosted.org/mailman/listinfo/cobbler > Here are the current thoughts Bill Peck and I are thinking about: https://fedorahosted.org/cobbler/wiki/PowerManagement We'll implement that as described unless anyone else has additional improvement ideas. _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org <mailto:cobbler@lists.fedorahosted.org> https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler@lists.fedorahosted.org