diff --git a/CHANGES b/CHANGES
index d17e95e453b..2202d619976 100644
--- a/CHANGES
+++ b/CHANGES
@@ -26,7 +26,6 @@ New Features:
* Dedicated High-Availability Hosts
* Support for Amazon Web Services API (formerly a separate package)
* AWS API Extensions to include Tagging
- * Cisco Nexus 1000v Virtual Switch for ESX
* Support for Nicira NVP (L2)
* Ceph RBD Support for KVM
* Support for Caringo as Secondary Storage
diff --git a/docs/en-US/release-notes.xml b/docs/en-US/release-notes.xml
index ff324ae9666..4c060733145 100644
--- a/docs/en-US/release-notes.xml
+++ b/docs/en-US/release-notes.xml
@@ -1259,14 +1259,6 @@ Done restarting router(s).
easily enabled by setting the appropriate global configuration parameter and performing a
few setup steps.
-
- Support for Cisco Nexus 1000v Virtual Switch
- In addition to standard vSwitch, Cisco Nexus 1000v is now supported for virtual
- network configuration in VMware vSphere deployments. With this, guest traffic isolation
- through VLANs is possible in VMware environment. Using Nexus virtual switch simplifies
- configuring and monitoring virtual networks that span across a large number of hosts, and
- facilitates live migration in VMWare-based cloud deployment.
-
Issues Fixed in 4.0
@@ -1464,11 +1456,6 @@ Done restarting router(s).
Creating a VLAN range using Zone ID without network ID now
succeeds.
-
- CS-15256
- If adding a cluster fails the first time, now able to associate cluster
- with Nexus VSM upon retry.
-
CS-15243
Now check to be sure source NAT and VPN have same
@@ -1565,12 +1552,6 @@ Done restarting router(s).
Automatically starting the Console Proxy no longer fails due to its
missing volume on the primary storage
-
- CS-14952
- The vCenter IP Address and the datacenter information are now present in
- the "virtual_supervisor_module" table. The Nexus virtual switch credentials are
- now encrypted.
-
CS-14907
User is now correctly prevented from trying to download an uploaded
@@ -1966,6 +1947,14 @@ Done restarting router(s).
+
+ CLOUDSTACK-301
+ Nexus 1000v DVS integration is not functional
+ This source code release includes some partial functionality to
+ support the Cisco Nexus 1000v Distributed Virtual Switch within a VMware
+ hypervisor environment. The functionality is not complete at this time.
+
+
CLOUDSTACK-279
Deleting a project fails when executed by the regular user. This works as
@@ -2105,34 +2094,12 @@ Done restarting router(s).
Egress rules are not working in NetScaler loadbalancer.
-
- CS-15198
- Peak bandwidth (PIR) and burst size shaping policies are not applied on
- Nexus 1000v virtual switch interface.
-
CS-15163
The minimum limit is not honored when there is not enough capacity to
deploy all the VMs and the ec2-run-instances command with the -n >n1 -n2>
option is used to deploy multiple VMs.
-
- CS-15124
- Mixed switch environment is not supported. The zone can either be
- deployed as Standard vSwitch based or Nexus virtual switch based.
-
-
- CS-15118
- In a deployment with Nexus 1000v virtual switch, zone VLAN range is not
- validated against the reserved list of VLANs for Nexus 1000v.
-
-
- CS-15117
- In a deployment with Nexus 1000v virtual switch, disable/enable operation
- of the Nexus virtual switch is not working as expected. The Nexus 1000v virtual
- switch continues to be used to create network or edit network operations even
- after disabling the switch.
-
CS-15105
The cloud-sysvmadm script does not work if the integration.api.port
@@ -2375,34 +2342,12 @@ Done restarting router(s).
The cloud-sysvmadm script does not work if the integration.api.port
parameter is set to any port other than 8096.
-
- CS-15117
- In a deployment with Nexus 1000v virtual switch, disable/enable operation
- of the Nexus virtual switch is not working as expected. The Nexus 1000v virtual
- switch continues to be used to create network or edit network operations even
- after disabling the switch.
-
-
- CS-15118
- In a deployment with Nexus 1000v virtual switch, zone VLAN range is not
- validated against the reserved list of VLANs for Nexus 1000v.
-
-
- CS-15124
- Mixed switch environment is not supported. The zone can either be
- deployed as Standard vSwitch based or Nexus virtual switch based.
-
CS-15163
The minimum limit is not honored when there is not enough capacity to
deploy all the VMs and the ec2-run-instances command with the -n >n1 -n2>
option is used to deploy multiple VMs.
-
- CS-15198
- Peak bandwidth (PIR) and burst size shaping policies are not applied on
- Nexus 1000v virtual switch interface.
-
@@ -2539,20 +2484,6 @@ Done restarting router(s).
listVpnConnections (Lists site to site vpn connection gateways)
-
- listCiscoNexusVSMs(Retrieves information of a Cisco Nexus 1000v virtual switch
- associated with a cluster. It lists the control VLAN ID, packet VLAN ID, and data VLAN
- ID, as well as the IP address of the Nexus virtual switch)
-
-
- enableCiscoNexusVSM(Enables a Cisco Nexus VSM device)
-
-
- disableCiscoNexusVSM (Disables a Cisco Nexus VSM device)
-
-
- deleteCiscoNexusVSM (Deletes a Cisco Nexus VSM device)
-
markDefaultZoneForAccount (Marks a default zone for the current account)