Code Deployment with GridGain 9

To create a new deployment unit, click Add Deployment Unit and specify its name in the following dialog.

Any other name format will not pass the validation. Pre-release attributes are not supported, so you cannot assign unit a version like 1.2.3-alpha.

The newly created deployment unit is stored as a draft. As long as it is in the Draft state and has not been deployed, you can rename it. Once deployed, the unit cannot be renamed, you can only delete it or clone and assign it a version.

For a deployment unit to be eligible for deployment, it must contain the dependencies required to perform compute jobs. You can either upload the needed files or provide a direct URL to download them.

To add dependencies, first select your deployment unit while it is in the Draft state as you cannot add artifacts if the unit has already been deployed.

Then click Add Artifact. In the subsequent dialog, you have two options:

After adding all required dependencies click Deploy. You will be asked to set the deployment unit version before deployment.

When you deploy a unit, you choose an initial set of nodes: all nodes, a majority, or a specific subset. If you choose a majority or subset, the unit is deployed on-demand to other nodes when they first need it to avoid unnecessary early copying.

You can view the version history in a separate tab accessible from the Deployment Units list.

Deployment units are immutable, so you must create and deploy a new version whenever you want to change dependencies. To update a deployment unit:

To create a new deployment based on an existing version, click Clone and Deploy from the version’s menu and enter a new semver. This option may be useful for quickly replacing a unit deployed with an incorrect version.

You cannot Clone or Clone and Deploy units that were deployed via the CLI. To manage a CLI-deployed unit through Nebula, create a draft version from this unit, add artifacts, and deploy the new version.

Nebula keeps a complete history of all deployment unit versions in the Version History table.

The table provides the following information:

If you want to switch to an older version (for example, one of the updated dependencies did not work as expected), you can deploy the previous version.

Nebula will create a new version that copies all dependencies from the selected version.

This section lets you upload an artifact to Nebula. Uploaded artifacts will be stored on the Nebula host and sent to all deployment units as needed.

To add a new artifact, click Add artifact button and select the file you needThe artifact will then be stored locally and made available for use with your deployment units.

To see all deployment units that use a specific artifact, click ⋮ and select View dependent list. The dialog that opens lists all deployment units that use the selected artifact.

To delete an artifact, click ⋮ and select Remove. If the selected artifact has dependents, they show in the Dependent list dialog - see Checking Dependent List. You must delete the dependent deployment units before you can remove the artifact itself.