Project

General

Profile

Actions

Feature #10768

closed

Keep important data on volumes within OpenStack cloud

Added by Evgeny Novikov 10 months ago. Updated 7 months ago.

Status:
Closed
Priority:
High
Category:
Deployment
Target version:
Start date:
03/25/2021
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

At the moment all Klever data is stored on an instance disk that is fast, but not reliable. It has sense to store a database and directory media to a separate, slow but reliable volume. I suggest to create and to attach volumes of 200 GB by default, but, perhaps, there may be an option to adjust the volume size.

It is important to check whether volumes will operate well after various operations with instances, especially, after resizing (#10767).

A very advanced feature that may be rather useful nevertheless is an ability to attach an existing volume to a new instance. This may be helpful, e.g. when an instance fails but the user would like to use its volume further. I am not sure that this will happen often, so, maybe it will be better to do this manually, though, this is not trivial.

Actions #1

Updated by Evgeny Novikov 10 months ago

  • Description updated (diff)
Actions #2

Updated by Ilya Shchepetkov 7 months ago

  • Status changed from New to Resolved

Implemented in the feature-10768 branch.

Currently it is not possible to attach an existing volume to a new instance: if it is important, you should create a separate issue.

Actions #3

Updated by Evgeny Novikov 7 months ago

  • Status changed from Resolved to Closed

Great! At last we will be able to sleep calmly. After some testing I merged the branch to master in 240765bd9. You can update existing instances (volumes will not be created there).

Actions

Also available in: Atom PDF