diff options
Diffstat (limited to 'TAO/CIAO/docs/schema/ServerResourceUsage.txt')
| -rw-r--r-- | TAO/CIAO/docs/schema/ServerResourceUsage.txt | 111 |
1 files changed, 0 insertions, 111 deletions
diff --git a/TAO/CIAO/docs/schema/ServerResourceUsage.txt b/TAO/CIAO/docs/schema/ServerResourceUsage.txt deleted file mode 100644 index 1300110babb..00000000000 --- a/TAO/CIAO/docs/schema/ServerResourceUsage.txt +++ /dev/null @@ -1,111 +0,0 @@ - How to use CIAOServerResources.xsd - -Assuming we store two CIAO:ServerResources documents in two XML files -called "RTLinuxServerConfig.xml" and "RTwIN32ServerConfig.xml" -respectively. We will specify their IDs in a DeploymentPlan via -infoProperfy with the equivalent of the following struct: - - struct CIAOServerResourcesRef - { - string resourceId; - string filename; - }; - -So, the DeploymentPlan should look something like: - - <infoProperty> - <name>CIAOServerResourceRef</name> - <value> - <type> - <kind>tk_struct</kind> <!-- I don't know how to specify the - type of CIAO:ServerResourceRef - struct here --> - </type> - <value> - <name>resourceId</name> - <value> - <type>tk_tring</type> - <value>RTConfig4LinuxBox</value> <!-- Component instances - will refer to this - name to specify - required server - config --> - </value> - <name>filename</name> - <value> - <type>tk_tring</type> - <value>RTLinuxServerConfig.xml</value> - </value> - </value> - </value> - - <name>CIAOServerResourceRef</name> - <value> - <type> - <kind>tk_struct</kind> <!-- I don't know how to specify the - type of CIAO:ServerResourceRef - struct here --> - </type> - <value> - <name>resourceId</name> - <value> - <type>tk_tring</type> - <value>RTConfig4Win32Box</value> <!-- Component instances - will refer to this - name to specify - required server - config --> - </value> - <name>filename</name> - <value> - <type>tk_tring</type> - <value>RTWin32ServerConfig.xml</value> - </value> - </value> - </value> - </infoProperty> - -We can now use the policy sets defined in the XML documents to -instantiate components. A component instance in deployment plan can -specify the policies it wishes to be instantiated with. To use this -feature, one need to specify both the resouceID and the ID for the -policySet as following: - - <deploymentplan> - .... - <instance ...> - - - <deployedResource> - <resourceUsage>InstanceUsesResource</resourceUsage> - <requirementName>CIAO:PolicySet</requirementName> - <resourceName>here_we_insert_the_CIAO:PolicySet_ID</resourcename> - <resourceValue> - <type>tk_null</type> - <value></value> - </resourceValue> - </deployedResource> - - <deployedResource> - <resourceUsage>InstanceUsesResource</resourceUsage> - <requirementName>CIAO:ServerResources</requirementName> - <resourceName>here_we_insert_the_CIAO:ServerResources_ID - defined in infoProperty</resourcename> - <resourceValue> - <type>tk_null</type> - <value></value> - </resourceValue> - </deployedResource> - - </instance> - </deploymentplan> - -If only ID of CIAO:ServerResources is specified, we are using it as a -collocation constraint. I.e., if two instances are deployed to the -same target node with different ServerResources IDs, DAnCE should -create two differnet NodeApplication on the same node. - -Likewise, specifying different CIAO:PolicySet IDs will force component -instances to be deployed into different containers (if they have the -same target node and ServerResource ID.) - |