ansible issueshttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues2021-09-03T15:58:06+02:00https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/15Provision new user rule2021-09-03T15:58:06+02:00sg7149Provision new user ruleRolle zum Anlegen und Entfernen von neuen Nutzern.
* [ ] JIRA-Ticket für Confluence-User https://docs.ansible.com/ansible/latest/jira_module.html (u-Kürzel)
* [ ] FreeIPA-Account (Nachname)
Leider noch nicht automatisierbar sind Sympa ...Rolle zum Anlegen und Entfernen von neuen Nutzern.
* [ ] JIRA-Ticket für Confluence-User https://docs.ansible.com/ansible/latest/jira_module.html (u-Kürzel)
* [ ] FreeIPA-Account (Nachname)
Leider noch nicht automatisierbar sind Sympa und GitLab-Gruppen-Angehörigkeit
Bitte auch mit issue #13 abstimmenhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/25texlive package names might change in future Fedora releases2021-09-03T14:43:48+02:00sg7149texlive package names might change in future Fedora releasesFedora 27 does not use the current stable TexLive version 2017.
For the next Fedora release the names of the texlive packages might change, because there is an [issue about renaming](https://bugzilla.redhat.com/show_bug.cgi?id=1505342) f...Fedora 27 does not use the current stable TexLive version 2017.
For the next Fedora release the names of the texlive packages might change, because there is an [issue about renaming](https://bugzilla.redhat.com/show_bug.cgi?id=1505342) from `texlive` into `texlive-base` and `texlive`.
Test via copr:
```
dnf copr enable spot/texlive
```https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/35Icinga2021-09-03T15:49:56+02:00sg7149IcingaHost: las126.las.kit.edu, las100, las101, +Opt-In
OS: Fedora, CentOS
Software name:
--------------
Icinga2 or other monitoring software
Software installation instruction if not in repos:
-----------------------------------------------...Host: las126.las.kit.edu, las100, las101, +Opt-In
OS: Fedora, CentOS
Software name:
--------------
Icinga2 or other monitoring software
Software installation instruction if not in repos:
--------------------------------------------------
* Temperatures
* HDD live and
* Load
* Network connectivity are very simple to install as far as I know.
Status of our services
* DHCPd
More difficult/not implemented yet, but basic features might be detectable with other modules:
* IPA functionality
Probably there are already roles in the ansible-Galaxy.
Possibly also interesting for:
-------------------------------
Clients as Opt-In, because it causes privacy issues (admins can see for how long the computer was turned on and how long a user was logged in, to name just a few)
User stories (kind of):
-----------------------
Clients:
* The user starts a job on his computer and he cannot log-in at the next morning. Is the computer gone for good? Is it just still to busy to take care of things like the log-in-manager? Are the hard-drives gone, because of the room heated up? -> Get hints of the cause of the problem.
* The user cannot log-in. Maybe IPA the network is down and therefore she cannot log-in, maybe IPA is down, maybe she just typed a wrong password.
Server:
* IPA went down and nobody notices it, because sssd caches it and no log-in errors occurred until half a year later. Then one can find out, since when IPA was not working and if a update might have triggered it. Or one can prevent it in the first place, by regularly monitoring the monitoring software.
* DHCPd went down and nobody notices it, because the workstations work with fixed IPs
* Docker GitLab-runner do not work and jobs have to fail to recognize it. Maybe an system update caused this and not a reboot without autostart.
* sharelatex is down and one gets a mail/call from CN, because they want to collaborate on a paper that needs to be submitted the next day.
/cc @project-managerhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/37Docker Gitlab-CI runner2021-09-03T15:49:17+02:00sg7149Docker Gitlab-CI runner* [x] Install GitLab-CI runners (docker) on a proper computer (ask @gethmannn for documentation on the installation on Fedora and it's pitfalls) and
* [ ] create example `.gitlab-ci.yml` files for typical use-cases
* [ ] LaTeX: compil...* [x] Install GitLab-CI runners (docker) on a proper computer (ask @gethmannn for documentation on the installation on Fedora and it's pitfalls) and
* [ ] create example `.gitlab-ci.yml` files for typical use-cases
* [ ] LaTeX: compilation of a document
* [ ] Python: linting PEP-8 or formatting with yapf
* [ ] shell: run shellcheck
* [ ] Document how to use the CI
* [ ] For the owner of the repo
* [ ] For a user who might be confused about merge requests or push commands being rejected
Things to discuss:
* Worth it?
* las126 or las101
* install runner on all clients? That would be a much bigger task imho.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/45Create test infrastructure for ansible2021-09-03T15:41:08+02:00sg7149Create test infrastructure for ansibleTest ansible roles with GitLab-CI.
[ ] CI runners that start a new Docker of the currently supported Fedoras and run `sites.yml`Test ansible roles with GitLab-CI.
[ ] CI runners that start a new Docker of the currently supported Fedoras and run `sites.yml`https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/52pyepics does not work on CN with Python 32019-02-14T15:21:55+01:00sg7149pyepics does not work on CN with Python 3pyepics is not importable with Python 3
@ucegg : I cannot reproduce this behaviour, so please elaborate on this issue.
My try shows the following expected behaviour:
```
messuser@las94:~$ python2
Python 2.7.15 (default, Oct 15 2018, 18...pyepics is not importable with Python 3
@ucegg : I cannot reproduce this behaviour, so please elaborate on this issue.
My try shows the following expected behaviour:
```
messuser@las94:~$ python2
Python 2.7.15 (default, Oct 15 2018, 18:36:25)
[GCC 7.3.1 20180712 (Red Hat 7.3.1-6)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import epics
>>> exit()
messuser@las94:~$ python3
Python 3.6.6 (default, Jul 19 2018, 16:29:00)
[GCC 7.3.1 20180303 (Red Hat 7.3.1-5)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import epics
>>> exit()
```
and not an `ImportError`https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/53sublime-merge2019-02-08T20:48:36+01:00sg7149sublime-mergehttps://www.sublimemerge.com/docs/linux_repositories#dnf
might be a software that is useful for new git users and those who prefer GUIs over CLI and do not use IDEs (PyCharm) either.https://www.sublimemerge.com/docs/linux_repositories#dnf
might be a software that is useful for new git users and those who prefer GUIs over CLI and do not use IDEs (PyCharm) either.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/85Opera on Fedora 312020-03-02T14:52:39+01:00sg7149Opera on Fedora 31To work around Opera not starting on Fedora 31 I linked the libhwloc.so.5->libhwloc.so.15.
Maybe one should also copy libhwloc.so.5 from CentOS7 (kantine) instead of linking the new one.
Probably also the new Opera 2020 will not depend ...To work around Opera not starting on Fedora 31 I linked the libhwloc.so.5->libhwloc.so.15.
Maybe one should also copy libhwloc.so.5 from CentOS7 (kantine) instead of linking the new one.
Probably also the new Opera 2020 will not depend on libhwloc.so.15, because their webpage claims to support RHEL7, but not RHEL8 and even RHEL8 seems to have libhwloc.so.5 instead of .15.