aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSteve McIntyre <steve.mcintyre@linaro.org>2015-07-31 16:55:54 +0100
committerSteve McIntyre <steve.mcintyre@linaro.org>2015-07-31 16:55:54 +0100
commitcc52470a1c1681a22ba40f0019987e1252cba653 (patch)
tree75f3ddabd36477882886d015b56584feaa36f248
parent866353e8e55f5753c09f46d79a14fd4e97f86505 (diff)
Updating README files for release v0.3v0.3
Change-Id: I344147b0b47df20224952d34c46efd3eb233ec2c
-rw-r--r--README20
-rw-r--r--test/README13
2 files changed, 21 insertions, 12 deletions
diff --git a/README b/README
index 445ff28..983a586 100644
--- a/README
+++ b/README
@@ -17,11 +17,19 @@ that other network management programs also exist, but either they
don't manage VLANs in the way we want or they depend on large
frameworks like Openstack.
-For *now*, VLANd includes two drivers for different families of Cisco
-switches. That's not great as a cross-platform selling point, but
-they're all we have available at the moment. Initial work is underway
-to support some TP-Link switches too, using the same driver API, and
-it is expected that more drivers will be included in future
+VLANd currently includes four drivers for different models of switch
+from three different vendors:
+
+ * CiscoCatalyst for the Cisco Catalyst 3750 (and compatible)
+ * CiscoSX300 for the Cisco SF300 and SG300 (and compatible)
+ * NetgearXSM for the Netgear XSM 7224S (and compatible)
+ * TPLinkTLSG2XXX for the TP-Link TL-SG2216 (and compatible)
+
+These cover a range of switches across a huge range of prices, from
+100M up to 10G ports. VLANd supports interoperable VLANs across all
+these devices, verified using the Linaro test lab and our test suite.
+
+It is expected that more drivers will be included in future
releases. Please feel free to propose more target devices, or (better)
send patches!
@@ -103,5 +111,5 @@ the GNU General Public License, version 2 (or any later version). See
the accompanying COPYING file for more details.
--------------------------------------------------------------------------
-README for VLANd 0.2, 13th February 2015
+README for VLANd 0.3, 31st July 2015
Steve McIntyre <steve.mcintyre@linaro.org>
diff --git a/test/README b/test/README
index 4c53a12..294836e 100644
--- a/test/README
+++ b/test/README
@@ -63,9 +63,9 @@ vlandswitch03 is a 24-port Netgear XSM 7224S (all 10G ports)
The test machines are a set of old/spare machines that we had in the
Linaro lab: 3 TI Panda boards, 4 Samsung Arndale boards and 3
-Freescale iMX53 Quickstart boards. The ordering doesn't matter here at
-all - we just want a set of machines with onboard ethernet that we can
-run trivial (ping and report) scripts on.
+Freescale iMX53 Quickstart boards. The ordering and the machine type
+doesn't matter here at all - we just want a set of machines with
+onboard ethernet that we can run trivial (ping and report) scripts on.
Initial test coverage
=====================
@@ -77,14 +77,15 @@ through. Each is of the style:
* Ensure all the ports we're using are on their base VLANs
* Start all the test machines logging (and wait 60s)
* Create some VLANs
- * Wait 10s for everything to settle
+ * Wait for everything to settle
* Move some of the ports to those new VLANs
- * Wait 60s for everything to settle
+ * Wait for everything to settle
* Move things back to their base VLANs
- * Wait 10s for everything to settle
+ * Wait for everything to settle
* Stop all the test machines logging (and wait 60s)
* Grab all the logs and store them as test results
* END
+ * Parse the results and say PASS/FAIL
As each test should put things back into a known sane state, they can
be chained together easily.