participate.html 2.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. {% extends "base.html" %}
  2. {% block content %}
  3. <h2>I want to participate!</h2>
  4. <p>This tool relies on a pool of workers, all over dn42, that process
  5. requests, perform ping measurements, and report back the results. You're
  6. welcome to add your own machines to the pool!</p>
  7. <h3>Registering a worker</h3>
  8. <p>You need to separately register each computer that will provide
  9. measurements. Manual validation is performed for each registration.</p>
  10. <p>The contact information is free-form, and will be shown to users when
  11. they launch measurements. This allows users to contact you if they want
  12. to peer.</p>
  13. <form class="participant_form" action="/create/participant" method="POST">
  14. <label for="name">Machine name (required)</label>
  15. <input type="text" name="name" id="name" /><br />
  16. <label for="contact">Mean of contacting you, like IRC nick, mail address, ... (optional)</label>
  17. <input type="text" name="contact" id="contact" /><br />
  18. <label for="country">Country code where this machine is located (optional)</label>
  19. <input type="text" name="country" id="country" /><br />
  20. <label for="comment">Free-form comment, like tunnel technology (GRE, OpenVPN, ...), or things like &quot;very shitty DSL&quot; (optional)</label>
  21. <input type="text" name="comment" id="comment" /><br />
  22. <input type="submit" value="Register" />
  23. </form>
  24. <h3>Measurement scripts</h3>
  25. <p>Currently, two measurement scripts are available, depending on your needs:
  26. <ul>
  27. <li><a href="/script.sh">shell script implemented as a self-contained loop</a></li>
  28. <li><a href="/cron.sh">shell script that you can run in cron</a></li>
  29. </ul>
  30. For both scripts, you need to edit the UUID variable to put your own UUID.
  31. </p>
  32. <p>Of course, you can write your own measurement scripts, using the
  33. still-undocumented API. Please make sure that your scripts are not too
  34. aggressive: you should not fetch jobs more often than 30 seconds, while 1
  35. minute is a good value. Please include a fairly large amount of jitter (a
  36. random sleep of at most 30 seconds, for instance). This avoids
  37. synchronisation between participants.</p>
  38. {% endblock %}