8459ch05.fm Draft Document for Review December 11, 2019 1:55 pm GLYPH<SM590000> Soft-affinity : All virtual machines from this rule will be hosted on the same host if  possible, but if not possible they still will be scheduled instead of failure and set the status  of the rule to  violated . GLYPH<SM590000> Soft-anti-affinity : All virtual machines from this rule will be hosted on different host, if  possible, but if not possible they still will be scheduled instead of failure and set the status  of the rule to  violated . If the rule status is  violated , review the placement of the virtual machines. For any virtual  machines that are on an incorrect host, you can migrate it to the correct host using LPM. PowerVC image A custom image must be created in PowerVC before starting the deployment. OpenShift has  specific requirements: GLYPH<SM590000> RHEL 7.6 for POWER8 and RHEL-ALT 7.6 for POWER9 Minimum installation. GLYPH<SM590000> SELinux must be set to enforcing. GLYPH<SM590000> NetworkManager must be enabled and running. GLYPH<SM590000> Firewall must be enabled and running. GLYPH<SM590000> Set host name from DNS (set_hostname_from_dns) in cloud-init. Note:  For more details about image creation in PowerVC, see the following link: https://ibm.co/34wFSvt Project and user High availability Hardware high availability A project, sometimes referred to as a tenant, is a unit of ownership. Most resources, such as  virtual machines, volumes, and images, belong to a specific project. Only users with a role  assignment for a given project can work with the resources belonging to that project. The  ibm-default  project is created during installation, but PowerVC supports the creation of  additional projects for resource segregation. When possible, it is recommended to create a new user and project for the OpenShift  environment. High availability is a requirement for any production deployment. A crucial consideration for  high availability is the removal of single points of failure (SPOFs). This reference architecture  is highly available at all layers (Hardware, PowerVM, PowerVC and OpenShift). You must take care to eliminate single points of failure at the hardware layer. Hardware fault  tolerance recommendations implemented in this architecture include: GLYPH<SM590000> Redundant server power supplies connected to different power sources. GLYPH<SM590000> Redundant network adapters connected to redundant network switches. GLYPH<SM590000> Redundant Fibre Channel adapters connected to redundant SAN fabrics. PowerVM high availability The specifics of the VIOS configuration when using LPAR with a production OpenShift  Container Platform are: GLYPH<SM590000> If I/O virtualization is used, a dual-VIOS setup is mandatory. You can have more than two  VIOSes in the system separating different environments, such as production and test or  multiple customers 80  Red Hat OpenShift and IBM Cloud Paks on IBM Power Systems: Volume 1