Oracle Cloud Infrastructure Documentation

Creating a Mount Target

Create a File Storage mount target.

When you create a new file system, you can create a mount target and export for the file system. You can also create a mount target later for file systems in a specified compartment and subnet. A file system can only be associated with a mount target in the same availability domain.

Caution

Each mount target requires three internal IP addresses in the subnet to function. Don't use /30 or smaller subnets for mount target creation because they don't have enough available IP addresses. Two of the IP addresses are used during mount target creation. The third IP address must remain available for the mount target to use for high availability failover.
    1. Open the navigation menu and click Storage. Under File Storage, click Mount Targets.

    2. In the List scope section, under Compartment, select a compartment.

    3. Click Create Mount Target.

    4. In the Create Mount Target panel, provide the following details:

      • To enable compartment selection for the mount target, its VCN, or subnet resources, click the related link.
      • Create in Compartment: Specify the compartment in which you want to create the file system.
      • (Optional) New Mount Target name: Replace the default with a friendly name for the mount target. It doesn't have to be unique; an Oracle Cloud Identifier (OCID) uniquely identifies the mount target. Avoid entering confidential information.
        Note

        The mount target name is different than the DNS hostname, which is specified in the advanced options.
      • Availability Domain: The AD in which to create the mount target.
        Important

        While it's possible to access mount targets from any AD in a region, for best performance, the mount targets should be in the same availability domain as the compute instances that access them. For more information, see Regions and Availability Domains.
      • Virtual Cloud Network Compartment: The compartment containing the cloud network (VCN) in which to create the mount target.
      • Virtual Cloud Network: Select the cloud network (VCN) where you want to create the new mount target.
      • Subnet Compartment: Specify the compartment containing a subnet within the VCN to attach the mount target to.
      • Subnet: Select a subnet to attach the mount target to. Subnets can be either AD-specific or regional (regional ones have "regional" after the name). For more information, see VCNs and Subnets.
        Caution

        Each mount target requires three internal IP addresses in the subnet to function. Don't use /30 or smaller subnets for mount target creation because they don't have enough available IP addresses. Two of the IP addresses are used during mount target creation. The third IP address must remain available for the mount target to use for high availability failover. For more information, see Mount Target Limitations and Considerations.

      • Use network security groups to control traffic: Select this option to add this mount target to an existing NSG. Choose an NSG from the list.

        Important

        Rules for the NSG you select must be configured to allow traffic to the mount target's VNIC using specific protocols and ports. For more information, see Configuring VCN Security Rules for File Storage.

    5. (Optional) Show advanced options: Click to configure the mount target's advanced options.

      • IP address: Specify an unused IP address in the subnet you selected for the mount target.

      • Hostname: Specify a hostname you want to assign to the mount target.

        Note

        The File Storage service constructs a fully qualified domain name (FQDN) by combining the hostname with the FQDN of the subnet the mount target is located in.

        For example, myhostname.subnet123.dnslabel.oraclevcn.com.

        After the mount target is created, the hostname may be changed in the mount target's details page. For more information, see Managing Mount Targets.

        Important

        If enabling Kerberos authentication for a mount target in a VCN that uses the default Internet and VCN Resolver for DNS, you must specify a hostname.
    6. (Optional) Show 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.
    7. To create the mount target, click Create.
    8. (Optional) To save the configuration as a Resource Manager stack, click Save as stack. For more information, see Managing Stacks.

  • Use the fs mount-target create command and required parameters to create a mount target:

    oci fs mount-target create --availability-domain <target_availability domain> --compartment-id <target_compartment_id> --subnet-id <subnet_OCID> --display-name "<My Mount Target>"

    Avoid entering confidential information.

    Use the --nsg-ids parameter to add the mount target to a NSG. For example: --nsg-ids '["<nsg_OCID_1>","<nsg_OCID_2"]'.

    For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

  • Run the CreateMountTarget operation to create a mount target.

    For information about using the API and signing requests, see REST API documentation and Security Credentials. For information about SDKs, see SDKs and the CLI.