Michael: Created page with "== Installing VSMP for Cloud == The software need to need to be installed on the head node and consists on two parts: the image manager and the vSMP image. These must be cop..."

2014-01-17T10:09:06Z

Created page with "== Installing VSMP for Cloud == The software need to need to be installed on the head node and consists on two parts: the image manager and the vSMP image. These must be cop..."

New page

== Installing VSMP for Cloud ==

The software need to need to be installed on the head node and consists on two parts: the image manager and the vSMP image.

These must be copied to /cm/local/apps/vsmp. Then /cm/local/apps/vsmp/vSMP.img muyst link to the image being used.

<syntaxhighlight>
cp image_manager /cm/local/apps/vsmp/
cp vSMP-3.5.155.img /cm/local/apps/vsmp
ln -sf vSMP-3.5.155.img /cm/local/apps/vsmp/vSMP.img
</syntaxhighlight>

== Creating Virtual SMP Nodes ==

Virutal Nodes can be created using the GUI of cmsh.

=== GUI ===

Click on the virtual folder and the click add. This will create a node that acts and looks like any physical node. It will have an extra tab to configure when physical nodes should be used as part of the vSMP node.

Nodes that are part of the vSMP node will be put into the aggregated state and will boo the vSMP kernel. Once all members have booted they will be formed into a single node.

=== CMSH ===

<syntaxhighlight>
[mc]% device add virtualsmpnode vsmp001
[mc->device*[vsmp001*]]% set members node001 node002 node003
[mc->device*[vsmp001*]]% interfaces
[mc->device*[vsmp001*]->interfaces]% add physical BOOTIF
[mc->device*[vsmp001*]->interfaces*[BOOTIF*]]% set ip 10.141.10.1
[mc->device*[vsmp001*]->interfaces*[BOOTIF*]]% set network internalnet
[mc->device*[vsmp001*]->interfaces*[BOOTIF*]]% exit
[mc->device*[vsmp001*]->interfaces*]% exit
[mc->device*[vsmp001*]]% set provisioninginterface BOOTIF
[mc->device*[vsmp001*]]% commit
...
[mc->device[vsmp001]]% power reset -n vsmp001
</syntaxhighlight>

After the virtual SMP node boots, it must be identified in the same way that
a new physical node has to be identified at first boot.

== vSMP Settings ==

The settings can be accessed in teh same way as other nodes through the GUI of through CMSH:

<syntaxhighlight>
mycluster:~ # cmsh
[mc]% device use vnode001
[mc->device[vnode001]]% vsmpsettings
[mc->device[vnode001]->vsmpsettings]% show
Parameter Value
------------------------------ -----------------------------------------
Boot device
Console redirection all
Extended acpi no
Fault tolerance RESTART
Hyperthreading no
List of boards -
Minimal boards 2
Restart on failure no
Revision
System memory 100
Type VScaleMPSettings
Update backplane no
[mc->device[vnode001]->vsmpsettings]% set systemmemory 90
[mc->device[vnode001]->vsmpsettings*]% commit
</syntaxhighlight>

Bright:ScaleMP - Revision history

Michael: Created page with "== Installing VSMP for Cloud == The software need to need to be installed on the head node and consists on two parts: the image manager and the vSMP image. These must be cop..."