openstack evaluation report

OpenStackEvaluationReportPage1

OpenStackEvaluationReport

28August2015

Version1.3


TableofContents

DocumentHistory

DocumentScope

ExecutiveSummary

Introduction

Prerequisites

EvaluationDetails

Testrun1

Testrun2

Testrun3

Testrun4

Results

InstallationInformation

UsageInformation

EvaluationResult

Appendix1:SuggestionsforEvaluationProcedureRevisions


A. DocumentHistory

RelevantSections Version Date Changes Author

EntireDocument 1.0 04/23/2015 CreatedDocument

JasonCharcalla

EntireDocument 1.1 05/07/2015 Majoredits JasonCharcalla

EntireDocument 1.2 07/30/2015 Majoredits PeterEnstrom,JasonCharcalla

EntireDocument 1.3 08/28/2015 FinalDraft Peter Enstrom,Jason Charcalla,Robert Budden,DerekSimmel


B. DocumentScope

ThisdocumentistheevaluationreportforthefunctionalevaluationofOpenStack.TheresultsoftheevaluationandthecollectedinformationhereareintendedforthebenefitoftheXSEDEprojectandthegeneraleSciencecommunity.


C. ExecutiveSummary

AnevaluationoftheOpenStackIcehouseandJunoreleaseswasperformedbytheTechnologyInvestigationService(TIS)evaluationteamledbyRobertBudden.TheothermembersoftheevaluationteamwereJasonCharcalla,andDerekSimmel.TheteamevaluatedmultipleversionsofOpenStack,apublicandprivatecloudsoftwarestackthatallowsuserstoprovisionvirtualandphysicalresources.TheteamhasconcludedthatOpenStackprovidestechnologiesthatwillbeessentialtoXSEDESPcloudoperationsinthenearfuture.XSEDESPoperationsstaffshouldbecomefamiliarwithOpenStackasitisrapidlyemergingasthedefactostandardforvirtualizedinfrastructuredeployment.

OpenStackisacomplexsuitethatprovidesanabstractionlayerforalldatacenterinfrastructureandservices.Assuch,OpenStackdeployment,monitoring,maintenanceandoperationrequiresateamofstaffwithknowledge,rolesandresponsibilitiesthatcovertheequivalentspaceasforconventionalmachineroominfrastructureandservicedeployments,includingsystemsmanagementandadministration,networking,security,userinterfacesandusersupport.

WerecommendadoptionofOpenStackforlarger-scaleimplementationswithenoughstaffandresourcesdedicatedtoitforlongtermoperation.ProjectsinterestedintheservicesandcapabilitiesprovidedbyOpenStackarewell-advisedtoidentifyandworkwithanexistingproduction-qualityoperatorofOpenStackinfrastructureratherthanto“rolltheirown.”

OncefamiliarizedwiththevariouscomponentsadministratorsshouldfindthatOpenStackprovidesareliableplatformforinfrastructureservicevirtualizationthatismaturingatagrowingrate.

Teamrecommendssoftware:YES


D. Introduction

OpenStackisalarge,complexcollectionofopensourceprojectsthatcombinedprovideenduserstheabilitytoprovisionvirtual(andphysical)machines,networks,storageandotherresources.OpenStackisanabstractionlayerwhichprovidesthetoolsnecessarytoimplement,scale,andsupportlargepoolsofcomputing,storageandnetworkresources..

OpenStackenablesorganizationstoprovideendusersandcustomerswitharobustselectionofPAAS(platformasaservice)andSAAS(softwareasaservice)offeringsoutofthebox.OpenStackcurrentlysupportstheprovisioningof“baremetal”servers,Linux(LXC)andDockercontainers,aswellastypicalKVMvirtualmachinesupport.Additionallyitprovidestheabilitytoprovisionnetworks,storageresources,anddatabaseservices.TheupcomingOpenStackproject‘Sahara’introducesbigdataprocessingcapabilitieswithHadoop.

EssentialcomponentsofOpenStackincludeKeystone(Accountmanagement),Nova(Computeresourcesandscheduling),Neutron(Networkprovisioning),Swift(objectstorage),Glance(Imagecatalogue),andCinder(blockstorage).Mostoftheseprojectsrelyheavilyonvariouscommonopensourcetechnologiessuchasdatabases,LVM,DHCP,messagequeuing(RabbitMQ,Qpid,ZeroMQ),OpenvSwitch(OvS),OpenFlow,andothers.Thesecombinedtechnologiesallowittovirtualizeanentiremachineroom,resultinginaninfrastructureprojectthatisverycomplicatedandhardtomasterwithoutexpertsupport.Thefollowingillustrationfromthewww.OpenStack.orgwebsite1providesahigh-levelviewoftheOpenStackecosystem:

OpenStackhasinrecentyearsrapidlygainedamajorshareofthepublicandprivatecloudinfrastructureprovidersaroundtheglobe.Turnoutforthebi-annualOpenStackSummitconferencehasgrownfrom75in2010toover6000inMay2015.TheannualOpenStackSummitandOpenStackDeveloperconferencescoincidewiththe6monthOpenStackreleasecycle,which

1http://www.openstack.org/themes/openstack/images/openstack-software-diagram.png


combinedwithoutstandingcommunitysupporthasfurtherfueledtheproject’sexplosivegrowth.

AsmorecomputationalresourcescontinuetomovefrombaremetaltoIAAS(Infrastructureasaservice)cloudimplementations,OpenStackmaybecomeanessentialpieceinXSEDE’sSPinfrastructure.TheOpenStack-basedNSFChameleonandCloudLabprojectsandforthcomingPSCBridgesandTACC/IUJetStreamsystemshighlightXSEDE’sgrowinginterestinOpenStackasanessentialinfrastructuretechnology.ThisTISevaluationprovidesvaluableadvanceexperimentationanddocumentationfortheseprojectstobuildupon.

OpenStackcanbeinstalledonvariouscomputeandnetworkhardwareplatformsaswellasvariousflavorsofLinux.SeveralmajoroperatingsystemvendorshavebeguntopackagetheirowndistributionofOpenStack.Inthisevaluation,wechosetoimplementonCentOSusingRedHat’sRDOinstallationscripts.RDOisnotanacronym;itisthenameofaprojectstartedbyRedHattobuildadistributionofOpenStack.TheRDOproductreliesheavilyonthePuppetconfigurationmanagementtooltoensuretheconsistencyofserviceandnodeconfigurations.TheteaminvestigatedtheRDOinstallationprocess,administratorfeaturessuchasusermanagement,andenduserfeaturesincludingCLIandweb-basedprovisioningofvirtualresources.

Prerequisites

PrerequisitesforasuccessfulOpenStackdeploymentincludemultiplededicatedservers,withstorageandappropriatenetworking,includingavailabilityofpubliclyaccessibleIPaddressesforvirtualsystemsthataremeanttobedirectlyaccessiblebyremoteusers.ThebaseoperatingsystemforOpenStackinfrastructureandcloudnodesistypicallyawell-supportedLinuxdistribution.Forthepurposesofthisevaluation,wehaveemployedCentOS6.6andCentOS7.1.AswehavechosentoimplementOpenStackusingtheRedhatRDOdistribution,accesstotheRedhatRDOrepositories


