SGI and SUSE OpenStack Cloud Reference Architecture...Table of Contents page Introduction ...

Table of Contents page

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Solution Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Solution Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Appendices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

SGI and SUSE® OpenStack Cloud Reference Architecture

White PaperSUSE.OpenStack.Cloud

2

SUSE OpenStack Cloud White PaperSGI and SUSE OpenStack Cloud Reference Architecture

This.private.cloud.instance.can.be.used.for.any.of.the.typical.use.cases,.but.the.primary.motivation.is.for.High.Performance.Computing.(HPC).customers.who.might.require.an.environment.for.investigations,.proof-of-concept.and.overflow.types.of.activi-ties.beyond.their.normal,.dedicated.HPC.resources ..The.docu-ment.discusses.key.areas.of.integrating.SGI.Rackable,.scale-out.and.specialized,.SGI.UV.scale-up.computing.hardware.with.SUSE®.OpenStack.Cloud.software.while.including.specific.infor-mation.to.leverage.the.highly.automated.nature.of.the.software ..Following.these.recommendations.and.best.practices.will.allow.an.organization.to.quickly.and.confidently.deploy.the.required.infrastructure.that.yields.a.secure,.scalable,.performant,.highly.available.private.cloud.instance.for.HPC.workloads,.whether.tar-geting.testing,.development.or.production.usage.of.the.services .

The.target.audience.is.IT.professionals.responsible.for.setting.up,.configuring,.administering.and.operating.a.private.cloud.infrastructure .

Solution OverviewWhile.public.cloud.services.have.existed.for.some.time,.a.private.cloud.enables.companies.to.take.advantage.of.the.benefits.of.cloud.computing.with.less.risk.of.data.exposure.and.more.con-trol.of.resources.because.it.is.operated.behind.the.local.corpo-rate.firewall ..Private.cloud.resources.can.be.used.across.many.groups,.delivering.access.to.IT.resources.and.abstracting.the.complex,.internal.infrastructures.from.end.users ..This.abstrac-tion.also.applies.to.development.and.information.technology.operational.professionals.(DevOps) ..It.allows.individual.virtual.machines.or.workloads.to.be.provisioned.on.demand,.subject.to.allowed.quotas,.from.predefined.templates.with.little.concern.about.the.underlying.infrastructure.or.resources ..Services,.con-sisting.of.many.workloads,.can.be.provisioned.for.use.in.min-utes.and.then.scaled.appropriately.to.meet.service.demands ..For.further.reference,.the.National.Institute.of.Standards.and.Technology’s.(NIST).Definition.of.Cloud.Computing1.describes.the.important.characteristics.of.cloud.computing .

Through.integrated,.open.source.software.frameworks.such.as.OpenStack,.enterprises.can.establish.an.Infrastructure-as-a-Service.(IaaS2).private.cloud.that.delivers.on-demand.access.to.pools.of.compute,.storage.and.networking.resources.for.use.within.their.organization,.as.shown.in.the.following.illustration:

IntroductionThis white paper is written to help an organization, already familiar with HPC concepts, create and deploy an on-premises private cloud instance contained within its own network space, using computing and storage resources under its direct control.

__________

1 http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf

2 https://en.wikipedia.org/wiki/Cloud_computing#Infrastructure_as_a_service_.28IaaS.29

http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf

https://en.wikipedia.org/wiki/Cloud_computing#Infrastructure_as_a_service_.28IaaS.29

3www.suse.com

The.underlying.network,.compute.and.storage.resources.can.essentially.be.pre-provisioned.as.necessary.to.meet.the.overall.requirements.of.the.applications.and.services.to.be.deployed.later.in.the.cloud.instance ..Compute.resources.are.provided.via.physical.servers.by.utilizing.a.hypervisor.to.run.virtual.ma-chine.workloads ..Providing.storage.resources.is.accomplished.via.distributed,.resilient.file.systems.across.industry-standard.hardware.with.local.storage.devices ..Networking.provides.the.unifying.connectivity.that.ties.the.compute,.storage.and.man-agement.elements.of.the.private.cloud.together ..Finally,.the.private.cloud.software.provides.the.user.interface.for.setup,.configuration.and.maintenance,.as.well.as.the.long-term.opera-tion.of.the.cloud.by.bonding.these.three.core.components.into.a.cohesive.service.offering .

The.remainder.of.this.white.paper.will.present.a.complete,.ready-to-use.private.cloud.solution ..The.focus.is.to.create.a.starter.cloud.instance,.using.minimal.nodes.yet.with.all.the.fea-tures.included.to.effectively.scale.as.the.usage.grows.over.time ..First,.it.will.discuss.preparations.and.considerations.across.the.various.infrastructure.elements.common.to.the.overall.solution ..Then.it.will.detail.the.steps.required.for.private.cloud.integration,.starting.with.the.setup.of.the.control.plane.and.followed.by.the.storage.and.compute.resources,.along.with.some.easy.ways.to.validate.the.installation.and.functionality.of.all.the.components .

Preparation

FACILITY CONSIDERATIONS

The.heating,.ventilation,.air.conditioning.(HVAC).and.power.re-quirements.for.a.private.cloud.deployment.need.to.be.carefully.

assessed ..As.a.reminder,.ensure.that.calculated.power.consump-tion.and.cooling.take.into.account.the.requirements.of.a.fully.utilized.infrastructure.since.a.private.cloud.instance.is.a.shared.resource.subject.to.the.needs.and.use.of.potentially.many.work-loads.and.users.at.any.given.time ..During.the.project.quoting.process,.resources.from.the.SGI.Site.Planning.team.can.provide.power.and.cooling.specifications.and.requirements.specific.to.the.systems.being.deployed .

NETWORK CONSIDERATIONS

Networking.is.the.technology.component.likely.to.take.the.most.upfront.planning.because.networking.requirements.for.a.pri-vate.cloud.instance.have.a.fair.amount.of.complexity,.especially.when.it.is.being.integrated.into.an.existing.IT.infrastructure.and.network.topology ..This.white.paper.provides.specific.recom-mendations.for.the.networking.topology.often.used.in.HPC.environments.and.equipment.that.meet.both.scale.and.perfor-mance.requirements,.with.later.sections.describing.the.specific.network.subnets.and.virtual.LAN.designations.needed.to.satisfy.the.design.decisions .

For.the.physical.switching.layer,.a.single.48.port.top-of-rack.(ToR).1GbE.switch.is.utilized.for.the.bonded.interfaces.with.separate.1GbE.switches.for.the.BMC.and.for.the.storage.networks,.since.all.the.systems.platforms.have.1GbE.network.interfaces ..Certainly.this.can.be.made.more.redundant.by.adding.a.peer.switch,.be-cause.the.networking.mode.for.the.majority.of.the.subnets.are.bonded.across.multiple.interfaces ..As.usage.grows,.both.the.sys-tem.network.interfaces.and.switches.can.be.upgraded.to.faster.interconnect.speeds ..The.basic.network.topology.is.shown.in.Figure.2.on.the.following.page .

Note:Ensurethatallsimilarswitchingdevicesareconsistentanduptodatewithregardtofirmwareversionstoreducepotentialtroubleshootingissueslater.

Tip:Meticulouscareofthenetworkwiringfromthevariousre-sourcenodesandswitchesmakestroubleshootingmucheasier.Wherepossible,alsolabelconnectionsandsticktoconsistentpatternsofport/placementofconnections,asshowninthefol-lowingillustration.

Figure 1. PrivateCloudUsersandResources

http://www.suse.com

4


At.this.point,.it.is.instructive.to.introduce.the.necessary.network.name.spaces.for.this.private.cloud.instance ..The.name.spaces.and.the.functions.they.provide.are.fundamental.to.a.private.cloud.im-plementation ..The.various.network.ranges.are.needed.to.manage,.operate,.access.and.provide.isolation.for.all.the.components.and.services ..Table.1.summarizes.the.various.network.name.spaces.used.in.this.implementation .

