1. I believe `bootstrap --config` affects just the 'controller' and 'default' models while `--model-default` affects all models, including any future ones. Perhaps `--model-default` should be renamed `--model-defaults`.
2. Agreed.
3. I would avoid the term "application constraints". I'm still unsure of what you mean by it. When you do `add-machine --constraints` are these application constraints?
4. The documentation will need to be altered. I went with the earlier statement that individual `--bootstrap-constraints` override corresponding values from `--constraints`. From what I understand now, when used in combination, each "batch" of constraints is fenced off from the other. This is clearer.
Nicely done.
Comments:
1. I believe `bootstrap --config` affects just the 'controller' and 'default' models while `--model-default` affects all models, including any future ones. Perhaps `--model-default` should be renamed `--model-defaults`.
2. Agreed.
3. I would avoid the term "application constraints". I'm still unsure of what you mean by it. When you do `add-machine --constraints` are these application constraints?
4. The documentation will need to be altered. I went with the earlier statement that individual `--bootstrap- constraints` override corresponding values from `--constraints`. From what I understand now, when used in combination, each "batch" of constraints is fenced off from the other. This is clearer.