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
feat(nms): Enable federation mapping configuration capability on federated LTE networks #11952
Conversation
Thanks for opening a PR! 💯
Howto
More infoPlease take a moment to read through the Magma project's
If this is your first Magma PR, also consider reading
|
nms/packages/magmalte/app/views/equipment/FEGGatewayDetailConfig.js
Outdated
Show resolved
Hide resolved
nms/packages/magmalte/app/views/network/NetworkFederationConfig.js
Outdated
Show resolved
Hide resolved
nms/packages/magmalte/app/views/network/NetworkFederationConfig.js
Outdated
Show resolved
Hide resolved
Looks good to me, but the tests need to be adapted https://github.com/magma/magma/runs/5415473763?check_suite_focus=true |
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.
See comment above
const classes = useStyles(); | ||
const {values} = props; | ||
const onChange = field => event => | ||
// $FlowFixMe Set state for each field |
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.
Unexpected '$FlowFixMe' comment: '$FlowFixMe Set state for each field'.
@@ -54,6 +55,8 @@ export default function FEGGatewayConfig() { | |||
const ctx = useContext(FEGGatewayContext); | |||
const gwInfo: federation_gateway = ctx.state[gatewayId]; | |||
|
|||
console.log('gwInfo:', gwInfo); |
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.
Unexpected console statement.
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.
The test were actually broken for a reason.
I fixed the bug so that we can finally merge this.
Signed-off-by: Andrei Lee <andreilee@fb.com>
Signed-off-by: Thomas Schmitt <thomas.schmitt@tngtech.com>
…rated LTE networks (magma#11952) * feat(nms): Add federated mode mapping capability Signed-off-by: Andrei Lee <andreilee@fb.com> * feat(nms): Only show federation tab for FEG_LTE networks Signed-off-by: Thomas Schmitt <thomas.schmitt@tngtech.com> Co-authored-by: Thomas Schmitt <thomas.schmitt@tngtech.com>
Summary
This bridges a gap in feature parity between the Orc8r API and NMS.
Enables the ability to configure routing for a federated LTE network, as specified here.
This screenshot shows the addition of additional configuration displayed in the network page for a federated LTE network, specifically "Federated Mapping Mode"
Clicking the "Edit" button, opens up a modal for configuring the federated LTE network. A new tab has been added, labeled "Federation":
There is also the capability to configure the routing/mappings for federation purposes:
Test Plan
Checked enabling/disabling mapping mode
Checked adding/editing/deleting mappings, and persistence across page refreshes, and consistency with direct access through Orc8r API
Additional Information