DC/OS (Datacenter Operating System) is a novel solution to simply and efficiently run services and applications across on-premises, cloud or hybrid environments. Even though you can run any type of applications, DC/OS is an excellent fit for container based architectures.
Deploying a MySQL instance on DC/OS requires just a few clicks, but once the service is running, you may have a few questions, such as:
-"What" is actually running?
-How is data persistence is handled?
-How can I enable HA for my databases
The goal of this session is to help answer these questions and share some of the thought processes and lessons learned from a real-world implementation, provide the background of how DC/OS operates, and identify key items that need to be considered when deploying database services.
An increasing number of stateless applications are being deployed in containers and managed by cluster schedulers. Until recently, stateful services like database have been overlooked by many container-based orchestration systems.
In this talk, Bryant and Joshua will discuss the trade-offs of containerizing databases and survey the current support for databases in open source projects like Kubernetes and Apache Mesos. They will also dive into the architecture and operational concerns addressed by the tools they built to deploy and manage MySQL, PostgreSQL, and Redis in Docker containers as part of the Database team at New Relic.
In this session, John Jainschigg, Master of the Universe, and Bill Bauman, Head of Innovation and Strategy at Opsview, will review the steps taken to build a simple Kubernetes infrastructure to support serverless workloads.
The infrastructure includes an installation of Percona DB for writing form, structured data.
This is relatively high level, focused on the capabilities and possibilities of what can be accomplished using modern technologies including orchestrated containers and serverless infrastructure in your own datacenter. A key point of interest during the discovery phase was, how do we monitor this thing?
We're eager to discuss your ideas, questions and comments, so join us!
In this session, we will discuss our fully automated failover solution running in containers on Kubernetes. Using Orchestrator for MySQL failovers, ProxySQL to route queries and a Zookeeper-backed application we wrote called Taiji for service discovery, database failures and topology changes are handled without any human intervention. This system is tolerant to network partitions and connectivity issues, node failures, and even full region outages.
After adding additional functionality to Orchestrator, we have it deployed with the raft consensus protocol and automatic failovers enabled. ProxySQL is deployed alongside a Taiji container that watches for changes in Zookeeper. All topology changes are automatically pushed to Zookeeper via Orchestrator callback scripts and a Taiji agent that performs health checks on databases. In less than a second, these changes are pushed to ProxySQL, so our application will seamlessly begin sending read and write queries to the proper database.
This talk is about measuring and reducing noise in benchmark results. Properly tuning the operating system and hardware to achieve stable results in benchmarks becomes an art in itself these days. There may be many reasons for that:
- jitter in CPU and I/O schedulers
- dynamic CPU frequency scaling
- process address space randomization
- kernel configuration
If you are not seeing stable results in your performance comparisons, you are wasting your time. Since I do a lot of MySQL benchmarks as a part of my job, I have collected a number of recipes to measure and reduce system noise and achieve more stable numbers in benchmarks. I'm going to describe those recipes as well as the new sysbench module implemented to automate those tasks and simplify system tuning for other people.
Learn about the benefits of running your database on the Mesosphere cloud container platform, and get a preview of what Percona is working on with Mesosphere.
Apache Mesos and DC/OS are powerful tools to manage, deploy, and maintain services. But, rolling your own stateful application on top of DC/OS requires a deep understanding of Apache Mesos primitives and DC/OS components. Enter the DC/OS SDK.
Planning to run MySQL, but want HA or horizontal scaling? Galera seems like the perfect fit! It can be, so long as your developers are aware of several important hazards. Galera's documentation hints at these, but understanding their implications can be tricky.
I'll show a series of demos which will show you the street signs you'll encounter on the road to Galera. This guide will help you choose the best path for your users. I'll expand on what I've presented before to provide better Galera background and a new demo of how multiple readers can read different data for the same queries over extended periods of time.
Cloud Foundry, an OSS PaaS project, gives developers self-service access to DBs. CF-MySQL provides CF Operators a reliable, automated, Galera cluster. We'll share what we've learned: what worked, and what we'd do differently next time.
Kubernetes is the most popular container orchestrator and is enabling enterprises to rapidly containerize their application stacks. Kubernetes' adoption still faces many challenges, particularly when it comes to stateful applications.
The engineers at Kasten have open sourced Kanister to allow ops teams to incorporate their existing tools into Kubernetes. Kanister is a framework for domain experts to write blueprints specifying how to perform data management in Kubernetes. Each blueprint is specific to a data service, like MySQL and can be modified to integrate with your infrastructure. The talk will conclude with demos of backup and restore of MySQL and MongoDB using example blueprints included with Kanister.
This talk will be targeted towards anyone interesting in running stateful applications in Kubernetes. The audience will learn why the current primitives exposed by Kubernetes aren't sufficient for data operations and how Kanister fills in the gaps.
MySQL is the world's most popular open source database and Kubernetes, an open source container orchestration system, is the fastest growing open source project and most vibrant community.
There have been some misconceptions about running stateful applications-- databases in particular-- on Kubernetes because of how it lends itself well to scaling applications which are more ephemeral in nature as well as a concern that Kubernetes would add more complexity to already complex applications like databases.
With newer Kubernetes features such as StatefulSets and operators now available with Kubernetes, running databases on Kubernetes allows a whole new way of thinking about database deployments and made easier than ever.
This talk will cover various Kubernetes features and two important projects that showcase these features and exemplify how Kubernetes is a ideal platform for MySQL: Vitess, Youtube's massively sharded back-end database, and the new MySQL Operator by Oracle.