Changes between Version 12 and Version 13 of Internal/Infrastructure/OMF/GridServicesApi

Timestamp:

Mar 24, 2006, 4:51:51 PM (18 years ago)

Author:

sswami

Comment:

—

Internal/Infrastructure/OMF/GridServicesApi

@@ -5 +5 @@
 http://<serviceGroup name>:5012/<serviceGroup name>/<service name>?<1st arg>=<arg_1_value>&<2nd_arg>=<arg_2_value>
 
-
-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:
+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?nodes=[1,1]"
 }}}
-
+OR 
+{{{
+http://<serviceGroup name>:5012/<serviceGroup name>/<service name>?<domain>=<domain name>&<1st_arg>=<arg_1_value>&<2nd_arg>=<arg_2_value>
+
+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]
+}}}
 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.