>> help findResource
findResource Find available distributed computing resources
OUT = findResource('scheduler','type', SCHEDTYPE)
OUT = findResource('worker')
return an array, OUT, containing objects representing all available
distributed computing schedulers of the given type, or workers. SCHEDTYPE
can be 'jobmanager', 'LSF', 'mpiexec', or any string starting with
'generic'. You can use different scheduler types starting with 'generic' to
identify one generic scheduler or configuration from another. For
third-party schedulers, job data is stored in the location specified by the
scheduler object's DataLocation property.
OUT = findResource('scheduler','type','jobmanager','LookupURL','HOST:PORT')
OUT = findResource('worker','LookupURL','HOST:PORT')
use the lookup process of the job manager running at a specific
location. The lookup process is part of a job manager. By default,
findResource uses all the lookup processes that are available to the local
machine via multicast. If you specify 'LookupURL' with a host and port,
findResource uses the job manager lookup process running at that
location. This URL is where the lookup is performed from, it is not
necessarily the host running the job manager or worker. This unicast call is
useful when you want to find resources that might not be available via
multicast or in a network that does not support multicast.
Note: LookupURL is ignored when finding third-party schedulers.
OUT = findResource(... ,'P1', V1, 'P2', V2,...)
returns an array, OUT, of resources whose property names and property values
match those passed as parameter-value pairs, P1, V1, P2, V2.
Note that the property value pairs can be in any format supported by the SET
function.
When a property value is specified, it must use the same exact value that
the GET function returns, including letter case. For example, if GET returns
the Name property value as 'MyJobManager', then findResource will not find
that object if searching for a Name property value of 'myjobmanager'.
Remarks
Note that it is permissible to use parameter-value string pairs, structures,
and parameter-value cell array pairs in the same call to findResource. The
parameter-value pairs can also be specified as a configuration, described in
the "Programming with User Configurations" section in the documentation.
Examples:
Find a particular job manager by its name.
jm1 = findResource('scheduler','type','jobmanager', ...
'Name', 'ClusterQueue1');
Find all job managers. In this example, there are four.
all_job_managers = findResource('scheduler','type','jobmanager')
all_job_managers =
distcomp.jobmanager: 1-by-4
Find all job managers accessible from the lookup service on a particular
host.
jms = findResource('scheduler','type','jobmanager', ...
'LookupURL','MyJobManagerHost');
Find a particular job manager accessible from the lookup service on a
particular host. In this example, subnet2.host_alpha port 6789 is where the
lookup is performed, but the job manager named SN2Jmgr might be running on
another machine.
jm = findResource('scheduler','type','jobmanager', ...
'LookupURL', 'subnet2.host_alpha:6789', ...
'Name', 'SN2JMgr');
Find the LSF scheduler on the network.
lsf_sched = findResource('scheduler','type','LSF')
See also findJob, findTask.
# posted by samuel @ 12:04 AM