Preface¶
Welcome
Welcome to OpenStack Bootcamp III (OS300). This course covers the critical skills needed to install, configure, and maintain a highly available production grade OpenStack cloud.
What version OpenStack?
In this course you will use Fuel 7.0 to deploy OpenStack Kilo. The latest Fuel release is 9.0, which can be used to deploy OpenStack Mitaka. In general all of the instructions provided in this document are applicable to the Liberty and Mitaka releases. Wherever it is possible we will provide key differences between Fuel 7.0 and 9.0 and OpenStack releases.
Course Objectives
After completing this course you will understand:
- Different deployments modes for OpenStack services in a multi-node cloud
- Different architectures of highly available (HA) OpenStack cloud
- How to plan the hardware resources you need to deploy a multi-node OpenStack cloud
- Ceph concepts, features, and how it fits with OpenStack
- OpenStack Networking concepts and features
- OpenStack Fuel features, architecture, and limitations
- How to Compare Fuel with other OpenStack deployments tools
Also you will able to:
- Use OpenStack Fuel to deploy a highly available OpenStack cloud from scratch
- Use OpenStack Murano and Application Catalog to deploy applications on the top of OpenStack
- Use OpenStack Sahara to deploy and manage a data-intensive application cluster (Hadoop or Spark) on top of OpenStack
- Do a basic administration of OpenStack cloud
- Use the existing Fuel plugins and implement custom plugins to extend Fuel
This Guide Structure
This guide is designed to complement instructor-led presentations by providing step-by-step instructions for hands-on exercises. It describes how to operate OpenStack services in a functional test environment and, by example, teaches you how to create a new OpenStack environment.
Every chapter of this guide starts with Chapter Details and finishes with Checkpoint.
Chapter Details
Each chapter opens with a short description of the chapter’s goals and objectives, and an outline of the included sections.
Checkpoint
Each chapter ends with a summary of what was covered in the section. You can use Checkpoints to verify your understanding of the topic.
There are a number of notations that are used throughout the guide. They are here to provide you with extra information on the task at hand. Do not execute the steps listed in the notations.
Notes
Notes are tips, shortcuts or alternative approaches for the task at hand.
Reference
References are links to external documentation relevant to a subject.
Important
Important boxes indicate a warning or caution. They detail things that are easily missed and should not be overlooked. This is information that you must be aware of before proceeding.
Code blocks:
Commands to be executed in a terminal window
and an example of the output
Commands need to be executed exactly as they are written with the exception of the command prompt and the parts enclosed in < >, which need to be substituted with your data (typically either the lab environment IP address or ID of a previously created entity). Code blocks can also contain additional comments and/or instructions. The # sign marks the beginning of such comments and/or instructions.
Example of the code block:
[root@fuel ~]# fuel plugins --install <fuel-plugin-file>
...
[root@fuel ~]# fuel plugins --list
# The output will contain the installed plugin name
id | name | version | package_version
----|--------------------------|----------|--------
1 | <fuel-plugin-name> | 1.0.0 | 2.0.0
Here you are expected to execute the commands fuel plugins --install <fuel-plugin-file> and fuel plugins --list. The lines prefixed with # provide additional instructions and [root@fuel ~]# is the command prompt. The actual output may be different from the ones shown in the examples. For longer outputs, the non-important part is excluded and is typically substituted with “...”.
Contents
