Remote data is data that resides elsewhere than on the execution host.
In order to use remote data:
The execution host must be properly configured to find the data.
If the data is elsewhere than on the execution host, the user must specify the host where the data is located.
 |
| |
|
 | NOTE: "Remote data" is in reference to the execution host. When an action executes a remote application using local data, that data is considered remote data, in that it must be NFS-accessible to the execution host.
|
|
| |
|
To specify remote data |
|
When you drop a file on an action icon, the data host is known automatically.
When prompted for the filename, use the syntax:
If data_host is remote, then data_host: is replaced with /mount-point/data_host/. For example,
hpcvxba:/tmp/data1 managed by automount becomes
/net/hpcvxba/tmp/data1.
The action definition can specify the current working directory using the CWD field. If you then respond to a prompt with the filename or a relative path, the action will use the current working directory.
Example. Suppose the following action is defined and invoked from local host here. The action will execute the xsetrootgif command locally. If the user supplies a relative path in reponse to the prompt, the command will look for the data in /usr/local/gif on host paecom.
ACTION Use_gif_Backdrop
CWD paecom:/usr/local/gif
EXEC-STRING /usr/local/bin/xsetrootgif -gif %(File)Arg_1"gif file:"%
END
|
Example. Like the previous example, this action is invoked from host here and gets its data from paecom if the user specifies a relative path. However, the application is located on host ellcom.
ACTION Edit_QS_document
CWD paecom:/QSproject/documents/
EXEC-HOST ellcom
EXEC-STRING /usr/local/bin/IslandWrite %(File)Arg_1"Document:"%
END
|
Configuring systems for remote data access |
|
This section describes how a system must be configured
so VUE processes (e.g. the File Manager) run on the system
can access data files on other hosts.
The VUE remote data model assumes all data files can be
accessed via a pathname such as:
/mount_point/data_host/path/filename
|
Before a system can access remote data, the remote
data host must export the desired file system to the system
and the system must use automount or mount to
mount the remote file system.
For example, if the following action:
/usr/vue/bin/vueaction edit /home/bob/foo
|
is invoked on the host hostaa, and the execution host of the edit action is the system hostbb, then HP VUE expands the pathname of file foo to:
/mount_point/hostaa/home/bob/foo
|
If the execution string of action edit is my_editor, then the command line executed on host hostbb is:
my_editor /mount_point/hostaa/home/bob/foo
|
Therefore, host hostbb must have the appropriate mount to the /home/bob directory of hostaa for the edit action to get the correct file. Note that if file foo is actually on a file system of another host (and not on host hostaa), for example host diskfarm, then the above expanded path is still
generated—VUE assumes the file is on host hostaa.
If the desired file is actually on a filesystem mounted on a third
machine (diskfarm), it must be referenced by an absolute symlink on hostaa. That is, in the example above, /home must be made in the following way on hostaa and hostbb:
ln -s /mount_point/diskfarm/homedir /home
|
This is because the symlink causes the actual path referenced to be
/mount_point/diskfarm/homedir on hostbb.
Specifying remote data on a diskless client |
|
This section describes how a host must be configured so it
can access data files on a diskless client.
As described in “Configuring systems for remote data access”,
VUE's remote data model assumes all data files can be accessed via a pathname like:
/mount_point/data_host/path/filename
|
automount.
Since diskless clients do not have any disks to export, this
model is not supported if the host trying to access the data is
using automount. When automount is used, data files on the
diskless client can be accessed using the diskless client's
server as the data host.
For example, to access file
/home/bob/foo on diskless client dclient, whose server is
host dserver, an action like the following could be used:
/usr/vue/bin/vueaction action dserver:/home/bob/foo
|
This example assumes that a network home has been established as
described in “Example: Configuring networked sessions”.
Manual mounts. If a host trying to access a data file on a diskless client is using mount (and not automount), the host can be configured to access the file by doing the following:
Mount the desired file system from the diskless client's server
Create a symbolic link from the diskless client's server to the diskless client
For example, to access data file /home/bob/foo on diskless client dclient, being served by host dserver, the following could be done:
% mkdir -p /nfs/dserver/home
% mount dserver:/home /nfs/dserver/home
% mkdir -p /nfs/dclient
% ln -s /nfs/dserver/home /nfs/dclient/home
|
Once this is done, then the following action can be invoked:
/usr/vue/bin/vueaction action dclient:/home/bob/foo
|
Configuring a diskless client as a remote execution host |
|
10.0 systems. Diskless clients can only be used as remote execution hosts if they are configured to use the sharedtmpdir authentication mechanism described in “User Authentication During Remote Execution”. Once this is done, HP-UX 10.0 VUE clients (for example, the VUE File Manager) are able to execute actions on a diskless client.
9.* systems. VUE clients on HP-UX 9.0 will need to configure the client host so that it appears to have a pathname to the diskless client's authentication directory.
Remember that /nfs must be used as the mount point for HP-UX 9.0 systems, and that automount is not used to manage /nfs.
For example, if the diskless client is dclient, its server is dserver, the mount point on these hosts is /nfs and the sharedtmpdir file on dclient contains:
then the following must be done on the 9.0 client host before an action can be executed on the diskless client dclient:
% mkdir -p /nfs/dserver/var/tmp
% mount dserver:/var/tmp /nfs/dserver/var/tmp
% mkdir -p /nfs/dclient/nfs
% ln -s /nfs/dserver /nfs/dclient/nfs/dserver
|
Printable version
