-
Notifications
You must be signed in to change notification settings - Fork 37
(Released) Roadmap for Cellery 0.4.0
Cellery 0.4.0 will be released on the 4th of October 2019. Below are the features that will be included in this release.
Cellery has support to run the existing tests written in any language with 0.3.0 release, where the tests can be included in the docker image and executed. In addition to that, with this release, the developers will be able to provide the inline tests along with the cell file. Here the telepresence and intended cell instances to be tested will be started first, then the tests can be executed against those cell instances, and finally the initiated instances can be terminated. Due to the telepresence, the cell instance can be directly accessed by URL.
Databases, caching servers, file system persistence for some artefacts, state, logs, etc are often used along with micro services. Hence it is required to claim the persistence from the kubernetes cluster for a component (e.g: micro services, database, or caching servers) in a cell (ie, stateful cell). From 0.4.0 Cellery, this feature will be included therefore the state of the component can be stored in a persistent storage, hence the updates/restarts/sclaing operations will preserve the states of the component.
Currently the configurations of a component are included via environmental variables where the hostname, and port of another component in a cell, or another cell’s API details are passed. But this is not always sufficient, and components often mount a configuration file, security token, password, etc. From Cellery 0.4.0, we provide support to attach both config maps, and secrets to the component.
So far the cells have a gateway, and network boundary around the components deployed in a cell the incoming traffic. But there are situations, where users or developers are skeptical about the additional hop for the gateway, and simply require a solution which allows to combine the components of their application together and deploy, and manage. This is packaging in cellery is called as Composite. And we will introduce the support for composites from 0.4.0 onwards.
Cellery 0.3.0 works with Istio version 1.0.2. There are many improvements and bug fixes are made for the latest Istio version 1.2.2. Therefore, Cellery 0.4.0 will upgrade its supported version to 1.2.2.
Currently we support WSO2 Micro gateway as the HTTP API Ingress. Due to performance improvements, and additional transport support, from Cellery 0.4.0 onwards we are going to allow envoy also as an HTTP API Ingress in addition to WSO2 micro gateway.
Improved version of Cellery Hub will be launched during Cellery 0.4.0 release. With this new update, users will be able to delete, modify the images, and organizations.
Cell updates, and route-traffic commands was introduced during cellery 0.3.0 release which helps to update a new version of a cell. Some improvements for the route-traffic command will be introduced, where the users can provide the header of the request by which target cell is determined. This is very helpful to provide a graceful update, and this will mimic the behaviour a sticky session and provide a consistent experience for the user irrespective of the update.
Cellery releases up to now were using WSO2 SP for observability, and directly publishes the telemetry without going through the mixer. But we realize that this will hinder the functionality of already existing adapters used with mixer. Therefore, Cellery 0.4.0 will also include WSO2 SP as a mixer adapter and collect the required telemetry information.