Changeset - 335a132f436e
[Not reviewed]
0 1 0
Branko Majic (branko) - 2 months ago 2024-03-04 22:24:23
branko@majic.rs
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.
1 file changed with 13 insertions and 12 deletions:
0 comments (0 inline, 0 general)
docs/usage.rst
Show inline comments
 
@@ -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
 
<https://www.debian.org/releases/bullseye/amd64/apb.en.html>`_ for
 
<https://www.debian.org/releases/bookworm/amd64/apb.en.html>`_ for
 
more details.
 

	
 
If you need to, you can easily serve the preseed files from the Ansible server
0 comments (0 inline, 0 general)