1.
INOVASI
INFORMATIKA
INDONESIA
War of Openstack PrivateWar of Openstack Private
Cloud DistributionCloud Distribution
Yusuf Hadiwinata Sutandar

2.
In 2008 NASA Create Nebula is an open source cloud computingIn 2008 NASA Create Nebula is an open source cloud computing
platform that was developed to provide an easily quantifiable andplatform that was developed to provide an easily quantifiable and
improved alternative to building additional expensive data centers andimproved alternative to building additional expensive data centers and
to provide an easier way for NASA scientists and researchers to shareto provide an easier way for NASA scientists and researchers to share
large, complex data sets with external partners and the public. Nebulalarge, complex data sets with external partners and the public. Nebula
is currently an Infrastructure-as-a-Service (IaaS) implementation thatis currently an Infrastructure-as-a-Service (IaaS) implementation that
provides scalable compute and storage for science data and Web-provides scalable compute and storage for science data and Web-
based applicationsbased applications
Once upon a timeOnce upon a time
In 2012, NASA shutdownIn 2012, NASA shutdown
Nebula based on theNebula based on the
result of 5-month testresult of 5-month test
that benchmarkedthat benchmarked
Nebula capabilitiesNebula capabilities
against those Amazonagainst those Amazon
and Microsoftand Microsoft

3.
Openstack was bornOpenstack was born
Then, in 2010, NASA andThen, in 2010, NASA and
Rackspace started workingRackspace started working
together on OpenStack –together on OpenStack –
which was initially based, atwhich was initially based, at
least in part, on NASA'sleast in part, on NASA's
Nebula. Things worked well,Nebula. Things worked well,
and in 2012 the OpenStackand in 2012 the OpenStack
Foundation was born. All ofFoundation was born. All of
which is a long way of saying “which is a long way of saying “
OpenStack comes from outerOpenStack comes from outer
space... kinda....”space... kinda....”

4.
Evolution of OpenStack -Evolution of OpenStack -
From Infancy to EnterpriseFrom Infancy to Enterprise
http://www.tiki-toki.com/timeline/entry/138134/OpenStack-http://www.tiki-toki.com/timeline/entry/138134/OpenStack-
History/#vars!date=2010-03-30_23:29:30!History/#vars!date=2010-03-30_23:29:30!

5.
Evolution of OpenStack -Evolution of OpenStack -
From Infancy to EnterpriseFrom Infancy to Enterprise

6.
SUSE, Red Hat and Canonical. These “BigSUSE, Red Hat and Canonical. These “Big
Three” of the Linux desktop (and server)Three” of the Linux desktop (and server)
world are here (among many others) in a bigworld are here (among many others) in a big
way. But each is taking their own, uniqueway. But each is taking their own, unique
approach to OpenStack.approach to OpenStack.
The "Big Three Kingdom"The "Big Three Kingdom"
Openstack distrosOpenstack distros

7.
Openstack Kingdom TerritoryOpenstack Kingdom Territory
on the Beginningon the Beginning

8.
Red Hat KingdomRed Hat Kingdom
Enterprises can start with RDO,Enterprises can start with RDO,
the community edition andthe community edition and
move to the enterprise versionmove to the enterprise version
post evaluation. With thepost evaluation. With the
integration of tools like Puppetintegration of tools like Puppet
and Foreman, Red Hat simplifiedand Foreman, Red Hat simplified
the OpenStack deployment.the OpenStack deployment.
Based on the same model of Fedora and RedBased on the same model of Fedora and Red
Hat Enterprise Linux, OpenStack from RedHat Enterprise Linux, OpenStack from Red
Hat is available in two flavors – 1) Red HatHat is available in two flavors – 1) Red Hat
Distribution of OpenStack (RDO) and, 2) RedDistribution of OpenStack (RDO) and, 2) Red
Hat Enterprise Linux OpenStack Platform.Hat Enterprise Linux OpenStack Platform.

9.
Based on a tool named Landscape, Canonical wantsBased on a tool named Landscape, Canonical wants
to simplify OpenStack deployment. According toto simplify OpenStack deployment. According to
Canonical, “Landscape provides a single, easy-to-Canonical, “Landscape provides a single, easy-to-
use, browser-based control panel, through which youuse, browser-based control panel, through which you
can manage your machines from anywherecan manage your machines from anywhere
Ubuntu KingdomUbuntu Kingdom
With a fully scriptable API, you canWith a fully scriptable API, you can
integrate it with your current Linuxintegrate it with your current Linux
management tools, extending theirmanagement tools, extending their
capabilities and giving you thecapabilities and giving you the
power to do more with fewerpower to do more with fewer
resources”. This sounds similar toresources”. This sounds similar to
Red Hat’s Foreman and Mirantis’Red Hat’s Foreman and Mirantis’
FuelFuel

10.
SUSE OpenStack Cloud makes it easier forSUSE OpenStack Cloud makes it easier for
customers to realize the benefits of a privatecustomers to realize the benefits of a private
cloud, saving them money and time they cancloud, saving them money and time they can
use to better serve their own customers anduse to better serve their own customers and
businessbusiness
Suse KingdomSuse Kingdom
The SUSE OpenStack CloudThe SUSE OpenStack Cloud
Administration Server can helpAdministration Server can help
overcome the challenges ofovercome the challenges of
setting up an OpenStack server.setting up an OpenStack server.
SUSE OpenStack Cloud 5 featuresSUSE OpenStack Cloud 5 features
a structured installation processa structured installation process
with an easy to use graphical userwith an easy to use graphical user
interfaceinterface

11.
Ubuntu Start InvasionUbuntu Start Invasion

12.
The New Kingdom:The New Kingdom:
Mirantis OpenStackMirantis OpenStack
Which brings us to Mirantis. As a relativelyWhich brings us to Mirantis. As a relatively
new vendor and entrant to the world of opennew vendor and entrant to the world of open
source, they have been considered by manysource, they have been considered by many
as a wildcard, by others as an annoyance.as a wildcard, by others as an annoyance.
There is no denying their momentum, withThere is no denying their momentum, with
almost 1000 employees around the world,almost 1000 employees around the world,
and wins with enterprise, telco and softwareand wins with enterprise, telco and software
companies, combined with six figure fundingcompanies, combined with six figure funding
from deep pockets such as Intel. Mirantis’from deep pockets such as Intel. Mirantis’
focus is 100% on OpenStack, period.focus is 100% on OpenStack, period.
Much of the focus at Mirantis is tackling keyMuch of the focus at Mirantis is tackling key
problems around deployment (hence theirproblems around deployment (hence their
contribution of the Fuel project), upgrade-ability (acontribution of the Fuel project), upgrade-ability (a
serious problem in OpenStack) and operationalserious problem in OpenStack) and operational
lifecycle management which is perhaps the biggestlifecycle management which is perhaps the biggest
challenge of allchallenge of all

13.
Openstack NowOpenstack Now
InvasionInvasion
OpenstackOpenstack
Market ShareMarket Share
20172017
Civilization continues toCivilization continues to
GrowGrow
https://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdfhttps://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdf

14.
Where are OpenStackWhere are OpenStack
civilization users located?civilization users located?

15.
Warrior and AbilityWarrior and Ability

16.
Warrior and AbilityWarrior and Ability

17.
The Strongest WarriorThe Strongest Warrior
Libvirt KVMLibvirt KVM
(x86)(x86)
11 2233
Libvirt QEMULibvirt QEMU
(x86)(x86)
XenServerXenServer
This is the Strongest Warrior with lot of AbilityThis is the Strongest Warrior with lot of Ability
and Skilland Skill
https://docs.openstack.org/nova/latest/user/support-matrix.htmlhttps://docs.openstack.org/nova/latest/user/support-matrix.html

18.
So which Kingdom Have / Support This 3 Greatest WarriorSo which Kingdom Have / Support This 3 Greatest Warrior
Kingdom WarriorsKingdom Warriors
XenServerXenServerLibvirt QEMULibvirt QEMU
(x86)(x86)
Libvirt KVMLibvirt KVM
(x86)(x86)
Esxi/VmwarEsxi/Vmwar
ee
Libvirt QEMULibvirt QEMU
(x86)(x86)
Libvirt KVMLibvirt KVM
(x86)(x86)
Esxi/VmwarEsxi/Vmwar
ee
Libvirt QEMULibvirt QEMU
(x86)(x86)
Libvirt KVMLibvirt KVM
(x86)(x86)
XenServerXenServerEsxi/VmwarEsxi/Vmwar
ee
Libvirt QEMULibvirt QEMU
(x86)(x86)
Libvirt KVMLibvirt KVM
(x86)(x86)
XenServerXenServerEsxi/VmwarEsxi/Vmwar
ee
Libvirt QEMULibvirt QEMU
(x86)(x86)
Libvirt KVMLibvirt KVM
(x86)(x86)
XenServerXenServerEsxi/VmwarEsxi/Vmwar
ee
Libvirt QEMULibvirt QEMU
(x86)(x86)
Libvirt KVMLibvirt KVM
(x86)(x86)
XenServerXenServer
Esxi/VmwarEsxi/Vmwar
ee
Libvirt QEMULibvirt QEMU
(x86)(x86)
Libvirt KVMLibvirt KVM
(x86)(x86)
XenServerXenServerEsxi/VmwarEsxi/Vmwar
ee
Libvirt QEMULibvirt QEMU
(x86)(x86)
Libvirt KVMLibvirt KVM
(x86)(x86)
XenServerXenServerEsxi/VmwarEsxi/Vmwar
ee
Libvirt QEMULibvirt QEMU
(x86)(x86)
Libvirt KVMLibvirt KVM
(x86)(x86)
XenServerXenServerEsxi/VmwarEsxi/Vmwar
ee
Libvirt QEMULibvirt QEMU
(x86)(x86)
Libvirt KVMLibvirt KVM
(x86)(x86)
XenServerXenServer LXCLXC
https://www.openstack.org/marketplace/distros/https://www.openstack.org/marketplace/distros/

19.
Type of Cloud are RunningType of Cloud are Running
OpenstackOpenstack

20.
Operating System for CloudOperating System for Cloud

21.
Openstack ComputeOpenstack Compute
Hypervisor are in useHypervisor are in use

22.
Warrior is not Just EnoughWarrior is not Just Enough
Wee need to Review:Wee need to Review:
●
Ease of DeploymentEase of Deployment
●
Ongoing operationsOngoing operations
●
Reliability at scaleReliability at scale
●
Developer productivityDeveloper productivity
●
Open source approach &Open source approach &
community participationcommunity participation
●
Lifecycle managementLifecycle management
●
ExtensibilityExtensibility
●
InteroperabilityInteroperability
●
Completeness of offeringCompleteness of offering

23.
How the Kingdom is builtHow the Kingdom is built
Installation ProceduresInstallation Procedures
●
This review consists of the overall processThis review consists of the overall process
for getting both distributions from barefor getting both distributions from bare
metal and an ISO to an up-and-runningmetal and an ISO to an up-and-running
OpenStack environment capable ofOpenStack environment capable of
launching instances and workloads.launching instances and workloads.
Scoring Metrics:Scoring Metrics:
●
Guided vs manual installation stepsGuided vs manual installation steps
●
Time required for installation and deploymentTime required for installation and deployment
●
Frequency and types of tripping points/issuesFrequency and types of tripping points/issues
●
Troubleshooting requiredTroubleshooting required

