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>
+ exclude existing host-only nets from list of host interfaces
+ interface and mocks for system calls to net.*
Signed-off-by: Paul Callahan <paul.callahan@gmail.com>
If you already have docker machine cloned, or want to use an
existing workspace to clone it to, this helps with what your
GOPATH should be set to.
Also cleanining up the formatting of the previous block to
match others on the page.
Signed-off-by: Christy Perez <christy@linux.vnet.ibm.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>
This commit temporarily removes Azure driver and its dependencies
from the source tree and adds dependencies for the new Azure driver
(so that Azure driver PR will not have godeps changes and will be
easier to review).
Signed-off-by: Ahmet Alp Balkan <ahmetalpbalkan@gmail.com>
Maintains support for loading old Driver config.json that use the
singular `SecurityGroupName` field, but also adds a new plural
`SecurityGroupNames` field.
This change also bumps to latest stretchr/testify, in the course of
adding a dep on stretchr/testify/mock to help test the modified
`configureSecurityGroups` code.
The unused `deleteSecurityGroup` is dropped as well.
Signed-off-by: John Sirois <john.sirois@gmail.com>
Signed-off-by: Bill Farner <terasurfer@gmail.com>
Vincent Bernat