Page Comparison

...

1. Follow Cray's instructions for updating a repository (Refer to the section on "Install Third-Party Software with a Custom Image" in the Software Installation and Configuration Guide in Cray document S-2559).  Use the same repo that was used for the existing installed image.  
   For example, if the repo was called my_repo the command might look something like:
   smw# repo update -a "./pbspro-server-18.2.0.20171109010636-0.x86_64.rpm" my_repo
2. Follow Cray's instructions for updating a package collection in Cray document S-2559.
   1. For example if the original package collection was called my_collection the command might look something like:
      smw# pkgcoll update -p pbspro-server-18.2.0.20171109010636-0.x86_64 my_collection
       
   2. Use the pkgcoll show to see what's in the package collection my_collection.  For example:
      

      smw# pkgcoll show my_collection
      my_collection:
      name: my_collection
      packages:
      pbspro-server-18.2.0.20171018010818-0.x86_64
      pbspro-server-18.2.0.20171109010636-0.x86_64

   3. Use the package collection update remove option to remove the older PBS Pro version.  For example:
      smw# pkgcoll update -P pbspro-server-18.2.0.20171018010818-0.x86_64 my_collection
      
      
   4. Using the package collection show command should now only show one PBS Pro RPM version.
      
      
3. Even though changes have been made to the repo and the package collection the original recipe should still validate at this point.
4. Follow Cray's instructions (in Cray document S-2559) to build and push/package the image using image using the original recipe.  Use a new image name in order to keep the original image untouched.  For example, if the original recipe name was my_recipe and the original image created was my_recipe_image, then the new image might be my_new_image and the command might look something like:
   smw# image create -r my_recipe my_new_image
   smw# image export my_new_image 
       a.  Do this for each type of image that is needed (e.g. server, login, etc.)
5.  Follow Cray's instructions (in Cray document S-2559) to assign the new boot image to the nodes where PBS Professional should be installed.  This includes all nodes running PBS Professional services (e.g. pbs_server, pbs_mom, etc.) and those requiring access to PBS Pro commands (e.g. qsub, qstat, etc.).  Include the original configuration set that contains the persistent information.  For example the command might look something like:
   smw# cnode update -i  /var/opt/cray/imps/boot_images/<image name>.cpio -c <configuration set name> <cname-of-node-to-update or group-to-update>
6. Reboot the system.
7. Log on to the nodes that are hosting PBS Professional daemons and start PBS.
   # /etc/init.d/pbs start
8. At this point PBS Professional will be up and running, and connected to ALPS.  Prior queued jobs will still be queued.  
   Remember to turn on scheduling so PBS Pro can resume normal operation.

...