-
Notifications
You must be signed in to change notification settings - Fork 267
docs(ins): update creation funnel #5988
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Néda <[email protected]>
Co-authored-by: Néda <[email protected]>
| - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed. | ||
| - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. | ||
| - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Noble GPU OS 13 (NVIDIA)**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers. | ||
| 3. Select the desired GPU Instance type and choose and its Availability Zone in the pop-up. Click **Configure Instance** to continue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 3. Select the desired GPU Instance type and choose and its Availability Zone in the pop-up. Click **Configure Instance** to continue. | |
| 3. Select the desired GPU Instance type and choose its Availability Zone in the pop-up. Click **Configure Instance** to continue. |
| - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Noble GPU OS 13 (NVIDIA)**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers. | ||
| 3. Select the desired GPU Instance type and choose and its Availability Zone in the pop-up. Click **Configure Instance** to continue. | ||
| <Message type="tip"> | ||
| You can use the filter to find the GPU Instance type that suits best your requirements. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| You can use the filter to find the GPU Instance type that suits best your requirements. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. | |
| You can use the filter to find the GPU Instance type that best meets your requirements. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. |
| 4. Once you have completed the configuration, click on **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. | ||
| - Click **Review** to view a summary of your Instance configuration and estimated costs. | ||
|
|
||
| 5. Once you have verified the configuration of your GPU Instance, click **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 5. Once you have verified the configuration of your GPU Instance, click **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. | |
| 5. Review your GPU Instance configuration and click **Create Instance**. You will receive a notification once the Instance is ready for use. |
| - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed. | ||
| - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. | ||
| - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Noble GPU OS 13 (NVIDIA)**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers. | ||
| 3. Select the desired GPU Instance type and choose and its Availability Zone in the pop-up. Click **Configure Instance** to continue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 3. Select the desired GPU Instance type and choose and its Availability Zone in the pop-up. Click **Configure Instance** to continue. | |
| 3. Select the desired GPU Instance type and choose its Availability Zone in the pop-up. Click **Configure Instance** to continue. |
| - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Noble GPU OS 13 (NVIDIA)**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers. | ||
| 3. Select the desired GPU Instance type and choose and its Availability Zone in the pop-up. Click **Configure Instance** to continue. | ||
| <Message type="tip"> | ||
| You can use the filter to find the GPU Instance type that suits best your requirements. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| You can use the filter to find the GPU Instance type that suits best your requirements. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. | |
| You can use the filter to find the GPU Instance type that best meets your requirements. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. |
| 4. Once you have completed the configuration, click on **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. | ||
| - Click **Review** to view a summary of your Instance configuration and estimated costs. | ||
|
|
||
| 5. Once you have verified the configuration of your GPU Instance, click on **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 5. Once you have verified the configuration of your GPU Instance, click on **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. | |
| 5. Review your GPU Instance configuration and click **Create Instance**. You will receive a notification once the Instance is ready for use. |
| <Message type="tip"> | ||
| Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/instances/reference-content/choosing-instance-type/). | ||
| </Message> | ||
| 4. Select the desired Instance type and choose and Availability Zone in the pop-up. Click **Configure Instance** to continue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 4. Select the desired Instance type and choose and Availability Zone in the pop-up. Click **Configure Instance** to continue. | |
| 4. Select your desired Instance type and choose an Availability Zone in the pop-up. Click **Configure Instance** to continue. |
| - **Verify the [SSH keys](/organizations-and-projects/concepts/#ssh-key)** that will give you access to your Instance. | ||
| - **Verify the Estimated cost** of your Instance, based on the specifications you chose. | ||
| 4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready. | ||
| - (Optional) Click **+ Cloud-init** and toggle the switch to be able to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - (Optional) Click **+ Cloud-init** and toggle the switch to be able to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. | |
| - (Optional) Click **+ Cloud-init** and toggle the switch to set up a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. |
| 6. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready. | ||
|
|
||
| Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/instances/how-to/create-an-instance/), and other information, settings, and actions for the Instance. | ||
| Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/instances/how-to/connect-to-instance/), and other information, settings, and actions for the Instance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/instances/how-to/connect-to-instance/), and other information, settings, and actions for the Instance. | |
| Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see your Instance's Public IP, the SSH command to [connect to it](/instances/how-to/connect-to-instance/), and other information, settings, and actions. |
| <Message type="tip"> | ||
| Currently, only selected **General Purpose** Instances are compatible with Windows OS. | ||
| </Message> | ||
| 4. Select the desired Instance type and choose and Availability Zone in the pop-up. Click **Configure Instance** to continue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 4. Select the desired Instance type and choose and Availability Zone in the pop-up. Click **Configure Instance** to continue. | |
| 4. Select the desired Instance type and choose an Availability Zone in the pop-up. Click **Configure Instance** to continue. |
| </Message> | ||
| - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave these options at their default values. | ||
| Cloud-init scripts are the standard way to automate Instance setup, such as setting up software, users, and system configurations at the first boot. | ||
| - (Optional) Click **+ Cloud-init** and toggle the switch to be able to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - (Optional) Click **+ Cloud-init** and toggle the switch to be able to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. | |
| - (Optional) Click **+ Cloud-init** and toggle the switch to set up a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. |
| ## How to create a Linux Instance | ||
|
|
||
| 1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays. | ||
| 2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays. | |
| 2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers/create) displays. |
|
|
||
| 1. Click **CPU & GPU Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays. | ||
| 2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays. | ||
| 3. Chose an **Instance range**. You can choose from [General Purpose](/instances/reference-content/general-purpose), [Development](/instances/reference-content/development/), or [Specialized](/instances/reference-content/specialized/) Instances. Click **See Instances**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 3. Chose an **Instance range**. You can choose from [General Purpose](/instances/reference-content/general-purpose), [Development](/instances/reference-content/development/), or [Specialized](/instances/reference-content/specialized/) Instances. Click **See Instances**. | |
| 3. Choose an **Instance range** from [General Purpose](/instances/reference-content/general-purpose), [Development](/instances/reference-content/development/), or [Specialized](/instances/reference-content/specialized/) Instances. Click **See Instances**. |
| <Message type="tip"> | ||
| Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/instances/reference-content/choosing-instance-type/). | ||
| </Message> | ||
| 4. Select the desired Instance type and choose and Availability Zone in the pop-up. Click **Configure Instance** to continue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 4. Select the desired Instance type and choose and Availability Zone in the pop-up. Click **Configure Instance** to continue. | |
| 4. Select the desired Instance type and choose an Availability Zone in the pop-up. Click **Configure Instance** to continue. |
| - **Choose an Availability Zone**, which represents the geographical region where your Instance will be deployed. | ||
| - **Choose an Instance type**. <br /> | ||
| Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/instances/reference-content/choosing-instance-type/). | ||
| 3. Chose an **Instance range**. You can choose from [General Purpose](/instances/reference-content/general-purpose), [Development](/instances/reference-content/development/), or [Specialized](/instances/reference-content/specialized/) Instances. Click **See Instances**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 3. Chose an **Instance range**. You can choose from [General Purpose](/instances/reference-content/general-purpose), [Development](/instances/reference-content/development/), or [Specialized](/instances/reference-content/specialized/) Instances. Click **See Instances**. | |
| 3. Choose an **Instance range**. You can choose from [General Purpose](/instances/reference-content/general-purpose), [Development](/instances/reference-content/development/), or [Specialized](/instances/reference-content/specialized/) Instances. Click **See Instances**. |
| - Choose an **Availability Zone**, which represents the geographical region where your Instance will be deployed. | ||
| - **Choose a Windows** Instance type from the **General Purpose** range. | ||
| - **Choose a Windows Server image** to run on your Instance. | ||
| 3. Chose the **General Purpose** Instance range. Click **See Instances**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 3. Chose the **General Purpose** Instance range. Click **See Instances**. | |
| 3. Choose the **General Purpose** Instance range. Click **See Instances**. |
| - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/instances/concepts/#tags) to help you organize your Instance. | ||
| - **Choose an image** to run on your Instance. <br /> | ||
| This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/instances/reference-content/images-and-instantapps/). | ||
| - **Add volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - **Add volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed. | |
| - **Add volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block volumes, as needed. |
| - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. If needed, the boot volume can be changed after the creation of the Instance; [see how](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume). | ||
| - Booting from a volume that either lacks an OS or is among multiple volumes with identical operating systems can lead to inconsistent boot outcomes. | ||
| </Message> | ||
| - **Configure network** of the Instance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - **Configure network** of the Instance. | |
| - **Configure the network** of the Instance: |
| </Message> | ||
| - **Configure network** of the Instance. | ||
| - Leave the checkbox ticked to assign a **Public IPv4** to the Instance. You can either allocate a new IPv4 address or select one or multiple existing IPv4s. Alternatively, uncheck the box if you do not want an IPv4. | ||
| - Leave the checkbox ticked to assign a **Public IPv6** to the Instance. You can either allocate a new IPv6 address or select one or multiple existing IPv6s. Alternatively, uncheck the box if you do not want an IPv6. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - Leave the checkbox ticked to assign a **Public IPv6** to the Instance. You can either allocate a new IPv6 address or select one or multiple existing IPv6s. Alternatively, uncheck the box if you do not want an IPv6. | |
| - Leave the checkbox ticked to assign a **Public IPv6** to the Instance. You can either allocate a new IPv6 address or select one or multiple existing IPv6 addresses. Alternatively, uncheck the box if you do not want an IPv6. |
| <Message type="note"> | ||
| You can attach up to 5 IPv4 and 5 IPv6 addresses to an Instance, which is useful for running different services or applications on the same Instance. | ||
| </Message> | ||
| - (Optional) Click **+ Cloud-init** and toggle the switch to be able to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - (Optional) Click **+ Cloud-init** and toggle the switch to be able to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. | |
| - (Optional) Click **+ Cloud-init** and toggle the switch to set up a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave this option set to its default values. |
| - Click **Review** to view a summary of your Instance configuration and estimated costs. | ||
| 6. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready. | ||
|
|
||
| Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/instances/how-to/connect-to-instance/), and other information, settings, and actions for the Instance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/instances/how-to/connect-to-instance/), and other information, settings, and actions for the Instance. | |
| Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see your Instance's Public IP, the SSH command to [connect to it](/instances/how-to/connect-to-instance/), and other information, settings, and actions. |
Your checklist for this pull request
Description
Updated Instances creation funnel