I had this issue preventing me to start a call, which happened on two different browsers. It turned out that the pulseaudio service was hung, and no audio devices were available for the browser to use.
In that case it makes sense to check:
if pulseaudio is running
systemctl status --user pulseaudio
if pulseaudio is running, that you have a list from input (sources) and output (sinks) audio devices in the Gnome Desktop Settings. You can also check from the command line with
OpenShift is Red Hat’s Kubernetes distribution: it is basically the upstream Kubernetes delivered with monitoring, logging, CI/CD, underlying OS, tested upgrade paths not found with a manual kubernetes.io kubeadm install.
OpenShift upstream project
Kubernetes API Server audit log
AWS Trusted Advisor
OpenShift Operator Hub
AWS Identity and Access Management (IAM)
Red Hat SSO
AWS Elastisc Beanstalk
OpenShift Source2Image (S2I)
ODF Rados Gateway
AWS Elastic Bloc Storage
ODF Rados Block Device
AWS Elastic File System
ODF Ceph FS
Amazon Simple Notification Service
OpenShift Streams for Apache Kafka
Amazon Guard Duty
API Server audit log review, ACS Runtime detection
a bit of advertising-free space. The blog at wordpress.com has a prominent header indicating I am using the free plan, but I am OK so far with that.
What stays the same:
Blogger and WordPress.com offer both tag-based RSS feed exports, so I decided to keep for Debian Planet a feed containing only the posts related to free, libre and opensource software.
I was not ready to make the jump to a self hosted static blog generator, as I still wanted to have the possibility to comment, without me having to host the comment subsystem.
On the personal side, I also intend to pause twitter activity, as I notice current microblogging platforms tend to mostly contain flame wars, self promotion, or shared links I could find anyway with a good feed reader.
In regards to safety of data, it looks similar to the raft algorithm used by etcd with three members as a write is only ack’ed if it has been fsynced by two servers, the difference is that raft has a leader election, whereas in PostgreSQL the leader is set at startup and you have to build yourself the election mechanism.
There is no special cloud magic here, it is just database good practices paid by the minute.