Add dirk to community sudo group
[cacert-infradocs.git] / docs / glossary.rst
1 Glossary
2 ========
4 .. glossary::
5 :sorted:
8 LXC is a userspace interface to the Linux kernel containment features.
9 See `The LXC introduction
10 <>`_ on the Linux containers
11 website for more information
13 Container
14 A container is an isolated system with a separate root file system and
15 operating system userland. The containers share a common operating system
16 kernel.
18 LVM
19 Logical volume manager. The LVM allows to allocate space on block
20 devices more dynamically than with traditional partitions. The block
21 devices are managed as physical volumes (PVs) that are grouped in volume
22 groups (VGs). Space can be allocated as logical volumes (LVs) that can be
23 formatted using regular file system tools. LVs can be resized without
24 reboot. LVM provides snapshot functionality that is useful for backup and
25 upgrade procedures.
27 Infrastructure Team Lead
28 This person is appointed to coordinate the non-critical infrastructure
29 team by a board motion. The Infrastructure Team Lead works with
30 :term:`Infrastructure Administrators <Infrastructure Administrator>` and
31 the :term:`Critical System Administrators <Critical System
32 Administrator>`.
34 Infrastructure Administrator
35 Infrastructure Administrators have :program:`sudo` access to one or
36 multiple infrastructure systems. Most of them are :term:`Application
37 Administrators <Application Administrator>` too.
39 Critical System Administrator
40 The Critical System Administrators take care of the critical systems
41 required for the CA and RA operation, they have access to the Internet
42 firewall and DNS setup.
44 Application Administrator
45 An Application Administrator takes care of the functionality of one or
46 more server applications. Application Administrators do not necessarily
47 need system level access if the managed application has other means of
48 administration, for example a web based administration frontend.
51 Domain Key Identified Mail
52 A mechanism where legitimate mail for a domain is verifiable by a
53 signature in a mail header and a corresponding public key in a specific
54 :term:`DNS` record. Outgoing mail servers for the domain have to be
55 configured to add the necessary signature to mails for their domains.
57 DNS
58 Domain Name System
59 DNS maps names to other information, the most well known use case is
60 mapping human readable names to IP addresses, but their are more
61 applications for DNS like service discovery, storage of public keys and
62 other public information.