The RLT Blog - Page 6 of 16 - Root Level Technology

The RLT Blog - Page 6 of 16 - Root Level Technology

Root Level Technology Joins The HashiCorp Partner Program

Houston, Texas, Nov. 21, 2018 – Root Level Technology, a highly-specialized cloud strategy partner, today announced that it is now fully engaged in the HashiCorp Partner Program.   A global partner network based around DevOps principles, cloud technologies, and data center management, the HashiCorp Partner Network offers participating organizations access to learning, technical, sales, and marketing resources. Partners can select a specific path depending on their business objectives, and can then use the expertise gained through the program to better serve their clients, at the same time deepening their relationship with HashiCorp.   Every Root Level Technology employee is certified with the full HashiCorp toolset and is equipped with the foundational knowledge to engage with clients and vendors alike, implementing […]

Continue reading

Creating a Private Hybrid Kubernetes Cluster Pt. 2

To pick up where I left off in the previous post, I had just finished attempting to create a cluster using Windows Server 1709 and 1607. In each of these I was able to get the cluster created, but there were still some issues that prevented the cluster from being usable with Windows workloads (e.g., Windows containers wouldn’t start, meaning that the cluster was no better than a Linux-only cluster).   Then, I acquired the most recent 1803 Windows Server. I went back and re-tried it using Rancher.   After a couple of minor hiccups (getting Docker installed and running was a bit more difficult than expected: https://docs.microsoft.com/en-us/virtualization/Windowscontainers/quick-start/quick-start-Windows-server https://blog.docker.com/2016/09/build-your-first-docker-Windows-server-container/), I saw a curious error when first attempting to join the […]

Continue reading

Creating a Private Hybrid Kubernetes Cluster Pt. 1

This is the first of a two-part post detailing my work to create a private hybrid Kubernetes Cluster.   I was asked recently to set up a hybrid Kubernetes (K8s) cluster so that it could run both Windows and Linux workloads. Full disclosure: I’m highly opinionated that anything that Windows can do Linux can do better. However, despite my opinions, customers are allowed to make choices with which I disagree, so I got to work. When undertaking a project like this, I generally try to do it once in a development environment, which helps me identify and resolve issues ahead of time, before working on customer resources.   And so we begin.   The customer wanted to run all of […]

Continue reading

IBM’s acquisition of RedHat

This weekend IBM announced plans to purchase a majority stake in Red Hat for combination of cash and debt valued at ~$34B. This values Red Hat at $190/share. According to IBM’s CEO, this move is designed to put them in the leadership position in the hybrid cloud landscape. In IBM’s vision, the hybrid cloud (or having resources in several different cloud provider’s ecosystems), is going to be the next evolution in cloud computing, and one that will play to IBM’s newly-acquired strengths.   While before the announcement IBM was not a major player in this space, it is clear that IBM intends to be a major player in cloud computing technologies, as it appears to be trying to catch up […]

Continue reading

How to deal with master node failure in a MongoDB cluster with a replica set

When MongoDB cluster is set up with replica set, one of the secondaries will take the role of the primary when Master is down. In case of a failure, the switch should be processed automatically. One of the remaining secondaries calls for an election to select a new primary and automatically resume normal operations.     The median time before a cluster elects a new primary should not typically exceed 12 seconds, assuming default replica configuration settings. This includes time required to mark the primary as unavailable and call and complete an election. You can tune this time period by modifying the settings.electionTimeoutMillis replication configuration option. Factors such as network latency may extend the time required for replica set elections […]

Continue reading