Bug 5214 - enhancement to node picking in resource pool
: enhancement to node picking in resource pool
Status: RESOLVED FIXED
: Nimbus
Workspace service
: TP1.2.2
: PC Linux
: P3 enhancement
: TP1.2.3
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2007-04-16 12:02 by
Modified: 2007-04-16 12:16 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2007-04-16 12:02:45
This enhancement would extend the resource pool implementation to allow
different nodes in the pool to support different associations (network pools). 
For example, consider a common situation where there are two networking pools:
"public" and "private".  Not every resource pool node's NIC may be switched
onto the public network.  With this enhancement, a request for a workspace that
needed both public and private could only be launched on the nodes with support
for both.  The enhancement would be generic though, allowing for any
complicated permutation.
------- Comment #1 From 2007-04-16 12:08:21 -------
Instead of simple hostname + memory:

vmm1 2048
vmm2 2048

One can now specify explicitly what associations each node supports:

vmm1 2048
vmm2 2048 *
vmm3 1024 public
vmm4 2048 private1,private2
vmm5 2048 *

If the third column is blank or contains "*" then that means it supports all
associations. I made "*" an option in order to remind the user that something
is happening in the third column if they like that, but left blankspace as an
option for convenience and to not break compatibility with pool configs from
previous workspace versions.
------- Comment #2 From 2007-04-16 12:16:45 -------
(feature added as of TP1.2.3)