-
Notifications
You must be signed in to change notification settings - Fork 1
YUM repositories and mirrors
RPM publication on YUM repositories is organized into 2 phases:
- the package is uploaded to the master mirror
- at regular intervals, the mirrors are synced with master mirrors
There are 2 master mirrors:
- packages.nethserver.org: Community master mirror
- packages.nethesis.it: Enterprise master mirror
Access to master mirrors is strictly regulated. See:
- https://github.com/nethesis/ansible-nethinfra
- https://github.com/nethesis/ansible-nethinfra/blob/master/docs/pkg.md
RPMs are published to packages.nethserver.org and are instantly accessible to anyone.
As exception, nethserver-testing repository is not mirrored to save bandwidth.
How to create a mirror: http://community.nethserver.org/t/how-to-create-your-own-nethserver-mirror/344
HTTP access: http://packages.nethserver.org/nethserver/
RPMs are published to packages.nethesis.it and are directly accessible only from Nethesis (see below).
The public mirror is synced overnight, once a day
HTTP access: http://packages.nethesis.it/nethserver/enterprise/
Enterprise repositories are directly accessible only to Nethesis network without using server registration key.
cat > /etc/yum.repos.d/neth_install.repo << EOF
[nethesis-updates]
name=Nethesis - updates
baseurl=http://packages.nethesis.it/nethserver/enterprise/\$releasever/nethesis-updates/\$basearch
gpgcheck=0
enablegroups=1
enabled=1
http_caching=none
[nethesis-testing]
name=Nethesis - testing
baseurl=http://packages.nethesis.it/nethserver/enterprise/\$releasever/nethesis-testing/\$basearch
gpgcheck=0
enablegroups=0
enabled=1
http_caching=none
EOF
| tier | day | coverage |
|---|---|---|
| base | Tue | 5% |
| t1 | Wed | 15% |
| t2 | Thu | 30% |
| t3 | Fri | 50% |
More info available at packages.nethesis.it.
Q. If a developer releases a packages inside nethserver-testing, when the package will be available to users?
A. Immediately from packages.nethserver.org, by enabling nethserver-testing repository in the machine.
Q. If a developer releases a packages inside nethserver-updates (community), when the package will be available to users?
A. Immediately from community mirror, by enabling nethserver-updates repository in the machine; otherwise since the next week, accordingly to above automatic calendar
Q. If a developer releases a packages inside inside an Enterprise repository (testing, updates, upgrades), when the package will be available to users as manual update?
A. The next day, from update.nethesis.it
Q. If a developer releases a packages inside inside nethesis-updates, when the package will be available to users as automatic update?
A. The update will be available from next day.