CHANGELOG.md 4.3 KB
Newer Older
1 2
# Zoe Changelog

3 4
## Version 2017.06

Daniele Venzano's avatar
Daniele Venzano committed
5 6 7 8
* ZApp description format revision
* use JSON schemas to validate ZApps
* Expand the execution list API, adding filtering capabilities to limit the number of results returned
* Several minor bug fixes
9 10 11 12 13 14
* Deployment scripts and zoe frontend moved to external repository for easier maintenance and testing
* Removed proxy code
* ZApps have been split into multiple repositories for easier maintenance, testing and automated building
* Tyk or Kong can be used to provide SSL termination and authentication to the API
* Documentation update
* A new script `create_db_tables.py` can be used to create the schema in an empty database, useful for CI scenarios
15

Daniele Venzano's avatar
Daniele Venzano committed
16 17 18 19 20 21 22 23 24 25
## Version 2017.03

* Major documentation update
* Deployment scripts to install Zoe on Linux (Kubernetes or Swarm back-ends) or Windows
* Kubernetes back-end
* Updated Swarm backend, uses the new Docker Python API
* Zoe code now goes through an automated testing pipeline
* Added unit and integration tests
* Preview of the new AngularJS front-end

26 27 28 29 30 31 32
## Version 0.10.2

* Documentation updates
* Log management bug fixes
* Fix a bug with the scheduler time trigger
* Sort by ID when listing execution from the command-line client

33 34
## Version 0.10.1

Daniele Venzano's avatar
Daniele Venzano committed
35 36
* Service discovery API endpoint: simple, read-only, unauthenticated access to a list of DNS names of services. Needed for frameworks that need a list of hosts for configuration, can be used by scripts in the images.
* Add `-s` option to the `start` command of the commandline client to have it wait for execution termination and stream the log meanwhile.
Daniele Venzano's avatar
Daniele Venzano committed
37
* Add the `workspace-deployment-path` option in the configuration file. It should be used when the workspace path should be build not with the deployment name, but with something else.
Daniele Venzano's avatar
Daniele Venzano committed
38 39
* All errors generated by docker while creating containers are now considered as fatal, except the "not enough free resource" one. When a fatal error is generated, Zoe will not try to start the execution again.
* Error messages generated by Docker are now exposed to the user
Daniele Venzano's avatar
Daniele Venzano committed
40
* (experimental) if the configuration option `service-log-path` is set, container output is saved from docker into the specified directory. If the logs are big, this can have a significant impact on execution termination time
41

42 43 44 45
## Version 0.10.0

* This version is the start of a new series of releases moving toward a new architecture
* Only one overlay network (created by the sysadmin) will be used by all Zoe executions. We provide Dockerfiles for SOCKS and SSHd containers that can be used to give users access inside the Zoe overlay network. These containers will no longer be managed by Zoe.
Daniele Venzano's avatar
Daniele Venzano committed
46 47 48
* Move the REST API in the web process and add a ZeroMQ-based API between the web and the master.
* Move all user management in the web process.
* Use Postgresql to store the state
49
* Rename the zoe-web component in zoe-api to better describe its new role
Daniele Venzano's avatar
Daniele Venzano committed
50
* User authentication can be performed by a CSV text file or via LDAP
51

52 53 54 55 56
## Version 0.9.7

* Check application description version during validation.
* Bump application description version to 2 since we are going to make some major changes in the format
* Add fields `total_count`, `essential_count` and `startup_order` to service descriptions.
57
* Comment code related to the parsing of cluster statistics from Swarm. The data returned by API changes too often and parsing it consistently is too complex. A bug is open on the Swarm issue tracker.
58 59 60 61 62 63 64 65 66 67 68 69

## Version 0.9.6

* Workspaces: Zoe now supports starting containers with a directory from the hosts mounted as a volume. The directory is private for the user and is not wiped when the Zoe execution terminates. There are some issues with file permissions when the container images define users with arbitrary UIDs.
* Add an error status and error message visible to the user when Zoe fails starting an execution
* Add a Docker Compose file to help test deployments
* The gateway container image is now configurable
* Move applications to their own repository (zoe-applications)
* Move the Zoe logger code into its own repository
* Update the stats module to the latest Docker version. Since the Python Docker API refuses to provide machine readable output, we have to stay locked to Docker versions
* Add date and time to log output produced by Zoe processes
* Expand the web interface, users can now list, start, terminate and restart executions