Page History

...

• The isolated port(I-port) in private vlan concept fit prefect for our requirement. Basically we just need to make every user VM connect to I-port of the switch(vswitch or open vswitch), every dhcp server connect to P-port of the switch, then it would be enough for isolation and communication.
• But open vswitch(used by XenServer and KVM) doesn't have PVLAN support. vSwitch(for VMware) support it by default.
• So we need extra effort to simulate PVLAN on open vswitch(ovs) for Xen and KVM.
  • We would modify flow table, to:
  • 1. For every traffic leave user VM, tagged with secondary isolate vlan tag.
  • 2. Allow secondary isolated vlan tagged traffic reach DHCP server, by change the vlan tag to primary vlan tag.
  • 3. The gateway should know nothing about PVLAN, and the switch connect to the gateway should translate all the secondary vlan to primary vlan for communicating with gateway.

...

Assumptions / Pre-requisites

• Need PVLAN supported switch(refer to http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a0080094830.shtml) to connect to host.
• Only one switch would connect to gateway, other switches need to be connect to this switch via trunk port.
  • It's an ideal situation. Only Cisco Catalyst 4500 has pvlan promiscuous trunk mode to trunk both normal vlan and pvlan to pvlan-unaware switch.
  • For other Catalyst pvlan support switch, you need to connect switch to upper switch using at least (pvlan number + 1) cables to archive this.

...

• Though CloudStack didn't control switch, the switches must support Private VLAN in order to get the whole setup work. This would require certain Cisco Catalyst switches.
  • It's likely we would need Catalyst 4500 series for PVLAN promiscuous trunk support.
• The topological of switch and router would be:
  • All L2 switch(which are aware of PVLAN) connected to each other, and one of them(and only one of them) connect to router.
  • All the ports connected to the host would be configured in trunk mode, allow mgmt vlan, primary vlan(public vlan) and secondary isolated vlan.
  • The switch port connect to the router would be configured in PVLAN promiscuous trunk mode, which would translate secondary isolated vlan to primary vlan for router(which doesn't have knowledge of PVLAN).
  • If your Catalyst switch support PVLAN but not PVLAN promiscuous trunk mode(AFAIK, only Catalyst 4500 series support the mode), you need:
    • 1. Configure one of switch port as trunk for mgmt network(mgmt vlan)
    • 2. For each PVLAN, connect one port of Catalyst switch to upper switch, set the port in Catalyst Switch in promiscuous mode for one pair of PVLAN, set the port in upper switch to "access" mode, only allow traffic of primary vlan of the PVLAN pair.

Web Services APIs

PVLAN can be enabled on shared networks. Shared networks are created by admin users, end user vms are allowed to have nics on shared networks.
Modify createNetworkCmd :(for shared networks)

• Add a new parameter: secondary_isolated_vlan:
  • Not a required paramter. if the parameter is not null, then PVLAN would be enabled.
  • When the parameter is set, it must be advance shared network.

UI flow

• either demonstrate it visually here or link to relevant mockupsThe admin creates a shared vlan. She is asked if it is a PVLAN. If yes, in addition to the primary vlan id, she is asked for the secondary vlan id.
  The pre-confirmation dialog asks her to make sure her physical infrastructure is configured in the same fashion.

IP Clearance

• what dependencies will you be adding to the project?

...