README.md 1.89 KB
Newer Older
julian.gethmann's avatar
julian.gethmann committed
1
# Ansible repository for LAS/CS NSQ computer
2
You need to have access to this repository (viz you need to add your public ssh-key (`ssh-keygen`) to your profile here.
julian.gethmann's avatar
julian.gethmann committed
3
4
5
`git clone git@git.scc.kit.edu:las/ansible.git`

## How to use ansible for software installation/computer setup
6
7
8
9
10
Add your computer to the hosts file or if you are just testing add it to the local file.
Add your hostname under each role name (the name in the square brackets) you want to be run on your computer.
Also create a new file with an named 
after your [fully-qualified-domain-name](https://de.wikipedia.org/wiki/Domain_(Internet)#Fully_Qualified_Domain_Name_.28FQDN.29}) in the `host_vars` directory including a [yaml](https://docs.ansible.com/ansible/YAMLSyntax.html) list with some host specific configuration variables, e. g. copy another similar host and adjust it.
These files do not have the `.yml` extension and do not start with `---`
julian.gethmann's avatar
julian.gethmann committed
11
12
* install ansible (`dnf install ansible`)
* run ansible-pull (`ansible-pull -U git@git.scc.kit.edu:las/ansible.git`)
julian.gethmann's avatar
julian.gethmann committed
13
14
15
16
17
18
19
20
21
22
23

### Ask for new software
Open an issue in the GitLab issue tracker with the label: softwarerequest
## How to get new software on your computer

## Available roles

* common.yml: basic configuration for all LAS/NSQ computers
* clients.yml: all computers not acting as a server (only)
* desktop.yml: all desktop computers including laptops (having X11/Wayland)
* admin.yml: tools for administrators
24
* latex.yml: basic LaTeX installation (KIT classes not yet)
julian.gethmann's avatar
julian.gethmann committed
25
26
27
28
29
30
31
32

# Develope new roles, extend or modify existing ones and update roles for new software

## Branches
All roles in the master branch should work and should not brake on any of our systems (desktop, server, simulation, notebooks) and the site.yml should always be runnable.

For developement and testing you should use development branches

julian.gethmann's avatar
julian.gethmann committed
33
34
35
36
37
## TODO
* nfs-server, lasarchiv1
* epics
* elegant (blas: gescheit die key-verwaltung lösen)
* dhcpd