Skip to content
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

[dhcp_relay] DHCPv6 automatic test #3565

Merged
merged 2 commits into from
Jul 8, 2021
Merged

[dhcp_relay] DHCPv6 automatic test #3565

merged 2 commits into from
Jul 8, 2021

Conversation

shlomibitton
Copy link
Contributor

@shlomibitton shlomibitton commented Jun 1, 2021

Description of PR

Summary:
DHCPv6 infrastructure and automatic test.

Type of change

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

Approach

What is the motivation for this PR?

Add DHCPv6 automatic test infrastructure and PTF test.

How did you do it?

Enhance the minigraph_facts.py and minigraph_dpg.j2 to support DHCPv6 instances.
Add DHCPv6 servers to lab.yml file.
This will deploy on a DUT DHCPv6 servers on regression run.
Develop a test with 3 test cases:

  • test_dhcp_relay_default
  • test_dhcp_relay_after_link_flap
  • test_dhcp_relay_start_with_uplinks_down

Develop a PTF runner test to simulate the traffic according to the test case from sonic-mgmt.

How did you verify/test it?

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

T0

@shlomibitton shlomibitton requested a review from a team as a code owner June 1, 2021 11:38
Add DHCPv6 PTF test
Add infrastructure for generating minigraph xml file with DHCPv6 servers

Change-Id: I8ae4feea5d47bf512c84a160757288a5d3376cf5
Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>
@lgtm-com
Copy link

lgtm-com bot commented Jun 1, 2021

This pull request introduces 4 alerts when merging bc239b4 into 79b9e47 - view on LGTM.com

new alerts:

  • 4 for Variable defined multiple times

@wangxin
Copy link
Collaborator

wangxin commented Jun 3, 2021

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@wangxin
Copy link
Collaborator

wangxin commented Jun 28, 2021

@shlomibitton Can you fix the LGTM alerts 4 for Variable defined multiple times?

@shlomibitton
Copy link
Contributor Author

shlomibitton commented Jun 28, 2021

@shlomibitton Can you fix the LGTM alerts 4 for Variable defined multiple times?

@wangxin Fixed

@tahmed-dev tahmed-dev requested a review from kellyyeh July 1, 2021 16:51
@tahmed-dev
Copy link
Contributor

@kellyyeh, please review this PR.

Copy link
Contributor

@kellyyeh kellyyeh left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks for your work!

@wangxin wangxin merged commit cf45c59 into sonic-net:master Jul 8, 2021
wangxin added a commit that referenced this pull request Jul 9, 2021
bingwang-ms pushed a commit that referenced this pull request Jul 9, 2021
lguohan pushed a commit to sonic-net/sonic-buildimage that referenced this pull request Jul 16, 2021
Why I did it
Currently SONiC use the 'isc-dhcp-relay' package to allow DHCP relay functionality on IPv4 networks only.
This will allow the IPv6 functionality along the IPv4 type.

How I did it
Edit supervisord template to start DHCPv6 instances when configured to do so on Config DB.
Align cfg unit test to the new change.
Add DHCPv6 relay minigraph parsing support and a suitable t0 topology xml file for UT.

How to verify it
Configure DHCPv6 agents as described on the feature HLD: sonic-net/SONiC#765
Test it with real client/server with IPv6 or use the dedicated automatic test: sonic-net/sonic-mgmt#3565
Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>

* Split docker-dhcp-relay.supervisord.conf.j2 template into several files for easier code maintenance
judyjoseph pushed a commit to sonic-net/sonic-buildimage that referenced this pull request Aug 4, 2021
Why I did it
Currently SONiC use the 'isc-dhcp-relay' package to allow DHCP relay functionality on IPv4 networks only.
This will allow the IPv6 functionality along the IPv4 type.

How I did it
Edit supervisord template to start DHCPv6 instances when configured to do so on Config DB.
Align cfg unit test to the new change.
Add DHCPv6 relay minigraph parsing support and a suitable t0 topology xml file for UT.

How to verify it
Configure DHCPv6 agents as described on the feature HLD: sonic-net/SONiC#765
Test it with real client/server with IPv6 or use the dedicated automatic test: sonic-net/sonic-mgmt#3565
Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>

* Split docker-dhcp-relay.supervisord.conf.j2 template into several files for easier code maintenance
carl-nokia pushed a commit to carl-nokia/sonic-buildimage that referenced this pull request Aug 7, 2021
Why I did it
Currently SONiC use the 'isc-dhcp-relay' package to allow DHCP relay functionality on IPv4 networks only.
This will allow the IPv6 functionality along the IPv4 type.

How I did it
Edit supervisord template to start DHCPv6 instances when configured to do so on Config DB.
Align cfg unit test to the new change.
Add DHCPv6 relay minigraph parsing support and a suitable t0 topology xml file for UT.

How to verify it
Configure DHCPv6 agents as described on the feature HLD: sonic-net/SONiC#765
Test it with real client/server with IPv6 or use the dedicated automatic test: sonic-net/sonic-mgmt#3565
Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>

* Split docker-dhcp-relay.supervisord.conf.j2 template into several files for easier code maintenance
vmittal-msft pushed a commit to vmittal-msft/sonic-mgmt that referenced this pull request Sep 28, 2021
What is the motivation for this PR?
Add DHCPv6 automatic test infrastructure and PTF test.

How did you do it?
Enhance the minigraph_facts.py and minigraph_dpg.j2 to support DHCPv6 instances.
Add DHCPv6 servers to lab.yml file.
This will deploy on a DUT DHCPv6 servers on regression run.
Develop a test with 3 test cases:

test_dhcp_relay_default
test_dhcp_relay_after_link_flap
test_dhcp_relay_start_with_uplinks_down
Develop a PTF runner test to simulate the traffic according to the test case from sonic-mgmt.

How did you verify/test it?
Use testbed-cli.sh to generate and deploy a minigraph with DHCPv6 instances on a switch.
Run the test.
This test depends on PR: [dhcp_relay] DHCP relay support for IPv6 sonic-buildimage#7772

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

Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>
vmittal-msft pushed a commit to vmittal-msft/sonic-mgmt that referenced this pull request Sep 28, 2021
kellyyeh pushed a commit to kellyyeh/sonic-buildimage that referenced this pull request Sep 29, 2021
Why I did it
Currently SONiC use the 'isc-dhcp-relay' package to allow DHCP relay functionality on IPv4 networks only.
This will allow the IPv6 functionality along the IPv4 type.

How I did it
Edit supervisord template to start DHCPv6 instances when configured to do so on Config DB.
Align cfg unit test to the new change.
Add DHCPv6 relay minigraph parsing support and a suitable t0 topology xml file for UT.

How to verify it
Configure DHCPv6 agents as described on the feature HLD: sonic-net/SONiC#765
Test it with real client/server with IPv6 or use the dedicated automatic test: sonic-net/sonic-mgmt#3565
Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>

* Split docker-dhcp-relay.supervisord.conf.j2 template into several files for easier code maintenance

(cherry picked from commit 604becd)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants