Attachment C_IaaMS Storage Modeling Requirements.pdf

ATTACHMENT C – IAAMS STORAGE MODELING REQUIREMENTS

All capacities shall meet the following storage modeling requirements:

1.0 SERVICE MANAGEMENT MODEL

1.1 MINIMALLY MANAGED

Services designated as minimally managed shall meet the following requirements:

1. The Contractor shall prepare, ship, install, and configure all hardware required to make the usable capacity fully available to the target application.

1.2 FULLY MANAGED

Services designated as fully managed shall meet all requirements of a minimally managed service above, and shall include the following additional requirements:

1. The Contractor shall provide all day-to-day management of the solution to include, at a minimum:

a. Patch management, including the development of test plans, testing patch deployment within a non-production environment, development of implementation procedures, development of backout procedures, and solicitation of change control approval from the VA.

b. Configuration of permissions, access control lists, firewalls, and other security administration tasks.

c. Troubleshooting for end users of the solution.

2. The Contractor shall provide any professional services necessary to integrate with VAs Enterprise Service Desk. The contractor shall perform the following tasks:

a. Gain and maintain access to VAs existing ServiceNow ticket management platform.

b. Monitor ServiceNow for trouble tickets and change control requests specific to any infrastructure maintained by the Contractor.

c. Maintain, respond to, redirect, and/or close any tickets assigned to the

Contractor.

d. Open, maintain, and close change control requests for any work that falls under an existing VA change control process.

2.0 STORAGE DELIVERY MODEL

2.1 MINIMUM USABLE CAPACITY

Any reference to “minimum usable capacity” shall calculate the minimum usable capacity as the capacity made available to VA across a single optional tier at a single facility.

2.2 FILE CAPACITY

All storage services providing file capacity shall meet the following requirements:

1. The solution must be capable of presenting data in the following protocols:

a. SMB v2.0

b. SMB v3.0 and later

i. Solution shall implement the continuously available share property.

ii. Solution shall implement persistent handles.

iii. Solution shall implement remote volume shadow service (VSS), permitting native snapshot access from a Windows 10-based client without requiring installation of client-based software.

c. NFS v3

i. Solution shall support 64-bit file sizes.

ii. Solution shall support asynchronous writes to the server.

d. NFS v4.1

i. Solution shall support NFS session trunking (multipathing).

2. The solution shall provide snapshot capability.

a. The solution shall allow administrators to create snapshots on demand.

b. The solution shall include scheduling capability, permitting snapshots to be created and deleted based on a configurable schedule created by an administrator.

c. The solution shall permit up to 20 snapshots to be created without reducing the solution below the performance thresholds included in this document.

3. The solution shall provide automated data tiering capability, in which data is programmatically moved to the appropriate performance tier based on historical data usage.

4. File storage capacity shall be made available in the following performance tiers:

a. High Performance – Storage capacity within this tier shall meet the following performance requirements:

i. A minimum throughput of 400 megabits per second (Mbps) per terabyte of minimum usable capacity. Throughput shall be calculated using the following criteria:

1) System is configured to meet all requirements of the PWS.

2) Input/Output (IO) consists of 80% read and 20% write operations.

3) The block size shall be 64 kilobytes (KB).

4) The minimum working set size shall be 100 gigabytes (GB).

ii. The system shall respond to storage requests and provide the first byte (“time to first byte”) within 10 milliseconds.

b. Mixed Performance/Capacity – Storage capacity within this tier shall meet the following performance requirements:

i. A minimum throughput of 60Mbps per terabyte of minimum usable capacity. Throughput shall be calculated using the following criteria:

1) System is configured to meet all performance, reliability, security, and integrity requirements of the PWS.

2) Input/Output (IO) consists of 80% read and 20% write operations.

3) The block size shall be 64 KB.

4) The minimum working set size shall be 100 GB.

ii. The system shall respond to storage requests and provide the first byte

(“time to first byte”) within 10 milliseconds.

c. High Capacity – Storage capacity within this tier shall meet the following performance requirements:

i. A minimum throughput of 10 Mbps per terabyte of minimum usable capacity. Throughput shall be calculated using the following criteria:

1) System is configured to meet all performance, reliability, security, and integrity requirements of the PWS.

2) Input/Output (IO) consists of 80% read and 20% write operations.

3) The block size shall be 64 KB.

4) The minimum working set size shall be 100 GB.

ii. The system shall respond to storage requests and provide the first byte (“time to first byte”) within 10 milliseconds.

2.3 BLOCK CAPACITY

All storage services providing block capacity shall meet the following requirements:

1. The solution must be capable of presenting data in the following protocols:

a. Internet Small Computer Systems Interface (iSCSI)

b. Fibre Channel (FC)

c. Fibre Channel over Ethernet (FCoE)

2. The solution shall provide snapshot capability.

a. The solution shall allow administrators to create snapshots on demand.

