Role-Based Configuration

A typical OpenStack deployment consists of network nodes, controller nodes, and hypervisor nodes, each of which is also typically associated with a set of default role assignments.  Bright OpenStack embraces this concept, and empowers it with the idea of role assignments. Administrators can easily customize which exact OpenStack services are to be run on controllers, and which on network nodes.  This makes small clouds easy to configure, but also makes it possible to create complex configurations, like a cloud with different types of controller nodes.

Bright’s easy and flexible handling of OpenStack role assignments enables users to respond nimbly to changes in resource allocation and usage.  Whether these changes occur slowly, over time, or immediately due to something like a usage spike in a specific service, Bright users can simply switch roles over to cover the new requirements set.    

Once the OpenStack instance is up and running, Bright makes it easy to monitor both nodes and associated roles, keeping an eye on all resources and how they are assigned within the OpenStack environment.