The package deployment process has two phases: First, service packages are copied to the central repository on the repository server, the host on which the rs service is running. Then, when workload comes in, the service package is copied to compute hosts and uncompressed.
Package removal also has two phases: When a request to remove a package is made, service packages are removed from the central repository. Then, when a new application is deployed and existing packages on the compute hosts are no longer needed, packages are removed from compute hosts. For existing applications, when an existing package is updated, the packages that exist on compute hosts are overwritten when workload comes in.
You deploy the service package using the Platform Management Console or the soamdeploy add command. With the Platform Management Console, you use the Add/Remove Applications wizard or the global action Add package to repository in Manage Service Packages.
As workload comes in, the specified service in the application profile is requested for tasks. Platform Symphony checks whether the required service is already on the compute host.
If the service is not already on the compute host, the Repository Service copies the service package from the repository server to the compute host, and uncompresses it, ready to be used.
You request to remove the service package using the Platform Management Console or the soamdeploy remove command, or you update an existing package through the Management Console or the soamdeploy add command.
Whenever a new package is deployed on to the host, the removed package is deleted. Whenever an updated package is deployed on to the host, the existing package is overwritten with the updated package.