We are pleased to announce the GA of MetroÆ v3.0.3 and the corresponding Docker container v1.0.2.
There are two changes.
- For MetroÆ, someone in the field discovered that our schema validation was forcing the yum_proxy setting in common.yml to be of format `hostname`. This is incorrect because a yum proxy should be of the form `https://hostname.domain:port`. This is the only change you will find in v3.0.3.
- For the Docker container, we discovered that under certain conditions we were not properly handling the container’s ssh keys. This bug involves the way the container is built, not any MetroÆ code. We fixed the build and have added an automated test to capture this problem in the future.
You can access MetroAE via guthub, as always:
If you want to use or update to the latest container, follow these steps:
- ./metroae destroy
- ./metroae pull
- ./metroae <install_everything or some other command>
The last line will start your container automatically using the same data and image directories you provided during the original setup. You will just be able to pick up where you left off with no loss of data.
More details for Docker container operation can be found in Documentation/DOCKER.md in the github repo.