Ben Ford
Community lead, developer advocate, and founder; I get to build neat things -and- talk to people! \o/ I've been in the tech industry in one way or another since the late 90's doing everything from devops before devops was a thing at a tiny security startup, to forensics investigations, to maintaining a compute cluster for a computational anthropology department at an American university and teaching the grad students how to write distributed Java code to run on it.
I run marathons in those funny finger shoes and my social engagement is primarily at https://hachyderm.io/@binford2k. You may have heard of that thing I'm building -- https://overlookinfratech.com.
Sessions
Vox Pupuli's Community Day is a space for community and contributors to engage directly with each other and collaboratively learn and make some magic. Do you have a burgeoning project you want to workshop and get feedback and ideas on? Do you want get the first glimpses at changes coming to the OpenVox platform? Or maybe you'd just like to help shape the next year of the community.
Expect a full day of content facilitated by the Vox Pupuli community leaders. We'll talk about the roadmap for the platform. We'll collaborate on ideas and get a pulse on what people are working on and help each other solve problems. If time and interest allows, we will hold bird of a feather sessions and/or lightning talks.
Bring projects you'd like to work on and get advice and guidance from peers and Vox Pupuli contributors. We'll have workshop time on TBD topics.
New to the community? Learn about ways to participate and how to get involved with Vox Pupuli, our premier community group.
With the unexpected proliferation of Puppet implementations, you may be wondering how to test your modules effectively. Interestingly, this isn't a new problem. It's a somewhat known secret that even the Supported modules on the Puppet Forge weren't ever tested against Puppet Enterprise, but like Bruno we don't talk about that. Because it didn't really matter, except -- well, when it did.
That was bad enough, but now we've splintered into four separate implementations built by two wildly different groups with very different priorities. We have the legacy Open Source Puppet that's still in broad use, there's the new proprietary Puppet Core which requires a EULA and a license key to download, there's Puppet Enterprise which used to be built on OSP but will be based on Puppet Core going forward. And now we have the truly Open Source OpenVox implementation built by your friends at Vox Pupuli. They're diverging as we speak.
This talk will go over topics such as
- why it's difficult for community module authors to test their code against Puppet Core.
- why it's (was) effectively impossible to test modules against multiple implementations.
- the legal thorniness preventing Vox Pupuli from signing the EULA.
- the rough spot the ecosystem has been forced into in which paid customers were being forced into using effectively untested modules.
Many of my customers are current or former Puppet customers and they're methodically migrating from legacy OSP to OpenVox so they can keep up with security patches, project evolution, and new features. But module and gem test suites have always been written with the assumption that they only had to test against legacy OSP. Some can be tricked into running against OpenVox, but being able to test against both at the same time? Not a chance.
My customers cannot and will not accept an ecosystem with untested code, and you probably don't want to either. But you still need a way to continue testing on legacy OSP until your migration to OpenVox is complete.
We have been hard at work building a pipeline that makes this possible, with very little upstream modification. Come see how it works.
I'm sure I don't have to describe the chaos inflicted on the Puppet community when Perforce decided to sequester the source away. Open Source Puppet is no more and many of us have been suddenly thrust into the roles of managing a large group maintaining a large, mature, and very hairy bit of software.
Let's take a no-holds-barred stroll through the story of this last year. I'll share some of the things that worked really well, and a whole lot of things that haven't. We'll talk about some tech challenges that were smaller hills to climb than we thought, and some that turned out to be real bears. I'll talk a bit about the biggest challenge we've faced. (Hint, it's people, time, and communication. It's always people, time and communication.)
Are you interested in starting a company? A year ago, a friend and I got a wild hair and did just that. We took no VC, committed to Open Source and sticking it to the man. A year in, things are developing much slower than I’d wanted but we’re doing all right. We’re signing some decent contracts and have made our first few hires.
I’d like to tell you a few quick stories and maybe help you work up the nerve to jump in the pool too.
Vox Pupuli's Community Day is a space for community and contributors to engage directly with each other and collaboratively learn and make some magic. Do you have a burgeoning project you want to workshop and get feedback and ideas on? Do you want get the first glimpses at changes coming to the OpenVox platform? Or maybe you'd just like to help shape the next year of the community.
Expect a full day of content facilitated by the Vox Pupuli community leaders. We'll talk about the roadmap for the platform. We'll collaborate on ideas and get a pulse on what people are working on and help each other solve problems. If time and interest allows, we will hold bird of a feather sessions and/or lightning talks.
Bring projects you'd like to work on and get advice and guidance from peers and Vox Pupuli contributors. We'll have workshop time on TBD topics.
New to the community? Learn about ways to participate and how to get involved with Vox Pupuli, our premier community group.