-
Notifications
You must be signed in to change notification settings - Fork 379
LACP Resilience update guide #8476
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
base: develop
Are you sure you want to change the base?
Conversation
LAST MINUTE INFO : |
@SlimJ4 , please make sure the 2nd guide from your PR contains also a meta.yaml and that the index contains the 2 created guides. BTW, the second guide should also be available in French. |
@Y0Coss , my mistake - this second guide is currently a WIP, and should not have been included in this PR. It already has a dedicated branch, and I think what happened is I mistakenly saved a version of this guide in this branch while switching branches. I will remove it ASAP. |
Removed the NIST storage wipe guide mistakenly included in this PR - it should have its own.
@SlimJ4 , is it November 10th or October 10th? (see the date you indicated in the PR description) |
@Y0Coss, I was definitely not in working shape when I posted this ! Second significant mistake here. |
pages/bare_metal_cloud/dedicated_servers/lacp-resilience-scale-hg/guide.fr-fr.md
Outdated
Show resolved
Hide resolved
Désormais : | ||
|
||
- Les agrégations logiques seront réparties sur **deux cartes réseau distinctes** (sans modification physique du câblage). | ||
- Les agrégations existantes ne sont pas modifiées. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
À mettre en premier élément de la liste et ajouer du gras
- Les agrégations existantes ne sont pas modifiées. | |
- Les agrégations existantes **ne sont pas modifiées**. |
|
||
Sous réserve d’une configuration correcte côté OS, cette évolution permet : | ||
|
||
- **Disponibilité renforcée** : meilleure tolérance aux pannes matérielles (cartes réseau, switches, connectique). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ça fait bizarre "permet disponibilité renforcée" sans article
pages/bare_metal_cloud/dedicated_servers/lacp-resilience-scale-hg/guide.fr-fr.md
Outdated
Show resolved
Hide resolved
pages/bare_metal_cloud/dedicated_servers/lacp-resilience-scale-hg/guide.en-gb.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pages/bare_metal_cloud/dedicated_servers/lacp-resilience-scale-hg/guide.fr-fr.md
Outdated
Show resolved
Hide resolved
- Logical aggregations will be spread across **two distinct network cards** (with no physical cabling modification). | ||
- Existing aggregations are not modified. | ||
|
||
{.thumbnail} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
{.thumbnail} | |
{.thumbnail} |
…-hg/guide.fr-fr.md Co-authored-by: Louis Sautier <sautier.louis@gmail.com>
…-hg/guide.fr-fr.md Co-authored-by: Louis Sautier <sautier.louis@gmail.com>
…-hg/guide.en-gb.md Co-authored-by: Louis Sautier <sautier.louis@gmail.com>
…-hg/guide.fr-fr.md Co-authored-by: Louis Sautier <sautier.louis@gmail.com>
Switched the picture to an svg file, small text edits to improve clarity.
1d7311c
to
061ef0e
Compare
@Y0Coss, @SlimJ4, j'ai fait quelques petits changements. Pouvez-vous faire une relecture et publier la documentation aujourd'hui ou demain ? On va finalement publier immédiatement car la communication envoyée aux clients contiendra un lien vers la page de documentation. On pourra toujours mettre à jour cette page par la suite si nécessaire. |
What type of Pull Request is this?
Description
This guide explains to OVHcloud clients how the new LACP update affects network connectivity resilience, and how to enable it on their existing infrastructure.
Mandatory information