On a hunch I tried using the install keyword with nodeset in additon to
osimage, and it actually set the provmethod to install like I wanted, but I
got a warning:

# nodeset xcat-serv1 install osimage=centos6.4-x86_64-install-service
Warning: The options "install", "netboot", and "statelite" have been
deprecated. They should continue to work in this release, but have not been
tested as carefully, and some new functions are not available with these
options.  For full function and support, use "nodeset <noderange>
osimage=<osimage_name>" instead.
xcat-serv1: install centos6.4-x86_64-service

# lsdef xcat-serv1
Object name: xcat-serv1
    arch=x86_64
    currchain=boot
    currstate=install centos6.4-x86_64-service
    groups=service,ipmi,all
    initrd=xcat/centos6.4/x86_64/service/initrd.img
    installnic=mac
    ip=10.20.254.227
    kcmdline=quiet repo=http://10.20.0.1:80/install/centos6.4/x86_64 ks=
http://10.20.0.1:80/install/autoinst/xcat-serv1 ksdevice=00:50:56:bc:0c:db
    kernel=xcat/centos6.4/x86_64/service/vmlinuz
    mac=00:50:56:bc:0c:db
    netboot=xnba
    nfsserver=10.20.0.1
    nodetype=osi
    os=centos6.4

postscripts=syslog,remoteshell,ospkgs,addsiteyum,otherpkgs,syncfiles,ifcfg-eth,fstab,servicenode
    primarynic=mac
    profile=service
    provmethod=install
    setupconserver=1
    setupdhcp=1
    setupnameserver=1
    setupnfs=1
    setupntp=1
    setuptftp=1
    status=booting
    statustime=01-17-2014 16:05:46
    tftpserver=10.20.0.1
    updatestatus=failed
    updatestatustime=01-17-2014 17:47:47
    xcatmaster=10.20.0.1

If that warning is correct that "install", "netboot", and "statelite" are
deprecated then that means that we cannot use the
/install/custom/<install|netboot|statelite>/<platform> directories any
more. Does that mean we will have to have one directory for each osimage
name under /install/custom/ now? That would be significantly less
convenient - though doable. Since you also suggested
/install/custom/install/centos
as a good directory to use, were you aware of this?

That actually lines up with the (now deprecated?) documentation though:
"On Linux, if provmethod for the node is install, netboot or statelite ,
the os, profile, and arch of that node are used to search for the files in
/install/custom/provmethod>/<platform> first, and then in
/opt/xcat/share/xcat/<provmethod>/<platform>."
http://sourceforge.net/apps/mediawiki/xcat/index.php?title=Using_Provmethod%3Dinstall,netboot_or_statelite


In any case, what is the recommended thing for me to do given my
configuration?

-Josh


On Tue, Jan 21, 2014 at 4:24 PM, Josh Nielsen <jniel...@hudsonalpha.org>wrote:

