iaas: reference OSISM instead of copying docs

The IaaS Layer of the docs is not maintained within the SCS community
repositories: at build time getDocs.js cloned osism/osism.github.io and
copied three trees verbatim into docs/02-iaas/ (the OpenStack tools, the
whole guides tree, and the testbed). These were partial, drifting copies
of osism.tech/docs that went stale and mixed with the few pages that are
maintained in this repository.

Stop mirroring OSISM and instead present it as the stack the SCS IaaS
reference implementation was built with, linking out to the official
OSISM documentation:

- Remove the three osism/osism.github.io entries from docs.package.json
  so no OSISM content is copied on build.
- Add an SCS-authored landing page (docs/02-iaas/index.md) that frames
  OSISM (OpenStack, Ceph, Kolla/kolla-ansible) as the reference
  implementation, notes that SCS is a modular software stack with more
  than one implementation nowadays, links to the top-level OSISM
  documentation categories, and surfaces the Image Manager and Flavor
  Manager tools OSISM provides for SCS standard compliance.
- Point the IaaS Layer sidebar category at the new landing page and drop
  the Components sub-category (image/flavor manager were OSISM pulls).
- Repoint every internal link that targeted the removed OSISM copies to
  osism.tech (index.mdx, faq, artcodix, preinstall-checklist,
  identity-federation-in-scs) and update the architecture overview data
  so the IaaS tiles link to the OSISM tool pages.

Guides and Deployment Examples now resolve to only the pages maintained
in this repository (security groups, user data backups, artcodix).
Verified with a production build: no IaaS-related broken links remain
and all outbound OSISM/scs.community links resolve.

DocImpact
Assisted-by: Claude:claude-opus-4-8
Signed-off-by: Jan Klare <klare@osism.tech>

Author: jklare

contributor-docs/operations/iam/identity-federation-in-scs.md

@@ -13,8 +13,8 @@ to achieve that goal. To simplify connecting the different parts of SCS
 to customer owned IAM solutions, SCS deploys Keycloak as central Identity
 Provider (IdP) service.
 
