What I use to Provision my personal Desktops with Ansible. The goal is to create a playbooks (and related roles in other repos) to quickly provision: Typically the latest Fedora and PopOS systems for my desktop general usage. This is not meant to be a highly generic set of playbooks that should work on anyone's hardware and OS, its more for me and for others to get a starting place. NOTE: Many of the logical aspects of the configuration elements these playbooks utilize has moved or will be moved to Ansible Roles in the near future. Ansible roles are generic and reusable, some of these roles are available and maintained by other on Ansible Galaxy while other roles are my own here on GitHub. This repo will ultimately be the orchestration for these roles as well as a placeholder for some of the vars that become parameters to the roles.
- Fedora playbooks and roles are tested and target to Fedora 40 KDE Spin and Nobara 40 KDE Spin
- PopOS is tested and target to PopOS 22.04 LTS with KDE (Kubuntu desktop)
Currently these playbooks where designed for local execution. Meaning the command node and managed node are the same. These are all run on and against localhost.
If you want to install KDE in Pop (which is what is tested) then before you install the bootstrap run a one time script:
curl -s https://raw.githubusercontent.com/billwheatley/provision-desktop/master/pre-pop-kde.sh | bash -NOTE: this is a temporary step until issue 8 is solved
sudo hostnamectl set-hostname <new hostname>Bootstrap Functions:
- Install Ansible, git and sshpass (compatible with
apt-get,dnforyumpackage managers) - Get these playbooks on your machine
- Ensure "
python" (without numbers) is in the path for Ansible - Generate ssh keys for the local user
From a directory you want to store these (ex: ~/dev/ansible-desktop/)
As your main admin/sudo user (do not sudo the call, that is done in the script):
cd ~
mkdir -p ~/dev/ansible-desktop
cd ~/dev/ansible-desktop
curl -s https://raw.githubusercontent.com/billwheatley/provision-desktop/master/bootstrap.sh | bash -If you plan on pushing changes from the clone of this repo created by the bootstrap there are several steps you need to remember to take.
The bootstrap created an ssh key and you will need to associate that to the Github account that has access to this repo
Copy your public key:
cat ~/.ssh/id_rsa.pubAdd your new SSH Key public key in Github SSH Key Settings
git remote set-url origin [email protected]:billwheatley/provision-desktop.gitSince these instructions are often done right after a fresh install, remember:
- Set your name globally.
- Configure just this repo's email address to the one associated with your GitHub account.
git config --global user.name "Bill Wheatley"
git config user.email [email protected]Sometimes we have those random rpms and debs that are not in public repos most because of distribution restrictions. Short of private repos, an easy solution is maintaining a local directory of these is just to drop these into a folder and this will pick up and install them.
Place your rpms in $HOME/automated-install/rpm/
If you have dependent rpms make sure they are also in the dir, these will be installed in a single command and rpm will figure out the dependencies. If your dependencies are packages in repos make sure those are added to one of the package repos. Those will be run before this.
This directory is not required if you have no rpms outside a repo.
Note: currently there is no automated upgrade of local rpms, see issue #14
Coming soon
Do the following as your main admin/sudo user (do not sudo the call, that is done in the script):
./provision-localhost.shThe script is designed to be run without any options however there are custom behaviors, you can use the -h option to see a current list of options:
./provision-localhost.sh -h