Stingray Content Delivery Cloud
Contents
1. Navigate to Catalogs gt Locations in the UI figure 1 2 Provide a Name for the location and click Add Location figure 2 3 The settings page for the created monitor is now loaded Define the location with one of the radio button options figure 3 4 Click Update Location to save the settings figure 3 figure 1 ft Home e meeen CU Catalogs Diagnose Activity System Catalogs Locations GLB Services Rules Java Aptimizer Monitors figure 2 Tech Tip Create new GLB Location To ensure Traffic Manager sends the request to the Name ongin closest location available an accurate location must Location be configured figure 3 Name origin Position D No position Select a country Specify latitude longitude coordinates Latitude 4577 Longitude 119 52 Choose location on map Update Location Configure GLB Service Now that the GLB Service has been created some additional settings need to be configured Step 1 In the Basic Settings section Next to Enabled Select the Yes radio button and click Update Step 2 The GLB Service now needs to know what IP addresses and monitors to use for each site click on Locations and Monitoring 12 OJoyent Y w Basic Settings The basic settings specify the domains used by this GLB service Name Example GLB Service J be a list of Fully Qualified Domain Names that you ike to balance globally Responses from th2. Site Monitors To ensure that traffic is only directed to the sites that are available the GLB service uses Stingray Traffic Manager s monitoring functionality N O OF ff WB DN To create site monitors Navigate to Catalogs gt Monitors in the Ul Provide a Name for the monitor Select the monitor type Select Pool GLB for the scope Provide the hostname or IP address and port for the location Click Create Monitor Repeat the steps for each site configured to respond to client requests In this example both the origin and edge sites will serve client requests Create new monitor Name Origini example com The internal monitor implementation of this monitor type Ping monitor TCP Connect monitor HTTP monitor TCP transaction monitor External program monitor SIP monitor RTSP monitor A monitor can either monitor each node in the pool separately and disable an individual node if it fails or it can monitor a specific machine and disable the entire pool if that machine fails GLB location monitors must monitor a specific machine scope Node Monitor each node in the pool separately Pool GLB Monitor a specified machine IP or hostname to monitor origin example com 80 Create Monitor 11 OJoyent Create GLB Locations GLB locations are used by Global Load Balancing Services to identify where the services are that they are load balancing across To create a GLB Location 1
3. in local Content Cache and to deliver the response directly If the resource is not available locally or is dynamic the edge Traffic Manager will request the data from the origin site and store any objects for subsequent requests Increase the performance of more than just static content and provide users with a consistent and reliable yet personalized experience for their applications OJoyent Stingray Traffic Manager A Flexible Solution Stingray Traffic Manager is advanced layer 7 ADC available as a software install on a Joyent Private Cloud deployment or virtual appliance in the Joyent Public Cloud This flexibility ensures that the content delivery solution is not compromised as it can be deployed and torn down quickly and easily The flexibility of Stingray software enables you to quickly deploy on the platform and location that best fits your needs With Stingray you can provision unlimited sites across all supported platforms Support multiple origins for performance or availability AND Provision Stingray at the edge based upon user distribution and demand Pay for what you use and with Traffic Manager s auto scaling and dynamically provision edge locations or origin application servers Data Center OJoyent Deployment Tasks This guide assumes an understanding into the basic concepts of configuring and working with Stingray Traffic Manager DNS and Cache Headers for deploying a content delivery cloud on Joyent inf
4. to respond to the users DNS query for www example com with the address of the site the will respond to the request When a service is hosted in multiple locations each instance of the service will be available from a different IP address However an end user will use a single domain name to access the service Stingray manipulates the DNS resolution of this domain name to control how each user is directed to a location It monitors the performance and availability of each location to inform the load balancing decisions it makes OJoyent Stingray works with a standard round robin DNS configuration The DNS servers are configured to return the IP addresses of all of the locations hosting a service Stingray operates as a proxy in front of DNS servers and rewrites the round robin DNS responses ensuring that the client is directed to the single most appropriate location The IP address for each location that will serve traffic should be added as an A Record for the DNS name of the service for global load balancing This deployment is for htto Avww example com but to ensure functionality for the people who don t use www i e htto example com included is example com This could also be achieved with DNS redirection CNAME records Deployment with Joyent Public Cloud This section assumes the user has established an account with the Joyent Public Cloud and is able to provision virtual machines Create the Stingray ins
5. to the web servers A maximum of one request per second will be forwarded the remainder will continue to be served from the cache This prevents bursts of traffic to your web servers when an item expires from the cache Setting this value to o will stop the traffic manager updating the cache before it expires webcache refresh_time 2 seconds You can see what pages are in the cache on the Activity gt Content Cache page a View cache contents Controls for the global cache size can be found on the System gt Global Settings page gt Modify global cache size Caching Details What can be cached By Default not all web content can be cached Stingray Traffic Manager conforms to the caching recommendations of RFC 2616 which describe how web browsers and server can specify cache behavior However if an application is misconfigured and does not provide the correct cache control information then a TrafficScript or RuleBuilder can be 10 OJoyent used to override default caching logic Client and Server HTTP Cache Control headers can also make requests responses not cacheable Applications can use expires header to control how long to cache an object Objects can use the vary header to control which requests can use a cached copy This allows different versions of objects to be cached for different users Only HTTP GET and HEAD requests are cacheable Objects that use HTTP basic authentication are not cacheable Create
6. with or without a distribution network Create a Virtual server for the application HTTP Port 80 and configure the actual servers as the load balanced pool members OJoyent Please refer to Stingray Documentation and Community for application specific configuration and performance optimizations for each virtual server configuration DNS Virtual Servers Each site providing global load balancing is configured with a DNS UDP 58 Virtual server to use the real DNS servers hosting the example com zone as the pool nodes Traffic IP Groups Virtual Servers Pools Config Summary Configuration Summary Unfold All Fold All This is a summary of your current configuration Each row shows the logical associations between traffic management objects The highlighted column shows the current sort order mames ome ree ee nsi example com 53 ns2 example com 53 Origini App app 1 example com 80 app2 example com 80 Traffic IP Groups Virtual Servers Pools Config Summary Configuration Summary Unfold All Fold All This is a summary of your current configuration Each row shows the logical associations between traffic management objects The highlighted column shows the current sort order Ea Virtual Servers V Rules v ns1 example com 53 ns2 example com 53 Example com WWW i Origin2 App app3 example com 80 ORIGIN Servers app4 example com 80 80 i Configure Edge Virtual Servers Each edge site will have a virtual serve
7. B Service Load Balancing settings control how traffic is distributed between locations Defines the global load balancing algorithm to be used algorithm Load Geographic Adaptive Round Robin Weighted Random Active Passive Apply Changes Apply GLB Service The final step in the configurations is to apply GLB Services configuration to the DNS Virtual Server 1 Navigate to the GLB Services setting for the DNS Virtual Server Services gt VIRTUAL SERVER NAME HERE gt GLB Services 2 Select the GLB Service name previously created from the drop down list 3 Click Add Service to apply and save your changes 1 Services Q Catalogs Diagnose Activity System ards raffic IP Groups Virtual Servers gt Example com DNS Your configuration has been updated GLB Services GLB Services associated with this Virtual Server will be used modify DNS responses A records that have matching GLB Services will be processed by them Where there is more than one matching GLB Service the most specific match will be used e Pools Config Summary No GLB Services have been associated with this Virtual Server E vice 3 Ee Manage GLB Services in catalog 2 OJoyent Conclusion Riverbed Stingray Content Delivery Cloud offers an application owner flexibility and control of content delivery It can offer significant improvements in end user experience in application environmen
8. OJoyent stingray Content Delivery Cloud Executive Summary The Riverbed Stingray Content Delivery Cloud CDC is a fast and efficient application delivery platform for end users However unlike a CDN which leverages a global network of servers to deliver content for all CDN customers the Content Delivery Cloud utilizes Joyent public or private infrastructure to provide the points of presence that offer a private CDN like experience for the delivery of a company s content Stingray enables these services without the need for large initial capital investment or a complex infrastructure Typical deployments will utilize Stingray Traffic Managers auto scaling content caching bandwidth management performance monitoring and optimization features Additional functionality such as Stingray Application Firewall for deeper application level threat identification and mitigation and Stingray Aptimizer for user content optimization will help enhance the performance and security of the application OJoyent Introducing the Riverbed Stingray Content Delivery Cloud The Riverbed Stingray Content Delivery Cloud CDC is a fast and efficient application delivery platform for end users However unlike a CDN which leverages a global network of servers to deliver content for all CDN customers the Content Delivery Cloud utilizes Joyent public or private infrastructure to provide the points of presence that offer a private CDN like experienc
9. Origin Sites origini example com 80 Edge default origin2 example com 80 80 Tech Tip Although not required consider configuring the origin pools to use IP persistence to ensure all requests for the session go back to the same origin location Configure Edge Caching The key difference between the edge and origin is not just where the content is coming from but the ability to serve the requests from local cache OJoyent This allows Stingray to store objects and when another client requests the object Stingray will send the content directly rather than forwarding the request to the origin site To enable content caching 1 Navigate to the edge virtual server settings then content caching 2 Select the Yes radio button 3 Click update at the end of the page q Virtual Sero D a Web pages generated by your web servers can be cached to speed up your services amp Caching settings These settings control what is cached by this virtual server If set to Yes the traffico she web server responses en SS Maximum time period to cache web pages for 2 webcache time 600 seconds Time period to cache error pages for webcache errorpage_time 30 seconds The Cache Control header to add to every cached HTTP response zo cacke OF max age 600 for example webcache control_out If a cached page is about to expire within this time the traffic manager will start to forward some new requests on
10. e back end DNS servers for queries not match this list will be forwarded to the client unmodified Note may be a wild card yomains Domains Remove www example com E example com F Add new domain to the list Edit load balance clients and how they are monitored This service can route traffic to the following locations origin2 edgel edge2 edge3 edge4 origini V Load Balancing Edit Load Balancing settings control how traffic is distributed between locations Load balancing algorithm in use Adaptive Geo Effect 50 Configure GLB Locations and Monitoring The Locations and Monitoring page allows you to add and remove pre defined locations to your service The Add Location section allows you to add new locations and each added location contains a link to remove it The GLB Service created in the previous step will contain the locations selected when the service was created but the configuration is not complete Each location will should be configured with its corresponding IP address and Site Monitor previously created To complete the locations configuration complete the following steps for each site or location used 1 In the Local IPs field enter the corresponding Tech Tip IP address for the location The Local IPs value is one of the e In this example 10 2 0 2 IP addresses used in the DNS 2 Under Add new monitor to the list select Cran DEN E tor aaa the site monitor we previo
11. e for the delivery of a company s content Stingray enables these services without the need for large initial capital investment or a complex infrastructure Typical deployments will utilize Stingray Traffic Managers auto scaling content caching bandwidth management performance monitoring and optimization features Additional functionality such as Stingray Application Firewall for deeper application level threat identification and mitigation and Stingray Aptimizer for user content optimization will helo enhance the performance and security of the application How a Stingray Content Delivery Cloud Works Extending a deployment by provisioning additional traffic managers closer to users accelerates performance Stingray Traffic Manager can be used to deliver your entire application including dynamic static and streaming content using a global network of Stingray Traffic Managers Stingray proxies user requests to the application connections to the origin are monitored and optimized by Traffic Manager With In minutes extend Stingray functionality to existin Global Load balancing users gray y g are routed to the location EEE closest to them If any Provision edge sites when where and as needed for monitor detects location is user performance too busy or unavailable Stingray will automatically send the request to the next best location Requests are examined by Traffic Manager to determine if the object is available
12. onfiguration High CPU 1 75 ah 1 059 Dwtacenmter Mermi y 2 Standard 1 75 FE 0 988 Standard 1 38 RAI YCPU and Surstng S GB Dai Hourly Est Monthly Standard 3 75 a 1 052 0 988 721 24 DA a is gt GB RA VCPU eng Cursing 123 GB Das Change Configuration High CPU 7 Baai 1 440 7 4 urs 4 Name your instance Stamdard 7 5 Ths is optiona 7 ae 1 172 tandard 7 5 GB RAN 2 vCPUs and Bursting 730 GB Disi ph ein 8 OA RANE PUS and turs 1377 GE 4 1 512 Connecting to Stingray 1 Wait for the status of the Stingray instance to change to running then click on the machine name 2 Two IP addresses are displayed for the machine The first IP address is public 3 Click on the Credentials link to display the account names and passwords for access 4 Open a browser to httos oubliclPaddress 9090 The Stingray login screen is displayed 5 Enter stingray in the Username field and the password displayed for the stingray user from step 2 in the Password field Configure Origin Virtual Servers In this deployment the original application is configured in an active active configuration across two data centers Each origin site will have Stingray origin1 and origin2 are configured with an application in this example HTTP and DNS virtual server to use the actual application servers local to each Traffic Manager as the pool nodes HTTP Virtual Servers Each origin Stingray is configured as it would be
13. r to deliver the application and a virtual server to deliver GLB managed DNS responses to the users With each edge Stingray deployment the virtual servers created are similar to the virtual servers created at the origin sites with the exception of the application HTTP virtual server The HTTP virtual server at the edge is configured as to use the Traffic Managers OJoyent at the origin as the pool nodes Utilizing Traffic Manager s functionality at the origin enables optimal performance and control for the application delivery HTTP Virtual Servers The virtual server at each edge site is configured to use the origin sites as the pool nodes DNS Virtual Servers Each site providing global load balancing is configured to use the real DNS servers hosting the example com zone as the pool nodes Tech Tip The Edge DNS Virtual Servers are configured the same as the origin sites For this deployment the DNS virtual servers at both the edge and origin are configured the same and use the same application nodes Traffic IP Groups Virtual Servers Pools Config Summary Configuration Summary Unfold All Fold All This is a summary of your current configuration Each row shows the logical associations between traffic management objects The highlighted column shows the current sort order Virtual Servers V v Example com DNS Use Example com nsi example com 53 53 default DNS Servers ns2 example com 53 Example com WWW
14. rastructure For complete information and configuration steps please refer to the User Manual e Configure DNS Zones e Stingray Deployment Tasks e Deployment with Joyent e Create Virtual Servers e HTTP at the Origin e HITP at the Edge e DNS for Origin and Edge e Configure Edge Cache e Create Site Monitors OJoyent e Create GLB Locations e Create GLB Service e Configure GLB Details Architecture Considerations e Content caching requires Stingray 1000L or above GLB requires Stingray 2000L or above e All sites must have content caching enabled for optimal performance it is recommended that all sites perform GLB address resolution e For a deployment with minimum redundancy GLB functionality can be deployed in two sites and additional sites can be deployed with just content caching Reference Architecture origini example com 10 1 0 1 Data Center 1 origin2 example com 10 2 0 2 DataCenter 2 edget example com 472 16 1 1 Joyent Bay Area edge2 example com 172 16 2 1 Joyent Las Vegas edge3 example com 172 16 3 1 Joyent Virginia edge4 example com 172 16 4 1 Joyent Amsterdam app1 example com 10 1 100 1 Data Center 1 app2 example com 40 1 100 2 Data Center 1 app3 example com 10 2 100 1 Data Center 2 app4 example com 10 2 100 2 Data Center 2 Configure DNS Zones To send the users to the best location Stingray Global Load Balancing will used
15. t where there is rapid business growth or change It can reduce management overhead and CAPEX commitments while providing the scalability to meet business requirements About Joyent Joyent is the high performance cloud infrastructure and data analytics company The Joyent Cloud is built from the ground up to meet the requirements of today s demanding real time web and mobile applications The Joyent Manta Storage Service is the first compute on storage innovation that eliminates data movement and enables inexpensive lightning fast big data analysis in place transforming the economics and utility of object storage and real time big data For more information visit htto Avww joyent com About Riverbed Riverbed delivers performance for the globally connected enterprise With Riverbed enterprises can successfully and intelligently implement strategic initiatives such as virtualization consolidation cloud computing and disaster recovery without fear of compromising performance By giving enterprises the platform they need to understand optimize and consolidate their IT Riverbed helps enterprises to build a fast fluid and dynamic IT architecture that aligns with the business needs of the organization Additional information about Riverbed NASDAQ RVBD is available at www riverbed com
16. tance 1 Sign on to the Joyent Cloud portal at httos my joyentcloud com The console displays a summary of the virtual machines created in the Joyent Cloud 2 Click Add a machine 3 Select the data center where the Stingray instance is to be deployed As of May 2013 the available data center locations are 1 US West 1 San Francisco CA 2 US SW 1 Las Vegas NV 3 US East 1 Ashburn VA 4 EU AMS 1 Amsterdam 4 In the Select an image section enter stm in the search field Then select the image with the desired bandwidth and features OJoyent C f amp https myjoyentcioud com n J O Y e n i Dashboard Compute Storage My Account Compute Create Instance US Sw 4 bal All ol str trn 1000H 4 Stmpray Traffic Waneger 9 2 0 1000H image version 1 11 stm 1000M Stingray Traffic Nanaper 9 2 0 1000W image version 111 1 H stm 1000M SAF Sungay Traffic Waneser image version 131 1 e a lt gt Aer m X SAF stm 2000L Stingray Treftc Manager 9 2 20000 image version 13 11 Create the Stingray instance continued 5 Select the option with the desired combination of RAM disk space and CPU Enter a name for the instance and click Create instance 6 The virtual machine just created Is displayed on the console with a status of provisioning OJoyent oyent Dashboard Jompute Storage My Account ompoute Create Instance Package Types Selected c
17. usly created for that aalemaine in ine clarralle site or address configured e In this example Origin2 example com 13 OJoyent Y origin2 Specify the settings for this location Draining Yes No Local IPs There are no local IPs currently defined for this location Add new IP to the list 10 2 0 2 Monitors There are no monitors currently defined for this location Add new monitor to the list Origin2 example com v Manage monitors in catalog Update x Remove this location Directing the Traffic Configure GLB Algorithm By default the GLB Service created with the Adaptive algorithm with a 50 effect on the clients geo location Several load balancing methods are available allowing you to direct your traffic accordingly To distribute traffic based solely on the geographic location of each client you should change the GLB service configuration to use the Geographic algorithm 1 To Change the GLB algorithm l Tech Tip Navigate to the load balancing setting for the TE Using the geographic algorithm GLB service eI GLB Services gt SERVICE NAME HERE gt Load Balancing seems to be the best choice but in a situation where the load on a particular site results in lower user 2 Select the Geographic radio button ae performance the Adaptive with 3 Click Update to save your changes l Geo Effect could provide the best user experience 14 OJoyent GLB Service StingrayEdge GL
Download Pdf Manuals
Related Search