Superdome 2 and vpars......

[Converger]

Fellas,
On the manual of VPAR I read that is possible on the fly increase/decrease CPU and memory but on the administrator guide of SD2 I read "Any modification to a vPar can be done only when the vPar is in the Down state". It seems that the right truth is about of SD2, in fact:

Feb 24 10:03:29 vparmodify: vparmodify -N 1 -p 1 -m cpu:::4
Feb 24 10:03:29 parcon: Note: Attempting to Modify Virtual Partition
Feb 24 10:03:30 parcon: Error: nPartition 1: vPar 1: Failed to Modify Virtual Partition in nPartition. Error: Specified partition is active.

My question: for change any resource "on the fly" I need to install any other software or I at actual state is not possible ?

Regards,
Massimo

[Kenan Erdey]

Hi,

we haven't set our sd2 yet it's waiting already :) But i read this thread. as i understand vpar is now in firmware not as software. So it has limited features if you want to use it from fw not from vpar software.

http://h30499.www3.hp.com/t5/Virtualization/vPars-software-on-SD2-servers/m-p/4733125#M2620

[Torsten.]

You can do noting on the fly with the first release of firmware - we all waiting for an update ...

[Converger]

Kenan,
on the SD2 the vpar commands are only available from OA and the vpar are completely indipendent from Npar.

In the cloud scenario one of the feature that we'll aspect from SD2 is to move dinamically resource (e.g. ram or cpu) from vpar to vpar: this is not possible as shown of vparmodify output above.

We are think if we are setup correctly the SD2 or not....

Regards,
Massimo

[Converger]

Torsten,
are u sure that only a problem of firmware ?

I know that there is a new one but in the RN I don't see that fix this issue.

Ciao,
Massimo

[Torsten.]

vPars commands a available from OA *or* the vPar itself. The OS commands are passed to the OA, so this is more or less the same.

With this first release of firmware (even if bugfix releases are available now) you don't have any dynamic functionality as known from the older superdomes (e.g. dynamic cells, dynamic CPU, dynamic memory, OLAR, etc ...).


Just for fun, try olrad:

# olrad -q
Error : Capability not implemented; Could not obtain information of all slots

[Converger]

Torsten,
you're right.

the mother of all questions is:
what is the firmware that permit the moving of the resources "on the fly"?

I mean: now the latest is 1.2.67 and the new one (1.3.30 or .31) don't fix this.

Ciao,
Massimo

[Torsten.]

I hope this famous second release will be out soon ...

[Kenan Erdey]

good to hear that, hp catches up with ibm in virtualisation.(virtualisation on fw)