New to MaaS, OpenStack & Juju.

[derwood2]

Heya Folks,

While I'm new to the community of Ubuntu, I would just like to say "hi"

I have myself a copy of both server version of Ubuntu 14.4 and 16.4 both LTS versions, I'm having some nightmares here for the last week and I'm feeling at a loss with the ease at which the almost single page installation, quick setups for getting MaaS, OpenStack and Juju installed and running. I'm even awaiting for contact from Ubuntu Advantage because I love the idea of getting some support here and in the long term too.

Firstly I have a setup exactly like this:

Region and cluster controller:
DELL FS12-NV7 x 1
dual socket quad core 2372 EE
16 GB RAM
160GB HDD
Dual 1Gbit NICs
IP: 192.168.0.3

Nodes:
DELL CS24-NV7 x 4 (This number will grow to around ten to fourteen)
Dual socket quad cores 2373 EE
16 GB RAM
2x 80GB HDDs
Dual 1Gbit NICs
IP | DHCP

Networking:
8 port Gbit switch

Home Router:
192.168.0.1

it's all fairly simple, my home router has a link to a port on my switch, the region/cluster controller has port two and each node has a port then on after that, if I install 14.4 server edition, then MaaS WoL never finds a node ever but it appears OpenStack and Juju would install fine from launching the commands to install and configure, I can even make an SSH key and it works, but I cannot add any more MaaS APIkeys.

Trying to install 16.4 LTS with MaaS 2.0 always finds the nodes, I can do as I please with them and it's a simple process, but trying to install OpenStack or Juju never turns up much at all, even trying conjure-up using any setting offered always dies and can never bootstrap, I also cannot add an SSH key ever, but I can create as many MaaS APIkeys as I wish.

I've been playing with this for a complete week, using all means before me from finding documentation online, work arounds, commands to get me a little further.. Anything.

So far work around commands come in all shapes, always best to install just the server first then edit the locale file so that it has LC_ALL=C, this seems to prevent the databases from messing up later on when you're installing OpenStack, juju and other SQL style databases,

I really need some help here, I would just simple like to at least have a single physical server (region/node controller) and a set of four nodes set-up without playing around with VM installs, Would anyone like to walk and talk me through from the initial inserting the .ISO in the drive up until it's all working. I would even be happy to pay a fee to someone willing to help me out.

At the end of the day the whole idea of me doing this was to be able to launch a VM on my laptops or from my workstations that could use all available RAM,Compute resources when I require while also being able to launch other VMs here and there for doing tasks.. So I'm at a bit of a loss here currently.

Thanks to anyone that can help me out with my personal private cloud mess..

[derwood2]

I was just thinking about a fee to someone for helping me out?

How would £10GBP per hour until whichever Ubuntu 14.4/16.4LTS along with MaaS either 1.9/2.0, with all nodes, Openstack and Juju are installed and we can get a few VM instances running to do as I wish?

I'd be happy to do this via the internet using video skyping and would be willing to donate a further 10GBP to Ubuntu for supporting the community further.

[derwood2]

That should bring you up a display like below..


Now what we should do is “enable DHCP” you can do this by clicking on the “take action” orange button.




it's given us these simple options and I've applied them



Now I'm going back to the “nodes” page and going to see if I can start a node up by pressing the power button, if nothing comes of anything, I shall manually input the MAC address of the node and restart that idea again



WOW!, my node is already set to PXE boot once I press the power button, fired up straight away, then turned off.. I see this as being normal and it's just getting to know the MaaS region/rack controller.


So I go and click on the node that's showing in the “nodes” page, and I need to edit it's name so I just click top left and upon the name to rename it!




Also I need to edit it's power type, I want this to be “manual” like below..



Now I need to repeat what I have done, on the same amount of nodes I currently have, that being three of exactly the same machine.. chip for chip!


Node002: Does not want to come up, it's trying to boot but showing


“IP-Config: enp0s8 hardware maas -enlist hostname maas-enlist IP-Config: no response after 9 seconds – giving up”


I've tried it twice, to boot now, so I will enter that manually after I have tried my last node..

-Node3 has done exactly as it should, and the same as node one.. Come-up, been noticed and gone down..


Even though all three nodes are exactly the same down to their motherboard, and even including the exact same setting within the BIOS something is a miss here..


So node 2 I shall, manually add in and see what comes of it..


I just tried node002 again, just out of interest, and it turned out to work this time! Third time lucky!
Edited the name and edited the “manual” power setting too..



So it appears we can find all the nodes I have, now to “commission” them..



now all machines are showing as ready..



After this we need to install “Autopilot”, “OpenStack”, “Juju” Simple.. But is it...

[derwood2]

This is what I have done the last two hours..

Firstly, install Ubuntu 16.4LTS server edition with nothing apart from at the “choose software to install screen” selecting:


*standard system utilities
*OpenSSH Server
*Virtual Machine Host


once installed open an SSH link to the server IP, login, sorted a server install is comlete at the base..


now using this link:
https://maas.ubuntu.com/docs/install.html


it alerts me that to install MaaS I need to type in these commands as follows below:



*But just before that type in sudo nano /etc/defaults/locale and then enter this into the file CTRL+O, return, CTRL-X to exit..
LC_ALL=C


then carry on with below to save an issues with database issues..


Adding MAAS package repository is simple. At the command line, type:
$ sudo add-apt-repository ppa:maas/stable You will be asked to confirm whether you would like to add this repository, and its key. Upon configumation, the following needs to be typed at the command line:
$ sudo apt-get updateInstalling a Single Node MAAS

At the command line, type:
$ sudo apt-get install maas
post install requires you to create an admin MaaS account using this command:
sudo maas-region-admin createadmin
and fill in what required...



didge@WOPR:~$ sudo maas createadmin
Username: root
Password:
Again:
Email: dar@URL.co.uk
didge@WOPR:~$


If you tried to login in to IP/MAAS prior to this you'll see a screen telling to to make a user, like below..




First lets start downloading some “images” for the nodes, like below:


Takes a little while, so lets setup the account. My HomeRouter has the IP of 192.168.0.1, my MaaS region/rack controller is 192.168.0.3 and each of the nodes will be getting their IP from the 192.168.0.1(HomeRouter)
Goto “Networks” and click on the main IP address for the NIC like below where highlighted.


After clicking on the highlighted IP you should see a screen like this.




Seems fairly simple
here its marked “Gateway IP” you would add the MaaS server IP
(192.168.0.3) and in the DNS field you want (192.168.0.1) because
that si the HomeRouter handing out IP addresses for everything linked
inside the home network.
So lets try it..

Check on the images that have been downloading, they might have finished by now:


Just leave all that
as it is for now..

*Just to note
NIC 0 MAC address: 6c:f0:49:68:b7:** (DHCP 192.168.0.3)

NIC 1 MAC address: 6c:f0:49:68:b7:** (Unconfigured)



Under the “networks” button click on the first fabric option because this will most likely be your main NIC and where it says “VLAN” and below that “untagged” highlight it and click it like below.