zimoch/Controls-docs
0
0
Fork 0
forked from Controls/gitea-pages
Code Pull Requests Actions Activity

make the important things first

Browse Source
This commit is contained in:
buchel_k
2024-04-18 16:09:06 +02:00
parent cf87bbf05c
commit 58cf9b7614
1 changed files with 16 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
infrastructure-guide/custom_repositories.md
+16 -13
View File
@@ -1,11 +1,23 @@
# Custom RPM Repositories
It is possible to manage own RPM repositories which are accessible inside PSI.
If you need one please contact the Linux Core team (linux-eng@psi.ch).
To setup the your custom repository/ies we need following information:
- Name of the repository
- Do you want to have your repository available for __all__ RHEL major versions (i.e. all RHEL major versions will see the same packages) or do you need a repository for each RHEL major version (i.e. you can have different packages for each RHEL major version)?
## Usage
On `lxsup.psi.ch` you can easily access this data on `/packages_misc`.
The backend for these custom repos is on a NFS4 share. This share can be mounted from __lx-fs:/packages_misc__
On __Linux__ systems you should be able to mount the share like this
```bash
mount -t nfs4 -o sec=krb5,nfsvers=4 lx-fs.psi.ch:/packages_misc /mnt
mount -t nfs4 -o sec=krb5 lx-fs.psi.ch:/packages_misc /mnt
```
On __MacOS__ you could mount and access the share like this:
@@ -26,7 +38,6 @@ kinit
```
On lxsup.psi.ch you can easily access and test and use the NFS share by accessing `/packages_misc`.
## Overview
Custom repositories are provided by the central repository server as all other repositories. They will be available on the URL
@@ -50,15 +61,7 @@ The structure of the share is usually as follows:
The access control is done by a Unix group usually named `unx-<something>_adm` (most of the time this is a group that also gives access to hiera repos)
## Setup
If you need a custom RPM repository where you can place your specific RPMs/packages please contact the Linux Core team (linux-eng@psi.ch).
To setup the your custom repository/ies we need following information:
- Name of the repository
- Do you want to have your repository available for __all__ RHEL major versions (i.e. all RHEL major versions will see the same packages) or do you need a repository for each RHEL major version (i.e. you can have different packages for each RHEL major version)?
### Implementation
## Preparation for new Custom RPM Repository
The packages_misc share is only root writeable from lx-sync-01.psi.ch. Therefore the initial setup needs to be done there.
@@ -71,8 +74,8 @@ chmod g+w <reponame>
chmod g+s <reponame>
```
To sync the repo and make it available there need to be a sync config added to https://git.psi.ch/linux-infra/rpm-repo-utils/-/tree/main/etc?ref_type=heads
To sync the repo and make it available there needs to be a sync config added to https://git.psi.ch/linux-infra/rpm-repo-utils/-/tree/main/etc?ref_type=heads
(inside the __*-misc__ directories)
After adding this config the changes need to be deployed on lx-sync-01.psi.ch.
(either bootstrap/ansible or a manual `git pull` in `/opt/rpm-repo-utils/`)
(either bootstrap/ansible or a manual `git pull` in `/opt/rpm-repo-utils/`)