"nodeset netboot" has been deprecated in xcat 2.10:
https://github.com/xcat2/xcat-core/wiki/XCAT_2.10_Release_Notes
"non-osimage features have been deprecated in xCAT 2.10, you could not run
nodeset install|netboot|statelite for RHEL, SLES and Ubuntu nodes any more.
See documentation Convert Non-osimage Based System To Osimage Based System
for more details on how to convert to osimage based configuration."

Trying it anyway yields this:

ismgp92:~ # tabedit nodetype
ismgp92:~ # tabdump nodetype
#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
"lpar",,"ppc64",,,,,,
"test880m","boottarget","ppc64","mytarget",,,,,

ismgp92:~ # nodeset test880m netboot
test880m: netboot boottarget-ppc64-mytarget
Error: stop configuration because yaboot DOES NOT work for  provision,
please change noderes.netboot=grub2 instead.
ismgp92:~ # echo $?
1

ismgp92:~ # tabdump nodetype
#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
"lpar",,"ppc64",,,,,,
"test880m","boottarget","ppc64","mytarget","netboot",,,,


Contrary to what nodeset netboot outputs, I already confirmed that yaboot
does work for provisioning:
It worked in my environment using a manually modified yaboot.conf file.

Despite the error message, nodeset netboot did create a yaboot.conf which
corresponds to myboottarget:

ismgp92:~ # cat /tftpboot/yaboot.conf-<MACaddr>
#netboot boottarget-ppc64-mytarget
timeout=5
image=linux64
        label=xcat
        initrd=initrd64

ismgp92:~ # tabdump boottarget
#bprofile,kernel,initrd,kcmdline,comments,disable
"mytarget","linux64","initrd64",,,


In that yaboot.conf, an append="..." line is still missing, so no
repository and no autoyast profile are passed to yaboot, which will not
provide a working node provisioning.
If I edit these parameters into boottarget.kcmdline, then nodeset netboot
does add the append=..." line according to boottarget.kcmdline.
But still, xcat does not generate the autoyast profile this way.
Also, following the same procedure with "nodeset install" instead of
"nodeset netboot" doesn't create an autoyast profile.

And still, nodeset netboot|install is deprecated .
As far as I understand the documentations, they are saying that this
functionality has been consolidated into "nodeset osimage=<osimage>".
Doesn't this mean, that there should be a way to successfully do osimage
provisioning using the osimage attribute "boottarget" to specify customized
kernel, initrd (and kcmdline)?




Mit freundlichen Grüßen / Kind regards

Michael Bausch

IT Specialist
GTS Infrastructure Services Delivery DACH
Server and SAP Infrastructure Services
_______________________________________________________________________________________________________________

IBM Deutschland Business & Technology Services GmbH
Ibm-Allee 1
71139 Ehningen
Germany
Mobile: +49-172-7344238
E-Mail: [email protected]
_______________________________________________________________________________________________________________

IBM Deutschland Business & Technology Services GmbH / Geschäftsführung:
Baerbel Altmann, Frank Hammer, Thorsten Moehring
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart,
HRB 17122



From:   "Casandra H Qiu" <[email protected]>
To:     xCAT Users Mailing list <[email protected]>
Date:   21.12.2015 19:36
Subject:        Re: [xcat-user] failing to specify custom kernel, initrd,
            kcmdline via boottarget



After you set up nodetype table, I think you only needs to do

#nodeset test880m netboot


Thanks,
Casandra
...................................................................
Casandra Hong Qiu
Phone: (845) 433-9291, t/l 293-9291
Office: B/002, Floor 3, Z13
[email protected]



Inactive hide details for "Michael Bausch" ---12/21/2015 11:42:00 AM---I
manually changed my nodetype table and did another nod"Michael Bausch"
---12/21/2015 11:42:00 AM---I manually changed my nodetype table and did
another nodeset attempt. The resulting yaboot.conf is s

