From 4e84daec86f8bfe2e4a07ef337ba4c1fa7b79da7 Mon Sep 17 00:00:00 2001 From: "James E. Blair" Date: Sat, 28 Jun 2014 07:43:19 -0700 Subject: [PATCH] Update gerrit project rename instructions To current (hacky) procedure to stop puppet runs from puppetmaster. Change-Id: I7a76fc4fd020c6dd6e8f05f417ec58a6410fac84 --- doc/source/gerrit.rst | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/doc/source/gerrit.rst b/doc/source/gerrit.rst index 5ed335c04f..a2b3646991 100644 --- a/doc/source/gerrit.rst +++ b/doc/source/gerrit.rst @@ -391,11 +391,14 @@ To rename a project: #. Prepare a change to the Puppet configuration which updates projects.yaml/ACLs and jenkins-job-builder for the new name. -#. Stop puppet on review.openstack.org to prevent your interim - configuration changes from being reset by the project management - routines:: +#. Stop puppet runs on the puppetmaster to prevent early application + of configuration changes:: - sudo puppetd --disable + sudo crontab -u root -e + + Comment out the crontab entries. Use ps to make sure that a run is + not currently in progress. When it finishes, make sure the entry + has not been added back to the crontab. #. Gracefully stop Zuul on zuul.openstack.org:: @@ -445,9 +448,9 @@ To rename a project: #. Merge the prepared Puppet configuration change, removing the original Jenkins jobs via the Jenkins WebUI later if needed. -#. Start puppet again on review.openstack.org:: +#. Re-enable puppet runs on the puppetmaster:: - sudo puppetd --enable + sudo crontab -u root -e #. Rename the project in GitHub or, if this is a move to a new org, let the project management run create it for you and then remove the