From ab7cedc5f38e90ad8775b4b59b13f742a4830330 Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Wed, 28 Jul 2021 13:49:33 +0200
Subject: [PATCH] Move warm archive to filesystems
---
.../docs/data_lifecycle/file_systems.md | 21 +++++++++++++++++++
.../docs/data_lifecycle/warm_archive.md | 20 ------------------
doc.zih.tu-dresden.de/mkdocs.yml | 1 -
3 files changed, 21 insertions(+), 21 deletions(-)
delete mode 100644 doc.zih.tu-dresden.de/docs/data_lifecycle/warm_archive.md
diff --git a/doc.zih.tu-dresden.de/docs/data_lifecycle/file_systems.md b/doc.zih.tu-dresden.de/docs/data_lifecycle/file_systems.md
index 9f949354a..0eeefc7bc 100644
--- a/doc.zih.tu-dresden.de/docs/data_lifecycle/file_systems.md
+++ b/doc.zih.tu-dresden.de/docs/data_lifecycle/file_systems.md
@@ -102,8 +102,29 @@ directory will be distributed over 20 OSTs.
## Warm Archive
+!!! warning
+ This is under construction. The functionality is not there, yet.
+
+The warm archive is intended a storage space for the duration of a running HPC-DA project. It can
+NOT substitute a long-term archive. It consists of 20 storage nodes with a net capacity of 10 PB.
+Within Taurus (including the HPC-DA nodes), the management software "Quobyte" enables access via
+
+- native quobyte client - read-only from compute nodes, read-write
+ from login and nvme nodes
+- S3 - read-write from all nodes,
+- Cinder (from OpenStack cluster).
+
+For external access, you can use:
+
+- S3 to `<bucket>.s3.taurusexport.hrsk.tu-dresden.de`
+- or normal file transfer via our taurusexport nodes (see [DataManagement](overview.md)).
+
+An HPC-DA project can apply for storage space in the warm archive. This is limited in capacity and
+duration.
TODO
+
+
## Recommendations for File System Usage
To work as efficient as possible, consider the following points
diff --git a/doc.zih.tu-dresden.de/docs/data_lifecycle/warm_archive.md b/doc.zih.tu-dresden.de/docs/data_lifecycle/warm_archive.md
deleted file mode 100644
index c98087cc4..000000000
--- a/doc.zih.tu-dresden.de/docs/data_lifecycle/warm_archive.md
+++ /dev/null
@@ -1,20 +0,0 @@
-# Warm Archive
-
-**This page is under construction. The functionality is not there, yet.**
-
-The warm archive is intended a storage space for the duration of a running HPC-DA project. It can
-NOT substitute a long-term archive. It consists of 20 storage nodes with a net capacity of 10 PB.
-Within Taurus (including the HPC-DA nodes), the management software "Quobyte" enables access via
-
-- native quobyte client - read-only from compute nodes, read-write
- from login and nvme nodes
-- S3 - read-write from all nodes,
-- Cinder (from OpenStack cluster).
-
-For external access, you can use:
-
-- S3 to `<bucket>.s3.taurusexport.hrsk.tu-dresden.de`
-- or normal file transfer via our taurusexport nodes (see [DataManagement](overview.md)).
-
-An HPC-DA project can apply for storage space in the warm archive. This is limited in capacity and
-duration.
diff --git a/doc.zih.tu-dresden.de/mkdocs.yml b/doc.zih.tu-dresden.de/mkdocs.yml
index bc9ba2245..3a35cda61 100644
--- a/doc.zih.tu-dresden.de/mkdocs.yml
+++ b/doc.zih.tu-dresden.de/mkdocs.yml
@@ -78,7 +78,6 @@ nav:
- BeeGFS: data_lifecycle/bee_gfs.md
- Intermediate Archive: data_lifecycle/intermediate_archive.md
- Filesystems: data_lifecycle/file_systems.md
- - Warm Archive: data_lifecycle/warm_archive.md
- HPC Storage Concept 2019: data_lifecycle/hpc_storage_concept2019.md
- Preservation of Research Data: data_lifecycle/preservation_research_data.md
- Structuring Experiments: data_lifecycle/experiments.md
--
GitLab