8.5 Create Custom Projects

Shares are grouped together as Projects. For example, you can create a project for Dept_1. Dept_1 will contain department-level shares.

To create the Dept_1 project, do the following:

1. In the Browser User Interface (BUI), click the Shares tab.

   The shares page is displayed.

2. Click the Projects panel.
3. Click the + button above the list of projects in the project panel.
4. Enter a name for the project, such as Dept_1. The new project Dept_1 is listed on the Project Panel, which is on the left navigation pane.
5. Click the General tab on the Dept_1 project page to set project properties. This section of the BUI controls overall settings for the project that are independent of any particular protocol and are not related to access control or snapshots. While the CLI groups all properties in a single list, this section describes the behavior of the properties in both contexts.

   The project settings page contains three sections: Space Usage (Users and Groups), Inherited Properties, and Default Settings (File systems and LUNs). Table 8-2 describes the project settings.

   Table 8-2 Project Settings

   Section and Setting	Description
   Space Usage	Space within a storage pool is shared between all shares. File systems can grow or shrink dynamically as needed, though it is also possible to enforce space restrictions on a per-share basis. Quota - Sets a maximum limit on the total amount of space consumed by all file systems and LUNs within the project. Reservation - Guarantees a minimum amount of space for use across all file systems and LUNs within the project.
   Inherited Properties	Standard properties that can either be inherited by shares within the project. The behavior of these properties is identical to that at the shares level. Mountpoint - The location where the file system is mounted. This property is only valid for file systems. Oracle recommends that you use specify /export/<project_name> as the default mountpoint. By using this consistently, you can group all shares and mount under the relevant project. It also prevents multiple shares from using the same mount points. Note that the same storage appliance is used by a multiple departments (15 in the case of Exalogic machine full rack configuration). The departments will have a similar share structure, such as /export/dept_1/<share1>, /export/dept_2/share1, and so on. Read only - Controls whether the file system contents are read only. This property is only valid for file systems. Update access time on read - Controls whether the access time for files is updated on read. This property is only valid for file systems. Non-blocking mandatory locking - Controls whether CIFS locking semantics are enforced over POSIX semantics. This property is only valid for file systems. Data deduplication - Controls whether duplicate copies of data are eliminated. Data compression - Controls whether data is compressed before being written to disk. Checksum - Controls the checksum used for data blocks. Cache device usage - Controls whether cache devices are used for the share. Synchronous write bias - Controls the behavior when servicing synchronous writes. By default, the system optimizes synchronous writes for latency, which leverages the log devices to provide fast response times. Database record size - Controls the block size used by the file system. This property is only valid for file systems. By default, file systems will use a block size just large enough to hold the file, or 128K for large files. This means that any file over 128K in size will be using 128K blocks. If an application then writes to the file in small chunks, it will necessitate reading and writing out an entire 128K block, even if the amount of data being written is comparatively small. The property can be set to any power of 2 from 512 to 128K. Additional replication - Controls number of copies stored of each block, above and beyond any redundancy of the storage pool. Virus scan - Controls whether this file system is scanned for viruses. This property is only valid for file systems. Prevent destruction - When set, the share or project cannot be destroyed. This includes destroying a share through dependent clones, destroying a share within a project, or destroying a replication package. Restrict ownership change - By default, this check box is selected and the ownership of files can only be changed by a root user. This property can be removed on a per-filesystem or per-project basis by deselecting this check box. When deselected, file ownership can be changed by the owner of the file or directory.
   Default Settings	Custom settings for file systems, to be used as default, include the following: User - User that is the current owner of the directory. Group - Group that is the current owner of the directory. Permissions - Permissions include Read (R), Write (W), or Execute (X). Custom settings for LUNs, to be used as default, include the following: Volume Size - Controls the size of the LUN. By default, LUNs reserve enough space to completely fill the volume Thin provisioned - Controls whether space is reserved for the volume. This property is only valid for LUNs. By default, a LUN reserves exactly enough space to completely fill the volume. This ensures that clients will not get out-of-space errors at inopportune times. This property allows the volume size to exceed the amount of available space. When set, the LUN will consume only the space that has been written to the LUN. While this allows for thin provisioning of LUNs, most file systems do not expect to get "out of space" from underlying devices, and if the share runs out of space, it may cause instability or a corruption on clients, or both. Volume block size - The native block size for LUNs. This can be any power of 2 from 512 bytes to 128K, and the default is 8K.

6. After entering your choices, click Apply.