In the Plug It In: Designing for Extensibility there was something untold: But what if your driver requires some third-party tools to be available on the system? That’s where things get a bit more complicated but still solvable. Indeed, some of the power drivers supported by MAAS rely on third-party tools that need to be installed on the system. But what if there is no way to run snap install or apt install? ...
I am not going to start yet another debate about whether snaps are good or bad and if you should use it. For me snaps are solving a lot of problems. Yes, they might be not ideal but they work and they work well (both from a developer and a user perspective). I recently heard someone’s claim that once application is packed as a snap you cannot modify it. For example, you cannot edit a Python file (related to a deployed snap) and thus you cannot quickly add more logging which could help troubleshooting and hotfixing various issues, because the whole snap is read-only. ...
Disclaimer: I am a Senior Engineer on the team building MAAS at Canonical. Opinions expressed are solely my own. Some of you might not know, but MAAS is an evolution of Ubuntu Orchestra which originated back in 2011. Every now and then it’s good to revisit old design decisions, especially if they could be solved more efficiently today. New languages and frameworks have emerged and user needs have evolved as well. That’s why I am always looking for ways we can improve MAAS. Let’s try to model power drivers differently. ...
Hic sunt dracones! Why am I doing all of this? Over the past few years, a lot of people have asked me to explain them what MAAS is and what is netboot. So I thought it would be a good idea to write about the problem itself and how solutions evolved over time. Before tackling things like quadratic equations, you start by learning numbers and basic arithmetic, right? In the previous post we’ve covered RARP and got to the state where our machine was requesting /tftpboot/kernel.10.166.116.76 over TFTP. ...
These days, we take certain things for granted: there’s always DHCP, PXE-enabled clients and modern UEFI firmware with rich UI and mouse support. Imagine we are in the 1980s: the Xerox Alto already exists, but it’s still too early even for BOOTP. Though the world looked very different back then, the problem of network booting was already there. The concept is simple: computer contains bootstrap code stored in a non-volatile memory (e.g. ROM), which allows it to connect to a server and retrieve the kernel over a network. ...
We all love to say that tests are important and strive to get at least 80% test coverage. But very often, tests are not considered to be a real code. Developers treat tests as second-class citizens. It’s just a test; who cares if it is messy, right? And nowadays, with all the AI coding assistant tools, we can just ask the machine to write tests for us because writing tests is boring. ...
When you’re testing software that interacts with another system, it’s common to mock all the dependencies. But let’s be real – mocks are great for simulating interactions, yet they don’t give you any guarantees that the actual integration between systems will work as expected. What is the purpose of mocking database if your code relies on the database behavior (e.g. unique index constraint)? You should always consider writing integration tests! ...
I do have my global .gitconfig where I prefer to have my personal email address, and for every work related repository I used to do git config user.email [email protected] but there are always situations when I forget to do this. Here comes the solution: includeIf that is available since git 2.13 and makes it a bit easier. In my ~/.gitconfig I do have: [includeIf "gitdir:~/D/canonical"] path = ~/D/canonical/.gitconfig And under ~/D/canonical I simply have another .gitconfig where I set my user.email to my corporate email address. And voila, it will automagically apply a proper email for every git repository under configured path. ...
Back in a day I had a homepage – a place where I collected interesting findings and discussed various topics with others via guestbooks. But with the rise of social networks that quickly became obsolete as everyone moved to MySpace, then Facebook, and later Twitter or Mastodon. Yet, despite all these social media platforms, I never felt like I had a true home on the web. This blog is my attempt to change this. Here, I’ll share my findings on anything related to software development (and not only) that can potentially be interesting to others. ...