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

[AGW + Orc8r] Replace subscriberDB streaming when EPS authentication service is active #13249

Open
3 of 5 tasks
ssanadhya opened this issue Jul 8, 2022 · 6 comments
Open
3 of 5 tasks
Assignees
Labels
component: agw Access gateway-related issue component: orc8r Orchestrator-related issue

Comments

@ssanadhya
Copy link
Collaborator

ssanadhya commented Jul 8, 2022

In order to address #12907, #13048 adds logic to enable EPS authentication service in Orc8r whenever the CloudSubscriberdbEnabled flag is set to true.

When EPS authentication service is enabled, the Orc8r needs to stop streaming subscriber information to Subscriberdb on AGW. As part of this change, the APN specific configs, such as static IP address(es), vlan-id, etc, which are needed by Mobilityd on AGW will not be streamed.

This issue tracks the steps needed to make the config available to Mobilityd when EPS authentication service is used for authentication instead of AGW's SubscriberDB. Specifically,

@ssanadhya ssanadhya changed the title [AGW + Orc8r] Remove subscriberDB streaming when EPS authentication service is active [AGW + Orc8r] Replace subscriberDB streaming when EPS authentication service is active Jul 8, 2022
@stale stale bot added the wontfix This will not be worked on label Oct 17, 2022
@lucasgonze
Copy link
Contributor

lucasgonze commented Oct 31, 2022

This got bogged down when Varun left. The remaining work needs an owner.

Only remaining tasks are adding:

  • integration tests for CI
  • documentation

@stale stale bot removed the wontfix This will not be worked on label Oct 31, 2022
@magma magma deleted a comment from stale bot Nov 2, 2022
@sebathomas
Copy link
Contributor

@ssanadhya

Do we have some more information about the content of the changes that needs to be documented? Is everything in this ticket, the linked security issue, and the linked PRs?

Also, which features should be tested? I assume this would need to be a federated integration test since it involves AGW and Orc8r?

@sebathomas
Copy link
Contributor

It looks like #13252 and #13251 are not done but were closed by the stalebot. So there is probably more left to do than writing tests and documentation.

@lucasgonze
Copy link
Contributor

@sebathomas are you comfortable owning #13251?

@sebathomas
Copy link
Contributor

Yes, we'll estimate it in the team tomorrow.

@sebathomas
Copy link
Contributor

And I added another subtask for documentation + tests.

@nstng nstng added component: orc8r Orchestrator-related issue component: agw Access gateway-related issue labels Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: agw Access gateway-related issue component: orc8r Orchestrator-related issue
Projects
None yet
Development

No branches or pull requests

6 participants