Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Puppet Contributor Summit - Gent 2015
1. Gent 2015 Contributor Summit Kick-Off
Eric Sorenson - @ahpook
Ryan Coleman - @ryanycoleman
Deepak Giridharagopal - @grim_radical
2.
3. Community health by the numbers
Stats site:
http://bitergia.dev.puppetlabs.com
Custom metrics for pull requests:
http://pullrequestmetrics.herokuapp.com
Donnie Berkholz' CFGMGMT DEATHMATCH
http://www.slideshare.net/dberkholz/is-your-community-
healthy-metrics-on-the-top-cm-software
10. Other Big Changes
Dynamic scope gone, except defaults
Stricter number parsing (octal => 644)(octal => 0644)
More 'language-y' features like array +
Die, undef, die!!
11. Puppet Client
Focus on Speed, Ubiquity, and Clean Re-Implementation.
Command and control tools that integrate tightly with our
ecosystem.
welcome
‘contributor summit’ -- this is the third one.
puppetcamps are running 30-50% new to puppet
wanted to focus in on foss contributors with dedicated time and space
still early , so lets figure it out together — the ground rules are assume everyone is acting in good faith, try to make that a safe assumption.
this is a pretty free-wheeling presentation, i have some points to get through but we have plenty of time so raise hand if there's an important point you want to make before i move onto the next slide.
So we’ve got this cool new bitergia site that’s pulling stats from all the projects, that’s where most of the graphs that come from are from
Hailey Kenney did a cool intern project last summer , custom stats around pull request cycle time
Donnie's talk yesterday hit a bunch of metrics across all the communities. Basically, things are fine though there's definitely some oxygen-sucking going on from Ansible and Docker.
20 camps through 2014
PUGs in 50 cities
#puppethack on dec 4 - deeper engagement vs tons of tickets. portland, pilzn, stockholm, jasper got jruby->freebsd, brice got cursive clojure. s/o to felix, colleen, dom cleal for diving in. not sure when next will be, mid 2015.
PR triage are awesome - who's particpated? who knows when they are?
please join! even if you only have a small idea for a PR, we want to help!
How many are running under 'future parser' at least some of the time?
Future parser in 3 = ONLY parser in 4.
Some awesome wins, including some performance boosts out of the gate, iteration, better default syntax. we'll get into that more later.
two big points:
the last 3.7.x will have the same parser impl as latest 4.x so you have an upgrade path
we're constantly working to refine and adapt the syntax and semantics of these features so they help SOLVE YOUR PROBLEMS. if something seems wrong or crazy, please SAY SO.
beyond the syntax stuff there are a batch of language changes
TODO check number parsing.
array and merge concatentation, better error reporting, unless+else supported.
and josh hoblitt's baby, making undef consistent.
long thread on puppet-dev about this.
not completely altrusitic, because our goal is to simplify the QA matrix and eliminate upgrade problems for FOSS->PE migrations.
but there are benefits for users plus us
no more distro ruby problems.
no more httpd.conf conflicts
tell me why this causes you trouble, and if there's something that can reduce the
Luke mentioned "server in clojure, agents in C++"
We haven't started on the agent rewrite
There's a huge amount of emergent behaviour that we need to understand and reconcile before diving in
meantime we can fix the thing we have, now
like to make no-op more consistent (some of that in pup 4 - no-op directly on a resource will ignore notify events)
and make a stronger assertion about catalog version before trying to DDOS the master
people don't know it's out there!
give it a try instead of your apache+passenger rig, you'll like it!
in addition to the network stack, there's a CA that drops in to existing infrastructure
and overall, with the 1.0 ability to flush jruby when you know something's wrong, it's like passenger++
So the next step is to actually fix some of the CA problems we've had since 0.13.
Build a router so that we can dispatch requests for a given environment to a specific pool of compilers.
And add some commercial features that are next level, like automatic file sync.