Creating a Patch Baseline

Scenarios

Create a patch baseline on Cloud Operations Center.

Procedure

1. Log in to COC.
2. In the navigation pane on the left, choose Resource O&M. On the displayed page, click Patch management.
3. On the displayed page, click Patch Baseline to view the baseline list.
   Figure 1 Patch baseline list
   

4. Click Creating Patch Baseline.
   Figure 2 Creating a patch baseline
   

5. Set the patch baseline information as prompted.
   Figure 3 Setting the patch baseline information
   
   

   Table 1 describes the parameters for creating an installation rule baseline.

   Table 2 describes the parameters for creating a custom baseline.

   Table 1 OS installation rule baseline

   Field	Options	Description
   Product	Huawei Cloud EulerOS All Huawei Cloud EulerOS 1.1 Huawei Cloud EulerOS 2.0 CentOS All CentOS7.2 CentOS7.3 CentOS7.4 CentOS7.5 CentOS7.6 CentOS7.7 CentOS7.8 CentOS7.9 CentOS8.0 CentOS8.1 CentOS8.2 EulerOS All EulerOS 2.2 EulerOS 2.5 EulerOS 2.8 EulerOS 2.9 EulerOS 2.10	OS of patches. Only the patches of the selected OS can be scanned and repaired.
   Category	All Security Bugfix Enhancement Recommended Newpackage	Category of patches. The patches of the selected category are scanned and repaired.
   Severity	All Critical Important Moderate Low None	Severity level of patches. The patches of the selected severity level can be scanned and repaired.
   Automatic Approval	Approve the patch after a specified number of days. Approve patches released before the specified date.	Automatically approve patches that meet specified conditions.
   Specified Days	0 to 365	This parameter is mandatory when Approve the patch after a specified number of days. is selected.
   Specified Date	None	This parameter is mandatory when Approve patches released before the specified date. is selected.
   Compliance Reporting	Unspecified Critical High Medium Low Suggestion	Level of a patch that meets the patch baseline in the compliance report
   Install Non-Security Patches	None	If you do not select this option, the patches with vulnerabilities will not be upgraded during patch repairing.
   Exceptional Patches	None	The formats of the software packages of approved patches and rejected patches are as follows: The format of a complete software package name: example-1.0.0-1.r1.hce2.x86_64. The format of the software package name that contains a single wildcard: example-1.0.0*.x86_64.

   Table 2 Customized installation rule

   Field	Options	Description
   Product	Huawei Cloud EulerOS All Huawei Cloud EulerOS 1.1 Huawei Cloud EulerOS 2.0 CentOS All CentOS 7.2 CentOS 7.3 CentOS 7.4 CentOS 7.5 CentOS 7.6 CentOS 7.7 CentOS 7.8 CentOS 7.9 CentOS 8.0 CentOS 8.1 CentOS 8.2 EulerOS All EulerOS 2.2 EulerOS 2.5 EulerOS 2.8 EulerOS 2.9 EulerOS 2.10	Product attribute of the patch. Only the patches of the selected OS can be scanned and repaired.
   Compliance Reporting	Unspecified Critical High Medium Low Suggestion	Level of a patch that meets the patch baseline in the compliance report
   Baseline patch	None	You can customize the version and release number of a baseline path. Only the patches that match the customized baseline patch can be scanned and installed. A maximum of 1,000 baseline patches can be uploaded for a baseline. The patch name can contain a maximum of 200 characters, including letters, digits, underscores (_), hyphens (-), dots (.), asterisks (*), and plus signs (+). The data in the second column consists of the version number (including letters, digits, underscores, dots, and colons) and the release number (including letters, digits, underscores, and dots) that are separated by a hyphen (-). Both two types of numbers can contain a maximum of 50 characters.

6. Click Submit.
   Figure 4 Creating a customized patching baseline