1 | <!-- $Id$ --> |
---|
2 | |
---|
3 | <chapter> |
---|
4 | <title>Installation</title> |
---|
5 | <para> |
---|
6 | Before being able to use <application>PyKota</application>, you have of course to |
---|
7 | install it first. But before installing, you must carefully plan your installation. |
---|
8 | </para> |
---|
9 | |
---|
10 | <para> |
---|
11 | First you have to determine which machine will be the <application>PyKota</application> |
---|
12 | <glossaryterm>Storage Server</glossaryterm>. The Storage Server is the host responsible |
---|
13 | for keeping a centralized database of print usage for all your printers, users and groups. |
---|
14 | </para> |
---|
15 | |
---|
16 | <para> |
---|
17 | Then you have to list all the <glossaryterm>Print Servers</glossaryterm> for which |
---|
18 | you plan to use <glossaryterm>print quota</glossaryterm> facilities. |
---|
19 | </para> |
---|
20 | |
---|
21 | <para> |
---|
22 | Now we will see what has to be done on these servers. |
---|
23 | <note> |
---|
24 | <title>Note</title> |
---|
25 | <para> |
---|
26 | Of course, depending on the size of your network, you may very well |
---|
27 | use the same machine as both a Print Server and a Storage Server. |
---|
28 | This is especially the case if you've got only one server. |
---|
29 | </para> |
---|
30 | </note> |
---|
31 | </para> |
---|
32 | |
---|
33 | <sect1> |
---|
34 | <title>Storage Server Installation</title> |
---|
35 | |
---|
36 | <para> |
---|
37 | Depending on <application>PyKota</application>'s version number, different |
---|
38 | types of storage backends may be supported, so we will see for each one of |
---|
39 | them how to configure it. |
---|
40 | </para> |
---|
41 | |
---|
42 | <sect2> |
---|
43 | <title>PostgreSQL</title> |
---|
44 | |
---|
45 | <para> |
---|
46 | <application>PostgreSQL</application> is an <glossaryterm>Object Relationnal DataBase |
---|
47 | Management System</glossaryterm> distributed under a <glossaryterm>Free Software</glossaryterm> |
---|
48 | license from the |
---|
49 | <ulink url="http://www.postgresql.org">http://www.postgresql.org</ulink> |
---|
50 | web site. It certainely is the free <acronym>RDBMS</acronym> which has the most advanced |
---|
51 | features, and is widely used all over the world. |
---|
52 | </para> |
---|
53 | |
---|
54 | <para> |
---|
55 | To configure your Storage Server, you must have PostgreSQL already working. |
---|
56 | The complete installation of <application>PostgreSQL</application> is not covered by |
---|
57 | the present manual, please refer to your system's documentation or to |
---|
58 | <ulink url="http://www.postgresql.org">http://www.postgresql.org</ulink> for |
---|
59 | details. |
---|
60 | </para> |
---|
61 | |
---|
62 | <para> |
---|
63 | One thing you have to check, though, is that every Print Server on which you |
---|
64 | want to install the print quota mechanism, i.e. the print servers, must be able to connect to the |
---|
65 | <application>PostgreSQL</application> server. In the default installation of |
---|
66 | <application>PostgreSQL</application> this may not be the case for security reasons, except if both |
---|
67 | servers are in fact the same machine. In any case, it is recommended that you |
---|
68 | check the <filename>/etc/postgresql/pg_hba.conf</filename> and modify it if |
---|
69 | needed. This file is self documented and its modification is straightforward. |
---|
70 | You also have to make sure that <application>PostgreSQL</application> accepts <acronym>TCP/IP</acronym> connections. |
---|
71 | To do so you either have to launch it with the <option>-i</option> option or |
---|
72 | modify the <filename>/etc/postgresql/postgresql.conf</filename>, which is |
---|
73 | self documented and easy to modify too. |
---|
74 | <tip> |
---|
75 | <title>Tip</title> |
---|
76 | <para> |
---|
77 | Don't forget to restart <application>PostgreSQL</application> if you modify |
---|
78 | any of its configuration files, in order for the changes to take effect. |
---|
79 | </para> |
---|
80 | </tip> |
---|
81 | </para> |
---|
82 | |
---|
83 | <para> |
---|
84 | Be careful, you may be unable to connect from a Print Server to the <application>PostgreSQL</application> |
---|
85 | server even if the configuration is correct. Sometimes your connections may be blocked by |
---|
86 | one or more network firewalls along the route from one machine to the other. If this |
---|
87 | is the case, then the best thing you can do is to ask your <glossaryterm>Network Administrator</glossaryterm> |
---|
88 | to not filter the IP port used by <application>PostgreSQL</application>, which is |
---|
89 | usually port 5432/tcp. |
---|
90 | <tip> |
---|
91 | <title>Tip</title> |
---|
92 | <para> |
---|
93 | The TCP/IP network port used by PostgreSQL may be different. When in doubt, ask your |
---|
94 | <glossaryterm>System Administrator</glossaryterm> for the correct value. |
---|
95 | </para> |
---|
96 | </tip> |
---|
97 | </para> |
---|
98 | |
---|
99 | <para> |
---|
100 | TODO. |
---|
101 | </para> |
---|
102 | </sect2> |
---|
103 | |
---|
104 | <sect2> |
---|
105 | <title>MySQL</title> |
---|
106 | |
---|
107 | <para> |
---|
108 | A <application>MySQL</application> Storage Backend is planned, but it actually |
---|
109 | doesn't exist. |
---|
110 | </para> |
---|
111 | </sect2> |
---|
112 | |
---|
113 | <sect2> |
---|
114 | <title>LDAP</title> |
---|
115 | |
---|
116 | <para> |
---|
117 | An <application>LDAP</application> Storage Backend is planned, but it actually |
---|
118 | doesn't exist. Some people may already be working on this, though. |
---|
119 | </para> |
---|
120 | </sect2> |
---|
121 | |
---|
122 | <sect2> |
---|
123 | <title>Berkeley DB</title> |
---|
124 | |
---|
125 | <para> |
---|
126 | A <application>Berkeley DB</application> Storage Backend is planned, but it actually |
---|
127 | doesn't exist. It seems that remote storage won't be possible with such a backend, |
---|
128 | so in other terms this means that you will have a different quota database on |
---|
129 | each print server. This may still prove to be useful for small configurations. |
---|
130 | </para> |
---|
131 | </sect2> |
---|
132 | </sect1> |
---|
133 | |
---|
134 | <sect1> |
---|
135 | <title>Print Server Installation</title> |
---|
136 | |
---|
137 | <para> |
---|
138 | For each Print Server on which you plan to implement the print quota |
---|
139 | mechanism, you have, of course, to have an already working printing environment. |
---|
140 | Currently <application>PyKota</application> only works with the |
---|
141 | <ulink url="http://www.cups.org"><application>CUPS</application></ulink> environment, |
---|
142 | but more may be added in the future. |
---|
143 | </para> |
---|
144 | |
---|
145 | <para> |
---|
146 | TODO |
---|
147 | </para> |
---|
148 | </sect1> |
---|
149 | </chapter> |
---|
150 | |
---|
151 | <!-- |
---|
152 | |
---|
153 | $Log$ |
---|
154 | Revision 1.5 2003/03/22 13:11:33 jalet |
---|
155 | The port on which the Quota Storage Sever is listening can now |
---|
156 | be set in the configuration file (see sample). |
---|
157 | Better error handling if PygreSQL is not installed. |
---|
158 | Improved documentation. |
---|
159 | Version number changed to 1.02alpha |
---|
160 | |
---|
161 | Revision 1.4 2003/03/22 07:20:38 jalet |
---|
162 | More information wrt PostgreSQL tcp/ip configuration. |
---|
163 | |
---|
164 | Revision 1.3 2003/03/18 22:18:25 jalet |
---|
165 | The documentation will only be a sequence of chapters in a single part, not |
---|
166 | multiple parts each including chapters. |
---|
167 | |
---|
168 | Revision 1.2 2003/03/18 22:10:54 jalet |
---|
169 | Documentation improvements. |
---|
170 | |
---|
171 | Revision 1.1 2003/02/08 00:03:35 jalet |
---|
172 | Documentation skeleton added |
---|
173 | |
---|
174 | |
---|
175 | --> |
---|