이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 2. Top New Features
This section provides an overview of the top new features in this release of Red Hat OpenStack Platform.
2.1. Red Hat OpenStack Platform Director
This section outlines the top new features for the director.
- Custom Roles and Composable Services
- Monolithic templates have been decomposed into a set of multiple smaller discrete templates, each representing a composable service. These can be deployed on a standalone node, or combined with other services in the form of Custom Roles.Note the following guidelines and limitations for the composable node architecture:
- You can assign any
systemdmanaged service to a supported standalone custom role. - You cannot split Pacemaker-managed services. This is because the Pacemaker manages the same set of services on each node within the overcloud cluster. Splitting Pacemaker-managed services can cause cluster deployment errors. These services should remain on the Controller role.
- You cannot change to custom roles and composable services during the upgrade process from Red Hat OpenStack Platform 9 to 10. The upgrade scripts can only accommodate the default overcloud roles.
- You can create additional custom roles after the initial deployment and deploy them to scale existing services.
- You cannot modify the list of services for any role after deploying an overcloud. Modifying the service lists after Overcloud deployment can cause deployment errors and leave orphaned services on nodes.
For more information on supported architecture for custom roles and composable services, see Composable Services and Custom Roles in the Advanced Overcloud Customization guide. - Graphical User Interface
- Director can now be managed using a Graphical User Interface, which includes integrated templates, a built-in workflow, and pre- and post-flight validation checking. You use the GUI to create Role Assignments and perform node registration and introspection.
- Separation of the Hardware Deployment Phase and Generic Node Deployment
- The director workflow now includes a clear separation of the hardware deployment phase. This delineates where a user registers hardware to the inventory, uploads images, and defines hardware profiles. This phase is completed by deploying a given image to a specific hardware node. This separation allows you to deploy Red Hat Enterprise Linux onto a hardware node and hand it over to a user.
