Skip to content

Conversation

SlimJ4
Copy link
Contributor

@SlimJ4 SlimJ4 commented Oct 3, 2025

What type of Pull Request is this?

  • New guide(s)

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

  • This Pull Request should not be merged before : 2025/11/17

@SlimJ4 SlimJ4 added the Guide creation The Pull Request contains at least 1 new guide (meta.yaml and index edition needed) label Oct 3, 2025
@Jessica41 Jessica41 self-assigned this Oct 3, 2025
@SlimJ4
Copy link
Contributor Author

SlimJ4 commented Oct 3, 2025

LAST MINUTE INFO :
The guide should not be published until the 10th of November (initially, it was to be published ASAP).

@Y0Coss Y0Coss added the Do not merge yet This Pull Request is awaiting a GO from product teams or has to be merged on a defined date. label Oct 3, 2025
@Y0Coss
Copy link
Collaborator

Y0Coss commented Oct 6, 2025

@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.

@SlimJ4
Copy link
Contributor Author

SlimJ4 commented Oct 9, 2025

@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.

SlimJ4 and others added 3 commits October 9, 2025 11:05
Removed the NIST storage wipe guide mistakenly included in this PR - it should have its own.
@Y0Coss
Copy link
Collaborator

Y0Coss commented Oct 10, 2025

LAST MINUTE INFO : The guide should not be published until the 10th of November (initially, it was to be published ASAP).

@SlimJ4 , is it November 10th or October 10th? (see the date you indicated in the PR description)

@SlimJ4
Copy link
Contributor Author

SlimJ4 commented Oct 10, 2025

@Y0Coss, I was definitely not in working shape when I posted this ! Second significant mistake here.
It was indeed November 10th, so 2025/11/10. I've been notified today that this is no longer the case, and this should not be merged before November 17th, so I updated the date (correctly this time).

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.
Copy link
Member

@sbraz sbraz Oct 21, 2025

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

Suggested change
- 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).
Copy link
Member

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use this transparent SVG, it'll look better
Architecture schema redesign

- Logical aggregations will be spread across **two distinct network cards** (with no physical cabling modification).
- Existing aggregations are not modified.

![Resilience comparison before/after](images/resilience_comparison.png){.thumbnail}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
![Resilience comparison before/after](images/resilience_comparison.png){.thumbnail}
![Before/after resilience comparison](images/resilience_comparison.png){.thumbnail}

SlimJ4 and others added 3 commits October 21, 2025 22:55
…-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>
SlimJ4 and others added 3 commits October 21, 2025 22:56
…-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.
@sbraz sbraz force-pushed the sa-lacp-resilience branch from 1d7311c to 061ef0e Compare October 23, 2025 17:04
@sbraz
Copy link
Member

sbraz commented Oct 23, 2025

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Do not merge yet This Pull Request is awaiting a GO from product teams or has to be merged on a defined date. Guide creation The Pull Request contains at least 1 new guide (meta.yaml and index edition needed)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants