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

Update the Client Runs to use the node-manager #494

Open
lancewf opened this issue Jun 4, 2019 · 2 comments
Open

Update the Client Runs to use the node-manager #494

lancewf opened this issue Jun 4, 2019 · 2 comments
Labels
automate-ui tech debt This issue addresses tech debt in our code base

Comments

@lancewf
Copy link
Contributor

lancewf commented Jun 4, 2019

User Story

Update the Client Runs page to use node data from the node-manager. This is a start in moving away from the node-state index in elasticsearch. This is also a start in combining node information from the compliance pages with Client Runs pages.

Benefits:

  • Allows pagination of over 10,000 nodes
  • Mapping/table migrations
  • IAMv2 Project updates
  • Relational Database features

Research Areas:

  • Suggestions from the search bar

Tasks:

This can be completed in separate PRs.

  • Node List
  • Node counts
  • Suggestions
  • Node Export

Definition of Done

The Client Runs node list page will pull all its information from the node-manager and not the config-mgmt-service.

Demo Script / Repro Steps

  1. Add nodes
  2. Open the Client Runs page
  3. Ensure all information is correctly displayed.
@lancewf lancewf added the tech debt This issue addresses tech debt in our code base label Jun 4, 2019
@vjeffrey
Copy link

vjeffrey commented Jun 6, 2019

Another research area might be how to handle the whole "missing nodes" thing

@lancewf
Copy link
Contributor Author

lancewf commented Jun 20, 2019

This task will have to be done after this one is complete. #616

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automate-ui tech debt This issue addresses tech debt in our code base
Projects
None yet
Development

No branches or pull requests

2 participants