Skip to content

Commit e900d5a

Browse files
authored
Merge pull request linode#2567 from Guaris/rc-v0.17
[Release] v0.17 Anais Nin
2 parents 6da8fbe + 9210509 commit e900d5a

File tree

11 files changed

+47
-22
lines changed

11 files changed

+47
-22
lines changed

docs/platform/disk-images/copying-a-disk-image-over-ssh/index.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,6 @@ description: "Create a disk image using dd and download it to another machine ov
66
keywords: ["copy", "disk", "ssh", "dd"]
77
license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
88
aliases: ['migration/ssh-copy/','migrate-to-linode/disk-images/copying-a-disk-image-over-ssh/','platform/disk-images/copying-a-disk-image-over-ssh/']
9-
modified: 2019-01-14
109
modified_by:
1110
name: Linode
1211
published: 2012-06-04
@@ -19,13 +18,17 @@ Piping SSH commands to utilities such as `dd`, `gzip`, or `rsync` is an easy way
1918

2019
This guide demonstrates how to download a `.img` file to your computer over SSH containing a block-level copy of your Linode's disk device created with `dd`.
2120

21+
{{< note >}}
22+
If the amount of data on your disk is much less than the size of the disk, then downloading a copy with `dd` can take longer than just downloading your files. If you're interested in downloading individual files or directories, review the options listed in our [Download Files from Your Linode](/docs/security/data-portability/download-files-from-your-linode/) and [Backing Up Your Data](/docs/security/backups/backing-up-your-data/) guides.
23+
{{< /note >}}
24+
2225
## Download a Disk over SSH
2326

2427
### Boot into Rescue Mode
2528

2629
1. Prepare the receiving computer by verifying that SSH is installed. Most Linux/Unix-like systems include OpenSSH in their package base by default. If the receiving system is Microsoft Windows, there are multiple SSH solutions available such as [Cygwin and PuTTY](/docs/networking/ssh/using-ssh-on-windows).
2730

