Perun repository overview

About this page

This page contains high-level description of how Perun AAI GitLab and GitHub repositories are organized and the reasons behind it.

Page owner: @Peter Lényi
Classification: community
Target audience: Perun team, Perun AAI community and partners

GitLab

Group hierarchy

Ther is one root group. It has one direct subgroup for each virtual team for compartmentalization Additional subgroups on lower levels of hierarchy can exist as needed to stay organized.

Perun projects

Perun group aggregates all subgroups and projects related to development and deployment of Perun AAI.

There should only be projects which are shared / included by other projects in the hierarchy.

Perun IdM projects

Perun IdM group owns projects related to development of Perun IdM by the Stribog team.

Currently, there is one project for backend, two for frontend: Old GUI vs. New GUI, and two for service scripts: for Linux vs. Windows machines.

Perun ProxyIdP projects coming soon

Perun ProxyIdP group owns projects related to development of Perun ProxyIdP by the Svarog team.

There are projects which are shared / included by other projects in the hierarchy. And then there are subgroups organized per programming language – currently Java, PHP and Python.

Perun DevOps projects coming soon

Perun DevOps group owns projects related to deployment of Perun AAI solution by the DevOps team.

There is a subgroup with projects related to Ansible and another one with projects related to Docker.

Compartmentalization is most important for this group as it is responsible for various secrets.

GitHub

Repository structure

CESNET organization owns ca. 300 repositories in total. Of those, the Perun-Admins team owns twelve.

Perun IdM repositories

There are five main Perun IdM repositories. They are mirrors of the GitLab Perun IdM projects.

Perun DevOps repositories

There are some repositories related to deployment of Perun AAI solution by the DevOps team. They should all be moved to GitLab.