This repository provides a service that installs OpenShift. Its main benefits include a minimum amount of prerequisites from the user's infrastructure, as well as comprehensive pre-flight validations to ensure a successful installation. The service exposes either a REST API, or it can be deployed as an Operator where it exposes a Kubernetes-native API via Custom Resources. A UI is available that uses the REST API.
The Assisted Service can currently install clusters with highly-available control planes (3 hosts and above) and can also install Single-Node OpenShift (SNO). Highly available clusters are configured to use OpenShift's baremetal platform (typically used in bare metal IPI deployments), while SNO uses none (typically used in UPI deployments).
The basic flow for creating a new OpenShift cluster using the Assisted Service via the UI or REST API is:
- Create a new Cluster resource with the minimal required properties.
- Generate and download a bootable image which is customized for that cluster. This image is based on RHCOS and is customized to automatically run an agent upon boot.
- Boot the hosts that will form the cluster with the image from the previous step. The boot method is left to the user (e.g., USB drive, virtual media, PXE, etc.).
- The agent running on each host contacts the Assisted Service via REST API and performs discovery (sends hardware inventory and connectivity information).
- The UI guides the user through the installation, with the service performing validations along the way. Alternatively, this can be done via API.
- Once all validations pass, the user may initiate the installation. Progress may be viewed via the UI or API, and logs are made available for download directly from the service.
Below are some recent demos and blog posts:
- Blog, Jan 2021: Using the OpenShift Assisted Installer Service to Deploy an OpenShift Cluster on Bare Metal and vSphere
- Blog and demo, Dec 2020: Making OpenShift on Bare Metal easy
- Blog and demo, Oct 2020: It's Inside your House! Assisted Installer on Bare Metal Demonstration
By continuing to read this document you will learn how to build and deploy Assisted Service. If you are interested in using Assisted Service to deploy an OCP cluster, please refer to the User Documentation.
- Docker or Podman.
For podman make sure to enable podman socket and update skipper.yaml to map it properly - skipper https://github.com/stratoscale/skipper
- minikube (for tests)
- kubectl
- Python modules
pip install waiting
To push your build target to a Docker registry you first need to change the default target.
- Create a quay.io or Docker Hub account if you don't already have one. These instructions refer to quay.io, Docker Hub is similar.
- Create a repository called assisted-service.
- Make sure you have your
~/.docker/config.jsonfile set up to point to your account. For quay.io, you can go to quay.io -> User Settings, and click "Generate Encrypted Password" under "Docker CLI Password". - Login to quay.io using
docker login quay.io. - Export the
SERVICEenvironment variable to your Docker registry, and pass a tag of your choice, e.g., "test":
export SERVICE=quay.io/<username>/assisted-service:<tag>For the first build of the build container run:
skipper build assisted-service-buildskipper make allAfter every change in the API (swagger.yaml) the code should be generated and the build must pass.
skipper make generate-from-swaggerMore information is available here: Assisted Installer Testing
If you want to update the underlying operating system image used by the discovery iso, follow these steps:
-
Choose the base os image you want to use
-
Build the new iso generator image
# Example with RHCOS BASE_OS_IMAGE=https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/pre-release/latest/rhcos-4.6.0-0.nightly-2020-08-26-093617-x86_64-live.x86_64.iso make build-assisted-iso-generator-image
The deployment is a system deployment, it contains all the components the service need for all the operations to work (if implemented). S3 service (minio), DB and will use the image generator to create the images in the deployed S3 and create relevant bucket in S3.
make deploy-on-k8sBesides default minikube deployment, the service supports deployment to OpenShift cluster using ingress as the access point to the service.
skipper make deploy-all TARGET=oc-ingressThis deployment option have multiple optional parameters that should be used in case you are not the Admin of the cluster:
APPLY_NAMESPACE- True by default. Will try to deploy "assisted-installer" namespace, if you are not the Admin of the cluster or maybe you don't have permissions for this operation you may skip namespace deployment.INGRESS_DOMAIN- By default deployment script will try to get the domain prefix from OpenShift ingress controller. If you don't have access to it then you may specify the domain yourself. For example:apps.ocp.prod.psi.redhat.comDISABLE_TLS- Based on the target environment, routes that are being used are HTTPS. Setting it to true will make HTTP routes instead.
To set the parameters simply add them in the end of the command, for example:
skipper make deploy-all TARGET=oc-ingress APPLY_NAMESPACE=False INGRESS_DOMAIN=apps.ocp.prod.psi.redhat.comNote: All deployment configurations are under the deploy directory in case more detailed configuration is required.
This service supports optional UI deployment.
skipper make deploy-ui* In case you are using podman run the above command without skipper.
For OpenShift users, look at the service deployment options on OpenShift platform.
See - deploy monitoring
This feature is for internal usage and not recommended to use by external users. This option will select the required tag that will be used for each dependency. If deploy-all use a new tag the update will be done automatically and there is no need to reboot/rollout any deployment.
Deploy images according to the manifest:
skipper make deploy-all DEPLOY_MANIFEST_PATH=./assisted-installer.yamlDeploy images according to the manifest in the assisted-installer-deployment repo (require git tag/branch/hash):
skipper make deploy-all DEPLOY_MANIFEST_TAG=masterDeploy all the images with the same tag. The tag is not validated, so you need to make sure it actually exists.
skipper make deploy-all DEPLOY_TAG=<tag>Default tag is latest
There are two ways the assisted service can be deployed without using a Kubernetes cluster:
In this scenario the service and associated components are deployed onto your local host as a pod using Podman.
See the README for details.
assisted-service maintains a cache of openshift-baremetal-install binaries at
$WORK_DIR/installercache/. Persistent storage can optionally be mounted
there to persist the cache across container restarts. However, that storage
should not be shared across multiple assisted-service processes.
Currently there is no mechanism to expire openshift-baremetal-install binaries out of the cache. The recommendation for now is to allow the cache to use the container's own local storage that will vanish when the Pod gets replaced, for example during upgrade. That will prevent the cache from growing forever while allowing it to be effective most of the time.
A document that can assist troubleshooting: link
Markdown formatted documentation is available in the docs directory.
https://github.com/oshercc/coreos_installation_iso
Image in charge of generating the Fedora-coreOs image used to install the host with the relevant ignition file.
Image is uploaded to deployed S3 under the name template "installer-image-<cluster-id>".
The Assisted Installer is also available for users as a SAAS hosted in console.redhat.com.
More information is available here: Assisted Installer on console.redhat.com
It's possible to modify the discovery ISO (via the API) to enable password login for troubleshooting purposes.
More information is available here: Set discovery ISO user password example
Please, read our CONTRIBUTING guidelines for more info about how to create, document, and review PRs.
![@dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=64&v=4){kind=small}