(https://www.rdoproject.org)isalsonecessary.

BasedonourexperimentationusingIcehouse,Juno,andKiloreleasesofOpenStack,acompleteandself-containedRedHatRDOinstallationofOpenStackmaybedeployedonasinglesystemwiththefollowingminimumhostsystemcapacities:

● 8GBRAM● oneormoremulti-corex86_64IntelXeonorequivalentprocessors● 100GBlocaldisk(CentOS7+OpenStackinstallationoccupies~6.2GB)● oneormorenetworkinterfaceswithatleast1Gb/sthroughput

Inaddition,itishelpfultohaveaprivateadministrativeconsoleinterfaceavailableviaIPMIorserialconsoletothehostsystemsonwhichtheOpenStackinstallationisoperating.Itisessentialthattheseadministrativeinterfacesarestronglysecuredagainstpublicaccess;ideallytheseinterfacesshouldincorporatemulti-factorauthenticationmethods.

Inamultinodeconfiguration,specialattentionmustbepaidnetworktopology.AlthoughitistechnicallypossibletodeployOpenStackwithasinglenetworkinterfacepernode,theteamrecommendsaminimumoftwo.ThismethodallowsyoutoisolateOpenStackmanagementtrafficfromthe(user)tenantNeutrontraffic.ItshouldalsobenotedthatOpenStackprovidesitsownDHCPservices;therefore,unlessyouhaveanisolatedsubnet,coordinationwithyoursite’snetworkadministrationteamwillberequired.

FortheJunoandKiloreleasesofOpenStack,therecommendedbaseoperatingsystemfortheRDOinstallationhostisRedHatEnterpriseLinux7oritsequivalent.CentOS6canbeusedforpreviousversions.WeemployedaminimalinstallationofCentOS7forthispurposeinthisevaluation.


E. EvaluationDetails

Therequirementsdefinedforthisevaluationwere:

● Thesoftwarewillnotifyadminsofservicefailures.● ThesoftwarewillallowuserstodeployVMsquicklywithinanenvironmentthatwillallow

useofcustomnetworksettings,licensekeys,anduserdefinablecomputeresources.● Thesoftwarewillprovideusererrormessagesthatareappropriate,usefulandnon-cryptic.● Thesoftwarewillallowper-projectnetworkstobecreateddynamicallybyauser● ThesoftwarewillprovidemultiplewaysforausertoaccesstheirVMs(directSSHtopublic

IP,dashboardconsole)● Thedashboardinterfacemustbeeasytolearn.● ThedashboardinterfacemustallowuserstouploadanddownloadVMimages

DuetoOpenStack’ssizeandcomplexity,thetestplanwasdesignedtotouchuponalimitedbutsufficientcollectionofcomponents.ThisincludestheinstallationprocessviatheRDOdeploymentscripts,modifyinganexistingOpenStackcluster,andsimpleandcomplexvirtualmachineprovisioningthatemulatestheuserexperience.Administrativefeaturessuchasusermanagementandtroubleshootinglogswerealsoincluded.

OpenStacktestdeploymentswereconfiguredatbothPSCandNICS.

PittsburghSupercomputingCenter(PSC):

SeveraldifferentsystemswereemployedtoprototypeandlearnaboutRDO-basedOpenStackdeployment.Afinaltestsetupwasdeployedusingthreeservers,namedriverrun.psc.edu,winterfell.psc.eduandthunder.psc.edu.TheriverrunandwinterfellnodeshaveSupermicroX7DBNmotherboardswith8-coreIntelXeonE5345processorsrunningat2.33GHzand8GBRAMinstalled.ThethundernodeisanoldernVidia-basedsystemwithadual-coreAMDOpteron165processorrunningat1.8GHzand4GBRAMinstalled.Allthreenodeshavepairsof250GBor512GBlocalSATAharddrives.Completeandself-containedRDOinstallationsofOpenStackweremadeonriverrunandwinterfell,andthunderwasaddedasanadditionalcomputenode.TwoIntele10001GbpsnetworkinterfacesoneachnodewereconnectedviaCAT5coppertoalocalCiscoswitchinaconventional(i.e.,non-trunk)mode.

NationalInstituteforComputationalSciences(NICS):

TheNICSOpenStackdeploymentconsistof6Cray(Appro)bladeswithdedicatednetworkswitchinghardware.EachbladehasasingleIntelXeonE5-2670processorrunningat2.6GHzwith64GBRAMand1TboflocalSATAHDDstorage.Adedicated1GbpsEthernetswitchisutilizedforallmanagementtrafficwhileNeutronnetworkingoperatesonaseparate10GigEinterface.NeutronwasconfiguredinVLANmodewithmultipleVLANstrunkedtoeachcorresponding10GigEportallowingtenantnetworkstomaptoaVLANforeaseofadministrationandtroubleshooting.All6nodessitbehindasingleloginserver.This


allowsforaddedsecurityinthatallOpenStackAPIendpointsandvirtualmachinefloatingIP’sresideinanon-routablesubnetonlyaccessiblefromthedesignatedloginmachine.TheloginserverrequiresstandardNICSRSAOne-TimePassword(OTP)authentication.AdditionallythisallowsformorefloatingIP’stobeavailable.

TheIcehouseversionofOpenStackwaschosenforthisinstanceasitwasthecurrentversionatthetime.Theclusterisconfiguredwithonecloudcontrollernode(Keystone,Cinder,Swift,Nova,andHorizon),onenetworknode(Neutron),and4cloudcomputenodes(Nova).

Testrun1-CloudInstallation:

InthisfirsttestOpenStackwasinstalledonmachinesatbothPSCandNICS.AtPSC,Junowasinstalledonthemachinesriverrun.psc.eduandwinterfell.psc.edu.AtNICS,IcehousewasinstalledontheThunderheadsystemwhichiscomprisedof6Cray(Appro)bladesandcanbeaccessedfromitsdesignatedloginnode.

● InstallOpenStackviatheRDOinstalltool,asdescribedathttps://www.rdoproject.org/Quickstart

● Testthattheinstallwasasuccesswithvariousweb-basedandCLIcommands.● AddanadditionalcomputenodetotheclusterusingtheRDOpackstackutility.

Testrun2-Simplenodeprovisioning:

ThesimplenodeprovisioningtestsevaluatedtheabilityforuserstoprovisionvirtualmachinesfromboththeCLIandHorizondashboardwebinterface.ThesetestsweredesignedtoexerciseprovisioningofmultipleVM’ssimultaneously.Theyalsoincorporatedsituationsdesignedtoinduceerrorstoensuretheywerereportedinauser-friendlyway.

● SuccessfullylogintotheHorizondashboardorsourcetheprovidedCLIkeystonerc_adminfilegeneratedbyRDO.Thekeystonerc_adminfilecontainslogincredentialsandtheauthenticationURLofthekeystoneservice.

● ProvisionasinglevirtualmachineinstancewiththeappropriateSSHkey,securitygroups,andnetworkconfiguration.

● LogintothenewinstanceviaSSH.● Provisionanewinstancewithadditionaldisk,memory,andCPUresources(flavors).● Provisionfivevirtualmachinessimultaneously.● Provisiontenvirtualmachinessimultaneously.● Attempttoprovisionmoremachinesthanyourquotawillallowandrecordtheerror.

Testrun3-Complexnodeprovisioning:

ThecomplexnodeprovisioningportionofthetestsevaluatedtheabilitytoattachpersistentblockstoragedevicestovirtualmachinesviatheCinderAPIs.Theteamalsotestedadvancednetworkingfunctionalitiesbyassigningmultiplevirtualnetworkstorunningvirtualmachineinstances.


● CreateandattachaCinderblockstoragevolumetoavirtualmachineinstance.● Verifyblockstorageiswritableandpersistent.● Createandattachmultiplenetworkstoavirtualmachineinstance.● Performbasicnetworktestingwithpingandiperf3.

Testrun4-Cloudmanagement:

TheteamtestedadministrationfunctionalityofOpenStack.ThesefeatureswouldbeusedbyusersupportstaffinafulldeploymentandnotjusttheOpenStacksystemadministrators.Becauseofthis,errorreportingforbasicfeatures(e.g.,duplicateuserandfailedauthenticationattempts)wereincorporatedintotheevaluation.Usermanagementfunctionalityincludingaddingnewusersandprojects(“tenants”),aswellastheabilitytouploadcustomimagesandtoconfiguretenantnetworkswerealsotested.

● AddusersandtenantsviatheCLItoolsandverifytheycanlogintoHorizon.● AddatenantNetworkandrouter.● Addapubliccloudimagethatisaccessiblebyallusers.● Verifyerrormessageswereloggedfortroubleshooting

TestRunResults

PSC:

TheRDO-basedinstallationmethodprovidesaquickwaytogetaworkinginstallationwiththeprimarycomponentsofOpenStackdeployed.RDOhandlesthegorydetailsandmanualsetupofpasswords,authenticationkeys,databases,andnumerousconfigurationfiles.Atthestartofthisinvestigation,aHavanasetupwasmanuallysetupatPSCwithouttheaidofRDO,whichwasimmenselymorecomplicatedandtimeconsumingthantheautomatedRDOinstallation.

AsoftheJunorelease,theconfigurationofnetworkinginterfaces,virtualroutersorswitches,andpoolofaddressesforVMinstancesrequiresmodificationofnetworkinterfacedefinitionspriortoRDOinstallationofOpenStack,whichisnotinitiallyobvious.AccesstorunninginstancesofVMsfromexternalsystemsalsorequiresmodificationsthatarenotwell-documented.

AsoftheJunoandKiloreleases,therearestillsomequirkswiththeinitialnetworkingsetup,specificallywiththehostportionoftheadvancednetworkingservice,Neutron.RDOattemptstoeditthefilesin/etc/sysconfig/network-scripts/ifcfg-XXXtomigrateRedHat/CentOS6-styleeth#interfacestoanOvSbridge.MostoftheconfigurationisdoneproperlybuthandcheckingisrequiredBEFORErebooting.Namely,theuseofsystemdconventionsdefaultontheRedHat/CentOS7hostOSmayneedtobereverted(i.e.IPADDR0,GATEWAY0,etc.).The/etc/sysconfig/network-scripts/ifcfg-br-exnetworkinterfaceconfigurationfileneedstobemanuallycorrectedafterRDOrunstodefineaworkingconfigurationasanOVSBridgeinterfacetotheexternalnetwork.ItisadvisabletohaveasecondaryprivatenetworkinterfacerunningorIPMIincaseofconfigurationerrors,sothatthehostremainsaccessibleviaasecuredIPMIorothersecondaryconsoledespite


networkconfigurationproblemsontheprimaryexternalnetworkinterface.

Additionally,theinternalNeutronconfigurationislefttotheadministrator.ScriptsweredevelopedandareavailableontheXSEDEwikitoaid/automatetheinitialsetupofexternalnetworks,project/tenantvirtualrouters,andprivatevirtualsubnets.ThesepiecesarerequiredtosuccessfullydeployvirtualmachinesunderOpenStack.Thescriptandsampleconfigurationfilecanbefoundat:https://www.xsede.org/web/staff/staff-wiki/-/wiki/Main/OpenStack+Cloud+Evaluation#section-OpenStack+Cloud+Evaluation-KiloNeutronConfigurationSimplified

OnekeyissuewithRDOandNeutronisthatthedefaultDNSMasqsetupisnotconfiguredproperly;thisbreaksSNATconnectivityfromspawnedvirtualmachines.Itisnecessarytoedit/etc/neutron/dhcp_agent.iniandupdatethednsmasq_dns_serversanddhcp_domainlinesaccordingly.Thesevaluesarerequiredforcorrectvirtualrouteroperation.

Whendeployingamulti-nodeOpenStacksetupusingRDOandusingNeutronfornetworkmanagement,itisimportantNOTtousethe--all-in-oneoptioninthepackstackanswersfile.ThisconfigurationoptionaffectstheinitialOVSbridgesetupandmayintroduceproblemsduringthe“addacomputenode”phase.

NICS:

NICSutilizedtheRDOinstallationmethodaswell.WhileextremelyusefulinensuringthatnopiecesofOpenStackareoverlookedduringtheprocess,severalattemptswererequiredtoproduceaworkingRDOanswerfile.Theteamencounteredmultipleinstanceswhereerrorswerenotcorrectlyreportedorhadlittledocumentation.Themajorityoftheseissuesgravitatedaroundthenetworkingcomponents.AthoroughunderstandingofnetworkingandaproperimplementationplanareessentialtoproducingaworkingRDOdeploymentofOpenStack.

OpenStackisstillanactiveandrapidlydevelopedsoftwarewhichismaturingquickly.Atthetimeofthiswritingtheversionsourteamtestedhavebeensupersededbynewerreleases.Thecurrentrelease,Kilo,wasmadeavailableApril30,2015,withthefollowonrelease,Liberty,scheduledforOctober2015.Becauseofthe6-monthreleasecycle,thedocumentationandinstallproceduresarenotaspolishedandcurrentasdesired.InitialplanningofacloudinfrastructurebasedonOpenStackisproblematic,duetothecomplexityofOpenStack,itslargenumberofconfigurationoptionsandnumerouscomponentservices.Additionally,vagueerrormessagesaddtothedifficultylevelandincreasetheslopeoftheOpenStacklearningcurve.TheteamagreesthattheseissueswillprobablybeworkedoutastheprojectmaturesandgreaterexperienceisgainedwiththeOpenStackecosystem.ItshouldbenotedthattherapidlygrowingOpenStackcommunityisworkinghardtoreducethecomplexityoftheinstallationwiththedevelopmentofmultipleopensourceandcommercialproductsfordeployment.

Onceallthepiecesareinplaceandfunctioningcorrectly,OpenStackfunctionsasarobustcloudsoftwarestackprovidinguserswithmultiplemethodsforprovisioningandmaintainingvirtualmachinesandotherresourcessuchasstorageandcustomnetworkingsetups.


F. InstallationInformation

Asacollectionofprojectsandcommonlyusedopensourcesoftware,OpenStackhasmultipleinstallationmethods.Themosttime-consuming(albeitinstructive)oftheseoptionsistomanuallyinstallallofthevariouscomponents.Becauseofitsoverallcomplexity,theteamchosetouseRDO,aRedHat-sponsoredOpenStackinstallertool.RDOgreatlysimplifiestheprocessbyallowingtheadministratortoselectalldesiredcomponentsinasingleanswerfile.ThisanswerfileisthenusedtodeployalltherequiredandselectedcomponentsonasingleormultinodeOpenStackcluster.AhighleveloverviewoftheRDOinstallationprocedureissummarizedasfollows:

1. Determinewhathardwarewillbecomethecontroller,networking,andcomputenodes.Cablethemanagementandneutronnetworkconnectionsaccordingly.

2. InstallRedHatorCentOS(version7recommended)onallnodesandensureinstalledsoftwareandservicesareuptodateviayumupdate.

3. ConfigurenetworkanddocumentinterfacesplannedforuseinOpenStack.4. Onadedicatedcontrollermanagementnode,installtheRDOpackagerepositoryand

packstackpackage:a. `yuminstall-yhttps://rdoproject.org/repos/rdo-release.rpm`b. `yuminstall-yOpenStack-packstack`

5. Foramulti-nodeinstallation,generateandmodifythedefaultpackstackanswersfiletoyourenvironment:

a. `packstack--gen-answer-file=packstack-answers-file.txt`6. Runthepackstackcommandwiththegeneratedanswerfile:

a. `packstack--answer-file=packstack-answers-file.txt`Uponrunningpackstack,itwillrequesttherootpasswordforeachnodeandenablepasswordlessSSHwiththemusingpublickeyauthentication.PuppetmanifestfilesgeneratedbypackstackensurethatalloftheOpenStackcomponentsareinstalledandconfiguredconsistently.


G. UsageInformation

AdministratorsandusershavemultiplewaystointeractwithOpenStack.TwoofthemostcommonmethodsaretheHorizonwebdashboardandtheOpenStackCLItools.RestfulAPIendpointsarealsoavailableforadvanceduserstowritetheirowncustomuserinterfaces.Horizondashboardaccessiswelldocumentedandwillnotbecoveredinthissection.

CLIaccessrequirestheinstallationtheOpenStackclienttoolsandcreationofakeystone_rcfile,whichissourcedintheuser’sshelltosetuptheenvironmentandprovidelogincredentialstotheclienttools.EachOpenStackprojecthasitsownCLItoolswhichareinstalledviathepythonpippackagemanagementsystem.Forexample,theNovaclientmaybeinstalledvia`pipinstallpython-novaclient`.Thenamingconventionfortheclienttoolsavailableviapipis“python-<OpenStack-Project-Name>client”.


H. EvaluationResult

WeattributesomedegreeofthedifficultiesencounteredingettingtheOpenStackinstallationsoperatingfortestpurposestoourowninexperiencewiththeproduct.TheRedHatRDOdistributionofOpenStackdoesmuchtoenablearapidinitialdeploymentofOpenStack,butdoesnotrelieveusoftheresponsibilitytomastertheessentialconfigurationknowledgeandskillsrequiredtooperateanOpenStackecosystem.ItremainsessentialforoperatorstofullyfamiliarizethemselveswiththecomponentsandmethodsofinstallationdetailedintheOpenStackdocumentationmatchingthereleasebeingused(e.g.,theOpenStackJunodocumentationforRedHatandrelatedLinuxdistributionsavailableathttp://docs.OpenStack.org/juno/install-guide/install/yum/content/).

TheOpenStacklearningcurveisfairlysteep,andtherapidpaceofOpenStackdevelopment,withmajorreleasesevery6months,requiresOpenStackoperatorstocontinuouslydedicatetimeandresourcestostayingabreastofOpenStackdevelopments.ItisthereforeprudenttoconsiderOpenStackasasoftware-basedoperationsecosystemthatrequiresasufficientlylargeteamofoperatorstodesign,deploy,operate,monitor,supportandmaintain,muchasonemightdoforaconventionalHPCsystemsmachineroom;theteamshouldincludememberswithknowledge,skillsandassignedresponsibilityfordesign,implementation,operationandmaintenanceinareasincluding:

● infrastructureacquisitionandscalingfortheOpenStacksoftwareitself● OpenStacksoftwareadministrationandmaintenance● networking,networkvirtualizationtechniques,andsoftwaredefinednetworking(SDN)● riskassessmentandpolicydefinition● securityinstrumentation,monitoring,andoperations● virtualmachines(KVM),(Docker)containersandapplications,and“baremetal”system

building● librarystewardshipforVMs,applications,andsystemimages● userexperiencedesignanduserinterfacedesign

WerecommendadoptionofOpenStackforlarger-scaleimplementationswithenoughstaffandresourcesdedicatedtoitforlongtermoperation.ProjectsinterestedintheservicesandcapabilitiesprovidedbyOpenStackarewell-advisedtoidentifyandworkwithanexistingproduction-qualityoperatorofOpenStackinfrastructureratherthanto“rolltheirown.”


I. Appendix1:SuggestionsforEvaluationProcedureRevisions

1. GiventhescopeandcomplexityofinfrastructuremanagementecosystemssuchasOpenStack,progressmaybefacilitatedbyhavingtheentireevaluationteamworkthroughanddocumentimplementationstagesandteststogetherinaseriesofclosedworkshopsessionsconductedatasinglesite,withsitesubjectmatterexpertsavailableforconsultationasneeded(e.g.,sitenetworkadministrationstaff).

openstack evaluation report

Documents