Skip to content

Commit ba18b78

Browse files
committed
Removing references to the Nexus 1KV as a functional switching option, due to delaying CLOUDSTACK-301 to a later release.
1 parent f1e05ac commit ba18b78

2 files changed

Lines changed: 8 additions & 78 deletions

File tree

CHANGES

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,6 @@ New Features:
2626
* Dedicated High-Availability Hosts
2727
* Support for Amazon Web Services API (formerly a separate package)
2828
* AWS API Extensions to include Tagging
29-
* Cisco Nexus 1000v Virtual Switch for ESX
3029
* Support for Nicira NVP (L2)
3130
* Ceph RBD Support for KVM
3231
* Support for Caringo as Secondary Storage

docs/en-US/release-notes.xml

Lines changed: 8 additions & 77 deletions
Original file line numberDiff line numberDiff line change
@@ -1259,14 +1259,6 @@ Done restarting router(s).
12591259
easily enabled by setting the appropriate global configuration parameter and performing a
12601260
few setup steps.</para>
12611261
</section>
1262-
<section id="support-nexus-dvswitch">
1263-
<title>Support for Cisco Nexus 1000v Virtual Switch</title>
1264-
<para>In addition to standard vSwitch, Cisco Nexus 1000v is now supported for virtual
1265-
network configuration in VMware vSphere deployments. With this, guest traffic isolation
1266-
through VLANs is possible in VMware environment. Using Nexus virtual switch simplifies
1267-
configuring and monitoring virtual networks that span across a large number of hosts, and
1268-
facilitates live migration in VMWare-based cloud deployment.</para>
1269-
</section>
12701262
</section>
12711263
<section id="issues-fixed-4.0">
12721264
<title>Issues Fixed in 4.0</title>
@@ -1464,11 +1456,6 @@ Done restarting router(s).
14641456
<entry><para>Creating a VLAN range using Zone ID without network ID now
14651457
succeeds.</para></entry>
14661458
</row>
1467-
<row>
1468-
<entry><para>CS-15256</para></entry>
1469-
<entry><para>If adding a cluster fails the first time, now able to associate cluster
1470-
with Nexus VSM upon retry.</para></entry>
1471-
</row>
14721459
<row>
14731460
<entry><para>CS-15243</para></entry>
14741461
<entry><para>Now check to be sure source NAT and VPN have same
@@ -1565,12 +1552,6 @@ Done restarting router(s).
15651552
<entry><para>Automatically starting the Console Proxy no longer fails due to its
15661553
missing volume on the primary storage</para></entry>
15671554
</row>
1568-
<row>
1569-
<entry><para>CS-14952</para></entry>
1570-
<entry><para>The vCenter IP Address and the datacenter information are now present in
1571-
the "virtual_supervisor_module" table. The Nexus virtual switch credentials are
1572-
now encrypted.</para></entry>
1573-
</row>
15741555
<row>
15751556
<entry><para>CS-14907</para></entry>
15761557
<entry><para>User is now correctly prevented from trying to download an uploaded
@@ -1966,6 +1947,14 @@ Done restarting router(s).
19661947
</row>
19671948
</thead>
19681949
<tbody>
1950+
<row>
1951+
<entry><para>CLOUDSTACK-301</para></entry>
1952+
<entry><para>Nexus 1000v DVS integration is not functional</para>
1953+
<para>This source code release includes some partial functionality to
1954+
support the Cisco Nexus 1000v Distributed Virtual Switch within a VMware
1955+
hypervisor environment. The functionality is not complete at this time.</para>
1956+
</entry>
1957+
</row>
19691958
<row>
19701959
<entry><para>CLOUDSTACK-279</para></entry>
19711960
<entry><para>Deleting a project fails when executed by the regular user. This works as
@@ -2105,34 +2094,12 @@ Done restarting router(s).
21052094
<entry><para>Egress rules are not working in NetScaler loadbalancer.</para>
21062095
</entry>
21072096
</row>
2108-
<row>
2109-
<entry><para>CS-15198</para></entry>
2110-
<entry><para>Peak bandwidth (PIR) and burst size shaping policies are not applied on
2111-
Nexus 1000v virtual switch interface.</para></entry>
2112-
</row>
21132097
<row>
21142098
<entry><para>CS-15163</para></entry>
21152099
<entry><para>The minimum limit is not honored when there is not enough capacity to
21162100
deploy all the VMs and the ec2-run-instances command with the -n &gt;n1 -n2&gt;
21172101
option is used to deploy multiple VMs.</para></entry>
21182102
</row>
2119-
<row>
2120-
<entry><para>CS-15124</para></entry>
2121-
<entry><para>Mixed switch environment is not supported. The zone can either be
2122-
deployed as Standard vSwitch based or Nexus virtual switch based.</para></entry>
2123-
</row>
2124-
<row>
2125-
<entry><para>CS-15118</para></entry>
2126-
<entry><para>In a deployment with Nexus 1000v virtual switch, zone VLAN range is not
2127-
validated against the reserved list of VLANs for Nexus 1000v.</para></entry>
2128-
</row>
2129-
<row>
2130-
<entry><para>CS-15117</para></entry>
2131-
<entry><para>In a deployment with Nexus 1000v virtual switch, disable/enable operation
2132-
of the Nexus virtual switch is not working as expected. The Nexus 1000v virtual
2133-
switch continues to be used to create network or edit network operations even
2134-
after disabling the switch.</para></entry>
2135-
</row>
21362103
<row>
21372104
<entry><para>CS-15105</para></entry>
21382105
<entry><para>The cloud-sysvmadm script does not work if the integration.api.port
@@ -2375,34 +2342,12 @@ Done restarting router(s).
23752342
<entry><para>The cloud-sysvmadm script does not work if the integration.api.port
23762343
parameter is set to any port other than 8096.</para></entry>
23772344
</row>
2378-
<row>
2379-
<entry><para>CS-15117</para></entry>
2380-
<entry><para>In a deployment with Nexus 1000v virtual switch, disable/enable operation
2381-
of the Nexus virtual switch is not working as expected. The Nexus 1000v virtual
2382-
switch continues to be used to create network or edit network operations even
2383-
after disabling the switch.</para></entry>
2384-
</row>
2385-
<row>
2386-
<entry><para>CS-15118</para></entry>
2387-
<entry><para>In a deployment with Nexus 1000v virtual switch, zone VLAN range is not
2388-
validated against the reserved list of VLANs for Nexus 1000v.</para></entry>
2389-
</row>
2390-
<row>
2391-
<entry><para>CS-15124</para></entry>
2392-
<entry><para>Mixed switch environment is not supported. The zone can either be
2393-
deployed as Standard vSwitch based or Nexus virtual switch based.</para></entry>
2394-
</row>
23952345
<row>
23962346
<entry><para>CS-15163</para></entry>
23972347
<entry><para>The minimum limit is not honored when there is not enough capacity to
23982348
deploy all the VMs and the ec2-run-instances command with the -n &gt;n1 -n2&gt;
23992349
option is used to deploy multiple VMs.</para></entry>
24002350
</row>
2401-
<row>
2402-
<entry><para>CS-15198</para></entry>
2403-
<entry><para>Peak bandwidth (PIR) and burst size shaping policies are not applied on
2404-
Nexus 1000v virtual switch interface.</para></entry>
2405-
</row>
24062351
</tbody>
24072352
</tgroup>
24082353
</informaltable>
@@ -2539,20 +2484,6 @@ Done restarting router(s).
25392484
<listitem>
25402485
<para>listVpnConnections (Lists site to site vpn connection gateways)</para>
25412486
</listitem>
2542-
<listitem>
2543-
<para>listCiscoNexusVSMs(Retrieves information of a Cisco Nexus 1000v virtual switch
2544-
associated with a cluster. It lists the control VLAN ID, packet VLAN ID, and data VLAN
2545-
ID, as well as the IP address of the Nexus virtual switch)</para>
2546-
</listitem>
2547-
<listitem>
2548-
<para>enableCiscoNexusVSM(Enables a Cisco Nexus VSM device)</para>
2549-
</listitem>
2550-
<listitem>
2551-
<para>disableCiscoNexusVSM (Disables a Cisco Nexus VSM device)</para>
2552-
</listitem>
2553-
<listitem>
2554-
<para>deleteCiscoNexusVSM (Deletes a Cisco Nexus VSM device)</para>
2555-
</listitem>
25562487
<listitem>
25572488
<para>markDefaultZoneForAccount (Marks a default zone for the current account)</para>
25582489
</listitem>

0 commit comments

Comments
 (0)