Open Source in a Lean Environment

by Lean DUS

Slide 1

Slide 1 text

open source software in an agile environment

Slide 2

Slide 2 text

who am I? jöran vinzens system administrator

Slide 3

Slide 3 text

what is sipgate? phone service provider Private and Business DE / UK MVNO

Slide 4

Slide 4 text

what is sipgate? LEAN SCRUM & KANBAN

Slide 5

Slide 5 text

what is sipgate? started with Open Source amount raised over years

Slide 6

Slide 6 text

open source? icinga, nagios, cacti, asterisk, kamailio, yate, RTP proxy, RTP engine, homer, captureagent, pacemaker, jenkins, ansible, DRBD, nginx, ganeti, qemu / KVM, net-snmp, quagga, puppet, tshark, postfix, squid, vim, sox, linux kernel, apache, firefox, gnome, KDE, freeradius, bind, percona, open LDAP, HA proxy, pound, lighthttpd, bacula, php, python, gcc, cups, perl, openjdk, exim, foreman, git, ecplipse, stun, libre office, imagemagick, lame, mpg123, ruby, redis, memcache, beaver, casperjs, pahntomjs, mongoDB, note.JS, openAFS, openSSH, openVPN, openSSL, samba, syslog-ng, vs-ftpd, spandsp, wireshark, bootstrap, jquery, requireJS, wildfly, elasicsearch, logstash, kibana, iTerm, atom, meteor, virtualBox, vlc, calibre, keepass, observium, as-stats, ntop-ng, osmocomBB, osmoBTS, BIRD etc...

Slide 7

Slide 7 text

why? pros: security reason financial reason flexibility (own improvements) benefit from community

Slide 8

Slide 8 text

why? pros: security reason financial reason flexibility (own improvements) benefit from community cons: no company to blame bugs in software no one cares short release cycles

Slide 9

Slide 9 text

~500 systems how to maintain? the question is:

Slide 10

Slide 10 text

software maintenance security minor major

Slide 11

Slide 11 text

software maintenance - security fixes operations team using kanban next story to be done delay everything else often at night (downtime)

Slide 12

Slide 12 text

software maintenance – minor release operations team using kanban normal story, no delay help from development rollout no downtime

Slide 13

Slide 13 text

software maintenance – major release temp team of developers Only one task to do rollout by temp team or operations team

Slide 14

Slide 14 text

software maintenance – what can we improve? less manual work get faster less failure potential more automatic tests

Slide 15

Slide 15 text

software maintenance – goal Stable and Up-to-date systems only standard code one click deployment continuous delivery

Slide 16

Slide 16 text

lessons learned asterisk 1.6 to 1.8

Slide 17

Slide 17 text

lessons learned kamailio no patches

Slide 18

Slide 18 text

lessons learned puppet and ansible

Slide 19

Slide 19 text

summary Failing is an option Keep systems up-to-date Automate as much as possible