This article is the final in a series taking readers on a journey to peek inside life in a Red Hat Open Innovation Labs residency.
This is the top-tier experience for any customer*, exposing them to open collaboration, open technologies, and fast agile application delivery methods.
This experience often escapes organizations attempting digital transformation, so through submersion in an Open Innovation Labs residency, Red Hat shares its experience in managing, developing, and delivering solutions with communities, open technologies, and open collaboration.
Join me as I share experiences from inside a real-life residency, watching Red Hat work intimately with a customer, exposing new ways of working, leveraging open technologies using fast, agile application delivery methods and open collaboration.
In the first part, I shared what’s in a Red Hat Open Innovation Labs residency. Then in part two, I looked at what I encountered as the residency progressed towards delivery. All that’s left now is to share the delivery week, known as Demo Day.
Continue reading “Inside a Red Hat Open Innovation Labs Residency (Part 3)”
This series (see Part 1) takes the reader on a journey, taking a peek inside a Red Hat Open Innovation Labs Residency. A top tier experience for any customer*, a residency exposes them to open collaboration, open technologies, and fast agile application delivery methods.
This experience often escapes organizations attempting digital transformation. Through submersion in an Open Innovation Labs residency, Red Hat shares its experience in managing, developing, and delivering solutions. This is about successfully achieving organizational goals using open communities, open technologies, and open collaboration.
Join me as I share experiences from inside a real life residency. Watch how Red Hat engages intimately with a customer by exposing them to new ways of working. It is demonstrated by leveraging open technologies using fast and agile application delivery methods with open collaboration.
Continue reading “Inside a Red Hat Open Innovation Labs Residency (Part 2)”
OpenShift and Kubernetes do a great job of working to make sure calls to your microservice are routed to the correct pods. After all, that’s one of the raison d’être for Kubernetes: routing and load balancing. What if, however, you want to customize the routing? What if you want to run two versions at the same time? How do Istio Route Rules handle this?
[This is part two of my ten-week Introduction to Istio series. My previous article was Part 1: Introduction to Istio; It Makes a Mesh of Things.]
Continue reading “Istio Route Rules: Telling Service Requests Where to Go”
This series takes the reader on a journey, taking a peek inside life in a Red Hat Open Innovation Labs residency. This is the top tier experience for any customer; exposing them to open collaboration, open technologies, and fast agile application delivery methods.
Continue reading “Inside a Red Hat Open Innovation Labs Residency – (Part 1)”
Logs are like gold dust. Taken alone they may not be worth much, but put together and worked by a skillful goldsmith they may become very valuable. OpenShift comes with The EFK stack: Elasticsearch, Fluentd, and Kibana. Applications running on OpenShift get their logs automatically aggregated to provide valuable information on their state and health during tests and in production.
The only requirement is that the application sends its logs to the standard output. OpenShift does the rest. Simple enough!
In this blog I am covering a few points that may help you with bringing your logs from raw material to a more valuable product.
Continue reading “Structured application logs in OpenShift”
Beta testing is fundamentally all about the testing of a product performed by real users in a real environment. There are many tags we use to refer to the testing of similar characteristics, such as User Acceptance Testing (UAT), Customer Acceptance Testing (CAT), Customer Validation, and Field Testing (more popular in Europe). Whichever tag we use for these testing cases, the basic components are more or less the same. To discover and fix potential issues, this involves the user and front-end user interface (UI) testing, as well as the user experience (UX) related testing. This always happens in the iteration of the software development lifecycle (SDLC) where the idea has transformed into design and has passed the development phases, while the unit and integration testing has already been completed.
Continue reading “Beta Testing in the Ever-Changing World of Automation”
APIs are critical to automation, integration and developing cloud-native applications, and it’s vital they can be scaled to meet the demands of your user-base. In this article, we’ll create a database-backed REST API based on the Python Falcon framework using Red Hat Software Collections (RHSCL), test how it performs, and scale-out in response to a growing user-base.
Continue reading Create a scalable REST API with Falcon and RHSCL
This article would help to configure http2 protocol support for the camel-undertow component.
- Camel’s undertow component use embedded undertow web-container of version undertow-core:jar:1.4.21. This version also supports the http2 connection.
- I have used camel version 2.21.0-SNAPSHOT from upstream https://github.com/apache/camel.
- Also, the curl version to test application using camel-undertow component is 7.53.1. This curl version supports –http2 flag for sending an http2 request.
- I have also used nghttp to test application from linux terminal. However, this article is not about http2 insights.
- For http2 details, I found articles  and  helpful.
Continue reading “Using Camel-Undertow component supporting http2 connection”
Jenkinsfiles have only become a part of Jenkins since version 2 but they have quickly become the de-facto standard for building continuous delivery pipelines with Jenkins.
Jenkinsfile allows defining pipelines as code using a groovy DSL syntax and checking it into source version control which allows you to track, review, audit and manage the lifecycle of changes to the continuous delivery pipelines the same way that you manage the source code of your application.
Although the groovy DSL syntax which is called the “scripted syntax” is the more well-known and established syntax for building Jenkins pipelines and was the default when Jenkins 2 was released. Support for a newer declarative syntax is also added since Jenkins 2.5 in order to offer a simplified way for controlling all aspects of the pipeline. Although the scripted and declarative syntax provides two ways to define your pipeline, they both translate to the same execution blocks in Jenkins and achieve the same result.
Continue reading “Building Declarative Pipelines with OpenShift DSL Plugin”
Before I start talking about IT and how you can manage, control, and optimize your Hybrid IT infrastructure, I propose that we reflect directly on your living room, where you usually watch TV, movies, listen to music, play video games, etc. Even if you do not enjoy this type of entertainment, you know that for each of these devices, it is common to use a remote control allowing you to switch between them, manage them, and control all of your favorite programming. While these devices are converging to an all-in-one architecture, they are truly multi-functional. We’ve learned how to handle remote controls at a very young age and it’s the reality we live in. In this case, you are faced with heterogeneous devices and various remote controls, where the number of controls increases as you acquire new devices. It is difficult to have to manage the complexity of a simple task that is to manage your schedule, operating multiple devices, through different controls, with numerous features, and different vendors. Products and vendors bring specific features, use different nomenclature, and provide some features which may or may not be compatible with each other. Going beyond, some of these features made available by vendors, will not even be used throughout the lifetime of these devices, a real waste!
Picture 1 – Managing many devices with many remote controls
Considering this scenario, you might be wondering: What is the relationship of the complexity of having to deal with various entertainment devices and remote controls with your IT infrastructure? And what does this have to do with cloud computing or Hybrid IT?
Continue reading “CloudForms: Manage your IT and Hybrid Cloud through a single platform”