COMPUTING AND STORAGE PLATFORM CONSIDERATIONS

One.of.the.benefits.of.a.private.cloud.implementation.is.that.SGI.Rackable,.scale-out.servers.can.fulfill.many.of.the.needs.for.various.roles ..To.reduce.the.time.spent.on.hardware.specification.for.an.initial.private.cloud.implementation,.this.hardware.set.can.be.very.general.purpose.and.allow.for.a.wide.range.of.configura-tion.options.yet.still.meet.the.demands.of.the.intended.usage .

The.SGI.C2112-4RP43.series.of.servers.deliver.top.value.and.per-formance.with.four.independent.nodes.in.a.single.2U.chassis.and.up.to.12.hard.disk.drives ..In.this.configuration,.each.node.can.fulfill.any.of.the.roles.in.the.private.cloud.instance .

Network Name Space

Network Description/Considerations

Admin bond

Private.deployment.and.management.network.to.access.the.Administration.Server.and.all.nodes.for.administration.purposes ..

.Do.not.allow.access.from.the.outside.and.keep.the.admin.network.completely.separate .

BMC eth0

The.default.setup.lets.you.access.and.manage.any.available.BMC.(Baseboard..Management.Controller).of.the.resource.nodes.via.IPMI.(Intelligent.Platform..Management.Interface).from.this.network ..

.Do.not.allow.access.from.the.outside.and.keep.this.network.completely.separate .

Storage bond (storage nodes)

Private.SUSE.OpenStack.Cloud.internal.virtual.network ..This.network.is.used.by.Ceph.and.OpenStack.Object.Store.(Swift).only ..It.should.not.be.accessed.by.users ..

.Do.not.allow.access.from.the.outside.and.keep.this.network.completely.separate .

Public, Nova-floating bond (control nodes)

The.only.public.networks.provided.by.SUSE.Open-Stack.Cloud ..You.can.access.the.OpenStack.Dashboard.(Horizon).and.all.workload.instances.(provided.they.have.been.equipped.with.a.floating.IP).via.this.public.network ..

.The.public.network.is.accessed.only.by.a.gateway,.which.needs.to.be.provided.externally ..All.SUSE.OpenStack.Cloud.users.and.administrators.need.to.be.able.to.access.the.public.network .

.The.public.and.nova-floating.functions.are.split.to.address.security.concerns,.so.that.the.OpenStack.Dashboard.and.APIs.are.able.to.be.assessed.from..one.range.and.the.floating.IPs.assigned.to.the..workload.are.in.another.network.range .

Software Defined Network (os_sdn) bond:VLAN:400

Private.SUSE.OpenStack.Cloud.internal.virtual.network ..This.network.is.used.when.OpenStack.Networking.(Neutron).is.configured.to.use.Open.vSwitch.with..GRE.tunneling.for.the.virtual.networks ..This.network..is.not.accessed.by.users .

This.VLAN.should.be.enabled.on.all.switch.ports.for..the.admin.network.interfaces .

Private (nova-fixed) bond:VLAN:500

Private.SUSE.OpenStack.Cloud.internal.virtual.network ..This.network.is.used.for.inter-instance..communication.and.provides.access.to.the.outside.world.for.the.instances ..The.gateway.required.is.also.automatically.provided.by.SUSE.OpenStack.Cloud .

Figure 2. SystemNetworkInterfaceandSwitchWiringSchematic

Table 1. NetworkNameSpaceDescriptions

__________

3 www.sgi.com/products/servers/rackable/2u_intel.html

http://www.sgi.com/products/servers/rackable/2u_intel.html

5www.suse.com

In.addition,.the.SGI.UV4.scale-up.systems.can.be.utilized.to.pro-vide.“super.node”.compute.resources,.allowing.very.large.indi-vidual.workloads.or.large.numbers.of.workloads.to.share.this.resource ..Commonly.used.in.HPC.environments,.these.nodes.provide.large.processor.socket.counts.and.huge.shared.memory.capacities.across.a.single.system .

Note:Ensurethatallsimilarsystemdevicesareconsistentanduptodatewithregardtofirmwareversionstoreducepotentialtroubleshootingissueslater.

To.ease.later.setup.and.selection.of.the.system.nodes.for.each.role,.it.makes.good.sense.to.allocate.the.eventual.roles.to.similar.functions.across.the.various.chassis.and.to.collect.some.basic.information.from.each.node.as.shown.in.Figure.3.below .

Figure 3. Allocationofrolesacrossresourcenodes

__________

4 www.sgi.com/products/servers/uv/

http://www.sgi.com/products/servers/uv/

http://www.suse.com

6


SOFTWARE COMPONENT CONSIDERATIONS

The.current,.de.facto.open.source.standard.of.private.cloud.soft-ware.is.OpenStack5 ..Because.of.its.vibrant.ecosystem.of.projects.and.governing.body.overseeing.the.inclusion.and.coordination.of.new.offerings,.each.release.provides.an.ever-expanding.scope.of.functionality ..

SUSE.OpenStack.Cloud6.provides.an.enterprise-grade.implemen-tation.of.OpenStack.components.and.includes.other.tools.neces-sary.for.a.complete.private.cloud.implementation ..Augmenting.the.upstream.OpenStack.projects,.SUSE.OpenStack.Cloud.in-cludes.a.complete.deployment.framework.in.addition.to.provid-ing.core.services.such.as.the.underlying.database.and.message.queue ..With.its.multi-hypervisor.support,.SUSE.OpenStack.Cloud.affords.choice.in.the.virtualization.arena.while.leveraging.exist-ing.expertise;.however,.this.implementation.focuses.on.a.single.hypervisor.technology ..To.meet.the.customer.needs.of.an.inher-ently.multi-user.platform.such.as.a.private.cloud,.both.the.control.plane.and.the.compute.plane.services.are.made.highly.available.to.complement.the.inherent.resiliency.in.the.storage.services .

There.are.four.types.of.nodes.in.a.full.SUSE.OpenStack.Cloud.deployment:

AnAdministrationServerprovidesallservicesneededtosetup,deployandmaintaintheotherthreetypesofresourcenodesintheprivatecloudinstallation.Theprimaryuserofthisnodeanditswebinterfaceisthecloudadministrator.

OneormoreControlNodeshostthecoreOpenStackservicesneededtoorchestratevirtualmachinesdeployedontheComputeNodesandutilizevolumesfromtheStorageNodesintheprivatecloudinstallation.MultipleControlNodescanbeclusteredtogethertoprovidehighlyavailableservices.

TwoormoreStorageNodesactasaproviderofpersistentcloud-basedstorageelementsandcanofferOpenStackObjectStorage(Swift)aswellasCeph-basedoptions.Bothobject-andblock-basedstoragetypesaresupported,giventheunderlyingtechnology.Bydesign,thesestorageservicesareinherentlyresilienttoprotectagainstcomponentfailures.UserswilltypicallyinteractwiththeStorageNodesonlythroughtheuseofvolumesviatheself-serviceclouddashboard.

AnynumberofComputeNodes,eachofwhichisaphysi-cal,dedicatedserverrunningahypervisorandservesasthehostfortheeventualdeploymentofworkloadsandservices.MultipleComputeNodes,usingKVM,canbeconfiguredwithalightweightclustertechnologytomakefailoverofworkloadinstancesautomatic.UserswilltypicallyinteractwiththeComputeNodesonlythroughtheself-servicedashboardserviceastheylaunchtheirVMworkloads.

The.typical.user.and.administrator.interactions.with.the.services.and.node.types.are.shown.in.the.Figure.4.below:

After.all.of.these.basics.are.in.place,.you.can.build.the.private.cloud.instance ..The.following.sections.detail.specific.aspects.of.the.solution.components.being.deployed,.along.with.their.related.design.decisions .

Solution ComponentsTo.coordinate.all.user-facing.functionality.and.abstraction.of.infrastructure.resources,.a.private.cloud.instance.requires.some.dedicated.administrative.and.control.resources,.in.addition.to.the.actual.storage.and.compute.resources ..As.with.most.IT.infra-structures,.this.covers.the.traditional.disciplines.of.networking,.systems.and.software,.so.the.relevant.aspects.will.be.included.in.each.section ..

Figure 4. UserInteractionwithSUSEOpenStackCloudNodesandServices

__________

5 www.openstack.org6 www.suse.com/products/suse-openstack-cloud

http://www.openstack.org

http://www.suse.com/products/suse-openstack-cloud

7www.suse.com

The.following.is.a.detailed.account.of.deploying.each.of.these.components,.along.with.their.respective.design.decisions.and.scalability.recommendations ..In.general,.this.document.is.meant.as.a.companion.guide.to.the.official.network,.system.and.soft-ware7.product.deployment.documentation,.citing.specific.set-tings.as.needed.to.accomplish.the.respective.design.decisions .

SUSE OpenStack Cloud Administration ServerThe.SUSE.OpenStack.Cloud.Administration.Server.provides.the.deployment.framework,.along.with.other.tools.and.needed.ser-vices.for.the.cloud.instance—such.as.DHCP,.DNS,.NTP,.PXE.and.TFTP ..These.components.are.set.up,.configured.and.accessed.from.a.web.interface.that.guides.all.the.remaining.installation.and.configuration.tasks.through.the.use.of.barclamps .

The.Administration.Server.also.commonly.hosts.the.necessary.software.repositories.for.SUSE.Linux.Enterprise.Server.and.SUSE.OpenStack.Cloud,.along.with.other.software.products,.as.they.are.needed.to.deploy.the.Control,.Compute.and.Storage.Nodes ..Most.of.the.remaining.Control,.Compute.and.Storage.Nodes.are.all.provisioned.by.simply.PXE.network.booting.from.the.SUSE.OpenStack.Cloud.Administration.Server .

Process:

TheBMCforthissystemshouldbeconnectedtoanexternalnetworkaccessibleoutsideofthecloudtofacilitatesetupandlatermanagementofthisnode.

UsingoneoftheavailableSGIC2112-4RP47nodes,performabare-metalinstallationoftheSUSELinuxEnterpriseServer12-SP1operatingsystemwithSUSEOpenStackCloud6usedduringtheinstallasanadd-on.

Configureoneinterfaceofthe1GbENICsbeingusedfortheAdminNetwork(forexample,eth1,eth2,eth3)withthestaticIPaddressoftheAdministrationServer.Theinstall-suse-cloudscriptwillexpandthistoabondinterfaceasdescribedbythe/etc/crowbar/network.jsonfile.Alsomakesurethehosthasafullqualifieddomainname,verifiedbyhostname-f.

Ifaminimalinstallationisperformed,itisveryusefultoinstallorenabletheRemoteAdministrationVNCinorderto

provideaconvenientgraphicaluserinterfaceforlatertaskswithinthecloudinstance.Itmightalsobenecessarytoinstalladditionalpackages(suchasJavaandawebbrowser)toaccessBMCvirtualconsolesfromthisinterface.

RegisterthesystemintheSUSECustomerCenter(SCC)duringoraftertheinstallationtoensurethatallthelatestsoftwareupdatesarepresent.

Completetheinstallationstepsasdescribedinthedeploymentguide,withthefollowingguidance:

. –. .Ensure.that.the.system.is.configured.to.have.a.valid.Network.Time.Protocol.(NTP).source,.as.this.will.become.a.reference.for.the.cloud.resource.nodes.as.well .

. –. .Install.the.Subscription.Management.Tool.(SMT).on.this.system .

. –. .Include.both.the.High.Availability.Extension.and.SUSE.Enterprise.Storages.repositories .

Note:Sometimeisrequiredtosetupallofthisproperlyandtomirrorallcontent.Beforeproceeding,itisimperativethatallthesoftwarerepositoriesaremirroredandavailableontheSUSEOpenStackCloudAdministrationServer.

Note:ItisimportanttoensurethattheAdministrationServerhasallavailablepackageupdatesinstalledbyregisteringwiththeSUSECustomerCenterorbyutilizingthelocalrepositoriesofupdatesalreadyavailableonthisnode.

Note:Proceedonlyuptothe“CrowbarSetup”section.

Tip:Beforeproceedingbeyondthiscriticaljuncture,thefollow-ingnetworkdesigndecisionsarenecessarytolockdowntheconfigurationfortherestofthisprivatecloudinstancedeploy-ment.Otheroptionsareavailablebutarebeyondthescopeofthisdocument.

Design Decisions:The.network.mode.across.the.resource.nodes.will.be.“team,”.yet.distinct.interfaces.will.be.used.for.some.of.the.remaining.cloud.networks,.with.the.following.settings:

Note:RefertotheNetworkNameSpaces(Table.1.on.page.4)andtoappendices,forboththeswitchsettingsandforthesystembootandNICsettings.

__________

7 www.suse.com/documentation/suse-openstack-cloud-6/

http://www.suse.com/documentation/suse-openstack-cloud-6/

http://www.suse.com

8


BMCs.for.all.nodes,.except.for.the.Administration.Server,.will.connect.through.their.own.switch.and.reside.as.an.untagged.VLAN.on.their.respective.1GbE.NICs.(for.example,.eth0) ..The.BMC.network.will.connect.to.the.BMC.network.on.the.admin.node.(for.example,.eth5) .

Admin.network.will.exist.as.untagged.VLANs.on.their.respec-tive.1GbE.NICs.(for.example,.eth1,.eth2).and.will.provide.the.PXE.booting.interface ..These.two.interfaces.will.be.bonded.together.on.all.the.SGI.C2112-4RP4.systems.in.a.balance-alb,.mode.6,.network.configuration .

Storage.and.public.network.on.the.appropriate.control.and.stor-age.nodes.will.exist.as.untagged.VLANs.on.the.1GbE.NICs.(for.example,.eth3.eth5) .

For.the.remainder.of.this.document,.the.following.example.IP.addresses.and.subnets.were.used.for.the.various.network.name.spaces.(substitute.as.appropriate.for.your.local.environment.and.for.the.remainder.of.this.document):

BMC/BMC_VLAN.:.192 .168 .126 .0/24.(untagged),Admin.:.192 .168 .124 .0/24.(untagged),Storage.:.192 .168 .125 .0/24.(untagged),

Nova.Floating.:.128 .162 .252 .64/26.(untagged),Public.:.128 .162 .252 .0 ./25.(untagged),OS_SDN.:.192 .168 .130 .0/24.(VLAN.400),Nova.Fixed.:.192 .168 .123 .0/24.(VLAN.500)

Atthispoint,carefullyreviewtheCrowbarSetupsectionofthedeploymentdocument:

. –. .Ensure.that.the.IP.address.of.the.Administration.Server.is.as.desired.and.resides.in.the.Admin.Network.subnet.range .

. –. .Manually.edit.the./etc/crowbar/network .json.file.to.reflect:

. ... •. .the.conduit.map.of.“team”.configuration.section..correctly.references:

. . -.bmc/bastion:."?1g5"

. . -.intf1:."?1g1",."?1g2"

. . -..Intf2:."?1g4",."?1g6"

. ... •. ..team_mode.:.6

. ... •. ..add.an.interface.map.for.the.SGI."C2112-4RP4"

