Dataline presentation ong cloudbursting at FOSE, March 2009

1. quot;Cloudburstingquot;
FOR OPERATIONAL AND TACTICAL EMPLOYMENT
KEVIN JACKSON
DIRECTOR, BUSINESS DEVELOPMENT

2. As per Geva Perry
Cloudburst (negative): The failure of a cloud computing environment due to

the inability to handle a spike in demand.
Reference:quot;The only way to do cloud computing efficiently is to share the cloud -
to establish a broad, multitenant grid (or a number of them) that balances the
loads of many different companies. Otherwise, it'll be one cloudburst after
another, and a whole lot of underutilized capital assets.quot; Source: Nicholas Carr:
Intuit's cloudburst frustrates customers.
Cloudburst (positive): The dynamic deployment of a software application that

runs on internal organizational compute resources to a public cloud to address a
spike in demand.
Reference: quot;ISV virtual appliances should underpin a new surge in cloud use
followed by self-service mechanisms and enterprise connectors enabling
organizations to 'cloudburst' to using cloud services.quot; Source: The 451
Group:RightScale rolls its on-ramp toward other cloud systems (subscription
required)
Related uses: Cloudbursting. Reference quot;In addition to direct sales to
enterprises, going forward it hopes that extending out from private clouds to
public ones – what we like to call 'cloudbursting' – will become a prevailing IT
weather pattern and provide it with additional opportunities. quot; Source: The 451
Group: Q-Layer has the wisdom to enable private clouds (subscription required)

3. Cloudbursting – Jeff Barr, Reuven Cohen, Bob Lozano, etc.
Marry the traditional safe enterprise computing model with cloud computing;

in essence, bursting into the cloud when necessary or using the cloud when
additional compute resources are required temporarily.
Traditionally been applied to resource allocation and automated

provisioning/de-provisioning of resources, historically focused on bandwidth.
Today, in the cloud, it is being applied to resources such as servers,
application servers, application delivery systems, and other infrastructure
required to provide on-demand computing environments that expand and
contract as necessary, without manual intervention.
The hybrid application deployment model involving cloud computing requires

additional intelligence on the part of the application delivery network. The
application delivery network must be able to understand what is being
requested and where it resides; it must be able to intelligently route
requests. This, too, is a fundamental attribute of cloud computing
infrastructure: intelligence. When distributing an application across multiple
locations, whether local servers or remote data centers or quot;in the cloudquot;, it
becomes necessary for a controlling node to properly route those requests
based on application data.

4. Value
Positives Concerns
 Reduced Capital  Security
expenditure  Availability/
 Maintain SLA during Latency
surge  Transparency
 Increased reliability  Traceability
 Enhanced  Connectivity
capabilities requirements
 Increased efficiency  Flexibility
 Data duplication

5. Other Pluses
 Cost savings realized by organizations that take
advantage of cloudbursting instead of building their
own infrastructure.
 Can also be an efficient method of assisting with
scaling rapid growth sites at which the rate of traffic
growth is outpacing the ability of IT to obtain,
prepare and deploy infrastructure.
 Can also be extended as a disaster recovery plan in
order to reduce the costs associated with building out
and maintaining a secondary, idle data center.

6. LA Fire Emergency Solution
External Cloud
DHS
Any
EC2 Google
Provider
Stealth Network Security
Policy manager
Queing System
DHS
Assistance Local Batch System Database
Form

10. How do you do it?
 You must have the application deployed and available
inside the cloud. It may be possible to deploy
applications on-demand to the cloud computing
provider, but most providers will likely require the
application be deployed before it is needed.
 You must have a global load balancer capable of
deciding when to direct requests to a secondary site.
 You must have a way to determine when your
application infrastructure is near capacity.
An application delivery controller (intelligent load
balancer) is the most efficient mechanism for making
this determination.

11. Conclusion
 Well understood technically with many enabling
products available
 Excellent option for
• Surge requirements
• Seasonal requirements
• Research & development
• Ad-hoc computing networks
 Capability worth exploring

12. For more information:
 Kevin Jackson
• Kevin.jackson@dataline.com
 Cloud Musings blog
• http://Cloudcomputing.dataline.com
 Government Cloud Computing
• http://Govcloud.ulitzer.com