24.
Warrior is not Just EnoughWarrior is not Just Enough
Lifecycle managementLifecycle management
●
Continuing operations for OpenStack is a differentContinuing operations for OpenStack is a different
challenge to meet than the initial configuration andchallenge to meet than the initial configuration and
deployment, so we have broken it out separately. Indeployment, so we have broken it out separately. In
this category, we look at the abilities for eachthis category, we look at the abilities for each
distribution to scale up and down, patch an existingdistribution to scale up and down, patch an existing
environment, and eventually upgrade it to the nextenvironment, and eventually upgrade it to the next
major revision.major revision.
Scoring Metrics:Scoring Metrics:
●
Ease and automation of scaling the physical infrastructure up/downEase and automation of scaling the physical infrastructure up/down
●
Patching methods and documentationPatching methods and documentation
●
Method and documentation for updatingMethod and documentation for updating
●
Managing multiple environmentsManaging multiple environments

25.
Warrior is not Just EnoughWarrior is not Just Enough
Downstream Testing & Stability ImprovementsDownstream Testing & Stability Improvements
●
In this review we compare theIn this review we compare the
stability enhancements of thestability enhancements of the
distributions. We could try todistributions. We could try to
use metrics such as failures atuse metrics such as failures at
real customers or number ofreal customers or number of
critical bugs filed by customers,critical bugs filed by customers,
but generally this data is hard tobut generally this data is hard to
come by or proprietary (or both).come by or proprietary (or both).
So instead, we will scoreSo instead, we will score
reliability at scale based onreliability at scale based on
these four factors:these four factors:
Scoring Metrics:Scoring Metrics:
●
Validation testingValidation testing
●
PackagingPackaging
●
Reference architecturesReference architectures

26.
Warrior is not Just EnoughWarrior is not Just Enough
Developer productivityDeveloper productivity
●
OpenStack, or any private cloud, is not an end in itself.OpenStack, or any private cloud, is not an end in itself.
Most companies build it to enable workloads likeMost companies build it to enable workloads like
developer productivity tools, big data, NFV, etc. We seedeveloper productivity tools, big data, NFV, etc. We see
unlocking developer productivity as the most importantunlocking developer productivity as the most important
use case, and therefore we made it a comparison review.use case, and therefore we made it a comparison review.
Scoring Metrics:Scoring Metrics:
●
PaaS supportPaaS support
●
CMP supportCMP support
●
Container framework supportContainer framework support
●
App Catalog supportApp Catalog support

27.
Warrior is not Just EnoughWarrior is not Just Enough
Open Source & CommunityOpen Source & Community
●
Users get creative when trying to figure out which distro toUsers get creative when trying to figure out which distro to
buy. One way they figure this out is by studying thebuy. One way they figure this out is by studying the
contributions of the vendor and to see how well they playcontributions of the vendor and to see how well they play
in the community. The arguments for open source are wellin the community. The arguments for open source are well
known; the ability to ‘look under the hood’, so to speak,known; the ability to ‘look under the hood’, so to speak,
and freely change and customize the code to fit yourand freely change and customize the code to fit your
requirements. But not all players in the open sourcerequirements. But not all players in the open source
community are created equalcommunity are created equal
Scoring Metrics:Scoring Metrics:
●
Open-source approachOpen-source approach
●
Contributions by commitsContributions by commits
●
Contributions by bug fixesContributions by bug fixes
●
Thought leadershipThought leadership

28.
Warrior is not Just EnoughWarrior is not Just Enough
Developer productivityDeveloper productivity
●
OpenStack, or any private cloud, is not an end inOpenStack, or any private cloud, is not an end in
itself. Most companies build it to enable workloadsitself. Most companies build it to enable workloads
like developer productivity tools, big data, NFV, etc.like developer productivity tools, big data, NFV, etc.
We see unlocking developer productivity as the mostWe see unlocking developer productivity as the most
important use case, and therefore we made it aimportant use case, and therefore we made it a
comparison review.comparison review.
Scoring Metrics:Scoring Metrics:
●
PaaS supportPaaS support
●
CMP supportCMP support
●
Container framework supportContainer framework support
●
App Catalog supportApp Catalog support

