[telemetry] Implement Forwarder using RNDIS.

tools/telemetry/telemetry/core/browser_options.py

Index: tools/telemetry/telemetry/core/browser_options.py
diff --git a/tools/telemetry/telemetry/core/browser_options.py b/tools/telemetry/telemetry/core/browser_options.py
index 4078fe47b2ffc902ac3ed8c377d2ffedc2341519..2fc41299bb85ea63750b1972779c146a7783af23 100644
--- a/tools/telemetry/telemetry/core/browser_options.py
+++ b/tools/telemetry/telemetry/core/browser_options.py
@@ -86,6 +86,9 @@ class BrowserOptions(optparse.Values):
              'kept. When this is run via a sharder '
              'the test server ports should be kept and '
              'should not be reset.')
+    group.add_option('--android_rndis', action='store_true',

[tonyg, 2013/08/22 23:55:03]

While I like bulach's goal of having a controlled rollout, the unfortunate thing
about a real command line flag is that this will require a master restart to
toggle this flag on the chromium.perf waterfall. To avoid this hassle, I suggest
we just add a local boolean _USE_RDNIS_FORWARDING and set it to False in this
patch. Then when we experiment with enabling this, we can just change the value
with a simple chromium src commit.

[szym, 2013/08/23 15:33:41]

Ack.

+        help='Use RNDIS forwarding on Android. '
+             'Fall back to user-space Forwarder on failure.')

[tonyg, 2013/08/22 23:55:03]

If this flag is set, I don't think we want to fall back. It should fail hard if
rndis doesn't work.

[szym, 2013/08/23 15:33:41]

What if there's no flag? I'm assuming you are suggesting to remove it above.

     group.add_option(
         '--remote',
         dest='cros_remote',