Reliable server pooling [Elektronische Ressource] : evaluation, optimization and extension of a novel IETF architecture / by Thomas Dreibholz

Thomas Dreibholz

Description

ReliableServerPoolingEvaluation,OptimizationandExtensionofaNovelIETFArchitectureDISSERTATIONtoobtaintheacademicgradedoctorrerumnaturalium(dr. rer. nat.)inComputerScienceSubmittedtotheFacultyofEconomicsInstituteforComputerScienceandBusinessInformationSystemsUniversityofDuisburg EssenbyDipl. Inform. ThomasDreibholzbornon29.09.1976inBergneustadt,GermanyPresidentoftheUniversityofDuisburg Essen:Prof.Dr.LotharZechlinDeanoftheFacultyofEconomics:Prof.Dr.HendrikSchroder¨Reviewers:1. Prof. Dr. Ing. ErwinP.Rathgeb2. Prof. Dr. KlausEchtleSubmittedon: November28,2006DateofDisputation: March07,2007iiSelbstandigk¨ eitserklarung¨Hiermiterklare¨ ich,dievorliegendeArbeitselbstandig¨ ohnefremdeHilfeverfaßtundnurdieangege beneLiteraturundHilfsmittelverwendetzuhaben.ThomasDreibholzNovember28,2006iiiivAbstractThe Reliable Server Pooling (RSerPool) architecture currently under standardization by the IETFRSerPool Working Group is an overlay network framework to provide server replication and ses sion failover capabilities to applications using it. These functionalities as such are not new, but theircombinationintoonegeneric,application independentframeworkis.InitialgoalofthisthesisistogaininsightintothecomplexRSerPoolmechanismsbyperformingexperimental and simulative proof of concept tests. The further goals are to systematically validatetheRSerPoolarchitectureanditsprotocols,provideimprovementsandoptimizationswherenecessaryand propose extensions if useful.

Sujets

• Informatik

Informations

• Publié par: universitat_duisburg-essen
• Publié le: 01 janvier 2007
• Nombre de lectures: 583
• Langue: English
• Poids de l'ouvrage: 8 Mo

Extrait

PoolingerServReliable

Evaluation,OptimizationandExtensionofaNovelIETFArchitecture

DISSERTATION

gradeacademictheobtaintodoctor(dr.rerumrer.nat.)naturalium
ScienceComputerin

FacultySubmittedoftoEconomicsthe
InstituteforComputerUniversityScienceofandDuisburBusinessg-EssenInformationSystems

byDipl.-Inform.DreibholzThomasbornon29.09.1976inBergneustadt,Germany

PresidentoftheUniversityofDuisburg-Essen:
ZechlinLothar.DrProf.DeanoftheFacultyofEconomics:
Prof.Dr.HendrikSchr¨oder
wers:vieRe

1.2.Prof.Prof.DrDr..-Ing.KlausErwinEchtleP.Rathgeb

on:SubmittedDisputation:ofDate

NoMarchvember07,28,20072006

ii

Selbst¨andigkeitserkl¨arung

Hiermiterkl¨areich,dievorliegendeArbeitselbst¨andig

HilfsmittelundLiteraturbene

DreibholzThomas

embervNo

28,

2006

verwendet

zu

haben.

iii

ohne

fremde

Hilfe

erfvaßt

und

nur

die

ge-ange

vi

Abstract

