Story Description
As part of the initial deployment validation, we need to perform a comprehensive sanity check of the latest CI framework code and enable controlled deployment and configuration workflows. This effort will establish a stable baseline for SRIOV and OVS-DPDK deployments while accommodating current infrastructure constraints and preparing for future scalability.

Goal: 

Scope of Work

1. Code Sanity Check and Deployment Enablement

• Perform a full sanity check using the latest CI framework codebase.

• Validate that One-Click Deployment steps are documented and executable for:

• • SRIOV-based deployments

• • OVS-DPDK-based deployments

• Ensure deployment steps are repeatable and suitable for initial validation cycles.

2. Traffic Generation Host Management

• The Traffic Generator Host will be:

• • Managed manually, without any automation scripts.

• • Explicitly excluded from full integration with the core automation framework.

• This approach ensures operational flexibility during early validation and troubleshooting phases.

3. Tenant VM Configuration (Current Scope)

• Tenant VM creation and resource allocation will use static binding for the initial deployment.

• Static binding is required due to:

• • Absence of the Crucible OSP endpoint in the current RHOSO-18 environment.

• • Non-homogeneous hardware across the lab infrastructure.

• This ensures predictable placement and reliable validation results.

Future Scope:

• Generalise Tenant VM and resource configuration using common variables.

• Enable dynamic binding to support:

• • Improved scalability

• • Performance lab expansion

• • Broader hardware compatibility
• Integrate additional endpoints (including Crucible OSP) when available.

Acceptance Criteria

• Sanity check of the latest CI framework code completes successfully.

• One-Click deployment steps are validated for both SRIOV and OVS-DPDK.

• Traffic Generator Host is operational via manual management without automation dependency.

• Tenant VMs are successfully deployed using static binding.

• Future enhancements are clearly documented but not implemented in this story.