Types of deployment

There are two types of deployment supported in Symphony:

  1. Deployment of service packages, containing Symphony applications

  2. File packages, which may contain files, binaries or other executables, patch updates, data or other files you want to make available to all or many hosts in the cluster

Both types of deployment deploy packages to the repository server, which stores the package files.

Service package deployment

Service package deployment is accomplished using the application deployment wizard, or the soamdeploy command. When you deploy a Symphony service package, the packages are downloaded to compute hosts on demand. This type of deployment is optimized to handle version updates of your service package.

This is the recommended method for deploying your Symphony service packages.

File package deployment

File package deployment is accomplished using the rsdeploy command. This type of deployment copies and installs one file package to many hosts at a time, whether the file package is needed by the receiving hosts or not. Install and uninstall operations to and from the compute hosts must be initiated by the user. There is no package version logic to manage versioning. Only hosts that are available at the time the installation operation occurs receive the package. All adding, removing, installing and uninstalling of packages are under direct user control.

This type of deployment can help you deploy Symphony patches more easily, load existing executables onto multiple hosts in the cluster, or load data required by many hosts.