Skip to content

Commit 1c4d948

Browse files
add onboarding for SCS Hardware Landscape
Signed-off-by: Marvin Frommhold <[email protected]>
1 parent 3870e8a commit 1c4d948

File tree

3 files changed

+65
-3
lines changed

3 files changed

+65
-3
lines changed

community/cloud-resources/cloud-resources.md

Lines changed: 38 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,44 @@ This document gives an overview of the test and development cloud resources curr
44

55
## How to request cloud resources
66

7-
To request access to an existing project, please contact the responsible community member. To apply for a new project, please create a pull request against this document (leave `Unique Identifier` blank) and assign it to the particular CSP team (e.g. @SovereignCloudStack/plusserver, @SovereignCloudStack/wavecon, ...)
7+
To request access to an existing project, please contact the responsible community member as described below.
88

9-
## plusserver (SCS2)
9+
## SCS Hardware Landscape
10+
11+
For access to the SCS Hardware Landscape, please send an email to the [SCS Project Board](https://docs.scs.community/community/governance/project-board) at [[email protected]](mailto:[email protected]).
12+
Please note that the email address you provide will also be used for your login details and further communication.
13+
The email should contain the following information:
14+
15+
- link to PR for [SSH access](#ssh-access)
16+
- OPTIONAL: if needed, information about the SSH key to be used
17+
- link to PR for [VPN access](#vpn-access)
18+
19+
### SSH Access
20+
21+
To request SSH access, [create a PR by following the steps 1 and 2](https://github.com/SovereignCloudStack/hardware-landscape/blob/main/documentation/System_Runbooks.md#manage-ssh-access-and-adminstrative-permissions).
22+
Assign the PR to the members of the SCS Project Board.
23+
Please note to specify your GitHub handle and that your GitHub SSH key (`https://github.com/<GITHUB_HANDLE>.keys`) will be used by default unless otherwise specified in your initial email request.
24+
Once the PR has been accepted, [configure your SSH access](https://github.com/SovereignCloudStack/hardware-landscape/blob/main/documentation/System_Usage.md#configure-ssh-access).
25+
26+
### VPN Access
27+
28+
To request VPN access, [create a PR by following the steps 1 to 3](https://github.com/SovereignCloudStack/hardware-landscape/blob/main/documentation/System_Usage.md#configure-vpn-access).
29+
Assign the PR to the members of the SCS Project Board.
30+
Once the PR has been accepted, [configure your VPN access by following the steps 5 to 7](https://github.com/SovereignCloudStack/hardware-landscape/blob/main/documentation/System_Usage.md#configure-vpn-access).
31+
32+
### SCS Hardware Landscape Usage
33+
34+
More information on how to use the Hardware Landscape can be found [here](hardware-landscape.md).
35+
36+
## SCS2 @ plusserver
1037

1138
SCS2 is the successor to gx-scs (or SCS1), which no longer exists.
1239

40+
To apply for a new project, please create a pull request against this document (leave `Unique Identifier` blank) and assign it to the CSP team @SovereignCloudStack/plusserver.
41+
1342
### SCS2 Usage
1443

15-
A brief guide on how to use the resources provided by plusserver GmbH can be found [here](plusserver-gx-scs.md)
44+
A brief guide on how to use the resources provided by plusserver GmbH can be found [here](plusserver-gx-scs.md).
1645

1746
### SCS2 Users
1847

@@ -65,6 +94,12 @@ Service users will have their default_project_id set to a specific project and w
6594

6695
## Wavecon
6796

97+
To apply for a new project, please create a pull request against this document (leave `Unique Identifier` blank) and assign it to the CSP team @SovereignCloudStack/wavecon.
98+
99+
### Wavestack Usage
100+
101+
A brief guide on how to use the resources provided by Wavecon GmbH can be found [here](wavestack.md).
102+
68103
### Wavestack Service Users
69104

70105
| Unique Identifier | Service User Name | Full Access on | Community Contact | Description | Needed until |
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
title: Getting Started with SCS Hardware Landscape
3+
version: 2025-12-19
4+
author: Marvin Frommhold
5+
---
6+
7+
## Getting Started with the SCS Hardware Landscape
8+
9+
The SCS Hardware Landscape is a publicly accessible training and demonstration environment of the SCS reference implementation on hardware operated by the Forum SCS-Standards.
10+
Interested parties, for example customers who want to test their software for SCS compatibility, can get access to it.
11+
It is currently running at a colocation of ScaleUp Technologies.
12+
13+
### URLs for accessing the SCS Hardware Landscape
14+
15+
- UI (horizon): [https://api.dc1.muc.cloud.cnds.io/project/](https://api.dc1.muc.cloud.cnds.io/project/)
16+
- API auth URL: [https://api.dc1.muc.cloud.cnds.io:5000/](https://api.dc1.muc.cloud.cnds.io:5000/)
17+
- Object Storage endpoint: [https://api.dc1.muc.cloud.cnds.io:8080/](https://api.dc1.muc.cloud.cnds.io:8080/)
18+
- DNS Management: [https://portal.cnds.io/](https://portal.cnds.io/)
19+
20+
### Authentication (UI)
21+
22+
For the login you will need your email address you provided to the Project Board and your password.
23+
24+
### Documentation of the SCS Hardware Landscape
25+
26+
A brief documentation of the SCS Hardware Landscape can be found on the ["Hardware-Landscape turnkey solution page"](https://docs.scs.community/docs/turnkey-solution/hardware-landscape) and in the [SCS Hardware Landscape repository](https://github.com/SovereignCloudStack/hardware-landscape).

sidebarsCommunity.js

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,7 @@ const sidebars = {
6464
items: [
6565
'cloud-resources/cloud-resources',
6666
'cloud-resources/getting-started-openstack',
67+
'cloud-resources/hardware-landscape',
6768
'cloud-resources/plusserver-gx-scs',
6869
'cloud-resources/wavestack'
6970
]

0 commit comments

Comments
 (0)