The MAAS root node has internet access available and is attached to both your LAN on eth0 (with internet access available) and your virtual network on eth1.

Those networks are physically connected and available to the host via separate wired interfaces. IP forwarding is used to route packets between the virtual machines and the LAN on the MAAS controller node.You may have one, especially in your production network. There are no firewalls between the internet and the MAAS nodes.Additional virtual networks necessary for Openstack are discussed later. The network model chosen for this lab deployment included three networks from the MAAS perspective. Then it’s time to roll our collective sleeves up and jump in. I’ll cover network aspects, then the hardware assumptions, then software requirements for the host system’s set up. For more comprehensive reading on Openstack architecture and layout, I recommend Piotr Siwczak’s discussion on Openstack deployment Topologies.įirst, I’ll outline a few assumptions based on my test set up. Make note this set up is purely for a functional model and has never been tested for performance. Simulated High Availability on VMWare Fusion or Workstation will be a future topic. The deployment is relatively simple with no High Availability. The goal of this guide is to provide a means to create a simple virtualized Openstack environment running on a single physical host such as a Mac Pro. There are many advantages including cost, flexibility in deployment models, and ease of use to name a few. VMWare Fusion provides an excellent host layer for functional testing. Are you wrestling with getting MAAS or Metal-as-a-Service up and running with Juju and Openstack in a private cloud environment? It’s much easier than you think.

Vmware fusion 8.5 on osx 10.8