How to Install Openstack Ocata Release on a Single Node

OpenStack Ocata, the 15th release of the most widely deployed open source software for building clouds, offers substantial innovation in integrating bare metal, virtual machines and containers on a single network, with a single set of APIs that are the de facto global standard for private clouds.

Ocata’s features and enhancements include improving the ease of deploying, managing and upgrading container orchestration.

What's New in Ocata Release

Container Orchestration

OpenStack continues to grow its support for container-based application frameworks and deployment tools, improving the ease of deploying, managing and upgrading container orchestration, treating it as a micro services application. Other container-related enhancements include:

• Magnum now supports Mesosphere DC/OS as a cluster type and Kubernetes support now includes the new SUSE distribution
• Kolla support for Kubernetes at the control plane
• Kuryr container networking service now supports Docker Swarm

Kolla (containerized OpenStack services), Kuryr (bridging container networking and storage with OpenStack) and Zun (container management) project saw the most contributor growth in this release cycle.The new Fuxi (“FOO-si”) subproject of Kuryr connects Cinder and Manila storage to container environments.

Improved Upgrades

OpenStack Ocata continues to focus on improving upgrades, such as with Nova, which is in use by virtually all OpenStack clouds. A new "Nova-status upgrade check" CLI (command line interface) enables operators to test the readiness of their deployments to see if they can safely upgrade to Ocata or find out what needs to be addressed before upgrading to ensure stability and reliability.

This is especially important as OpenStack’s adoption shows increasing maturity, with a 20% increase in production deployments year-over-year, reaching 71% in production or full operational use, according to the latest OpenStack User Survey.

Performance at Scale

Ocata also offers better performance at scale, with a new Nova “placement” API that helps users intelligently allocate resources based on application needs. Additionally, Cells v2 has become default in Nova. Additional performance improvements include:

• Horizon dashboard now supports keystone-to-keystone federation as new os-profiler UI, which gives operators the ability to detect performance issues across OpenStack services

• Auto-provisioning for Keystone federated identity dynamically creates a project and assigns a federated user a role upon successful authentication

• Ironic bare metal service becomes more robust with networking and driver enhancements

• Zaqar messaging service added Swift object storage as a backend to easily leverage an existing Swift cluster without deploying another MongoDB or Redis cluster

• Greatly improved performance and CPU usage for Telemetry projects: storing millions of metrics per second is now possible using Ceilometer with Gnocchi storage engine

• Active/Active HA in Cinder service can now be implemented by drivers

• Congress governance framework now has policy language enhancements to enable network address operations for better network and security governance

This guide will take you through the steps to deploy an Openstack Ocata infrastructure on a single node using Devstack.

Prerequisites

To follow this guide, you will need

• A virtual machine or a bare metal hardware with virtualization capability including 14GB of Memory or more for the best results and at least 100 GB of hard disk space.
• Ubuntu 16.04 LTS server.

Installing OpenStack

First, we need to execute the git command to clone devstack. Access your Ubuntu Server over ssh and type the following commands.

cd /
sudo git clone https://git.openstack.org/openstack-dev/devstack -b stable/ocata

Now, we need to copy the sample local.conf file and set a password that will be used during the automated deployment.

cd devstack/
sudo cp samples/local.conf local.conf
sudo nano local.conf

Scroll down until you see the password variables.  You need to set your password after ADMIN_PASSWORD=, and change the other three to $ADMIN_PASSWORD.  This makes everything use the same password during the installation.

ADMIN_PASSWORD=yourpassword
MYSQL_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=$ADMIN_PASSWORD
SERVICE_PASSWORD=$ADMIN_PASSWORD

Make sure it looks like as shown in image below before saving and closing.

Here we'll run a script to create a new user for OpenStack, then make that new user the owner of the devstack folder.

sudo /devstack/tools/create-stack-user.sh
sudo chown -R stack:stack /devstack

Now we need to execute the following command to begin the installation openstack. This will take several minutes to complete.

sudo su stack
/devstack/stack.sh

Once set up completed, you will eventually end up looking at something like this.

As you can see, two users have been created for you; admin and demo.  Your password is the password you set earlier.  These are the usernames you will use to login to the OpenStack Horizon Dashboard.  Take note of the Horizon web address listed in your terminal. 

Open up a browser, and get into the Horizon Dashboard by accessing the Ubuntu machine IP address http://192.168.0.116/dashboard.

Log in with the admin user so you can explore its features.

You will need to use the demo user, or create a new user, to create and deploy instances.