TheReliableServerPooling(RSerPool)architecturecurrentlyunderstandardizationbytheIETF
RSerPoolWorkingGroupisanoverlaynetworkframeworktoprovideserverreplicationandses-
sionfailovercapabilitiestoapplicationsusingit.Thesefunctionalitiesassucharenotnew,buttheir
combinationintoonegeneric,application-independentframeworkis.
InitialgoalofthisthesisistogaininsightintothecomplexRSerPoolmechanismsbyperforming
experimentalandsimulativeproof-of-concepttests.Thefurthergoalsaretosystematicallyvalidate
theRSerPoolarchitectureanditsprotocols,provideimprovementsandoptimizationswherenecessary
andproposeextensionsifuseful.Basedontheseevaluations,recommendationstoimplementersand
usersofRSerPoolshouldbeprovided,givingguidelinesforthetuningofsystemparametersandthe
appropriateconfigurationofapplicationscenarios.Inparticular,itisalsoagoaltotransferinsights,
optimizationsandextensionsoftheRSerPoolprotocolsfromsimulationtorealityandalsotobring
theachievementsfromresearchintoapplicationbysupportingandcontributingrelevantresultstothe
IETFsongoingRSerPoolstandardizationprocess.
Toachievethedescribedgoals,aprototypeimplementationaswellasasimulationmodelare
designedandrealizedatfirst.Usingagenericapplicationmodelandappropriateperformancemet-
rics,theperformanceofRSerPoolsystemsinfailure-freeandserverfailurescenariosissystematically
evaluatedinordertoidentifycriticalparameterrangesandproblematicprotocolbehaviour.Improve-
mentsdevelopedasresultoftheseperformanceanalysesareevaluatedandfinallycontributedintothe
RSerPool.ofprocessstandardization

ords:eywKReliableServerPooling,Evaluation,Optimization,Extension

v

vi

wledgementsAckno

ThisthesisistheresultofmyworkasresearchassociateintheComputerNetworkingTechnology
point,GroupIofwtheouldlikInstituteetoeforxpressmyExperimentalacknowledgementMathematicstoatevtheerybodyUnivhaersityvingofDuisbsupportedurg-Essen.meduringAtthismy
research.RSerPoolInparticular,Iwouldliketothankmyprimaryadvisor,ErwinP.Rathgeb,forhissupportofmy
RSerPoolresearchandthisthesis,aswellasmysecondaryadvisorKlausEchtleforhisthesisreview.
Furthermore,IwouldliketoexpressmyspecialthankstomyformercolleagueAndreasJungmaierfor
ashiswellgreatascooperationMichaelTin¨uxtheenSCfromTPLItheB/SMO¨CKunsterETAPUniIvprojectersityof(whichAppliedisthebasisSciencesofmyforRShisPLIBsupportprototype),ofthe
RSPLIBprojectandourIETFstandardizationcontributions.Furthermore,Iwouldliketothankmy
studentassistantsSebastianRohde(forwritingtheinitialversionoftheDemonstrationSystemGUI
myfortheRShand-writtenPLIBprototype)RSerPoolandsketchesJobinusingPulinthanaththeDIA(fordrawingapplicationprogram).testing,aswellasdrawingalotof
Indepartmentaddition,forIwsupportiouldngalsomyliketoRSerPoolthanktheprojectSiemensduringICNitsfirstInformationthreeandyears,aswellCommunicationastheNetwDeutscheorks
Forschungsgemeinschaft(DFG)forsponsoringtheprojectforanotherfouryears.
holzforFinallythe,Iyearswouldofliketoencouragementthankmyfandathersupport.ErnstG¨unterDreibholzandmymotherAnneloreDreib-

vii

viii

Contents

ContentsoductionIntr11.1Motivation........................................
1.2ScopeandRelatedWork................................
1.2.1Availability...................................
1.2.2LoadBalancing.................................
1.2.3FaultTolerance.................................
1.2.4ReliableServerPooling............................
1.3GoalsofthisThesis...................................
1.4OrganizationofthisThesis...............................
BasicsorkingNetw22.1TheOSIandTCP/IPNetworkingModels.......................
2.2TheStandardizationofNetworkProtocols.......................
2.3TheNetworkLayer...................................
2.3.1IPVersion4...................................
2.3.2IPVersion6...................................
2.4TheTransportLayer..................................
2.4.1UDP......................................
2.4.2TCP.......................................
2.4.3SCTP......................................
2.4.3.1Introduction.............................
2.4.3.2PacketFormat............................
2.4.3.3AssociationEstablishment......................
2.4.3.4Multi-Homing............................
2.4.3.5CongestionControl.........................
2.4.3.6UserDataTransport.........................
2.4.3.7Extensions..............................
2.5Summary........................................
3ReliableServerPooling
3.1Introduction.......................................
3.2TheRequirementsforRSerPool............................
3.3TheRSerPoolArchitecture...............................
3.4AMigrationPathforLegacyApplications.......................
ix

