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: docs/index.mdx
+32-10Lines changed: 32 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -16,32 +16,54 @@ SCS is built, backed, and operated by an active open-source community worldwide.
16
16
17
17
## Use Cases and Deployment Examples
18
18
19
-
### IaaS Layer
19
+
### Virtualization (IaaS) Layer
20
20
21
-
#### Quick Start with Cloud-In-A-Box
21
+
The SCS IaaS Reference Implementation is based on [OSISM](https://osism.tech/).
22
22
23
-
The fastest way to get in touch with SCS is to deploy a SCS cloud virtually. The Cloud-In-A-Box was built explicitly for this scenario. Check it out [here](/docs/iaas/guides/deploy-guide/examples/cloud-in-a-box)
23
+
#### Quick Start with Cloud-in-a-Box
24
+
25
+
You can do a single node installation for learning, testing or development purposes.
26
+
The Cloud-in-a-Box configuration was built explicitly for this scenario.
27
+
Check it out [here](/docs/iaas/deployment-examples/cloud-in-a-box)
28
+
It comes with a complete set of services, even Ceph is part of it
29
+
(despite of course not offering much redundancy on a single-node).
24
30
25
31
#### Reference Implementation Testbed
26
32
33
+
The fastest way to get in touch with SCS is to deploy a SCS cloud virtually.
34
+
27
35
This means that you set up an SCS test installation including all the infrastructure
28
36
pieces such as database, message queueing, ceph, monitoring and logging, IAM, the
29
37
[OpenStack](https://openstack.org/) core services, and (soon) the Container layer
30
-
on top of an existing IaaS platform.
38
+
on top of an existing OpenStack IaaS platform, ideally one that allows for nested
39
+
virtualization.
31
40
32
-
The SCS IaaS reference implementation is based on [OSISM](https://osism.tech/). Read on the
33
-
[OSISM testbed docs](https://docs.osism.de/testbed/) to learn how to get the
41
+
Read the [testbed docs](/docs/iaas/deployment-examples/testbed) to learn how to get the
34
42
testbed running. Please read carefully through the
35
-
[deployment](https://docs.osism.de/testbed/deployment.html) section of the
43
+
[deployment](/docs/iaas/deployment-examples/testbed#deployment) section of the
36
44
manual.
37
45
46
+
#### Examples for real deployments
47
+
48
+
[artcodix](https://artcodix.com/) has [shared](/docs/iaas/deployment-examples/artcodix/)
49
+
some details on their production setup. The SCS team itself has created [extensive
50
+
documentation](/docs/turnkey-solution/hardware-landscape/) including details on the
51
+
used hardware.
52
+
38
53
### Container Layer
39
54
55
+
The Reference Implementation (v2) for the container (Kubernetes-as-a-Service = KaaS) layer
56
+
is provided by [Cluster Stacks](/docs/category/cluster-stacks)
57
+
from [syself](https://syself.com/).
58
+
40
59
#### Cluster Stacks
41
60
42
-
With the Cluster Stacks, in the V2 KaaS reference implementation, we provide an opinionated optimized configuration of Kubernetes clusters. Through better packaging, integrated testing, and bundled configuration, SCS-based Kubernetes clusters provide easier individualization.
43
-
Throughout the R6 development cycle Cluster Stacks are taken from a technical preview to be [functional and available on top of the IaaS reference implementation](https://github.com/SovereignCloudStack/issues/milestone/8) as well to replace the V1 KaaS reference implementation [k8s-cluster-api-provider](https://github.com/SovereignCloudStack/k8s-cluster-api-provider/).
44
-
The Cluster Stacks can already be tried with the [demo](https://github.com/SovereignCloudStack/cluster-stacks-demo) repository. Although this is based on the not-production-ready Docker provider, the usage is the same for every provider.
61
+
With the Cluster Stacks, in the V2 KaaS reference implementation, we provide an opinionated optimized configuration of Kubernetes cluster management based on [Kubernetes Cluster-API](https://cluster-api.sigs.k8s.io/).
62
+
Through better packaging, integrated testing, and bundled configuration, SCS-based Kubernetes clusters provide easier individualization.
63
+
Throughout the R6 development cycle Cluster Stacks were taken from a technical preview to be [functional and available on top of the IaaS reference implementation](https://github.com/SovereignCloudStack/issues/milestone/8) as well to replace the V1 KaaS reference implementation [k8s-cluster-api-provider](https://github.com/SovereignCloudStack/k8s-cluster-api-provider/).
64
+
The Cluster Stacks have fully replaced V1 meanwhile to be the production-grade KaaS solution in SCS, please check out the
For demo, test and development purposes, you can also try the [demo](https://github.com/SovereignCloudStack/cluster-stacks-demo) repository which is an implementation using the (not-for-production) Docker provider. Implementations for other infrastructure are intended; the one for Hetzner for example is maintained by syself itself.
0 commit comments