Skip to content
Snippets Groups Projects
Commit 422bc3bc authored by Uwe Jandt (DESY, HIFIS)'s avatar Uwe Jandt (DESY, HIFIS)
Browse files

Minor spelling corrections

parent 45e07ccc
No related branches found
No related tags found
1 merge request!3928-Helmholtz Cloud Announcement
...@@ -14,23 +14,24 @@ The upcoming Helmholtz Cloud will initially consist of approximately 20 of 25 se ...@@ -14,23 +14,24 @@ The upcoming Helmholtz Cloud will initially consist of approximately 20 of 25 se
#### How can I access it? And when? #### How can I access it? And when?
It is the purpose of HIFIS to allow a common, harmonized access to Helmholtz Cloud services via It is the purpose of HIFIS to allow a common, harmonized access to Helmholtz Cloud services via
a single portal -- the Cloud Access Layer: a single portal -- the Cloud Access Layer --
and Single-Sign-On (SSO). and Single-Sign-On (SSO).
The initial set of services as well as the first version of the access layer is scheduled to be available by the end of 2020. The initial set of services as well as the first version of the access layer is scheduled to be available by the end of 2020.
[**See also our roadmap**](roadmap). [**Have a look at our roadmap!**](roadmap).
#### What are the plans for the Cloud Access Layer? #### What are the plans for the Cloud Access Layer?
The initial version of the Cloud Access Layer is planned to be kept simple while at the same time incorporating one of the most important features, the single-sign on functionality. Further functionality of the first version includes The initial version of the Cloud Access Layer is planned to be kept simple while at the same time incorporating one of the most important features, the single-sign on (SSO) functionality.
* list of services Further functionality of the first version includes:
* detail view for services * List of services;
* possibility to access a service via a link * Detailed view for services;
* indication of service status * Possibility to access a service via a link;
* Indication of service status.
Later versions will contain more enhanced features like Later versions will contain more enhanced features like:
* personal workspace with overview about the personal set of services * Personal workspace with overview about the personal set of services;
* possibility to request more specific setup of services * Possibility to request more specific setup of services;
* creation of meta services, e.g. combination of JupyterLab with HPC resources and a storage service * Creation of meta services, e.g. combination of JupyterLab with HPC resources and a storage service.
If you have suggestions about additional use cases and functionality, please feel free to contact us. We appreciate all input from the user community! If you have suggestions about additional use cases and functionality, please feel free to contact us. We appreciate all input from the user community!
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment