Changes between Version 6 and Version 7 of bridge-ndl-to-controls

Show
Ignore:
Timestamp:
04/22/11 13:30:48 (8 years ago)
Author:
ibaldin (IP: 108.65.61.102)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • bridge-ndl-to-controls

    v6 v7  
    33== Overview ==  
    44 
    5 Many existing ORCA controls use table-driven resource descriptions (resource, type, quantity) tuples. Examples of such controls are  [source:orca/trunk/core/policy/src/main/java/orca/policy/core/SimpleVMControl.java orca.policy.core.SimpleVMControl] used for XX.vm resources and  [source:orca/trunk/core/policy/src/main/java/orca/policy/core/VlanControl.java orca.policy.core.VlanControl] used for XX.vlan resources. Controls are specified as part of resource pool specification in the actors configuration file. Originally ORCA required duplicate specification of resources in both NDL and attributes and properties in the actors configuration file.  
     5Many existing ORCA controls used by authority actors rely on table-driven resource descriptions: (resource type, quantity) tuples. They also use attributes and properties. Examples of such controls are  [source:orca/trunk/core/policy/src/main/java/orca/policy/core/SimpleVMControl.java orca.policy.core.SimpleVMControl] used for XX.vm resources and  [source:orca/trunk/core/policy/src/main/java/orca/policy/core/VlanControl.java orca.policy.core.VlanControl] used for XX.vlan resources. Controls are specified as part of resource pool specification in the actors configuration file. Originally ORCA required duplicate specification of resources in both NDL and attributes and properties in the actors configuration file.  
    66 
    77For example the SimpleVMControl required attributes to be specified (in the config file for the site authority):