+ daniil.klimuk@3mdeb.com
+ 
+
+???
+
+- Time for this slid: 10s
+- Idea/goal of this slide: Just start it
+- What to say: "Hello there! I am going to present you Dasharo Tools Suite
+status and future improvements."
+- Notes:
+
+---
+
+# Who am I?
+
+.left-column50[.center[
+
+ daniil.klimuk@3mdeb.com
+
+-
+ 
+ linkedin.com/in/daniil-klimuk-9358a1271/
+
+]
+
+.right-column50[.center[
]]
+
+.right-columt50[.center[3mdeb Zarhus team member]]
+
+.right-column50[
+- https://3mdeb.com
+-
+ Book a call
+
+-
+ Sign up for the newsletter
+
+]
+
+???
+
+- Time for this slide: 25s
+- Idea/goal of this slide: Present yourself
+- What to say: "My name is Daniil. I am junior embedded system developer
+interested in system level programming and security. Currently I am a member of
+3mdeb Zarhus team, and responsible, among other, for Dasharo Tools Suite."
+- Notes:
+
+---
+
+# Agenda
+
+* What is DTS?
+* DTS statistics Q3-Q4 2024.
+ + Issues
+ + Contributions.
+ + Features.
+ + Hardware support.
+* DTS current architecture and tests.
+* DTS new architecture and tests.
+* Roadmap Q1-Q2 2025
+* Q&A
+
+???
+
+- Time for this slide: 35s
+- Idea/goal of this slide: Introduce agenda
+- What to say: "Here is the agenda for this meeting. After a brief intro into
+DTS we will take a look on DTS latest contribution and features statistics. Then
+we will discuss the transition between old and new DTS architecture. After the
+architecture a new testsuites will be presented and described. Then we will
+finish with questions and answers, where you will be able to ask questions and
+share your ideas."
+- Notes:
+
+---
+
+# What is DTS?
+
+.center[
]
+
+.center[Solid and Secure bridge]
+
+???
+
+- Time for this slide: 50s
+- Idea/goal of this slide: Present DTS
+- What to say: "What is DTS? DTS states for Dasharo Tools Souite and is a tiny
+Linux Kernel built for 64-bit x86with goal to make Dasharo user experience
+easier. Actually, it could be thought of as a solid and secure bridge between a
+user and Dasharo. It has several Dasharo and Coreboot tools built in, as well
+as other, firmware related tools for enhanced debugging and programming. But
+most importantly, it has a layer of automation and GUI scripts that make DTS
+more user-friendly."
+- Notes:
+
+---
+
+# DTS statistics
+
+.center[
]
+
+.center[Two big releases: 2.0.0 and 2.1.0!]
+
+???
+
+- Time for this slide: 45s
+- Idea/goal of this slide: Present DTS issues statistics
+- What to say: "There have been a lot of changes in DTS since first half of 2024
+year. We had several minor releases with hot fixes and, most importantly we had
+two big releases 2.0.0 and 2.1.0. Unfortunately, our plan to win in issues fight
+met a counterattack, and now we are fighting back. Here I would like to thank
+all of users who add issues and participate in discussions, it is really
+important for developers. Great thanks to all of you!"
+- Notes:
+
+---
+
+# DTS changes
+
+.left-column50[
+Updates:
+* Linux Kernel to 6.6.21
+* Updates for meta layers
+
+New features:
+* pre-commit now used everywhere
+* Some new tools
+* Verbose debugging mode
+* New GUI
+* DTS extensions feature
+* UEFI Capsule Update support
+* DTS is now in netboot.xyz official support
+]
+
+.right-column50[.center[
+
+]]
+
+???
+
+- Time for this slide: 1.5m
+- Idea/goal of this slide: Present DTS new features and updates
+- What to say:
+ + "Here is a list of most important changes and updates since Q2. First of
+ all, all meta layers have been updated to new Yocto long term support release,
+ therefore all tools have been updated too. A huge list of new features have
+ been added.
+
+ + "Now pre-commit is being used in all DTS-related repositories, so the DTS
+ code now is more readable and contribution-friendly."
+
+ + "Some new tools were added into DTS image, including tools for Dasharo
+ TrustRoot provisioning for Intel Bay Trail."
+
+ + "Verbose debugging mode has been added for leveraging testing and developing
+ processes"
+
+ + "New GUI and DTS extensions were released."
+
+ + "A new way to deploy Dasharo has been added - that is UEFI Capsule Update
+ now is supported by some platforms. For those who are unfamiliar with it. It
+ is a new and more secure way to update your firmware. Instead of useng some
+ complex and not always stable tools for updates - you just feed your update
+ file directly to currently installed firmware and the firmware will handle the
+ update for you."
+
+ + "Good news for those who love iPXE, DTS is now officially supported in
+ netboot.xyz."
+
+- Notes:
+
+---
+
+# DTS changes
+
+.left-column50[
+New supported platforms:
+* Novacustom MTL
+* Dell Optiplex 7010/9010
+* ODROID-H4
+* Updated MSI Z690 and Z790
+
+Important changes:
+* DTS script moved to a separate repository
+* Enhanced debugging and testing
+* Qemu is now supported
+]
+
+.right-column50[.center[
]]
+
+???
+
+- Time for this slide: 1m
+- Idea/goal of this slide: Present DTS new features and updates
+- What to say:
+
+ + "A list of supported HW platforms has been extended too. In last two updates
+ two families have joined Dasharo: Novacustom Meteorlake laptops and Dell
+ Optiplex PCs. MSIs and some other platforms got updates too."
+
+ + "And about more important changes. dts-scripts has moved to another repo,
+ and now is being linked to DTS image from a recipe. dts-scripts was modified
+ to support new tests, more about this later. And, from update 2.1.0 Qemu
+ support has been added for DTS, now we are working to get best of this
+ support!"
+
+ + "You can see here on the right side the results of the verbose mode feature."
+
+- Notes:
+
+---
+
+# New GUI
+
+.left-column50[.center[
]]
+
+.right-column45[.center[
+
]]
+.right-column50[.center[
]]
+.right-column50[.center[
+
]
+
+???
+
+- Time for this slide: 1m (35s~)
+- Idea/goal of this slide: Present DTS old architecture
+- What to say: "Now about problems that appeared lately. Currently DTS has a
+monolitic architecture, we have almost
+everything in two files. This was OK until DTS started to grow. Then we faced
+several problems related to scalability, stability and testing, that now
+result in issues. We, as well, did not have full test coverage for this
+architecture, only some unit tests and a few end-to-end regression tests were
+implemented."
+- Notes:
+
+---
+
+# DTS new architecture
+
+.center[
]
+.center[More inf.: https://github.com/Dasharo/dasharo-issues/issues/1067]
+
+???
+
+- Time for this slide: 2m (50s~)
+- Idea/goal of this slide: Present DTS new architecture
+- What to say: "But now we are thinking about redesigning DTS so it will have a
+clear and consice structure. As you can see it will be divided into modules with
+a defined interfaces between each other, enhancing developing and debugging
+processes. All configuration, that is now stored in bare Bash code will be
+stored directly in Linux FS in files in human-readable format. Hardware-depended
+code will be separated into a module, named HAL that states for Hardware
+Abstraction Layer where it will reside alongise with mocking functions, named
+HAL for tests on the diagram, that will make running DTS on Qemu possible. We
+have decided to change DTS language as well, new DTS architecture will be
+implemented mostly in GO language."
+- Notes:
+
+---
+
+# DTS new tests
+
+.center[
]
+.center[More inf.: https://github.com/Dasharo/dasharo-issues/issues/1067]
+
+???
+
+- Time for this slide: 2m (1m~)
+- Idea/goal of this slide: Present DTS new tests
+- What to say: "At the same time, we want to develop a test suite that will
+cover entire DTS. As you can see, we are planning two types of tests: end-to-end
+tests and unit tests, and we would like to do as many testing as possible using
+OSFV on Qemu. Therefore end-to-end tests will be intirely hardware-independed
+and automated. As you can see these tests cover most of DTS
+structure. The goal of this tests is to keep large and crucial parts of DTS
+stable and secure. On the other hand, unit tests, will cover all
+hardware-depended code, that could not be tested on Qemu. These tests will be
+mostly automated utilizing OSFV functionalities and devices in our lab. But some
+of them may require manual steps, which is ok for some systems."
+- Notes:
+
+---
+
+# DTS new tests
+
+.left-column50[
+End-to-end tests:
+* Will be launched by OSFV
+* Will be launched on Qemu
+* Will test DTS logic as well as user experience
+* Some of them will be used in CIs
+* First version of it is already in integration (check `open-source-firmware-validation/dts`)
+
+What we will get:
+* More stable and secure DTS
+* Strictly defined and tracked user experience features
+* Less time wasted on SW tests
+]
+
+.right-column30[.center[
]]
+
+???
+
+- Time for this slide: 1.5m (40s~)
+- Idea/goal of this slide: Present DTS E2E tests
+- What to say: "Here you can se an example of end-to-end test workflow. It will
+start from booting DTS and choosing an option from a list of options that a user
+can see when he boots DTS. After choosing an option, test will read output and
+check whether DTS went through all steps for a chosen option. These steps will
+be marked by anchors. These anchors are simple prints for user, that inform
+where DTS is now and what it is doing. In case of a fail a simple error will be
+printed, informing test about some issue. This will trigger test fail. If
+there will be no fails, DTS will go down to rebooting message, which will signal
+to the test, that everything passed with success. This tests, as was said, will
+cover most of the DTS logic. It may seem that there is a lot to implement. But
+it is not true, because these tests will utilize all exeisting functionalities
+from Dasharo OSFV. Even if it will take some time to integrate, the long
+term outcome is worth it. Because with these tests we will be able to easily
+verify entire DTS during merging of every PR. Ability to run on Qemu will allow
+us to run these tests implicitly using Ci/CD workflows. As was said, these
+tests will use GUI interface, which is a default GUI used by users. This fact
+will help to make the GUI more strict and user-friendly. First version of these
+test is already being integrated, and a PR CI/CD workflow is already being
+tested."
+- Notes:
+
+---
+
+# DTS new tests
+
+.left-column50[
+Unit tests:
+* Will be launched by OSFV
+* Will be launched on real HW
+* Will test HW-specific logic
+* Will be used in every HW-related release
+
+What we will get:
+* Separate HW tests from SF tests
+* More stable and secure DTS
+* Less time wasted on HW releases
+]
+
+.right-column30[.center[
]]
+
+???
+
+- Time for this slide: 1m (40s~)
+- Idea/goal of this slide: Present DTS unit tests
+- What to say: "Coming back to DTS unit tests. The only module that will have
+these tests is the HAL, that connects entire DTS with real hardware. The HAL
+will contain hardware-specific workflows, or functions that read or write to
+hardware, so the unit tests will be writtent to test this code on real hardware.
+The HAL will be divided into a modules and every modele will be tested
+separately. As was said before, most of these test will utilize OSFV automation,
+but some of them may require manual steps. These tests will help us define a
+clear way to validate per platform updates. But ok, the new features are good.
+But when they will be integrated?"
+- Notes:
+
+---
+
+# Roadmap
+
+.center[
]
+
+.center[Some simultaneous development out there!]
+
+???
+
+- Time for this slide: 1.5m
+- Idea/goal of this slide: Present roadmap
+- What to say: "We have prepared a roadmap for first half of 2025 year. New year
+will start from some internal ifrastructure changes. These will be mostly
+invisible for end user changes. But there is one thing to note. Previously, we
+were limited by our ifrastructure in terms of authentication method, that
+resulted in a strange, inconvenient credentials. But after the changes new
+clients will get credentials in more convenient format. And who knows, maybe we
+will migrate to certificates in near future. After the infrastructure we will
+focus on GUI polishing and preparation for further implementation of the E2E
+tests, including rewriting credentials-related code for more security. And then,
+we will continnue developing the tests suites described previously. These
+changes will be released as a part of DTS version 2. For the time being we do
+not know, whether it will be several releases, or one, that will cover all these
+changes. Semelteneously, while extending current version of DTS we will start
+developing the next one, that will include the refactoring into a new DTS
+architecture and GO language."
+- Notes:
+
+---
+
+