As mentioned from Stephane, this is intentional, and trying to follow
the "spec" seems like it will likely cause more problems than doing what
we're currently doing.
** Changed in: juju
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Not seeing an advantage in changing range for LXD at this point, unless
we get our own reserved named range. Marking won't fix.
** Changed in: lxd (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: lxd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1660542
Title:
container mac addresses should use 'locally assigned' section
To manage
We track Juju 2.x issues in "juju" project. Re-targeting :D
** Also affects: juju
Importance: Undecided
Status: New
** Changed in: juju
Status: New => Triaged
** Changed in: juju
Importance: Undecided => Medium
** No longer affects: juju-core
--
You received this bug
Copy/pasting from the e-mail I just sent you:
"""
It's a reserved prefix by Xen for use by hypervisors and has been used
by a fair number of other hypervisors and container projects who didn't
get their own allocation.
So I remember someone looking into using a different prefix in the past,
** Project changed: lxd => lxd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1660542
Title:
container mac addresses should use 'locally assigned' section
To manage notifications about
