3d753a48d2
- Mock-Webserver v2.2.0 - Vendor, defined dependency bcprov-jdk15on > Previously, the dependency got excluded; otherwise, it conflicted with the existing bouncy castle version used in JClouds. - Mock-Webserver v3.14.9 - The vendor does not define a bouncy castle dependency anymore; instead, it moved to the okhttp-tls module. - Introduce the okhttp-tls module for tests in the core module. The following APIs (Docker, Elastic-Stack) and providers Softlayer extend their respective MockTest from BaseMockWebServerTest. The mock base test is located in the test jar of JClouds core module. - Due to conflicting bouncy castle classes in the classpath, those which get loaded from the okhttp-tls module, and those defined in JClouds bouncy castle module, the bouncy castle dependency of okhttp-tls has to get skipped for the two APIs and providers mentioned. Side note: The JClouds GAE driver module also requires the new okhttp-tls dependency because of the following chain of inheritance. Different from the situation above, the bouncy castle classes of the okhttp-tls got not excluded. GaeHttpCommandExecutorServiceIntegrationTest -> BaseHttpCommandExecutorServiceIntegrationTest -> BaseMockWebServerTest The reason for this is unknown to me.
Docker as a local cloud provider
jclouds-docker is a local cloud provider modelled on docker. Similar to other jclouds supported providers, it supports the same portable abstractions offered by jclouds.
Setup
Please follow these steps to configure your workstation for jclouds-docker:
- install the latest Docker release (please visit https://docs.docker.com/installation/)
- enable remote access to Docker
Sample configuration for Linux systems using systemd
Run following commands on a machine where is the Docker Engine installed.
It enables remote access (plain TCP - only for loopback address 127.0.0.1)
on standard port 2375.
# switch to root account
sudo su -
# create override for docker start-script
mkdir /etc/systemd/system/docker.service.d
cat << EOT > /etc/systemd/system/docker.service.d/allow-tcp.conf
[Service]
ExecStart=
ExecStart=/usr/bin/docker daemon -H fd:// -H tcp://
EOT
# reload configuration and restart docker daemon
systemctl daemon-reload
systemctl restart docker
# close the 'root' session
exit
If the -H fd:// Docker daemon parameter doesn't work on your Linux (e.g. Fedora),
then replace it by -H unix:///var/run/docker.sock
Find more details in Control and configure Docker with systemd guide.
Running live tests
The DOCKER_HOST environment variable has to be configured as it's used as a value for test.docker.endpoint system property.
export DOCKER_HOST="http://localhost:2375/"
mvn -Plive integration-test
Notice, if you are using Docker for Mac, Docker Remote API may not be available over HTTP.
In the [Known issue]{https://docs.docker.com/docker-for-mac/troubleshoot/#known-issues) Docker team recommend to use socat
to expose docker.sock over tcp. You may find useful the following simple commands:
docker run -d -v /var/run/docker.sock:/var/run/docker.sock -p 127.0.0.1:1234:1234 bobrik/socat TCP-LISTEN:1234,fork UNIX-CONNECT:/var/run/docker.sock
and then
export DOCKER_HOST=http://localhost:1234
mvn -Plive integration-test
How it works
--------------- -------------
| Image(s) | | Node(s) |
--------------- -------------
--------- docker remote api ----------------------------------------
| jclouds | ---------------------------> | DOCKER_HOST |
--------- ----------------------------------------
Components
- jclouds - acts as a java client to access to docker features
- DOCKER_HOST - hosts Docker API, NB: jclouds-docker assumes that the latest Docker is installed
- Image - it is a docker image that can be started.
- Node - is a docker container
Assumptions
- jclouds-docker assumes that the images specified using the template are ssh'able.
Notes:
- report any issues you find at jclouds issues
- jclouds-docker has been tested on Mac OSX and Linux. However, it has never been tried on Windows.
Troubleshooting
As jclouds docker support is quite new, issues may occasionally arise. You can try to remove all containers to get things going again:
docker rm -f `docker ps -aq`