Bug 1579681

Summary:	[Deployment][RHOSP-14] Lift the restriction on choices for `cpu_model_extra_flags` config attribute
Product:	Red Hat OpenStack	Reporter:	Rajesh Tailor <ratailor>
Component:	puppet-nova	Assignee:	Rajesh Tailor <ratailor>
Status:	CLOSED ERRATA	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	14.0 (Rocky)	CC:	jjoyce, jschluet, lyarwood, nlevinki, slinaber, tvignaud
Target Milestone:	Upstream M2	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	puppet-nova-13.1.1-0.20180709142740.fa5ce48.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1579691 1579699 (view as bug list)		Environment:
Last Closed:	2019-01-11 11:49:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1579691, 1579693, 1579694, 1579699

Description Rajesh Tailor 2018-05-18 06:56:56 UTC

(This bug is a follow-up item to the:
https://bugzilla.redhat.com/show_bug.cgi?id=1547954 -- Deployment RFE: add ability to configure extra CPU flags for named CPU models)

This introduced the Nova configuration attribute
`[libvirt]/cpu_model_extra_flags`, we have restricted the choices to be
only 'PCID' -- to alleviate the immediate guest performance degradation
as a result of applying the "Meltdown" CVE fixes.

Now remove that restriction to allow adding and removing multiple CPU
flags, making way for other use cases.

Use cases:

  - Ability to use 1GB huge pages with Haswell model as one use case for
    extra flags:

        cpu_model=Haswell-noTSX-IBRS 
        cpu_model_extra_flags="pdpe1gb"

  - Nested Virtualization -- an operator can specify the Intel 'vmx' or
    AMD 'svm' flags in the level-1 Nova guest.

Comment 7 errata-xmlrpc 2019-01-11 11:49:53 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045