Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How to succeed on migration projects


Published on

Lessons learned on migration projects.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

How to succeed on migration projects

  1. 1. I want to break free Migration to Free Software. Uruguayan Navy Mail Services case. Enrique M. Verdes UYLUG
  2. 2. whoami <ul><li>Senior specialist, Systems & IT Dpt. At CONATEL S.A.
  3. 3. Two migrations at CACSON Credit Union
  4. 4. Mail services migration project at Uruguay Navy.
  5. 5. ORT Uruguay University professor since 2002. </li></ul>
  6. 6. About what we will be talking The case Lets review the project and it's characteristics The tips How to have success in your migration project.
  7. 7. Who made this project succeed <ul><li>Andrés Tarallo, my partner, provided specific experience working with mail services.
  8. 8. Cn. Gonzalo Montaña, Ltn. Gerardo Estellano & Alf. Benjamín Regueiro, from Navy N6 Dpt.
  9. 9. Postfix community. </li></ul>
  10. 10. The case Because of obsolescense of hardware a new server was needed. That meant a migration to a new version of MS Windows and Exchange server. Budget constraints made this unviable, so this was the opportunity to move to free software. I'd want to point that the navy was already using free software.
  11. 11. What should be migrated <ul><li>Because of lack of reliability a multiserver configuration was used.
  12. 12. This was managed by Exchange transparently and we needed to emulate this. </li></ul>
  13. 13. Our solution <ul><li>The components we choose: </li><ul><li>OpenLDAP for the users data backend.
  14. 14. Postfix as the SMTP server, for security, maturity and ease of management.
  15. 15. Cyrus for IMAP and POP access and user authentication using SASL.
  16. 16. Some homemade scripts to automate tasks. </li></ul></ul>
  17. 17. The configuration <ul><li>The key component of the Postfix configuration are: </li><ul><li>The virtual lookup tables.
  18. 18. The transport table. </li></ul><li>We used the vaddress attribute of the ldap open-xchange.schema to route mails to the apropiate server.
  19. 19. With the mailEnabled attribute set to no the mail was routed to the Exchange Server. By this we move the accounts little by little.
  20. 20. LDAP is replicated in each server running Postfix. </li></ul>
  21. 21. As dicas!! From this and other experiences I'd like to give some tips and tools to help you who want to be free.
  22. 22. What we learned: UAF <ul><li>There are three factor to take into account in any migration project. </li><ul><li>The U sers (all of them).
  23. 23. The legacy A pplications.
  24. 24. The data storage F ormat. </li></ul><li>If you miss any one of them, you will have problems.
  25. 25. Software engineering background helps a lot!! </li></ul>
  26. 26. Software Engineering Life Cycle Analisys Requirements Capture Design Implementation Validation Deployment & Maintenance Retirement
  27. 27. How to handle UAF <ul><li>Users make the 80% of the success. </li><ul><li>You need commitment from the management. But not political decisions messing up.
  28. 28. Users ALLWAYS oppose changes by default.
  29. 29. Identify all users and how they use the system. If necesary write use-cases. </li></ul><li>Carefull planning. </li><ul><li>Big bang seldom works. </li></ul><li>Store your data in standar formats. </li><ul><li>Proprietary software don't like when people want to get out. </li></ul></ul>
  30. 30. This may help you.
  31. 31. An example from our case <ul><li>An application to track fishing ships had trouble getting mail from the Cyrus-Imap server when the system was put in production. This was a BIG problem.
  32. 32. It's virtually impossible to extract user information from Exchange. </li></ul>
  33. 33. Remember <ul><li>People use computers to get things done, so, software is for people, not people for software. </li></ul>
  34. 34. ... and at the end... any questions?
  35. 35. Tank you very much Muito obrigado Fica de olho em
  36. 36. Copyright Enrique M. Verdes – 2008 Esta obra está bajo una licencia Reconocimiento-No comercial-Compartir bajo la misma licencia 3.0 Unported de Creative Commons. Para ver una copia de esta licencia, visite o envie una carta a Creative Commons, 171 Second Street, Suite 300, San Francisco, California 94105, USA.