. . -.{

. . -.. . . . . . "bus_order":.[

. . -.. . . . . . "0000:00/0000:00:02 .0/0000:02:00 .0",

. . -.. . . . . . "0000:00/0000:00:02 .0/0000:02:00 .1",

. . -.. . . . . . "0000:00/0000:00:02 .0/0000:02:00 .2",

. . -.. . . . . . "0000:00/0000:00:02 .0/0000:02:00 .3",

. . -.. . . . . . "0000:00/0000:00:1c .0/0000:07:00 .0",

. . -.. . . . . . "0000:00/0000:00:1c .0/0000:07:00 .1"

. . -.. . . . . .],

. . -.. . . . . . "pattern":."S2600WP"

. . -.}

. ... •. ..and.potentially.one.for.any.SGI.UV.nodes.to.ensure.the.desired.NIC.ordering

Tocompletethesetup,eitherutilizethe“screeninstall-suse-cloud”setupscriptwhiledirectlyloggedintotheAdmini-strationServerorstarttheCrowbarserviceandconnecttothewebserverathttp://<IPofAdministrationServer>tostarttheprocess.

Note:Whenthisprevioustaskcompletes,reviewthenotedlogfileforanyissuesandresolvethembeforeproceeding.Moreinformationcanbefoundinthetroubleshootingsectionofthedeploymentguide.

Atthispoint,logintothewebinterfaceoftheAdministrationServertopreparefordeploymentoftheremainingresourcenodesandservices:

. –. .Modify.the.IPMI.barclamp,.setting.the.“Enable.BMC”.to.true,.and.update.the.login.credentials.to.match.the.BMC.settings;.then.apply .

. –. .If.you.would.like,.we.strongly.recommend.to.directly.ac-cess.the.nodes.with.a.root.login,.follow.the.material.from.the.deployment.guide.noted.as.“How.to.provide.Kernel.Parameters.for.the.SLEShammer.Discover.image”.for.nodes.in.the.Discovered.state.and.“Direct.root.Login”.sec-tions.for.systems.in.the.Allocated.state ..Otherwise,.you.will.only.be.able.to.access.the.systems.via.ssh.from.the.Administration.Server .

9www.suse.com

SincetheSGIUVnodescomewithapre-installedcustomerimage,baseduponSUSELinuxEnterpriseServer12SP1,performthefollowingstepstogetthemintoadiscoveredstatebytheAdministrationServer:

. –. ..grep.'483|484|485'./etc/group.(and.for.any.found,.move.those.to.a.new.GID.via.groupmod.-g.<newGID>.groupname)

. –. ..egrep.'483|484|485'./etc/passwd.(and.for.any.found,.move.those.to.a.new.UID.via.usermod.-u.<newUID>.username)

. –. ..zypper.lr.(and.remove.any.repositories.SUSE.OpenStack.Cloud.will.add.during.the.crowbar_register.process)

. –. ..wget.http://92.168.124.10:8091/suse-12.1/x86_64/crowbar_register

. –. ..chmod.a+x. ./crowbar_register

. –. ..screen. ./crowbar_register

NowbooteachoftheremainingresourcenodesviaPXE.Eachnodeshouldbedisplayedontheadministrativewebinterfaceinadiscoveredstate.

Note:Itisimportanttoverifythateachrespectivenodehastheexpecteddiskdrivevolumes,networkinterfacesandotherphysicalattributesasameansofcorrelatingtotheeventualrole.

Then.each.resource.can.be.allocated.with.a.basic.operating.sys-tem,.either.in.an.iterative.process.by.editing.each.node.or.in.the.bulk.allocation.mode,.per.Table.2.at.right .

At.this.point,.you.are.ready.to.begin.assigning.the.services.and.roles.to.the.various.resource.nodes.as.described.in.the.following.sections .

SUSE OpenStack Cloud Control NodesA.SUSE.OpenStack.Cloud.Control.Node.is.managed.and.de-ployed.through.the.SUSE.OpenStack.Cloud.Administration.Server.web.interface ..To.ensure.the.high.availability.of.the.control.plane,.you.need.to.create.a.cluster.of.dedicated.Control.Nodes.with.at.least.one.pair.of.nodes.needed.for.a.cluster ..An.odd.number.of.cluster.member.nodes.is.preferred.to.establish.and.maintain.a.quorum ..Multiple.clusters.are.allowed,.should.services.need.to.be.isolated.for.performance.or.other.considerations,.

such.as.whether.the.service.is.stateful.or.can.be.used.only.in.an.active-passive.mode .

Design Decisions:

The.stateful.services.for.the.Database.and.Message.Queue.will.be.deployed.on.a.pair.of.nodes.and.then.later.assigned.to.those.roles ..Combine.two.resource.nodes.(data1,.data2).into.an.HA.cluster.configuration.("data").for.these.services.via.the.Pacemaker.barclamp .

Combine.three.resource.nodes.(control1,.control2,.control3).into.an.HA.cluster.configuration.("control").for.the.remaining.control.services.via.the.Pacemaker.barclamp ..This.cluster.can.then.be.as-signed.to.many.of.the.remaining.controller.OpenStack.services .

Resource Node

Target Platform

Atlas

Group

Intended Role

SGI C2112-4RP4 SUSE.Linux..Enterprise.12.SP1

data1 Data Controller


data2 Data Controller


control1 Control Controller





SGI UV 300 SUSE.Linux..Enterprise.12.SP1

compute1 Compute Compute

SGI UV 2000 SUSE.Linux..Enterprise.12.SP1







storage1 Storage Storage







Table 2. AssociationofResourceNodestoRolesandFunctions

http://92.168.124.10:8091/suse-12.1/x86_64/crowbar_register

http://www.suse.com

10


Process:

ForanHPC-centriccloudinstancelikethis,someparametersmightneedtobeadjustedtodealwiththeexpectedelevatedlevelsofusage.Onthetworespectivenodes("data1","data2"),performthefollowingconfigurationsetttingadjustments,priortocreatingthecluster:

. –. ...cat.<<./EOF.>>./etc/security/limits .conf.qpidd.soft.nofile. 16384.qpidd.hard. nofile. 16384.rabbitmq. soft. nofile. 16384.rabbitmq. hard. nofile. 16384.postgres. soft. nofile. 16384.postgres. hard. nofile. 16384.#.Increase.number.of.procs.*. soft. nproc. 10240.root. soft.nproc. unlimited./EOF

. –. ...cat.<</EOF.>.>/etc/systemd/system/rabbitmq-server .service. .include./usr/lib/systemd/system/rabbitmq-server .service.[Service].LimitNOFILE=16384./EOF

Thenrebootthetwonodestomakesurethesettingsareinplaceforthefollowingsteps.

ApplythePacemakerbarclamptotherespectiveclusternodes:

. –. ...Create.a.recognizable.proposal.name.(for.example,."data") .

. –. ...Set.DRBD:.true

. –. ...For.STONITH,.select.“Configured.with.one.resource.per.node”.with.the.respective.parameters:

. ... •. ..Fencing.agent:.external/ipmi

. ... •. .Parameters.for.each.agent.(respectively):.ipaddr=<BMCIPAddress>.userid=<BMCLogin>.passwd=<BMCPassword>.interface=lanplus

. ... •. .Include.the.pair.of.respective.cluster.nodes.into.."pacemaker-cluster-member".and."hawk-server" .

. –. ...Then.apply.the.proposal .

Withthe"data"clusterinplace,thefollowingtwoofthefoundationalservicesneededbytheprivatecloudinstanceareshownbelowandcanbelayeredontothiscluster,withthesettingsnotedinthedescriptionfieldofthefollowingtable:

.

.

.

.

.

.

ApplythePacemakerbarclamptotheremainingcontrolandcomputeclusternodes:

. –. ..Create.a.recognizable.proposal.name.(for.example,."control") .

. –. ..For.STONITH,.select.“Configured.with.one.resource.per.node”.with.the.respective.parameters:

. ... •. ..Fencing.agent:.external/ipmi

. ... •. ..Parameters.for.each.agent.(respectively):.ipaddr=<BMCIPAddress>.userid=<BMCLogin>.passwd=<BMCPassword>.interface=lanplus

. ... •. ..Include.the.three.respective.cluster.nodes.("control1",."control2",."control3").into."pacemaker-cluster-.member”".and."hawk-server".roles .

. ... •. ..Include.the.four.respective.compute.nodes.(“compute1,.compute2,.compute3,.compute4).into.the.pacemaker-remote.role .

. –. ..Then.apply.the.proposal .

Note:AsyoumightnoticewhenvisitingtheHighAvailabilityWebConsole(HAWK)interfaces(viathelinkonanyoftheclustered"data"or"control"nodepages),theseservicesmightexistondifferentnodes,assumingmorethanonenodeisinthecluster.

Tip:ProceedtosetuptheSUSEOpenStackCloudStorageNodesasnotedinthatsection;thenreturnheretocompletethesetupofthecontrolplane.

Foundational Services

OpenStack Project Name

Description

Database N/A Backend.database.for.OpenStack.Services.that.tracks.current..information.about.users.and..instances .

Storage.Mode.:.DRBD Size.to.Allocate.for.DRBD..Device.

(in.GB).:.500

Message Queue N/A Enables.OpenStack.services.to..communicate.with.the.other.nodes..via.Advanced.Message.Queue..Protocol.(AMQP) .

Storage.Mode.:.DRBD Size.to.Allocate.for.DRBD..Device.

(in.GB).:.500

Table 3. FoundationalServicesforOpenStack

11www.suse.com

Process (post Storage Node):

Assigntherolesfromthefollowingservicestothe"control" cluster,subjecttotheconfigurationsettingsnotedinthedescriptionfieldofthefollowingtable:

Tip:ProceedtosetuptheSUSEOpenStackCloudComputeNodesasnotedinthatsection;thenreturnheretocompletethesetupofthecontrolplane.

Process (post Compute Node):

Assignthefollowingrolestothe"control"clusterforeachofthefollowingservices,subjecttotheconfigurationsettingsinthedescriptionfieldofthefollowingtable:

Design Decision:

The.following.OpenStack.services.available.in.SUSE.OpenStack.Cloud.are.not.deployed.in.this.configuration:.FileShare.(Manilla),.nor.any.of.the.Tech.Preview.services,.for.example,.Database-as-a-Service.(Trove),.Elastic.Map.Reduce.(Sahara),.Bare.Metal.Install.(Ironic),.nova-docker .

Core OpenStack Services


Description

Identity Keystone Provides.an.authentication.and..authorization.service.for.other..OpenStack.services ..Provides.a..catalog.of.endpoints.for.all..OpenStack.services .

Image Glance Stores.and.retrieves.virtual.machine.disk.images ..OpenStack.Compute.makes.use.of.this.during.instance.provisioning .

Default.Storage.Store.:.Rados

Block Storage Cinder Provides.persistent.block.storage..to.running.instances ..Its.pluggable.driver.architecture.facilitates.the.creation.and.management.of.block.storage.devices .

Delete.the.Backend:.default Add.new.Cinder.Backend.

–. Type.of.Volume.:.RADOS Assign."cinder-volume".role.to.

.storage1,.storage2,.storage3

Networking Neutron Enables.network-connectivity-as-a-.service.for.other.OpenStack.services,..such.as.OpenStack.Compute ..Provides.an.API.for.users.to.define.networks.and.the.attachments.into.them ..Has.a.pluggable.architecture.that.supports.many.popular.net.working.vendors.and.technologies .

OpenStack Services


Description

Compute Nova Manages.the.lifecycle.of.compute.instances.in.an.OpenStack.environ-ment ..Responsibilities.include..spawning,.scheduling.and.decommis-sioning.virtual.machines.on.demand .

nova-compute-kvm.:.control..(4.remote.nodes)

Dashboard Horizon Provides.a.web-based,.self-service.portal.to.interact.with..underlying.OpenStack.services,.such.as.launching.an.instance,.assigning.IP.addresses.and.configuring.access.controls .

Telemetry Ceilometer Monitors.and.meters.the.OpenStack.cloud.for.billing,.benchmarking,..scalability.and.statistical.purposes ..Note.that.the.MongoDB.backend.is.still.in.a.technical.preview.status .

ceilometer-agent.:.compute1,..compute2,.compute3,.compute4

Orchestration Heat Orchestrates.multiple.composite.cloud.applications.by.using.either.the.native.HOT.template.format.or.the.AWS.Cloud.Formation.template.format,.through.both.an.OpenStack-native.REST.API.and.a.Cloud..Formation-compatible.Query.API .

Integration Test Suite (Optional)

Tempest Set.of.integration.tests.to.be.run.against.a.live.OpenStack.instance,..include.batteries.of.tests.for..OpenStack.API.validation,.scenarios.and.other.specific.tests.useful.in..validating.an.OpenStack.deployment

tempest.:.control1

Table 4. CoreOpenStackServices

Table 5. OpenStackServices

http://www.suse.com

12


SUSE OpenStack Cloud Storage NodesA.SUSE.OpenStack.Cloud.Storage.Node.is.managed.and.de-ployed.through.the.SUSE.OpenStack.Cloud.Administration.Server.web.interface ..These.nodes.act.as.a.provider.of.persis-tent.cloud-based.storage.elements.and.offer.a.management.in-terface ..This.storage.can.be.presented.in.both.object.or.block.format,.furnish.volumes.for.a.workload.instance.or.even.act.as.the.underlying.storage.for.some.of.the.core.OpenStack.services ..Multiple.Storage.Nodes.should.be.deployed.to.provide.data.re-dundancy.and.resiliency.in.case.of.component.or.system.failures,.as.detailed.in.this.document ..Storage.Nodes,.with.OSD.roles,.can.be.added.over.time.to.increase.the.storage.capacity .

Design Decisions:

Three.Resource.Nodes.(storage1,.storage2,.storage3).and.the.remaining.node.(storage4,.for.the.Ceph.management.interface.known.as.Calamari).will.be.combined.into.a.Ceph.configuration.to.provide.backend.storage.for.the.private.cloud.instance .

Note:TheMONprocessesalsorunonthesesamestoragenodes.NootherOpenStackservicesarepermittedonthesenodes.ItissufficienttouseonlythesethreeinitialMONnodesandnotaddadditionalonesevenforverylargestorageclusters.

Process:

Assignthe"ceph-calamari"roletothestorage4node. Assignthe"ceph-osd"and"ceph-mon"rolestothe

storage1,storage2andstorage3resourcenodes. Assignthe"ceph-radosgw"roletostorage1node. Applythebarclampproposal.

Note:Bydefault,allunuseddiskdriveswillbeallocatedtotheOSDfunction.

Tip:WiththeStorageNodessetup,returntothepoststoragenodeportionoftheControlNodesetup.

SUSE OpenStack Cloud Compute NodesA.SUSE.OpenStack.Cloud.Compute.Node.is.managed.and.deployed.through.the.SUSE.OpenStack.Cloud.Administration.Server.web.interface ..More.Compute.Nodes.can.be.added.over.time.as.needed.to.address.increased.workload.hosting,.and.avail-ability.zones.can.be.utilized.to.achieve.logical.groupings.of.sys-tems.and.then.to.allow.selective.spreading.of.workloads.across.these.zones.for.availability.concerns .

Design Decisions:

Four.resource.nodes.(compute1,.compute2,.compute3,.com-pute4).were.already.incorporated.into.the.existing."control"..plane.cluster.configuration.to.provide.workload.failover.capabilities .

All.Compute.Nodes.will.provide.the.KVM.hypervisor .

