Ansible Collection - redhat_cop.fedora_desktop

Introduction

This collection offers a set of roles and other utilities to build and configure a Fedora Desktop in a fully automated and repeatable manner.

Even though the automation is mainly based on Ansible and is packaged as an Ansible collection, certain elements are not related to Ansible (mainly the scripts) to simplify the bootstrap if you don't have Ansible yet installed.

This documentation uses the following terminology:

1. the "control host" is a "RHEL-ish" Linux machine (Fedora, CentOS, ...) on which you'll prepare the configuration for the Fedora Desktop, and use Ansible to start the deployment.
2. the "desktop", even if it might be a laptop or any other form factor, even a VM, is the machine you are planning to install Fedora onto.
3. the "webserver" is a web server, which one doesn't matter, from which you'll serve the kickstart file necessary to steer the installation. The control host can be used as webserver.

Newcomers instructions

Those instructions are meant to get people without Ansible knowledge started. If you're a seasoned Ansible user, you can simply use this collection like any other Ansible collection, and consider these instructions as one usage example of it. These instructions are kept on purpose as straightforward as possible, even the scripts have more options than described, and the roles/modules used probably even more.

1. get the collection on your control host, either using Git or ansible-galaxy, and change to the corresponding directory:

# using Git with SSH key (requires a GitHub account)
git clone [email protected]:redhat-cop/automate_fedora_desktop.git
cd automate_fedora_desktop

# using Git with HTTPS (without GitHub account necessary)
git clone https://github.com/redhat-cop/automate_fedora_desktop.git
cd automate_fedora_desktop

# or using ansible-galaxy (once this collection has been released)
ansible-galaxy collection install redhat_cop.fedora_desktop
cd ~/.ansible/collections/ansible_collections/redhat_cop/fedora_desktop/

2. Call ./scripts/00_control_bootstrap.sh to install the necessary pre-requisites on the control node. You will need sudo rights to install Ansible and a few other dependencies. The -h option gives you a short usage help. The developer mode only makes sense if you've downloaded this collection using Git, and plan to modify it.

3. Call ./scripts/10_inventory_create.sh <desktop-name> to create a basic inventory for the desktop. The -h option gives you a short usage help. In the Ansible world, an inventory is a set of hosts and their variables. Go through the variable files created under ./inventory.myown.d/host_vars/<desktop-name> and adapt them to your needs. Each file should have a set of YAML variables sufficiently explained, but in doubt you can check the file roles/<role-name>/README.md where role-name is the same as the file's name in the inventory.

4. Download the (latest) Fedora Server Network Install ISO image, and verify it according to the instructions on the web page! Then copy the ISO image to the correct USB stick (pay attention to the correct X according to lsblk! See preparation details) with sudo dd if=Fedora-Server-netinst-x86_64-38-1.6.iso of=/dev/sdX bs=8M status=progress.

5. Call ./scripts/20_desktop_create.sh -so <desktop-name> to create the desktop. The -h option gives you a short usage help. In the current state of the implementation, only a kickstart file is created and served via a simple but insecure approach. Perhaps we can do more in the future, but for now the control host acts as webserver. The playbook will hang for one hour, giving you ample time to install your new desktop. You can kill the playbook but beware that the HTTP server will continue to run and needs to be killed if you want to restart the playbook with the same port.

6. From now on, be VERY CAREFUL: the new desktop will be completely WIPED. Boot the new desktop from the previously created USB stick (how depends on its make), then

   1. Select the first line of the menu (Start Fedora...) with the up/down keys and press 'e' for Edit.
   2. Edit the 'linuxefi' line: linuxefi inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-38 inst.ks=http://my.own.web.server:8000/myhost.ks (basically replace quiet with inst.ks=...). Check more boot options.
   3. Press Ctrl-x to start
   4. Wait until the laptop is installed and rebooted. You can login as local admin, or your own user, and continue with the configuration, SSHD runs and Ansible is installed. If defined so, this Git repo is already available in /var/tmp/fedansy to continue.

7. You're almost there, you only need to configure your main user or the admin user:

   1. if not already done during the kickstarted installation, you need to copythe collection and your inventory locally (as in step 1) and prepare the machine (as in step 2).
   2. for the last step explained here, you'll call directly Ansible as an exercise with ansible-playbook --inventory /var/tmp/fedansy/inventory.myown.d redhat_cop.fedora_desktop.user_configure --limit $(hostname) --connection local or shorter `ansible-playbook -i /var/tmp/fedansy/inventory.myown.d redhat_cop.fedora_desktop.user_configure -l $(hostname) -c local.

NOTE: other created users on the same machine can as well configure their environment automatically but they'll need to create their own inventory for the user_* roles.

Maintenance

Once you've configured your system and your user, you should make sure to keep your inventory safely somewhere, so that you can re-create your desktop if needed.

As your needs evolve, and this collection gets new feature, you can extend and modify the inventory and call again and again the correct playbooks to update accordingly your system:

1. update locally the system with ./scripts/80_desktop_update_local.sh -r.

2. re-configure the system with ansible-playbook --inventory /var/tmp/fedansy/inventory.myown.d redhat_cop.fedora_desktop.system_configure --limit $(hostname) --connection local -K.

3. re-configure the user with ansible-playbook --inventory /var/tmp/fedansy/inventory.myown.d redhat_cop.fedora_desktop.user_configure --limit $(hostname) --connection local.

4. or call a single role with something like ./scripts/90_call_role.sh system_software.

And with sufficient Ansible knowledge, you can do all this and much more, even remotely and on multiple desktops at once. Learn Ansible and try it!

Contribute

See our Contributor Guide.