From 335a132f436e23e603aa8d1f6268fbbecbec51ea 2024-03-04 22:24:23 From: Branko Majic Date: 2024-03-04 22:24:23 Subject: [PATCH] MAR-192: Updated controller and base server installation instructions to use Debian 12 Bookworm: - Reword some senteces. - Some reformatting changes. - Update list of packages getting installed in the Python virtual environment. --- diff --git a/docs/usage.rst b/docs/usage.rst index 73b942195261a64b809d9a47bdaae52b86fc76b3..d13a877ece8b0b193dfc63456843896aabd20968 100644 --- a/docs/usage.rst +++ b/docs/usage.rst @@ -47,22 +47,23 @@ Pre-requisites For the set-up outlined in this usage guide you'll need the following: -* One server where Ansible will be installed at. Debian Bullseye will +* One server where Ansible will be installed at. Debian Bookworm will be installed on top of this server. The server will be set-up manually (this is currently out of scope for the *Majic Ansible Roles* automated set-up). -* Three servers where the services will be set-up. All servers must be able to - communicate over network with each-other, the Ansible servers, and with - Internet. Debian Bullseye will be installed on top of this server as part of the - usage instructions. -* Debian Bullseye network install CD. +* Three servers where the services will be set-up. All servers must be + able to communicate over network with each-other, the Ansible + servers, and with Internet. Debian Bookworm will be installed on top + of these servers as part of the usage instructions. +* Debian Bookworm network installation CD. * All servers should be on the same network. * IP addresses for all servers should be known. * Netmask for all servers should be known. * Gateway for all servers should be known. -In case of the servers listed above, it might be safest to have them as VMs - -this is cheapest thing to do, and simplest (who wants to deal with pesky hardware anyway?). +In case of the servers listed above, it might be safest to have them +as virtual machines - this is cheapest thing to do, and simplest (who +wants to deal with pesky hardware anyway?). Usage instructions assume the following: @@ -147,11 +148,11 @@ packages, and to prepare the environment a bit on the Ansible server: mkdir ~/mysite/ mkvirtualenv -p /usr/bin/python3 -a ~/mysite/ mysite pip install -U pip setuptools - pip install 'ansible~=2.9.0' dnspython netaddr + pip install 'ansible~=2.9.0' netaddr .. warning:: - The ``dnspython`` package is important since it is used internally via - ``dig`` lookup plugin. + The ``netaddr`` package is important since it is used internally via + ``ipv4/ipv6`` lookup plugin. Cloning the *Majic Ansible Roles* @@ -428,7 +429,7 @@ You have your preseed files now, so you can go ahead and install the servers ``comms.example.com``, ``www.example.com``, and ``bak.example.com`` using them with network install CD. Have a look at `Debian instructions -`_ for +`_ for more details. If you need to, you can easily serve the preseed files from the Ansible server