Jira (PDB-1820) Include 'status' field in 'nodes' endpoint

1 view
Skip to first unread message

David McCauley (JIRA)

unread,
Jul 23, 2015, 6:18:06 AM7/23/15
to puppe...@googlegroups.com
David McCauley created an issue
 
PuppetDB / New Feature PDB-1820
Include 'status' field in 'nodes' endpoint
Issue Type: New Feature New Feature
Affects Versions: PDB 3.0.0
Assignee: Unassigned
Components: PE
Created: 2015/07/23 3:17 AM
Priority: Normal Normal
Reporter: David McCauley

Currently in PE we display a view of all available nodes in a table. A column of this table is the 'run status' of a given node.

To acquire the data for this table we first make a call to the 'nodes' endpoint for all of the data except the 'run status' where we make a separate request to the 'reports'. We then combine this data and pass it to the UI.

It would help us greatly if a new 'node' endpoint were to contain this 'status' field from the latest report. We would like to be able to run filter queries upon this field and page on this new endpoint if possible.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Atlassian logo

Karel Brezina (JIRA)

unread,
Aug 4, 2015, 11:59:06 AM8/4/15
to puppe...@googlegroups.com
Karel Brezina commented on New Feature PDB-1820
 
Re: Include 'status' field in 'nodes' endpoint

'run status' can contain the following values:

  • "changed", "failed", "noop", "unchanged" - based on the latest report status
  • "unreported" - when no report exists
  • "unresponsive" - when no report has arrived within a given time period

Similarly, as in https://github.com/puppetlabs/pe-puppetdb-extensions/blob/master/documentation/api/pe/v1/state-overview.markdown.

The endpoint should support:

  • pagination by limit & offset parameters
  • filtering on facts and status
  • sorting

Wyatt Alt (JIRA)

unread,
Aug 11, 2015, 2:20:09 PM8/11/15
to puppe...@googlegroups.com
Wyatt Alt commented on New Feature PDB-1820

Karel Brezina David McCauley I think this should include the report hash as well as status, right?

Wyatt Alt (JIRA)

unread,
Aug 11, 2015, 2:21:09 PM8/11/15
to puppe...@googlegroups.com
Wyatt Alt updated an issue
 
Change By: Wyatt Alt
Fix Version/s: PDB 3.2.0

Jonathan Newman (JIRA)

unread,
Aug 11, 2015, 2:24:04 PM8/11/15
to puppe...@googlegroups.com

Scott Walker (JIRA)

unread,
Aug 12, 2015, 3:58:06 AM8/12/15
to puppe...@googlegroups.com
Scott Walker commented on New Feature PDB-1820

I don't think we need the endpoint to support filtering - we layer our filtering on top of it. We can also infer unresponsive based on time. I think we're good if we can have a /v4/nodes endpoints that includes actual latest report status (i.e. no direct support for "unresponsive" or "unreported") and the report hash.

Jonathan Newman (JIRA)

unread,
Aug 12, 2015, 11:00:20 AM8/12/15
to puppe...@googlegroups.com

Wyatt Alt Just to be clear, we are talking about augmenting the existing nodes endpoint with some additional data, not creating a new one?

Wyatt Alt (JIRA)

unread,
Aug 12, 2015, 11:20:11 AM8/12/15
to puppe...@googlegroups.com
Wyatt Alt commented on New Feature PDB-1820

Jonathan Newman same endpoint

Wyatt Alt (JIRA)

unread,
Aug 12, 2015, 11:21:15 AM8/12/15
to puppe...@googlegroups.com
Wyatt Alt updated an issue
Change By: Wyatt Alt
Currently in PE we display a view of all available nodes in a table. A column of this table is the 'run status' of a given node.

To acquire the data for this table we first make a call to the 'nodes' endpoint for all of the data except the 'run status' where we make a separate request to the 'reports'. We then combine this data and pass it to the UI.

It would help us greatly if  a new  the  ' node nodes ' endpoint were to contain this 'status' field from the latest report. We would like to be able to run filter queries upon this field and page on this new endpoint if possible.

Wyatt Alt (JIRA)

unread,
Aug 12, 2015, 11:21:18 AM8/12/15
to puppe...@googlegroups.com
Wyatt Alt commented on New Feature PDB-1820
 
Re: Include 'status' field in 'nodes' endpoint

updated the description to reflect that

Jonathan Newman (JIRA)

unread,
Aug 12, 2015, 11:39:51 AM8/12/15
to puppe...@googlegroups.com

Thanks!

Wyatt Alt (JIRA)

unread,
Aug 18, 2015, 12:33:09 PM8/18/15
to puppe...@googlegroups.com
Wyatt Alt updated an issue
Change By: Wyatt Alt
Story Points: 1

Wyatt Alt (JIRA)

unread,
Aug 18, 2015, 12:33:12 PM8/18/15
to puppe...@googlegroups.com
Wyatt Alt updated an issue
Change By: Wyatt Alt
Sprint: PuppetDB 2015-08-26

Wyatt Alt (JIRA)

unread,
Aug 18, 2015, 12:33:16 PM8/18/15
to puppe...@googlegroups.com
Wyatt Alt assigned an issue to Wyatt Alt
Change By: Wyatt Alt
Assignee: Wyatt Alt

Wyatt Alt (JIRA)

unread,
Aug 25, 2015, 3:43:07 PM8/25/15
to puppe...@googlegroups.com
Wyatt Alt updated an issue
Change By: Wyatt Alt
Scope Change Category: Adopted
Scope Change Reason: had time, blocking UI work

Wyatt Alt (JIRA)

unread,
Aug 26, 2015, 11:40:10 AM8/26/15
to puppe...@googlegroups.com

David McCauley (JIRA)

unread,
Aug 26, 2015, 12:43:06 PM8/26/15
to puppe...@googlegroups.com

Kurt Wall (JIRA)

unread,
Oct 1, 2015, 2:58:09 PM10/1/15
to puppe...@googlegroups.com
Kurt Wall updated an issue
 
Change By: Kurt Wall
QA Status: Reviewed
QA Risk Assessment: Low
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Atlassian logo

Claudia Petty (Jira)

unread,
Jun 21, 2023, 11:03:14 AM6/21/23
to puppe...@googlegroups.com
Claudia Petty updated an issue
Change By: Claudia Petty
Labels: new-feature
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages