diff --git a/.gitignore b/.gitignore index 274324331f9..4661ea2750b 100644 --- a/.gitignore +++ b/.gitignore @@ -68,3 +68,5 @@ awsapi/overlays/ *.egg-info/ docs/tmp docs/publish +docs/runbook/tmp +docs/runbook/publish diff --git a/docs/runbook/tmp/en-US/pdf/Apache_CloudStack-3.0.2-Runbook-en-US.pdf b/docs/runbook/tmp/en-US/pdf/Apache_CloudStack-3.0.2-Runbook-en-US.pdf deleted file mode 100644 index d3b6ba0d212..00000000000 Binary files a/docs/runbook/tmp/en-US/pdf/Apache_CloudStack-3.0.2-Runbook-en-US.pdf and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Author_Group.xml b/docs/runbook/tmp/en-US/xml/Author_Group.xml deleted file mode 100644 index c0e946a4de0..00000000000 --- a/docs/runbook/tmp/en-US/xml/Author_Group.xml +++ /dev/null @@ -1,29 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - Apache - CloudStack - - - - diff --git a/docs/runbook/tmp/en-US/xml/Book_Info.xml b/docs/runbook/tmp/en-US/xml/Book_Info.xml deleted file mode 100644 index 4d32f7eef7a..00000000000 --- a/docs/runbook/tmp/en-US/xml/Book_Info.xml +++ /dev/null @@ -1,47 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - Runbook - Prescriptive instructions for deploying Apache CloudStack - Apache CloudStack - 3.0.2 - 0 - 0 - - - These runbooks are designed to provide a strict environment to guarantee a higher degree of success in initial deployments of Apache CloudStack. All of the elements of the environment will be provided to you. Apache CloudStack is capable of much more complex configurations, but they are beyond the scope of this document. - - - - - - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Chapter.xml b/docs/runbook/tmp/en-US/xml/Chapter.xml deleted file mode 100644 index d760ed81a82..00000000000 --- a/docs/runbook/tmp/en-US/xml/Chapter.xml +++ /dev/null @@ -1,55 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - Test Chapter - - This is a test paragraph - -
- Test Section 1 - - This is a test paragraph in a section - - -
- -
- Test Section 2 - - This is a test paragraph in Section 2 - - - - listitem text - - - - - - - - -
- - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/Conventions.xml b/docs/runbook/tmp/en-US/xml/Common_Content/Conventions.xml deleted file mode 100644 index cd7e8d46ae6..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/Conventions.xml +++ /dev/null @@ -1,178 +0,0 @@ - - -%BOOK_ENTITIES; -]> -
- Document Conventions - - This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information. - - - In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default. - -
- Typographic Conventions - - Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows. - - - Mono-spaced Bold - - - Used to highlight system input, including shell commands, file names and paths. Also used to highlight keycaps and key combinations. For example: - -
- - To see the contents of the file my_next_bestselling_novel in your current working directory, enter the cat my_next_bestselling_novel command at the shell prompt and press Enter to execute the command. - - -
- - The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold and all distinguishable thanks to context. - - - Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example: - -
- - Press Enter to execute the command. - - - Press CtrlAltF2 to switch to the first virtual terminal. Press CtrlAltF1 to return to your X-Windows session. - - -
- - The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with each set pressed simultaneously). - - - If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in mono-spaced bold. For example: - -
- - File-related classes include filesystem for file systems, file for files, and dir for directories. Each class has its own associated set of permissions. - - -
- - Proportional Bold - - - This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example: - -
- - Choose SystemPreferencesMouse from the main menu bar to launch Mouse Preferences. In the Buttons tab, click the Left-handed mouse check box and click Close to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand). - - - To insert a special character into a gedit file, choose ApplicationsAccessoriesCharacter Map from the main menu bar. Next, choose SearchFind… from the Character Map menu bar, type the name of the character in the Search field and click Next. The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the Copy button. Now switch back to your document and choose EditPaste from the gedit menu bar. - - -
- - The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context. - - - Mono-spaced Bold Italic or Proportional Bold Italic - - - Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example: - -
- - To connect to a remote machine using ssh, type ssh username@domain.name at a shell prompt. If the remote machine is example.com and your username on that machine is john, type ssh john@example.com. - - - The mount -o remount file-system command remounts the named file system. For example, to remount the /home file system, the command is mount -o remount /home. - - - To see the version of a currently installed package, use the rpm -q package command. It will return a result as follows: package-version-release. - - -
- - Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system. - - - Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example: - -
- - Publican is a DocBook publishing system. - - -
- -
- -
- Pull-quote Conventions - - Terminal output and source code listings are set off visually from the surrounding text. - - - Output sent to a terminal is set in mono-spaced roman and presented thus: - - -books Desktop documentation drafts mss photos stuff svn -books_tests Desktop1 downloads images notes scripts svgs - - Source-code listings are also set in mono-spaced roman but add syntax highlighting as follows: - - -package org.jboss.book.jca.ex1; - -import javax.naming.InitialContext; - -public class ExClient -{ - public static void main(String args[]) - throws Exception - { - InitialContext iniCtx = new InitialContext(); - Object ref = iniCtx.lookup("EchoBean"); - EchoHome home = (EchoHome) ref; - Echo echo = home.create(); - - System.out.println("Created Echo"); - - System.out.println("Echo.echo('Hello') = " + echo.echo("Hello")); - } -} - -
- -
- Notes and Warnings - - Finally, we use three visual styles to draw attention to information that might otherwise be overlooked. - - - Note - - Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier. - - - - - Important - - Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration. - - - - - Warning - - Warnings should not be ignored. Ignoring warnings will most likely cause data loss. - - - - -
- - -
- - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/Feedback.xml b/docs/runbook/tmp/en-US/xml/Common_Content/Feedback.xml deleted file mode 100644 index 0f8803bf4d5..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/Feedback.xml +++ /dev/null @@ -1,22 +0,0 @@ - - -%BOOK_ENTITIES; -]> -
- We Need Feedback! - - feedback1 - contact information for this brand - - - - If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a bug: http://bugs.cloudstack.org against the component Doc - - - If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily. - - -
- - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/Legal_Notice.xml b/docs/runbook/tmp/en-US/xml/Common_Content/Legal_Notice.xml deleted file mode 100644 index c193284071f..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/Legal_Notice.xml +++ /dev/null @@ -1,23 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at - - - http://www.apache.org/licenses/LICENSE-2.0 - - - Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. - - - Apache CloudStack is an effort undergoing incubation at The Apache Software Foundation (ASF). - - - Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/css/common.css b/docs/runbook/tmp/en-US/xml/Common_Content/css/common.css deleted file mode 100644 index d7dc3f27be8..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/css/common.css +++ /dev/null @@ -1,1528 +0,0 @@ -* { - widows: 2 !important; - orphans: 2 !important; -} - -body, h1, h2, h3, h4, h5, h6, pre, li, div { - line-height: 1.29em; -} - -body { - background-color: white; - margin:0 auto; - font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif; - font-size:12px; - max-width:55em; - color:black; -} - -body.toc_embeded { - /*for web hosting system only*/ - margin-left: 300px; -} - -object.toc, iframe.toc { - /*for web hosting system only*/ - border-style:none; - position:fixed; - width:290px; - height:99.99%; - top:0; - left:0; - z-index: 100; - border-style:none; - border-right:1px solid #999; -} - -/* Hide web menu */ - -body.notoc { - margin-left: 3em; -} - -iframe.notoc { - border-style:none; - border: none; - padding: 0em; - position:fixed; - width: 21px; - height: 29px; - top: 0px; - left:0; - overflow: hidden; - margin: 0em; - margin-left: -3px; -} -/* End hide web menu */ - -/* desktop styles */ -body.desktop { - margin-left: 26em; -} - -body.desktop .book > .toc { - display:block; - width:24em; - height:99%; - position:fixed; - overflow:auto; - top:0px; - left:0px; - padding-left:1em; - background-color:#EEEEEE; -} - -.toc { - line-height:1.35em; -} - -.toc .glossary, -.toc .chapter, .toc .appendix { - margin-top:1em; -} - -.toc .part { - margin-top:1em; - display:block; -} - -span.glossary, -span.appendix { - display:block; - margin-top:0.5em; -} - -div { - padding-top:0px; -} - -div.section { - padding-top:1em; -} - -p, div.para, div.formalpara { - padding-top:0px; - margin-top:0.3em; - padding-bottom:0px; - margin-bottom:1em; -} - -/*Links*/ -a { - outline: none; -} - -a:link { - text-decoration:none; - border-bottom: 1px dotted ; - color:#3366cc; -} - -a:visited { - text-decoration:none; - border-bottom: 1px dotted ; - color:#003366; -} - -div.longdesc-link { - float:right; - color:#999; -} - -.toc a, .qandaset a { - font-weight:normal; - border:none; -} - -.toc a:hover, .qandaset a:hover -{ - border-bottom: 1px dotted; -} - -/*headings*/ -h1, h2, h3, h4, h5, h6 { - color: #336699; - margin-top: 0em; - margin-bottom: 0em; - background-color: transparent; - page-break-inside: avoid; - page-break-after: avoid; -} - -h1 { - font-size:2.0em; -} - -.titlepage h1.title { - font-size: 3.0em; - padding-top: 1em; - text-align:left; -} - -.book > .titlepage h1.title { - text-align:center; -} - -.article > .titlepage h1.title { - text-align:center; -} - -.set .titlepage > div > div > h1.title { - text-align:center; -} - -.producttitle { - margin-top: 0em; - margin-bottom: 0em; - font-size: 3.0em; - font-weight: bold; - background: #003d6e url(../images/h1-bg.png) top left repeat-x; - color: white; - text-align: center; - padding: 0.7em; -} - -.titlepage .corpauthor { - margin-top: 1em; - text-align: center; -} - -.section h1.title { - font-size: 1.6em; - padding: 0em; - color: #336699; - text-align: left; - background: white; -} - -h2 { - font-size:1.6em; -} - - -h2.subtitle, h3.subtitle { - margin-top: 1em; - margin-bottom: 1em; - font-size: 1.4em; - text-align: center; -} - -.preface > div > div > div > h2.title { - margin-top: 1em; - font-size: 2.0em; -} - -.appendix h2 { - margin-top: 1em; - font-size: 2.0em; -} - - - -h3 { - font-size:1.3em; - padding-top:0em; - padding-bottom:0em; -} -h4 { - font-size:1.1em; - padding-top:0em; - padding-bottom:0em; -} - -h5 { - font-size:1em; -} - -h6 { - font-size:1em; -} - -h5.formalpara { - font-size:1em; - margin-top:2em; - margin-bottom:.8em; -} - -.abstract h6 { - margin-top:1em; - margin-bottom:.5em; - font-size:2em; -} - -/*element rules*/ -hr { - border-collapse: collapse; - border-style:none; - border-top: 1px dotted #ccc; - width:100%; - margin-top: 3em; -} - -/* web site rules */ -ul.languages, .languages li { - display:inline; - padding:0em; -} - -.languages li a { - padding:0em .5em; - text-decoration: none; -} - -.languages li p, .languages li div.para { - display:inline; -} - -.languages li a:link, .languages li a:visited { - color:#444; -} - -.languages li a:hover, .languages li a:focus, .languages li a:active { - color:black; -} - -ul.languages { - display:block; - background-color:#eee; - padding:.5em; -} - -/*supporting stylesheets*/ - -/*unique to the webpage only*/ -.books { - position:relative; -} - -.versions li { - width:100%; - clear:both; - display:block; -} - -a.version { - font-size:2em; - text-decoration:none; - width:100%; - display:block; - padding:1em 0em .2em 0em; - clear:both; -} - -a.version:before { - content:"Version"; - font-size:smaller; -} - -a.version:visited, a.version:link { - color:#666; -} - -a.version:focus, a.version:hover { - color:black; -} - -.books { - display:block; - position:relative; - clear:both; - width:100%; -} - -.books li { - display:block; - width:200px; - float:left; - position:relative; - clear: none ; -} - -.books .html { - width:170px; - display:block; -} - -.books .pdf { - position:absolute; - left:170px; - top:0px; - font-size:smaller; -} - -.books .pdf:link, .books .pdf:visited { - color:#555; -} - -.books .pdf:hover, .books .pdf:focus { - color:#000; -} - -.books li a { - text-decoration:none; -} - -.books li a:hover { - color:black; -} - -/*products*/ -.products li { - display: block; - width:300px; - float:left; -} - -.products li a { - width:300px; - padding:.5em 0em; -} - -.products ul { - clear:both; -} - -/*revision history*/ -.revhistory { - display:block; -} - -.revhistory table { - background-color:transparent; - border-color:#fff; - padding:0em; - margin: 0; - border-collapse:collapse; - border-style:none; -} - -.revhistory td { - text-align :left; - padding:0em; - border: none; - border-top: 1px solid #fff; - font-weight: bold; -} - -.revhistory .simplelist td { - font-weight: normal; -} - -.revhistory .simplelist { - margin-bottom: 1.5em; - margin-left: 1em; -} - -.revhistory table th { - display: none; -} - - -/*credits*/ -.authorgroup div { - clear:both; - text-align: center; -} - -h3.author { - margin: 0em; - padding: 0em; - padding-top: 1em; -} - -.authorgroup h4 { - padding: 0em; - margin: 0em; - padding-top: 1em; - margin-top: 1em; -} - -.author, -.editor, -.translator, -.othercredit, -.contrib { - display: block; -} - -.revhistory .author { - display: inline; -} - -.othercredit h3 { - padding-top: 1em; -} - - -.othercredit { - margin:0em; - padding:0em; -} - -.releaseinfo { - clear: both; -} - -.copyright { - margin-top: 1em; -} - -/* qanda sets */ -.answer { - margin-bottom:1em; - border-bottom:1px dotted #ccc; -} - -.qandaset .toc { - border-bottom:1px dotted #ccc; -} - -.question { - font-weight:bold; -} - -.answer .data, .question .data { - padding-left: 2.6em; -} - -.answer label, .question label { - float:left; - font-weight:bold; -} - -/* inline syntax highlighting */ -.perl_Alert { - color: #0000ff; -} - -.perl_BaseN { - color: #007f00; -} - -.perl_BString { - color: #5C3566; -} - -.perl_Char { - color: #ff00ff; -} - -.perl_Comment { - color: #FF00FF; -} - - -.perl_DataType { - color: #0000ff; -} - - -.perl_DecVal { - color: #00007f; -} - - -.perl_Error { - color: #ff0000; -} - - -.perl_Float { - color: #00007f; -} - - -.perl_Function { - color: #007f00; -} - - -.perl_IString { - color: #5C3566; -} - - -.perl_Keyword { - color: #002F5D; -} - - -.perl_Operator { - color: #ffa500; -} - - -.perl_Others { - color: #b03060; -} - - -.perl_RegionMarker { - color: #96b9ff; -} - - -.perl_Reserved { - color: #9b30ff; -} - - -.perl_String { - color: #5C3566; -} - - -.perl_Variable { - color: #0000ff; -} - - -.perl_Warning { - color: #0000ff; -} - -/*Lists*/ -ul { - padding-left:1.6em; - list-style-image:url(../images/dot.png); - list-style-type: circle; -} - -ul ul { - list-style-image:url(../images/dot2.png); - list-style-type: circle; -} - -ol { - list-style-image:none; - list-style-type: decimal; -} - -ol ol { - list-style-type: lower-alpha; -} - -ol.arabic { - list-style-type: decimal; -} - -ol.loweralpha { - list-style-type: lower-alpha; -} - -ol.lowerroman { - list-style-type: lower-roman; -} - -ol.upperalpha { - list-style-type: upper-alpha; -} - -ol.upperroman { - list-style-type: upper-roman; -} - -dt { - font-weight:bold; - margin-bottom:0em; - padding-bottom:0em; -} - -dd { - margin:0em; - margin-left:2em; - padding-top:0em; - padding-bottom: 1em; -} - -li { - padding-top:0px; - margin-top:0em; - padding-bottom:0px; - margin-bottom:0.4em; -} - -li p, li div.para { - padding-top:0px; - margin-top:0em; - padding-bottom:0px; - margin-bottom:0.3em; -} - -/*images*/ -img { - display:block; - margin: 2em 0; -} - -.inlinemediaobject, .inlinemediaobject img { - display:inline; - margin:0em; -} - -.figure img { - display:block; - margin:0; - page-break-inside: avoid; -} - -.figure .title { - margin:0em; - margin-bottom:2em; - padding:0px; -} - -/*document modes*/ -.confidential { - background-color:#900; - color:White; - padding:.5em .5em; - text-transform:uppercase; - text-align:center; -} - -.longdesc-link { - display:none; -} - -.longdesc { - display:none; -} - -.prompt { - padding:0em .3em; -} - -/*user interface styles*/ -.screen .replaceable { -} - -.guibutton, .guilabel { - font-family: "liberation mono", "bitstream vera mono", "dejavu mono", monospace; - font-weight: bold; - white-space: nowrap; -} - -.example { - background-color: #ffffff; - border-left: 3px solid #aaaaaa; - padding-top: 1em; - padding-bottom: 0.1em; -} - -.example h6 { - padding-left: 10px; -} - -.example-contents { - padding-left: 10px; - background-color: #ffffff; -} - -.example-contents .para { -/* padding: 10px;*/ -} - -/*terminal/console text*/ -.computeroutput, -.option { - font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace; - font-weight:bold; -} - -.replaceable { - font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace; - font-style: italic; -} - -.command, .filename, .keycap, .classname, .literal { - font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace; - font-weight:bold; -} - -/* no bold in toc */ -.toc * { - font-weight: inherit; -} - -pre { - font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace; - display:block; - background-color: #f5f5f5; - color: #000000; - border: 1px solid #aaaaaa; - margin-bottom: 0.3em; - padding:.5em 1em; - white-space: pre-wrap; /* css-3 */ - white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */ - white-space: -pre-wrap; /* Opera 4-6 */ - white-space: -o-pre-wrap; /* Opera 7 */ - word-wrap: break-word; /* Internet Explorer 5.5+ */ - font-size: 0.9em; -} - -pre .replaceable, -pre .keycap { -} - -code { - font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace; -/* white-space: nowrap;*/ - white-space: pre-wrap; - word-wrap: break-word; - font-weight:bold; -} - -.parameter code { - display: inline; - white-space: pre-wrap; /* css-3 */ - white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */ - white-space: -pre-wrap; /* Opera 4-6 */ - white-space: -o-pre-wrap; /* Opera 7 */ - word-wrap: break-word; /* Internet Explorer 5.5+ */ -} - -/*Notifications*/ -div.warning:before { - content:url(../images/warning.png); - padding-left: 5px; -} - -div.note:before { - content:url(../images/note.png); - padding-left: 5px; -} - -div.important:before { - content:url(../images/important.png); - padding-left: 5px; -} - -div.warning, div.note, div.important { - color: black; - margin: 0em; - padding: 0em; - background: none; - background-color: white; - margin-bottom: 1em; - border-bottom: 1px solid #aaaaaa; - page-break-inside: avoid; -} - -div.warning h2, div.note h2,div.important h2 { - margin: 0em; - padding: 0em; - color: #eeeeec; - padding-top: 0px; - padding-bottom: 0px; - height: 1.4em; - line-height: 1.4em; - font-size: 1.4em; - display:inline; -} - -div.admonition_header { - clear: both; - margin: 0em; - padding: 0em; - margin-top: -3.3em; - padding-left: 58px; - line-height: 1.0em; - font-size: 1.0em; -} - -div.warning div.admonition_header { - background: url(../images/red.png) top left repeat-x; - background-color: #590000; -} - -div.note div.admonition_header { - background: url(../images/green.png) top right repeat-x; - background-color: #597800; -} - -div.important div.admonition_header { - background: url(../images/yellow.png) top right repeat-x; - background-color: #a6710f; -} - -div.warning p, div.warning div.para, -div.note p, div.note div.para, -div.important p, div.important div.para { - padding: 0em; - margin: 0em; -} - -div.admonition { - border: none; - border-left: 1px solid #aaaaaa; - border-right: 1px solid #aaaaaa; - padding:0em; - margin:0em; - padding-top: 1.5em; - padding-bottom: 1em; - padding-left: 2em; - padding-right: 1em; - background-color: #eeeeec; - -moz-border-radius: 0px; - -webkit-border-radius: 0px; - border-radius: 0px; -} - -/*Page Title*/ -#title { - display:block; - height:45px; - padding-bottom:1em; - margin:0em; -} - -#title a.left{ - display:inline; - border:none; -} - -#title a.left img{ - border:none; - float:left; - margin:0em; - margin-top:.7em; -} - -#title a.right { - padding-bottom:1em; -} - -#title a.right img { - border:none; - float:right; - margin:0em; - margin-top:.7em; -} - -/*Table*/ -div.table { - page-break-inside: avoid; -} - -table { - border:1px solid #6c614b; - width:100%; - border-collapse:collapse; -} - -table.simplelist, .calloutlist table { - border-style: none; -} - -table th { - text-align:left; - background-color:#6699cc; - padding:.3em .5em; - color:white; -} - -table td { - padding:.15em .5em; -} - -table tr.even td { - background-color:#f5f5f5; -} - -table th p:first-child, table td p:first-child, table li p:first-child, -table th div.para:first-child, table td div.para:first-child, table li div.para:first-child { - margin-top:0em; - padding-top:0em; - display:inline; -} - -th, td { - border-style:none; - vertical-align: top; - border: 1px solid #000; -} - -.simplelist th, .simplelist td { - border: none; -} - -table table td { - border-bottom:1px dotted #aaa; - background-color:white; - padding:.6em 0em; -} - -table table { - border:1px solid white; -} - -td.remarkval { - color:#444; -} - -td.fieldval { - font-weight:bold; -} - -.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost { - color:white; - font-weight:bold; - background-color:#999; - width:120px; -} - -td.remarkval { - width:230px; -} - -td.tname { - font-weight:bold; -} - -th.dbfield { - width:120px; -} - -th.dbtype { - width:70px; -} - -th.dbdefault { - width:70px; -} - -th.dbnul { - width:70px; -} - -th.dbkey { - width:70px; -} - -span.book { - margin-top:4em; - display:block; - font-size:11pt; -} - -span.book a{ - font-weight:bold; -} -span.chapter { - display:block; - margin-top:0.5em; -} - -table.simplelist td, .calloutlist table td { - border-style: none; -} - -/*Breadcrumbs*/ -#breadcrumbs ul li.first:before { - content:" "; -} - -#breadcrumbs { - color:#900; - padding:3px; - margin-bottom:25px; -} - -#breadcrumbs ul { - margin-left:0; - padding-left:0; - display:inline; - border:none; -} - -#breadcrumbs ul li { - margin-left:0; - padding-left:2px; - border:none; - list-style:none; - display:inline; -} - -#breadcrumbs ul li:before { - content:"\0020 \0020 \0020 \00BB \0020"; - color:#333; -} - -/*index*/ -.glossary h3, -.index h3 { - font-size: 2em; - color:#aaa; - margin:0em; -} - -.indexdiv { - margin-bottom:1em; -} - -.glossary dt, -.index dt { - color:#444; - padding-top:.5em; -} - -.glossary dl dl dt, -.index dl dl dt { - color:#777; - font-weight:normal; - padding-top:0em; -} - -.index dl dl dt:before { - content:"- "; - color:#ccc; -} - -/*changes*/ -.footnote { - font-size: .7em; - margin:0em; - color:#222; -} - -table .footnote { -} - -sup { - color:#999; - margin:0em; - padding:0em; - line-height: .4em; - font-size: 1em; - padding-left:0em; -} - -.footnote { - position:relative; -} - -.footnote sup { - color:#e3dcc0; - position:absolute; - left: .4em; -} - -.footnote sup a:link, -.footnote sup a:visited { - color:#92917d; - text-decoration:none; -} - -.footnote:hover sup a { - text-decoration:none; -} - -.footnote p,.footnote div.para { - padding-left:2em; -} - -.footnote a:link, -.footnote a:visited { - color:#00537c; -} - -.footnote a:hover { -} - -/**/ -div.chapter { - margin-top:3em; - page-break-inside: avoid; -} - -div.preface { - page-break-inside: avoid; -} - -div.section { - margin-top:1em; - page-break-inside: auto; -} - -div.note .replaceable, -div.important .replaceable, -div.warning .replaceable, -div.note .keycap, -div.important .keycap, -div.warning .keycap -{ -} - -ul li p:last-child, ul li div.para:last-child { - margin-bottom:0em; - padding-bottom:0em; -} - -/*document navigation*/ -.docnav a, .docnav strong { - border:none; - text-decoration:none; - font-weight:normal; -} - -.docnav { - list-style:none; - margin:0em; - padding:0em; - position:relative; - width:100%; - padding-bottom:2em; - padding-top:1em; - border-top:1px dotted #ccc; -} - -.docnav li { - list-style:none; - margin:0em; - padding:0em; - display:inline; - font-size:.8em; -} - -.docnav li:before { - content:" "; -} - -.docnav li.previous, .docnav li.next { - position:absolute; - top:1em; -} - -.docnav li.up, .docnav li.home { - margin:0em 1.5em; -} - -.docnav li.previous { - left:0px; - text-align:left; -} - -.docnav li.next { - right:0px; - text-align:right; -} - -.docnav li.previous strong, .docnav li.next strong { - height:22px; - display:block; -} - -.docnav { - margin:0 auto; - text-align:center; -} - -.docnav li.next a strong { - background: url(../images/stock-go-forward.png) top right no-repeat; - padding-top:3px; - padding-bottom:4px; - padding-right:28px; - font-size:1.2em; -} - -.docnav li.previous a strong { - background: url(../images/stock-go-back.png) top left no-repeat; - padding-top:3px; - padding-bottom:4px; - padding-left:28px; - padding-right:0.5em; - font-size:1.2em; -} - -.docnav li.home a strong { - background: url(../images/stock-home.png) top left no-repeat; - padding:5px; - padding-left:28px; - font-size:1.2em; -} - -.docnav li.up a strong { - background: url(../images/stock-go-up.png) top left no-repeat; - padding:5px; - padding-left:28px; - font-size:1.2em; -} - -.docnav a:link, .docnav a:visited { - color:#666; -} - -.docnav a:hover, .docnav a:focus, .docnav a:active { - color:black; -} - -.docnav a { - max-width: 10em; - overflow:hidden; -} - -.docnav a:link strong { - text-decoration:none; -} - -.docnav { - margin:0 auto; - text-align:center; -} - -ul.docnav { - margin-bottom: 1em; -} -/* Reports */ -.reports ul { - list-style:none; - margin:0em; - padding:0em; -} - -.reports li{ - margin:0em; - padding:0em; -} - -.reports li.odd { - background-color: #eeeeee; - margin:0em; - padding:0em; -} - -.reports dl { - display:inline; - margin:0em; - padding:0em; - float:right; - margin-right: 17em; - margin-top:-1.3em; -} - -.reports dt { - display:inline; - margin:0em; - padding:0em; -} - -.reports dd { - display:inline; - margin:0em; - padding:0em; - padding-right:.5em; -} - -.reports h2, .reports h3{ - display:inline; - padding-right:.5em; - font-size:10pt; - font-weight:normal; -} - -.reports div.progress { - display:inline; - float:right; - width:16em; - background:#c00 url(../images/shine.png) top left repeat-x; - margin:0em; - margin-top:-1.3em; - padding:0em; - border:none; -} - -/*uniform*/ -body.results, body.reports { - max-width:57em ; - padding:0em; -} - -/*Progress Bar*/ -div.progress { - display:block; - float:left; - width:16em; - background:#c00 url(../images/shine.png) top left repeat-x; - height:1em; -} - -div.progress span { - height:1em; - float:left; -} - -div.progress span.translated { - background:#6c3 url(../images/shine.png) top left repeat-x; -} - -div.progress span.fuzzy { - background:#ff9f00 url(../images/shine.png) top left repeat-x; -} - - -/*Results*/ - -.results ul { - list-style:none; - margin:0em; - padding:0em; -} - -.results li{ - margin:0em; - padding:0em; -} - -.results li.odd { - background-color: #eeeeee; - margin:0em; - padding:0em; -} - -.results dl { - display:inline; - margin:0em; - padding:0em; - float:right; - margin-right: 17em; - margin-top:-1.3em; -} - -.results dt { - display:inline; - margin:0em; - padding:0em; -} - -.results dd { - display:inline; - margin:0em; - padding:0em; - padding-right:.5em; -} - -.results h2, .results h3 { - display:inline; - padding-right:.5em; - font-size:10pt; - font-weight:normal; -} - -.results div.progress { - display:inline; - float:right; - width:16em; - background:#c00 url(../images/shine.png) top left repeat-x; - margin:0em; - margin-top:-1.3em; - padding:0em; - border:none; -} - -/* Dirty EVIL Mozilla hack for round corners */ -pre { - -moz-border-radius:11px; - -webkit-border-radius:11px; - border-radius: 11px; - page-break-inside: avoid; -} - -.example { - -moz-border-radius:0px; - -webkit-border-radius:0px; - border-radius: 0px; - page-break-inside: avoid; -} - -.package, .citetitle { - font-style: italic; -} - -.titlepage .edition { - color: #336699; - background-color: transparent; - margin-top: 1em; - margin-bottom: 1em; - font-size: 1.4em; - font-weight: bold; - text-align: center; -} - -span.remark { - background-color: #ff00ff; -} - -.draft { - background-image: url(../images/watermark-draft.png); - background-repeat: repeat-y; - background-position: center; -} - -.foreignphrase { - font-style: inherit; -} - -dt { - clear:both; -} - -dt img { - border-style: none; - max-width: 112px; -} - -dt object { - max-width: 112px; -} - -dt .inlinemediaobject, dt object { - display: inline; - float: left; - margin-bottom: 1em; - padding-right: 1em; - width: 112px; -} - -dl:after { - display: block; - clear: both; - content: ""; -} - -.toc dd { - padding-bottom: 0em; - margin-bottom: 1em; - padding-left: 1.3em; - margin-left: 0em; -} - -div.toc > dl > dt { - padding-bottom: 0em; - margin-bottom: 0em; - margin-top: 1em; -} - - -.strikethrough { - text-decoration: line-through; -} - -.underline { - text-decoration: underline; -} - -.calloutlist img, .callout { - padding: 0em; - margin: 0em; - width: 12pt; - display: inline; - vertical-align: middle; -} - -.stepalternatives { - list-style-image: none; - list-style-type: none; -} - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/css/default.css b/docs/runbook/tmp/en-US/xml/Common_Content/css/default.css deleted file mode 100644 index bf38ebb5931..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/css/default.css +++ /dev/null @@ -1,3 +0,0 @@ -@import url("common.css"); -@import url("overrides.css"); -@import url("lang.css"); diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/css/lang.css b/docs/runbook/tmp/en-US/xml/Common_Content/css/lang.css deleted file mode 100644 index 81c3115605a..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/css/lang.css +++ /dev/null @@ -1,2 +0,0 @@ -/* place holder */ - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/css/overrides.css b/docs/runbook/tmp/en-US/xml/Common_Content/css/overrides.css deleted file mode 100644 index ebd9730b690..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/css/overrides.css +++ /dev/null @@ -1,57 +0,0 @@ -a:link { - color:#0066cc; -} - -a:visited { - color:#6699cc; -} - -h1 { - color:#3c6eb4; -} - -.producttitle { - background: #3c6eb4 url(../images/h1-bg.png) top left repeat; -} - -.section h1.title { - color:#3c6eb4; -} - - -h2,h3,h4,h5,h6 { - color:#3c6eb4 -} - -table { - border:1px solid #3c6eb4; -} - -table th { - background-color:#3c6eb4; -} - -table tr.even td { - background-color:#f5f5f5; -} - -#title a { - height:54px; -} - -.term{ - color:#a70000; -} - -.revhistory table th { - color:#3c6eb4; -} - -.edition { - color: #3c6eb4; -} - -span.remark{ - background-color: #ffff00; -} - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/css/print.css b/docs/runbook/tmp/en-US/xml/Common_Content/css/print.css deleted file mode 100644 index 773d8ae1b1c..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/css/print.css +++ /dev/null @@ -1,16 +0,0 @@ -@import url("common.css"); -@import url("overrides.css"); -@import url("lang.css"); - -#tocframe { - display: none; -} - -body.toc_embeded { - margin-left: 30px; -} - -.producttitle { - color: #336699; -} - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/1.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/1.png deleted file mode 100644 index ef0beba8510..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/1.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/1.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/1.svg deleted file mode 100644 index 4c6bf579527..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/1.svg +++ /dev/null @@ -1,27 +0,0 @@ - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/10.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/10.png deleted file mode 100644 index 05f22391ea7..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/10.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/10.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/10.svg deleted file mode 100644 index 0edda5b6fa6..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/10.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/11.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/11.png deleted file mode 100644 index 32b4a04831e..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/11.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/11.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/11.svg deleted file mode 100644 index c95afcc14a1..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/11.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/12.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/12.png deleted file mode 100644 index 45fa4892a94..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/12.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/12.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/12.svg deleted file mode 100644 index e3c3fd66c7d..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/12.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/13.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/13.png deleted file mode 100644 index 0b766d3f87b..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/13.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/13.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/13.svg deleted file mode 100644 index 35b4969143d..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/13.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/14.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/14.png deleted file mode 100644 index 2e1d73716c2..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/14.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/14.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/14.svg deleted file mode 100644 index 832f816799a..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/14.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/15.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/15.png deleted file mode 100644 index 7d21c66bb04..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/15.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/15.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/15.svg deleted file mode 100644 index 830d65439c6..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/15.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/16.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/16.png deleted file mode 100644 index ff396af2fa6..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/16.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/16.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/16.svg deleted file mode 100644 index 24d1eea0458..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/16.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/17.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/17.png deleted file mode 100644 index f1ba68a7f60..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/17.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/17.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/17.svg deleted file mode 100644 index 7796bd1d7db..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/17.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/18.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/18.png deleted file mode 100644 index df920d02515..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/18.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/18.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/18.svg deleted file mode 100644 index 356f207eefb..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/18.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/19.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/19.png deleted file mode 100644 index bda9a8c559d..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/19.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/19.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/19.svg deleted file mode 100644 index 385378074ed..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/19.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/2.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/2.png deleted file mode 100644 index b95445a4e73..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/2.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/2.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/2.svg deleted file mode 100644 index 236a8dacbc4..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/2.svg +++ /dev/null @@ -1,27 +0,0 @@ - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/20.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/20.png deleted file mode 100644 index c30191a3653..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/20.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/20.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/20.svg deleted file mode 100644 index d41206eec57..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/20.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/21.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/21.png deleted file mode 100644 index fa3aa907dcf..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/21.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/21.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/21.svg deleted file mode 100644 index b17f23a5a9a..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/21.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/22.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/22.png deleted file mode 100644 index b724ced1311..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/22.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/22.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/22.svg deleted file mode 100644 index 22deeb3edbb..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/22.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/23.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/23.png deleted file mode 100644 index 8b69b829282..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/23.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/23.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/23.svg deleted file mode 100644 index c0a33eeb0b0..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/23.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/24.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/24.png deleted file mode 100644 index 863ce3b6632..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/24.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/24.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/24.svg deleted file mode 100644 index 27e1d39c94f..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/24.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/25.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/25.png deleted file mode 100644 index cc23b9b2b04..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/25.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/25.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/25.svg deleted file mode 100644 index 114e1a26ba6..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/25.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/26.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/26.png deleted file mode 100644 index 583fe34867d..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/26.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/26.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/26.svg deleted file mode 100644 index e9b5d239b55..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/26.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/27.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/27.png deleted file mode 100644 index d1c3dfa457a..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/27.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/27.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/27.svg deleted file mode 100644 index 4a80177b68d..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/27.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/28.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/28.png deleted file mode 100644 index f5db74735d7..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/28.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/28.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/28.svg deleted file mode 100644 index d453f299fa2..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/28.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/29.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/29.png deleted file mode 100644 index 9a3141ec42e..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/29.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/29.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/29.svg deleted file mode 100644 index 04b5c5034fc..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/29.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/3.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/3.png deleted file mode 100644 index a4754f0615c..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/3.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/3.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/3.svg deleted file mode 100644 index e2f17168da1..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/3.svg +++ /dev/null @@ -1,27 +0,0 @@ - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/30.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/30.png deleted file mode 100644 index 9d3db242d90..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/30.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/30.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/30.svg deleted file mode 100644 index 5cdcf65e846..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/30.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/31.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/31.png deleted file mode 100644 index 9e2675da589..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/31.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/31.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/31.svg deleted file mode 100644 index f0fdb294dd8..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/31.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/32.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/32.png deleted file mode 100644 index 20f1bb23c4b..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/32.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/32.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/32.svg deleted file mode 100644 index 93829281032..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/32.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/33.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/33.png deleted file mode 100644 index 01407e6bcce..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/33.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/33.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/33.svg deleted file mode 100644 index f46815f7ea6..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/33.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/34.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/34.png deleted file mode 100644 index ba443525397..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/34.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/34.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/34.svg deleted file mode 100644 index 7bbdf5b9ab2..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/34.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/35.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/35.png deleted file mode 100644 index 21d4575cf27..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/35.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/35.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/35.svg deleted file mode 100644 index 8e19553af20..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/35.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/36.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/36.png deleted file mode 100644 index b5402b57788..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/36.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/36.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/36.svg deleted file mode 100644 index d364dbf51bb..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/36.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/37.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/37.png deleted file mode 100644 index 9fd99d22058..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/37.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/37.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/37.svg deleted file mode 100644 index 771fa4d110b..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/37.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/38.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/38.png deleted file mode 100644 index 3ce6027f00f..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/38.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/38.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/38.svg deleted file mode 100644 index 487e0ef3051..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/38.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/39.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/39.png deleted file mode 100644 index d6894500c24..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/39.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/39.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/39.svg deleted file mode 100644 index cea69f715f9..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/39.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/4.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/4.png deleted file mode 100644 index f6c113563a1..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/4.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/4.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/4.svg deleted file mode 100644 index 3b537d4a19b..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/4.svg +++ /dev/null @@ -1,27 +0,0 @@ - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/40.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/40.png deleted file mode 100644 index 0d3532e0f3f..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/40.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/40.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/40.svg deleted file mode 100644 index bb4e1d7b8fc..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/40.svg +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/5.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/5.png deleted file mode 100644 index 4ced5472dfc..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/5.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/5.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/5.svg deleted file mode 100644 index ec2715dea0b..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/5.svg +++ /dev/null @@ -1,27 +0,0 @@ - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/6.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/6.png deleted file mode 100644 index 22fc272c050..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/6.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/6.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/6.svg deleted file mode 100644 index b8062936898..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/6.svg +++ /dev/null @@ -1,27 +0,0 @@ - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/7.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/7.png deleted file mode 100644 index 9b1f20a9816..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/7.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/7.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/7.svg deleted file mode 100644 index 871e0eff74f..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/7.svg +++ /dev/null @@ -1,27 +0,0 @@ - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/8.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/8.png deleted file mode 100644 index ac38ae5bffd..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/8.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/8.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/8.svg deleted file mode 100644 index 10e612f6eb9..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/8.svg +++ /dev/null @@ -1,27 +0,0 @@ - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/9.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/9.png deleted file mode 100644 index a2972dbc216..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/9.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/9.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/9.svg deleted file mode 100644 index c488b6e4fa4..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/9.svg +++ /dev/null @@ -1,27 +0,0 @@ - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/dot.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/dot.png deleted file mode 100644 index 079add95ded..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/dot.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/dot2.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/dot2.png deleted file mode 100644 index 8348fcd054a..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/dot2.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/green.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/green.png deleted file mode 100644 index ebb3c247dea..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/green.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/h1-bg.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/h1-bg.png deleted file mode 100644 index a2aad24b329..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/h1-bg.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/image_left.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/image_left.png deleted file mode 100644 index 2831477642c..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/image_left.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/image_right.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/image_right.png deleted file mode 100644 index 19a6cca5336..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/image_right.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/important.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/important.png deleted file mode 100644 index 969562b7bc7..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/important.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/important.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/important.svg deleted file mode 100644 index 064c783b538..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/important.svg +++ /dev/null @@ -1,30 +0,0 @@ - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/note.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/note.png deleted file mode 100644 index d04775d9905..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/note.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/note.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/note.svg deleted file mode 100644 index abe5a602468..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/note.svg +++ /dev/null @@ -1,28 +0,0 @@ - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/red.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/red.png deleted file mode 100644 index d32d5e2e80a..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/red.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/shine.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/shine.png deleted file mode 100644 index a18f7c4612e..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/shine.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/stock-go-back.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/stock-go-back.png deleted file mode 100644 index 00850b21b23..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/stock-go-back.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/stock-go-forward.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/stock-go-forward.png deleted file mode 100644 index cc2797a4686..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/stock-go-forward.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/stock-go-up.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/stock-go-up.png deleted file mode 100644 index 1ebf2799c35..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/stock-go-up.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/stock-home.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/stock-home.png deleted file mode 100644 index 3f0c1906343..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/stock-home.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/title_logo.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/title_logo.png deleted file mode 100644 index 58a1b56cfe8..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/title_logo.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/title_logo.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/title_logo.svg deleted file mode 100644 index e8b3eca8d82..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/title_logo.svg +++ /dev/null @@ -1,335 +0,0 @@ - - - -image/svg+xml - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -open source cloud computing - - - - - \ No newline at end of file diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/warning.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/warning.png deleted file mode 100644 index 94b69d1ff1f..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/warning.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/warning.svg b/docs/runbook/tmp/en-US/xml/Common_Content/images/warning.svg deleted file mode 100644 index 4231e5ac041..00000000000 --- a/docs/runbook/tmp/en-US/xml/Common_Content/images/warning.svg +++ /dev/null @@ -1,130 +0,0 @@ - - - - - - - image/svg+xml - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/watermark-draft.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/watermark-draft.png deleted file mode 100644 index 0ead5af8bb8..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/watermark-draft.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Common_Content/images/yellow.png b/docs/runbook/tmp/en-US/xml/Common_Content/images/yellow.png deleted file mode 100644 index 223865d77fa..00000000000 Binary files a/docs/runbook/tmp/en-US/xml/Common_Content/images/yellow.png and /dev/null differ diff --git a/docs/runbook/tmp/en-US/xml/Environment.xml b/docs/runbook/tmp/en-US/xml/Environment.xml deleted file mode 100644 index 93b765d72ce..00000000000 --- a/docs/runbook/tmp/en-US/xml/Environment.xml +++ /dev/null @@ -1,248 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - Environment - - Before you begin, you need to prepare the environment before you install CloudStack. We will go over the steps to prepare now. - -
- Operating System - - Using the CentOS 6.2 x86_64 minimal install ISO, you'll need to install CentOS on your hardware. The defaults will generally be acceptable for this installation. - - - Once this installation is complete, you'll want to connect to your freshly installed machine via SSH as the root user. Note that you should not allow root logins in a production environment, so be sure to turn off remote logins once you have finished the installation and configuration. - -
- Configuring the network - - By default the network will not come up on your hardware and you will need to configure it to work in your environment. Since we specified that there will be no DHCP server in this environment we will be manually configuring your network interface. We will assume, for the purposes of this exercise, that eth0 is the only network interface that will be connected and used. - - - Connecting via the console you should login as root. Check the file /etc/sysconfig/network-scripts/ifcfg-eth0, it will look like this by default: - -DEVICE="eth0" -HWADDR="52:54:00:B9:A6:C0" -NM_CONTROLLED="yes" -ONBOOT="no" - - - - - Unfortunately, this configuration will not permit you to connect to the network, and is also unsuitable for our purposes with CloudStack. We want to configure that file so that it specifies the IP address, netmask, etc., as shown in the following example: - - - Hardware Addresses - - You should not use the hardware address (aka MAC address) from our example for your configuration. It is network interface specific, so you should keep the address already provided in the HWADDR directive. - - - - - -DEVICE=eth0 -HWADDR=52:54:00:B9:A6:C0 -NM_CONTROLLED=no -ONBOOT=yes -BOOTPROTO=none -IPADDR=172.16.10.2 -NETMASK=255.255.255.0 -GATEWAY=172.16.10.1 -DNS1=8.8.8.8 -DNS2=8.8.4.4 - - - IP Addressing - - Throughout this document we are assuming that you will have a /24 network for your CloudStack implementation. This can be any RFC 1918 network. However, we are assuming that you will match the machine address that we are using. Thus we may use 172.16.10.2 and because you might be using the 192.168.55.0/24 network you would use 192.168.55.2 - - - - - Now that we have the configuration files properly set up, we need to run a few commands to start up the network - - -# chkconfig network on - -# service network start - -
- -
- Hostname - - Cloudstack requires that the hostname be properly set. If you used the default options in the installation, then your hostname is currently set to localhost.localdomain. To test this we will run: - - -# hostname --fqdn - - At this point it will likely return: - - -localhost - - To rectify this situation - we'll set the hostname by editing the /etc/hosts file so that it follows a similar format to this example: - -127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 -172.16.10.2 srvr1.cloud.priv - - - - - After you've modified that file, go ahead and restart the network using: - - -# service network restart - - Now recheck with the hostname --fqdn command and ensure that it returns a FQDN response - - -
- -
- SELinux - - At the moment, for CloudStack to work properly SELinux must be set to permissive. We want to both configure this for future boots and modify it in the current running system. - - - To configure SELinux to be permissive in the running system we need to run the following command: - - -# setenforce 0 - - To ensure that it remains in that state we need to configure the file /etc/selinux/config to reflect the permissive state, as shown in this example: - - - - -# This file controls the state of SELinux on the system. -# SELINUX= can take one of these three values: -# enforcing - SELinux security policy is enforced. -# permissive - SELinux prints warnings instead of enforcing. -# disabled - No SELinux policy is loaded. -SELINUX=permissive -# SELINUXTYPE= can take one of these two values: -# targeted - Targeted processes are protected, -# mls - Multi Level Security protection. -SELINUXTYPE=targeted - - -
- -
- NTP - - NTP configuration is a necessity for keeping all of the clocks in your cloud servers in sync. However, NTP is not installed by default. So we'll install and and configure NTP at this stage. Installation is accomplished as follows: - - -# yum install ntp - - The actual default configuration is fine for our purposes, so we merely need to enable it and set it to start on boot as follows: - - -# chkconfig ntpd on - -# service ntpd start - -
- - -
- -
- NFS - - Our configuration is going to use NFS for both primary and secondary storage. We are going to go ahead and setup two NFS shares for those purposes. We'll start out by installing nfs-utils. - - -# yum install nfs-utils - - We now need to configure NFS to serve up two different shares. This is handled comparatively easily in the /etc/exports file. You should ensure that it has the following content: - - - -/secondary *(rw,async,no_root_squash) -/primary *(rw,async,no_root_squash) - - - You will note that we specified two directories that don't exist (yet) on the system. We'll go ahead and create those directories and set permissions appropriately on them with the following commands: - - - -# mkdir /primary -# mkdir /secondary - - - CentOS 6.x releases use NFSv4 by default. NFSv4 requires that domain setting matches on all clients. In our case, the domain is cloud.priv, so ensure that the domain setting in /etc/idmapd.conf is uncommented and set as follows: - - -Domain = cloud.priv - - Now you'll need uncomment the configuration values in the file /etc/sysconfig/nfs - - - -LOCKD_TCPPORT=32803 -LOCKD_UDPPORT=32769 -MOUNTD_PORT=892 -RQUOTAD_PORT=875 -STATD_PORT=662 -STATD_OUTGOING_PORT=2020 - - - Now we need to configure the firewall to permit incoming NFS connections. Edit the file /etc/sysconfig/iptables - - - --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 111 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 111 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 2049 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 32803 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 32769 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 892 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 892 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 875 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 875 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 662 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 662 -j ACCEPT - - - Now you can restart the iptables service with the following command: - - -# service iptables restart - - We now need to configure nfs service to start on boot and actually start it on the host by executing the following commands: - - - - # service rpcbind start - # service nfs start - # chkconfig rpcbind on - # chkconfig nfs on - - -
- - - - diff --git a/docs/runbook/tmp/en-US/xml/Management.xml b/docs/runbook/tmp/en-US/xml/Management.xml deleted file mode 100644 index 8cbd8f87d34..00000000000 --- a/docs/runbook/tmp/en-US/xml/Management.xml +++ /dev/null @@ -1,125 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - Installation of the management server - - Now it is time to start installing CloudStack's management server and some of the related components. - -
- Database Installation and Configuration - - We'll start out by installing MySQL and configuring some options to ensure CloudStack runs well. - - - To install MySQL run the following command: -# yum -y install mysql-server - - - - With MySQL installed we need to make a few configuration changes to /etc/my.cnf. Specifically we need to add the following options to the [mysqld] section: - -innodb_rollback_on_timeout=1 -innodb_lock_wait_timeout=600 -max_connections=350 -log-bin=mysql-bin -binlog-format = 'ROW' - - - - - Now that MySQL is properly configured we can start it and configure it to start on boot as follows: - - # service mysqld start - # chkconfig mysqld on - - - - -
- -
- Extraction - - The next step is to extract the contents of the CloudStack tarball (mentioned in ) you downloaded previously. To extract the contents of this tarball use the following command: - - - - # tar -xzvf CloudStack-oss-3.0.2-1-rhel6.2.tar.gz - - - For the next few sections you'll need to cd into the first level that was just created. - - -
- -
- Installation - - Now that you are in the directory created by extracting the tarball, it's now time to install. We'll run ./install.sh and choose option . This will install the management server and necessary dependencies. - - - With the application itself installed we can now setup the database, we'll do that with the following command and options: - - - - # cloud-setup-databases cloud:password@localhost --deploy-as=root - - - When this process is finished, you should see a message like "CloudStack has successfully initialized the database." - - - Now that the database has been created, we can take the final step in setting up the management server by issuing the following command: - - - - # cloud-setup-mangament - - -
- -
- System Template Setup - - CloudStack uses a number of system VMs to provide functionality for accessing the console of virtual machines, providing various networking services, and managing various aspects of storage. This step will acquire those system images ready for deployment when we bootstrap your cloud. - - - The place we are going to download these images to is the secondary storage share that we setup earlier, so we'll need to mount that share with the mount command run on the management server: - - - - # mount -t nfs 172.16.10.2:/secondary /mnt/secondary - - - Now we need to download the system VM template and deploy that to the share we just mounted. The management server includes a script to properly manipulate the system VMs images. - - - - # /usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -F - - - That concludes our setup of the management server. We still need to configure CloudStack, but we will do that after we get our hypervisor set up. - - -
- - - diff --git a/docs/runbook/tmp/en-US/xml/Overview.xml b/docs/runbook/tmp/en-US/xml/Overview.xml deleted file mode 100644 index 05b6e8d6126..00000000000 --- a/docs/runbook/tmp/en-US/xml/Overview.xml +++ /dev/null @@ -1,87 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - Overview - - Infrastructure-as-a-Service (IaaS) clouds can be a complex thing to build, and by definition they have a plethora of options, which often lead to confusion for even experienced admins who are newcomers to building cloud platforms. The goal for this runbook is to provide a straightforward set of instructions to get you up and running with CloudStack with a minimum amount of trouble. - -
- What exactly are we building? - - This runbook will focus on building a CloudStack cloud using KVM with CentOS 6.2 with NFS storage on a flat layer-2 network utilizing layer-3 network isolation (aka Security Groups), and doing it all on a single piece of hardware. - - - KVM, or Kernel-based Virtual Machine is a virtualization technology for the Linux kernel. KVM supports native virtualization atop processors with hardware virtualization extensions. - - - Security Groups act as distributed firewalls that control access to a group of virtual machines. - - -
- -
- High level overview of the process - - Before we actually get to installing CloudStack, we'll start with installing our base operating system, and then configuring that to act as an NFS server for several types of storage. We'll install the management server, download the systemVMs, and finally install the agent software. Finally we'll spend a good deal of time configuring the entire cloud in the CloudStack web interface. - - -
- -
- Prerequisites - - To complete this runbook you'll need the following items: - - - - At least one computer which supports hardware virtualization. - - - - - - The CentOS 6.2 x86_64 minimal install CD - - - - - - A /24 network with the gateway being at xxx.xxx.xxx.1, no DHCP should be on this network and none of the computers running CloudStack may have a dynamic address. - - - - - - Copy of CloudStack 3.0.2 for RHEL and CentOS 6.2 - - - - - - - - -
- - - - diff --git a/docs/runbook/tmp/en-US/xml/Preface.xml b/docs/runbook/tmp/en-US/xml/Preface.xml deleted file mode 100644 index 556e2121d28..00000000000 --- a/docs/runbook/tmp/en-US/xml/Preface.xml +++ /dev/null @@ -1,29 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - Preface - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Revision_History.xml b/docs/runbook/tmp/en-US/xml/Revision_History.xml deleted file mode 100644 index 1927b3c5510..00000000000 --- a/docs/runbook/tmp/en-US/xml/Revision_History.xml +++ /dev/null @@ -1,43 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - Revision History - - - - 0-0 - Mon Jun 25 2012 - - - Initial creation of book by publican - - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Runbook.ent b/docs/runbook/tmp/en-US/xml/Runbook.ent deleted file mode 100644 index cdc00b05f62..00000000000 --- a/docs/runbook/tmp/en-US/xml/Runbook.ent +++ /dev/null @@ -1,22 +0,0 @@ - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/Runbook.fo b/docs/runbook/tmp/en-US/xml/Runbook.fo deleted file mode 100644 index 96b05a6d61c..00000000000 --- a/docs/runbook/tmp/en-US/xml/Runbook.fo +++ /dev/null @@ -1,416 +0,0 @@ - -Runbook - Prescriptive instructions for deploying Apache CloudStackDocBook XSL Stylesheets with Apache FOPRunbookTable of ContentsPreface1. Document Conventions1.1. Typographic Conventions1.2. Pull-quote Conventions1.3. Notes and Warnings2. We Need Feedback!Chapter 1. Overview1.1. What exactly are we building?1.2. High level overview of the process1.3. PrerequisitesChapter 2. Environment2.1. Operating System2.1.1. Configuring the network2.1.2. Hostname2.1.3. SELinux2.1.4. NTP2.2. NFSChapter 3. Installation of the management server3.1. Database Installation and Configuration3.2. Extraction3.3. Installation3.4. System Template SetupChapter 4. KVM Setup and installation4.1. Prerequisites4.2. Installation4.3. KVM ConfigurationChapter 5. Configuration5.1. UI Access5.2. Setting up a Zone5.3. Pod Configuration5.4. Cluster5.4.1. Primary Storage5.4.2. Secondary StorageAppendix A. Revision HistoryRunbookApache CloudStack 3.0.2RunbookPrescriptive instructions for deploying Apache CloudStack - - - Apache CloudStackApache CloudStack 3.0.2 RunbookPrescriptive instructions for deploying Apache CloudStackEdition 0AuthorApache CloudStack - Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. - - Apache CloudStack is an effort undergoing incubation at The Apache Software Foundation (ASF). - - Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. - - These runbooks are designed to provide a strict environment to guarantee a higher degree of success in initial deployments of Apache CloudStack. All of the elements of the environment will be provided to you. Apache CloudStack is capable of much more complex configurations, but they are beyond the scope of this document. - RunbookPreface   1. Document Conventions 1.1. Typographic Conventions 1.2. Pull-quote Conventions 1.3. Notes and Warnings 2. We Need Feedback! 1. Overview   1.1. What exactly are we building? 1.2. High level overview of the process 1.3. Prerequisites 2. Environment   2.1. Operating System 2.1.1. Configuring the network 2.1.2. Hostname 2.1.3. SELinux 2.1.4. NTP 2.2. NFS 3. Installation of the management server   3.1. Database Installation and Configuration 3.2. Extraction 3.3. Installation 3.4. System Template Setup 4. KVM Setup and installation   4.1. Prerequisites 4.2. Installation 4.3. KVM Configuration 5. Configuration   5.1. UI Access 5.2. Setting up a Zone 5.3. Pod Configuration 5.4. Cluster 5.4.1. Primary Storage 5.4.2. Secondary Storage A. Revision History   PrefacePrefaceDocument Conventions1. Document Conventions - This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information. - - In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts11 https://fedorahosted.org/liberation-fonts/ set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default. - Typographic Conventions1.1. Typographic Conventions - Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows. - - Mono-spaced Bold - - Used to highlight system input, including shell commands, file names and paths. Also used to highlight keycaps and key combinations. For example: - - To see the contents of the file my_next_bestselling_novel in your current working directory, enter the cat my_next_bestselling_novel command at the shell prompt and press Enter to execute the command. - - The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold and all distinguishable thanks to context. - - Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example: - - Press Enter to execute the command. - - Press Ctrl+Alt+F2 to switch to the first virtual terminal. Press Ctrl+Alt+F1 to return to your X-Windows session. - - The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with each set pressed simultaneously). - - If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in mono-spaced bold. For example: - - File-related classes include filesystem for file systems, file for files, and dir for directories. Each class has its own associated set of permissions. - - Proportional Bold - - This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example: - - Choose System → Preferences → Mouse from the main menu bar to launch Mouse Preferences. In the Buttons tab, click the Left-handed mouse check box and click Close to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand). - - To insert a special character into a gedit file, choose Applications → Accessories → Character Map from the main menu bar. Next, choose Search → Find… from the Character Map menu bar, type the name of the character in the Search field and click Next. The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the Copy button. Now switch back to your document and choose Edit → Paste from the gedit menu bar. - - The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context. - - Mono-spaced Bold Italic or Proportional Bold Italic - - Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example: - - To connect to a remote machine using ssh, type ssh username@domain.name at a shell prompt. If the remote machine is example.com and your username on that machine is john, type ssh john@example.com. - - The mount -o remount file-system command remounts the named file system. For example, to remount the /home file system, the command is mount -o remount /home. - - To see the version of a currently installed package, use the rpm -q package command. It will return a result as follows: package-version-release. - - Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system. - - Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example: - - Publican is a DocBook publishing system. - Pull-quote Conventions1.2. Pull-quote Conventions - Terminal output and source code listings are set off visually from the surrounding text. - - Output sent to a terminal is set in mono-spaced roman and presented thus: - books Desktop documentation drafts mss photos stuff svn -books_tests Desktop1 downloads images notes scripts svgs - Source-code listings are also set in mono-spaced roman but add syntax highlighting as follows: - package org.jboss.book.jca.ex1; - -import javax.naming.InitialContext; - -public class ExClient -{ - public static void main(String args[]) - throws Exception - { - InitialContext iniCtx = new InitialContext(); - Object ref = iniCtx.lookup("EchoBean"); - EchoHome home = (EchoHome) ref; - Echo echo = home.create(); - - System.out.println("Created Echo"); - - System.out.println("Echo.echo('Hello') = " + echo.echo("Hello")); - } -}Notes and Warnings1.3. Notes and Warnings - Finally, we use three visual styles to draw attention to information that might otherwise be overlooked. - Note - Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier. - Important - Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration. - Warning - Warnings should not be ignored. Ignoring warnings will most likely cause data loss. - We Need Feedback!2. We Need Feedback! - If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a bug: http://bugs.cloudstack.org against the component Doc - - If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily. - Chapter 1.Chapter 1. OverviewOverview - Infrastructure-as-a-Service (IaaS) clouds can be a complex thing to build, and by definition they have a plethora of options, which often lead to confusion for even experienced admins who are newcomers to building cloud platforms. The goal for this runbook is to provide a straightforward set of instructions to get you up and running with CloudStack with a minimum amount of trouble. - What exactly are we building?1.1. What exactly are we building? - This runbook will focus on building a CloudStack cloud using KVM with CentOS 6.2 with NFS storage on a flat layer-2 network utilizing layer-3 network isolation (aka Security Groups), and doing it all on a single piece of hardware. - - KVM, or Kernel-based Virtual Machine is a virtualization technology for the Linux kernel. KVM supports native virtualization atop processors with hardware virtualization extensions. - - Security Groups act as distributed firewalls that control access to a group of virtual machines. - High level overview of the process1.2. High level overview of the process - Before we actually get to installing CloudStack, we'll start with installing our base operating system, and then configuring that to act as an NFS server for several types of storage. We'll install the management server, download the systemVMs, and finally install the agent software. Finally we'll spend a good deal of time configuring the entire cloud in the CloudStack web interface. - Prerequisites1.3. Prerequisites - To complete this runbook you'll need the following items: - 1. - At least one computer which supports hardware virtualization. - 2. - The CentOS 6.2 x86_64 minimal install CD 11 http://mirrors.kernel.org/centos/6.2/isos/x86_64/CentOS-6.2-x86_64-minimal.iso - 3. - A /24 network with the gateway being at xxx.xxx.xxx.1, no DHCP should be on this network and none of the computers running CloudStack may have a dynamic address. - 4. - Copy of CloudStack 3.0.2 for RHEL and CentOS 6.2 22 http://sourceforge.net/projects/cloudstack/files/CloudStack%20Acton/3.0.2/CloudStack-oss-3.0.2-1-rhel6.2.tar.gz/download - - - Chapter 2.Chapter 2. EnvironmentEnvironment - Before you begin, you need to prepare the environment before you install CloudStack. We will go over the steps to prepare now. - Operating System2.1. Operating System - Using the CentOS 6.2 x86_64 minimal install ISO, you'll need to install CentOS on your hardware. The defaults will generally be acceptable for this installation. - - Once this installation is complete, you'll want to connect to your freshly installed machine via SSH as the root user. Note that you should not allow root logins in a production environment, so be sure to turn off remote logins once you have finished the installation and configuration. - Configuring the network2.1.1. Configuring the network - By default the network will not come up on your hardware and you will need to configure it to work in your environment. Since we specified that there will be no DHCP server in this environment we will be manually configuring your network interface. We will assume, for the purposes of this exercise, that eth0 is the only network interface that will be connected and used. - - Connecting via the console you should login as root. Check the file /etc/sysconfig/network-scripts/ifcfg-eth0, it will look like this by default: - -DEVICE="eth0" -HWADDR="52:54:00:B9:A6:C0" -NM_CONTROLLED="yes" -ONBOOT="no" - - - - Unfortunately, this configuration will not permit you to connect to the network, and is also unsuitable for our purposes with CloudStack. We want to configure that file so that it specifies the IP address, netmask, etc., as shown in the following example: - Hardware Addresses - You should not use the hardware address (aka MAC address) from our example for your configuration. It is network interface specific, so you should keep the address already provided in the HWADDR directive. - -DEVICE=eth0 -HWADDR=52:54:00:B9:A6:C0 -NM_CONTROLLED=no -ONBOOT=yes -BOOTPROTO=none -IPADDR=172.16.10.2 -NETMASK=255.255.255.0 -GATEWAY=172.16.10.1 -DNS1=8.8.8.8 -DNS2=8.8.4.4 -IP Addressing - Throughout this document we are assuming that you will have a /24 network for your CloudStack implementation. This can be any RFC 1918 network. However, we are assuming that you will match the machine address that we are using. Thus we may use 172.16.10.2 and because you might be using the 192.168.55.0/24 network you would use 192.168.55.2 - - Now that we have the configuration files properly set up, we need to run a few commands to start up the network - # chkconfig network on# service network startHostname2.1.2. Hostname - Cloudstack requires that the hostname be properly set. If you used the default options in the installation, then your hostname is currently set to localhost.localdomain. To test this we will run: - # hostname --fqdn - At this point it will likely return: - localhost - To rectify this situation - we'll set the hostname by editing the /etc/hosts file so that it follows a similar format to this example: - -127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 -172.16.10.2 srvr1.cloud.priv - - - - After you've modified that file, go ahead and restart the network using: - # service network restart - Now recheck with the hostname --fqdn command and ensure that it returns a FQDN response - SELinux2.1.3. SELinux - At the moment, for CloudStack to work properly SELinux must be set to permissive. We want to both configure this for future boots and modify it in the current running system. - - To configure SELinux to be permissive in the running system we need to run the following command: - # setenforce 0 - To ensure that it remains in that state we need to configure the file /etc/selinux/config to reflect the permissive state, as shown in this example: - - -# This file controls the state of SELinux on the system. -# SELINUX= can take one of these three values: -# enforcing - SELinux security policy is enforced. -# permissive - SELinux prints warnings instead of enforcing. -# disabled - No SELinux policy is loaded. -SELINUX=permissive -# SELINUXTYPE= can take one of these two values: -# targeted - Targeted processes are protected, -# mls - Multi Level Security protection. -SELINUXTYPE=targeted -NTP2.1.4. NTP - NTP configuration is a necessity for keeping all of the clocks in your cloud servers in sync. However, NTP is not installed by default. So we'll install and and configure NTP at this stage. Installation is accomplished as follows: - # yum install ntp - The actual default configuration is fine for our purposes, so we merely need to enable it and set it to start on boot as follows: - # chkconfig ntpd on# service ntpd startNFS2.2. NFS - Our configuration is going to use NFS for both primary and secondary storage. We are going to go ahead and setup two NFS shares for those purposes. We'll start out by installing nfs-utils. - # yum install nfs-utils - We now need to configure NFS to serve up two different shares. This is handled comparatively easily in the /etc/exports file. You should ensure that it has the following content: - -/secondary *(rw,async,no_root_squash) -/primary *(rw,async,no_root_squash) - - You will note that we specified two directories that don't exist (yet) on the system. We'll go ahead and create those directories and set permissions appropriately on them with the following commands: - -# mkdir /primary -# mkdir /secondary - - CentOS 6.x releases use NFSv4 by default. NFSv4 requires that domain setting matches on all clients. In our case, the domain is cloud.priv, so ensure that the domain setting in /etc/idmapd.conf is uncommented and set as follows: - Domain = cloud.priv - Now you'll need uncomment the configuration values in the file /etc/sysconfig/nfs - -LOCKD_TCPPORT=32803 -LOCKD_UDPPORT=32769 -MOUNTD_PORT=892 -RQUOTAD_PORT=875 -STATD_PORT=662 -STATD_OUTGOING_PORT=2020 - - Now we need to configure the firewall to permit incoming NFS connections. Edit the file /etc/sysconfig/iptables - --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 111 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 111 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 2049 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 32803 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 32769 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 892 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 892 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 875 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 875 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 662 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 662 -j ACCEPT - - Now you can restart the iptables service with the following command: - # service iptables restart - We now need to configure nfs service to start on boot and actually start it on the host by executing the following commands: - - # service rpcbind start - # service nfs start - # chkconfig rpcbind on - # chkconfig nfs on -Chapter 3.Chapter 3. Installation of the management serverInstallation of the management server - Now it is time to start installing CloudStack's management server and some of the related components. - Database Installation and Configuration3.1. Database Installation and Configuration - We'll start out by installing MySQL and configuring some options to ensure CloudStack runs well. - - To install MySQL run the following command: -# yum -y install mysql-server - - - With MySQL installed we need to make a few configuration changes to /etc/my.cnf. Specifically we need to add the following options to the [mysqld] section: - -innodb_rollback_on_timeout=1 -innodb_lock_wait_timeout=600 -max_connections=350 -log-bin=mysql-bin -binlog-format = 'ROW' - - - - Now that MySQL is properly configured we can start it and configure it to start on boot as follows: - - # service mysqld start - # chkconfig mysqld on - - - Extraction3.2. Extraction - The next step is to extract the contents of the CloudStack tarball (mentioned in Section 1.3, “Prerequisites”) you downloaded previously. To extract the contents of this tarball use the following command: - - # tar -xzvf CloudStack-oss-3.0.2-1-rhel6.2.tar.gz - - For the next few sections you'll need to cd into the first level that was just created. - Installation3.3. Installation - Now that you are in the directory created by extracting the tarball, it's now time to install. We'll run ./install.sh and choose option M. This will install the management server and necessary dependencies. - - With the application itself installed we can now setup the database, we'll do that with the following command and options: - - # cloud-setup-databases cloud:password@localhost --deploy-as=root - - When this process is finished, you should see a message like "CloudStack has successfully initialized the database." - - Now that the database has been created, we can take the final step in setting up the management server by issuing the following command: - - # cloud-setup-mangament -System Template Setup3.4. System Template Setup - CloudStack uses a number of system VMs to provide functionality for accessing the console of virtual machines, providing various networking services, and managing various aspects of storage. This step will acquire those system images ready for deployment when we bootstrap your cloud. - - The place we are going to download these images to is the secondary storage share that we setup earlier, so we'll need to mount that share with the mount command run on the management server: - - # mount -t nfs 172.16.10.2:/secondary /mnt/secondary - - Now we need to download the system VM template and deploy that to the share we just mounted. The management server includes a script to properly manipulate the system VMs images. - - # /usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -F - - That concludes our setup of the management server. We still need to configure CloudStack, but we will do that after we get our hypervisor set up. - Chapter 4.Chapter 4. KVM Setup and installationKVM Setup and installation - KVM is the hypervisor we'll be using - we will recover the initial setup which has already been done on the hypervisor host and cover installation of the agent software, you can use the same steps to add additional KVM nodes to your CloudStack environment. - Prerequisites4.1. Prerequisites - We explicitly are using the management server as a compute node as well, which means that we have already performed many of the prerequisite steps when setting up the management server, but we will list them here for clarity. Those steps are: - 1. - Section 2.1.1, “Configuring the network” - 2. - Section 2.1.2, “Hostname” - 3. - Section 2.1.3, “SELinux” - 4. - Section 2.1.4, “NTP” - - - - You shouldn't need to do that for the management server, of course, but any additional hosts will need for you to complete the above steps. - Installation4.2. Installation - You'll need to ensure that you are in the directory that was created when we extracted the the tarball. Section 3.2, “Extraction” - - You'll be running ./install.sh again and this time choosing A which will install the software necessary for managing a KVM node. - KVM Configuration4.3. KVM Configuration - KVM configuration is relatively simple at only a single item. We need to edit the QEMU VNC configuration. This is done by editing /etc/libvirt/qemu.conf and ensuring the following line is present and uncommented. -vnc_listen=0.0.0.0 - - - You can now just restart the libvirt daemon by issuing the following command: -# service libvirt restart - - - That concludes our installation and configuration of KVM, and we'll now move to using the CloudStack UI for the actual configuration of our cloud. - Chapter 5.Chapter 5. ConfigurationConfiguration - As we noted before we will be using security groups to provide isolation and by default that implies that we'll be using a flat layer-2 network. It also means that the simplicity of our setup means that we can use the quick installer. - UI Access5.1. UI Access - To get access to CloudStack's web interface, merely point your browser to http://172.16.10.2:8080/client The default username is 'admin', and the default password is 'password'. You should see a splash screen that allows you to choose several options for setting up CloudStack. You should choose the Continue with Basic Setup option. - - You should now see a prompt requiring you to change the password for the admin user. Please do so. - Setting up a Zone5.2. Setting up a Zone - A zone is the largest organization entity in CloudStack - and we'll be creating one, this should be the screen that you see in front of you now. And for us there are 5 pieces of information that we need. - 1. - Name - we will set this to the ever-descriptive 'Zone1' for our cloud. - 2. - Public DNS 1 - we will set this to '8.8.8.8' for our cloud. - 3. - Public DNS 2 - we will set this to '8.8.4.4' for our cloud. - 4. - Internal DNS1 - we will also set this to '8.8.8.8' for our cloud. - 5. - Internal DNS2 - we will also set this to '8.8.8.4' for our cloud. - - - Notes about DNS settings - CloudStack distinguishes between internal and public DNS. Internal DNS is assumed to be capable of resolving internal-only hostnames, such as your NFS server’s DNS name. Public DNS is provided to the guest VMs to resolve public IP addresses. You can enter the same DNS server for both types, but if you do so, you must make sure that both internal and public IP addresses can route to the DNS server. In our specific case we will not use any names for resources internally, and we have indeed them set to look to the same external resource so as to not add a namerserver setup to our list of requirements. - Pod Configuration5.3. Pod Configuration - Now that we've added a Zone, the next step that comes up is a prompt for information regading a pod. Which is looking for 4 items. - 1. - Name - We'll use Pod1 for our cloud. - 2. - Gateway - We'll use 172.16.10.1 as our gateway - 3. - Netmask - We'll use 255.255.255.0 - 4. - Start/end reserved system IPs - we will use 172.16.10.10-172.16.10.20 - 5. - Guest gateway - We'll use 172.16.10.1 - 6. - Guest netmask - We'll use 255.255.255.0 - 7. - Guest start/end IP - We'll use 172.16.10.30-172.16.10.200 - - - Cluster5.4. Cluster - Now that we've added a Zone, we need only add a few more items for configuring the cluster. - 1. - Name - We'll use Cluster1 - 2. - Hypervisor - Choose KVM - - - - You should be prompted to add the first host to your cluster at this point. Only a few bits of information are needed. - 1. - Hostname - we'll use the IP address 172.16.10.2 since we didn't set up a DNS server. - 2. - Username - we'll use 'root' - 3. - Password - enter the operating system password for the root user - - - Primary Storage5.4.1. Primary Storage - With you cluster now setup - you should be prompted for primary storage information. Choose NFS as the storage type and then enter the following values in the fields: - 1. - Name - We'll use 'Primary1' - 2. - Server - We'll be using the IP address 172.16.10.2 - 3. - Path - Well define /primary as the path we are using - - - Secondary Storage5.4.2. Secondary Storage - If this is a new zone, you'll be prompted for secondary storage information - populate it as follows: - 1. - NFS server - We'll use the IP address 172.16.10.2 - 2. - Path - We'll use /secondary - - - - Now, click Launch and your cloud should begin setup - it may take several minutes depending on your internet connection speed for setup to finalize. - Appendix A. Revision HistoryAppendix A. Revision History - Revision 0-0Mon Jun 25 2012 - Initial creation of book by publican - - - - diff --git a/docs/runbook/tmp/en-US/xml/Runbook.xml b/docs/runbook/tmp/en-US/xml/Runbook.xml deleted file mode 100644 index cf200cff74f..00000000000 --- a/docs/runbook/tmp/en-US/xml/Runbook.xml +++ /dev/null @@ -1,33 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml/config.xml b/docs/runbook/tmp/en-US/xml/config.xml deleted file mode 100644 index ce6bf16a2d9..00000000000 --- a/docs/runbook/tmp/en-US/xml/config.xml +++ /dev/null @@ -1,249 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - Configuration - - As we noted before we will be using security groups to provide isolation and by default that implies that we'll be using a flat layer-2 network. It also means that the simplicity of our setup means that we can use the quick installer. - -
- UI Access - - To get access to CloudStack's web interface, merely point your browser to http://172.16.10.2:8080/client The default username is 'admin', and the default password is 'password'. You should see a splash screen that allows you to choose several options for setting up CloudStack. You should choose the option. - - - You should now see a prompt requiring you to change the password for the admin user. Please do so. - - -
- -
- Setting up a Zone - - A zone is the largest organization entity in CloudStack - and we'll be creating one, this should be the screen that you see in front of you now. And for us there are 5 pieces of information that we need. - - - - Name - we will set this to the ever-descriptive 'Zone1' for our cloud. - - - - - - Public DNS 1 - we will set this to '8.8.8.8' for our cloud. - - - - - - Public DNS 2 - we will set this to '8.8.4.4' for our cloud. - - - - - - Internal DNS1 - we will also set this to '8.8.8.8' for our cloud. - - - - - - Internal DNS2 - we will also set this to '8.8.8.4' for our cloud. - - - - - - - - - Notes about DNS settings - - CloudStack distinguishes between internal and public DNS. Internal DNS is assumed to be capable of resolving internal-only hostnames, such as your NFS server’s DNS name. Public DNS is provided to the guest VMs to resolve public IP addresses. You can enter the same DNS server for both types, but if you do so, you must make sure that both internal and public IP addresses can route to the DNS server. In our specific case we will not use any names for resources internally, and we have indeed them set to look to the same external resource so as to not add a namerserver setup to our list of requirements. - - - - -
- -
- Pod Configuration - - Now that we've added a Zone, the next step that comes up is a prompt for information regading a pod. Which is looking for 4 items. - - - - Name - We'll use Pod1 for our cloud. - - - - - - Gateway - We'll use 172.16.10.1 as our gateway - - - - - - Netmask - We'll use 255.255.255.0 - - - - - - Start/end reserved system IPs - we will use 172.16.10.10-172.16.10.20 - - - - - - Guest gateway - We'll use 172.16.10.1 - - - - - - Guest netmask - We'll use 255.255.255.0 - - - - - - Guest start/end IP - We'll use 172.16.10.30-172.16.10.200 - - - - - - - - -
- -
- Cluster - - Now that we've added a Zone, we need only add a few more items for configuring the cluster. - - - - Name - We'll use Cluster1 - - - - - - Hypervisor - Choose KVM - - - - - - - - - You should be prompted to add the first host to your cluster at this point. Only a few bits of information are needed. - - - - Hostname - we'll use the IP address 172.16.10.2 since we didn't set up a DNS server. - - - - - - Username - we'll use 'root' - - - - - - Password - enter the operating system password for the root user - - - - - - - -
- Primary Storage - - With you cluster now setup - you should be prompted for primary storage information. Choose NFS as the storage type and then enter the following values in the fields: - - - - Name - We'll use 'Primary1' - - - - - - Server - We'll be using the IP address 172.16.10.2 - - - - - - Path - Well define /primary as the path we are using - - - - - - - - -
- -
- Secondary Storage - - If this is a new zone, you'll be prompted for secondary storage information - populate it as follows: - - - - NFS server - We'll use the IP address 172.16.10.2 - - - - - - Path - We'll use /secondary - - - - - - - - - Now, click Launch and your cloud should begin setup - it may take several minutes depending on your internet connection speed for setup to finalize. - - -
- - -
- - - - diff --git a/docs/runbook/tmp/en-US/xml/kvm.xml b/docs/runbook/tmp/en-US/xml/kvm.xml deleted file mode 100644 index b60e3537ad4..00000000000 --- a/docs/runbook/tmp/en-US/xml/kvm.xml +++ /dev/null @@ -1,97 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - KVM Setup and installation - - KVM is the hypervisor we'll be using - we will recover the initial setup which has already been done on the hypervisor host and cover installation of the agent software, you can use the same steps to add additional KVM nodes to your CloudStack environment. - -
- Prerequisites - - We explicitly are using the management server as a compute node as well, which means that we have already performed many of the prerequisite steps when setting up the management server, but we will list them here for clarity. Those steps are: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - You shouldn't need to do that for the management server, of course, but any additional hosts will need for you to complete the above steps. - - -
- -
- Installation - - You'll need to ensure that you are in the directory that was created when we extracted the the tarball. - - - You'll be running ./install.sh again and this time choosing which will install the software necessary for managing a KVM node. - - -
- -
- KVM Configuration - - KVM configuration is relatively simple at only a single item. We need to edit the QEMU VNC configuration. This is done by editing /etc/libvirt/qemu.conf and ensuring the following line is present and uncommented. -vnc_listen=0.0.0.0 - - - - You can now just restart the libvirt daemon by issuing the following command: -# service libvirt restart - - - - That concludes our installation and configuration of KVM, and we'll now move to using the CloudStack UI for the actual configuration of our cloud. - - -
- - - - diff --git a/docs/runbook/tmp/en-US/xml_tmp/Author_Group.xml b/docs/runbook/tmp/en-US/xml_tmp/Author_Group.xml deleted file mode 100644 index ba9e651f876..00000000000 --- a/docs/runbook/tmp/en-US/xml_tmp/Author_Group.xml +++ /dev/null @@ -1,32 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - - Apache - CloudStack - - - diff --git a/docs/runbook/tmp/en-US/xml_tmp/Book_Info.xml b/docs/runbook/tmp/en-US/xml_tmp/Book_Info.xml deleted file mode 100644 index ec591446856..00000000000 --- a/docs/runbook/tmp/en-US/xml_tmp/Book_Info.xml +++ /dev/null @@ -1,52 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - Runbook - Prescriptive instructions for deploying Apache CloudStack - Apache CloudStack - 3.0.2 - 0 - 0 - - - These runbooks are designed to provide a strict environment to guarantee - a higher degree of success in initial deployments of Apache CloudStack. - All of the elements of the environment will be provided to you. - Apache CloudStack is capable of much more complex configurations, - but they are beyond the scope of this document. - - - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml_tmp/Chapter.xml b/docs/runbook/tmp/en-US/xml_tmp/Chapter.xml deleted file mode 100644 index 4adf63c207a..00000000000 --- a/docs/runbook/tmp/en-US/xml_tmp/Chapter.xml +++ /dev/null @@ -1,53 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - Test Chapter - - This is a test paragraph - -
- Test Section 1 - - This is a test paragraph in a section - -
- -
- Test Section 2 - - This is a test paragraph in Section 2 - - - - listitem text - - - - -
- - - diff --git a/docs/runbook/tmp/en-US/xml_tmp/Environment.xml b/docs/runbook/tmp/en-US/xml_tmp/Environment.xml deleted file mode 100644 index 781e05de182..00000000000 --- a/docs/runbook/tmp/en-US/xml_tmp/Environment.xml +++ /dev/null @@ -1,235 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - Environment - - Before you begin, you need to prepare the environment before you install CloudStack. - We will go over the steps to prepare now. - -
- Operating System - - Using the CentOS 6.2 x86_64 minimal install ISO, you'll need to install CentOS - on your hardware. The defaults will generally be acceptable for this installation. - - - Once this installation is complete, you'll want to connect to your freshly - installed machine via SSH as the root user. Note that you should not allow root - logins in a production environment, so be sure to turn off remote logins once you - have finished the installation and configuration. - -
- Configuring the network - - By default the network will not come up on your hardware and you - will need to configure it to work in your environment. Since we - specified that there will be no DHCP server in this environment - we will be manually configuring your network interface. We will - assume, for the purposes of this exercise, that eth0 is the only network - interface that will be connected and used. - - - Connecting via the console you should login as root. Check the - file /etc/sysconfig/network-scripts/ifcfg-eth0, - it will look like this by default: - -DEVICE="eth0" -HWADDR="52:54:00:B9:A6:C0" -NM_CONTROLLED="yes" -ONBOOT="no" - - - - Unfortunately, this configuration will not permit you to connect to the network, - and is also unsuitable for our purposes with CloudStack. We want to - configure that file so that it specifies the IP address, netmask, etc., as shown - in the following example: - - - Hardware Addresses - You should not use the hardware address (aka MAC address) from our example - for your configuration. It is network interface specific, so you should keep the - address already provided in the HWADDR directive. - - - -DEVICE=eth0 -HWADDR=52:54:00:B9:A6:C0 -NM_CONTROLLED=no -ONBOOT=yes -BOOTPROTO=none -IPADDR=172.16.10.2 -NETMASK=255.255.255.0 -GATEWAY=172.16.10.1 -DNS1=8.8.8.8 -DNS2=8.8.4.4 - - - IP Addressing - Throughout this document we are assuming that you will - have a /24 network for your CloudStack implementation. This can be any - RFC 1918 network. However, we are assuming that you will match the - machine address that we are using. Thus we may use - 172.16.10.2 and because - you might be using the 192.168.55.0/24 network you would use - 192.168.55.2 - - - Now that we have the configuration files properly set up, we need to run a - few commands to start up the network - # chkconfig network on - # service network start -
-
- Hostname - - Cloudstack requires that the hostname be properly set. If you used the default - options in the installation, then your hostname is currently set to - localhost.localdomain. To test this we will run: - # hostname --fqdn - At this point it will likely return: - localhost - To rectify this situation - we'll set the hostname by editing the - /etc/hosts file so that it follows a similar format to this example: -127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 -172.16.10.2 srvr1.cloud.priv - - - After you've modified that file, go ahead and restart the network using: -# service network restart - Now recheck with the hostname --fqdn command and ensure that it returns - a FQDN response -
-
- SELinux - At the moment, for CloudStack to work properly SELinux must be - set to permissive. We want to both configure this for future boots and modify it - in the current running system. - - To configure SELinux to be permissive in the running system we need to run - the following command: - # setenforce 0 - - To ensure that it remains in that state we need to configure the file - /etc/selinux/config to reflect the permissive state, - as shown in this example: - - -# This file controls the state of SELinux on the system. -# SELINUX= can take one of these three values: -# enforcing - SELinux security policy is enforced. -# permissive - SELinux prints warnings instead of enforcing. -# disabled - No SELinux policy is loaded. -SELINUX=permissive -# SELINUXTYPE= can take one of these two values: -# targeted - Targeted processes are protected, -# mls - Multi Level Security protection. -SELINUXTYPE=targeted - - -
-
- NTP - NTP configuration is a necessity for keeping all of the clocks in your cloud - servers in sync. However, NTP is not installed by default. So we'll install and - and configure NTP at this stage. Installation is accomplished as follows: - - # yum install ntp - The actual default configuration is fine for our purposes, so we merely need to - enable it and set it to start on boot as follows: - # chkconfig ntpd on - # service ntpd start -
-
-
- NFS - - Our configuration is going to use NFS for both primary and secondary - storage. We are going to go ahead and setup two NFS shares for those - purposes. We'll start out by installing - nfs-utils. - - # yum install nfs-utils - - We now need to configure NFS to serve up two different shares. This is handled comparatively easily - in the /etc/exports file. You should ensure that it has the following content: - - -/secondary *(rw,async,no_root_squash) -/primary *(rw,async,no_root_squash) - - - You will note that we specified two directories that don't exist (yet) on the system. - We'll go ahead and create those directories and set permissions appropriately on them with the following commands: - - -# mkdir /primary -# mkdir /secondary - - CentOS 6.x releases use NFSv4 by default. NFSv4 requires that domain setting matches on all clients. - In our case, the domain is cloud.priv, so ensure that the domain setting in /etc/idmapd.conf - is uncommented and set as follows: - Domain = cloud.priv - Now you'll need uncomment the configuration values in the file /etc/sysconfig/nfs - -LOCKD_TCPPORT=32803 -LOCKD_UDPPORT=32769 -MOUNTD_PORT=892 -RQUOTAD_PORT=875 -STATD_PORT=662 -STATD_OUTGOING_PORT=2020 - - Now we need to configure the firewall to permit incoming NFS connections. - Edit the file /etc/sysconfig/iptables - - --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 111 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 111 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 2049 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 32803 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 32769 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 892 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 892 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 875 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 875 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 662 -j ACCEPT --A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 662 -j ACCEPT - - Now you can restart the iptables service with the following command: - - # service iptables restart - We now need to configure nfs service to start on boot and actually start it on the host by - executing the following commands: - - # service rpcbind start - # service nfs start - # chkconfig rpcbind on - # chkconfig nfs on - -
- - - diff --git a/docs/runbook/tmp/en-US/xml_tmp/Management.xml b/docs/runbook/tmp/en-US/xml_tmp/Management.xml deleted file mode 100644 index 0df2bf118f9..00000000000 --- a/docs/runbook/tmp/en-US/xml_tmp/Management.xml +++ /dev/null @@ -1,127 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - Installation of the management server - - Now it is time to start installing CloudStack's management server - and some of the related components. - -
- Database Installation and Configuration - - We'll start out by installing MySQL and configuring - some options to ensure CloudStack runs well. - - - To install MySQL run the following command: - # yum -y install mysql-server - - With MySQL installed we need to make - a few configuration changes to /etc/my.cnf. - Specifically we need to add the following options to the [mysqld] section: - -innodb_rollback_on_timeout=1 -innodb_lock_wait_timeout=600 -max_connections=350 -log-bin=mysql-bin -binlog-format = 'ROW' - - - - Now that MySQL is properly configured we can - start it and configure it to start on boot as follows: - - # service mysqld start - # chkconfig mysqld on - - - -
- -
- Extraction - - The next step is to extract the contents of the CloudStack tarball - (mentioned in ) you - downloaded previously. To extract the contents of this tarball use - the following command: - - - # tar -xzvf CloudStack-oss-3.0.2-1-rhel6.2.tar.gz - - For the next few sections you'll need to cd into the first level that was just created. - -
-
- Installation - Now that you are in the directory created by extracting the tarball, it's now time to install. We'll run - ./install.sh and choose option . This will install the management server - and necessary dependencies. - - With the application itself installed we can now setup the database, we'll do that with the following command - and options: - - - # cloud-setup-databases cloud:password@localhost --deploy-as=root - - When this process is finished, you should see a message like "CloudStack has successfully initialized the database." - - Now that the database has been created, we can take the final step in setting up the management server by issuing the following command: - - # cloud-setup-mangament - -
-
- System Template Setup - CloudStack uses a number of system VMs to provide functionality for - accessing the console of virtual machines, providing various networking - services, and managing various aspects of storage. This step will - acquire those system images ready for deployment when we bootstrap - your cloud. - - - The place we are going to download these images to is the secondary - storage share that we setup earlier, so we'll need to mount that share - with the mount command run on the management server: - - - # mount -t nfs 172.16.10.2:/secondary /mnt/secondary - - - Now we need to download the system VM template and deploy that to the - share we just mounted. The management server includes a script to properly - manipulate the system VMs images. - - - # /usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -F - - - That concludes our setup of the management server. We still need to - configure CloudStack, but we will do that after we get our hypervisor - set up. - -
- diff --git a/docs/runbook/tmp/en-US/xml_tmp/Overview.xml b/docs/runbook/tmp/en-US/xml_tmp/Overview.xml deleted file mode 100644 index f69798fdb67..00000000000 --- a/docs/runbook/tmp/en-US/xml_tmp/Overview.xml +++ /dev/null @@ -1,100 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - Overview - - Infrastructure-as-a-Service (IaaS) clouds can be a complex thing to build, - and by definition they have a plethora of options, which often lead to confusion - for even experienced admins who are newcomers to building cloud platforms. - The goal for this runbook is to provide a straightforward set of instructions - to get you up and running with CloudStack with a minimum amount of trouble. - -
- What exactly are we building? - - This runbook will focus on building a CloudStack cloud using KVM with - CentOS 6.2 with NFS storage on a flat layer-2 network utilizing - layer-3 network isolation (aka Security Groups), and doing it all - on a single piece of hardware. - - - KVM, or Kernel-based Virtual Machine is a virtualization technology - for the Linux kernel. KVM supports native virtualization atop - processors with hardware virtualization extensions. - - - Security Groups act as distributed firewalls that control access - to a group of virtual machines. - -
-
- High level overview of the process - - Before we actually get to installing CloudStack, we'll start with - installing our base operating system, and then configuring that to act - as an NFS server for several types of storage. We'll install the - management server, download the systemVMs, and finally install the agent - software. Finally we'll spend a good deal of time configuring the entire - cloud in the CloudStack web interface. - -
-
- Prerequisites - - To complete this runbook you'll need the following items: - - - - At least one computer which supports hardware virtualization. - - - - - The - - CentOS 6.2 x86_64 minimal install CD - - - - - - A /24 network with the gateway being at xxx.xxx.xxx.1, no DHCP should be on this network and - none of the computers running CloudStack may have a dynamic address. - - - - - Copy of - - CloudStack 3.0.2 for RHEL and CentOS 6.2 - - - - - -
- - diff --git a/docs/runbook/tmp/en-US/xml_tmp/Preface.xml b/docs/runbook/tmp/en-US/xml_tmp/Preface.xml deleted file mode 100644 index 7a622674443..00000000000 --- a/docs/runbook/tmp/en-US/xml_tmp/Preface.xml +++ /dev/null @@ -1,33 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - Preface - - - - - - diff --git a/docs/runbook/tmp/en-US/xml_tmp/Revision_History.xml b/docs/runbook/tmp/en-US/xml_tmp/Revision_History.xml deleted file mode 100644 index 4aecafd1d66..00000000000 --- a/docs/runbook/tmp/en-US/xml_tmp/Revision_History.xml +++ /dev/null @@ -1,42 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - Revision History - - - - 0-0 - Mon Jun 25 2012 - - - Initial creation of book by publican - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml_tmp/Runbook.ent b/docs/runbook/tmp/en-US/xml_tmp/Runbook.ent deleted file mode 100644 index cdc00b05f62..00000000000 --- a/docs/runbook/tmp/en-US/xml_tmp/Runbook.ent +++ /dev/null @@ -1,22 +0,0 @@ - - - - - - diff --git a/docs/runbook/tmp/en-US/xml_tmp/Runbook.xml b/docs/runbook/tmp/en-US/xml_tmp/Runbook.xml deleted file mode 100644 index 11f195ca828..00000000000 --- a/docs/runbook/tmp/en-US/xml_tmp/Runbook.xml +++ /dev/null @@ -1,37 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - - - - - - - - - - - diff --git a/docs/runbook/tmp/en-US/xml_tmp/config.xml b/docs/runbook/tmp/en-US/xml_tmp/config.xml deleted file mode 100644 index 90c34957fb1..00000000000 --- a/docs/runbook/tmp/en-US/xml_tmp/config.xml +++ /dev/null @@ -1,177 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - Configuration - - As we noted before we will be using security groups to provide isolation - and by default that implies that we'll be using a flat layer-2 network. - It also means that the simplicity of our setup means that we can use the - quick installer. - -
- UI Access - - To get access to CloudStack's web interface, merely point your - browser to http://172.16.10.2:8080/client - The default username is 'admin', and the default password is 'password'. - You should see a splash screen that allows you to choose several options - for setting up CloudStack. You should choose the - option. - - - You should now see a prompt requiring you to change the password for - the admin user. Please do so. - -
-
- Setting up a Zone - - A zone is the largest organization entity in CloudStack - and we'll be creating one, this - should be the screen that you see in front of you now. And for us there are 5 pieces of - information that we need. - - - Name - we will set this to the ever-descriptive 'Zone1' for our cloud. - - - Public DNS 1 - we will set this to '8.8.8.8' for our cloud. - - - Public DNS 2 - we will set this to '8.8.4.4' for our cloud. - - - Internal DNS1 - we will also set this to '8.8.8.8' for our cloud. - - - Internal DNS2 - we will also set this to '8.8.8.4' for our cloud. - - - - - Notes about DNS settings - - CloudStack distinguishes between internal and public DNS. Internal - DNS is assumed to be capable of resolving internal-only - hostnames, such as your NFS server’s DNS name. Public DNS is - provided to the guest VMs to resolve public IP addresses. You can - enter the same DNS server for both types, but if you do so, you - must make sure that both internal and public IP addresses can - route to the DNS server. In our specific case we will not use any - names for resources internally, and we have indeed them set to look - to the same external resource so as to not add a namerserver setup - to our list of requirements. - - -
-
- Pod Configuration - Now that we've added a Zone, the next step that comes up is a prompt - for information regading a pod. Which is looking for 4 items. - - - Name - We'll use Pod1 for our cloud. - - - Gateway - We'll use 172.16.10.1 as our gateway - - - Netmask - We'll use 255.255.255.0 - - - Start/end reserved system IPs - we will use 172.16.10.10-172.16.10.20 - - - Guest gateway - We'll use 172.16.10.1 - - - Guest netmask - We'll use 255.255.255.0 - - - Guest start/end IP - We'll use 172.16.10.30-172.16.10.200 - - - -
-
- Cluster - Now that we've added a Zone, we need only add a few more items for configuring the cluster. - - - Name - We'll use Cluster1 - - - Hypervisor - Choose KVM - - - - You should be prompted to add the first host to your cluster at this point. Only a few bits of information are needed. - - - Hostname - we'll use the IP address 172.16.10.2 since we didn't set up a DNS server. - - - Username - we'll use 'root' - - - Password - enter the operating system password for the root user - - - -
- Primary Storage - With you cluster now setup - you should be prompted for primary storage information. Choose NFS as the storage type and then enter the following values in the fields: - - - Name - We'll use 'Primary1' - - - Server - We'll be using the IP address 172.16.10.2 - - - Path - Well define /primary as the path we are using - - - -
-
- Secondary Storage - If this is a new zone, you'll be prompted for secondary storage information - populate it as follows: - - - NFS server - We'll use the IP address 172.16.10.2 - - - Path - We'll use /secondary - - - - Now, click Launch and your cloud should begin setup - it may take several minutes depending on your internet connection speed for setup to finalize. -
-
- - - - diff --git a/docs/runbook/tmp/en-US/xml_tmp/kvm.xml b/docs/runbook/tmp/en-US/xml_tmp/kvm.xml deleted file mode 100644 index 03119496a2c..00000000000 --- a/docs/runbook/tmp/en-US/xml_tmp/kvm.xml +++ /dev/null @@ -1,103 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - KVM Setup and installation - - KVM is the hypervisor we'll be using - we will recover the initial setup - which has already been done on the hypervisor host and cover installation - of the agent software, you can use the same steps to add additional KVM - nodes to your CloudStack environment. - -
- Prerequisites - - We explicitly are using the management server as a compute node as well, - which means that we have already performed many of the prerequisite steps - when setting up the management server, but we will list them here for - clarity. Those steps are: - - - - - - - - - - - - - - - - - - - - - - - - - You shouldn't need to do that for the management server, of course, but - any additional hosts will need for you to complete the above steps. - -
- -
- Installation - - You'll need to ensure that you are in the directory that was created when - we extracted the the tarball. - - - - You'll be running ./install.sh again and this time - choosing which will install the software necessary for - managing a KVM node. - -
-
- KVM Configuration - - KVM configuration is relatively simple at only a single item. We need to - edit the QEMU VNC configuration. This is done by editing - /etc/libvirt/qemu.conf and ensuring the following - line is present and uncommented. - vnc_listen=0.0.0.0 - - - You can now just restart the libvirt daemon by issuing the following command: - # service libvirt restart - - - That concludes our installation and configuration of KVM, and we'll now move to using the CloudStack UI - for the actual configuration of our cloud. - -
- - -