2019-10-03 08:33:31 +00:00
|
|
|
#!/usr/bin/env bash
|
|
|
|
|
|
|
|
set -e
|
|
|
|
|
|
|
|
SCRIPT_DIR="$(dirname "$BASH_SOURCE")"
|
|
|
|
SCRIPT_DIR="$(realpath "$SCRIPT_DIR")"
|
|
|
|
|
|
|
|
num_vcpus=$(( $(lscpu -p | tail -1 | cut -d "," -f 1) + 1 ))
|
|
|
|
|
|
|
|
CEPH_DIR="${CEPH_DIR:-$SCRIPT_DIR}"
|
|
|
|
BUILD_DIR="${BUILD_DIR:-${CEPH_DIR}/build}"
|
|
|
|
DEPS_DIR="${DEPS_DIR:-$CEPH_DIR/build.deps}"
|
|
|
|
|
|
|
|
CLEAN_BUILD=${CLEAN_BUILD:-}
|
|
|
|
SKIP_BUILD=${SKIP_BUILD:-}
|
|
|
|
NUM_WORKERS=${NUM_WORKERS:-$num_vcpus}
|
|
|
|
DEV_BUILD=${DEV_BUILD:-}
|
|
|
|
|
|
|
|
# We'll have to be explicit here since auto-detecting doesn't work
|
|
|
|
# properly when cross compiling.
|
|
|
|
ALLOCATOR=${ALLOCATOR:-libc}
|
|
|
|
# Debug builds don't work with MINGW for the time being, failing with
|
|
|
|
# can't close <file>: File too big
|
|
|
|
# -Wa,-mbig-obj does not help.
|
|
|
|
CMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE:-RelWithDebInfo}
|
|
|
|
|
|
|
|
depsSrcDir="$DEPS_DIR/src"
|
|
|
|
depsToolsetDir="$DEPS_DIR/mingw"
|
|
|
|
|
|
|
|
lz4Dir="${depsToolsetDir}/lz4"
|
|
|
|
sslDir="${depsToolsetDir}/openssl"
|
|
|
|
curlDir="${depsToolsetDir}/curl"
|
|
|
|
boostDir="${depsToolsetDir}/boost"
|
|
|
|
zlibDir="${depsToolsetDir}/zlib"
|
|
|
|
backtraceDir="${depsToolsetDir}/backtrace"
|
|
|
|
snappyDir="${depsToolsetDir}/snappy"
|
|
|
|
winLibDir="${depsToolsetDir}/windows/lib"
|
2019-11-25 15:00:59 +00:00
|
|
|
generatorUsed="Unix Makefiles"
|
rbd: allow mounting images on Windows
This change will allow mapping rbd images on Windows, leveraging the
WNBD[1] Virtual Storport Miniport driver [2].
The behavior and CLI is similar to the Linux rbd-nbd, with a few
notable differences:
* device paths cannot be requested. The disk number and path will
be picked by Windows. If a device path is provided by the user
when mapping an image, it will be used as an identifier, which
can also be used when unmapping the image.
* the "show" command was added, which describes a specific mapping.
This can be used for retrieving the disk path.
* the "service" command was added, allowing rbd-wnbd to run as a
Windows service. All mappings are currently perisistent, being
recreated when the service stops, unless explicitly unmapped.
The service disconnects the mappings when being stopped.
* the "list" command also includes a "status" column.
The purpose of the "service" mode is to ensure that mappings survive
reboots and that the Windows service start order can be adjusted so
that rbd images can be mapped before starting services that may depend
on it, such as VMMS.
The mapped images can either be consumed by the host directly or exposed
to Hyper-V VMs.
While at it, we'll skip building rbd-mirror as it's quite unlikely that
this daemon is going to be used on Windows for now.
[1] https://github.com/cloudbase/wnbd
[2] https://docs.microsoft.com/en-us/windows-hardware/drivers/storage/overview-of-storage-virtual-miniport-drivers
Signed-off-by: Lucian Petrut <lpetrut@cloudbasesolutions.com>
Signed-off-by: Alin Gabriel Serdean <aserdean@cloudbasesolutions.com>
2020-07-30 11:40:31 +00:00
|
|
|
wnbdSrcDir="${depsSrcDir}/wnbd"
|
|
|
|
wnbdLibDir="${depsToolsetDir}/wnbd/lib"
|
2019-10-03 08:33:31 +00:00
|
|
|
|
|
|
|
depsDirs="$lz4Dir;$curlDir;$sslDir;$boostDir;$zlibDir;$backtraceDir;$snappyDir"
|
|
|
|
depsDirs+=";$winLibDir"
|
|
|
|
|
|
|
|
# That's actually a dll, we may want to rename the file.
|
|
|
|
lz4Lib="${lz4Dir}/lib/liblz4.so.1.9.2"
|
|
|
|
lz4Include="${lz4Dir}/lib"
|
|
|
|
curlLib="${curlDir}/lib/libcurl.dll.a"
|
|
|
|
curlInclude="${curlDir}/include"
|
|
|
|
|
|
|
|
if [[ -n $CLEAN_BUILD ]]; then
|
|
|
|
echo "Cleaning up build dir: $BUILD_DIR"
|
|
|
|
rm -rf $BUILD_DIR
|
|
|
|
fi
|
|
|
|
|
|
|
|
if [[ ! -d $DEPS_DIR ]]; then
|
|
|
|
echo "Preparing dependencies: $DEPS_DIR"
|
|
|
|
NUM_WORKERS=$NUM_WORKERS DEPS_DIR=$DEPS_DIR \
|
|
|
|
"$SCRIPT_DIR/win32_deps_build.sh"
|
|
|
|
fi
|
|
|
|
|
|
|
|
mkdir -p $BUILD_DIR
|
|
|
|
cd $BUILD_DIR
|
|
|
|
|
|
|
|
# We'll need to cross compile Boost.Python before enabling
|
|
|
|
# "WITH_MGR".
|
|
|
|
echo "Generating solution. Log: ${BUILD_DIR}/cmake.log"
|
|
|
|
|
|
|
|
# This isn't propagated to some of the subprojects, we'll use an env variable
|
|
|
|
# for now.
|
|
|
|
export CMAKE_PREFIX_PATH=$depsDirs
|
|
|
|
|
|
|
|
if [[ -n $DEV_BUILD ]]; then
|
|
|
|
echo "Dev build enabled."
|
|
|
|
echo "Git versioning will be disabled."
|
|
|
|
ENABLE_GIT_VERSION="OFF"
|
|
|
|
else
|
|
|
|
ENABLE_GIT_VERSION="ON"
|
|
|
|
fi
|
|
|
|
|
|
|
|
# As opposed to Linux, Windows shared libraries can't have unresolved
|
|
|
|
# symbols. Until we fix the dependencies (which are either unspecified
|
|
|
|
# or circular), we'll have to stick to static linking.
|
|
|
|
cmake -D CMAKE_PREFIX_PATH=$depsDirs \
|
|
|
|
-D CMAKE_TOOLCHAIN_FILE="$CEPH_DIR/cmake/toolchains/mingw32.cmake" \
|
|
|
|
-D WITH_RDMA=OFF -D WITH_OPENLDAP=OFF \
|
|
|
|
-D WITH_GSSAPI=OFF -D WITH_FUSE=OFF -D WITH_XFS=OFF \
|
|
|
|
-D WITH_BLUESTORE=OFF -D WITH_LEVELDB=OFF \
|
|
|
|
-D WITH_LTTNG=OFF -D WITH_BABELTRACE=OFF \
|
|
|
|
-D WITH_SYSTEM_BOOST=ON -D WITH_MGR=OFF \
|
|
|
|
-D WITH_LIBCEPHFS=OFF -D WITH_KRBD=OFF -D WITH_RADOSGW=OFF \
|
|
|
|
-D ENABLE_SHARED=OFF -D WITH_RBD=ON -D BUILD_GMOCK=OFF \
|
|
|
|
-D WITH_CEPHFS=OFF -D WITH_MANPAGE=OFF \
|
|
|
|
-D WITH_MGR_DASHBOARD_FRONTEND=OFF -D WITH_SYSTEMD=OFF -D WITH_TESTS=OFF \
|
|
|
|
-D LZ4_INCLUDE_DIR=$lz4Include -D LZ4_LIBRARY=$lz4Lib \
|
|
|
|
-D Backtrace_Header="$backtraceDir/include/backtrace.h" \
|
|
|
|
-D Backtrace_INCLUDE_DIR="$backtraceDir/include" \
|
|
|
|
-D Backtrace_LIBRARY="$backtraceDir/lib/libbacktrace.dll.a" \
|
|
|
|
-D Boost_THREADAPI="pthread" \
|
|
|
|
-D ENABLE_GIT_VERSION=$ENABLE_GIT_VERSION \
|
|
|
|
-D ALLOCATOR="$ALLOCATOR" -D CMAKE_BUILD_TYPE=$CMAKE_BUILD_TYPE \
|
rbd: allow mounting images on Windows
This change will allow mapping rbd images on Windows, leveraging the
WNBD[1] Virtual Storport Miniport driver [2].
The behavior and CLI is similar to the Linux rbd-nbd, with a few
notable differences:
* device paths cannot be requested. The disk number and path will
be picked by Windows. If a device path is provided by the user
when mapping an image, it will be used as an identifier, which
can also be used when unmapping the image.
* the "show" command was added, which describes a specific mapping.
This can be used for retrieving the disk path.
* the "service" command was added, allowing rbd-wnbd to run as a
Windows service. All mappings are currently perisistent, being
recreated when the service stops, unless explicitly unmapped.
The service disconnects the mappings when being stopped.
* the "list" command also includes a "status" column.
The purpose of the "service" mode is to ensure that mappings survive
reboots and that the Windows service start order can be adjusted so
that rbd images can be mapped before starting services that may depend
on it, such as VMMS.
The mapped images can either be consumed by the host directly or exposed
to Hyper-V VMs.
While at it, we'll skip building rbd-mirror as it's quite unlikely that
this daemon is going to be used on Windows for now.
[1] https://github.com/cloudbase/wnbd
[2] https://docs.microsoft.com/en-us/windows-hardware/drivers/storage/overview-of-storage-virtual-miniport-drivers
Signed-off-by: Lucian Petrut <lpetrut@cloudbasesolutions.com>
Signed-off-by: Alin Gabriel Serdean <aserdean@cloudbasesolutions.com>
2020-07-30 11:40:31 +00:00
|
|
|
-D WNBD_INCLUDE_DIRS="$wnbdSrcDir/include" \
|
|
|
|
-D WNBD_LIBRARIES="$wnbdLibDir/libwnbd.a" \
|
2019-10-03 08:33:31 +00:00
|
|
|
-G "$generatorUsed" \
|
|
|
|
$CEPH_DIR 2>&1 | tee "${BUILD_DIR}/cmake.log"
|
|
|
|
|
|
|
|
if [[ -z $SKIP_BUILD ]]; then
|
|
|
|
echo "Building using $NUM_WORKERS workers. Log: ${BUILD_DIR}/build.log"
|
2019-11-25 15:00:59 +00:00
|
|
|
echo "" > "${BUILD_DIR}/build.log"
|
|
|
|
|
|
|
|
# We're going to use an associative array having subdirectories as keys
|
|
|
|
# and targets as values.
|
|
|
|
declare -A make_targets
|
|
|
|
make_targets["src/tools"]="ceph-conf ceph_radosacl ceph_scratchtool rados"
|
|
|
|
make_targets["src/tools/immutable_object_cache"]="all"
|
|
|
|
make_targets["src/tools/rbd"]="all"
|
rbd: allow mounting images on Windows
This change will allow mapping rbd images on Windows, leveraging the
WNBD[1] Virtual Storport Miniport driver [2].
The behavior and CLI is similar to the Linux rbd-nbd, with a few
notable differences:
* device paths cannot be requested. The disk number and path will
be picked by Windows. If a device path is provided by the user
when mapping an image, it will be used as an identifier, which
can also be used when unmapping the image.
* the "show" command was added, which describes a specific mapping.
This can be used for retrieving the disk path.
* the "service" command was added, allowing rbd-wnbd to run as a
Windows service. All mappings are currently perisistent, being
recreated when the service stops, unless explicitly unmapped.
The service disconnects the mappings when being stopped.
* the "list" command also includes a "status" column.
The purpose of the "service" mode is to ensure that mappings survive
reboots and that the Windows service start order can be adjusted so
that rbd images can be mapped before starting services that may depend
on it, such as VMMS.
The mapped images can either be consumed by the host directly or exposed
to Hyper-V VMs.
While at it, we'll skip building rbd-mirror as it's quite unlikely that
this daemon is going to be used on Windows for now.
[1] https://github.com/cloudbase/wnbd
[2] https://docs.microsoft.com/en-us/windows-hardware/drivers/storage/overview-of-storage-virtual-miniport-drivers
Signed-off-by: Lucian Petrut <lpetrut@cloudbasesolutions.com>
Signed-off-by: Alin Gabriel Serdean <aserdean@cloudbasesolutions.com>
2020-07-30 11:40:31 +00:00
|
|
|
make_targets["src/tools/rbd_wnbd"]="all"
|
2019-11-25 15:00:59 +00:00
|
|
|
make_targets["src/compressor"]="all"
|
|
|
|
|
|
|
|
for target_subdir in "${!make_targets[@]}"; do
|
|
|
|
echo "Building $target_subdir: ${make_targets[$target_subdir]}" | tee -a "${BUILD_DIR}/build.log"
|
|
|
|
make -j $NUM_WORKERS -C $target_subdir ${make_targets[$target_subdir]} 2>&1 | tee -a "${BUILD_DIR}/build.log"
|
|
|
|
done
|
2019-10-03 08:33:31 +00:00
|
|
|
fi
|