Types of CDN Deployment
There are two main ways to get up and running with OnApp CDN. You can build a CDN using your own physical hardware, and add locations from our global CDN marketplace; or you can build a CDN entirely from marketplace resources.
If you are an existing OnApp Cloud user and have a Control Panel server installed, you do not have to perform any server setup procedures. Just proceed with CDN Activation & Configuration Process steps.
CDN with Marketplace Resources Only
This is the simplest way to configure OnApp CDN, since it involves minimal hardware.
In essence you're building a virtual CDN. You don't host your own physical edge servers: instead, you subscribe to locations on the OnApp CDN marketplace, purchase CDN bandwidth from other providers, and resell it to your customers.
Obviously, without your own edge servers you won't be able to provide local edge resources to your customers, or sell edge server resources on the marketplace.
Basic hardware required:
1x Control Panel server | This hosts the OnApp Control Panel, where you manage your marketplace resources, users, billing and so on. |
Own Edge Servers with Marketplace Resources
To provision your own local edge server resources you will need to create a small OnApp Cloud. Existing OnApp Cloud users can deploy edge servers in their existing cloud.
The edge server is a virtual appliance that is deployed and managed in much the same way as a virtual machine. They are hosted on compure resource(s) and will need their own primary storage volume(s).
Basic hardware required:
1x Control Panel server | This hosts the OnApp Control Panel, where you manage your local edge servers, marketplace resources, users, billing and so on. |
1x compute resource server | This hosts the edge server virtual appliance and provides its physical CPU and storage resources. Any edge servers you deploy in your cloud can be used by any of your Control Panel Servers. |