Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/document scs2 #298

Merged
merged 7 commits into from
Feb 14, 2025
Merged

Feat/document scs2 #298

Show file tree
Hide file tree
Changes from 5 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
05ebb1c
Chore: Use autogenerated index rather than manual one.
garloff Feb 10, 2025
2a63084
Document existence of SCS2 and projects there.
garloff Feb 10, 2025
59171bd
Avoid / in subtitle.
garloff Feb 12, 2025
339b0b4
Reformat URLs.
garloff Feb 13, 2025
74fb6b3
Merge branch 'main' into feat/document-scs2
garloff Feb 13, 2025
12bb038
Be more specific on shutdown of SCS1.
garloff Feb 13, 2025
3a23ae8
Merge branch 'main' into feat/document-scs2
garloff Feb 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 36 additions & 11 deletions community/cloud-resources/cloud-resources.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,13 +6,13 @@ This document gives an overview of the test and development cloud resources curr

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, ...)

## plusserver
## plusserver (SCS1 aka gx-scs)

### Usage
### SCS1 Usage

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

### Users
### SCS1 Users

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.
`prefix-<$github handle>`
Expand All @@ -31,7 +31,7 @@ Example:
> **Note**
> 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.

### Service Users
### SCS1 Service Users

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.

Expand All @@ -44,7 +44,7 @@ Service users will have their default_project_id set to a specific project and w
| 1b6bb583fc5e40e49f2a7e9b4301de65 | u500924-svc-zuul | p500924-scs-zuul | o-otte | Service User - SCS Zuul | 30.11.2024 |
| | | | | | |

### Projects
### SCS1 Projects

| Unique Identifier | Project Name | Community Contact | Description | Needed until |
| :------------------------------: | --------------------------- | ------------------------ | ------------------------------------- | :----------: |
Expand Down Expand Up @@ -80,20 +80,45 @@ Service users will have their default_project_id set to a specific project and w
| 5c6d4d7183834eafbc20108ad647a9c0 | p500924-kaas-playground8 | jschoone | Playground8 for Hackathon | 30.09.2024 |
| 7e18881932f749baa7d547ebd407b8d8 | p500924-kaas-playground9 | jschoone | Playground9 for Hackathon | 30.09.2024 |
| d9dc2f33e76240219db484526e9f601d | p500924-akafazov | akafazov | akafazov Testbed | 30.04.2024 |
| b07ad6a84982471b9a344ef9947f0e0f | p500924-gtema | gtema | Testbed for gtema | ∞ |
| e89ac8c9f66f46b5a983b2a05d2a66ec | p500924-zuse-z3 | zuse-z3 | Josefine's gx-scs project | ∞ |
| fc1f7a0e10a64d6083dcdbcb7ccf6ff4 | p500924-compliance-monitor | mbuechse | SCS Compliance Monitor Deployment | ∞ |
| eba5414a4f8549b28a62af199d82dab5 | p500924-tsmado | tsmado | tsmado's gx-scs project | ∞ |
| b07ad6a84982471b9a344ef9947f0e0f | p500924-gtema | gtema | Testbed for gtema | ∞ |
| e89ac8c9f66f46b5a983b2a05d2a66ec | p500924-zuse-z3 | zuse-z3 | Josefine's gx-scs project | ∞ |
| fc1f7a0e10a64d6083dcdbcb7ccf6ff4 | p500924-compliance-monitor | mbuechse | SCS Compliance Monitor Deployment | ∞ |
| eba5414a4f8549b28a62af199d82dab5 | p500924-tsmado | tsmado | tsmado's gx-scs project | ∞ |

## plusserver (SCS2)

### SCS2 Usage

The [guide for SCS1](plusserver-gx-scs.md) applies also to SCS2.

### SCS2 Users

