[
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 configured on 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
implements the capability to monitor the availability of the switch when it is
configured first time. When the switch is configured it is added to ClousStack
ResourceManager which enables the periodic pinging(monitoring) of the switch.
The Plugin would provide the implementation for getting the switch status. It
would be getting the current configuration.
If there are no VMs running for any of the isolated Networks using the physical
switch, the monitoring capability is disabled for the switch.
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 configured on 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 when it is configured first time.
If there are no VMs running for any of the isolated Networks using the physical
switch, the monitoring is disabled for the switch.
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.
> 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 4.1.1 or above.
> The following models are supported:
> VDX 8770, VDX 8770-8, VDX 8770-4, VDX 6740, VDX 6740T, VDX 6730, VDX 6720,
> VDX 6710
> 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 configured on 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 implements the capability to monitor the
> availability of the switch when it is configured first time. When the switch
> is configured it is added to ClousStack ResourceManager which enables the
> periodic pinging(monitoring) of the switch. The Plugin would provide the
> implementation for getting the switch status. It would be getting the current
> configuration.
> If there are no VMs running for any of the isolated Networks using the
> physical switch, the monitoring capability is disabled for the switch.
> 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)
