|
|
(168 intermediate revisions by one other user not shown) |
Line 1: |
Line 1: |
| 1 Introduction
| | = OpenStack in EPEL = |
| 1.1 Purpose
| |
|
| |
|
| The intent of this document is to provide the Open Source and Red Hat communities with a guide to deploy OpenStack infrastructures using Puppet/Foreman system management solution. | | The OpenStack Folsom was retired from EPEL 6. |
| | | Please visit [http://openstack.redhat.com/Quickstart RDO project] for running OpenStack on EL platforms. |
| We are describing how to deploy and provision the management system itself and how to use it to deploy OpenStack Controller and OpenStack Compute nodes.
| |
| | |
| Note: This information has been gathered from a OpenStack lab project using the latest data available at the time of writing.
| |
| 1.2 Assumptions
| |
| | |
| Upstream OpenStack based on Folsom (2012.2) from EPEL6
| |
| | |
| The Operating System is Red Hat Enterprise Linux - RHEL6.4+. All machines (Virtual or Physical) have been provisioned with a base RHEL6 system and up to date.
| |
| | |
| The system management is based on Foreman 1.1 from the Foreman Yum Repo and Puppet 2.6.17 from the Extra Packages for Enterprise Linux 6 (EPEL6)/
| |
| | |
| Foreman provides full system provisioning, meanwhile this is not covered here, at least for now.
| |
| | |
| Foreman Smart-proxy runs on the same host as Foreman. Please adjust accordingly if running on a separate host.
| |
| | |
| 1.3 Conventions
| |
| | |
| All the code examples shown in this documentation use the following highlight:
| |
| | |
| This is a dummy system command!
| |
| | |
| All the code examples unless specified otherwise, are to be run as root
| |
| | |
| The URL provided to be used must have the host replaced by the corresponding one for the targeted environment
| |
| | |
| <nowiki><H1 CLASS="western" STYLE="page-break-before: always"> 2 Architecture</H1>
| |
| <H2 CLASS="western"> 2.1 OpenStack Components</H2>
| |
| <P CLASS="western">The idea is to have a Management system to be able
| |
| to quick deploy OpenStack Controllers or OpenStack Compute nodes.</P>
| |
| <P CLASS="western">An Openstack Controller Server regroups the
| |
| following OpenStack modules:</P>
| |
| <UL>
| |
| <LI><P CLASS="western">OpenStack Nova Keystone, the identity server</P>
| |
| <LI><P CLASS="western">OpenStack Nova Glance, the image repository</P>
| |
| <LI><P CLASS="western">OpenStack Nova Scheduler</P>
| |
| <LI><P CLASS="western">OpenStack Nova Horizon, the dashboard</P>
| |
| <LI><P CLASS="western">OpenStack Nova API</P>
| |
| <LI><P CLASS="western">QPID the AMQP Messaging Broker</P>
| |
| <LI><P CLASS="western" ALIGN=LEFT>Mysql backend</P>
| |
| <LI><P CLASS="western" ALIGN=LEFT>An OpenStack-Compute</P>
| |
| </UL>
| |
| <P CLASS="western">An OpenStack Compute consists of the following
| |
| modules:</P>
| |
| <UL>
| |
| <LI><P CLASS="western">OpenStack Nova Compute</P>
| |
| <LI><P CLASS="western">OpenStack Nova Network</P>
| |
| <LI><P CLASS="western">OpenStack Nova API</P>
| |
| <LI><P CLASS="western" ALIGN=LEFT>Libvirt and dependant packages</P>
| |
| </UL>
| |
| <H2 CLASS="western"> 2.2 Environment</H2></nowiki>
| |