|
1 | 1 | # Hardware classification controller
|
2 | 2 |
|
3 |
| -Controller for matching expected hardware characteristics to BareMetalHost's |
4 |
| -hardware details. |
| 3 | +Hardware Classification Controller (HWCC) goal is to identify right matched |
| 4 | +host for user provided hardware configurations. |
5 | 5 |
|
6 |
| -The HWCC (Hardware Classification Controller) implements Kubernetes API for |
7 |
| -labeling the matching hosts. Implemented `hardware-classification` CRD expects |
8 |
| -profile having hardware configurations for CPU, RAM, Disk and NIC. |
9 |
| - |
10 |
| -Comparision and validation is done on list of baremetalhosts in ready state |
11 |
| -provided by `BMO` against hardware configuration mentioned in |
12 |
| -metal3.io_v1alpha1_hardwareclassification.yaml. |
| 6 | +User provides workload profile which has set of hardware configuration |
| 7 | +parameters (CPU, RAM, DISK and NIC). HWCC fetches the hosts from BMO. |
| 8 | +It then filters the ready state hosts and compares those with the expected |
| 9 | +configurations provided by user in profile. The hosts matched to any of the |
| 10 | +configurations are then labelled accordingly. |
13 | 11 |
|
14 | 12 | More capabilities are being added regularly. See open issues and pull
|
15 | 13 | requests for more information on work in progress.
|
16 | 14 |
|
17 | 15 | For more information about Metal³, the Hardware Classification, and other
|
18 |
| -related components, see the [Metal³ docs](https://github.com/metal3-io/metal3-docs) and |
| 16 | +related components, see the |
| 17 | +[Metal³ docs](https://github.com/metal3-io/metal3-docs)and |
19 | 18 | [Kubebuilder Book](https://book.kubebuilder.io/quick-start.html#create-a-project).
|
20 | 19 |
|
21 | 20 | ## Resources
|
|
0 commit comments