openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 00:48:01 +01:00
Code Issues Releases Activity
Files
b861fb8d1fe02da170cbb977e5f74d9d1d76384c
openshift-docs/modules/telco-core-installation.adoc
Kevin Quinn be8a6929c7 TELCODOCS-1506 Telco CORE Reference Design Specification 
ref config updates

Adding generated YAML + modules from the RDS

Reorganizing TOC

Adding latest RDS updates

RDS doc updates

RDS YAML updates

Shanes review

latest updates + new components overview diagram

David J's review comments

CCS attributes update

Ian's review comments

adding Hari's deviations update

updating 4.14 link URLs

Generalizes scope and deviation topics for RAN and Core

updates for RDS prod version

update deviations wording

Updating deviation and scope topics

consolidate dev and scope topics + intro

Adding link to ztp-site-generate procedure

typo

final changes for RDS

typos

Ian's comments

update for RDS terminology

remove core CRs note

add GH core CRs link
2023-12-14 09:24:03 +00:00

26 lines
1.2 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
// Module included in the following assemblies:
//
// * telco_ref_design_specs/ran/telco-core-ref-components.adoc
:_mod-docs-content-type: REFERENCE
[id="telco-core-installation_{context}"]
= Installation
New in this release::
Description::
{rds-caps} clusters can be installed using the Agent Based Installer (ABI). This method allows users to install {product-title} on bare metal servers without requiring additional servers or VMs for managing the installation. The ABI installer can be run on any system for example a laptop to generate an ISO installation image. This ISO is used as the installation media for the cluster supervisor nodes. Progress can be monitored using the ABI tool from any system with network connectivity to the supervisor node’s API interfaces.
* Installation from declarative CRs
* Does not require additional servers to support installation
* Supports install in disconnected environment
Limits and requirements::
* Disconnected installation requires a reachable registry with all required content mirrored.
Engineering considerations::
* Networking configuration should be applied as NMState configuration during installation in preference to day-2 configuration by using the NMState Operator.
View Git Blame Copy Permalink