Network File System

The Network File System (NFS) is a distributed file system that allows a client computer to access files over a network as though the files were on local storage. Oracle Application Container Cloud Service supports mounting of NFS volumes into the application containers running on Oracle Cloud Infrastructure Classic accounts.

To specify the NFS volumes, set the following parameters in the deployment.json file:

  • volumes – Represents the list of volumes. This element can contain more than one block of sub-elements. Each block specifies one volume.

    • name – (required) Mounted volume name.

    • type – (required) Type of the volume. Currently only nfs is supported.

    • device – (required) Defines the IP address and the path of the volume. For example, x.x.x.x:/shares/nfs1

    • mount_options – (optional for Oracle Cloud Infrastructure Classic) If the mount_options parameter isn’t specified, it takes the default values. If it’s present all sub-elements must be specified.

      • vers=<value>Oracle Application Container Cloud Service supports NFS 4 for Oracle Cloud Infrastructure Classic accounts. The default value is 4.

      • soft/hard – Specifies whether the program using a file via an NFS connection should stop and wait (hard) for the server to come back online, if the host serving the exported file system is unavailable, or if it should report an error (soft). The default value is soft.

      • timeo=<value> – Specifies the number of seconds to pass before the error is reported.

      • bg – This is known as a background mount. It does the mount in the background if it fails the first time and thus lets the system continue booting even if there are NFS problems. With this option, a time out or failure causes the mount(8) command to fork a child which continues to attempt to mount the export. The parent immediately returns with a zero exit code.

      • tcp – Specifies to use the TCP protocol.

      • rw– Specifies read and write access.

Example 2-3 deployment.json

{
	"memory": "1G",
	"instances": 1,
	"environment": {},
	"secureEnvironment": [],
	"system_properties": {},
	"services": [],
	"volumes": [{
			"name": "vol1",
			"type": "nfs",
			"device": "100.100.64.47:/fss",
			"mount_options": ["vers=4", "soft", "timeo=180", "bg", "tcp", "rw"]
		}
	]
}

It's customer's responsibility to make sure the NFS server is accessible from the Oracle Application Container Cloud Service application.