Private clouds are cloud infrastructure that resides within a company's own datacenter and is managed internally. They allow a company to have cloud-like capabilities while maintaining control and security over their own data. Private clouds work by using virtualization and a controller to provision and track physical resources like servers, storage, and networks as more capacity is needed. The document discusses the private cloud platforms Eucalyptus, OpenStack, and CloudStack, comparing their architectures, development histories, and strengths for different use cases.

1. Private
Clouds
Eucalyptus, OpenStack, CloudStack

2. Let’s do this
• What are they?
• And I can use them for?
• How do they work?
• Eucalyptus
• OpenStack
• CloudStack

3. Private Clouds – What are
they?
It is a Cloud which resides within your own
datacenter, company or systems in which all the data
is stored within your location, plus it is managed by
you. In other words you are the King of the Cloud.
In the private cloud the resource capacity is limited by
the physical infrastructure which you rely on.

4. Private vs Public
http://blogs.msdn.com/b/arunrakwal/

5. And can I use them for?
Private clouds can be use for many use cases
• Research
• Data Analysis
• Development and Testing
• Web applications
But its mostly used by industries which are governed
by security audits (PCI, SOX) or stored sensitive data
which can not be hosted in a public cloud due to
security reasons.

6. How do they work?
Based on virtualization.
A controller usually coordinates the provision and
keeps track of all the resources
(network, storage, virtual machines).
If more capacity is needed, more physical servers or
nertworks are added.

7. How do they work?

8. Eucalyptus
• First cloud platform released to the public (2008)
• Development cycle is every 2 years
• 100% compatible with Amazon web services API
• Mostly used by universities and business which use
AWS services.
• Uses as simple design architecture (controller –
node)
• Supports KVM, Xen and Vmware provisioning
• Interaction with Vmware and enterprise storage
require paid licenses.
• Written in Java and C++

9. OpenStack
• Released by rackspace and NASA in 2010.
• Faster development cycle (2 relases per year) but it
makes it really difficult to keep up with updates once
you install it.
• Has some compatibility with Amazon API.
• KVM is the hypervisor of choice.
• In theory supports Vmware, Xen.
• Complex design and architecture (multiple components
with interdependencies).
• Becoming more popular in last year.
• Originally used by rackspace to promote their
“Alternative to AWS”.
• Written in Python

10. CloudStack
• Released also in 2010 by Cloud.com, formerly
known as VMOps which now is part of Citrix.
• Citrix released the code to the Apache fundation in
2012 and as for now CloudStack is an Apache
project.
• Has it’s own API and its compatible with some of the
Amazon AWS api.
• Provides built-in virtual routers, firewalls and load
balancers.
• Has the best User interface of all the 3 projects.
• Hypervisor agnostic.
• Written in Java

11. Let’s play
DEMO

12. Which one is better?
It really depends on your needs.
Are you going to use AWS for production? – Go Eucalyptus
You wont be using AWS? – Openstack or Cloudstack
Do you need built in features now instead of waiting for the
community to build them? – Go Cloudstack
Have a large infrastructure and free hands? - Go
openstack

13. Questions?
Eucalyptus
https://www.eucalyptus.com/docs/eucalyptus/3.4/in
dex.html#install-guide/installing_euca_release.html
OpenStack
http://devstack.org
CloudStack
http://docs.cloudstack.apache.org/projects/cloudsta
ck-installation/en/latest/qig.html

14. Thanks