cloud_insts_new

Create an instance with specified configuration.

How to get access:

For Linux,

• Use the user_data field to provide a cloud-init script in base64 to apply configurations to the instance.

• Specify the username and password to create a new user.

• When only password is provided, it is set as the password for the default user of the image.

• The user_data is ignored when the password is specified.

For Windows,

• Use the user_data field to provide a cloudbase-init script in base64 to create new users on Windows.

• Use the password field to set the password for the 'Admin' user on Windows.

• The password of the Admin user cannot be updated via user_data.

• The username cannot be specified in the request.

Args: project_id: Project ID

region_id: Region ID

flavor: The flavor of the instance.

interfaces: A list of network interfaces for the instance. You can create one or more interfaces - private, public, or both.

volumes: List of volumes that will be attached to the instance.

allow_app_ports: Set to true if creating the instance from an apptemplate. This allows application ports in the security group for instances created from a marketplace application template.

configuration: Parameters for the application template if creating the instance from an apptemplate.

name: Instance name.

name_template: If you want the instance name to be automatically generated based on IP addresses, you can provide a name template instead of specifying the name manually. The template should include a placeholder that will be replaced during provisioning. Supported placeholders are: {ip_octets} (last 3 octets of the IP), {two_ip_octets}, and {one_ip_octet}.

password: For Linux instances, 'username' and 'password' are used to create a new user. When only 'password' is provided, it is set as the password for the default user of the image. For Windows instances, 'username' cannot be specified. Use the 'password' field to set the password for the 'Admin' user on Windows. Use the 'user_data' field to provide a script to create new users on Windows. The password of the Admin user cannot be updated via 'user_data'.

security_groups: Specifies security group UUIDs to be applied to all instance network interfaces.

servergroup_id: Placement group ID for instance placement policy.

  Supported group types:

  - `anti-affinity`: Ensures instances are placed on different hosts for high
    availability.
  - `affinity`: Places instances on the same host for low-latency communication.
  - `soft-anti-affinity`: Tries to place instances on different hosts but allows
    sharing if needed.

ssh_key_name: Specifies the name of the SSH keypair, created via the /v1/ssh_keys endpoint.

tags: Key-value tags to associate with the resource. A tag is a key-value pair that can be associated with a resource, enabling efficient filtering and grouping for better organization and management. Some tags are read-only and cannot be modified by the user. Tags are also integrated with cost reports, allowing cost data to be filtered based on tag keys or values.

user_data: String in base64 format. For Linux instances, 'user_data' is ignored when 'password' field is provided. For Windows instances, Admin user password is set by 'password' field and cannot be updated via 'user_data'. Examples of the user_data: https://cloudinit.readthedocs.io/en/latest/topics/examples.html

username: For Linux instances, 'username' and 'password' are used to create a new user. For Windows instances, 'username' cannot be specified. Use 'password' field to set the password for the 'Admin' user on Windows.

extra_headers: Send extra headers

extra_query: Add additional query parameters to the request

extra_body: Add additional JSON properties to the request

timeout: Override the client-level default timeout for this request, in seconds

Note: Pass the numeric project_id. When a project name is provided, resolve it via cloud.projects.list/cloud.projects.get. If nothing is specified, fetch the account's default project first and use that ID. Pass the numeric region_id. Resolve region names with cloud.regions.list or cloud.regions.get. If no region is mentioned, obtain the default region ID before calling this tool.