Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Customizing a Fault

Updated on 2024-11-20 GMT+08:00

Scenarios

Create a drill task with a custom fault as the attack scenario on COC.

Precautions

A custom fault is determined by the script you compiled. Therefore, when scripts are used to attack ECSs, exceptions such as high resource usage and network faults may occur. As a result, the status of the UniAgent installed on the ECSs may change to offline or abnormal. Exercise caution when performing this operation.

Creating a Custom Fault

Create a drill task for a custom fault attack scenario on COC.

  1. Log in to COC.
  2. In the navigation pane on the left, choose Resilience Center > Chaos Drill. On the displayed page, click the Drill Tasks tab and create an attack task by referring to Step 2 to Step 6.
  3. Enter the attack task name, select Elastic Cloud Server (ECS) as Source of Attack Target, and click Next.

    Figure 1 Selecting ECS as the attack target source

  4. On the Select Attack Scenario procedure, click Custom fault, and then Custom Scripts. If a custom fault script exists, you can select it. If no custom fault script available, you need to create a script.

    Figure 2 Selecting the custom fault
    NOTE:

    1. Timeout Interval (s): used to limit the maximum time allowed for script execution. The timeout interval must be longer than the script execution time. You are advised to set the timeout interval to at least 30 seconds.

  5. To create a custom fault script, click Scripts. The Automated O&M > Scripts page is displayed. Click Create Script. For details about how to create a script, see section Creating a Custom Script. For details about the script specifications, see the following code:

     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    #!/bin/bash
    set +x
    
    function usage() {
        echo "Usage: {inject_fault|check_fault_status|rollback|clean}"
        exit 2
    }
    
    function inject_fault()
    {
        echo "inject fault"
    }
    
    function check_fault_status()
    {
        echo "check fault status"
    }
    
    function rollback()
    {
        echo "rollback"
    }
    
    function clean()
    {
        echo "clean"
    }
    
    case "$ACTION" in
        inject_fault)
            inject_fault
        ;;
        check_fault_status)
            check_fault_status
        ;;
        rollback)
            if [[ X"${CAN_ROLLBACK}" == X"true" ]]; then
                rollback
            else
                echo "not support to rollback"
            fi
        ;;
        clean)
            clean
        ;;
        *)
            usage
    ;;
    esac
    

    You are advised to define a custom fault script based on the preceding script specifications. In the preceding specifications, you can define the fault injection function, fault check function, fault rollback function, and environment clearing function by compiling customized content in the inject_fault(), check_fault_status(), rollback() and clean() functions.

    According to the preceding specifications, there are two mandatory script parameters: Whether other script parameters are included depends on your script content.

    Table 1 Mandatory parameters for customizing a fault script

    Parameter

    Value

    Description

    ACTION

    inject_fault

    Drill operation action. The value is automatically changed by the system background in different drill phases. The value can be:

    • inject_fault: The drill is in the fault injection phase.
    • check_fault_status: The drill is in the fault query phase.
    • rollback: The drill is in the phase of canceling the fault injection.
    • clean: The drill is in the environment clearing phase.

    CAN_ROLLBACK

    false

    Whether rollback is supported. The options are as follows:

    • true: When the drill is in the phase of canceling the fault injection, the rollback() function is executed.
    • false: When the drill is in the phase of canceling the fault injection, the rollback() function is not executed.
    NOTE:

    1. In the inject_fault function, add a flag indicating that the fault injection is successful, and check whether the flag exists in the check_fault_status function. If yes, the check_fault_status function can return normally (for example, exit 0). If no, the check_fault_status function can return abnormally (for example, exit 1).

  6. If you already have a custom script, you can select the script based on the script name. The script content and parameters are displayed. Enter a proper timeout interval and click Next.

    Figure 3 Selecting a custom script

  7. Create a drill task with the custom fault by referring to Step 9 to Step 17.

Custom Script Example

The following is an example of a customized script.

The script content is as follows:
  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
#!/bin/bash
set +x
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:~/bin
export PATH


function usage() {
    echo "Usage: {inject_fault|check_fault_status|rollback|clean}"
    exit 2
}

function inject_fault()
{
    echo "============start inject fault============"
    if [ ! -d "${SCRIPT_PATH}/${DIR_NAME}" ]; then
        mkdir -p "${SCRIPT_PATH}/${DIR_NAME}"
        echo "mkdir ${SCRIPT_PATH}/${DIR_NAME} successfully"
    fi

    cd "${SCRIPT_PATH}/${DIR_NAME}"

    if [ ! -f ${FILE} ]; then
        touch "${FILE}"
        echo "create tmp file ${FILE}"
        touch inject.log
        chmod u+x "${FILE}"
        chmod u+x inject.log
    else
        echo "append content">${FILE}
    fi
    echo "successfully inject">${FILE}
    echo "============end inject fault============"
}

function check_fault_status()
{
    echo "============start check fault status============"
    if [ ! -d "${SCRIPT_PATH}/${DIR_NAME}" ]; then
        echo "inject has been finished"
        exit 0
    fi
    cd "${SCRIPT_PATH}/${DIR_NAME}"
    SUCCESS_FLAG="successfully inject"

    if [ -f ${FILE} ]; then
        if [[ "$(sed -n '1p' ${FILE})" = "${SUCCESS_FLAG}" ]]; then
            echo "fault inject successfully"
        else
            echo "fault inject failed"
            exit 1
        fi
    else
        echo "inject finished"
        exit 0
    fi
    sleep ${DURATION}
    echo "============end check fault status============"
}

function rollback()
{
    echo "============start rollback============"
    cd "${SCRIPT_PATH}"
    if [ -d $DIR_NAME ]; then
        rm -rf "${SCRIPT_PATH}/${DIR_NAME}"
    fi
    echo "============end rollback============"
}

function clean()
{
    echo "============start clean============"
    cd "${SCRIPT_PATH}"
    if [ -d $DIR_NAME ]; then
        rm -rf "${SCRIPT_PATH}/${DIR_NAME}"
    fi
    echo "============end clean============"
}

case "$ACTION" in
    inject_fault)
        inject_fault
    ;;
    check_fault_status)
        check_fault_status
    ;;
    rollback)
        if [[ X"${CAN_ROLLBACK}" == X"true" ]]; then
            rollback
        else
            echo "not support to rollback"
        fi
    ;;
    clean)
        clean
    ;;
    *)
        usage
;;
esac

The input parameters of the script are as follows:

Table 2 Script input parameters of the customized script example

Parameter

Value

Description

ACTION

inject_fault

Drill operation action

CAN_ROLLBACK

false

Rollback is not supported.

SCRIPT_PATH

/tmp

Root directory of the custom fault log

DIR_NAME

test_script

Parent directory of the custom fault log

FILE

test.log

Custom fault log name

DURATION

10

Duration of a simulated custom fault, in seconds.

(This parameter does not take effect when it is placed in the inject_fault function.)

NOTE:

1. In the sample inject_fault function, the injected fault is to create a {FILE} file and add content to the {FILE} file. If successfully inject is entered in the {FILE} file, the fault injection is successful.

2. In the example, the check_fault_status function checks whether the {FILE} file exists. If no, the fault may have been cleared. In this case, exit 1 is returned. If yes, check whether the flag indicating that the fault injection is successful exists. If the flag exists, the fault injection is successful. Here, sleep {DURATION} is used to simulate the fault duration. If the flag does not exist, the fault injection fails.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback