OpenStack Technology

Breaking the Enterprise Barrier

© 2014 & 2015 Hewlett-Packard Development Company, L.P.

Published by:

HP Press

660 4th Street, #802

San Francisco, CA 94107

All rights reserved. No part of this book may be reproduced or transmitted in any form

or by any means, electronic or mechanical, including photocopying, recording, or by any

information storage and retrieval system, without written permission from the

publisher, except for the inclusion of brief quotations in a review.

WARNING AND DISCLAIMER

This book is designed to provide information about OpenStack cloud computing and HP

Helion OpenStack technology. Every e]ort has been made to make this book as

complete and as accurate as possible, but no warranty or ^tness is implied. The

information is provided on an “as is” basis.

The author, HP Press, and Hewlett-Packard Development Company, L.P., shall have

neither liability nor responsibility to any person or entity with respect to any loss or

damages arising from the information contained in this book or from the use of the

discs or programs that may accompany it. The opinions expressed in this book belong

to the author and are not necessarily those of Hewlett-Packard Development Company,

L.P. Readers should be aware that Internet websites o]ered as citations and/or sources

for further information may have changed or disappeared between the time this is

written and when it is read.

TRADEMARK ACKNOWLEDGEMENTS

All terms mentioned in this book that are known to be trademarks or service marks

have been appropriately capitalized. HP Press or Hewlett Packard Inc. cannot attest to

the accuracy of this information. Use of a term in this book should not be regarded as

a]ecting the validity of any trademark or service mark.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

The OpenStack Word Mark and OpenStack Logo are either registered trademarks/

service marks or trademarks/service marks of the OpenStack Foundation, in the United

States and other countries and are used with the OpenStack Foundation's permission.

We are not a]iliated with, endorsed or sponsored by the OpenStack Foundation, or the

OpenStack community. Pivotal and Cloud Foundry are trademarks and/or registered

trademarks of Pivotal Software, Inc. in the United States and/or other countries.

FEEDBACK INFORMATION

At HP Press, our goal is to create in-depth technical books of the best quality and value.

Each book is crafted with care and precision, undergoing rigorous development that

involves the expertise of members from the professional technical community.

Readers feedback is a continuation of the process. If you have any comments regarding

how we could improve the quality of this book, or otherwise alter it to better suit your

needs, you can contact us through email at hppress@epac.com. Please make sure to

include the book title in your message.

We appreciate your feedback.

HP HEADQUARTERS

Hewlett-Packard Company

3000 Hanover Street

Palo Alto, CA 94304

USA

Phone: (+1) 650-857-1501

Fax: (+1) 650-857-5518

HP, COMPAQ and any other product or service name or slogan or logo contained in the HP Press

publications or website are trademarks of HP and its suppliers or licensors and may not be

copied, imitated, or used, in whole or in part, without the prior written permission of HP or the

applicable trademark holder. Ownership of all such trademarks and the goodwill associated

therewith remains with HP or the applicable trademark holder. Without limiting the generality

of the foregoing: a. Microsoft, Windows and Windows Vista are either US registered trademarks

or trademarks of Microsoft Corporation in the United States and/or other countries; and b.

Celeron, Celeron Inside, Centrino, Centrino Inside, Core Inside, Intel, Intel Logo, Intel Atom, Intel

Atom Inside, Intel Core, Intel Core Inside, Intel Inside Logo, Intel Viiv, Intel vPro, Itanium,

Itanium Inside, Pentium, Pentium Inside, ViiV Inside, vPro Inside, Xeon, and Xeon Inside are

trademarks of Intel Corporation in the U.S. and other countries.

'

CONTENTS

Chapter 1 Introduction

Why we wrote this bookWho this book is forWhat you will learn

Chapter 2 A case for cloud computing

The new reality of ITWe are drowning in dataPeople adopt more and more mobile devicesWe expect security and accountabilityCloud becomes the storage medium of choice

Cloud computing to the rescueThe world around us is getting smarterWe expect our data centers to shrink andexpand on demandMobile apps are hungry for bandwidthWe want to know moreWhat do we do now?What the cloud needs to deliver

Chapter 3 Why we need open source clouds

Hybrid deliveryOpen standards are a good thingAn operating system for the cloud

Why HP chose OpenStack technologyNo love for proprietary cloudsOpen = TrustedMaturityAppeal to our own peopleDynamic growthIndustry-wide supportGlobal communitySound governance model

An easy decision to make

Chapter 4 Just how serious is HP about OpenStack technology?

HP’s contributions to the OpenStack projectInvolved from the beginningProject governanceFinancial support

Commitment to the project governance and processesHP is always one of the top <ve code contributorsto OpenStackDedicated sta;Successful commercial deployments of OpenStacktechnologyTransparency and accountability

Expert leadershipCoopetition and giving back to the communityHP Helion

An all-hands e;ortWhat is HP Helion?It’s a journey

Chapter 5 What is HP Helion OpenStack?

Why we created HP Helion OpenStackMain advantages of HP Helion OpenStack

Simple installationOpenStack technology at scaleWell-paced innovationSimpli<ed managementAutomated delivery of additional functionality and contentInteroperabilityGood <t for all data centers, large and smallSimple data sovereigntyLower cost of migrationA truly open cloud operating systemModel once, deploy everywhereRapid provisioningSharing resourcesMulti-cloud provider supportHybrid provisioningSupported by HP

HP Helion PlatformPartner and ISV support

Chapter 6 Inside HP Helion OpenStack

The architecture of HP Helion OpenStackThe HP Helion OpenStack core servicesHP Helion OpenStack value-added servicesAdministering HP Helion OpenStack

Chapter 7 Use cases

Accelerate application testing and developmentDevelop and deploy cloud-native applicationsManage large-scale object storage

Chapter 8 Where do I go from here?

Online resources

Chapter 1

IntrIntroductionoduction

In this chapter✓ Why we wrote this book

✓ Who this book is for

✓ What you will learn

Why we wrote this book

Welcome!

We wrote this book to introduce HP’s views on the future of data center models,

cloud computing, and OpenStack technology and to introduce our foundational

platform, which is based on OpenStack software and provides a common

architecture for hybrid delivery across the HP Helion portfolio.

This is the story of our cloud journey, an explanation of the choices we made, and an

invitation to join us on that journey into the future. We explain why we chose

OpenStack technology, and how we are going to support our clients on their own

cloud computing journey.

Who this book is for

If you are a CTO, data center administrator, systems architect, or an IT professional-

looking for an enterprise-grade, hybrid delivery, cloud computing solution that is

open, trusted, and reliable, we wrote this book for you. It is also for (and dedicated

to) all you pioneers who fearlessly pushed the needle forward and moved the

industry to the next major phase of its technology lifecycle. We had a great time

producing this book, and we hope you will enjoy reading it.

What you will learn

This book explains how cloud computing is a solution to the problems facing data

centers today and to highlight the cutting-edge technology (including OpenStack

cloud computing) that HP helped bring to its current state. Once you more fully

understand this relatively new technical approach, we believe you too will see that it

is the right choice for the future of cloud computing.

In the following pages you will learn about the challenges facing data centers today,

why cloud computing is the best technology we have to cope with those challenges,

and why OpenStack technology provides the best cloud computing operating system

for your data center. You will learn how deeply involved in OpenStack cloud

computing we are, what cloud computing means for the future of HP, and how we

built HP Helion OpenStack—an enterprise-grade OpenStack distribution ready to

help you realize your hybrid cloud delivery needs.

Chapter 2

A case fA case for clor clooud cud compomputinguting

In this chapter✓ The new reality of IT

✓ The need for a new data center model

✓ A case for cloud computing

The new reality of ITAre you ready? The way you deploy, manage, and use your IT infrastructure is aboutto change.

Cloud computing is about to take over data centers around the world and dispel theold ways of thinking about IT infrastructure. And we are not talking about takingover the odd surviving mainframes, but the data centers designed to meet thedemands of the old (yes, already old!) client-server model.

Don’t believe it? Remember the mighty mainframes that ruled the data processingworld and stared down at the tiny UNIX boxes? They are gone now. Client-serverdata centers are on the same path.

Where are they now?Mainframes turned out to be very similar to dinosaurs. Too big, too slow, notcapable of adapting to the changing world, and way too expensive to buyand run. Buying a mainframe was like building a power plant—onlygovernments and banks could aOord that kind of investment. Thirty yearsago it seemed like they would be with us forever. Yet, they are practicallyextinct today.

A feisty, young challenger—the client-server model based on UNIX, sealedthe fate of the mainframe. It looked like a toy at Prst, but then Oracle,Sybase, and Informix showed the world that the client-server architecturewas a much more aOordable business proposition. So good, in fact, that thearchitecture made it possible to build numerous Internet-based businesses.It drove demand for new, bigger data centers all over the world. UNIX was in,and mainframes were out.

Today, only a few universities bother to teach courses that cover themainframe architecture, and those that do it spare mainframes some timeonly because they consider that knowledge essential to understanding theorigins of the modern data center. Much like the dinosaur—mainframes arelong gone, but studying their fossils helps us better understand other livingorganisms.

Such is life …

Cloud computing is aboutto take over data centersaround the world.

The old adage “nothing is constant except change” couldnot be more apt than when applied to the world of IT.Today, the world of IT must deal with one of the greatestshifts the data center business has ever seen. The highly

dynamic, unpredictable, and rapidly growing nature of demand for compute,networking, and storage capabilities created a need for this dramatic change.The simple fact is the traditional data center architectures no longer deal eOectivelywith the new reality of IT—a fact that is beginning to dawn on data center facilities’providers and users worldwide.

Four trends dePne the new style of IT: Big Data, mobility, security, and cloud.

We are drowning in dataPundits continue to argue about what Big Data is exactly. Meanwhile, every day wepretend to cope with this data tsunami of our own making.

The days of people performing data entry on myriads of PCs is long gone. No humanarmy could keep up with all the data collected these days.

Smart phones, smart buildings, smart appliances, smart cities, smart cars, smartroads, combined with country-wide CCTV networks, traOic monitoring networks,environmental monitoring networks, industrial monitoring networks—thesetechnologies barely existed Pve years ago. Today, all of these and more run untoldnumbers of data-producing and data-crunching applications all day, every day.

Each new device or app generates gigabytes—even terabytes—of data per day. Allthat data needs its own backend capable of sending, requesting, and processinginformation on a massive scale, stretching the limits of the old hardware, software,and data centers. Quite frankly, we need to be planning for the exabyte age becausethat future is rapidly unfolding before our eyes.

Check out these published statistics:

• Scientists at CERN run experiments that generate over one petabyte of data persecond during Large Hadron Collider experiments.1

Currently, most of that data has to be discarded because they cannot store andprocess it all for technical and Pnancial reasons. Even with international funding,it is too expensive to pay for a massive, purpose-built IT infrastructure capable ofcapturing and processing vast amounts of data generated in a split second.

• Twitter delivers 500 million tweets per day.2

If every tweet is roughly a 4KB JSON object, it means that Twitter has to handleover 2 TB worth of data every day. All that data needs to be stored, delivered, andanalyzed. It cannot be lost, and it must be available for retrieval in the future.The 2 TB estimate does not include images and other forms of media Twitterstores and delivers using its infrastructure. It also does not include the centralprocessing unit (CPU) cycles and network resources necessary to create andresolve links using the Twitter URL shortener. And let us not forget that Twitterdoes it all in real time, without dropping data even when a global event causes asudden spike in demand for its resources.

• Instagram captures, stores, and delivers over 2.5 billion likes per day.3

Instagram likes are a small, but very important subset of the data thatInstagram’s backend has to handle with great care and speed. Each like is a simplemessage represented by a JSON object, possibly under 1 KB. But even if it is thattiny, Instagram is still dealing with at least 2.5 TB of like data per day. That datacarries important information about who likes what, when, and on what platformthe like was created and delivered.

• Facebook manages 600 TB of data per day.4

With video, photos, texts, and likes from more than 1 billion users worldwide,Facebook handles a daily data blizzard of around 600 TB. All that data has to becaptured, sifted, served, and warehoused in a fashion that takes into accountFacebook’s growth. On account of its highly visual nature, Facebook’sinfrastructure needs are even more sophisticated than that of Twitter.

Each new device or appgenerates gigabytes-eventerabytes-of data per day.

All these represent some of the extreme cases, yet anymobile application or online service that becomespopular faces similar problems of availability, capacity,and scalability—usually when they are least prepared

for it. We see this happen when someone creates something trendy and its adoptionspreads like wildPre. Or the opposite extreme also happens when the next big thingmeans that old favorites get abandoned and lots of expensive servers that used toprovide those old favorites sit idle.

People adopt more and more mobile devicesWith feature phones being replaced by smart phones and personal computers beingreplaced by tablets, the use of always-on, always-connected devices is growingexponentially worldwide. People often carry a phone or two plus a tablet and maybeeven a smartwatch.

These billions of devices need to be connected 24/7, making capacity planning anightmare at best. No one can predict how many devices will be turned on and, onceactivated, when and which apps users will install.

The majority of smart devices are designed to communicate with the home base;they check for and download software updates, send usage data, or simply performtheir job taking temperature, recording movement, or uploading holiday snaps.

It is impossible to predict the amount of data they will generate or the Internet traOicebbs and Qows they may produce. Still, when it comes to those who buy our devicesand use our apps, this unpredictability is not an acceptable excuse for poor service.

Despite attempts at prognostication, nobody knows which device is going to getpopular, when, and what will be its rate of adoption. Therefore, backend capacityplanning is an impossible task. Still, no excuse—your data center must cope withthose demands, whether short-lived or ongoing, or your customers will dump yourproducts and services for the competition.

We expect security and accountabilityYou have seen the headlines telling tales of security breaches and the risk of identitytheft. Every business and person knows that security, trust, transparency, andaccountability are crucial in every context, but especially with regard to digital data.Everyone wants to know who has access to data and how we can preserve itsintegrity and sovereignty. Both security and accountability encompass legal andpolitical ramiPcations and are of great strategic importance to businesses,governments, and ordinary people.

Cloud becomes the storage medium of choiceCloud storage has actually been around for more than half a decade and is beingused by hundreds of millions of people and companies to store their documents,pictures, videos, life streams, metadata, and so forth. Smart devices often come witha choice of two or more cloud storage accounts. The masses and the businesses havevoted with their money and attention, preferring not to manage diOerent Ple formatsand storage devices. Instead, their computers, smart phones, and tablets do it forthem.

Despite all attempts at prognostication,nobody knows which device is goingto get popular, when, and what will beits rate of adoption. Therefore, backendcapacity planning is an impossibletask.

The demand for cloud storage is onlygoing to continue to grow as we connectevery device capable of running a TCP/IPcommunication stack to the Internet.Cloud storage only paints the Prst part ofthe picture, however.

Using the cloud for compute functions means the continual adoption and expansionof cloud platforms.

Equally as important as cloud storage are cloud-based applications: from oOicesuites to image processors to other kinds of applications not yet envisioned. Appsare pushing the adoption of cloud technology. With the mammoth amounts of dataand proliferation of devices using apps in multiple formats and on multiple platformssuch as binaries, HTML5, or emulated apps, cloud emerges as the only smart choiceto deliver what businesses and individuals expect.

Cloud computing to the rescueWhile Big Data, mobility, security, and cloud comprise current IT trends, it is obviousthat cloud also provides a way to deal with the other three IT trends. The challengesposed by these trends have one thing in common—they are, by nature, highlydynamic and unpredictable. It is hard to predict how much capacity needs to beprovisioned when some obscure mobile app suddenly goes viral gaining tens ofthousands of users overnight.

Let us take a closer look at some of these challenges.

The world around us is getting smarterAlthough not all of us are early adopters picking up the latest and greatest smartdevice, worldwide more and more people use an increasingly large number ofdevices equipped with sensors that gather and relay data about their own state,users, location, environment, the apps they are running, and usage patterns.

Many of these smart sensors are in reality tiny computers capable of running theTCP/IP communication stack suite as well as being capable of communicating usingHTTP and Secure Sockets Layer (SSL). By their function, then, each sensorautomatically becomes a web client in need of servers to talk to. Large networks ofsmart sensors enable the creation of smart cities, smart cars, smart roads, smart

buildings, smart appliances, smart quantiPed self-monitors, and a plethora of smartenvironmental sensors to form what is broadly called the Internet of Things.

We expect our data centers to shrink and expand on demandWe continue to process more and more information and increasingly rely oncomputers and networks in all aspects of our lives, thus increasing the demand fordata processing power, storage, and networking—an incalculable and inconstantdemand.

From small startups to big organizations like banks or retailers, the need for dataprocessing capability varies dynamically in ways that a traditional data center cannotdeal with in a cost-eOicient manner. The only approach available to theseadministrators is to design and build their data centers to handle the worst-casescenarios, a very costly option for a traditional brick-and-mortar data center model.

It may help to think of capacity planning in a diOerent way.

What the Dutch can teach us about capacity planningIf you know the variables inQuencing the demand for processing power,bandwidth, and storage capacity, you can handle capacity planning withconPdence. When that demand is unknown, the best you can do is plan forthe worst-case scenario.

Consider how the Dutch must plan for the ever-present threat of Qoodingfrom the North Sea. Years of protecting their reclaimed land have shownthat the water level can vary from 0 m to 10 m. To deal with the possiblevariance, it makes no sense to just take the average and build a dam 5 mtall—it must be at least 10 m whether water levels rise or not.

The same principle applies to data centers. If you need 1000 servers tohandle a spike in the demand for processing power on just 1 day in a month,you still need to keep those servers humming in their racks 365 days a year,even if that capacity is utilized only on payday.

Building and maintaining a data center capable of handling spikes in demand—evenpredictable ones—that happen on fewer than 20 days per year is not only expensive,but it is also wasteful; it requires an enormous amount of capital to design, build,and keep the data centers running.

The new data center has to adapt to the changes in the demand for processingpower and has to be able to do it within minutes. A sudden spike in the amount ofdata sent by billions of devices may occur instantly, without warning as well as beover just as quickly—delivering and conPguring servers to deal with a sudden spikemakes no sense and inevitably comes too late. The old data center model oOers noanswer to these questions, making businesses less competitive and less nimble bytying up a lot of capital resources.

Mobile apps are hungry for bandwidthOne of the reasons these spikes happen is that mobile devices run a variety ofapplications that are expected to always work. Earlier we discussed the growingadoption of all sorts of mobile devices. Now let us consider the bandwidth capacitythis growth requires.

Many applications require daily updates. The infrastructure that handles thoseupdates must be able to cope with the challenges of distributing the right payloadsto the right clients over unstable connections that oOer high latency and very limitedbandwidth.

To better understand the magnitude of the problem, realize that an update to an appwith a small 100 KB binary and one million users generates a bandwidth bill for over90 GB. When Apple ships a new version of iOS, the bandwidth requirement is north of600 MB.

Email, Twitter, Facebook, conferencing apps, and calendars are just a fewapplications that have to be updated, sometimes multiple times per day. You neverknow and cannot plan for a sudden spike in demand for bandwidth, storage, andcomputing power when millions of people want to Pnd out or comment on the latestnews or entertainment phenomenon.

We want to know moreThe billions of connected devices and apps cause a massive headache for anyonecharged with capacity planning—all those always-on, always-syncing sources ofdata generating output in a variety of often unstructured formats, all expecting real-time communication with the home base.

Those communications no longer center around uploads, downloads, and accesscontrol. Smart devices today “speak” with the home base and with each other. Theystream audio and video and process more data than desktop PCs used to ploughthrough 5 years ago.

And it is not just business apps, games, or social media services that need ITinfrastructures that can facilitate communications in real time. Even something asapparently simple as a shopping list app requires a reliable, secure backend capableof delivering and handling real-time updates.

Beyond storing and retrieving data, we now search for meaningful patterns, trends,sentiments, and early warning signals inside vast quantities of data. We used towant to store and retrieve digital still images. Today, we want to run them throughimage recognition software looking for faces, brand logos, and more.

Beyond storing and retrieving data, wenow search for meaningful patterns,trends, sentiments, and early warningsignals inside vast quantities of data.

We used to be happy to have the ability tochat using plain text. Today, we wrap whatwe are saying online in JSON or XMLstructures and mix it with images, videos,and audio Ples to search for actionable

data points. Now, we look for clues that let us Pnd out more about the people behindthe messages. We want to know more about the location of the event captured on a

digital still. We want to monitor sentiment and approximate gender, annual income,and other data points, and we want to do it in under a second.

As we get better at devising more accurate data analysis algorithms, we often wantto reassess old information along with the new, creating a temporary demand foradditional compute, network, and storage resources.

The myriad of types of data formats and analytical algorithms that dig through themountains of data present a huge challenge to the application architects who haveto use new tools, new algorithms, and vast amounts of CPU power, storage space,and network bandwidth to keep up with the ebbs and Qows of the tidal waves of dataand the demand for immediate answers.

With this explosion in the amount and the variety of data, our ability to reliablypredict changes in demand for compute power, storage capacity, or networkbandwidth is gone.

Data centers of today have to deal with a deluge of information coming from anever-increasing number of new sources capable of generating gigabytes, oftenterabytes, of data per day as we cover our world with one network after another,each smarter than the previous one, each capable of gathering more informationthan ever before.

What do we do now?The traditional data center model does not have enough Qexibility to deliver theresources necessary to handle such unpredictable spikes in demand. Even the bestlogistics will not help if you need a thousand servers delivered, conPgured, tested,and put into production overnight. If somehow you could manage to stand up a newbatch of servers overnight, once the spike ends and the demand ceases, theirsupplier will not take them back from you; the time and money is gone.

A better solution would be aOordable cloud computing infrastructure. Thanks to thehard work of the people involved in hardware virtualization and cloud computingtechnologies, we are now at a point in time when it is possible to launch hundreds orthousands of servers with a single script or an API call. Another call candecommission them in a few minutes, all done without having to rewire physicalswitches, servers, and disk arrays.

If you are ready to address the data and usage problems facing all of us now,consider the following advantages cloud computing oOers:

• Virtual hardware can be provisioned and decommissioned within minutes even ona weekend (when the server suppliers are closed and the data centers operatewith minimal staO). This feat is impossible to achieve with bare metal servers.Nobody delivers and deploys real hardware servers as fast as you can deployvirtual servers, with the click of a mouse button or a call to a RESTful API.

• When you no longer need the cloud resources you ordered, all you have to do isdelete them and you are no longer paying for them. Cloud computing replacescapital expenditure with operational expenditure, making operating your owndata center much more aOordable.

• You can create large-scale backends that exist and operate for short periods oftime. Coming back to the Large Hadron Collider experiments mentioned earlier,the problem of capturing, storing, and processing data from scientiPcexperiments can be solved using temporary, on-demand compute resources. Orconsider how banks benePt from on-demand storage and compute resources tolower the cost of operating their own data centers when they need to deployextra capacity on paydays or bond settlement days.

What the cloud needs to deliverWhile having the ability to add compute, networking, or storage resources ondemand is very appealing, cloud computing platforms must change to provideopenness, interoperability accountability, and the greatest promise of cloudcomputing—hybrid delivery.

Cloud computing platformsmust change to provideopenness, interoperabilityaccountability, and thegreatest promise of cloudcomputing-hybrid delivery.

Even the best cloud computing platforms today do notinteroperate very well. They are warehouses of blackboxes of goods with varied quality. Their oftenproprietary nature makes it very costly to moveinfrastructure from one public cloud to another orfrom a private cloud to a public cloud. This has tochange if we want to reap the most attractive benePts

of the cloud. And it has changed, as you will learn on the following pages. Read on toPnd out where the cloud innovators are taking us.

REFERENCES1. CERN. home.web.cern.ch/about/updates/2013/04/animation-shows-lhc-data-

processing

2. Twitter. https://about.twitter.com/company 2015

3. Instagram. https://instagram.com/press/ 2015

4. Facebook. https://code.facebook.com/posts/229861827208629/scaling-the-facebook-data-warehouse-to-300-pb/

Chapter 3

WhWhy wy we need oe need open sopen soururcce cle clooudsuds

In this chapter✓ Delivering on the greatest promise of cloud computing—hybrid delivery

✓ The need for open standards in the cloud

✓ The need for an operating system for the cloud

✓ The question of trust

✓ What the industry thinks of the OpenStack project

✓ A vibrant community

✓ A sound governance model

✓ The many reasons for HP’s involvement in the OpenStack community

Cloud computing is a very compelling concept, but the everyday reality isunapologetically practical and leaves little or no time to ponder upon the fascinatingconcepts of compute, networking, or storage abstraction.

After working on our own in-house cloud computing projects for a while, HP sawgreat promise in the OpenStack cloud computing project, and in 2011 decided that itwas time for a change in thinking about the cloud—from it being just one of manyproducts and services in our portfolio to treating it as the platform for delivery offuture products and services.

There is an acute need for anoperating system for the cloud.

We will go into more details later, but Prst it maybe helpful for you to know what OpenStacktechnology is. From openstack.org1 , “OpenStack is

a cloud operating system that controls large pools of compute, storage, andnetworking resources throughout a datacenter, all managed through a dashboardthat gives administrators control while empowering their users to provisionresources through a web interface.”

What we needed was a technology platform that would help us realize the fullpotential of cloud computing in the enterprise. Two of the most important things welearned from talking to our customers were that cloud computing will never deliverwhat it promises unless we make hybrid delivery a reality, and that there is an acuteneed for an operating system for the cloud.

Hybrid deliveryNobody can build and maintain enough data centers to adapt to the changes indemand for data processing resources. As our customers began to investigate thecloud as a possible solution, the following models of cloud delivery emerged:

• Private cloud—Owned and managed by the customer.

• Managed cloud—Owned by the customer, but managed by a third party.

• Public cloud—Cloud as a service, so the customer only pays for the resourcesthey use.

Most customers who use the cloud to adapt to the new reality of IT use a mixture ofprivate, public, and managed clouds from diOerent providers.

Cloud computing willnever deliver what itpromises unless we makehybrid delivery a reality.

One of the greatest impediments to a wider adoption ofcloud computing in the enterprise is the complexity ofredeploying the cloud-based infrastructure on a diOerentcloud platform from a diOerent provider.

What we need is a solution that enables hybrid delivery so moving data orapplications between private, managed, and public clouds becomes relativelysimple. These truly dynamic clouds would make it possible to provision extraresources on a public cloud when the private cloud cannot cope with a spike indemand. The way things are at the moment with OpenStack-based clouds, thisrequires a hybrid cloud management layer on top of the OpenStack infrastructure.

Open standards are a good thingWhen the world of IT adopts a standard, formal or informal, everybody movesforward faster. We have seen numerous examples of this approach working inpractice, such as the standard C library, Portable Operating System Interface (POSIX),TCP/IP, or HTTP.

We need the same thing to happen in the world of cloud computing because openstandards in the cloud:

• Accelerate the process of migration from the old data centers to the cloud.

• Allow customers to compare the diOerent clouds and choose one that meets theirneeds.

• Allow providers to compete in a more transparent environment.

• Create a rich ecosystem of vendors providing value-add enhancements to the coreplatform, without breaking compatibility with the core and with other add-ons.

• Enable greater interoperability between public and private clouds.

An operating system for the cloudWhen we begin to think of data centers as pools of compute, networking, andstorage resources, they start to resemble the basic design of a computer, albeit ahuge one. Any computer, whether a tiny embedded device, a powerful server, or asmartphone in our pocket, needs an operating system.

The more open and sophisticated the operating system, the better the hardwarebecomes; the more services it provides, the better the applications built on top of itbecome. A good operating system is like a coral reef supporting a complexecosystem. A lot of the advances in the history of computing would not havehappened were it not for the free and open BSDs, Linux®, Android, and the like.

What we need now is the equivalent of Linux for the cloud. It must support a varietyof hardware used in data centers and expose the data centers’ capabilities viasimple, standard APIs. Only then will it become interesting for developers to buildapps, services, and additional content that enhance the platform.

Examples of such add-ons for a cloud operating system include drivers for newstorage hardware, application monitoring tools, energy eOiciency monitoring,prebuilt virtual images, prebuilt infrastructure templates for ready-made mobile appbackends, and more.

Why HP chose OpenStack technologyIn our search for a cloud operating system, HP considered all options available in2011, proprietary and open. As we went through the list of our requirements, itbecame increasingly apparent that the most important question asked by ourcustomers was the one of trust. It may have been disguised as a question aboutreliability, security, scalability, compliance, openness, transparency, or data

sovereignty, but our customers ultimately wanted to know if they could trust theircloud platform.

No love for proprietary cloudsWhile proprietary public clouds have been very successful, they cannot positivelyanswer a number of questions asked by their customers. For example, none of theexisting proprietary public clouds are available for private cloud deployments.

Proprietary public cloud vendors are not keen to give their code to customers and letthem run it on their own infrastructure. This rules out proprietary public clouds in thehybrid cloud delivery model for many customers. The complexity, the costs, andsometimes the plain incompatibility of the public cloud with the customer’s privatecloud make bursting very diOicult.

While proprietary publicclouds have been verysuccessful, they cannotpositively answer anumber of questionsasked by their customers.

Another problem with proprietary public clouds is thefact that they are black boxes: you do not necessarilyknow what software they are running, and you do notnecessarily know what hardware they are using. If youwant to burst into another proprietary cloud, you mayneed to redesign your infrastructure again, which may bejust too expensive.

As we looked at various proprietary cloud platforms, we quickly realized that theywere not the right Pt for HP and its customers.

Open = TrustedWhen HP started looking to build technology we could use as a basis for our cloudoperating system and as a cloud delivery platform, we decided to use an open sourcemodel that lets everyone who is interested check the quality of the code and its innerworkings and suggest improvements, or submit Pxes.

Problems with open source software typically get Pxed fast, because softwaredevelopers in the open source community truly want to make the code better. Opensource software shortens the development process by removing the need tonegotiate new license agreements and by leveraging the entire community ofdevelopers, reducing the time required to implement patches and changes. Thisopen source development process makes open source software trustworthy in theeyes of customers who no longer trust proprietary black boxes.

On the Qip side, we were not interested in projects that had loose governance andwere subject to the whims of developers. Our customers want to know that the opensource projects they rely on for their business are:

• Well-organized—There is a clearly dePned process for code submissions,reviews, removal, and maintenance.

• Stable—There are roadmaps, features get delivered on time, and there is a long-term vision and commitment.

• Business-friendly—Successful open source projects are often those that do notoppose commercial entities adding value to the ecosystem. (See Apache, Linux,WordPress, and others.)

• Open to feedback from users—Projects that listen to their users are more likelyto make their users happy.

The OpenStack project was not the only open source project of its kind in 2011, but itcertainly did exhibit these traits. Here is how the OpenStack project dePnes “open”on their own blog (openstack.org2):

• Open source (not open core) with appropriate license (in our case, Apache 2.0which is OSI3 approved, GPLv3 compatible, and DFSG4 compatible)

• Open Design

• Open Development

• Open Community

Data sovereigntyThe project’s commitment to openness helps tremendously in this day and age whencustomers no longer trust vendors, governments, or each other. As more and moredata is stored in the cloud, the following are heard in conversations related to theissue of trust:

• Data integrity

• Data sovereignty

• Industrial espionage

• Sabotage

The increasingly complex political and legal landscape that businesses andgovernments deal with daily only serves to exacerbate these concerns.

Proprietary cloud providers cannot give satisfactory answers to the questionsrelated to these hot issues. Going forward we believe the obvious choice for a cloudplatform must be open. The hard reality of doing business in this day and age is thattrust is at a low ebb and black boxes only increase wariness.

MaturityWhen HP started to look for a candidate for a cloud operating system, we had achoice of building it from scratch, buying one, or joining a mature open sourceproject. The OpenStack project was oOicially announced in 2010, and by the time HPoOicially joined in 2011, it had three major releases on its CV.

Now nearly 5 years old, OpenStack technology is ready for enterprise-gradeapplications. Large organizations like banks or telecoms are already using it inproduction, furnishing the best testament for a software project.

OpenStack technology isdesigned to be massivelyscalable, with no hardwaredependencies.

The maturity of the OpenStack platform shows in itsdesign: it has a modular architecture with eachcomponent communicating with others and with theoutside world via a set of simple, well-dePnedRESTful APIs.

All OpenStack projects are designed to be easily extended to support new hardware,new hypervisors, new protocols, and new identity veriPcation mechanisms.OpenStack technology is designed to be massively scalable, with no hardwaredependencies.

Appeal to our own peopleHP did not have to force our staO to join the OpenStack project. People working indiOerent divisions at HP have been involved in the development of OpenStacktechnology before the company itself got involved.

It happened because the OpenStack platform was and still is seen by HP’s ownengineers as the cloud technology solution they were looking for and somethingthey wanted to get involved in. We did not have to force our engineers to work withthe OpenStack project. They started submitting code before the company even had achance to form an oOicial strategy.

This widespread internal adoption of the project proved to be a strong predictor ofsuccess that could only benePt our customers. When engineers work on somethingthey would work on even if nobody asked them to, the result often produces high-quality code along with a sense of ownership and responsibility that cannot beenforced via an oOicial corporate policy. Bluntly speaking, there is no better indicatorof a project’s future success than the engineers’ willingness to work on it voluntarily.

Dynamic growthFor a project that started in July 2010, the OpenStack project has had a phenomenalrun. So far it has maintained a steady stream of releases approximately every 6months, which is an amazing pace of development considering the size and thecomplexity of the source code. Here are some facts:5

• In 2010, the OpenStack project consisted of just two projects (Nova and Swift).

• In 2013, there were already nine projects under the OpenStack umbrella. In 2015,there are now over 20 projects.

• Currently in 2015, there are over 3,500 total developers who have contributed tothe OpenStack code base, coming from over 170 companies.

• The total number of all tests, unit and integration has passed 15,000.

• The Kilo release alone added 394 new features, over 7,200 bug Pxes, and 21,000patches from 1,500 contributors.

• The number of developers working on the OpenStack project is greater than thenumber of developers working on any other open source cloud operating systemproject.

These measures establish the OpenStack project as one of the fastest, mostdynamically growing open source project in history.

Industry-wide supportThe OpenStack project has wide industry support from many major vendors. The listof Platinum members of the OpenStack Foundation includes some of the largestcompanies in the business:

• AT&T

• Canonical

• HP

• IBM

• Intel

• Rackspace

• Red Hat

• SUSE

Other large companies that support the OpenStack project include Cisco, Dell,Mirantis, NEC, Symantec, VMware, and Yahoo. For a complete list of corporatesponsors visit www.openstack.org/foundation/companies.

Global communityA strong, enthusiastic community is crucial to the long-term survival of any project,but it is especially important for the survival of open source projects. A large,dynamic community of developers, users, and supporters serves to make the projectgrow and thrive. The global OpenStack community ticks all those boxes.

The OpenStack project has a global community of more than 10,000 supporters,developers, and users in nearly 100 countries actively participating in code

development, online discussions, deployment, and support. More than 350companies are involved in the OpenStack ecosystem.6

Sound governance modelThe OpenStack community is a meritocracy. The OpenStack Foundation and projectis governed by the following bodies:

• The Board of Directors to manage the aOairs and business of the Foundation.

• The Technical Committee to manage the technical matters.

Each governing body is responsible for a diOerent area of the project’s activities andhas its roles and responsibilities dePned in the Foundation’s bylaws. Along withthese two oOicial governing bodies, the OpenStack project benePts from an activeuser community.

The OpenStack FoundationAccording to its bylaws, the OpenStack Foundation’s purpose is to “develop, support,protect, and promote the open source cloud computing project which is known as theOpenStack Project.”7

The Board of DirectorsBoard of Directors of the OpenStack Foundation is responsible for managing theaOairs and business of the Foundation, including the strategic and Pnancial oversightof its resources and its staO. It cannot exceed 24 members.

Since no organization can have more than two employees on the Board of Directors,it is impossible for any one entity to dominate the direction of the project and causetensions that may lead to a breakup of the project.

MembersThe OpenStack Foundation recognizes three types of members, with diOerent votingpowers and numbers of seats on the Foundation’s Board of Directors. The seats onthe Board of Directors are split into equal parts among Platinum, Gold, and Individualmembers:

• Platinum—No more than eight members. These members are companies whomake signiPcant Pnancial and resource commitments to the OpenStack project.Platinum members become involved at that level because they have aligned theircorporate strategy with the mission of the OpenStack project. To achieve theirgoals, they may assign their own staO (developers, legal, documentation, and soforth) to work on the OpenStack project. Platinum members can appoint onerepresentative to the Board of Directors.

• Gold—There are eight seats on the Board elected from the gold members. Thislevel of membership requires lower Pnancial and resource commitments than

Platinum membership. Members elect their own representatives to the Board ofDirectors.

• Individual—There are eight seats on the Board elected by the Individualmembers of the community.

Technical CommitteeThe Technical Committee of the OpenStack Foundation is responsible for dePningand delivering the technical goals of the OpenStack software project. The membersof the Technical Committee are elected by the active technical contributors on astaggered basis, with half of the committee being up for election every 6 months.

User CommitteeThe User Committee was created to give the users of OpenStack technology a way torelay their requirements and concerns in an organized, formal fashion. Its goals areas follows:

• Consolidate user requirements. This gives users a voice on all matters related tothe project and helps the Technical Committee and the Board of Directors dePnefuture goals of the project.

• Present user requirements to the OpenStack Foundation Board of Directors and tothe Technical Committee.

• Create guidelines that instruct developers on when and how to ask for userfeedback.

• Track OpenStack deployments and use. The project maintains an extensiveanalytics website that gives deep insights into the project’s progress.

• Disseminate OpenStack user stories. These are essential to help accelerate theadoption of OpenStack technology.

• Work with the global community of OpenStack user groups. With over 18,000members, the global OpenStack community must be managed in a way that helpseach member participate and proPt from being a member.

Legal A-airs CommitteeThe Legal AOairs Committee is an advisory committee which advises the Board ofDirectors on matters relating to intellectual property protection and management.

New projectsThe OpenStack Foundation dePnes an oOicial process for the inclusion of newprojects under the OpenStack umbrella and to leverage the OpenStack trademark.The Prst stage in the life of a new project begins with an idea and an initialimplementation and ends with a Pnished design and a working implementation that

all interested parties can agree upon. There are some fundamental principles thatthe project must meet:

• Open source

• Open community

• Open development

• Open design

Uni.ed licensingThe license for the OpenStack project and all of its member projects is the Apache2.0 license, a well-known and widely adopted open source license with an explicitpatent grant.

FundingPlatinum members provide a signiPcant amount of funding for the OpenStackFoundation. The remainder is provided by Gold members, Corporate Sponsors, andStartup Sponsors.

An easy decision to makeWith so many arguments in favor of adopting the OpenStack platform, it seemedunwise for HP to not consider it, or to instead follow the proprietary route. The onlyother option, developing our own cloud operating system, just did not make businesssense.

Going at it together, rather than alone, proved the smartest route, and that is why onJuly 27, 2011, HP oOicially announced its intention to join and support theOpenStack project.

REFERENCES1. OpenStack. http://www.openstack.org/software 4/28/15

2. OpenStack. http://www.openstack.org/blog/2010/09/openstack-governance/

3. Open Source Initiative. opensource.org 2015

4. Debian Free Software Guidelines, a part of the Debian Social Contract. www.debian.org/social_contract 2015

5. CloudScaling. www.cloudscaling.com/blog/cloud-computing/openstack-at-3-this-is-what-winning-looks-like/

6. OpenStack. https://www.openstack.org/foundation/companies/

7. OpenStack. www.openstack.org/legal/bylaws-of-the-openstack-foundation/

Chapter 4

JusJust hot how seriow serious is HP abous is HP about OpenSut OpenStacktackttechnolechnologogyy??

In this chapter✓ The history of HP’s involvement with the OpenStack project

✓ How HP participates in the OpenStack ecosystem

✓ HP’s commitment to OpenStack technology

✓ HP Helion

HP employees have been involved in the OpenStack community from the early daysand were instrumental from the beginning of the project. Our Crst involvement was aform of unoBicial, grass-roots participation by HP’s engineers, who simply wanted toget involved in a cool project or felt that OpenStack technology could potentially helpthem solve the problems they were facing at work. HP engineers working on our ownpublic cloud found out about OpenStack technology and started contributing theirtime and code.

In 2011, HP moved to the point of considering OpenStack technology for its cloud-computing platform. As noted in the last chapter, we evaluated many proprietaryand open platforms and came to the conclusion that OpenStack cloud computingmet HP’s requirements. Once this decision was made, HP jumped in withdetermination.

HP’s contributions to the OpenStack projectHP is one of the major contributors to the OpenStack project in terms of funding,resource allocation, testing, community participation, reviews, code contributions,training, and commercial deployments.

Involved from the beginningHP employees have been involved in the OpenStack project from its early days in2010, and formally as a company since July 27, 2011 when HP announced itsintention to join and support the OpenStack Project.

The OpenStack Foundation was created in 2012, and HP is a Platinum foundingmember of the OpenStack Foundation.

Project governanceHP takes its involvement in the project seriously, and we participate in many facetsof the project, including its governance, where HP is involved at all levels with:

• Two employees on the Board of Directors (one HP’s designated representative,the other representing Individual members)

• Members on the:

• Technical Committee (Cve elected members)

• Legal ABairs Committee

• User Committee

• Project Incubation

• Training programs

• DefCore Committee

• Project Technical Leads (for the Kilo release):

• Neutron

• Keystone

• Trove

• Ironic

• Designate

• Infra

• QA

• Oslo

Our involvement in various aspects of the project governance gives us a chance toinDuence project strategy, governance, roadmap, blueprints, and development. Thisensures that our customers know that they are working with people who haveintimate knowledge of all aspects of OpenStack technology, and that their feedbackwill be listened to and relayed to other members of the OpenStack project.

We cannot force anyone to implement or accept the changes we are proposing, butwe can make sure that they are at least heard and considered.

Financial supportAs a Platinum member, HP is committed to provide its share of funding for theproject. This is on top of our voluntary commitment of infrastructure, time, power,staB, marketing, committees, and code.

Commitment to the project governance and processesHP is fully committed to the OpenStack governance model and the checks andbalances mechanisms implemented in the project’s bylaws.

HP is always one of the top contributors to OpenStackWhen the OpenStack project began its life as an open source project, it had twomajor code contributors and two projects. Today, there are over 20 projects andthousands of contributors, and according to stackalytics.com, HP is consistently oneof the top three employee contributors, including being the number one contributorfor the Havana, Juno, and Kilo releases and number two for Icehouse. Thesecontributions represent a massive investment in developer time on HP’s part, and weplan to continue that commitment.

Dedicated staBWhile developers are a signiCcant part of our staB assigned to work on theOpenStack project, they are by no means the only ones participating in the project.Other employees of HP participating in the OpenStack project include operationspersonnel, documentation teams, training teams, and QA staB.

Our employees act as Technical Leaders for some projects and our legal staBparticipates in the Legal ABairs Committee.

Running our own OpenStack-based public cloud gave usunique and invaluable practicalexperience.

HP is the only organization other than theOpenStack Foundation itself that provides adedicated group of employees to the OpenStackDeveloper Infrastructure and ContinuousIntegration projects.

We also contribute OpenStack cloud accounts required to keep the OpenStackDeveloper Infrastructure and Continuous Integration projects running.

Successful commercial deployments of OpenStack technologyWhen we committed ourselves to the OpenStack project, we quickly started usingthe software to run our public cloud because that was the only way we could Cnd outhow well the OpenStack platform would cope with customer demands as well asdetermine what it needed in order to become a viable solution for the enterprise.

Running our own OpenStack-based public cloud gives us unique and invaluablepractical experience deploying thousands of OpenStack compute nodes and multiplepetabytes of storage managed by OpenStack technology.

The hands-on experience we gained running an OpenStack-based public cloudhelped us understand how OpenStack technology needs to be hardened, deployed,and enhanced for production use in real-life applications. We had to develop our owntools, extensions, plug-ins, and management and monitoring add-ons.

Transparency and accountabilityHP is fully aware of the fact that our involvement and our fulCllment of the promisesmade to customers and to the OpenStack community are open to public scrutiny. Byvirtue of being involved in an open source project, HP has to be committed to thevision and the rules of engagement of the project. Everybody can see our code,proposals, decisions, votes, blueprints, and comments. The history of ourinvolvement with the OpenStack project conCrms our commitment to its principles.

Expert leadershipThe cloud team at HP includes industry veterans with extensive experience building,managing, governing, and delivering large-scale projects and enterprise-gradeproducts based on Linux, Apache, and other major open source systems. Many ofthese team members used to work on open source projects at Canonical, IBM, Sun,or MySQL and have extensive knowledge of the enterprise market.

Coopetition and giving back to the communityHP Crmly believes in sharing and giving back to the community. These values weredeeply ingrained in our culture by our founders; therefore, we do not believe in azero sum game in the case of the OpenStack community. Even though it may seem

contradictory to our goals, we sometimes work with our competitors, helping themintegrate their solutions with the OpenStack platform, because we believe that wewill all beneCt from OpenStack technology if we help our customers integrate it withthe solutions they are already using or choose to use in the future. We want to workwith our competitors to help create a rich ecosystem around OpenStack cloudsolutions where all kinds of participants, large and small, can Cnd opportunities forsuccess.

HP HelionThe IT industry often spews nothing but static in an attempt to address the issues ofthe day. Thus, it is fair to ask, is HP truly committed to OpenStack technology? Thatis essentially what HP is showing with the OpenStack platform and our HP Helionportfolio.

• The analysis of the trends discussed in Chapter 2, “A case for cloud computing,”has convinced us that the cloud is the future.

• The cloud is already driving many of the internal eBorts inside HP, and you canexpect it to become even more important in the coming months and years. Oncewe made our choices, we became engaged with the project on all levels.

An all-hands eBort• The cloud is having a profound eBect on HP as a company. Having a clear strategy

for the future can work wonders for a business as large as HP. Once we deCnedour goals and chose the platform, we could see ourselves reaping the beneCts ofthose choices even before we started oBering our own distribution of OpenStacksoftware to customers.

• Just like Linux in the past, the OpenStack project is one of those projects thatintroduces major changes to the way a company thinks, operates, and sees itsfuture. OpenStack technology is the basis of the HP Helion distribution.

• HP is fully committed to making cloud technology a signiCcant distributionchannel for delivery of our future products and services.

What is HP Helion?HP Helion is a comprehensive portfolio of products and services that makes it easyfor organizations to build, manage and consume workloads in a hybrid ITenvironment. HP Helion is the fabric of your enterprise. It brings together all thebeneCts and agility of cloud computing, all the possibilities and interoperability ofopen source, and the security and reliability that enterprises need to move forwardwith conCdence.

It’s a journeyCloud is a journey for HP just like it is for our customers. We started with a goodbase, and we have already built tools and services that enhance the experience. We

have been learning by doing: submitting code, helping the code get better, lettingpeople try OpenStack software, and running our own HP Public Cloud, which is thesecond-largest public cloud based on OpenStack technology. We continuously testand deploy the latest code from the OpenStack core.

We are learning from all of these eBorts, and what we have learned helps us betterserve our customers and the OpenStack community. We are packaging ourexperiences in technology such as HP Helion OpenStack or extensions to OpenStacksoftware. We are also enhancing all of our products and services that can beneCtfrom HP Helion OpenStack.

It is an exciting time to be involved in the OpenStack project, and we are ascommitted to it as we can possibly be. Our commitment has allowed us to becomeexperienced, knowledgeable guides helping our customers on their own journey intothe cloud.

Chapter 5

WhWhaat is HP Helion OpenSt is HP Helion OpenStacktack??

In this chapter✓ Why we created HP Helion OpenStack

✓ Main advantages of HP Helion OpenStack

✓ Where does OpenStack technology and HP Helion OpenStack Et within HP’s strategy

✓ Who HP Helion OpenStack is for

✓ Partner and ISV support

HP Helion OpenStack is an open and extensible cloud platform based on OpenStacktechnology. It is a curated, tested, enterprise-grade distribution of OpenStack cloudsoftware, designed to deliver the best open source cloud computing technology in astable, maintainable, and easy to install and manage package. Essentially, HP HelionOpenStack is enterprise-grade OpenStack technology, speciEcally designed to caterto the needs of large organizations looking for a platform that enables a hybridcloud delivery model.

Why package free software?We decided to package a curated, tested, enterprise-grade OpenStackdistribution to cater to enterprise and service provider customers. Toachieve that, the software must be delivered in a way that makes it easy forthe customer to use. This approach has helped turn Linux into the dominantserver operating system, and we want to help repeat that success story withOpenStack technology.

Why we created HP Helion OpenStackSoftware projects, including those releasing the fruits of their labor as open source,often produce source code not Et for immediate consumption. The more complex thecode, the more time and eDort it takes to get it running. This explains the popularityof various Linux distributions, software package installation tools, and setuptutorials.

At the end of the day, customers want a working product that does not require themto spend time experimenting with various conEguration options. OpenStacksoftware faces issues similar to those faced by Linux—with over 20 projects underthe OpenStack umbrella, it takes a lot of learning and experimentation to get themall conEgured and running the way the user wants.

Even when open source software is packaged in a way that makes it possible todeploy by developers with a deep understanding of its internal architecture, it is notusually Et for use in the enterprise, if only because of the sheer number of possibleconEguration options and various dependencies that typically come with uniqueconEguration processes.

OpenStack software is, in this regard, quite similar to the Linux kernel, which by itselfis not of much use to most users. The source code of the kernel and the additionalsoftware that turns the kernel into an operating system are not very useful in sourcecode form. Linux becomes useful for production applications only after it has beentested and packaged in a way that makes all those millions of lines of code easy toinstall and manage.

Just as Linux needs to be packaged and oDered as a curated distribution, so does theOpenStack platform. The challenges of installing OpenStack software are evenbigger because you need to understand the hardware conEgurations, networkingtopology complexities, and storage strategy and also understand your scalability,performance, and high availability needs.

Our customers want to run OpenStack software, but they are not comfortableplaying with various conEguration settings, certainly not when they are trying todeploy the OpenStack platform on hundreds or thousands of servers.

HP Helion OpenStack was developed to address the complexities of installing andrunning an open source project in an enterprise environment.

Main advantages of HP Helion OpenStackHP Helion OpenStack adds functionality to the OpenStack platform, bringing muchneeded improvements for our enterprise customers. This is what we mean by“enterprise-grade OpenStack technology.”

Simple installationThe OpenStack platform is an open source product that is very powerful and veryFexible, but requires extensive knowledge of its inner workings to properly set upeach component, using conEguration Eles to make them all work together.Customers usually do not have the resources necessary to gain all that knowledgeand would rather use an installer that hides all that complexity behind a simpleinterface.

To make OpenStack software more friendly to the operations staD, our engineersspent a lot of time enhancing the current OpenStack deployment framework. Wealso added a cloud installation and conEguration tool that helps the user install apreconEgured cloud.

The tool provides a wizard-like experience to deploy complex services with easypoint-and-click conEguration options. The users decide which nodes they wish todeploy and which services, and the tool handles the installation and conEguration.

By making it easier to install, HP makes HP Helion OpenStack an attractiveproposition for those who are discouraged from trying OpenStack software becauseof its “some assembly required” nature.

OpenStack technology at scaleYears of experience running the second biggest public cloud powered by OpenStacktechnology have taught us a lot about OpenStack code for enterprise deployments.This expertise helps us curate the code for our customers.

Enhanced securityBased on our hands-on experience, HP places great value on security for enterprisedeployments, and has developed speciEc security processes to govern our buildingand engineering of HP Helion OpenStack. The HP Helion Security Review Processfollows 4 speciEc steps:

1) Architectural Blueprint Design Reviews

2) Vulnerability Scanning

3) Penetration Testing

4) Source Code Analysis

In addition to this HP Helion Security Review Process, HP builds in speciEc securityprotections and integrations with HP Helion OpenStack. For example, HP HelionOpenStack secures the network during installation by implementing security rulesthat allow only the ports that need to access the network installation to be opened.This limits the surface of vulnerability and allows customers to maintain an overallhigher level of system integrity. HP Helion OpenStack also enables an additionallayer of automated protection against VM breakouts by proactively protecting theoperating system and the applications from external or internal threats.

