The CRUSH algorithm determines how to store and retrieve data by computing data storage locations. CRUSH empowers Ceph clients to communicate with OSDs directly rather than through a centralized server or broker. With an algorithmically determined method of storing and retrieving data, Ceph avoids a single point of failure, a performance bottleneck, and a physical limit to its scalability. CRUSH requires a map of your cluster, and uses the CRUSH map to pseudo-randomly store and retrieve data in OSDs with a uniform distribution of data across the cluster.

I have my favorite card game from childhood . Unfortunately description is available only in Russian https://uk.wikipedia.org/wiki/%D0%94%D0%B5%D0%B1%D0%B5%D1%80%D1%86%D1%8C . Currently my friends spreed across the globe and here in Germany no one except my wife knows the rules . I would like to to have ability to play this game with my friends like I did in school/univercity.

Description

Liz is the Rancher AI assistant for cluster operations.

Description

In my -almost - 3 years in QE-SAP, I have encountered various cases where I had to dig deep into countless and huge logs, visit other pages and perform multiple back-and-forths to get a good idea about the causes and effects of a test failure. Many of those tedious steps could - and should - be handled by automation, so that we can focus on meaningful tasks. This hackweek, I will attempt to create a tool - or, at least a PoC - to handle some of these problems.

If you are now thinking of Salt-SSH, this is not completely wrong, but also not right. What we are talking about here, is an other Transport for Salt, a replacement for ZeroMQ.

This project aims to run VMs in a CaaSP 4 cluster using kubevirt and a libvirt+qemu container (aka compute container) based on SLES15 SP1/2. Compute containers based on openSUSE Leap15.1 and SLES15 SP1 already available in registry.opensuse.org and registry.suse.com respectively. VMs can be deployed to the cluster but there are several functional problems that need investigating, e.g. accessing the VM's serial and VNC consoles, proper network access, etc.

Description