PR#1044: docs: updates for parallel actions - copr/copr

copr / copr

#1044 docs: updates for parallel actions

Merged 4 years ago by praiskup. Opened 4 years ago by praiskup.

Unknown source parallel-act-doc-changes into master

docs: updates for parallel actions

Pavel Raiskup • 4 years ago

93c7640

doc/how_to_release_copr.rst

file modified

+2 -7

		`@@ -60,12 +60,8 @@`

		`alembic-3 upgrade head`

		`- Note: If there is a new version of copr-rpmbuild, run this on backend::`
		`-`
		`- redis-cli`
		`- 127.0.0.1:6379> FLUSHALL`
		`- cleanup_vm_nova.py`
		`- systemctl restart copr-backend`
		`+ Note: If there is a new version of copr-rpmbuild, follow the`
		+ :ref:`terminate_os_vms` and :ref:`terminate_resalloc_vms` instructions.


		`Call for QA`
		`@@ -196,7 +192,6 @@`

		`Note: You shouldn't need to upgrade DB manually, playbook covers it.`

		`- Note: If there is a new version of copr-rpmbuild, throw away all builders and reprovision them.`

		`Test production machine`
		`-----------------------`

doc/how_to_upgrade_persistent_instances.rst

file modified

+9 -4

		`@@ -170,6 +170,7 @@`
		Run provision playbooks for ``copr-backend`` and ``copr-keygen`` to propagate the changes
		`to the respective instances.`

		+ .. _`terminate_resalloc_vms`:

		`Terminate resalloc resources`
		`............................`
		`@@ -187,6 +188,8 @@`
		`resalloc-maint resource-delete $(resalloc-maint resource-list \| cut -d' ' -f1)`


		+ .. _`terminate_os_vms`:
		`+`
		`Terminate OpenStack VMs`
		`.......................`

		`@@ -195,10 +198,12 @@`

		`# systemctl stop copr-backend # ensure that new are not allocated anymore`
		`# su - copr`
		`- $ redis-cli # drop the DB`
		`- 127.0.0.1:6379> FLUSHALL`
		`- ^D`
		`- $ cleanup_vm_nova.py # clean all VMs not in DB`
		`+`
		`+ # drop the builders from DB`
		`+ $ redis-cli --scan --pattern 'copr:backend:vm_instance:hset::Copr_builder_*' \| xargs redis-cli del`
		`+`
		`+ # shutdown all the VMs which are not in DB`
		`+ $ cleanup_vm_nova.py`


		`Downgrade python novaclient`

praiskup commented 4 years ago

It is not wise to run flushdb in redis anymore, that could kill action
worker on background and cause inconsistent outputs. Also make sure we
document the same stuff on one place.