| 2015-07-10 14:09:09 |
Gema Gomez |
bug |
|
|
added bug |
| 2015-07-10 14:12:35 |
Curtis Hovey |
juju-core: status |
New |
Triaged |
|
| 2015-07-10 14:12:37 |
Curtis Hovey |
juju-core: importance |
Undecided |
High |
|
| 2015-07-10 14:12:40 |
Curtis Hovey |
juju-core: milestone |
|
1.25.0 |
|
| 2015-07-10 14:13:01 |
Curtis Hovey |
tags |
sts |
lxc network sts ubuntu-openstack |
|
| 2015-08-13 21:53:45 |
Curtis Hovey |
tags |
lxc network sts ubuntu-openstack |
bug-squad lxc network sts ubuntu-openstack |
|
| 2015-08-25 14:41:53 |
Jorge Niedbalski |
description |
I am trying to deploy automatically 3 ubuntu servers with 3 lxc containers on each of the nodes:
ubuntu:
branch: lp:charms/trusty/ubuntu
num_units: 3
constraints: mem=2G
rabbitmq-server:
branch: lp:charms/trusty/rabbitmq-server
num_units: 3
constraints: mem=1G
to: [ "lxc:ubuntu=0", "lxc:ubuntu=1", "lxc:ubuntu=2" ]
See full environment: http://bazaar.launchpad.net/~openstack-charm-testers/+junk/tempest/view/head:/rabbitHA.yaml
When deployed, the lxc containers are forced into:
LXC_DHCP_RANGE="10.0.3.2,10.0.3.254,infinite"
... instead of being plugged into the network of the deployment.
The problem is that these lxcs are not accessible. I was expecting the behaviour to be exactly like the maas provider. |
I am trying to deploy automatically 3 ubuntu servers with 3 lxc containers on each of the nodes:
ubuntu:
branch: lp:charms/trusty/ubuntu
num_units: 3
constraints: mem=2G
rabbitmq-server:
branch: lp:charms/trusty/rabbitmq-server
num_units: 3
constraints: mem=1G
to: [ "lxc:ubuntu=0", "lxc:ubuntu=1", "lxc:ubuntu=2" ]
See full environment: http://bazaar.launchpad.net/~openstack-charm-testers/+junk/tempest/view/head:/rabbitHA.yaml
When deployed, the lxc containers are forced into:
LXC_DHCP_RANGE="10.0.3.2,10.0.3.254,infinite"
... instead of being plugged into the network of the deployment.
The problem is that these lxcs are not accessible. I was expecting the behaviour to be exactly like the maas provider.
This happens on OpenStack provider and in our opinion should be working on the same way MAAS provider is working. |
|
| 2015-08-25 15:35:59 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2015-08-25 15:57:26 |
Ray Wang |
bug |
|
|
added subscriber Ray Wang |
| 2015-08-27 14:21:29 |
Curtis Hovey |
juju-core: milestone |
1.25-alpha1 |
1.25-beta1 |
|
| 2015-09-16 01:03:56 |
Alexis Bruemmer |
juju-core: milestone |
1.25-beta1 |
1.26-alpha1 |
|
| 2015-10-27 13:04:12 |
Mario Splivalo |
bug |
|
|
added subscriber Mario Splivalo |
| 2015-11-03 22:18:34 |
Curtis Hovey |
juju-core: milestone |
1.26-alpha1 |
1.26-alpha2 |
|
| 2015-11-18 22:05:46 |
Cheryl Jennings |
juju-core: milestone |
1.26-alpha2 |
1.26.0 |
|
| 2015-12-07 04:00:16 |
Cheryl Jennings |
juju-core: milestone |
1.26.0 |
2.0-beta5 |
|
| 2016-02-08 19:04:19 |
Jorge Niedbalski |
tags |
bug-squad lxc network sts ubuntu-openstack |
bug-squad lxc network sts sts-needs-review ubuntu-openstack |
|
| 2016-03-07 21:44:08 |
Cheryl Jennings |
juju-core: milestone |
2.0-beta5 |
2.0-beta4 |
|
| 2016-04-02 16:03:35 |
Cheryl Jennings |
juju-core: milestone |
2.0-beta4 |
2.1.0 |
|
| 2016-04-18 04:28:44 |
Roy Zuo |
bug |
|
|
added subscriber Roy Zuo |
| 2016-08-11 14:02:26 |
Jorge Niedbalski |
tags |
bug-squad lxc network sts sts-needs-review ubuntu-openstack |
bug-squad lxc network sts-rfe ubuntu-openstack |
|
| 2016-08-11 15:22:04 |
Jorge Niedbalski |
tags |
bug-squad lxc network sts-rfe ubuntu-openstack |
bug-squad lxc network sts sts-rfe ubuntu-openstack |
|
| 2016-08-22 22:51:39 |
Canonical Juju QA Bot |
affects |
juju-core |
juju |
|
| 2016-08-22 22:51:39 |
Canonical Juju QA Bot |
juju: milestone |
2.1.0 |
|
|
| 2016-08-22 22:51:41 |
Canonical Juju QA Bot |
juju: milestone |
|
2.1.0 |
|
| 2017-02-08 06:35:58 |
Anastasia |
tags |
bug-squad lxc network sts sts-rfe ubuntu-openstack |
addressable-containers bug-squad lxc network sts sts-rfe ubuntu-openstack |
|
| 2017-02-08 06:36:04 |
Anastasia |
juju: milestone |
2.1.0 |
2.2.0 |
|
| 2017-02-16 16:04:26 |
Curtis Hovey |
summary |
When using openstack as provider lxc containers get a hardcoded ip |
container addressability When using openstack as provider lxc containers get a hardcoded ip |
|
| 2017-03-24 16:56:06 |
Curtis Hovey |
juju: milestone |
2.2-beta1 |
2.2-beta2 |
|
| 2017-03-24 17:35:16 |
Gema Gomez |
removed subscriber Gema Gomez |
|
|
|
| 2017-03-30 20:40:37 |
Curtis Hovey |
juju: milestone |
2.2-beta2 |
2.2-beta3 |
|
| 2017-04-28 15:27:05 |
Canonical Juju QA Bot |
juju: milestone |
2.2-beta3 |
2.2-beta4 |
|
| 2017-05-11 18:21:46 |
Canonical Juju QA Bot |
juju: milestone |
2.2-beta4 |
2.2-rc1 |
|
| 2017-05-31 01:55:44 |
Tim Penhey |
juju: milestone |
2.2-rc1 |
|
|
| 2018-07-03 04:30:39 |
Ray Wang |
removed subscriber Ray Wang |
|
|
|
| 2021-01-12 16:00:46 |
Felipe Reyes |
tags |
addressable-containers bug-squad lxc network sts sts-rfe ubuntu-openstack |
addressable-containers bug-squad lxc network seg ubuntu-openstack |
|