See [SCS1](#SCS1 Users).

### SCS2 Projects

| Unique Identifier | Project Name | Community Contact | Description | Needed until |
| :------------------------------: | -------------------------- | ----------------- | --------------------------------- | :----------: |
| 9c482c928d68470ea35a764e1ba9211a | p500924-compliance-monitor | mbuechse | SCS Compliance Monitor Deployment | ∞ |
| fe66fd7655814078924155876562dd3d | p500924-scs-community | fkr | SCS Community Project | ∞ |
| 4a8829a5ecad480d8dde1e46a9c5284b | p500924-health-monitor | garloff | SCS Health Monitor | ∞ |
| 34d3d89fc74e4db5a6df1c9ebf2f3a2a | p500924-scs-zuul | garloff | SCS Zuul | ∞ |
| f2eccb67b16f4430b6d5e70afb515f9d | p500924-harbor | chess-knight | SCS Registry (Harbor) | ∞ |
| 45b5e27a5fe3431083e450cf2d13e71b | p500924-kaas-playground1 | jschoone | Playground1 for Hackathon | 30.09.2024 |
| ef12fed77f114eb4a20068f0422a8109 | p500924-kaas-playground2 | jschoone | Playground2 for Hackathon | 30.09.2024 |
| bf8d511728a44072b7c97b1fe00947b8 | p500924-kaas-playground3 | jschoone | Playground3 for Hackathon | 30.09.2024 |
| 61b315797c75431787dc20a61cbaf052 | p500924-kaas-playground4 | jschoone | Playground4 for Hackathon | 30.09.2024 |
| 94f7c7507be1484a9ce6aba20d19d1c6 | p500924-kaas-playground5 | jschoone | Playground5 for Hackathon | 30.09.2024 |

## Wavecon

### Service Users
### Wavestack Service Users

| Unique Identifier | Service User Name | Full Access on | Community Contact | Description | Needed until |
| :------------------------------: | ----------------- | -------------- | ----------------- | --------------------------------------------- | :----------: |
| df4af5376bbd4de587c4335622149be7 | scs-standards | scs-standards | itrich | Service User - SCS Standards Compliance Check | ∞ |

### Projects
### Wavestack Projects

| Unique Identifier | Project Name | Community Contact | Description | Needed until |
| :------------------------------: | ------------------ | ----------------- | ------------------ | :----------: |
Expand Down
28 changes: 24 additions & 4 deletions community/cloud-resources/plusserver-gx-scs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,22 +4,42 @@ version: 2022-12-22
author: Ralf Heiringhoff, Mathias Fechner
---

## Getting Started for the Gaia-X Demonstrator @ plusserver
## Getting Started on SCS1 (the Gaia-X Demonstrator @ plusserver, aka. gx-scs)

## URLs for access
### URLs for accessing SCS1

- UI (Horizon): [https://ui.gx-scs.sovereignit.cloud/](https://ui.gx-scs.sovereignit.cloud/)
- API auth url (Keystone): [https://api.gx-scs.sovereignit.cloud:5000](https://api.gx-scs.sovereignit.cloud:5000)
- Object Storage endpoint (S3/SWIFT): [https://api.gx-scs.sovereignit.cloud:8080](https://api.gx-scs.sovereignit.cloud:8080)

## Authentication (UI)
### Authentication (UI)

For your login you will need:

- Username (`u500924-<$github-handle>`)
- Password
- Domain (`d500924`)

## Getting Started with OpenStack
### Getting Started with OpenStack

See [Getting Started with OpenStack](./getting-started-openstack.md)

## Getting started on SCS2 (the successor to SCS1)

After having used the SCS1 environment for validation, testing,
skill building and having provided generous access to the SCS community,
it will no longer be taken care of well by PlusServer as of January 2025
and can thus be expected to run out of capacity and fail in other ways.
It will be switched off in the coming months.
SCS1 is replaced by the newer SCS2 environment that is maintained by
PlusServer as reference environment and PS has agreed to provide community
resources on SCS2. All SCS community activities that continue to be needed
should move to SCS2.

Access to SCS2 is handled in the same way as to SCS1.

### URLs for accessing SCS2

- UI (horizon): [https://scs2.api.pco.get-cloud.io/](https://scs2.api.pco.get-cloud.io/)
- API auth URL: [https://scs2.api.pco.get-cloud.io:5000/](https://scs2.api.pco.get-cloud.io:5000/)
- Object Storage EP: [https://scs2.api.pco.get-cloud.io:8080/](https://scs2.api.pco.get-cloud.io:8080/)
Loading