chore(sessiond): GRPC printing

[vikramgreddy]

Signed-off-by: Vikram G vikram.gurrappagaru@radisys.com

Summary

PrintGrpcMessage to DirectorydClient.cpp on request

Test Plan

make integ_test
make test session_manager

Additional Information

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[github-actions]

feg-workflow

    2 files  202 suites   37s ⏱️
371 tests 371 ✔️ 0 💤 0 ❌
385 runs  385 ✔️ 0 💤 0 ❌

Results for commit 6f04a68.

♻️ This comment has been updated with latest results.

[uri200]

Thanks @vikramgreddy.

This will print the request. We will also need to print the response.
Unfortunately the way CPP manages grpc message does not allow us to use the same strategy here, so using your IDE, please search all the instances where those functions are called and print the response. For example here
http://github.com/magma/magma/blob/master/lte/gateway/c/session_manager/SessionProxyResponderHandler.cpp#L78-L78

[uri200]

Also you can try to see the logs running S1AP test and enable grpc printing on sessiond.yml. To do that you could go your vagrant vm and change print_grpc_payload: True at /etc/magma/sessiond.yml. Then from your host (not vagrant) you can run

cd magma/lte/gateway
 fab integ_test:provision_vm=False,rerun_fails=0,no_build=True,skip_unit_tests=True

To run the test.

From your Vagrant VM you will be able to see sessiond logs using

sudo journalctl -fu magma@sessiond

In case you need it, you can add some extra prints to the function and rebuild sessiond to see if they print the message.

Note that using s1ap tester will be very useful on the future to test out stuff that can't be tested with unit test

[github-actions]

agw-workflow

     77 files     122 suites   6m 42s ⏱️
1 157 tests 1 153 ✔️ 4 💤 0 ❌
1 158 runs  1 154 ✔️ 4 💤 0 ❌

Results for commit 6f04a68.

♻️ This comment has been updated with latest results.