Infrastructure Coders January Meetup

Seek have kindly offered to host the January meetup and will supply food and beverages.

Contact @geekle (http://twitter.com/geekle) or @dlutzy (http://twitter.com/dlutzy) if you wish to talk.

Talks

-----
Lindsay Holmwood (@auxesis (http://twitter.com/auxesis)) on "Ript: making Linux firewall change management resilient"

Netfilter is an extremely powerful framework for manipulating packets, but does anyone enjoy using iptables? Tools for managing small rulesets have a steep learning curve, and most tools don't take availablity into account when managing large rulesets.

Enter Ript, a clean and opinionated Domain Specific Language for describing firewall rules, and a tool that implements database migrations-like functionality for applying these rules with zero downtime.

At Ript's core is an easy to use Ruby DSL for describing both simple and complex sets of iptables firewall rules, with helpers for all the common use cases: accepting, dropping, & rejecting packets, as well as for performing DNAT and SNAT.

Ript provides a method to group common sets of rules together called "partitions", which are used at rule application time to perform zero-downtime migrations.

In this talk Lindsay Holmwood will take you on a whirlwind tour of the DSL, explain how Ript utilises iptables features to work its magic, and provide some concrete examples of how Ript can help increase the reliability of the services you deliver.

Darragh Kennedy (@darraghke (https://twitter.com/darraghke)) on "Software is eating the Infrastructure"

In this talk, Darragh will with the big picture;

The Lonely Planet Infrastructure as code rollercoaster what's to be learnt surviving a disrupted business model. Devops, agile, infrastructure as code, sdn why does this matter? Is infrastructure now a utility/commodity? A high level view of the state of the Software defined networking market And then the good stuff some code from our Software Defined Data Centre journey from @luker667 (https://twitter.com/luker667) and @mriddle89 (https://twitter.com/mriddle89) followed by questions.