Creating an Environment

Creating an Environment

1. Log in to ServiceStage.
2. Choose Environment Management > Create Environment and configure the environment. Parameters marked with an asterisk (*) are mandatory.

   Parameter	Description
   *Environment	Environment name. Enter 2 to 64 case-insensitive characters. Start with a letter and end with a letter or digit. Only use letters, digits, underscores (_), and hyphens (-).
   *Enterprise Project	Enterprise projects let you manage cloud resources and users by project. It is available after you enable the enterprise project function.
   Description	Environment description. Click and enter up to 128 characters. Click to save the description.
   *VPC	NOTICE: After the environment is created, the VPC cannot be modified during Modifying an Environment. Select the VPC where the environment resource is located based on your service requirements. VPC where the environment resources are located. To use a created VPC, select a VPC created under the current account from the drop-down list. To use a shared VPC, select a VPC that another account shares with the current account from the drop-down list. VPC owners can share the subnets in a VPC with one or multiple accounts through Resource Access Manager (RAM). Through VPC sharing, you can easily configure and manage multiple accounts' resources at low costs. For more information about VPC and subnet sharing, see VPC Sharing. To use a new VPC, click Create a VPC. For details, see Creating a VPC.
   *Environment Type	Environment type. VM: applicable to VM-based deployment. Components are deployed on VMs using software packages. Kubernetes: applicable to container-based deployment (CCE). Components are deployed using container images and scheduled by Kubernetes. NOTE: For details about the component deployment mode, see Deploying a Component. If the environment type is Kubernetes and CCE is used for deployment, you are advised to run the following command on the CCE node to add a firewall: iptables --append OUTPUT --proto tcp --destination 169.254.169.254 --match owner ! --uid-owner root -j REJECT 169.254.169.254 is a special address in OpenStack and is used to provide instance metadata and user data services. This command prevents non-root users from obtaining sensitive information or performing unauthorized operations using this address.
   *Tags NOTE: Tags can be set in CN East2.	Tags are used to identify cloud resources. When you have multiple cloud resources of the same type, you can use tags to classify them based on usage, owner, or environment. If your organization has configured tag policies for ServiceStage, add tags to trackers based on the policies. If a tag does not comply with the tag policies, environment creation may fail. Contact your administrator to learn more about tag policies. Each environment can have a maximum of 20 tags. Click Add Tag. The Add Tag dialog box is displayed. Click Add Tag. Enter the key and value of the tag. The key contains 1 to 36 characters, including digits, letters, underscores (_), or hyphens (-). The value contains 2 to 43 characters, including digits, letters, underscores (_), periods (.), or hyphens (-). It is recommended that you create a predefined tag on TMS to add the same tag to different resources. Click OK.

   Figure 1 Configuring an environment
   

3. Click Create Now.

   After the environment is created, go to the environment details page to view the environment details and configure environment resources.

Follow-Up Operations

• After a Kubernetes environment is created, bind a CCE cluster to the environment before using the environment to deploy components. For details, see Managing CCE Resources.
• After an environment is created, the compute resources (excluding CCE clusters), network resources, and middleware need to be managed together to form an environment. For details, see Managing Basic Resources.