I am trying to get a private cloud running in a test environment with the use of virtual box, there have been a number of sites I have seen where this is a possibility. If this test is successful it's a real possibility that my organization would deploy this in a true production environment.
5 - VirtualBox VM's (I realize I will need to add two more nodes before I can truly use openstack, but I need one working node before I start anything else.... Servernames:
- server-maas1 (Maas master)
I have manually booted each VM node with 12.04 ISO, and selected Ubuntu with maas, followed the normal steps, and enlist with server-maas1 (which it does discover server-maas1) Once selected it sigkills and shutdowns. (This I gathered is normal) Server-maas1 updates to display the node declared (I have done this on the other 3 nodes as well) So server-maas1 indicates I have 4 nodes, but never seen.
I proceed to accept and commission each node, as well as change to wake-on-lan. Note: I am not using maas-dhcp, as there is a DHCP server running on my current network. All nodes are in a "commissioning" state. None of the node detail pages contains a "start node" button to try to PXE boot these VMs.
All of these VirtualBox VMs are in fact using bridged adapter (and Promiscuous mode set to Allow All, Boot Order indicates Network boot first, Adapter type (Intel Pro/1000 MT Desktop (82540EM).
At this stage I am pretty much stuck. So moving forward a few steps:
Juju is running on server-maas1, here are the
evironments: maas: type: maas maas-server: 'http://172.16.41.12:80/MAAS' maas-oauth: 'My API Key' admin-secret: 'nothing' default-series: precise
I get a 409 error after trying to bootstrap this. I assume this is a because of more than one reason. DNS settings of some sort? Nodes are not working with MAAS correctly etc.
I believe most of my problems are caused by not running maas-dhcp, but I do not have the luxury to run maas-dhcp on this environment. According to this https://wiki.ubuntu.com/ServerTeam/MAAS, under the heading "Installation and initial set-up"
How you install and run MAAS depends largely on whether you have control of the network you're using.
In this guide, we'll look at two common scenarios:
You own the network: you own the network you're connecting to and you're happy to let MAAS own that network's DHCP. You're experimenting while using someone else's network: you can't allow MAAS to own the network's DHCP. We'll look at both of these ways to run MAAS.
Well the "You're experimenting while using someone else's network:" is never explained. Is this not an option right now?