5th Berlin DevOps Meetup

See Berlin DevOps homepage for group info.

"Continuous Delivery – the tech parts" by Jens Bräuer

Very interesting talk about the technical details of automating a complete server environment with AWS, RPM, YUM, MCollective, Puppet and Jenkins.

Some things I noted:

Amazon S3 <-> YUM Integration (use S3 as YUM repo backend)
Using a distributed HTTP-based document store as a YUM repo backend to solve the availability problem sounds like a really good idea.

Software packages bring their own monitoring and load balancer configuration

He also recommended http://mmonit.com/monit/ for monitoring and http://haproxy.1wt.eu/ for load balancing. Their software packages bring their own monitoring and load balancing configuration that is dropped into /etc/monit.d and /etc/haproxy.d. Each server monitors itself with monit and a central Icinga instance monitors the monit processes on all servers. MCollective collects the HA-proxy configuration from all servers and delivers it to the actual load balancers. They see it as a benefit that the developers also write the load balancer configuration for their services. I find this very cool and impressive!

Access his slides here.

"Scalarium running on Scalarium" by Jonathan Weiss, Peritor

This talk is about EC2 & Eucalyptus cluster management. See http://www.scalarium.com/ for the full marketing info.

Jonathan explained in detail how they bootstrap an initial Scalarium instance with Capistrano which is then used to bootstrap a second instance. These two instances can then manage each other which provides true redundancy.

And of course Peritor is hiring, like everybody else :-)

The discussion after the presentation was very interesting. This is the 3rd or 4th Scalarium presentation I have seen and I like it more with each time. I think they really build an interesting technology there that turns AWS into a reliable and managable platform.

“Silicon Berlin” and “Velocity Europe post-mortem” by Schlomo Schapiro, ImmobilienScout24

This was my talk:

This talk helped me to understand that we need a short definition of the Silicon Berlin idea. Here is my first attempt at writing a short pitch, please comment to improve:

Silicon Berlin is a label or brand that hopes to unite Berlin web companies to make Berlin a better place for web companies. It can serve as a label under which a community of web companies and IT people can act together. Silicon Berlin - beeing a true community effort - is not owned by anybody and can be used by anyone interested to further their goals with regard to making Berlin more attractive for web companies and for people who like to work in web companies.

See the following for more information about the topic:

If you don't like the name, logo or anything else, please drop me a line (or comment) with an alternative suggestion.

Thanks a lot to everybody who came and took part in the discussion.


Like this content? You could send me something from my Amazon Wishlist. Need commercial support? Contact me for Consulting Services.

Popular posts from this blog

Overriding / Patching Linux System Serial Number

A Login Security Architecture Without Passwords

The Demise of KaiOS - Alcatel 3088X