Skip to content

Commit 0e2ee33

Browse files
committed
Better wording what CiaB is (it's single-node).
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]>
1 parent 47d68a5 commit 0e2ee33

File tree

1 file changed

+24
-5
lines changed

1 file changed

+24
-5
lines changed

docs/index.mdx

Lines changed: 24 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,27 +16,46 @@ SCS is built, backed, and operated by an active open-source community worldwide.
1616

1717
## Use Cases and Deployment Examples
1818

19-
### IaaS Layer
19+
### Virtualization (IaaS) Layer
20+
21+
The SCS IaaS reference implementation is based on [OSISM](https://osism.tech/).
2022

2123
#### Quick Start with Cloud-In-A-Box
2224

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

2531
#### Reference Implementation Testbed
2632

33+
The fastest way to get in touch with SCS is to deploy a SCS cloud virtually.
34+
2735
This means that you set up an SCS test installation including all the infrastructure
2836
pieces such as database, message queueing, ceph, monitoring and logging, IAM, the
2937
[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.
3140

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
3442
testbed running. Please read carefully through the
3543
[deployment](https://docs.osism.de/testbed/deployment.html) section of the
3644
manual.
3745

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+
3853
### Container Layer
3954

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+
4059
#### Cluster Stacks
4160

4261
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

Comments
 (0)