PageRenderTime 30ms CodeModel.GetById 38ms RepoModel.GetById 0ms app.codeStats 0ms

/oldblog/migration/input/Execution-architecture-design.md

https://gitlab.com/colmsjo/develvm
Markdown | 86 lines | 52 code | 34 blank | 0 comment | 0 complexity | 06aeab9b021fdd773f8db1d72cb6af65 MD5 | raw file
Possible License(s): Apache-2.0, AGPL-1.0, BSD-3-Clause, CC-BY-3.0, MIT 
    

  1. [[wiki]] > [[Technical Architecture]] > [[Execution Architecture]]
    2. 

  2. 

  3. h1. Execution Architecture Design
    4. 

  4. 

  5. h2. PHP & MySQL Execution Architecture Design
    6. 

  6. 

  7. h3. Background
    8. 

  8. 

  9. Links:
    10. 

  10. * MySQL cluster: http://www.google.se/url?sa=t&rct=j&q=mysql%20proxies%20load%20balancinf%2Bpdf&source=web&cd=2&ved=0CDYQFjAB&url=http%3A%2F%2Fdownloads.mysql.com%2Fforge%2Fslides%2FMySQL-Proxy.pdf&ei=JkXjTvOJIqTR4QSjoZWUBQ&usg=AFQjCNEbFSNCWhdhdj70i3ZFbG60cD949A
    11. 

  11. * http://wiki.scalr.net/Tutorials/Setup_MySQL_proxy?highlight=mysql+proxy
    12. 

  12. 

  13. A load balancing cluster with failover functionality will be used. Initial thoughts on desgin:
    14. 

  14. * one laod balancer (likely ngix), 
    15. 

  15. * two apache server - need HA client in order to mange failover between the two MySQL proxies
    16. 

  16. * two MySQL server, one master and one slave
    17. 

  17. * Two load balancing MySQL proxies will be used to manage that writes are written to the master and reads distributed to all servers
    18. 

  18. 

  19. Scalr's pre-configured images are used. 
    20. 

    21. 

  21. Ubuntu 10.04 will be used for both application servers and database servers. The main reason is that ubuntu has a newer PHP version than CentOS 5,5.
    22. 

  22. 

  23. The MySQL database server will run on failover cluster using MySQL master-slave synchronization. 
    24. 

  24. 

  25. The laod balancer will initially run a micro image while the database and application server runs on small images.
    26. 

  26. 

  27. Application and database server should have minimum 2 instances in the scaling options. Maximum should also be set to two instances (and scaling disabled).
    28. 

  28. 

  29. The server will consist of:
    30. 

  30. * Load balancer: lb-nginx-centos-ebs ubuntu 10.04l, x32
    31. 

  31. * Applications servers: app-apache-ubuntu-ebs Ubuntu 10.04, x32
    32. 

  32. * Database servers: percona-ubuntu1004 Ubuntu 10.04, x32
    33. 

  33. 

  34. 

  35. Platform: Amazon EC2
    36. 

  36. Location: AWS /EU West 1 (Ireland)
    37. 

  37. 

  38. 

  39. h3. Application server
    40. 

  40. 

  41. The OS for the application server is Ubuntu 10.04. PHP version is 5.3.X.
    42. 

  42. 

  43. In addition to the standard modules should the following modules should be installed:
    44. 

  44. * php-pecl-apc - PHP opcache
    45. 

  45. * Postfix (for sending mail)
    46. 

  46. * Subversion client
    47. 

  47. * ec2-api-tools
    48. 

  48. 

  49. Consider the folowing for system Admin:
    50. 

  50. * webmin (not installed yet)
    51. 

  51. * phpMyAdmin (not installed yet)
    52. 

  52. 

  53. 

  54. h4. SSL
    55. 

  55. 

  56. All communication with vTiger and the portal should be encrypted with SSL. It should not be possible to connect using standard http. Port 80 should be closed in the firewall and apache should not listen on port 80.
    57. 

  57. 

  58. A SSL certificate from RapidSSL is available here. This is a wildcard certificate that can be used for all subdomains of gizurcloud.com
    59. 

  59. http://s2.gizur.com:81/attachments/download/64/gizurcloud.com_RapidSSL_Wildcard_Order.pdf
    60. 

  60. 

  61. Preparations (needed for the vTifger portal to work):
    62. 

  62. <pre>
    63. 

  63. sudo apt-get install php5-curl
    64. 

  64. service apache2 restart
    65. 

  65. </pre>
    66. 

  66. 

  67. SSL is configured in scalr when setting up the virtual host.
    68. 

  68. 

  69. h3. Database server
    70. 

  70. 

  71. Standard MySQL 5 is used. The scalr MySQL role which has a master/slave setup is used.
    72. 

  72. 

  73. 

  74. h3. Management Server
    75. 

  75. 

  76. The scalr ASP service will be used for the production environment. 
    77. 

  77. 

  78. Login here: https://my.scalr.net/#/dashboard
    79. 

  79. 

  80. 

  81. h4. Testing of scalr 
    82. 

  82. 

  83. Scalr is open source and it is possible to install your own scalr server. This requires that you have your own nameservers for the managed domain though.
    84. 

  84. A separate scalr test environment is usefull when doing performance testing since scalr charges based on the number of servers being managed. 
    85. 

  85. 

  86. Howto install a scalr server on ubuntu is described here: [[Installation of management server]]. Scalr supports centos but I've not been able to install all dependencies on Rackspace centos 5.6.
    87.