[yocto] [yocto-autobuilder][PATCH v1 2/4] README: add high level overview, fix build slave description

[stefan at agner.ch]

From: Stefan Agner <stefan at agner.ch>

Replace builders with build slaves, since this are different things
in BuildBot world. Also add a section with some high level view
what Autobuilder actually is.

Signed-off-by: Stefan Agner <stefan at agner.ch>
---
 README                 |  8 ++++----
 README-NEW-AUTOBUILDER | 11 +++++++++++
 2 files changed, 15 insertions(+), 4 deletions(-)

diff --git a/README b/README
index c7c9acf..3b418fd 100644
--- a/README
+++ b/README
@@ -26,7 +26,7 @@ Setup
        connection that I haven't figured out yet. Manually connecting seems to 
        set up the session correctly.)
 
-2. Adding additional builders
+2. Adding additional build slaves
 
     The production yocto autobuilder uses a cluster of build slaves, all sharing
     the same SSTATE_DIR and DL_DIR via an NFS4 mounted NAS. The main nightly 
@@ -36,7 +36,7 @@ Setup
     In theory you could also run your build slaves with NO_NETWORK to enforce a 
     single point of populating DL_DIR.
 
-    Running multiple builders is fairly simple, but does require some setup.
+    Running multiple build slaves is fairly simple, but does require some setup.
 
     1. Ensure the autobuilder.conf for each build slave is appropriate. As
        certain variables are set within this file that are local to each builder
@@ -45,7 +45,7 @@ Setup
     2. Within yocto-master/master.cfg make the following changes substituing 
        <PASS> for your debug password and  max_builds for the number of builds 
        you wish to run on each builder. Your main builder that will run the 
-       nightly trigger buildset should have at least 2 builders running.
+       nightly trigger buildset should have at least 2 build slaves running.
 
 
 c['slaves'] = [BuildSlave("builder1", "<PASS>", max_builds=3),
@@ -53,7 +53,7 @@ c['slaves'] = [BuildSlave("builder1", "<PASS>", max_builds=3),
                BuildSlave("builder3", "<PASS>", max_builds=3),
                BuildSlave("builder4", "<PASS>", max_builds=3)]
 
-    3. For each buildslave change yocto-slave/buildbot.tac to point to the 
+    3. For each build slave change yocto-slave/buildbot.tac to point to the 
        correct build master and port. The default setup points to local host.
 
 buildmaster_host = 'builder1.myproject.org'
diff --git a/README-NEW-AUTOBUILDER b/README-NEW-AUTOBUILDER
index 1e46f5b..acb5387 100644
--- a/README-NEW-AUTOBUILDER
+++ b/README-NEW-AUTOBUILDER
@@ -23,6 +23,17 @@ TODO
 - deploy stuff
 - killing triggers. this has been a long standing issue. look into
 
+What is it
+------------
+Yocto Autobuilder is essentially some extension to the vanilla build bot.
+This extension mainly addresses configuration file handling and Yocto specific
+build steps.
+For better maintainability, the Autobuilder (see Autobuilder.py located at
+lib/python2.7/site-packages/autobuilder/), handles configuration from multiple
+files.
+Additional build steps such as CheckOutLayers.py or CreateBBLayersConf are
+Yocto specific and simplify the bulders configuration.
+
 Setup
 ------------
 Nothing here has changed much. 
-- 
1.9.0