The egoscale binding for exoscale was limiting the images that could be
selected by a user to Ubuntu one only. Enable the use of arbitrary
images. For example, the following images are now available:
- centos-6.6
- centos-7.1
- coreos-stable-835
- debian-7
- debian-8
- ubuntu-12.04
- ubuntu-14.04
- ubuntu-15.10
The default user for non-Ubuntu images are not "ubuntu". Let the user
choose the appropriate user ("core" for CoreOS and "debian" for Debian).
CoreOS user are likely to want the ability to provide custom user data
as it enables the configuration of the etcd cluster. We add an option to
provide custom user data file. Moreover, we remove some of the default
options as they are not supported in CoreOS and are useless on
Debian/Ubuntu:
- Resizing of rootfs is already done on all images by default.
- Docker Machine will set the hostname as part of the provisioning.
Signed-off-by: Vincent Bernat <Vincent.Bernat@exoscale.ch>
This flag creates Azure VMs with static public IPs that don’t
get released when the VM is deallocated.
Signed-off-by: Ahmet Alp Balkan <ahmetalpbalkan@gmail.com>
Added flag `--generic-engine-port` to `generic` drive in order to specify other port than `2376` on
Docker engine.
Updated `generic` driver documentation.
Signed-off-by: Tiago Pires <tandrepires@gmail.com>
- Default image now is ubuntu server 15.10. This ensures consistency with
other cloud drivers.
- Better error message when virtual machine already exists.
- Change default SSH user from `ubuntu` to `docker-user`.
Signed-off-by: Ahmet Alp Balkan <ahmetalpbalkan@gmail.com>
The new driver uses Azure Resource Manager APIs and offers a lot
more functionality compared to the old Azure driver. It is also
easier to authenticate and does not require user to create and place
certificate files. It only has a single required argument.
This is a breaking change: The new driver cannot work with machines
created with the older Azure driver and vice versa (as the APIs are
entirely different and resources are not shared between old/new azure
APIs).
The new driver addresses many issues about the azure driver reported
so far.
This resolves#2742, resolves#1368, resolves#1142, resolves#2236,
resolves#2408, resolves#1126, resolves#774.
Signed-off-by: Ahmet Alp Balkan <ahmetalpbalkan@gmail.com>
With VirtualBox 5.0.14r105127, 'virtio-net' is not a valid name for the option. The correct option appears to be 'virtio'.
Signed-off-by: Michael A. Smith <michaels@syapse.com>
When connecting to single ESXi host (opposed to vCenter) --vmwarevsphere-datacenter has to be set to "ha-datacenter"
Signed-off-by: Dalibor Petras <dalibor.petras@flowconnect.com>
Some AWS API failures are retryable, so we should give the option to attempt
retries in these cases. One particular example is the API rate limiting that
kicks in if you try to create many machines in parallel. Without this change,
I can only create ~3 machines in parallel, but with this change I can easily
create 10 or more machines in parallel.
While this change helps `ls`, given the current fan-out model for plugins, once
you get a large number of AWS machines, you'll still wind up seeing
"RequestLimitExceeded: Request limit exceeded." errors.
Signed-off-by: Daniel Hiltgen <daniel.hiltgen@docker.com>
fixes#1904 Non EbsOptimized instances will be created by default but adding the flag
UseEbsOptimizedInstance will create and EBSOptimized Instance if the instance type supports it.
Signed-off-by: Jeffrey Ellin <jeff@ellin.com>
