On 10/3/2013 8:12 AM, MasterPO wrote:
Unfortunately, for me all this does is make the puppet-master host go
100% busy between the dashboard and mysqld.
I am running Dashboard version 1.2.23 with puppet-server version 3.2.4
and mysql version 5.1.69 on RHEL 6.4
I get the same result running John
Unfortunately, for me all this does is make the puppet-master host go 100%
busy between the dashboard and mysqld.
I am running Dashboard version 1.2.23 with puppet-server version 3.2.4 and
mysql version 5.1.69 on RHEL 6.4
I get the same result running John's cli rake command.
Any ideas?
Than
Great ! Thank you John...
If I understand correctly, the "node:del" action will delete the node from
dashboard database, while the "reports:prune:orphaned" will delete reports
& inventory files on the server.
Does anyone see other useful actions to launch while decomissioning a node ?
Best regard
On 25 July 2013 22:54, yannig rousseau wrote:
> Do you know if it's possible to lauch it from a script (maybe a sql
> request ?)
rake --silent node:del name=deleteme RAILS_ENV=production
I also run a job each day to tidy up the database:
# Purged nodes leave behind orphaned records:
#
http://
Do you know if it's possible to lauch it from a script (maybe a sql request
?)
On Thu, Jul 25, 2013 at 2:17 PM, Klavs Klavsen wrote:
> that job just removes reports for hosts - it does't remove the actual
>> hosts.
>
>
> You need to pick the node in puppet-dashboard webinterface - and choose
> d
>
> that job just removes reports for hosts - it does't remove the actual
> hosts.
You need to pick the node in puppet-dashboard webinterface - and choose
delete (upper right corner)
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsub