Hello everyone,
It’s a lovely grey and rainy day here in the Dutch summer, as good a day as any to release a new little project.
Its name is Puppetboard and has as aim to replace Puppet Dashboard’s reporting functionality. It does not nor will it include ENC features. It does all this without storing any data itself but querying PuppetDB instead.
The whole thing is built in Python and relies on Flask and WTForms. The communication logic has been split of in its own library called pypuppetdb which makes heavy use of the requests library. The interface is powered by Twitter Bootstrap with the Flatly theme.
Though I’ve pushed all the code out and made it public it’s all very young but it works fairly well. However, I’ve committed numerous barbarities in the code just to get things working and to figure out how to handle certain things. For the foreseeable time in the future I’ll be working on cleaning all this up and figuring out what I can do on my side and on PuppetDB’s side to make all this work a little better. Especially when it comes to dealing with big responses from PuppetDB...
This is the first time I’m open sourcing a project so that too is all new to me. I’d welcome the feedback and if someone feels brave enough even commits on the projects but try and be gentle about it :-). I’ll also be at PuppetConf including the Developer Day so feel free to reach out to me in person.
To the code:
* puppetboard: https://github.com/nedap/puppetboard
* pypuppetdb: https://github.com/nedap/pypuppetdb
I realise that puppetboard doesn't have a test suite right now but it will soon. In order to do so I have to restructure a few things about it first. The installation documentation will improve with it.
Pypuppetdb's test suite will be expanding the coming days once I'm done mocking the HTTP requests _query() makes and manage to get a decent and big enough set of test data to feed into PuppetDB. This will allow me to run integration tests and benchmark certain changes I have in mind.
I’m hoping to be able to get a release out every month with improvements to both projects, perhaps even faster in the beginning but it remains to be seen how much time I’ll be able to spend on it.
A special thanks goes out to Ken Barber for helping out with all things PuppetDB and coming up with a way to run PuppetDB on Travis so we can run integration tests. Hunter, thank you for being so interested in this project and pushing me to release it.
—
Daniele Sluijters
Nedap | Steppingstone
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To post to this group, send email to puppet...@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Hey, I lost this instruction ( was not in the group in august)
Really nice software, being using it for a couple of months, although I think it lacks some things to be even more useful( at least for me):
- in the main page nodes are in unchanged, changed or error state, would be nice to have the outofsync state( although I don't know if you can get this state without analyzing the full report)
- in the nodes page be able to filter to show last changed reports, last error reports and so on, showing only last ten reports I think is not useful enough.
And that it's :)
Thanks,
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6e95c3f7-3825-4bfc-a912-88b1ef08337e%40googlegroups.com.
Out of sync means that there are configurations in the node that doesn't meet the configuration it should have. It is useful if you work in noop mode by default.
I'm the yaml report files when a resource doesn't meet the configuration established in puppet master it appears as out of sync.
Regards,
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1b7c31c2-f073-4390-9d74-addfd8e863ed%40googlegroups.com.
You should SR it for the OpenSUSE systems:management:puppet repo so its available along with puppetdb and puppet.
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/a0e4ac7d-f470-48ad-8c0e-0ac3817aee40%40googlegroups.com.