Expert Mode: Launching Instances Using Cockpit

Using Cockpit, you can launch one or more fully custom instances in the public Cloud or in a Virtual Private Cloud (VPC).

The Basic, Advanced and Expert Modes enable you to define different attributes of the instances, but only the Expert Mode enables you to launch several instances in the same launch request. These instances are grouped within a same reservation.

Launching Instances Using Cockpit v1

Open the Create Instance Window

  1. Click Compute > Instances.

  2. Click Create > Expert Mode.
    The CREATE INSTANCE window appears.

    You can also click the OMI from which you want to launch instances in the Outscale Machine Images page, and then click Create Instance . The CREATE INSTANCE window appears with the selected OMI.

Configure Your Instance

Choose a Name, Tenancy Option, and Shutdown Behavior

  1. (optional) In the Instance name field, type a name for your instances.

    This name must contain between 1 and 255 ASCII printable characters.

    This name is used as a tag associated with your instance.

  2. (optional) Check the Tenancy box to launch dedicated instances.
    For more information, see About Instances.

  3. (optional) Select one of the following values from the Shutdown behavior option list:

    • Stop: When you initiate shutdown, the instances stop.

    • Terminate: When you initiate shutdown, the instances stop and are terminated.

    • Restart: When you initiate shutdown, the instances stop then automatically restart.

  4. Click Next.
    The OMI selection screen appears.

Choose an OMI

  1. Select an OMI for your instances.

  2. Click Next.
    The Instance type selection screen appears.

Choose an Instance Type and the Number of Instances

  1. In the OUTSCALE Instance Type section, specify the following attributes for your instances:

    • CPU: The processor generation.

    • Performance: The performance flag.

      • Highest Performance: Provides maximum compute capacity on all the cores of the VM. This option is ideal for intensive compute applications.

      • High Performance: Provides high compute capacity on all the cores of the VM. This option offers small performance variability and applies to most cases.

      • Medium Performance: Provides performance with significant variability on all the cores of the VM. This option does not guarantee consistent performance, but is ideal for machines with low CPU demand.

    • Core(s): The number of vCores, up to 78.

    • Memory (GiB): The amount of memory, up to 1039 GiB.

    For more information about instance types, see Instance Types.

    To function properly, Windows instances require at least a v3 processor generation, 2 vCores, and 4 GiB of memory.

  2. In the Number of Instances section, specify the number of instances you want to launch.

    You can launch up to 20 instances at a time.

  3. Click Next.
    The VPC screen appears.

Choose the Public Cloud or a VPC and an AZ

  1. If you want to launch instances in the public Cloud:

    1. Leave No VPC selected.

    2. Select the AZ where you want to launch your instances.

      When launching instances in the public Cloud, you cannot define the private IP of the instances.

  2. If you want to launch instances in a VPC:

    1. Select a VPC.

    2. Select one of the subnets of the VPC.

    3. (optional) In the Private IP field, if you are launching one instance only, type the private IP for the instance, within the IP range of the subnet.

      When you launch instances in a VPC using the Expert mode:

      • Only the AZ of the chosen subnet is listed.

      • Flexible network interfaces (FNIs) are automatically created and attached to the instances.

  3. Click Next.
    The Security group screen appears.

Choose Security Groups

  1. If you want to assign one or more existing security groups to your instances, select them from the list.

    This list depends on the choice you made in the Public/Private Cloud screen. If you chose a VPC, only the security groups of the chosen VPC are listed.

  2. To create a new security group to assign to the instances:

    1. In the Name field of the New Security Group section, type a name for the security group.

    2. In the Description field, type its description.

      • The name must be unique in your account for the public Cloud or for each VPC.

      • The name of the security group must not start with sg-.

      • Each name and description can contain between 1 and 255 characters. Allowed characters are a-z, A-Z, 0-9, spaces, and _.-:/()#,@[]+=&;\{}!$*.

  3. Click Next.
    The Keypair screen appears.

    If you do not choose any security group, the default security group of the account or VPC is assigned to the instances.

Choose a Keypair

  1. If you want to assign an existing keypair to your instances, select it from the list.

    If you have set a default keypair in the Settings page of Cockpit, it is pre-selected.

  2. If you want to create a new keypair to assign to your instances, type a name for the keypair in the Name field of the New Keypair section.

  3. Click Next.
    The User Data screen appears.

    In Expert Mode, you can launch an instance without assigning any keypair to it. However, all official OMIs use keypairs as their authentication system. Therefore, if you want to be able to access an instance launched from an official OMI, you need to assign it a keypair either during this step or later. To assign a keypair later, see Modifying an Instance Attribute.

Specify User Data

  1. (optional) Type user data for the instances in the User Data fields.
    For more information, see Configuring an Instance with User Data and OUTSCALE Tags.

    Cockpit then encodes this user data to Base64. The maximum size for the Base64-encoded user data is 500 kibibytes (KiB).

  2. Click Next.
    The Summary screen appears.

Confirm the Launch

  1. Review the settings you have specified for the instances.

  2. Click Create to validate.
    The instances are launched.

    If you have created a keypair, you are prompted to download a file containing the private key of the keypair. Save this file carefully, as it is required to connect to your instances. 3DS OUTSCALE cannot provide any copy in case of loss.

Launching VMs Using Cockpit v2-beta

Open the Create VMs Window

