8.3 KiB
Development
This document will help to setup your development environment and run tests. If you encounter a problem, please file an issue.
Table of contents
- Development
- Table of contents
Building Milvus with Docker
Official releases are built using Docker containers. To build Milvus using Docker please follow these instructions.
Building Milvus on a local OS/shell environment
The details below outline the hardware and software requirements for building on Linux.
Hardware Requirements
Milvus is written in Go and C++, compiling it can use a lot of resources. We recommend the following for any physical or virtual machine being used for building Milvus.
- 8GB of RAM
- 50GB of free disk space
Software Requirements
In fact, all Linux distributions are available to develop Milvus. The following only contains commands on Ubuntu and CentOS, because we mainly use them. If you develop Milvus on other distributions, you are welcome to improve this document.
Dependencies
- Debian/Ubuntu
$ sudo apt update
$ sudo apt install -y build-essential ccache gfortran \
libssl-dev zlib1g-dev python3-dev libcurl4-openssl-dev libtbb-dev\
libboost-regex-dev libboost-program-options-dev libboost-system-dev \
libboost-filesystem-dev libboost-serialization-dev libboost-python-dev
- CentOS
$ sudo yum install -y epel-release centos-release-scl-rh && \
$ sudo yum install -y git make automake openssl-devel zlib-devel \
libcurl-devel python3-devel \
devtoolset-7-gcc devtoolset-7-gcc-c++ devtoolset-7-gcc-gfortran \
llvm-toolset-7.0-clang llvm-toolset-7.0-clang-tools-extra \
ccache lcov
$ echo "source scl_source enable devtoolset-7" | sudo tee -a /etc/profile.d/devtoolset-7.sh
$ echo "source scl_source enable llvm-toolset-7.0" | sudo tee -a /etc/profile.d/llvm-toolset-7.sh
$ echo "export CLANG_TOOLS_PATH=/opt/rh/llvm-toolset-7.0/root/usr/bin" | sudo tee -a /etc/profile.d/llvm-toolset-7.sh
$ source "/etc/profile.d/llvm-toolset-7.sh"
# Install tbb
$ git clone https://github.com/wjakob/tbb.git && \
cd tbb/build && \
cmake .. && make -j && \
sudo make install && \
cd ../../ && rm -rf tbb/
# Install boost
$ wget -q https://boostorg.jfrog.io/artifactory/main/release/1.65.1/source/boost_1_65_1.tar.gz && \
tar zxf boost_1_65_1.tar.gz && cd boost_1_65_1 && \
./bootstrap.sh --prefix=/usr/local --with-toolset=gcc --without-libraries=python && \
sudo ./b2 -j2 --prefix=/usr/local --without-python toolset=gcc install && \
cd ../ && rm -rf ./boost_1_65_1*
Once you have finished, confirm that gcc and make are installed:
$ gcc --version
$ make --version
CMake
The algorithm library of Milvus, Knowhere is written in c++. CMake is required in the Milvus compilation. If you don't have it, please follow the instructions in the Installing CMake.
Confirm that cmake is available:
$ cmake --version
Note: 3.18 or higher cmake version is required to build Milvus.
Go
Milvus is written in Go. If you don't have a Go development environment, please follow the instructions in the Go Getting Started guide.
Confirm that your GOPATH and GOBIN environment variables are correctly set as detailed in How to Write Go Code before proceeding.
$ go version
Note: go1.15 is required to build Milvus.
Docker & Docker Compose
Milvus depends on etcd, Pulsar and MinIO. Using Docker Compose to manage these is an easy way in local development. To install Docker and Docker Compose in your development environment, follow the instructions from the Docker website below:
- Docker: https://docs.docker.com/get-docker/
- Docker Compose: https://docs.docker.com/compose/install/
Building Milvus
To build the Milvus project, run the following command:
$ make all
If this command succeed, you will now have an executable at bin/milvus off of your Milvus project directory.
If you want to update proto file before make, we can use the following command:
$ make generated-proto-go
If you want to know more, you can read Makefile.
A Quick Start for Testing Milvus
Presubmission Verification
Presubmission verification provides a battery of checks and tests to give your pull request the best chance of being accepted. Developers need to run as many verification tests as possible locally.
To run all presubmission verification tests, use this command:
$ make verifiers
Unit Tests
Pull requests need to pass all unit tests. To run every unit test, use this command:
$ make unittest
Before using make unittest command, we should run a milvus's deployment environment which helps us to do go test. Here we use local docker environment, use the following commands:
# Using cluster environment
$ cd deployments/docker/dev
$ docker-compose up -d
$ cd ../../../
$ make unittest
# Or using standalone environment
$ cd deployments/docker/standalone
$ docker-compose up -d
$ cd ../../../
$ make unittest
To run only cpp test, we can use this command:
make test-cpp
To run only go test, we can use this command:
make test-go
To run single test case, for instance, run TestSearchTask in /internal/proxy directory, use
$ go test -v ./internal/proxy/ -test.run TestSearchTask
Code coverage
Before submitting your Pull Request, make sure your code change is covered by unit test. Use the following commands to check code coverage rate:
Install lcov(cpp code coverage tool):
$ sudo apt-get install lcov
Run unit test and generate code coverage report:
$ make codecov
This command will generate html report for Golang and C++ respectively.
For Golang report, open the go_coverage.html under milvus project path.
For C++ report, open the cpp_coverage/index.html under milvus project path.
You also can generate Golang coverage report by:
$ make codecov-go
Or C++ coverage report by:
$ make codecov-cpp
E2E Tests
Milvus uses Python SDK to write test cases to verify the correctness of Milvus functions. Before running E2E tests, you need a running Milvus:
# Running Milvus cluster
$ cd deployments/docker/dev
$ docker-compose up -d
$ cd ../../../
$ ./scripts/start_cluster.sh
# Or running Milvus standalone
$ cd deployments/docker/standalone
$ docker-compose up -d
$ cd ../../../
$ ./scripts/start_standalone.sh
To run E2E tests, use these commands:
$ cd tests/python_client
$ pip install -r requirements.txt
$ pytest --tags=L0 -n auto
Test on local branch
On Linux
After preparing deployment environment, we can start the cluster on your host machine
$ ./scripts/start_cluster.sh
With docker
start the cluster on your host machine
$ ./build/builder.sh make install // build milvus
$ ./build/build_image.sh // build milvus lastest docker
$ docker images // check if milvus latest image is ready
REPOSITORY TAG IMAGE ID CREATED SIZE
milvusdb/milvus latest 63c62ff7c1b7 52 minutes ago 570MB
$ install with docker compose
GitHub Flow
To check out code to work on, please refer to the GitHub Flow.