osc compute server rebuild254

Rebuild Server (rebuild Action) (microversion = 2.54)

Usage: osc compute server rebuild254 [OPTIONS] --image-ref <IMAGE_REF> <ID>

Arguments:

  • <ID> — id parameter for /v2.1/servers/{id}/action API

Options:

  • --access-ipv4 <ACCESS_IPV4> — IPv4 address that should be used to access this server

  • --access-ipv6 <ACCESS_IPV6> — IPv6 address that should be used to access this server

  • --admin-pass <ADMIN_PASS> — The administrative password of the server. If you omit this parameter, the operation generates a new password

  • --description <DESCRIPTION> — A free form description of the server. Limited to 255 characters in length. Before microversion 2.19 this was set to the server name.

    New in version 2.19

  • --image-ref <IMAGE_REF> — The UUID of the image to rebuild for your server instance. It must be a valid UUID otherwise API will return 400. To rebuild a volume-backed server with a new image, at least microversion 2.93 needs to be provided in the request else the request will fall back to old behaviour i.e. the API will return 400 (for an image different from the image used when creating the volume). For non-volume-backed servers, specifying a new image will result in validating that the image is acceptable for the current compute host on which the server exists. If the new image is not valid, the server will go into ERROR status

  • --key-name <KEY_NAME> — Key pair name for rebuild API. If null is specified, the existing keypair is unset.

    Note

    Users within the same project are able to rebuild other user’s instances in that project with a new keypair. Keys are owned by users (which is the only resource that’s true of). Servers are owned by projects. Because of this a rebuild with a key_name is looking up the keypair by the user calling rebuild.

    New in version 2.54

  • --metadata <key=value> — Metadata key and value pairs. The maximum size of the metadata key and value is 255 bytes each

  • --name <NAME> — The server name

  • --os-dcf-disk-config <OS_DCF_DISK_CONFIG> — Controls how the API partitions the disk when you create, rebuild, or resize servers. A server inherits the OS-DCF:diskConfig value from the image from which it was created, and an image inherits the OS-DCF:diskConfig value from the server from which it was created. To override the inherited setting, you can include this attribute in the request body of a server create, rebuild, or resize request. If the OS-DCF:diskConfig value for an image is MANUAL, you cannot create a server from that image and set its OS-DCF:diskConfig value to AUTO. A valid value is:

    • AUTO. The API builds the server with a single partition the size of the target flavor disk. The API automatically adjusts the file system to fit the entire partition. - MANUAL. The API builds the server by using whatever partition scheme and file system is in the source image. If the target flavor disk is larger, the API does not partition the remaining disk space.

    Possible values: auto, manual

  • --personality <JSON> — The file path and contents, text only, to inject into the server at launch. The maximum size of the file path data is 255 bytes. The maximum limit is the number of allowed bytes in the decoded, rather than encoded, data.

    Available until version 2.56

  • --preserve-ephemeral <PRESERVE_EPHEMERAL> — Indicates whether the server is rebuilt with the preservation of the ephemeral partition (true).

    Note

    This only works with baremetal servers provided by Ironic. Passing it to any other server instance results in a fault and will prevent the rebuild from happening.

    Possible values: true, false