What's new in RPCO r12.2#
Read this page to understand the significant changes in RPCO Release r12.2.
RPCO r12.2 provides basic load balancing functionality, in a new or existing RPCO deployment, to applications running on instances within a customer cloud. The LBaaS service is a Rackspace-supported feature provided as a technical preview, suitable for development or test workloads. It should not be used for production workloads. Follow-on releases of RPCO might use a different agent and therefore provide no direct migration path.
Understand the following characteristics of the LBaaS technical preview:
- The preview release is not intended to provide highly scalable or highly available load balancing services.
- Testing and recommended usage is limited to 10 members in a pool and no more than 20 pools.
- Virtual load balancers deployed as part of the LBaaS service are not monitored for availability or performance.
- RPCO r12.2 enables LBaaS v2 with the default HAProxy-based agent.
- The Octavia agent is not supported.
- Integration with physical load balancer devices is not supported.
- Customers can use API or CLI LBaaS interfaces.
- A Dashboard panel for LBaaS is not available.
- SDN integration is not supported.
RPCO r12.2 brings a new, optional security hardening role that provides increased security for the host operating system and many common services running on the host. You can pick and choose which of the provided security configurations to apply, or change many of them to be more or less stringent.
If your RPCO environment is exposed to the internet or must conform to elevated standards such as for PCI-DSS or NIST compliance, consider applying the hardened configuration. We recommend that you test this role and any related configuration changes in a non-production environment.
Detailed information about the security hardening role and its application is provided in the OpenStack-Ansible documentation. See docs.openstack.org/developer/openstack-ansible-security.