Workshop - Best of Both Worlds_ Combine KG and Vector search for enhanced R...
SM16 - Can i move my stuff to openstack
1. Can I Move My Stuff To OpenStack?
Intro to OpenStack
Comparing OpenStack to VMware and Hyper-V
http://tpittman.wordpress.comTony Pittman @pittmantony
2. www.siriuscom.com 5/17/2016 2
Agenda
• Introduction
• What is OpenStack?
• Comparing to VMware and Hyper-V
• Where does OpenStack fit?
• What else is out there?
• Questions
• Closing
3. www.siriuscom.com 5/17/2016 4
What is OpenStack?
• Collection of projects
• Open source
• Open standards
• AWS-style Infrastructure-as-a-Service (IaaS) private or
public cloud
4. www.siriuscom.com 5/17/2016 5
Who is OpenStack for?
• Institutions and service providers with physical
hardware that they'd like to use for large-scale cloud
deployments
• Companies who have specific requirements which
prevent them from running in a public cloud
• OpenStack is probably not something that the average
business would consider deploying themselves yet.
-- from FAQ on openstack.org
5. www.siriuscom.com 5/17/2016 6
OpenStack Releases and Projects
• New Release twice a year
• Each Release specifies a version of each project
• Each Project is developed separately
• Projects updated constantly, between Releases
6. www.siriuscom.com 5/17/2016 7
OpenStack Releases
• Releases named after cities, kinda
• Alphabetical order
• Kilo – Security-supported
• Liberty – Security-supported
• Mitaka – Current stable release - as of April 7
• Newton – Under Development – design in Austin 2 weeks ago
• Ocata - Future
7. www.siriuscom.com 5/17/2016 8
OpenStack Core Projects
Nova
Compute
Neutron
Software defined
networking
Keystone
Identity
management
Cinder
Block based
storage
Glance
Image repository
(templates)
Swift
Object based
storage
9. www.siriuscom.com 5/17/2016 10
Nova
• This is the compute layer
• Terminology:
• Node = physical group of resources, usually 1 host
• Host Aggregate = group of similar resources, in VMware terms a
“cluster”, Instances are deployed onto Host Aggregates.
• Availability zone = logical segregation for physical isolation or
redundancy
• Instance = Virtual machine
• Flavor = predefined size of VM
11. www.siriuscom.com 5/17/2016 12
Nova
• Usually based on KVM as a hypervisor.
• A Nova node = Single KVM host
• This is “bread and butter” OpenStack
• When people think about “Replacing VMware”, this is
usually what they’re thinking about
13. www.siriuscom.com 5/17/2016 14
Neutron
• Software Defined Networking
• Similar to VMware NSX
• NOT similar to Cisco ACI
• Based on VXLAN
• Was very unstable a couple years ago, got a re-write, now
pretty good
14. www.siriuscom.com 5/17/2016 15
Neutron
• Fixed IP gets assigned to each instance when instance is
created
• The rest of the network is unaware of this subnet and these IP’s
• Floating IP gets assigned to an instance if needed
• Instance is unaware of this IP
• NAT is used to map these together
• NLB through LBaaS functionality
15. www.siriuscom.com 5/17/2016 16
Storage
• Ephemeral storage
• Accessible from within the VM, deleted when VM is terminated
• Swift (object)
• Accessible anywhere via API
• Cinder (block)
• Accessible from within the VM, as a block device
• Storage mfg write their own Cinder drivers
• These are used in things like EMC VIPR Controller
19. www.siriuscom.com 5/17/2016 20
Comparing to VMware and Hyper-V
VMware & Hyper-V
• Designed to run unique
OS instances
• Operate like traditional
open systems
environment
• Humans, installing OS’s
from a pretty GUI
OpenStack
• Designed to run generic,
disposable OS instances
• Deploy instances
programmatically
• Orchestration workflows
deploy OS’s that need
little human interaction
20. www.siriuscom.com 5/17/2016 21
Comparing to VMware and Hyper-V
• Not really designed for Windows support
• Not many environments running Windows VM’s on OpenStack
• That means not much knowledge out there about Windows on
OpenStack
• No Windows cluster support
• Don’t expect good high-availability options
• Use vSphere as the Nova hypervisor if HA is needed
(but in that case, why not vRA instead of OpenStack?)
• These two things rule out OpenStack for most customers
22. www.siriuscom.com 5/17/2016 23
Where does OpenStack fit?
• Institutions and service providers with physical
hardware that they'd like to use for large-scale cloud
deployments
• Companies who have specific requirements which
prevent them from running in a public cloud
• OpenStack is probably not something that the average
business would consider deploying themselves yet.
-- from FAQ on openstack.org
23. www.siriuscom.com 5/17/2016 24
Where does OpenStack fit?
• Organizations with application development teams
• Developing cloud native apps primarily on Linux
• Need to run apps on-premises
• Want to empower their developers
• Want Infrastructure as a Service (VM granularity, in
contrast to containers or baremetal)
24. www.siriuscom.com 5/17/2016 25
What Else Is Out There?
• Public cloud
• If considering OpenStack, it’s an on-premises version of AWS /
Azure / Google Cloud Platform
• When considering next platforms:
• 3rd platform / webscale / cloud native
• Containers
• Lighter than VM’s
• If considering OpenStack, could make more sense to go Containers
• 2017 this session might be about Docker instead
30. www.siriuscom.com 5/17/2016 31
What do you need to get started?
“An enthusiastic sysadmin, an anchor
tenant, and metrics to measure success
against”
31. www.siriuscom.com 5/17/2016 32
Containers and Bare Metal
Lots of focus on using OpenStack for:
• IaaS for containers and/or PaaS
• Baremetal deployment via Ironic, for PaaS or containers
32. www.siriuscom.com 5/17/2016 33
Article on TechReckoning :
1. If you haven't at least dipped your toes into
OpenStack yet, then it's not for you right now.
2. I still wonder, however, if OpenStack is
solving 2010's problem, not 2020's.
TechReckoning article
Austin
Bexar
Cactus
Diablo
Essex
Folsom
Grizzly
Havana
Icehouse
Juno
Kilo
Liberty
Mitaka (Tokyo)
Newton (Austin)
Ocata (Barcelona)
Core services are defined by DefCore Committee
Trove = Databasse
Sahara = Elastic Map Reduce
Zaqar = Messaging Service
Designate = DNS Service
Barbican = Key Management
Magnum = Containers
Murano = Application Catalog
Congress = Governance
Blueprints / workflows – Cloudify
Python & API’s - have to understand these thoroughly. A lot of google searches when looking for help return nothing or end up on Python message board
DNS in a NAT defined world
CloudCruiser for chargeback
SaltStack or Ansible (Python based), or Puppet or Chef (very complex)