This document describes the applications and projects in CODING Continuous Deployment (CODING-CD).
You must activate the CODING DevOps service for your Tencent Cloud account before you can use CODING Project Management (CODING-PM).
All the applications and projects in CODING-CD are level-1 resources belonging to an enterprise or team. There is a one-to-many relationship between them; that is, one project can contain multiple applications, and one application can belong to multiple projects.
With this design, Ops personnel can focus on the management of the continuous deployment of the applications (deployment pipelines, infrastructure, etc.), while non-Ops personnel (generally developers) only need to handle the project dimension (submitting release orders, viewing release details, etc.), so that the former can focus on infrastructure Ops in the cloud, and the latter can carry out most of the business Ops within projects and create a complete closed loop from the requirement to the release.
An application is the basic deployment unit in CODING-CD. Each includes several application clusters as well as security groups and load balancers. It abstracts the set of deployed software and usually represents the services you want to deploy, their configurations, and the basic settings required for their execution. The recommended approach is for one application to correspond to one service in the microservice architecture.
In the microservice architecture, a microservice corresponds to a CODING-CD application. You can set the corresponding relationships based on your preferences. The following example shows the relationships among a team, projects, applications, clusters, and cloud accounts:
Team: XXX Technology Co., Ltd. | |||
---|---|---|---|
Cloud account |
|
||
Project 1: An E-Commerce Site for In-Vehicle Products |
|
||
Project 2: An E-Commerce Site for Clothes |
|
||
CODING-CD Console |
|
A cloud account is the token for accessing cloud resources. To create an application in the CODING-CD Console, click Application > Create App in the navigation bar. Before you create an application, make sure that you have completed Cloud Account Binding.
Click "Deployment Console" on the left side of the homepage, and then click Create App in the upper-right corner.
After creating an application in the CODING-CD Console, you can directly associate it with a project on the homepage of the console.
When Ops personnel completes the Deployment Pipeline Configuration of an application, developers can create a complete closed DevOps loop from project collaboration to application release within a project. For example, when a new version needs to be released, developers go to Continuous Deployment > Kubernetes to create a release order, which automatically triggers the execution of the deployment pipeline. Developers can view the release status and historical details at any time.
After you create an application in the CODING-CD Console, you can change the application fields and notifications in the Configuration of the application, or delete it.
Notifications can be sent through CODING, WeCom, DingTalk, and Feishu.
You can disable the function entries that you do not need in the Features section. This will merely hide the function entries in the console, and will not delete their data.The function entries of deployment pipelines, clusters, load balancers, and security groups can be hidden:
You can click Cluster > Service Group > Instance Details to view the custom link of the running instance. The link offers brief information on the instance, such as the log and health status.
The IP address that corresponds to the custom link can be a public or private IP address. The default port is 80. But you can set another port number that starts with :
in the "Path" text field, such as :7002/health
.
Note:You can enter an expression in the URL field to reference more instance fields. For example, a Tencent Cloud instance can use
{region}
to reference the region where the instance resides.
Note:Traffic protection is designed to ensure that at least one instance is operating normally at any time.
Once the function is enabled, when a user or script tries to delete, disable or scale a service group, the CODING Console will verify if at least one instance in the cluster is running normally. If not, the request will be rejected.
Field | Required? | Description |
---|---|---|
Cloud account | Yes | The cloud account for enabling traffic protection |
Region | Yes | Choose the region(s). `*` indicates all the regions. |
Group | No | The cluster group for enabling traffic protection. If this field is left empty, the cluster does not belong to any group. |
Details | No | A level-3 field that differentiates clusters. The service groups with the same `${Application}-${Stack}-${Detail}` belong to the same cluster. |
If there is a service group in an application, you need to delete the service group first.
In the CODING-CD Console, click the gear icon in the lower-right corner of the application. After you open the application configuration page, click Delete.
Was this page helpful?