Skip to content

Stop exabgp processes before remove PTF container (for both old and new exabgp process naming convention)#7587

Merged
lizhijianrd merged 2 commits intosonic-net:masterfrom
lizhijianrd:fix-remove-topo-0227
Feb 28, 2023
Merged

Stop exabgp processes before remove PTF container (for both old and new exabgp process naming convention)#7587
lizhijianrd merged 2 commits intosonic-net:masterfrom
lizhijianrd:fix-remove-topo-0227

Conversation

@lizhijianrd
Copy link
Contributor

@lizhijianrd lizhijianrd commented Feb 27, 2023

Description of PR

Summary:
While removing topo of a testbed, we have to ensure that all the exabgp processes are stopped before PTF container be removed:

  • For old naming convention, exabgp processes are named like exabgp-ARISTA01T0 and exabgp-ARISTA01T0-v6.
  • For new naming convention, exabgp processes are named like exabgpv4:exabgp-ARISTA01T0 and exabgpv6:exabgp-ARISTA01T0-v6.

In this PR, I added some check to ensure both type of exabgp processes are stopped.

Type of change

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

Back port request

  • 201911
  • 202012
  • 202205

Approach

What is the motivation for this PR?

Ensure all the exabgp processes are stopped before PTF container be removed.

How did you do it?

  1. For the new naming convention, use ansible supervisor module to stop process group exabgpv4 and exabgpv6.
  2. For the old naming convention, use exabgp.py library to stop processes one by one.

How did you verify/test it?

Verified on both type of PTF containers.

Any platform specific information?

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

Documentation

@lizhijianrd lizhijianrd merged commit 37273ae into sonic-net:master Feb 28, 2023
@lizhijianrd lizhijianrd deleted the fix-remove-topo-0227 branch February 28, 2023 00:51
wangxin pushed a commit that referenced this pull request Feb 28, 2023
…ew exabgp process naming convention) (#7587)

What is the motivation for this PR?
While removing topo of a testbed, we have to ensure that all the exabgp processes are stopped before PTF container be removed:
* For old naming convention, exabgp processes are named like exabgp-ARISTA01T0 and exabgp-ARISTA01T0-v6.
* For new naming convention, exabgp processes are named like exabgpv4:exabgp-ARISTA01T0 and exabgpv6:exabgp-ARISTA01T0-v6.
In this PR, I added some check to ensure both type of exabgp processes are stopped.

How did you do it?
1. For the new naming convention, use ansible supervisor module to stop process group exabgpv4 and exabgpv6.
2. For the old naming convention, use exabgp.py library to stop processes one by one.

How did you verify/test it?
Verified on both type of PTF containers.

Signed-off-by: Zhijian Li <[email protected]>
wangxin pushed a commit that referenced this pull request Feb 28, 2023
…ew exabgp process naming convention) (#7587)

What is the motivation for this PR?
While removing topo of a testbed, we have to ensure that all the exabgp processes are stopped before PTF container be removed:
* For old naming convention, exabgp processes are named like exabgp-ARISTA01T0 and exabgp-ARISTA01T0-v6.
* For new naming convention, exabgp processes are named like exabgpv4:exabgp-ARISTA01T0 and exabgpv6:exabgp-ARISTA01T0-v6.
In this PR, I added some check to ensure both type of exabgp processes are stopped.

How did you do it?
1. For the new naming convention, use ansible supervisor module to stop process group exabgpv4 and exabgpv6.
2. For the old naming convention, use exabgp.py library to stop processes one by one.

How did you verify/test it?
Verified on both type of PTF containers.

Signed-off-by: Zhijian Li <[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.

2 participants