Issue #2603 has been updated by Roberto Moral.
The report generation (RRD or png files) being created by other application is not a problem. There are already a couple of ways to display the data once its been imported into a/the database, while puppetview way of extending the reports by adding a call to the puppetview rails app to import the yaml files directly works it adds the need for a rails app external to puppet to put the reports in the database when pretty much all the functionality is already present in puppet itself. ---------------------------------------- Feature #2603: Reports should be stored in the Database if Stored Config is enable. http://projects.reductivelabs.com/issues/2603 Author: Roberto Moral Status: Needs design decision Priority: Normal Assigned to: Luke Kanies Category: reports Target version: Affected version: 0.25.0 Keywords: Branch: As the number of servers managed by puppet grows the number of yaml files used for custom reports grows exponentially. While 5 million entries in the Database do not affect performance, 5 million files have an impact on file system performance. There should be a way to store the reports in the database in addition to the already existent report types. -- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
