modified conf.py, reorganized the html output
This commit is contained in:
svetlana
parent
330dc45f5c
commit
f990fc33a5
|
|
@ -1,189 +0,0 @@
|
|||
{#
|
||||
mirantis/layout.html
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
Sphinx layout template for the Mirantis cloud theme.
|
||||
|
||||
:copyright: Copyright 2009-2011 Assurance Technologies LLC
|
||||
:license: BSD
|
||||
|
||||
:copyright: Copyright 2013, Mirantis Inc.
|
||||
:license: APL v2
|
||||
|
||||
roottarget - optional target for root link (default to toc)
|
||||
logotarget - optional target for logo link (defaults to root target)
|
||||
googleanalytics_id - if set, enabled google analytics snippet & footer
|
||||
googleanalytics_path - optional subpatch for GA cookie
|
||||
collapsiblesidebar - enable collapsible sidebar support
|
||||
|
||||
#}
|
||||
|
||||
{% extends "cloud/layout.html" %}
|
||||
|
||||
{%- block sidebarlogo %}
|
||||
{%- if logo %}
|
||||
<p class="logo"><a href="{{ pathto(theme_logotarget) }}">
|
||||
<img class="logo" src="{{ pathto('_static/' + logo, 1) }}" alt="Logo"/>
|
||||
</a><br>Version {{ version }}
|
||||
|
||||
</p>
|
||||
{%- endif %}
|
||||
{%- endblock %}
|
||||
|
||||
{%- block relbar1 %}
|
||||
<div class="relbar-top">
|
||||
<div class="related_hf">
|
||||
<div id="header">
|
||||
<div id="header_content">
|
||||
|
||||
<table class="pageheader" cellpadding="0" cellspacing="0">
|
||||
<tbody><tr>
|
||||
<td width="167px" height="107px"><a href="http://www.mirantis.com/" title="Mirantis"><img src="http://fuel.mirantis.com/wp-content/themes/carrington-jam-1.4/img/logo.gif" alt="Fuel" border="0"></a></td>
|
||||
<td>
|
||||
<div id="top-menu">
|
||||
<div id="enhancedtextwidget-2" class="widget widget_text"><!--Top menu--> <div class="textwidget"><table align="right">
|
||||
<tbody><tr><td>
|
||||
<div id="ttopmenu"><a class="top" href="http://www.mirantis.com/blog/">Blog</a> <a class="top" href="http://www.mirantis.com/careers/">Careers</a> <a class="top" href="http://fuel.mirantis.com/contact/">Contact Us</a></div>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody></table></div>
|
||||
<div class="clear"></div></div> </div><!--#top-menu-->
|
||||
<div id="main-menu">
|
||||
<div id="text-5" class="widget widget_text"><!--Main menu--> <div class="textwidget"><div id="main-menu">
|
||||
<div class="widget widget_text" id="text-28">
|
||||
<div id="masthead">
|
||||
<div id="globalNav">
|
||||
<div id="globalLink">
|
||||
<a name="gl0" class="glink" id="gl0" href="http://www.mirantis.com/openstack-services/">OpenStack Services</a>
|
||||
<a name="gl1" class="glink" id="gl1" href="http://www.mirantis.com/training/">Training</a>
|
||||
<a name="gl2" class="glink" id="gl2" href="http://fuel.mirantis.com/" style="color:#D3301A;">Fuel for OpenStack</a>
|
||||
<a name="gl3" class="glink" id="gl3" href="http://www.mirantis.com/openstack-use-cases/">Use Cases</a>
|
||||
<a name="gl4" class="glink" id="gl4" href="http://www.mirantis.com/why-mirantis/">Why Mirantis</a>
|
||||
<a name="gl5" class="glink" id="gl5" href="http://www.mirantis.com/company/">Company</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div></div>
|
||||
<div class="clear"></div></div><div id="enhancedtextwidget-9" class="widget widget_text">
|
||||
<!--#main-menu-->
|
||||
</td>
|
||||
</tr>
|
||||
</tbody></table>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
{{ relbar() }}
|
||||
</div>
|
||||
{% endblock %}
|
||||
|
||||
{% block extrahead_ -%}
|
||||
{{ super() }}
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
{%- if theme_googleanalytics_id -%}
|
||||
<script type="text/javascript">
|
||||
var ga_enabled = !$.cookie('disable-ga');
|
||||
if(ga_enabled){
|
||||
var _gaq = _gaq || [];
|
||||
_gaq.push(['_setAccount', '{{ theme_googleanalytics_id }}']);
|
||||
|
||||
_gaq.push(['_setCookiePath', '{{ theme_googleanalytics_path }}']);
|
||||
_gaq.push(['_setDomainName', 'mirantis.com']);
|
||||
_gaq.push(['_setDetectFlash', false]);
|
||||
_gaq.push(['_trackPageview']);
|
||||
(function() {
|
||||
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
|
||||
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
|
||||
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
|
||||
})();
|
||||
}
|
||||
</script>
|
||||
{%- endif %}
|
||||
{%- endblock %}
|
||||
|
||||
{%- block relbar2 %}
|
||||
<div class="relbar-bottom">
|
||||
{{ relbar() }}
|
||||
|
||||
<div id="disqus_thread"></div>
|
||||
<script type="text/javascript">
|
||||
/* * * CONFIGURATION VARIABLES: EDIT BEFORE PASTING INTO YOUR WEBPAGE * * */
|
||||
var disqus_shortname = 'fuel-docs'; // required: replace example with your forum shortname
|
||||
|
||||
/* * * DON'T EDIT BELOW THIS LINE * * */
|
||||
(function() {
|
||||
var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
|
||||
dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';
|
||||
(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
|
||||
})();
|
||||
</script>
|
||||
<noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
|
||||
<a href="http://disqus.com" class="dsq-brlink">comments powered by <span class="logo-disqus">Disqus</span></a>
|
||||
|
||||
|
||||
<div class="related_hf">
|
||||
<div id="footer">
|
||||
<div id="footer_content">
|
||||
<div id="text-2" class="widget widget_text"><!--Footer--> <div class="textwidget"><table width="100%" border="0" cellpadding="0" cellspacing="0" id="foottable">
|
||||
<tbody><tr>
|
||||
<td valign="top">
|
||||
<span class="fgeneral">Mirantis Inc.<br>
|
||||
<span class="fslogan">OpenStack Clouds. Delivered.</span></span>
|
||||
</td>
|
||||
<td valign="top">
|
||||
<span class="fgeneral">© 2005–2013</span> <span class="fgeneralblue">All Rights Reserved</span>
|
||||
</td>
|
||||
<td valign="top">
|
||||
<div id="fbox">
|
||||
<span class="fgeneral">615 National Ave, Suite 100<br>
|
||||
Mountain View, CA 94043</span></div>
|
||||
</td>
|
||||
<td valign="top">
|
||||
<div id="fbox">
|
||||
<span class="fgeneralblue">Phone</span> <span class="fgeneral">650-963-9828</span>
|
||||
<br>
|
||||
<span class="fgeneralblue">Fax</span> <span class="fgeneral">650-968-2997</span>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody></table>
|
||||
</div>
|
||||
<div class="clear"></div></div><div id="text-12" class="widget widget_text"><!--Footer_CC-->
|
||||
<div class="clear"></div></div><div id="DNSindicator"></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<!-- Yandex.Metrika counter -->
|
||||
<script type="text/javascript">
|
||||
(function (d, w, c) {
|
||||
(w[c] = w[c] || []).push(function() {
|
||||
try {
|
||||
w.yaCounter20556736 = new Ya.Metrika({id:20556736,
|
||||
clickmap:true,
|
||||
trackLinks:true,
|
||||
accurateTrackBounce:true,
|
||||
ut:"noindex"});
|
||||
} catch(e) { }
|
||||
});
|
||||
|
||||
var n = d.getElementsByTagName("script")[0],
|
||||
s = d.createElement("script"),
|
||||
f = function () { n.parentNode.insertBefore(s, n); };
|
||||
s.type = "text/javascript";
|
||||
s.async = true;
|
||||
s.src = (d.location.protocol == "https:" ? "https:" : "http:") + "//mc.yandex.ru/metrika/watch.js";
|
||||
|
||||
if (w.opera == "[object Opera]") {
|
||||
d.addEventListener("DOMContentLoaded", f, false);
|
||||
} else { f(); }
|
||||
})(document, window, "yandex_metrika_callbacks");
|
||||
</script>
|
||||
<noscript><div><img src="//mc.yandex.ru/watch/20556736?ut=noindex" style="position:absolute; left:-9999px;" alt="" /></div></noscript>
|
||||
<!-- /Yandex.Metrika counter -->
|
||||
|
||||
</div>
|
||||
</div>
|
||||
{% endblock %}
|
||||
|
||||
9
conf.py
9
conf.py
|
|
@ -47,7 +47,7 @@ source_suffix = '.rst'
|
|||
#source_encoding = 'utf-8-sig'
|
||||
|
||||
# The master toctree document.
|
||||
master_doc = 'contents'
|
||||
# master_doc = 'contents'
|
||||
|
||||
# General information about the project.
|
||||
project = u'Fuel for OpenStack'
|
||||
|
|
@ -148,7 +148,7 @@ html_use_smartypants = False
|
|||
|
||||
# Custom sidebar templates, maps document names to template names.
|
||||
html_sidebars = {
|
||||
'**': ['searchbox.html', 'globaltoc.html', 'doc_license.html'],
|
||||
'**': ['searchbox.html', 'globaltoc.html', 'doc_license.html', 'relations.html'],
|
||||
}
|
||||
|
||||
# Additional templates that should be rendered to pages, maps page names to
|
||||
|
|
@ -203,6 +203,8 @@ latex_elements = {
|
|||
latex_documents = [
|
||||
('index', 'fuel.tex', u'Fuel for OpenStack | Documentation',
|
||||
u'Mirantis Inc.', 'manual'),
|
||||
('install', 'install.tex', u'Fuel Installation Guide | Documentation',
|
||||
u'Mirantis Inc.', 'manual'),
|
||||
]
|
||||
|
||||
# The name of an image file (relative to this directory) to place at the top of
|
||||
|
|
@ -282,7 +284,8 @@ nwdiag_antialias = True
|
|||
extensions += ['rst2pdf.pdfbuilder']
|
||||
pdf_documents = [
|
||||
('pdf_index', u'Fuel-for-OpenStack-3.1-UserGuide', u'User Guide',
|
||||
u'2013, Mirantis Inc.')
|
||||
u'2013, Mirantis Inc.'),
|
||||
('pdf_install', u'Fuel-for-Openstack-3.1-InstallGuide', u'Installation Guide', u'2013, Mirantis, Inc.')
|
||||
# (master_doc, project, project, copyright),
|
||||
]
|
||||
pdf_stylesheets = ['letter', 'mirantis']
|
||||
|
|
|
|||
15
contents.rst
15
contents.rst
|
|
@ -1,16 +1,13 @@
|
|||
.. index Table of Contents
|
||||
.. index Documentation
|
||||
|
||||
.. _ToC:
|
||||
.. _Documentation:
|
||||
|
||||
.. toctree:: Table of Contents
|
||||
.. toctree:: Documentation
|
||||
:maxdepth: 2
|
||||
|
||||
index
|
||||
about-fuel
|
||||
release-notes
|
||||
install-guide
|
||||
user-guide
|
||||
reference-architecture
|
||||
production-considerations
|
||||
installation-fuel-ui
|
||||
installation-fuel-cli
|
||||
release-notes
|
||||
frequently-asked-questions
|
||||
copyright
|
||||
|
|
|
|||
|
|
@ -0,0 +1,18 @@
|
|||
..index:: copyright_page
|
||||
|
||||
©2013 Mirantis, Inc. All rights reserved.
|
||||
|
||||
This product is protected by U.S. and international copyright and
|
||||
intellectual property laws. No part of this publication may be
|
||||
reproduced in any written, electronic, recording, or photocopying
|
||||
form without written permission of Mirantis, Inc.
|
||||
|
||||
Mirantis, Inc. reserves the right to modify the content of this
|
||||
document at any time without prior notice. Functionality described
|
||||
in the document may not be available at the moment. The document
|
||||
contains the latest information at the time of publication.
|
||||
|
||||
Mirantis, Inc. and the Mirantis Logo are trademarks of Mirantis, Inc.
|
||||
and/or its affiliates in the United States an other countries.
|
||||
Third party trademarks, service marks, and names mentioned in this
|
||||
document are the properties of their respective owners.
|
||||
|
|
@ -1,9 +1,9 @@
|
|||
.. index:: FAQ (Frequently Asked Questions)
|
||||
.. index:: F.A.Q.
|
||||
|
||||
.. _FAQ:
|
||||
.. _F.A.Q.:
|
||||
|
||||
===========================================
|
||||
FAQ (Frequently Asked Questions) and HowTos
|
||||
F.A.Q
|
||||
===========================================
|
||||
|
||||
.. contents:: :local:
|
||||
|
|
|
|||
98
index.rst
98
index.rst
|
|
@ -1,82 +1,40 @@
|
|||
.. index:: Introduction
|
||||
.. index:: Home page
|
||||
|
||||
.. _Introduction:
|
||||
.. _Homepage:
|
||||
|
||||
===============================
|
||||
Introducing Fuel™ for OpenStack
|
||||
Welcome to Fuel™ Documentation
|
||||
===============================
|
||||
|
||||
OpenStack is an extensible, versatile, and flexible cloud management
|
||||
platform. By exposing its portfolio of cloud infrastructure services –
|
||||
compute, storage, networking and other core resources — through ReST APIs,
|
||||
OpenStack enables a wide range of control over these services, both from the
|
||||
perspective of an integrated Infrastructure as a Service (IaaS) controlled
|
||||
by applications, as well as automated manipulation of the infrastructure
|
||||
itself.
|
||||
This page contains the most recent Fuel documentation.
|
||||
Select a document from the left menu and navigate through the topics.
|
||||
|
||||
This architectural flexibility doesn’t set itself up magically. It asks you,
|
||||
the user and cloud administrator, to organize and manage an extensive array
|
||||
of configuration options. Consequently, getting the most out of your
|
||||
OpenStack cloud over time – in terms of flexibility, scalability, and
|
||||
manageability – requires a thoughtful combination of complex configuration
|
||||
choices. This can be very time consuming and requires that you become
|
||||
familiar with a lot of documentation from a number of different projects.
|
||||
PDFs
|
||||
---------
|
||||
The following Fuel documentation is available in PDF:
|
||||
|
||||
Mirantis Fuel™ for OpenStack was created to eliminate exactly these problems.
|
||||
This step-by-step guide takes you through this process of:
|
||||
* Installation Guide
|
||||
|
||||
This document describes how to install pre-configure your
|
||||
OpenStack environment and install the Fuel Master Node.
|
||||
|
||||
* User Guide
|
||||
|
||||
This document describes how to deploy compute nodes for Fuel.
|
||||
|
||||
* Configuring OpenStack and its supporting components into a robust cloud
|
||||
architecture
|
||||
* Deploying that architecture through an effective, well-integrated automation
|
||||
package that sets up and maintains the components and their configurations
|
||||
* Providing access to a well-integrated, up-to-date set of components known to
|
||||
work together
|
||||
* Reference Architecture
|
||||
|
||||
A deep dive into the structure of the Fuel OpenStack environment,
|
||||
network considerations, and deployment options.
|
||||
|
||||
Fuel™ for OpenStack can be used to create virtually any OpenStack
|
||||
configuration. To make things easier, the installation includes several
|
||||
pre-defined architectures. For the sake of simplicity, this guide emphasises
|
||||
a single, common reference architecture; the multi-node, high-availability
|
||||
configuration. We begin with an explanation of this architecture, then move
|
||||
on to the details of creating the configuration in a test environment using
|
||||
VirtualBox. Finally, we give you the information you need to know to create
|
||||
this and other OpenStack architectures in a production environment.
|
||||
Download an ISO
|
||||
--------------------------
|
||||
Use the following link to download the latest Fuel ISO:
|
||||
|
||||
This guide assumes that you are familiar with general Linux commands and
|
||||
administration concepts, as well as general networking concepts. You should
|
||||
have some familiarity with grid or virtualization systems such as Amazon Web
|
||||
Services or VMware, as well as OpenStack itself, but you don't need to be an
|
||||
expert.
|
||||
http://fuel.mirantis.com/fuel-overview/
|
||||
|
||||
The Fuel User Guide is organized as follows:
|
||||
Demos and tutorials:
|
||||
--------------------------
|
||||
Watch the Fuel demos:
|
||||
|
||||
* :ref:`About_Fuel`, gives you an
|
||||
overview of Fuel and gives you a general idea of how it works.
|
||||
|
||||
* :ref:`Reference-Architectures`, provides a
|
||||
general look at the components that make up OpenStack.
|
||||
|
||||
* :ref:`Create-Cluster-UI`,
|
||||
takes you step-by-step through the process of creating a high-availability
|
||||
OpenStack cluster using Fuel UI.
|
||||
|
||||
* :ref:`Deploy-Cluster-CLI`,
|
||||
takes you step-by-step through the more advanced process of creating a
|
||||
high-availability OpenStack cluster using the command line and Puppet
|
||||
manifests.
|
||||
|
||||
* :ref:`Production`, looks at the
|
||||
real-world questions and problems involved in creating an OpenStack cluster
|
||||
for production use. We discuss issues such as network layout and hardware
|
||||
requirements, and provide tips and tricks for creating a cluster of up to 100
|
||||
nodes.
|
||||
|
||||
* With the current (3.1) release Fuel UI (aka FuelWeb) and Fuel CLI
|
||||
(aka Fuel Library) are integrated. We encourage all users to use the Fuel
|
||||
UI for installation and configuration. However, the standard Fuel CLI
|
||||
installation process is still available for those who prefer a more
|
||||
detailed approach to deployment. Even with a utility as powerful as Fuel,
|
||||
creating an OpenStack cluster can be complex, and :ref:`FAQ` section covers
|
||||
many of the issues that tend to arise during the process.
|
||||
|
||||
Lets start off by taking a closer look at Fuel itself. We'll start by explaining
|
||||
:ref:`How-Fuel-Works` and then move to the process of installation itself.
|
||||
http://www.youtube.com/watch?v=9YMyvIr0Gsg
|
||||
|
|
@ -0,0 +1,29 @@
|
|||
.. index:: Installation Guide
|
||||
.. _Installation_Guide:
|
||||
|
||||
=====================
|
||||
Installation Guide
|
||||
=====================
|
||||
|
||||
.. contents:: :local:
|
||||
:depth: 2
|
||||
|
||||
.. include:: /pages/preface/preface.rst
|
||||
.. include:: /pages/about-fuel/prerequisites.rst
|
||||
.. include:: /pages/about-fuel/0030-how-it-works.rst
|
||||
.. include:: /pages/about-fuel/0040-reference-topologies.rst
|
||||
.. include:: /pages/about-fuel/0050-supported-software.rst
|
||||
.. include:: /pages/about-fuel/0060-download-fuel.rst
|
||||
.. include:: /pages/production-considerations/0015-sizing-hardware.rst
|
||||
.. include:: /pages/production-considerations/0020-deployment-pipeline.rst
|
||||
.. include:: /pages/production-considerations/0030-large-deployments.rst
|
||||
.. include:: /pages/installation-fuel-ui/install.rst
|
||||
.. include:: /pages/installation-fuel-ui/networks.rst
|
||||
.. include:: /pages/installation-fuel-cli/0000-preamble.rst
|
||||
.. include:: /pages/installation-fuel-cli/0010-introduction.rst
|
||||
.. include:: /pages/installation-fuel-cli/0015-before-you-start.rst
|
||||
.. include:: /pages/installation-fuel-cli/0020-machines.rst
|
||||
.. include:: /pages/installation-fuel-cli/0057-prepare-for-deployment.rst
|
||||
.. include:: /pages/installation-fuel-cli/0060-understand-the-manifest.rst
|
||||
.. include:: /pages/installation-fuel-cli/0070-orchestration.rst
|
||||
.. include:: /pages/installation-fuel-cli/0080-testing-openstack.rst
|
||||
|
|
@ -0,0 +1,49 @@
|
|||
..raw:: pdf
|
||||
|
||||
PageBreak
|
||||
|
||||
..index:: Prerequisites
|
||||
|
||||
Hardware Requirements
|
||||
===========================
|
||||
The amount of hardware depends on your deployment requirements.
|
||||
When you plan your OpenStack environment, consider the following:
|
||||
|
||||
* **CPU**
|
||||
|
||||
Depends on the number of virtual machines that you plan to deploy
|
||||
in your cloud environment and the CPU per virtual machine.
|
||||
See :ref:'Calculating CPU Requirements'
|
||||
|
||||
* **Memory**
|
||||
|
||||
Depends on the amount of RAM assigned per virtual machine and the
|
||||
controller node.
|
||||
|
||||
* **Storage**
|
||||
|
||||
Depends on the local drive space per virtual machine, remote volumes
|
||||
that can be attached to a virtual machine, and object storage.
|
||||
|
||||
* **Networking**
|
||||
|
||||
Depends on the OpenStack architecture, network bandwidth per virtual
|
||||
machine, and network storage.
|
||||
|
||||
Example of Hardware Requirements Calculation
|
||||
-------------------------------------------------
|
||||
When you calculate resources for your OpenStack environment, consider
|
||||
resources required for expanding your environment.
|
||||
|
||||
The example described in this section presumes that your environment
|
||||
has the following prerequisites:
|
||||
|
||||
* 100 virtual machines
|
||||
* 2 x Amazon EC2 compute units 2 GHz average
|
||||
* 16 x Amazon EC2 compute units 16 GHz maximum
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,41 @@
|
|||
.. index:: Introduction
|
||||
|
||||
.. _Introduction:
|
||||
|
||||
Introducing Fuel™ for OpenStack
|
||||
===============================
|
||||
|
||||
OpenStack is an extensible, versatile, and flexible cloud management
|
||||
platform. By exposing its portfolio of cloud infrastructure services –
|
||||
compute, storage, networking and other core resources — through ReST APIs,
|
||||
OpenStack enables a wide range of control over these services, both from the
|
||||
perspective of an integrated Infrastructure as a Service (IaaS) controlled
|
||||
by applications, as well as automated manipulation of the infrastructure
|
||||
itself.
|
||||
|
||||
This architectural flexibility doesn’t set itself up magically. It asks you,
|
||||
the user and cloud administrator, to organize and manage an extensive array
|
||||
of configuration options. Consequently, getting the most out of your
|
||||
OpenStack cloud over time – in terms of flexibility, scalability, and
|
||||
manageability – requires a thoughtful combination of complex configuration
|
||||
choices. This can be very time consuming and requires that you become
|
||||
familiar with a lot of documentation from a number of different projects.
|
||||
|
||||
Mirantis Fuel™ for OpenStack was created to eliminate exactly these problems.
|
||||
This step-by-step guide takes you through this process of:
|
||||
|
||||
* Configuring OpenStack and its supporting components into a robust cloud
|
||||
architecture
|
||||
* Deploying that architecture through an effective, well-integrated automation
|
||||
package that sets up and maintains the components and their configurations
|
||||
* Providing access to a well-integrated, up-to-date set of components known to
|
||||
work together
|
||||
|
||||
Fuel™ for OpenStack can be used to create virtually any OpenStack
|
||||
configuration. To make things easier, the installation includes several
|
||||
pre-defined architectures. For the sake of simplicity, this guide emphasises
|
||||
a single, common reference architecture; the multi-node, high-availability
|
||||
configuration. We begin with an explanation of this architecture, then move
|
||||
on to the details of creating the configuration in a test environment using
|
||||
VirtualBox. Finally, we give you the information you need to know to create
|
||||
this and other OpenStack architectures in a production environment.
|
||||
Binary file not shown.
|
|
@ -0,0 +1,26 @@
|
|||
.. index:: Preface
|
||||
|
||||
.. _Preface:
|
||||
|
||||
Preface
|
||||
=============================
|
||||
|
||||
This documentation provides information on how to use Mirantis Fuel
|
||||
to deploy OpenStack environment. The information is for reference purposes
|
||||
and is subject to change.
|
||||
|
||||
Intended Audience
|
||||
-----------------------------
|
||||
|
||||
This documentation is intended for OpenStack administrators and
|
||||
assumes that you have experience with network and cloud concepts.
|
||||
|
||||
Documentation History
|
||||
-----------------------------
|
||||
The following table lists the released revisions of this documentation:
|
||||
|
||||
+--------------------+----------------------------+
|
||||
|Revision Date |Description |
|
||||
+====================+============================+
|
||||
|September, 2013 |Testing Preface |
|
||||
+--------------------+----------------------------+
|
||||
|
|
@ -0,0 +1,103 @@
|
|||
.. raw:: pdf
|
||||
|
||||
PageBreak
|
||||
|
||||
.. index:: Fuel UI: Network Issues
|
||||
|
||||
Network Issues
|
||||
==============
|
||||
|
||||
Fuel has a built-in capability to run network check before or after OpenStack
|
||||
deployment. Currently it can check connectivity between nodes within
|
||||
configured VLANs on configured server interfaces. Image below shows sample
|
||||
result of such check. By using this simple table it is easy to say which
|
||||
interfaces do not receive certain VLAN IDs. Usually it means that switch or
|
||||
multiple switches are not configured correctly and do not allow certain
|
||||
tagged traffic to pass through.
|
||||
|
||||
.. image:: /_images/net_verify_failure.jpg
|
||||
:align: center
|
||||
|
||||
On VirtualBox
|
||||
-------------
|
||||
|
||||
Scripts which are provided for quick Fuel setup, create 3 host-interface
|
||||
adapters. Basically networking works as this being a 3 bridges, in each of
|
||||
them the only one VMs interfaces is connected. It means there is only L2
|
||||
connectivity between VMs on interfaces with the same name. If you try to
|
||||
move, for example, management network to `eth1` on Controller node, and the
|
||||
same network to `eth2` on the Compute, then there will be no connectivity
|
||||
between OpenStack services in spite of being configured to live on the same
|
||||
VLAN. It is very easy to validate network settings before deployment by
|
||||
clicking the "Verify Networks" button.
|
||||
If you need to access OpenStack REST API over Public network, VNC console of VMs,
|
||||
Horizon in HA mode or VMs, refer to this section: :ref:`access_to_public_net`.
|
||||
|
||||
Timeout In Connection to OpenStack API From Client Applications
|
||||
---------------------------------------------------------------
|
||||
|
||||
If you use Java, Python or any other code to work with OpenStack API, all
|
||||
connections should be done over OpenStack Public network. To explain why we
|
||||
can not use Fuel network, let's try to run nova client with debug
|
||||
option enabled::
|
||||
|
||||
[root@controller-6 ~]# nova --debug list
|
||||
|
||||
REQ: curl -i http://192.168.0.2:5000/v2.0/tokens -X POST -H "Content-Type: appli
|
||||
cation/json" -H "Accept: application/json" -H "User-Agent: python-novaclient" -d
|
||||
'{"auth": {"tenantName": "admin", "passwordCredentials": {"username": "admin",
|
||||
"password": "admin"}}}'
|
||||
|
||||
INFO (connectionpool:191) Starting new HTTP connection (1): 192.168.0.2
|
||||
DEBUG (connectionpool:283) "POST /v2.0/tokens HTTP/1.1" 200 2702
|
||||
RESP: [200] {'date': 'Tue, 06 Aug 2013 13:01:05 GMT', 'content-type': 'applicati
|
||||
on/json', 'content-length': '2702', 'vary': 'X-Auth-Token'}
|
||||
RESP BODY: {"access": {"token": {"issued_at": "2013-08-06T13:01:05.616481", "exp
|
||||
ires": "2013-08-07T13:01:05Z", "id": "c321cd823c8a4852aea4b870a03c8f72", "tenant
|
||||
": {"description": "admin tenant", "enabled": true, "id": "8eee400f7a8a4f35b7a92
|
||||
bc6cb54de42", "name": "admin"}}, "serviceCatalog": [{"endpoints": [{"adminURL":
|
||||
"http://192.168.0.2:8774/v2/8eee400f7a8a4f35b7a92bc6cb54de42", "region": "Region
|
||||
One", "internalURL": "http://192.168.0.2:8774/v2/8eee400f7a8a4f35b7a92bc6cb54de4
|
||||
2", "id": "6b9563c1e37542519e4fc601b994f980", "publicURL": "http://172.16.1.2:87
|
||||
74/v2/8eee400f7a8a4f35b7a92bc6cb54de42"}], "endpoints_links": [], "type": "compu
|
||||
te", "name": "nova"}, {"endpoints": [{"adminURL": "http://192.168.0.2:8080", "re
|
||||
gion": "RegionOne", "internalURL": "http://192.168.0.2:8080", "id": "4db0e11de35
|
||||
74c889179f499f1e53c7e", "publicURL": "http://172.16.1.2:8080"}], "endpoints_link
|
||||
s": [], "type": "s3", "name": "swift_s3"}, {"endpoints": [{"adminURL": "http://1
|
||||
92.168.0.2:9292", "region": "RegionOne", "internalURL": "http://192.168.0.2:9292
|
||||
", "id": "960a3ad83e4043bbbc708733571d433b", "publicURL": "http://172.16.1.2:929
|
||||
2"}], "endpoints_links": [], "type": "image", "name": "glance"}, {"endpoints": [
|
||||
{"adminURL": "http://192.168.0.2:8776/v1/8eee400f7a8a4f35b7a92bc6cb54de42", "reg
|
||||
ion": "RegionOne", "internalURL": "http://192.168.0.2:8776/v1/8eee400f7a8a4f35b7
|
||||
a92bc6cb54de42", "id": "055edb2aface49c28576347a8c2a5e35", "publicURL": "http://
|
||||
172.16.1.2:8776/v1/8eee400f7a8a4f35b7a92bc6cb54de42"}], "endpoints_links": [], "
|
||||
type": "volume", "name": "cinder"}, {"endpoints": [{"adminURL": "http://192.168.
|
||||
0.2:8773/services/Admin", "region": "RegionOne", "internalURL": "http://192.168.
|
||||
0.2:8773/services/Cloud", "id": "1e5e51a640f94e60aed0a5296eebdb51", "publicURL":
|
||||
"http://172.16.1.2:8773/services/Cloud"}], "endpoints_links": [], "type": "ec2"
|
||||
, "name": "nova_ec2"}, {"endpoints": [{"adminURL": "http://192.168.0.2:8080/",
|
||||
"region": "RegionOne", "internalURL": "http://192.168.0.2:8080/v1/AUTH_8eee400f
|
||||
7a8a4f35b7a92bc6cb54de42", "id": "081a50a3c9fa49719673a52420a87557", "publicURL
|
||||
": "http://172.16.1.2:8080/v1/AUTH_8eee400f7a8a4f35b7a92bc6cb54de42"}], "endpoi
|
||||
nts_links": [], "type": "object-store", "name": "swift"}, {"endpoints": [{"admi
|
||||
nURL": "http://192.168.0.2:35357/v2.0", "region": "RegionOne", "internalURL": "
|
||||
http://192.168.0.2:5000/v2.0", "id": "057a7f8e9a9f4defb1966825de957f5b", "publi
|
||||
cURL": "http://172.16.1.2:5000/v2.0"}], "endpoints_links": [], "type": "identit
|
||||
y", "name": "keystone"}], "user": {"username": "admin", "roles_links": [], "id"
|
||||
: "717701504566411794a9cfcea1a85c1f", "roles": [{"name": "admin"}], "name": "ad
|
||||
min"}, "metadata": {"is_admin": 0, "roles": ["90a1f4f29aef48d7bce3ada631a54261"
|
||||
]}}}
|
||||
|
||||
REQ: curl -i http://172.16.1.2:8774/v2/8eee400f7a8a4f35b7a92bc6cb54de42/servers/
|
||||
detail -X GET -H "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -
|
||||
H "Accept: application/json" -H "X-Auth-Token: c321cd823c8a4852aea4b870a03c8f72"
|
||||
|
||||
INFO (connectionpool:191) Starting new HTTP connection (1): 172.16.1.2
|
||||
|
||||
Even though initial connection was in 192.168.0.2, then client tries to
|
||||
access Public network for Nova API. The reason is because Keystone returns
|
||||
the list of OpenStack services URLs, and for production-grade deployments it
|
||||
is required to access services over public network.
|
||||
|
||||
.. seealso:: :ref:`access_to_public_net` if you want to configure the installation
|
||||
on VirtualBox to make all these issues fixed.
|
||||
|
|
@ -0,0 +1,26 @@
|
|||
.. index:: Preface
|
||||
|
||||
.. _Preface:
|
||||
=============================
|
||||
Preface
|
||||
=============================
|
||||
|
||||
This documentation provides information on how to use Mirantis Fuel
|
||||
to deploy OpenStack environment. The information is for reference purposes
|
||||
and is subject to change.
|
||||
|
||||
Intended Audience
|
||||
-----------------------------
|
||||
|
||||
This documentation is intended for OpenStack administrators and
|
||||
assumes that you have experience with network and cloud concepts.
|
||||
|
||||
Documentation History
|
||||
-----------------------------
|
||||
The following table lists the released revisions of this documentation:
|
||||
|
||||
+--------------------+----------------------------+
|
||||
|Revision Date |Description |
|
||||
+====================+============================+
|
||||
|September, 2013 |Testing Preface |
|
||||
+--------------------+----------------------------+
|
||||
|
|
@ -0,0 +1,36 @@
|
|||
..raw:: pdf
|
||||
|
||||
PageBreak
|
||||
|
||||
..index:: Prerequisites
|
||||
|
||||
Hardware Requirements
|
||||
===========================
|
||||
The amount of hardware depends on your deployment requirements.
|
||||
When you plan your OpenStack environment, consider the following:
|
||||
|
||||
* Processing
|
||||
|
||||
Depends on the number of virtual machines that you plan to deploy
|
||||
in your cloud environment and the CPU per virtual machine.
|
||||
See :ref:'Calculating CPU Requirements'
|
||||
|
||||
* Memory
|
||||
|
||||
Depends on the amount of RAM assigned per virtual machine and the
|
||||
controller node.
|
||||
|
||||
* Storage
|
||||
|
||||
Depends on the local drive space per virtual machine, remote volumes
|
||||
that can be attached to a virtual machine, and object storage.
|
||||
|
||||
* Networking
|
||||
|
||||
Depends on the OpenStack architecture, network bandwidth per virtual
|
||||
machine, and network storage.
|
||||
|
||||
Calculating CPU Requirements
|
||||
---------------------------------
|
||||
|
||||
Calculating Memory Requirements
|
||||
|
|
@ -0,0 +1,15 @@
|
|||
.. index:: User Guide
|
||||
.. _User_Guide:
|
||||
|
||||
=====================
|
||||
User Guide
|
||||
=====================
|
||||
|
||||
.. contents:: :local:
|
||||
:depth: 2
|
||||
|
||||
.. include:: /pages/preface/preface.rst
|
||||
.. include:: /pages/about-fuel/0070-introduction.rst
|
||||
.. include:: /pages/installation-fuel-ui/red_hat_openstack.rst
|
||||
.. include:: /pages/installation-fuel-ui/post-install-healthchecks.rst
|
||||
.. include:: /pages/troubleshooting-ug-network-issues.rst
|
||||
Loading…
Reference in New Issue