Book Image

OpenStack Essentials - Second Edition

By : Dan Radez
Book Image

OpenStack Essentials - Second Edition

By: Dan Radez

Overview of this book

OpenStack is a widely popular platform for cloud computing. Applications that are built for this platform are resilient to failure and convenient to scale. This book, an update to our extremely popular OpenStack Essentials (published in May 2015) will help you master not only the essential bits, but will also examine the new features of the latest OpenStack release - Mitaka; showcasing how to put them to work straight away. This book begins with the installation and demonstration of the architecture. This book will tech you the core 8 topics of OpenStack. They are Keystone for Identity Management, Glance for Image management, Neutron for network management, Nova for instance management, Cinder for Block storage, Swift for Object storage, Ceilometer for Telemetry and Heat for Orchestration. Further more you will learn about launching and configuring Docker containers and also about scaling them horizontally. You will also learn about monitoring and Troubleshooting OpenStack.
Table of Contents (20 chapters)
OpenStack Essentials Second Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Launching a stack


Let's use the HOT hello world. The template can be passed to the Heat stack-create command as a local file, a URL to pull it from the network somewhere, or even as a Swift object if it was stored in Swift. It is important to validate a template. Pull down a copy of the template to your local filesystem.

Before you use this template, edit it and remove the constraints from admin_pass. It will make it easier to experiment with. Remove the lines under admin_pass that include constraints, length, and its description and both allowed_pattern and its description lines.

A template can be validated with Heat's template-validate command. Validating a template requires you to source a keystonerc file, use your overcloudrc file and then make sure that the template still validates with the changes you have made, as shown here:

undercloud# heat template-validate -f hello_world.yaml

Once the template validates, Heat will output a JSON representation of what it parsed from the template...