[CLOUDSTACK-6925] [OVS] get rid custom logic to create bridges on hosts in the XenServer pool

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 4.2.0
• Fix Version/s: 4.4.0
• Security Level: Public (Anyone can view this level - this is the default.)
• Assignee: Murali Reddy
• Reporter: Murali Reddy
• Created: 17/Jun/14 11:35
• Updated: 17/Jun/14 12:34
• Resolved: 17/Jun/14 12:27

Description

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.