Bright:upgrade image

Clone and Edit and Existing Image

If you are using the same OS as a previously created image, cloning it is the easiest method to create a new image. Clicking on clone will ask you for a name for the new image. Click save and the new image wll be created in /cm/images. It will also appear in the list in the GUI.

Using cmsh:

softwareimage clone <oldimage> <newimage>
#It will take some time for the image to be cloned, wait until this has completed before making further changes

From here the image will need to be edited to make the required changes. There are two way to do this. Clicking the image in the GUI you can access the root shell under the tasks tab.

From the command line you can run the command:

chroot /cm/images/<image name>

If you want a node category to boot off this now image/clone, then move the category software image across: (in this example, we cloned a dtn-image, data transfer node)

[root@hyalite ~]# cmsh
[hyalite]% softwareimage
[hyalite->softwareimage]% clone dtn-image dtn-image-copy-01-09-16.1
[hyalite->softwareimage*[dtn-image-copy-01-09-16.1*]]% commit
[hyalite->softwareimage[dtn-image-copy-01-09-16.1]]% 
Mon Sep  5 06:46:26 2016 [notice] hyalite: Started to copy: /cm/images/dtn-image -> /cm/images/dtn-image-copy-01-09-16.1
# wait a few mins until finished (not necessary but didnt take too long) 
[hyalite->softwareimage]% category 
[hyalite->category]% list
Type   Name (key)               Software image          
------ ------------------------ ------------------------
Node   default                  default-image-copy-01-0+
Node   dtn                      dtn-image               
Node   mds                      default-image           
Node   oss                      default-image           
Node   perfsonar                default-image           
Node   vmware                   samba-image 
[hyalite->category]% use dtn 
[hyalite->category[dtn]]% set softwareimage dtn-image-copy-01-09-16.1
[hyalite->category*[dtn*]]% commit
[hyalite->category[dtn]]% 
# then reboot dtn nodes to provison new image - after making whatever changes required in /cm chroot

Run a new Kernel

Since the image cannot be rebooted the kernel will not change. To force the new kernel to un after isntalltion use cmsh:

[root@head1 ~]# cmsh
[head1]% softwareimage set <image_name> kernelversion <kernel>

Create a new category

It may be that you need to clone a category and change the image used to keep other settings the same:

category clone <oldcategory > <newcategory >
#wait until the image has been cloned
category set <category > softwareimage <image>