For customers interested in additional security monitoring, HP Helion OpenStackintegrates with HP ArcSight to provide extended centralized logging capabilities toenhance the speed with which customers might identify and respond to systemthreats.

Well-paced innovationBy providing a stable mechanism for applying and rolling back patches andupgrades, HP Helion OpenStack helps enterprise customers ride the wave ofinnovation while using a trusted, tested, and deployable platform. HP HelionOpenStack lets customers choose which new OpenStack software features theywant to enable and when.

SimpliEed managementHP Helion OpenStack helps enterprise customers keep up with the speed ofdevelopment of OpenStack technology, in an organized, predictable manner. It takesthe pain out of OpenStack upgrades and patches by automating that process.

HP Helion OpenStack plugs into a Helion download network which distributespatches and upgrades straight from HP to the customer’s cloud environment. All

HP Helion OpenStack helpsenterprise customers ride thewave of innovation while using atrusted, tested, and deployableplatform.

patches and updates to the HP HelionOpenStack environment are thoroughlyreviewed and tested by HP, which only releasespatches that can be safely applied to thecustomer’s cloud without disruptingoperations.

The administrators see those patches and updates in their HP Helion OpenStackoperational dashboard and can decide which ones they want to apply. Applyingpatches and updates requires zero cloud downtime. If necessary, updates andupgrades can be rolled back using the same visual interface found in the HP HelionOpenStack operational dashboard.

Automated delivery of additional functionality and contentPatches and updates are not the only types of content that can be delivered to thecustomer’s cloud. The HP Helion Downloads and Resources website can be leveragedto deliver additional functionality in the form of plugins, extensions, and new

modules, and can also deliver additional content, such as virtual machine images,scripts, or training materials. HP is constantly evolving the site. Customers candownload and install infrastructure for building backends for web apps, mobile apps,online shops, development environments, and more.

InteroperabilityA common, open source cloud platform makes it easier to achieve interoperabilitybetween clouds oDered by diDerent providers or deployed at diDerent data centersowned by the same organization. Workload transfer becomes as easy as executingan infrastructure template.

Good Et for all data centers, large and smallWith the advent of the HP Moonshot hardware platform, the HP Helion Rack solution,or other cutting edge HP server technology, your data center need not live in abunker, but may Et into the oDice next door. HP Helion OpenStack is designed to bescalable and work with OpenStack-compatible hardware infrastructures of any size,from a few old servers to an air-conditioned underground data center housingthousands of machines.

This makes HP Helion OpenStack a good Et for both departmental clouds and forwhole enterprises. In addition to our HP Helion OpenStack Community distribution,we also oDer an HP Helion OpenStack edition that has been optimized to scale forthe very large needs of enterprises and service providers.

Simple data sovereigntyBy using open source software and technologies and deploying their workloads onprivate clouds, customers can gain the convenience of large-scale cloudmanagement and the maximum possible levels of data sovereignty.

Lower cost of migrationClouds based on proprietary solutions increase the cost of migration and might evenrequire reengineering of the whole application. This process may have to berepeated for each public cloud, which is unfeasible and ultimately limits workloadportability. The concept of not being able to get your code or data out of a third-party provider’s data center is also not acceptable.

Also, with HP Helion any third-party solutions based on OpenStack technology canbe easily migrated along with the customer’s base infrastructure. This is not possiblewith a proprietary cloud.

Standardizing on the OpenStack platform gives cloud users greater freedom ofchoice and avoids their being held hostage because of an investment in just onevendor’s ecosystem. It also provides an opportunity for third parties to oDersolutions based on OpenStack technology that can be migrated along with the wholecloud.

A truly open cloud operating systemHP’s focus is on making HP hardware and software work well with the HP Helionportfolio and OpenStack technology. But thanks to the open source nature of theproject, our customers will be able to use HP Helion OpenStack with hardware andsoftware provided by other vendors, too. Open source provides the ability forvendors to provide drivers that expose their solutions to the OpenStack platform.The distribution is available under an open source license, so ISVs can easily use it tocreate their own applications.

HP Helion OpenStack follows the architectural principles behind OpenStacktechnology. Our enhancements to OpenStack software are compatible with theexisting extension frameworks, or implemented as separate modules accessible viaRESTful APIs.

Model once, deploy everywhereHP Helion OpenStack introduces a powerful set of tools for modeling andprovisioning infrastructure on diDerent OpenStack-based clouds, used to describeinfrastructure in terms of required resources and the relationships between them.

• Our implementation of infrastructure includes hooks for executing actualdeployment scripts.

• HP Helion OpenStack includes versioning tools to enable rollbacks and changetracking.

• The Helion download network can be used to distribute infrastructure for thosewho would rather reuse a tested infrastructure than spend time building andtesting their own.

Rapid provisioningOnce infrastructure has been designed and tested, administrators can reuse thedesigns to quickly recreate the infrastructures they represent.

You can model your infrastructure, connect your model to deployment scripts, anduse those highly abstract recipes to provision complex backends with only a fewclicks.

Sharing resourcesThe HP Helion OpenStack resource pool registry and capability tagging serviceallows customers to publish and browse information about available cloudresources. This facilitates cloud resource selection optimized for speciEc workloads,streamlining utilization of their clouds.

Multi-cloud provider supportThe HP Helion OpenStack resource pool registry can store information about bothpublic and private clouds. Right now, when there is a need for extra capacity, thecloud administrator has to provision it manually. We intend for administrators to

have an option to dynamically provision additional capacity by setting rules andtriggers for infrastructure and for the matching resource pools. This will enableautomated bursting from private into multiple public clouds.

Hybrid provisioningHP Helion OpenStack helps its users achieve the goal of hybrid delivery with the helpof the infrastructure and the resource pool registry. HP Helion OpenStack let cloud

HP Helion OpenStack helps usersachieve the goal of hybrid deliverywith the infrastructure templates andthe resource pool registry.

administrators describe what resources theyneed and then choose the cloud they want todeploy that infrastructure on by selecting theresource pools that match the requirementsfrom a list returned by the registry.

We intend customers to have the functionality that allows you to split workloadsacross diDerent clouds via Keystone federation capabilities introduced in the Kilorelease, and deploy databases on private cloud resources while the web applicationserver runs on public cloud resources.

Supported by HPA lot of enterprise customers are facing the same issues with OpenStack technologythat they faced a few years ago with Linux—there was nobody who would takeresponsibility and support enterprise users; there was nobody who would try to helpintroduce changes or improvements to the Linux source code in the form of drivers,Ele systems, or protocol support. HP takes responsibility. We provide paid technicalsupport options to every customer purchasing an HP Helion OpenStack license toensure HP Helion OpenStack stays up and running at peak performance.

For customers who are looking for more specialized OpenStack professionalservices, HP also has unparalleled OpenStack consultants all over the world who willpartner with you to get to market faster, oDer innovative services, and providevaluable guidance along your OpenStack journey. Please visit the HP HelionProfessional Services section on hp.com/helion for additional information.

HP’s OpenStack Technology IndemniEcation ProgramSubject to the terms and conditions of a separate indemnity agreement, qualiEed HPHelion OpenStack customers with a current support agreement are eligible for theHP’s OpenStack Technology IndemniEcation Program, under which HP will indemnify,defend, and settle third party copyright, patent, and trade secret infringementclaims directed to OpenStack code, alone or in combination with Linux code, in HPHelion OpenStack. Subject to the terms of the indemnity agreement, HP is oDeringthis indemnity with no monetary cap, a key diDerentiator from our competitors thatdemonstrates HP’s commitment to the OpenStack platform and community.

HP Helion PlatformThe HP Helion platform is comprised of the HP Helion OpenStack distribution and theHP Helion Development Platform, which provide the common foundation for HPHelion products and services.

Partner and ISV supportThe rich HP Helion OpenStack ecosystem enables developers, software andhardware vendors, and worldwide partners to create new solutions and tap newmarkets. HP makes HP Helion OpenStack available for testing and integrationpurposes. Hardware and software vendors can test their products with it through ourcomprehensive HP Helion Ready program, which includes consultation with ourtechnical experts and infrastructure resources.

HP Helion Ready partners are able to leverage HP’s marketing engines and otherresources to accelerate business momentum, open new markets, and driveadditional revenue.

Chapter 6

Inside HP Helion OpenSInside HP Helion OpenStacktack

In this chapter✓ How HP Helion OpenStack enhances and augments OpenStack technology

✓ How much OpenStack code is inside HP Helion OpenStack

✓ The future of HP Helion OpenStack enhancements to the OpenStack platform

HP Helion OpenStack is a curated distribution based on OpenStack softwaredesigned to meet the expectations of the enterprise customer. The OpenStackproject is, in many ways, similar to the Linux kernel project—the value of its sourcecode increases greatly through the addition of the software that lets it interface withthe open and proprietary products and services developed. HP Helion OpenStackpackages core OpenStack software with HP value-add services, written to extend thecore OpenStack code base to oHer a supported product that enterprise customerscan easily install, use, and manage.

HP Helion OpenStack oHers three distributions to meet users’ diHerent needs:

• HP Helion OpenStack Community edition—A free-to-download distribution thatcloud administrators can use to evaluate, develop, and deploy a private cloudbased on OpenStack technology. HP Helion OpenStack Community acceleratesdeployment and simpliIes the management of small-scale, open cloudenvironments and cloud-native infrastructure services.

• HP Helion OpenStack—An enterprise-grade commercial distribution andsupported product with the openness, Jexibility, and additional IP to speed clouddeployment and cloud application development while simplifying managementfor large-scale private, public, and hybrid clouds.

• HP Helion OpenStack Carrier Grade edition—An OpenStack solution optimizedspeciIcally for telecommunications carriers.

Staying true to the communityHP develops technologies designed to enhance and extend the OpenStackprojects. And staying true to the community, HP contributes much of thatcode upstream to the OpenStack community to advance the core of sharedopen source code.

The architecture of HP Helion OpenStackHP Helion OpenStack retains the OpenStack platform’s highly modular design andfollows the conventions of communicating between components via RESTful APIs.This design makes the OpenStack platform and HP Helion OpenStack more resilient,scalable, and maintainable by separating the implementation details of variousfunctionalities from each other.

The architecture of HP Helion OpenStack can be broken into two environments:

• Execution—Managing above the cloud. This is where you create projects, users,and provision infrastructure.

• Administration—Managing below the cloud, This is where you deIne andmanage the conIguration of your cloud, where you manage and maintain yourcloud, and where you extend/expand it.

