Skip to content

Latest commit

 

History

History
213 lines (148 loc) · 4.83 KB

README.md

File metadata and controls

213 lines (148 loc) · 4.83 KB
Raw

Ganeti RPM Packaging

Build Test

Ganeti RPM Packaging for RHEL/CentOS/Rocky Linux/others.

Packaging status

  • RHEL/CentOS/Rocky Linux/others 8.x: 3.0.2-1
  • RHEL/CentOS/others 7.x: 3.0.2-1

Documentation

YUM/DNF repository and binary RPM files

Building RPM Packages with Docker

You can build RPM packages in Docker.

# Rocky Linux 8
./build rockylinux:8

# CentOS 7
./build centos:7

Debug and manual mode:

# Rocky Linux 8
./build -d rockylinux:8

# CentOS 7
./build -d centos:7

# Setup
cd /pkg
./setup

# Build
./build-rpm ...

Usage: build

Run on host.

Usage:
    build [-d] BUILD_IMAGE_NAME:BUILD_IMAGE_TAG [BUILD_RPM_ARGS]

    Options:
        -d Debug mode

        BUILD_RPM_ARGS
            build-rpm options (default: -a -bi -o yes)

    Environment variables:
        BUILD_HOSTNAME: container host name

    Build for Rocky Linux 8:
        build rockylinux:8

    Build for CentOS 7:
        build centos:7

Usage: build-rpm

Run in a container.

Usage:
    build-rpm [-a|-d|-p] [-c|-C] [-b] [-s] [-i] [-u] [-o yes|no] [package...]

    Target Options:
        -a all packages (ganeti and its dependencies and integ-ganeti repo, snf-image)
        -d ganeti dependencies packages only
        -p the specified package(s) only. Available packages are:
            ganeti dependencies (el8 only):
                python-bitarray
            ganeti dependencies (el7 only):
                python-inotify
            ganeti:
                ganeti ganeti-instance-debootstrap
            snf-image:
                python-prctl snf-image
            integ-ganeti-repo:
                integ-ganeti-release

    Task Options:
        -c Clean clean the rpmbuild directory, but preserve downloaded archives
        -C Completely clean the rpmbuild directory

        -b Build packages
        -o Overwrite built package: yes|no (Default: manual)

        -s Sign built packages

        -i Install built packages
        -u Uninstall installed packages

        Task Execution Order:
            Uninstall -> Clean -> Build -> Sign -> Install

        If the build (-b) and install (-i) options are specified at the same time,
        the installation will be done immediately after the individual packages are built.
        This is to resolve dependencies needed to build the next package.

Run build command in the container

All packages + uninstall, clean, build, and install:

./build-rpm -a -ucbi

Ganeti dependencies packages + uninstall, clean, build, and install:

./build-rpm -d -ucbi

The specified package(s) + uninstall, clean, build, and install:

./build-rpm -p -ucbi PACKAGE

Build all packages with no overwrite and install:

./build-rpm -a -bi -o no

Build the new ganeti RPM package version using the already released dependency libraries and install:

# Rocky Linux 8
dnf install https://jfut.integ.jp/linux/ganeti/8/x86_64/integ-ganeti-release-8-1.el8.noarch.rpm
dnf config-manager --enable integ-ganeti
./build-rpm -p -bi ganeti

# CentOS 7
yum install http://jfut.integ.jp/linux/ganeti/7/x86_64/integ-ganeti-release-7-3.el7.noarch.rpm
yum-config-manager --enable integ-ganeti
./build-rpm -p -bi ganeti

Signing RPM Packages

Run the container with bash:

# Rocky Linux 8
BUILD_HOSTNAME=rockylinux-8.github.integ.jp
docker run -h "${BUILD_HOSTNAME}" --rm -it -v $PWD:/pkg -v ~/.gnupg.el8:/root/.gnupg rockylinux:8 bash

# CentOS 7
BUILD_HOSTNAME=centos-7.github.integ.jp
docker run -h "${BUILD_HOSTNAME}" --rm -it -v $PWD:/pkg -v ~/.gnupg.el7:/root/.gnupg centos:7 bash

# Setup
yum -y install findutils rpm-sign pinentry

# Set your gpg name
echo "%_gpg_name jfut-rpm@integ.jp" >> ~/.rpmmacros

Sign all packages:

cd /pkg
./build-rpm -a -s

Sign the specified package(s) only:

./build-rpm -p -s PACAKGE

Other Ganeti resources

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

Release tag

e.g.:

git tag -a v3.0.2-1 -m "v3.0.2-1"
git push origin refs/tags/v3.0.2-1