Functions QuickStart on an OCI Compute Instance

If suitable users and groups don't exist already:

1. Sign in to the Console as a tenancy administrator.
2. Open the navigation menu and click Identity & Security. Under Identity, click Domains.
3. Create a new group by clicking Groups and then Create Group.
   
4. Create a new user by clicking Users and then Create User.
   
5. Add a user to a group by clicking Groups, then the name of the group, and then Add User to Group.
   

See Configuration Notes for more information.

If a suitable compartment in which to create network resources and OCI Functions resources doesn't exist already:

1. Sign in to the Console as a tenancy administrator.
2. Open the navigation menu and click Identity & Security. Under Identity, click Compartments.
3. Click Create Compartment.
   

See Configuration Notes for more information.

If a suitable VCN in which to create network resources doesn't exist already:

See Configuration Notes for more information.

If one or more OCI Functions users is not a tenancy administrator:

1. Sign in to the Console as a tenancy administrator.
2. Open the navigation menu and click Identity & Security. Under Identity, click Policies.

3. Click Create Policy, specify a name and description for the new policy, and select the tenancy's root compartment.

4. Use the Policy Builder to create the policy. Select Functions from the list of Policy use cases, and base the policy on the policy template Let users create, deploy, and manage functions and applications.

   

   The policy template includes the following policy statements:

   • Allow group <group-name> to use cloud-shell in tenancy
   • Allow group <group-name> to manage repos in tenancy
   • Allow group <group-name> to read objectstorage-namespaces in tenancy
   • Allow group <group-name> to manage logging-family in tenancy
   • Allow group <group-name> to read metrics in tenancy
   • Allow group <group-name> to manage functions-family in tenancy
   • Allow group <group-name> to use virtual-network-family in tenancy
   • Allow group <group-name> to use apm-domains in tenancy
   • Allow group <group-name> to read vaults in tenancy
   • Allow group <group-name> to use keys in tenancy
   • Allow service faas to use apm-domains in tenancy
   • Allow service faas to read repos in tenancy where request.operation='ListContainerImageSignatures'
   • Allow service faas to {KEY_READ} in tenancy where request.operation='GetKeyVersion'
   • Allow service faas to {KEY_VERIFY} in tenancy where request.operation='Verify'

   If necessary, you can restrict these policy statements by compartment.

See Configuration Notes for more information.

1. Sign in to the Console as a functions developer.
2. Open the navigation menu and click Developer Services. Under Functions, click Applications.
3. Select the region you're using with OCI Functions.
4. Click Create Application.
   
5. Specify:
   • helloworld-app as the name for the new application. You'll deploy your first function in this application, and specify this application when invoking the function.
   • The VCN and subnet in which to run the function. Note that a public subnet requires an internet gateway in the VCN, and a private subnet requires a service gateway in the VCN.
6. Click Create.

See detailed instructions for more information.

1. Sign in to the Console as a tenancy administrator.
2. Open the navigation menu and click Compute. Under Compute, click Instances.
3. Select the compartment in which to create network resources and OCI Functions resources.
4. If a suitable compute instance doesn't exist in the compartment already, click Create Instance and:
   • select the compartment, VCN, and subnets for use with OCI Functions
   • specify that a public IP address is to be assigned to the new compute instance
   • select the file that contains the SSH key to access the new compute instance

5. On the Instance Details page, copy the OCID and public IP address of the compute instance to use as the development environment.

See Creating an Instance for more information.

Create a new dynamic group to include the compute instance:

1. Open the navigation menu and click Identity & Security. Under Identity, click Domains. Under Identity domain, click Dynamic groups.
2. Create a new dynamic group.

3. Enter a rule that includes the compute instance's OCID:

   ANY {instance.id = '<instance-ocid>'}

See Managing Dynamic Groups for more information.

Create a policy to give the new dynamic group access to function resources, network resources, and Oracle Cloud Infrastructure Registry:

1. Open the navigation menu and click Identity & Security. Under Identity, click Policies.

2. Click Create Policy and use the Policy Builder's manual editor to create a new policy with the following policy statements:

   • Allow dynamic-group <dynamic-group-name> to manage functions-family in compartment <compartment-name>
   • Allow dynamic-group <dynamic-group-name> to use virtual-network-family in compartment <compartment-name>
   • Allow dynamic-group <dynamic-group-name> to read repos in tenancy

See Managing Policies for more information.

In a terminal window in your development environment:

1. Confirm that Docker is installed by entering:

   docker version

   If you see an error message indicating that Docker is not installed, you have to install Docker before proceeding. See the Docker documentation for your platform (for Oracle Linux, see here).

   Assuming Docker is installed, go to the Prerequisites section of the Fn Project home page on GitHub and confirm that the installed version of Docker is at least the minimum version specified there. If not, re-install Docker before proceeding.

2. Launch the standard hello-world Docker image as a container to confirm that Docker is running by entering:

   docker run hello-world

   If you see an error message indicating that Docker is not running, you have to start the Docker daemon before proceeding. See the Docker documentation.

See Configuration Notes for more information.

In a terminal window in your development environment:

