Sebc sg 2018

README.md

@@ -1,6 +1,5 @@
-# <center>Services Enablement Boot Camp 
-# <center> AKA Field Channel Enablement Install/Ops
-# <center> 
+# <center>Services Enablement Boot Camp
+# <center>
 
 This repository contains materials for Cloudera's Services Enablement
 Boot Camp and Cloudera FCE's internal boot camp.
@@ -22,10 +21,8 @@ as we will explain in class. The only changes you should make directly
 to your GitHub copy are Issues and Milestones, which are described in
 `README.md`.
 
-Add your instructors as Collaborators to your GitHub repo. Because
-we have 25 students and 4 people to facilitate labs, we'll give you
-all the GitHub names you need at the beginning of class. The lead
-instructor's GitHub name is `mfernest`.
+Add your instructor(s) as Collaborators to your GitHub repo. The lead
+instructor's GitHub name is `manojsundaram`.
 
 Adding your instructors as Collaborators will let them create <i>pull
 requests</i> on your work. This is a way of editing your submissions
@@ -64,7 +61,7 @@ repo:
     * Create two milestones: `Labs` and `Challenges`
     * Set the deadlines for Thursday and Friday of the current week.
 * Click the `Labels` button and change your labels as follows:
-    * Change `bug` to `stuck` 
+    * Change `bug` to `stuck`
     * Change `duplicate` to `started`
     * Change `enhancement` to `didNotSubmit`
     * Change `help wanted` to `complete`
@@ -78,4 +75,3 @@ all the settings described here, and point out anything that isn't
 setup correctly. This issue will be the only one you're asked to
 close.  All other issues are to be closed by an instructor to show
 no further review is needed.
-

README_Docs.md

