** Changed in: nova
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1022612
Title:
private instance IPs can only reach public IPs in other regions,
AFAIK this is a design issue with nova-network that isn't easy to fix.
The preffered way forward is to Neutron.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1022612
Title:
private in
Nick, no documentation of the behavior does not mean the behavior still
exists in the code, so it is not enough.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1022612
Title:
private i
If anything, this looks related to bug #1178745
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1022612
Title:
private instance IPs can only reach public IPs in other regions, not
the
Joe Gordon: Are you unable to reproduce this? We found documentation of
this behaviour in openstack's official Web pages. Is that not enough?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/b
Are a1/a2 on the same host? what version of nova etc?
** Changed in: nova
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1022612
Title:
private insta
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1022612
Title:
private instance IPs can only reach public IPs in other
>From http://docs.openstack.org/folsom/openstack-compute/admin/content
/associating-public-ip.html:
"""
Traffic between VMs using floating IPs:
Note that due to the way floating IPs are implemented using a source NAT (SNAT
rule in iptables), inconsistent behaviour of security groups can be seen
This may be pertinent:
http://docs.openstack.org/trunk/openstack-compute/admin/content
/associating-public-ip.html
"Note that you cannot SSH to an instance with a public IP from within
the same server as the routing configuration won't allow it."
This would explain the reason why 'a1' can't see
Confirmed; instances within a region don't appear to be able to contact
public addresses for either themselves or other instances in the same
region.
** Changed in: nova (Ubuntu)
Status: New => Confirmed
** Changed in: nova (Ubuntu)
Importance: Undecided => High
--
You received this b
FTR, actually A1 can't reach it's public IP either.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1022612
Title:
private instance IPs can only reach public IPs in other regions, not
11 matches
Mail list logo
