The first Open Infra Structure Summit Denver Spring 2019 has just ended after the last OpenStack Summit Berlin 2018, the original.
Der erste Open Infra Structure Summit Denver Frühjahr 2019 ist gerade zu Ende gegangen nach dem letzten OpenStack Summit Berlin 2018, das Original quasi.
What happened in 2018? Time for a review based on my Twitter timeline
Mostly interesting to see what's going on the modern guiding culture of music. The source of investigation is the music section of the shopping mall, broadcast radio station, or YouTube. Here is a way to auto-generate a playlist with the Top 50 rated video clips of the category 10 (Music) and the region DE
This review falls back in the year 2015, my first visit of an OpenStack Summit in Tokyo.
I recognized how cool would be to have a OpenStack Summit in Germany, especially in Berlin area, where I live.
Just around this time (2015/2016) the OpenStack Foundations sent out a Call for Venue, so I proposed Berlin ICC as the convention area.
Unfortunatelly that building was closed and Messe Berlin starts with construction of the CityCube. Now, in 2018, the OpenStack Summit is gone, just 2 days before as the last OpenStack Summit which will we ever haved. The OpenInfrastructure Summit was born here and the first one will be held in Denver (US) April/May 2019.
Mein letzter Blogartikel zum Thema DevOps ist jetzt ueber 6 Jahre her. Damals gings noch um Schatten-IT und dem steten Grabenkampf zwischen Entwicklung und Betrieb. Mittlerweile bin ich selt einiger Zeit Mitglied in einem DevOps-Team, was ein Paradoxum an sich ist, denn sowas wie DevOps-Teams gibt es gar nicht. Stattdessen geht es um den Flow.
My last blog post about DevOps is now over 6 years ago. At that time, it was still about shadow IT and the constant trench war between development and operation. By now I am a member of a DevOps team, which is a paradox in itself, because there are no such things as DevOps teams. Instead, it's about the flow.
in my last vacation I spent most of the time to visit the OpenStack Summit in Vancouver. It's my 4th Summit and it's one of the best Summit. The bar is very high vor the upcoming event in Berlin.
Wikipedia schreibt: Ein Hackathon (Wortschöpfung aus „Hack“ und „Marathon“) ist eine kollaborative Software- und Hardwareentwicklungsveranstaltung. [...] Ziel eines Hackathons ist es, innerhalb der Dauer dieser Veranstaltung gemeinsam nützliche, kreative oder unterhaltsame Softwareprodukte herzustellen.
Wie geht sowas?
After another year with work and usage of Ansible-OTC I want to share a project update and the vision for 2018.
- Role collection. There are a lots of roles in the Github Repo. This is good to show the work of OTC-API and for demonstration, but bad for overview and automation. I tried to collect functions following the CRUD standard into new roles. I.e. otc_ecs should Create, Read, Update, and Delete ECS resources on OTC: https://github.com/eumel8/ansible-otc/tree/dev/roles/otc_ecs
- Input-Handler. It was a good idea to use ini-files for configuration items, because it's good readable and easy to unterstand. Previously I used yml-files for the same function, other projects are using json. To split this function more from the Ansible roles I created different handlers for ini, yml and json, so the customer can choice: https://github.com/eumel8/ansible-otc/tree/dev/playbooks/vars
- Testing. Ansible developement goes really fast, so code can sometimes break because things aren't working anymore in newer versions of Ansible or Python. I started to play with Travis and included some functional tests: https://travis-ci.org/eumel8/ansible-otc
- Documentation. There are multiple Markdown files for use cases and role description. I switched to Sphinx, which is more portable and documentation is nearly to the code like the role documentation. A published version is on http://ansible-otc.readthedocs.io/en/dev/?badge=latest
As you can see the next release of Ansible-OTC will contain a lot of changes, so it will be easier to use OTC with Ansible.