From 7b86b0e1987eb014f52a6c4fd35f3a65dd05062d Mon Sep 17 00:00:00 2001 From: Jan Siwiec <jan.siwiec@vsb.cz> Date: Thu, 30 Mar 2023 09:50:40 +0200 Subject: [PATCH] proofread --- .../docs/additional-information/storage-capabilities.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/topics/compute/openstack/docs/additional-information/storage-capabilities.md b/topics/compute/openstack/docs/additional-information/storage-capabilities.md index dc1f93cb..63c17be5 100644 --- a/topics/compute/openstack/docs/additional-information/storage-capabilities.md +++ b/topics/compute/openstack/docs/additional-information/storage-capabilities.md @@ -11,6 +11,6 @@ Default MetaCentrum Cloud storage is implemented via the CEPH storage cluster de For instances, that require high throughput and IOPS, it is possible to utilize hypervisor local SSDs. Requirements for instances on hypervisor local SSD: * instances can be deployed only via API (CLI, Ansible, Terraform ...), instances deployed via web GUI (Horizon) will always use CEPH for its storage -* supported only by flavors with ssd-ephem suffix (e.g. hpc.4core-16ram-ssd-ephem) +* supported only by flavors with the `ssd-ephem` suffix (e.g. `hpc.4core-16ram-ssd-ephem`) * instances can be rebooted without prior notice or you can be required to delete them * you can request them when asking for a new project, or an existing project on cloud@metacentrum.cz -- GitLab