doc/nodepool: update vhd-util docs

Update the docs on the package generation for the automated building
we have implemented.

Change-Id: I60816ab8686cc32b3767fc13295b95ed42e02483
This commit is contained in:
Ian Wienand 2023-01-10 15:12:55 +11:00
parent 8b42a38df2
commit 67c32f5f0d
No known key found for this signature in database

View File

@ -109,31 +109,9 @@ considered the next-most-recent image.
vhd-util vhd-util
======== ========
Creating images for Rackspace requires a patched version of vhd-util to convert Creating images for Rackspace requires a patched version of vhd-util
the images into the appropriate VHD format. A package is manually managed to convert the images into the appropriate VHD format. See the
at `ppa:openstack-ci-core/vhd-util` and is based on a git repo at `opendev/infra-vhd-util-deb
https://github.com/emonty/vhd-util <https://opendev.org/opendev/infra-vhd-util-deb>`__ for details of
this custom package. This is installed on a production host via a PPA
Updating vhd-util built and published by jobs in this repository.
-----------------
Should it become required to update vhd-util before Infra has a proper
packaging repo or solution in place, one should clone from the git repo::
$ git clone git://github.com/emonty/vhd-util
$ cd vhd-util
Then perform whatever updates and packaging work are needed. The repo is
formatted as a git-buildpackage repo with `--pristine-tar`. When you're ready
to upload a new verion, commit, create a source package and a tag::
$ git-buildpackage --git-tag --git-sign-tags -S
This will make a source package in the parent directory. Upload it to
launchpad::
$ cd ..
$ dput ppa:openstack-ci-core/vhd-util vhd-util_$version_source.changes
Then probably pushing the repo to github and submitting a pull request so that
we can keep up with the change is not a terrible idea.