In the VMs dashboard, click IconAddFull Create VMs.
The CREATE VMs - EXPERT MODE window appears.

Configure Your VM

Choose a Name, Tenancy Option, and Shutdown Behavior

  1. (optional) In the VM name field, type a name for your VMs.

    This name must contain between 1 and 255 ASCII printable characters.

    This name is used as a tag associated with your VM.

  2. (optional) Check the Dedicated box to launch dedicated VMs.
    For more information, see About Instances.

  3. (optional) Select one of the following values from the Shutdown behavior option list:

    • Stop: When you initiate shutdown, the VMs stop.

    • Delete: When you initiate shutdown, the VMs stop and are deleted.

    • Restart: When you initiate shutdown, the VMs stop then automatically restart.

  4. Click Next.
    The Image selection screen appears.

Choose an Image

  1. Select an image for your VMs.

  2. Click Next.
    The VM Type selection screen appears.

Choose a VM Type and the Number of VMs

  1. Specify the following attributes for your VMs:

    • CPU generation: The processor generation.

    • Performance: The performance flag.

      • Highest Performance: Provides maximum compute capacity on all the cores of the VM. This option is ideal for intensive compute applications.

      • High Performance: Provides high compute capacity on all the cores of the VM. This option offers small performance variability and applies to most cases.

      • Medium Performance: Provides performance with significant variability on all the cores of the VM. This option does not guarantee consistent performance, but is ideal for machines with low CPU demand.

    • Core(s): The number of vCores, up to 78.

    • Memory (GiB): The amount of memory, up to 1039 GiB.

    For more information about VM types, see Instance Types.

    To function properly, Windows VMs require at least a v3 processor generation, 2 vCores, and 4 GiB of memory.

  2. Specify the number of VMs you want to launch.

    You can launch up to 20 instances at a time.

  3. Click Next.
    The Net screen appears.

Choose the Public Cloud or a Net and a Subregion

  1. If you want to launch VMs in the public Cloud:

    1. Leave the Public Cloud switch on.

    2. Select the Subregion where you want to launch your VMs.

      When launching VMs in the public Cloud, you cannot define the private IP of the VMs.

  2. If you want to launch VMs in a Net:

    1. Switch off Public Cloud.

    2. Select one of your Subnets in the Subnet list.

    3. (optional) In the Private IP field, if you are launching one VM only, type the private IP address for the VM, within the IP address range of the subnet.

      When you launch VMs in a Net using the Expert mode:

      • Only the Subregion of the chosen subnet is listed.

      • Network interface cards (NICs) are automatically created and attached to the VMs.

  3. Click Next.
    The Root Volume screen appears.

Choose a Root Volume

  1. If you want your VMs to use a default root volume:

    1. Select Proceed with a default root volume.

    2. (optional) In the Volume Name field, type a name for your root volume.

  2. If you want to customize the root volume of your VMs:

    1. Select Customize the root volume.

    2. (optional) In the Volume Name field, type a name for your root volume.

    3. Select one of the following values from the Volume Type option list:

      • standard for a Magnetic volume

      • gp2 for a Performance volume

      • io1 for an Enterprise volume

        If you select io1, you have to set the number of IOPS you need.

        For more information, see About Volumes > Volume Types and IOPS.

    4. In the Volume Size field, specify the size of the volume (in GiB).

  3. Click Next.
    The Security group screen appears.

Choose Security Groups

  1. If you want to assign a default security group to your VMs, select Proceed with a default security group.

  2. If you want to assign one or more existing security groups to your VMs, select Select one or more existing security groups and select them from the list that appears.

    This list depends on the choice you made in the Public Cloud/Net screen. If you chose a Net, only the security groups of the chosen Net are listed.

  3. If you want to assign a new security group to your VMs, select Create a new security group:

    1. In the Name field, type a name for the security group.

    2. In the Description field, type its description.

      • The name must be unique in your account for the public Cloud or for each Net.

      • The name of the security group must not start with sg-.

      • Each name and description can contain between 1 and 255 characters. Allowed characters are a-z, A-Z, 0-9, spaces, and _.-:/()#,@[]+=&;\{}!$*.

  4. Click Next.
    The Keypair screen appears.

Choose a Keypair

  1. If you want to assign an existing keypair to your VMs, select it from the list.

  2. If you want to create a new keypair to assign to your VMs, select Create a new keypair:

    1. In the Keypair name field, type a name for the keypair.

    2. Click Create and download keypair.

      Once you have downloaded the file containing the private key of the keypair, save it carefully, as it is required to connect to your VMs. 3DS OUTSCALE cannot provide any copy in case of loss.

  3. If you do not want to assign a keypair to your VMs, select Proceed without a keypair.

    In Expert Mode, you can launch a VM without assigning any keypair to it. However, all official images use keypairs as their authentication system. Therefore, if you want to be able to access a VM launched from an official image, you need to assign it a keypair either during this step or later. To assign a keypair later, see Modifying an Instance Attribute.

  4. Click Next.
    The User Data screen appears.

Specify User Data

  1. (optional) Type user data for the VMs in the User Data fields.
    For more information, see Configuring an Instance with User Data and OUTSCALE Tags.

    Cockpit then encodes this user data to Base64. The maximum size for the Base64-encoded user data is 500 kibibytes (KiB).

  2. Click Next.
    The Summary screen appears.