container addressability When using openstack as provider lxc containers get a hardcoded ip

Bug #1473466 reported by Gema Gomez on 2015-07-10
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
juju
High
Unassigned

Bug Description

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.

This happens on OpenStack provider and in our opinion should be working on the same way MAAS provider is working.

Curtis Hovey (sinzui) on 2015-07-10
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.25.0
tags: added: lxc network ubuntu-openstack
Curtis Hovey (sinzui) on 2015-08-13
tags: added: bug-squad
Jorge Niedbalski (niedbalski) wrote :

The workaround used to fix this on OpenStack provider.

1. Add a new interface to your VM:

vi /etc/network/interfaces.d/juju-br0.cfg

# The primary network interface
auto juju-br0
iface juju-br0 inet dhcp
bridge_ports eth0

2. In /var/lib/lxc/juju-machine-23-lxc-0/config:

lxc.network.link = juju-br0

3. Go to your dhcp namespace (sudo ip netns exec
qdhcp-b9c1579d-79e2-4215-8ba0-ee4649d9c38f bash on this machine):

3.1 Add the new entries to
/var/lib/neutron/dhcp/b9c1579d-79e2-4215-8ba0-ee4649d9c38f/hosts

3.2 Restart the dnsmasq process with:
kill -HUP $PID

3.3 Restart the ubuntu hosts that contain the lxcs

description: updated
Dimiter Naydenov (dimitern) wrote :

Addressable containers on OpenStack are not yet supported, so the workaround you're describing is a possible way to get close to what juju does on MAAS (juju-br0 is not even created on OpenStack).

We do plan to have the same level of support for addressable containers in OpenStack, as in MAAS and EC2 (currently only with the address-allocation feature flag set at bootstrap), but it's not considered a priority vs. AWS VPC support for example.

Curtis Hovey (sinzui) on 2015-08-27
Changed in juju-core:
milestone: 1.25-alpha1 → 1.25-beta1
Changed in juju-core:
milestone: 1.25-beta1 → 1.26-alpha1
Curtis Hovey (sinzui) on 2015-11-03
Changed in juju-core:
milestone: 1.26-alpha1 → 1.26-alpha2
Changed in juju-core:
milestone: 1.26-alpha2 → 1.26.0
Changed in juju-core:
milestone: 1.26.0 → 2.0-beta5
tags: added: sts-needs-review
Changed in juju-core:
milestone: 2.0-beta5 → 2.0-beta4
Changed in juju-core:
milestone: 2.0-beta4 → 2.1.0
tags: added: sts-rfe
removed: sts sts-needs-review
tags: added: sts
affects: juju-core → juju
Changed in juju:
milestone: 2.1.0 → none
milestone: none → 2.1.0
tags: added: addressable-containers
Changed in juju:
milestone: 2.1.0 → 2.2.0
Curtis Hovey (sinzui) on 2017-02-16
summary: - When using openstack as provider lxc containers get a hardcoded ip
+ container addressability When using openstack as provider lxc containers
+ get a hardcoded ip
Curtis Hovey (sinzui) on 2017-03-24
Changed in juju:
milestone: 2.2-beta1 → 2.2-beta2
Curtis Hovey (sinzui) on 2017-03-30
Changed in juju:
milestone: 2.2-beta2 → 2.2-beta3
Changed in juju:
milestone: 2.2-beta3 → 2.2-beta4
Changed in juju:
milestone: 2.2-beta4 → 2.2-rc1
Tim Penhey (thumper) wrote :

This work is targetted for 2.3. A milestone will be set again once the work starts.

Changed in juju:
milestone: 2.2-rc1 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers