You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: community/cloud-resources/cloud-resources.md
+34-54Lines changed: 34 additions & 54 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,97 +6,77 @@ This document gives an overview of the test and development cloud resources curr
6
6
7
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, ...)
8
8
9
-
## plusserver
9
+
## plusserver (SCS2)
10
10
11
-
### Usage
11
+
SCS2 is the successor to gx-scs (or SCS1), which no longer exists.
12
+
13
+
### SCS2 Usage
12
14
13
15
A brief guide on how to use the resources provided by plusserver GmbH can be found [here](plusserver-gx-scs.md)
14
16
15
-
### Users
17
+
### SCS2 Users
16
18
17
19
As suggested in [#155](https://github.com/SovereignCloudStack/standards/issues/155) the username for non-"service users" will contain the users github handle and are prefixed with a plusserver default.
18
20
`prefix-<$github handle>`
19
21
20
22
> **Note**
21
23
> ATM this is not directly connected to the SovereignCloudStack github org membership, accounts will be created manually for now.
22
24
25
+
<!-- markdownlint-disable search-replace -->
26
+
23
27
Example:
24
28
25
-
| github handle | plusserver login |
29
+
| github handle |plusserver login |
26
30
| :-----------: | :-----------------: |
27
-
| frosty-geek | u500924-frosty-geek |
31
+
|frosty-geek | u500924-frosty-geek |
28
32
| fkr | u500924-fkr |
29
33
|||
30
34
31
-
> **Note**
32
-
> To easy collaboration & transparency within the SCS team all users will have their default_project_id set to `p500924-scs-community` by default and will have full access on all projects listed below.
33
-
34
-
### Service Users
35
+
### SCS2 Service Users
35
36
36
37
Service users will have their default_project_id set to a specific project and will NOT be granted full access to other projects by default.
37
38
38
39
| Unique Identifier | Service User Name | Full Access on | Community Contact | Description | Needed until |
0 commit comments