The recommended steps to upgrade your Compute Server (and Cluster Manager, if applicable) are as follows:
- Download and install the new version of Gurobi Remote Services on each server (and the Cluster Manager, if applicable). When upgrading to a major version, set up the new license file on each Compute Server.
- Configure the new installation:
- Locate the existing configuration file(s) for your Compute Server(s) (and Cluster Manager, if applicable). The Compute Server configuration file can be found in the old version's Remote Services installation directory at
./bin/grb_rs.cnf
. The Cluster Manager configuration file can be found at./bin/grb_rsm.cnf
. - Verify that the settings listed in the configuration file(s) are correct.
- Copy the configuration file(s) to the appropriate location(s) in the new installation directory of Gurobi Remote Services.
- Locate the existing configuration file(s) for your Compute Server(s) (and Cluster Manager, if applicable). The Compute Server configuration file can be found in the old version's Remote Services installation directory at
- Stop and uninstall Gurobi Remote Services
grb_rs
on each server. If you are running Remote Services as a service, you can stop it withgrb_rs stop
and uninstall withgrb_rs uninstall
. - Stop and uninstall the Cluster Manager
grb_rsm
, if applicable. - Update the appropriate environment variables on each server so they point to the new installation directory. On Linux, this entails extending the environment variable
PATH
to include the new installation directory and removing the reference to the old one(s). We suggest doing so in a persistent way by modifying the appropriate script file (e.g..bashrc
,.bash_profile
,.profile
, etc.). On Windows and macOS, this is usually set up correctly by the installation procedure. - Remove all deprecated installation directories from each server.
- Start the Gurobi Cluster Manager
grb_rsm
, if applicable. - Start Gurobi Remote Services
grb_rs
on each server. To start Remote Services as a service, usegrb_rs start
instead.
Note 1: In case you are not using the Cluster Manager but a pure Compute Server environment, you can skip the steps related to the Cluster Manager.
Note 2: If you are running the new Compute Server(s) on the same machine(s) with the same settings as before, it should not be necessary to update the client license files.
Note 3: If some of your clients are still running a version that will no longer be supported by the version of Compute Server you are about to install, you need to upgrade those clients to a supported version.
Note 4: You may need to update firewall rules for the new executables.
Upgrading client machines
After upgrading the Compute Server, all clients can also upgrade their Gurobi Optimizer version.
We highly recommend upgrading all clients to the latest version of our products once the Compute Server is upgraded. However, the Compute Server contains runtimes for all supported previous versions. So an upgrade from the client side is optional (as long as the client version is still supported) because backward compatibility is ensured for all minor and technical releases up to the previous major Gurobi release. The exact list of supported versions by your current Compute Server installation corresponds to the runtimes of your Compute Server, which can be found in the directory <installdir>/bin/data/runtimes
, where <installdir>
refers to your Remote Services installation directory.
If some clients choose not to upgrade (but stay at a previous supported version), the only implication is that they will not be able to use the latest Gurobi version.
Comments
0 comments
Article is closed for comments.