[atlas] probe allocations

On 13.11.2013, at 19:26 , Andreas Strikos <astrikos at ripe.net> wrote:

> ... That situation was handled smoothly before a month, where we did a big change in the whole Atlas machinery in order to allow addition/removal of probes for all UDMs and unfortunately we broke this part. ...

With hindsight(!) this shows that adding and removing probes in existing measurements was probably not such a good design choice, although I supported it in order to allow repleneshing the probe pool of long-running measurements. Maybe it would be better to revisit that design and go for creating new measurements based on existing ones. We could maintain the genesis history, e.g. which measurement was used as a basis for creating the new one. This would allow tracing back the chain. We could also note that a measurement was used as a template for new measurements which allows following the genesis chain forward. This would solve Gert's use case.

It is never too late to review a design choice. It may be painful; but if it prevents future pain it may be the right thing to do.

Daniel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20131114/6f8a5289/attachment.sig>