root / pykota / trunk / README @ 2714

Revision 2714, 27.5 kB (checked in by jerome, 19 years ago)

Updated installation doc.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1# $Id$
2
3PyKota - Print Quotas for CUPS and LPRng
4
5(c) 2003, 2004, 2005, 2006 Jerome Alet <alet@librelogiciel.com>
6This program is free software; you can redistribute it and/or modify
7it under the terms of the GNU General Public License as published by
8the Free Software Foundation; either version 2 of the License, or
9(at your option) any later version.
10
11This program is distributed in the hope that it will be useful,
12but WITHOUT ANY WARRANTY; without even the implied warranty of
13MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
14GNU General Public License for more details.
15
16You should have received a copy of the GNU General Public License
17along with this program; if not, write to the Free Software
18Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
19
20====================================================================
21
22READ SPECIAL LICENSING AND REDISTRIBUTION TERMS IN THE FILE 'LICENSE'
23
24====================================================================
25
26PyKota features :
27-----------------
28
29    Free Software :
30   
31        - Licensed under the terms of the GNU General Public License.
32       
33    Commercially Supported :   
34   
35        - Support Contracts are available from http://www.librelogiciel.com/techsupport/
36       
37    Operating systems :
38   
39        - Any Unix-like system as print server.
40           
41        - Any operating system as client.
42           
43    Printing systems :
44   
45        - Supports both CUPS and LPRng as the printing system.
46          NB : LPRng is only supported with versions
47          of PyKota <= v1.22HotFix1, but support for LPRng
48          may be reintroduced at a later date.
49          This version DOES NOT support LPRng !
50       
51    Databases :
52   
53        - Supports PostgreSQL as the database backend.
54          An SQL script to create the database is included.
55       
56        - Supports any LDAP server as the database backend.
57          Complete LDAP schema and sample empty tree are included.
58          Plugging PyKota into your existing LDAP infrastructure
59          is really easy thanks to PyKota's great configurability.
60         
61        - Supports SQLite as the database backend.
62          An SQL script to create the database is included.
63         
64        - Supports MySQL as the database backend.
65          An SQL script to create the database is included.
66
67        - The print jobs history can be stored in any database 
68          of your choice (or in plain text files) if needed.
69         
70        - Master and slave databases are supported : master 
71          in read+write mode, slave in readonly mode.
72          Master and slave databases can be of different types !
73           
74    Printers :       
75   
76        - Hardware or Software accounting methods are completely
77          configurable.
78         
79        - Supports any printer which can report its internal
80          page counter. Can ask printers for their internal
81          page counter via SNMP, Netatalk, PJL, PS, or any
82          other way.
83          This is completely configurable.
84         
85        - Supports DSC compliant and binary PostScript, PDF, PCL5 (up to),
86          PCLXL (aka PCL6), ESC/P2, DVI, TIFF, OpenDocument (OpenOffice.org)
87          and Zenographics ZjStream natively (through the direct use of
88          pkpgcounter's code) for software accounting methods. More formats
89          to come.
90         
91        - Supports any other Page Description Language for which you 
92          have a parser which can be scripted.
93           
94    Quota systems :       
95   
96        - Supports printers and printers groups quotas.
97       
98        - Supports users and users groups quotas.
99       
100        - Supports page quotas.
101          Page quotas can be set differently on a per printer
102          and per user/group basis.
103       
104        - Supports account balance quotas in any currency.
105          Account balance quotas can be set on a per user
106          basis. The account balance is shared amongst
107          all printers. The history of payments (positive
108          or negative credits to an user account) is kept.
109         
110        - Supports high granularity periodic print quotas : down
111          to one minute intervals if needed.
112       
113        - Page quotas and account balance can be set/reset
114          independantly.
115         
116        - Page quotas can be set on a per user or per group basis
117          for a particular printer.
118         
119        - Price per page and per job can be set differently 
120          on any printer.
121       
122        - Low level of page quota or account balance are
123          configurable.
124         
125        - Both soft and hard limit with configurable grace delay 
126          can be set for page quota.
127         
128        - Both soft and hard limits can be increased or decreased at will. 
129       
130        - Possibility to disable quota enforcement for any user
131          or group, while still keeping page accounting.
132         
133        - Each user can have an overcharging (or undercharging) factor, 
134          which is applied whenever PyKota computes the cost of a
135          print job.
136         
137        - Specific pages and credits counters can be defined per billing code,
138          and can be reset independantly of the printing history.
139         
140        - Supports a passthrough mode for printers, which doesn't modify 
141          users quota when they print.
142         
143        - Supports a maximum number of pages per job, configurable for each 
144          printer.
145         
146        - Each user can be completely forbidden to print, independantly from
147          other users.
148         
149        - A transparent printing mode is supported for users, in which
150          their quota is not modified when they print.
151         
152    Administration :       
153   
154        - Almost turn-key solution, with the help of the pkturnkey command
155          line tool for database initialization and initial configuration.
156         
157        - Powerful delegation of administrative priviledges.
158       
159        - Powerful administration tools can be used to
160          automate setting or resetting of quotas or
161          account balances at specific intervals.
162         
163        - Administration tools can modify several users, 
164          groups, or printers at once with the use of
165          powerful wildcard characters.
166         
167        - Account balances can be set, incremented, or 
168          decremented. History of payments is kept.
169         
170        - Number of pages used can be set, incremented, or 
171          decremented.
172         
173        - Both printers and users can be automatically added on
174          first print in a completely configurable way.
175         
176        - Quota report generator available either from the 
177          command line or in any web browser.
178          The web-based quota report generator can be
179          user/password protected.
180         
181        - Print quote generator can tell users how much 
182          a print job will cost them in advance.
183         
184        - PDF invoice generator to charge back users.
185         
186        - Policy with regard to unregistered users can   
187          be configured for each printer to either deny
188          printing, allow printing, or delegate the
189          decision to any external tool.
190         
191        - Warning and error messages can be automatically 
192          sent via email or via any other mean to the administrator,
193          the user, both, or none.
194         
195        - Warning and error messages' content is completely
196          configurable.
197         
198        - Configuration can be changed without needing to 
199          restart the printing system.
200       
201        - Complete print job history is kept. This can be
202          disabled if needed.
203         
204        - Automated low quota or balance remainder can be
205          scheduled regularly or launched manually.
206         
207        - Starting and Ending personalized dynamic banners can be
208          generated on the fly, and accounted for or not, depending
209          on some configuration settings.
210          Banners can still be enabled even if the print job is denied.
211          NB : Banners are a CUPS only feature for now.
212         
213        - Duplicate print jobs can be forbidden automatically. The decision
214          can be left to any script to decide this on a per job basis.
215         
216        - Username and billing code can be overwritten at printing time,
217          to allow people to login as guest users and print as authenticated
218          users, for example.
219         
220        - Powerful data dumper to export datas to other
221          software (spreadsheets for example). Actually
222          supported formats are :
223         
224            - Comma separated values ;
225           
226            - Semicolon separated values ;
227           
228            - Tab separated values ;
229           
230            - XML.
231           
232            - CUPS' page_log format, to easily interface in
233              real time with third party apps like phpPrintAnalyzer
234              and similar tools.
235         
236    User Interface :         
237   
238        - All the command line tools accept the -h | --help
239          command line option which prints all the available
240          options and show usage examples.
241         
242        - Completely internationalized. Actually supports at least partially
243          English, French, Polish, Spanish, Portuguese, Brazilian, Swedish,
244          Thai, Greek, German, Italian, Norwegian (Bokm�, Turkish
245          and traditional Chinese languages.
246          More to come.
247         
248        - Web enabled print quota monitor, data dumper, and quote
249          generator.
250       
251        - An On Screen Display X-Window print quota monitor is included.
252       
253        - An email gateway to allow users to retrieve their print quota
254          information by sending an email message to a dedicated address
255          is included.
256       
257        - A cross-platform print quota monitor will soon be available
258          as an purchaseable add-on.
259         
260        - Third party web based management tools are available.
261
262====================================================================
263       
264Planned features are described in the TODO file.
265
266Actually two (or an infinity of) page accounting methods are
267implemented :
268
269  - The 'hardware' method consists in querying the printer (via SNMP
270    or Netatalk or any other method of your choice) for its total pages
271    counter.
272    This is done both at the beginning and at the end of a
273    print job. The counters difference is then immediately used to
274    decrease the user's account balance or increase his quota usage.
275   
276  - The 'software' method consists in delegating the computation of the
277    job's size in number of pages to any external command of your choice.
278    The command can read the job's data from its standard input and MUST
279    output the job's size on its standard output. Changes to the user
280    account are reported immediately.
281   
282    PyKota featured an internal software accounting method which handles
283    several Page Description Languages : DSC compliant and binary PostScript,
284    PDF, PCLXL (aka PCL6), PCL3/4/5, ESC/P2, DVI, TIFF, OpenOffice.org Writer
285    and OpenOffice.org Impress. This software is now distributed separately
286    as 'pkpgcounter', and not included anymore in PyKota, so you must now
287    download and install it before running PyKota.
288   
289PyKota is known to work fine with most laser printers, either with
290software accounting, or with hardware accounting if the printer
291supports this.
292
293============================================================
294
295SUPPORT CONTRACTS:
296==================
297
298  You can now purchase 8x5x365@NextBusinessDay Technical
299  Support Contracts from us. The yearly fee is computed with 
300  the following formula :
301
302  (100.0 * NbPrintServers) + (2.5 * NbPrinters) + (0.04 * NbUsers) EUROS.
303 
304  This fee includes the VAT, and a free subscription to Official
305  PyKota packages.
306
307  Please send an email to alet@librelogiciel.com if you're
308  interested in purchasing such a contract.   
309
310  Remember that purchasing a support contract for Free Software like PyKota
311  is a great way to show your appreciation for the work already being done
312  on this project, and will help to improve this software in the future.
313
314============================================================
315
316INSTALLATION:
317=============
318
319NB :
320====
321
322  PyKota's documentation is available as DocBook SGML sources
323  files in the pykota/docs directory. If you obtained an
324  Official package, in the same directory you'll also find
325  the documentation in HTML and PDF formats.
326 
327  PyKota's collaborative documentation is available from :
328 
329    http://www.librelogiciel.com/software/PyKota/WiKota/
330   
331  You may learn more about PyKota, if it fits your own organization,
332  its internal working, and some potential performance drawbacks and
333  how to avoid them, in a document created by Ryan Suarez at :
334 
335    http://archive.macosxlabs.org/forum/webcrossing_archive/documentation/Pykota_and_CUPS/Pykota_and_CUPS.html
336
337  You may also find the following document interesting :
338 
339    http://es.tldp.org/Tutoriales/doc-openldap-samba-cups-python/
340   
341  This document, written in Spanish by Sergio Gonzalez Gonzalez, 
342  describes the integration of PyKota into an OpenLDAP + Samba
343  + CUPS installation. Even for people who can't read spanish
344  this document is really interesting, and contains lots of
345  screenshots.
346 
347  Finally, SuSe users may find the following document to best describe
348  how to install PyKota on their favorite distribution. It's a Spanish
349  document written by Dennis Romero, and is mostly outdated now :
350 
351    http://www.cvr.espol.edu.ec/people/dennis/Pykota1.19-SuSE9.1.pdf
352 
353 
354Prerequisite :
355--------------
356   
357  See :
358 
359    http://www.librelogiciel.com/software/PyKota/WiKota/Dependencies
360   
361  for an up-to-date list, or see below (maybe not up-to-date) :
362 
363  You need to have the following tools installed on the CUPS Server :
364 
365    - CUPS (http://www.cups.org)
366    - Python v2.1 or above (http://www.python.org)
367    - eGenix' mxDateTime Python extension (http://www.egenix.com)
368    - The pkpgcounter command line tool, version 1.56 or higher. This
369      tool is now mandatory for PyKota to work.
370      (http://www.librelogiciel.com/software/)
371    - The JAXML Python module to be able to dump datas in the XML format.
372      (http://www.librelogiciel.com/software/)
373    - The Python-SNMP module to query printers for their page counter.
374      (http://pysnmp.sourceforge.net).
375      IMPORTANT : version 3.4.4 (or 3.4.3 or 3.4.2) is REQUIRED.
376      Versions 2.x or 4.x won't work for now.
377    - The Python-OSD module to use the graphical print quota reminder.
378      (http://repose.cx/pyosd/)
379    - SNMP tools (specifically the snmpget command) if you prefer to
380      use your own script to request query printers.
381      (http://www.net-snmp.org)
382    - Netatalk (specifically the pap command) if you plan to
383      request your printer's lifetime page counter via AppleTalk.
384      (http://netatalk.sourceforge.net)
385    - The ReportLab Python module (http://www.reportlab.org) if you want 
386      to have PyKota generate nice banners for you.
387    - The Python Imaging Library (aka PIL) module
388      (http://www.pythonware.com/downloads) if you want to have PyKota
389      generate nice banners for you.
390    - PostgreSQL's PygreSQL Python extension and the PostgreSQL client
391      libraries if you plan to use PostgreSQL as the database backend.
392      (http://www.postgresql.org and http://www.pygreql.org)
393 or     
394    - python-ldap Python module and the OpenLDAP client libraries 
395      if you plan to use an LDAP server as the database backend.
396      (http://www.openldap.org and http://python-ldap.sourceforge.net)
397 or
398    - SQLite v3.2.7 and the SQLite libraries if you plan to use SQLite
399      as the database backend (http://www.sqlite.org). You also need the
400      PySQLite module v2.0.5 or higher (http://www.pysqlite.org)
401 or
402    - The MySQL-python bindings.
403      IMPORTANT: If you are using MySQL 4.1, then MySQL-python must be
404      version 1.2 or greater. Version 1.0 does not work correctly with 4.1.
405     
406   
407  On Intel i386 architecture, and for performance reasons, it is
408  strongly suggested that you install the Python accelerator Psyco,
409  available at :
410 
411      http://psyco.sourceforge.net
412     
413  Under Debian :   
414 
415      $ apt-get install python-psyco
416     
417  Other architectures may be supported as well in the future, check   
418  this on Psyco's website.
419 
420  Installing Psyco is not mandatory, but it will speedup PCL5 parsing
421  by almost 3 times. PostScript and PDF parsing can also benefit,
422  but in an almost unnoticeable manner since this part of the code
423  is already optimal. For PCL5 this is a completely different matter,
424  and if you install Psyco you will never regret it !
425  Same remark applies for PCL6 (aka PCLXL) : the parser is completely
426  different, but the performance gain with Psyco is impressive.
427 
428  You may also benefit from having the following tools installed to
429  deal with some printers :
430 
431    - npadmin
432    - netcat
433    - ghostscript
434   
435  You need to have the following tools installed on the database
436  server :
437 
438    - PostgreSQL (http://www.postgresql.org)
439   
440  or 
441 
442    - OpenLDAP, or any other LDAP server (http://www.openldap.org)
443   
444  or   
445 
446    - SQLite, v3.2.7 or higher (http://www.sqlite.org).
447      Beware : with SQLite the database server and the print
448      servers MUST be the very same machine.
449     
450  or     
451 
452    - MySQL 4.0 or higher.
453   
454  This list of prerequisite software may change in the future, when
455  PyKota will support more functionnalities you will be given
456  alternatives.
457 
458  Of course the Print Server and the database server can be the
459  very same machine if you've got a tiny network, or you can have
460  multiple Print Servers all storing their quotas on the same database
461  server if you've got a bigger network. (NB : with SQLite, the database
462  can't be shared between several print servers)
463 
464Hint : 
465------
466
467  - The Debian GNU/Linux distribution is to our knowledge the
468    easiest distribution to install PyKota on, because all
469    of PyKota dependencies are already included, excepted
470    for the PySNMP (http://pysnmp.sourceforge.net) module
471    and the pkpgcounter utility which for now have to be downloaded
472    and installed separately.
473
474Then :   
475------
476 
477Download the latest PyKota version from the Subversion tree :
478
479    $ svn co svn://svn.librelogiciel.com/pykota/trunk pykota
480
481You can now check if the dependencies are correct by typing :
482
483    $ python checkdeps.py
484   
485    An availability report for all the software needed by PyKota
486    will be displayed : you'll have to install the missing
487    software if you want PyKota to work correctly.
488   
489To install the software, just type :
490
491    $ python setup.py install
492
493You may need to be logged in with sufficient privileges (e.g. root)
494
495Create a system user for PyKota :
496
497    $ adduser --system --group --home /etc/pykota --gecos PyKota pykota
498   
499Put the user your printing system is run as in the pykota system group :
500
501    $ adduser lp pykota
502   
503    NB : on our system, the CUPS printing system runs as system user 'lp'.
504    Please adapt this to your own system.
505
506Go to the initscripts subdirectory of PyKota's sources, and choose
507the appropriate storage backend for your configuration. Read carefully
508the associated README file and execute the initialization script
509to create an empty PyKota database. Upgrade scripts may be
510provided as well. NB : if you use PostgreSQL, a good way to
511make PyKota work first time is to modify PostgreSQL's pg_hba.conf
512to allow the 'trust' database connection mode. However once PyKota
513works it is HIGHLY RECOMMENDED TO CHANGE THIS TO A MORE SECURE
514VALUE.
515
516Copy the conf/pykota.conf.sample and  conf/pykotadmin.conf.sample
517sample configuration files to /etc/pykota/pykota.conf and
518/etc/pykota/pykotadmin.conf 
519The installation script usually copies these files into /usr/share/pykota
520
521NB : You can move PyKota's configuration files elsewhere, they will
522be searched first in user pykota's home directory.
523
524You need to adapt these files to your own needs. Especially you may
525have to create sections named after your own printers, and change
526the administrator's email address which by default is
527root@localhost. Read and try to understand these two very well
528commented files, so that you'll encounter less problems later.
529
530Also be sure to double check that commands that query printers
531for their internal page counter work from the command line
532before using them in PyKota's configuration.
533
534The rest of the installation depends on your printing system :
535
536  - CUPS Printing System :
537 
538    Once and for all :
539   
540        Create a symbolic link to the cupspykota backend
541        in CUPS's backend directory :
542       
543          $ cd /usr/lib/cups/backend
544          $ ln -s /usr/share/pykota/cupspykota cupspykota
545         
546        Restart CUPS so that the new backend can be detected.
547       
548          $ /etc/init.d/cupsys restart
549         
550        or :   
551     
552          $ /etc/rc.d/init.d/cupsys restart
553         
554        or any similar command depending on your operating system. 
555         
556    For new printers :
557   
558        Go to CUPS management interface (http://localhost:631)
559        and choose the appropriate PyKota managed device depending
560        on the type of printer you use. For example, if your
561        printer is waiting on :
562       
563            socket://myprinter.example.com:9100
564           
565        Then choose :   
566       
567            cupspykota:socket://myprinter.example.com:9100
568           
569        Configure your printer as usual.   
570       
571        Now double check /etc/pykota/pykota.conf
572       
573        You should manually create a section named after the
574        printer you've just added, unless you have set
575        all options globally.
576       
577        The new pkturnkey command can help you with correct settings
578        for your printers, but don't rely on it because it is still
579        experimental work. To have pkturnkey give you some hints
580        about what to put into pykota.conf, just use its --doconf
581        command line switch :
582       
583          $ pkturnkey --doconf
584       
585        pkturnkey will try to tell you what is the best accounting
586        method for each printer and will print some lines you'll
587        just have to copy&paste in the appropriate sections in
588        /etc/pykota/pykota.conf
589       
590        For more informations about what pkturnkey can do for you,
591        see pkturnkey's manual page or use the --help command
592        line switch :
593       
594          $ pkturnkey --help | less
595       
596        That's all.
597   
598    For existing printers :
599   
600        The easiest is to directly modify the DeviceURI lines
601        in /etc/cups/printers.conf, you just have to put
602        'cupspykota:' in front of what is already on these lines.
603        For example, replace :
604   
605            DeviceURI socket://myprinter.example.com:9100
606       
607        with :   
608   
609            DeviceURI cupspykota:socket://myprinter.example.com:9100
610           
611        or :   
612       
613            DeviceURI cupspykota://socket://myprinter.example.com:9100
614       
615        Save the file and restart CUPS.
616       
617        Here too, you may find it interesting to use the pkturnkey command as
618        described above to help with manual configuration of the file
619        /etc/pykota/pykota.conf
620
621  - LPRng Printing System :
622 
623    IMPORTANT : This release of PyKota DOES NOT support LPRng.
624   
625    If you want to use PyKota with LPRng, you have to download
626    an earlier release of PyKota, for example v1.22HotFix1.
627       
628Now you can begin to populate the PyKota's database with printers,
629users and groups :
630 
631Add printers and users to the quota system and set their quota values :
632
633You can either use pkturnkey, or do the same things manually by
634using the pkprinters, pkusers and edpykota command line tools :
635
636Create printers :
637
638    $ pkprinters --help
639   
640    will tell you how to create, manage or delete printers and
641    printers groups.
642   
643    $ pkprinters --add --charge 0.05 hp2100
644   
645    would add the printer named hp2100 with a price per page
646    of 0.05 unit.
647
648Create users :
649
650    $ pkusers --add --limitby balance --balane 10.0 jerome
651   
652    would create user jerome and give him ten credits to spend
653    on any printer.
654   
655Finally create print quota entries :
656
657    $ edpykota --add -P hp2100 jerome
658       
659    This will create a print quota entry for user jerome on   
660    printer hp2100. The print quota entry holds the number of
661    pages printed on a particular printer for a particular
662    user, as well as optional page limits to be used instead
663    of balance limits. See pkusers and edpykota's manual
664    pages for details.
665   
666Restart CUPS, for example under Debian GNU/Linux systems :         
667
668    $ /etc/init.d/cupsys restart
669   
670Your users now should be able to print but not exceed their
671printing quota.
672
673To see printer quota usage on printer hp2100, you can use :
674
675    $ repykota --printer hp2100
676   
677or :
678
679    $ repykota
680   
681    which will print quota usage for all users on all printers,
682    along with totals, if you are a PyKota Administator. If you are
683    a regular user, only your own quota report will be produced.
684   
685Quota reports are also available remotely by using the CGI script
686printquota.cgi provided in the cgi-bin/ subdirectory. You can
687also use the CSS stylesheet present in the stylesheets/ subdirectory
688and put it at your web server's DocumentRoot, to benefit from a nicer
689look, especially quota violations will appear in different colors.
690
691For additionnal security concerns, please give a look at the SECURITY
692file which is part of this software.
693
694To diagnose a problem when something doesn't work as expected,
695please read the very first entry in the FAQ document.
696           
697============================================================
698
699Additionnal tools :
700-------------------
701
702Some people have developped tools around PyKota, and make
703them available under the GNU General Public License :
704
705  - Kanakorn Horsiritham developped phpPykotaAdmin which is
706    a web based database independant administrative GUI,
707    written in PHP.
708 
709      http://opensource.psu.ac.th/~kanakorn/mambo/
710     
711    He was also kind enough to write an installation guide 
712    in english for CUPS and PyKota with phpPykotaAdmin on Fedora
713    Core 3. You'll find this document on the same website.
714   
715    This great software currently at version 0.3 is a wonderful
716    basis for an administrative GUI since it only depends on
717    PyKota commands to be present to successfully manage
718    PyKota's database.
719 
720Additionnal software will be listed here when they will be 
721ready.
722
723============================================================
724
725Mailing list :
726--------------
727
728  A mailing list is dedicated to Pykota, you can subscribe to it
729  or consult its archives at :
730 
731    http://cgi.librelogiciel.com/mailman/listinfo/pykota
732   
733  The mailing list is the preferred way to obtain support, because 
734  all members can help and can also benefit from the solutions
735  proposed by other members.
736 
737  Posts by non-members are usually rejected.
738 
739  The mailing list language is english and only english.
740   
741IRC :   
742-----
743
744  You can also chat with us :
745 
746        /server irc.freenode.net
747        /join #pykota
748       
749  Preferred language on this channel is english, but french     
750  is also accepted. Try to avoid exposing complex problems
751  in french because english speaking people on the channel
752  wouldn't benefit from the solutions.
753 
754  PyKota's main author is known as 'tamere' on IRC.
755   
756============================================================
757   
758Please e-mail bugs to the mailing list at : pykota@librelogiciel.com
759or to the main author at : alet@librelogiciel.com (Jerome Alet)
Note: See TracBrowser for help on using the browser.