Add cluster support, different software provisioning

[rschmied]

• allow cluster deployments on AWS
  • create and use a non-default VPC
  • allow to enable EBS encryption (fixes #8) a cluster section has been added to the config file. Some keywords have changed (hostname -> controller_hostname). See also a new "Cluster" section in the AWS documentation
• use the CML .pkg software distribution file instead of multiple .deb packages (this is a breaking change -- you need to change the configuration and upload the .pkg to cloud storage instead of the .deb. deb -> software
• the PaTTY customization script has been removed. PaTTY is included in the .pkg. Its installation and configuration is now controlled by a new keyword enable_patty in the common section of the config.
• add a common script file which has currently a function to determine whether the instance is a controller or not. This makes it easier to install only controller relevant elements and omit them on computes (usable within the main cml.sh file as well as in the customization scripts).
• explicitly disable bridge0 and also disable the virl2-bridge-setup.py script by inserting exit() as the 2nd line. This will ensure that service restarts will not try to re-create the bridge0 interface.

[rschmied]

I'll consolidate the typos and will test the Azure cloud-init/netplan interaction. Also testing if I can add another ubuntu user to prevent the last cloud init module from failing (cosmetic...)

[orndor]

• allow cluster deployments on AWS

  • this also now uses a non-default VPC (fixes No support for custom VPCs #9)

Hi @rschmied. I wanted to clarify the request on No support for custom VPCs #9. Deploying to an available (i.e. existing) custom VPC was the original request, as AWS enterprise users will likely have VPC compliance mechanisms in place and preassigned, in-use IP space they'll need to fit this into.

Not objecting to this change going in as-is, but again, just wanted to clarify the original request if this pull request is the proposed fix.

[rschmied]

Thanks @orndor for the clarification. We’ll adjust. Either the “fixes” part or the code.

[rschmied]

@amieczko-te Iast commit regarding network configuration seems to work OK for me, both on Azure as well as on AWS. Removing the custom 00-cml2-base.yaml applies the configuration OK to the "physical" NIC. As we're not using bridge0 in cloud, it's safe to remove it, afaict.