On 13/06/16 22:58, Rick Harding wrote: > On Sat, Jun 11, 2016 at 6:32 PM Ian Booth <ian.bo...@canonical.com> wrote: > >> We are also storing any config specified in clouds.yaml separately. These >> items, >> such as apt-mirror, are shared between models and are used by default if >> not >> specified in a hosted model. But you can override any such items as well >> simply >> by setting them on the model. For now, the semantics of this change are >> transparent - get-model-config will show the accumulation of shared and >> model >> specific settings. But we are looking to add a command to show/set shared >> config. Thus you will be able to say update a http-proxy setting across all >> hosted models within a controller with one command: >> >> juju set-shared-config http-proxy=foo >> >> NB command name to be decided. >> > > Ian, can we setup some time to chat on this. I'm curious if, rather than a > command to explicitly "set everywhere" we follow the model that the config > is inherited unless overridden for a specific model. Then by setting it on
What you say above is how it will work. You bootstrap a controller and any config specified in clouds.yaml for that cloud becomes the default inherited config for all hosted models add to the controller. But you can then choose to set a config value on your hosted model, and that will override anything that was being used as the default. > the controller all models would get it. If you want it set on a specific > model, you'd set it on the model. In that way there'd not be a third/new > command for setting config. > "Setting it on the controller" - that's what we are proposing. Once you have bootstrapped the controller and the shared default config for hosted models has been set up (by virtue of the settings in clouds.yaml), you then need a way to alter that shared config. Is that what you mean? What command would you like for that? We have $ juju set-model-config foo=bar That sets foo on the current model. Or $ juju -m mymodel set-model-config foo=bar operates on model mymodel. The above are model commands. So we need a way to set foo=bar on the controller itself (ie update the shared controller wide config). What are you proposing? Did you intend that setting foo on the controller model would satisfy the requirement? That seems to be wrong for 2 reasons: 1. It's a model not a controller 2. The controller model can be used to host applications (eg nagios), and as such the controller model settings may we be required to be set in and of themselves, and to conflate those with default controller side config seems wrong. Maybe I'm thinking wrongly, but I make a very clear distinction in my mind between the controller and its models. There should be separate commands for managing controller artifacts, including ACLs, vs model artifacts. Speaking of ACLs, the same distinction applies. You want to manage access to the controller - who can create models, who can share models, who can delete models not their own, who can register users etc - vs model level operations - who can deploy applications etc. And so again, the controller model permissions are different semantically to the controller permissions. You can manage who can create applications in the controller model, which is different to an operation on the controller itself like registering a user. You may grant fred access to the controller model, but not the controller itself. Or maybe I'm misunderstanding what you mean? -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
