This is the openSUSE Management Tool. It is used by different teams related with openSUSE like:
- openSUSE Admin Team
- openSUSE Team at SUSE
If you have any question, please contact any of the above teams.
The first steps to a more modern infrastructure
Hack Week 17 was the perfect opportunity to try modern technologies in order to take our infrastructure one step further. The beginning of this journey is here, enjoy :)
Extended maintenance this Thursday, 2017-12-07
As announced on [status.opensuse.org](https://status.opensuse.org/schedules/5), we will have a bigger scheduled maintenance work ahead on Thursday, 2017-12-07, from 08:00 until 10:00 CET (07:00 until 09:00 UTC).
New Galera cluster running in production
Two important databases are using the new (mariadb) galera cluster now: https://connect.opensuse.org and https://progress.opensuse.org are now completely migrated.
Statistic pages from our Monitoring
While monitoring helps to get informed about outages and problems, it also allows you to get some trends about services and produce nice graphs from it.
New Galera Cluster up and running
While we still migrate services over into the "openSUSE Heroes" network, we also use the time to improve the old setup and implement a more robust and reliable infrastructure.
openSUSE Leap 15.2 (16/04/2019 02:18 pm)
Tasks related to the openSUSE Leap 15.2 release
openQA Infrastructure (16/10/2018 09:06 am)
Problems not to be fixed in github repos of os-autoinst or openQA, but not test related either. Mainly things about openqa.suse.de and openqa.opensuse.org
QA (15/06/2018 06:37 pm)
General project coordinating the quality assurance and development of test automation for SUSE and openSUSE products
openSUSE Leap 15.1 (30/05/2018 03:19 pm)
Tasks related to the openSUSE Leap 15.1 release
invis-sub-setup (09/03/2018 11:13 am)
The goal of this project is to develop a software-package for an easy setup of an invis "subsidiary" server. This server is an file-server at it's own, he is placed at a subsidiary location of a company. His connection to the main invis-server is realized via vpn. He should be a domain-member-server and it should be possible to synchronize data between main- and subsidiary-server....