Page tree
Skip to end of metadata
Go to start of metadata

OnApp CDN is a software product that works with OnApp Cloud v2.3 and later. If you enable CDN for your end users, they can get access to a network of global edge servers (yours, and/or those provided by other cloud hosts) and use that network to deliver web content more quickly and reliably to visitors all over the world. Your CDN is managed alongside your cloud using your OnApp Control Panel. See http://www.onapp.com/cdn for more information.

OnApp provides the following CDN types:

  • HTTP Pull
  • HTP Push
  • Live Streaming
  • On Demand Streaming

Push

HTTP Push method is similar to secondary server:  the user uploads content to CDN and links to it, so the content is physically stored at CDN storage servers.

Pull  

With an HTTP Pull CDN, the website owner stores content on their server and rewrites URLs to include a subdomain. Then, when the specific content is requested, it is pulled to the CDN network from the host and delivered to the closest point to the consumer who requested that content (the content is cached on edge server).

Streaming

There are two supported streaming types in the OnApp CDN – live streaming and on demand streaming. Only mp4 and flv files are currently supported by VoD streaming.

Live streaming

Live streaming CDN allows to deliver the content to end users in a live broadcast mode. When using a live streaming CDN service, end user receive media the same time like a traditional broadcasting.

Video On Demand streaming

Video On Demand streaming CDN allows to deliver video on request and makes it repeatedly accessed. Consumers can control content and are able to fast forward or rewind it the same as live streaming.


To utilize CDN streaming service, you have to deploy CDN streaming Edge Server.

Setting up OnApp CDN includes:

  • Enabling CDN for your cloud in the OnApp customer dashboard (contact OnApp Support if you don’t have dashboard access)
  • Running CDN Setup wizard in your OnApp Control Panel
  • Setting up storage servers
  • Setting up edge servers
  • Adding CDN edge groups and assigning them to buckets
  • Creating CDN resources (when you create a CDN resource, CDN is enabled automatically in the OnApp)
  • Assigning the bucket to a user, and setting their permissions. 

Storage servers store web content to be distributed over the Content Delivery Network. The content is then cached by edge servers and delivered to consumers.

Edge servers cache web content and deliver it to website visitors. They are deployed on compute resources and managed just like VSs. You can use edge servers to sell CDN bandwidth to your end users, and/or submit the edge server to the OnApp CDN marketplace and sell your bandwidth to other hosts. You can create as many edge servers as you need and place them on different compute resources in different geographical locations, and easily broaden your CDN by combining your own edge servers with other locations on the CDN marketplace. You can even build a CDN solely with marketplace resources. For details, refer to the Edge servers chapter.

Edge groups are groups of edge servers – your own, and those you subscribe to from the CDN marketplace. They are usually grouped by location, so they represent a pool of servers for a given geographical area.

Edge groups are assigned to buckets to set the prices for the bandwidth that your end users consume. You can assign several groups to one bucket at a time, and establish different geographical zones with different pricing. The bandwidth pricing of the bucket is the price for CDN bandwidth sold to your end users.

CDN resources are specific servers with content an end user wants to distribute via the CDN. CDN resources are assigned to edge groups, which determines the list of servers taking part in distributing/caching of their data.


PLEASE NOTE: Starting from the OnApp Cloud v3.0, CDN is enabled automatically after adding the first DNS record or CDN resource.

  • No labels