1 Introduction
Black Duck is a pioneer in the development of open source testing tools company, whose products include Protex and HUB, Protex emphasis on precision and accuracy of detection, and HUB emphasis on speed and ease of testing.
1.1 Protex
Protex platform is a key component of the kit Black Duck, to provide users with fine-grained (Fragment levels) and high-precision detection capability revenue code, which operates based Black Duck Knowledge (Knowledge Base, KB), supports the deployment of localized use.
1.2 HUB
HUB is an easy to use Black Duck's open source code detection tools for users with a coarse-grained (Open Source component level) open source code detection capability, but it is faster, easy to use, for the code detection accuracy is not high demand more suitable for users, and in addition can detect open HUB compliance, the user can also be found in the open-source software loopholes. HUB relying on Black Duck's open source knowledge base and third-party vulnerability database (NVD), can quickly detect open source software user code contained in the library. HUB's deployment to cloud deployment, open source knowledge base deployed in the cloud, maintained by Black Duck's professional team, users simply install HUB scan test server, the server will scan the user's local feature value of the user code (Hash value) upload to the cloud server, cloud server or the user code and open source code to compare and match results back scan server user test analysis and presentation. HUB compared Protex, provide a richer API, facilitating integration with other systems.
2 Docker installation Blackduck
2.1 Why Docker?
Docker architecture for the Black Duck brings a number of significant improvements:
- Simplified installation and update
- Than a similar virtual machine (VM) take up less space
- Adapt to customer's environment
- Improve performance
Black Duck is deployed as a set of Docker containers, which together constitute the application. Each container play different roles. For example, Web application container handling UI requests, and acts as a container Solr enterprise search platform components. For detailed instructions on each container role, see Synopsys software integrity community "black duck Docker Installation Guide" on.
2.2 Installation Environmental Requirements
Hardware (minimum specifications) | software | The preferred operating system |
64-bit processor core 5 | Docker 17.03.x or Docker 17.06.x (CE or EE) | CentOS 7.3 |
20 GB of RAM | Scheduling tools, such as Docker Swarm **, Docker Compose, Docker Run or Kubernetes. | Ubuntu 16.04.x |
250 GB, and free space for other database containers hubs | For more information about scheduling technology supported, see "Docker Installation Guide." | Oracle Enterprise Linux 7.3 |
Free space for database backup | Red Hat Enterprise Linux Server 7.3 | |
SUSE Linux Enterprise Server 12.x | ||
Docker 17.03.x supported Linux operating system |
2.3 experimental environment
Ali cloud ESS host 8CPU 30GARM 1Mbps 250G hard drive 40G system disk centos7.3
Installation Step 2.4
2.4.1 Installation docker
1, the installation dependencies
yum install -y yum-utils device-mapper-persistent-data lvm2
2, the changes and the use of stable source of yum
yum-config-manager \ --add-repo \ https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
3, the source cache software update yum
yum makecache fast
4, the installation docker-ce
yum install docker-ce
5, start docker
systemctl start docker
6, the establishment of user groups docker
sudo groupadd docker
7, the current user is added docker group (root user can not)
usermod -aG docker $USER
8, the docker configured to start automatically when the system restarts
systemctl enable docker
2.4.2 Installation Blackduck
1. Go to github in Blackduck hub space , and select "blackducksoftware / hub", find the latest version of the hub connection and copy
wget + link address (for example: wget HTTPS: // github.com/blackducksoftware/hub/archive/v4.4.0.tar.gz)
2, extract the installation package
tar xvf installation package name
3, find the hub-proxy.env and the hub-webserver.env file and change the file localhost native IP.
4, the installation package to the path docker-swarm folder Run
docker swarm init
5, ready to install Blackduck, followed by the deployment of all containers composed of Blackduck
docker stack deploy -c docker-compose.yml hub
6, completed the deployment of Docker Swarm
docker service scale hub_jobrunner = 2
2.4.3 to verify and log
1, to determine whether all containers of the state of health
docker ps
2, Blackduck login address for the host IP, port 443, the protocol is https, login user name sysadmin, password blackduck.
3, the next interview login screen map, but it needs to be noted that in order to enter after purchase registration ID, or can not use.
References:
https://www.synopsys.com/blogs/software-security/installing-black-duck-hub/