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
+21-71Lines changed: 21 additions & 71 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,15 @@ 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 (SCS1 aka gx-scs)
9
+
## plusserver (SCS2)
10
+
11
+
SCS2 is the successor to gx-scs (or SCS1), which no longer exists.
10
12
11
-
### SCS1 Usage
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
-
### SCS1 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>`
@@ -28,10 +30,7 @@ Example:
28
30
| fkr | u500924-fkr |
29
31
|||
30
32
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
-
### SCS1 Service Users
33
+
### SCS2 Service Users
35
34
36
35
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
36
@@ -44,72 +43,23 @@ Service users will have their default_project_id set to a specific project and w
44
43
| 1b6bb583fc5e40e49f2a7e9b4301de65 | u500924-svc-zuul | p500924-scs-zuul | o-otte | Service User - SCS Zuul | 30.11.2024 |
45
44
|||||||
46
45
47
-
### SCS1 Projects
48
-
49
-
| Unique Identifier | Project Name | Community Contact | Description | Needed until |
Copy file name to clipboardExpand all lines: community/tools/jitsi.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,14 +11,14 @@ The server uses an automated deployment based on the
11
11
12
12
Configuration is such everyone who knows the room can connect, unless the moderator
13
13
sets a password/PIN. Opening a new room requires authentication. (Contact
14
-
[Kurt](https://scs.community/garloff) if you need a password.)
14
+
[Kurt](https://github.com/garloff) if you need a password.)
15
15
16
16
Links to the meeting room (as well as dial-in information) are in the appointments
17
17
in the public calendar.
18
18
19
19
## Usage
20
20
21
-
Connect with a desktop browser or (for mobile devices) the Jitsi Meet App.
21
+
Connect with a desktop browser, the Jitsi [desktop app](https://github.com/jitsi/jitsi-meet-electron) or the Jitsi [mobile app](https://jitsi.org/downloads/).
22
22
23
23
Use the little arrows in the control bar at the bottom to select speaker, microphone
24
24
and camera in case you lack audio/video.
@@ -78,7 +78,9 @@ to change room assignment or to resolve issues with dial-in.
78
78
## Browser specific hints
79
79
80
80
Traditionally, the [blink](https://en.wikipedia.org/wiki/Blink_%28browser_engine%29)-based
81
-
browsers (like Google Chrome, Chromium, Edge, ...) supported WebRTC best.
81
+
browsers (like Google Chrome, Chromium, Edge, ...) support WebRTC best.
82
+
A Jitsi [desktop app](https://github.com/jitsi/jitsi-meet-electron) and Jitsi [mobile app](https://jitsi.org/downloads/) is also available.
83
+
82
84
Safari and Firefox do work, but at the cost of inferior codecs or increased CPU or
83
85
bandwidth requirements (e.g. due to missing [SimulCast](https://en.wikipedia.org/wiki/Simulcast)
0 commit comments