Resolution:
Read-only, Shared mount point Engine Installation for GridServer 4.2


You can run Engines from multiple hosts from a single shared read-only installation mount point. This requires initial access to the shared mount point with write rights so you can download DSEngineLinux.tar.gz and run configure.sh there.

Do the following:

1) On your intended read-only shared filesystem

    * Download DSEngineLinux.tar.gz installation file and unpack it:

gzip -d -c DSEngineLinux.tar.gz | tar xvf -

    * Next, cd to DSEngine and run configure.sh script. You must set the alternate profiles directory to a writable location for Engine hosts (can be local to Engine hosts):

./configure.sh -s &ltDirector_url>:&ltDirector_port> -P &ltprofiles_dir> -l [y|n]

For example:

./configure.sh -s 192.168.20.147:8000 -P /test/profiles -l n

In this example, /test/profiles is created if it doesn't exist. You can also create /test/profiles locally on the Engine host machine once you run engine.sh there, as specified in step 4 below.

2) On your Director

    * Create Engine profiles for your read-only Engines
          o In Engine&gtEngine Configuration, create a new Configuration, for example, linux:read_only.
          o In Classes, Libraries and Paths section set:
                + Grid Library Path, Default JAR and Class Path and Default Library Path to shared read-only directories.
                + Work Directory and Data Directory to writable locations.
          o Click Save to save your changes.

3) On each Broker that will use read-only engines

    * Disable resource synchronization
          o In Configuration&gtResource Deployment, set: Engine Synchronization Enabled=Disabled.
          o You must use a shared mount point for libraries and resources (set in Engine Configuration(s) created on Director) and you must update them manually.

4) On each Engine host

    * Create or verify writable location(s) for work and data directories specified in intended Engine Configuration created in step 2. Creating actual work and data directories is unecessary.
    * Create or verify writable location for profiles directory as specified while running configure.sh in step 1. Profiles directory can be shared. All configuration information and daemon logging is then stored in the subdirectories, each subdirectory bearing the name of Engine daemon hostname.
    * Mount the read-only filesystem and go to DSEngine directory from step 1.
    * Run
      ./engine.sh start &ltengine_config_from_step2>
      This starts a daemon and instance(s) of Engines with engine_config_from_step2 configuration. It also creates a subdirectory in profiles directory that holds config information and daemon logs.