Comment 20 for bug 1768308
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #20 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
@Peter Matulis (petermatulis),
At the end of the day, a constraint can only be a machine constraint - it is specifying a hardware characteristic.
However, a constraint can be specified at different stages of system deployment. In Juju, you can specify a constraint when:
a. you add a machine, see 'juju help add-machine'. This is an instruction for this one machine.;
b. you deploy an application, see 'juju help deploy'. This is an instruction for all unit machines for this application.;
c. you bootstrap a controller, see 'juju help bootstrap'. This is an instruction for all machines in this model. This is the bit that needs some love as per comment # 14. We need to have the ability to propagate it to all models within the controller as well as have the ability to override it at 'add-model'.
As you can see, these correspond directly to 'hierarchical scopes' you describe above. So I am trying to figure out where is the confusion...
I also feel like the bug report is not the right place to clarify an understanding of a concept. I am happy to have a discussion outside of the bug tracker with the view to have this added to online documentation.