[
https://issues.apache.org/jira/browse/CLOUDSTACK-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajani Karuturi updated CLOUDSTACK-6823:
----------------------------------------
Fix Version/s: (was: 4.5.0)
4.5.1
> Brocade Network plugin to orchestrate Brocade VDX switches
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-6823
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6823
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Affects Versions: 4.4.0
> Environment: • CloudStack supported KVM Hypervisor, VMWare,
> XenServer
> • Brocade VDX switches running Network Operating System 5.0 or above. The
> following models are supported:
> o VDX 8770, VDX 8770-8, VDX 8770-4, VDX 6740 and VDX 6740T
> Reporter: Ritu Sabharwal
> Assignee: Ritu Sabharwal
> Labels: Brocade
> Fix For: 4.5.1
>
>
> This plugin is focused on providing L2 services initially with other services
> coming in later. This feature is about a CloudStack network-guru plugin to
> automatically orchestrate Brocade’s switches to provide tenant isolation via
> VLAN. When isolated networks are created from CloudStack and allocated VLAN,
> a port profile is created on the switch for the network with the VLAN profile
> for the allocated VLAN which defines the VLAN membership for the overall port
> profile. When a VM is created and attached to the network, the VMs MAC
> address is associated with the port profile of the network. The port profile
> is applied to the switch when the MAC address is learned. When the VM is
> deleted, the VMs MAC address is disassociated from the port profile of the
> network. When an isolated Network is deleted, the port-profile for the
> network is deleted from the switches. The plugin also implements the
> capability to monitor the availability of the switch when it is configured
> first time. If there are no isolated Networks using the physical switch, the
> monitoring capability is disabled for the switch.
> The Brocade Network Plugin orchestrates Brocade’s switches using REST APIs.
> The plugin uses pre-configured properties file to provide the details of
> Brocade switches (IP Address, UserName, Password). In order to find out which
> switches are connected to the hypervisor hosts, the plugin uses the
> properties file to specify the pod to switch mapping.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
