Download - Releasing Puppet: Automating Packaging for Many Platforms or 'Make all the things' - PuppetConf 2013

Packaging: Or how to make all the thingsMoses Mendoza and Matthaus OwensRelease Team | Puppet Labs @MosesMendoza@mlitteken

Friday, August 23, 13

puppetconf.com #puppetconf

Introduction

• Why package at all?

• How would I do this?

• Architecting for abstraction

• There be dragons - danger!

• How the F* we did this



You can deliver more than the source.



Why bother?



Why?

• Ease adoption

• Format familiarity

• MOAR power!

• Easier to deploy

• Consistent user experience

• End build tool proliferation



If it’s so awesome, why isn’t everyone doing it?

• Expense!

• Learning stuff is hard!

• Maintenance

• NO demand (or so you think)

• Somebody’s already doing it for me!



But wait!

• Expense (start small! start free!)

• Learning stuff is hard! (Learning is fun!)

• Maintenance (you’re right! That is hard!)

• NO demand (or so you think)

• Somebody’s already doing it for me!

• control your release



Create demand



Alright, I’m in. Now what?



Level up! packaging++

• Pick your distro

• Do some research about the distro

• Read the Maintainers Manual

• http://www.debian.org/doc/manuals/maint-guide/

• https://fedoraproject.org/wiki/Packaging:Guidelines


http://www.debian.org/doc/manuals/maint-guide/

http://www.debian.org/doc/manuals/maint-guide/

https://fedoraproject.org/wiki/Packaging:Guidelines

https://fedoraproject.org/wiki/Packaging:Guidelines


Answer the following:

• Where do I put stuff? (FS pathing)

• How does the system handle services?

• What are the package management tools?

• Can they express dependencies?

• What does the metadata look like?



And these also:

• How does versioning work?

• Can I uninstall?

• Upgrade?

• How are configuration files handled?

• Can I do pre-install configuration? post-?



Package and Sign

• Fire up a VM and play with the tools

• Start small

• Package your project

• Who made this package, anyway?

• Make a gpg key and publish it

• Sign your package!



Potential Next Steps...

• Get your package to your users!

• Become a distro maintainer

• Host basic downloads

• Host package repositories (yum, apt...)



Pitfallsask us how we know.

• Sprawl...... . .

• Variation in workflows

• Historically preserved cruft

• Shipping without testing

• Over-abstraction



Architect for Abstractiontools on tools on tools.

• Snowflakes Are Bad (tm)

• Cross-platform tools

• Start small but lay expansion groundwork

• Don’t hard code paths

• Work in a workspace

• Make infrastructure assumptions configurable



Architect for Abstractiontools on tools on tools.

• Define a user interface API for automation

• Try a layered approach

• Entry points call to Abstractions call to System tools



how Puppet Labs does it

el fedora debian

ubuntuandmore

windows

rubygems tarball osx

build ship



the base layer

rake ruby make - tool for automation in ruby

ruby methods for utilities and system tool wrappers

system tools to create packages



rake ruby make



More than in the middle

• Ruby utilities to wrap system tools

• Data lives in projects, not in tools

• Packaging automation in a separate repo

• Automation completely project agnostic



Setup workflow

puppet/ext/packaging

github.com/puppetlabs/packaging

puppet/Rakefile

rake package:apple



so far so good!

• Wherefrom cometh the build hosts?

• How do I get from here to them?

but...



System configuration?github.com/puppetlabs/puppetlabs-{deb,rpm}-builder



• Jenkins has: master/slave, queuing, triggers

• Builders become Jenkins slaves

• Builders categorized by capability (label)



Right place, right time

• Create per-build jobs from templates

• Builds are matrix jobs

• Groovy Label Assignment Plugin to assign

• Use labels to assign jobs



• On-demand capacity

• Parallelized

• Automatically triggered

• Jobs chained into a pipeline on the fly

• Open source: github.com/puppetlabs/packaging

Where we are today


Thank YouMoses Mendoza and Matthaus OwensRelease Engineering | Puppet Labs @MosesMendoza@mlitteken

Collaborate. Automate. Ship.


Follow us on Twitter @puppetlabs

youtube.com/puppetlabsinc

slideshare.net/puppetlabs

Collaborate. Automate. Ship.


Download - Releasing Puppet: Automating Packaging for Many Platforms or 'Make all the things' - PuppetConf 2013

Top Related