From: "Michael Bausch" <[email protected]>
To: xCAT Users Mailing list <[email protected]>
Date: 12/21/2015 11:42 AM
Subject: Re: [xcat-user] failing to specify custom kernel, initrd, kcmdline
via boottarget



I manually changed my nodetype table and did another nodeset attempt.
The resulting yaboot.conf is still the same as in all other attempts
before.

In addition to that, nodeset seems to undo my changes to the nodetype
table:
After running nodeset, the boottarget definitions in the nodetype table
have been changed to what looks like default osimage values:

ismgp92:~ # tabedit nodetype
ismgp92:~ # tabdump nodetype
#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
"lpar",,"ppc64",,,,,,
"test880m","boottarget","ppc64","mytarget",,,,,


ismgp92:~ # nodeset test880m osimage=myimage
test880m: install sles11sp4sap-ppc64-compute


ismgp92:~ # tabdump nodetype
#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
"lpar",,"ppc64",,,,,,
"test880m","sles11sp4sap","ppc64","compute","myimage",,,,


Mit freundlichen Grüßen / Kind regards

Michael Bausch

IT Specialist
GTS Infrastructure Services Delivery DACH
Server and SAP Infrastructure Services
_______________________________________________________________________________________________________________

IBM Deutschland Business & Technology Services GmbH
Ibm-Allee 1
71139 Ehningen
Germany
_______________________________________________________________________________________________________________

IBM Deutschland Business & Technology Services GmbH / Geschäftsführung:
Baerbel Altmann, Frank Hammer, Thorsten Moehring
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart,
HRB 17122

Inactive hide details for "Casandra H Qiu" ---21.12.2015 15:57:17---What's
in your nodetype table? should have something like t"Casandra H Qiu"
---21.12.2015 15:57:17---What's in your nodetype table? should have
something like this in the nodetype table:

From: "Casandra H Qiu" <[email protected]>
To: xCAT Users Mailing list <[email protected]>
Date: 21.12.2015 15:57
Subject: Re: [xcat-user] failing to specify custom kernel, initrd, kcmdline
via boottarget



What's in your nodetype table?

should have something like this in the nodetype table:

#node,os,arch,profile,nodetype,comments,disable
"test880m","boottarget","ppc64","mytarget",,,

You may need to use tabedit nodetype to modify this table if you didn't see
those.


Thanks,
Casandra

...................................................................
Casandra Hong Qiu
Phone: (845) 433-9291, t/l 293-9291
Office: B/002, Floor 3, Z13
[email protected]



Inactive hide details for "Michael Bausch" ---12/19/2015 12:07:10 PM---Hi
all, what is the correct procedure to do xcat osimage"Michael Bausch"
---12/19/2015 12:07:10 PM---Hi all, what is the correct procedure to do
xcat osimage provisioning with

From: "Michael Bausch" <[email protected]>
To: [email protected]
Date: 12/19/2015 12:07 PM
Subject: [xcat-user] failing to specify custom kernel, initrd, kcmdline via
boottarget



Hi all,

what is the correct procedure to do xcat osimage provisioning with
customized kernel, initrd (and kcmdline)?

I am on xcat 2.11 on SLES for SAP Applications 11.4 on IBM Power (ppc64),
trying to do provisioning of the same OS to LPARs of the same architecture.

According to
http://xcat-docs.readthedocs.org/en/2.11/guides/admin-guides/references/man7/osimage.7.html

the following should do the trick:
"boottarget (linuximage.boottarget)
The name of the boottarget definition. When this attribute is set, xCAT
will use the kernel, initrd and kernel params defined in the boottarget
definition instead of the default."

Trying to implement this, I just don't manage to get it working:

ismgp92:~ # lsdef -t osimage myimage
Object name: myimage
boottarget=mytarget
imagetype=linux
osarch=ppc64
osdistroname=sles11sp4sap-ppc64
osname=Linux
osvers=sles11sp4sap
otherpkgdir=/install/post/otherpkgs/sles11sp4sap/ppc64
pkgdir=/install/repos/sles11sp4sap/ppc64
pkglist=/opt/xcat/share/xcat/install/sles/compute.pkglist
profile=compute
provmethod=install
template=/opt/xcat/share/xcat/install/sles/compute.tmpl

