Control CPUs between npars and vpars

[Joy_S]

Dear Support :

My customer has 128-way superdome running two npars and on each npar we have mutiple of vpars , SD running hpux 11.31 , with WLM ver.A.03.02.02 , is it supported to move CPUs between vpars on different npars on demand ? if yes how can I define movng CPU conditions based on system CPU threshold and not only certain application ?

[Don Morris_1]

The only way to move cpus between vpars on different nPars would be to move the Cells containing the cpus (and the entire Cell) between the nPars first. (Get the cpus out of the vPars, OLD the Cell from Source nPar, OLA to Dest nPar, then move the cpus to the appropriate vPar).

nPars by definition are isolated from each other -- if you could move individual cpus between them, you'd lose all electrical isolation and you'd be just as well off to run the whole thing as a single nPar with a bunch of vPars.

[Joy_S]

Ok that is clear now ..
Next step to configure certain vpars with min/max CPUs and create a pool of "on-demand CPUs" to be moved to vpars where CPU threshold reach 65% and freed once this % decreased , also system has some icap CPUs, how can I do such configuration ?

[Torsten.]

A lot of new features coming with 11.31.
One of them is the online addition of cell to a running nPar.

This means you can add a unassigned cell to a npar to make it available for assigning to a vpar. IMHO in addition with WLM you can do this on demand - more or less.

Refer to the documentation of the single items on docs.hp.com

[Joy_S]

Alright I am going to close this thread and open new one for configuration

[Mark Coffey_2 · Accepted solution]

Moving CPU resources across nPars is supported by WLM with the help of Instant Capactiy. As a previous posting said, the nPars are electrically isolated from each other, so the physical CPU is not moved across the nPar, rather the right-to-use the CPU is migrated (a CPU is deactivated in one nPar and activated in another). This keeps the number of CPUs at or below the number of licensed CPUs for the complex.

To familiarize yourself with the capabilities of Cell OL* operations, or dynamic nPars, check out the following whitepaper. One thing to note is that dynamic nPar operations cannot be run on an nPar running vPars.

http://docs.hp.com/en/10907/dynamic_nPars_WP.pdf


Configuring WLM to move CPUs around to the partition that needs the CPUs the most is definitely possible. Since iCAP CPUs will be involved, you will need to use just one wlmpard configuration across the entire complex being managed. The easiest way to get started on a configuration that does this is to use WLM's host-based configuration where the entire OS instance is considered a workload (there are no sub-OS workloads defined in this case).

[Victor Burguillos_4]

Configuring WLM to move CPUs around to the partition that needs the CPUs the most is definitely possible. Since iCAP CPUs will be involved, you will need to use just one wlmpard configuration across the entire complex being managed. The easiest way to get started on a configuration that does this is to use WLM's host-based configuration where the entire OS instance is considered a workload (there are no sub-OS workloads defined in this case).

[Joy_S]

Thank you Mark for detailed feedback

[Joy_S]

The solution worked for me , thank for support