Setting up private cloud controller
Rick Harding
rick.harding at canonical.com
Mon Nov 14 17:47:45 UTC 2016
On Mon, Nov 14, 2016 at 12:00 PM Jonathan D. Proulx <jon at csail.mit.edu>
wrote:
>
> Continuing to try and get a Juju controller in my (14.04/Mitaka)
> OpenStack Cloud. Working with juju 2.0.1 from Xenial client.
>
> My next issue is I need to specify a network for the controller as
> bootstrapping now fails with:
>
> returned unexpected status: 409; error info: {"conflictingRequest":
> {"message": "Multiple possible networks found, use a Network ID to be more
> specific.", "code": 409}}}])
>
You can bootstrap by providing additional config to help Juju know which
network to use.
juju bootstrap --config network=$UUID
I'd tried a 'network: <uuid>' in the cloud definition YAML in both the
> region block and the top level of the named cloud but it doesn't show
> when I 'juju show-cloud' so unsurprisingly seems to have no effect.
>
Yes, this needs to be in the clouds.yaml file in the yaml nested below the
key called "config".
So you need to edit: ~/.local/share/juju/clouds.yaml
and add a subsection to the cloud in question:
clouds:
myopenstack:
config:
network: $UUID
That should get you off to the races.
Rick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20161114/205bce68/attachment.html>
More information about the Juju
mailing list