As we are in the middle of our Sprint 11 (which ends on 7th Feb 2020), I want to give you an overview about our current work for that sprint and our roadmap to the next DATAGERRY version 1.1.0.
In Sprint 11, we are working on the following topics:
[NET-239] LDAP authentication
We prepared our authentication module to support external authentication providers and implemented the authentication against LDAP as a first external provider. Other authentication providers can be added in very simple way. We also added a logic to configure external authentication providers in the frontend. When a user logs in, we check, if a local user with the given username exists. If not, we’ll ask the external authentication provider for that user (e.g. LDAP). The work on that feature is already been done.
[NET-270] Frontend beautification
We found some smaller issues in the frontend of DATAGERRY 1.0.0 and wanted to make some usability improvements. This included the object navigation bar on the left side (which didn’t look nice for object types with longer names), some work on the object tables (mostly the width of columns) and a more compact view of the object view/object edit pages with an additional save button on the edit page, if you have to scroll. The work on that feature has also been done.
[NET-274/NET-277] Ansible integration
For our Exportd we added an exporter class to provide an dynamic inventory for Ansible. Ansible is a config management tool for systems like servers, routers, etc. The machines, that should be managed, needs to be configured in an inventory which Ansible can get from an external source, like a script or plugin. In a first version, we will provide a little shell script for Ansible, which gets inventory information from DATAGERRY. Until now, our Exportd only supported push jobs and exported objects eventbased (on object added, edited or deleted) to an external system. We extended Exportd to also allow pull jobs, that can be triggered by a HTTP call to our REST API and directly returns a result, which can be used in other systems. The little shell script we provide for Ansible will send an HTTP request to the new REST endpoint, which returns the Ansible dynamic inventory. I’ll get back to you with a knowledge base article, when we finished that feature. Most of the work is done here, but we need some more testing and the documentation needs to be written.
[NET-265] Redesign Search-Engine
We are not very happy with the search for objects in the current version of DATAGERRY, so we decided to redesign the search completely. The new search should be started in an new intelligent searchbar, which detects object types, public ids and usual searchstrings. The search results should be presented in a Google style result page. We just started with the development of that feature.
[NET-264] Handle inactive objects correctly in all parts of DATAGERRY
If you disable an object, it should not been displayed by default in search results, object tables and stats and also not considered by Exportd. We finished the development of that feature.
Some smaller things
[NET-240] Migrate the yourCMDB ExternalSystemCpanelDns plugin
[NET-266] Extend setup with Nginx HTTP proxy
[NET-267] Redesign Docker tags
[NET-272] Migrate the yourCMDB ExternalSystemCsv exporter
[NET-306] Allow HTTP Basic Authentication for REST API
The next release
The next release of DATAGERRY will be 1.1.0, which will include all features mentioned above and some more. You can have a look into our roadmap to get some more details. We don’t have a fixed release date for 1.1.0 at the moment, but it will be in the next months, most likely in March. I’ll keep you updated on that.
Let me know your thoughts about our current work