January 20-22, 2012, Hilton Los Angeles Airport Hotel


Keith Larson

MySQL Replication

MySQL Replication is a native feature of MySQL. This session will give a broad overview of replication within MySQL as well as a simple real world configuration example to get you started. We will then continue with a more  in-depth investigation of the MySQL Replication Features in MySQL 5.6.

  • MySQL Replication Overview
  • Replication Configuration
  • --- Examples of a Real World Setup
  • MySQL 5.6 Replication Features
  • Replication Monitoring



Christer Edwards

Remote Execution Management with Salt

Simplicity: Versatility between massive scale deployments and smaller systems may seem daunting, but Salt is very simple to set up and maintain, regardless of the size of the project. The architecture of Salt is designed to work with any number of servers, from a handful of local network systems to international deployments across disparate datacenters. The topology is a simple server/client model with the needed functionality built into a single set of daemons. While the default configuration will work with little to no modification, Salt can be fine tuned to meet specific needs.

Parallel execution: The core function of Salt is to enable remote commands to be called in parallel rather than in serial, to use a secure and encrypted protocol, the smallest and fastest network payloads possible, and with a simple programmer interface. Salt also introduces more granular controls to the realm of remote execution, allowing for commands to be executed in parallel and for systems to be targeted based on more than just hostname, but by system properties.

Building on proven technology: Salt takes advantage of a number of technologies and techniques. The networking layer is built with the excellent ZeroMQ networking library, so Salt itself contains a viable, and transparent, AMQ broker inside the daemon. Salt uses public keys for authentication with the master daemon, then uses faster AES encryption for payload communication, this means that authentication and encryption are also built into Salt. Salt takes advantage of communication via Python msgpack, enabling fast and light network traffic.

Python client interface: In order to allow for simple expansion, Salt execution routines can be written as plain Python modules and the data collected from Salt executions can be sent back to the master server, or to any arbitrary program. Salt can be called from a simple Python API, or from the command line, so that Salt can be used to execute one-off commands as well as operate as an integral part of a larger application.

Fast, flexible, scalable: The result is a system that can execute commands across groups of varying size, from very few to very many servers at considerably high speed. A system that is very fast, easy to set up and amazingly malleable, able to suit the needs of any number of servers working within the same system. Salt’s unique architecture brings together the best of the remote execution world, amplifies its capabilities and expands its range, resulting in this system that is as versatile as it is practical, able to suit any network.

Open: Salt is developed under the Apache 2.0 licence, and can be used for open and proprietary projects. Please submit your expansions back to the Salt project so that we can all benefit together as Salt grows. So, please feel free to sprinkle some of this around your systems and let the deliciousness come forth.


Bradley Kuhn

12 Years of FLOSS License Compliance: A Historical Perspective

Kuhn began working on GPL enforcement in 1999 by doing C&CS (complete and corresponding source) checks for the Free Software Foundation (FSF). Over the next 12 years, Kuhn was involved with every major effort to enforce the GPL in the USA. Kuhn's talk starts even earlier than that: with the first-ever GPL violation in history in 1989, and continues with GPL violations through the era of big iron computing to the current standard of embedded device GPL violations that are widely prevalent. Kuhn will explain the conditions in the industry that cause violations and how non-profit organizations like the FSF and Software Freedom Conservancy have worked to ensure that developers' copyleft license choices have been upheld and defended throughout the last decade. 

Link to the presentationhttp://ebb.org/bkuhn/talks/SCALE-2012/compliance.html

Source code is here: https://gitorious.org/bkuhn/talks/trees/master/SCALE-2012/


Kris Moore

Introduction to PC-BSD 9

The PC-BSD has grown and matured greatly over the past several years to become the most popular BSD based desktop operating system. PC-BSD is built upon the popular FreeBSD operating system, but is not a fork. Instead PC-BSD maintains FreeBSD compatibility in every way, while expanding upon it with a variety of new tools and utilities for both casual desktop users, as well as advanced server administrators. One of the first things an end user will appreciate is the easy to use graphical installer. During the installation options are provided to install both the Desktop (PC-BSD) or Server (FreeBSD) all from the same media. Support for some of the advanced file-systems that FreeBSD offers are included, such as ZFS, UFS with journaling, Geom-based disk encryption, automatic disk-labeling and more. After setting up disk options, users are given a choice between a variety of open-source desktop environments, such as KDE, GNOME, XFCE, LXDE, WindowMaker, Fluxbox and more. Based upon the users selections, the desktop is installed with the relevant FreeBSD packages, along with the PC-BSD control panel and related tools. Among these are graphical utilities for setting up the display (xorg) configuration, network management, user data backups, firewall configuration, the AppCafe and more. At first glance a Linux desktop user may not notice the real differences between PC-BSD and a typical Linux distribution. Most of the same open-source software is available, such as LibreOffice, VirtualBox, Firefox and others, so that most desktop users can immediately become productive on their new desktop. However when we begin to dig deeper into the base operating system the differences will quickly become apparent. The FreeBSD base operation system is designed quite differently from a typical Linux distribution. Instead of just a kernel, with a variety of packages installed, FreeBSD includes both a complete kernel and base world environment which are tightly integrated into one operating system, which tends to be developed conservatively and not vary wildly from revision to revision, making it a very stable platform for application development and distribution. In addition to the differences between development, the BSD license itself is quite different from the various "flavors" of the GPL. Under the BSD license users and developers are granted ultimate freedom by being able to use the software in any way they see fit, and only requiring that the original copyright notice be kept intact. Another way in which PC-BSD is unique is the package management system it utilizes. The PBI (Push Button Installer) format provides users with a method of installing applications without the worry of dependency issues causing problems elsewhere on the system. PBIs are packaged with dependent libraries and files included, so that they can run independent of the other applications / libraries that the users desktop may be using. In version 9.0 of PC-BSD this format has been greatly improved with advanced library sharing between PBIs, which maintain their independent functionality, but still saves disk and runtime memory space. Due to the independent nature of the package management system, PC-BSD upgrades are performed in a much more conservative manner, with most system packages only being updated in the case of security concerns. This means that the typical desktop versions, such as KDE, Xorg and others will only be updated when upgrading to a new PC-BSD version, such as 9.0 -> 9.1. This has the effect of keeping the users desktop very stable during its lifetime and provide developers additional time to test and fix new bugs and regressions which crop up from newer versions of upstream packages. One powerful feature of FreeBSD in the server market is its ability to easily setup and run a large number of "jails", which are self-contained chroot environments that provide ultimate security, with a very minimal virtualization footprint. PC-BSD includes some several features based around this jail system, including the Warden, which is a graphical management utility and the "Port Jail" environment. The Warden allows users, in a easy to use graphical format, create, start, stop and remove jails from the users system, making it easy to setup multiple environments for services such as Apache, mysql, postfix, sendmail and others. The "Port Jail" system is unique to PC-BSD, and offers a way for users to build and run traditional FreeBSD packages from either "pkg_add" or the FreeBSD ports tree in a sandbox environment, without the risk of changing or breaking the installed desktop packages. All of these features combined into PC-BSD makes it an exciting desktop to install and learn about the BSD platform on. By continuing to expand the capabilities of its graphical utilities, the system has steadily become easier to use, and more accessible to the casual computing market, as well as more productive for developers and administrators.


David Stokes

MySQL Update

MySQL has added several new features with the 5.5 release and the 5.6 previews. This session is an over view of the new features and how they can best be utilized. New features in replication, InnoDB, plug-in authentication, connection pooling, enterprise tools, performance, and NoSQL access of data will be included. This session is intended for all levels of attendees. This will cover changes and updates to the MySQL database server, data connectors, enterprise tools, MySQL cluster, Workbench, and more. The new features of the preview releases will be details to help the community prepare for new features being developed.


Owen DeLong

IPv6 Essentials for Linux Administrators

Back by popular demand, this standing-room only talk is updated from last year and introduces participants to the concepts of IPv6 and shows how they can easily add IPv6 capabilities to their Linux Systems, even if their ISP doesn't yet support IPv6. It covers all the basics, including interface configuration, DNS, Web services, Email, etc. A Q&A period at the end will allow participants to get answers to their IPv6 questions.


Cat Allman

Fundraising 101 (or "Free as in Freedom So Who Pays for the Beer?")

Free and Open Source software may be largely created and maintained by the passion of volunteers, but projects still need funds to pay for things like bandwidth, hardware and the all important tee-shirts. Asking for money is hard – and taking it can be a lot more complicated than you might think. This talk covers the basics of sourcing financial support for your project. Topics to be discussed include: - Types of potential sponsors - Big bites or lots of small ones: deciding on a strategy - How to find them - What do sponsors want to buy – and what are you prepared to sell? - How to “make the ask” – and how not to - More than money: other kinds of donations to consider - The devil is in the details, aka paperwork & time management - Some ideas on how to accept funds - Does your project need it's own Foundation? - Special considerations for events - Pitfalls to avoid Participants in this session should walk out with the information they need to develop at least the outline of a fund-raising plan for your project.



Subscribe to RSS - Everyone