Skip to content
This repository has been archived by the owner on Mar 31, 2023. It is now read-only.

Remove cache access from NCM gRPC client #735

Open
xieus opened this issue Jan 31, 2022 · 0 comments · May be fixed by #740
Open

Remove cache access from NCM gRPC client #735

xieus opened this issue Jan 31, 2022 · 0 comments · May be fixed by #740
Assignees
Labels
enhancement New feature or request

Comments

@xieus
Copy link
Contributor

xieus commented Jan 31, 2022

In the services/network_config_manager/src/main/java/com/futurewei/alcor/netwconfigmanager/client/gRPC/GoalStateClientImpl.java, the GS gRPC client calls the ResourceStateCache service which further access Resource State Cache.

Ideally, we would like to have a gRPC client free of any database/cache access and handle only the Goal State communication.

The DB access should be moved to the upper level service layer, which packs DB information, calls gRPC client with the requested db information.

@xieus xieus added the enhancement New feature or request label Jan 31, 2022
@DavidLiu506 DavidLiu506 linked a pull request Feb 4, 2022 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants