Monitoring Camel with Prometheus in Red Hat OpenShift

This walk-through example will encourage you to build an Apache Camel application from scratch, deploy it in a Kubernetes environment, gather metrics using Prometheus and display them in Grafana. Monitoring will automatically adjust when the system scales up or down. Table of Contents Introduction About Prometheus To-Do overview Scraping data The application Enabling Prometheus Enabling … Read moreMonitoring Camel with Prometheus in Red Hat OpenShift

OPENSHIFT NETWORKING FROM A CONTAINER/WORKLOAD POINT OF VIEW – PART 6: CONTROLLING EGRESS TRAFFIC

OpenShift 3.3 and later contain the functionality to route pod traffic to the external world via a well-defined IP address. This is useful for example if your external services are protected using a firewall and you do not want to open the firewall to all cluster nodes. The way it works is that a egress … Read moreOPENSHIFT NETWORKING FROM A CONTAINER/WORKLOAD POINT OF VIEW – PART 6: CONTROLLING EGRESS TRAFFIC

OPENSHIFT NETWORKING FROM A CONTAINER/WORKLOAD POINT OF VIEW – PART 5: OPENSHIFT ROUTER

In the OpenShift world, Services take place on the OSI Layer 3 / IP, while Routing is an OSI Layer 7 / HTTP/TLS concept. Once you’ve wrapped your head around this backwards choice of naming, things are fairly easy: An OpenShift Router is a component which listens on a physical host’s HTTP/S ports for incoming … Read moreOPENSHIFT NETWORKING FROM A CONTAINER/WORKLOAD POINT OF VIEW – PART 5: OPENSHIFT ROUTER

OPENSHIFT NETWORKING FROM A CONTAINER/WORKLOAD POINT OF VIEW – PART 4: CONTAINER NETWORKING USING OPENSHIFT/KUBERNETES SERVICES

To allow stable endpoints in an environment of ever changing starting and stopping Pods (and therefore constantly changing IP addresses), Kubernetes introduces (and OpenShift uses) the concept of services. Services are stable IP addresses (taken per default from the 172.30.0.0/16 subnet) that remain the same as long as the service exists. Connection requests to a … Read moreOPENSHIFT NETWORKING FROM A CONTAINER/WORKLOAD POINT OF VIEW – PART 4: CONTAINER NETWORKING USING OPENSHIFT/KUBERNETES SERVICES

OPENSHIFT NETWORKING FROM A CONTAINER/WORKLOAD POINT OF VIEW – PART 3: CONTAINER NETWORKING ACROSS OPENSHIFT NODES

So far, this sounds like a lot of effort to achieve a little more than a plain docker host – containers that can talk to each other and to the host network, potentially segregated based on kubernetes namespace. However OpenShift SDN also allows pods on different nodes to communicate with each other. To this end, … Read moreOPENSHIFT NETWORKING FROM A CONTAINER/WORKLOAD POINT OF VIEW – PART 3: CONTAINER NETWORKING ACROSS OPENSHIFT NODES

OpenShift Networking from a container/workload point of view – Part 2: Container Networking on an OpenShift Node

In OpenShift, networking is equally simple from a container point of view. Within the container’s namespace there is a eth0 network interface configured and services such as DNS just work. You can still use dedicated NICs on the host to isolate specific types of traffic. What’s the difference? It turns out there is hardly any … Read moreOpenShift Networking from a container/workload point of view – Part 2: Container Networking on an OpenShift Node

OpenShift 3.1 Networking from a container/workload point of view – Part 1: Container Networking on a plain Docker Host

From a container point of view, networking on a plain Docker Host is simple. A running container is nothing more than a Linux process which is namespaced and constrained with regards to access (SELinux) and resource consumption (cgroups). In each namespace, there is a single (virtual) network interface called eth0 which is assigned an IP … Read moreOpenShift 3.1 Networking from a container/workload point of view – Part 1: Container Networking on a plain Docker Host

All in One IoT Demo with JBoss Fuse, BPM Suite and BRMS

This is part 5 of my IoT series of blogs. So far we did look at the following topic Introduction into the planned scenario Building a Raspberry Pi based Smart Gateway ESP8266 and DHT22 based smart sensor Putting the Smart into the Smart IoT Device In this blog we will create a first running version of … Read moreAll in One IoT Demo with JBoss Fuse, BPM Suite and BRMS

Building the IoT Smart Gateway with Docker, Raspberry Pi and JBoss for the “lazy” ones – Ansible rules!

If you have followed my earlier posts, then you know, that I’m in the process of building an IoT Demo, with a Raspberry Pi2  as the Smart Gateway. During this process, I had to re-install my Raspberry multiple times, but after the second time I got a bit tired of doing the same steps over … Read moreBuilding the IoT Smart Gateway with Docker, Raspberry Pi and JBoss for the “lazy” ones – Ansible rules!

Putting the Smart into the Smart IoT Device

This is part 4 in my IoT series of blogs. The first parts did cover the following topics: Introduction into the planned scenario Building a Raspberry Pi based Smart Gateway ESP8266 and DHT22 based smart sensor This blog will describe how to enable the Smart Gateway to handle, enhance and forward incoming messages. As for … Read morePutting the Smart into the Smart IoT Device