@@ -1,17 +1,17 @@
 ## Notes on Cloudera documentation
 
 * Cloudera documentation is [available online](http://www.cloudera.com/documentation.html) in HTML and PDF format.
-* The current release is C5.9
+* The current release is C5.14
 
-Consider downloading these documents in PDF format. They are 
+Consider downloading these documents in PDF format. They are
 easier to read than the online HTML-based format.
 
 The docs may be updated between point releases to address typos and
 errors, but can also add new volumes or split materials to different
 volumes. There is currently no release notice that announces these
 updates.
 
-The C5.9 release comes with thirteen different documents:
+The C5.14 release comes with thirteen different documents:
 
 
 * [Introduction](http://www.cloudera.com/content/www/en-us/documentation/enterprise/latest/PDF/cloudera-introduction.pdf)

challenges/challenges.md

@@ -6,7 +6,7 @@
 ---
 <div style="page-break-after: always;"></div>
 
-# <center> Challenges - October 13, 2017 - Austin, TX 
+# <center> Challenges - May 18, 2018 - Singapore
 
 * Overview
   * Build a CM-managed CDH cluster and secure it
@@ -18,7 +18,7 @@
   * Submit only your own work
 * Update GitHub often -- don't wait until the end
 * If you break your cluster, or your cluster breaks you:
-  * Tell the instructor 
+  * Tell the instructor
   * Push the work you have into GitHub
   * Create an Issue to describe what you think went wrong
 
@@ -28,33 +28,34 @@
 ## <center> Challenge Setup
 
 * Create the Issue `Challenges Setup`
-* Make sure `mfernest` is a Collaborator
+* Make sure `manojsundaram` and `melvin-koh` are Collaborators
 * Assign the Issue to yourself and label it `started`
+* Destroy your lab instances and create 5 new instances (Follow the same instructions from the lab, plus make sure your root volume EBS storage has 50 GB allocated).
 * In the file `challenges/labs/0_setup.md`:
-  * List the cloud provider you are using 
+  * List the cloud provider you are using
   * List your instances by IP address and DNS name (don't use `/etc/hosts` for this)
-  * List the Linux release you are using 
-  * List the file system capacity for the first node 
-  * List the command and output for `yum repolist enabled` 
+  * List the Linux release you are using
+  * List the file system capacity for the first node
+  * List the command and output for `yum repolist enabled`
 * Add the following Linux accounts to all nodes
   * User `jimenez` with a UID of `2800`
   * User `beltran` with a UID of `2900`
   * Create the group `astros` and add `beltran` to it
   * Create the group `rangers` and add `jimenez` to it
-* List the `/etc/passwd` entries for `jimenez` and `beltran` 
+* List the `/etc/passwd` entries for `jimenez` and `beltran`
   * Do not list the entire file
-* List the `/etc/group` entries for `astros` and `rangers` 
+* List the `/etc/group` entries for `astros` and `rangers`
   * Do not list the entire file
-* Push these updates to GitHub 
-* Label your Issue `review` 
+* Push these updates to GitHub
+* Label your Issue `review`
 * Assign the Issue to the instructor
 
 ---
 <div style="page-break-after: always;"></div>
 
-## <center> Challenge 1: Install a MySQL server
+## <center> Challenge 1: Install a MySQL/MariaDB server
 
-* Create the Issue `Install Database` 
+* Create the Issue `Install Database`
 * Assign the Issue to yourself and label it `started`
 * Install MySQL 5.5 or MariaDB 5.5 on the first node listed in `0_setup.md`
   * Use a YUM repository to install the package
@@ -69,24 +70,24 @@
   * `hue`
   * `sentry`
 * Record the following in `challenges/labs/1_db-server.md`
-  * The command `hostname -f` and its output 
-  * The command `mysql -u <user> -p<password> -e "status;"` and its output 
-  * The command `mysql -u <user>  -p<password> -e "show databases;"` and its output 
+  * The command `hostname -f` and its output
+  * The command `mysql -u <user> -p<password> -e "status;"` and its output
+  * The command `mysql -u <user>  -p<password> -e "show databases;"` and its output
 * Push this work to GitHub
 * Label the Issue `review` and assign it to the instructor
 
 ---
 <div style="page-break-after: always;"></div>
 
-## <center> Challenge 2: Install Cloudera Manager 
+## <center> Challenge 2: Install Cloudera Manager
 
 * Create the Issue `Install CM`
 * Assign yourself and label it `started`
 * Install Cloudera Manager on the second node listed in `0_setup.md`
 * List the command and output for `ls /etc/yum.repos.d` in `challenges/labs/1_cm.md`
   * Copy `cloudera-manager.repo` to `challenges/labs/2_cloudera-manager.repo.md`
 * Connect Cloudera Manager Server to its database
-  * Use the `scm_prepare_database.sh` script to create the `db.properties` file 
+  * Use the `scm_prepare_database.sh` script to create the `db.properties` file
   * List the full command and its output in `2_properties.md`
   * Add the `db.properties` file content to `2_properties.md`
 * Start the Cloudera Manager server
@@ -99,7 +100,7 @@
 ---
 <div style="page-break-after: always;"></div>
 
-## <center> Challenge 3 - Install CDH 5.8
+## <center> Challenge 3 - Install CDH 5.13
 
 * Create the Issue `Install CDH`
 * Assign yourself and label it `started`
@@ -108,7 +109,7 @@
 * Create user directories in HDFS for `jimenez` and `beltran`
 * Add the following to `3_cm.md`:
     * The command and output for `hdfs dfs -ls /user`
-    * The command and output from the CM API call `../api/v5/hosts` 
+    * The command and output from the CM API call `../api/v5/hosts`
     * The command and output from the CM API call `../api/v11/clusters/<githubName>/services`
 * Install the Hive sample data using Hue
     * Copy a Hue screen that shows the tables are loaded to `challenges/labs/3_hue_hive.png`
@@ -123,13 +124,13 @@
 * Create the Issue `Test HDFS`
 * Assign yourself and label it `started`
 * As user `jimenez`, use `teragen` to generate a 65,536,000-record dataset
-  * Write the output to 8 files 
+  * Write the output to 8 files
   * Set the block size to 64 MB
   * Set the mapper container size to 512 MiB
   * Name the target directory `tgen`
   * Use the `time` command to capture job duration
 * Put the following in `challenges/labs/4_teragen.md`
-  * The full `teragen` command and output 
+  * The full `teragen` command and output
   * The result of the `time` command
   * The command and output of `hdfs dfs -ls /user/jimenez/tgen`
   * The command and output of `hadoop fsck -blocks /user/jimenez`
@@ -145,16 +146,16 @@
 * Assign the issue to yourself and label it `started`
 * Install an MIT KDC on the first node of your cluster
   * Name your realm after your GitHub handle
-  * Use `TX` as a suffix
-  * For example: `MFERNEST.TX`
+  * Use `SG` as a suffix
+  * For example: `MANOJS.SG`
 * Create Kerberos user principals for `jimenez`, `beltran`, and `cloudera-scm`
   * Assign `cloudera-scm` the privileges needed to create service principals and keytab files
 * Kerberize the cluster
 * Run the `terasort` program as user `jimenez` with the output target `/user/jimenez/tsort`
   * Use the `tgen` directory as input
   * Copy the command and full output to `challenges/labs/5_terasort.md`
 * Run the Hadoop `pi` program as user `beltran`
-  * Use the task parameters to `50` and `100` 
+  * Use the task parameters to `50` and `100`
   * Copy the command and full output to `challenges/labs/5_pi.md`
 *  Copy the configuration files in `/var/kerberos/krb5kdc/` to your repo:
     * Add the prefix `5_` and the suffix `.md` to the original file name
@@ -177,7 +178,7 @@
   * Assign the `astros` group to this role
 * Use `beeline` to select ten records from `web_logs`
 * Use `beeswax` to select ten records from `customers`
-* Capture the beeline text and save to `6_beeline.md` 
+* Capture the beeline text and save to `6_beeline.md`
 * Screen-capture the results for beeswax and save to `6_beeswax.png`
 * Label the issue `review`
 * Assign the issue to the instructor
@@ -189,10 +190,6 @@
 ## <center> When time runs out:
 
 * Commit any outstanding changes from your repo to GitHub
-* Email `mfe@cloudera.com`that you have stopped pushing to your repo
-* In-class candidates only:
-  * Please fill out [this survey form](https://goo.gl/forms/pmHeHx03zRu3cnlc2)
-  * Add your comments to `labs/7_feedback_final.md` -- remember to commit them!
-
+* Email `manojs@cloudera.com`that you have stopped pushing to your repo
 ---
 <div style="page-break-after: always;"></div>

clients/hue.md

@@ -19,7 +19,6 @@
 ## <center> <a name="hue_design_goals">HUE Design & Goals</a>
 
 * Customizable service portal
-    * Customer success story: [RainStor Embraces HUE](http://rainstor.com/rainstor-embraces-hue/)
 * Three client authentication modes
 * Graphical browsing and reporting
 * Application UIs
@@ -31,7 +30,7 @@
 
 ## <center> Current Version & Resources
 
-* C5.9 ==> [Hue 3.11](http://gethue.com/category/3-11/)
+* C5.14 ==> Hue 3.9.0
     * Apache-licensed, not an ASF project
     * Ported to HDP, MapR, Pivotal, IBM Big Insights
 * [Online demo available](http://demo.gethue.com/)
@@ -44,8 +43,8 @@
 
 ## <center> <a name="hue_services">HUE's Services</a>
 
-* <a href="hue_query_editors">Query editors</a>
-* <a href="hue_data_browsers">Data browsers</a>
+* [Query editors](hue.md#-query-support)
+* [Data browsers](hue.md#-data--metadata-browsers)
 * <a href="#hue_workflow_tools">Workflow tools</a>
 * <a href="#hue_search_console">Cloudera Search console</a>