-
Notifications
You must be signed in to change notification settings - Fork 37
Roadmap for Cellery 0.2.0 (Released)
Cellery 0.2.0 will be released on 11th of April 2019. Below are the features that will be included in this release.
Currently, the cells can have components that expose backend HTTP APIs. But an enterprise application is not complete without having support for frontend applications such as React Application, WebApp based on JSP, PHP, etc. Therefore cellery should be able to support web ingresses in a component. The web traffic for the component will be routed via Global Web Gateway, whereas the external backend API requests will be routed via the Global API gateway.
Web ingress may expose non-secured content or secured content. And hence it can be exposed via HTTP or HTTPS. Therefore cellery should support for secure web ingresses as well.
In order to permit the web traffic inside the cellery system, and provide the SSO login flow, it's required to have a global web gateway.
A lightweight IDP is required for cellery system components such as APIM, and observability to provide access control. This will also be used by Global Web Gateway to provide the SSO flow.
Cellery run commands will start the instance of an image, and optionally users can provide the list of depending cell instance names as command line arguments. If the dependent instances are not up and running, then cell instance cannot be started, and it will fail. Therefore we introduce --start-dependencies flag to start the dependencies recursively if those are not already started, before starting the intended cell.
The current cellery file can contain the docker image name, and this feature allows users to have the docker file path as well. Therefore, when cellery build is performed, the relevant docker file will be built first and consequently, cellery image will be built.
This includes below improvements
- Remove ballerina.io package from cellery init file
- APIDefinition struct, read swagger file and generate API Defintion
- Rename HttpApiIngress
- Remove 'public' from access modifiers
- Rename exposeGlobalAPI -> exposeGlobal
- Rename exposeIngressFrom -> exposeLocal"
Cellery installation should install only cellery controller along with istio components. This will have a very minimal system requirement for cellery installation, therefore local setup will become a more lightweight.
As the minimum cellery installation only consist of cellery controller, users should be able to optionally select and install other system components such as Global APIM and Observability.
Once the cell images are built, the users should be able to graphically visualize the cells it's depending on, and the components within the cell. This also should be possible with the cell images that were pulled from cellery repository.
The CLI commands will be revamped such that is will have more consistency.
Users can log in to cellery hub, and therefore they need to provide the user details every time they try to push the cell image to cellery hub.