Help Center/ Elastic Cloud Server/ API Reference/ APIs (Recommended)/ Status Management/ Reinstalling an ECS OS (Using an Image with Cloud-Init Installed)
Updated on 2022-09-26 GMT+08:00

Reinstalling an ECS OS (Using an Image with Cloud-Init Installed)

Function

This API is used to reinstall an ECS OS. During the system disk reinstallation using the original image, the data disks of the ECS remain unchanged.

After this API is called, the system uninstalls the system disk, uses the original image to create a system disk, and attaches it to the ECS. In this way, the OS is reinstalled.

Constraints

  • You can only use an image with Cloud-Init or Cloudbase-Init installed. If the image has no Cloudbase-Init or Cloudbase-init installed, use the API described in Reinstalling an ECS OS (Using an Image Without Cloud-Init Installed).
  • You are not allowed to reinstall the OS of an ECS that does not have the system disk.
  • You are not allowed to perform other operations when reinstalling the OS. Otherwise, reinstalling the OS will fail.

URI

POST /v2/{project_id}/cloudservers/{server_id}/reinstallos

Table 1 describes the parameters in the URI.
Table 1 Parameter description

Parameter

Mandatory

Description

project_id

Yes

Specifies the project ID.

For details about how to obtain the ID, see Obtaining a Project ID.

server_id

Yes

Specifies the ECS ID.

Request

Table 2 describes the request parameters.
Table 2 Request parameters

Parameter

Mandatory

Type

Description

os-reinstall

Yes

Object

Reinstalls an ECS OS. For details, see Table 3.

Table 3 os-reinstall field description

Parameter

Mandatory

Type

Description

adminpass

No

String

Specifies the initial password of the ECS administrator.

The Linux administrator username is root.

Password complexity requirements:

  • 8 to 26 characters
  • The password must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?~#*).
NOTE:
  • Linux ECSs can use user_data to inject passwords. In such a case, adminpass is unavailable.
  • Either adminpass or keyname is set.
  • If both adminpass and keyname are empty, user_data in metadata must be set.

keyname

No

String

Specifies the key pair name.

Keys can be created using the key creating API (Creating and Importing an SSH Key Pair) or obtained using the SSH key query API (Querying SSH Key Pairs).

userid

No

String

Specifies the user ID.

metadata

No

Object

Specifies metadata of the reinstalled ECS.

For more information, see Table 4.

mode

No

String

Specifies whether the ECS supports OS reinstallation when the ECS is running.

If the parameter value is withStopServer, the ECS supports OS reinstallation when the ECS is running. In such a case, the system automatically stops the ECS before reinstalling its OS.

Table 4 metadata field description

Parameter

Mandatory

Type

Description

user_data

No

String

Specifies the user data to be injected to the ECS during the creation. Text and text files can be injected.

NOTE:
  • The content of user_data must be encoded with base64.
  • The maximum size of the content to be injected (before encoding) is 32 KB.

For more details, see Injecting User Data into ECSs.

Examples

Before base64 encoding:

  • Linux
    #! /bin/bash
    echo user_test >> /home/user.txt

After base64 encoding:

  • Linux
    IyEgL2Jpbi9iYXNoDQplY2hvIHVzZXJfdGVzdCAmZ3Q7Jmd0OyAvaG9tZS91c2VyLnR4dA==

Response

See Responses (Task).

Example Request

  • Example URL request
    POST https://{endpoint}/v2/{project_id}/cloudservers/{server_id}/reinstallos
  • Example request 1 (using a password to remotely log in to an ECS with OS reinstalled)
    {
        "os-reinstall": {
            "adminpass": "!QAZxsw2", 
            "userid": "7e25b1da389f4697a79df3a0e5bd494e",
            "mode": "withStopServer"
        }
    }
  • Example request 2 (using a key to remotely log in to an ECS with OS reinstalled)
    {
        "os-reinstall": {
            "keyname": "KeyPair-350b", 
            "userid": "7e25b1da389f4697a79df3a0e5bd494e"
        }
    }

Example Response

See Responses (Task).

{      
    "job_id": "70a599e0-31e7-49b7-b260-868f441e862b" 
}

Error Codes

See Error Codes.