Cloud computing presentation explanation.ppt

Cloud computing presentation explanation

2. Syllabus
Chapert-1:
Data Centers to Cloud
1. Move into The Cloud.
2. Know Your Software Licenses.
3. The shift to a Cloud Cost Model.
4. Service Levels for Cloud Architecture.
Chapter-2:
Security
1. Disaster Recovery.
2. Web Application Design.
3. Machine Image Design.
4. Privacy Design.
5. Database Management.
6. Data Security.
7. Network Security.
8. Host Security.
9. Compromise Response.

3. 1. Move into The Cloud.
The digital economy requires unfettered connectivity,
regardless of your circumstances. 
 Employees need access to their data at all times, from
any location, using any device in order to quickly
respond to customers, close a big deal, and handle
daily operations.
Most company IT teams control everything
technology-related to improve operational efficiency.
You don't need control.
Act like a startup.
Technology as a service.
Manage your budget.

4. Cloud Computing Attributes

5. Total Cost of Ownership

6. 2.Know Your Software Licenses.
Traditional licensing system
Traditional Infrastructure (S/w ,H/W) need licenses.
Cloud Licensing
You can not port your traditional data centers
license to the Cloud.
You can only pay as you use.
Today Cloud environments in Operation
CPU-Hour
Example The Cheapest Virtual Machine in the Amazon
Cloud.

7. Cont…
Traditional Environment
To provide service through internet vendors following
technique like:
1. From Mid night to 9 am
Run your application on two application servers for
redundancy’s sake.
2. From, 9 am to 5 pm
Launch 6 additional application servers to support business
hours demand.
3. For the evening hours through midnight.
Reduce the system down to four application servers.
 you have to purchase and run eight servers the entire
time

8. Cont…
Moving into the Cloud. Licensing terms:
Does the software support usage based costs (CPU-hour,
user, etc…).
Does the software allow operation in virtualized
environment.
Ideal Cloud licensing model is OPEN SOURCE.
Ex: AMAZON CLOUD
Some Open Source Solutions:
Apache, Linux Distributions.
You can do, whatever you want , you may have deal
with license if you get supported version of open source
software.
Ex: Redhat Enterprice, Linux, MySQL Enterprice.
These are cloud friendly licensing systems

9. Pure open source case:
Cloud licensing model charges by the CPU- hour.
Hour based licensing Charges offering software
Companies:
Microsoft, Red Hat, Sun ,etc…(Adapted per CPU hour
terms to support cloud Computing).
Software licensing :
License tied to a specific MAC or IP Address, or other
license management systems.
But which may not support enough for cloud
environment

10. Amazon Simple Storage Service (S3)
Unlimited Storage.
Pay for what you use:
$0.20 per GByte of data transferred,
$0.15 per GByte-Month for storage used,
Second Life Update:
1TBytes, 40,000 downloads in 24 hours - $200,

11. Custom installation(inflexible) offered by the
traditional licensing software but cloud offers all
in flexible manner.
Some CPU based licenses require validation
against a Licensing a server.
Licensing software cloud give more benefits.

12. 3. The shift to a cloud cost model
You pay for resources in the cloud as you use them.
Amazon cloud cost model : CPU- Hour
Other cloud cost models: RAM-Hour
Example: cost model
Let one load balance, two application servers, two database servers.
Suppose costs for core infrastructure is:
$0.10/CPU-Hour: One Load Balancer
$0.40/CPU-Hour: Two Application Servers
$0.80/CPU-Hour: Two Database Servers
Each day you would pay:
$2.40+$44.0+$38.40=$84.80
Yearly
$30,952.00
Here not included software licensing fees and cloud management
tools or human resource

13. Cont..
How to Approach Cost Comparisons.
Cloud and other models cost comparison is based
on Hardware depreciation period(Generally it
is 2 or 3 yrs)

14. Cloud Cost model: we consider the following
elements
Estimate costs of virtual server usage over 3 years
Estimate licensing fees to support virtual server
usage over 3 years
Estimate cost for cloud infrastructure management
tools
Estimate labour costs for creating machine images ,
managing the infrastructure , and responding issue
over the 3 years period.
Any third party setup cost for the environment.

15. Up Front Models: we consider the following
issues
What are your upfront cost( setup fees, physical
space, h/w purchases, license fee ,etc..)
What labour is require to setup the infrastructure.
What are the costs associated with running the
infrastructure( hosting space, insurance. ..)
What are the ongoing license subscriptions /
upgrade fees? Maintenance fees?

16. A simple ROI(Return On Investment Model) Analysis.
General Model- Your new IT Shop:( Minimum requirement)
Half rack at a reliable ISP with sufficient bandwidth to
support your needs.
Two good firewalls
One h/w load balancer
Two good GB Ethernet switches
Six Solid, Commodity business servers,
Cloud Model: new IT Shop:
One medium 32 bit instance
4 large 64 bit instances during standard usage, sale to meet up
standard demand.

17. Cost of Internal shop > Cost of Cloud shop.
Where the cloud saves the money?
Issues like labor, infrastructure, ….etc

18. 4.Service Level for cloud applications
Availability
How to estimate the availability of your system
a=(p-(cxd))/p
 where a= expected availability
p= the measurement period
c= the % of likely hood (a server loss in a given period)
d= expected down time from the loss of the server.
To achieve accuracy availability( network cable
loss or reconfigure system or recovery case…..)
a = (p- sum(c1xd1:cnxdn))/p