From Fedora Project Wiki

Line 24: Line 24:
= Network Architecture =
= Network Architecture =


Following diagram shows overall network architecture.
Following diagram shows overall network architecture. fedoraproject.org and admin.fedoraproject.org are round robin dns entries. They are populated based on geoip information. For example, for North america they get a pool of servers in North america. Each of those servers in dns is a proxy server. It accepts connections using apache. apache uses haproxy as a backend, and in turn some(but not all) services use varnish for caching. Requests are replied to from cache if varnish has it cached, otherwise it sends into a backend application server. Many of these are in the main datacenter in phx2 and some are at other sites. The application server processes the request and sends it back.
[[Image:FINArchitecture.png|border|thumb|center|650px|alt=Infrastructure Network Architecture|Infrastructure Network Architecture]]
[[Image:FINArchitecture.png|border|thumb|center|650px|alt=Infrastructure Network Architecture|Infrastructure Network Architecture]]



Revision as of 01:33, 21 September 2012


Global Presence

Fedora Infrastructure Network spans multiple continents. Datacenters are present in North America, UK and Germany. List of Datacenters goes as follows:

  1. phx2 - main Datacenter in Phoenix, AZ, USA
  2. rdu - North Carolina, USA
  3. tummy - Colorado, USA
  4. serverbeach - San Antonio, TX, USA
  5. telia - Germany
  6. osuosl - Oregon, USA
  7. bodhost - UK
  8. ibiblio - North Carolina, USA
  9. internetx - Germany
  10. colocation america - LA, USA

Network Topology

This section shows how our severs are interconnected or connected to the outside world.

Infrastructure Network Topology
Infrastructure Network Topology

Network Architecture

Following diagram shows overall network architecture. fedoraproject.org and admin.fedoraproject.org are round robin dns entries. They are populated based on geoip information. For example, for North america they get a pool of servers in North america. Each of those servers in dns is a proxy server. It accepts connections using apache. apache uses haproxy as a backend, and in turn some(but not all) services use varnish for caching. Requests are replied to from cache if varnish has it cached, otherwise it sends into a backend application server. Many of these are in the main datacenter in phx2 and some are at other sites. The application server processes the request and sends it back.

Infrastructure Network Architecture
Infrastructure Network Architecture

Front End

This is a view of our network from the outside up to the application layer.

File:Infrastructure Architecture frontend.png
Infrastructure Frontend Diagram

Proxy View

This shows whats going on in the proxies.

File:Infrastructure Architecture proxy.png
Infrastructure Proxy Server Diagram

Application Layer

This is a generic view of how our applications work. Each application may have its own design, but the premise is the same.

File:Infrastructure Architecture applicationLayer.png
Infrastructure Application Layer Diagram

Contributing

One can contribute to Fedora Infrastructure in several ways. If you are looking to improve the quality of content in this page then have a look at GettingStarted. And if you are wondering why no server in a great country like yours and want to make donations of hardware please visit our donations and sponsors page.