Heh, I got it to work by hacking a "next" command into the port 3002 installmonitor and using "updateflag.awk $XCAT 3002 next". It's not the right way to do it, but it allowed me to move forward and get all of the pieces together.
I'll try again using stunnel. On 07/28/2011 01:46 AM, Xiao Peng Wang wrote: > > You should make the 'nextdestiny' was run to change the chain list in > the chain table. You can tabdump chain table to see whether it has > happened to move the 'install' into the currstate. The nextdestiny > cannot work without the help of stunnel, refer to the > /etc/init.d/S11stunnel in the nbfs.gz > > The important thing is after running of configure, the biossetup > system should reboot so that system can do the next destiny. > > Thanks > Best Regards > ---------------------------------------------------------------------- > Wang Xiaopeng (王晓朋) > IBM China System Technology Laboratory > Tel: 86-10-82453455 > Email: [email protected] > Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, > Haidian District Beijing P.R.China 100193 > > Inactive hide details for Garrick Staples ---2011-07-28 > 04:09:07---What's the proper way to chain through a netboot osimage? > I'Garrick Staples ---2011-07-28 04:09:07---What's the proper way to > chain through a netboot osimage? I've created an image (genimage/packimage > > From: Garrick Staples <[email protected]> > To: xCAT Users Mailing list <[email protected]> > Date: 2011-07-28 04:09 > Subject: [xcat-user] chain through a stateless netboot osimage? > > ------------------------------------------------------------------------ > > > > What's the proper way to chain through a netboot osimage? I've created > an image (genimage/packimage) that does BIOS updates and configs and it > works great. I just can't seem to chain out of it. I copied the > "nextdestiny" scripts into my new netboot image and they seem to run > without error. > > Upon discovery, I want xCAT to do nodediscover, bmcsetup, boot to my > biossetup profile, and then do a full disk install of centos. > > I have a group entry in the chain table: > "metal",,,"runcmd=bmcsetup,osimage=centos5.6-x86_64-netboot-biossetup,install=centos5-x86_64-metal","nodediscover",, > > > All of the individual parts work. I can nodeset it to runcmd=bmcsetup > and it does chain through to biossetup, but then it gets stuck. xcatd > never changes the boot state again. What's the magic to get xcatd to > nodeset to install=centos5-x86_64-metal? > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > xCAT-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xcat-user > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > > > _______________________________________________ > xCAT-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xcat-user ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
