EdgeNext Documentation

Edge BMC Service Level Agreement

The Service Level Agreement ("SLA") stipulates the service
availability level index and compensation scheme of Bare Metal Cloud
("BMC") provided by EdgeNext for you. In particular, unless
otherwise agreed, the Agreement does not apply to the specification
family of BMC beta test and invited test.

Article 1 Service Description

1. BMC (Bare Metal Cloud) is a flexible, secure and stable computing service located in the edge cluster, which helps you reduce IT costs, improve operation and maintenance efficiency, and enable you to focus more on core business innovation.

Article 2 Service Definitions

1. Service period: a service period is one calendar month. A period shorter than a calendar month is also counted as one service period.

2. Total number of minutes of single-instance service period: the total number of days of single-instance service period x 24 (hours) x 60 (minutes).

3. Instance unavailable: where a BMC instance for which exit and entrance permission rules have been set is unable to establish both-way (exit/entrance) connection with any one IP address by using TCP or UDP protocol and this state lasts for over one minute, the BMC instance is deemed unavailable in that minute.

4. Down time of single-instance service: where a BMC instance is unable to establish network connection with any one IP address by the exit and entrance permission rules within a minute, the BMC instance service is deemed unavailable in that minute, and the 5 consecutive minutes or longer time during which the service provided by BMC is unavailable is counted as down time. Down time excludes routine system maintenance time and any down time on account of the user, any third party or force majeure.

5. Single-region multi-AZ service unavailable: where the user's BMC instances are deployed in at least 2 availability zones (hereinafter referred to as single-region multi-AZ service) in one region, all BMC instances of the user are unavailable in any one availability zone in the region and the user's BMC instances in the other availability zones in the region are also unavailable (hereinafter referred to as: unavailable BMC instances in the other availability zones in one region), the BMC instances in the other availability zones in the region are deemed single-region multi-AZ service unavailable.

6. Minutes of single-instance single-region multi-AZ service unavailable: the sum of minutes of unavailable single-region multi-AZ service of single BMC instance in one service period.

7. Monthly service fee: the total amount of service fee paid by you for a single BMC instance in one service period (calendar month). Where you pay the service fee for multiple months in one time, the monthly service fee will be shared and calculated according to the paid amount and months.

Article 3 Service Availability

1. Service availability calculation formula = (total due service time of all instances at the node in the service period - down time of the node instances in the service period) / total due service time of all instances at the node in the service period

2. Service availability commitment

   2.1 For the single-instance dimension, EdgeNext undertakes that the service availability of BMC in one service period is not less than 99.9%;
   2.2 For the single-region multi-AZ dimension, EdgeNext undertakes that the service availability of BMC in one service period is not less than 99.9%.

3. Where BMC does not fulfill the availability promise, you are entitled to obtaining the compensation as stipulated in Article 4 herein. Such compensation does not cover the service unavailability arising from any of the following factors:

   3.1 Any network or equipment fault or configuration adjustment other than the equipment of EdgeNext;

   3.2 Hacker attack on any of your application programs;

   3.3 Loss or leakage of data, password or PIN code caused by improper maintenance or protection by you;

   3.4 Your negligence or any action authorized by you;

   3.5 You fail to follow the product manual or recommendations of EdgeNext, e.g. unavailability happens because you conduct shutdown, reboot or cloud drive uninstallation of BMC instance by using the control methods such as control console, API or CLI;

   3.6 Data is erased due to crash of local drive, and thus service is rendered unavailable due to dependence on local drive or the data in local drive;

   3.7 Any error in BMC instance resulting from any software installed by you or any third-party software or configuration not directly run by EdgeNext;

   3.8 The service is suspended or terminated because you fail to comply with the EdgeNext Bare Metal Cloud Service Contract or Supplementary Agreement thereto, including the situation where BMC instance is temporarily denied service or released due tonon-payment of service fee;

   3.9 Short-term service interruption caused by routine maintenance or upgrading of BMC conducted by EdgeNext in accordance with the EdgeNext Bare Metal Cloud Service Contract or Supplementary Agreement thereto; and

   3.10 Force majeure.

Article 4 Compensation Scheme

1. For the service availability of the BMC product used by you, EdgeNext may choose to use any of the following compensation schemes, depending on actual business conditions.

1.1 Compensation with voucher

The compensation amount is calculated by the criteria in the table below. Compensation is granted only through the voucher for purchase of BMC product, and the total amount of compensation is no more than the monthly service fee paid by you for the node month in which the expected service availability is not fulfilled (excluding the fee paid by the
voucher).

Service availability	Amount of compensation voucher
< 99.9%, ≥ 99%	10% of the service fee for the instance in the node month
< 99%, ≥ 95%	25% of the service fee for the instance in the node month
< 95%	50% of the service fee for the instance in the node month

1.2 Compensation for duration of failure

Compensated duration is calculated by the criteria in the table below, and the total compensated duration is no more than the total service duration of all servers in the service cluster in the current month. (Excluding the compensated duration in the current month)

Service availability	Compensated duration
< 99.9%, ≥ 99%	10% of the total service duration of the instance in the node month
< 99%, ≥ 95%	25% of the total service duration of the instance in the node month
< 95%	50% of the total service duration of the instance in the node month

2. Deadline for compensation request
   You may submit the compensation request after the fifth (5th) working day of each month for the BMC service that did not achieve the expected availability in the previous month. The compensation request must be submitted within two (2) months after the month in which BMC service did not achieve the expected availability. Any compensation request submitted beyond such deadline will not be accepted.