/ 
Tapper-MCP-5.0.0
River stage one • 4 direct dependents • 5 total dependents

Changes for version 5.0.0 - 2016-02-15

  • internal refactoring
  • use MooseX::Daemonize for daemon
  • plugin system for organizing MCP functionality
  • now as plugins: console handling, reset handling
  • host pool handling: many "anonymous" hosts that have a common name where only the count matters but not the particular single name. Think of cloud instances.
  • merged TestrunDB/ReportsDB
  • polishing edge cases around:
    • MCP chil exit handling
    • state handling when installation is skipped
    • output directory cleanup
    • interdependent scenarios
    • explicit db disconnects in MCP children

Documentation

tapper-mcp-daemonize
cmdline frontend to Tapper::MCP::Master
tapper-mcp-daemon
cmdline frontend to Tapper::MCP/daemonize

Modules

Tapper::MCP
Tapper - Central master control program of Tapper automation
Tapper::MCP::Child
Control one specific testrun on MCP side
Tapper::MCP::Config
Tapper::MCP::Control
Tapper::MCP::Daemon
Tapper::MCP::Info
Tapper::MCP::Master
Wait for new testruns and start a new child when needed
Tapper::MCP::Net
Tapper::MCP::Net::Reset::DoNothing
Tapper::MCP::Net::Reset::Exec
Tapper::MCP::Net::Reset::OSRC
Tapper::MCP::Net::Reset::PM211MIP
Tapper::MCP::Net::TAP
Tapper::MCP::Plugin
Tapper::MCP::Plugin::Test::All
Tapper::MCP::Scheduler::Algorithm
name of the queue has to be unique
Tapper::MCP::Scheduler::Algorithm::DummyAlgorithm
Dummy algorithm for testing
Tapper::MCP::Scheduler::Algorithm::WFQ
Scheduling algorithm "Weighted Fair Queueing"
Tapper::MCP::Scheduler::Builder
Generate Testruns
Tapper::MCP::Scheduler::Controller
Main class of the scheduler
Tapper::MCP::Scheduler::Host
Tapper::MCP::Scheduler::Job
Tapper::MCP::Scheduler::ObjectBuilder
Tapper::MCP::Scheduler::PrioQueue
Object for test queue abstraction
Tapper::MCP::Scheduler::Queue
Tapper::MCP::State
Tapper::MCP::State::Details
Tapper::MCP::State::Plugin::Dummy
Tapper::MCP::State::Plugin::OSRC

Other files