Comment 0 for bug 1473466

Revision history for this message
Gema Gomez (gema) wrote : When using openstack as provider lxc containers get a hardcoded ip

I am trying to deploy automatically 3 ubuntu servers with 3 lxc containers on each of the nodes:

    ubuntu:
      branch: lp:charms/trusty/ubuntu
      num_units: 3
      constraints: mem=2G
    rabbitmq-server:
      branch: lp:charms/trusty/rabbitmq-server
      num_units: 3
      constraints: mem=1G
      to: [ "lxc:ubuntu=0", "lxc:ubuntu=1", "lxc:ubuntu=2" ]

See full environment: http://bazaar.launchpad.net/~openstack-charm-testers/+junk/tempest/view/head:/rabbitHA.yaml

When deployed, the lxc containers are forced into:

LXC_DHCP_RANGE="10.0.3.2,10.0.3.254,infinite"

... instead of being plugged into the network of the deployment.

The problem is that these lxcs are not accessible. I was expecting the behaviour to be exactly like the maas provider.