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

group by fact #321

Open
anarcat opened this issue Apr 29, 2015 · 9 comments
Open

group by fact #321

anarcat opened this issue Apr 29, 2015 · 9 comments

Comments

@anarcat
Copy link

anarcat commented Apr 29, 2015

one thing that puppet-board does and puppet-dashboard doesn't is to allow grouping results by fact.

for example, this screenshot shows a report listing the puppetversion of all nodes in one view:

screenshot of puppetboard showing all nodes's puppetversion fact

is this something that works in puppet-dashboard or that is planned?

thanks

@sodabrew
Copy link
Owner

sodabrew commented Apr 29, 2015 via email

@anarcat
Copy link
Author

anarcat commented Apr 29, 2015

any advice on where one would start coding this? or UX recommndations should this be a new tab? i initially tried to make the "inventory search" do the right thing but it has to take a value for the fact and it displays only a static set of columns...

@sodabrew
Copy link
Owner

Is this for the Inventory view of nodes, or for displaying Variables across multiple nodes/classes/groups?

@anarcat
Copy link
Author

anarcat commented May 1, 2015

i don't quite care where it's done, really. :) the idea is to display the value of a single (or even better, multiple) fact(s) across multiple nodes.

@arnaudmm
Copy link

arnaudmm commented May 5, 2015

Let me elucidate something... To do that, puppetdashboard has to talk to puppetdb api hasn't it ?

Because puppetdashboard can't storeconfig, puppetdb is here for that.

Correct me if I'm wrong but I don't think puppetdashboard is (yet) puppetdb aware..

If you consider to do so, reports can also be stored (an retrieved) in(from) puppetdb. I don't know if it's a good idea. I'm currently using puppetdashboard as an ENC and puppetboard for digging into puppetdb datas (and import/export resources into it)

"Puppet enterprise dashboard" actually is a mix of your puppet dasbhoard and puppetboard. So I think a call has to be done here:

  • use puppetdashboard for ENC fonctionnality only AND use puppetboard for catalog/fact/reports explorations.
  • or try to "merge" projects to do the same than puppet enterprise dashboard

What do you think about this ? @sodabrew

@anarcat
Copy link
Author

anarcat commented May 5, 2015

hmm... i believe puppet-dashboard already talks to puppetdb, at least i had to install it as a dependency when i setup puppet-dashboard.

no?

@sodabrew
Copy link
Owner

sodabrew commented May 5, 2015 via email

@arnaudmm
Copy link

arnaudmm commented May 6, 2015

Yeah that is what I was thinking. Would be great to have a project doing
both : getting informations from puppetdb and being an ENC :-)

It's a big change and it comes with design consideration

2015-05-05 22:38 GMT+02:00 Aaron Stone [email protected]:

Negative, puppet dashboard doesn't talk to puppetdb at this time. Pull
requests welcome!!


Reply to this email directly or view it on GitHub
#321 (comment)
.

@anarcat
Copy link
Author

anarcat commented May 14, 2015

that's really weird: for some reason i configured puppetdb first here:

http://isuma-media-players.readthedocs.org/en/latest/configmanagement.html#configuring-a-dashboard

maybe i was confused with puppetboard? anyways, it seems it can run alongside puppetdb fine right now :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants