Command add-model

Usage: juju add-model [options] <model name> [cloud|region|(cloud/region)]

Summary:

Adds a hosted model.

Options:

-B, --no-browser-login (= false)

Do not use web browser for authentication

-c, --controller (= "")

Controller to operate in

--config (= )

Path to YAML model configuration file or individual options (–config config.yaml [–config key=value …])

--credential (= "")

Credential used to add the model

--no-switch (= false)

Do not switch to the newly created model

--owner (= "")

The owner of the new model if not the current user

Details:

Adding a model is typically done in order to run a specific workload.

To add a model, you must specify a model name. Model names can be duplicated across controllers but must be unique per user for any given controller. In other words, Alice and Bob can each have their own model called “secret” but Alice can have only one model called “secret” in a controller.

Model names may only contain lowercase letters, digits and hyphens, and may not start with a hyphen.

To add a model, Juju requires a credential:

     * if you have a default (or just one) credential defined at client
      (i.e. in credentials.yaml), then juju will use that;
      * if you have no default (and multiple) credentials defined at the client, 
      then you must specify one using --credential;
      * as the admin user you can omit the credential, 
      and the credential used to bootstrap will be used.

To add a credential for add-model, use one of the juju add-credential or juju autoload-credentials commands. These will add credentials to the Juju client, which juju add-model will upload to the controller as necessary.

You may also supply model-specific configuration as well as a cloud/region to which this model will be deployed. The cloud/region and credentials are the ones used to create any future resources within the model.

If no cloud/region is specified, then the model will be deployed to the same cloud/region as the controller model. If a region is specified without a cloud qualifier, then it is assumed to be in the same cloud as the controller model. It is not currently possible for a controller to manage multiple clouds, so the only valid cloud is the same cloud as the controller model is deployed to. This may change in a future release.

Examples:

   juju add-model mymodel
    juju add-model mymodel us-east-1
    juju add-model mymodel aws/us-east-1
    juju add-model mymodel --config my-config.yaml --config image-stream=daily
    juju add-model mymodel --credential credential_name --config authorized-keys="ssh-rsa ..."