1. CLOUD COMPUTING
OVERVIEW, DIRECTION
AND
PLAN OF ACTION BY
C S R PRABHU

2. Cloud Computing - Some terms
Term cloud is used as a metaphor for Internet
Concept generally incorporates combinations of the following :-
Infrastructure as a service (IaaS)‏
Platform as a service (PaaS)‏
Software as a service(SaaS)‏
Not to be confused with
Grid Computing – a form of distributed computing
Collection of loosely coupled, networked computers acting in concert to perform very large tasks
Utility Computing – packaging of computing resources such as computing power, storage, also as metered services
Autonomic computing – self managed

3. Grid Computing Share Computers and data
Evolved to harness inexpensive computers in Data Centre to solve variety of problems
Harness power of loosely coupled computers to solve a technical or mathematical problem
Used in commercial applications for drug discovery, economic forecasting, sesimic analysis and back-office
Small to big
Can be confined to a corporation
Large public collaboration across many companies and networks
eGovernance Grid
NICNET & SWANs to be integrated
Grid SOA to be implemented to create Web Service Repositories (presented previously)‏

4. Grid Computing Most grid solutions are built on Computer Agents
Resource Manager
Scheduler
Compute grids
Batch up jobs
Submit the job to the scheduler, specifiying requirements and SLA(specs) required for running the job
Scheduler matches specs with available resources and schedules the job to be run
Farms could be as large as 10K cpus
Most financial firms have grids like this
Grids lack automation, agility, simplicity and SLA guarantees

5. Utility Computing More related to cloud computing
- Applications, storage, computing power and network
Requires cloud like infrastructure
Pay by the drink model
- Similar to electric service at home
Pay for extra resources when needed
- To handle expected surge in demand
- Unanticipated surges in demand
Better economics

6. Cloud computing – History
Evolved over a period of time
Roots traced back to Application Service Providers in the 1990’s
Parallels to SaaS
Evolved from Utility computing and is a broader concept

7. Cloud computing Much more broader concept Encompasses IIAS, PAAS, SAAS
Dynamic provision of services/resource pools in a co- ordinated fashion
On demand computing – No waiting period
Location of resource is irrelevant
May be relevant from performance(network latency) perspective, data locality

8. Cloud computing Applications run somewhere on the cloud
Web applications fulfill these for end user
However, for application developers and IT
Allows develop, deploy and run applications that can easily grow capacity(scalability), work fast (performance), and offer good reliability
Without concern for the nature and location of underlying infrastructure
Activate, retire resources
Dynamically update infrastructure elements without affecting the business

9. Clouds Versus Grids Clouds and Grids are distinct Cloud
Full private cluster is provisioned
Individual user can only get a tiny fraction of the total resource pool
No support for cloud federation except through the client interface
Opaque with respect to resources
Grid
Built so that individual users can get most, if not all of the resources in a single request
Middleware approach takes federation as a first principle
Resources are exposed, often as bare metal
These differences mandate different architectures for each

10. Cloud Mythologies
Cloud computing infrastructure is just a web service interface to operating system virtualization.
“I’m running Xen in my data Centre – I’m running a private cloud.”
Cloud computing imposes a significant performance penalty over “bare metal” provisioning.
“I won’t be able to run a private cloud because my users will not tolerate the performance hit.”
Clouds and Grids are equivalent
“In the mid 1990s, the term grid was coined to describe technologies that would allow consumers to obtain computing power on demand.”

11. Commercial clouds

12. Cloud Anatomy Application Services(services on demand)‏
Gmail, GoogleCalender
Payroll, HR, CRM etc
Sugarm CRM, IBM Lotus Live
Platform Services (resources on demand)‏
Middleware, Intergation, Messaging, Information, connectivity etc
AWS, IBM Virtual images, CastIron, Google Appengine
Infrastructure as services(physical assets as services)‏
IBM Blue house, VMWare, Amazon EC2, Microsoft Azure Platform, Sun Parascale and more

13. Cloud Computing - layers
Architecture

14. What is a Cloud? Cloud Middle Ware Resources Services Storage Network
Individuals
Corporations
Non-Commercial
Government
Cloud Middle Ware
Storage
Provisioning OS
Provisioning
Network
Provisioning
Service(apps)‏
Provisioning
SLA(monitor),
Security, Billing,
Payment
Resources
Services
Storage
Network OS

15. Why cloud computing
Data Centres are notoriously underutilized, often idle 85% of the time
Over provisioning
Insufficient capacity planning and sizing
Improper understanding of scalability requirements etc
Thought leaders from Gartner, Forrester, and IDC—agree that this new model offers significant advantages for fast- paced startups, SMBs and enterprises alike.
Cost effective solutions to key business demands
Move workloads to improve efficiency

16. How do they work? Public Clouds are opaque
What applications will work well in a cloud?
Many of the advantages offered by Public Clouds appear useful for “on premise” IT
Self-service provisioning
Legacy support
Flexible resource allocation
What extensions or modifications are required to support a wider variety of services and applications?
Data assimilation
Multiplayer gaming
Mobile devices

17. Cloud computing - Characteristics
Agility – On demand computing infrastructure
Linearly scalable – challenge
Reliability and fault tolerance
Self healing – Hot backups, etc
SLA driven – Policies on how quickly requests are processed
Multi-tenancy – Several customers share infrastructure, without compromising privacy and security of each of the customer’s data
Service-oriented – compose applications out of loosely coupled services. One service failure will not disrupt other services. Expose these services as API’s
Virtualized – decoupled from underlying hardware. Multiple applications can run in one computer
Data, Data, Data
Distributing, partitioning, security, and synchronization

18. Public, Private and Hybrid clouds

19. Public clouds Open for use by general public
Exist beyond firewall, fully hosted and managed by the vendor
Individuals, corporations and others
Amazon's Web Services and Google appEngine are examples
Offers startups and SMB’s quick setup, scalability, flexibility and automated management. Pay as you go model helps startups to start small and go big
Security and compliance?
Reliability concerns hinder the adoption of cloud
Amazon S3 services were down for 6 hours

20. Public Clouds (Now)‏
Large scale infrastructure available on a rental basis
Operating System virtualization(e.g. Xen, kvm) provides CPU isolation
“Roll-your-own” network provisioning provides network isolation
Overlay Networks
Multiple Virtual Networks (Overlaid on one Physical Network)‏
Locally specific storage abstractions
Fully customer self-service
Service Level Agreements (SLAs) are advertized
Requests are accepted and resources granted via web services
Customers access resources remotely via the Internet
Accountability is e-commerce based
Web-based transaction
“Pay-as-you-go” and flat-rate subscription
Customer service, refunds, etc.

21. Private Clouds Within the boundaries(firewall) of the organization
All advantages of public cloud with one major difference
Reduce operation costs
Has to be managed by the enterprise
Fine grained control over resources
More secure as they are internal to org
Schedule and reshuffle resources based on business demands
Ideal for apps related to tight security and regulatory concerns
Development requires hardware investments and in-house expertise
Cost could be high - cost might exceed public clouds
NIC can have a private cloud over NICNET

22. Clouds and SOA SOA Enabled cloud computing to what is today
Physical infrastructure like SOA must be discoverable, manageable and governable
REST Protocol also used (Representational State Transfer)‏

23. Clouds for Developers
Ability to acquire, deploy, configure and host environments
Perform development unit testing, prototyping and full product testing

24. Open Source Cloud Infrastructure
Simple
Transparent => need to “see” into the cloud
Scalable => complexity often limits scalability
Secure => limits adoptability
Extensible
New application classes and service classes may require new features
Clouds are new => need to extend while retaining useful features
Commodity-based
Must leverage extensive catalog of open source software offerings
New, unstable, and unsupported infrastructure design is a barrier to uptake, experimentation, and adoption
Easy
To install => system administration time is expensive
To maintain => system administration time is really expensive

25. Microsoft and Amazon face challenges
Globus/Nimbus
Client-side cloud-computing interface to Globus-enabled TeraPort cluster at U of C
Based on GT4 and the Globus Virtual Workspace Service
Shares upsides and downsides of Globus- based grid technologies
Enomalism (now called ECP)‏
Start-up company distributing open source
REST APIs
Reservoir
European open cloud project
Many layers of cloud services and tools
Ambitious and wide-reaching but not yet accessible as an implementation

26. Microsoft and Amazon face challenges
Eucalyptus
Cloud Computing on Clusters
Amazon Web Services compatible
Supports kvm and Xen
OpenNebula
Joyent
Based on Java Script and Git

27. Open Source Cloud Ecosystem - Tools
RightScale
Startup focused on providing client tools as SaaS hosted in AWS
Uses the REST interface
Canonical
Ubuntu 9.10 (Karmic Koala)‏
Includes KVM and Xen Hypervisors

28. Open Source Cloud Anatomy
Extensibility :
Simple architecture and open internal APIs
Client-side interface
Amazon’s AWS interface and functionality (familiar and testable)‏
Networking
Virtual private network per cloud
Must function as an overlay => cannot supplant local networking
Security
Must be compatible with local security policies
Packaging, installation, maintenance
system administration staff is an important constituency for uptake

29. Open Source Cloud Anatomy
Private clouds are really hybrid clouds
Users want private clouds to export the same APIs as the public clouds
In the Enterprise, the storage model is key
Scalable “blob” storage doesn’t quite fit the notion of “data file.”
Cloud Federation is a policy mediation problem
No good way to translate SLAs in a cloud allocation chain
“Cloud Bursting” will only work if SLAs are congruent
Customer SLAs allow applications to consider cost as first-class principle
Buy the computational, network, and storage capabilities that are required

30. Open Source Clouds

31. Eucalyptus (Elastic Utility Computing Architecture Linking Your Programs To Useful Systems)‏

32. Clouds and Virtualization
Operating System virtualization (Xen, KVM, VMWare, HyperV) is only apparent for IaaS
AppEngine = BigTable
Hypervisors virtualize CPU, Memory, and local device access as a single virtual machine (VM)‏
IaaS Cloud allocation is
Set of VMs
Set of storage resources
Private network
Allocation is atomic
SLA
Monitoring

33. Cloud Performance
Extensive performance study using HPC applications and benchmarks
Two questions:
Performance impact of virtualization
Performance impact of cloud infrastructure
Observations:
Random access disk is slower with Xen
CPU bound can be faster with Xen -> depends on configuration
Kernel version is far more important
No statistically detectable overhead
AWS small appears to throttle network bandwidth and (maybe) disk bandwidth -> $0.10 / CPU hour

34. Cloud computing open issues
Governance
Security, Privacy and control
SLA guarantees
Ownership and control
Compliance and auditing
Sarbanes and Oxley Act
Reliability
Good servive provider with % availability
Cloud independence – Vendor lockin?
Cloud provider goes out of business

35. Cloud computing open issues
Data Security
Cloud lockin and Loss of control
Plan for moving data along with Cloud provider
Cost?
Simplicity?
Tools
Controls on sensitive data?
Out of business
Big and small
Scalability and cost outweigh reliability for small businesses
Big businesses may have a problem

36. Cloud articles http://blogs.zdnet.com/Hinchcliffe/?p=488&tag=btxcsim
/tc _445669_page_3.htm
chjournal/0904_amrehein/0904_amrehein.html

37. Battle in the cloud Amazon Web Services Google App Engine
Free upto 500 MB,
Free for small scale applications?
Universities?
Pay when you scale
GoGrid
.. Some more Hosting companies
Where is HP, IBM, Oracle(+sun) and Dell?

38. Cloud in NIC Single Data Centre Cloud Eucalyptus : Proven Technology
Company Support Available
Multi Data Centre Cloud over NICNET
Grid Enabled Cloud
Nimbus :
On GT4 and Xen

39. Use Cases of Cloud for NIC & eGovernance
NIC internal usage :
NIC private cloud on Data Centres :
NIC staff at District Centres, NIC staff at NIC Block Centres can utilise cloud services as virtual resources (where setting up real IT infrastructure may not be prossible or may be too expensive)‏

40. Central Government Departments & Public Sector Undertakings
NIC cloud services can be offered to Central Government Departments & Public Sector Undertakings for their own utilisation on chargeable basis

41. State Government Departments
Secretariat :
Virtual resources & cloud services can be provided to Secretariat Applications from the Data Centre (eg. New Secretariat campus in Chennai for Tamilnadu Government)‏
State Data Centres :
Cloud services can be built on State Data Centres to provide virtual resources & services for various State Government Departments and also State Public Sector Undertakings

42. State Government Departments
District Collectorates & District Level Departments of State Government :
Virtual resources/Cloud services can be provided from State Data Centre
Taluka & Block Level Government offices :
Site Preparation & IT Infrastructure :
Costs can be substantially reduced at District, Taluka & Block Levels

43. Why Cloud Computing on NIC’s Data Centres ?
Multiplication effect of servers and platforms on NIC Data
Centres as :
1. Infrastructure as a Service
Beneficial for NIC State Centres, NIC District Centres and also proposed Block Centres
Results in significant savings on IT and non IT infrastructure
2. Platform as a Service
Beneficial for NIC State Centres and NIC District Centres and also proposed Block Centres
Results in Significant Capabilities at no cost
3. Software as a Service
Already available

44. Plan of Action Testing of Eucalyptus & Nimbus
Prototype deployment & operationalisation on a single Data Centre
Phase wise expansion of cloud services in all Data Centres using Eucalyptus & Nimbus
Adequate infrastructure & manpower to be provided
Tie up with Eucalyptus services company for support

45. T H A N K Y O U