Steps

OpenWhisk Actions Developer Lifecycle

Step1 of 5

Step 1

Introduction

OpenShift Container Platform

Red Hat OpenShift Container Platform is based on Kubernetes which is probably the most used Orchestrator for containers running in production. OpenShift is currently the only container platform based on Kuberenetes that offers multitenancy. This means that developers can have their own personal, isolated projects to test and verify application before committing to a shared code repository.

Apache OpenWhisk(Incubating)

Apache OpenWhisk(Incubating) is a serverless, open source cloud platform
that executes functions in response to events in any scale.

Since we will be using the user called developer throught this scenario it will be ideal to add admin role to the user developer to peform required tasks without switching user.

oc adm policy add-role-to-user admin developer -n faas

4. Open the OpenShift Web Console

OpenShift ships with a web-based console that will allow users to
perform various tasks via a browser. To get a feel for how the web console
works, click on the "OpenShift Console" tab next to the "Local Web Browser" tab.

The first screen you will see is the authentication screen. Enter your username and password and
then login, the default credentials is developer/developer:

After you have authenticated to the web console, you will be presented with a list of projects that your user has permission to view.

Click on your new project name to be taken to the project overview page which will list all of the routes, services, deployments, and pods that you have created as part of your project.

Congratulations

You have now prepared OpenShift environment for deploying ApacheOpenWhisk.

By default the OpenWhisk nginx route is configured to do "Redirect" for edge termination, in Katacoda
all the requests are secured hence we need to modify nginx route openwhisk insecureEdgeTerminationPolicy to "Allow"

Debugging Scenarios

Help

Katacoda offerings an Interactive Learning Environment for Developers. This course uses a command line and a pre-configured sandboxed environment for you to use. Below are useful commands when working with the environment.

cd <directory>

Change directory

ls

List directory

echo 'contents' > <file>

Write contents to a file

cat <file>

Output contents of file

Vim

In the case of certain exercises you will be required to edit files or text. The best approach is with Vim. Vim has two different modes, one for entering commands (Command Mode) and the other for entering text (Insert Mode). You need to switch between these two modes based on what you want to do. The basic commands are: