Comment 1 for bug 314726

With the introduction of activities, requests to test images are initiated from the hardware certification website rather than from each satellite server. So, the probing of the image sites such as cdimage.u.c and releases.u.c is performed centrally and then corresponding activities can be enqueued for each satellite server. For example, upon probing a new milestone, a request could be enqueued to test all systems. As another example, upon probing a daily current image, a request could simply be enqueued for a single machine or one of each machine category.

In order to support this new concept, the satellite server should now run a derivation of the checkbox-compatibility project in order to exchange messages with the hardware certification website using a streamlined protocol. Furthermore, the code base now becomes more streamlined by using checkbox derivations instead of yet another design.