-
Notifications
You must be signed in to change notification settings - Fork 391
feat(opcp): create guide how to see node inventory #8766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 2 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
72aa66f
feat(opcp): create guide how to see node inventory
ThibautOVH 0cb64a1
update dashboard definition
ThibautOVH 2dd4ee1
Update pages/hosted_private_cloud/opcp/how-to-see-node-inventory/guid…
ThibautOVH a4f2bf1
update from home to openstack-overview dash
ThibautOVH 7b5e884
fix typo
ThibautOVH 6da8c81
fix netbox description
ThibautOVH e85e577
add en version
ThibautOVH 9b3b451
proofreading
benchbzh a639694
images_resizing
benchbzh b23085c
fix screen language
ThibautOVH a1da882
date update & minor update EN version
benchbzh bd8eebe
date update
benchbzh 1095010
Update pages/hosted_private_cloud/opcp/how-to-see-node-inventory/guid…
benchbzh b45453e
Update pages/hosted_private_cloud/opcp/how-to-see-node-inventory/guid…
benchbzh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
154 changes: 154 additions & 0 deletions
154
pages/hosted_private_cloud/opcp/how-to-see-node-inventory/guide.fr-fr.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,154 @@ | ||
| --- | ||
| title: "OPCP - Comment visualiser l'inventaire des noeuds" | ||
| excerpt: "Apprenez à consulter l'inventaire des noeuds" | ||
| updated: 2025-12-02 | ||
| --- | ||
|
|
||
| ## Objectif | ||
|
|
||
| Ce guide explique comment consulter l’inventaire matériel, les ressources consommées et disponibles dans une plateforme **OVHcloud OnPrem Cloud Platform (OPCP)**, à l’aide de : | ||
|
|
||
| - **Grafana** : monitoring en temps réel de l’infrastructure | ||
| - **NetBox** : inventaire physique et logique | ||
| - **OpenStack Horizon** : inventaire ironic via Horizon | ||
| - **OpenStack CLI** : inventaire ironic via CLI | ||
|
|
||
| Un noeud dans OpenStack correspond à un serveur physique du rack OPCP. Dans ce guide, nous parlerons donc de **noeud** pour désigner un serveur physique. | ||
|
|
||
| ## Prérequis | ||
|
|
||
| - Être administrateur de l'infrastructure [OPCP](/links/hosted-private-cloud/onprem-cloud-platform) et avoir accès à l'interface d'administration `admin.dashboard`. | ||
| - Un accès **[OpenStack CLI configuré](/pages/hosted_private_cloud/opcp/how-to-use-api-and-get-credentials)** avec les droits nécessaires (`clouds.yaml` ou variables d’environnement). | ||
|
|
||
| ## En pratique | ||
|
|
||
| ### 1. Inventaire et monitoring via Grafana | ||
|
|
||
| Grafana fournit une vue de monitoring en temps réel et permet de suivre facilement l'évolution de votre parc OPCP. | ||
|
|
||
| #### 1.1 Accéder au dashboard Home | ||
|
|
||
| 1. Connectez-vous à l’URL d'administration `admin.dashboard`. | ||
| 2. Cliquez sur **Grafana**. | ||
| 3. Cliquez sur **Dashboards** et recherchez le dashboard **Home**. | ||
|
|
||
| Vous devriez voir un dashboard similaire à l'image suivante : | ||
| {.thumbnail} | ||
|
|
||
| #### 1.2 Comprendre le dashboard Home | ||
|
|
||
| Le dashboard affiche : | ||
|
|
||
| - L'état des services OpenStack | ||
| - Le nombre total de noeuds : **Total enrolled Ironic nodes** | ||
| - Le nombre de noeuds utilisé : **Allocated Ironic nodes** | ||
| - Le nombre de noeuds disponible et pas en maintenance : **Available Ironic nodes** | ||
| - Le nombre de noeuds en attente/erreur : **Waiting Ironic nodes** | ||
| - La liste des noeuds en erreurs ou en maintenance : **List of failed and maintenance nodes** | ||
|
|
||
| ### 2. Inventaire matériel et logique avec NetBox | ||
|
|
||
| NetBox est la référence pour gérer l’inventaire physique, réseau et logique de votre infrastructure. | ||
|
|
||
| #### 2.1 Accéder à NetBox | ||
|
|
||
| 1. Connectez-vous à l’URL d'administration `admin.dashboard`. | ||
| 2. Cliquez sur **NetBox**. | ||
|
|
||
| #### 2.2 Consulter l’inventaire des noeuds | ||
|
|
||
| Dans **Appareils**, vous pouvez voir la liste complète des équipements de votre rack OPCP (noeuds, équipements réseau, etc.). | ||
|
|
||
| Vous pouvez : | ||
|
|
||
| - utiliser la recherche rapide pour trouver un élément par nom | ||
| - utiliser **Filtres** pour une recherche avancée | ||
|
|
||
| Exemple : lister tous les noeuds non en production en appliquant les filtres suivants : | ||
|
|
||
| - **Statut** : Démonté, Inventaire, Échoué, Planifié | ||
| - **Rôle** : server | ||
|
|
||
| {.thumbnail} | ||
|
|
||
| Vous pouvez enregistrer la recherche pour la réutiliser plus tard. | ||
|
|
||
| ### 3. OpenStack Horizon – Ironic UI | ||
|
|
||
| #### 3.1 Accéder à l'interface Ironic | ||
|
|
||
| 1. Connectez-vous à l’URL d'administration `admin.dashboard` | ||
| 2. Cliquez sur **Horizon** | ||
| 3. Cliquez sur **Admin** | ||
| 4. Cliquez sur **System**, puis **Ironic Bare Metal Provisioning** | ||
|
|
||
| #### 3.2 Lister tous les noeuds | ||
|
|
||
| Dans **Ironic Bare Metal Provisioning**, vous pouvez voir tous les noeuds. | ||
|
|
||
| Vous pouvez filtrer les noeuds selon leur statut, par exemple : `Provisioning State = failed`. | ||
|
|
||
| {.thumbnail} | ||
|
|
||
| ### 4. État des ressources via OpenStack CLI | ||
|
|
||
| Le CLI OpenStack permet d’obtenir l’état **en temps réel** des ressources allouées et disponibles. | ||
|
|
||
| #### 4.1 Lister tous les noeuds | ||
|
|
||
| ```bash | ||
| openstack baremetal node list | ||
| ``` | ||
|
|
||
| **Exemple de sortie :** | ||
|
|
||
| ```bash | ||
| +--------------------------------------+----------------+--------------------------------------+-------------+--------------------+-------------+ | ||
| | UUID | Name | Instance UUID | Power State | Provisioning State | Maintenance | | ||
| +--------------------------------------+----------------+--------------------------------------+-------------+--------------------+-------------+ | ||
| | 88830859-5b16-4935-8f41-d381b754cbe5 | SERVER-1 | None | power off | available | False | | ||
| | 726bb7e9-3b20-4a44-99d7-2af747983781 | SERVER-2 | None | power off | available | False | | ||
| | af711edf-a579-491e-b474-3c03639ed99b | SERVER-3 | 83b7083b-bbdd-4327-941c-ee91197818c5 | power on | active | False | | ||
| +--------------------------------------+----------------+--------------------------------------+-------------+--------------------+-------------+ | ||
| ``` | ||
|
|
||
| #### 4.2 Filtrer les noeuds | ||
|
|
||
| Vous pouvez filtrer les résultats à l'aide de **--provision-state** pour voir les noeuds dans un statut spécifique, ou encore **--maintenance** pour voir les noeuds en maintenance. | ||
| Tous les filtres sont disponibles via `--help`. | ||
|
|
||
| **Exemple de sortie :** | ||
|
|
||
| ```bash | ||
| $ openstack baremetal node list --provision-state "clean failed" | ||
| +--------------------------------------+----------------+---------------+-------------+--------------------+-------------+ | ||
| | UUID | Name | Instance UUID | Power State | Provisioning State | Maintenance | | ||
| +--------------------------------------+----------------+---------------+-------------+--------------------+-------------+ | ||
| | 37f96160-16cf-47e6-8bee-0ee42a59fafe | SERVER-1 | None | power off | clean failed | False | | ||
| | 5678b6ff-1909-466f-857a-c8818a5ecd61 | SERVER-2 | None | power off | clean failed | False | | ||
| | cf5ee1ce-913a-4bff-a343-c391d8b3b667 | SERVER-3 | None | power off | clean failed | False | | ||
| +--------------------------------------+----------------+---------------+-------------+--------------------+-------------+ | ||
| ``` | ||
|
|
||
| ```bash | ||
| $ openstack baremetal node list --maintenance | ||
| +--------------------------------------+--------------+--------------------------------------+-------------+--------------------+-------------+ | ||
| | UUID | Name | Instance UUID | Power State | Provisioning State | Maintenance | | ||
| +--------------------------------------+--------------+--------------------------------------+-------------+--------------------+-------------+ | ||
| | 4e1108e1-3049-46fc-adb5-b27ba607710d | SERVER-4 | 9b972076-2c58-496b-9690-0f1b40d54660 | None | deploy failed | True | | ||
| +--------------------------------------+--------------+--------------------------------------+-------------+--------------------+-------------+ | ||
| ``` | ||
|
|
||
| #### 4.3 Détails d'un noeud | ||
|
|
||
| Pour récupérer toutes les informations concernant un noeud, par exemple pour identifier la dernière erreur et comprendre pourquoi le déploiement a échoué : | ||
|
|
||
| ```bash | ||
| openstack baremetal node show <node-id> | ||
| ``` | ||
|
|
||
| ## Notes & bonnes pratiques | ||
|
|
||
| - Vérifiez régulièrement Grafana pour anticiper la saturation des ressources et détecter les noeuds inactifs. | ||
ThibautOVH marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Utilisez NetBox comme **source de vérité** pour le matériel et les adresses IP. | ||
| - Documentez toujours les changements dans NetBox pour conserver un inventaire fiable. | ||
ThibautOVH marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
Binary file added
BIN
+82.1 KB
...ivate_cloud/opcp/how-to-see-node-inventory/images/01-grafana-dashboard-home.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+124 KB
...ivate_cloud/opcp/how-to-see-node-inventory/images/02-netbox-devices-filters.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+49.6 KB
...ate_cloud/opcp/how-to-see-node-inventory/images/03-openstack-horizon-ironic.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 2 additions & 0 deletions
2
pages/hosted_private_cloud/opcp/how-to-see-node-inventory/meta.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| id: f4fe93d1-bd94-4dd9-a443-4057f9c47ef7 | ||
| full_slug: opcp-node-inventory |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.