EN | ES
On January 15, 2021, the Release 2.3.0 of Onesait Platform (Immortal version) has been published, following our versioning policy: Version Policy onesait Cloud Platform).
You can follow our roadmap at Roadmap onesait Platform
Below you can see the main features of this release.
This version supports the development of microservices and all types of applications. To help in this type of development, the platform allows visual development with a LowCode approach incorporating a centralized web console that supports administration, configuration, development and deployment.
In this version we have incorporated important features:
- Centralized Log: This is a functionality that you had requested from us on different occasions and although the CaaS platforms already support this we have decided to incorporate a centralized log management solution. We have chosen to base it on Graylog, which is an open-source solution specialized in centralized log management and also takes advantage of the previous work that other colleagues did in the Onesait Revolution initiative (team onesaitplatform-revolution-onelog).
In this first version of the functionality the logs of the platform components have been centralized and it is indicated how to adapt the logs of other components (for example a microservice) allowing to make complete searches by component, time, type of log,...
In the next release we will integrate Graylog's UI into the Platform Control Panel.
You can find more information about this functionality en esta entrada.
- Keycloak Integration as Identity Manager Advanced: As you know, the platform includes an Identity Manager built on top of Spring Cloud Security that covers typical security use cases such as authentication, authorization, realms, plugins,... (more info here). In some cases we have detected that this functionality is not enough in the projects and products, for example when it is necessary to authenticate against multiple user and authentication provider repositories (user federation), integration with other IMs (identity brokering), customization of the authentication flow and sessions... So we have decided to incorporate Keycloak as an alternative Identity Manager for these scenarios and have chosen Keycloak for being a reference open-source solution in this field.
In this integration we have mapped the Keycloak Realms with the platform verticals, the Keycloak Clients with the Platform Realms and as default Provider we use the Platform ConfigDB (although LDAP can also be used).
Learn more about integration in this guide: Soporte a Keycloak como Identity Manager Avanzado
You can find a usage guide here: Generación de aplicaciones web Vue.js a partir de un diseño FIGMA
- (New) Centralized Configuration: Although this functionality already existed it was more intended to be used by platform administrators and internally by the platform. In this release the functionality has been remodeled so that developers can create their own configurations and also use them from their own microservices or applications
More information in the section: Central Configuration Guides
- Queries Export from Query Tool: Many of you were missing a utility that would allow you to export the data of a query made from the Query Tool in various formats, well here it is!
The utility allows you to export the results of the query in CSV and JSON, also if you are an administrator the limit of records that the platform configures will not be applied, so in a query you will be able to export all the data:
You can find more details in the section Query Tool Guides
- Caché at APIs:When defining an API on the platform, a caching interval (in minutes) can be entered as a configuration attribute:. This will be the time in which the records will be valid in the cache. Once this period of permanence is exceeded, the data origin information will be retrieved again.
You can see how this functionality works in detail: Caché en APIs
- Asynchronous import/export tool launch in this version we have improved the tool that allows you to export and import the platform elements so that the launch is asynchronous and so that those uncomfortable timeouts do not happen to you ;)
More information in the section Export-Import Tool Guides
- Several improvements (we listen to your requests) in this release we have incorporated several improvements that come from your requests (both as a ticket and from Delibera), some of them are
Pagination in Realms users list:
Configuration for not loading sample data in platform installation
Bulk support of upserts in Dataflow's UPDATE component:
Improvements to the management APIs of the Open Data component
Improvements in new SQL Engine: supporting operators (pj select 2+3*6/(5-3) from Restaurants, unions,...
Physical removal of users (from list and detail)
Improvements in the deployment of microservices in Openshift (https routes and new option to upgrade microservices and edit environment variables)
This distribution of the platform supports the development of systems that use the platform's intelligence capabilities, either with its AI capabilities, ingest from different sources, analytics, visualization,...
And in this quarter we have worked on this:
- DocumentDB support in Semantic DataHub: from this release you can use DocumentDB as other of the persistence engines supported by the platform (you know that we support any relational database, MongoDB, Elasticsearch, Kudu, HIVE, CosmosDB,...) DocumentDB (más info sobre DocumentDB) is an agile, scalable, highly available and fully managed document database service on Amazon AWS that is fully compatible with MongoDB's API and operation.
Thanks to the new SQL query engine we will be able to use an instance of DocumentDB as if it were a MongoDB 4.0, allowing all the development done to be compatible.
Here you can see the supported Storages in Platform: Storage Engines for Entities
- AuroraDB support in Semantic DataHub: Amazon Aurora is a MySQL and PostgreSQL compatible relational database offered by AWS as a service. The integration with AuroraDB allows us to use it as ConfigDB for platform deployments but also as a relational database on which to manage platform concepts.
- API REST for DataRefiner component: in this release we extended the platform APIs with one to be able to access the DataRefiner (DataRefiner Guides) component via API REST and thus automate the loading and cleaning of data coming in various formats (such as XSL, CSV, XML, JSON) before loading it into the platform.
This distribution of the platform supports the development of IoT systems, both in the Cloud and Edge environments.
In this quarter we have made progress in:
- Synoptic Engine Extensibility with external SVG libraries: our powerful synoptic engine is based on SVG for the creation of all the UI in SCADA style. In this release we have incorporated an improvement that allows to load new SVG component libraries to compose our synoptics:
Más info en esta entrada.
Within this section we include all the tools, utilities and platform capabilities that help in the Development and Operation.
- New Operations Manual: In this version we have revised and improved all the documentation about the operation of the existing platform to create a complete operations manual.
This manual is intended to serve as a basis for the teams using the Enterprise version that need to know the operation of Onesait Platform Engine & Intelligence and includes basic operation, special operations and troubleshooting.
- Inclusion of Billing in Operation Console: we continue to work on the Operation Console (see section) and have added the Billing functionality. From this section the user will be able to consult the monthly cost of each of his environments for each project, as well as the total monthly cost of the whole project, including in this cost the platform subscriptions (type, size, modules) and the size of the OpenShift namespace:
- Platform distributions on Helm Charts: In this release, important improvements have been added to the Helm Chart for the deployment of Kubernetes' cluster platform as Openshift. Based on the different platform distributions, the chart has been divided into independent charts following the same logic. In addition, work has been done to further automate the deployment process, with practically no manual intervention required.
Más info aquí.
- Signed distribution of platform modules with Docker Content Trust: From this version onwards when generating the platform Docker images these are signed to guarantee that the distributed images have not been altered in the process known in Docker as DCT (Docker Content Trust):
Más info aquí.
This line of work includes all the tasks related to the Platform Community, of which the Open Source version of Onesait Platform is a part, as well as the different communication channels of the Platform.
Regarding the strategy set for 2020 on the lines of the Community, during this last quarter we have worked on the following points: