OnApp CDN requirements

Hardware and marketplace specs

OnApp CDN has modest hardware requirements for the controller, edge and storage servers. In addition, there a few things you should note if you plan to submit edge servers to the OnApp CDN Federation marketplace.

Hardware requirements

To run your own PoP you'll need one controller server, at least one edge server (hypervisor) and storage (SAN, or local storage in your edge server). OnApp Cloud customers can use existing controller/hypervisor/storage hardware in most cases. Alternatively, you can build a CDN purely from our online marketplace, which just requires a controller server - all PoPs are sourced from the marketplace.

Please note that you cannot use OnApp CDN with the free version of OnApp Cloud: you need a full license. 

  • OnApp Controller server

  • > Dual or Quad Core 2Ghz+ CPU
  • > 8GB+ RAM
  • > 100GB RAID 1
  • > 1x Gbit NIC (2 recommended for redundancy)

  • Edge servers

  • > Quad core 2GHz+
  • > 8GB+ RAM
  • > 30GB disk space (for the OS)
  • > Separate disk for local storage (SSD recommended)
  • > 2x Gbit NICs

  • Storage

  • > Any block storage (SSDs optional, but recommended
       for maximum IO performance)

CDN marketplace requirements

To sell CDN bandwidth through our online marketplace, you must first submit your PoP (edge server) for assessment. All PoPs are assessed before they are accepted into the marketplace, so we can ensure effective CDN performance for providers and end users. The assessment process includes: 

Benchmarking

We benchmark your PoP via SSH. It must meet these minimum requirements:

  • 2 or more edge servers (for redundancy)
  • 8GB RAM
  • 100GB disk space
  • 10,000,000 bytes/second (read)
  • 200 files/second (read)
  • 1 MB/second download speed
  • Max marketplace price of $0.05/GB (EU/US) or $0.20/GB (rest of world)

Location/existing coverage

Next we consider your PoP's physical location. Our aim is to ensure broad CDN coverage while preventing saturation of edge servers in a given location.

  • For example, a PoP in a new location is likely to be accepted as long as it passes the benchmark process.
  • In a location with many existing PoPs, your server may not be accepted unless it has unusually good performance characteristics. 

Benchmark + location  = decision!

If your PoP is accepted, it is available immediately on the marketplace. 

  • If your PoP is not accepted for performance reasons, we'll raise a ticket for resolution with you, and keep it in view for reassessment in the future.
  • If location issues prevented your PoP being accepted, we'll keep in view for reassessment in the future.