POC GUIDELINES
Framework for realistic and meaningful proof-of-concept evaluation of the StratiSYSTEM platform.
INTRODUCTION
This guide provides step-by-step guidance for successfully deploying and validating a StratiSYSTEM proof-of-concept (PoC) environment. Whether evaluating performance, scalability, application compatibility, availability, or operational simplicity, this guide is designed to help organizations achieve a successful PoC with minimal complexity and maximum impact.
By following the recommended practices outlined in this guide, organizations can effectively demonstrate the value, flexibility, and capabilities of the StratiSYSTEM platform within a real-world operating environment.
POC REQUIREMENTS
As with production deployments, a PoC may involve a variety of hardware, networking, and storage configurations. The following requirements establish the minimum recommended baseline for a successful and functional PoC environment.
Server Infrastructure
A minimum of one (1) Intel or AMD x86-based server node is required, with three (3) nodes preferred. StratiSYSTEM supports industry-standard x86 server platforms regardless of vendor, make, or model, subject to hardware compatibility.
| Component | Minimum Configuration | Recommended Configuration |
|---|---|---|
| Server Nodes | 1 node | 3 nodes |
| Processor | 1 x 16-core processor, 2.0 GHz or higher | 2 x 16-core processors, 2.0 GHz or higher |
| System Memory | 64 GB RAM | 128 GB RAM or greater |
| Operating System Disk | 1 x 200 GB disk or larger | 200 GB or larger |
| Data Disks | 2 x HDD, SSD, or NVMe devices of any capacity | Configuration appropriate for the intended workloads |
| Network Interfaces | 1 x 10GbE port | 2 x 10GbE ports or faster for public and private network segmentation |
Network Infrastructure and Services
The following network infrastructure and supporting services must be available and properly configured prior to beginning the PoC deployment:
- A jump station or administrative workstation with SSH and SCP tools, such as PuTTY or OpenSSH, installed and operational.
- Appropriate LAN IP addresses allocated to each participating server node.
- Access to DNS services for any required record additions or modifications.
- Operational out-of-band (OOB) management access, such as iLO, iDRAC, or IPMI, including any licenses required to mount virtual ISO media.
- If OOB management is unavailable, the installation ISO may be written to a bootable USB device using a utility such as Rufus.
- When using OOB virtual media, installation must be performed using a direct LAN connection to the OOB management interface.
- Internet connectivity from all participating nodes to access SteelDome and other required software repositories during deployment.
- Network switching and routing infrastructure configured appropriately for the intended PoC evaluation.
- Any required advanced networking configurations, including IEEE 802.3ad (LACP) and load balancing, configured and tested prior to deployment.
- All applicable switch ports configured and validated for the intended operational mode.
IMPORTANT
Do not manually modify the network configuration of a StratiSYSTEM host. All host-level network configuration changes must be performed using the integrated StratiSYSTEM management services by SteelDome personnel as part of the deployment preparation process.
Storage Infrastructure
For PoC environments that include StratiSTOR or HyperSERV, the following additional storage requirements apply:
- Each participating storage node must have access to the physical storage devices required for the intended cluster configuration.
- Storage devices may consist of HDD, SSD, NVMe, or a combination of supported storage technologies.
- If hardware RAID controllers are present, it is preferred that RAID functionality be disabled and the controller configured in HBA, passthrough, or JBOD mode.
- For RAID controllers that do not support direct disk passthrough, individual physical disks may need to be presented as independent, single-disk RAID-0 virtual devices. Refer to the hardware manufacturer's documentation for controller-specific configuration requirements.
IMPORTANT
All servers, storage devices, network infrastructure, management interfaces, and supporting services must be properly configured, validated, and fully operational prior to the start of the PoC.
POC SUCCESS CRITERIA
A clear understanding of the objectives and measurable success criteria must be established and agreed upon by all participating stakeholders before deploying the PoC environment.
At a minimum, the PoC should provide operational validation across the following areas:
- Performance: Validation of infrastructure and application performance against agreed-upon requirements.
- Availability: Validation of service continuity, resiliency, and recovery capabilities appropriate for the deployed configuration.
- Serviceability: Evaluation of administrative operations, monitoring, maintenance, and troubleshooting capabilities.
- Flexibility: Evaluation of deployment options, workload compatibility, scalability, and infrastructure adaptability.
- Interoperability: Validation of compatibility with existing applications, infrastructure, and supporting services.
POC Execution Phases
Members of the SteelDome engineering team will collaborate with the client engineering team throughout all phases of the PoC. A typical engagement follows the structured execution phases outlined below.
| Phase | Activity | Objective |
|---|---|---|
| 01 | Planning and Review | Establish requirements, deployment architecture, evaluation objectives, and measurable success criteria. |
| 02 | Baseline Deployment | Install and configure the StratiSYSTEM environment and validate baseline infrastructure operations. |
| 03 | Feature Enablement | Configure and enable platform capabilities relevant to the evaluation objectives. |
| 04 | Feature Testing | Validate the functionality and operational behavior of selected platform capabilities. |
| 05 | Performance Testing | Measure infrastructure and workload performance against established requirements. |
| 06 | Interoperability Testing | Validate compatibility with existing infrastructure, applications, workloads, and supporting services. |
| 07 | Failure Injection Testing | Evaluate availability, fault tolerance, recovery behavior, and operational resiliency within controlled failure scenarios. |
| 08 | Success Determination | Review evaluation results against agreed-upon success criteria and determine the appropriate next steps. |
POC Timeline and Engineering Checkpoints
PoC timelines may vary depending on deployment complexity, infrastructure readiness, workload requirements, and the scope of the evaluation. However, the target completion window is generally within 30 to 45 days following the initial deployment.
Regular engineering checkpoints between SteelDome and the client are encouraged throughout the evaluation to:
- Review progress against established objectives and milestones.
- Identify and resolve technical issues or deployment dependencies.
- Review testing results and document findings.
- Maintain alignment between engineering teams and project stakeholders.
- Ensure the evaluation remains focused on achieving a measurable and beneficial outcome.
RECOMMENDED PRACTICE
Establish a recurring engineering checkpoint at the beginning of the PoC and maintain a shared record of evaluation objectives, test results, outstanding issues, and completion status throughout the engagement.
Upon completion of the evaluation, SteelDome and the client engineering team will jointly review the results, determine whether the established success criteria have been achieved, and identify the appropriate next steps toward production deployment.