Subject: [trill] TRILL FGL should support VM mobility

From: Haoweiguo <[email-masked]>
Date: Thu, 2 May 2013 12:40:19 +0000

Hi all,

The VMs belonging to same tenant can spread over multiple edge RBs, these VMs can use different local vlan to access same FGL network. FGL allocation can be through centralized orchestrator or distributed protocol and FGL should be ensured to be same in all trill campus for same tenant.
1,Centralized method:
When first VM belonging to a tenant accesses to trill campus, orchestrator should allocate new FGL to the tenant and download FGL and access vlan mapping information to the access edge RB. Later when other VMs of the tenant access,the orchestrator should use VN name to find already allocated FGL. If FGL is found successful, the orchestrator should use the already allocated FGL and download FGL and access vlan mapping information to the new access edge RB.

2,Distributed method:
When first VM belonging to a tenant accesses to trill campus,  edge RB allocates FGL by VN Name. Then the RB floods FGL and VN Name mapping information to TRILL campus, all other RBs should save the mapping information for later use. Later when other RBs of the tenant access to other edge RB, the edge RB should use VN name to find already allocated FGL by other edge RB.

Does trill protocol should be extended to support flooding FGL and VN name mapping information? comments are welcomed!

thanks

weiguo