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
It can be deployed in a VM, but most of the time is not.
Fix link to CiaB docs.
Restructure the sections a bit.
Signed-off-by: Kurt Garloff <[email protected]>
Copy file name to clipboardExpand all lines: docs/index.mdx
+24-5Lines changed: 24 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,27 +16,46 @@ 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
+
21
+
The SCS IaaS reference implementation is based on [OSISM](https://osism.tech/).
20
22
21
23
#### Quick Start with Cloud-In-A-Box
22
24
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)
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
43
[deployment](https://docs.osism.de/testbed/deployment.html) 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-Services = KaaS) layer
56
+
is provided by [Cluster-Stacks](https://docs-staging.scs.community/docs/category/cluster-stacks)
57
+
from [syself](https://syself.com/).
58
+
40
59
#### Cluster Stacks
41
60
42
61
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.
0 commit comments