Debian Codegraph @

manuals/en/developers/platformsupport.tex

raw
1 %%
2 %%
3
4 \chapter{Platform Support}
5 \label{blb:_PlatformChapter}
6 \index{Support!Platform}
7 \index{Platform Support}
8
9 \section{General}
10 \index{General }
11
12 This chapter describes the requirements for having a
13 supported platform (Operating System). In general, Bacula is
14 quite portable. It supports 32 and 64 bit architectures as well
15 as bigendian and littleendian machines. For full
16 support, the platform (Operating System) must implement POSIX Unix
17 system calls. However, for File daemon support only, a small
18 compatibility library can be written to support almost any
19 architecture.
20
21 Currently Linux, FreeBSD, and Solaris are fully supported
22 platforms, which means that the code has been tested on those
23 machines and passes a full set of regression tests.
24
25 In addition, the Windows File daemon is supported on most versions
26 of Windows, and finally, there are a number of other platforms
27 where the File daemon (client) is known to run: NetBSD, OpenBSD,
28 Mac OSX, SGI, ...
29
30 \section{Requirements to become a Supported Platform}
31 \index{Requirements!Platform}
32 \index{Platform Requirements}
33
34 As mentioned above, in order to become a fully supported platform, it
35 must support POSIX Unix system calls. In addition, the following
36 requirements must be met:
37
38 \begin{bitemize}
39 \item The principal developer (currently Kern) must have
40 non-root ssh access to a test machine running the platform.
41 \item The ideal requirements and minimum requirements
42 for this machine are given below.
43 \item There must be a defined platform champion who is normally
44 a system administrator for the machine that is available. This
45 person need not be a developer/programmer but must be familiar
46 with system administration of the platform.
47 \item There must be at least one person designated who will
48 run regression tests prior to each release. Releases occur
49 approximately once every 6 months, but can be more frequent.
50 It takes at most a day's effort to setup the regression scripts
51 in the beginning, and after that, they can either be run daily
52 or on demand before a release. Running the regression scripts
53 involves only one or two command line commands and is fully
54 automated.
55 \item Ideally there are one or more persons who will package
56 each Bacula release.
57 \item Ideally there are one or more developers who can respond to
58 and fix platform specific bugs.
59 \end{bitemize}
60
61 Ideal requirements for a test machine:
62 \begin{bitemize}
63 \item The principal developer will have non-root ssh access to
64 the test machine at all times.
65 \item The principal developer will have a root password.
66 \item The test machine will provide approximately 200 MB of
67 disk space for continual use.
68 \item The test machine will have approximately 500 MB of free
69 disk space for temporary use.
70 \item The test machine will run the most common version of the OS.
71 \item The test machine will have an autochanger of DDS-4 technology
72 or later having two or more tapes.
73 \item The test machine will have MySQL and/or PostgreSQL database
74 access for account "bacula" available.
75 \item The test machine will have sftp access.
76 \item The test machine will provide an smtp server.
77 \end{bitemize}
78
79 Minimum requirements for a test machine:
80 \begin{bitemize}
81 \item The principal developer will have non-root ssh access to
82 the test machine when requested approximately once a month.
83 \item The principal developer not have root access.
84 \item The test machine will provide approximately 80 MB of
85 disk space for continual use.
86 \item The test machine will have approximately 300 MB of free
87 disk space for temporary use.
88 \item The test machine will run the the OS.
89 \item The test machine will have a tape drive of DDS-4 technology
90 or later that can be scheduled for access.
91 \item The test machine will not have MySQL and/or PostgreSQL database
92 access.
93 \item The test machine will have no sftp access.
94 \item The test machine will provide no email access.
95 \end{bitemize}
96
97 Bare bones test machine requirements:
98 \begin{bitemize}
99 \item The test machine is available only to a designated
100 test person (your own machine).
101 \item The designated test person runs the regression
102 tests on demand.
103 \item The test machine has a tape drive available.
104 \end{bitemize}