CloudOps Orchestration Service:Manage custom extensions in batches

In the Extension Configuration step, set the parameters as prompted.

Examples for installation script and uninstallation script:

• Sample installation script

  #!/bin/bash
  #######  Usage notes of the installation script template for single-process software packages  #########
  #1. By default, this script is executed in the root directory. The default directory is /root for an ECS instance that runs Linux.
  #2. After the software is installed by using the script, the remote download path is deleted by default.
  #3. We recommend that you use the job_start function to customize the software.
  #4. The process ID of the software package must be stored in the specified path based on the process ID storage constraints.
  
  #######  error code specification  #########
  # Please update this documentation if new error code is added.
  # 1   => install fail
  # 2   => check health fail
  # 3   => record process id fail
  # 4   => user shell fail
  
  function user_shell() {
      # Run the custom installation script.
      $nohup java -jar demo-1.0.0-SNAPSHOT.jar > /demo.log 2>&1 &
      # Stop running the custom installation script.
  }
  
  ##### When the script starts to run, you can invoke this function to display the timestamp and process ID of the software package and store the process ID in the specified path. 
  function job_start() {
      user_shell
      if [ $?  -ne 0 ]; then
          exit4
      else
          # This constraint cannot be deleted.
          now=$(date +'%Y-%m-%d %H:%M:%S')
          pid=$!
          echo "[$now][$pid] job_start"
          pidPath="/etc/aliyun"
          if [ !  -d $pidPath ]; then
              mkdir -p /etc/aliyun
              echo "Create the $pidPath path to store the process ID."
          fi
          echo "$pid" > "$pidPath/main_process_id"
          if [ $?  -ne 0 ]; then
              exit3
          fi
      fi
  }
  
  ##### Invoke this function to check whether the service runs as expected. You can check the process status or call the curl command in this function.
  function check_health() {
      now=$(date +'%Y-%m-%d %H:%M:%S')
      echo "[$now][$$] check_health"
  }
  
  function exit1() {
    echo "exit code 1, install fail"
    exit 1
  }
  
  function exit2() {
    echo "exit code 2, check health fail"
    exit 2
  }
  
  function exit3() {
    echo "exit code 3, record process id fail"
    exit 3
  }
  
  function exit4() {
    echo "exit code 4, user shell fail"
    exit 4
  }
  
  
  ##### If 0 is returned, the execution is successful. Otherwise, the execution fails.
  function main() {
      job_start
      if [ $?  -ne 0 ]; then
          exit1
      fi
      check_health
      if [ $?  -ne 0 ]; then
          exit2
      fi
  }
  
  ##### The execution is triggered. OOS automatically records logs for the execution.
  main

• Sample uninstallation script

  #!/bin/bash
  ##### When the script starts to run, you can invoke the function to display the timestamp and the process ID. 
  function job_stop() {
      pid=$(cat /etc/aliyun/main_process_id)
      kill -9 $pid
      now=`date +'%Y-%m-%d %H:%M:%S'`
      echo "[$now][$pid] job_stop"
  }
  
  job_stop
  if [ $?  -ne 0 ]; then
      echo "[$now][$$] job stop failed."
      exit 1
  fi

On the Create Task Batch Software Management page, set the parameters as prompted and click Create.

• Set Operation to Uninstall.

• Set Extension Name to Custom Extension and select the custom extension to be uninstalled.

• Set Select Instances to Manually Select Instances and select the ECS instances on which you want to uninstall the extension.

In the Parameter Confirmation dialog box, confirm the parameters and click OK.

After the custom extension is uninstalled, you can view the uninstallation task on the Task Execution Management page.