| 2016-09-16 19:38:40 |
Larry Michel |
bug |
|
|
added bug |
| 2016-09-16 19:40:05 |
Larry Michel |
description |
For bug 1592811, we have the limitation that networking for LXD container is over lxdbr0 which is not attached to any physical network. What happens is that if we want to have a dense deployment, then the LXD containers come up on a LXD internal network which cannot be reached from a different host. This doesn't work and without lxdbr0 tied to an external network and all the Juju services cannot be deployed successfully.
Per conversation with frobware and mackgreagoir, perhaps juju could provide one or more config options for specifying a bridge to use instead of lxdbr0 and location of the cloud init image with the bridge already configured.
frobware asked me to follow up with a bug on this. So this would be a request for Juju config option for specifying the location of the cloud init image so Juju could point to custom cloud image's location. In that case, either lxdbr0 could already be tied to a physical adapter or the image has a bridge configured on top of a NIC The bridge name could then be a Juju config option or it could be a known bridge name such as br100 or br-int which would not necessitate a config option for it. |
For bug 1592811, we have the limitation that networking for LXD container is over lxdbr0 which is not attached to any physical network. What happens is that if we want to have a dense deployment, then the LXD containers come up on a LXD internal network which cannot be reached from a different host. This doesn't work and without lxdbr0 tied to an external network, all the Juju services cannot be deployed successfully.
Per conversation with frobware and mackgreagoir, perhaps juju could provide one or more config options for specifying a bridge to use instead of lxdbr0 and also the location of the cloud init image with the bridge already configured.
frobware asked me to follow up with a bug on this to describe the issue and request. So this would be a request for Juju config option for specifying the location of the cloud init image so Juju could point to custom cloud image's location. In that case, either lxdbr0 could already be tied to a physical adapter or the image has a bridge configured on top of a NIC The bridge name could then be a Juju config option or it could be a known bridge name such as br100 or br-int which would not necessitate a config option for it. |
|
| 2016-09-16 19:58:21 |
Larry Michel |
description |
For bug 1592811, we have the limitation that networking for LXD container is over lxdbr0 which is not attached to any physical network. What happens is that if we want to have a dense deployment, then the LXD containers come up on a LXD internal network which cannot be reached from a different host. This doesn't work and without lxdbr0 tied to an external network, all the Juju services cannot be deployed successfully.
Per conversation with frobware and mackgreagoir, perhaps juju could provide one or more config options for specifying a bridge to use instead of lxdbr0 and also the location of the cloud init image with the bridge already configured.
frobware asked me to follow up with a bug on this to describe the issue and request. So this would be a request for Juju config option for specifying the location of the cloud init image so Juju could point to custom cloud image's location. In that case, either lxdbr0 could already be tied to a physical adapter or the image has a bridge configured on top of a NIC The bridge name could then be a Juju config option or it could be a known bridge name such as br100 or br-int which would not necessitate a config option for it. |
For bug 1592811, we have the limitation that networking for LXD container is over lxdbr0 which is not attached to any physical network. What happens is that if we want to have a dense deployment, then the LXD containers come up on a LXD internal network which cannot be reached from a different host. This doesn't work since lxdbr0 is not tied to an external network; hence, all the Juju services cannot be deployed successfully.
Per conversation with frobware and mackgreagoir, perhaps juju can provide one or more additional config options for specifying a bridge to use instead of lxdbr0 and also the location of the cloud init image with the bridge already configured.
frobware asked me to follow up with a bug on this to describe the issue and request. So this would be a request for Juju config option for specifying the location of the cloud init image so Juju could point to custom cloud image's location. In that case, the image would have a bridge configured on top of a NIC. Then, the bridge name would then be a Juju config option or it could be a known bridge name such as br100 or br-int which would not necessitate a config option for it. |
|
| 2016-09-18 22:58:22 |
Anastasia |
juju: status |
New |
Triaged |
|
| 2016-09-18 22:58:24 |
Anastasia |
juju: importance |
Undecided |
High |
|
| 2016-09-18 22:58:27 |
Anastasia |
juju: milestone |
|
2.0-rc2 |
|
| 2016-09-18 22:58:36 |
Anastasia |
juju: assignee |
|
Richard Harding (rharding) |
|
| 2016-09-19 17:36:07 |
Richard Harding |
tags |
oil oil-2.0 |
network oil oil-2.0 |
|
| 2016-09-20 14:41:34 |
Larry Michel |
bug task added |
|
cloud-images |
|
| 2016-09-29 13:56:57 |
Richard Harding |
juju: milestone |
2.0-rc2 |
2.0.0 |
|
| 2016-10-05 20:49:13 |
Alexis Bruemmer |
juju: milestone |
2.0.0 |
2.1.0 |
|
| 2017-02-02 10:52:47 |
Anastasia |
juju: assignee |
Richard Harding (rharding) |
|
|
| 2017-02-15 11:42:52 |
Anastasia |
juju: milestone |
2.1.0 |
|
|
| 2017-02-15 11:49:03 |
Anastasia |
juju: importance |
High |
Wishlist |
|
| 2017-02-15 12:09:45 |
Dan Watkins |
cloud-images: status |
New |
Invalid |
|
| 2022-11-03 16:19:08 |
Canonical Juju QA Bot |
juju: status |
Triaged |
Expired |
|
| 2022-11-03 16:19:09 |
Canonical Juju QA Bot |
tags |
network oil oil-2.0 |
expirebugs-bot network oil oil-2.0 |
|
