Skip to content

[ansible][minigraph] Fix minigraph template for devices which have autoneg enabled but the topo file does not contain autoneg interfaces#15134

Merged
wangxin merged 3 commits intosonic-net:masterfrom
vdahiya12:dev/vdahiya/fix-non-autoneg
Oct 25, 2024
Merged

[ansible][minigraph] Fix minigraph template for devices which have autoneg enabled but the topo file does not contain autoneg interfaces#15134
wangxin merged 3 commits intosonic-net:masterfrom
vdahiya12:dev/vdahiya/fix-non-autoneg

Conversation

@vdahiya12
Copy link
Contributor

@vdahiya12 vdahiya12 commented Oct 24, 2024

Description of PR

This pull request updates the Jinja2 template minigraph_link_meta.j2 by modifying the generation of the section.

Key Changes:

  • The condition has been changed from simply checking if msft_an_enabled is defined to also checking if vm_topo_config.get('autoneg_interfaces') is not None.
  • This ensures that the section is only included if both msft_an_enabled is defined and the autoneg_interfaces attribute in vm_topo_config exists and is not None.

This ensures if some testbeds/devices have msft_an_enabled they do not end up treated as autoneg devices unless the topo file contains the AN interface list

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 202012
  • 202205
  • 202305
  • 202311
  • 202405

Approach

What is the motivation for this PR?

How did you do it?

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

…ellanox and add EOS 7260 template changes

Signed-off-by: Vaibhav Dahiya <[email protected]>
autoneg enabled but the topo file does not contain autoneg interfaces

Signed-off-by: Vaibhav Dahiya <[email protected]>
@mssonicbld
Copy link
Collaborator

@vdahiya12 PR conflicts with 202311 branch

@mssonicbld
Copy link
Collaborator

@vdahiya12 PR conflicts with 202405 branch

@mssonicbld
Copy link
Collaborator

@vdahiya12 PR conflicts with 202305 branch