1. Install the Fn Project CLI using the appropriate instructions below for your environment:
   • Linux or MacOS: Enter:

     curl -LSs https://raw.githubusercontent.com/fnproject/cli/master/install | sh

   • MacOS using Homebrew: Enter:

     brew update && brew install fn

   • Windows: Follow the Install Fn Client instructions on GitHub.
   • Linux, MacOS, or Windows: Download and run the binary from the Fn Project Releases page on GitHub.
2. Confirm that the Fn Project CLI has been installed by entering:

   fn version

See Configuration Notes for more information.

In a terminal window in your development environment:

1. Create a new Fn Project CLI context by entering:

   fn create context <my-context> --provider oracle-ip

   Note that you specify --provider oracle-ip to enable authentication and authorization using instance OCIDs, dynamic groups, and policies granting permissions to those dynamic groups.

2. Specify that the Fn Project CLI is to use the new context by entering:

   fn use context <my-context>

See Configuration Notes for more information.

In a terminal window in your development environment:

1. Configure the new Fn Project CLI context with the OCID of the compartment you want to own deployed functions

   fn update context oracle.compartment-id <compartment-ocid>

2. Configure the new context with the api-url endpoint to use when calling the OCI API by entering:

   fn update context api-url <api-endpoint>

   where <api-endpoint> is one of the endpoints in the list of Functions endpoints in Functions API, in the format https://functions.<region-identifier>.oci.oraclecloud.com. For example:

   fn update context api-url https://functions.us-phoenix-1.oci.oraclecloud.com

3. Configure the Fn Project CLI context with the Oracle Cloud Infrastructure Registry address in the current region and tenancy that you want to use with OCI Functions:

   fn update context registry <region-key>.ocir.io/<tenancy-namespace>/<repo-name-prefix>

   where <repo-name-prefix> is a prefix of your choosing for the Oracle Cloud Infrastructure Registry repository in which to store images for the function. For example:

   fn update context registry phx.ocir.io/ansh81vru1zp/acme-repo

4. Configure the Fn Project CLI context with the OCID of the compartment for repositories to and from which you want OCI Functions to push and pull function images, by entering:

   fn update context oracle.image-compartment-id <compartment-ocid>

   For example:

   fn update context oracle.image-compartment-id ocid1.compartment.oc1..aaaaaaaaquqe______z2q

   If you do not specify a value for oracle.image-compartment-id, OCI Functions pushes and pulls images to and from repositories in the root compartment.

See Configuration Notes for more information.

1. Sign in to the Console as a functions developer.
2. Open the User menu and go to User Settings. On the Auth Tokens page, click Generate Token.
3. Enter a meaningful description for the auth token in the Generate Token dialog, and click Generate Token. The new auth token is displayed.
4. Copy the auth token immediately to a secure location from where you can retrieve it later, because you won't see the auth token again in the Console.
5. Close the Generate Token dialog.

See Configuration Notes for more information.

In a terminal window in your development environment:

1. Enter the following command:

   docker login -u '<tenancy-namespace>/<user-name>' <region-key>.ocir.io

   For example:

   docker login -u 'ansh81vru1zp/jdoe@acme.com' phx.ocir.io

   If your tenancy is federated with Oracle Identity Cloud Service, the format will be slightly different. For example:

   docker login -u 'ansh81vru1zp/oracleidentitycloudservice/jdoe@acme.com' phx.ocir.io

2. When prompted for a password, enter the Oracle Cloud Infrastructure auth token that you created and copied earlier. For example, 6aN...6MqX

   You're now ready to start creating, deploying, and invoking functions.

See Configuration Notes for more information.

In the terminal window:

1. Create a helloworld java function by entering:

   fn init --runtime java hello-java

   A directory called hello-java is created, containing:

   • a function definition file called func.yaml
   • a /src directory containing source files and directories for the helloworld function
   • a Maven configuration file called pom.xml that specifies the dependencies required to compile the function

   Java is just one of several supported languages.

   See detailed instructions for more information.

In the terminal window:

1. Change directory to the hello-java directory created in the previous step:

   cd hello-java

2. Enter the following single Fn Project command to build the function and its dependencies as a Docker image called hello-java, push the image to the specified Docker registry, and deploy the function to OCI Functions in the helloworld-app application that you created earlier:

   fn -v deploy --app helloworld-app

3. (Optional) Confirm that the function has been deployed to OCI Functions by clicking Functions (under Resources on the details page for the helloworld-app application) and noting that the hello-java function now appears.

See detailed instructions for more information.

In the terminal window:

1. Invoke the hello-java function by entering:

   fn invoke helloworld-app hello-java

   The 'Hello world!' message is displayed.

2. Invoke the hello-java function with the parameter 'John' by entering:

   echo -n 'John' | fn invoke helloworld-app hello-java

   The 'Hello John!' message is displayed.

Congratulations! You've just created, deployed, and invoked your first function using OCI Functions!

See detailed instructions for more information.

Now that you've created, deployed, and invoked a function, learn how to:

• view function logs in the Oracle Cloud Infrastructure Logging service, or by configuring a syslog URL (see Storing and Viewing Function Logs
• explore OCI Functions using samples on GitHub (see Oracle Functions Samples)
• invoke a function using SDKs (see Using SDKs to Invoke Functions)

You're done!