Skip to content

Commit 3411f7e

Browse files
nmelehan-akamainmelehanjddocs
authored
AWS and GCP block storage migration guides (#7210)
* GCP and AWS Block Storage migration guides * GCP and AWS Block Storage migration guides * GCP and AWS Block Storage migration guides * copy edit * Vale fix * diagram fix * frontmatter fix * Vale fix * Vale fix * Diagram fixes --------- Co-authored-by: Nathan Melehan <[email protected]> Co-authored-by: jddocs <[email protected]>
1 parent b04871d commit 3411f7e

File tree

8 files changed

+1105
-183
lines changed

8 files changed

+1105
-183
lines changed

ci/vale/dictionary.txt

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1022,6 +1022,8 @@ hybla
10221022
Hydrolix
10231023
hykes
10241024
hypercorn
1025+
Hyperdisk
1026+
Hyperdisks
10251027
hyperefficient
10261028
HyperLogLog
10271029
hyperparameter

docs/guides/applications/containers/build-a-cloud-native-private-registry-with-quay/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ keywords: ['build cloud-native container registry with quay','red hat quay','cen
99
license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
1010
---
1111

12-
Docker doesn’t provide long term storage or image distribution capabilities, so developers need something more. [Docker Registry](https://docs.docker.com/registry/) performs these tasks, and using it guarantees the same application runtime environment through virtualization. However, building an image can involve a significant time investment, which is where [Quay](https://www.redhat.com/en/resources/quay-datasheet) (pronounced *kway*) comes in. A registry like Quay can both build and store containers. You can then deploy these containers in a shorter time and with less effort than using Docker Registry. This guide explains how Quay can be an essential part of the development process and details how to deploy a Quay registry.
12+
Docker doesn’t provide long term storage or image distribution capabilities, so developers need something more. [Docker Registry](https://docs.docker.com/registry/) performs these tasks, and using it guarantees the same application runtime environment through virtualization. However, building an image can involve a significant time investment, which is where [Quay](https://www.redhat.com/en/resources/quay-datasheet) comes in. A registry like Quay can both build and store containers. You can then deploy these containers in a shorter time and with less effort than using Docker Registry. This guide explains how Quay can be an essential part of the development process and details how to deploy a Quay registry.
1313

1414
## What is Red Hat Quay?
1515

docs/guides/platform/migrate-to-linode/migrate-from-aws-ebs-to-linode-block-storage/aws-block-storage-migration-workflow.svg

Lines changed: 164 additions & 0 deletions
Loading

docs/guides/platform/migrate-to-linode/migrate-from-aws-ebs-to-linode-block-storage/index.md

Lines changed: 285 additions & 0 deletions
Large diffs are not rendered by default.

docs/guides/platform/migrate-to-linode/migrate-from-azure-disk-storage-to-linode-block-storage/azure-block-storage-migration-workflow.svg

Lines changed: 176 additions & 177 deletions
Loading

docs/guides/platform/migrate-to-linode/migrate-from-azure-disk-storage-to-linode-block-storage/index.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,11 @@
11
---
22
slug: migrate-from-azure-disk-storage-to-linode-block-storage
33
title: "Migrate From Azure Disk Storage to Linode Block Storage"
4-
description: "Two to three sentences describing your guide."
5-
og_description: "Optional two to three sentences describing your guide when shared on social media. If omitted, the `description` parameter is used within social links."
4+
description: "Learn how to migrate data from an Azure Disk Storage managed disk to a Linode Block Storage Volume."
65
authors: ["Leon Yen","Nathan Melehan"]
76
contributors: ["Leon Yen","Nathan Melehan"]
87
published: 2024-11-18
9-
keywords: ['list','of','keywords','and key phrases']
8+
keywords: ['migrate','azure disk storage','linode block storage']
109
license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
1110
---
1211

@@ -20,8 +19,7 @@ This guide describes the process of migrating a single volume from Azure Disk St
2019

2120
2. The Azure VM sends data on the Azure data disk to a Block Storage Volume attached to the Linode instance via an established rsync connection.
2221

23-
2a. Egress costs for the migrated data are measured when the data leaves the Azure platform. These costs are billed by Azure.
24-
22+
1. Egress costs for the migrated data are measured when the data leaves the Azure platform. These costs are billed by Azure.
2523
{#azure-linode-bs-migration .large-diagram}
2624

2725
## Linode Block Storage vs. Azure Disk Storage

docs/guides/platform/migrate-to-linode/migrate-from-gcp-hyperdisk-and-persistent-disk-to-linode-block-storage/gcp-block-storage-migration-workflow.svg

Lines changed: 191 additions & 0 deletions
Loading

docs/guides/platform/migrate-to-linode/migrate-from-gcp-hyperdisk-and-persistent-disk-to-linode-block-storage/index.md

Lines changed: 283 additions & 0 deletions
Large diffs are not rendered by default.

0 commit comments

Comments
 (0)