Parameter sets

更新时间:
复制 MD 格式

As a service provider, you can use parameter sets to pre-configure some or all of the parameters for your service. This simplifies the deployment process for users by reducing complexity and preventing configuration errors. You can offer multiple parameter sets as best-practice configurations for different scenarios. You can also enable a custom parameter set to give users maximum flexibility. When parameter sets are configured for a service, users must select a parameter set to create a service instance, and then configure any remaining parameters.

Prerequisites

Your service template in Compute Nest contains parameters.

Procedure

  1. Log in to the Compute Nest console.

  2. On the Create New Service page, after you select a deployment region and enter the template content, click Add Parameter Set.

  3. In the parameter set configuration section that appears, select the parameters to include in the set.

    The available parameters are the input parameters parsed from your template.

    1. In the Add Parameter column, select the parameter you want to add.

    2. In the Plan column, modify the plan name and define the parameter values.

      Note
      • Parameter set names must be unique.

      • If you select an instance type in the Parameter Selection column, you can specify a single instance type or a range of instance types when creating the parameter set.

      You can add multiple parameter sets to offer various configurations. This allows users to choose the option that best fits their needs.

  4. (Optional) Select Support custom parameter set, and then set a name for the custom parameter set.

    A custom parameter set allows users to define the values of any parameter within the set.

    The configuration table includes two preset plan columns, Plan 1 and Plan 2, and a Custom Plan column. Configured parameters include System Disk Size (GB) (200 for Plan 1, 300 for Plan 2), Billing Method (PostPaid for both), and Public Bandwidth (10 for Plan 1, 20 for Plan 2). You can click Add Parameter to add parameter rows, click Add Parameter Set to add plan columns, or click Clear All Plans to reset the configuration.

  5. (Optional) Select Support plan category, set a plan category name, and define the plan category to which each parameter set belongs.

    This setting restricts how users can modify the configuration of their service instances. When modifying the configuration, users can switch only to parameter sets within the same plan category. Selecting this option adds a Plan Category row to the configuration table. You can then edit the category name for each parameter set, such as default or default1.

User view

  • If you do not configure any parameter sets, users see all parameters from the template and must configure each one. When deploying a service instance, the Parameter Settings section displays configuration options such as: Availability Zone (multiple zones can be selected, such as China East 1 Availability Zone B), Worker Node Instance Type (search and select an instance type, such as ecs.c6.large), Worker Node System Disk Size (default 120 GiB), Number of Worker Nodes (range 2–300, default 3), Instance Password (required), and Enable Public Access for API Server. At the bottom of the page, users must select the checkbox for the Compute Nest Service Agreement, can view the Cost Estimate, and then click Create to complete the deployment.

  • If you configure parameter sets, users must select a plan and then configure any remaining parameters. The deployment page shows a Plan Selection section with cards for a Basic plan (Number of worker nodes: 3, System disk size: 40 GB, Instance type: ecs.n4.large) and an Advanced plan (Number of worker nodes: 5, System disk size: 120 GB, Instance type: ecs.sn1.large) that users can click to select. Below this, the Parameter Settings section contains options such as Availability Zone (supports multiple zones), an Instance Password input field (8 to 30 characters, must contain three of the following: uppercase letters, lowercase letters, numbers, and special characters), and Enable Public Access for API Server. At the bottom are the Create button and the Compute Nest Service Agreement checkbox.

  • If you enable a custom parameter set, users can define the parameter values when they deploy a service instance. The deployment page displays a Plan Selection area that compares Plan 1, Plan 2, and a Custom Plan side-by-side. Each predefined plan lists specific values for various disk specifications (Random Data Disk Type, Sequential Data Disk Type, Data Ingestion Disk Type, System Disk Type, Metadata Disk Type) and the ECS Instance Type. For example, Plan 1 uses the ecs.r7a.2xlarge (8 vCPU, 64 GiB) instance type, an AMD-based memory-optimized r7a instance. Plan 2 uses ecs.g7a.4xlarge (16 vCPU, 64 GiB), an AMD-based general-purpose g7a instance. When a user selects the Custom Plan, all values show as N/A, allowing the user to configure each item.