标签: puppet-dashboard

Puppet-reports 在以下位置使用了大量磁盘空间：

/var/lib/puppet/reports
/var/lib/mysql

假设它将所有报告存储在 MySQL 数据库中，因为两个路径的大小大致相同。该resource_statuses表由行的每个代表在报告文件中的行。

• 在 Puppet-dashboard 或 PuppetDB 处理完 /var/lib/puppet/reports 中的报告后，是否可以安全地删除它们？
• 处理报告的最佳做法是什么？
• 有没有办法让Puppet-dashboard 在处理完yaml报告文件后自动删除它们？

有没有一种（简单的）方法让 puppet 使用 Internet 上可用的文件作为文件的 Source 属性？

例如：

file { "/home/text.txt":
  source => [
    "http://www.example.com/text.txt",
  ]
}

我使用的是 Ubuntu 12.04 LTS（32 位，服务器）、puppet 2.7.17、ruby 1.8.7.352 ruby​​gems 1.8.15。和 Apache 2.2.22。

当我尝试运行命令来迁移数据库时，

<server>:/usr/share/puppet-dashboard# rake RAILS_ENV=production db:migrate

我收到以下错误：

NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21.
NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will …