Answers to the Quiz
Add-on Operators of Red Hat OpenStack Services on OpenShift
-
Which of the following is the best description of the OpenStack add-on operator from Red Hat OpenStack Services on OpenShift?
-
It is a Kubernetes add-on operator that manages VMs running in OpenStack clusters.
Incorrect: OpenStack services, such as Nova and Heat, manage VMs running in OpenStack clusters. -
It is a Kubernetes add-on operator that manages the control and data planes of OpenStack clusters.
Correct: Directly, or through its child add-on operators, the OpenStack add-on operator manages all of an OpenStack cluster. -
It is an OpenShift cluster operator that enables running containerized applications on OpenStack clusters.
Incorrect: The OpenStack add-on operator is NOT an OpenShift cluster operator. -
It is an OpenShift cluster operator that manages OpenStack compute nodes. Incorrect: The OpenStack add-on operator is NOT an OpenShift cluster operator and it also manages an OpenStack control plane, besides its compute nodes.
-
-
Which of the child operators of the OpenStack add-on operator runs Ansible playbooks to configure OpenStack compute nodes?
-
The Bare Metal add-on operator
Incorrect: The Bare Metal operator provisions physical servers with BMC management hardware. -
The Data Plane add-on operator
Correct: The Data Plane add-on operator configures, using Ansible playbooks, both pre-provisioned and user-provisioned OpenStack compute nodes. -
The Infrastructure add-on operator
Incorrect: The Infrastructure add-on operator deals with networking infrastructure for compute nodes, more specifically: IPAM and DNS resolution. -
The Ironic add-on operator
Incorrect: The Ironic add-on operator manages the OpenStack Ironic service, which provisions physical servers with BMC hardware as server instances for an OpenStack project. -
The Nova add-on operator
Incorrect: The Nova add-on operator manages the OpenStack Nova service, which manages virtual machines (VMs) running on OpenStack compute nodes.
-
-
Which component of Red Hat OpenShift manages add-on operators such as the OpenStack add-on operator from Red Hat OpenStack Services on OpenShift?
-
Helm
Incorrect: Helm is a popular tool to install and upgrade containerized applications on Kubernetes, it could be used to install add-on operators, but it is not the best tool for this task and it is not supported by Red Hat for Red Hat OpenStack Services on OpenShift. -
OpenStack Heat
Incorrect: Heat manages workloads based on VMs on OpenStack, it cannot manage add-on operators in OpenShift. -
The Operator SDK
Incorrect: The Operator SDK is a tool for developing, testing, and packaging add-on operators, but it does not manage add-on operators installed in a Kubernetes cluster. -
The Operator Lifecycle Manager (OLM)
Correct: The OLM is the tool recommended and supported by Red Hat for installing Red Hat OpenStack Services on OpenShift and other add-on operators from Red Hat and third-party vendors. -
The Cluster Version Operator (CVO)
Incorrect: The CVO manages OpenShift installation and upgrades, and OpenShift cluster operators.
-
-
Which of the following is the best description of Kubernetes add-on operators?
-
Applications that manage hardware resources, such as GPUs.
Incorrect: Add-on operators can manage hardware resources, but they can manage other kinds of entities too. -
Applications that manage running applications, such as relational databases.
Incorrect: Add-on operators can manage other applications, but they can manage other kinds of entities too. -
Applications which manage networking equipment, such as IP routers.
Incorrect: Add-on operators can manage hardware appliances, but they can manage other kinds of entities too. -
Applications which manage physical servers with BMC hardware.
Incorrect: Add-on operators can manage server machines, but they can manage other kinds of entities too. -
All of the above could be Kubernetes add-on operators.
Correct: Kubernetes add-on operators could manage all these kinds of entities and more.
-
-
Which of the following custom resource types always require customized instances for a specific OpenStack cluster?
-
Control Plane
Correct: All OpenStack clusters require a Control Plane resource instance that configures its OpenStack services. -
Data Plane Deployment
Correct: All OpenStack clusters require a Data Plane Deployment resource instance which triggers running the Ansible playbooks which configure its OpenStack compute nodes. -
Data Plane Service
Incorrect: OpenStack clusters can use only the predefined Data Plane Services from Red Hat OpenStack Services on OpenShift and be fully functional. -
Network Configuration
Correct: All OpenStack clusters require a Network Configuration instance which configures IP subnet ranges and VLAN IDs for its compute nodes. -
Node Set
Correct: All OpenStack clusters require a Node Set resource instance which lists its compute nodes.
-