There used to be a tool called tel that would show information about a user including his phone number, room number, etc:
$ tel tux
------------------------------------------------------------
Name : Tux Pinguin
Login : tpinguin
Phone : +49-911-740 53 - 12345
Department : [SUSE] SUSE LINUX GmbH
Position : Employee
Location : Maxtorhof, Room 3.2.15
Tasks : Be there and look nice
Absence : *** no absence data from workday (yet) ***
------------------------------------------------------------
As the backend (which is written in tcl and requires a tcl/tk application to change any data) is somewhat outdated and not really developed any further, there is now a new web based tool "Geekos" that provides a map of the building(s) and contains all the users.
Sadly this means that the data in the old tel backend ("present server") is not updated anymore and is even completely missing some users.
There is an LDAP based tool telnovell that provides a similar functionality to tel but is missing a very important information (the room number which is not stored in LDAP) and also has a very hard to understand code.
The goal of this project shall be to provide yet another tel tool that will query the information from Geekos. As Geekos is already aggregating information from different sources including LDAP and Externaltools all required information is present there. Also Geekos has a JSON API.
Done!
I finished a basic version of geekotel: https://gitlab.suse.de/dheidler/geekotel/
Sample output:
./gtel.py tux
------------------------------------------------------------
Name : Tux Pinguin
Login : tpinguin
Title : Linux Mascot
Team : Unicorn Team
Phone : +49 911 7405 3456
Mobile : +49 161 12345678
E-Mail : tpinguin@suse.com
Location : Room 3.2.15, Nürnberg, Germany
Workforce ID : 12345
Costcenter : 678901234
Accounts : GitHub : pinguu
------------------------------------------------------------
This project is part of:
Hack Week 19
Activity
Comments
Be the first to comment!
Similar Projects
Bring to Cockpit + System Roles capabilities from YAST by miguelpc
Bring to Cockpit + System Roles features from YAST
Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.
Goals
The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.
Resources
A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit
Linux System Roles: https://linux-system-roles.github.io/