Howto

Incus which is named after the Cumulonimbus incus or anvil cloud, written in Go is a next-generation system container, application container, and virtual machine manager. History Based on LXC for containers and QEMU for virtual machines, it offers a seamless cloud-like experience scaling from a developer’s laptop to a full cluster of up to 50 servers. When running a system container, Incus simulates a virtual version of a full operating system. To do this, it uses the functionality provided by the kernel running on the host system. ...

I’ve been using Midnight Commander for years and I still enjoy it pretty much. The first time I’ve seen a file manager using the multi-column layout was on NeXTSTEP operating system. It was pretty smart, I felt in love with this operating system. When I first used yazi it reminded me of the early days of this OS who hasn’t been around long enough for my taste. So let me introduce you to yazi, a terminal based multi-column file manager written in Rust. ...

After two years of efforts and a $300k donation to the Zig Software Foundation, Mitchell Hashimoto has just announced the availability of version 1.0 of his Ghostty terminal emulator. He wanted Ghostty to be fast, feature-rich, and native on MacOS and Linux. I couldn’t find on the documentation a list of default key bindings for MacOS so here it is, plus some more stuff that I used extracted from the documentation. We don’t see any new terminal emulator often, so I urge you to try it out. ...

Containers are taking the IT world by storm, instead of re-inventing the wheel, CoreOS wants to offer the next-generation open source app container runtime, designed for security, simplicity and composability. But above all, they want to play fair with the ecosystem by ensuring it is built on common open standards and use what’s readily available like systemd and Kubernetes. rkt is written in Go, it compile to a single static binary, so it is easily portable to any modern system, for the rest read on. ...

In the last few articles, I’ve detailed the workflow to deploy Mirantis Cloud Platform (aka MK now MCP) based on Mirantis OpenStack and a Reclass Model Driven Architecture (MDA). But you may want to use a different backend for storage then our standard MCP one, the reference Cinder LVM ISCSI Driver. In this MCP cookbook article, I’ll guide you step by step, to use Ceph as your storage backend for Glance (Images), Cinder (Volumes) and Nova (Guest Disks). You can use any of these options alone or combined. ...

In this article we assume that you are familiar with Salt, formulas, reclass and OpenStack-Salt. This is my cheatsheet which drives you step by step to deploy OpenStack Mitaka based on the latest model, using a new Cluster Class. If you feel lost, feel free to get back to the beginning. What’s new The mk-lab-salt model, built for training and development, introduce the following new features Salt Master now runs on Ubuntu 16.04 LTS OpenStack packages comes from Mirantis repositories New top level cluster class allows a simple modeling of multiple deployments in a single reclass model. Mirantis Stacklight, logging, monitoring and alerting tooling is now integrated Modeling your Infrastructure In this session, I’ll be using my forked repository of Mirantis mk-lab-salt-model infrastructure modeling. ...

After having reviewed Salt, Salt Formulas and reclass, it’s now time to put everything together to deploy OpenStack from openstack-salt project which use an elegant Model-Driven Architecture stored in a git repository which can be used for the life cycle management, auditing and documenting your infrastructure. Imagine a service oriented, repeatable, documented tooling to deploy OpenStack which also can be used to Deploy monitoring Update OpenStack config Audit the deployment through git workflow Document it from a single source of truth Upgrade OpenStack With the following core principles ...

Now that data center are software driven, it is crucial to have a single source of truth, a kind of know all inventory about your resources, your nodes, their functions and their associated parameters, which describe everything and store it in a single location. Welcome reclass which use Class inheritance to define nodes roles and avoid duplication by gathering all important datacenter parameters in a central location. All of this will then be used by your automation tools like Salt, Ansible or Puppet to bootstrap your infrastructure as a software. In other words, reclass can be classified as a hierarchical inventory management solution. Let see how we could use it with Salt. ...