Changes between Version 2 and Version 3 of container-infrastructure


Ignore:
Timestamp:
Jun 15, 2018, 9:42:02 AM (13 months ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • container-infrastructure

    v2 v3  
    2121There are also a number of secondary goals which we hope to achieve but not at the expense of our first goal:
    2222
    23  * *Ability to scale from a few thousand users to millions of users:* this goal is the primary goal of most container based technologies, however, it only marginally applies to us. Yes, we want to be able to handle a web site that becomes explosively popular over night. However, our primary need is to handle thousands of relatively low traffic web sites rather than a single high traffic web site. This goal is still an important secondary goal so we have the ability to support the few members that are focused on growing their Internet resources into the millions.
     23 * ''Ability to scale from a few thousand users to millions of users:'' this goal is the primary goal of most container based technologies, however, it only marginally applies to us. Yes, we want to be able to handle a web site that becomes explosively popular over night. However, our primary need is to handle thousands of relatively low traffic web sites rather than a single high traffic web site. This goal is still an important secondary goal so we have the ability to support the few members that are focused on growing their Internet resources into the millions.
    2424
    25  * *Ability to instantly recover from hardware failure:* this goal is also a primary goal of most container based technologies, but does not apply well to us. It largely depends on hardware capacity that is more than double the capacity you need to run your servers. When you have access to leased hardware via Amazon, this is quite simple and affordable. When you own all of your hardware it is prohibitively expensive. This goal still remains as an important secondary goal - and the ability to manually recover from hardware failure in a matter of minutes will still be possible. However, auto fail-over will most likely not be feasible for all member services.
     25 * ''Ability to instantly recover from hardware failure:'' this goal is also a primary goal of most container based technologies, but does not apply well to us. It largely depends on hardware capacity that is more than double the capacity you need to run your servers. When you have access to leased hardware via Amazon, this is quite simple and affordable. When you own all of your hardware it is prohibitively expensive. This goal still remains as an important secondary goal - and the ability to manually recover from hardware failure in a matter of minutes will still be possible. However, auto fail-over will most likely not be feasible for all member services.
    2626
    2727== First Steps ==
     
    3737Our current infrastructure mostly uses the Domain Name System (DNS) to determine which member web sites, email etc. should be routed to which of our 75 MOSH's.
    3838
    39 To prepare for the container-based approach, we will need to change, so that the DNS system routes all members to one or serveral public facing servers, and these servers in turn route the request to the appropriate place in our network.
     39To prepare for the container-based approach, we will need to change, so that the DNS system routes all members to one or several public facing servers, and these servers in turn route the request to the appropriate place in our network.
    4040
    4141We are currently using this approach for email - all members configure there email programs to send and receive via mail.mayfirst.org - which in turn routes the request to the appropriate server.
     
    5757Network storage means that a hard disk that is mounted on one physical server can be quickly unmounted on that server and re-mounted on a different server. It is a critical component to a container-based infrastructure in general and meeting our primary goal in particular.
    5858
    59 Currently, all hard disks in our network are provided by the physical servers hosting the services.
     59Currently, all hard disks in our network are provided by the physical servers hosting the services which means moving data is a slow and resource-intensive process.
    6060
    6161We will need to invest in a dedicated server to provide file systems to our network and begin experimenting with moving our data to this new server.