-
Notifications
You must be signed in to change notification settings - Fork 79
Add support for callhome to RNC application #2242
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @Tobianas, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request introduces support for NETCONF callhome functionality into the RNC application. The changes enable the RNC module to initiate connections back to a NETCONF server, enhancing its network management capabilities by allowing devices to 'call home' to the controller. This involves integrating the necessary callhome plugin, configuring its startup, and ensuring its graceful shutdown within the RNC module's lifecycle.
Highlights
- Callhome Plugin Integration: The RNC Lighty Module now imports and utilizes
NetconfCallhomePlugin
andNetconfCallhomePluginBuilder
classes, indicating the introduction of NETCONF callhome capabilities. - Module Initialization and Configuration: A
NetconfCallhomePlugin
instance is initialized and started within theinitModules()
method ofRncLightyModule
. It is configured using existinglightyController
services,NetconfConfiguration
,RestConfConfiguration
's host address, and a hardcoded port4334
. - Error Handling and Resource Management: New exception handling for
ExecutionException
,InterruptedException
, andTimeoutException
has been added specifically for callhome plugin initialization. Additionally, theclose()
method now includes logic to properly shut down theNetconfCallhomePlugin
instance, ensuring resource cleanup.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request adds support for NETCONF call-home functionality to the RNC application. The changes correctly initialize and shut down the call-home plugin. However, I've identified a few issues that should be addressed:
- Error handling for call-home initialization is incorrect; it reports success even on failure.
- The shutdown process for the call-home plugin doesn't check for success, which could hide resource cleanup issues.
I've provided detailed comments and suggestions to fix these issues.
...gator/lighty-rnc-module/src/main/java/io/lighty/applications/rnc/module/RncLightyModule.java
Outdated
Show resolved
Hide resolved
...gator/lighty-rnc-module/src/main/java/io/lighty/applications/rnc/module/RncLightyModule.java
Outdated
Show resolved
Hide resolved
f40d207
to
1be7810
Compare
...gator/lighty-rnc-module/src/main/java/io/lighty/applications/rnc/module/RncLightyModule.java
Outdated
Show resolved
Hide resolved
...etconf-sb/src/main/java/io/lighty/modules/southbound/netconf/impl/NetconfCallhomePlugin.java
Outdated
Show resolved
Hide resolved
...ty-modules/lighty-jetty-server/src/main/java/io/lighty/server/config/LightyServerConfig.java
Show resolved
Hide resolved
Add support for callhome in RNC application as described in lighty-netconf-sb README file. To use callhome, user still needs to add odl-netconf-callhome-server. JIRA: LIGHTY-375 Signed-off-by: tobias.pobocik <tobias.pobocik@pantheon.tech>
Port was unused and hard-coded. This patch adds ability to configure the callhome port using config file. By default, the callhome port is set to 4334 JIRA: LIGHTY-375 Signed-off-by: tobias.pobocik <tobias.pobocik@pantheon.tech>
Add support for callhome in RNC application as described in lighty-netconf-sb README file. To use callhome, user still needs to add odl-netconf-callhome-server.