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
Copy file name to clipboardExpand all lines: asciidoc/components/metal3.adoc
+18-6Lines changed: 18 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,16 +19,28 @@ management capabilities for Kubernetes.
19
19
Metal^3^ provides Kubernetes-native resources to manage the lifecycle of bare-metal servers
20
20
which support management via out-of-band protocols such as https://www.dmtf.org/standards/redfish[Redfish].
21
21
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.
24
26
25
27
== How does SUSE Edge use Metal^3^?
26
28
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: +
29
35
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
0 commit comments