opendev/puppet-openstackci
Code Issues Proposed changes

Initiate nodepool-builder on third_party_ci.rst

Browse Source 
There is a missing step on the third_party_ci docs to initiate nodepool-builder
service. Without that, the image-build command gets stuck since the builder
isn't there to issue the image creation to DIB.

Change-Id: Ib213c7e779657dc2d08268b6b11ed88702b7612b
This commit is contained in:
Thiago Paiva 2016-03-15 15:49:08 -03:00 committed by Thiago Paiva Brito
parent 084da0b68f
commit 3cfc815b34
1 changed files with 23 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/source/third_party_ci.rst
View File

@ -344,7 +344,22 @@ Start nodepool
--------------
The first time starting nodepool, it's recommended to manually build the
image to aid in debugging any issues:
image to aid in debugging any issues. To do that, first, initiate the
nodepool-builder service:
::
sudo service nodepool-builder start
The nodepool-builder service is responsible for receiving image building
requests and calling Disk Image Builder to carry on the image creation.
You can see its logs by typing:
::
view /var/log/nodepool/nodepool-builder.log
Next, log into the nodepool user to issue manually the image building:
::
@ -360,6 +375,13 @@ image to aid in debugging any issues:
# file as the 'name' field in the section 'diskimages'.
nodepool image-build <image-name>
You can follow the image creation process by seeing the image creation
log:
::
tail -f /var/log/nodepool/image/image.log
If you run into issues building the image, the `documentation provided
here can help you
debug <https://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/elements/README.rst>`__