Openstack

As we’ve already seen in our previous articles Mirantis Cloud Platform (MCP) is really flexible and can tackle lots of different use cases. Last time we’ve looked at using Ceph as the OpenStack storage backend. Today we are reviewing different ways to leverage Neutron Open vSwitch ML2 plugin instead of the standard OpenContrail SDN solution to offer networking as a service to our users. Introduction To model Open vSwitch Networking in MCP, we first have to choose between different options. What kind of segmentation we’ll be using for our tenant networks, VxLAN or VLAN ? Do we want to use distributed routers (DVR) for East-West routing, and also to directly access floating IPs on Compute ? ...

In the last few articles, I’ve detailed the workflow to deploy Mirantis Cloud Platform (aka MK now MCP) based on Mirantis OpenStack and a Reclass Model Driven Architecture (MDA). But you may want to use a different backend for storage then our standard MCP one, the reference Cinder LVM ISCSI Driver. In this MCP cookbook article, I’ll guide you step by step, to use Ceph as your storage backend for Glance (Images), Cinder (Volumes) and Nova (Guest Disks). You can use any of these options alone or combined. ...

In this article we assume that you are familiar with Salt, formulas, reclass and OpenStack-Salt. This is my cheatsheet which drives you step by step to deploy OpenStack Mitaka based on the latest model, using a new Cluster Class. If you feel lost, feel free to get back to the beginning. What’s new The mk-lab-salt model, built for training and development, introduce the following new features Salt Master now runs on Ubuntu 16.04 LTS OpenStack packages comes from Mirantis repositories New top level cluster class allows a simple modeling of multiple deployments in a single reclass model. Mirantis Stacklight, logging, monitoring and alerting tooling is now integrated Modeling your Infrastructure In this session, I’ll be using my forked repository of Mirantis mk-lab-salt-model infrastructure modeling. ...

After having reviewed Salt, Salt Formulas and reclass, it’s now time to put everything together to deploy OpenStack from openstack-salt project which use an elegant Model-Driven Architecture stored in a git repository which can be used for the life cycle management, auditing and documenting your infrastructure. Imagine a service oriented, repeatable, documented tooling to deploy OpenStack which also can be used to Deploy monitoring Update OpenStack config Audit the deployment through git workflow Document it from a single source of truth Upgrade OpenStack With the following core principles ...

Software Defined Networking (SDN) is often qualified as immature and tagged as complicated. Amongst the many solution available on the market, some of them can do a tremendous job of decoupling physical networking from logical networks used by cloud consumers. It then empower end users to deploy whatever architecture they need on their own. So deploying OpenStack without making sure to tackle the networking requirements of your team could be a recipe for failure. ...

OpenStack is evolving at a rapid pace and for those of you that were here in the early beginning, you may have lost track of the new kids on the block. OpenStack CLI tools is one of them, and is a common client which does many things. In this article I’ll not only review this one but will gather all the toolkit at our disposal from the command line to drive Mirantis OpenStack. Please fasten your seat belts ;) ...

In the Enterprise world, user authenticates over an Lightweight Directory Access Protocol (LDAP) most of the time. Openstack Keystone, the identity service, integrates natively with LDAP directories for authentication and authorization services. The configuration of Keystone can be automated using Mirantis LDAP Fuel Plugin. This article is a step by step guide to integrate Keystone to OpenLDAP but any other LDAP directory including Active Directory could do a perfect job too. Keystone domains The Fuel LDAP Plugin is using the concept of Keystone Domains and put domain specific configuration in ...

In large datacenters it’s common for each rack to live in its own broadcast domain. Fuel allows to deploy nodes on different networks by leveraging its Node Groups functionnality. In this article we’ll details the required steps to make this possible using Mirantis OpenStack 7.0 and we’ll also review Node Groups support improvements coming in MOS 8.0. Terminology In such a large scale architecture, its often required to associate each rack with its own list of logical networks. So we can leverage the Node Groups functionnality of Fuel to create as much network declaration as we require for the following logical networks: ...