> Okay, great. I have the new service image created now. I am confused
> though why it is giving the node the incorrect provmethod though when I
> nodeset it. Here is it the output from my terminal:
>
> # lsdef -t osimage -l centos6.4-x86_64-install-service
> Object name: centos6.4-x86_64-install-service
>     imagetype=linux
>     osarch=x86_64
>     osname=Linux
>     osvers=centos6.4
>     otherpkgdir=/install/post/otherpkgs/centos6.4/x86_64
>     pkgdir=/install/centos6.4/x86_64
>     pkglist=/install/custom/install/centos/service.otherpkgs.pkglist
>     profile=service
>     provmethod=install
>     template=/install/custom/install/centos/service.tmpl
>
> # nodeset xcat-serv1 osimage=centos6.4-x86_64-install-service
> xcat-serv1: install centos6.4-x86_64-service
>
> # lsdef xcat-serv1
> Object name: xcat-serv1
>     arch=x86_64
>     currchain=boot
>     currstate=install centos6.4-x86_64-service
>     groups=service,ipmi,all
>     initrd=xcat/osimage/centos6.4-x86_64-install-service/initrd.img
>     installnic=mac
>     ip=10.20.254.227
>     kcmdline=quiet repo=http://10.20.0.1:80/install/centos6.4/x86_64 ks=
> http://10.20.0.1:80/install/autoinst/xcat-serv1 ksdevice=00:50:56:bc:0c:db
>     kernel=xcat/osimage/centos6.4-x86_64-install-service/vmlinuz
>     mac=00:50:56:bc:0c:db
>     netboot=xnba
>     nfsserver=10.20.0.1
>     nodetype=osi
>     os=centos6.4
>
> postscripts=syslog,remoteshell,ospkgs,addsiteyum,otherpkgs,syncfiles,ifcfg-eth,fstab,servicenode
>     primarynic=mac
>     profile=service
>     provmethod=centos6.4-x86_64-install-service
>     setupconserver=1
>     setupdhcp=1
>     setupnameserver=1
>     setupnfs=1
>     setupntp=1
>     setuptftp=1
>     status=booting
>     statustime=01-17-2014 16:05:46
>     tftpserver=10.20.0.1
>     updatestatus=failed
>     updatestatustime=01-17-2014 17:47:47
>     xcatmaster=10.20.0.1
>
> The provmethod is set to "install" on the service image but somehow the
> nodeset is giving the node "provmethod=centos6.4-x86_64-install-service"
> instead. From a previous deployment I discovered that this causes it to
> look for the .tmpl and .pkglist files in
> /install/custom/centos6.4-x86_64-install-service/centos (following the
> /install/custom/<provmethod>/<OS> scheme) which does not exist. I'm not
> sure if that will cause problems with the "initrd" and "kernel" options as
> well. What is xcat/osimage/* relative to for those parameters, since the
> full path is not given? I don't recognize the path.
>
> Thanks,
> Josh
>
>
> On Tue, Jan 21, 2014 at 12:07 PM, Linda Mellor <mel...@us.ibm.com> wrote:
>
>> Josh,
>> Unfortunately, it looks like xCAT does not provide a pre-defined service
>> node install image for centos.  Our development and test efforts for the RH
>> variations (centos, fedora, etc.) are pretty limited due to resource
>> constraints.  So, you will need to create your own osimage definition for
>> this.
>>
>> Since you are doing a fulldisk install, I would suggest making a copy of
>> one of your existing centos install images:
>>
>>    lsdef -t osimage -l -z -o centos6.4-x86_64-install-all >
>>    /tmp/service.def
>>
>> Edit the definition file, changing any "install-all" filenames to new
>> filenames for files you will create.  Putting them somewhere like
>> /install/custom/install/centos  might be a good location.  Then you can
>> look at the files xCAT ships for service node images in fedora or redhat:
>>  /opt/xcat/share/xcat/install/fedora or /opt/xcat/share/xcat/install/rh,
>> finding something that will be a good starting point.  Copy those files to
>> your custom directory, rename/edit them as you need to for centos.
>>
>> Then edit that /tmp/service.def you created to point to your new custom
>> files, and change the name of the osimage object to a new name for your
>> image.  Next, create your new xCAT osimage definition:
>>
>>    cat /tmp/service.def | mkdef -z
>>    lsdef -t osimage -l <your new image name>
>>
>> Then you should be able to simply:
>>
>>    nodeset <node> osimage=<your new image name>
>>
>> and see the correct install template file get created in
>> /install/autoinst/<node>
>> Finally, network boot the node to start the install process.
>>
>>
>> I assume you are already following this, but the section on installing a
>> diskfull service node in the Linux Hierarchical Cluster doc is a pretty
>> good resource for most of this:
>>
>> http://sourceforge.net/apps/mediawiki/xcat/index.php?title=Setting_Up_a_Linux_Hierarchical_Cluster#Set_Up_the_Service_Nodes_for_Stateful_.28Diskful.29_Installation
>>
>> Linda
>>
>> [image: Inactive hide details for Josh Nielsen ---01/21/2014 11:15:36
>> AM---Actually genimage looks like it is for statelite images, whi]Josh
>> Nielsen ---01/21/2014 11:15:36 AM---Actually genimage looks like it is for
>> statelite images, which is not what I need. I in fact need to
>>
>> From: Josh Nielsen <jniel...@hudsonalpha.org>
>> To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>,
>> Date: 01/21/2014 11:15 AM
>> Subject: Re: [xcat-user] Determine which otherpkgs.pkglist file is being
>> used
>> ------------------------------
>>
>>
>>
>> Actually genimage looks like it is for statelite images, which is not
>> what I need. I in fact need to create a centos6.4-x86_64-install-service
>> image since I do not have one (see my centos 6.4 images below). I don't
>> have to run copycds again do I? How do I create a new osimage definition
>> specifically with a "service" profile?
>>
>> My existing Centos 6.4 images:
>>
>> centos6.4-x86_64-install-all  (osimage)
>> centos6.4-x86_64-install-compute  (osimage)
>> centos6.4-x86_64-install-iscsi  (osimage)
>> centos6.4-x86_64-install-kvm  (osimage)
>> centos6.4-x86_64-install-login  (osimage)
>> centos6.4-x86_64-install-storage  (osimage)
>> centos6.4-x86_64-install-xen  (osimage)
>> centos6.4-x86_64-netboot-compute  (osimage)
>> centos6.4-x86_64-netboot-kvm  (osimage)
>> centos6.4-x86_64-netboot-xen  (osimage)
>> centos6.4-x86_64-statelite-compute  (osimage)
>> centos6.4-x86_64-statelite-kvm  (osimage)
>> centos6.4-x86_64-statelite-xen  (osimage)
>>
>> -Josh
>>
>>
>>
>> On Mon, Jan 20, 2014 at 8:22 AM, Lissa Valletta 
>> <*lis...@us.ibm.com*<lis...@us.ibm.com>>
>> wrote:
>>
>>    You should also have a diskfull service node image 
>> centos6.4-x86_64-install-service.
>>     Normally the service nodes are diskfull but they can be diskless.
>>
>>
>>    Lissa K. Valletta
>>    8-3/B10
>>    Poughkeepsie, NY 12601
>>    (tie 293) 433-3102
>>
>>
>>
>>    [image: Inactive hide details for Josh Nielsen ---01/17/2014 07:01:23
>>    PM---Answering more of my questions (I think): genimage -p [profi]Josh
>>    Nielsen ---01/17/2014 07:01:23 PM---Answering more of my questions (I
>>    think): genimage -p [profile] looks like the way to go to make a s
>>
>>    From: Josh Nielsen <*jniel...@hudsonalpha.org*<jniel...@hudsonalpha.org>
>>    >
>>    To: xCAT Users Mailing list 
>> <*xcat-user@lists.sourceforge.net*<xcat-user@lists.sourceforge.net>>,
>>
>>    Date: 01/17/2014 07:01 PM
>>    Subject: Re: [xcat-user] Determine which otherpkgs.pkglist file is
>>    being used
>>    ------------------------------
>>
>>
>>
>>    Answering more of my questions (I think): genimage -p [profile] looks
>>    like the way to go to make a service specific osimage. Am I on the right
>>    track?
>>
>>
>>    On Fri, Jan 17, 2014 at 5:56 PM, Josh Nielsen <
>>    *jniel...@hudsonalpha.org* <jniel...@hudsonalpha.org>> wrote:
>>       It is definitely related. After my chdef fixes the entry for
>>       xcat-serv1 looked like this:
>>
>>       profile=service
>>       provmethod=install
>>
>>       and after a ""nodeset xcat-serv1
>>       osimage=centos6.4-x86_64-install-compute" it looked like this:
>>
>>       profile=compute
>>       provmethod=centos6.4-x86_64-install-compute
>>
>>       The osimage or something else in a table that "nodeset" parses is
>>       changing the associations of the service node. I guess I need a 
>> "service
>>       specific" osimage. Nothing I can see in my xcat tables associates the
>>       service node with the "compute" group as all so I'm guessing it is the
>>       osimage doing it. Lissa mentioned how to create a diskless osimage, 
>> but I
>>       have a diskful node. How can I create a diskful osimage for a service 
>> node
>>       that will not change the provmethod to "compute" but rather "service"?
>>
>>       Thanks,
>>       Josh
>>
>>
>>
>>       On Fri, Jan 17, 2014 at 5:49 PM, Josh Nielsen <
>>       *jniel...@hudsonalpha.org* <jniel...@hudsonalpha.org>> wrote:
>>          Nevermind, it was the funky "provmethod" value. Would
>>          provisioning it with "nodeset xcat-serv1
>>          osimage=centos6.4-x86_64-install-compute" change the "provmethod" 
>> to the
>>          same thing as the osimage? The provmethod needs to simply be 
>> "install". Not
>>          sure how it got the same name as the osimage.
>>
>>          -Josh
>>
>>
>>          On Fri, Jan 17, 2014 at 5:43 PM, Josh Nielsen <
>>          *jniel...@hudsonalpha.org* <jniel...@hudsonalpha.org>> wrote:
>>             A node I am deploying seems to be grabbing the wrong
>>             otherpkgs.pkglist file. I have placed pkglist files
>>             in /install/custom/install/centos and created one the service
>>             group/profile. In that directory are these files:
>>
>>             compute.otherpkgs.pkglist
>>             compute.pkglist
>>             compute.tmpl
>>             hinode01.tmpl
>>             service.otherpkgs.pkglist
>>             service.tmpl
>>
>>             I want to use the "service.otherpkgs.pkglist" file. I
>>             deployed a node xcat-serv1 which belongs to the service group 
>> but it did
>>             not install the RPMs I specified in the otherpkgs.pkglist file 
>> for
>>             'service'. When I did an lsdef I saw that the profile was set to 
>> "compute"
>>             and realized that would be a problem so I changed it to 
>> 'service' as well
>>             and tried an "updatenode xcat-serv1 otherpkgs" but it didn't 
>> make a
>>             difference. Here is the current node definition:
>>
>>             [root@x3650-head01 centos]# lsdef xcat-serv1
>>             Object name: xcat-serv1
>>                 arch=x86_64
>>                 currchain=boot
>>                 currstate=boot
>>                 groups=service,ipmi,all
>>
>>             initrd=xcat/osimage/centos6.4-x86_64-install-compute/initrd.img
>>                 installnic=mac
>>
>>             kernel=xcat/osimage/centos6.4-x86_64-install-compute/vmlinuz
>>                 netboot=xnba
>>                 nodetype=osi
>>                 os=centos6.4
>>
>>             
>> postscripts=syslog,remoteshell,ospkgs,addsiteyum,otherpkgs,syncfiles,ifcfg-eth,fstab,servicenode
>>                 primarynic=mac
>>                 profile=service
>>                 provmethod=centos6.4-x86_64-install-compute
>>               <snipped>
>>
>>             The "groups" and "profile" look correct now, but I still
>>             can't get the right packages to install. Is there a particular 
>> line in the
>>             "otherpkgs" postscript I could use to print a variable with the 
>> file name
>>             of the file chosen/matched against? I looked but only found a 
>> variable with
>>             the actual parsed packages from whatever file it chose. It looks 
>> like it is
>>             using the compute.otherpkgs.pkglist. I can't quite figure out 
>> why it
>>             wouldn't match though.
>>
>>             This page seems to indicate that my directory and
>>             nomenclature for the files is correct:
>>             
>> *http://sourceforge.net/apps/mediawiki/xcat/index.php?title=Using_Provmethod%3Dinstall,netboot_or_statelite*<http://sourceforge.net/apps/mediawiki/xcat/index.php?title=Using_Provmethod%3Dinstall,netboot_or_statelite>.
>>             And I know the kickstarts from that folder work since they are 
>> used during
>>             provisioning.
>>
>>             It is usually something simple. Does anyone see what I am
>>             missing?
>>
>>             Thanks,
>>             Josh
>>
>>    
>> ------------------------------------------------------------------------------
>>    CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>>    Learn Why More Businesses Are Choosing CenturyLink Cloud For
>>    Critical Workloads, Development Environments & Everything In Between.
>>    Get a Quote or Start a Free Trial Today.
>>
>>    
>> *http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk*<http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk>
>>    _______________________________________________
>>    xCAT-user mailing list
>> *xCAT-user@lists.sourceforge.net* <xCAT-user@lists.sourceforge.net>
>> *https://lists.sourceforge.net/lists/listinfo/xcat-user*<https://lists.sourceforge.net/lists/listinfo/xcat-user>
>>
>>
>>
>>    
>> ------------------------------------------------------------------------------
>>    CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>>    Learn Why More Businesses Are Choosing CenturyLink Cloud For
>>    Critical Workloads, Development Environments & Everything In Between.
>>    Get a Quote or Start a Free Trial Today.
>>
>>    
>> *http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk*<http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk>
>>    _______________________________________________
>>    xCAT-user mailing list
>> *xCAT-user@lists.sourceforge.net* <xCAT-user@lists.sourceforge.net>
>> *https://lists.sourceforge.net/lists/listinfo/xcat-user*<https://lists.sourceforge.net/lists/listinfo/xcat-user>
>>
>>
>> ------------------------------------------------------------------------------
>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>> Learn Why More Businesses Are Choosing CenturyLink Cloud For
>> Critical Workloads, Development Environments & Everything In Between.
>> Get a Quote or Start a Free Trial Today.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>> _______________________________________________
>> xCAT-user mailing list
>> xCAT-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/xcat-user
>>
>>
>>
>> ------------------------------------------------------------------------------
>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>> Learn Why More Businesses Are Choosing CenturyLink Cloud For
>> Critical Workloads, Development Environments & Everything In Between.
>> Get a Quote or Start a Free Trial Today.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>> _______________________________________________
>> xCAT-user mailing list
>> xCAT-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/xcat-user
>>
>>
>

<<graycol.gif>>

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to