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

Support TCP and UDP connectivity testing from miniccc #1457

Merged
merged 1 commit into from
Oct 6, 2021

Conversation

activeshadow
Copy link
Contributor

minimega, miniccc, and ron were updated to support executing tcp/udp
connectivity tests directly from miniccc agents.

ron was updated to include a new ConnTest command struct that
encapsulates the endpoint to test against, how long to wait, and what
UDP packet to send (if necessary).

miniccc was updated to include a handler for the new ConnTest command
that simply tries to dial the endpoint (in the case of TCP), and if
necessary write the UDP packet to the socket (in the case of UDP).

minimega was updated to include support for a new "cc test-conn"
command, as well as adding a "connectivity" column to the "cc commands"
table.

Documentation for minimega's "cc" command was also updated to include
details and examples of how to use the new "test-conn" command.

minimega, miniccc, and ron were updated to support executing tcp/udp
connectivity tests directly from miniccc agents.

ron was updated to include a new `ConnTest` command struct that
encapsulates the endpoint to test against, how long to wait, and what
UDP packet to send (if necessary).

miniccc was updated to include a handler for the new `ConnTest` command
that simply tries to dial the endpoint (in the case of TCP), and if
necessary write the UDP packet to the socket (in the case of UDP).

minimega was updated to include support for a new "cc test-conn"
command, as well as adding a "connectivity" column to the "cc commands"
table.

Documentation for minimega's "cc" command was also updated to include
details and examples of how to use the new "test-conn" command.
@activeshadow
Copy link
Contributor Author

The reason for this new miniccc feature is to support connectivity testing without having to require certain executables to be available in target VMs and/or having to add a custom executable to VMs when the miniccc agent is already present in all the VMs. The main driver for connectivity testing is the state of health app available in phenix.

@aherna aherna self-assigned this Aug 23, 2021
Copy link
Contributor

@aherna aherna left a comment

Choose a reason for hiding this comment

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

Having issues on connectivity test with containers, getting no responses but can other wise use miniccc @activeshadow

@activeshadow
Copy link
Contributor Author

Having issues on connectivity test with containers, getting no responses but can other wise use miniccc @activeshadow

@aherna can you provide a little more detail about how you're testing and what you're seeing? For example, is the issue with testing connectivity to a container from a VM, or to a VM from a container, or to a container from a container? Is the target VM/container running a service on the protocol/port your testing connectivity to?

Copy link
Contributor

@aherna aherna left a comment

Choose a reason for hiding this comment

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

LGTM

@aherna aherna merged commit cb60299 into sandia-minimega:master Oct 6, 2021
@activeshadow activeshadow deleted the tcp-conn-test branch October 26, 2021 16:22
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.

2 participants