29.
Warrior is not Just EnoughWarrior is not Just Enough
ExtensibilityExtensibility
●
This review is about the ability for users to customizeThis review is about the ability for users to customize
and extend their OpenStack solution. This involvesand extend their OpenStack solution. This involves
the ability to choose from lists of third-party pluginsthe ability to choose from lists of third-party plugins
for their specific use case and the capability offor their specific use case and the capability of
developing their own unique plugin for deployingdeveloping their own unique plugin for deploying
and managing their environments.and managing their environments.
Scoring Metrics:Scoring Metrics:
●
Catalog of pluginsCatalog of plugins
●
Availability of aAvailability of a
documented frameworkdocumented framework
for DIY pluginsfor DIY plugins

30.
The Kingdom IntegrationThe Kingdom Integration
InteroperabilityInteroperability
●
OpenStack requires numerous integrations “above” theOpenStack requires numerous integrations “above” the
stack in terms of PaaS, containers, CMP, and otherstack in terms of PaaS, containers, CMP, and other
middleware, and “below” the stack in terms of hypervisors,middleware, and “below” the stack in terms of hypervisors,
storage, networking/SDN, and so on. This is one section thatstorage, networking/SDN, and so on. This is one section that
we couldn’t get hard evidence supporting the numbers ofwe couldn’t get hard evidence supporting the numbers of
partners for Red Hat’s distribution across the technologypartners for Red Hat’s distribution across the technology
silos, so we are focusing on the transparency of thesilos, so we are focusing on the transparency of the
validation process.validation process.

31.
Warrior is not Just EnoughWarrior is not Just Enough
Completeness of offeringCompleteness of offering
●
In comparing the completeness of the distribution offeringIn comparing the completeness of the distribution offering
we look beyond the software itself at aspectswe look beyond the software itself at aspects
surrounding the use of the product: available training,surrounding the use of the product: available training,
professional services, and support.professional services, and support.
Scoring Metrics:Scoring Metrics:
●
TrainingTraining
●
Professional services and supportProfessional services and support
offeringsofferings
●
SUSE Certified Administrator (SCA) in OpenStack CloudSUSE Certified Administrator (SCA) in OpenStack Cloud
●
Red Hat Certified System Administrator 1 & 2in Red HatRed Hat Certified System Administrator 1 & 2in Red Hat
OpenStackOpenStack
●
Mirantis: OCM50/100: OpenStack CertificationMirantis: OCM50/100: OpenStack Certification
●
Ubuntu: OpenStack FundamentalsUbuntu: OpenStack Fundamentals

32.
The Greatest KingdomThe Greatest Kingdom
Ease of DeploymentEase of Deployment 8 7 8 7
Ongoing operationsOngoing operations 7 7 7 7
Reliability at scaleReliability at scale 8 8 6 7
Developer productivityDeveloper productivity 7 7 8 7
Open source approachOpen source approach
community participationcommunity participation
7 8 7 6
Lifecycle managementLifecycle management 7 7 7 7
ExtensibilityExtensibility 7 8 8 7
InteroperabilityInteroperability 7 7 8 7
Completeness of offeringCompleteness of offering 7 7 8 7
Total PointTotal Point 65 66 67 62

33.
Let's discuss the top 2Let's discuss the top 2
Ubuntu Kingdom vs Mirantis Kingdom –Ubuntu Kingdom vs Mirantis Kingdom –
Who`s the winnersWho`s the winners
●
Baremetal ProvisioningBaremetal Provisioning
●
Openstack Deployment ModelOpenstack Deployment Model
●
Customizing Openstack RolesCustomizing Openstack Roles

