Skip to content

Commit 33eb1e4

Browse files
authored
Minor Doc improvements Metal3 (#1011)
* Changed macro version-sl-micro to version-operatingsystem * Some minor changes to Metal3 language * Addressed review comments
1 parent eb0dcff commit 33eb1e4

File tree

1 file changed

+18
-6
lines changed

1 file changed

+18
-6
lines changed

asciidoc/components/metal3.adoc

Lines changed: 18 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,16 +19,28 @@ management capabilities for Kubernetes.
1919
Metal^3^ provides Kubernetes-native resources to manage the lifecycle of bare-metal servers
2020
which support management via out-of-band protocols such as https://www.dmtf.org/standards/redfish[Redfish].
2121

22-
It also has mature support for https://cluster-api.sigs.k8s.io/[Cluster API (CAPI)] which enables management
23-
of infrastructure resources across multiple infrastructure providers via broadly adopted vendor-neutral APIs.
22+
It also has mature support for https://cluster-api.sigs.k8s.io/[Cluster API (CAPI)].
23+
This enables management of hardware resources across multiple
24+
infrastructure providers via broadly adopted vendor-neutral APIs.
25+
Cluster API uses Metal^3^ as an infrastructure backend for Machine objects.
2426

2527
== How does SUSE Edge use Metal^3^?
2628

27-
This method is useful for scenarios where the target hardware supports out-of-band management, and a fully automated
28-
infrastructure management flow is desired.
29+
SUSE Edge uses Metal^3^ to manage the lifecycle of physical hardware, such as
30+
servers. The hardware needs to support an out-of-band management protocol that
31+
is supported by Metal^3^ (e.g. Redfish). When a SUSE Edge management cluster
32+
provisions or deprovisions downstream clusters, Metal^3^ will interact with a
33+
server's BMC via Redfish. The following actions are typically part of this
34+
interaction: +
2935

30-
This method provides declarative APIs that enable inventory and state management of bare-metal servers, including
31-
automated inspection, cleaning and provisioning/deprovisioning.
36+
* Mount and umount Virtual Media.
37+
* Power on, power off, and reset servers.
38+
39+
This approach is useful for scenarios where the target hardware supports out-of-band management, and a fully automated infrastructure management flow is desired.
40+
41+
Metal^3^ and CAPI provide declarative APIs that enable inventory and state
42+
management of bare-metal servers, including automated inspection, cleaning, and
43+
provisioning/deprovisioning.
3244

3345
== Known issues
3446

0 commit comments

Comments
 (0)