The execution environment o]ers functionality that makes the cloud run on top of

the customer’s infrastructure, while the administration environment o]ers

functionality required to install, con^gure, manage, and upgrade an HP Helion

OpenStack-based cloud.

Furthermore, the execution environment is broken into ^ve layers:

• Kernel—Implements functionality similar to the kernel of an operating system,

abstracting the complexity of the underlying infrastructure behind a uni^ed,

application interface implemented as a set of RESTful APIs. These APIs serve a

very similar purpose to the standard libraries found in Linux or in Windows

operating systems.

• Base—Supports the work of the kernel.

• UI—Provides a uni^ed user experience for managing tasks in the cloud.

• Subsystem—Expands supportability functionality for managing enterprise-grade

cloud environments.

• Linux platform—O]ers a Linux operating system running the managed cloud

controllers and nodes.

The HP Helion OpenStack core services

The HP Helion OpenStack core services are comprised of the following OpenStack

projects:

• Keystone (identity management service)

• Glance (virtual image management service)

• Horizon (dashboard)

• Ceilometer (metering)

• Heat (orchestration)

• Nova (hypervisor and virtual machine management service)

• Cinder (volume management service)

• Swift (object storage service)

• Neutron (virtual networking service)

• Ironic (bare metal provisioning)

• Designate (DNS as a Service)

• Monasca (monitoring at scale)

• Barbican (data encryption)

Each of the core services in HP Helion OpenStack ships with additional plugins that

enhance the overall interoperability of the system. For a full list of currently

supported and planned projects, visit docs.hpcloud.com.

Identity service (Keystone)The OpenStack Keystone service facilitates user authentication (commonly referred

Each of the core services in HP HelionOpenStack ships with additionalplugins that enhance the overallinteroperability of the system.

to as “login”) and access authorization for allOpenStack services. Keystone supports aplugin architecture that enables it to beintegrated with external authenticationsystems like LDAP or Microsoft Active

Directory that are commonly used by enterprise customers for central userauthentication as well as diHerent types of authentication methods such as Multi-Factor Authentication (MFA). These integration options are conIgured by the cloudadministrator during the initial system conIguration. Keystone also provides a built-in user management system that is targeted at proof of concept or smalldeployments.

Upon successful authentication, users registered with HP Helion OpenStack receive atoken that identiIes them within the cloud. This token is used to obtain access toNova, Glance, Swift, and other HP Helion OpenStack components. The token is alsoused to identify the user roles that are assigned by the cloud administrator and arespeciIc to each OpenStack service. Keystone also provides a service catalog thatlists the accessible OpenStack service API endpoints (via a URL).

Support for organizing users, resources, and security groups is available via theKeystone project entity. Membership in a project is determined by the Keystoneadministrator and can be autopopulated based on external LDAP and MicrosoftActive Directory membership information. Keystone also provides support for anorganizational level called domains. Domains provide the means to organize a multi-tenant HP Helion OpenStack implementation by providing secure organizationalboundaries with each domain having its own administrator, projects, resources,policies, and users that are not shared with other organizations. Each domain can beconIgured to authenticate users from a separate authentication source. Forexample, an HP Helion OpenStack deployment could have an internal domainintended for employees that is conIgured to authenticate against the enterpriseMicrosoft Directory and an external domain intended for partners and customersthat is conIgured against a separate authentication source.

Image service (Glance)Glance is used to discover, register, retrieve, and manage the catalog of the virtual

machine images within an HP Helion OpenStack cloud. Unlike database or ^le system

backups, virtual machine images store the complete state of a machine and its ^le

system, letting you stop and restart them at a later date. Provisioning a new server,

complete with the software and often the data it needs to operate is now a matter of

loading the virtual image onto a virtual machine. This enables a number of

scenarios:

• At the most basic level, OpenStack cloud administrators may use Glance to create

precon^gured application servers, development environments, staging

environments, and so forth.

• You do not have to limit yourself to single servers. It is possible to store whole

backends containing load balancers, application servers, database servers,

queues, and more saved as virtual machines, ready for deployment at a moment’s

notice.

• If you require an even higher level of sophistication, you can turn parts of your

cloud o] during the day and restart them at night when the prices of energy are

lower. Or if you require continuous availability, you can start and stop parts of

your infrastructure in di]erent time zones so you are always paying less for

energy.

For all those scenarios, you need a robust image management service with a simple

management interface and an API. That is what Glance was created for. It provides

two APIs:

• Metadata API—For managing virtual image metadata. It is used to create,

modify, download, and delete virtual images and their associated metadata

records.

• Binary Data API—For managing actual virtual images. You can use it to store and

download the images.

• Metadata De:nitions API—For describing available key-value pair metadata that

can be used on di]erent types of resources (images, artifacts, volumes, _avors,

aggregates, and so forth).

Glance is independent of the storage medium—you can use it with a local disk array,

network storage, block storage, or object storage.

Metering (Ceilometer)The HP Helion OpenStack metering service, currently based on the OpenStack

Ceilometer API, is focused on the collection and storage of OpenStack infrastructure

and network usage metrics that are used as the information source for general

usage display and for downstream or external showback/chargeback and billing

applications. The metering service collects data that is submitted by and unique to

each OpenStack service, such as network bandwidth used, the creation of a new

compute instance, and the creation of a Cinder or Swift storage volume. This data is

continually submitted by each service, collected by the metering service, and then

stored in a Ceilometer-speci^c database. Access to all collected data is provided by

the Ceilometer API and available to external applications.

Orchestration (Heat)Heat is the template-driven engine project in OpenStack that allows application

developers to describe and automate the deployment of infrastructure. Heat uses a

_exible template language that can specify compute, storage, and networking

con^gurations as well as detailed postdeployment activity to automate the full

provisioning of infrastructure, services, and applications. The orchestration engine is

also capable of performing autoscaling of certain infrastructure elements.

Compute service (Nova)Nova implements the OpenStack cloud computing system and binds all of its

components, using a shared-nothing, modular, messaging-based architecture via

RESTful APIs. Nova is responsible for managing hypervisors and virtual machines.

Nova is not tied to any particular hardware virtualization technology, data store,

identity service, or networking topology. All of its components communicate with

each other via RESTful APIs and are themselves implementation-agnostic. Such an

approach results in a highly _exible framework that can be adapted to new

technologies with as little e]ort as necessary.

HP’s contributions to Nova include adding scalability across Availability Zones and

Regions. HP Helion OpenStack ships with support for KVM and VMware® ESX®

hypervisors.

Block storage service (Cinder)Cinder is an interface between cloud servers and block storage resources. It can be

used to connect cloud servers to high-performance storage resources for I/O-

intensive applications like databases. Cinder volumes can be used to boot virtual

machines or they can be mounted under the servers’ ^le systems.

One particularly useful feature of the Cinder block storage component is the ability

to take snapshots of the data for backup and restore purposes. Within HP Helion

OpenStack, block storage is also used to store backups of virtual machine volumes.

HP Helion OpenStack supports HP 3PAR StoreServ Storage, HP StoreVirtual Storage

and other products in the HP Converged Storage portfolio. Both Internet Small

Computer System Interface (iSCSI) and Fibre Channel are supported. These

enhancements let enterprise customers use HP Helion OpenStack with advanced

storage products and technologies, such as self-managing storage, software-

de^ned storage, or storage federation.

The HP Helion OpenStack community edition ships with the Logical Volume Manager

(LVM) Cinder plugin for raw storage and logical volume support.

Object storage service (Swift)Swift provides a massively scalable and highly available storage solution by relaxing

some of the constraints of traditional ^le systems. Essentially, this type of storage is

built on the idea that all storage hardware fails at every level at some point.

Infrequently encountered failures that would hamstring other storage systems, such

as issues taking down RAID cards or entire servers, are handled gracefully with

object storage. Data objects are stored or retrieved from the Swift cluster using a

RESTful HTTP interface. All client requests are sent to a proxy server that determines

which object servers will store copies of the object or which object server it can

retrieve the object from.

Swift places copies of every object across the cluster in as unique-as-possible

locations: ^rst by region, then zone, then server, then drive. For instance, in a cluster

with three zones, Swift will place the objects in all three zones. In a cluster with one

zone and three nodes, Swift will place objects on each node. Swift does this

automatically. In this manner, failures of disks, servers, network connections, and so

forth, can be sustained without loss of data. Swift clusters scale easily by adding

more nodes.

Swift storage can be used for backup and archives, long-term data retention, and

storing massive amounts of unstructured data that is infrequently accessed. Swift

storage is a good ^t for vertical industry segments like media and entertainment,

^nancial, healthcare, pharmaceuticals, oil and gas, government, and education.

You do not have to run Nova to use Swift; it is a standalone system that happens to

easily integrate with the compute service.

Networking service (Neutron)Neutron is an API that enables network services within HP Helion OpenStack. UsingNeutron you can provision basic connectivity and higher-level network services suchas routing, naming, Irewalling, VPN connectivity, and load balancing. Using Neutronyou can create and manage multiple networks for diHerent traHic types such as:

• Management network—Used for internal communication between OpenStackcomponents for the purposes of monitoring and management.

• Data network—Internal network used by virtual machines managed byOpenStack software.

• External network—Provides access to the Internet.

• API network—Provides access from the Internet to the OpenStack API.

At its most basic level, Neutron manages networks, subnets, and ports.

• Switching—Allows entry of traHic from externally deIned networks (providernetworks). HP Helion OpenStack by default uses Open vSwitch (OVS) as its virtualswitch.

• Routing—Routing is a service that enables traHic to move between twonetworks. HP Helion OpenStack implements distributed virtual router (DVR)technology that optimizes this service by distributing it to all the nodes in anetwork. DVR is an HP contribution to the OpenStack project.

• Security groups—Implement security groups and rule management on a virtualmachine level.

• L4 Services—Neutron manages L4 services such as address translation (NAT),public addressing (FIP), and naming (DNS and DHCP).

• Load Balancer as a Service (LBaaS)—Balances network traHic for virtualmachines, on a per-machine, per-network, or per-protocol basis. Implementssession persistence and application service monitoring.

• Firewall as a Service—Secures traHic at the router.

• Virtual Private Network as a Service (VPNaaS)—Sets up and manages VPNs forextending your cloud’s private networks to other networks. Tenants can createmultiple VPN connections, connect two private networks, and use IKEv1 and IPSecpolicies and strong encryption. Dead Peer Detection is also available as astandard.

Bare metal provisioning (Ironic)Ironic uses industry-standard IPMI technology to provide a remote “hypervisor” forhardware, making physical machines as easy to provision as virtual machines withinthe cloud. Bare metal as a service beneIts any workload that requires the rawperformance of dedicated hardware, i.e., databases, graphics rendering, or high-performance computing tasks. It is also useful for IT service teams providing a self-service portal for hardware management.

