Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1578489

Summary: Clarify NFV Update YAMLs in Upgrading RHOSP document
Product: Red Hat OpenStack Reporter: Andrew Ludwar <aludwar>
Component: documentationAssignee: Sandra McCann <samccann>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: medium Docs Contact:
Priority: medium    
Version: 10.0 (Newton)CC: samccann, srevivo
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-28 15:27:23 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: 1570832    

Description Andrew Ludwar 2018-05-15 17:05:45 UTC
Description of problem:

The current wording caused some customer confusion regarding which YAML files should be used when running an OSP10 minor update procedure. [1]. I assume these are to be used when upgrading a non-DPDK environment to a DPDK environment. Essentially enabling DPDK during the update process when wanting to transition the environment to something used for NFV workloads. The wording could be interpreted as updating OVS in an OVS-DPDK environment, which if the environment was originally deployed with DPDK, this would change some of the settings as the YAMLs are slightly different.

I suppose it's also possible these were for when updating from OVS 2.5 to OVS 2.6. Some clarification could be added, new deployments include OVS 2.6 now.

Current:

"These sample YAML files upgrade OVS for an OVS-DPDK deployment."


Proposed change:

"These sample YAML files upgrade OVS to an OVS-DPDK deployment, when wanting to transition the environment to OVS with DPDK functionality enabled."

OR 

"These sample YAML files upgrade OVS for an OVS-DPDK deployment, when updating from OVS 2.5 to OVS 2.6."




[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/upgrading_red_hat_openstack_platform/index#appe-sample-upgrade-files



Version-Release number of selected component (if applicable):

OSP10.


Actual results:

The wording caused some confusion during customer updates.


Expected results:

The wording is explicit enough to determine which update scenario these YAMLs apply to.


Additional info:

The largest difference I could find between the first-boot.yaml and post-install.yaml included in the NFV config guide and the mentioned NFV Update guide is how the LCORE_LIST variable is populated. NFV Config Guide passes HostCpusList to it, while the NFV Update guide parses it from /etc/sysconfig/openvswitch DPDK_OPTIONS parameter. When a customer used these YAMLs to update an already deployed NFV OVS-DPDK environment, it changed some of their OVS DPDK config settings.

NFV Upgrade Guide:
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/upgrading_red_hat_openstack_platform/index#appe-sample-upgrade-files

NFV Configuration Guide:
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/network_functions_virtualization_configuration_guide/index#modify_link_linkend_ap_ovsdpdk_first_boot_first_boot_yaml_link