-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add guide on how to migrate from quobyte to ceph
- Loading branch information
Zaid Abu-Tarboush
committed
Nov 28, 2024
1 parent
5c0fd7f
commit c35ecfd
Showing
1 changed file
with
69 additions
and
0 deletions.
There are no files selected for viewing
69 changes: 69 additions & 0 deletions
69
user/pages/03.Howtos/16.migrate-quobyte-to-ceph/docs.en.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,69 @@ | ||
--- | ||
title: 'How to Migrate From Quobyte to Ceph Storage' | ||
date: '28-11-2024 02:48' | ||
taxonomy: | ||
category: | ||
- docs | ||
--- | ||
|
||
## Overview | ||
In this guide we will provide a way to migrate your VMs with ephemeral storage, block storage, and object storage. | ||
|
||
## Compute Workloads (VM flavor and ephemeral storage) | ||
Migrating a VM from Quobyte to Ceph storage means moving from *m1* to *m2* flavor. To do that, you need to create an image of the VM with ephemeral storage and then create a new VM based on the that image. | ||
|
||
Create an image: | ||
```shell | ||
openstack server image create <server> --name <target-image-name> | ||
``` | ||
|
||
Wait until the image reaches an active state: | ||
```shell | ||
openstack image show <target-image> -c status | ||
``` | ||
|
||
Create a new VM with an *m2* flavor based on the created image: | ||
```shell | ||
openstack server create <server-name> --image <image> --flavor m2.<size> | ||
``` | ||
|
||
If the old and new VMs are not in the same region, you will need to download the created image and upload it to the new region: | ||
```shell | ||
openstack --os-region <source-region> image save <image> --file <filename> | ||
openstack --os-region <target-region> image create <image-name> --file <filename> | ||
|
||
``` | ||
|
||
|
||
## Block Storage Volumes | ||
Block storage volumes can also be migrated by creating an image of the existing one and then creating a new volume based on that image. | ||
|
||
Create an image: | ||
```shell | ||
openstack image create <target-image-name> --volume <volume> | ||
|
||
``` | ||
|
||
Wait until the image reaches an active state: | ||
```shell | ||
openstack image show <target-image> -c status | ||
|
||
``` | ||
|
||
Create a new volume based on the created image and make sure you specify the volume type as `ceph`: | ||
```shell | ||
openstack volume create <name> --image <image> --type ceph --size <size> | ||
``` | ||
|
||
If the old and new volumes are not in the same region, you will need to download the created image and upload it to the new region: | ||
```shell | ||
openstack --os-region <source-region> image save <image> --file <filename> | ||
openstack --os-region <target-region> image create <image-name> --file <filename> | ||
|
||
``` | ||
|
||
|
||
## Object Storage | ||
For Quobyte-based object storage (s3._REGION_.cloud.syseleven.net) and ceph-based (objectstorage.fes.cloud.syseleven.net) the same access/secret key pair can be used. | ||
|
||
There are no special tools available to move/copy buckets or partial content internally between two object storage clusters. You will need to download the content and upload it again with your choice of tools. |