CloudOYE CDN USER MANUAL

Transcription

1

2 CloudOYE CDN USER MANUAL

3 Password - Based Access Logon to Enter your Username & Password In case, you have forgotten your password, click Forgot your password to request a new one.

4 INSTRUCTIONS TO CREATE CloudOYE CDN Resource

5 Once you have entered your credentials successfully, you ll get to see your dashboard. 1. Click Resources given in the left hand side panel of your dashboard

6 You ll be redirected to a screen CDN Resources

7 Click CDN Resource Wizard on the right hand side of the panel of your dashboard.

8 Now, create your CloudOYE CDN Resource in 4 easy steps TYPE SELECT PROPERTIES EDGE LOCATIONS ADVANCED SETTINGS

9 STEP1 TYPE SELECT

10 1. Select the type for creation of a new CDN resource in your control panel. 2. Click HTTP 3. Click Next

11 STEP2 CREATE PROPERTIES

12 Now, fill in: 1. CDN Hostname: Enter your domain name, i.e. the URL of your website. For e.g. www. cloudoye.net 2. Enable SSL: SSL is optional. Drag the bar to enable it, else leave it as it is. 3. Content Origin: It is by default set on PULL, as you re required to pull the data from multiple locations during CDN resource creation 4. Origins: Type in your website s IP address, if you re using more than one origin. (You site should remain the same as your domain name entered above) 5. Click Next Note: Please type the full hostname and ensure that it does not end with r.worldssl.net, otherwise SSL will be enabled automatically.

13 STEP3 Edge Locations

14 You ll be redirected to a screen Edge Groups Now, select the Global CDN checkbox.

15 1. Click Create CDN Resource. You have successfully created your CloudOYE CDN Resource.

16 How to edit the settings of your CDN Resource

17 Go back to your dashboard 1. Click Resources given in the left hand side panel of your dashboard. 2. Your Cloud CDN Resource is given in your domain name. 3. Select edit option from the drop down bar of Action button on the right hand side panel of your dashboard. 4. Now, click action icon corresponding to you domain name. 5. You ll be shown 3 options: Advanced Reporting, Edit and Delete 6. Select Edit to make the required changes in your created CDN resource

18 You will be directed to CDN Resource Properties page Now, do the required changes and click on the save button given on the right hand side panel of your dashboard.

19 How to check the advanced reporting of your CDN Resource

20 Go back to your dashboard 1. Click Resources given in the left hand side panel of your dashboard. 2. Your Cloud CDN Hosting Resource is given in your domain name. 3. Select edit option from the drop down bar of Action button on the right hand side panel of your dashboard. 4. Now, click action icon corresponding to you domain name. 5. You ll be shown 3 options: Advanced Reporting, Edit and Delete 6. Select Advanced Reporting to check advanced reporting of your CDN Resources.

21 You will be directed to Advanced Reporting page

22 Filter Your Advance Reporting Choose your Start & End Time for Advanced Reporting Click Start Time Next, choose the desired date from the calendar Boot Virtual Server You can also see & set the time according to your location time-zone Simply drag the bar Click Apply. Your status will be shown at the below

23 Filter Your Location Choose your location. Click Locations Next, choose the desired location from the list. Click Apply

24 You will get information related to bandwidth and cache utilization of selected time frame

25 How to perform website CDN integration?

26 Website CDN Integration You have the following options for CDN resource creation: Partial site integration Full site integration

27 Partial Site Integration Once CNAME is setup, edit your website HTML code. Change all the static content link to use the URL of cdn.mywebsite.com Remain the existing URL link for dynamic content which requires frequent change This can be explained with help of the following example: CDN Hostname: Your CDN hostname should be like cdn.mywebsite.com Origin: The result is as follows: On CDN - cdn.mywebsite.com/image/abc.jpg On CDN - cdn.mywebsite.com/mp3/sing.mp3 Request goes back to the origin -

28 Full Site Integration Once CNAME is setup, the origin ( is served through CDN. Set a no-cache http header at the origin on dynamic files/folders, in this case dynamic.db This can be explained with the help of following example: CDN Hostname: Origin: The result is as follows: On CDN - cdn.mywebsite.com/image/abc.jpg On CDN - cdn.mywebsite.com/mp3/sing.mp3 Request goes back to the origin -

29 How to verify if the website is on CDN

30 Please check

31 What is onapp CDN DNS redirection?

32 It is a tool to simulate real time DNS redirection result. To log on, go to :

33 How to compare CDN content with Debugger?

34 It is a tool to test if CDN edge server is returning good result. To log on, go to :

35 CDN Reporting

36 Detailed Reporting CDN helps to perform detailed reporting based on the bandwidth statistics. Select the following filters: Date and Time range CDN resources Locations

37 Advanced Reporting Advanced reporting can be performed with the HTTP Status code of CDN resource. This will show the total number of http requests for a specific period.

38 Caching Mechanism Generally, there are 3 levels of content expiry settings in an OnApp CDN solution: Origin Server Here end users may modify the cache control header at the origin server (where the content is hosted), eg Apache config or htaccess rule. CDN Resource Level - Customers may configure the CDN site's content expiry setting at CP by navigating to [ CDN Resource] -> Create/Edit CDN Resource -> Enable Advanced Settings. Cloud Owner Level - Cloud owner may configure the global content expiry time in the dashboard. The default time is 60 minutes. The maximum cache size for a file is 2GB (HTTP PULL). Anything larger than 2GB can still be served by the CDN edge server, however it would not be cached.

39 The curl request to the origin URL can be made as : Use of Curl Command [cs.yap@onappgw ~]$ curl -I HTTP/ OK Date: Thu, 26 Jun :10:17 GMT Server: Apache/ (Unix) mod_ssl/ OpenSSL/0.9.8e-fips-rhel5 mod_bwlimited/1.4 PHP/ Last-Modified: Tue, 12 Nov :18:34 GMT Accept-Ranges: bytes Content-Length: Cache-Control: max-age= , public Expires: Sat, 26 Jul :10:17 GMT Content-Type: image/png First Request to CDN url: [cs.yap@onappgw ~]$ curl -I platform.png HTTP/ OK Server: nginx Date: Thu, 26 Jun :10:47 GMT Content-Type: image/png Content-Length: Connection: keep-alive Last-Modified: Tue, 12 Nov :18:34 GMT Cache-Control: max-age= , public Expires: Sat, 26 Jul :10:47 GMT X-Edge-IP: X-Edge-Location: Amsterdam, NL X-Cache: MISS Accept-Ranges: bytes

40 Purge and Prefetch Purge Purge function can be used to clear the cache in the CDN edge server. Once the cache is cleared, when a visitor request comes in again, the CDN edge server will PULL from the origin, and get the latest up-to-date content. You can purge on file path: cdn.mywebsite.com/image/abc.jpg You can issue a Full Site Purge, where all cache files under CDN resource cdn.mywebsite.com will be cleared Prefetch With prefetch command, you can pre-populate the files from the origin to the CDN edge server to ensure that the files are ready to be cached in the CDN edge server before the visitors request for it. The prefetch is in url path format, for example: cdn.mywebsite.com/image/abc.jpg

41 For Sales Information Contact No: India US sales@cloudoye.com For Customer Support Contact No: /19 support@cloudoye.com

42 Thank You!