Suse Cloud, Openstack and Virtualisation for the

EnterpriseDatalounges Oy @datalounges

http://www.datalounges.com

Agenda• Introduction and Datalounges background

• Todays market: shark eat shark

• Openstack in the enterprise: ready or not

• Suse Cloud, reasons behind the choice

• Infrastructure design

• Implementation, the nitty gritty story

• What Enterprise wants, Enterprise gets

• Target Market / Target Products

• Questions?

Background: Datalounges• Decades of Multinational Corporate IT in experience

• Frustrated with vendor offering and sales tactics with lock-in

• Surveyed large (1000+ employees) Enterprise customer about current Cloud offering and what is wanted

• Catering Enterprise: a whole new level of pain with HUGE rewards (not monetary).

Todays Market, Shark eat Shark

• Many Cloud vendors, all the same product

• vServer cheap at first glance, hidden costs ridiculous, example: Azure, Amazon, digital ocean

• Same business model for small businesses, not easily adjustable for enterprise.

• Enterprise = budgeting, budgeting != flexible costs

• Vendor approach is: Go in on small budget and speed, make customer adjust to us.

• Overselling in some cases is not anymore based on efficiency but on cash raking. Ratios of 24-32/1 Physical core is not unheard of, some vendors go as high as 48-64/1

• Buzzwords like SSD, instant server etc. dominate the market.

Openstack for the enterprise, ready or not

Positives:

• Short answer: yes… mostly

• Openstack provides flexibility, reliability and elasticity combined with speed that matches near hardware platform

• Opensource and a proper governance and the growth potential makes Openstack one of the most ideal OS Products for Enterprise.

• Ready “distributions” provide Enterprise with support options.

• The concept for the user to forget the hardware layer completely and be able to spin up VMs based on quotas is very appealing.

Openstack for the enterprise, ready or not

Challenges:

• Openstack is NOT easy to maintain

• Monitoring Openstack is non-existent (DIY or a combination of many tools, NONE of which is properly documented)

• To be effective and reliable, Openstack requires a good selection of hardware before hosting a VM can even start.

• Proof of concepts are quite difficult and require a steep learning curve.

Suse Cloud, reasons behind the choice

• Enterprise offering with Enterprise support

• Ease of maintaining and deployment of new resources (Crowbar)

• Well documented setup

• SAP and Microsoft support SLES -> broad support on horizontal level -> flexibility for customers

• Multi-Hypervisor support out of the box

• Driver Support for Windows

• Designed for large environments with a lot of flexibility

Infrastructure Design: Hardware

• Blade servers in Multiple Blade Centers

• Rack Servers for additional computing power

• Storage over Fibre-channel

• 10gbit Ethernet for Blades for fast deployment

• Multiple gigabit Internet interfaces for reliability and speed.

• PB possibility storage, across multiple channels for resiliency

Infrastructure Design: Software

• Suse Cloud with Suse Manager for Patch deployment and maintenance

• CePH Storage backend with Glance and Cinder interfacing with it

• Customized Openstack Dashboard (why re-invent the wheel)

• LBaaS, VPNaaS - Site to site and via OpenVPN appliance for remote access

• Project/Customer Environment approach, transparently granting access via VPN tunnels to own environments

• Full Console access to server,Windows 2008, R2, 2012, 2012R2 support and image deployment

• Customzied Windows images for customer (branded, pre-configured with specific toolchains etc.)

• Combination of ceilometer and other monitoring tools (working on an Openstack monitoring tool which interfaces to ceilometer)

Implementation, the nitty gritty story

• Base install of Admin node done via Admin appliance from Suse Studio

• Networking in small steps with long design times

• Several attempts failed due to “human” error

• Research and performance test, failed hardware

• Failover tests, “plug the chord” tests

• Burning the house down!

What Enterprise wants, Enterprise gets

• Enterprise largely runs on: Windows, Active Directory, Exchange, SAP

• Enterprise wants flexibility on the vendors side

• Enterprise wants to control the resources and be able to manage their own “Virtual Datacenter”

• Enterprise wants proper budgeting

• Enterprise wants reliability

• Achievable through: Connect::Expand::Grow philosophy

• Connect to your Cloud environment transparently as if it were your own network

• Expand your network and infrastructure according to your needs

• Grow your network and your business with resources on demand

Target Market/ Target Products

Target Market:

• Customers who know what they wantand are looking for environments, not VMs

• Medium to Large companies that have the need to grow their infrastructure

• Development Companies who need test and development environments (SAP, Microsoft products)

Target Product examples:

• Delayed replication environments

• Upgrade path environments

• Test and development environments

• Production environments that need flexibility and reliability

Product example: resource environment

Baremetal Systems

Environment

Customer Network

Dashboard Interface as

Control

Customer Network

Resource Pool• RAM • Cores • Storage( Block and Object) • IP Addresses

VM1 VM2 VM3

Questions?

http://www.datalounges.com@datalounges