{{ 'New Repository' | translate }}

New Repository

Basic Information

Choose Default to enable the repository for all architectures

Sync Settings

URL of the registry you want to sync. Example: https://registry-1.docker.io/

Comma separated list of releases (suite or codename) to sync from. Default: stable

Comma separated list of components to sync from (leave clear to sync all). Example: main

Comma separated list of processor architectures to filter the sync by. Example: amd64

Choose one of the policy selections for downloading ostree content from upstream url during synchronization. Choose "Latest" for downloading the latest version of the upstream branch. Choose "All History" to download all available versions of the upstream repository (this may take a large amount of space). Choose "Custom Depth" and provide an number to indicate the number of prior versions of the upstream branch to download.

Name of the upstream repository you want to sync. Example: 'busybox' or 'fedora/ssh'.

Select content units to ignore while synchronizing this repository.

Selecting this option will result in Katello verifying that the upstream url's SSL certificates are signed by a trusted CA. Unselect if you do not want this verification.

Username of the upstream repository user for authentication. Leave empty if repository does not require authentication.

Password of the upstream repository user for authentication. Leave empty if repository does not require authentication.

For On Demand synchronization, only the metadata is downloaded during sync and packages are fetched and stored on the filesystem when clients request them. For Background synchronization, a background task will download all packages after the initial sync. The Immediate option will download all metadata and packages immediately during the sync.

Selecting this option will result in contents that are no longer part of the upstream repository being removed during synchronization.

Selecting this option will result in the globally configured http proxy from not being used.

Published Repository Information

For older operating systems such as Red Hat Enterprise Linux 5 or CentOS 5 it is recommended to use sha1.