b. The solution shall include scheduling capability, permitting snapshots to be created and deleted based on a configurable schedule created by an administrator.

c. The solution shall permit up to 20 snapshots to be created without reducing the solution below the performance thresholds included in this document.

3. Block storage capacity shall be made available in the following performance tiers:

a. High Performance – Storage capacity within this tier shall meet the following

i. A minimum of 10,000 input/output operations per second (IOPS) per terabyte of minimum usable capacity. IOPS shall be calculated using the following criteria:

1) System is configured to meet all performance, reliability, security, and integrity requirements of the PWS.

2) Input/Output (IO) consists of 70% read and 30% write operations.

3) The block size shall be 4 KB.

4) The minimum working set size shall be 100 GB.

ii. The system shall respond to storage requests and provide the first byte (“time to first byte”) within 10 milliseconds.

b. Mixed Performance/Capacity – Storage capacity within this tier shall meet the following performance requirements:

i. A minimum of 1,000 input/output operations per second (IOPS) per terabyte of minimum usable capacity. IOPS shall be calculated using the following criteria:

1) System is configured to meet all performance, reliability, security, and integrity requirements of the PWS.

2) Input/Output (IO) consists of 70% read and 30% write operations.

3) The block size shall be 4 KB.

4) The minimum working set size shall be 100 GB.

c. High Capacity – Storage capacity within this tier shall meet the following performance requirements:

i. A minimum of 250 input/output operations per second (IOPS) per terabyte of minimum usable capacity. IOPS shall be calculated using the following criteria:

1) System is configured to meet all performance, reliability, security, and integrity requirements of the PWS.

2) Input/Output (IO) consists of 70% read and 30% write operations.

3) The block size shall be 4 KB.

4) The minimum working set size shall be 100 GB.

2.4 OBJECT CAPACITY

All storage services providing object capacity shall meet the following requirements:

1. The solution must be capable of presenting data in the following protocols:

a. Representational State Transfer (REST)

2. Object Storage capacity shall be made available in the following performance tiers:

a. High Performance – Storage capacity within this tier shall meet the following performance requirements:

i. A minimum throughput of 400 megabits per second (400Mbps) per terabyte of minimum usable capacity. Throughput shall be calculated using the following criteria:

1) System is configured to meet all performance, reliability, security, and integrity requirements of the PWS.

2) Input/Output (IO) consists of 80% read and 20% write operations.

3) The object size shall be 1 MB.

4) The minimum working set size shall be 100 GB.

ii. The system shall respond to storage requests and provide the first byte

(“time to first byte”) within 10 milliseconds.

b. Mixed Performance/Capacity – Storage capacity within this tier shall meet the following performance requirements:

i. A minimum throughput of 60 megabits per second (60Mbps) per terabyte of minimum usable capacity. Throughput shall be calculated using the following criteria:

1) System is configured to meet all performance, reliability, security, and integrity requirements of the PWS.

2) Input/Output (IO) consists of 80% read and 20% write operations.

3) The object size shall be 1 MB.

4) The minimum working set size shall be 100 GB.

c. High Capacity – Storage capacity within this tier shall meet the following

i. A minimum throughput of 10 megabits per second (10Mbps) per terabyte of minimum usable capacity. Throughput shall be calculated using the following criteria:

1) System is configured to meet all performance, reliability, security, and integrity requirements of the PWS.

2) Input/Output (IO) consists of 80% read and 20% write operations.

3) The object size shall be 1 MB.

4) The minimum working set size shall be 100 GB.

2.5 BACKUP CAPACITY

All storage services providing backup capacity shall meet the following requirements:

1. The capacity provided for backup must be wholly discrete from all other storage and compute capacity. It may not share compute or storage resources, including, but not limited to, servers, nodes, disks, controllers, chassis, etc.

2. The solution shall be a CommVault HyperScale validated platform.

3. The solution must be capable of presenting data in the following protocols:

a. SMB v2.0

b. SMB v3.0

i. Solution shall implement the continuously available share property.

ii. Solution shall implement persistent handles.

iii. Solution shall implement remote volume shadow service (VSS), permitting native snapshot access from a Windows 10-based client without requiring installation of client-based software.

c. NFS v3

i. Solution shall support 64-bit file sizes.

ii. Solution shall support asynchronous writes to the server.

4. Storage capacity shall meet the following performance requirements:

a. A minimum throughput of 10 megabits per second (10Mbps) per terabyte of minimum usable capacity. Throughput shall be calculated using the following criteria:

i. System is configured to meet all performance, reliability, security, and integrity requirements of the PWS.

ii. Input/Output (IO) consists of 70% write and 30% read operations.

iii. The minimum working set size shall be 100 GB.

iv. The system shall respond to storage requests and provide the first byte

(“time to first byte”) within 10 milliseconds.

The system shall support a minimum of four concurrent requests per terabyte of minimum capacity.