https://github.com/metaswitch/azure-blobrepo-rpm
Functionality to create and maintain an RPM package repository in Azure Blob Storage
https://github.com/metaswitch/azure-blobrepo-rpm
azure-storage blob-storage function-app rpm rpm-packages
Last synced: 6 months ago
JSON representation
Functionality to create and maintain an RPM package repository in Azure Blob Storage
- Host: GitHub
- URL: https://github.com/metaswitch/azure-blobrepo-rpm
- Owner: Metaswitch
- License: mit
- Created: 2024-09-18T13:45:03.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2025-03-31T16:31:29.000Z (6 months ago)
- Last Synced: 2025-04-01T13:17:38.473Z (6 months ago)
- Topics: azure-storage, blob-storage, function-app, rpm, rpm-packages
- Language: Python
- Homepage:
- Size: 202 KB
- Stars: 1
- Watchers: 2
- Forks: 1
- Open Issues: 9
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Security: SECURITY.md
- Support: SUPPORT.md
Awesome Lists containing this project
README
# azure-blobrepo-rpm
Functionality to create an RPM package repository in Azure Blob Storage with
an Azure Function App to keep it up to date.
For use with [microsoft/dnf-plugin-azure-auth](https://github.com/microsoft/dnf-plugin-azure-auth).
# Getting Started
## Required tools
- `poetry` and `poetry-plugin-export`: required for running the creation commands and exporting dependencies to requirements.txt format.
- Poetry installation instructions are available at https://python-poetry.org/docs/#installation
- Once poetry is installed, run
```bash
poetry self add poetry-plugin-export
```
to install `poetry-plugin-export`.
- Azure CLI
- Installation instructions available at https://learn.microsoft.com/en-us/cli/azure/install-azure-cli
- Docker
- Installation instructions available at https://docs.docker.com/engine/install/
## Basic usage
To create a new RPM package repository with an Azure Function App, run
```bash
poetry run create-resources
```
with the name of the desired resource group. The scripting will autogenerate a
package repository name for you - `rpmrepo` followed by a unique string to
differentiate it across Azure.
If you wish to control the suffix used, you can pass the `--suffix` parameter:
```bash
poetry run create-resources --suffix
```
which will attempt to create a storage container named `rpmrepo`.
By default all resources are created in the `eastus` location - this can be
overridden by passing the `--location` parameter:
```bash
poetry run create-resources --location uksouth
```
## Installing the `dnf` plugin and downloading packages
To install packages from your new repository:
### For distribution repositories
- Create a repository file `/etc/yum.repos.d/.repo` with the following content
for each distribution you want to support:
```ini
[{distribution}]
name={distribution}
baseurl={base url given by create-resources}/{distribution-letters}/{distribution-numbers}/
enabled=1
gpgcheck=0
skip_if_unavailable=1
```
and add an entry to `/etc/dnf/plugins/azure_auth.conf` with the following format:
```ini
[{distribution}]
```
For example, to support a distribution `el8` in storage account `rpmrepodemo`
the repository and config file might look like:
```ini
[rpmrepodemoel8]
name=rpmrepodemoel8
baseurl=https://rpmrepodemo.blob.core.windows.net/packages/el/8/
enabled=1
gpgcheck=0
skip_if_unavailable=1
```
```ini
[rpmrepodemoel8]
```
and a distribution 'fc34' would look like:
```ini
[rpmrepodemofc34]
name=rpmrepodemofc34
baseurl=https://rpmrepodemo.blob.core.windows.net/packages/fc/34/
enabled=1
gpgcheck=0
skip_if_unavailable=1
```
```ini
[rpmrepodemofc34]
```
Multiple repository definitions can exist in the same repository file.
Multiple entries can exist in `azure_auth.conf`.
### For flat repositories
- Create a repository file `/etc/yum.repos.d/.repo` with the following content:
```ini
[]
name=
baseurl={base url given by create-resources}/
enabled=1
gpgcheck=0
skip_if_unavailable=1
```
- Add an entry to `/etc/dnf/plugins/azure_auth.conf` with the following format:
```ini
[]
```
### For all repository types
- Install `dnf-plugin-azure-auth`.
- Install the plugin from https://github.com/microsoft/dnf-plugin-azure-auth
- Now, use yum/dnf as normal! The plugin will authenticate using the `az` cli
tool to generate credentials for the repository.
```shell
$ dnf list | grep rpmrepo
Using Azure authentication for rpmrepodemocm2
demo.x86_64 1.0.0-1.cm2 rpmrepodemocm2
```
# Design
The function app works as follows:
- It is triggered whenever an `.rpm` file is uploaded to the monitored blob
storage container in the configured upload directory.
- It is triggered by an Event Grid trigger.
- The packages are organised by distribution.
- This is determined by the `release` of the package - the expected format
for this is
`.[.]`
- The distribution is expected to be a series of letters followed by a series
of numbers
- Any packages without a distribution are moved to the `rejected` folder.
- Any packages that have the same name as an existing package remain in
the upload directory.
- It then iterates over all `.rpm` files and looks for a matching `.package` file.
- If that file does not exist, it is created
- The `.rpm` file is downloaded and repository metadata is generated using
`createrepo_c`.
- The metadata is bundled into the `.package` file.
- All `.package` files within a distribution are iterated over, downloaded, and
combined into a single set of repository metadata using `mergerepo_c`.
## Speed of repository update
The function app triggers at the speed of an Event Grid trigger running in Consumption
mode; in the worst case this means triggering from a Cold Start. In practice
the repository is updated within 1 minute.
# Project
## Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
## Trademarks
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft
trademarks or logos is subject to and must follow
[Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general).
Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
Any use of third-party trademarks or logos are subject to those third-party's policies.