Source files of fsfe.org, pdfreaders.org, freeyourandroid.org, ilovefs.org, drm.info, and test.fsfe.org. Contribute: https://fsfe.org/contribute/web/ https://fsfe.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

news-20150527-01.en.xhtml 4.5KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <html newsdate="2015-05-27">
  3. <head>
  4. <title>FSFE is looking for a systems administrator and
  5. architect</title>
  6. </head>
  7. <body class="press release">
  8. <h1>FSFE is looking for a systems administrator and
  9. architect</h1>
  10. <p newsteaser="yes">
  11. <strong>Please note that this position is no longer open for
  12. applications.</strong><br />
  13. The Free Software Foundation Europe was
  14. founded in 2001 and has gone through a tremendous growth
  15. since then, both in the number of volunteers and staff, and
  16. also in the complexity of our technical infrastructure and
  17. the number of services we run and offer for both internal and
  18. external use. We're currently looking for a system
  19. administrator and architect that, for a limited time, can
  20. support us in our work to migrate our services to a new
  21. infrastructure.</p>
  22. <p>The migration project will move our services to a new
  23. infrastructure and revise the services we currently offer.
  24. The goal of the project is to make the infrastructure more
  25. coherent, with less dependencies, and with a separation of
  26. services that make it easier for volunteers to manage and
  27. help the organisation manage individual services in the long
  28. term.</p>
  29. <h2>Who we're looking for</h2>
  30. <p>We're looking for a senior system administrator or systems
  31. architect that can work in close coordination with our
  32. existing system administrators, staff and volunteers, to
  33. support our migration project through all of its stages,
  34. starting with the archaeological challenge of creating a high
  35. level overview of our services and their dependencies, and
  36. ending with the migration of our core services. Key skills
  37. will include technical documentation, virtualization
  38. environments, MTAs (Postfix), database servers and web
  39. services.</p>
  40. <h2>What we need to do</h2>
  41. <p>The person we're looking with will be tasked with the
  42. following. Please note that the first steps are more detailed
  43. than the latter steps, and we'll work together to
  44. continuously revise this plan as we go. All of this will also
  45. involve coordination with others, and a lot of information,
  46. especially for the first parts, can be gotten from existing
  47. documentation or from other system administrators.</p>
  48. <ol>
  49. <li>Create a high level service documentation, with a focus
  50. on (for each service):
  51. <ol>
  52. <li>Authentication mechanisms</li>
  53. <li>Code base (custom work, patches, or off the shelf
  54. components)</li>
  55. <li>Interdependencies with other services</li>
  56. <li>Physical / virtual infrastructure location</li>
  57. <li>Usage (estimate usage from logs etc, as well as a
  58. brief synopsis of who the main users are:
  59. external, internal, etc)</li>
  60. </ol></li>
  61. <li>Additional documentation that may be needed for
  62. specific services (such as mail), the nature of which will
  63. need to be discussed and determined at a later time, when
  64. the first high level overview is complete.</li>
  65. <li>Analyse the current services and propose a new
  66. architecture, focusing on the services and the dependencies
  67. between them.</li>
  68. <li>Provide a migration plan that detail the steps needed
  69. to be taken in order to successfully migrate our existing
  70. services to the new architecture and infrastructure.</li>
  71. <li>Migrate, and support the migration, of core services to
  72. it, including shutting down and removing old services in an
  73. orderly fashion.</li>
  74. </ol>
  75. <h2>Location and travel</h2>
  76. <p>The FSFE system administrators work largely remotely, and
  77. most of the work can be done from anywhere in the world. It's
  78. beneficial for communication that the person helping us is
  79. roughly located in Europe, and one or two trips may be needed
  80. to meet with other system administrators and staff.</p>
  81. <h2>More information</h2>
  82. <p>If you think that you're the right person, know someone who
  83. is, or just want more information, you're more than welcome to
  84. reach out to FSFE's executive director <a href="/about/oberg/">
  85. Jonas Öberg</a>, preferrably by email to
  86. <a href="mailto:jonas@fsfe.org">jonas@fsfe.org</a>.
  87. </p>
  88. </body>
  89. <sidebar promo="about-fsfe"></sidebar>
  90. <tags>
  91. <tag>front-page</tag>
  92. </tags>
  93. </html>