This should help diagnosing any failures while running the state scripts. Errors now contain the full description, not just the error code and all output from state scripts is logged to stderr. Mender 1.3 introduces several improvements to logging the output of the state scripts. State scripts, introduced in Mender 1.2, became a popular feature set. To alleviate this, the Mender client now supports resuming of downloads, so it will pick up from the byte where it left off when downloading the Artifact from the server! State scripts improvements In fact, this may cause the download to be restarted many times in unreliable networks because it may be interrupted over and over. If you have a large Artifact (.mender) file and the connection gets interrupted as your devices are close to finishing the download, it is quite wasteful to start the download from scratch again. disk images (.sdimg) and Artifacts (.mender), for Mender supporting Raspberry Pi 3 for future versions of Mender so you can easily test and build for this device type! It is very likely other revisions of the Raspberry Pi will work well too. In addition, we will provide demo images, i.e. We are very happy to add Raspberry Pi 3 as a reference device to Mender 1.3 and future versions! This means that we will include Raspberry Pi 3 in our CI environment and ensure it works with future versions of Mender as well. We hope we were able to make a good compromise with the design and would be very interested in hearing your feedback! Raspberry Pi 3 reference device Good onboarding is important, it strikes a balance between allowing users to play around without getting lost or overwhelmed. You can hide or show the help tips by clicking your email address at the top right: For instance, it will direct you back if you go to the Deployments tab before you have any devices connected: One of the first improvements you will notice in Mender 1.3 is a step in this direction: the new in-product onboarding guide.įor example, if you have not yet connected any devices to the server it will let you know about the next steps to do this: However, it is even better if documentation is not needed at all because the product is self-explanatory. Meta-mender has a brand new rocko branch, so you can integrate Mender with this newest stable release of the Yocto Project! In-product onboardingĭocumentation quality is a key focus area for Mender in order to make Mender easy to use. We welcome any feedback on this direction! Yocto Project rocko (2.4) support This would remove the need for patching U-Boot altogether, and we can run-time test the partition selection code that runs on all boards. One interesting next step we are considering is to use the UEFI-provider in U-Boot in order to load an UEFI-app that does the partition selection, rather than patching the existing U-Boot that comes with the board. In addition, we are researching several areas to simplify device integration with Mender even further in the future. To test the automated patching, please use the current rocko (2.4) branch of meta-mender (or later). The meta-mender-beaglebone layer has been removed, as the automatic patching produces the required integration for this board. So there might still be some diagnostics and tweaking required, but it significantly lowers the effort required to integrate a new device as you will always have a good starting point! Note however that as we do not have access to those 600 boards, we cannot do run-time tests on them, only compile-time tests. Our goal is that these 600 boards that already compile will continue to compile with the automatically generated Mender patch. To address this, we have automated the generation of the required board-specific U-Boot patch! We have compile-tested the generated patches against all boards supported by U-Boot.Ĭurrently about 1400 boards are supported by U-Boot itself, however only about 600 of them compile successfully out of the box. The integration with U-Boot is required in order for Mender to support robust and atomic updates out of the box by switching between two root file systems. The feedback from the community is that Mender's U-Boot integration was the hardest part, especially for developers who have not worked with U-Boot in the past. Therefore it is important to make it as easy as possible to integrate a new device with Mender. However, production-grade boards are usually custom in order to make them fit a form factor and reduce the cost of mass production by removing unnecessary hardware features. To make testing easier we provide demo images for a set of reference devices. Easier device integration: Automated U-Boot patching The key features of Mender 1.3 are covered below below, and you can see the detailed items in the Mender 1.3.0 release notes. We are happy to announce the production release of Mender 1.3.0!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |