Compute Nest provides multiple types of deployment packages to help you efficiently and quickly deploy services in various scenarios. These deployment packages include Elastic Compute Service (ECS) images, files, container images, and Helm charts.
What is a deployment package?
A deployment package is a carrier used in the deployment process, such as an ECS image, Helm chart, file, or container image. You can select an appropriate deployment package type for a service based on the deployment scenario.
Compute Nest provide the following capabilities for deployment packages:
Replication: Deployment packages can be replicated across regions. After you select a region, deployment packages can be automatically replicated to that region.
Mapping: Compute Nest automatically maps a service instance to a deployment package in the region in which the service instance is to be deployed.
Permission management: Compute Nest provides strict permission control on deployment packages. The public or private attribute of a service determines the attribute of the deployment package associated with the service.
ECS image deployment package
In ECS-based deployment scenarios, we recommend that you pack the software package and environment into an ECS image deployment package. The deployment by using an ECS image deployment package is fast to start and does not rely on Internet access. In principle, Compute Nest replicates an image from one region to other regions and make the image public for all users.
For more information, see ECS image deployment packages.
Container image deployment package
We recommend that you use Container image deployment packages when Docker container images are used for service deployment. Compute Nest provides a public Alibaba Cloud Container Registry repository to manage and store container image deployment packages. The container image deployment packages of multiple tenants are isolated by using namespaces. When you create a container image deployment package, you can upload your image to a namespace by using a temporary key. When a customer creates a service instance, the image is pulled from the repository by using a temporary key.
Container image deployment packages can be pulled only over the Internet. The ECS instances or Container Service for Kubernetes (ACK) clusters to which you want to pull container image deployment packages must be able to access the Internet. This deployment package type is applicable only to one-time deployment scenarios because a container image deployment package is pulled by using a temporary key. It cannot be used for scaling or applications that need to dynamically pull images.
For more information, see Manage container image deployment packages.
File deployment package
In script-based deployment scenarios, you may need to download some software resources during the deployment process. The software download may time out due to a large file size or fail due to lack of Internet access. To resolve the preceding issues, we recommend that you download files in the form of file deployment packages.
In principle, Compute Nest provides an Object Storage Service (OSS) bucket for each region. After you upload your files to Compute Nest, Compute Nest copies the files to the bucket in each region. Then, a script can download a file from an internal HTTP address generated by Compute Nest for the file in the corresponding OSS bucket. File download over an internal network is faster and more stable and secure.
For more information, see File deployment packages.
Helm chart deployment package
We recommend that you use Helm chart deployment packages in scenarios in which you need to use a Helm chart to manage YAML files due to a complex service structure. Similar to container image deployment packages, Helm chart deployment packages are stored in the public Container Registry repository of Compute Nest. You can upload your local Helm chart to the Container Registry repository of Compute Nest by using a temporary key. Then, you can pull the Helm chart over the Internet by using a temporary key.
For more information, see Helm chart deployment packages.