ࡱ; L  !"#$%&'()*+-./0123456789:;<=>?@ABCDEFGHIJKMNORoot Entry  !"#$%&(*+,- ®`VTextStarWriter 5.0 Ȉ 4 SfxDocumentInfo Alan Robertson $01,DAlan Robertson sX1L8Alan Robertson sX18 Info 0 Info 1 Info 2 Info 3 $01,D^-#<44Standard LIBIMBEDDED LIBIMBEDDED TASK,0,1,H32,0,100,1,5961;39594;125;1824;35016;13344;41892;0;0SW5HDR.0sX1L8!  Internet linkVisited Internet LinkFootnote SymbolBullet Symbols:TeletypeNumbering Symbols Footnote anchor Line numbering 345167281 294833101Outline0 # R  n+.starbats n+.starbats6 n+.starbatsQ n+.starbatsl n+.starbats n+.starbats n+.starbats n+.starbats n+.starbats n+.starbats R   n+.starbats n+.starbats6 n+.starbatsQ n+.starbatsl n+.starbats n+.starbats n+.starbats n+.starbats n+.starbats n+.starbats ZSBX sb Z Standard StarBASICSBX ARXSWG, A<  #$%&'()*./0123456789:;<=>?@ABCDGHK  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFQRSTUD0A!'*@XX%'@:eX']@  starbatsCourierTimes New RomanStandardXX!X3'^@id d d xd d d XXX"X,X6X@' @X'@X'@XX+'$(@XXX8'&@;XX9''@^X'(A@. !. n. . XX!X-6')@X@'1 @ rdrddrdddddd7ddd7dd`dddd*d*dd*ddddddXX!X4XGXZXmXXXA'2j@dddxdddddxdxdddXXX&X2X>XJ7S;"@SXX8S<4@XXX"9S=(@XX('@$@XR'D@XJJ@=XDe8WvfnRPZ$' '(. . p. @ . . . . . P. . . !. $. `'. 0*. -. /. 2. p5. @8. ;. =. @. 6')} 2o  'K Internet link Internet link@!''Visited Internet LinkVisited Internet Link!''Footnote SymbolFootnote SymbolBullet SymbolsBullet Symbols''TeletypeTeletype':Numbering SymbolsNumbering SymbolsFootnote anchorFootnote anchor%' Line numberingLine numbering FrameFrame;7S<8S=9S>> GraphicsGraphics;7S<8S=9S>> OLEOLE;7S<8S=9S>> FormulaFormula1@'<8S>> StandardStandard@HeaderStandardHeader('JJ Header leftStandard Header left('JJFooterStandardFooter('JJHeadingStandard Text body@''2A'DR'  Text bodyStandard Text body@ ''$+'&8''9')6'1@'2A'33 Heading 1Heading Text body''$+'33 Horizontal LineStandard Text body'2A'@('0Table Contents Text bodyTable Contents Table HeadingTable Contents Table Heading'$+'SenderStandardSender ' Heading 2Heading Text body@''$+'33DR'  Heading 3Heading Text body''$+'&8''9'('2A'33  Heading 4Heading Text body''  Heading 5Heading Text body'' Heading 6Heading Text body'' List HeadingStandard List Contents1@'0 List ContentsStandard List Contents1@'0 References Text body References('1@'Text body indent Text bodyText body indent1@'List Text bodyListCaptionStandardCaption' '2A'JJIndexStandardIndexJJ Abstract Text bodyAbstract1@'dt Text bodydd'1@'2A'33DR'dd Text bodydt1@'FootnoteStandardFootnote'1@'JJ R(\`8f*xI.f4wB M ^ SBX AR SBX AR2c%bqqOh+'0 h t 197@S@it@t@ǻAlan RobertsonAlan RobertsonSW5HDR.0sX1L8!,= Frameformat ZeichenformatTextformatvorlageStandardHeader Header leftFooter Heading Text body  Heading 10Horizontal LineTable Contents Table HeadingSender  Heading 2  Heading 3  Heading 4 Heading 5 Heading 60 List Heading0 List Contents ReferencesText body indentListCaption IndexAbstractdtdd Footnote Internet linkVisited Internet LinkFootnote SymbolBullet Symbols:TeletypeNumbering Symbols Footnote anchor Line numbering Frame Graphics OLE FormulaRoot 43 Column 44 Column 45 Column 46 Column 47 Column 48 Column 49 50 51Standard First Page Right Page Left PageHTMLFootnote  Illustration Table TextDrawingY 9.Y :.Y ;.Y <.q'y& GeneralGeneraldNC#,###.00#,###.00SystemNC #,##0.00 CCC#,##0.00 CCCNC$#,##0.--;[RED]-$#,##0.-- $#,##0.---$#,##0.--REDNC$ MM/DD/YYYYMM/DD/YYYY def/SystemNC%MM/DD/YYMM/DD/YY def/SystemNC&NNNNMMMM DD, YYYYNNNNMMMM  DD, YYYYSystemNC' MMM D, YYMMM D, YY def/SystemNC. [HH]:MM:SS.00 [HH ]:MM:SS .00NC3MM/DD/YYYY HH:MM:SS MM/DD/YYYY HH :MM:SS  NCK MMM D, YYYYMMM D, YYYY def/SystemNCL MMMM D, YYYYMMMM  D, YYYY def/SystemNCM NN, MMM D, YYNN, MMM D, YY def/SystemNCNNN, MMMM D, YYYYNN, MMMM  D, YYYY def/SystemNCONNNNMMMM D, YYYYNNNNMMMM  D, YYYY def/SystemNCP D. MMM. YYYYD. MMM. YYYYDIN 5008 (EN 28601)NCQ D. MMMM YYYYD. MMMM  YYYYDIN 5008 (EN 28601)NCRMM-DDMM-DDDIN 5008 (EN 28601)NCSYY-MM-DDYY-MM-DDDIN 5008 (EN 28601)NCT YYYY-MM-DDYYYY-MM-DDDIN 5008 (EN 28601)NCUWWWWNCStandardStandarddNC#.##0,00#.##0,00SystemNC #.##0,00 CCC#.##0,00 CCCNC#.##0,-- DM;[ROT]-#.##0,-- DM #.##0,-- DM-#.##0,-- DMROTNC TT.MM.JJJJTT.MM.JJJJ def/SystemNCTT.MM.JJTT.MM.JJ def/SystemNCNNNNT. MMMM JJJJNNNNT. MMMM  JJJJSystemNC T. MMM JJT. MMM JJ def/SystemNC [HH]:MM:SS,00 [HH ]:MM:SS ,00NCTT.MM.JJJJ HH:MM:SS TT.MM.JJJJ HH :MM:SS  NC T. MMM JJJJT. MMM JJJJ def/SystemNC T. MMMM JJJJT. MMMM  JJJJ def/SystemNC NN, T. MMM JJNN, T. MMM JJ def/SystemNCNN, T. MMMM JJJJNN, T. MMMM  JJJJ def/SystemNCNNNNT. MMMM JJJJNNNNT. MMMM  JJJJ def/SystemNC T. MMM. JJJJT. MMM. JJJJDIN 5008 (EN 28601)NC T. MMMM JJJJT. MMMM  JJJJDIN 5008 (EN 28601)NCMM-TTMM-TTDIN 5008 (EN 28601)NCJJ-MM-TTJJ-MM-TTDIN 5008 (EN 28601)NC JJJJ-MM-TTJJJJ-MM-TTDIN 5008 (EN 28601)NCWWWWNC' GeneralGeneraldNC' #,###.00#,###.00SystemNC('  #,##0.00 CCC#,##0.00 CCCNC)' $#,##0.--;[RED]-$#,##0.-- $#,##0.---$#,##0.--REDNC4'  MM/DD/YYYYMM/DD/YYYY def/SystemNC5' MM/DD/YYMM/DD/YY def/SystemNC6' NNNNMMMM DD, YYYYNNNNMMMM  DD, YYYYSystemNC7'  MMM D, YYMMM D, YY def/SystemNC>'  [HH]:MM:SS.00 [HH ]:MM:SS .00NCC' MM/DD/YYYY HH:MM:SS MM/DD/YYYY HH :MM:SS  NC['  MMM D, YYYYMMM D, YYYY def/SystemNC\'  MMMM D, YYYYMMMM  D, YYYY def/SystemNC]'  NN, MMM D, YYNN, MMM D, YY def/SystemNC^' NN, MMMM D, YYYYNN, MMMM  D, YYYY def/SystemNC_' NNNNMMMM D, YYYYNNNNMMMM  D, YYYY def/SystemNC`'  D. MMM. YYYYD. MMM. YYYYDIN 5008 (EN 28601)NCa'  D. MMMM YYYYD. MMMM  YYYYDIN 5008 (EN 28601)NCb' MM-DDMM-DDDIN 5008 (EN 28601)NCc' YY-MM-DDYY-MM-DDDIN 5008 (EN 28601)NCd'  YYYY-MM-DDYYYY-MM-DDDIN 5008 (EN 28601)NCe' WWWWNCBoeqeoeP%p  332$99 SpAP/=APdddAPddA PA  PAPd!SfAP/=APdddAPddA PAPd!p 462$99 SUAP/=APdddAPddA PA  PSAAP/=APdddAPddp 562$99 SUAP/=APpdddpAPndndA PA  PSAAP/=APpdddpAPndndp 652$99 SUAP/=APdpddAPndndA PA  PSAAP/=APdpddAPndndp 732$:: SpAP/=APnd7ddnAP7d7dA PA  PAPd+)S\AP/=APnd7ddnAP7d7dAPd+)p 882$SAAP.AAPndnddnAPndndSAAP.AAPndnddnAPndndZSW5HDR.0sX1L8C(569a(Build:5169)(SV569)]D!Address Book Fileaddress!,= Frameformat ZeichenformatTextformatvorlageStandardHeader Header leftFooter Heading Text body  Heading 10Horizontal LineTable Contents Table HeadingSender  Heading 2  Heading 3  Heading 4 Heading 5 Heading 60 List Heading0 List Contents ReferencesText body indentListCaption IndexAbstractdtdd Footnote Internet linkVisited Internet LinkFootnote SymbolBullet Symbols:TeletypeNumbering Symbols Footnote anchor Line numbering Frame Graphics OLE FormulaRoot 43 Column 44 Column 45 Column 46 Column 47 Column 48 Column 49 50 51Standard First Page Right Page Left PageHTMLFootnote  Illustration Table TextDrawingd3q"1 $4 5*%jK standard.dic(sun.dic@ soffice.dicX IgnoreAllListY 9.Y :.Y ;.Y <.6N/Tt$4The Open Cluster Framework (OCF) -A proposed charterS%A P3ATimesA84dT$IAlan Robertson - IBM Linux Technology Center - alanr@{unix.sh|us.ibm.com}SAd A @A8 A8 ,A8 ,IA8=>w/6> T6$ABSTRACTS#A  A A @T$One of the most commonly identified features which is felt to be necessary for LinuxTM to be considered "enterprise-ready" is High-Availability. High-Availability (HA) systems provide increased service availability through clustering techniques. Linux is also well-known for its Beowulf High Performance clustering software - which provides the most cost-effective supercomputing available for any platform.A8 A8TV:eTv$kAs befits the importance of these capabilities, a number of open source clustering projects have been created. These projects were been created independently largely for complex historical reasons, not generally because of political, philosophical or licensing differences. Because of these kinds of historical reasons, they originally shared little or no code. This minimized the benefits of the open source model, which both encourages and benefits from the sharing of common components. However, many of them share the need for a component for resetting cluster members. A component was created for filling this need with the specific intent of being a common component across open HA systems. This was quite successful, and this component has become standard across most open source HA systems. All of the projects involved have benefitted from this commonality.TC$8In light of this success, the author began to search for more ways to extend these benefits across a broader set of cluster infrastructure components. Towards this end, we have begun an effort to create a standard Open Clustering Framework specification, and have begun to implement a reference implementation.I'Section1sp1SeA PAPxxA  PA/PdxhhA PNV'IM'Section2sp12SeA PAPA  PA/PdhU V A PN&-T=$ BackgroundS(A LucidasansA T$This document has many holes in it, and will be filled out to include lots of missing details. Part of the purpose of these initial meetings is to fill in some of these gaps.S-ATimesA  A TM$The Open Cluster FrameworkS(A LucidasansA T;$OCF APIsS(A LucidasansA T$$The Open Cluster Framework will define a series of APIs - a set of external APIs and a set of internal APIs. It is intended that many clustering systems will eventually conform to the applicable external APIs. Defining these APIs is fundamentally a standards effort whose output includes these APIs. A second part of the OCF effort is to define a reference implementation of the standards. It is expected that the reference implementation will be developed in parallel with the standards themselves.S#ATimesA T$QClustering implementations which are based on the the OCF reference implementation will also conform to the internal (component) APIs as well. It is perfectly acceptable for a completely closed system not based in any way on the reference implementation to conform to the internal APIs, but it is not expected to be a common occurrence.S#ATimesA TO$OCF Reference ImplementationS(A LucidasansA T $The OCF reference implementation will be available for download - and will be licensed under an open source license - see the section on OCF IP policies for more details. This effort will be a full-fledged community development effort to develop a set of common clustering utilities which could be used in a demanding commercial setting. It is also the intent of the reference implementation that it could be used in conjunction with commercial components and implementations.S#ATimesA TB$The OCF ProcessS(A LucidasansA T$The OCF working group will be self-governing, operating under as few constraints as are consistent with the needs of the task, legal prudence, and the wishes of the participants.S#ATimesA T$This section obviously needs a good bit more work, and needs to cover things like what membership means, who can participate, what the method of reaching a decision is, etc.S#ATimesA TB$OCF IP PoliciesS(A LucidasansA T$All OCF documentation will be available free of charge. There will be no charge associated with writing software which conforms to the specification, and no standard will be approved which is known to require the payment of royalties. In other words, the standards we create will be Royalty-Free (RF). However, there may be a trademarked designation for implementations which have been officially certified as conforming to the specification. If such a designation is created, there will likely be a charge for it. The documentation will be provided under a license similar to the Open Publication License or the GNU Free Documentation License. The software of the reference implementation will be provided under the GNU Lesser General Public License (LGPL). Certain selected pieces of software which are classified more as templates, and have not significant algorithmic or testing value may be licensed under the BSD license. It isn't clear if these will be provided as part of the documentation or part of the source to the reference implementation, or some in each. Software or documentation "templates" will be under a slightly less restrictive license than the components of the framework itself. S#ATimesA T,$These practices are expected to be consistent with the recommendations of the Free Standards Group for their standards. We will likely adopt their IP policy for standards as is. We are currently exploring affiliation with the Free Standards Group (FSG).S#ATimesA Tj$<The OCF working group will refine and ratify these policies.S#ATimesA Tc$0Ways to Participate in the OCF Standards ProcessS(A LucidasansA T$~For legal reasons, it is our expectation that there will be three classes of participation in the OCF standards working group.S#ATimesA TB$Participants - people who subscribe to the associated standards mailing lists. All of these people will be informed of the IP policies of the OCF process, and their continued participation constitutes agreement with them.SQAPdddATimesA A @ 2948331013T)$Individual members - people who actively contribute language and suggestions to the standards process and have formally agreed to be bound by the OCF IP policy as individuals (not their employers).SQAPdddATimesA A @ 2948331013TC$Corporate members - people who participate on behalf of their company, and who will be asked to conform to the IP policy on behalf of their company, and who's company has signed the appropriate agreements for them to do so.SQAPdddATimesA A @ 2948331013TW$$Ways to Conform to the OCF StandardsS(A LucidasansA T$yThere are several ways which one can write software which conforms to the OCF standards. A few examples are given below:S#ATimesA T$sProvide a product consisting strictly of (a subset of) software components taken from the reference implementation.SQAPdddATimesA A @ 3451672813T$Provide a product consisting of mainly components from the reference implementation, with a few unique components - which are known to meet the standard APIs.SQAPdddATimesA A @ 3451672813Tj$Provide a product consisting of a few components from the reference implementation, and a large body of software not from the reference implementation, but with a set of interfaces to the functions provided by this product which conform to the standardized APIs.SQAPdddATimesA A @ 3451672813T$Provide a product consisting entirely of proprietary software with interfaces which conform to the reference APIs, and whose internal architecture bears no resemblance to OCF components.SQAPdddATimesA A @ 3451672813TM$All of these are legitimate ways to conform to the standard. The first ones are lower-cost to write and maintain, and enjoy the well-known benefits of the open source development model. A company may start out with the in one model, and migrate to the "mostly open" approach over time.S#ATimesA Tq$CThis flexibility will allow a company to continue to meet the needs of their customers, and provide familiar interfaces, while migrating over time to have less and less unique software in their package. This lets them concentrate their development effort on the components which their customers have the most unique needs.S#ATimesA TU$"The Future of the Linux-HA projectS(A LucidasansA T$It is currently planned that the Linux-HA software be migrated to this new framework model, and that it will contribute to this framework project and provide reference components for it. Customers which are currently using the software will be able to use the new versions as they become available. The transformation of the heartbeat software to this new model is already underway.S#ATimesA TJ$The Linux-HA To Do listS(A LucidasansA T$dThe Linux-HA To Do list will be updated to include items associated with OCF development activities.S#ATimesA T=$ ConclusionS(A LucidasansA T$Everything from here on down contains a good bit of old stuff, and is not all relevant to this document ;-). Please feel free to ignore it at this time ;-)S(A LucidasansA T[$AcknowledgmentsA8A8 LucidasansA833T6$ To Learn MoreSA LucidasansT$The Linux-HA web site can be found at [Rob00]. Copies of documents related to the Open Clustering Framework, can currently be found at http://linux-ha.org/framework/A8&-A8T*$ ReferencesSA33T$[Milz99] Milz, Harald: "The Linux High Availability HOWTO". http://metalab.unc.edu/pub/linux/ALPHA/linux-ha/High-Availability-HOWTO.htmlAg8 =Lhttp://metalab.unc.edu/pub/Linux/ALPHA/linux-ha/High-Availability-HOWTO.htmlA8=wDT$Z[Phi98] In Search of Clusters, by Gregory F. Pfister, 2nd Edition 1998, Prentice Hall PTR.SA A8 A879:eT$W[Rob00] Robertson, A. L.,: "The High-Availability Linux Project". Http://linux-ha.org/A/8 CWhttp://Linux-ha.org/T$g[Twe00] Tweedie, S. C.,: "Barrier Operations". http://linux-ha.org/PhaseII/WhitePapers/sct/barrier.txtAR8 0g7http://linux-ha.org/PhaseII/WhitePapers/sct/barrier.txtwDL X\ T$X[Vas00] Vasa, M.,: "The Linux Fail Safe Project". http://oss.sgi.com/projects/failsafe/A/8 3Xhttp://Linux-ha.org/wOT'$t referA8T $SAJGeneric PrinterSGENPRT PostScriptH`Tl`Tld,,lprdefault_queueSGENPRT7 U.'V88/,?D/=U$2P33U$2?B$B$$B.$bx$B$U*x<|B $Z U*x<  B$ U*x<+"$$S2͞"G?„"?bE bE b5E b-`E b   r"UGIE?@T"E?b'b'zb   ж>/=U$2p33–U$2?ӂ"$2S2%"G22? "2? bE@bEDbxHb 5EIb 3abH"xefb%':xhb_)zjb,mb0YxnH"EGI2E2?@,"E2? b1rbxewbaxe|b> z~bbvxbx bxF!bK!x"bG%xF#b+x'$f}/=U$2P33FU$2?2"$r S2 "Gr r ?"r ? b%b#&b 5E'b (b5E)b*b5E+b`E,b--"EGIr Er ?@"Er ? b-Rb.b/b 6x0b 6x1b x2b x3b2bx4bbx5ZRoot Entry ®`V CompObj<Ole persist elements" SfxDocumentInfo uStarBASIC BasicManager2 4SfxWindowsCSwNumRulesSfxStyleSheetsStandard'jSummaryInformation( )@SwPageStyleSheets$ >0StarWriterDocument&,>