Mais conteúdo relacionado Semelhante a Which cloud(s) & why? Defining Clouds and Best Practices (20) Which cloud(s) & why? Defining Clouds and Best Practices1. © 2013 Eucalyptus Systems, Inc.
Which Cloud(s) &
Why? Defining Clouds
and Best Practices
Paul Weiss
Technical Marketing Manager
1
2. © 2013 Eucalyptus Systems, Inc.
Agenda
• Why Cloud?
• Define Cloud
• Cloud Models
• Old vs New
• Benefits of Cloud
• How to Select the Right Cloud Model(s)
• How to Select the Applications to Move into the Cloud
• How to Successfully Migrate Applications into the Cloud
• Best Practices (Getting Started)
2
5. © 2013 Eucalyptus Systems, Inc.
The Connected Life by 2020
5
Be prepared to support 3x the workload in 7 years
6. © 2013 Eucalyptus Systems, Inc.
What’s Driving Cloud Adoption
6
Source: 2012 Future of Cloud Survey
Scalability is the #1 reason for cloud. Remember 3x
in 7 years
7. © 2013 Eucalyptus Systems, Inc.
Tomorrow’s Cloud Forecast
7
Source: 2012 Future of Cloud Survey
Hybrid is the only way to scale to 3x in 7 years
9. © 2013 Eucalyptus Systems, Inc.
Cloud Computing Definition
• Industry surveys indicate that the desire to move to cloud
computing is widespread. So what is cloud computing?
• National Institute of Standards and Technology (NIST)
definition:
“. . . a model for enabling ubiquitous, convenient, on-demand
network access to a shared pool of configurable computing
resources . . . that can be rapidly provisioned and released
with minimal management effort or service provider
interaction.”
9
12. © 2013 Eucalyptus Systems, Inc.
Cloud Deployment Models
Private Cloud Community Cloud Public Cloud
The cloud infrastructure is
operated entirely for an
organization.
The cloud infrastructure is
shared by several
organizations and supports a
specific community that has
shared concerns.
The cloud infrastructure is
made available to the general
public or a large industry
group and is owned by an
organization selling cloud
services.
• Secure
• Predictable Performance
• Existing resources
• Path to hybrid cloud
• Control
• Cost control
• Designed w/ a purpose
• Scale
• Cost savings (if managed)
• Cost savings (if managed)
• Scale
• Regions to span
• Many services
Eucalyptus, Apache Cloud
Stack, OpenStack
AWS GovCloud AWS, GCE, Windows Azure,
RackSpace
~~~~ Hybrid Cloud ~~~~
12
13. © 2013 Eucalyptus Systems, Inc.
Traditional IT Deployment Model
(OLD)
13
• In a traditional
model, the user
must work through
the IT department to
provision a server.
• This is a multi-stage
process that has
inherent delays.
• Can take
days, weeks, or
even months
User requests server
Server provisioned
Wait
Negotiate resource
configuration
Negotiate business
case
Approved?
IT available?
no
no
yes
yes
Old methods will not scale to the 3x we need to
support
14. © 2013 Eucalyptus Systems, Inc.
Cloud Computing Deployment Model
(NEW)
14
• In a cloud computing model
the user can self-provision
servers that fall within
predefined IT resource
policies.
• This model eliminates many
of the inherent delays in the
traditional deployment model.
• Deployment time reduced to
minutes
User requests server
Server provisioned
IT defines resource
policies
Within policies?
yes
no
Cloud computing deployment model will help us
scale to support the 3x demand
15. © 2013 Eucalyptus Systems, Inc.
Differences Between Virtualization
and Cloud Computing
15
Traditional
Virtualization
Cloud Computing
VM Location on a specific host on any host in
availability zone
VM Storage persistent ephemeral (except for
volumes)
VM Resources (CPU,
memory)
customizable standard sizes (Small,
Medium, Large, etc.)
VM Resource Change
Method
resize existing VM launch new VM
Time to Provision Minutes/Hours/Days Minutes
VM Failure Recovery
Method
attempt to recover failed
VM
discard and start new
VM
Virtualization alone is not cloud!
16. © 2013 Eucalyptus Systems, Inc.
Some Benefits of Cloud Computing
• Application scalability
• Agility
• Cost control
• Time to Market
• Security
• Better utilization of resources
• Disaster Recovery
• Remove IT silos
16
#1 – Scalability
#2 – Agility
#3 Cost
17. © 2013 Eucalyptus Systems, Inc.17
The Roadmap Through Private Cloud
After virtualization, private cloud is the next step
18. © 2013 Eucalyptus Systems, Inc.
IaaS Use Cases - Getting Started
• Transient apps: dev & test environments
• Bursty workloads: web and mobile applications
• Big data: analytics and computations
• Gaming applications
and: hybrid clouds, rich media encoding/decoding, complex and large-scale data
processing, training & e-learning, storage-as-a-service, remote desktop hosting,
public cloud, carrier-grade cloud
18
Dev / Test is a great place to start
19. © 2013 Eucalyptus Systems, Inc.
To Cloud or Not? – Think about
• Dev / Test – on ramp to public cloud
• Security
• Intellectual Property (IP)
• Manufacturing
• Some Enterprise Applications
19
Every application needs to be carefully evaluated –
to cloud or not!
22. © 2013 Eucalyptus Systems, Inc.
What’s in an Image?
• Not running
• Operating System
• Current Patches*
• Application*
Note: An image is stored in the cloud, not running
22
An image is a stored snap-shot or disk copy of a
system, ready to be launched
23. © 2013 Eucalyptus Systems, Inc.
What’s in an Instance?
• Running copy of an image
• Configured size (VM Type)
– CPU
– Memory
– Disk
– Network / Security
• Operating System
• Current Patches
• User(s) – keys by default, LDAP, AD
• Additional storage if needed
• Application(s)
• Connections to other systems – LB’s, DB’s, etc.
23
An instance is a running virtual machine, based on
an image, ready to use
24. © 2013 Eucalyptus Systems, Inc.
Images
Machine Size
• CPU(s)
• Mem
• Disk
• Network
Operation
System
Initial
Configuration
(network,
access,
mounts, etc)
Patches Application Application
Configuration
Basic Virtual
Machine
Manually
Configure
Choose ISO,
Manually
install
Manual
configuration
Manually
install
Manually
install
Manual
configuration
Advanced
Virtual
Machine
Boot pre-configured VM template Manual
configuration
Manual update Installed with
template
Manual
configuration
Basic Cloud
Instance
Choose VM-
Type
Choose Image Cloud
configured
Manually
install
Manually
install
Manually
configured
Semi-
Automated
Cloud
Choose VM-
Type
Choose Image Cloud
configured
Configuration Management
Agent managed
Fully
Automated
Cloud
Using monitoring, load-balancing, auto-scaling – cloud automatically provisions / de-provisions as needed
to maintain work-load.
24
Think about supporting 3x the workload
25. © 2013 Eucalyptus Systems, Inc.
Instance Flow
25
VM Size OS Install
Initial
Config
App
Install
Patch
Install
Final
Config
How many of these steps do you want to do
manually?
26. © 2013 Eucalyptus Systems, Inc.
How to start an Instance
• Start basic instance
– $euca-run-instances emi-12345 –k mykey
• Advanced instance start
– $ euca-run-instances emi-12345 –k mykey –g my_security_group –t
Vmtype –f cloud-config.txt
26
27. © 2013 Eucalyptus Systems, Inc.
Cloud-init
$ cat cloud-config.txt
#cloud-config
# upgrade the instance on first boot
package_upgrade: true
# setup mount points
mounts:
- [ sdc, /opt/data ]
# install additional packages at first boot
packages:
- your favorite configuration management system agent
27
28. © 2013 Eucalyptus Systems, Inc.
Application Groups
Apache + HAProxy Apache + HAProxy
App Server 1 App Server 2 App Server 3 App Server n
Master
DB
Slave
DBEBS
Vol.
EBS
Vol.
Walrus
Your Site
Daily Snapshots Rolling Snapshots
Replication
172.168.2.54 172.168.9.87
Web-Tier Group #1
App-Tier #1
29. © 2013 Eucalyptus Systems, Inc.
Web-Tier Group #1
• VM Type: Large
– 2 CPU
– 8 GB RAM
– 160 GB Disk
• Update OS
• Install Apache + HA Proxy
• Connect to App-Tier Message Queue
• Add IP to load balancer
• Report success to monitoring tool when above is done
29
30. © 2013 Eucalyptus Systems, Inc.
App-Tier Group #1
• VM Type: X-Large
– 4 CPU
– 16 GB RAM
– 160 GB Disk
• Update OS
• Install Application Server
• Connect to App-Tier Message Queue
• Connect to Database Message Queue
• Report success to monitoring tool when above is done
30
31. © 2013 Eucalyptus Systems, Inc.
Monitor Each Tier
• Understand load placed on tier
• Knows how to scale up when demand increases
– Max instances
• Knows how to scale down when demand decreases
– Min instances
31
Group applications, monitor and scale up or down
as needed to meet demand and contain cost.
33. © 2013 Eucalyptus Systems, Inc.
Application Dependency Mapping
33
Has risk assessment and dependancy mapping
been done on every mission critical application?
34. © 2013 Eucalyptus Systems, Inc.
Less Complex
34
Keep it simple for first time success!
35. © 2013 Eucalyptus Systems, Inc.
Examples of Tight / Loose Coupling
• Example of tight coupling:
Controller A Controller B Controller C
Controller A Controller B Controller C
Controller A Controller B Controller C
Controller A Controller B Controller C
Q
1
Q
1
Q
1
• Example of loose coupling using queues:
Design for scalability
36. © 2013 Eucalyptus Systems, Inc.
Example of Scalability Design
Apache + HAProxy Apache + HAProxy
App Server 1 App Server 2 App Server 3 App Server n
Master
DB
Slave
DBEBS
Vol.
EBS
Vol.
Walrus
Your Site
Daily Snapshots Rolling Snapshots
Replication
172.168.2.54 172.168.9.87
37. © 2013 Eucalyptus Systems, Inc.
Design for Scalability
• A scalable application architecture is critical to take
advantage of a scalable infrastructure
• Load balancing and proxying
• Caching
– Don’t generate the same content twice
• No central point of data storage contention
– Shared Nothing / Sharding / Distributed Caching
• Loose coupling of processing requestors and responders
38. © 2013 Eucalyptus Systems, Inc.
Design for Failure
• "Everything fails, all the time“
- Werner Vogels, CTO Amazon.com
• Avoid single points of failure
• Assume everything fails, and design backwards
• Design for failure and your app won’t fail
40. © 2013 Eucalyptus Systems, Inc.
Stage-Move-Manage Cloud
EBS
S3
EC2
IAMEMI
S3EC2 EBS
IAM
AMI
• Multi-vendor Virtualization
• Multi-vendor Storage
• Data center Networking
• Infrastructure Meshed
Applications
• Layer over multi-vendor
complexity
• Separate application logic
from infrastructure
• Store data with cloud
compute accessibility
• Create LDAP/AD to IAM
bridge
• Seamless access to on-
demand capacity
• On-demand pricing
• Better application
availability
• Better data resiliency
Cloud Management Framework
41. © 2013 Eucalyptus Systems, Inc.
Hybrid Cloud API Compatibility
41
Test on-premise cloud compatibility with proven
applications
42. © 2013 Eucalyptus Systems, Inc.
AWS & Eucalyptus Compatibility
42
How compatible is the hybrid solution?
44. © 2013 Eucalyptus Systems, Inc.
Mirroring / Replication
Scaled down
Standby
Data
Volume
Application
Server
Reverse
Proxy /
Caching
Server
AWS Region
Slave
Database
Server
Data
Volume
Application
Server
Reverse
Proxy /
Caching
Server
Eucalyptus On-Premise IaaS
Master
Database
Server
Pilot Light
Not Running
Pilot Light System
www1.eucalyptus-labs.com
46. © 2013 Eucalyptus Systems, Inc.
Mirroring / Replication
Data
Volume
Application
Server
Reverse
Proxy /
Caching
Server
AWS Region
Slave
Database
Server
Data
Volume
Application
Server
Reverse
Proxy /
Caching
Server
Eucalyptus On-Premise IaaS
Master
Database
Server
Pilot Light - recovery
Start in
minutes
Add additional
capacity as needed
www2.eucalyptus-labs.com
X
49. © 2013 Eucalyptus Systems, Inc.49
The Roadmap Through Private Cloud
Can you support 3x? Planning is critical!
50. © 2013 Eucalyptus Systems, Inc.
Cloud Best Practices (requirements)
• Risk assessment on all mission critical applications
• Dependency mapping on all mission critical applications
• Gather application issues
• Application requirements (OS, platform)
• Machine requirements (CPU, Memory)
• Network requirements
• Storage requirements (space and IOPS)
• Benchmark virtual machine / application
• Document application monitoring
50
51. © 2013 Eucalyptus Systems, Inc.
Cloud Best Practices (Getting Started)
• Review NIST Special Publication 800-146
• Review Gartner Cloud Roadmap
• Decide what cloud model(s) you will start with
• Get executive sponsorship
• Agree what success looks like
• Create a project plan
• Train staff
• Choose an application that makes sense
• Benchmark application in the cloud (compare)
– Performance, Availability & Scalability
• Monitor
51
52. © 2013 Eucalyptus Systems, Inc.
Thank you.
52
Paul Weiss
paul.weiss@eucalyptus.com
@Paul_Weiss
Notas do Editor How many connected devices do you own?By 2020 we will have to support about 24 billion devices. That’s only 7 short years away!Can your current data center support a 3x increase? What are your plans to support the increase?http://gigaom.com/cloud/internet-of-things-will-have-24-billion-devices-by-2020/ The biggest cloud drivers are:Scalability – supporting that 3x increase by 2020Agility – current data center thinking in not very flexible. We allocate resources based on projects. We ask our architects how much CPU, memory, disk space a project requires and build systems from there. What about point #1? If an application needs to scale, can it?Cost – as with most things, cost saving is always good. One point here is, we need to utilize what we have more efficiently. Virtualization took us from 5-15% utilization to about 30-50%. Think about that, data center resources sitting idle for 50-70% of the time. We have to get better at this.Remember – Can your data center support a 3x increase? What our future looks like. As we move toward our 2020 goal of supporting 3x the workloads of today, we will use a mix of public and private cloud to support the increasing demand. Or what we call Hybrid Cloud. http://csrc.nist.gov/publications/drafts/800-145/Draft-SP-800-145_cloud-definition.pdfPretty much any IT survey in the last 2 years puts cloud and virtualization among the top goals for most companies.So what is cloud computing? Seems like every company says that they have a cloud today, but do they? Are they just cloud-washing?NIST offers a broad definition covering all aspects of cloud computing.More detail on the following pages. From the top done.Deployment modelsService models5 Essential Characteristics What does a cloud look like? What characteristics does it need?On-demand self-service – Self-service to me takes on two characteristics. The first is a for individual consumers of the cloud to have portal like access. The second is to allow programmatic access. An API. This is for build and automation tools, orchestration engines, monitoring frameworks. Network access – People have to able to access what we build on these cloudsResource pooling – combine our resources. No more silo’s or equipment. Let others shareElasticity – the ability to change or be flexibleMeasured service – charge back or show back AWS: Amazon Web ServicesGCE: Google Compute Engine Approvals and deployments depend on humans and therefore have the potential for delays. Deployment can take days, weeks, or even months. The cloud itself, not the IT department, checks to see if the request is within policies. Because humans are less involved there is no potential for delay. How are we going to get there?Server virtualizationDistributed virtualizationPrivate Cloud – EucalyptusHybrid Cloud – Eucalyptus and Amazon AWS – this is were we can share the load across the on-premise Eucalyptus cloud and the public Amazon AWS cloud. This gives you the maximum flexibility.Public Cloud- Amazon AWS – moving as much of your workloads into the public cloud.Link to Gartner research:http://www.internap.com/wp-content/uploads/Virtualization-to-the-Cloud-Internap_vol2_issue2.pdf Bursty workloads – seasonal spikesTransient apps – QABig data – move from data-warehousing analyzing in real timeGaming – could be spikey How are we going to get there?Server virtualizationDistributed virtualizationPrivate Cloud – EucalyptusHybrid Cloud – Eucalyptus and Amazon AWS – this is were we can share the load across the on-premise Eucalyptus cloud and the public Amazon AWS cloud. This gives you the maximum flexibility.Public Cloud- Amazon AWS – moving as much of your workloads into the public cloud.Link to Gartner research:http://www.internap.com/wp-content/uploads/Virtualization-to-the-Cloud-Internap_vol2_issue2.pdf