Bug 1823352

Summary:	[Docs][RHOSP16.1][OVN] OVN Migration steps need to define director tuning parameters for larger scale environment
Product:	Red Hat OpenStack	Reporter:	Pradipta Kumar Sahoo <psahoo>
Component:	documentation	Assignee:	James Smith <jamsmith>
Status:	CLOSED DUPLICATE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.1 (Train)	CC:	apevec, dalvarez, jamsmith, jlibosva, lhh, majopela, scohen, smalleni, stchen, vkommadi
Target Milestone:	z4	Keywords:	Reopened, Triaged
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	[Docs][RHOSP16.1][OVN] OVN Migration steps need to define director tuning parameters for larger scale environment
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-08 05:03:36 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:	1792500, 1818866
Bug Blocks:

Description Pradipta Kumar Sahoo 2020-04-13 12:50:29 UTC

Description of problem:
Currently, OSP16 OVN integration guide didn't include the tunning details for the larger-scale environment.

Version-Release number of selected component (if applicable):
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html-single/networking_with_open_virtual_network/index#migrating-ml2ovs-to-ovn

Expected results:
Referring to primary bz [1], the document should enhance with the limitation and fine tunning details for larger-scale migration

Additional info:
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1818866

Comment 1 Sai Sindhur Malleni 2020-04-13 15:12:07 UTC

Pradipta,

Can you add what those tunings are, to the BZ for tracking.

Comment 2 Pradipta Kumar Sahoo 2020-04-13 15:51:19 UTC

Hi Sai,

So far below tunning are applied in Undercloud OSP services, But it's not yet finalised as we are still troubleshooting the environment with DF team.

Heat:
	# crudini --get /var/lib/config-data/puppet-generated/heat/etc/heat/heat.conf oslo_messaging_rabbit heartbeat_timeout_threshold
	600

	# grep ^[^#] /var/lib/config-data/puppet-generated/heat_api/etc/httpd/conf/httpd.conf  | grep -i time
	Timeout 600
	KeepAliveTimeout 15

Mistral
	# crudini --set /var/lib/config-data/puppet-generated/mistral/etc/mistral/mistral.conf DEFAULT rpc_response_timeout 600
	# grep ^[^#] /var/lib/config-data/puppet-generated/mistral/etc/mistral/mistral.conf|grep timeout
	rpc_response_timeout=600

	$ sudo grep --color api_workers /var/lib/config-data/puppet-generated/mistral/etc/mistral/mistral.conf
	api_workers=12

	# grep ^[^#] /var/lib/config-data/puppet-generated/mistral/etc/httpd/conf/httpd.conf  | grep Timeout
	Timeout 600
	KeepAliveTimeout 15

	$ sudo grep --color processes /var/lib/config-data/puppet-generated/mistral/etc/httpd/conf.d/10-mistral_wsgi.conf
	 WSGIDaemonProcess mistral display-name=mistral_wsgi group=mistral processes=12 threads=1 user=mistral


Keystone:
	# crudini --set /var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf oslo_messaging_rabbit heartbeat_timeout_threshold 600

	# crudini --get /var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf oslo_messaging_rabbit heartbeat_timeout_threshold
	600

	# grep ^[^#] /var/lib/config-data/puppet-generated/keystone/etc/httpd/conf/httpd.conf |grep Timeout
	Timeout 600

Zaqar

	# crudini --get /var/lib/config-data/puppet-generated/zaqar/etc/zaqar/zaqar.conf DEFAULT rpc_response_timeout
	600

	# grep ^[^#] /var/lib/config-data/puppet-generated/zaqar/etc/httpd/conf/httpd.conf |grep Timeout
	Timeout 600

	$ sudo grep --color processes /var/lib/config-data/puppet-generated/zaqar/etc/httpd/conf.d/10-zaqar_wsgi.conf
	WSGIDaemonProcess zaqar-server display-name=zaqar_wsgi group=zaqar processes=12 threads=1 user=zaqar


Restarted services:
	$ for i in `sudo podman ps | grep -E "heat|mistral|keystone|zaqar" |awk '{print $11}'`; do sudo podman restart $i; done

BR,
Pradipta

Comment 3 stchen 2020-11-04 19:47:41 UTC

Closing EOL, OSP 16.0 has been retired as of Oct 27, 2020

Comment 9 Pradipta Kumar Sahoo 2021-11-08 05:03:36 UTC

Hi James,

Sure we can close 1823352 as a duplicate of 2017906 as the requested steps are included.

BR,
Pradipta

*** This bug has been marked as a duplicate of bug 2017906 ***