Overview

The OpenShift Online web console is a user interface accessible from a web browser. Developers can use the web console to visualize, browse, and manage the contents of projects.

JavaScript must be enabled to use the web console. For the best experience, use a web browser that supports WebSockets.

CLI Downloads

You can download and unpack the CLI from the Command Line Tools page on the web console for use on Linux, MacOSX, and Windows clients.

Command Line Tools

Browser Requirements

The following browser versions and operating systems can be used to access the web console.

Table 1. Browser Requirements
Browser (Latest Stable) Operating System

Firefox

Fedora 23, Windows 8

Internet Explorer

Windows 8

Chrome

Fedora 23, Windows 8, and MacOSX

Safari

MacOSX, iPad 2, iPhone 4

Project Overviews

After logging in, the web console provides developers with an overview for the currently selected project:

Web Console Project Overview
Figure 1. Web Console Project Overview
1 The project selector allows you to switch between projects you have access to.
2 Create new applications using a source repository or using a template.
3 The Overview tab (currently selected) visualizes the contents of your project with a high-level view of each component.
4 Applications tab: Browse and perform actions on your deployments, pods, services, and routes.
5 Builds tab: Browse and perform actions on your builds and image streams.
6 Resources tab: View your current quota consumption and other resources.
7 Storage tab: View persistent volume claims and request storage for your applications.
8 Monitoring tab: View logs for builds, pods, and deployments, as well as event notifications for all objects in your project.

JVM Console

For pods based on Java images, the web console also exposes access to a hawt.io-based JVM console for viewing and managing any relevant integration components. A Connect link is displayed in the pod’s details on the Browse → Pods page, provided the container has a port named jolokia.

Pod with a Link to the JVM Console
Figure 2. Pod with a Link to the JVM Console

After connecting to the JVM console, different pages are displayed depending on which components are relevant to the connected pod.

JVM Console
Figure 3. JVM Console

The following pages are available:

Page Description

JMX

View and manage JMX domains and mbeans.

Threads

View and monitor the state of threads.

ActiveMQ

View and manage Apache ActiveMQ brokers.

Camel

View and and manage Apache Camel routes and dependencies.

OSGi

View and manage the JBoss Fuse OSGi environment.

StatefulSets

A StatefulSet controller provides a unique identity to its pods and determines the order of deployments and scaling. StatefulSet is useful for unique network identifiers, persistent storage, graceful deployment and scaling, and graceful deletion and termination.

StatefulSets view in OpenShift
Figure 4. StatefulSet in OpenShift Online