I was very happy to have been interviewed on CoderRadio! We had a great discussion on how PiCluster started and programming in general. I like that I was able to talk about my life’s work in open source. We discussed how I started my first project MephistoBackup and how hard it is to get community involvement in an open source project. This blog was also featured and I explained what linux-toys.com is all about. Finally, I was able to talk about my other main Project Cloud Explorer and the exciting features that it has.
I embedded the interview in this post so you can watch it easily here or on YouTube.
Thank you JupiterBroadcasting for having me on CoderRadio. I was always a big fan of the network. Their wonderful content helped me get back into Linux in their early days with the Linux Action Show. Their shows are very inspirational and I hope that you will also learn a lot about the Linux ecosystem and become a fan.
I am pleased to announce PiCluster version 2.0! In case you are unfamiliar with PiCluster, it is a container management tool written in Node.js used to manage Docker containers. It has been a long journey this past year coming up with new features and trying to community involvement. In this post, I will go over the contributions that the community has made for this release and discuss the exciting new feature: automatic container failover to different hosts.
PiCluster is a great platform to manage and orchestrate Docker containers. Although it started as a way to manage my Raspberry Pi’s, it can be run on any operating system that supports Node.js and Docker. PiCluster has been under heavy development lately and I like to share what is new in v1.9.
Web applications typically feed information back and forth from a database to process information for the user. Organizations need to build applications that can scale with their business. While it is easy to scale web applications with containers and cloud platforms, the last thing that an IT administrator would want is a bottleneck at the database because it would affect application performance and availability at scale. One way to address these concerns is by using a clustered database solution such as ScyllaDB. This blog post will demonstrate how to use Node.js and ScyllaDB running in Docker.
I am pleased to announce PiCluster v1.7. In this release, I wanted to make PiCluster easier to use by having the Web Console handle most of the common configuration file changes. Not everyone enjoys editing json files including myself. Now let’s go over what is new in this release.
I am pleased to announce v1.6 of PiCluster. In this release there are a few usability bugs fixed and a new feature that allows you to change the host of a running container. Having the ability to easily change where a container is running is a standard and crucial feature to expect from a container management platform. I am glad that it is finally here and let’s explore how it works!
I am pleased to announce the new version of PiCluster. In this release, users can connect to a host running an rsyslog server and the PiCluster agent to view the log drain in the PiCluster web console and run searches. This combined integration provides a single pane of glass to monitor physical hosts and Docker containers easily. Let’s take a look on how to enable this functionality.
Most people will say that 2016 was a terrible year and can’t wait for 2017. I agree that 2016 was not perfect for many people but it was a great year for linux-toys. I made this blog with the goal to influence people and drive that creative spark that we all have inside. In this blog post I will go over the website statistics and discuss a few of the blog entries that I thought were most influential for the year.
I was always fascinated with distributed filesystems and wanted to learn more about Gluster since it is becoming more popular in larger open-source projects. Since I have a few Raspberry Pi’s, I thought that now is the best time to learn. This blog post will explain how to run Gluster on a two-node Raspberry Pi cluster from a Docker container.
Two Raspberry Pi’s (rpi-1 and rpi-2)
Running a Gluster image from a local Docker registry
Hostnames are resolvable in /etc/hosts on both Pi’s
I recently started to check out Kubernetes and wanted to share with everyone how I got WordPress running on it as a three-tier application. I made the decision to learn Kubernetes because Docker Swarm was not working well for me. To start, I downloaded and installed MiniKube on my laptop.
I then created three Docker images and pushed them to my Docker Hub registry: