Updates install guide with Horizon config information.
Updates with Grizzly and Havana info including new integrated projects. Updates to point to epel repo for RHEL/Fedora/Centos for grizzly. Updates to images where needed. Fix bug 1154325 Fix bug 1154141 Change-Id: Id417de4241b4e8096949a0dd09985739c7a1deb6
This commit is contained in:
annegentle
parent
4ee3fc0cef
commit
a5a86695d4
@ -23,8 +23,8 @@
|
||||
conflict - so if you see issues during package installation,
|
||||
consider filing a bug.</para></listitem>
|
||||
<listitem><para>Monitor your systems and ensure they are not overloaded.
|
||||
Some parts of OpenStack use a lot of CPU time (eg Swift Proxy
|
||||
Servers), while others are IO focused (eg Swift Object Server).
|
||||
Some parts of OpenStack use a lot of CPU time (such as Swift Proxy
|
||||
Servers), while others are IO focused (such as Swift Object Servers).
|
||||
Try to balance these so they complement each other.
|
||||
</para></listitem>
|
||||
<listitem><para>Beware of security. Different parts of OpenStack assume
|
||||
|
||||
@ -248,30 +248,33 @@ the first software that runs is Xen.
|
||||
This means the software you install on your compute host is XenServer or XCP,
|
||||
not the operating system you wish to run the OpenStack code on.
|
||||
The OpenStack services will run in a VM you install on top of XenServer.</para>
|
||||
|
||||
<para>
|
||||
Before you can install your system
|
||||
you must decide if you want to install Citrix XenServer
|
||||
(either the free edition, or one of the paid editions)
|
||||
or Xen Cloud Platform from Xen.org.
|
||||
You can download the software from the following locations:
|
||||
<itemizedlist>
|
||||
<listitem><para><link
|
||||
xlink:href="http://www.citrix.com/XenServer/download">
|
||||
http://www.citrix.com/XenServer/download
|
||||
</link></para></listitem>
|
||||
<listitem><para><link
|
||||
xlink:href="http://www.xen.org/download/xcp/index.html">
|
||||
http://www.xen.org/download/xcp/index.html
|
||||
</link></para></listitem>
|
||||
</itemizedlist>
|
||||
When installing many servers, you may find it easier to perform
|
||||
<link xlink:href="http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_boot_install">
|
||||
PXE boot installations of XenServer or XCP</link>.
|
||||
You can also package up any post install changes you wish to make
|
||||
to your XenServer by
|
||||
<link xlink:href="http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/supplemental_pack_ddk.html">
|
||||
creating your own XenServer supplemental pack</link>.</para>
|
||||
<para> Before you can install your system you must decide if you want
|
||||
to install Citrix XenServer (either the free edition, or
|
||||
one of the paid editions) or Xen Cloud Platform from
|
||||
Xen.org. You can download the software from the following
|
||||
locations: <itemizedlist>
|
||||
<listitem>
|
||||
<para><link
|
||||
xlink:href="http://www.citrix.com/XenServer/download"
|
||||
> http://www.citrix.com/XenServer/download
|
||||
</link></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><link
|
||||
xlink:href="http://www.xen.org/download/xcp/index.html"
|
||||
>
|
||||
http://www.xen.org/download/xcp/index.html
|
||||
</link></para>
|
||||
</listitem>
|
||||
</itemizedlist> When installing many servers, you may find
|
||||
it easier to perform <link
|
||||
xlink:href="http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_boot_install"
|
||||
> PXE boot installations of XenServer or XCP</link>.
|
||||
You can also package up any post install changes you wish
|
||||
to make to your XenServer by <link
|
||||
xlink:href="http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/supplemental_pack_ddk.html"
|
||||
> creating your own XenServer supplemental
|
||||
pack</link>.</para>
|
||||
|
||||
<para>It is also possible to get XCP by installing the <emphasis
|
||||
role="bold">xcp-xenapi</emphasis> package on Debian
|
||||
|
||||
@ -198,10 +198,12 @@ libvirt_cpu_model=Nehalem</programlisting>
|
||||
<simplesect>
|
||||
<title>None (default for all libvirt-driven hypervisors other than KVM &
|
||||
QEMU)</title>
|
||||
<para>If your nova.conf contains <literal>libvirt_cpu_mode=none</literal>, then libvirt
|
||||
will not specify any CPU model at all. It will leave it up to the hypervisor to
|
||||
choose the default model. This setting is equivalent to the Compute service behavior
|
||||
prior to the Folsom release. </para>
|
||||
<para>If your <filename>nova.conf</filename> contains
|
||||
<literal>libvirt_cpu_mode=none</literal>, then
|
||||
libvirt will not specify any CPU model at all. It will
|
||||
leave it up to the hypervisor to choose the default
|
||||
model. This setting is equivalent to the Compute
|
||||
service behavior prior to the Folsom release. </para>
|
||||
</simplesect>
|
||||
</section>
|
||||
<section xml:id="xml-troubleshooting">
|
||||
|
||||
@ -7,16 +7,13 @@
|
||||
xml:id="about-the-dashboard">
|
||||
<title>About the Dashboard</title>
|
||||
<!--<?dbhtml stop-chunking?>-->
|
||||
<para>You can use a dashboard interface with an OpenStack
|
||||
Compute installation with a web-based console provided by
|
||||
the Openstack-Dashboard project. It provides web-based
|
||||
<para>You can use a dashboard interface with an OpenStack Compute
|
||||
installation with a web-based console provided by the
|
||||
OpenStack Dashboard project. It provides web-based
|
||||
interactions with the OpenStack Compute cloud controller
|
||||
through the OpenStack APIs. For more information about the
|
||||
Openstack-Dashboard project, please visit: <link
|
||||
xlink:href="https://github.com/openstack/horizon/"
|
||||
>https://github.com/openstack/horizon/</link>. These
|
||||
instructions are for an example deployment configured with
|
||||
an Apache web server. </para>
|
||||
through the OpenStack APIs. These instructions are
|
||||
for an example deployment configured with an
|
||||
Apache web server. </para>
|
||||
|
||||
<xi:include href="../openstack-install/dashboard-system-reqs.xml"/>
|
||||
<xi:include href="../openstack-install/dashboard-install.xml"/>
|
||||
@ -24,4 +21,4 @@
|
||||
<xi:include href="../openstack-install/dashboard-verify.xml"/>
|
||||
<xi:include href="../common/dashboard_customizing.xml"/>
|
||||
<xi:include href="../common/dashboardlaunchinginstances.xml"/>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
@ -28,7 +28,7 @@
|
||||
<releaseinfo>Grizzly, Compute 2013.1, Network 2013.1, Object Storage
|
||||
1.7.6</releaseinfo>
|
||||
<productname>OpenStack</productname>
|
||||
<pubdate>2013-02-12</pubdate>
|
||||
<pubdate>2013-03-26</pubdate>
|
||||
<legalnotice role="apache2">
|
||||
<annotation>
|
||||
<remark>Copyright details are filled in by the template.</remark>
|
||||
@ -53,6 +53,18 @@
|
||||
as well as sample configuration files. </para>
|
||||
</abstract>
|
||||
<revhistory>
|
||||
<revision>
|
||||
<date>2013-03-26</date>
|
||||
<revdescription>
|
||||
<itemizedlist spacing="compact">
|
||||
<listitem>
|
||||
<para>Updates Dashboard (Horizon)
|
||||
information for Grizzly
|
||||
release.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</revdescription>
|
||||
</revision>
|
||||
<revision>
|
||||
<date>2013-02-12</date>
|
||||
<revdescription>
|
||||
@ -366,8 +378,6 @@
|
||||
<xi:include href="ch_instances-running.xml"/>
|
||||
<xi:include href="ch_installobjectstorage.xml"/>
|
||||
<xi:include href="ch_installdashboard.xml"/>
|
||||
<xi:include href="ch_upgrading_from_essex.xml"/>
|
||||
<xi:include href="ap_configuration_files.xml"/>
|
||||
<xi:include href="ap_installingfolsom.xml"/>
|
||||
|
||||
</book>
|
||||
|
||||
@ -5,8 +5,12 @@
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
|
||||
<title>Installation Assumptions</title>
|
||||
<para>OpenStack Compute has a large number of configuration
|
||||
options. To simplify this installation guide, we make
|
||||
a number of assumptions about the target installation.</para>
|
||||
options. To simplify this installation guide, we make a number
|
||||
of assumptions about the target installation. If you want a
|
||||
longer conceptual planning guide that discusses considerations
|
||||
of these decisions, refer to the <link
|
||||
xlink:href="../openstack-ops/content/">OpenStack
|
||||
Operations Guide</link>.</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para os="rhel;centos;fedora">You have a collection of
|
||||
@ -69,9 +73,10 @@
|
||||
</listitem>
|
||||
<listitem os="ubuntu">
|
||||
<para>On Ubuntu, enable the <link
|
||||
xlink:href="https://wiki.ubuntu.com/ServerTeam/CloudArchive">Cloud
|
||||
Archive</link> repository by adding the following to
|
||||
/etc/apt/sources.list.d/folsom.list:<screen>deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/folsom main</screen></para>
|
||||
xlink:href="https://wiki.ubuntu.com/ServerTeam/CloudArchive"
|
||||
>Cloud Archive</link> repository by adding the
|
||||
following to
|
||||
/etc/apt/sources.list.d/grizzly.list:<screen>deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main</screen></para>
|
||||
<para>Prior to running apt-get update and apt-get upgrade, install the keyring :</para>
|
||||
<screen>sudo apt-get install ubuntu-cloud-keyring</screen>
|
||||
</listitem>
|
||||
@ -84,8 +89,8 @@
|
||||
<command>apt-get upgrade</command> prior to
|
||||
the installation.</para>
|
||||
</listitem>
|
||||
<listitem os="rhel;fedora;centos"><para>On RHEL (and derivatives) enable the EPEL repository by running:</para>
|
||||
<screen><prompt>$</prompt> <userinput>sudo rpm -Uvh http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm</userinput></screen></listitem>
|
||||
<listitem os="rhel;fedora;centos"><para>On RHEL (and derivatives) enable this testing repo for grizzly. </para>
|
||||
<screen><prompt>$</prompt> <userinput>wget http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/epel-openstack-grizzly.repo -O /etc/yum.repos.d/epel-openstack-grizzly.repo</userinput></screen></listitem>
|
||||
</itemizedlist>
|
||||
<para>This installation process walks through installing a cloud
|
||||
controller node and a compute node using a set of packages
|
||||
|
||||
@ -20,14 +20,14 @@
|
||||
<figure><title>Underlying technologies (Scenario 1)</title>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="figures/nova-external-1.svg" scale="60" />
|
||||
<imagedata fileref="figures/nova-external-1.png" scale="60" />
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</figure>
|
||||
<figure><title>Underlying technologies (Scenario 2)</title>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="figures/nova-external-2.svg" scale="60" />
|
||||
<imagedata fileref="figures/nova-external-2.png" scale="60" />
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</figure>
|
||||
@ -99,14 +99,17 @@
|
||||
</simplesect>
|
||||
<simplesect>
|
||||
<title>Cinder</title>
|
||||
<para>By default, <systemitem class="service">Cinder</systemitem> service uses <emphasis
|
||||
role="italic">LVM</emphasis> to create and manage local volumes, and exports them
|
||||
via iSCSI using <emphasis role="italic">IET</emphasis> or <emphasis role="italic">tgt</emphasis>.
|
||||
It can also be configured to use other iSCSI-based storage technologies.</para>
|
||||
<para>In the Folsom OpenStack release, functionality available through
|
||||
<systemitem class="service">nova-volume</systemitem> is also available through a
|
||||
separate OpenStack Volumes project, code-named
|
||||
Cinder.</para>
|
||||
<para>By default, <systemitem class="service"
|
||||
>Cinder</systemitem> service uses <emphasis
|
||||
role="italic">LVM</emphasis> to create and manage
|
||||
local volumes, and exports them via iSCSI using <emphasis
|
||||
role="italic">IET</emphasis> or <emphasis
|
||||
role="italic">tgt</emphasis>. It can also be
|
||||
configured to use other iSCSI-based storage technologies.
|
||||
Functionality previously available through <systemitem
|
||||
class="service">nova-volume</systemitem> is now
|
||||
available through a separate OpenStack Block Storage
|
||||
project, code-named Cinder.</para>
|
||||
</simplesect>
|
||||
<simplesect>
|
||||
<title>openstack-dashboard</title>
|
||||
|
||||
@ -17,11 +17,18 @@
|
||||
Identity, then goes through Image and Compute and also
|
||||
provides deployment information about an Object Storage
|
||||
installation.</para>
|
||||
<para>If you are interested in how to plan for and operate an
|
||||
OpenStack cloud, refer to the <link
|
||||
xlink:href="http://docs.openstack.org/ops/">OpenStack
|
||||
Operations Guide</link>.</para>
|
||||
<para>Here are the overall steps for a manual install:</para>
|
||||
<orderedlist>
|
||||
<listitem><para>Review the most supported platforms. Red Hat Enterprise Linux,
|
||||
Scientific Linux, CentOS, Fedora, Debian, and Ubuntu
|
||||
are the most tested platforms currently. </para></listitem>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Review the most supported platforms. Red Hat
|
||||
Enterprise Linux, Scientific Linux, CentOS, Fedora,
|
||||
Debian, and Ubuntu are the most tested platforms
|
||||
currently. </para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Install the Identity Service (Keystone).</para>
|
||||
</listitem>
|
||||
@ -34,7 +41,7 @@
|
||||
<listitem>
|
||||
<para>Configure the Image Service.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<listitem>
|
||||
<para>Install Compute (Nova).</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
@ -42,9 +49,10 @@
|
||||
Compute.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Configure Compute with FlatDHCP networking
|
||||
using <literal>192.168.100.0/24</literal> as the fixed range for our guest
|
||||
VMs on a bridge named <literal>br100</literal>. </para>
|
||||
<para>Configure Compute with FlatDHCP networking using
|
||||
<literal>192.168.100.0/24</literal> as the fixed
|
||||
range for our guest VMs on a bridge named
|
||||
<literal>br100</literal>. </para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Create and initialize the Compute database with
|
||||
@ -71,78 +79,90 @@
|
||||
<para>Launch an image through the Dashboard to verify the
|
||||
entire installation.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<section xml:id="installing-openstack-compute-on-ubuntu" os="ubuntu">
|
||||
</orderedlist>
|
||||
|
||||
<section xml:id="installing-openstack-compute-on-ubuntu"
|
||||
os="ubuntu">
|
||||
<title>Installing on Ubuntu</title>
|
||||
|
||||
<para>How you go about installing OpenStack Compute depends on your goals
|
||||
for the installation. You can use an ISO image, you can use a scripted
|
||||
installation, and you can manually install with a step-by-step
|
||||
installation as described in this manual.</para>
|
||||
|
||||
<section xml:id="iso-ubuntu-installation">
|
||||
|
||||
<para>How you go about installing OpenStack Compute depends on
|
||||
your goals for the installation. You can use an ISO image,
|
||||
you can use a scripted installation, and you can manually
|
||||
install with a step-by-step installation as described in
|
||||
this manual.</para>
|
||||
|
||||
<section xml:id="iso-ubuntu-installation" os="ubuntu">
|
||||
<title>ISO Installation</title>
|
||||
|
||||
|
||||
<para>See <link
|
||||
xlink:href="http://www.rackspace.com/knowledge_center/article/installing-rackspace-private-cloud-on-physical-hardware"
|
||||
>Installing Rackspace Private Cloud on Physical
|
||||
Hardware</link> for download links and instructions for the
|
||||
Rackspace Private Cloud ISO. For documentation on the
|
||||
Rackspace, see <link xlink:href="http://www.rackspace.com/cloud/private">http://www.rackspace.com/cloud/private</link>. </para>
|
||||
xlink:href="http://www.rackspace.com/knowledge_center/article/installing-rackspace-private-cloud-on-physical-hardware"
|
||||
>Installing Rackspace Private Cloud on Physical
|
||||
Hardware</link> for download links and
|
||||
instructions for the Rackspace Private Cloud ISO. For
|
||||
documentation on the Rackspace, see <link
|
||||
xlink:href="http://www.rackspace.com/cloud/private"
|
||||
>http://www.rackspace.com/cloud/private</link>.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section xml:id="manual-ubuntu-installation">
|
||||
|
||||
<section xml:id="manual-ubuntu-installation" os="ubuntu">
|
||||
<title>Manual Installation on Ubuntu</title>
|
||||
|
||||
<para>The manual installation involves installing from packages
|
||||
shipped on Ubuntu 12.10 using the Cloud Archive as a user with root (or sudo)
|
||||
permission. This guide provides
|
||||
instructions for installing using Ubuntu packages. </para>
|
||||
|
||||
<para>The manual installation involves installing from
|
||||
packages shipped on Ubuntu 12.10 using the Cloud
|
||||
Archive as a user with root (or sudo) permission. This
|
||||
guide provides instructions for installing using
|
||||
Ubuntu packages. </para>
|
||||
</section>
|
||||
<section xml:id="scripted-dev-installation">
|
||||
<title>Scripted Development Installation</title>
|
||||
|
||||
<para>You can download a script for a standalone install for
|
||||
proof-of-concept, learning, or for development purposes for Ubuntu 12.04 or Fedora 16
|
||||
at <link
|
||||
xlink:href="http://devstack.org">https://devstack.org</link>.</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Install Ubuntu 12.04 or Fedora 16:</para>
|
||||
|
||||
<para>In order to correctly install all the dependencies, we assume
|
||||
a specific version of the OS to make it as easy as possible.</para>
|
||||
</listitem>
|
||||
</section>
|
||||
<section xml:id="scripted-dev-installation">
|
||||
<title>Scripted Development Installation</title>
|
||||
|
||||
<para>You can download a script for a standalone install
|
||||
for proof-of-concept, learning, or for development
|
||||
purposes for Ubuntu 12.04 or Fedora 16 at <link
|
||||
xlink:href="http://devstack.org"
|
||||
>https://devstack.org</link>.</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Install Ubuntu 12.04 or Fedora 16:</para>
|
||||
|
||||
<listitem>
|
||||
<para>Download DevStack:</para>
|
||||
|
||||
<screen><prompt>$</prompt> <userinput>git clone git://github.com/openstack-dev/devstack.git</userinput></screen>
|
||||
|
||||
<para>The devstack repository contains a script that installs OpenStack
|
||||
Compute, Object Storage, the Image Service, Volumes, the Dashboard and the Identity Service and offers
|
||||
templates for configuration files plus data scripts.</para>
|
||||
</listitem>
|
||||
<para>In order to correctly install all the
|
||||
dependencies, we assume a specific version of
|
||||
the OS to make it as easy as possible.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Download DevStack:</para>
|
||||
|
||||
<listitem>
|
||||
<para>Start the install:</para>
|
||||
|
||||
<screen><prompt>$</prompt> <userinput>cd devstack; ./stack.sh</userinput></screen>
|
||||
|
||||
<para>It takes a few minutes, we recommend <link
|
||||
xlink:href="http://devstack.org/stack.sh.html">reading the
|
||||
well-documented script</link> while it is building to learn more
|
||||
about what is going on.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</section>
|
||||
<screen><prompt>$</prompt> <userinput>git clone git://github.com/openstack-dev/devstack.git</userinput></screen>
|
||||
|
||||
<para>The devstack repository contains a script
|
||||
that installs OpenStack Compute, Object
|
||||
Storage, the Image Service, Volumes, the
|
||||
Dashboard and the Identity Service and offers
|
||||
templates for configuration files plus data
|
||||
scripts.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Start the install:</para>
|
||||
|
||||
<screen><prompt>$</prompt> <userinput>cd devstack; ./stack.sh</userinput></screen>
|
||||
|
||||
<para>It takes a few minutes, we recommend <link
|
||||
xlink:href="http://devstack.org/stack.sh.html"
|
||||
>reading the well-documented script</link>
|
||||
while it is building to learn more about what
|
||||
is going on.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</section>
|
||||
<xi:include href="example-installation-arch.xml"/>
|
||||
<xi:include href="service-arch.xml"/>
|
||||
<xi:include href="compute-sys-requirements.xml" />
|
||||
<xi:include href="compute-network-planning.xml" />
|
||||
<xi:include href="compute-sys-requirements.xml"/>
|
||||
<xi:include href="compute-network-planning.xml"/>
|
||||
<xi:include href="installing-ntp.xml"/>
|
||||
<xi:include href="installing-mysql.xml"/>
|
||||
<xi:include href="installing-rabbitmq.xml"/>
|
||||
|
||||
@ -10,7 +10,7 @@
|
||||
Version Names
|
||||
</title>
|
||||
<para>Each OpenStack release has a name, in increasing alphabetical
|
||||
order (e.g., Grizzly follows Folsom). There are also version numbers
|
||||
order (e.g., Havana follows Grizzly). There are also version numbers
|
||||
corresponding to these releases, but the numbering schemes are
|
||||
different for OpenStack Compute and OpenStack Object Storage, as
|
||||
shown in the table below:
|
||||
@ -28,6 +28,12 @@
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Havana</td>
|
||||
<td>October 2013</td>
|
||||
<td>2013.3</td>
|
||||
<td>unknown</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><link xlink:href="http://wiki.openstack.org/ReleaseNotes/Grizzly">Grizzly</link></td>
|
||||
<td>April 2013</td>
|
||||
@ -159,6 +165,40 @@
|
||||
service has a configuration file called
|
||||
<filename>keystone.conf</filename>.
|
||||
</para>
|
||||
<para>In addition, projects can go through an incubation phase
|
||||
and become integrated with other OpenStack services that
|
||||
release as a group with integrated testing. Two projects
|
||||
went through that process and will be integrated with the
|
||||
Havana release:</para>
|
||||
<table rules="all" width="100%">
|
||||
<caption>Code names</caption>
|
||||
<col width="50%"/>
|
||||
<col width="50%"/>
|
||||
<thead>
|
||||
<tr>
|
||||
<td>Service name</td>
|
||||
<td>Code name</td>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<para>Metering</para>
|
||||
</td>
|
||||
<td>
|
||||
<para>Ceilometer</para>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<para>Orchestration</para>
|
||||
</td>
|
||||
<td>
|
||||
<para>Heat</para>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<section xml:id="terminology-services">
|
||||
<title>OpenStack Services and Linux Services</title>
|
||||
|
||||
@ -11,8 +11,8 @@
|
||||
<screen>E: Unable to locate package nova-novncproxy</screen>ensure
|
||||
that you have installed the Ubuntu Cloud Archive packages by
|
||||
adding the following to
|
||||
<filename>/etc/apt/sources.list.d/folsom.list</filename>:
|
||||
<screen>deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/folsom main</screen>Prior
|
||||
<filename>/etc/apt/sources.list.d/grizzly.list</filename>:
|
||||
<screen>deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main</screen>Prior
|
||||
to running apt-get update and apt-get upgrade, install the
|
||||
keyring:
|
||||
<screen>sudo apt-get install ubuntu-cloud-keyring</screen>
|
||||
|
||||
@ -82,16 +82,16 @@
|
||||
xlink:href="http://wiki.openstack.org/Packaging"
|
||||
>http://wiki.openstack.org/Packaging</link> for additional
|
||||
links. <note>
|
||||
<para os="ubuntu">The Folsom release of OpenStack Compute
|
||||
requires Ubuntu 12.04 or later, as the version of
|
||||
libvirt that ships with Ubuntu 11.10 does not function
|
||||
properly with OpenStack due to <link
|
||||
<para os="ubuntu">OpenStack Compute requires Ubuntu 12.04
|
||||
or later, as the version of libvirt that ships with
|
||||
Ubuntu 11.10 does not function properly with OpenStack
|
||||
due to <link
|
||||
xlink:href="https://bugs.launchpad.net/nova/+bug/1011863"
|
||||
>bug #1011863</link>.</para>
|
||||
<para os="fedora">The Folsom release of OpenStack Compute
|
||||
requires Fedora 16 or later, as the version of libvirt
|
||||
that ships with Fedora 15 does not function properly
|
||||
with OpenStack due to <link
|
||||
<para os="fedora">OpenStack Compute requires Fedora 16 or
|
||||
later, as the version of libvirt that ships with
|
||||
Fedora 15 does not function properly with OpenStack
|
||||
due to <link
|
||||
xlink:href="https://bugs.launchpad.net/nova/+bug/1011863"
|
||||
>bug #1011863</link>.</para>
|
||||
</note></para>
|
||||
|
||||
@ -23,10 +23,10 @@ nova-consoleauth myhost nova enabled :-) 2012-04-02 14:06:10</compute
|
||||
the XXX state.</para>
|
||||
</note>You can find the version of the installation by using
|
||||
the <command>nova-manage</command> command, as root:</para>
|
||||
<screen><prompt>#</prompt> <userinput>nova-manage version list</userinput></screen>
|
||||
<screen><prompt>#</prompt> <userinput>nova-manage version</userinput></screen>
|
||||
|
||||
<para>The version number 2012.2 corresponds with the Folsom
|
||||
<para>The version number 2013.1 corresponds with the Grizzly
|
||||
release of Compute.</para>
|
||||
|
||||
<literallayout class="monospaced">2012.2 (2012.1-LOCALBRANCH:LOCALREVISION)</literallayout>
|
||||
<literallayout class="monospaced">2013.1 </literallayout>
|
||||
</section>
|
||||
|
||||
@ -4,19 +4,15 @@
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
|
||||
<title>Configuring the Dashboard</title>
|
||||
<para>A full example <filename>local_settings.py</filename> file is included in the Appendix of the OpenStack
|
||||
Install and Deploy manual. Here are some common options:</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><literal>SWIFT_ENABLED</literal>: If an Object Storage (Swift) endpoint is
|
||||
available and configured in the Identity service catalog, set <literal>SWIFT_ENABLED
|
||||
= True</literal>. </para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><literal>QUANTUM_ENABLED</literal>: If a Network Connection (Quantum) service is
|
||||
available and configured in the Identity service catalog, set
|
||||
<literal>QUANTUM_ENABLED = True</literal>. Else keep it FALSE if you are not
|
||||
using Quantum.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
<para>
|
||||
Specify the host for your OpenStack Identity Service endpoint
|
||||
in the local_settings.py file with the OPENSTACK_HOST setting.
|
||||
An example is included:
|
||||
</para>
|
||||
<programlisting><xi:include parse="text" href="samples/local_settings.py"/></programlisting>
|
||||
<para>The HORIZON_CONFIG dictionary contains all the settings for
|
||||
the Dashboard. Whether or not a service is in the Dashboard
|
||||
depends on the Service Catalog configuration in the Identity
|
||||
service. Refer to <link xlink:href="http://docs.openstack.org/developer/horizon/topics/settings.html">Horizon Settings and Configuration</link> for the
|
||||
full listing.</para>
|
||||
</section>
|
||||
|
||||
@ -1,7 +1,9 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<section xml:id="installing-openstack-dashboard" xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
|
||||
<title>Installing the OpenStack Dashboard</title>
|
||||
<para>Here are the overall steps for creating the OpenStack dashboard.</para>
|
||||
<para>Here are the overall steps for creating the OpenStack
|
||||
dashboard. Details about deployment are available at <link xlink:href="http://docs.openstack.org/developer/horizon/topics/deployment.html">Deploying
|
||||
Horizon</link>.</para>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Install the OpenStack Dashboard framework including Apache and related
|
||||
|
||||
@ -5,13 +5,11 @@
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
|
||||
<title>Validating the Dashboard Install</title>
|
||||
<para>To validate the Dashboard installation, point your browser at
|
||||
http://192.168.206.130/horizon. Note that you cannot use VNC Console
|
||||
from a Chrome browser. You need both Flash installed and a
|
||||
Firefox browser. Once you connect to the Dashboard with the
|
||||
URL, you should see a login window. Enter the credentials for
|
||||
users you created with the Identity Service, Keystone. For
|
||||
example, enter "admin" for the username and "secrete" as
|
||||
the password.</para>
|
||||
http://192.168.206.130. Once you connect to the Dashboard with
|
||||
the URL, you should see a login window. Enter the credentials
|
||||
for users you created with the Identity Service, Keystone. For
|
||||
example, enter "admin" for the username and "secrete" as the
|
||||
password.</para>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="figures/dashboard-overview.png"
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 187 KiB After Width: | Height: | Size: 504 KiB |
@ -4655,7 +4655,7 @@
|
||||
xlink:href="#linearGradient2817"
|
||||
id="linearGradient16802"
|
||||
gradientUnits="userSpaceOnUse"
|
||||
gradientTransform="matrix(0.49114184,0,0,0.6629986,189.52223,210.60917)"
|
||||
gradientTransform="matrix(0.68986128,0,0,0.6629986,133.87777,210.60917)"
|
||||
x1="247.14285"
|
||||
y1="484.50504"
|
||||
x2="213.57144"
|
||||
@ -4841,11 +4841,11 @@
|
||||
borderopacity="1.0"
|
||||
inkscape:pageopacity="0.0"
|
||||
inkscape:pageshadow="2"
|
||||
inkscape:zoom="0.6491111"
|
||||
inkscape:cx="219.31218"
|
||||
inkscape:cy="664.4532"
|
||||
inkscape:zoom="0.65186683"
|
||||
inkscape:cx="372.04724"
|
||||
inkscape:cy="526.18109"
|
||||
inkscape:document-units="px"
|
||||
inkscape:current-layer="layer1"
|
||||
inkscape:current-layer="g16939"
|
||||
showgrid="false"
|
||||
inkscape:window-width="1145"
|
||||
inkscape:window-height="934"
|
||||
@ -4897,16 +4897,16 @@
|
||||
y="404.50504" /></flowRegion><flowPara
|
||||
id="flowPara2835" /></flowRoot> <g
|
||||
id="g16794"
|
||||
transform="translate(-24.010968,-5.3372475)">
|
||||
transform="translate(-20.010968,-5.3372475)">
|
||||
<rect
|
||||
ry="11.945394"
|
||||
rx="8.8490124"
|
||||
rx="12.429385"
|
||||
y="496.79114"
|
||||
x="276.52448"
|
||||
x="256.08176"
|
||||
height="70.088417"
|
||||
width="89.808792"
|
||||
width="126.14606"
|
||||
id="rect2815"
|
||||
style="fill:url(#linearGradient16802);fill-opacity:1;stroke:#000000;stroke-opacity:1" />
|
||||
style="fill:url(#linearGradient16802);fill-opacity:1;stroke:#000000;stroke-width:1.18516123;stroke-opacity:1" />
|
||||
<text
|
||||
id="text2825"
|
||||
y="519.22876"
|
||||
@ -4928,13 +4928,24 @@
|
||||
x="321.43179"
|
||||
id="tspan2839"
|
||||
sodipodi:role="line"
|
||||
style="font-size:12px;stroke:none">Messaging</tspan><tspan
|
||||
style="font-size:12px;stroke:none">Messaging server</tspan><tspan
|
||||
y="559.44421"
|
||||
x="321.43179"
|
||||
sodipodi:role="line"
|
||||
style="font-size:12px;stroke:none"
|
||||
id="tspan9256">(RabbitMQ)</tspan></text>
|
||||
</g>
|
||||
id="tspan9256" /></text>
|
||||
<flowRoot
|
||||
xml:space="preserve"
|
||||
id="flowRoot3876"
|
||||
style="font-size:12px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
|
||||
transform="translate(24.010968,5.3372475)"><flowRegion
|
||||
id="flowRegion3878"><rect
|
||||
id="rect3880"
|
||||
width="0"
|
||||
height="24.544891"
|
||||
x="302.20895"
|
||||
y="539.98761" /></flowRegion><flowPara
|
||||
id="flowPara3882">z</flowPara></flowRoot> </g>
|
||||
<g
|
||||
id="g16889"
|
||||
transform="translate(0.50596409,-29.325539)">
|
||||
@ -5559,7 +5570,7 @@
|
||||
y="485.27835"
|
||||
x="93.898621"
|
||||
id="tspan9302-8"
|
||||
sodipodi:role="line">User authorisation</tspan></text>
|
||||
sodipodi:role="line">User authorization</tspan></text>
|
||||
<text
|
||||
id="text9304-5"
|
||||
y="508.6889"
|
||||
@ -5581,6 +5592,18 @@
|
||||
x="93.686707"
|
||||
sodipodi:role="line"
|
||||
style="font-size:12px;stroke:none" /></text>
|
||||
<text
|
||||
xml:space="preserve"
|
||||
style="font-size:12px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
|
||||
x="-35.283279"
|
||||
y="507.77243"
|
||||
id="text3886"
|
||||
sodipodi:linespacing="125%"
|
||||
transform="translate(-2.3108524,-4.038323)"><tspan
|
||||
sodipodi:role="line"
|
||||
id="tspan3888"
|
||||
x="-35.283279"
|
||||
y="507.77243">s</tspan></text>
|
||||
</g>
|
||||
<path
|
||||
style="fill:none;stroke:#000000;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-start:url(#Arrow1Lstart-5);marker-end:url(#Arrow1Lend-9)"
|
||||
@ -5604,7 +5627,7 @@
|
||||
inkscape:connector-curvature="0" />
|
||||
<path
|
||||
style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-start:url(#Arrow1Lstart-5);marker-end:url(#Arrow1Lend-9)"
|
||||
d="m 249.36342,387.69125 35.92229,103.76264"
|
||||
d="m 249.71117,387.69125 36.95251,103.76264"
|
||||
id="path17011"
|
||||
inkscape:connector-type="polyline"
|
||||
inkscape:connection-start="#g16889"
|
||||
@ -5614,7 +5637,7 @@
|
||||
inkscape:connector-curvature="0" />
|
||||
<path
|
||||
style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-start:url(#Arrow1Lstart-5);marker-end:url(#Arrow1Lend-9)"
|
||||
d="M 254.88157,495.24992 144.01331,413.80352"
|
||||
d="M 251.03072,491.45389 144.42253,413.80352"
|
||||
id="path17013"
|
||||
inkscape:connector-type="polyline"
|
||||
inkscape:connection-start="#g16794"
|
||||
@ -5624,7 +5647,7 @@
|
||||
inkscape:connector-curvature="0" />
|
||||
<path
|
||||
style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-start:url(#Arrow1Lstart-5);marker-end:url(#Arrow1Lend-9)"
|
||||
d="m 385.14058,375.96289 -67.30106,115.491"
|
||||
d="m 385.46635,375.96289 -66.22687,115.491"
|
||||
id="path17015"
|
||||
inkscape:connector-type="polyline"
|
||||
inkscape:connection-end="#g16794"
|
||||
@ -5682,7 +5705,7 @@
|
||||
</g>
|
||||
<path
|
||||
style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-start:url(#Arrow1Lstart-5);marker-end:url(#Arrow1Lend-9)"
|
||||
d="m 406.64919,515.24899 -64.32689,6.62466"
|
||||
d="m 406.64919,515.32528 -44.43234,4.61776"
|
||||
id="path17017"
|
||||
inkscape:connector-type="polyline"
|
||||
inkscape:connection-start="#g16785"
|
||||
@ -5692,7 +5715,7 @@
|
||||
inkscape:connector-curvature="0" />
|
||||
<path
|
||||
style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-start:url(#Arrow1Lstart-5);marker-end:url(#Arrow1Lend-9)"
|
||||
d="M 413.14924,577.4452 342.3223,546.26585"
|
||||
d="M 413.45513,577.28123 361.30431,554.11308"
|
||||
id="path17023"
|
||||
inkscape:connector-type="polyline"
|
||||
inkscape:connection-start="#g16948"
|
||||
@ -5812,7 +5835,7 @@
|
||||
</g>
|
||||
<path
|
||||
style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-start:url(#Arrow1Lstart-5);marker-end:url(#Arrow1Lend-9)"
|
||||
d="M 352.22222,659.42236 311.86654,561.54231"
|
||||
d="M 352.58215,659.42236 313.23232,561.54231"
|
||||
id="path17447"
|
||||
inkscape:connector-type="polyline"
|
||||
inkscape:connection-start="#g17417"
|
||||
@ -5867,7 +5890,7 @@
|
||||
</g>
|
||||
<path
|
||||
style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-start:url(#Arrow1Lstart-5);marker-end:url(#Arrow1Lend-9)"
|
||||
d="m 197.27203,593.26309 56.4451,-37.63067"
|
||||
d="m 197.8659,593.26309 48.40612,-31.91055"
|
||||
id="path20277"
|
||||
inkscape:connector-type="polyline"
|
||||
inkscape:connection-start="#g20255"
|
||||
|
||||
|
Before Width: | Height: | Size: 204 KiB After Width: | Height: | Size: 205 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 70 KiB After Width: | Height: | Size: 79 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 54 KiB After Width: | Height: | Size: 112 KiB |
File diff suppressed because one or more lines are too long
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 35 KiB |
@ -17,11 +17,14 @@
|
||||
<prompt>#</prompt> <userinput>service ntp restart</userinput></screen>
|
||||
<screen os="rhel;fedora;centos"><prompt>$</prompt> <userinput>sudo service ntpd start</userinput>
|
||||
<prompt>$</prompt> <userinput>sudo chkconfig ntpd on</userinput></screen>
|
||||
<para>Set up the NTP client on your compute node so that the time between controller node and
|
||||
compute node is synchronized. The simplest way to do this is to add a daily cron job that
|
||||
synchonizes the compute node's clock with the controller node. You can accomplish this by
|
||||
adding a file, owned by root, marked executable, at
|
||||
<filename>/etc/cron.daily/ntpdate</filename> that contains the
|
||||
<para>Set up the NTP client on your compute node so that the time
|
||||
between controller node and compute node is synchronized. The
|
||||
simplest way to do this is to add a daily cron job that
|
||||
synchronizes the compute node's clock with the controller
|
||||
node. You can accomplish this by adding a file, owned by root,
|
||||
marked executable, at
|
||||
<filename>/etc/cron.daily/ntpdate</filename> that contains
|
||||
the
|
||||
following:<programlisting>ntpdate <replaceable><hostname or IP address of controller></replaceable>
|
||||
hwclock -w</programlisting></para>
|
||||
<para>If a large clock skew builds up between the compute nodes and the controller node, then
|
||||
|
||||
@ -4,9 +4,8 @@
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
|
||||
<title>Installing A Messaging Server</title>
|
||||
<para os="ubuntu">Install the messaging queue server, either Qpid or RabbitMQ.</para>
|
||||
<para>You have
|
||||
the option of installing either Apache Qpid, usually for rpm based systems, or RabbitMQ, usually for Ubuntu systems.
|
||||
<para>Install the messaging queue server. Typically this is either Qpid or RabbitMQ but ZeroMQ (0MQ) is also available.</para>
|
||||
<para>
|
||||
If Qpid is to be installed, refer to the Compute
|
||||
Administration Manual for configuration instructions, including adding rpc_backend=nova.rpc.impl_qpid to your <filename>nova.conf</filename>.</para>
|
||||
<screen os="ubuntu">sudo apt-get install rabbitmq-server</screen>
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
[DEFAULT]
|
||||
rootwrap_config=/etc/cinder/rootwrap.conf
|
||||
sql_connection = mysql://cinder:openstack@10.211.55.20/cinder
|
||||
sql_connection = mysql://cinder:openstack@192.168.127.130/cinder
|
||||
api_paste_config = /etc/cinder/api-paste.ini
|
||||
|
||||
iscsi_helper=tgtadm
|
||||
|
||||
@ -1,104 +1,202 @@
|
||||
import os
|
||||
|
||||
from django.utils.translation import ugettext_lazy as _
|
||||
|
||||
from openstack_dashboard import exceptions
|
||||
|
||||
DEBUG = True
|
||||
TEMPLATE_DEBUG = DEBUG
|
||||
PROD = False
|
||||
USE_SSL = False
|
||||
|
||||
LOCAL_PATH = os.path.dirname(os.path.abspath(__file__))
|
||||
#DATABASES = {
|
||||
# 'default': {
|
||||
# 'ENGINE': 'django.db.backends.sqlite3',
|
||||
# 'NAME': os.path.join(LOCAL_PATH, 'dashboard_openstack.sqlite3'),
|
||||
# },
|
||||
#}
|
||||
# Set SSL proxy settings:
|
||||
# For Django 1.4+ pass this header from the proxy after terminating the SSL,
|
||||
# and don't forget to strip it from the client's request.
|
||||
# For more information see:
|
||||
# https://docs.djangoproject.com/en/1.4/ref/settings/#secure-proxy-ssl-header
|
||||
# SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTOCOL', 'https')
|
||||
|
||||
DATABASES = {
|
||||
'default': {
|
||||
'ENGINE': 'django.db.backends.mysql',
|
||||
'NAME': 'dash',
|
||||
'USER': 'dash',
|
||||
'PASSWORD': 'yourpassword',
|
||||
'HOST': 'localhost',
|
||||
'default-character-set': 'utf8'
|
||||
# If Horizon is being served through SSL, then uncomment the following two
|
||||
# settings to better secure the cookies from security exploits
|
||||
#CSRF_COOKIE_SECURE = True
|
||||
#SESSION_COOKIE_SECURE = True
|
||||
|
||||
# Default OpenStack Dashboard configuration.
|
||||
HORIZON_CONFIG = {
|
||||
'dashboards': ('project', 'admin', 'settings',),
|
||||
'default_dashboard': 'project',
|
||||
'user_home': 'openstack_dashboard.views.get_user_home',
|
||||
'ajax_queue_limit': 10,
|
||||
'auto_fade_alerts': {
|
||||
'delay': 3000,
|
||||
'fade_duration': 1500,
|
||||
'types': ['alert-success', 'alert-info']
|
||||
},
|
||||
'help_url': "http://docs.openstack.org",
|
||||
'exceptions': {'recoverable': exceptions.RECOVERABLE,
|
||||
'not_found': exceptions.NOT_FOUND,
|
||||
'unauthorized': exceptions.UNAUTHORIZED},
|
||||
}
|
||||
|
||||
CACHE_BACKEND = 'dummy://'
|
||||
# Specify a regular expression to validate user passwords.
|
||||
# HORIZON_CONFIG["password_validator"] = {
|
||||
# "regex": '.*',
|
||||
# "help_text": _("Your password does not meet the requirements.")
|
||||
# }
|
||||
|
||||
SESSION_ENGINE = 'django.contrib.sessions.backends.cached_db'
|
||||
# Disable simplified floating IP address management for deployments with
|
||||
# multiple floating IP pools or complex network requirements.
|
||||
# HORIZON_CONFIG["simple_ip_management"] = False
|
||||
|
||||
# Turn off browser autocompletion for the login form if so desired.
|
||||
# HORIZON_CONFIG["password_autocomplete"] = "off"
|
||||
|
||||
LOCAL_PATH = os.path.dirname(os.path.abspath(__file__))
|
||||
|
||||
# Set custom secret key:
|
||||
# You can either set it to a specific value or you can let horizion generate a
|
||||
# default secret key that is unique on this machine, e.i. regardless of the
|
||||
# amount of Python WSGI workers (if used behind Apache+mod_wsgi): However, there
|
||||
# may be situations where you would want to set this explicitly, e.g. when
|
||||
# multiple dashboard instances are distributed on different machines (usually
|
||||
# behind a load-balancer). Either you have to make sure that a session gets all
|
||||
# requests routed to the same dashboard instance or you set the same SECRET_KEY
|
||||
# for all of them.
|
||||
# from horizon.utils import secret_key
|
||||
# SECRET_KEY = secret_key.generate_or_read_from_file(os.path.join(LOCAL_PATH, '.secret_key_store'))
|
||||
|
||||
# We recommend you use memcached for development; otherwise after every reload
|
||||
# of the django development server, you will have to login again. To use
|
||||
# memcached set CACHES to something like
|
||||
# CACHES = {
|
||||
# 'default': {
|
||||
# 'BACKEND' : 'django.core.cache.backends.memcached.MemcachedCache',
|
||||
# 'LOCATION' : '127.0.0.1:11211',
|
||||
# }
|
||||
#}
|
||||
|
||||
CACHES = {
|
||||
'default': {
|
||||
'BACKEND' : 'django.core.cache.backends.locmem.LocMemCache'
|
||||
}
|
||||
}
|
||||
|
||||
# Send email to the console by default
|
||||
EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'
|
||||
# Or send them to /dev/null
|
||||
#EMAIL_BACKEND = 'django.core.mail.backends.dummy.EmailBackend'
|
||||
|
||||
# django-mailer uses a different settings attribute
|
||||
MAILER_EMAIL_BACKEND = EMAIL_BACKEND
|
||||
|
||||
# Configure these for your outgoing email host
|
||||
# EMAIL_HOST = 'smtp.my-company.com'
|
||||
# EMAIL_PORT = 25
|
||||
# EMAIL_HOST_USER = 'djangomail'
|
||||
# EMAIL_HOST_PASSWORD = 'top-secret!'
|
||||
|
||||
# For multiple regions uncomment this configuration, and add (endpoint, title).
|
||||
# AVAILABLE_REGIONS = [
|
||||
# ('http://cluster1.example.com:5000/v2.0', 'cluster1'),
|
||||
# ('http://cluster2.example.com:5000/v2.0', 'cluster2'),
|
||||
# ]
|
||||
|
||||
OPENSTACK_KEYSTONE_URL = "http://localhost:5000/v2.0/"
|
||||
# FIXME: this is only needed until keystone fixes its GET /tenants call
|
||||
# so that it doesn't return everything for admins
|
||||
OPENSTACK_KEYSTONE_ADMIN_URL = "http://localhost:35357/v2.0"
|
||||
OPENSTACK_HOST = "192.168.127.130"
|
||||
OPENSTACK_KEYSTONE_URL = "http://%s:5000/v2.0" % OPENSTACK_HOST
|
||||
OPENSTACK_KEYSTONE_DEFAULT_ROLE = "Member"
|
||||
|
||||
# NOTE(tres): Available services should come from the service
|
||||
# catalog in Keystone.
|
||||
SWIFT_ENABLED = False
|
||||
# Disable SSL certificate checks (useful for self-signed certificates):
|
||||
# OPENSTACK_SSL_NO_VERIFY = True
|
||||
|
||||
# Configure quantum connection details for networking
|
||||
QUANTUM_ENABLED = False
|
||||
QUANTUM_URL = '127.0.0.1'
|
||||
QUANTUM_PORT = '9696'
|
||||
QUANTUM_TENANT = '1234'
|
||||
QUANTUM_CLIENT_VERSION='0.1'
|
||||
# The OPENSTACK_KEYSTONE_BACKEND settings can be used to identify the
|
||||
# capabilities of the auth backend for Keystone.
|
||||
# If Keystone has been configured to use LDAP as the auth backend then set
|
||||
# can_edit_user to False and name to 'ldap'.
|
||||
#
|
||||
# TODO(tres): Remove these once Keystone has an API to identify auth backend.
|
||||
OPENSTACK_KEYSTONE_BACKEND = {
|
||||
'name': 'native',
|
||||
'can_edit_user': True,
|
||||
'can_edit_project': True
|
||||
}
|
||||
|
||||
# If you have external monitoring links
|
||||
EXTERNAL_MONITORING = [
|
||||
['Nagios','http://foo.com'],
|
||||
['Ganglia','http://bar.com'],
|
||||
]
|
||||
|
||||
# If you do not have external monitoring links
|
||||
# EXTERNAL_MONITORING = []
|
||||
|
||||
# Uncomment the following segment to silence most logging
|
||||
# django.db and boto DEBUG logging is extremely verbose.
|
||||
#LOGGING = {
|
||||
# 'version': 1,
|
||||
# # set to True will disable all logging except that specified, unless
|
||||
# # nothing is specified except that django.db.backends will still log,
|
||||
# # even when set to True, so disable explicitly
|
||||
# 'disable_existing_loggers': False,
|
||||
# 'handlers': {
|
||||
# 'null': {
|
||||
# 'level': 'DEBUG',
|
||||
# 'class': 'django.utils.log.NullHandler',
|
||||
# },
|
||||
# 'console': {
|
||||
# 'level': 'DEBUG',
|
||||
# 'class': 'logging.StreamHandler',
|
||||
# },
|
||||
# },
|
||||
# 'loggers': {
|
||||
# # Comment or Uncomment these to turn on/off logging output
|
||||
# 'django.db.backends': {
|
||||
# 'handlers': ['null'],
|
||||
# 'propagate': False,
|
||||
# },
|
||||
# 'django_openstack': {
|
||||
# 'handlers': ['null'],
|
||||
# 'propagate': False,
|
||||
# },
|
||||
# }
|
||||
#}
|
||||
OPENSTACK_HYPERVISOR_FEATURES = {
|
||||
'can_set_mount_point': True,
|
||||
|
||||
# How much ram on each compute host?
|
||||
COMPUTE_HOST_RAM_GB = 16
|
||||
# NOTE: as of Grizzly this is not yet supported in Nova so enabling this
|
||||
# setting will not do anything useful
|
||||
'can_encrypt_volumes': False
|
||||
}
|
||||
|
||||
# The OPENSTACK_QUANTUM_NETWORK settings can be used to enable optional
|
||||
# services provided by quantum. Currently only the load balancer service
|
||||
# is available.
|
||||
OPENSTACK_QUANTUM_NETWORK = {
|
||||
'enable_lb': False
|
||||
}
|
||||
|
||||
# OPENSTACK_ENDPOINT_TYPE specifies the endpoint type to use for the endpoints
|
||||
# in the Keystone service catalog. Use this setting when Horizon is running
|
||||
# external to the OpenStack environment. The default is 'internalURL'.
|
||||
#OPENSTACK_ENDPOINT_TYPE = "publicURL"
|
||||
|
||||
# The number of objects (Swift containers/objects or images) to display
|
||||
# on a single page before providing a paging element (a "more" link)
|
||||
# to paginate results.
|
||||
API_RESULT_LIMIT = 1000
|
||||
API_RESULT_PAGE_SIZE = 20
|
||||
|
||||
# The timezone of the server. This should correspond with the timezone
|
||||
# of your entire OpenStack installation, and hopefully be in UTC.
|
||||
TIME_ZONE = "UTC"
|
||||
|
||||
LOGGING = {
|
||||
'version': 1,
|
||||
# When set to True this will disable all logging except
|
||||
# for loggers specified in this configuration dictionary. Note that
|
||||
# if nothing is specified here and disable_existing_loggers is True,
|
||||
# django.db.backends will still log unless it is disabled explicitly.
|
||||
'disable_existing_loggers': False,
|
||||
'handlers': {
|
||||
'null': {
|
||||
'level': 'DEBUG',
|
||||
'class': 'django.utils.log.NullHandler',
|
||||
},
|
||||
'console': {
|
||||
# Set the level to "DEBUG" for verbose output logging.
|
||||
'level': 'INFO',
|
||||
'class': 'logging.StreamHandler',
|
||||
},
|
||||
},
|
||||
'loggers': {
|
||||
# Logging from django.db.backends is VERY verbose, send to null
|
||||
# by default.
|
||||
'django.db.backends': {
|
||||
'handlers': ['null'],
|
||||
'propagate': False,
|
||||
},
|
||||
'requests': {
|
||||
'handlers': ['null'],
|
||||
'propagate': False,
|
||||
},
|
||||
'horizon': {
|
||||
'handlers': ['console'],
|
||||
'propagate': False,
|
||||
},
|
||||
'openstack_dashboard': {
|
||||
'handlers': ['console'],
|
||||
'propagate': False,
|
||||
},
|
||||
'novaclient': {
|
||||
'handlers': ['console'],
|
||||
'propagate': False,
|
||||
},
|
||||
'keystoneclient': {
|
||||
'handlers': ['console'],
|
||||
'propagate': False,
|
||||
},
|
||||
'glanceclient': {
|
||||
'handlers': ['console'],
|
||||
'propagate': False,
|
||||
},
|
||||
'nose.plugins.manager': {
|
||||
'handlers': ['console'],
|
||||
'propagate': False,
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user