Howto

For all ICT related questions and problems within FNWI please contact C&CZ. Helpdesk & Sysadmin phone room mail +31 24 36 20000 HG00.051 helpdesk@science.ru.nl Visiting address We are located on in the front part of wing 5, ground floor of the Huygens Building (rooms HG00.051, HG00.509 and HG00.545). The helpdesk is available during office hours (8:30 - 17:00). During that time the office is staffed. Full address: Huygens Building, HG00.051, Heyendaalseweg 135, 6525 AJ Nijmegen ...

To ensure the stability and security of our compute clusters, C&CZ performs regular maintenance. Info ...

The Uncloud Howto delves deep(er) into what you get when you have an Uncloud cluster to play with. Keeping services within a cluster up to date is essential, but manually updating versions can quickly become tedious. This guide explains how to connect a GitLab project to an Uncloud cluster to automate the deployment of new images and services. Prerequisites An Uncloud cluster. For Gitlab to have access the config.yaml should: current_context: test contexts: test: connections: - ssh: uc@uncloud5.vm.science.ru.nl ssh_key_file: $UNCLOUD_SSH_PRIVATE_KEY machine_id: 0b104736144524a903ae4d523c0e0ed5 The idea of the $UNCLOUD_SSH_PRIVATE_KEY variable is that it is populated by Gitlab. SSH access to the cluster. See the access section. As the SSH private key need to be uploaded into GitLab it is advisable to just create another SSH key of type login for cluster access. Make sure your application is available as a container image. See our image project for an example. You’ll need a runner that is able to run docker or docker-in-docker. Of course you are also free to run container images from the Docker registry. A compose.yaml with the services you want to deploy. See compose.yaml changes for Uncloud specific differences below in this document. CI/CD Configuration Next, we need to teach Gitlab how to connect to the cluster. Lets create the following variables in the Gitlab project: ...

You were just given an Uncloud cluster. Now what? This howto explains what Uncloud is, why we think its needed and some pointers other documentation. At the end you’ll find a FAQ like section. We very much want Uncloud to profit from our use, so our intention is to upstream as much documentation as possible. Also see my personal journey with Uncloud; those articles are also in the process of being integrated with the Uncloud documentation. ...

Computer cluster architecture The clusternodes that we manage for the various departments are all connected to the network, but not all are in the same subnet/vlan. We strive to keep the nodes of a single group in the same vlan to optimise internal network traffic. Connectivity with the storage servers for shares and homedirectories is always routed through the firewall, thus it is less performant than a local server and much less performant than local (within the server) storage on /scratch. ...

This document gives a short description which decisions have to be made before creating a new web site. C&CZ is not the communications department, officially all communication and therefore web sites should be provided and endorsed by the communication department. However, sometimes a web site is actually an application with a web interface and this can usually not be provided via the official communication website. Preferably a site with a URL like https://<somesite>.science.ru.nl is used, but if necessary, we can request an additional domain under whatever toplevel you need. Be aware that this is most likely against the official policy regarding websites. ...

C&CZ manages about 400 Linux servers and hundreds of Linux workstations. The servers are distributed over three datacenters. Workstations C&CZ manages (for departments) workstations with Ubuntu Linux. There are also Linux workstations in the PC-rooms for general use by anybody with a Science login, but also by all RU employees and students and guests with a temporary login. Linux login servers A few secure shell servers are available for Students and Staff of the Faculty (everyone with a Science account). You can use it just as you like, as long as you do not cause problems for other users. ...

Science login A Science login provides faculty students and employees access to services like networked storage, computer labs, JupyterHub, clusternodes and GitLab & Mattermost. A Science login usually resembles your name and does not contain periods, capital letters or an at sign (@). For example johndoe. All settings related to your Science login, like setting your password, MFA, storage, groups and email aliases can be managed in DIY. See the DIY howto for more information. For Students & Employees To create your Science login: ...

Introduction In our Faculty, different types of data storage are offered: Storage class Description Risk for data loss Home directories Small (several GB), reliable, backed up storage for individuals low Network shares Larger (1-200 TB), reliable, backed up storage for individuals or groups low Local storage Not backed up storage on desktop computers and cluster nodes, likely to be lost in case of a hardware problem or when the machine gets reinstalled high Home directories Your Science login comes with a home directory of 5GB at no costs. This is a safe place to store your work related documents. Home directories are stored on reliable hardware and backed up automatically. If you need more than 5GB of storage, you can enlarge it on DIY. Before doing so, you may want to clean up some data. ...

location Operations/helpdesk is located in room HG00.051. Type of help available User support for students and staff (General IT questions) Installation and maintenance of hardware available for students, especially the computer labs and public workstations General support of computer equipment in research departments Assistance for, or advice with respect to, PC installation and software repairing PC’s and laptops