34.
Ubuntu vs MirantisUbuntu vs Mirantis
Baremetal ProvisioningBaremetal Provisioning
Transform your physical infrastructure into a cloudTransform your physical infrastructure into a cloud
MAAS is a server provisioning tool which offersMAAS is a server provisioning tool which offers
complete automation of your physical servers forcomplete automation of your physical servers for
amazing data centre operational efficiency. Onamazing data centre operational efficiency. On
premises, open source and supported.premises, open source and supported.
Fuel is an open source deployment and management tool forFuel is an open source deployment and management tool for
OpenStackOpenStack
Fuel brings consumer-grade simplicity to streamlineFuel brings consumer-grade simplicity to streamline
and accelerate the otherwise time-consuming, oftenand accelerate the otherwise time-consuming, often
complex, and error-prone process of deploying,complex, and error-prone process of deploying,
testing and maintaining various configuration flavors oftesting and maintaining various configuration flavors of
OpenStack at scaleOpenStack at scale

35.
Ubuntu vs MirantisUbuntu vs Mirantis
Openstack Deployment ModelOpenstack Deployment Model
OpenStack AutopilotOpenStack Autopilot
The Canonical OpenStack installer is the easiest wayThe Canonical OpenStack installer is the easiest way
to build a reference architecture OpenStack privateto build a reference architecture OpenStack private
cloud.cloud.
Fuel is an open source deployment and management tool forFuel is an open source deployment and management tool for
OpenStackOpenStack
Fuel is an open-source tool that enables you to easily and quicklyFuel is an open-source tool that enables you to easily and quickly
provision multiple OpenStack environments, as well as manageprovision multiple OpenStack environments, as well as manage
your environments after deployment. You can install Fuel andyour environments after deployment. You can install Fuel and
deploy your OpenStack environment on a virtual platform such asdeploy your OpenStack environment on a virtual platform such as
Oracle VirtualBox or VMware vSphere for testing purposes, asOracle VirtualBox or VMware vSphere for testing purposes, as
well as on bare-metal hardware for production.well as on bare-metal hardware for production.

36.
Ubuntu vs MirantisUbuntu vs Mirantis
Customizing Openstack RolesCustomizing Openstack Roles
Juju is a next generation service orchestration frameworkJuju is a next generation service orchestration framework
uju is a state-of-the-art, open source, universal modelling tool foruju is a state-of-the-art, open source, universal modelling tool for
service oriented architectures and application oriented deployments.service oriented architectures and application oriented deployments.
Juju allows you to deploy, configure, manage, maintain, and scaleJuju allows you to deploy, configure, manage, maintain, and scale
cloud applications quickly and efficiently on public clouds, as well ascloud applications quickly and efficiently on public clouds, as well as
on physical servers, OpenStack, and containerson physical servers, OpenStack, and containers
There is no Service modeling on MirantisThere is no Service modeling on Mirantis

37.
Ubuntu vs MirantisUbuntu vs Mirantis
Summary ResultSummary Result
Ubuntu Openstack SolutionUbuntu Openstack Solution
Ubuntu combine 3 Tools MaaS, LandscapeUbuntu combine 3 Tools MaaS, Landscape
(autopilot) to Provision, deploy and manage(autopilot) to Provision, deploy and manage
openstack roles. Ubuntu also support Serviceopenstack roles. Ubuntu also support Service
Modeling via JujuModeling via Juju
Mirantis Openstack SolutionMirantis Openstack Solution
Mirantis using Single tool to Provision, deploy,Mirantis using Single tool to Provision, deploy,
and Manage Openstack. The GUI is userand Manage Openstack. The GUI is user
friendly but Mirantis doesnt support Servicefriendly but Mirantis doesnt support Service
ModelingModeling

38.
Type of Cloud are RunningType of Cloud are Running
OpenstackOpenstack
Topic pada SlTopic pada Slide Iniide Ini

39.
Graha BIP 6th
Floor
Jl. Jend. Gatot Subroto Kav. 23
Jakarta 12930, Indonesia
Phone : (62) 21 290 23393
Fax : (62) 21 525 8065
info@i-3.co.id
www.i-3.co.id
INOVASI
INFORMATIKA
INDONESIA
Inovasi Informatika Indonesia I3_ID