You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Ritu Sabharwal (JIRA)" <ji...@apache.org> on 2014/06/03 00:31:03 UTC
[jira] [Updated] (CLOUDSTACK-6823) Brocade Network plugin to
orchestrate Brocade VDX switches
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ritu Sabharwal updated CLOUDSTACK-6823:
---------------------------------------
Description:
This plugin is focused on providing L2 services initially with other services coming in later. This feature is about a CloudStack network-element plugin to automatically orchestrate Brocade’s switches to provide tenant isolation via VLAN. When isolated networks are created from CloudStack and allocated VLAN, the same VLANs need to be propagated to the physical switches as well, so that when a VLAN-tagged packet arrives on a switch-port, the switch know which ports to flood the packet. When the last VM is destroyed for an isolated Network, the VLAN Id for the network is disabled from the switches as well. The plugin also enables the periodic monitoring of the switch by adding it to the CloudStack ResourceManager when it is configured first time.
The Brocade Network Plugin orchestrates Brocade’s switches directly using NETCONF. The plugin uses pre-configured properties file to provide the details of Brocade switches (IP Address, UserName, Password).
In order to find out which switch-ports are connected to the hypervisor hosts, the plugin uses the properties file to specify the guest-traffic-label to switch-port mapping.
was:
This plugin is focused on providing L2 services initially with other services coming in later. This feature is about a CloudStack network-element plugin to automatically orchestrate Brocade’s switches to provide tenant isolation via VLAN. When isolated networks are created from CloudStack and allocated VLAN, the same VLANs need to be propagated to the physical switches as well, so that when a VLAN-tagged packet arrives on a switch-port, the switch know which ports to flood the packet.
The Brocade Network Plugin can orchestrate Brocade’s switches directly using NETCONF. The plugin use pre-configured properties file to provide the details of Brocade switches (IP Address, UserName, Password).
In order to find out which switch-ports are connected to the hypervisor hosts, the plugin uses the properties file to specify the guest-traffic-label to switch-port mapping.
Environment:
• CloudStack supported KVM Hypervisor, VMWare, XenServer
• Brocade switches running NOS (e.g. VDX 67xx, VDX 87xx)
was:
• KVM Hypervisor, VMWare, XenServer
• Brocade switches running NOS (e.g. VDX 67xx, VDX 87xx)
> 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 switches running NOS (e.g. VDX 67xx, VDX 87xx)
> Reporter: Ritu Sabharwal
> Assignee: Ritu Sabharwal
> Labels: Brocade
> Fix For: 4.5.0
>
>
> This plugin is focused on providing L2 services initially with other services coming in later. This feature is about a CloudStack network-element plugin to automatically orchestrate Brocade’s switches to provide tenant isolation via VLAN. When isolated networks are created from CloudStack and allocated VLAN, the same VLANs need to be propagated to the physical switches as well, so that when a VLAN-tagged packet arrives on a switch-port, the switch know which ports to flood the packet. When the last VM is destroyed for an isolated Network, the VLAN Id for the network is disabled from the switches as well. The plugin also enables the periodic monitoring of the switch by adding it to the CloudStack ResourceManager when it is configured first time.
> The Brocade Network Plugin orchestrates Brocade’s switches directly using NETCONF. The plugin uses pre-configured properties file to provide the details of Brocade switches (IP Address, UserName, Password).
> In order to find out which switch-ports are connected to the hypervisor hosts, the plugin uses the properties file to specify the guest-traffic-label to switch-port mapping.
--
This message was sent by Atlassian JIRA
(v6.2#6252)