make kvm containers addressable (esp. on MAAS)
Bug #1431130 reported by
Dimiter Naydenov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
James Tunnicliffe | ||
Bug Description
After the bulk of the container addressability work landed, a few changes were made to the MAAS provider (removing juju-br0, as it causes more issues than it solves; instead LXC and KVM containers use the default bridge for their type - lxcbr0 and virbr0). As a consequence KVM containers became not addressable (using 192.168.122.0/24 addresses instead of one of the networks their host is on). Since the work was focused on getting LXC containers addressable on EC2 and MAAS, the KVM support needs to land (in 1.23-beta1) both to finish the CA feature and to restore the UX on MAAS + KVM.
A patch is already in progress, soon to be proposed.
Revision history for this message
| Dimiter Naydenov (dimitern) wrote | #1 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/
https:/