* Update the function, such that when subnet_id is null, then based on
the vlan, grab the details from the subnets defined, and update the
links based on this. This ensures that all subnets are auto-assigned
and the externel_vlan is dhcp from the upstream network
* Revert the network_auto function, as the above change would help with
the issues we faced before
* Update all the maas function calls, and assign them to a variable or
direct the output to /dev/null, as we don't want the screen to be
filled with all the information
TODO: Have viable output to the CLI, so that you have some details of
what is going on
* So that all the networks now will have be either static, auto or dhcp
* network_auto will not work out of the box, it can only effectively
work after commissioning of a machine
* Move stuff from common to default, as it didn't make sense
* use virsh_user instead, that was its more customisable
* Revert the change to manage-maas-nodes.sh now use extra function to
call maas_auto_assign_networks instead
* More comments to the code
* Move all configs into config directory
* Move all examples into example directoy
* Move all common functions into functions.sh
* Fine tune a few other functions
* Moved common hypervisor config away
* Added examples for some of the hypervisor configs
* Start work on snap enablement of boostrap-maas.sh script
* Make the variables consistent across all the functions
* build_fanout instead of build_timeout
* Release machine in maas, if we're wiping the disk for re-using
* Move the for loop to check for machine being ready into a function,
so that it's re-usable
* Update some formatting fixes to README.md
* Use the maas snap for the maas-cli stuff, as there is no recent maas-cli deb
* update the way to tag a node, which now works
* put back the double ampersand for creating the VM
* The script now adds N control nodes at the beginning
* Adds 4 extra interfaces, VLANs in my environment
* Adds the VMs to MAAS, commissions them, and updates the interfaces.
* Add a function that just wipes the VM disks, for re-purposing.
This allows to release the machines in MAAS, and then re-use them
without having to re-add/commission the machines.
