Changes between Version 32 and Version 33 of Internal/Infrastructure/OMF/GridServicesApi

Timestamp:

May 10, 2006, 3:15:38 PM (19 years ago)

Author:

faiyaz

Comment:

—

Internal/Infrastructure/OMF/GridServicesApi

@@ -1 @@
-== CMC Access Control ==
+== ORBIT WebServices API ==
 
 ORBIT support services have web based XML interfaces.  They all use the same framework and, therefore, have like syntax.  The services are accessed using either of the following schemes:
@@ -11 +11 @@
 }}}
 
-OR
- 
-{{{
-http://<serviceGroup name>:5012/<serviceGroup name>/<service name>?<domain>=<domain name>&<1st_arg>=<arg_1_value>&<2nd_arg>=<arg_2_value>
-
-Currently the valid domain name scheme is <subdomain-name>.orbit-lab.org, where 
-subdomain-name = {grid,sb1,sb2,sb3,sb4,sb5,sb6,sb7,sb8,sb9}. For instance, to turn on node1-1 
-using the CMC (from the console of one of the sandboxes or the grid), you would issue the following:
-
-wget -O - "http://cmc:5012/cmc/nodeSetOn?domain=sb8.orbit-lab.org&nodes=[1,1..5]"
-
-For instance, to turn on node1-1 on a sandbox using the CMC (from any of the internal machines),
-you would issue the following:
-
-wget -O - "http://sb8.orbit-lab.org:5012/cmc/nodeSetOn?domain=sb8.orbit-lab.org&nodes=[1,1..5]"
-
-}}}
 The services are location aware and will manipulate the resources for that specific location.  For instance, querying the CMC to turn on node1-1 from the console on sb1 will turn on node1-1 
 on sb1 and not any other resource.  Also, it is impossible for users in one location to issue commands for another.  For example, it is impossible to turn on nodes on the grid from the console of sb1.  One of the obvious advantages of this is experiment scripts/applications need only mention the service name to be portable.
@@ -33 +16 @@
 Below is a list of available services and their corresponding arguments.
 
-== CMC Access Control Policy ==
-{{{
-1.) Access is granted to ON (on, allOn, nodeSetOn), OFF (off, offHard, allOffHard, 
-    nodeSetOffHard, offSoft, nodeSetOffSoft, allOffSoft) and RESET (reset, nodeSetReset, 
-    allReset) services if you are in the same subdomain as the resource you are trying to 
-    control. For this case, the domain name need not be specified.
-
-2.) Access is granted to all services if you are on the same subnet as the primary CMC 
-    interface. The domain name needs to be specified in this case
-
-3.) Access is granted to STATUS (nodeStatus, allStatus) services from everywhere. The 
-    domain name needs to be specified in this case.
-}}}
-
+== Chassis Manager Controller (CMC) ==
+
+Services and arguments
 
 {{{
@@ -184 +156 @@
         </serviceGroup>
 }}}
+
+Command redirection to other resources.
+{{{
+http://<serviceGroup name>:5012/<serviceGroup name>/<service name>?<domain>=<domain name>&<1st_arg>=<arg_1_value>&<2nd_arg>=<arg_2_value>
+
+Currently the valid domain name scheme is <subdomain-name>.orbit-lab.org, where 
+subdomain-name = {grid,sb1,sb2,sb3,sb4,sb5,sb6,sb7,sb8,sb9}. For instance, to turn on node1-1.sb9.orbit-lab.org through node1-5.sb9.orbit-lab.org
+from an internal machine (i.e. internal1, internal2, internal3, internal4), you would issue the following:
+
+wget -O - "http://cmc:5012/cmc/nodeSetOn?domain=sb8.orbit-lab.org&nodes=[1,1..5]"
+
+It should be noted that most users will not need to specify the domain.  This is only for internal development use and will not work from any of the consoles.
+}}}
+
+Access Control Policy.
+{{{
+1.) Access is granted to ON (on, allOn, nodeSetOn), OFF (off, offHard, allOffHard, 
+    nodeSetOffHard, offSoft, nodeSetOffSoft, allOffSoft) and RESET (reset, nodeSetReset, 
+    allReset) services if you are in the same subdomain as the resource you are trying to 
+    control.
+
+2.) Access is granted to all services if you are on the internal subnet (10.0.0.0). The domain name needs to be specified in this case
+
+3.) Access is granted to STATUS (nodeStatus, allStatus) services from everywhere. The 
+    domain name needs to be specified in this case.
+}}}
+
 
 == Frisbee ==