Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Containers in OpenStack

You're reading from   Containers in OpenStack Leverage OpenStack services to make the most of Docker, Kubernetes and Mesos

Arrow left icon
Product type Paperback
Published in Dec 2017
Publisher Packt
ISBN-13 9781788394383
Length 176 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Pradeep Kumar Singh Pradeep Kumar Singh
Author Profile Icon Pradeep Kumar Singh
Pradeep Kumar Singh
Madhuri Kumari Madhuri Kumari
Author Profile Icon Madhuri Kumari
Madhuri Kumari
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. Working with Containers 2. Working with Container Orchestration Engines FREE CHAPTER 3. OpenStack Architecture 4. Containerization in OpenStack 5. Magnum – COE Management in OpenStack 6. Zun – Container Management in OpenStack 7. Kuryr – Container Plugin for OpenStack Networking 8. Murano – Containerized Application Deployment on OpenStack 9. Kolla – Containerized Deployment of OpenStack 10. Best Practices for Containers and OpenStack

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...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime