In my efforts in trying to bootstrap a vsphere controller, I’ve created a config yaml as:
primary-network: VLAN_802 datastore: H280-VIC847-0001 identity-url: https://candid.rnd.scania.com identity-public-key: zodxUe4yD0yZBufJajicc02aAQVrQAMVsrYG/631w1o= allow-model-access: true
Now, the bootstrap works (with Candid etc.) and ‘sometimes’ on the default model.
However: when I create new models with “juju add-model”, I can’t seem to get the “datastore” and primary-network to be inherited down to the new models I create from this controller. This prevents new machines from being deployed.
My question is:
- "How do I include configuration keys to apply for all new model creations - ideally part of the bootstrap config yaml?
I know how to set these values on a “per model basis”, like:
$ juju model-config datastore=H280-VIC847-0001 WARNING key "datastore" is not defined in the current model configuration: possible misspelling $ juju model-config primary-network=VLAN_802 WARNING key "primary-network" is not defined in the current model configuration: possible misspelling
Then I’m all good.
But I need this to be applied to all models being created from this controller.