This section introduces projects and shares.
All file systems and LUNs are grouped into projects. A project defines a common administrative control point for managing shares. All shares within a project can share common settings, and quotas can be enforced at the project level in addition to the share level. Projects can also be used solely for grouping logically related shares together, so their common attributes (such as accumulated space) can be accessed from a single point.By default, the appliance creates node-level projects based on the number of compute nodes in your Exalogic machine when a storage pool is first configured. For example, for a compute node with the host name abc, the default project abc_1 is created. You can create all shares within this default project. However, Oracle recommends that you create additional projects for organizational purposes.
Shares are file systems and LUNs that are exported over supported data protocols to clients of the appliance. File systems export a file-based hierarchy and can be accessed over NFS over IPoIB in the case of Exalogic machines. The project/share tuple is a unique identifier for a share within a pool. Multiple projects can contain shares with the same name, but a single project cannot contain shares with the same name. A single project can contain both file systems and LUNs, and they share the same namespace.
For a list of default shares created in the Exalogic machine, see Default Storage Configuration.