Bryant Son Bryant Jimin Son is a Senior Consultant at Red Hat, a technology company known for its RHEL Linux server and open source contributions. He is a certified RHCSA, Openshift Specialist in both Application Development and Infrastructure. At his current professional work, he successfully delivered three projects for Fortune 500 companies and provided the technical consulting. He has been worked on building the technology for clients leveraging the Red Hat and open source technology stacks like Openshift, BPM, CodeReady Workspace, Cloud Native Virtualization, ReactJS, and DevOps. As a part of Red Hat GiveBack, he has been contributed to number of public technical blog articles through Red Hat:, Red Hat Developer Blog, Red Hat Enable Systadmin, Red Hat Service. He is also a Dallas First & Third lead, which means leading the Dallas-Fort Worth based Red Hat consultants to host the events twice per month. He also initiated and led the University of Texas at Dallas x Red Hat night with a Red Hat Academy Manager, a Red Hat Principal Software Engineer, and a Red Hat Senior Consultant. He recruited new Red Hat consultants from the on-campus recruiting event at the University of Texas at Austin, and participated as the technical interviewer for the new candidates. Bryant is the President and Founder of non-profit association called Korean American IT Association group, known as KAITA ( As the President of KAITA, he flew multiple time to Los Angeles, Chicago, Austin, San Francisco, and Seoul (South Korea) to host the physical meetups, and he hosted three large size conferences: two at Dallas, Texas and one at Seoul, South Korea. He also reached out to KOTRA, Dallas Korea Chamber of Commerce to partner with them on the joint events. You can find KAITA news published through the major Dallas Korean Newspapers like NewKorea and KTN Dallas/DK Net Radio. With an entrepreneur personality, he started three startup projects previously and get inspired by actually meeting the various leaders along his career including Michael Dell, Tom Horton, Mark Cuban, Stephen Bird Josh Bauer, Bill Gates, Jeff Lawson, and Robert Metcalfe. He is actively working on updating the KAITA website and planning to launch two additional websites in near future (est. 2011). Prior to joining Red Hat, Bryant was a tech lead and an Architect at Citi Group's Citi Cloud team, directly reporting to the Director of Citi Cloud team. He built the in-house private Infrastructure as a Service (IaaS) cloud platform serving 8,000+ teams across Citi departments. He invented the DevOps workflow process using Jenkins pipeline and Apache Tomcat, migrated hundreds of tighly integrated Spring Boot + Java + JSP applications to the microservice, Single Page Application (SPA) webpage using REST API and AngularJS, thus reducing the deployment failure closer to 0% and increasing the server uptime to 99.99% by adopting the 12 Factor app principles. He proactively presented more than 30 time at Citi, including the presentation to VMWare consultants, the multiple presentation about the Citi Cloud vision to CTO and VP levels at Citi, and Citi conference presentations at Tampa, Florida and Toronto, Canada. He was the Subject Matter Expert (SME) of User Interface (UI) at his team, a DevOps lead, a full stack developer, and the direct mentor for two interns. Prior to Citi, Bryant worked at American Airlines, building the website (he helped to setup the functionality in AAdvantage page after you signed-in) in an Agile team as a full stack developer. At the Operation Research team at American Airlines, he created an internal flight decision tool to decide the cancellation, management, and scheduling of the flights to be used by the flight operators and dispatchers, which later became the patented technology. So, if you get a delay or a cancelation with American Airlines, you can partially blame him. As one of the ADEPT employees, which means he was recruited out of college, he also build the mobile/email notification page and the first ADEPT recruiting page. He also presented multiple time to VPs/SVPs, the CIO, and upper management when he was at the American Airlines. He also worked at IBM, Home Depot Austin Technology Center, KLRU-TV at Austin, Texas, and Division of Instructional Innovation and Assessment at the UT Austin. Bryant graduated with Bachelor of Sciences in Computer Science and Aerospace Engineering with minor concentration in Business at University of Texas at Austin.

Areas of Expertise

Openshift, Code Ready Workspace, RHEL, Full Stack Web Development, DevOps, Cloud Native Application

Recent Posts

How to switch Red Hat OpenShift Virtualization from hardware virtualization to software emulation

How to switch Red Hat OpenShift Virtualization from hardware virtualization to software emulation

OpenShift Virtualization is a feature of Red Hat OpenShift Container Platform (OCP) and OpenShift Kubernetes Engine that allows you to run and manage virtual machine workloads alongside container workloads. Based on the open source project KubeVirt, the goal of OpenShift Virtualization is to help enterprises move from a VM-based infrastructure to a Kubernetes-and-container-based stack, one application at a time.

In my previous article, I showed you how to set up and enable OpenShift Virtualization running on Amazon Web Services Elastic Compute Cloud (AWS EC2). In that article, I noted that OpenShift Virtualization looks for hardware virtualization by default, which requires a bare-metal server instance. If you are running OpenShift on AWS EC2, as I do, then you have to enable software emulation over the default hardware virtualization. Otherwise, you need a bare-metal instance from the public cloud provider or a pure bare-metal solution.

In this article, I show you how to switch OpenShift Virtualization from its default of hardware virtualization to QEMU-based software emulation. You will then be able to start and operate a virtual machine through OpenShift Virtualization, even in a non-bare metal instance such as AWS EC2.

Continue reading “How to switch Red Hat OpenShift Virtualization from hardware virtualization to software emulation”

Enable OpenShift Virtualization on Red Hat OpenShift

Enable OpenShift Virtualization on Red Hat OpenShift

Imagine an information technology (IT) world where everything is ideal: Every company has switched over to cloud-native applications, every application is containerized, everything is automated, and the IT people see that the world is good. Things are not so ideal in the real world, though, as we know. Applications remain tightly coupled with traditional virtual machine (VM) resources such as software libraries and hardware resources. The effort to migrate them from VMs to containers seems insurmountable, requiring years of dedicated spending and hours from developers and software architects.

The dilemma is that companies want all of their applications to eventually run on containers, but they also need to support applications running on VMs until that glorious shift happens. Given that application migration from VMs to containers will happen over the long haul, some companies are exploring a lift-and-shift approach. In theory, lift-and-shift would let us migrate tightly-coupled legacy applications to a container platform like Red Hat OpenShift. Rather than rewriting application code, developers would simply write interfaces (essentially, code with patterns) that are compatible with the existing structure.

Unfortunately, this scenario is unrealistic for legacy projects involving hundreds of application modules and packages. Therefore, it is logical to ask: What if there was a way to support existing applications running on virtual machines and new applications running on containers in one unified container-based platform?

Luckily, there is a way: Use a Kubernetes-based platform like OpenShift.

In this article, I introduce OpenShift Virtualization, a feature for Red Hat OpenShift Container Platform (OCP). OpenShift Virtualization allows you to run and manage virtual-machine workloads alongside container workloads.

Note: As of version 2.4 when CNV went GA, Container-Native Virtualization was renamed OpenShift Virtualization.

Continue reading “Enable OpenShift Virtualization on Red Hat OpenShift”

How to install CodeReady Workspaces in a restricted OpenShift 4 environment

How to install CodeReady Workspaces in a restricted OpenShift 4 environment

It’s your first day as a Java programmer, right out of college. You have received your badge, a shiny new laptop, and all of your software requests have been approved. Everything seems to be going well.

You install Eclipse and set up the required Java Development Kit (JDK) in your new development environment. You clone a project from the company’s GitHub repository, modify the code, and make your first commit. You are excited to be working on your first project.

But then, a few hours later, a senior programmer asks what version of the JDK you used. It seems that the pipeline is reporting a project failure. All you did was commit Java source code, not binary, and it worked perfectly on your local machine. What could possibly have gone wrong?

Coding in a restricted environment

The issue I described is well-known among programmers as the “It works on my computer, and I don’t know why it doesn’t work on your computer” problem. Fortunately, this is the type of problem Red Hat CodeReady Workspaces (CRW) can help you solve. CodeReady Workspaces is a cloud-based IDE based on Che. Whereas Che is an open source project, CRW is an enterprise-ready development environment that provides the security, stability, and consistency that many corporations require. All you have to do is open the CRW link in a web browser, sign in with your user credentials, and code inside the browser.

In this article, I show you how to install CodeReady Workspaces in a restricted Red Hat OpenShift 4 environment.

Continue reading “How to install CodeReady Workspaces in a restricted OpenShift 4 environment”