ix111223345779910101111121212121315151516171919202123

3.5TheProtocolStack...................................23
3.6TheApplicationScenarios...............................24
3.6.1TelephoneSignalling..............................25
3.6.2SessionInitiationProtocol(SIP)........................26
3.6.3IPFlowInformationExport(IPFIX)......................27
3.6.4LoadBalancing.................................27
3.6.5Real-TimeDistributedComputing.......................28
3.6.5.1Requirements............................29
3.6.5.2ApplicabilityofRSerPool......................29
3.6.6MobilitySupportforSCTP...........................29
3.6.7OtherApplicationScenarios..........................30
3.7TheRSerPoolComponents...............................31
3.7.1Registrar....................................31
3.7.1.1Announces..............................32
3.7.1.2PoolManagement..........................32
3.7.1.3PoolMonitoring...........................33
3.7.1.4ServerSelectionandFailureReporting...............35
3.7.1.5HandlespaceAuditandHandlingofPRFailures..........35
3.7.2PoolElement..................................35
3.7.3PoolUser....................................36
3.8TheProtocolDesign..................................37
3.9TheAggregateServerAccessProtocol.........................38
3.9.1Overview....................................38
3.9.2PoolElementFunctionality..........................39
3.9.2.1RegistrationandReregistration...................39
3.9.2.2Monitoring..............................42
3.9.2.3Deregistration............................42
3.9.3PoolUserFunctionality............................43
3.9.3.1HandleResolution..........................43
3.9.3.2FailureReport............................44
3.9.4AutomaticConfigurationFunctionality....................44
3.9.5SessionLayerFunctionality..........................45
3.9.5.1DataChannelandControlChannel.................45
3.9.5.2ASAPCookies............................46
3.9.5.3ASAPBusinessCards........................48
3.10TheEndpointHandlespaceRedundancyProtocol...................49
3.10.1Overview....................................49
3.10.2AutomaticConfiguration............................49
3.10.2.1TheENRPPresenceMessage....................49
3.10.2.2DynamicandStaticPeerTableConfiguration...........51
3.10.2.3MaintainingConnectionstoPeerRegistrars............52
3.10.2.4ObtainingthePeerTablefromPeerRegistrars...........52
3.10.3RegistrarInitialization.............................54
3.10.4HandleUpdate.................................55
3.10.5HandlespaceAuditandSynchronization....................56
3.10.6TakeoverProcedure...............................57
3.11ThePoolMemberSelectionPolicies..........................59
x

3.11.1Basics......................................60
3.11.2Non-AdaptivePolicies.............................60
3.11.2.1RoundRobinandWeightedRoundRobin.............60
3.11.2.2RandomandWeightedRandom...................61
3.11.3AdaptivePolicies................................61
3.11.3.1LeastUsed..............................61
3.11.3.2PriorityLeastUsed.........................61
3.12TheMechanismsforServiceReliabilityandAvailability...............62
3.12.1FailureModel..................................62
3.12.2MechanismsoftheTransportLayer......................62
3.12.3MechanismsoftheSessionLayer.......................63
3.12.4SupportforRedundancyModels........................65
3.13SecurityConsiderations.................................65
3.14Summary........................................65
67ManagementHandlespaceThe44.1Introduction.......................................67
4.2ImplementationHistoryandLessonsLearned..........