Issue #6992 has been updated by Daniel Pittman.
...so, after spending some time working with Randall it seems like the stuff I had done is not, technically, incorrect, but is far from complete. The next required step is that we need to define an efficient mechanism in the model that gives us access to the count of resources by status, along with providing the global sum. Both of those should be pushed down to the database server: our target is 3K nodes, so we absolutely need pagination of the displayed data, and we don't want to pay the cost of fetching all 3K nodes for every page display. Randall and I agree that the likely best initial cut is to fetch the data on demand, and then we can precalculate at report insert time, if it seems appropriate. Get it right, then get it fast. ---------------------------------------- Feature #6992: Show lists of nodes with summary of resource status https://projects.puppetlabs.com/issues/6992 Author: Randall Hansen Status: Accepted Priority: Normal Assignee: Daniel Pittman Category: Target version: Keywords: Branch: https://github.com/daniel-pittman/puppet-dashboard/commits/feature/next/6537-be-able-to-tell-if-a-node-is-pending Affected URL: Affected Dashboard version: Show resource status summary. Group nodes by their status: * Failed (the default tab) * Pending * Unresponsive * Compliant * All For each node, show count of resources in interesting states, e.g.,: * Failed * Pending * Successful One possible implementation is attached. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
