enable-ha and restore-backup ignore bootstrap's sane defaults

Bug #1641234 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
Triaged
High
Unassigned

Bug Description

Juju bootstrap command consistently selects a sensible machine to run the controller on. If I under spec the controller using --constraints mem=2G, the bootstrap command does the right think and selects a larger machine. The enable-ha and restore-backup commands do *not*!

For example. I see Juju is selecting t2.medium when bootstrapping, but enable-ha selected t2.small. Given Mongodb's greedy behaviour, the ha controllers are more likely to fail and probable take longer to come up.

This same poor selection strategy was also seen in rackspace.

Revision history for this message
John A Meinel (jameinel) wrote :

I believe we actually honor "--bootstrap-constraints" which are intended to be the "constraints for controller nodes".

We should confirm and document what constraints are applied to controllers vs what is model level constraints. Should we use the constraints on the controller model, should 'bootstrap-constraints' directly set constraints there.

tags: added: backup-restore
Ian Booth (wallyworld)
tags: removed: restore-backup
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers