cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ritu Sabharwal (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-6823) Brocade Network plugin to orchestrate Brocade VDX switches
Date Mon, 02 Jun 2014 17:00:05 GMT
Ritu Sabharwal created CLOUDSTACK-6823:

             Summary: Brocade Network plugin to orchestrate Brocade VDX switches
                 Key: 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: •	KVM Hypervisor, VMWare, XenServer
•	Brocade switches running NOS (e.g. VDX 67xx, VDX 87xx)
            Reporter: Ritu Sabharwal
            Assignee: Ritu Sabharwal
             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.
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. 

This message was sent by Atlassian JIRA

View raw message