Process:

OntheSGIUVnodes—duetoapotentialconflictwiththeversionoflibvirtddependenciesonthepre-installedimagecomparedtothoseavailableinthesoftwarerepositoriesontheAdministrationServer—performthefollowingpreparatorysteps:

. –. ..zypper.install.libvirt

. –. rpm.-e.libvirt

Tip:WiththeComputeNodesprepared,returntothepostComputeNodeportionoftheControlNodesetup.

Operational AspectsAt.this.point,.you.should.be.able.to.utilize.your.private.cloud.instance,.according.to.the.SUSE.OpenStack.Cloud.Admin,.User.and.Supplement.Guides,.with.the.ability.to.upload.images.for.deployment,.launch.workloads.and.manipulate.data.volumes ..For.reference,.an.export.of.the.deployed.instance.is.included.in.the.appendices,.showing.the.nodes.and.the.roles.deployed ..The.over-all,.logical.view.of.the.public.cloud.instance.constructed.per.the.steps.of.this.document.is.shown.on.the.following.page:

13www.suse.com

You.can.also.optionally.perform.a.basic.functionality.and.API.test.of.your.overall.installation,.utilizing.the.OpenStack.Integration.Test.Suite.(Tempest).to.exercise.the.“smoke”.tests.that.are.part.of.the.OpenStack.gate.process.as.described.in.the.deployment.guide .

Both.SGI.and.SUSE.can.provide.guidance,.training,.support.and.services.for.more.sophisticated.deployments.than.the.one.de-scribed.in.this.white.paper;.however,.they.are.beyond.the.scope.of.this.document ..As.you.progress.through.the.deployment.outlined.in.the.document,.if.any.errors.arise,.address.those.first.before.proceeding.onto.the.next.step.or.service ..If.you.cannot.resolve.the.issue.quickly,.check.to.see.if.the.troubleshooting.section.of.the.deployment.guide.can.help.or.generate.a.report.on.the.sus-pect.nodes.using.the.supportconfig.tool.or.via.the.“Utilities.->.Exported”.action.on.the.Crowbar.web.interface.before.contacting.your.support.organization .

Appendices

Bill of Materials: System

SGI RACKABLE C2112-4RP4

SGI UV

Bill of Materials: SoftwareQuantities.shown.cover.the.documented.configuration.(one.Administration.Server,.one.Calamari.Node,.five.total.HA.Control.Nodes,.four.HA.Compute.Nodes,.three.Storage.Nodes) ..See.Notes.below.for.guidelines.on.what.adjustments.are.needed.to.scale.beyond.this.initial.configuration .

Note:Possiblequantityadjustments:

(a)Increasequantity,ifneeded,foreachadditionalControlNode,beyondthetotaloffivecited.

(b)Increasequantity,ifneeded,foreachadditionalComputeNode,beyondthetotaloffoursocketpairscitedandtomatchthetotalnumberofsocketpairscontainedintheoverallcomputenodehostsbeingmanaged

(c)Increasequantity,ifneededtomatchthetotalnumberofsocketpairsforeachSUSE-basedComputeNoderunningKVMorXen,beyondthetotaloftheSolutionAdminhostandfourcitedComputeNodes.

(d)Incrementallyincreasequantity,foreachStorageNodebeyondthefirstfourallowedinSUSEEnterpriseStorageBase.

Figure 5. LogicalDiagramofthePrivateCloudSolution

Quantity SKU Description

12 C2112-4RP4 2.cpus,.40.cores,.128GB.main.memory,.(3).2TB.SATA.disks


1 874-006386 SUSE.OpenStack.Cloud.Control.Node.plus.Admin.Server,.x.86-64,.1.Instance,.Priority..Subscription,.3.Year

4(a) 874-006388 SUSE.OpenStack.Cloud.Control.Node,.x86-64,.1.Instance,.Priority.Subscription,.3.Year

4(b) 874-006390 SUSE.OpenStack.Cloud.Compute.Node,..x86-64,.1-2.Sockets,.Priority.Subscription,..3.Year

4(c) 874-006884 SUSE.Linux.Enterprise.Server,.x86.&.x86-64,.1-2.Sockets.with.Unlimited.Virtual.Machines,.Priority.Subscription,.3.Year

4(c) 874-006924 SUSE.Linux.High.Availability.Extension,.x86.&.x86-64,.1-2.Sockets.with.Inherited..Virtualization,.Inherited.Subscription,.3.Year

1 874-007040 SUSE.Enterprise.Storage.Base.Configuration,.x86-64,.4.OSD.Nodes.with.1-2.Sockets,..Priority.Subscription,.3.Year

(d) 874-007042 SUSE.Enterprise.Storage.Expansion.Node,.x86-64,.1.OSD.Node.with.1-2.Sockets,..Priority.Subscription,.3.Year


1 UV.300 Compute1.–.480.cores,.1TB.main.memory,..21TB.nVME.local.virtual.storage

1 UV.2000 Compute2.–.64.cores,.128GB.main.memory,.1 .8TB.SATA.local.virtual.storage

http://www.suse.com

14


Configuration: Software

SUSE OPENSTACK CLOUD CROWBAR BATCH EXPORT

(STRIP PW AND CAPTURE FROM LATEST)

---proposals:-.barclamp:.crowbar..attributes:....instances:......ganglia:.[]......nagios:.[]......provisioner:......-."/var/lib/crowbar/config/provisioner .json"......network:......-."/var/lib/crowbar/config/network .json"......ntp:......-."/var/lib/crowbar/config/ntp .json"......dns:......-."/var/lib/crowbar/config/dns .json"....realm:.SUSE.OpenStack.Cloud.Admin.Server....users:......machine-install:........password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>..deployment:....elements:......crowbar:......-.admin .cloud .sgi .com-.barclamp:.deployer..attributes:..deployment:....elements:......deployer-client:......-.admin .cloud .sgi .com......-."@@data1@@"......-."@@compute1@@"......-."@@control2@@"......-."@@compute4@@"......-."@@data2@@"......-."@@storage2@@"......-."@@control3@@"......-."@@control1@@"......-."@@storage1@@"......-."@@storage3@@"......-."@@storage4@@"......-."@@compute2@@"

......-."@@compute3@@"-.barclamp:.provisioner..attributes:....root_password_hash:."$1$YZnJXavJ$H50/asHVPQFAAIpb1vknX0"....timezone:.America/Chicago..deployment:....elements:......provisioner-server:......-.admin .cloud .sgi .com......provisioner-base:......-.admin .cloud .sgi .com......-."@@data1@@"......-."@@compute1@@"......-."@@control2@@"......-."@@compute4@@"......-."@@data2@@"......-."@@storage2@@"......-."@@control3@@"......-."@@control1@@"......-."@@storage1@@"......-."@@storage3@@"......-."@@storage4@@"......-."@@compute2@@"......-."@@compute3@@"......provisioner-bootdisk-finder:......-.admin .cloud .sgi .com......-."@@control2@@"......-."@@storage1@@"......-."@@control1@@"......-."@@compute4@@"......-."@@storage2@@"......-."@@data1@@"......-."@@storage4@@"......-."@@compute1@@"......-."@@data2@@"......-."@@storage3@@"......-."@@control3@@"......-."@@compute2@@"......-."@@compute3@@"-.barclamp:.ipmi..attributes:....bmc_enable:.true..deployment:

15www.suse.com

....elements:

......ipmi-discover:

......-.admin .cloud .sgi .com

......-."@@data1@@"

......-."@@compute1@@"

......-."@@control2@@"

......-."@@compute4@@"

......-."@@data2@@"

......-."@@storage2@@"

......-."@@control3@@"

......-."@@control1@@"

......-."@@storage1@@"

......-."@@storage3@@"

......-."@@storage4@@"

