juju probably should be using lxcbr0 instead of depending on libvirt-bin and using virbr0
Bug #996358 reported by
Stéphane Graber
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Fix Released
|
Low
|
Clint Byrum | ||
| juju (Ubuntu) |
Fix Released
|
Low
|
Clint Byrum | ||
Bug Description
While testing juju, I noticed that its lxc implementation depends on libvirt-bin just to have virbr0 initialized.
That seems to be a big dependency for something as trivial as creating a bridge and starting dnsmasq, even more so when lxc itself does that by default.
I think juju should drop all the current libvirt code and simply use lxcbr0 by default (as it's shipped by default in the lxc package since 12.04), probably allowing the user to select another bridge if they wish.
Related branches
lp:~clint-fewbar/pyjuju/local-cloud-img
- Kapil Thangavelu (community): Approve
-
Diff: 2440 lines (+724/-859)29 files modifiedMakefile (+1/-1)
juju/agents/tests/test_base.py (+1/-1)
juju/control/options.py (+1/-1)
juju/lib/lxc/__init__.py (+72/-94)
juju/lib/lxc/data/juju-create (+0/-156)
juju/lib/lxc/data/lxc.conf (+0/-3)
juju/lib/lxc/tests/test_lxc.py (+90/-92)
juju/lib/service.py (+19/-7)
juju/lib/tests/test_service.py (+17/-1)
juju/machine/tests/data/test_get_container (+44/-0)
juju/machine/tests/test_unit_deployment.py (+24/-40)
juju/machine/unit.py (+55/-59)
juju/providers/common/cloudinit.py (+79/-7)
juju/providers/common/tests/data/cloud_init_branch (+1/-1)
juju/providers/common/tests/data/cloud_init_branch_trunk (+1/-1)
juju/providers/common/tests/data/cloud_init_no_machine_id (+10/-0)
juju/providers/common/tests/data/cloud_init_ppa_apt_proxy (+39/-0)
juju/providers/common/tests/test_cloudinit.py (+36/-2)
juju/providers/common/utils.py (+7/-1)
juju/providers/ec2/tests/data/launch_cloud_init_branch (+1/-1)
juju/providers/local/__init__.py (+17/-14)
juju/providers/local/agent.py (+3/-9)
juju/providers/local/files.py (+11/-9)
juju/providers/local/network.py (+66/-118)
juju/providers/local/tests/test_agent.py (+13/-4)
juju/providers/local/tests/test_files.py (+9/-51)
juju/providers/local/tests/test_network.py (+106/-184)
juju/providers/local/tests/test_provider.py (+1/-1)
setup.py (+0/-1)
Revision history for this message
| Serge Hallyn (serge-hallyn) wrote | #1 |
| Changed in juju (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | #2 |
| Changed in juju (Ubuntu): | |
| status: | Confirmed → In Progress |
| assignee: | nobody → Clint Byrum (clint-fewbar) |
| status: | In Progress → Triaged |
| Changed in juju: | |
| status: | New → Triaged |
| status: | Triaged → In Progress |
| importance: | Undecided → Low |
| assignee: | nobody → Clint Byrum (clint-fewbar) |
| milestone: | none → 0.6 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
| Changed in juju (Ubuntu): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
Which as has been mentioned before would be particularly nice for juju inside nested containers.