| 2015-09-25 10:15:37 |
Rafael Ferreira |
bug |
|
|
added bug |
| 2015-09-25 10:15:37 |
Rafael Ferreira |
attachment added |
|
Captura de ecrã 2015-09-25, às 11.14.43.png https://bugs.launchpad.net/bugs/1499670/+attachment/4474208/+files/Captura%20de%20ecr%C3%A3%202015-09-25%2C%20%C3%A0s%2011.14.43.png |
|
| 2015-09-25 10:16:10 |
Rafael Ferreira |
description |
If we have one network topology like this one:
+-+
| | +--+ +--+
| | | | 10.0.0.4 router_interface | |
| | | | 20.0.0.1 router_interface | | + When we go to:
| | | | | | | /dashboard/project/instances/<instance-id>/
| | | | +-----+ | | | We have the option Associate Floating IP
| | | +------+ R2 +-------------------+ | | but when the pop up "Manage Floating IP
| | +----+ | | +-----+ | | | Associations" the instance ports are not
| +----------+ R1 +----------------+ | | | | listed because this instance can't have
| | +----+ | | | | v floating IPs.
| | | | | |
| | 172.24.4.2 router_gateway| | +--------------------+ | | +---------------+
| | 10.0.0.1 router_interface| +--+ Instance 1 | | +-----+ Instance 2 |
| | | | +--------------------+ | | +---------------+
| | | | 10.0.0.3 | | 20.0.0.3
| | | | 172.24.4.4 (floating ip) | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | |Private | |Private
| | | |10.0.0.0/24 | |20.0.0.0/24
| | +--+ +--+
| | External network:
| | 172.24.4.0/24
| |
+-+ |
If we have one network topology like this one:
<pre>
+-+
| | +--+ +--+
| | | | 10.0.0.4 router_interface | |
| | | | 20.0.0.1 router_interface | | + When we go to:
| | | | | | | /dashboard/project/instances/<instance-id>/
| | | | +-----+ | | | We have the option Associate Floating IP
| | | +------+ R2 +-------------------+ | | but when the pop up "Manage Floating IP
| | +----+ | | +-----+ | | | Associations" the instance ports are not
| +----------+ R1 +----------------+ | | | | listed because this instance can't have
| | +----+ | | | | v floating IPs.
| | | | | |
| | 172.24.4.2 router_gateway| | +--------------------+ | | +---------------+
| | 10.0.0.1 router_interface| +--+ Instance 1 | | +-----+ Instance 2 |
| | | | +--------------------+ | | +---------------+
| | | | 10.0.0.3 | | 20.0.0.3
| | | | 172.24.4.4 (floating ip) | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | |Private | |Private
| | | |10.0.0.0/24 | |20.0.0.0/24
| | +--+ +--+
| | External network:
| | 172.24.4.0/24
| |
+-+
</pre> |
|
| 2015-09-25 10:24:06 |
Rafael Ferreira |
description |
If we have one network topology like this one:
<pre>
+-+
| | +--+ +--+
| | | | 10.0.0.4 router_interface | |
| | | | 20.0.0.1 router_interface | | + When we go to:
| | | | | | | /dashboard/project/instances/<instance-id>/
| | | | +-----+ | | | We have the option Associate Floating IP
| | | +------+ R2 +-------------------+ | | but when the pop up "Manage Floating IP
| | +----+ | | +-----+ | | | Associations" the instance ports are not
| +----------+ R1 +----------------+ | | | | listed because this instance can't have
| | +----+ | | | | v floating IPs.
| | | | | |
| | 172.24.4.2 router_gateway| | +--------------------+ | | +---------------+
| | 10.0.0.1 router_interface| +--+ Instance 1 | | +-----+ Instance 2 |
| | | | +--------------------+ | | +---------------+
| | | | 10.0.0.3 | | 20.0.0.3
| | | | 172.24.4.4 (floating ip) | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | |Private | |Private
| | | |10.0.0.0/24 | |20.0.0.0/24
| | +--+ +--+
| | External network:
| | 172.24.4.0/24
| |
+-+
</pre> |
If we have one network topology like the one attached, the instance "ne2" has the IP 20.0.0.3 but the 20.0.0.0/24 isn't an external network, but when we go to http://host/dashboard/project/routers/<instance-id>/ we see the option "Associate Floating IP" and when the pop-up "Manage Floating IP Associations" opens there aren't any port of instance "ne2" listed, and this is correct, the network that the instance is attached isn't an external network but the option of "Associate Floating IP" is incorrect.
HORIZON_BRANCH=master |
|
| 2015-09-25 10:26:30 |
Rafael Ferreira |
horizon: assignee |
|
Rafael Ferreira (rafaelferreira) |
|
| 2015-09-25 10:26:35 |
Rafael Ferreira |
horizon: assignee |
Rafael Ferreira (rafaelferreira) |
|
|
| 2017-10-07 20:00:18 |
Akihiro Motoki |
tags |
|
neutron |
|
| 2017-10-09 09:00:26 |
Akihiro Motoki |
horizon: importance |
Undecided |
Wishlist |
|
| 2017-10-09 09:01:20 |
Akihiro Motoki |
description |
If we have one network topology like the one attached, the instance "ne2" has the IP 20.0.0.3 but the 20.0.0.0/24 isn't an external network, but when we go to http://host/dashboard/project/routers/<instance-id>/ we see the option "Associate Floating IP" and when the pop-up "Manage Floating IP Associations" opens there aren't any port of instance "ne2" listed, and this is correct, the network that the instance is attached isn't an external network but the option of "Associate Floating IP" is incorrect.
HORIZON_BRANCH=master |
If we have one network topology like the one attached, the instance "ne2" has the IP 20.0.0.3 but the 20.0.0.0/24 isn't an external network, but when we go to http://host/dashboard/project/instances/<instance-id>/ we see the option "Associate Floating IP" and when the pop-up "Manage Floating IP Associations" opens there aren't any port of instance "ne2" listed, and this is correct, the network that the instance is attached isn't an external network but the option of "Associate Floating IP" is incorrect.
HORIZON_BRANCH=master |
|
| 2017-10-21 01:39:01 |
Akihiro Motoki |
description |
If we have one network topology like the one attached, the instance "ne2" has the IP 20.0.0.3 but the 20.0.0.0/24 isn't an external network, but when we go to http://host/dashboard/project/instances/<instance-id>/ we see the option "Associate Floating IP" and when the pop-up "Manage Floating IP Associations" opens there aren't any port of instance "ne2" listed, and this is correct, the network that the instance is attached isn't an external network but the option of "Associate Floating IP" is incorrect.
HORIZON_BRANCH=master |
If we have one network topology like the one attached, the instance "ne2" has the IP 20.0.0.3 but the 20.0.0.0/24 is not connected to the external network, but when we go to http://host/dashboard/project/instances/<instance-id>/ we see the option "Associate Floating IP" and when the pop-up "Manage Floating IP Associations" opens there aren't any port of instance "ne2" listed, and this is correct. The network that the instance is attached to isn't reachable to an external network, so the option of "Associate Floating IP" is incorrect.
HORIZON_BRANCH=master |
|
