Commit dbeb2349 authored by julian.gethmann's avatar julian.gethmann

Update README.md

Add hint to the issues with explicit dependencies
parent 86ca71d6
......@@ -6,12 +6,12 @@ Then you can clone the git repository to work on in locally.
## How to use ansible for software installation/computer *setup*
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
Also create a new file which is named
after your [fully-qualified-domain-name](https://de.wikipedia.org/wiki/Domain_(Internet)#Fully_Qualified_Domain_Name_.28FQDN.29}) (FQDN) 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 `---`
Then create a file named after your FQDN with the extension ".yml" in the main directory of ansible which contains includes all the roles one want to run. This step needs root priviledges and therefore makes only sense for the first installation of a computer.
* install ansible and some dependencies (`dnf install ansible git python2-dnf libselinux-python`)
* run [ansible-pull](https://docs.ansible.com/ansible/playbooks_intro.html#ansible-pull) (`ansible-pull -K -U git@git.scc.kit.edu:las/ansible.git`)
* run [ansible-pull](https://docs.ansible.com/ansible/playbooks_intro.html#ansible-pull) (`ansible-pull -K -U git@git.scc.kit.edu:las/ansible.git playbook_name.yml`)
* If you only want some parts of the roles to be run, you can use the option `-t TAGNAME` to run only those tasks with the given tag.
### Ask for new software
......@@ -21,19 +21,23 @@ Open an issue in the GitLab issue tracker with the label: softwarerequest
## Available roles
* common.yml: basic configuration for all LAS/NSQ computers
* clients.yml: all computers not acting as a server (only)
* clients.yml: all computers not acting as a server (only) ^1
* desktop.yml: all desktop computers including laptops (having X11/Wayland)
* python.yml: basic python_stack for scientific Python usage (including fitting)
* ipynb.yml: IPython/Jupyter notebook
* python.yml: basic python_stack for scientific Python usage (including fitting) ^1
* ipynb.yml: IPython/Jupyter notebook ^1
* MAD-8: MAD 8 inofficial build for Fedora
* nfs.yml:
* nfs-server: export /las-archiv1 to our network
* lasarchiv: client side mount las126/las-archiv1
* opera.yml: Cobham's Opera3d (client)
* opera.yml: Cobham's Opera3d (client) ^2 ^3
* admin.yml: tools for administrators
* latex.yml: basic LaTeX installation (KIT classes not yet)
* latex.yml: basic LaTeX installation (KIT classes not yet) ^1
* kdev.yml: KDevelope (with Python PlugIn) ^1
### Opera
^1: (also put your FQDN to the \[common\] section in the hosts file as it depends hereon)
^3: (also put your FQDN to the \[lasarchiv\] section in the hosts file as it depends hereon)
### ^2 Opera
After installing Opera via ansible you must confirm the license agreement at first start and go to "Licensing -> Set License Path" and switch to `Other computer(s)` and fill in `@129.13.108.100`.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment