29 Jul
2018
29 Jul
'18
5:33 p.m.
On Sunday 29 of July 2018 12:15:07 Mike Bird wrote:
Hi Slávek,
I am not yet understanding why we have so much duplication. Why is
there not a "testing" release in the main repository instead of a
having a main repo and a DEB PSB repo and a RPM PSB repo in different
locations and using different tooling? (And soon in addition a new DEB
testing repo?)
I understand that PSB updates every two hours whereas the primary
mirror currently checks for updates three hours after the completion of
the previous run, but I could change the three hour delay to a ten
minute delay without adversely impacting Tim's bandwidth. What is the
average volume (GB) of DEB PSB updates published per day?
The standard single Debian repository structure is well understood by
all concerned. It reduces the number of downloads and upgrades needed
for new minor releases and generally provides a smoother and more
efficient transition from testing to release. Indeed Trinity
successfully used a single repo incorporating trinity-nightly-builds
for many years.
Hi Mike,
I'll start with the simplest part - RPM packages:
For RPM packages, there is nothing that QuickBuild could offer because it
is only for DEB packages. All RPM packages are created by François, where
the creation of source packages, building and publishing to the
repository takes place completely outside of the primary server - on
François server. From the François server, RPM repositories are first
synchronized to the primary TDE server => it takes some time because the
bandwidth to the primary server. Subsequently, RPM repositories are
synchronized from primary TDE server to the primary mirror => it takes
some time, because the bandwidth from the primary server. When this is
done, RPM packages are synchronized from primary mirror to other mirrors.
With a major update, such as a new TDE release, it usually takes several
days or even weeks. Note: The current RPM repository size is 43 GiB.
On a VPS that has the role of the main redirector, the RPM repository is
synchronized directly from the François server to the local cache on the
redirector. Due to the fact, that the redirector is on wide bandwidth
(300 Mbps) and the François server also has a good bandwidth,
synchronization takes place quickly - it usually takes only a few hours.
Once the RPM packages are available in the cache on the redirector, they
can be served to users directly from this cache, regardless of whether
synchronization from the François server to the primary TDE server has
already been completed, regardless of whether all subsequent
synchronizations are completed.
Advantages?
+ packages are accessible to users very soon after publishing by François
+ the time during which the RPM repository is inconsistent is very short
+ users' access to packages does not cause load of bandwidth to the primary
server
+ once some packages begin to be available at least on the primary mirror, the
redirector will then direct users' access to the mirror
Disadvantages?
+ on the redirector is required space for whole RPM repository
+ once mirrors synchronization is complete, cache of RPM packages on
redirector remain unused (until the next update by François)
Any comments, questions or suggestions for this part?
--
Slávek