forked from gnu-user/Tapper-Deployment
-
Notifications
You must be signed in to change notification settings - Fork 1
/
README
97 lines (74 loc) · 3.32 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
Tapper-Deployment
=================
This project is a fork of Tapper-Starterkit.
The Starterkit was meant to create an initial setup of Tapper to get
newcomers started, it is not expected to change much.
New development is mostly happening in Tapper-Deployment, containing
some of OSRC specific details, like additional 32bit images, client
packages, Python installation and much refactoring.
However, it is known to work for other users too who want to upgrade
Tapper from CPAN or even closely follow directly from github.
It should work as drop-in replacement for Tapper-Starterkit.
***
Just calling "make" provides you with an overview of the most common targets:
Try most common targets:
------------------------
make web -- update WebGUI
make mcp -- update MCP
make cli -- update CLI
make api -- update Tapper::Reports::API
make receiver -- update Tapper::Reports::Receiver
make action -- update Tapper::Action
make nfsrootperl -- update Tapper::Installer & friends in nfsroot
make clientpkgs -- create client packages (64bit + 32bit)
make clientpkgs++ -- update client packages (64bit + 32bit)
make baseimages -- create base images (64bit + 32bit)
make allautomation -- everything for automation
*except* the MCP-MessageReceiver
. cleanups to force rebuild
. nfsrootdir
. baseimages
. clientpkgs
. mcp
Special target:
---------------
make mcpmsgreceiver -- MCP-MessageReceiver
=> only do if *REALLY* needed
because it risks MCP persistence!
Other targets:
--------------
make nfsrootdir -- a base OS subdir bootable from NFS for Tapper::Installer
make localsetup -- most stuff to run a central Tapper host
but WITHOUT automation. Contains:
. reports receiver
. reports api
. web frontend
make tapperhost -- everything to run a central Tapper control host
INCLUSIVE automation. Contains:
. make installerchroot
. make baseimage64
. make clientpkg64
. make localsetup
make it so -- same as 'make tapperhost'
make clean -- remove intermediate build files+chroots
(keeps the final /data/tapper/... intact)
About Tapper
============
Tapper is an infrastructure for all aspects of testing
inclusive Operating Systems and Virtualization.
Tapper contains
- Automation
- Machine Scheduling
- Command line utils
- Web Frontend application
- Support for writing tests
- Powerful result evaluation API
- Testplan support with TaskJuggler
- Many use-cases from tracking test results to
benchmarking to full OS testing including virtualization
More information about Tapper:
- https://github.com/amd/Tapper-Doc/
- http://search.cpan.org/~amd/Tapper-Doc/
Other Tapper subprojects:
- https://github.com/amd
- http://search.cpan.org/~amd