......-."@@compute2@@"

......-."@@compute3@@"

......ipmi-configure:


......-."@@data1@@"

......-."@@compute1@@"

......-."@@control2@@"

......-."@@compute4@@"

......-."@@data2@@"

......-."@@storage2@@"

......-."@@control3@@"

......-."@@control1@@"

......-."@@storage1@@"

......-."@@storage3@@"

......-."@@storage4@@”

......-."@@compute2@@"

......-."@@compute3@@"

......bmc-nat-router:


......bmc-nat-client:

......-."@@data1@@"

......-."@@compute1@@"

......-."@@control2@@"

......-."@@compute4@@"

......-."@@data2@@"

......-."@@storage2@@"

......-."@@control3@@"

......-."@@control1@@"

......-."@@storage1@@"

......-."@@storage3@@"

......-."@@storage4@@"

......-."@@compute2@@"

......-."@@compute3@@"-.barclamp:.network..attributes:....mode:.team....teaming:......mode:.6....interface_map:....-.bus_order:......-.0000:00/0000:00:02 .0/0000:02:00 .0......-.0000:00/0000:00:02 .0/0000:02:00 .1......-.0000:00/0000:00:02 .0/0000:02:00 .2......-.0000:00/0000:00:02 .0/0000:02:00 .3......-.0000:00/0000:00:1c .0/0000:07:00 .0......-.0000:00/0000:00:1c .0/0000:07:00 .1......pattern:.S2600WP....-.bus_order:......-.0002:00/0002:00:03 .0/0002:02:00 .2/0002:04:06 .1......-.0002:00/0002:00:03 .0/0002:02:00 .0/0002:03:04 .0......-.0002:00/0002:00:03 .0/0002:02:00 .0/0002:03:04 .1......-.0002:00/0002:00:03 .0/0002:02:00 .2/0002:04:06 .0......-.0000:00/0000:00:03 .0/0000:01:00 .0......-.0000:00/0000:00:03 .0/0000:01:00 .1......pattern:.UV.2000....conduit_map:....-.conduit_list:........bmc:..........if_list:..........-."?1g5"........intf1:..........if_list:..........-."?1g1"..........-."?1g2"........intf2:..........if_list:..........-."?1g6"........bastion:..........if_list:..........-."?1g5"......pattern:.team/ .*/crowbar$....-.conduit_list:........bmc:..........if_list:

http://www.suse.com

16


..........-."?1g5"

........intf1:

..........if_list:

..........-."?1g1"

..........-."?1g2"

........intf2:

..........if_list:

..........-."?1g4"

.........-."?1g6"

........bastion:

..........if_list:

..........-."?1g5"

......pattern:.team/ .*/ .*

....-.conduit_list:

........intf0:

..........if_list:

..........-."?1g6"

........intf1:

..........if_list:

..........-."?1g1"

..........-."?1g2"

..........-."?1g3"

..........team_mode:.6

........intf2:

..........if_list:

..........-."?1g5"

........bastion:

..........if_list:

..........-."?1g5"

......pattern:.dual/ .*/crowbar$

....-.conduit_list:

........intf0:

..........if_list:

..........-."?1g5"

........intf1:

..........if_list:

..........-."?1g1"

..........-."?1g2"

..........-."?1g3"

..........team_mode:.6

........intf2:

..........if_list:

..........-."?1g6"

........bastion:

..........if_list:

..........-."?1g5"

......pattern:.dual/ .*/ .*

....networks:

......bastion:

........router_pref:.9

........netmask:.255 .255 .255 .0

........vlan:.0

........router:.128 .162 .252 .1

........use_vlan:.false

........subnet:.128 .162 .252 .0

........broadcast:.128 .162 .252 .255

........ranges:

..........admin:

............start:.128 .162 .252 .4

............end:.128 .162 .252 .4

........conduit:.bastion

........add_bridge:.false

......storage:

........conduit:.intf2


......public:



........subnet:.128 .162 .252 .0

........netmask:.255 .255 .255 .128

........broadcast:.128 .162 .252 .127

........router:.128 .162 .252 .1

........ranges:

..........host:

............start:.128 .162 .252 .65

............end:.128 .162 .252 .69

......nova_floating:



........subnet:.128 .162 .252 .64

........netmask:.255 .255 .255 .192

........broadcast:.128 .162 .252 .127

........ranges:

..........host:

............start:.128 .162 .252 .70

............end:.128 .162 .252 .126

......bmc:

........subnet:.192 .168 .126 .0

17www.suse.com

........broadcast:.192 .168 .126 .255

........ranges:

..........host:

............start:.192 .168 .126 .11

............end:.192 .168 .126 .190

......bmc_vlan:


........subnet:.192 .168 .126 .0

........broadcast:.192 .168 .126 .255

........ranges:

..........host:

............start:.192 .168 .126 .1

............end:.192 .168 .126 .2

......admin:


........router:.192 .168 .124 .10

..deployment:

....elements:

......switch_config:


......network:


......-."@@data1@@"

......-."@@compute1@@"

......-."@@control2@@"

......-."@@compute4@@"

......-."@@data2@@"

......-."@@storage2@@"

......-."@@control3@@"

......-."@@control1@@"

......-."@@storage1@@"

......-."@@storage3@@"

......-."@@storage4@@"

......-."@@compute2@@"

......-."@@compute3@@"-.barclamp:.dns..attributes:....domain:.cloud .sgi .com....forwarders:....-.128 .162 .236 .210....-.128 .162 .237 .211....-.137 .38 .225 .5..deployment:....elements:

......dns-server:


......dns-client:


......-."@@data1@@"

......-."@@compute1@@"

......-."@@control2@@"

......-."@@compute4@@"

......-."@@data2@@"

......-."@@storage2@@"

......-."@@control3@@"

......-."@@control1@@"

......-."@@storage1@@"

......-."@@storage3@@"

......-."@@storage4@@"

......-."@@compute2@@"

......-."@@compute3@@"-.barclamp:.logging..attributes:..deployment:....elements:......logging-server:......-.admin .cloud .sgi .com......logging-client:......-."@@data1@@"......-."@@compute1@@"......-."@@control2@@"......-."@@compute4@@"......-."@@data2@@"......-."@@storage2@@"......-."@@control3@@"......-."@@control1@@"......-."@@storage1@@"......-."@@storage3@@"......-."@@storage4@@"......-."@@compute2@@"......-."@@compute3@@"-.barclamp:.ntp..attributes:....external_servers:....-.198 .149 .32 .43..deployment:....elements:......ntp-server:

http://www.suse.com

18



......ntp-client:

......-."@@data1@@"

......-."@@compute1@@"

......-."@@control2@@"

......-."@@compute4@@"

......-."@@data2@@"

......-."@@storage2@@"

......-."@@control3@@"

......-."@@control1@@"

......-."@@storage1@@"

......-."@@storage3@@"

......-."@@storage4@@"

......-."@@compute2@@"

......-."@@compute3@@"-.barclamp:.pacemaker..name:.control..attributes:....corosync:......mcast_addr:.239 .255 .0 .2....stonith:......mode:.manual......sbd:........nodes:..........d00-e0-ed-50-4e-c2 .cloud .sgi .com:............devices:............-.''..........d00-e0-ed-2e-68-78 .cloud .sgi .com:............devices:............-.''..........d00-e0-ed-43-96-98 .cloud .sgi .com:............devices:............-.''..........d00-e0-ed-2e-68-70 .cloud .sgi .com:............devices:............-.''..........d00-e0-ed-0a-41-9f .cloud .sgi .com:............devices:............-.''..........d00-e0-ed-04-c5-4b .cloud .sgi .com:............devices:............-.''..........d00-e0-ed-50-4e-b2 .cloud .sgi .com:............devices:

............-.''

......per_node:

