Draft an Acceptable Use Policy for GPU hardware in Fedora Infrastructure #35

New issue

Open

opened 2026-07-16 19:45:11 +00:00 by jflory7 · 0 comments

jflory7 commented

2026-07-16 19:45:11 +00:00

Owner

Summary

Begin drafting an Acceptable Use Policy (AUP) for GPU hardware available through Fedora Infrastructure, with the goal of presenting it to the Fedora Infrastructure team for review.

Background

As GPU hardware becomes available in Fedora Infrastructure for CI and testing purposes, there is no documented policy defining acceptable use, access controls, or trust requirements. In the 2026-07-16 SIG meeting, @gordonmessmer observed that "CI" describes a mechanism for launching batch jobs, not a purpose. Without a policy that defines acceptable purposes, access controls are incomplete regardless of the technical mechanism used to run jobs. @tflink noted that Fedora Infrastructure has managed packager-checkout-able systems for exotic hardware (s390x, PPC) in the past, so precedent exists, though the details of how those were configured are unclear. @trix raised that trust boundaries must be part of any access model.

Details

This ticket is for initial SIG discussion and drafting. The AUP should address at minimum:

What purposes are acceptable for GPU hardware (e.g., package CI, hardware enablement testing).
What purposes are not acceptable (e.g., cryptocurrency mining, missile guidance systems, training your personal Skynet).
Access controls: who can submit jobs, and through what trust model.
How Fedora Infrastructure can detect or audit improper usage.
Precedent from past checkout-able systems in Fedora Infra.

This is not something the SIG can decide alone. Once we have an initial draft, we need to present it to the Fedora Infrastructure team for review and collaboration. See ai-ml/tickets#34 comment.

FYI

Tagging some folks from Infrastructure and QA for awareness: @kevin, @gwmngilfen, @adamwill, @kparal, @humaton. No action needed from any of you right now. We want to sketch out some initial ideas as a SIG first, and then bring something concrete to you for feedback. That said, if you have thoughts now, we would love to hear them.

Outcome

A draft AUP document ready to share with Fedora Infrastructure for feedback, with clear definitions of acceptable use, access controls, and trust requirements for GPU hardware.

_{Assisted-by: Claude Opus 4.6 (1M context)}

### Summary Begin drafting an Acceptable Use Policy (AUP) for GPU hardware available through Fedora Infrastructure, with the goal of presenting it to the Fedora Infrastructure team for review. ### Background As GPU hardware becomes available in Fedora Infrastructure for CI and testing purposes, there is no documented policy defining acceptable use, access controls, or trust requirements. In the [2026-07-16 SIG meeting](https://discussion.fedoraproject.org/t/fedora-ai-ml-sig-meeting-2026-07-16-skills-reviewers-team-approved-help-wanted-with-llama-cpp-and-navigating-gpu-infrastructure/196876), @gordonmessmer observed that "CI" describes a mechanism for launching batch jobs, not a purpose. Without a policy that defines acceptable purposes, access controls are incomplete regardless of the technical mechanism used to run jobs. @tflink noted that Fedora Infrastructure has managed packager-checkout-able systems for exotic hardware (s390x, PPC) in the past, so precedent exists, though the details of how those were configured are unclear. @trix raised that trust boundaries must be part of any access model. ### Details This ticket is for initial SIG discussion and drafting. The AUP should address at minimum: 1. What purposes are acceptable for GPU hardware (e.g., package CI, hardware enablement testing). 2. What purposes are not acceptable (e.g., cryptocurrency mining, missile guidance systems, training your personal Skynet). 3. Access controls: who can submit jobs, and through what trust model. 4. How Fedora Infrastructure can detect or audit improper usage. 5. Precedent from past checkout-able systems in Fedora Infra. This is not something the SIG can decide alone. Once we have an initial draft, we need to present it to the Fedora Infrastructure team for review and collaboration. See [ai-ml/tickets#34 comment](https://forge.fedoraproject.org/ai-ml/tickets/issues/34#issuecomment-1063263). ### FYI Tagging some folks from Infrastructure and QA for awareness: @kevin, @gwmngilfen, @adamwill, @kparal, @humaton. No action needed from any of you right now. We want to sketch out some initial ideas as a SIG first, and then bring something concrete to you for feedback. That said, if you have thoughts now, we would love to hear them. ### Outcome A draft AUP document ready to share with Fedora Infrastructure for feedback, with clear definitions of acceptable use, access controls, and trust requirements for GPU hardware. <sub>_Assisted-by: Claude Opus 4.6 (1M context)_</sub>