DataSynapse and Amazon EC2 Technical Overview


Published on

Published in: Technology
1 Comment
1 Like
  • Very interesting ppt. The research indicated PPT only contains 30% of information; therefore the 70% valuable information comes from the presenter himself/herself. provides you a chance to record your voice with your PowerPoint presentation and upload to the website. It can share with more readers and also promote your presentation more effectively on
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • DataSynapse and Amazon EC2 Technical Overview

    1. 1. A Technical Overview Leveraging Amazon Web Services with DataSynapse GridServer
    2. 2. Overview <ul><li>On Wednesday February 11th, DataSynapse announced support for Amazon EC2 and Amazon Web Services external cloud platform </li></ul><ul><ul><li>Customers will be able to run unlimited number of DataSynapse engines in the EC2 cloud </li></ul></ul><ul><li>As part of this announcement, DataSynapse is launching a beta program for Federator 1.5 </li></ul><ul><ul><li>This new release of the Federator grid management software makes integration with external clouds seamless </li></ul></ul><ul><ul><li>Beta program members can extend there current DataSynapse environment into the Amazon EC2 cloud, free for all of 2009 </li></ul></ul><ul><li>The objective of this strategy is to accelerate the adoption of external cloud computing models for mission critical business applications and lower the operating expenses for grid computing </li></ul>
    3. 3. GridServer and AWS Technical Overview
    4. 4. <ul><li>High performance service execution </li></ul><ul><li>Modern, open and extensible </li></ul><ul><li>Multi-platform, multi-language </li></ul><ul><li>Self-managing: </li></ul><ul><ul><li>HA/Failover </li></ul></ul><ul><ul><li>Deployment and provisioning </li></ul></ul><ul><ul><li>Monitoring </li></ul></ul><ul><li>Large platform ecosystem of premier ISVs </li></ul>GridServer – Service Execution Environment Grid Clients DataSynapse Manager
    5. 5. Federator – Grid Engine Management DataSynapse Federator Federator UI <ul><li>Policy based re-distribution of resources between resource pools </li></ul><ul><li>Centralized resource management </li></ul><ul><li>Enables running additional engine pools in the Amazon EC2 cloud </li></ul>GridServer 4.2 (U16) GridServer 5 (SP2) EC2 Engines
    6. 6. Federator - Integrating with Amazon WS <ul><li>Federator 1.5 extends GridServer seamlessly onto the Amazon cloud </li></ul><ul><ul><li>Save all your Amazon configuration information </li></ul></ul><ul><ul><li>Create policies for starting / stopping cloud based engines </li></ul></ul><ul><ul><li>Create secure connections to cloud based engeines </li></ul></ul>Grid Client Federator DataSynapse Manager On Premise In the Cloud
    7. 7. Activate Amazon EC2 Account <ul><li>Create an Amazon AWS account </li></ul><ul><ul><li>Web-based sign up, with credit card </li></ul></ul><ul><li>Sign up for DataSynapse paid AMI </li></ul><ul><ul><li>Retain your Activation Key </li></ul></ul><ul><li>Gather your Amazon keys </li></ul><ul><ul><li>Access Key ID </li></ul></ul><ul><ul><li>Generate public and private keys </li></ul></ul>
    8. 8. Setting Up Federator <ul><li>Install Federator software </li></ul><ul><li>Configure Federator for your GridServer Manager </li></ul><ul><li>Define a Virtual Resource Manager </li></ul><ul><ul><li>Basic information necessary to interact with EC2 (e.g., AWS login information) </li></ul></ul><ul><li>Define a Virtual Resource Group </li></ul><ul><ul><li>More dynamic configuration data, information specified in VRG closely tied to how customers will actually use virtual nodes </li></ul></ul><ul><li>Define Policy </li></ul><ul><ul><li>Assign Virtual Resource Group to target Resource Manager </li></ul></ul>
    9. 9. Starting Up the Proxy Service <ul><li>Federator uses AWS interface to create a cloud-side proxy based on Virtual Resource Manager Settings </li></ul>On Premise On AWS <ul><li>On premise proxy, installed as a service, will initiate secure cloud connections </li></ul><ul><li>AMI (Amazon Machine Image) for the Proxy is stored in S3, DataSynapse incurs the costs of this storage, not the client </li></ul>AWS EC2 Instance AWS Interfaces Federator DataSynapse Manager AWS S3 Storage Proxy Service AMI Proxy Service Proxy Service
    10. 10. Proxy Service <ul><li>Once proxy is running, Federator instructs the GridServer Manager to establish an SSH tunnel connection to the proxy </li></ul>Federator On Premise On AWS DataSynapse Manager Secure SSH Tunnel Secure connection point between on premise and cloud based resources Proxy Service <ul><li>Proxy model enables secure connectivity between GridServer Manager on premise and Amazon EC2 based DataSynapse resources </li></ul>Proxy Service
    11. 11. OpenVPN Alternative <ul><li>Amazon recommended model for extending your network into the cloud </li></ul><ul><li>Ethernet bridging enables cloud resources to securely access on premise resources </li></ul><ul><li>DataSynapse proxy service is used for resource caching </li></ul>Federator On Premise On AWS DataSynapse Manager Secure VPN connection VPN Server VPN Bridge Client Caching Service
    12. 12. DataSynapse AMIs <ul><li>Standardized machine images </li></ul><ul><ul><li>Common engine configuration </li></ul></ul><ul><ul><li>Supporting services </li></ul></ul><ul><li>Operating Systems </li></ul><ul><ul><li>Windows 2003 </li></ul></ul><ul><ul><li>Fedora </li></ul></ul><ul><ul><li>OpenSUSE </li></ul></ul><ul><li>AMI sets stored in each Region </li></ul><ul><ul><li>Windows 2003 unavailable in EMEA </li></ul></ul><ul><li>Users may build customized AMIs: </li></ul><ul><ul><li>Must be based on default AMIs </li></ul></ul><ul><ul><li>Storage and associated costs of custom AMIs are the responsibility of the client </li></ul></ul>AWS S3 Storage AWS EC2 Instance Windows 2003 (64bit) Fedora (32bit) OpenSUSE (64bit) Fedora (64bit) OpenSUSE (32bit) DS Engine
    13. 13. Activating Engines on Amazon EC2 Cloud <ul><li>When activation policy executes: </li></ul><ul><ul><li>Federator launches specified # of engine AMI instances </li></ul></ul><ul><ul><li>Federator configures each engine to use the Proxy </li></ul></ul>On Premise On AWS DS Manager Secure SSH Tunnel DS Base AMI DS S3 Account Custom AMI Client S3 Account Cloud based engines do not count against GridServer license counts DataSynapse Engines on EC2 Proxy Service Proxy Service Federator Activation Policy
    14. 14. Uploading Grid Libraries <ul><li>Proxy synchronizes grid library resources with the Manager </li></ul><ul><li>Grid libraries are then cached on the Proxy side for distribution to EC2-based Engines </li></ul>Federator On Premise On AWS DataSynapse Manager Proxy Service Secure SSH Tunnel GridLibs GridLibs Proxy Service
    15. 15. Configuring Engines on Amazon EC2 Cloud <ul><li>When an Engine comes online they will first check with the proxy for any GridLibs </li></ul><ul><li>Updates to engines are done within the EC2 environment, there are no additional costs associated with this </li></ul>Federator On Premise On AWS Secure SSH Tunnel GridLibs (cached) Engines Instances DataSynapse Manager Proxy Service Proxy Service
    16. 16. Submitting Work to Cloud Engines Instances Federator On Premise On AWS DataSynapse Manager Secure SSH Tunnel <ul><li>Clients submit work to the GridServer Manager as before, no change required </li></ul><ul><li>Engines then request work from the GridServer Manager via the Proxy </li></ul><ul><li>Engines will receive start/stop service commands directly from the GridServer Manager </li></ul>Grid Client Proxy Service Proxy Service
    17. 17. Use Cases <ul><li>Dev and Test Grids: </li></ul><ul><ul><li>GridServer environments are large – some customers running 10k+ engines </li></ul></ul><ul><ul><li>Difficult to duplicate the scale of environment for testing </li></ul></ul><ul><ul><li>GridServer and EC2 provides a low cost solution </li></ul></ul><ul><li>Disaster Recover Grids: </li></ul><ul><ul><li>Again with large environments – it is difficult to duplicate for DR function </li></ul></ul><ul><ul><li>GridServer and EC2 provides a low-cost, pay only when needed option </li></ul></ul><ul><li>“ Flex-Service”: </li></ul><ul><ul><li>If workloads are not meeting desired SLAs – it is expensive and time consuming to add more compute capacity to crowded, expensive corporate datacenters </li></ul></ul><ul><ul><li>GridServer and EC2 provides a low-cost, solution for ad-hoc workload surges </li></ul></ul>
    18. 18. Beta Program Overview
    19. 19. Federator 1.5 – Beta Program <ul><li>Program runs from April ‘09 through November ’09 </li></ul><ul><li>Registration will close on March 4 </li></ul><ul><li>Space is limited </li></ul><ul><li>$25K registration fee </li></ul>
    20. 20. Program Benefits <ul><li>Free use of DataSynapse Engines Running on Amazon EC2* </li></ul><ul><li>No limit on DataSynapse Engines Running on Amazon EC2 </li></ul><ul><li>DataSynapse Engines Running on Amazon EC2 don’t count against existing license caps </li></ul><ul><li>Access to Federator 1.5 Beta, with periodic updates </li></ul><ul><li>Discounts on GA version of Federator 1.5 </li></ul><ul><ul><li>* Amazon Infrastructure Charges Still Apply </li></ul></ul>
    21. 21. Pricing Post-Beta <ul><li>No limit on DataSynapse Engines Running on Amazon EC2 </li></ul><ul><li>DataSynapse Engines Running on Amazon EC2 don’t count against existing license caps </li></ul><ul><li>Engine charges are $0.10 per hour, plus Amazon infrastructure charges* </li></ul><ul><ul><li>* Dependent on Amazon Instance Selected </li></ul></ul>
    22. 22. Q & A