You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Marcus Sorensen (JIRA)" <ji...@apache.org> on 2012/10/31 16:49:12 UTC
[jira] [Created] (CLOUDSTACK-432) VPC router cannot resolve its own
host name, slowing down commands
Marcus Sorensen created CLOUDSTACK-432:
------------------------------------------
Summary: VPC router cannot resolve its own host name, slowing down commands
Key: CLOUDSTACK-432
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-432
Project: CloudStack
Issue Type: Bug
Components: Network Devices
Affects Versions: 4.0.0
Environment: Testing VPC router with KVM
Reporter: Marcus Sorensen
Fix For: 4.0.0
With standard virtual router we echo in the gateway address into /etc/hosts, but with VPC router we don't, since there are multiple gateways. This causes iptables commands to be slow, since it wants to look itself up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-432) VPC router cannot resolve its
own host name, slowing down commands
Posted by "Marcus Sorensen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Sorensen resolved CLOUDSTACK-432.
----------------------------------------
Resolution: Fixed
See 761b4f60a10a49dc71c9aafabe4ed35e4694fd56. This should be sucked into the next roll up of 4.0.x or any RC.
> VPC router cannot resolve its own host name, slowing down commands
> ------------------------------------------------------------------
>
> Key: CLOUDSTACK-432
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-432
> Project: CloudStack
> Issue Type: Bug
> Components: Network Devices
> Affects Versions: 4.0.0
> Environment: Testing VPC router with KVM
> Reporter: Marcus Sorensen
> Fix For: 4.0.0
>
>
> With standard virtual router we echo in the gateway address into /etc/hosts, but with VPC router we don't, since there are multiple gateways. This causes iptables commands to be slow, since it wants to look itself up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-432) VPC router cannot resolve its own
host name, slowing down commands
Posted by "Marcus Sorensen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Sorensen closed CLOUDSTACK-432.
--------------------------------------
> VPC router cannot resolve its own host name, slowing down commands
> ------------------------------------------------------------------
>
> Key: CLOUDSTACK-432
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-432
> Project: CloudStack
> Issue Type: Bug
> Components: Network Devices
> Affects Versions: 4.0.0
> Environment: Testing VPC router with KVM
> Reporter: Marcus Sorensen
> Fix For: 4.0.0
>
>
> With standard virtual router we echo in the gateway address into /etc/hosts, but with VPC router we don't, since there are multiple gateways. This causes iptables commands to be slow, since it wants to look itself up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira