I also see that this support has not been put in genimage yet. Sorry about that . Will open a work item.
Lissa K. Valletta 8-3/B10 Poughkeepsie, NY 12601 (tie 293) 433-3102 From: Lissa Valletta/Poughkeepsie/IBM@IBMUS To: xCAT Users Mailing list <[email protected]>, Cc: xCAT Users Mailing list <[email protected]> Date: 07/31/2013 12:49 PM Subject: Re: [xcat-user] genimage not using osdistroname You need to put that information in the osdistroname attribute in the osimage table not in the osdistro table. The man page for a table explains the attributes in that table, not in other tables. run lsdef v6.3.1-dl-compute I think you will see osdistroname is not set The best way to do things correctly is use the chdef commands for example chdef -t osimage v6.3.1-dl-compute osdistroname=centos6.3-x86_64 Lissa K. Valletta 8-3/B10 Poughkeepsie, NY 12601 (tie 293) 433-3102 Inactive hide details for Russell Jones ---07/30/2013 03:56:47 PM---Hi devs, According to the man page for the osimage table, oRussell Jones ---07/30/2013 03:56:47 PM---Hi devs, According to the man page for the osimage table, osdistroname is From: Russell Jones <[email protected]> To: xCAT Users Mailing list <[email protected]>, Date: 07/30/2013 03:56 PM Subject: [xcat-user] genimage not using osdistroname Hi devs, According to the man page for the osimage table, osdistroname is supposed to.....: osdistroname The name of the OS distro definition. This attribute can be used to specify which OS distro to use, instead of using the osname,osvers,and osarch attributes. I have this set, however when I try to do a genimage: [root@csclprd3 postscripts]# genimage v6.3.1-dl-compute Generating image: Error: osimage.osvers, osimage.osarch, osimage.profile and osimage.provmethod must be specified for the image v6.3.1-dl-compute in the database. Here's my osdistro table: #osdistroname,basename,majorversion,minorversion,arch,type,dirpaths,comments,disable "centos6.3-x86_64","centos","6","3","x86_64","Linux","/install/centos6.3/x86_64",, An lsdef of my osimage: Object name: v6.3.1-dl-compute groups=all imagetype=linux osarch=x86_64 osdistroname=centos6.3-x86_64 osname=Linux osvers=centos6.3 otherpkgdir=/install/post/otherpkgs/centos6.3/x86_64/ otherpkglist=/install/custom/netboot/centos/v6.3.1-dl-compute.otherpkgs.pkglist pkgdir=/install/centos6.3/x86_64/ pkglist=/install/custom/netboot/centos/v6.3.1-dl-compute.pkglist postbootscripts=otherpkgs postinstall=/install/custom/netboot/centos/v6.3.1-dl-compute.postinstall postscripts=hardeths,syslog,remoteshell,syncfiles,confignics,nfs_mounts.sh,setupscratch_nextgen.sh,localrepo.sh,sge_execd.sh,setupntp profile=v6.3.1-dl-compute provmethod=netboot rootimgdir=/install/netboot/centos6.3/x86_64/v6.3.1-dl-compute The only way to get past this is to set osvers and osarch. Thoughts? ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
<<inline: graycol.gif>>
------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