........agent:.external/ipmi

........nodes:

..........d00-e0-ed-2e-68-70 .cloud .sgi .com:

............params:.userid=root.passwd=cr0wBar!.interface=lanplus.ipaddr=192 .168 .126 .6..........d00-e0-ed-0a-41-9f .cloud .sgi .com:............params:.userid=ADMIN.passwd=ADMIN.interface=lanplus.ipaddr=128 .162 .244 .8..........d00-e0-ed-04-c5-4b .cloud .sgi .com:............params:.userid=ADMIN.passwd=ADMIN.interface=lanplus.ipaddr=128 .162 .244 .141..........d00-e0-ed-50-4e-b2 .cloud .sgi .com:............params:.userid=root.passwd=cr0wBar!.interface=lanplus.ipaddr=192 .168 .126 .4..........d00-e0-ed-50-4e-c2 .cloud .sgi .com:............params:.userid=root.passwd=cr0wBar!.interface=lanplus.ipaddr=192 .168 .124 .10..........d00-e0-ed-2e-68-78 .cloud .sgi .com:............params:.userid=root.passwd=cr0wBar!.interface=lanplus.ipaddr=192 .168 .124 .5..........d00-e0-ed-43-96-98 .cloud .sgi .com:............params:.userid=root.passwd=cr0wBar!.interface=lanplus.ipaddr=192 .168 .126 .9....drbd:......shared_secret:.giUf8bIbnFTH..deployment:....elements:......pacemaker-remote:......-."@@compute4@@"......-."@@compute3@@"......-."@@compute2@@"......-."@@compute1@@"......hawk-server:......-."@@control3@@"......-."@@control2@@"......-."@@control1@@"......pacemaker-cluster-member:......-."@@control3@@"......-."@@control2@@"......-."@@control1@@"-.barclamp:.pacemaker..name:.data

19www.suse.com

..attributes:

....stonith:

......sbd:

........nodes:

..........d00-e0-ed-48-bc-34 .cloud .sgi .com:

............devices:

............-.''

..........d00-e0-ed-50-4e-a6 .cloud .sgi .com:

............devices:

............-.''

......per_node:

........agent:.external/ipmi

........nodes:

..........d00-e0-ed-48-bc-34 .cloud .sgi .com:

............params:.userid=root.passwd=cr0wBar!.interface=lanplus.ipaddr=192 .168 .126 .7..........d00-e0-ed-50-4e-a6 .cloud .sgi .com:............params:.userid=root.passwd=cr0wBar!.interface=lanplus.ipaddr=192 .168 .126 .2....drbd:......enabled:.true......shared_secret:.evLTK8YuZqy5..deployment:....elements:......hawk-server:......-."@@data2@@"......-."@@data1@@"......pacemaker-cluster-member:......-."@@data2@@"......-."@@data1@@"-.barclamp:.database..attributes:....ha:......storage:........mode:.drbd........drbd:..........size:.500..deployment:....elements:......database-server:......-.cluster:data-.barclamp:.rabbitmq..attributes:....password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>

....ha:

......storage:

........mode:.drbd

........drbd:

..........size:.500

....trove:

......password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>

..deployment:

....elements:

......rabbitmq-server:

......-.cluster:data-.barclamp:.keystone..attributes:....database_instance:.default....rabbitmq_instance:.default....db:......password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>....service:......token:.1ti6yfosUYip..deployment:....elements:......keystone-server:......-.cluster:control-.barclamp:.ceph..attributes:....config:......fsid:.bfbfa42c-46e8-4221-8424-a8e9b92cea27....keystone_instance:.default..deployment:....elements:......ceph-calamari:......-."@@storage4@@"......ceph-mon:......-."@@storage3@@"......-."@@storage2@@"......-."@@storage1@@"......ceph-osd:......-."@@storage3@@"......-."@@storage2@@"......-."@@storage1@@"......ceph-radosgw:......-."@@storage1@@"-.barclamp:.glance..attributes:

http://www.suse.com

20


....service_password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>....db:......password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>....default_store:.rbd....keystone_instance:.default....database_instance:.default....rabbitmq_instance:.default..deployment:....elements:......glance-server:......-.cluster:control-.barclamp:.cinder..attributes:....rabbitmq_instance:.default....keystone_instance:.default....glance_instance:.default....database_instance:.default....service_password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>....volumes:....-.backend_driver:.rbd......backend_name:.default......rbd:........use_crowbar:.true........config_file:."/etc/ceph/ceph .conf"........admin_keyring:."/etc/ceph/ceph .client .admin .keyring"........pool:.volumes........user:.cinder........secret_uuid:.24a29b6c-0fa9-4354-b37f-7730c886d533....db:......password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>..deployment:....elements:......cinder-controller:......-.cluster:control......cinder-volume:......-."@@storage3@@"......-."@@storage2@@"......-."@@storage1@@"-.barclamp:.neutron..attributes:....service_password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>

....rabbitmq_instance:.default

....keystone_instance:.default

....database_instance:.default

....db:


..deployment:

....elements:

......neutron-server:

......-.cluster:control

......neutron-network:

......-.cluster:control-.barclamp:.nova..attributes:....service_password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>....neutron_metadata_proxy_shared_secret:.x6zl6HPVhSFY....database_instance:.default....rabbitmq_instance:.default....keystone_instance:.default....glance_instance:.default....cinder_instance:.default....neutron_instance:.default....itxt_instance:.''....db:......password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>..deployment:....elements:......nova-controller:......-.cluster:control......nova-compute-hyperv:.[]......nova-compute-kvm:......-.remotes:control......nova-compute-qemu:.[]......nova-compute-xen:.[]-.barclamp:.horizon..attributes:....nova_instance:.default....keystone_instance:.default....database_instance:.default....db:......password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>..deployment:....elements:......horizon-server:

21www.suse.com

......-.cluster:control-.barclamp:.heat..attributes:....rabbitmq_instance:.default....database_instance:.default....stack_domain_admin_password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>....keystone_instance:.default....service_password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>....auth_encryption_key:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>....db:......password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>..deployment:....elements:......heat-server:......-.cluster:control-.barclamp:.ceilometer..attributes:....metering_secret:.nrcsc1UTfkjc....rabbitmq_instance:.default....database_instance:.default....keystone_instance:.default....service_password:.<<CENSORED.BY.SUPPORTCONFIG.PLUGIN>>....db:


..deployment:

....elements:

......ceilometer-agent:

......-."@@compute2@@"

......-."@@compute3@@"

......-."@@compute1@@"

......-."@compute4@@"

......ceilometer-agent-hyperv:.[]

......ceilometer-central:


......ceilometer-server:


......ceilometer-swift-proxy-middleware:.[]-.barclamp:.tempest..attributes:....tempest_adm_password:.OwW1gGy07BTZ....tempest_adm_username:.tempest-adm-AxXNayxQUKmx....tempest_user_password:.pg6oqCBZx8Ep....tempest_user_username:.tempest-user-vUwDKR1JvjKH....tempest_user_tenant:.tempest-tenant-Q6SUoMGcVi21....nova_instance:.default..deployment:....elements:......tempest:......-."@@control1@@"

http://www.suse.com

www.suse.com

Contact your local SUSE Solutions Provider, or call SUSE at:

1.800.796.3700.U .S ./Canada

1.801.861.4500.Worldwide

SUSE

Maxfeldstrasse.5

90409.Nuremberg

Germany

262-002534-002 | 01/17 | © 2017 SUSE LLC. All rights reserved. SUSE and the SUSE logo are registered trademarks, and SUSE Enterprise Storage

is a trademark of SUSE LLC in the United States and other countries. All third-party trademarks are the property of their respective owners.

http://www.suse.com

SGI and SUSE OpenStack Cloud Reference Architecture...Table of Contents page Introduction ...

Documents