vdahiya12 added a commit to vdahiya12/sonic-mgmt that referenced this pull request Oct 25, 2024
…toneg enabled but the topo file does not contain autoneg interfaces (sonic-net#15134)

This pull request updates the Jinja2 template minigraph_link_meta.j2 by modifying the generation of the section.

Key Changes:
* The condition has been changed from simply checking if msft_an_enabled is defined to also checking if vm_topo_config.get('autoneg_interfaces') is not None.
* This ensures that the section is only included if both msft_an_enabled is defined and the autoneg_interfaces attribute in vm_topo_config exists and is not None.

This ensures if some testbeds/devices have msft_an_enabled they do not end up treated as autoneg devices unless the topo file contains the AN interface list

Signed-off-by: Vaibhav Dahiya <[email protected]>
vdahiya12 added a commit to vdahiya12/sonic-mgmt that referenced this pull request Oct 25, 2024
…toneg enabled but the topo file does not contain autoneg interfaces (sonic-net#15134)

This pull request updates the Jinja2 template minigraph_link_meta.j2 by modifying the generation of the section.

Key Changes:
* The condition has been changed from simply checking if msft_an_enabled is defined to also checking if vm_topo_config.get('autoneg_interfaces') is not None.
* This ensures that the section is only included if both msft_an_enabled is defined and the autoneg_interfaces attribute in vm_topo_config exists and is not None.

This ensures if some testbeds/devices have msft_an_enabled they do not end up treated as autoneg devices unless the topo file contains the AN interface list

Signed-off-by: Vaibhav Dahiya <[email protected]>
@vdahiya12
Copy link
Contributor Author

#15195 fixes 202405 conflict

vdahiya12 added a commit to vdahiya12/sonic-mgmt that referenced this pull request Oct 28, 2024
…toneg enabled but the topo file does not contain autoneg interfaces (sonic-net#15134)

This pull request updates the Jinja2 template minigraph_link_meta.j2 by modifying the generation of the section.

Key Changes:
* The condition has been changed from simply checking if msft_an_enabled is defined to also checking if vm_topo_config.get('autoneg_interfaces') is not None.
* This ensures that the section is only included if both msft_an_enabled is defined and the autoneg_interfaces attribute in vm_topo_config exists and is not None.

This ensures if some testbeds/devices have msft_an_enabled they do not end up treated as autoneg devices unless the topo file contains the AN interface list

Signed-off-by: Vaibhav Dahiya <[email protected]>
vdahiya12 added a commit to vdahiya12/sonic-mgmt that referenced this pull request Oct 28, 2024
…toneg enabled but the topo file does not contain autoneg interfaces (sonic-net#15134)

This pull request updates the Jinja2 template minigraph_link_meta.j2 by modifying the generation of the section.

Key Changes:
* The condition has been changed from simply checking if msft_an_enabled is defined to also checking if vm_topo_config.get('autoneg_interfaces') is not None.
* This ensures that the section is only included if both msft_an_enabled is defined and the autoneg_interfaces attribute in vm_topo_config exists and is not None.

This ensures if some testbeds/devices have msft_an_enabled they do not end up treated as autoneg devices unless the topo file contains the AN interface list

Signed-off-by: Vaibhav Dahiya <[email protected]>
wangxin pushed a commit that referenced this pull request Oct 29, 2024
…toneg enabled but the topo file does not contain autoneg interfaces (#15134) (#15195)

This pull request updates the Jinja2 template minigraph_link_meta.j2 by modifying the generation of the section.

Key Changes:
* The condition has been changed from simply checking if msft_an_enabled is defined to also checking if vm_topo_config.get('autoneg_interfaces') is not None.
* This ensures that the section is only included if both msft_an_enabled is defined and the autoneg_interfaces attribute in vm_topo_config exists and is not None.

This ensures if some testbeds/devices have msft_an_enabled they do not end up treated as autoneg devices unless the topo file contains the AN interface list

Signed-off-by: Vaibhav Dahiya <[email protected]>
wangxin pushed a commit that referenced this pull request Oct 29, 2024
…aph templates and fanout EOS (#13990) (#15196)

* [ansible][minigraph] add support for adding autonegotiation in minigraph templates and fanout EOS (#13990)

These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible

Two things are required for autoneg support

1. autoneg_enabled : True
must be enabled in inventory files
2. t0 topo file must have a port list for autoneg
Example:
intfs : [1, 2, 3, 4, 5, 6, 7, 8]
With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up

Signed-off-by: Vaibhav Dahiya <[email protected]>

* [ansible][minigraph] enhance template for adding autonegotiation in Mellanox and add EOS 7260 template changes (#15004)

Signed-off-by: Vaibhav Dahiya <[email protected]>

* [ansible][minigraph] Fix minigraph template for devices which have autoneg enabled but the topo file does not contain autoneg interfaces (#15134)

This pull request updates the Jinja2 template minigraph_link_meta.j2 by modifying the generation of the section.

Key Changes:
* The condition has been changed from simply checking if msft_an_enabled is defined to also checking if vm_topo_config.get('autoneg_interfaces') is not None.
* This ensures that the section is only included if both msft_an_enabled is defined and the autoneg_interfaces attribute in vm_topo_config exists and is not None.

This ensures if some testbeds/devices have msft_an_enabled they do not end up treated as autoneg devices unless the topo file contains the AN interface list

Signed-off-by: Vaibhav Dahiya <[email protected]>
wangxin pushed a commit that referenced this pull request Oct 29, 2024
…ph templates and fanout EOS (#13990) (#15197)

* [ansible][minigraph] add support for adding autonegotiation in minigraph templates and fanout EOS (#13990)

These changes add a support for adding auto negotiation to specific testbed based on variables defined in ansible

Two things are required for autoneg support

1. autoneg_enabled : True
must be enabled in inventory files
2. t0 topo file must have a port list for autoneg
Example:
intfs : [1, 2, 3, 4, 5, 6, 7, 8]
With these changes the PR includes changes to pick the port numbering from topo file and apply minigraph parsing changes such that during deploy-mg or gen-mg the required ports have autoneg and deployment is clean with link up

Signed-off-by: Vaibhav Dahiya <[email protected]>

* [ansible][minigraph] enhance template for adding autonegotiation in Mellanox and add EOS 7260 template changes (#15004)

Signed-off-by: Vaibhav Dahiya <[email protected]>

* [ansible][minigraph] Fix minigraph template for devices which have autoneg enabled but the topo file does not contain autoneg interfaces (#15134)

This pull request updates the Jinja2 template minigraph_link_meta.j2 by modifying the generation of the section.

Key Changes:
* The condition has been changed from simply checking if msft_an_enabled is defined to also checking if vm_topo_config.get('autoneg_interfaces') is not None.
* This ensures that the section is only included if both msft_an_enabled is defined and the autoneg_interfaces attribute in vm_topo_config exists and is not None.

This ensures if some testbeds/devices have msft_an_enabled they do not end up treated as autoneg devices unless the topo file contains the AN interface list

Signed-off-by: Vaibhav Dahiya <[email protected]>
sreejithsreekumaran pushed a commit to sreejithsreekumaran/sonic-mgmt that referenced this pull request Nov 15, 2024
…toneg enabled but the topo file does not contain autoneg interfaces (sonic-net#15134)

This pull request updates the Jinja2 template minigraph_link_meta.j2 by modifying the generation of the section.

Key Changes:
* The condition has been changed from simply checking if msft_an_enabled is defined to also checking if vm_topo_config.get('autoneg_interfaces') is not None.
* This ensures that the section is only included if both msft_an_enabled is defined and the autoneg_interfaces attribute in vm_topo_config exists and is not None.

This ensures if some testbeds/devices have msft_an_enabled they do not end up treated as autoneg devices unless the topo file contains the AN interface list

Signed-off-by: Vaibhav Dahiya <[email protected]>
yutongzhang-microsoft pushed a commit to yutongzhang-microsoft/sonic-mgmt that referenced this pull request Nov 21, 2024
…toneg enabled but the topo file does not contain autoneg interfaces (sonic-net#15134)

This pull request updates the Jinja2 template minigraph_link_meta.j2 by modifying the generation of the section.

Key Changes:
* The condition has been changed from simply checking if msft_an_enabled is defined to also checking if vm_topo_config.get('autoneg_interfaces') is not None.
* This ensures that the section is only included if both msft_an_enabled is defined and the autoneg_interfaces attribute in vm_topo_config exists and is not None.

This ensures if some testbeds/devices have msft_an_enabled they do not end up treated as autoneg devices unless the topo file contains the AN interface list

Signed-off-by: Vaibhav Dahiya <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants