The new 1.17.1 juju development release contains a workaround for the
bug[1] involving multiple networks set up on an Openstack deployment.
If you've run into this problem, be aware this is not a stable release
for production work, but please consider testing to verify the change
will work for you.

The problem manifests when nova refuses to boot any server when more
than one usable network exists:

    2014-01-29 16:14:54 ERROR juju.cmd supercommand.go:294 cannot
start bootstrap instance: cannot run instance: ...
    error info: {"badRequest": {"message": "Multiple possible networks
found, use a Network ID to be more specific.", "code": 400}}

Ideally nova/neutron would have the concept of a default network, as
at the juju level there is no sane way of determining which existing
network to use. In the future, juju will likely create and manage
networks through neutron, but this won't make the next stable release.

For now, environments.yaml has a new configuration option for
Openstack for specifying a single network that the juju environment
should use for all communication:

    # network specifies the network label or uuid to bring machines up on, in
    # the case where multiple networks exist. It may be omitted otherwise.
    network: <your network label or uuid>

Watch out for dangling a ~/.juju/environments/{ENV}.jenv file if
you've previously tried to bootstrap the environment and failed as a
bug[2] means the addition of the network config option will be missed.

Using `juju bootstrap --debug --show-log` will display a message
before starting the server if a network is selected:

    2014-01-29 14:27:03 DEBUG juju.provider.openstack provider.go:761
using network id "307e048a-99c7-40ef-9708-7b06da527682"

A related issue[3] with multiple networks, where bringing up a server
on multiple networks picks one arbitrarily, should also be possible to
avoid by explicitly setting the a single network using the
configuration option. Please tell me if this doesn't cover a use case
that requires multiple networks for juju machines.

Martin


[1]: juju-core broken with OpenStack Havana for tenants with multiple networks
<https://bugs.launchpad.net/juju-core/+bug/1241674>
[2]: Failed bootstrap can prevent future bootstraps
<https://bugs.launchpad.net/juju-core/+bug/1247152>
[3]: Juju unable to interact consistently with an openstack deployment
where tenant has multiple networks configured
<https://bugs.launchpad.net/juju/+bug/1188126>

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Reply via email to