메뉴
Run and create tests for netop-tools configuration generation. Use when running unitest.sh, validating YAML generation, creating new test cases, checking test baselines, debugging test failures, or verifying config changes don't break existing tests.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Configure netop-tools for a specific hardware platform and use case. Use when setting up global_ops_user.cfg, choosing a use case (sriovnet_rdma, sriovibnet_rdma, hostdev, ipoib, macvlan), selecting IPAM type, configuring NETOP_NETLIST device list, setting feature flags, or switching between platforms (DGX, Dell, Lenovo, OCI, SuperMicro).
Deploy NVIDIA Network Operator to a Kubernetes cluster via netop-tools. Use when installing network operator, setting up RDMA networking, deploying SR-IOV, running ins-network-operator.sh, generating Helm values, applying network CRDs, or troubleshooting deployment failures.
Manage SR-IOV virtual functions, PCI devices, link speed, and RDMA testing for NVIDIA Network Operator. Use when setting VFs, querying PCI devices, forcing link speed, running RDMA bandwidth tests, checking RDMA capability, managing node labels and taints, or cordoning nodes.
Diagnose and fix NVIDIA Network Operator issues in Kubernetes. Use when pods can't get RDMA network, SR-IOV VFs not showing, IP allocation failures, network attachment missing, must-gather diagnostics, operator pods crashing, NicClusterPolicy errors, or IPAM pool exhaustion.
Upgrade NVIDIA Network Operator to a new version. Use when changing NETOP_VERSION, running upgrade-network-operator.sh, migrating between operator versions, handling CRD schema changes, or rolling back a failed upgrade.
| name | testing-netop-configs |
| description | Run and create tests for netop-tools configuration generation. Use when running unitest.sh, validating YAML generation, creating new test cases, checking test baselines, debugging test failures, or verifying config changes don't break existing tests. |
Tests validate YAML generation by diffing output against baseline files.
source NETOP_ROOT_DIR.sh
# Run all tests
./tests/unitest.sh
# Run a specific test
./tests/unitest.sh tests/sriovnet_rdma/1/config
CREATE_CONFIG_ONLY=1 (generate YAML, don't deploy)config file as GLOBAL_OPS_USERinstall/ins-network-operator.sh to generate YAMLdiff -ruN between generated YAML and baseline *.yaml files| Directory | Scenarios |
|---|---|
tests/sriovnet_rdma/ | 1/, 2/, combined/, rdmaMode/ |
tests/sriovibnet_rdma/ | basic/, combined/ |
tests/hostdev/ | basic/, combined/ |
tests/macvlan_rdma_shared_device/ | 1/, combined/ |
tests/25_10/ | sriovnet_rdma/1/, sriovibnet_rdma/1/ |
# 1. Create test directory
mkdir -p tests/my_test
# 2. Create config file with overrides
cat > tests/my_test/config << 'EOF'
export NETOP_VERSION="26.1.0"
export USECASE="sriovnet_rdma"
export NETOP_NETLIST=( a,,,0000:08:00.0 b,,,0000:86:00.1 )
export DEVICE_TYPES=( "connectx-7" )
export NUM_VFS=8
# ... other overrides
EOF
# 3. Generate baseline YAML
export CREATE_CONFIG_ONLY=1
export GLOBAL_OPS_USER=$(pwd)/tests/my_test/config
source ${GLOBAL_OPS_USER}
${NETOP_ROOT_DIR}/install/ins-network-operator.sh
# 4. Copy generated YAML as baselines
cp usecase/${USECASE}/*.yaml tests/my_test/
# 5. Verify test passes
./tests/unitest.sh tests/my_test/config
tests/my_test/
config # Sourced as GLOBAL_OPS_USER (required)
netop.cfg # Optional use-case overrides
NicClusterPolicy.yaml # Baseline YAML files
values.yaml
network.yaml
ippool-*.yaml
...
When a test fails, unitest.sh shows the diff. Common causes:
| Symptom | Cause | Fix |
|---|---|---|
| All tests fail | Changed default in global_ops.cfg | Regenerate all baselines |
| One test fails | Config override missing | Add missing variable to test's config |
| New YAML file not compared | Test dir missing baseline | Copy generated file to test dir |
| Version-specific failures | NETOP_VERSION changed behavior | Create version-specific test under tests/ |
GitHub Actions (.github/workflows/main.yml) runs tests/unitest.sh on ubuntu-22.04 on every push. Tests are discovered automatically by finding config files via find.