cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-6925) [OVS] get rid custom logic to create bridges on hosts in the XenServer pool
Date Tue, 17 Jun 2014 12:11:02 GMT


ASF subversion and git services commented on CLOUDSTACK-6925:

Commit 8ca8a7217ec155a37b24e3d9cfc3d5fc67adef2d in cloudstack's branch refs/heads/4.4-forward
from [~murali.reddy]
[;h=8ca8a72 ]

CLOUDSTACK-6925: [OVS] get rid custom logic to create bridges on hosts
in the XenServer pool for GRE tunnel networks

Fix uses XenServer recommended way
which ensures bridge is created automatically on hosts in the pool for
GRE tunnel networks. Fix also gets rid of  error prone custom logic that ensures
bridge is created by plugging a VIF into the dom0 and connected to
GRE tunnel network.

> [OVS] get rid custom logic to create bridges on hosts in the XenServer pool
> ---------------------------------------------------------------------------
>                 Key: CLOUDSTACK-6925
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Murali Reddy
>            Assignee: Murali Reddy
>            Priority: Critical
>             Fix For: 4.4.0
> In XenServer, when we created a GRE tunnel network, they don't have a PIF attached it.
XenServer treats network without a PIF attached as internal network. In a pool, XenServer
internal network is visible across the hosts in the pool, but bridge is created only on the
first host on which VIF connected to internal network is started. On rest of the hosts when
VM is started, xapi fails with VM_REQUIRES_NETWORK exception. CloudStack had workaround for
this problem where it creates a dom0 VIF connected to the network. Which plugged and unplugged
to ensure bridge is created on all hosts in the pool. This approach is error prone and resulted
in multiple issues.
> Recommended way by XenServer, is to mark the network other-config param assume_network_is_shared
set to true.
> Network.other_config:assume_network_is_shared=true
> This will ensure, when a VM connected to a internal network is launched on any host in
the pool, bridge is automatically provisioned.

This message was sent by Atlassian JIRA

View raw message