Preparations

Preparing Resources

To facilitate subsequent operations, ensure that:

1. Create a VPC. For details, see Creating a VPC.
2. Create an exclusive ServiceComb engine with security authentication disabled. For details, see Creating a Microservice Engine.

   The VPC to which the ServiceComb engine belongs is the one created in 1. If the VPCs are inconsistent, correctly configure the VPC connectivity.

3. Create a CCE cluster. In a trial scenario, set Cluster Scale to 50 nodes and Master Nodes to Single. For details, see Buying a Cluster.
   • The VPC to which the CCE cluster belongs is the one created in 1.
   • The cluster contains at least one ECS node with 8 vCPUs and 16 GB memory or two ECS nodes with 4 vCPUs and 8 GB memory, and is bound to an EIP. For details, see Creating a Node.
   • The CCE cluster cannot be bound to other environments.

Registering a GitHub Account and Forking the Weather Forecast Source Code

1. Register a GitHub account.
2. Log in to GitHub.
3. Go to the weather forecast source code repository.
4. Fork the weather forecast source code repository to your account. For details, see Forking a repository.

Setting GitHub Repository Authorization

You can set GitHub repository authorization so that build projects and application components can use the authorization information to access the GitHub source code repository.

1. Log in to ServiceStage.
2. Choose Continuous Delivery > Repository Authorization > Create Authorization and configure authorization information by referring to the following table.

   Parameter	Description
   *Name	Use the default authorization name. The name cannot be changed after the authorization is created.
   *Repository Authorization	Select GitHub. Select OAuth for Method. Click Use OAuth Authorization and complete the authorization for accessing the GitHub source code repository as prompted.

Creating an Organization

1. Choose Deployment Source Management > Organization Management.
2. Click Create Organization. On the displayed page, specify Organization Name. For example, org-test.
3. Click OK.
   Figure 1 Creating an organization
   

Creating an Environment

1. Choose Environment Management > Create Environment. Then set required environment parameters by referring to the following table, and retain the default values for other parameters.

   Parameter	Description
   Environment	Enter an environment name, for example, env-test.
   Enterprise Project	default is selected by default. Enterprise projects let you manage cloud resources and users by project. It is available after you enable the enterprise project function.
   Environment Type	Select Kubernetes.
   HA Environment	Select No.
   VPC	Select the VPC prepared in Preparing Resources. NOTE: The VPC cannot be modified after the environment is created.
   Configuration Mode	Select Resource management.

   Figure 2 Configuring an environment
   

2. Click Create Now.
3. Choose Clusters under Compute and click Bind now.
4. In the dialog box that is displayed, select the CCE cluster created in Preparing Resources and click OK.
5. Choose ServiceComb Engines under Middleware and click Manage Resource.
6. In the dialog box that is displayed, select the ServiceComb engine created in Preparing Resources and click OK.

Creating an Application

1. Click in the upper left corner to return to the Environment Management page.
2. Choose Application Management > Create Application and set basic application information.
   1. Name: Enter weathermap.
      

      If an application with the same name already exists in the application list, rectify the fault by referring to What Should I Do If a Weather Forecast Application with the Same Name Exists in the Current Environment?

   2. Enterprise Project: default is selected by default. Enterprise projects let you manage cloud resources and users by project.

      It is available after you enable the enterprise project function.

3. Click OK.
   Figure 3 Creating an application