Wait for OCI CLI and Fn CLI to be installed
You need to provide details on the OCI tenancy you will work in and the OCI user you will work as. Please edit these two files:
Paste the contents provided by the workshop instructor into these two files.
Set the environment variable LAB_ID to the number provided to you by the workshop instructor.
Do not continue until you see the file
/root/allSetInBackground appear. If it appears, then the OCI CLI has been installed and you can continue.
Try out the following command to get a list of all namespaces you currently have access to - based on the OCI Configuration defined above.
oci os ns get
If you get a proper response, the OCI is configured correctly and you can proceed. If you run into an error, ask for help from your instructor.
Now Check the installed version of Fn CLI. Note: we do not need the Fn server at this stage.
Configure and set remote context
List the currently available Fn contexts
fn list contexts
Create an appropriate Fn context for working with OCI as provider (see OCI Docs on Functions).
fn create context lab-fn-context --provider oracle
fn use context lab-fn-context
Prepare a number of environment variables. Note: the assumptions here are that you are working in a tenancy in the Ashburn region and a compartment called lab-compartment exists as well as an API Gateway lab-apigw in that same compartment as well as an API Deployment called MY_API_DEPL# on the API Gateway. We need to get references to these resources in order to create new resources in the right place.
cs=$(oci iam compartment list) export compartmentId=$(echo $cs | jq -r --arg display_name "lab-compartment" '.data | map(select(."name" == $display_name)) | . | .id') apigws=$(oci api-gateway gateway list -c $compartmentId) export apiGatewayId=$(echo $apigws | jq -r --arg display_name "lab-apigw" '.data.items | map(select(."display-name" == $display_name)) | . | .id') depls=$(oci api-gateway deployment list -c $compartmentId) deploymentEndpoint=$(echo $depls | jq -r --arg display_name "MY_API_DEPL_$LAB_ID" '.data.items | map(select(."display-name" == $display_name)) | . | .endpoint') apiDeploymentId=$(echo $depls | jq -r --arg display_name "MY_API_DEPL_$LAB_ID" '.data.items | map(select(."display-name" == $display_name)) | . | .id') # get namespace nss=$(oci os ns get) export ns=$(echo $nss | jq -r '.data')
Update the context with the settings relevant for this workshop.
fn update context oracle.compartment-id $compartmentId fn update context api-url https://functions.us-ashburn-1.oci.oraclecloud.com fn update context registry iad.ocir.io/$ns/cloudlab-repo fn update context oracle.profile FN
You can list the currently available Fn contexts again and see whether your changes had an effect (of course they did)
fn list contexts
Next and finally, login to the private Docker Registry that is prepared for you on OCI.
docker login iad.ocir.io
The username you have to provide is composed of
<tenancy-namespace>/<username>. The password is an Authentication Token generated for the specified user. Both these values are provided by your workshop instructor.
And now we are finally ready to create Functions on Oracle Cloud Infrastructure and expose them through OCI API Gateway.