Ability to add extra NIC's in AWS & GCP deployment

[ajohnson-aerospike]

Sometimes more than one NIC is needed, it would be a really useful feature if when deploying into AWS or GCP that you could specify the number of Network Interface Cards to be provisioned.

[robertglonek]

Can do, except the scope will be limited. See scope below. The reason for limitation is we are trying to avoid adding cloud network management in aerolab (GCP and AWS VPC, subnets) beyond the minimum required.

For GCP, can add a new interface and attach to the instance, but creating the second required VPC for this will be out of scope. User will have to create their own second VPC and then aerolab can be told which VPC to use.

For AWS, multiple subnets must already exist and Aerolab will have to create a second NIC. After this it will have to attach it, and remember to cleanup on cluster destroy. Aerolab will not be managing the subnets, but given a second subnet in a parameter, it can add multiple NICs in different subnets.

[robertglonek]

We can include NUMA configuration tweak if we do this, to auto-configure NUMA and multi-asd.