{"schedule": {"version": "0.12", "base_url": "https://cfp.loadays.org/2019/schedule/", "conference": {"acronym": "2019", "title": "LOADays 2019", "start": "2019-05-04", "end": "2019-05-05", "daysCount": 2, "timeslot_duration": "00:05", "days": [{"index": 1, "date": "2019-05-04", "day_start": "2019-05-04T04:00:00+02:00", "day_end": "2019-05-05T03:59:00+02:00", "rooms": {"Room A": [{"id": 24, "guid": "3b99fbdf-11d7-5afc-9c3a-3ed9c16c9ab5", "logo": "", "date": "2019-05-04T10:00:00+02:00", "start": "10:00", "duration": "00:50", "room": "Room A", "slug": "2019-24-linux-curriculum-at-hogent", "url": "https://cfp.loadays.org/2019/talk/GT8NS7/", "title": "Linux curriculum at HOGENT", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "An overview of the Linux curriculum in the \"professional bachelor applied information theory\" at University College Ghent", "description": "In this talk, an overview is given of the Linux curriculum at University College Ghent (HOGENT). This is *not* intended as a commercial, but rather to share our experience, and to ask feedback from the audience. HOGENT is planning to implement a curriculum reform the coming years and would welcome input from professional Linux users and admins. If you are a Linux trainer or teacher, you are welcome to use our course materials that we made available under open content licenses.\r\n\r\nTalk topics include:\r\n\r\n- course overview\r\n- assignments\r\n- student projects and team work\r\n- open source/open content teaching tools and materials\r\n\r\nTalk slides are available here: <https://gitpitch.com/bertvv/presentation-linux-hogent>", "recording_license": "", "do_not_record": false, "persons": [{"id": 23, "code": "JP8JQQ", "public_name": "Bert Van Vreckem", "biography": "Bert is lecturer ICT at University College Ghent (HOGENT), where he teaches a.o. Linux, research techniques, and intro statistics.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 11, "guid": "3582dfc5-589e-5f67-9fdb-3a8cc47edb09", "logo": "", "date": "2019-05-04T11:00:00+02:00", "start": "11:00", "duration": "00:50", "room": "Room A", "slug": "2019-11-what-did-you-inspec-", "url": "https://cfp.loadays.org/2019/talk/TH8CFY/", "title": "What did you InSpec?", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "InSpec is an open-source testing framework created by Chef that enables you to specify compliance, security, and other policy requirements.\r\nHowever, the usage is not limited to compliance checking only as you can also use it to validate systems.\r\nAnd, as InSpec is code which is very readable and easy to implement it can be used in a lot of different cases.\r\nFor a DevOps engineer it is a must have to tool which can be used together with Chef, Puppet or Ansible.\r\nWe will go over the language, use cases along with short demo\u2019s.\r\n\r\nThe workshop can be retrieved from https://github.com/gdha/inspec-workshop", "description": "", "recording_license": "", "do_not_record": false, "persons": [{"id": 12, "code": "ARLQZP", "public_name": "Gratien D'haese", "biography": "Gratien D\u2019haese is a Belgian independent IT Consultant who is already 28 years active in the Unix world (and with Linux since its invention in 1991).\r\nGratien has a broad experience with Unix/Linux in general, Open Source software, Unix networking and security, big system administration tasks, clustering, consultancy, DevOps (chef, ansible) and project management.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 2, "guid": "6c7368e3-5110-5fcc-860c-4054a26f711b", "logo": "", "date": "2019-05-04T12:00:00+02:00", "start": "12:00", "duration": "00:50", "room": "Room A", "slug": "2019-2-running-containers-and-operating-system-images-with-systemd-nspawn", "url": "https://cfp.loadays.org/2019/talk/MHC3BE/", "title": "Running containers and Operating System images with systemd-nspawn", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "In this talk, I'll discuss `systemd-nspawn` and `machinectl`, two tools in the `systemd` suite for container management. We'll discuss the tools themselves, the differences between them and other container solutions and how to manage systems that use these containers.", "description": "According to its manpage, `systemd-nspawn`\r\n\r\n> may be used to run a command or OS in a light-weight namespace container. In many ways it is similar to chroot(1), but more powerful since it fully virtualizes the file system hierarchy, as well as the process tree, the various IPC subsystems and the host and domain name.\r\n\r\nIn this talk, I'll go over what all of this means, how to use `systemd-nspawn` and how nspawn differs from docker, lxc/lxd and qemu-kvm.\r\n\r\nAfter that, I'll discuss how to use the `systemd-nspawn` and `machinectl` commands, how to run services inside containers and how to introspect the containers.\r\n\r\nAfter this, I'll quickly touch on a related project called `mkosi` (\"make operating system image\") that can be used to create images for containers and virtual-machines in one go.\r\n\r\nBasic knowledge of systemd service management and containers is recommended to attend this talk.", "recording_license": "", "do_not_record": false, "persons": [{"id": 3, "code": "HXKQX3", "public_name": "Pieter Lexis", "biography": "Educated as a Systems and Network Engineer and having dabbled with DevOps-y things for years, Pieter's official title now is \"Senior PowerDNS Engineer\". As such, he works on the PowerDNS source code, the build/CI/packaging pipeline and running the infrastructure around the PowerDNS open source project. He is also involved in the broader DNS operations and standards communities to make the Internet a better place.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 4, "guid": "0fdbcc0c-53f4-5358-a848-32de51345d44", "logo": "", "date": "2019-05-04T14:00:00+02:00", "start": "14:00", "duration": "00:50", "room": "Room A", "slug": "2019-4-how-i-accidentally-became-an-electronics-engineer-actually-i-didn-t-", "url": "https://cfp.loadays.org/2019/talk/SSUFZP/", "title": "How I accidentally became an electronics engineer (actually I didn't)", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "A fun deep dive into the world of designing electronics intended to encourage you to look beyond the end of your (software) nose", "description": "AWS, DNS, K8S. We're being exposed to IT so much at work that some of us just call it a day and refrain from any hobbyist computer stuff in our private time and maybe you have also more important responsibilities to take care of such as family. But maybe you do still from time to time try to pursuit a fun project. If so, and if you know the \"bottom drawer syndrome\" (enthusiastically started something, first lost time, then interest, now stored things away out of sight) or if can relate to \"buy first, think of a purpose for it later\", this talk is for you.\r\n\r\nMy motivation was to bring both purpose and John Bercow, I mean, orrrrder, to two such gadgets in my drawer, a Raspberry Pi and a LED stripe. In this talk I will recap and take you along on my journey during which I had to leave my usual comfort zone, that is software, and delve into hardware and electronics. Don't worry, this is not going to be a electronics 101 course. Instead I want to remedy some unwarranted fears and encourage you to look beyond the end of your (software) nose as electronics illiteracy did not stop me either from being successful as proven by my PiStripe uHAT which I'll bring along (and maybe give away one or two).", "recording_license": "", "do_not_record": false, "persons": [{"id": 6, "code": "GB989R", "public_name": "Pieter Hollants", "biography": "Pieter Hollants solaced himself over the downfall of Commodore and the beloved Amiga world by discovering the Un*x/Linux world at the end of the 90s. After fulfilling his duties at the IT support front, promoting himself to \"Senior Intern\" at Linux outlet SUSE and abusing his position as Linux Systems Engineer at German Air Traffic Control to become a resident conference who^Wvisitor, Pieter has returned to enjoying the freedom as an independent Linux developer, consultant and occasional involuntary sysadmin. He runs some small Open Source projects of his own but mostly contributes every now and then, here and there and blogs at http://www.0xf8.org.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 17, "guid": "4639cf1e-4eec-52b9-a272-a6ecd5508d80", "logo": "", "date": "2019-05-04T15:00:00+02:00", "start": "15:00", "duration": "00:50", "room": "Room A", "slug": "2019-17-it-consultant-zabbix-trainer", "url": "https://cfp.loadays.org/2019/talk/VGS9YL/", "title": "IT Consultant / Zabbix Trainer", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "how to configure Low Level Discovery in zabbix for JMX  and what is new or coming in 4.2", "description": "The presentation will explain how to setup the configuration in Zabbix so that Java applications can be monitored without manual configuration. Ex: Garbage collectors will be created on the fly and removed when changed. In the end we will see a short overview about what's new in 4.2 or what can be expected in 4.2 (a non LTS version)", "recording_license": "", "do_not_record": false, "persons": [{"id": 19, "code": "3PSHPY", "public_name": "Patrik Uytterhoeven", "biography": "IT consultant and official Zabbix Trainer @ open-future with high interest in Zabbix, SeLinux and Ansible", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 5, "guid": "7d457e44-7a10-5c1f-8cea-ce419188f860", "logo": "", "date": "2019-05-04T16:00:00+02:00", "start": "16:00", "duration": "00:50", "room": "Room A", "slug": "2019-5-zabbix-loadable-c-modules-and-low-level-discovery-lld-", "url": "https://cfp.loadays.org/2019/talk/YCCEB3/", "title": "Zabbix loadable C modules and Low-Level Discovery (LLD)", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "We will discuss how we implement Zabbix Low-Level Discovery directly from a C module and how the same C module is used to provide up-to-date information to Zabbix items.", "description": "The Zabbix monitoring system has a number of different methods by which it can obtain monitoring data from systems or things it knows nothing about, but it can use scripts or programs you configure it to run in order to obtain the data you are interested in. You are probably aware of User Parameters and External Checks, and we'll shortly recapitulate.\r\n\r\nOne very powerful but slightly more complicated method for obtaining external data is by using dynamically loadable C modules. We discuss what these are, how you create them, and how you can use this arguably most efficient method to provide monitoring data to Zabbix.\r\n\r\nLow-level discovery provides a way to automatically create items, triggers, and graphs for different entities. For instance, Zabbix can automatically start monitoring file systems or network interfaces on your machine, without the need to create items for each file system or network interface manually.\r\n\r\nUsing a real-life practical example which we (_OwnTracks_) use to monitor vehicles issued with GPS trackers which end up communicating via MQTT, we will discuss how we implement Zabbix Low-Level Discovery directly from a C module and how the same C module is used to provide up-to-date information from the vehicles to Zabbix items. This basic principle can easily be adapted to provide similar functionality to Internet of Things (IoT) projects. While it helps if you can read a bit of C language code, if you cannot, we'll explain what's going on behind the scenes.", "recording_license": "", "do_not_record": false, "persons": [{"id": 2, "code": "VBP8TD", "public_name": "Jan-Piet Mens", "biography": "Jan-Piet Mens is an independent Unix/Linux consultant and sysadmin who's worked with Unix-systems since 1985.\r\n\r\nJP does odd bits of coding and works extensively with the Domain Name System and as such, he authored the book Alternative DNS Servers as well as a variety of other technical publications.  He contributed several modules and the documentation system to the Ansible project and dreamed up the Open Source (MQTT-based) OwnTracks project. JP blogs at https://jpmens.net", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 22, "guid": "16411920-44f6-5c87-80a0-e60d5b16116d", "logo": "", "date": "2019-05-04T17:00:00+02:00", "start": "17:00", "duration": "00:50", "room": "Room A", "slug": "2019-22-ignite-karaoke", "url": "https://cfp.loadays.org/2019/talk/9LFBP3/", "title": "Ignite Karaoke", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "@arrfab suggested this on Twitter", "description": "We can mix the regular ignites with a random deck of ingites and have volunteers present these slides before the Pizza party starts", "recording_license": "", "do_not_record": false, "persons": [{"id": 4, "code": "C7TBFX", "public_name": "Kris Buytaert", "biography": "Kris Buytaert is a long time Linux and Open Source Consultant. He's one of instigators of the devops movement, currently working for Inuits\r\n\r\nHe is frequently speaking at, or organizing different international conferences and has written about the same subjects in different Books, Papers and Articles\r\n\r\nHe spends most of his time working on bridging the gap between developers and operations with a strong focus on High Availability, Scalability , Virtualisation and Large Infrastructure Management projects hence trying to build infrastructures that can survive the 10th floor test, better known today as the cloud while actively promoting the devops idea !\r\n\r\nHis blog titled \"Everything is a Freaking DNS Problem\" can be found at http://www.krisbuytaert.be/blog/", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 36, "guid": "260380de-493a-5d27-b0d4-a26ca1fca8bb", "logo": "", "date": "2019-05-04T17:15:00+02:00", "start": "17:15", "duration": "00:05", "room": "Room A", "slug": "2019-36-tying-shoe-laces", "url": "https://cfp.loadays.org/2019/talk/CWEDZJ/", "title": "Tying shoe laces", "subtitle": "", "track": null, "type": "Ignite", "language": "en", "abstract": "It's not a coincidence if your shoe strings loosen all the time. If something that works for others but not for you, you're probably not doing it right.", "description": "", "recording_license": "", "do_not_record": false, "persons": [{"id": 30, "code": "U7SPR3", "public_name": "Tim Speetjens", "biography": "Yes, I have one", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 18, "guid": "178d4a64-b3e6-59b5-87a6-33e6447b4cb7", "logo": "", "date": "2019-05-04T17:30:00+02:00", "start": "17:30", "duration": "00:05", "room": "Room A", "slug": "2019-18-what-not-to-puppetize-and-how-to-do-it-anyway", "url": "https://cfp.loadays.org/2019/talk/YE8TTQ/", "title": "What not to puppetize and how to do it anyway", "subtitle": "", "track": null, "type": "Ignite", "language": "en", "abstract": "A brief rundown of what not to use puppet for and how to use it anyway.", "description": "Add a customer there were some interesting problems that where solved by puppet where it was not the best solution. This will showcase some of those cases. This ranges from adding users to adding a bookmark in the chosen browser.", "recording_license": "", "do_not_record": false, "persons": [{"id": 21, "code": "U3EHCF", "public_name": "Bart Janssens", "biography": "instance_no: 1957695\r\nDoes try to write decent code but does not always succeed.\r\n\r\nWorking for Inuits.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 32, "guid": "46fd66e5-838a-5433-943c-73f670f4f52f", "logo": "", "date": "2019-05-04T17:35:00+02:00", "start": "17:35", "duration": "00:05", "room": "Room A", "slug": "2019-32-using-prometheus-to-monitor-your-deployment-pipelines", "url": "https://cfp.loadays.org/2019/talk/ZQXSAG/", "title": "Using Prometheus to monitor your deployment pipelines", "subtitle": "", "track": null, "type": "Ignite", "language": "en", "abstract": "In order to optimize your continous delivery pipelines, and to make sure your delivery actually is continuous, it can be useful to collect some metrics about your pipelines. This talk is an introduction to jenkins_exporter, which can be employed in order to use Prometheus for this purpose.", "description": "In order to optimize your continous delivery pipelines, and to make sure your delivery actually is continuous, it can be useful to collect some metrics about your pipelines. \r\n\r\nThis talk introduces the Prometheus jenkins_exporter that I wrote for this purpose, how it came to be, and how it can be used to monitor pipelines in Jenkins. Specifically, ways to create dashboards and alerting rules to detect drift between versions deployed to different environments are discussed.", "recording_license": "", "do_not_record": false, "persons": [{"id": 28, "code": "AXJHHK", "public_name": "Lander Van  den Bulcke", "biography": "Open Source Consultant at Inuits; ops guy focusing on monitoring, infrastructure as code and continuous delivery.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 49, "guid": "5e6f4be7-d7e2-5906-8612-579c7e1f3073", "logo": "", "date": "2019-05-04T18:00:00+02:00", "start": "18:00", "duration": "03:00", "room": "Room A", "slug": "2019-49-pizza-party", "url": "https://cfp.loadays.org/2019/talk/XUKLKX/", "title": "Pizza Party", "subtitle": "", "track": null, "type": "Workshop", "language": "en", "abstract": "Have your own pizza build on demand.\r\nPizza and Beer ..\r\nMore Pizza..\r\nChat with speakers and attendees ...  \r\nMore Pizzaa ..", "description": "", "recording_license": "", "do_not_record": true, "persons": [{"id": 40, "code": "FLCTJZ", "public_name": "Everybody", "biography": null, "answers": []}], "links": [], "attachments": [], "answers": []}], "Room B": [{"id": 23, "guid": "12f79ca2-a6ea-56c5-9db5-d4dc605e074f", "logo": "", "date": "2019-05-04T11:00:00+02:00", "start": "11:00", "duration": "00:50", "room": "Room B", "slug": "2019-23-clean-bash-leveling-up-your-shell-scripting-skills", "url": "https://cfp.loadays.org/2019/talk/TFRG8G/", "title": "Clean Bash - Leveling up your shell scripting skills", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "An opinionated talk on maintainable, testable and readable shell scripts.", "description": "Bash: the scripting language everyone loves to hate. The syntax is arcane and hard to read. Some concepts, e.g. booleans and exit status, are fundamentally different than other scripting or programming languages, which confuses novice users. Bash is not really suited for large, complex scripts.  Bash scripts are usually one-offs: written once, and rarely touched afterwards.\r\n\r\nConsequenty, coding style, testability and maintainability are way down (or absent) on a sysadmin's priority list. \r\n\r\nHowever, Bash is ubiquitous. It's in every Linux and UNIX distribution, on every Mac laptop and, nowadays, even on Windows (when Git is installed). Even in the leanest, minimal, stripped down box, you at least have Bash. There are no dependencies. It's impossible to underestimate how useful it is for automating tedious tasks involving files or text. So there is definitely value in learning and using Bash.\r\n\r\nLet's say you have written shell scripts before. When you look at them again after months or even years, do you still understand how they work? If running a script fails, would you know what went wrong and how to look for bugs in the code? Does your script continue to work correctly if you run it multiple consecutive times? If you answered \"no\" to any of these questions, this talk is for you.\r\n\r\nTopics include:\r\n\r\n- Debugging and testing scripts\r\n- Improving readability\r\n- Robert C. Martin's \"Clean code\" applied to Bash\r\n- Idempotence\r\n\r\nTalk slides are available here: <https://gitpitch.com/bertvv/presentation-clean-bash>", "recording_license": "", "do_not_record": false, "persons": [{"id": 23, "code": "JP8JQQ", "public_name": "Bert Van Vreckem", "biography": "Bert is lecturer ICT at University College Ghent (HOGENT), where he teaches a.o. Linux, research techniques, and intro statistics.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 28, "guid": "2484e0ec-3969-526f-9118-12edd3be1426", "logo": "", "date": "2019-05-04T12:00:00+02:00", "start": "12:00", "duration": "00:50", "room": "Room B", "slug": "2019-28-what-you-most-likely-did-not-know-about-sudo-", "url": "https://cfp.loadays.org/2019/talk/8FUM8T/", "title": "What you most likely did not know about sudo\u2026", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "Sudo is installed by default on almost all Linux system, still even system administrators often only know it is the \u201cprefix\u201d to use before entering a command requiring root privileges. Learn how much more this simple looking tool can do!", "description": "Everybody knows sudo, right? Sudo allows a system administrator to give certain users  the ability to run some commands as root, while logging the executed commands and their arguments. It is installed by default on almost all Linux systems, and is available for most commercial UNIX systems. Still, even system administrators often only know it is the \u201cprefix\u201d to use before entering a command requiring root privileges. Learn how much more this simple looking tool can do!\r\nMost of the times the default configuration allows a group of users to run any commands:\r\n%wheel\tALL=(ALL)\tALL\r\nIt\u2019s a good first step, better than using the root account directly. This way you can trace who ran what commands on the system. But there are a lot more possibilities when configuring sudo, making your system more secure.\r\nLife is simple when when you have to give access a single user to a single command. But as soon as  you have multiple users with the same access rights, it is not just shorter but also easier to maintain, if you use aliases.\r\nFor added security, you can add a hash of binaries to sudo. This way if the binary changes for any reasons, like modifying it through a successful exploit, you can prevent it from being used.\r\n\r\nUsing sudo does not make much sense without proper logging and alerting. There are three major possibilities:\r\n- syslog: all events are logged to syslog. For additional security, collect sudo logs  centrally, so a malicious user cannot delete them easily.\r\n- e-mail: sudo can send e-mail alerts on different kinds of failures\r\n- debug: in depth logging of subsystems, mostly useful for developers\r\nSession recording is a fourth possibility. The terminal output can be saved in a local file and played back. You can play back what happened, even if the user started up an interactive shell.\r\n\r\nInstead of maintaining the sudoers file on each of your systems, you can use LDAP to configure sudo. It has some differences compared to a sudoers file, but also many advantages: \r\n- local users cannot manipulate the rules,\r\n- is easier to maintain,\r\n- goes live immediately.\r\n\r\nStarting with version 1.8, sudo has a plugin-based architecture. You can replace or extend sudo functionality using plugins. This way users can keep starting applications the usual way using sudo, but have a different configuration or policy engine behind the sudo command. There are both open source and commercial plugins available. For example the sudo_pair plugin \u2013 developed in Rust \u2013 enables monitoring and makes it possible to require interactive approval of sessions.\r\n\r\nAs you can see, sudo has several lesser-known features that can make monitoring and access management easier for large organizations.", "recording_license": "", "do_not_record": false, "persons": [{"id": 15, "code": "GZRL3C", "public_name": "Peter Czanik", "biography": "Peter is an engineer working as evangelist at Balabit (a One Identity business), the company that developed syslog-ng. He assists distributions to maintain the syslog-ng package, follows bug trackers, helps users and talks regularly at conferences (SCALE, All Things Open, FOSDEM, LOADays, and others). In his limited free time he is interested in non-x86 architectures, and works on one of his PPC or ARM machines.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 6, "guid": "eb0fbe03-fdd0-5bde-b382-589fe829da53", "logo": "", "date": "2019-05-04T14:00:00+02:00", "start": "14:00", "duration": "00:50", "room": "Room B", "slug": "2019-6--re-discovering-the-ssh-tips-for-ansible-centos-infra-use-case-", "url": "https://cfp.loadays.org/2019/talk/BJP9KR/", "title": "(Re)discovering the ssh tips for Ansible (CentOS infra use case)", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "Discovering (or rediscovering) ssh tips and tricks we can use with (and without) Ansible", "description": "While a lot of people are using Ansible for easy ad-hoc tasks, using it in production to manage a fleet of servers spread all around the world can be challenging.\r\nIn this talk we'll cover how , for the CentOS.org infra, we tried to optimize the playbook execution and we'll mainly dive into ssh itself (so the presented options can also be used outside of Ansible). \r\nWe'll cover things like :\r\n\r\n * SSH CA and certificates,\r\n * how to use bastion/jump hosts , etc.\r\n * Multi DC configurations\r\n\r\nSlides from this talk (uploaded after event) : https://people.centos.org/arrfab/Events/Loadays-2019/loadays-2019-ssh-tips.html", "recording_license": "", "do_not_record": false, "persons": [{"id": 7, "code": "8DYURM", "public_name": "Fabian Arrotin", "biography": "Fabian discovered (seriously) Linux in 1998 (his first \"attempt\" was a Slackware) with a RHL 5.2 install and tested several distributions but he always went back to Red Hat. When they decided to split between RHEL and Fedora core, he couldn't support the cost of an Enterprise Linux distro for his personal needs ( on his workstations and servers ). He then found the CentOS Project and quickly tried to be part of that community. Actually sysadmin for the CentOS.org infra", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 30, "guid": "c1fd7bcb-c0ce-5cfc-815c-ddd000d6f292", "logo": "/media/2019/images/9XX37L/molecule-logo.png", "date": "2019-05-04T15:00:00+02:00", "start": "15:00", "duration": "00:50", "room": "Room B", "slug": "2019-30-molecule-test-ansible", "url": "https://cfp.loadays.org/2019/talk/9XX37L/", "title": "molecule test ansible", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "Some bits about the Ansible Molecule project and how to use it.", "description": "A common need when you develop Ansible playbooks is to validate roles before production. For that purpose you need to instantiate temporary infrastructure. Molecule has been created to respond to this need. It has been promoted as a part of the official Ansible ecosystem last year, and is about to become the official SDK to develop and test new roles. This talk will take for granted that you know Ansible, present the tooling landscape around Molecule, showcase some basic usage, dissect a standard molecule scenario, and give some insights on how to integrate the tool in a delivery pipeline. We will go through some implementations done in the open source community: roles published in galaxy, projects relying on molecule for their QA testing (Kubernetes Operator SDK).", "recording_license": "", "do_not_record": false, "persons": [{"id": 26, "code": "7PX9DJ", "public_name": "Fabrice @themr0c Flore-Th\u00e9bault", "biography": "*  User & contributor in Molecule / Ansible ecosystem.\r\n*  Free Software Infrastructure Automation professional.\r\n*  Tech writer.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 3, "guid": "edaa68da-9e68-5a23-ad93-cbabe07e71ab", "logo": "", "date": "2019-05-04T16:00:00+02:00", "start": "16:00", "duration": "00:50", "room": "Room B", "slug": "2019-3-ansible-in-a-real-world-situation-the-one-role-to-rule-them-all-", "url": "https://cfp.loadays.org/2019/talk/GWEDAS/", "title": "Ansible in a real world situation. The One Role to Rule Them All!!", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "Ansible is often used in a develop, accept and production environment, but there are no general use cases available.\r\n\r\nThis presentation shows how we solved the `dev`, `acc` and `prod` environment issues within a clients setup and how this can aid you in solving similar problems.", "description": "When using Ansible in a real world situation, where there are multiple environments, like `dev`, `tst`, `acc` and `prod` it's hard to make sure the Ansible setup isn't to complex and that everything works.\r\n\r\nThis presentation can assist you to make decisions for you own environment.\r\nDecisions about:\r\n- Inventory structure\r\n- Variable setup", "recording_license": "", "do_not_record": false, "persons": [{"id": 5, "code": "QFXUTH", "public_name": "Ton Kersten", "biography": "Ton Kersten is a Linux consultant and trainer at AT Computing in the Netherlands where he helps customers with all kinds of Linux challenges. He also tries to teach them the Linux and Ansible way of life.\r\n\r\nHe enjoys music, photography, playing darts (badly), good food, beer and whisky.\r\n\r\n- Twitter: @TonKersten\r\n- Github: https://github.com/tonk", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 26, "guid": "541bfa2a-e4fd-50d5-8ced-0b6686e14e48", "logo": "", "date": "2019-05-04T17:00:00+02:00", "start": "17:00", "duration": "00:50", "room": "Room B", "slug": "2019-26-scaling-ansible", "url": "https://cfp.loadays.org/2019/talk/9LVCKD/", "title": "Scaling Ansible", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "Ansible agentless nature and semplicity are definitely two of the aspects that determined its incredible success as configuration management and automation tool.\r\nHowever - despite being very powerful - agentless automation has some limitations when managing complex distributed infrastructures.\r\nIn this talk we will deep dive into Ansible configuration and execution model to discuss some workarounds to effectively implement Ansible as configuration management tool at scale without compromising performances and/or the readability of the code.", "description": "This talk will walk through the incremental enhancements to the default Ansible configuration we have applied to one of the PowerDNS projects to effectively take down Ansible execution time from ~60 to ~6 minutes.", "recording_license": "", "do_not_record": false, "persons": [{"id": 24, "code": "CLQXCB", "public_name": "Andrea Tosatto", "biography": "Automating all the things with YAML.\r\nSRE at PowerDNS and Open-Xchange.", "answers": []}], "links": [], "attachments": [], "answers": []}]}}, {"index": 2, "date": "2019-05-05", "day_start": "2019-05-05T04:00:00+02:00", "day_end": "2019-05-06T03:59:00+02:00", "rooms": {"Room A": [{"id": 31, "guid": "8a405700-d7ba-5999-be4b-0212b3b595e9", "logo": "", "date": "2019-05-05T10:00:00+02:00", "start": "10:00", "duration": "00:50", "room": "Room A", "slug": "2019-31-come-listen-to-me-i-m-a-fraud-a-story-on-impostor-syndrome", "url": "https://cfp.loadays.org/2019/talk/RXVVYW/", "title": "Come listen to me, I\u2019m a fraud; a story on impostor syndrome", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "A story on success, impostor syndrome and self-inflicted, perpetually non-existent comfort zone.\r\n\r\nDo you recognize the fear of being exposed as a fraud? I do. And I\u2019ve had success because of the syndrome. I\u2019ve learned to harness it, figuring out how to come to terms with it and use it for good. I now live in a self-inflicted, perpetually non-existing comfort zone, and I want you to, too!", "description": "Come listen to my story and learn to harness your self-doubt. I\u2019m here to show the little things I did differently every day:\r\n- How being kind to yourself is key. Forgive, don\u2019t judge. Accept who you are.\r\n- Learn about your internal convictions and expose these to the world authentically and honestly.\r\n- How complimenting yourself and others goes a long way\r\n- Build a case for yourself by keep notes of people saying nice things about you\r\n- Self-doubt is a powerful tool as a leader, if used consciously\r\n- Focus on (professional) relationships, not on technical merit\r\n- Harness feedback, even it\u2019s scary\r\n\r\nWith these small, incremental improvements, I now live in a self-inflicted, perpetually non-existing comfort zone. I\u2019m constantly in the imposter zone, because I\u2019m constantly doing new things, learning new skills, meeting new people. And I love it! It has brought me many smaller and larger victories, a career that\u2019s led me to new and unexpected ventures and most importantly, a network of friends and relationships I otherwise would never have had.", "recording_license": "", "do_not_record": false, "persons": [{"id": 27, "code": "T9KRFR", "public_name": "Joep Piscaer", "biography": "Once a virtualization and storage consultant, he built IaaS-platforms, created an army of Community Managers, built, led and developed a team of technical architects.\r\nMost recently, Joep is building the Jumbo Tech Campus. Jumbo is the second biggest supermarket in the Netherlands and the fastest growing online supermarket of the Netherlands.\r\n\r\nAs the Technical Pathfinder, Joep is responsible for the DevOps way-of-work, tooling, cloud and open source strategy of the Tech Campus, the e-commerce software development house of Jumbo.\r\n\r\nHe runs his own blog, VirtualLifestyle.nl, speaks at industry events, occasional guest on theCube and he's a frequent delegate for TechFieldDay events.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 45, "guid": "a8ff4f67-acb7-5820-8364-bb573a7a35af", "logo": "", "date": "2019-05-05T11:00:00+02:00", "start": "11:00", "duration": "00:50", "room": "Room A", "slug": "2019-45-scale-your-metrics-with-elasticsearch", "url": "https://cfp.loadays.org/2019/talk/RDVLUD/", "title": "Scale Your Metrics with Elasticsearch", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "\"Only accept features that scale\" is one of Elasticsearch's engineering principles. So how do we scale metrics stored in Elasticsearch? And is that even possible on a full-text search engine?", "description": "This talk explores:\r\n\r\n* How are metrics stored in Elasticsearch? And how does this translate to disk use as well as query performance?\r\n* What does an efficient, multi-tier architecture look like that balances speed for today's data against density for older one?\r\n* How can you compress metrics and what does the mathematical model look like for that?\r\nWe are trying this hands-on during the talk since this has become much simpler recently.", "recording_license": "", "do_not_record": false, "persons": [{"id": 35, "code": "7AHGGJ", "public_name": "Philipp Krenn", "biography": "Philipp lives to demo interesting technology. Having worked as a web, infrastructure, and database engineer for more than ten years, Philipp is now working as a developer advocate at Elastic \u2014 the company behind the open source Elastic Stack consisting of Elasticsearch, Kibana, Beats, and Logstash. Based in Vienna, Austria, he is constantly traveling Europe and beyond to speak and discuss about open source software, search, databases, infrastructure, and security.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 41, "guid": "ac11e452-fdb3-58ea-b1b7-00a58c9d9c69", "logo": "", "date": "2019-05-05T12:00:00+02:00", "start": "12:00", "duration": "00:50", "room": "Room A", "slug": "2019-41-containers-on-rhel-8", "url": "https://cfp.loadays.org/2019/talk/8LJVEM/", "title": "Containers on RHEL 8", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "An introduction to Podman and Buildah", "description": "With the RHEL 8 Beta release it became clear that Red Hat is officially dropping Docker for its own solution when it comes to containers: podman. A technology which is not new but nevertheless interesting to take a look at. During this presentation the details on podman as well as the tool to build containers, Buildah, is discussed and demonstrated.", "recording_license": "", "do_not_record": false, "persons": [{"id": 33, "code": "G3GBAF", "public_name": "Christopher Peeters", "biography": "Christopher is a freelance systems engineer and trainer in Linux and open source technology. He's mainly focussing on automation and container technology. He's also active as a member of the ITGilde cooperative where he helps to build a community of freelance open source professionals. Christopher is a stickerless ambassador.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 47, "guid": "79464697-8c5c-55ae-9284-7adf261844ea", "logo": "", "date": "2019-05-05T14:00:00+02:00", "start": "14:00", "duration": "00:50", "room": "Room A", "slug": "2019-47-chaos-security-engineering-in-kubernetes", "url": "https://cfp.loadays.org/2019/talk/STRQAS/", "title": "Chaos security engineering in Kubernetes", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "Enterprise systems are as secure as their resilience to system glitches and human error. Even external attacks do not succeed so much due to the superiority or ingenuity of the attacker, rather than due to the inherent imperfections of our systems. Deployment of distributed technologies like Kubernetes in organizations fall short with respect to security. A pragmatic methodology is required, whereby chaos engineering principles are extended to security. In this session we will be discussing about patterns, best practices on how to continuously approach defense from inherent security flaws in software.", "description": "", "recording_license": "", "do_not_record": true, "persons": [{"id": 36, "code": "RCUQ7M", "public_name": "Evis Barbullushi", "biography": "A seasoned professional with solid experience in developing distributed solutions and solving significant integration challenges in organizations.\r\nSpecialities: Distributed Computing, Architecting for the Cloud, AppDev in the Cloud, Containerisation, Cloud and Microservices, Kubernetes, Openshift, Hybrid Cloud, AWS, GCP, Azure, Containers & Infrastructure\r\nSite Reliability Engineering, Microservices.\r\nCurrently working in the EMEA Specialist AppDev/Openshift team as Senior Solution Architect at Red Hat.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 37, "guid": "31fde532-b4de-5fe7-8c1b-77b902b9677d", "logo": "", "date": "2019-05-05T15:00:00+02:00", "start": "15:00", "duration": "00:50", "room": "Room A", "slug": "2019-37-ci-cd-with-openshift", "url": "https://cfp.loadays.org/2019/talk/PLVANX/", "title": "CI/CD with OpenShift", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "OpenShift, the container platform by Red Hat, offers Platform as a Service capabilities on top of Kubernetes.\r\nIn this presentation we will explore multiple ways to get from source to a deployable container. Once built, the story continues with having it deployed in multiple environments.", "description": "", "recording_license": "", "do_not_record": false, "persons": [{"id": 30, "code": "U7SPR3", "public_name": "Tim Speetjens", "biography": "Yes, I have one", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 40, "guid": "eb4dbb21-69c0-5104-858d-6ef4853d3d3a", "logo": "", "date": "2019-05-05T16:00:00+02:00", "start": "16:00", "duration": "00:50", "room": "Room A", "slug": "2019-40-metalk8s-an-opinionated-kubernetes-distribution-with-a-focus-on-long-term-on-prem-deployments", "url": "https://cfp.loadays.org/2019/talk/RCKHSM/", "title": "MetalK8s: An opinionated Kubernetes distribution with a focus on long-term on-prem deployments", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "In this session we discuss why Scality decided to use Kubernetes as the platform underlying its on-premise storage and data-management solutions, why we started the open-source [MetalK8s](https://github.com/scality/metalk8s) project, the lessons we learned from the first iteration, and most importantly what's coming in the next major version.", "description": "End of 2017, [Scality](https://scality.com) decided to use Kubernetes as a deployment mechanism for its open-source [Zenko](https://github.com/scality/Zenko) data-orchestration solution. When looking for a solution to deploy Kubernetes on-premise, including suitable operational tooling and the ability to run in enterprise customer data centers, we failed to find a readily-available suitable offering based on our long experience with these environments, neither open-source nor commercial. At this point, the decision was made to create a new distribution based on the well-known Kubespray project, but further focusing on on-premise, long-term clusters with built-in operational tooling, and make this available as an open-source project, also spearheading open-source development practices within the company.\r\n\r\nBased on the learning building and deploying [MetalK8s](https://github.com/scality/metalk8s) 1.x, we took the decision to base deployment and operations of our future products on Kubernetes as well, increasing the importance of Kubernetes as an 'implementation detail' of the final product running in our enterprise customer datacenters. At this point, we further increased investments into MetalK8s, and also take the opportunity to change its architecture based on some shortcomings identified in MetalK8s 1.x.\r\n\r\nAfter introducing our path to Kubernetes and an overview of the goals of the project, we discuss what MetalK8s 2.x brings compared to the 1.x version, including the architectural switch from 'one-off' Ansible playbooks to a more dynamic, event-driven cluster orchestrated through SaltStack, as well as a glimpse at its local storage (disks, RAID controllers,...) management features, and how these resources are made available to solutions deployed in the cluster.", "recording_license": "", "do_not_record": false, "persons": [{"id": 32, "code": "SKSNFG", "public_name": "Nicolas Trangez", "biography": "Nicolas is a senior architect in the Scality R&D team, focusing on defining and designing delivery, installation and operability of cloud-native solutions. He has a background in cloud, distributed systems and automation for 10+ years, and is a long-term Open Source contributor to various projects in multiple stacks. Startup-minded, Haskell\u2019ist and music lover. \r\n\r\nNicolas has spoken at OpenStack Summits, OUD, KubeCon/CloudNativeCon and various other occasions, and is the co-author of ACM RELENG and ICFP papers.\r\n\r\nTwitter: [@eikke](https://twitter.com/eikke/)\r\nGitHub: [NicolasT](https://github.com/NicolasT/)", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 8, "guid": "5c61683a-d34a-56a5-b7c6-58ae8e5d2dff", "logo": "/media/2019/images/BAQXTL/from-tesla-hacking-to-freedomev.jpg", "date": "2019-05-05T17:00:00+02:00", "start": "17:00", "duration": "00:50", "room": "Room A", "slug": "2019-8-from-tesla-hacking-to-the-freedomev-project", "url": "https://cfp.loadays.org/2019/talk/BAQXTL/", "title": "From Tesla Hacking to the FreedomEV Project", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "Tesla Hacking experiments evolved into the FreedomEV OpenSource project. Where are we at, what are the challenges and what's new?", "description": "Why should we take control of our own cars? What are the risks and rewards? What can we do and what not. What should we do and don't?", "recording_license": "", "do_not_record": false, "persons": [{"id": 8, "code": "ZZLH9E", "public_name": "Jasper Nuyens", "biography": "Jasper Nuyens is the founder and CEO of Linux Belgium. A small organisation which is providing Linux Courses, Consultancy and Support for the Linux operating system in Belgium. \r\nMr Nuyens has been pushing Linux forwards since he came into contact with it in 1993, and professionally since 1998.\r\nSoftware becomes a more important part of vehicles and he hopes this will be driven by OpenSource - not in a enclosed box - but in a way which empowers users instead.", "answers": []}], "links": [], "attachments": [], "answers": []}], "Room B": [{"id": 27, "guid": "1fb227b7-475f-5897-97b5-4996b1623a4a", "logo": "", "date": "2019-05-05T10:00:00+02:00", "start": "10:00", "duration": "00:50", "room": "Room B", "slug": "2019-27-oss-diversity-is-good-aka-why-we-run-various-dns-servers-flavors-in-centos-org-infra-", "url": "https://cfp.loadays.org/2019/talk/YBSKZA/", "title": "OSS diversity is good (aka why we run various DNS servers flavors in CentOS.org infra)", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "Why does centos.org infra use both Bind, Unbound, PowerDNS and Dnsmasq ? let's find out !", "description": "In this (brief ?) talk, we'll cover some of the DNS servers flavors that we use in the CentOS.org infra, and reasons why we do. So covering why we use Bind, Unbound, PowerDNS and Dnsmasq in parallel, as (depending on the case) authoritative or resolver/caching server[s]\r\n\r\nSlides : https://people.centos.org/arrfab/Events/Loadays-2019/loadays-2019-dns-diversity.html", "recording_license": "", "do_not_record": false, "persons": [{"id": 7, "code": "8DYURM", "public_name": "Fabian Arrotin", "biography": "Fabian discovered (seriously) Linux in 1998 (his first \"attempt\" was a Slackware) with a RHL 5.2 install and tested several distributions but he always went back to Red Hat. When they decided to split between RHEL and Fedora core, he couldn't support the cost of an Enterprise Linux distro for his personal needs ( on his workstations and servers ). He then found the CentOS Project and quickly tried to be part of that community. Actually sysadmin for the CentOS.org infra", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 15, "guid": "db4e397f-149b-54ca-9509-2570460079b2", "logo": "", "date": "2019-05-05T11:00:00+02:00", "start": "11:00", "duration": "00:50", "room": "Room B", "slug": "2019-15-bootstrap-your-cloud-infrastructure-using-puppet-and-hashicorp-stack", "url": "https://cfp.loadays.org/2019/talk/EPUH7J/", "title": "Bootstrap your Cloud Infrastructure using puppet and HashiCorp stack", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "This talk walks the audience through a green fields exercise that sets up service discovery using Consul, infrastructure as code using terraform, using images build with packer and configured using puppet.", "description": "We all love infrastructure as code, we automate everything \u2122 but how many  \r\nof us can really say we could destroy and recreate our core infrastructure  \r\nwithout human intervention. Can you be sure there isnt a DNS problem or  \r\nthat all the things \u2122 are done in the right order This talk walks the  \r\naudience through a green fields exercise that sets up service discovery  \r\nusing Consul, infrastructure as code using terraform, using images build  \r\nwith packer and configured using puppet.", "recording_license": "", "do_not_record": false, "persons": [{"id": 17, "code": "AHDMCX", "public_name": "Bram Vogelaar", "biography": "Bram spent the first part of his career as a Molecular Biologist , he then moved on to supporting his peers by building tools and platforms for them with a lot of Open Source technologies, after which he joined Inuits to focus on helping more people to deliver their software with Open Source tools.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 33, "guid": "9f9feec9-5235-5277-b623-615c73d7d310", "logo": "", "date": "2019-05-05T12:00:00+02:00", "start": "12:00", "duration": "00:50", "room": "Room B", "slug": "2019-33-leveraging-prometheus-service-discovery", "url": "https://cfp.loadays.org/2019/talk/BT8PAW/", "title": "Leveraging Prometheus service discovery", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "There are a multitude of ways to let Prometheus know about the systems you want it to monitor. This talk will introduce a number of ways you can leverage service discovery to let it generate the configuration for you.", "description": "Prometheus can get its list of targets in a number of ways: from static configurations over built-in service discovery all the way to custom service discovery implementations. This talk will give a brief overview of Prometheus itself, explain how these mechanisms actually work and show how they can be leveraged to autogenerate Prometheus configuration in a number of scenarios, from more classic environments based on Puppet to more \"modern\" environments employing immutable infrastructure principles.", "recording_license": "", "do_not_record": false, "persons": [{"id": 28, "code": "AXJHHK", "public_name": "Lander Van  den Bulcke", "biography": "Open Source Consultant at Inuits; ops guy focusing on monitoring, infrastructure as code and continuous delivery.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 20, "guid": "0bb85464-1c1e-5ba3-b3a5-fd7e9ab7e658", "logo": "", "date": "2019-05-05T14:00:00+02:00", "start": "14:00", "duration": "00:50", "room": "Room B", "slug": "2019-20-how-to-write-efficient-and-correct-mysql-recipes-for-you-configuration-management-system-in-2019", "url": "https://cfp.loadays.org/2019/talk/SZKHT9/", "title": "How to write efficient and correct MySQL recipes for you configuration management system in 2019", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "MySQL is a very popular open source database and for many years now, devops world encouraged DBAs to use system management system like puppet, chef, ansible to take care of the installation and configuration of their favorite database. This was brilliant ! However all the implementations are not optimal and mostly because there was no easy way to do differently. Since MySQL 8.0, with the help of the MySQL X admin API (and other improvements), it's now much easier and safer to manage MySQL via a configuration management system.", "description": "During this session, I won't tell which configuration management system to use neither which module bit I will explain what are the errors to not perform again and why. I will also show you how to use the MySQL X Admin API in your recipes.", "recording_license": "", "do_not_record": false, "persons": [{"id": 22, "code": "CLNHFG", "public_name": "lefred", "biography": "\"@lefred\" has been consulting OpenSource and MySQL for over 15 years. After graduating in Management Information Technology, Fr\u00e9d\u00e9ric Descamps started his career as a developer for an ERP under HPUX. He will then opt for a career in the world of open-source by joining one of the first Belgian start-up dedicated 100% to free projects around GNU/Linux. It is in 2011 that lefred joined Percona, one of the leading MySQL-based specialists. He decided to join the MySQL Community Team in 2016 as a MySQL Community Manager for EMEA & APAC. Fr\u00e9d\u00e9ric is also a regular speaker of OpenSource Conferences. His blog mostly dedicated to MySQL is http://lefred.be", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 10, "guid": "55fdc131-f406-5d5e-8265-594d81395e7d", "logo": "", "date": "2019-05-05T15:00:00+02:00", "start": "15:00", "duration": "00:50", "room": "Room B", "slug": "2019-10-open-source-databases-and-ha", "url": "https://cfp.loadays.org/2019/talk/NWYKLV/", "title": "Open Source databases and HA", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "High Availability is essential for business-critical applications. What options exist in the community and why should I choose one or the other?", "description": "HA is an essential part of an architectural setup. \r\nDeclaration of business and application requirements are essential during the actual design of the optimal database architecture. With increased levels of availability comes complexity and in some case operation woes. \r\n\r\nSo what are the increased availability options within MySQL and other open source RDBMS solutions? How would they compare to each other?\u001b \r\n\r\nThis presentation will cover:\r\n\r\n- The concept of increased availability, why it's essential for operations, what pitfalls exist.\r\n- Differences in between availability concepts\r\n- HA and MySQL \r\n- HA and PostgreSQL\r\n- HA and MongoDB\r\n- HA and the cloud, the good and the bad\r\n- Why HA is not DR", "recording_license": "", "do_not_record": false, "persons": [{"id": 11, "code": "MYVYST", "public_name": "Dimitri Vanoverbeke", "biography": "Dim0 has been working with Open Source technologies for 15 years. Since the age of six (thanks parents), he has been interested in everything with a digital pulse. \r\n\r\nDimitri is working for over 5 years for Percona, an Open Source focussed database organisation as a Solution engineer.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 42, "guid": "c785fa30-4452-53df-98e6-01100df81916", "logo": "", "date": "2019-05-05T16:00:00+02:00", "start": "16:00", "duration": "00:50", "room": "Room B", "slug": "2019-42-look-mom-without-containers-", "url": "https://cfp.loadays.org/2019/talk/G97X3X/", "title": "Look mom without containers!", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "An implementation of an immutable infrastructure using packer.io, terraform and ansible.", "description": "In this talk will be illustrate an example of deployment of a vertically and horizontally scalable infrastructure using the immutable infrastructure paradigm, on digitalocean cloud platforms.", "recording_license": "", "do_not_record": false, "persons": [{"id": 34, "code": "XVZFGQ", "public_name": "Matteo Valentini", "biography": "Developer at Nethesis. | Enthusiastic developer and system administrator, with a special interest in fields of networking, Linux embedded, security and cloud automations.", "answers": []}], "links": [], "attachments": [], "answers": []}, {"id": 7, "guid": "607e568b-0587-563c-b155-c0970d72ab38", "logo": "", "date": "2019-05-05T17:00:00+02:00", "start": "17:00", "duration": "00:50", "room": "Room B", "slug": "2019-7-running-a-mainframe-on-your-laptop-for-fun-and-profit-", "url": "https://cfp.loadays.org/2019/talk/YMXZRK/", "title": "Running a mainframe on your laptop (for fun and profit)", "subtitle": "", "track": null, "type": "Talk", "language": "en", "abstract": "In this session the speaker will help you in taking your first steps towards running your own mainframe on your own laptop. For fun. Or profit.", "description": "Yes, this talk is about running your own mainframe on your own hardware. Mainframes are old, yes, but they are still very much alive. New hardware is still being developed and there are a lot of fresh jobs in this area too. A lot of mainframes run COBOL workloads. COBOL is far from a dead language. It processes an estimated 85% of all business transactions, and 5 billion lines of new COBOL code are written every year. In this session the speaker will help you in take your first steps towards running your own mainframe. If you like then after this session you can continue to build your knowledge of mainframe systems using the links provided during the talk. Come on in and learn the basics of a completely different computer system! And it will take you less than an hour to do that!", "recording_license": "", "do_not_record": false, "persons": [{"id": 9, "code": "R8C8EU", "public_name": "Jeroen Baten", "biography": "I solve IT problems. I connect system A with system B. I teach people stuff. I do this mostly with Linux systems. To make stuff happen I write a lot of custom scripts in various programming lanuages like Perl, Python, Bash, C, Java, Ruby, etc. I have clients all over the world (Australia, Switserland, US, etc).\r\n\r\nI am also the project leader of the open source LibrePlan project. So go to that site (libreplan.org) if you need more information about an open source web-based project management application.\r\n\r\nI occasionally write an article for my blog, but I have also written a number of books:\r\n\r\n    LPI Essentials (Dutch)\r\n    Open ICT voor Managers (Dutch)\r\n    LibrePlan, the missing manual (English, French)", "answers": []}], "links": [], "attachments": [], "answers": []}]}}]}}}