POC GUIDELINES
Framework for realistic and meaningful proof-of-concept evaluation of the StratiSYSTEM platform.
INTRODUCTION
This guide provides clear, step-by-step guidance for successfully deploying and validating a StratiSYSTEM proof-of-concept (PoC) environment. Whether you are evaluating performance, scalability, application compatibility, or operational simplicity, this guide is designed to help you achieve a complete and successful PoC with minimal complexity and maximum impact. By following these best practices, you will be able to fully demonstrate the value and capabilities of the StratiSYSTEM platform in a real-world setting.
POC REQUIREMENTS
As with production deployments, a PoC can involve many different deployment configurations. At a minimum the following is needed for a functional baseline PoC to be successful:
- Minimum of one (1) Intel/AMD x86-based server node is required, with three (3) nodes preferred; any vendor, make, or model is supported.
- Node composition:
- Minimum of a 16-core processor, dual 16-core processors preferred, 2.0GHz or higher
- Minimum of 64 GB RAM, 128 GB preferred
- Minimum of one (1) OS disk, 200GB or larger
- Minimum of two (2) data disks, any capacity, and any combination of HDD/SSD/NVMe
- Minimum of one (1) 10GbE port, two (2) recommended for public and private network segmentation
- Network services:
- Jumpstation with SSH tools such as SCP and PuTTY installed.
- Local LAN IP addresses available per node.
- Access to DNS services for any needed record additions/changes.
- Ensure Out-of-band (OOB) management access is available (e.g. iLO, iDRAC, IPMI, etc.) and that the necessary license is installed to allow for mounting an ISO image.
- If no OOB management is available, then ripping the ISO to a USB using Rufus would be the alternative install method.
- Installation using a direct LAN connection to the OOB is required.
- Access to internet based repos must be allowed during the installation.
- Ensure switching and routing are correctly configured appropriate for the PoC evaluation.
- All nodes have access to the internet (only needed during deployment reach communicate with SteelDome repositories).
- Any advanced networking modes such as 802.3ad, load balancing, etc. are already configured and tested.
- Verify that the ports are configured properly for the desired operational mode.
- DO NOT modify the network configuration on the host manually. This should only be done using the built-in management services by SteelDome personnel prior to installation.
- Storage devices:
- If the PoC includes StratiSTOR or HyperSERV evaluation, ensure each node has access to the necessary storage devices to be used within the cluster.
- If RAID controllers are present, it is preferred to disable the RAID mode and switch to HBA/JBOD mode. Some controllers require presenting each disk as RAID-0 devices (see your specific manufacturer deployment guides for further details).
** NOTE: All systems and related components must be properly configured and fully operational prior to the start of the PoC.
POC SUCCESS CRITERIA
A general understanding of what defines success should be agreed upon prior to deploying the PoC. In general, operational validation of performance, availability, serviceability and flexibility are expected at a minimum.
Members of the SteelDome engineering team will work with the client engineering team throughout all phases of the PoC. The PoC will typically follow these phases:
- Preplanning development and review
- Baseline deployment
- Feature enablement
- Feature testing
- Performance testing
- Interoperability testing
- Failure injection testing
- Success determination
Timelines for PoCs can vary depending on a number of factors, however the PoC target completion window is generally within 30-45 days from deployment. Regular engineering checkpoints are encouraged during this window to maximize use of the time and keep the project moving forward to a beneficial outcome.