⭕
OpenShift Network Playground
  • Getting Started
    • OpenShift Network Playground Overview
    • Architecture
      • Fedora CoreOS
      • Network
      • DNS
      • DHCP
      • Proxy
      • DNS64
      • NAT64
      • PXE
  • Installation
    • Prerequisites
    • vSphere
    • RHEV
    • Libvirt
  • User Guide
    • Cockpit Console
    • CLI Tool
    • OpenShift Bare Metal IPI Cluster
    • Single Node OpenShift Cluster
    • Backup OpenShift Releases
    • Additional Network Interfaces
    • Cluster Node Access
    • Tools
    • Collection of Manifests
  • Troubleshooting
    • Cockpit Cluster deployment
  • FAQ
    • What is ONP?
    • What problem it solves?
    • How to access the cluster that is deployed inside the ONP?
Powered by GitBook
On this page
  • Custom OS
  • Upgrade
  • Access
  • Virtualization
  1. Getting Started
  2. Architecture

Fedora CoreOS

PreviousArchitectureNextNetwork

Last updated 1 year ago

Custom OS

The operating system that the OpenShift Network Playground uses is the custom one. It is assembled with the help of and . The OpenShift Network Playgound holds all the configurations. After building the ISO image, it is again customized to embed the ignition in the ISO to boot at the first time. The ONP provides the detailed information about the customization.

Upgrade

As of now, the in-place upgrade is not possible.

Access

Once the OpenShift Network Playground is deployed, it starts the Cockpit service and enables the access using the endpoint https://<IP>:9090. For both the Cockpit and SSH connection the credentials will be:

Credentials

username: onp

password: Onp@123

Virtualization

The virtualization is achieved with the help of Libvirt and KVM packages. To manage the virtual machines, the host has the package virsh. The virt-manger GUI tool can add the ONP host with the SSH credentials.

fedora-coreos-config
coreos-assembler
ignition
GitHub repository