---
type: "ABB"
nummer: "ABB-0400"
abb_id: "ABB-0400"
abb_nummer: "BA01"
naam: "Storage"
archimate_type: "Grouping"
laag: "Basisfunctionaliteit"
auteur: "R. Groenewoud"
status: "Niet vermeld"
gerelateerde_adrs: ["ADR-C05", "ADR-C06"]
archimate_element: "id-30440"
archimate_grouping: "id-30440"
archimate_technology_service: ["id-30286"]
archimate_view: "id-29956"
ontwerp_paragraaf: "5.3.5"
ontwerp_link: "../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#decompositie-abb-storage"
ontwerp_paragrafen: ["5.3.4", "5.3.5", "5.4.1", "5.4.3"]
ontwerp_links:
  - "../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#positionering-abb-storage"
  - "../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#decompositie-abb-storage"
  - "../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#positionering-abb-management-cluster"
  - "../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#positionering-abb-tenant-cluster"
---

# ABB-0400: Storage

```mermaid
%%{init: {"flowchart": {"nodeSpacing": 12, "rankSpacing": 12, "padding": 8}}}%%
flowchart TB
    %% id-30439 -> id-30440 (Grouping)
    subgraph v_id_30439["ABB: Storage"]
        direction TB
        %% id-30455 -> id-30286 (TechnologyService)
        v_id_30455["Storage"]
        %% id-30444 -> id-30445 (Grouping)
        subgraph v_id_30444["ABB: Block-Based Storage"]
            direction TB
            %% id-30446 -> id-30290 (TechnologyService)
            v_id_30446["Block-Based Storage (SAN)"]
        end
        %% id-30449 -> id-30450 (Grouping)
        subgraph v_id_30449["ABB: File-Based Storage"]
            direction TB
            %% id-30451 -> id-30288 (TechnologyService)
            v_id_30451["File-Based Storage (NAS)"]
        end
        %% id-30452 -> id-30453 (Grouping)
        subgraph v_id_30452["ABB: Object-Based Storage"]
            direction TB
            %% id-30454 -> id-30284 (TechnologyService)
            v_id_30454["Object-Based Storage"]
        end
        %% id-30441 -> id-30442 (Grouping)
        subgraph v_id_30441["ABB: Immutable Storage"]
            direction TB
            %% id-30443 -> id-30283 (TechnologyService)
            v_id_30443["Immutable Storage"]
        end
    end
    %% id-30457 -> id-30442 (Grouping)
    subgraph v_id_30457["ABB: Immutable Storage"]
        direction TB
        %% id-30458 -> id-30283 (TechnologyService)
        v_id_30458["Immutable Storage"]
    end
    v_id_30446 -->|Specialization| v_id_30455
    v_id_30451 -->|Specialization| v_id_30455
    v_id_30454 -->|Specialization| v_id_30455
    v_id_30458 -->|Specialization| v_id_30454
    style v_id_30455 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30446 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30444 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30451 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30449 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30454 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30452 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30443 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30441 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30439 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30458 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30457 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
```

## Positionering ABB “Storage”

Storage wordt afhankelijk van de benodigde schaalgrootte op twee manieren aangeboden: op basis van Hyper Converged Infrastructure (HCI) gebruikmakend van de storage op de fysieke servers of op basis van een storage array.

![Figuur 5‑12 Positionering ABB Storage](<../../input/markdown/media/media/image34.svg>)

## Decompositie ABB “Storage”

Storage wordt op 3 verschillende manieren ingezet: block-based, files-based en object-based.

![Figuur 5‑13 Decompositie ABB Storage](<../../input/markdown/media/media/image35.png>)

## Positionering ABB "Management Cluster"

De technologiestack bestaat uit één Kubernetes managementcluster die gebruikt wordt voor het beheer van meerdere tenantclusters.

![Figuur 5‑14 Positionering ABB Management Cluster](<../../input/markdown/media/media/image37.svg>)

## Positionering ABB "Tenant Cluster"

Elk Tenant Cluster bestaat uit Worker Nodes met eigen hardware. De Kubernetes control plan van elk Tenant Cluster maakt wel gebruik van gedeelde hardware (Hosted Control Plane).

![Figuur 5‑16 Positionering ABB Tenant Cluster](<../../input/markdown/media/media/image41.svg>)

Samenvatting uitgangspunten, architectuurkeuzes en aandachtspunten:

- De afnemer kan één of meerdere tenantclusters afnemen die zowel onderling als van tenantclusters van andere afnemers fysiek gescheiden zijn;

- Elke tenantcluster kan logisch verder opgedeeld worden in projecten die elk weer bestaan uit Kubernetes namespaces.
