Ubuntu Openstack install step 6: Ubuntu Linux MAAS commission nodes

14 thoughts on “Ubuntu Openstack install step 6: Ubuntu Linux MAAS commission nodes”

• why i have this prblems
  Error: No storage information. Commissioning this node will gather the st
  Error: Specify a storage device to be able to deploy this node.
  Error: Mount the root '/' filesystem to be able to deploy this node.
  Error: Failed to login to virsh console.
  please help mee i need finish my tesis :´(

• Thank you. These tutorials are very good.

  I have a question.

  My first note successful loading image from MAAS server. After then the note automatically shuts down. I think it's the same situation your tutorial, but I can't start from my MAAS server by using Commissioning command. This commissioning processing, loading long time, but that note not turn on. How to fix this error and what config am I missing?

  My MAAS server version is different your using version ?

  https://dl.dropboxusercontent.com/u/17601667/MASS.png

  I am using this tutorial – http://www.openstackbasement.com/home –

• Question:
  Your hardware, you mentionned "dell 780" , are they
  OptiPlex 780 ? and you have 7 of them, am I right? how much RAM on them? (btw I search docs and wanna have you confirming you're using non-ecc RAM)

• Router IP: 192.168.1.254
  MAAS SERVER IP: 192.168.1.134

  There is no proxy between internet. I am having the following error:

  Error log follows–changed http to xhttp to avoid link quota issues]
  Reading package lists…
  Building dependency tree…
  Reading state information…
  The following extra packages will be installed:
  libperl5.18 libsensors4 libsnmp-base libsnmp30
  Suggested packages:
  lm-sensors snmp-mibs-downloader snmpd
  The following NEW packages will be installed:
  libperl5.18 libsensors4 libsnmp-base libsnmp30 lldpd
  0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1144 kB of archives.
  After this operation, 4566 kB of additional disk space will be used.
  Err xhttp://archive.ubuntu.com//ubuntu/ trusty/main libsensors4 amd64 1:3.3.4-2ubuntu1
  Could not connect to 192.168.1.134:8000 (192.168.1.254). – connect (111: Connection refused)
  Err xhttp://archive.ubuntu.com//ubuntu/ trusty/main libperl5.18 amd64 5.18.2-2ubuntu1
  Unable to connect to 192.168.1.134:8000:
  Err xhttp://archive.ubuntu.com//ubuntu/ trusty/main libsnmp-base all 5.7.2~dfsg-8.1ubuntu3
  Unable to connect to 192.168.1.134:8000:
  Err xhttp://archive.ubuntu.com//ubuntu/ trusty/main libsnmp30 amd64 5.7.2~dfsg-8.1ubuntu3
  Unable to connect to 192.168.1.134:8000:
  Err xhttp://archive.ubuntu.com//ubuntu/ trusty/universe lldpd amd64 0.7.7-1
  Unable to connect to 192.168.1.134:8000:

• hi +openstackbasement,

  uptil step 5 i am doing ok. I can PXE boot my node and it gets add up i can even use WOL on first instance (between commissioning to ready status) during this time the system powers off and the system is in ready state. Now, here i get the problem my system shows the same power issue as before commissioing state after i pit it back on WOL as before from MASS i am unable to boot it Can you help me out in this regard. I am using DELL R520 machines as nodes and as MAAS server

• We reached to the step where we need to ping and nslookup. We aren't able to ping google.com and we are able to nslookup it. However, we are able to ping the server and unable to nslookup it. Also, we are able to update and install packages. Are we on the right track??? Please say yes 😉
  Also, note that we removed the dns-nameservers from the interfaces file

• Thank you for your valuable information 🙂 I have a small question. Is it important to have two NICs? or can I use eth0 and wlan0 instead? In other word, can I manage to install openstack on Seven machines in which each one has only one NIC?

• Anybody else get stuck with WOL? My setup won't power on the machines or commission them once powered manually!

• When i tried to deploy its got deployment failed. When see through the monitor it shows a error cant connect to http://ppa.launchpad.net. Plz help

• This was very helpful. Everything went according to it is in this video. but when i ssh ubuntu@10.1.1.151 , it asks me to accept the key, i select yes, it says permission denied (public key). Although, I did save the public key in root preference of MAAS. So, im at a pause. Not sure what to do next.

• Hey !! I would like to know why did you run this command (sudo dpkg-reconfigure maas-cluster-controller) to put your private network interface ? and not keeping your public ip address ?

  I'd like to know more stuff about Juju because when I run "juju bootstrap from my maas server" he didn't want to boot a node. I've got this message:

  juju bootstrap –debug
  2015-05-22 08:56:27 INFO juju.cmd supercommand.go:37 running juju [1.23.3-trusty-amd64 gc]
  2015-05-22 08:56:28 DEBUG juju.provider.maas environprovider.go:28 opening environment "maas".
  2015-05-22 08:59:29 DEBUG juju.environs.configstore disk.go:342 writing jenv file to /home/tibo/.juju/ environments/maas.jenv
  2015-05-22 09:05:30 DEBUG juju.cmd.juju common.go:90 Destroying environment.
  2015-05-22 09:05:30 INFO juju.cmd cmd.go:113 Bootstrap failed, destroying environment
  2015-05-22 09:05:30 INFO juju.provider.common destroy.go:15 destroying environment "maas"
  2015-05-22 09:08:30 ERROR juju.cmd.juju common.go:32 the environment could not be destroyed: gomaasapi : got error back from server: 504 Gateway Time-out (<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

  any idea ?

• It changed the power to something else after commissioning. I changed it back to WOL and its installing now. We will see if it changes again. Might be a bug in the newest Maas software.

• Acquire and start node does nothing. No power on even though it was able to during commission.

• i get Error: Unknown power_type 'ether_wake'. when i change mine to wake on lan in the maas gui

Comments are closed.