Openshift

RackN Test Framework

This content pack provides a test framework using pipelines for running tests.

Design Philosophy

The assumption is that tests are pipelines.

Architecture

Prerequisites

The environment must provide power management functions and next boot functions:

• poweron
• poweroff
• powercycle
• powerstatus
• nextbootpxe

These are used to manage the state of the machine.

For physical, this is handled by the ipmi plugin and assumes that ipmi/username, ipmi/password, and ipmi/address are set. For virtual, this assumes that there is a configured plugin to simulate these actions.

Infrastructure Requirements

Required Parameters

Optional Parameters

Troubleshooting

Common Commands

Resource Cleanup

Future Enhancements

Planned improvements: - more

RAW NOTES

You need a single node admin pool. rackn-test-admin-pool. This manages the batchs.

The context admin pool needs the following parameters:

• pipeline: batch-environment-cluster
• broker/name: context-broker
• cluster/count: 1

You need a context pool of workers. Teh default parameter is rackn/test/runner-pool. The default value is test-runner-pool. You need a vm/physical pool of machines in sledgehammer to start. Teh default parameter is rackn/test/machine-pool. The default value is test-machine-pool.

The context worker pool needs the following parameters:

• pipeline: batch-environment-cluster
• broker/name: context-broker
• cluster/count: 3 # the number of concurrent tests.

The vm/physical machine pool needs the following parameters:

• pipeline: rackn-test-bootenv-cluster
• broker/name:

With these clusters available, you can then run a batch tests.

Loading the universal content pack with test tags, we can run a test.