Skip to content

Release Note for Tukko - Version Rel_V1.1_Demo

Release Date

15.04.2024

Overview

A brief summary of the release, including the purpose and the impact on the users. Here we have gathered our progress to this day working on Tukko Traffic Visualizer. Our main goal was to focus on our team working and understand the roles were given to us, that's why our project is mostly based on great documentation which includes few actual implementation. In this release note, you can find out our features which were implemented to the application and links to our documentation on our OPF framework page.

Be free to ask us anything regarding to our project and give us some feedback!

New Features

-Feature 507: Feature, which allows platform engineers to configure and manage cloud-based infrastructure of Tukko Traffic Visualizer and allow developers and testers to constantly implement new features and testcases to the application.

  • Feature 203: Feature, which allows users to export data from specific dates, this allows user to examine the data first in Tukko and afterwards user is capable to download it as csv file to users own computer, which is then readable on Excel.

  • Feature 508: Feature, which allows platform engineers to actively monitor the health and performance of the application. This system is working on the Grafana platform.

  • Feature 106: Feature, which improves the dark mode features such as brightness, color contrast and more calming colors in Tukko.

Features under work

  • Feature 410: Configuration of secure HTTPS connection.
  • Feature 517: Maintainable documentation for stakeholders, this feature is been implemented throughout the whole project.
  • Feature 516: Manual testing for implemented features and Tukko in whole, this feature will be ready when all features has been implemented.

Known Issues

  • Issue 1: FEA203, when selected dates, it's only possible to export history data from previous months and not further.
  • Issue 2: FEA410, problem with the ports, https is needed to route from the same port where docker is located, but it's not allowing to have two connection on the same port.

Acknowledgements

Acknowledgements to the team members and any other parties involved in the release.

  • Team leader, Joonas Kuokkanen LinkedIn

  • Operations, Hanna Rantakokko LinkedIn

  • Tester, Honar Abdi

  • General/Developer, Santtu Lähderinne

  • Security, Arto Nieminen