* checkConfig is no longer a thing.
* Change the default Rackspace image to Ubuntu 14.04.
* Remove an unnecessary Network service.
* Show a nicer error when the Region is omitted.
Signed-off-by: Ash Wilson <ash.wilson@rackspace.com>
Boolean flag to indicate if docker have to
be installed on the machine. Useful when
docker is already installed and configured
in the OpenStack image. Default set to `true`
Signed-off-by: Guillaume Giamarchi <guillaume.giamarchi@gmail.com>
Otherwise, they interfere with the output of `machine url` and `machine ls`. `machine url`
is more important because it breaks the export statement to configure docker if it includes
additional output.
Signed-off-by: Ash Wilson <ash.wilson@rackspace.com>
* Use the initialized client
* Fix the endpointType conditional
* Don't die if OS-EXT-IPS is not present
* Only log Openstack creation for Openstack drivers
* There's no option for MachineName, yet
Signed-off-by: Ash Wilson <ash.wilson@rackspace.com>
Otherwise, because of the way Go does method dispatch, derived versions of
those methods will never be called.
Signed-off-by: Ash Wilson <ash.wilson@rackspace.com>
* Wrap openstack.Client in an interface.
* Alternate openstack Driver creation method.
* Register the Rackspace driver in commands.go.
Signed-off-by: Ash Wilson <ash.wilson@rackspace.com>
When sourcing an OpenStack rc file, both variables OS_TENANT_ID
and OS_TENANT_NAME are defined.
Signed-off-by: Vincent Giersch <vincent.giersch@ovh.net>
Several requirements for storing registry data have been compiled and the
backend layout has been refactored to comply. Specifically, we now store most
data as blobs that are linked from repositories. All data access is traversed
through repositories. Manifest updates are no longer destructive and support
references by digest or tag. Signatures for manifests are now stored externally
to the manifest payload to allow merging of signatures posted at different
time.
The design is detailed in the documentation for pathMapper.
Signed-off-by: Stephen J Day <stephen.day@docker.com>
Detecting tar files then falling back for calculating digests turned out to be
fairly unreliable. Likely, the implementation was broken for content that was
not a tarfile. Also, for the use case of the registry, it is really not needed.
This functionality has been removed in FromReader and FromBytes. FromTarArchive
has been added for convenience.
Signed-off-by: Stephen J Day <stephen.day@docker.com>
By adding some better error checking on `store.GetActive`, we can stop
getting panics on some commands
Signed-off-by: Simon Thulbourn <simon+github@thulbourn.com>
It turns out, that we only stored the actual disk inside the data store,
this brings it back inline with vmware
Signed-off-by: Simon Thulbourn <simon+github@thulbourn.com>
