Honza's IT blog about Linux and open source software, where you can enjoy posts about databases, programming, scripting, Fedora and another geeky stuff.

Sunday, January 31, 2016

CentOS Dojo 2016 Notes after lunch

This is a second part of my personal notes from this year's CentOS Dojo before Fosdem, first part includes notes from talks until lunch. So, after lunch, we returned to our chairs and heard these interesting talks.

4. Quickstart. Contributing packages to a CentOS Special Interest Group

Brian
talked about basics in centos build system, how to jojn SIGs and how to
build a package in CBS for a particular SIG. Really a "must seen" for
every newbie in centos SIG.

5. Path from Software Collections to Containers for OpenShift

My talk about experiences with creating Containers for Open Shift included two dozens of tips from various fields. We closely looked how to create a nice, Open Shift friendly container image (yes, it was about Docker) for PostgreSQL and Python. These two examples covered the most important information that one needs to create any similar database or application builder image. Later I went quickly through list of images that are already out there, made by Red Hat or CentOS and that are based on Software Collections packages. In the end I shortly introduced the concept of Nulecule and what this project is intended for.

6. Getting started with kubernetes

Kubernetes was described the same as other orchestration systems, even
condor which development started already in 1987. What makes the
technologies different from the PoV of potential developer folks is
language chosen to be written in.
Mesos was secretly influenced by
Borg, a group run by Google. It means guys creating k8s know what they
do, because we may see k8s as a new version of Mesos.
Basics of Kubernetes explained clearly and on simple examples -- what pods, services, replication controller do.
Atomic was presented as the solution to use k8s on CentOS.
For learning k8s use gh.c/skippbox/...8s
Terraform plan for deploying k8s on AWS with atomic host and flannel.
A demo showed automatically created k8s nodes and let them scale in AWS.

7. Atomic Developer Bundle - Containerized development made easy

Atomic
developer bundle, guys showed why there is something like ABD, stating
problems devels face today during application development, all on real
user stories. They showed Vagrant devel environment, running docker
secured by TLS, user being able to connect from host machine by evaling
'vagrant adbinfo' output that defines devel environment on host.
Another
example showed Eclipse running on the host, connecting to remote
docker, which is a scenario that might work from any OS, even windows.
Although the demo did not work and we could see the live-demo Murphy's
law in practice again, we got the point and I'm sure it worked fine just
before the talk.
ADB supports the OpenShift and other orchestrations technologies as well.
Why
centos? Because of community, that might give the needed feedback. In
the end the list of available links were mentioned and community was
called to action.
The future is so bright, I gotta wear shades.
Architecture is still a thing to be changed, they plan to make vagrantfiles easier.
Landrush does not work and some help is needed..
In
the end guys tried the demo again but with poor Internet connectivity
and Murphy's law working better, we saw only one step further.