-Currently this is deployed automatically only in the [osism/testbed](https://docs.scs.community/docs/iaas/guides/deploy-guide/examples/testbed/),
-which provides [its own documentation for authentication with OIDC](https://docs.scs.community/docs/iaas/guides/deploy-guide/examples/testbed#authentication-with-oidc).
+Currently this is deployed automatically only in the [OSISM testbed](https://osism.tech/docs/testbed/),
+which provides [its own documentation](https://osism.tech/docs/testbed/).
 
 The following sections describe how this is done.
 

docs.package.json

@@ -5,30 +5,12 @@
     "target": "docs",
     "label": "06-releases"
   },
-  {
-    "repo": "osism/osism.github.io",
-    "source": "docs/guides/operations-guide/openstack/tools/*",
-    "target": "docs/02-iaas/components",
-    "label": ""
-  },
   {
     "repo": "SovereignCloudStack/standards",
     "source": ["Standards/*.md", "Tests/scs-*.yaml"],
     "target": "standards",
     "label": ""
   },
-  {
-    "repo": "osism/osism.github.io",
-    "source": "docs/guides",
-    "target": "docs/02-iaas/",
-    "label": ""
-  },
-  {
-    "repo": "osism/osism.github.io",
-    "source": "docs/testbed",
-    "target": "docs/02-iaas/deployment-examples",
-    "label": ""
-  },
   {
     "repo": "SovereignCloudStack/k8s-harbor",
     "source": "docs",

docs/01-getting-started/preinstall-checklist.md

@@ -126,7 +126,7 @@ For the download of installation data such as container images, operating system
 either access to publicly accessible networks must be provided or a caching proxy or a dedicated
 repository server must be provided directly from the network for "Node communication".
 
-The [Configuration Guide](https://docs.scs.community/docs/iaas/guides/configuration-guide/proxy) provides more detailed information on how this can be configured.
+The OSISM [Configuration Guide](https://osism.tech/docs/guides/configuration-guide/) provides more detailed information on how this can be configured.
 
 TBD:
 

docs/02-iaas/deployment-examples/artcodix/index.mdx

@@ -158,4 +158,4 @@ the faster storage data can be replicated between nodes. This usually leads to i
 
 ## How to continue
 
-After implementing the recommended deployment example hardware, you can continue with the [deployment guide](https://docs.scs.community/docs/iaas/guides/deploy-guide/).
+After implementing the recommended deployment example hardware, you can continue with the OSISM [deployment guide](https://osism.tech/docs/guides/deploy-guide/).

docs/02-iaas/index.md

@@ -0,0 +1,62 @@
+---
+title: IaaS Layer
+sidebar_position: 1
+---
+
+# IaaS Layer
+
+The SCS reference implementation of the Infrastructure-as-a-Service (IaaS) layer
+was built with [**OSISM**](https://osism.tech/docs). It builds on
+[OpenStack](https://openstack.org/) for compute, network and identity services and
+[Ceph](https://ceph.io/) for storage. The OpenStack deployment is based on
+[Kolla](https://opendev.org/openstack/kolla) (container images) and
+[kolla-ansible](https://opendev.org/openstack/kolla-ansible), which OSISM wraps with
+additional Ansible playbooks and tooling to deploy and operate the whole stack.
+
+OSISM is the reference implementation, but not the only way to build an
+SCS-compatible cloud. SCS is a
+[modular software stack](https://sovereigncloudstack.org/en/modular-software-stack/):
+today, more than one implementation exists to build SCS-compatible clouds, and
+compliance is defined by the [standards](/standards) rather than by a single stack.
+
+:::info
+
+OSISM maintains its own, authoritative documentation. Rather than mirroring it
+here (and letting the copy drift out of date), this page links directly to the
+relevant sections of the official [OSISM documentation](https://osism.tech/docs/).
+
+:::
+
+## OSISM documentation
+
+- [Getting started](https://osism.tech/docs/) — introduction and overview of OSISM.
+- [Concepts](https://osism.tech/docs/concepts/) — architecture and core components.
+- [Guides](https://osism.tech/docs/guides/) — deployment, configuration, operations,
+  upgrade, troubleshooting and user guides.
+- [Testbed](https://osism.tech/docs/testbed/) — the fastest way to try SCS: a full
+  virtual SCS/OSISM installation you can deploy on top of an existing OpenStack cloud.
+- [Release Notes](https://osism.tech/docs/release-notes/) — per-release notes and
+  upgrade information.
+- [Appendix](https://osism.tech/docs/appendix/) — CLI reference, security advisories
+  and supported standards.
+
+## OpenStack tools
+
+OSISM maintains the OpenStack tooling that SCS relies on to meet its standards:
+
+- [Image Manager](https://osism.tech/docs/guides/operations-guide/openstack/tools/image-manager)
+  — manages the OpenStack images, used to provide the SCS mandatory and recommended
+  images.
+- [Flavor Manager](https://osism.tech/docs/guides/operations-guide/openstack/tools/flavor-manager)
+  — manages the OpenStack flavors, used to provide the SCS standard flavors.
+
+## In this section
+
+Alongside the OSISM reference, SCS maintains a few IaaS resources of its own:
+
+- **Guides** — SCS user-facing best practices, such as configuring
+  [security groups](/docs/iaas/guides/user-guide/security-groups)
+  and creating [user data backups](/docs/iaas/guides/user-guide/user-data-backups).
+- **Deployment examples** — real-world setups such as the
+  [artcodix](/docs/iaas/deployment-examples/artcodix/) production deployment and
+  the SCS [turnkey hardware landscape](/docs/turnkey-solution/hardware-landscape/).

docs/08-faq/index.mdx

@@ -47,7 +47,7 @@ IaaS stands for Infrastructure as a Service, providing virtualized computing res
 
 ## How is the IaaS layer structured?
 
-IaaS typically comprises virtual machines, storage, and network resources, all offered as scalable services. [Find the architecture here](https://docs.scs.community/docs/category/iaas-layer)
+IaaS typically comprises virtual machines, storage, and network resources, all offered as scalable services. [Find the architecture here](https://docs.scs.community/docs/iaas/)
 
 ## What does KaaS mean?
 
@@ -61,7 +61,7 @@ KaaS refers to Kubernetes as a Service, where providers offer Kubernetes Cluster
 
 **As a Cloud Service Provider**:
 
-- **Testbed**: Use the SCS test environment to experiment. [Link to Testbed/deployment example](https://docs.scs.community/docs/iaas/deployment-examples/cloud-in-a-box/advanced-guides/testbed)
+- **Testbed**: Use the SCS test environment to experiment. [Link to the OSISM testbed](https://osism.tech/docs/testbed/)
 
 ## I want to use an SCS Cloud! How do I get started?
 

docs/index.mdx

@@ -18,7 +18,9 @@ SCS is built, backed, and operated by an active open-source community worldwide.
 
 ### Virtualization (IaaS) Layer
 
-The SCS IaaS Reference Implementation is based on [OSISM](https://osism.tech/).
+The SCS IaaS reference implementation was built with [OSISM](https://osism.tech/docs).
+See the [IaaS Layer](/docs/iaas/) section for an overview and links
+to the official OSISM documentation.
 
 #### Reference Implementation Testbed
 
@@ -30,10 +32,8 @@ pieces such as database, message queueing, ceph, monitoring and logging, IAM, th
 on top of an existing OpenStack IaaS platform, ideally one that allows for nested
 virtualization.
 
-Read the [testbed docs](/docs/iaas/deployment-examples/testbed) to learn how to get the
-testbed running. Please read carefully through the
-[deployment](/docs/iaas/deployment-examples/testbed#deployment) section of the
-manual.
+Read the [OSISM testbed docs](https://osism.tech/docs/testbed/) to learn how to get
+the testbed running.
 
 #### Examples for real deployments
 

sidebarsDocs.js

@@ -8,7 +8,8 @@ const sidebarsDocs = {
       type: 'category',
       label: 'IaaS Layer',
       link: {
-        type: 'generated-index'
+        type: 'doc',
+        id: 'iaas/index'
       },
       items: [
         {
@@ -21,34 +22,6 @@ const sidebarsDocs = {
             }
           ]
         },
-        {
-          type: 'category',
-          label: 'Components',
-          link: {
-            type: 'generated-index'
-          },
-          items: [
-            {
-              type: 'category',
-              label: 'Openstack Image Manager',
-              link: {
-                id: 'iaas/components/image-manager/index',
-                type: 'doc'
-              },
-              items: [
-                {
-                  type: 'doc',
-                  id: 'iaas/components/image-manager/update'
-                }
-              ]
-            },
-            {
-              type: 'doc',
-              label: 'Openstack Flavor Manager',
-              id: 'iaas/components/flavor-manager'
-            }
-          ]
-        },
         {
           type: 'category',
           label: 'Deployment Examples',

static/data/architecturalOverviewData.json

@@ -71,18 +71,18 @@
     {
       "title": "IaaS Layer",
       "body": "SCS offers OpenStack infrastructure solutions based on KVM virtualization to deploy VM workloads and enabling the container layer optionally.",
-      "url": "/docs/category/iaas-layer",
+      "url": "/docs/iaas/",
       "buttonText": "Learn More",
       "components": [
         {
           "title": "Image Manager",
-          "url": "/docs/iaas/components/image-manager",
+          "url": "https://osism.tech/docs/guides/operations-guide/openstack/tools/image-manager",
           "mandatory": "true",
           "stable": "true"
         },
         {
           "title": "Flavor Manager",
-          "url": "/docs/iaas/components/flavor-manager",
+          "url": "https://osism.tech/docs/guides/operations-guide/openstack/tools/flavor-manager",
           "mandatory": "true",
           "stable": "true"
         }