Bright:upgrade image - Revision history

David: /* Run a new Kernel */

2016-09-05T13:59:02Z

Run a new Kernel

David at 13:23, 5 September 2016

2016-09-05T13:23:14Z

David at 13:22, 5 September 2016

2016-09-05T13:22:44Z

Michael: /* Create a new category */

2014-04-11T14:58:53Z

Create a new category

Michael: /* Create a new Categorie */

2014-04-11T14:58:32Z

Create a new Categorie

Michael: Created page with "== 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..."

2014-04-11T14:58:22Z

Created page with "== 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..."

New page

== 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:

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

From here the image will need to be edited tom ake 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:

<syntaxhighlight>
chroot /cm/images/<image name>
</syntaxhighlight>

== 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:

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

== Create a new Categorie ==

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

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

@@ Line 41: / Line 41: @@
 [hyalite->category*[dtn*]]% commit
 [hyalite->category[dtn]]%
 # then reboot dtn nodes to provison new image - after making whatever changes required in /cm chroot
 </syntaxhighlight>

@@ Line 30: / Line 30: @@
 == Create a new category ==
-It may be that you need to clone the catergoies and change the image used to keep other settings the same:
+It may be that you need to clone a category and change the image used to keep other settings the same:
 <syntaxhighlight>

@@ Line 56: / Line 56: @@
 [root@head1 ~]# cmsh
 [head1]% softwareimage set <image_name> kernelversion <kernel>
 </syntaxhighlight>

@@ Line 10: / Line 10: @@
 </syntaxhighlight>
-From here the image will need to be edited tom ake 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 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:
@@ Line 18: / Line 18: @@
 </syntaxhighlight>
 ==  Run a new Kernel ==