When used with HP’s Integrated Lights-Out management controllers, customersbeneIt from tight integration of hardware and advanced technology to accelerateand secure infrastructure deployment.

DNS as a Service (Designate)Designate is an OpenStack service that enables systems administrators and users tocreate, manage, and publish DNS records to a selection of public and private DNSservers. The DNS service can be accessed from the Horizon user interface as well beintegrated into deployment scripts via the Designate CLI and API. The currentlysupported DNS server deployment options included: Akamai, DYN, Microsoft DNS,and PowerDNS.

Monitoring at scale (Monasca)Monasca is an open-source, multi-tenant, highly scalable monitoring solutionintegrated with HP Helion OpenStack. It enables seamless operator monitoring of HPHelion OpenStack clouds via a single pane of glass and native API. Monasca enablesreal-time alerting, data correlation, performance visualization, and capacitymanagement of your HP Helion cloud.

Data encryption (Barbican)Barbican is a platform developed by the OpenStack community that includes aRESTful API designed to provide a complete lifecycle management of keys used forencrypting data and applications. It provides full lifecycle management includingprovisioning, assigning, revocation, storing, expiration, and reporting of keys usedfor encryption purposes, such as protecting data at rest and in transit, digitallysigning applications, and storing SSL certiIcates and passwords. Barbican alsosupports auditing and logging specially addressing compliance concerns.

Its special plugins (contributed by HP) available in the Kilo release include the abilityto store encryption keys securely in FIPS compliant hardware security devices suchas HP Atalla’s Enterprise Security Key Manager (ESKM) and allow for inInite scalingof encryption keys, particularly useful for large ephemeral clouds.

HP Helion OpenStack value-added servicesHP Helion OpenStack value-added services include the following:

Operational Functions:

• Backup and Restore—scripts and procedures are provided for the seed VM,undercloud, overcloud management controller and the MySQL databasedeployed in the controller cluster. These scripts are to be used byadministrators managing the OpenStack Cloud.

• Operational monitoring—Icinga (infrastructure monitoring), Monasca(monitoring at scale), Ops Console (uniIed operations council for HP HelionCloudSystem, HP Helion OpenStack, and HP Helion Development Platform).

• Centralized logging—An open source logging service that collects andaggregates HP Helion OpenStack and HP Helion Development platform systemlogs. The logging service consists of the following open source projects ElasticSearch, Logstash, and Kibana.

• Software De4ned Storage (SDS) using Ceph—Ceph is an open source fault-tolerant, scalable, software-deIned storage system. Built with enterprise classhardware, it delivers uniIed object and block storage with high availability anddurability.

Access to updates and bug 4xes: The Helion download catalog service provides amechanism to download content such as updates and bug Ixes, and install thecontent in the appropriate service (such as the identity service).

hLinux: We provide a core operating system for all compute nodes based on DebianLinux, curated and supported by HP.

Administering HP Helion OpenStackWhile you can run a personal cloud on a single server for testing andexperimentation, real-life enterprise clouds are made up of hundreds or thousandsof servers that need to be managed in an orderly fashion, preferably using agraphical user interface (GUI).

The administration environment of HP Helion OpenStack is made up of three distinctparts:

• The Tenant console used to manage and provision infrastructure—above thecloud.

• The Operations console dashboard for the cloud administrators.

• The Helion download network.

Tenant consoleThe Tenant console is the portal that allows you to manage and provisioninfrastructure—above the cloud. It is a Horizon dashboard with added panels for ourvalue-added services, including additional components and workJows thatimplement a visual interface to the add-on services found in HP Helion OpenStack.

Operations consoleThe Operations dashboard is the portal that allows you to manage and maintain thecloud infrastructure—below the cloud. HP Helion OpenStack cloud administratorscan use it to monitor health and performance, apply/roll back patches, install,enable, or disable plugins, and to scale the cloud in and out.

HP Helion Downloads and ResourcesThe HP Helion Downloads and Resources website is designed to make it easy to

manage, maintain, and update your HP Helion OpenStack environment. The HP

Helion Downloads and Resources website provides access to patching, patch

rollback, content, and other lifecycle management activities that enterprise

customers expect.

Chapter 7

UUse casese casess

In this chapter✓ Who beneAts from HP Helion OpenStack?

✓ Customer use cases

Our customers are using OpenStack technology to build amazing things. We loveseeing how customers use open source technology to make their businesses faster,more eAicient, and more proBtable.

Through HP’s experience with OpenStack technology and our own public cloud, wehave identiBed some very good matches for HP Helion OpenStack and the HP Helionproduct portfolio for enterprises and service providers to consider. Here are somereal life examples of HP Helion customers using our OpenStack technology in action:

Accelerate application testing and developmentA Silicon Valley-based enterprise that helps companies manage subscription servicesneeds to move as fast as its customers. Success hinges on delivering features andscaling as quickly as possible. The company’s senior director of quality assuranceknew a cloud strategy was essential. The only question was which cloud portfoliowas the best Bt for his enterprise. The company chose HP Helion.

Now, the IT department brings new applications to market before customers evenask for new features. IT managers can more rapidly respond to internal requests,even as IT costs go down. The company has moved out of the data center businessand is now focused squarely on creating new opportunities to enrich customerexperience.

Develop and deploy cloud-native applicationsApplications built in the cloud, thrive in the cloud. That is why one of the largestbanks in Europe uses HP Helion OpenStack to develop cloud-native applicationswhile simultaneously supporting existing applications.

The bank can now develop and deploy the mobile applications customers expectwith technology that seamlessly integrates the two most important open sourcecloud tools: OpenStack and Cloud Foundry™ technologies.

Manage large-scale object storageThere are few companies in the world with larger data storage needs than a Tokyo-based manufacturer of copiers, printers, digital cameras, and other industrialproducts. Even with its own virtualized infrastructure in a data center, themultinational corporation was having issues with data back-up. That’s when theInformation Infrastructure Control Department turned to HP Helion for help.

HP Helion’s Public Cloud Object Storage is based on OpenStack technology and anideal solution for backing up data across a range of formats, precisely the challengethe company was aiming to solve. “[A server] environment that would have takenmonths to prepare on-site can now be oAered in a matter of days,” says thecompany’s chief of Information Infrastructure Control Department.

HP Helion OpenStack is an especially attractive proposition for enterprise and

service provider customers who want to maintain compatibility with the OpenStack

platform and also get enterprise-grade functionality and support.

Of course we use HP Helion here at HP. This year, HPIT used the HP Helion

Development Platform (integrated with HP Helion OpenStack) to build, deploy, and

then continuously improve a custom app for SXSW. The app was up and running in

just three days, and the lead developer praised the minimal interruptions between

development and deployment.

The bene^ts are measured in more than time saved. HPIT recently asked Deloitte to

study how PaaS in_uences the total cost of ownership for 420 of our custom apps.

The study found that PaaS saves HPIT between 28-42%, resulting in signi^cant

^nancial savings.

HP IT is in the process of migrating current applications to the cloud and building

cloud-native applications with a target of 100% deployment using HP Helion

OpenStack.

Chapter 8

WherWhere do I ge do I go fro from herom heree??

In this chapter✓ Online resources

For more information on HP Helion, HP Helion OpenStack, the OpenStack

Foundation, and OpenStack technology please visit these online resources.

Online resources

• To learn more about HP Helion OpenStack, visit hp.com/helion/openstack and

docs.hpcloud.com/helion/openstack/1.1/technical-overview/

• To access the HP Helion Downloads and Resources website, visit

helion.hpwsportal.com

• To learn more about HP Helion, visit hp.com/helion

• To learn more about HP Helion Development Platform, visit hp.com/helion/

devplatform

• To learn more about OpenStack technology at HP, visit hp.com/cloud/openstack

• For OpenStack and HP Helion OpenStack training, visit the HP Helion Education

Services site: http://h10076.www1.hp.com/education/cloud.htm

• To learn more about the OpenStack community, visit openstack.org and

docs.openstack.org

• To learn more about OpenStack technology read, “OpenStack Cloud Computing:

Architecture Guide,” available at www.amazon.com/OpenStack-Cloud-

Computing-Architecture-Guide/dp/0956355684/

ref=cm_sw_em_r_dp_VSkvtb051JVZCVME_tt

AcknowledgmentsAt HP Press, our goal is to create in-depth technical books of the best quality andvalue. Each book is crafted with care and precision, undergoing rigorousdevelopment that involves the expertise of members from the professional technicalcommunity. We would like to acknowledge the team of experts who helped bring thisbook to market.

Author: Lisa-Marie Namphy (original edition published May 2014, written by Lisa-Marie Namphy and Jacek Artymiak)

Illustrator: Craighton Berman

HP Press Program Managers: Michael Bishop (HP) and Deena Patel/Anne-SophieGombart (EPAC)

HP Thought Leaders and Signi�cant Contributors:Tim Cuddy Bill HilfJ.R. Horton Jerome LabatWilliam L. Franklin Monty TaylorRoger Levy Tim LebelDeborah Martin Mark PerreiraDevananda van der Veen Matt Young

Other editors and contributors: Arlene Boyd, Jonathan Bryce, Robert Cathey, VikasDeolaliker, Joy Dorairaj, Rick Evans, Alex Gronke, Michael Hinnant, Paul Holland, MonuPradhan, Sanjay Sharma, Nissa Strottman, Travis Tripp, and Mudasser (Maz) Zaheer

Publisher: HP Press

We want to hear from you. Send email to hppress@epac.com.

HP HEADQUARTERSHewlett-Packard Company3000 Hanover StreetPalo Alto, CA 94304

About this bookThis book is meant to explain how cloud computing is a solution to the problems facingdata centers today and to highlight the cutting edge technology (including OpenStackcloud computing) that HP helped bring to the stage that it is today. If you are a CTO,data center administrator, systems architect, or an IT professional looking for anenterprise-grade, hybrid delivery cloud computing solution that’s open, trusted, andreliable, we wrote this book for you.

This book is also for (and dedicated to) all you pioneers who fearlessly pushed theneedle forward and moved the industry to the next major phase of its technologylifecycle. We had a great time producing this book and we hope you will enjoy reading it.

About HPHP creates new possibilities for technology to have a meaningful impact on people,businesses, governments, and society. As the world’s largest technology company, HPbrings together a portfolio that spans printing, personal computing, software, services,and IT infrastructure to solve customer problems. More information about HP (NYSE:HPQ) is available at www.hp.com.