Setting up a container

Set up the target release container on the Utility Node MSVM, Power9 management server, or any other management server, decompress installation packages, and start the container for system updates and prechecks.

Set up the target release container by completing these steps:

Decompress the package.

cd /home/deploy ; xz --decompress <xz package>

Decompress the generated tarball.
```
tar -xvf <uncompressed tarball>
```
Start the container.
```
sh <untarred binary file>
```
Note:
- If this is not the first time that you run the container or if there is no hardware change on the system, it is not necessary to cleanup the inventory. In a later step, the inventory file is filled with the latest hardware information of the system by running the essrun config load command.
- It is highly recommended to run the essrun config load command in a later step, even if the hardware inventory from the container is not deleted.
- Manage the deployment container by using the essmkyml script, not by using direct podman commands.
Import nodes configuration in to the management node.
```
essrun -N <management hostnames> config load -p
```
Use applicable managment hostnames to a management server. The following command is an example of which other nodes configuration can be imported.
```
essrun -N emsvm,ems,ems2,essio1,essio2,prt01,prt02 config load -p
```
Where:

emsvm

Specifies a management sever virtual machine.

ems

Specifies a management server.

essio1,essio2

Specifies I/O nodes.

prt01,prt02

Specifies protocol nodes.
Check nodes for issues.
```
essrun -N ems,ems2,essio1,essio2,prt01,prt02 update --precheck
```
Use IBM Storage Scale Systems Precheck tool to check all nodes before the upgrade.
If you run the precheck during the upgrade, the upgrade takes longer time. Therefore, it is recommended to run the precheck before you start the upgrade. For more information, see Checking the system health by using the decoupled precheck tool.