When you use Compute Nest services as a developer, you can select different types of services based on the scenarios. This topic describes the definitions and scenarios of different types of services and provides links to the relevant references.
The following table describes different types of services supported by Compute Nest, including their definitions and scenarios.
Service type | Definition | Description | References |
Private service | Software and resources are deployed within the customer accounts. | Private services are suitable for deploying Platform as a Service (PaaS) and Software as a Service (SaaS) applications in virtual private clouds (VPCs) within customer accounts. | |
Fully managed service | Software and resources are deployed within the service provider accounts. | Fully managed services are suitable for deploying PaaS and SaaS applications in VPCs within the service provider accounts. Service providers have full permissions to manage the cloud resources and customer applications. Compute Nest allows customers to use exclusive resources in the following services: single-tenant fully managed services and fully managed services deployed in multi-tenant Container Service for Kubernetes (ACK) clusters. In single-tenant fully managed services, resources are exclusive to each customer. In fully managed services deployed in multi-tenant ACK clusters, resources are exclusive to each pod. | |
Hosted O&M service | Customers authorize service providers to perform hosted O&M operations on specific cloud resources within a specific period. | After a service provider publishes a hosted O&M service, when a customer creates a service instance based on the service, the customer grants the service provider the permissions to perform hosted O&M operations. No cloud resources or applications are created during this process. |
Scenarios
Deploy a private service
Characteristics:
Resources are deployed in VPCs within the accounts of customers.
Resources are exclusive to each customer.
A central data center and cloud boxes are supported.
Private services in Compute Nest provide the following capabilities and benefits:
Private services can be published as Alibaba Cloud Marketplace products.
Private services can be sold based on the pay-as-you-go and subscription billing methods.
Configurations of service instances can be changed in Alibaba Cloud Marketplace.
Custom deployment interfaces are provided.
The resources detected during an inventory check must be available.
A comprehensive price inquiry feature is available.
Resources and software can be pulled and deployed in VPCs within the accounts of customers with a few clicks.
Versions of services and clusters of customers can be managed in a centralized manner.
Hosted O&M can be performed on clusters of customers and the audit feature is available.
Deploy a single-tenant fully managed service
Characteristics:
Resources are deployed in VPCs within the accounts of service providers.
Resources are exclusive to each customer.
Service providers provide services, and resources are invisible to customers.
Customers access services over the Internet or VPCs.
Deploy a fully managed service in a multi-tenant ACK cluster
Characteristics:
Resources are deployed in VPCs within the accounts of customers.
Resources of customers are deployed in an ACK cluster, pod resources are exclusive to customers, and the ACK cluster is shared by the customers.
Resources that are not deployed in the ACK cluster can be shared or exclusive to pods.
Customers access services over the Ingresses of ACK clusters or VPCs.
Fully managed services in Compute Nest provide the following capabilities and benefits:
Fully managed services can be published as Alibaba Cloud Marketplace products.
Fully managed services can be sold based on the pay-as-you-go and subscription billing methods.
Configurations of service instances can be changed in Alibaba Cloud Marketplace.
Custom deployment interfaces are provided.
Various custom components can be managed.
The resources detected during an inventory check must be available.
Resources and software can be pulled and deployed in VPCs within the accounts of service providers with a few clicks.
Connections to VPCs can be established in one of the following modes:
PrivateLink
VpcPeering
Versions of services and clusters of customers can be managed in a centralized manner.
The monitoring feature is supported for fully managed services. Customers can view the monitoring data.
Multiple accounts can be managed based on resource directories in single-tenant fully managed services.
Create a service
Determine a deployment architecture.
Before you create a service as a service provider, you must plan the deployment architecture of the service. The deployment architecture includes the types and configurations of the required cloud resources, and the network architecture.
Create a deployment package.
You must create a deployment package, such as an Elastic Compute Service (ECS) image, a Helm chart, an Object Storage Service (OSS) object, or a container image. You can select a deployment package based on your business requirements. For more information about deployment packages, see Deployment package overview.
Configure service information.
After you determine the deployment architecture, you must configure service information when you create the service, including the basic information, deployment configurations, O&M configurations, and advanced configurations of the service.
Compute Nest provides three types of services: private services, fully managed services, and hosted O&M services. The information that you need to configure varies with the service type. The following table describes the parameters that are used to create a private service.
Section
Parameter
Required
Description
Basic Information
Service Type
Yes
The type of the service. Compute Nest supports multiple types of services.
Service Information
Yes
The Service Information section contains parameters such as Service Icon, Service Name, Service Description, and Version Description.
Default Prefix for Service Instance Name
No
The default prefix of the service instance name. After you specify the default prefix, the prefix is automatically added to the service instance name when a customer deploys the service instance.
Tag Settings
No
The tag key and value. Select or enter a tag key and a tag value to add a tag to the service resources.
If multiple cloud resources that are associated with each other exist within your account, you can add custom tags to these resources to categorize the resources. This way, you can manage the resources in a centralized manner. For more information, see Add a custom tag.
Resource Group
No
The resource group to which you want to add the service resources. Service providers can use resource groups to group their cloud resources from dimensions, such as the usage, permissions, and ownership. This allows service providers to manage resources of multiple customers and projects in a hierarchical manner and implement more fine-grained authorization than that based on Alibaba Cloud accounts. For more information, see Manage resource groups.
Service Deployment
Deployment Settings
Yes
In the Deployment Settings section, you can use a template to define information such as the resources required to create your service and the dependencies among the resources.
The Deployment Settings section contains parameters such as Regions, template-related parameters, and parameter sets. You can import a scenario-based template or a custom template.
Deployed At
No
The estimated deployment duration and the deployment timeout period. For more information, see Configure an estimated deployment duration and a deployment timeout period.
Deployment Package Association
No
The deployment package that you want to associate with the service. If no deployment package is available, you must create a deployment package first. For more information, see Deployment package overview.
Application Group
No
The application groups of resources in the template. You can add all resources in the template to application groups. This way, you can manage the resources in a centralized manner.
Service O&M (Optional)
O&M
No
The O&M operations that the customer authorizes the service provider to perform on the service instances created based on the service.
Monitoring
No
The alert template provided by CloudMonitor. After you select an alert template, Compute Nest sends alert notifications to customers based on the trigger rules of the template.
Upgrade
No
Specifies whether to enable the upgrade feature for service instances. For more information, see Configure service upgrades.
Modify Configurations
No
Specifies whether to enable the configuration change feature for service instances. If you turn on Service Instance Configuration Change, you can specify whether your customers can modify the configurations of parameter sets and parameters that are configured for service instances.
Advanced Configuration (Optional)
Permission Settings
No
The permission settings for accessing the deployment URL of the service.
Trial Settings
No
Specifies whether to enable free trial for the template or the parameter set of the service. If you enable free trial for the template or the parameter set of your service, your customers can use the service free of charge within a period.
Network Settings
No
Specifies whether to enable private access to the service over VPCs. If you enable private access to the service over VPCs, customers can access the service over a private connection.
License Settings
No
The license management feature for the service. For more information, see CheckOutLicense.
Publish a service
To publish a service, you must perform operations such as testing the service, submitting the service for review, and publishing the service.
Operation | Description |
Test the service | After the service is created, you must test the service to ensure that the service is available. For more information, see Test a service. |
Pre-publish the service | You can pre-publish the service of a locked version, which can be shared with specified customers. |
Submit the service for review | After the service passes the test, click Submit Review to submit the service for review. Alibaba Cloud completes the review within three business days. |
Publish the service | After the service passes the review, click Publish Service to publish the service. You can provide the deployment URL of the service for your customers. The customers can access the deployment URL to create service instances. |
(Optional) Publish the service to Alibaba Cloud Marketplace | If you want to sell the service online, you can publish the service to Alibaba Cloud Marketplace. For more information, see Overview of selling Compute Nest services in Alibaba Cloud Marketplace. |