Book Image

Containers in OpenStack

Book Image

Containers in OpenStack

Overview of this book

Containers are one of the most talked about technologies of recent times. They have become increasingly popular as they are changing the way we develop, deploy, and run software applications. OpenStack gets tremendous traction as it is used by many organizations across the globe and as containers gain in popularity and become complex, it’s necessary for OpenStack to provide various infrastructure resources for containers, such as compute, network, and storage. Containers in OpenStack answers the question, how can OpenStack keep ahead of the increasing challenges of container technology? You will start by getting familiar with container and OpenStack basics, so that you understand how the container ecosystem and OpenStack work together. To understand networking, managing application services and deployment tools, the book has dedicated chapters for different OpenStack projects: Magnum, Zun, Kuryr, Murano, and Kolla. Towards the end, you will be introduced to some best practices to secure your containers and COE on OpenStack, with an overview of using each OpenStack projects for different use cases.
Table of Contents (17 chapters)
Title Page
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Walk-through


In this section, we will do a walk-through on how an application is deployed by Murano. Murano interacts with multiple OpenStack services for resources needed for application deployment.

The request flow for deploying an application in Murano is as follows:

  1. The user sends a REST API call to the murano-api service for deploying an environment via a CLI or Horizon when an authentication token is received from KeyStone
  2. The murano-api service receives the request and sends the request for validation token and access permission to KeyStone
  3. KeyStone validates the token and sends updated authentications headers with roles and permissions
  4. The murano-api service checks whether the session is valid or not. If the session is not valid or already deployed, the request fails with a 403 HTTP status
  5. A check is done to check if the environment was deleted previously or not. If not deleted, an entry is made in the task table to store the information of this action
  6. The murano-api service sends the request...