Creating Applications


Find out how to create applications with OCI Functions.

In OCI Functions, an application is a logical grouping of functions. The properties you specify for an application determine resource allocation and configuration for all functions in that application. You have to create a function within an application, so at least one application must exist before you can create a function in OCI Functions.

For more information about applications, see Applications.

Console
CLI
API
Confirm that you have completed the steps in the Functions QuickStart Guides.
Sign in to the Console as a functions developer.
In the Console, open the navigation menu and click Developer Services. Under Functions, click Applications.
Select the region you're using with OCI Functions.

We recommend that you use the same region as the Docker registry that's specified in the Fn Project CLI context. See Creating an Fn Project CLI Context to Connect to Oracle Cloud Infrastructure.

Select the compartment specified in the Fn Project CLI context. See Creating an Fn Project CLI Context to Connect to Oracle Cloud Infrastructure.

The Applications page shows the applications that are already defined in the compartment.

Click Create Application and specify the following details:

Name: A name for the new application (for example, acmeapp). Avoid entering confidential information.
VCN in <compartment-name>: The VCN (virtual cloud network) in which to run functions. For example, a VCN called acme-vcn-01
Subnets in <compartment-name>: The subnet (or subnets, up to a maximum of three) in which to run functions. For example, a public subnet called Public Subnet IHsY:US-PHOENIX-AD-1).

A public subnet requires an internet gateway in the VCN, and a private subnet requires a service gateway in the VCN. If a regional subnet has been defined, as a best practice, select that subnet to make it easier to implement failover across availability domains. If a regional subnet hasn't been defined and you need to meet high availability requirements, select multiple subnets. We recommend that the subnets are in the same region as the Docker registry that's specified in the Fn Project CLI context. For more information, see Creating an Fn Project CLI Context to Connect to Oracle Cloud Infrastructure.

Specifying a private subnet for an application doesn't prevent access from the internet to the invoke endpoints of functions in the application. Use identity policies to control access to function invoke endpoints. For details, see Controlling Access to Invoke and Manage Functions.

Shape: The processor architecture of the compute instances on which to deploy and run functions in the application. All the functions in the application are deployed and run on compute instances with the same architecture. The function's image must contain the necessary dependencies for the architecture you select, as follows:

Select the Generic_ARM shape if you always want functions in the application to run on compute instances with an Arm-based architecture. If you select this single architecture shape for the application, the function's image must contain the necessary dependencies for the Arm architecture (in either a single architecture image, or a multi-architecture image).
Select the Generic_X86 shape if you always want functions in the application to run on compute instances with an x86-based architecture. If you select this single architecture shape for the application, the function's image must contain the necessary dependencies for the x86 architecture (in either a single architecture image, or a multi-architecture image).
Select the Generic_X86_ARM shape if you want functions to run on compute instances with whichever architecture has sufficient capacity. In this case, OCI Functions selects the architecture on which to run functions based on available capacity. If you select this multi-architecture shape for the application, every function's image must contain the necessary dependencies for both the Arm architecture and the x86 architecture (in a multi-architecture image).

Note that you cannot change the application's shape after you have created the application. See Selecting a Single Architecture or Multi-Architecture Application Shape on which to run a Function.

Tagging options: If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you're not sure whether to apply tags, skip this option or ask an administrator. You can apply tags later.

Select one of the following options:

To create the application now, click Create. The new application appears in the list of applications.
To create the application later using Resource Manager and Terraform, click Save as stack to save the resource definition as a Terraform configuration. For more information about saving stacks from resource definitions, see Creating a Stack from a Resource Creation Page.



For more information click here https://docs.oracle.com/en-us/iaas/Content/Functions/Tasks/functionscreatingapps.htm#top