“Maas with power type for VMware ESXi on Ubuntu 16.04 LTS Server Edition”

ubuntu-16-04-lts

UBUNTU SERVER

1 STEP – INSTALL LIBVIRT ON MAAS

To allow to Maas to be able of doing the boot system for the nodes created on VMware ESXi, we need to do some tasks. As first think it’s necessary to install libvirt on our Maas server with the following command:

$: sudo apt-get install libvirt-bin

In order way to use the SSH service on nodes, on Maas an SSH private key has to be generated and then uploaded it to our host:

$: sudo mkdir -p /home/maas
$: sudo chown maas:maas /home/maas
$: sudo chsh -s /bin/bash maas
$: sudo su -u 
$: ssh-keygen -t rsa -b 4096
Generating public/private rsa .....
.....
....

Then copy the public key to /root/.ssh/authorized_keys2 on our host

$: ssh-copy-id -i ~/.ssh/id_rsa dakj@10.20.40.16
.....
.....
Number of key(s) added: 1
Now try logging into the machine, with:   "ssh 'dakj@1.1.110.1'"
and check to make sure that only the key(s) you wanted were added.

Finally we can test the connection toward VMware ESX:

$: virsh -c esx://root@10.20.253.180?no_verify=1 list --all
setlocale: No such file or directory

Enter root's password for 10.20.253.180: 
 Id    Name                           State
----------------------------------------------------
 -     Ubuntu Linux Landscape Node00  shut off
 -     Ubuntu Linux MaaS - 10.20.81.10 shut off
 -     Ubuntu Linux Openstack Node 01 shut off
 -     Ubuntu Linux Openstack Node 02 shut off
 -     Ubuntu Linux Openstack Node 03 shut off
 -     Ubuntu Linux Openstack Node 04 shut off
-----------------------------------------------

Then, we can configure our node to do the boot type with Virsh, the line of adding is the following:

esx://root@10.20.253.180?no_verify=1

while on node will appear that:

Screen Shot 2017-05-26 at 17.03.46

save that and run the commit, at the end our node will be in Ready status.


 

“cya to the next 1…. Njoy !”
bye dakj

Disclaimer: All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.

“We learn from our mistakes”

Advertisements