Ales Nosek - The Software Practitioner

Helping you navigate the world of Kubernetes.

May 14, 2018 - Comments - events

Red Hat Summit 2018

Last week, I had the pleasure of attending Red Hat Summit 2018. It was hosted at the Moscone Center in San Francisco, May 8-10, 2018. I greatly enjoyed this conference and would like to share with you some of the interesting things I learned there.

You can view video recordings of the general sessions as well as a selection of the breakout sessions on YouTube.

Major announcements

Red Hat OpenShift on Azure. Red Hat and Microsoft are introducing OpenShift as a fully managed service on Azure. This brings customers the possibility to freely move workloads between their on-premise OpenShift clusters and Azure. Many of the Azure services will be accessible from within OpenShift via the Service Catalog. In the future, Windows containers will be supported alongside Linux containers. Support for Red Hat OpenShift on Azure will be provided by both Red Hat and Microsoft.

Red Hat and IBM working toward a hybrid cloud. Red Hat and IBM are expanding their collaboration to bring together enterprise application platforms, Red Hat OpenShift and IBM Cloud Private. IBM’s recent move to re-engineer its entire software portfolio with containers, including WebSphere, MQ Series and Db2 will allow it to make this sofware available on the hybrid cloud with IBM Cloud Private and Red Hat OpenShift serving as the common foundation.

Both major announcements go along with the Red Hat’s vision of the future being the hybrid cloud. There’s no doubt that Red Hat stands behind the hybrid cloud. In one of the general sessions, I heard Red Hat’s Paul Cormier saying:

Hybrid cloud is the only practical way forward.

Sessions attended

  • CoreOS and Red Hat
    • After Red Hat acquired CoreOS in January this year, developers from both companies are busy with merging features of CoreOS Tectonic into Red Hat OpenShift. While CoreOS Tectonic was focused on operators, Red Hat OpenShift was more oriented toward developers. After the merge is completed, Red Hat OpenShift should become a product with a strong appeal to both operators and developers.
    • OpenShift console will be extended by an Admin console which is based on the Tectonic Console.
    • OpenShift is embracing the Operator Framework originally developed by CoreOS. Initially, more than 60 ISVs are planning to provide certified OpenShift operators to end users.
    • Quay Enterprise is going to be rebranded to Red Hat Quay. It remains a standalone product. Customers with higher demands may prefer leveraging Red Hat Quay in place of the integrated OpenShift image registry.
    • CoreOS Container Linux and RHEL Atomic Host are going to be merged into a new container operating system called Red Hat CoreOS. Initially, Red Hat CoreOS is going to be based on RHEL 7.5, however, later on Red Hat CoreOS will be updated faster than RHEL.
  • Next-generation tools for container technology
    • Dan Walsh discussed several Linux container related tools developed by his team: CRI-O container runtime, Buildah, Skopeo, and Podman. With a certain dose of sarcasm, Dan explained the flaws in the design of the Docker tool - mainly the unfortunate decision to create a “big fat” Docker daemon. Podman is a command-line tool that reimplements the Docker functionality without the need for a Docker daemon. In the future, Podman could replace the Docker tool.
  • Kubernetes and the platform of the future
    • This was a chat with Clayton Coleman (Chief Engineer for OpenShift) and Brandon Philips (previously CTO of CoreOS, acquired by Red Hat) about the future of Kubernetes and OpenShift projects.
    • Kubernetes is considered to be a new distributed operating system. “We have a deployment target for the open-source community for multiple machines, as we had Linux as a target for a single machine”.
  • Low-risk mono to microservices: Istio, Teiid, and Spring Boot
    • In this session, I learned about several open-source projects that may come in handy when moving toward a microservice architecture: Arquillian is an integration testing framework, Istio is a service mesh, Kiali is an Istio observability project, apicurio is a tool for designing RESTful APIs according to the OpenAPI specification, Teiid is a data virtualization system.
    • If you want to release your software frequently, monolithic architecture may become a bottleneck. You can begin to break up your monolithic project into microservices to speed up the release process. If you’ve gotten to the point where you can go faster, stop breaking things up! You don’t want to cross the point of diminishing returns. If there is some monolith left in your project, that’s okay.
  • OpenShift roadmap: You won’t believe what’s next
    • Prometheus monitoring system is going to be integrated into OpenShift more deeply. In addition to monitoring, metrics collected by Prometheus are going to be used for container auto healing.
    • Work is underway for Open Virtual Network (OVN) to become the default OpenShift SDN in the future.
    • Red Hat is investing in the KubeVirt project whose goal is to run virtual machines on Kubernetes/OpenShift.
    • Red Hat is also investing in Apache OpenWhisk. OpenWhisk is a serverless platform allowing to run functions on Kubernetes.
  • Intelligent applications on OpenShift from prototype to production
    • OpenShift is entering the big data arena. This was an introductory talk about running Spark on OpenShift for machine learning. If you are interested to run data analysis on OpenShift, check out the rad analytics project.

Some photos from the event

Opening keynote session.

Harbor cruise for Red Hat Certified Professionals, including myself ;-)

San Francisco skyline as viewed from the cruise.

Designing a Common Build System Four Ansible Practices I Would Recommend

comments powered by Disqus