Build new puppet-dashboard server
Bug #1218631 reported by
Elizabeth K. Joseph
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Core Infrastructure |
Fix Released
|
Medium
|
Spencer Krum |
Bug Description
The puppet-dashboard server is rax legacy and has some database problems. Today the disk filled up and now passenger won't start.
Instead of triaging the old system, we want to spin up a new one and implement some tuning procedures outlined on http://
Changed in openstack-ci: | |
assignee: | nobody → Elizabeth Krumbach Joseph (lyz) |
Changed in openstack-ci: | |
milestone: | none → havana |
status: | New → In Progress |
importance: | Undecided → Medium |
Changed in openstack-ci: | |
assignee: | Elizabeth Krumbach Joseph (lyz) → Spencer Krum (krum-spencer) |
To post a comment you must log in.
The "Optimize your database once a month" strategy was tried and tested by anteaya and fungi earlier this year: https:/ /review. openstack. org/#/c/ 23112/ Should follow up to see if we should pursue this again with a freshly configured MySQL database on the new server
At the same time as above, anteaya added the passenger optimizations: https:/ /review. openstack. org/#/c/ 23127/
Currently have a patch under review for monthly pruning of reports: https:/ /review. openstack. org/#/c/ 44368/