landscape-dense needs haproxy machine constraint
Bug #1677663 reported by
Kevin W Monroe
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Bundles |
Fix Released
|
Low
|
David Britton | ||
Bug Description
I deployed this to GCE:
https:/
Unfortunately, postgres never started because the machine OOM'd. Postgres, Rabbit, and Landscape are all deployed as lxd containers on the haproxy unit in this bundle, and by default, that unit comes up with only 1.7G ram on GCE.
Please consider adding a memory constraint to haproxy for the "dense" flavor. In my tests, 3.5G was enough to get the applications started, so "memory: 3G" would work.
Also consider a root-disk constraint, as the default disk size is pretty small for both AWS and GCE:
/dev/sda1 7.8G 6.1G 1.4G 83% /
You can see I've only got 1.4G free in the root filesystem, which I suspect won't last long.
Related branches
lp:~dpb/landscape-bundles/add-machine-contraints
- 🤖 Landscape Builder: Approve (test results)
- Francis Ginther (community): Approve
- Chad Smith: Approve
-
Diff: 13 lines (+2/-1)1 file modifiedlandscape-template.jinja2 (+2/-1)
| Changed in landscape-bundles: | |
| assignee: | nobody → David Britton (davidpbritton) |
| importance: | Undecided → Low |
| status: | New → In Progress |
| Changed in landscape-bundles: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| David Britton (dpb) wrote | #1 |
| Changed in landscape-bundles: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
cs:~landscape/