ismgp92:~ # tabdump boottarget
#bprofile,kernel,initrd,kcmdline,comments,disable
"mytarget","/install/repos/sles11sp4sap/ppc64/1/suseboot/linux64","/install/repos/sles11sp4sap/ppc64/1/suseboot/initrd64",,,


ismgp92:~ # nodeset test880m osimage=myimage
test880m: install sles11sp4sap-ppc64-compute

I would expect this to create a yaboot.conf file which will use linux64 and
initrd64 as specified in boottarget mytarget.
Instead of that, the generated yaboot.conf will boot kernel inst64 (not
linux64) and no initrd at all; xcat completely ignores my boottarget
specifications:

ismgp92:~ # cat /tftpboot/yaboot.conf-<MACaddr>
#install sles11sp4sap-ppc64-compute
timeout=5
image=xcat/osimage/myimage/inst64
label=xcat
append="quiet autoyast=http://<Server>:<Port>/install/autoinst/test880m
install=http://<Server>:<Port>/install/repos/sles11sp4sap/ppc64/1
netdevice=<MACaddr> dhcptimeout=150"


After manually copying linux64 and initrd64 to /tftpboot
and /tftpboot/xcat/osimage/myimage I also sequentially tried each of the
following boottargets:
"mytarget","xcat/osimage/myimage/linux64","xcat/osimage/myimage/initrd64",,,

"mytarget","/tftpboot/xcat/osimage/myimage/linux64","/tftpboot/xcat/osimage/myimage/initrd64",,,

"mytarget","/tftpboot/linux64","/tftpboot/initrd64",,,
"mytarget","linux64","initrd64",,,

The resulting yaboot.conf file was always the same as above.

I also tried assigning the node to my boottarget via the nodetype table as
documented in
http://sourceforge.net/p/xcat/wiki/BootTarget/
http://sourceforge.net/p/xcat/wiki/XCAT_vSMP_Foundation/

Again, the same result as above.

What is the correct way to assign specific kernel, initrd and kcmdline to a
node's netboot?
Any help would be highly appreciated.


Some words on my reasons for the above:

On my ppc64 hardware, yaboot fails to TFTP download files larger than 32MB.
inst64 as provided by the original SLES 11.4 DVD (which is also used by
xcat) is 34MB in size and therefore netbooting this kernel fails.
The same DVD utilizes a yaboot.cnf which uses a kernel and initrd to boot,
where each of the two files is smaller than 32MB:
image[64bit]=linux64
label=install
append="quiet sysrq=1 insmod=sym53c8xx insmod=ipr "
initrd=initrd64

Running nodeset and then manually editing linux64, initrd64 and kernel
parametrs into yaboot.conf leads to a successful netboot of the LPAR.
I just would like to have xcat insert these details into yaboot.conf
instead of vi.

Also, I would like to setup another osimage to netboot a SLES rescue
environment utilizing the kernel parameter rescue=1.



Mit freundlichen Grüßen / Kind regards

Michael Bausch

IT Specialist
GTS Infrastructure Services Delivery DACH
Server and SAP Infrastructure Services
_______________________________________________________________________________________________________________

IBM Deutschland Business & Technology Services GmbH
Ibm-Allee 1
71139 Ehningen
Germany
_______________________________________________________________________________________________________________

IBM Deutschland Business & Technology Services GmbH / Geschäftsführung:
Baerbel Altmann, Frank Hammer, Thorsten Moehring
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart,
HRB 17122
------------------------------------------------------------------------------

_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

------------------------------------------------------------------------------

_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

------------------------------------------------------------------------------

_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

------------------------------------------------------------------------------

_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

------------------------------------------------------------------------------
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to