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

One Node View #911

Open
vjeffrey opened this issue Jul 16, 2019 · 4 comments
Open

One Node View #911

vjeffrey opened this issue Jul 16, 2019 · 4 comments
Labels
Epic one node view requires planning Planning/storymapping for this epic has not yet been done.

Comments

@vjeffrey
Copy link

vjeffrey commented Jul 16, 2019

PROBLEM STATEMENT:

I want to be able to see the last ccr and scan status of all my nodes in one view.

Quickly understand the state of your nodes in a holistic way - one list view of all nodes, displaying node metadata, last run/scan status and end time, and a link to more details. Alert users of newly failing nodes.

This epic introduces new view in automate (possibly landing page?) that will give users a way to easily find nodes with failing scans/passing runs etc.

allows users to search by node metadata as well as penultimate and last scan and run status, combining any/all filters.

CUSTOMER IMPACT:

answers common questions for the users instead of making them ask/figure it out

ACCEPTANCE CRITERIA:

  • Show one page view of nodes for Infra, InSpec, and Applications services

  • The table will have the following values to view:

    • Node Name
    • Platform
    • Environment
    • Last Client Run (should link to details)
    • Last Scan (should link to details)
    • Service Status
  • Search bar

  • Sort on all table fields

  • page under "dashboards" top nav, side link called "Nodes" (?)

  • pagination! (100 rows per page. note this is not limited to the same 10k restrictions other list node views are limited to)

  • One node view will be under a feature flag

OUT OF SCOPE:

  • no gear icon on table
  • no download
  • no filter buttons
  • no status changes on search (static count)
  • no date ranges for search

TEST SCENARIO:

  • run a scan with audit cookbook
  • run a scan job
  • expect to see both nodes in the list
  • expect one node to have last ccr link and last scan link, one to only have last scan link

Aha! Link: https://chef.aha.io/epics/A2-E-98

@vjeffrey vjeffrey changed the title One Node View UI One Node View Jul 16, 2019
@vjeffrey vjeffrey added the requires planning Planning/storymapping for this epic has not yet been done. label Oct 4, 2019
@vjeffrey
Copy link
Author

vjeffrey commented Nov 19, 2019

notes from triad mtg november 19th:

  • search on node name, environment, platform
  • display those fields + last client run time + status & last scan time + status
  • sort on all table fields. sort under run and scan should be sorting by time not status
  • clicking on a client run or scan status/time link will lead do details page for that scan/run for that node
  • page under "dashboards" top nav, side link called "Nodes" (?)
  • pagination! (100 rows per page. note this is not limited to the same 10k restrictions other list node views are limited to)
  • no gear icon on table
  • no download
  • no status changes on search (static count)
  • no date ranges for search

the stuff that starts with "no" is to be possibly addressed at a later time

december 13:

  • add column for applications/service status per node

@vjeffrey
Copy link
Author

@alexpop had a great idea today -- a tooltip on the "last scan" and "last run" sections telling users what that means, for example for a user that only uses chef infra but not compliance and doesn't know what "last scan" is/how to do one

@vjeffrey
Copy link
Author

@jonong1972 what about allowing users to multi-select delete? that may be a nice feature to throw in as an easy way to clean up the nodes list as we start to expose data that was previously hidden...some users may have old/dup nodes they want to delete

@kmacgugan
Copy link

kmacgugan commented Jan 16, 2020

For infra nodes, node name is not a unique field, a node can be defined as a combination key of node name, org and chef server in the absence of a node ID. I think ideally we could get the node ID's and use a UUID to correlate nodes.

Here's some info about ID coordination in case it helps:
https://docs.google.com/document/d/1PAcw5nAXpywtyo6iql1UYpmb0rt2jYyb4aNAI8lLKds/edit

Hopefully this can help with some of the details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic one node view requires planning Planning/storymapping for this epic has not yet been done.
Projects
None yet
Development

No branches or pull requests

2 participants