[Bootstrapping] Introduce an accelerator to put a ChromeOS device into Slave OOBE process.

chrome/common/pref_names.cc

Index: chrome/common/pref_names.cc
diff --git a/chrome/common/pref_names.cc b/chrome/common/pref_names.cc
index bde96d1fceea656091082eb613fb6bc93d7758ef..3302cc2a872d64a54003a2a84ccae06e70d28acf 100644
--- a/chrome/common/pref_names.cc
+++ b/chrome/common/pref_names.cc
@@ -1836,6 +1836,12 @@ const char kCustomizationDefaultWallpaperURL[] =
 // System uptime, when last logout started.
 // This is saved to file and cleared after chrome process starts.
 const char kLogoutStartedLast[] = "chromeos.logout-started";
+
+// The role of the device in the OOBE bootstrapping process. If it's a "slave"

[achuithb, 2016/10/05 22:24:10]

Maybe this:
If the device is a "slave" device, it's eligible to be enrolled by a "master"
device (which could be an Android app).

[xdai1, 2016/10/05 23:57:29]

Done.

+// device, then it's eligible to be helped by a "master" device (can also be an
+// Android App) to go through OOBE process and get enrolled into enterprise.
+const char kOobeBootstrappingRole[] = "oobe_bootstrapping";

[achuithb, 2016/10/05 22:24:10]

"is_oobe_bootstrapping_slave"?

[xdai1, 2016/10/05 23:57:29]

Done.

+
 #endif  // defined(OS_CHROMEOS)
 
 // Whether there is a Flash version installed that supports clearing LSO data.