Description of problem: Currently, when Telco customers have to use RealTime hypervisors, we ask them to generate their own RT overcloud images [1] starting from the standard ones. This process creates the following issues: - Overcloud RT image does not follow the life-cycle of the standard x86 ones (manual generation vs update from package) - The creation process is somehow slow (>1h) and error-prone. Additionally, the official procedure even ask the user to add their own user/password in clear text to download the packages [1] - as a side effect, coming up an automated process is not that simple e.g. in case tuned's rt profile has a different version than tuned already installed in the standard overcloud image, also this package requires an update - In the end, those are custom images which may be mistrusted by the customer's security team given the lack of official package signature and image hash In general, providing official ones would result in cleaning up all the above issues and at the same time improving the customer experience. [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/network_functions_virtualization_planning_and_configuration_guide/parent_assembly_tuning#enabling_rt_kvm_for_nfv_workloads Version-Release number of selected component (if applicable): OSP13, OSP14, OSP15, OSP16 Actual results: RT overcloud image needs to be manually generated Expected results: $ sudo yum install -y rhosp-rt-director-images-x86_64.noarch Additional info: Due to the potential subscription issues, this new package could be included as part of "rhel-7-server-nfv-rpms" repo which is available only with the correct one.
An alternative approach to providing a separate image would be to solve this through TripleO, i.e. pulling in the required packages from a content source (Satellite or RHN). It of course creates a requirement that the node is registered, but this is (should be) true for most production deployments. Also, this way the responsibility for ensuring the correct entitlements exist is pused onto the end user, where I think it belongs.