Option for cloud-init or legacy customisation

[dbond007]

Right now customisation in vmware is being done via the legacy customisation.
Things like rancher need cloud-init to be enabled, this means the current setup will not work.
Reversing the changes fixes this for deploying nodes via rancher but doesnt work for deploying (at least in testing so far) in vmware.

An option should be present to set customisation type.

This config may link with the ansible issue, setting up via ansible instead of shell scripts.

[dbond007]

removed cloud-init completely in ubuntu as its causing problems now and then on boot when the 'fix' is applied in changing the startup dependencies in systemd. That has also been removed.