UVMS Role to restrict cross node launch

[Angus Reid]

​$U 6.9 Windows 2012 R2

Trying to create a role to restrict launching of uprocs from node A onto node B by command line.  This can be done via a mask in the MU  as long as the MUs are unique within a company,

i.e. MU on node A = node_A and MU on node B = node_B.
A MU mask in UVMS of MU=node_A* (use within launch) in the MU field of permissions on Objects in the DUAS roles on UVMS will only allow a command line launch on a MU on node A

The launch command does contain a node parameter and there may be a MU of the same name on both node A and node B though MU
 is defined to be local for each node.  MU on node A = node_C and MU on node B = node_C.

Is there a role that can be setup in UVMS (and applied to system user) that will prevent command line launches onto node A from node B? Using MUs would not work in this case as the MU is defined with the same name on both nodes.

[Eric Delawoevre]

Hi,

Yes
Indeed original fact that it's quite not properly used to have MU with the same name on different node (on same environnement)

For the Role, unfortunetly, I didn't see this affinity attribute.
It can be complex but you can:
* 2 user that belong to different group
* those 2 group have its own role
* each role --> each one node view
* each node view have the node A, and node B for the other

But you'll be stuck with the MU indeed





------------------------------
Main director
SynApps
------------------------------