28-
1. Reboot Your Linode into [rescue mode](/docs/troubleshooting/rescue-and-rebuild/#booting-into-rescue-mode) and connect to it using [Lish](/docs/platform/manager/remote-access/#console-access).
31+
1. Reboot Your Linode into [Rescue Mode](/docs/troubleshooting/rescue-and-rebuild/#booting-into-rescue-mode) and connect to it using [Lish](/docs/platform/manager/remote-access/#console-access).
2932

3033
1. Set a root password for the rescue system and start the SSH server:
3134

@@ -100,7 +103,7 @@ You may want to upload your disk image to a new server. For example, if you prev
100103

101104
1. Now use the remaining disk space to create the system drive you'll copy your disk image to. Enter a descriptive name in the **Label** field, and be sure the **Size** is large enough to hold the contents of the disk you are uploading. Click **Save Changes**.
102105

103-
1. Reboot Your Linode into [rescue mode](#boot-into-rescue-mode) and start the SSH server as described above.
106+
1. Reboot Your Linode into [Rescue Mode](#boot-into-rescue-mode) and start the SSH server as described above.
104107

105108
1. Upload the disk over SSH to the Linode. Replace `192.0.2.9` with the Linode's IP address and `/home/archive/linode.img` with the disk images's path.
106109

@@ -137,7 +140,7 @@ You can check if this is necessary by comparing the space of the filesystem to t
137140

138141
In the above example, the values in the **Size** column don't match. Although the disk is 30 GB, the filesystem can only see 24 GB.
139142

140-
To use all available space on the new disk, execute the following from rescue mode. Replace `/dev/sdx` with your system disk's device identifier (/dev/sda, /dev/sdb, etc.).
143+
To use all available space on the new disk, execute the following from Rescue Mode. Replace `/dev/sdx` with your system disk's device identifier (/dev/sda, /dev/sdb, etc.).
141144

142145
e2fsck -f /dev/sdx
143146
resize2fs /dev/sdx

docs/platform/how-to-choose-a-linode-plan/index.md

Lines changed: 29 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,16 +3,16 @@ author:
33
name: Linode
44
email: docs@linode.com
55
description: 'Decide which Linode plan is right for you.'
6-
keywords: ["choose", "help", "plan", "size", "nanode", "standard", "high memory", "dedicated", "dedicated CPU"]
6+
keywords: ["choose", "help", "plan", "size", "nanode", "standard", "high memory", "dedicated", "dedicated CPU", "GPU instance"]
77
license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
8-
modified: 2019-02-04
8+
modified: 2019-06-20
99
modified_by:
1010
name: Linode
1111
published: 2019-02-04
1212
title: How to Choose a Linode Plan
1313
---
1414

15-
Linode offers four instance types: **Nanode**, **Standard**, **High Memory**, and **Dedicated CPU**. For the Standard, High Memory, and Dedicated CPU types there are several hardware resource tiers, or plans, that you can choose from.
15+
Linode offers five instance types: **Nanode**, **Standard**, **High Memory**, **Dedicated CPU**, and **GPU Instances**. For the Standard, High Memory, Dedicated CPU, and GPU Instance types, there are several hardware resource tiers, or plans, that you can choose from.
1616

1717
When selecting a plan, it is important to understand the hardware resources allocated to your instance, like CPU, transfer, storage, and RAM. An understanding of your project's own needs and requirements is also useful. This guide provides an overview of all Linode instance types and plans, their corresponding use cases, and how to choose which one is right for you.
1818

@@ -31,15 +31,15 @@ Start by reviewing what each resource means for your application. If you're conf
3131
| Storage | Your server's built-in persistent storage. Large databases, media libraries, and other stores of files will require more storage space. Your Linode's storage is maintained on high-performance SSDs for fast access. You can also supplement your Linode's disks with extra [Block Storage Volumes](https://www.linode.com/blockstorage). |
3232
| Transfer | The total amount of traffic your server can emit over the course of a month. Inbound traffic sent to your Linode does not count against your transfer quota. If you exceed your quota, your service will not be shut off; instead, an overage will be billed. Review the [Network Transfer Quota](/docs/platform/billing-and-support/network-transfer-quota/) guide for more information about how transfer works. |
3333
| Network In | The maximum bandwidth for inbound traffic sent to your Linode. The bandwidth you observe will also depend on other factors, like the geographical distance between you and your Linode and the bandwidth of your local ISP. For help with choosing a data center that will feature the lowest latency and best bandwidth, review the [How to Choose a Data Center](/docs/platform/how-to-choose-a-data-center/) guide. |
34-
| Network Out | The maximum bandwidth for outbound traffic emitted by your Linode. The bandwidth you observe will also depend on other factors, like the geographical distance between you and your Linode and the bandwidth of your local ISP. For help with choosing a data center that will feature the lowest latency and best bandwidth, review the [How to Choose a Data Center](/docs/platform/how-to-choose-a-data-center/) guide. |
35-
34+
| Network Out | The maximum bandwidth for outbound traffic emitted by your Linode. The bandwidth you observe will also depend on other factors, like the geographical distance between you and your Linode and the bandwidth of your local ISP. For help with choosing a data center that will feature the lowest latency and best bandwidth, review the [How to Choose a Data Center](/docs/platform/how-to-choose-a-data-center/) guide.
35+
| GPU | GPU's, or Graphical Processing Units are specialized hardware units only available on our GPU instances. Originally designed to manipulate computer graphics and handle image processing, GPUs are now commonly also used for many compute intensive tasks that require thousands of simultaneous threads and the higher number of logical cores that a CPU can not provide alone.
3636
## General Principles when Choosing a Plan
3737

38-
The different Linode instance types represent different balances of the above resources. Nanode and Standard instances offer a general-purpose array of resources, High Memory instances favor higher memory allocations, and Dedicated CPU instances reserve physical CPU cores for you.
38+
The different Linode instance types represent different balances of the above resources. Nanode and Standard instances offer a general-purpose array of resources, High Memory instances favor higher memory allocations, Dedicated CPU instances reserve physical CPU cores for you, and GPU instances give you access to both dedicated CPU cores and are the only plan type that gives you access to a GPU.
3939

4040
At the same time, different kinds of applications have different resource requirements. Some applications may need to store a lot of data but require less processing power, some may need more memory than CPU, and some may be especially CPU-intensive. As a result, certain instance types can better serve certain applications. When creating your instances, consider what resources your application needs and then compare it with the resources specified by each of the instance types. The following sections include common use cases for each type, and one of these may resemble your needs.
4141

42-
Finally, a common strategy when setting up a new server is to start with a smaller instance and then resize your Linode if needed. At a minimum, you will need to choose a plan that offers enough disk space to store your data. You can then [monitor](/docs/uptime/monitoring-and-maintaining-your-server-new-manager/) the CPU, memory, and network usage of your application to determine if you need more of those resources.
42+
Finally, a common strategy when setting up a new server is to start with a smaller instance and then resize your Linode if needed. At a minimum, you will need to choose a plan that offers enough disk space to store your data. You can then [monitor](/docs/uptime/monitoring-and-maintaining-your-server-new-manager/) the CPU, GPU, memory, and network usage of your application to determine if you need more of those resources.
4343

4444
## 1. Nanode
4545

@@ -150,6 +150,28 @@ Furthermore, some CPU-intensive tasks may be triggered from other events in your
150150

151151
To view a full list of the Dedicated CPU instance plans, visit the [Linode Pricing](https://www.linode.com/pricing#all) page.
152152

153+
## 5. GPU Instances
154+
155+
GPU instances are the only plan that give you access to [NVIDIA Quadro RTX 6000 GPU cards](https://www.nvidia.com/content/dam/en-zz/Solutions/design-visualization/technologies/turing-architecture/NVIDIA-Turing-Architecture-Whitepaper.pdf) with Tensor, ray tracing (RT), and CUDA cores. GPUs are designed to process large blocks of data in parallel, meaning that they are an excellent choice for any workload requiring thousands of simultaneous threads. With significantly more logical cores than a standard CPU, GPUs can perform computations that process large amounts of data in parallel more efficiently.
156+
157+
### Use Cases
158+
159+
- [Machine Learning and AI](/docs/platform/linode-gpu/why-linode-gpu/#machine-learning-and-ai)
160+
- [Big Data](/docs/platform/linode-gpu/why-linode-gpu/#big-data)
161+
- [Video Encoding](/docs/platform/linode-gpu/why-linode-gpu/#video-encoding)
162+
- [General Purpose Computing Using NVIDIA's CUDA Toolkit](/docs/platform/linode-gpu/why-linode-gpu/#general-purpose-computing-using-cuda)
163+
- [Graphics Processing](/docs/platform/linode-gpu/why-linode-gpu/#graphics-processing)
153164

165+
### Base Plan
154166

167+
| Resource | Value |
168+
| -------- | ----- |
169+
| RTX6000 GPU | 1 GPU |
170+
| RAM | 32GB |
171+
| vCPU | 8 vCPUs |
172+
| Storage | 640 GB SSD Storage |
173+
| Transfer | 16 TB |
174+
| Network In | 40 Gbps |
175+
| Network Out | 100000 Mbps |
155176

177+
To view a full list of the Dedicated CPU instance plans, visit the [Linode Pricing](https://www.linode.com/pricing#all) page.

docs/platform/object-storage/host-static-site-object-storage/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ external_resources:
1818
- '[s3cmd Sync How-To](https://s3tools.org/s3cmd-sync)'
1919
---
2020
{{< note >}}
21-
Object Storage is currently in a closed early access Beta, and you may not have access to Object Storage through the Cloud Manager or other tools. To gain access to the Early Access Program (EAP), open up a Customer Support ticket noting that you'd like to be included in the program, or e-mail objbeta@linode.com
21+
Object Storage is currently in a closed early access Beta, and you may not have access to Object Storage through the Cloud Manager or other tools. To gain access to the Early Access Program (EAP), open up a Customer Support ticket noting that you'd like to be included in the program, or e-mail objbeta@linode.com -- beta access is completely free.
2222

2323
Additionally, because Object Storage is in Beta, there may be breaking changes to how you access and manage Object Storage. This guide will be updated to reflect these changes if and when they occur.
2424
{{</ note >}}
@@ -294,4 +294,4 @@ It may take a minute or two after your s3cmd sync completes for the page to appe
294294

295295
After uploading your static site to Linode Object Storage, you may want to use a custom domain for your site. To do this, you can add a CNAME entry to your domain's DNS records that aliases it to your Object Storage bucket's website URL. To learn about managing DNS records on Linode, see the [DNS Manager](/docs/platform/manager/dns-manager/) and [DNS Records: An Introduction](/docs/networking/dns/dns-records-an-introduction/) guides.
296296

297-
As noted before, it's possible to trigger automatic deployments to the Object Storage service when you push new content updates to GitHub or GitLab. This is done by leveraging a CI/CD (continuous integration/continuous delivery) tool like [Travis CI](https://travis-ci.org). Essentially, you would build your Hugo site within the Travis environment and then run the `s3cmd sync` command from it to your bucket.
297+
As noted before, it's possible to trigger automatic deployments to the Object Storage service when you push new content updates to GitHub or GitLab. This is done by leveraging a CI/CD (continuous integration/continuous delivery) tool like [Travis CI](https://travis-ci.org). Essentially, you would build your Hugo site within the Travis environment and then run the `s3cmd sync` command from it to your bucket.

docs/platform/object-storage/how-to-use-object-storage/index.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ external_resources:
1717
---
1818

1919
{{< note >}}
20-
Object Storage is currently in a closed early access Beta, and you may not have access to Object Storage through the Cloud Manager or other tools. To gain access to the Early Access Program (EAP), open up a Customer Support ticket noting that you'd like to be included in the program, or e-mail objbeta@linode.com
20+
Object Storage is currently in a closed early access Beta, and you may not have access to Object Storage through the Cloud Manager or other tools. To gain access to the Early Access Program (EAP), open up a Customer Support ticket noting that you'd like to be included in the program, or e-mail objbeta@linode.com -- beta access is completely free.
2121

2222
Additionally, because Object Storage is in Beta, there may be breaking changes to how you access and manage Object Storage. This guide will be updated to reflect these changes if and when they occur.
2323
{{</ note >}}
@@ -60,15 +60,15 @@ Object Storage is not available in the Linode Classic Manager.
6060

6161
![Click on the 'Access Keys' tab.](object-storage-access-keys-tab.png)
6262

63-
1. The **Create an Access Key** menu will appear.
63+
2. The **Create an Access Key** menu will appear.
6464

6565
![The 'Create an Access Key' menu.](object-storage-create-key.png)
6666

67-
1. Enter a label for the key pair. This label will be how you reference your key pair in the Linode Cloud Manager. Then, click **Submit**.
67+
3. Enter a label for the key pair. This label will be how you reference your key pair in the Linode Cloud Manager. Then, click **Submit**.
6868

69-
1. A window will appear that contains your access key and your secret key. Write these down somewhere secure. The access key will be visible in the Linode Cloud Manager, but **you will not be able to retrieve your secret key again once you close the window.**
69+
4. A window will appear that contains your access key and your secret key. Write these down somewhere secure. The access key will be visible in the Linode Cloud Manager, but **you will not be able to retrieve your secret key again once you close the window.**
7070

71-
![Your access key and secret key.](object-storage-acces-keys.png)
71+
![Your access key and secret key.](object-storage-access-keys.png)
7272

7373
You now have the credentials needed to connect to Linode Object Storage.
7474

@@ -94,15 +94,15 @@ The Cloud Manager provides a web interface for creating buckets. To create a buc
9494

9595
![The Object Storage menu.](object-storage-add-a-bucket.png)
9696

97-
1. The **Create a Bucket** menu will appear.
97+
2. The **Create a Bucket** menu will appear.
9898

9999
![The Create a Bucket menu.](object-storage-create-a-bucket.png)
100100

101-
1. Add a label for your bucket. A bucket's label needs to be unique within the cluster that it lives in, and this includes buckets of the same name on different Linode accounts. If the label you enter is already in use, you will have to choose a different label.
101+
3. Add a label for your bucket. A bucket's label needs to be unique within the cluster that it lives in, and this includes buckets of the same name on different Linode accounts. If the label you enter is already in use, you will have to choose a different label.
102102

103-
1. Choose a cluster location for the bucket to reside in.
103+
4. Choose a cluster location for the bucket to reside in.
104104

105-
1. Click **Submit**. You are now ready to upload objects to your bucket using one of the other tools outlined in this guide.
105+
5. Click **Submit**. You are now ready to upload objects to your bucket using one of the other tools outlined in this guide.
106106

107107
## s3cmd
108108

95.6 KB
Loading
263 KB
Loading
114 KB
Loading
158 KB
Loading

0 commit comments

Comments
 (0)