Feature request: FSxN Storage for Perforce Helix Core

[henrykie]

Use case

Perforce Helix Core with Amazon FSx for NetApp ONTAP

Currently, our Perforce Helix Core module leverages Amazon EBS for storage of the /hxdepots, /hxlogs, and /hxmetadata volumes. We should support the automated deployment and mounting of Amazon FSxN volumes for /hxdepots, and provide the ability for end-users of the module to configure multiple depot volumes.

Filesystem Creation and Volume Creation

The module should not be responsible for creation of the Amazon FSxN Filesystem. Instead, the module should take the filesystem ID or filesystem virtual machine ID as a variable, and provision the necessary volumes on the filesystem as needed.

Deliverables

• Example module configuration (/modules/perforce/helix-core/examples/fsxn) demonstrating FSxN filesystem creation, and Perforce Helix Core module usage with the FSxN filesystem.
• Automatic FSxN volume creation within the Helix Core module.
• Automatic mounting of the FSxN volumes to the Helix Core instance at the expected path.

Solution/User Experience

Example Usage

module "perforce_helix_core" {
    source = "cloud-game-development-toolkit/modules/perforce/helix-core"
    ...
    storage_type = "FSxN"
    amazon_fsxn_filesystem_id = aws_fsx_ontap_file_system.example.id
    depot_volumes = {
        "engine" = {
            size_in_gigabytes = 512
            # Other configuration specific to volume creation
        }
        "game" = {
            size_in_gigabytes = 1000
            # Other configuration specific to volume creation
        }
    }
    metadata_volume_size = 128
    logs_volume_size = 128
}

For details on volume creation see the aws_fsx_ontap_volume resource. Exactly which parameters we expose at the module level is still up for discussion.

Alternative solutions

NA