Leveraging Private Clouds with RightScale's ServerTemplate Methodology
•Descargar como PPTX, PDF•
2 recomendaciones•832 vistas
Rob Carr, Integration Engineer at RightScale, led this session at the RightScale User Conference 2010 in Santa Clara. Session Abstract: Enterprises that are required to keep physical control of infrastructure but want the benefits of public cloud elasticity are driving the development and adoption of private cloud technology. This session covers the emerging private cloud phenomenon and how RightScale allows you to leverage your existing infrastructure in new and exciting ways. We'll discuss the fundamentals of private cloud architectures, clarify how RightScale ServerTemplate technology drives value within private clouds, and demonstrate a hybrid cloud deployment in action.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (7)
Similar a Leveraging Private Clouds with RightScale's ServerTemplate Methodology
Similar a Leveraging Private Clouds with RightScale's ServerTemplate Methodology (20)
Más de RightScale
Más de RightScale (20)
Último
Último (20)
Leveraging Private Clouds with RightScale's ServerTemplate Methodology
- 1. Leveraging the Private Cloud Robert Carr, Professional Services
- 2. Welcome Concept to Reality Components of a Cloud Application Requirements Filters Dynamic Configuration Methodology Connecting the Cloud Hybrid-cloud Management Q&A
- 3. Concept to Reality Do private clouds exist? Vaporware becomes vendorware Cloud.com Eucalyptus OpenStack VMware vCloud Opensource / Commercial Offerings Enterprises deploying private clouds today
- 4. Customer Profiles Already committed to a private cloud project. Some public cloud success Adapting public cloud experience to their own internal operations Streamlining procurement Increasing transparency Proof-of-concept In-house learning Is it feasible and reasonable? What do you we do with all these servers? Information gathering Everyone wants to follow Reference architectures Best practices
- 5. Basic Private Cloud Layout Management Nodes API Storage Pools Compute Nodes
- 6. “Hybrid” cloud architectures Private Hybrid Bursting
- 7. Why Multi-cloud; Hybrid-cloud? Many Reasons: Geo-location Compliance Performance Price High availability Disaster recovery Freedom of choice / no lock-in Better utilization Excess capacity
- 10. Enable users through self-service
- 11. Maintain cost accounting and transparency
- 12. Control access to multiple resource pools
- 14. Bring the cloud to your data
- 15. Compliance
- 16. Data transfer performance / Cost
- 18. Your own custom cloud
- 19. One-size may not fit all
- 21. Define your requirements filters
- 22. What are you trying to accomplish?
- 24. Human costs / Training
- 25. Capital expenses for HW
- 27. Start Small
- 28. 10,000 nodes? Try 10, then 100
- 29. Work out the kinks
- 31. Design once deploy anywhere
- 32. Let the application dictate the infrastructure
- 33. Be selective
- 37. Control resource pool accessExperience Community and ISV assets Best practices Real world case studies
- 38. RightScale’s ServerTemplate Methodology Dynamic configuration Cloud Agnostic / Portable Modular and variable-based Re-usable and sharable Version controlled
- 39. Server Templates are Server DNA Cloud Agnostic One Asset, Multiple Options Public “Web Server” Private Future Cloud
- 40. RightScale Resource Pools Requirements Filter Application Portfolio Public Cloud (AWS; Rackspace Cloud) Performance App 1 App 1 Private Cloud (Eucalyptus; vCloud, etc.) Cost App 2 App 2 AWS VPC Security App N Compliance App N Resource Pools Reliability Internal DC CoLo Enabling “New IT”
- 44. Cloud Rollout – Initial Legacy EC2 interface AWS multi-cloud interface Operated by RS Cloud-specific Region-specific RightScale Gateway Target Cloud Asynchronous Event-based Encrypted Synchronous Poll-based Monitoring System RightScale Platform Syslog, mirrors firewall
- 45. Cloud Rollout – Gateway Migration Legacy EC2 interface AWS multi-cloud interface Cloud-specific Operated by RS Target Cloud Cloud-specific RightScale Gateway Asynchronous Event-based Encrypted Synchronous Poll-based Monitoring System RightScale Platform Syslog, mirrors firewall
- 46. Cloud Rollout – Full Deployment Legacy EC2 interface AWS multi-cloud interface Operated by RS Cloud-specific Target Cloud Asynchronous Event-based Encrypted Cloud-specific RightScale Gateway Synchronous Poll-based RightScale Platform Monitoring System Syslog, mirrors firewall
- 47. Demo: Managing Your Clouds Managing a Multi-Cloud Architecture RightScale Private Cloud Connectivity. Public Cloud Load Balancing Multiple Private Cloud Pools.
- 48. “RightScaleAnnounces Private Cloud Early Access Program Participants can Explore Private Cloud Technologies Using RightScale’s Reference Architecture for Eucalyptus and Cloud.com” More information Sales@RightScale.com For Copies of These Slides www.rightscale.com/conferenceAny Additional Questions? Conference@rightscale.com
Notas del editor
- The RightScale ServerTemplate methodology supports creating and re-using many of the same components through out the lifecycle. Let’s look a little more closely at how it does that. A ServerTemplate defines the software stack and behavior of a provisioned cloud server. ServerTemplates can be combined to create deployments that describe and launch entire environments. Each ServerTemplate contains a base machine image and a set of scripts. Typically, the base machine image installs both the operating system and the lightweight RightScale agent, RightLink, which enables and manages communication with the RightScale Cloud Management Platform. After the server boots up using this machine image, RightScale runs all the startup scripts specified to install the required software. While the server is running, the systems administrator is free to run any of the operational scripts through RightScale. And, when the user terminates the server, termination scripts are used to gracefully shut down the server.ServerTemplates reference re-usable scripts. Because both the ServerTemplates and the scripts are version controlled, and because deployments can be cloned and archived, any changes are easily tracked and propagated. These features provide all the power a systems administrator needs to easily manage, maintain and reproduce multiple environments.