Presentations
There are several ways to spin up a Kubernetes cluster and each technique has its own time and place depending on the complexity of your workloads.
In this session, Daniel will show you 4 different strategies for creating a Kubernetes cluster and unpack the pros and cons of each. From a simple and fast approach to a more technical but repeatable infrastructure-as-code strategy, and finally with a more in depth infrastructure-as-code solution, you’ll walk away with the building blocks to provision Kubernetes clusters that meet your needs.
The introduction of Infrastructure as Code or IaC has transformed how you can provision and deploy high-performance cloud-based IT infrastructures. IaC tools, such as Terraform, have been integrated into DevOps toolchains, saving DevOps teams from the excessive manual effort. While these tools undoubtedly help accelerate building IT infrastructures, their limitations can impact DevOps ability to optimize and improve control of their IaC processes, supporting future business needs. This talk will discuss strategies and tooling that alleviate some of those limitations.
It's 2021 and we're still dealing with integer overflow. Just a few months ago I came within 24 hours of watching one of the world's tech unicorns come to a stop because of a possible overflow problem. In this talk I'll talk about the nature of the problem, why we still see it today, and cover many of the various options to work your way through a pending int overflow. I also talk about some of the more advanced work we did to make sure our bases were covered, and walk through techniques you can use to keep from hitting the wall.
This is a tale about one company's experience with a database schema design refactor to use the Entity-Attribute-Value (EAV) data model on its members. I will describe the original data model and why there was a need to move to a new data model. There was some stumbling along the way but company recovered and succeeded in implementing the EAV data model. But some lingering questions remain...
The world is filled with concrete and tactile examples of poor application design and its impact on the real world. Come and listen do some of them!
Challenges in the adoption of Linux-based systems for companies have not gone unnoticed by cybercriminals. Attacks have been so widespread that the Department of homeland security has warned of increasing nation-states, criminal groups, and hacktivists against cloud-based enterprise resources.
Inclusiveness is vital for strengthening the sense of belonging. Community recognition thus needs to be more inclusive so that all community members, regardless of their background, interests, and skillset feel appreciated. Traditional recognition in open source tends to emphasize contributions in project repositories (or code), and we often miss valuable contributions from non-developers.
Ray will share his experience finding different contributions, community recognition examples (both good & bad), and feedback he received on community recognition programs over the years.
As we get deeper into Kubernetes yaml files, we see a lot of duplication. Can we move to a higher level that eliminates this duplication? Let's look at Helm, a tool both for templating k8s yaml files and for installing complex infrastructure dependencies as one package. With Helm 3, we now have deeper integration and more security when working with Kubernetes. Join us on this path to a simpler, more repeatable, and more discoverable yaml experience.
Desktop Linux has been around for decades, and has provided fertile ground for experimentation and evolution of the primary interfaces people use to interact with their PCs. One such form that is relatively lesser known is tiling window management. In this style users need not manage windows that stack upon and occlude one another. Rather, windows are each allotted a region of the screen and by default all windows are visible. Side-stepping the mouse-driven workflows of more prevalent desktops, tiling interfaces provide for simpler and faster keyboard-driven interaction.
SCaLE runs and operates on OpenWrt to provide WiFi to conference attendees. Starting with SCaLE 16x, the SCaLE Tech Team (responsible for the entirety of the conference network and wireless deployment) has continuously iterated, built, deployed, and tested the components of the conference wireless via its open source codebase. With the goal of providing a wireless experience that is exceptional for our attendees and also powered by open source software.