Mirantis OpenStack

  • Download

    Mirantis OpenStack is the zero lock-in distro that makes deploying your cloud easier, and more flexible, and more reliable.

  • On-Demand

    Mirantis OpenStack Express is on demand Private-Cloud-as-a-Service. Fire up your own cloud and deploy your workloads immediately.

Solutions Engineering

Services offerings for all phases of the OpenStack lifecycle, from green-field to migration to scale-out optimization, including Migration, Self-service IT as a Service (ITaaS), CI/CD. Learn More

Deployment and Operations

The deep bench of OpenStack infrrastructure experts has the proven experience across scores of deployments and uses cases, to ensure you get OpenStack running fast and delivering continuous ROI.

Driver Testing and Certification

Mirantis provides coding, testing and maintenance for OpenStack drivers to help infrastructure companies integrate with OpenStack and deliver innovation to cloud customers and operators. Learn More

Certification Exam

Know OpenStack? Prove it. An IT professional who has earned the Mirantis® Certificate of Expertise in OpenStack has demonstrated the skills, knowledge, and abilities needed to create, configure, and manage OpenStack environments.

OpenStack Bootcamp

New to OpenStack and need the skills to run an OpenStack cluster yourself? Our bestselling 3 day course gives you the hands-on knowledge you need.

OpenStack: Now

Your one stop for the latest news and technical updates from across OpenStack ecosystem and marketplace, for all the information you need stay on top of rapid the pace innovation.

Read the Latest

The #1 Pure Play OpenStack Company

Some vendors choose to “improve” OpenStack by salting it with their own exclusive technology. At Mirantis, we’re totally committed to keeping production open source clouds free of proprietary hooks or opaque packaging. When you choose to work with us, you stay in full control of your infrastructure roadmap.

Learn about Our Philosophy

Integrating OpenStack Nova-network with Infoblox IP Address Management

on October 7, 2012

What is Infoblox?

I think everybody reading this post knows or has heard about such network services as DNS and DHCP. These are core services and they are used everywhere. In a virtual environment such as OpenStack they built into the foundations.

Infoblox is an appliance-based, integrated DNS, DHCP, and IP address management product that solves a growing, critical problem in enterprise networking: keeping core network services infrastructure running nonstop. Infoblox also provides automatic network control solutions to enable cloud readiness all across your network.

You may want to use Infoblox with your OpenStack cloud to help make network address management more productive, stable and secure.

Nova-network and how it works

At the moment, nova-network is the daemon that deals with network configuration of host machines. It also provides virtual networks to enable instances to interact with each other and with the public network. Every instance is assigned to a private IP address from each nova-network service. These IP addresses are called fixed IPs, and OpenStack uses the term floating IP to refer to an IP address that can be dynamically added to a running instance.

Currently Nova supports three kinds of networks, implemented in three types of network managers:

  • Flat Network Manager

Each instance receives a fixed IP from the pool and all instances are attached to the same bridge by default. The bridge must be configured manually, while the networking configuration is injected into the instance before it is booted. And there is no floating IP feature in this mode.

  • Flat DHCP Network Manager

All instances are attached to a single bridge on the compute node. In addition, a DHCP server is running to configure instances. OpenStack starts a DHCP server to pass out IP addresses to VM instances from the specified subnet, in addition to manually configuring the networking bridge. Instances receive their fixed IPs by doing a dhcpdiscover. Moreover, a floating IP feature is provided.

  • VLAN Network Manager

In this mode, Nova creates a VLAN and bridge for each tenant. The project gets a range of private IPs that are only accessible from inside the VLAN. A DHCP server is started for each VLAN to pass out IP addresses to VM instances from the subnet assigned to the project.

The latter two use dnsmasq as the DHCP server, and the nova-network service is responsible for starting up dnsmasq processes. Dnsmasq serves the virtual machines’ requests and sorts out their issues. That’s why dnsmasq is an isolated system in some ways.

With DNS, for every instance in the OpenStack cloud, there is a “name-address” pair and a group of managers that publish information to the DNS server if it is used (there no special DNS server for working with virtual machines by default). In order to enter these instances from the outside world, we needed a tool.

Address management in OpenStack

We decided to fix this and make some changes in nova architecture to use Infoblox or something similar for this purpose. You can find our implementation here.

The first step is to switch from dnsmasq as the provider of DNS and DHCP services, so we created a special hierarchy with just a DHCP driver in root for this purpose. Our solution lies in using different drivers for different DHCP and DNS servers, and Infoblox can be one of them.

To do so, you create drivers to manage Infoblox DHCP and Infoblox DNS, which makes communication between nova-network and Infoblox possible. Thus, if you want to expand your cloud network configuration options and use something other than dnsmasq, Infoblox may be just what you need.

2 comments

2 Responses

  1. R. Krishna Kumar

    Can you please tell us in detail how you have achieved this. Is there only a configuration file change or code change needed to integrate infoblox with OpenStack.

    February 25, 2013 04:45
  2. Yury Taraday

    Hello. Have you seen my post with details about Infoblox-related Nova configuration?

    March 12, 2013 10:24

Some HTML is OK


or, reply to this post via trackback.