<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <meta name=Generator content="Microsoft Word 11 (filtered medium)">  <style>  </style> </head> <body lang=EN-US link=blue vlink=blue> <div class=Section1> You sound like an AIX admin splitting hairs here, but if you’re using intel h/w with a remote mgmt card (or some newer models w/o) you should be able to initiate the reboot/power-on of the node from the Satellite server using something like ipmish.<o:p></o:p> <o:p> </o:p> Frank LaMon<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: rhn-users-bounces@redhat.com [mailto:rhn-users-bounces@redhat.com] On Behalf Of Michael Barrett Sent: Thursday, March 20, 2008 9:21 AM To: Discussions about Red Hat Network (rhn.redhat.com) Subject: Re: [rhn-users] bare metal provisioning<o:p></o:p> </div> <o:p> </o:p> On Wed, Mar 19, 2008 at 4:09 PM, Máirín Duffy <<a href="mailto:duffy@redhat.com">duffy@redhat.com</a>> wrote:<o:p></o:p> <div> <blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt; margin-left:4.8pt;margin-right:0in'> <div> Hi Michael, Michael Barrett wrote:<o:p></o:p> </div> <div> > All of that just talks about PXE boot and kickstart. To say something > does bare metal provisioning implies that the software can remotely > trigger a boot on the hardware without an OS installed with the intent > to install an operating system.<o:p></o:p> </div> The product can absolutely do that, and it uses PXE and kickstart in order to do so. You can align specific ip addresses or ranges to particular kickstart profiles for ip-based customization, and use a customized bootcd or PXE to point all booting baremetal systems to one single Satellite address that then determines which kickstart file to provide to the system base on Satellite-side configuration.<o:p></o:p> <div> > That it has service processor > knowledge. (ie) it logs into the service process and issues the correct > boot command when the user in the application (RHN satellite) selects > that target (the service processor) and issues an OS provisioning job.<o:p></o:p> </div> What do you mean by service processor? Is this something specific to your hardware?<o:p></o:p> <div> > Does RHN Satellite do any of that? Or does it expect me to remotely > trigger the PXE boot via the service processor outside of it?<o:p></o:p> </div> I'm not quite sure I understand what you're asking enough to answer the question.<o:p></o:p> </blockquote> <div> There is a difference between remote OS provisioning and bare metal provisioning. It seems to me RHN Satellite can do remote OS provisioning but cannot facilitate bare metal provisioning. Bare metal provisioning implies RHN Satellite can (1) remotely boot a box causing it to search for a kickstart server without an OS installed and (2) trigger a OS provisioning task over the network. I have not seen where is does #1. I see where it does #2. To achieve #1 people use the service processor native to the hardware or impose terminal server networks with expect scripts. To say RHN Satellite can do number #1 means it has commands the user can select that will interact with these things (service processors or terminal server networks). To date in order to achieve bare metal provisioning with RHN I have to setup the provisioning task and then leave the application and do something (ie boot the box so that it PXE boots) at the host. That's not bare metal OS provisioning...that's remote OS provisioning. <o:p></o:p> </div> <blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt; margin-left:4.8pt;margin-right:0in'> ~m _______________________________________________ rhn-users mailing list <a href="mailto:rhn-users@redhat.com">rhn-users@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/rhn-users" target="_blank">https://www.redhat.com/mailman/listinfo/rhn-users</a><o:p></o:p> </blockquote> </div> <o:p> </o:p> </div> </body> </html> <HTML><BODY><hr size=1> This email transmission and any accompanying attachments may contain CSX privileged and confidential information intended only for the use of the intended addressee. Any dissemination, distribution, copying or action taken in reliance on the contents of this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error please immediately delete it and notify sender at the above CSX email address. Sender and CSX accept no liability for any damage caused directly or indirectly by receipt of this email. </BODY></HTML>