ADDED docs/manual/megatest-stand-alone-area.png Index: docs/manual/megatest-stand-alone-area.png ================================================================== --- /dev/null +++ docs/manual/megatest-stand-alone-area.png cannot compute difference between binary files ADDED docs/manual/megatest-system-architecture.png Index: docs/manual/megatest-system-architecture.png ================================================================== --- /dev/null +++ docs/manual/megatest-system-architecture.png cannot compute difference between binary files ADDED docs/manual/megatest-system-architecture.svg Index: docs/manual/megatest-system-architecture.svg ================================================================== --- /dev/null +++ docs/manual/megatest-system-architecture.svg @@ -0,0 +1,5662 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + + + + + run control + + + storageallocation + + + + + + + + + area/testsuite state/status database + configs and custom automation + + + + + run control + + + storageallocation + + + + + + + + + area/testsuite state/status database + configs and custom automation + + + + + + + + + + + compute cloud storage (NFS, moosefs etc.) + + job + + + job + + + job + + + + + run control + + + storageallocation + + + + + + + + + area/testsuite state/status database + configs and custom automation + + + + + + + + + + + + + + + + + postgresql database sync + + + + + + multi-area dashboard and xterm + + + + + multi-area web direct read and control + + multi-area control:- contours- sub-runs- file/vcs sensors- events + configs and custom automation + Megatest Full System Architecture + Index: docs/manual/megatest_manual.html ================================================================== --- docs/manual/megatest_manual.html +++ docs/manual/megatest_manual.html @@ -835,18 +835,19 @@ of a test or task. In most cases megatest is best used in conjunction with logpro or a similar tool to parse, analyze and decide on the test outcome.

@@ -890,13 +895,72 @@

Distributed Compute

Tests are launched using the launching system available for the distributed compute platform in use. A template script is provided which can launch jobs on local and remote Linux hosts. Currently megatest uses the network filesystem to call home to your master -sqlite3 database. Megatest has been used with the Intel Netbatch -system, the lsf batch system and it should be possible to use it with -other similar systems.

+sqlite3 database. Megatest has been used with the Intel Netbatch and +lsf (also known as openlava) batch systems and it should be +straightforward to use it with other similar systems.

+ + + +
+

Overview

+
+
+

Stand-alone Megatest Area

+

A single, stand-alone, Megatest based testsuite or "area" is +sufficient for most validation, automation and build problems.

+
+
+Static +
+
+

Megatest is designed as a distributed or decoupled system. This means +you can run the areas stand-alone with no additional +infrastructure. I.e. there are no databases, web servers or other +centralized resources needed. However as your needs grow you can +integrate multiple areas into a bigger system.

+
+

Component Descriptions

+
    +
  1. +

    +Multi-area dashboard and xterm. A gui (the dashboard) is usually the + best option for controlling and launching runs but all operations + can also be done from the commandline. Note: The not yet released + multi-area dashboard replaces the old dashboard for browsing and + controlling runs but for managing a single area the old dashboard + works very well. +

    +
  2. +
  3. +

    +Area/testsuite. This is your testsuite or automation definition and + consists of the information in megatest.config, runconfigs.config + and your testconfigs along with any custom scripting that can’t be + done with the native Megatest features. +

    +
  4. +
  5. +

    +If your testsuite or build automation is too large to run on a + single instance you can distribute your jobs into a compute server + pool. The only current requirements are password-less ssh access and + a network filesystem. +

    +
  6. +
+
+
+
+

Full System Architecture

+
+
+Static +
+

Installation

@@ -2969,10 +3033,10 @@

Index: docs/manual/megatest_manual.txt ================================================================== --- docs/manual/megatest_manual.txt +++ docs/manual/megatest_manual.txt @@ -55,27 +55,32 @@ owlfs for example) without being specialized for any specific problem space. Megatest in of itself does not know what constitutes a PASS or FAIL of a test or task. In most cases megatest is best used in conjunction with logpro or a similar tool to parse, analyze and decide on the test outcome. - * Self-checking -Repeatable strive for directed or self-checking test - as opposed to delta based tests. + * Self-checking - make it as easy as possible to write self-checking + tests (as opposed to using deltas, i.e. tests that compare with a + previous measurement to deterine PASS/FAIL). - * Traceable - environment variables, host OS and other possibly influential - variables are captured and kept recorded. + * Traceable - environment variables, host OS and other possibly + influential variables are captured and kept recorded. * Immutable - once a test is run it cannot be easily overwritten or modified accidentally. - * Repeatable - test results can be recreated in the future using all the original variables. - - * Relocatable - the testsuite or automation area can be checked out and the tests run anywhere in the disk hierarchy. - - * Encapsulated - the tests run in self-contained directories and all inputs - and outputs to the process can be found in the run areas. - - * Deployable - a testsuite is self-contained and can be bundled with a software project. + * Repeatable - test results can be recreated in the future using all + the original variables. + + * Relocatable - the testsuite or automation area can be checked out + and the tests run anywhere in the disk hierarchy. + + * Encapsulated - the tests run in self-contained directories and all + inputs and outputs to the process can be found in the run areas. + + * Deployable - a testsuite is self-contained and can be bundled with + a software project and easily used by others with little to no + setup burden. Megatest Architecture --------------------- Data separation @@ -90,13 +95,15 @@ Tests are launched using the launching system available for the distributed compute platform in use. A template script is provided which can launch jobs on local and remote Linux hosts. Currently megatest uses the network filesystem to call home to your master -sqlite3 database. Megatest has been used with the Intel Netbatch -system, the lsf batch system and it should be possible to use it with -other similar systems. +sqlite3 database. Megatest has been used with the Intel Netbatch and +lsf (also known as openlava) batch systems and it should be +straightforward to use it with other similar systems. + +include::overview.txt[] include::installation.txt[] include::getting_started.txt[] @@ -106,10 +113,11 @@ include::writing_tests.txt[] include::howto.txt[] include::reference.txt[] + Megatest Internals ------------------ ["graphviz", "server.png"] ADDED docs/manual/stand-alone-megatest-area.svg Index: docs/manual/stand-alone-megatest-area.svg ================================================================== --- /dev/null +++ docs/manual/stand-alone-megatest-area.svg cannot compute difference between binary files