Update README.md

Author: shaunsmith

0-Setup.md

@@ -0,0 +1,130 @@
+# Environment Setup
+
+For convenience, each lab participant will be provided with an Oracle Cloud
+Infrastructure virtual machine configured with all the tools you'll need for
+this workshop.
+
+Your workshop instructor will provide you with the following:
+
+1. Participant Number--your unique id that will be incorporated into your user
+   id and your virtual machine name.  We'll also use it in the labs.
+2. User Id/Password--to enable you to log into the OCI Console and to deploy
+   functions
+3. Tenancy Name--that you will use to log into the OCI account.
+4. Auth Token--used as your password when logging into OCIR
+5. IP Address--of your hosted development environment machine
+6. VNC Password--to allow you to log into your hosted development machine
+7. URL of the preview release of the OCI SDK which includes Functions support.
+
+> As you make your way through this lab, look out for this icon.
+![user input](images/userinput.png) Whenever you see it, it's time for you to
+perform an action.
+
+## Pre-requisites
+
+Before we get started you'll need to log into the OCI account you've been
+provided to change your password from the temporary initial password.  Although
+we're going to be working in the Phoenix region, you'll need to login into
+Ashburn to reset your password.
+
+![user input](images/userinput.png) Log into the OCI console in Ashburn
+specifying the **cloudnative-devrel** tenancy.  
+
+https://console.us-ashburn-1.oraclecloud.com
+
+![Login Tenancy](images/login.png)
+
+![user input](images/userinput.png) Provide your username along with the initial password you were provided.
+
+![Login User](images/login-user.png)
+
+![user input](images/userinput.png) Provide a new password satisfying the
+requirements and record it for use during the workshop.
+
+![Login New Password](images/login-new-password.png)
+
+![user input](images/userinput.png) Once you've successfully changed
+your password and logged in, log out.  Later on we'll be logging into the
+Phoenix region console.
+
+![Select Region](images/logout.png)
+
+## Configuring your Environment
+
+Now that your user account is accessible, let's log into the provided VM where
+you'll be ready to start no configuration.
+
+To access your cloud-based development environment you'll need a VNC client
+on your laptop.  You can use whatever you have previously installed or you can
+use the VNC Viewer for Chrome that is extremely easy to install.
+
+https://chrome.google.com/webstore/detail/vnc%C2%AE-viewer-for-google-ch/iabmpiboiopbgfabjmgeedhcmjenhbla/related
+
+> NOTE: If you're curious about how to setup your own machine to build functions
+> and deploy them to Oracle Functions you can follow the instructions in the
+> [Quick Start
+> Guide](https://www.oracle.com/webfolder/technetwork/tutorials/infographics/oci_faas_gettingstarted_quickview/functions_quickview_top/functions_quickview/index.html#)
+
+![user input](images/userinput.png) Log into your VM using the provided IP
+Address and password.  The VNC port is *5903* so the server address you'll need
+to provide will look like `n.n.n.n:5903`
+
+Enter the provided VNC password to complete your login.
+
+![vnc login](images/vnc-login.png)
+
+
+Open a terminal and type the following command to ensure you are using the
+`workshop` context that points to Oracle Functions:
+
+![user input](images/userinput.png)
+>```sh
+>fn ls contexts
+>```
+
+Your output should look something like the following:
+
+```shell
+CURRENT NAME      PROVIDER  API URL                                         REGISTRY
+        default   default
+*       workshop  oracle    https://functions.us-phoenix-1.oraclecloud.com  phx.ocir.io/cloudnative-devrel/workshop-NNN
+```
+
+Now to make sure you can be authenticated correctly and communicate with 
+Oracle Functions let's run a command to list all of the existing applications.
+It doesn't matter what the results--just that you do get result to confirm
+connectivity.
+
+![user input](images/userinput.png)
+>```sh
+>fn ls apps
+>```
+
+You may see a list of applications something like this:
+
+```shell
+NAME        ID
+labapp-NNN  ocid1.fnapp.oc1.us-phoenix-1.aaaaaaaaag4h7xotdzz27sp7z23ci6z4jqj4raq43ui6ouae5k2kl7irx34a
+```
+
+## Clone the Workshop Repo
+
+Before we actually get started let's clone the git repo for this workshop so
+that you have all of the necessary materials.  Open a terminal and, in your
+home directory (i.e., /home/demo) type:
+
+![user input](images/userinput.png)
+>```sh
+>git clone https://github.com/shaunsmith/functionslab.git
+>```
+
+In the `functionslab` folder you'll find the sources for this workshop along
+with materials for some of the labs you'll be doing. 
+
+## All Set!
+
+Now that you're logged into your development machine, cloned the repo, and are
+able to communicate with Oracle Functions it's time to get started!
+
+NEXT: [*Function Labs*](1-Labs.md), UP: [*INDEX*](README.md)
+

1-Labs.md

@@ -0,0 +1,66 @@
+# Functions Labs
+
+In each of the following labs you'll explore a different aspect of Oracle
+Functions from creating, to deploying, to troubleshooting, to invoking.  In all
+cases you'll be using the `fn` CLI extensively so you may find these references
+helpful:
+
+* [fn Commands
+  Cheatsheet](https://github.com/sachin-pikle/functionslab/wiki/Functions-Commands-Cheatsheet)
+
+* [fn CLI docs](https://github.com/fnproject/docs/blob/master/cli/README.md)
+
+## Your First Function
+
+Now that `fn` CLI is installed and your development envirionment is configured,
+we can dig into the creation and running of functions.  In this lab you'll
+create, deploy, and run a Node.js function.  If you aren't a Node.js programmer
+don't panic! All the code is provided and is pretty easy to understand.  The
+focus of this tutorial is on becoming familiar with the basics of Fn, not
+Node.js programming.
+
+So let's [create and deploy your first function](3-First-Function.md).
+
+## Java Functions
+
+Fn provides an FDK (Function Development Kit) for each of the core supported
+programming languages.  But the Java FDK is the most advanced with support for
+Maven builds, automatic function argument type conversions, and comprehenive
+support for function testing with JUnit.
+
+The [Introduction to Java Functions](4-Java-Functions.md) lab covers all these
+topics and more.
+
+## Troubleshooting
+
+If you've been following the instructions in the tutorials carefully you
+shouldn't have run into any unexpected failures--hopefully!!  But in real life
+when you're writing code things go wrong--builds fail, exceptions are thrown,
+etc.  Fortunately the
+[Troubleshooting](5-Troubleshooting.md) tutorial
+introduces techniques you can use to track down the source of a failure.
+
+## Containers as Functions
+
+One of the coolest features of Fn is that while it's easy to write functions in
+various programming languages, you can also deploy Docker images as functions.
+This opens up entire world's of opportunity as you can package existing code,
+utilities, or use a programming language not yet supported by Fn.  Try the
+[Containers as Functions](6-Container-as-Function.md)
+tutorial to see how easy it is.
+
+## Functions Clients
+
+Functions can be invoked over HTTP using their "invoke endpoint".  You can
+either invoke the endpoint directly or use the OCI SDK to both manage and invoke
+functions.  In the [Functions Clients](7-Functions-Clients.md) lab we'll explore
+both direct use of HTTP as well as invocation using the OCI SDK for Functions.
+
+## OCI Services
+
+Functions frequently interact with and use other cloud services.  Oracle OCI
+provides a rich set of cloud service for building cloud native applications
+including Object Storage, Caching, and Database.  In the [OCI
+Services](8-OCI-Services.md) lab you'll see how a function can use the OCI SDK
+to read and write data to Object Storage.  While the lab uses Object Storage as
+an example, the approach is similar across all OCI services.