Varlink is an interface description format and protocol that aims to make services accessible to both humans and machines in the simplest feasible way.

A varlink interface combines the classic UNIX command line options, STDIN/OUT/ERROR text formats, man pages, service metadata and provides the equivalent over a single file descriptor, a.k.a. “FD3”.

Varlink is plain-text, type-safe, discoverable, self-documenting, remotable, testable, easy to debug. Varlink is accessible from any programming environment. See the Ideals page for more. And everybody likes Screenshots.

A couple of days ago an interesting step-by-step guide on how to install Debian with full disk encryption, including /boot, using debian-installer was posted on the debian-boot mailinglist. This reminded me of the steps I used and wrote down a couple of month ago to create a similar setup. These steps describe a full disk (including /boot) encrypted setup on a non coreboot enabled system using the great grml live distro. (And just to be sure I just redid the same setup on a test device with the newest grml release Gnackwatschn):

Project Atomic is an umbrella for many projects related to re-designing the operating system around principles of "immutable infrastructure", using the LDK (Linux, Docker, Kubernetes) stack.

Many of the components of Project Atomic are upstream components of OpenShift Origin v3.

The primary building block of Project Atomic is the "Atomic Host", a lightweight container OS which implements these ideas. Atomic Hosts are immutable, since each is imaged from an upstream repository, supporting mass deployment. Applications run in containers. Atomic Host versions based on CentOS and Fedora are available, and there is also a downstream enterprise version in Red Hat Enterprise Linux.

Manage pods, containers, and container images.

• Modern user interface.
• Complete support of IMAP and SMTP protocols including SSL and STARTTLS.
• Sieve scripts (Filters and vacation message).
• Minimalistic resources requirements.
• Direct access to mail server is used (mails are not stored locally on web server).
• Allows for adding multiple accounts to primary one, simultaneous access to different accounts in different browser tabs is supported. Additional identities.
• Administrative panel for configuring main options.
• Really simple installation and update.
• Integration with Facebook, Google, Twitter and Dropbox.
• Managing folders list.
• Simple look'n'feel customization.
• Configurable multi-level caching system.
• Extending functionality with plugins installed through admin panel.
• Perfect rendering of complex HTML mails.
• Drag'n'drop for mails and attachments.
• Keyboard shortcuts support.
• Autocompletion of e-mail addresses.

containerd is available as a daemon for Linux and Windows. It manages the complete container lifecycle of its host system, from image transfer and storage to container execution and supervision to low-level storage to network attachments and beyond.

Automate all your cryptographic needs!
Goals

• Zero downtime
• Automatic certificate renewal
• Spam protection
• Updated DNS records

Configure once and always stay up to date.
Use cases

• Renew letsencrypt certicates
• Derive all kinds of data from the signature
• Ensure everything is secure

borgmatic is a simple Python wrapper script for the Borg backup software that initiates a backup, prunes any old backups according to a retention policy, and validates backups for consistency. The script supports specifying your settings in a declarative configuration file rather than having to put them all on the command-line, and handles common errors.

atticmatic is a simple Python wrapper script for the Attic and Borg backup software that initiates a backup, prunes any old backups according to a retention policy, and validates backups for consistency. The script supports specifying your settings in a declarative configuration file rather than having to put them all on the command-line, and handles common errors.

Pleroma is a free, federated social networking server built on open protocols. It is compatible with GNU Social, Mastodon, and many other ActivityPub and OStatus implementations.

The project consists of several components: Pleroma is the server implementation, and comes bundled with PleromaFE, the default frontend. Other useful utilities are also provided, such as an ActivityPub relay.

In Python, a decorator is a design pattern that we can use to add new functionality to an already existing object without the need to modify its structure. A decorator should be called directly before the function that is to be extended. With decorators, you can modify the functionality of a method, a function, or a class dynamically without directly using subclasses. This is a good idea when you want to extend the functionality of a function that you don't want to directly modify. Decorator patterns can be implemented everywhere, but Python provides more expressive syntax and features for that.

Der Supermoto-Gedanke lebt weiter, hauptsächlich in für Motorradfahrerverhältnisse recht jungen Köpfen. Er lebt dort aber gefährlich, denn jede Hard-Enduro, die sich zur Supermoto eignen würde, wird mit einer lächerlichen Leistung zugelassen, die nur dazu da ist, dass der Hersteller seine Rennsport-Zulassung dafür erhält. Wenn der Supermoto-Freund sich so ein Ding holt, kann er verschiedene Dinge über Straßenlegalität lernen, die meisten davon unerfreulich und teuer für ihn. Es gibt die Egal-TÜVer noch, die dir alles zulassen. Das funktioniert als Camouflage auch so lala. Du solltest das nur nicht mit Legalität verwechseln. Aus allen diesen Gründen gibt es nach einer Produktionspause wieder eine KTM 690 SMC R. Sie wiegt mit rund 160 kg eher schwer für eine Supermoto. Aber sie ist das einzig verbliebene legale Modell, wenn du 200-kg-Geräte wie Ducatis Hypermotard nicht mitzählen willst. Die Ducati ist in sich ein gutes Motorrad geworden, nur wie bei der Legalität: Verwechsle die Supermoto-Camouflage nicht damit, dass das auch wie eine fahren würde.

Modern, scalable and powerful
Productivity first and foremost
Loved by business, devs and IT

Build and orchestrate integration services, expose new or existing APIs, either cloud or on-premise, and use a wide range of connectors, data formats and protocols.

Zato facilitates intercommunication across applications and data sources spanning your organization's business or technical boundaries and beyond, enabling you to access, design, develop or discover new opportunities and processes.

Features

• Split tmux window into multiple panes
  • Build command lines & execute them on the panes
• Runnable from outside of tmux session
• Runnable from inside of tmux session
• Record operation log
• Flexible layout arrangement for panes
  • Select layout presets
  • Set columns or rows as you like
• Display pane title on each pane
• Generate command lines from standard input (Pipe mode)

Some months ago, Shlomi Noah published a series about Service Discovery. In his posts, Shlomi describes many ways for an application to find the master. He also gives detail on how these solutions cope with failover to a slave, including their integration with Orchestrator.

This is a great series, and I recommend its reading for everybody implementing master failover, with or without Orchestrator, and even if you are not fully automating the process yet. Taking a step back, I realized that service discovery is only one of the five parts of a full MySQL Master Failover Strategy, and this post is about these five parts. In some follow-up posts, I might analyze some deployments using the framework presented in this post.

This is the first in a series of posts reviewing methods for MySQL master discovery: the means by which an application connects to the master of a replication tree. Moreover, the means by which, upon master failover, it identifies and connects to the newly promoted master.

These posts are not concerned with the manner by which the replication failure detection and recovery take place. I will share orchestrator specific configuration/advice, and point out where cross DC orchestrator/raft setup plays part in discovery itself, but for the most part any recovery tool such as MHA, replication-manager, severalnines or other, is applicable.

We discuss asynchronous (or semi-synchronous) replication, a classic single-master-multiple-replicas setup. A later post will briefly discuss synchronous replication (Galera/XtraDB Cluster/InnoDB Cluster).