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.
 
 
 
 
 
 

97 lines
4.5 KiB

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