ubuntu charm lacks lxc bridge config
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
ubuntu (Juju Charms Collection) | Status tracked in Precise | |||||
Precise |
Incomplete
|
Undecided
|
Liang Chen | |||
Trusty |
Fix Released
|
Undecided
|
Liang Chen |
Bug Description
Current ubuntu charm doesn't provide any configuration options, so when deploy the following bundle in such a local env,
local env:
=======
local:
type: local
container: kvm
bundle:
=======
sample:
services:
ubuntu:
branch: lp:charms/ubuntu
series: trusty
constraints: mem=2G
num_units: 1
new-
mysql:
to: lxc:ubuntu=0
charm: "cs:trusty/mysql"
num_units: 1
wordpress:
to : lxc:ubuntu=0
charm: "cs:trusty/
num_units: 1
relations:
- - "wordpress:db"
- "mysql:db"
the mysql and wordpress nodes will not have their network configured properly. Because by default lxc in the ubuntu instance uses dnsmasq to provide dhcp on lxcbr0, and the dnsmasq will choose a subnet that's different from the network that the ubuntu kvm instance is in.
It would be good to add a config option for the ubuntu charm, so that uses can choose whether to create a different subnet or just bridge to the exist network that the ubuntu instance is in for lxc containers.
Related branches
- Charles Butler (community): Needs Fixing
- Antonio Rosales (community): Approve (community)
-
Diff: 3472 lines (+3356/-0)22 files modifiedcharm-helpers-hooks.yaml (+5/-0)
config.yaml (+8/-0)
hooks/charmhelpers/core/__init__.py (+15/-0)
hooks/charmhelpers/core/decorators.py (+57/-0)
hooks/charmhelpers/core/fstab.py (+134/-0)
hooks/charmhelpers/core/hookenv.py (+568/-0)
hooks/charmhelpers/core/host.py (+446/-0)
hooks/charmhelpers/core/services/__init__.py (+18/-0)
hooks/charmhelpers/core/services/base.py (+329/-0)
hooks/charmhelpers/core/services/helpers.py (+259/-0)
hooks/charmhelpers/core/strutils.py (+42/-0)
hooks/charmhelpers/core/sysctl.py (+56/-0)
hooks/charmhelpers/core/templating.py (+68/-0)
hooks/charmhelpers/core/unitdata.py (+477/-0)
hooks/charmhelpers/fetch/__init__.py (+439/-0)
hooks/charmhelpers/fetch/archiveurl.py (+161/-0)
hooks/charmhelpers/fetch/bzrurl.py (+78/-0)
hooks/charmhelpers/fetch/giturl.py (+71/-0)
hooks/config-changed (+43/-0)
hooks/hooks.py (+45/-0)
hooks/utils.py (+27/-0)
templates/lxc-bridge.conf (+10/-0)
- Charles Butler (community): Approve
- Antonio Rosales (community): Approve (community)
- Adam Israel (community): Needs Fixing
- Review Queue (community): Needs Fixing (automated testing)
-
Diff: 3472 lines (+3356/-0)22 files modifiedcharm-helpers-hooks.yaml (+5/-0)
config.yaml (+8/-0)
hooks/charmhelpers/core/__init__.py (+15/-0)
hooks/charmhelpers/core/decorators.py (+57/-0)
hooks/charmhelpers/core/fstab.py (+134/-0)
hooks/charmhelpers/core/hookenv.py (+568/-0)
hooks/charmhelpers/core/host.py (+446/-0)
hooks/charmhelpers/core/services/__init__.py (+18/-0)
hooks/charmhelpers/core/services/base.py (+329/-0)
hooks/charmhelpers/core/services/helpers.py (+259/-0)
hooks/charmhelpers/core/strutils.py (+42/-0)
hooks/charmhelpers/core/sysctl.py (+56/-0)
hooks/charmhelpers/core/templating.py (+68/-0)
hooks/charmhelpers/core/unitdata.py (+477/-0)
hooks/charmhelpers/fetch/__init__.py (+439/-0)
hooks/charmhelpers/fetch/archiveurl.py (+161/-0)
hooks/charmhelpers/fetch/bzrurl.py (+78/-0)
hooks/charmhelpers/fetch/giturl.py (+71/-0)
hooks/config-changed (+43/-0)
hooks/hooks.py (+45/-0)
hooks/utils.py (+27/-0)
templates/lxc-bridge.conf (+10/-0)
Changed in charms: | |
assignee: | nobody → Liang Chen (cbjchen) |
summary: |
- ubuntu charm lack lxc bridge config + ubuntu charm lacks lxc bridge config |
Changed in charms: | |
status: | New → In Progress |
Changed in charms: | |
status: | In Progress → Fix Released |
status: | Fix Released → Triaged |
affects: | Charms Precise → ubuntu (Charms Precise) |
@Liang,
Thanks for ensuring this Charm was also available for Precise. If you could please submit a merge proposal of your current branch, lp:~cbjchen/charms/trusty/ubuntu/lxc-network-config, against Precise we can test and then update the Ubuntu Precise charm.
While this is updated I'll put the status in "Incomplete" while you attach the Precise branch.
-thanks,
Antoino