forked from hyperledger/fabric
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge "Move Docker-Compose files into their own folder"
- Loading branch information
Showing
29 changed files
with
104 additions
and
65 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# BDD Docker Compose Files | ||
These files are utilized by the BDD tests to provide standardized environments | ||
for running tests cases against. They also conveniently demonstrate some of the | ||
different configurations that the peers can be run in. | ||
|
||
For convenience, all the configurations inherit from `compose-defaults.yml`. | ||
|
||
Two important notes: | ||
|
||
1. If a shell script is used as the docker comment to run (say, to add | ||
additional logic before starting a peer) then the shell script and the command | ||
should be invoked with an exec statement so that the signals that docker sends | ||
to the container get through to the process. Otherwise there will be a 10 | ||
second when stopping a container before docker sends a SIGKILL. | ||
See the command used for the peer in `compose-defaults.yml` for an example | ||
|
||
2. The name of peers should adhere to the convention of `vp[0-9]+` as this is | ||
the method as to which peers (as opposed to the membersrvc) are detected during | ||
the BDD runs. Peers are subjected to additional constraints before being | ||
considered 'ready'. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
vp: | ||
image: hyperledger/fabric-peer | ||
environment: | ||
- CORE_PEER_ADDRESSAUTODETECT=true | ||
- CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock | ||
# TODO: This is currently required due to BUG in variant logic based upon log level. | ||
- CORE_LOGGING_LEVEL=DEBUG | ||
# Script will wait until membersrvc is up (if it exists) before starting | ||
# $$GOPATH (double dollar) required to prevent docker-compose doing its own | ||
# substitution before the value gets to the container | ||
command: sh -c "exec $$GOPATH/src/github.com/hyperledger/fabric/bddtests/scripts/start-peer.sh" | ||
# Ideally we'd only mount /var/run/docker.sock but v1.5.2 of docker-compose | ||
# does not have to capability to mount individual files. Hence we mount the | ||
# entire folder in specific folder and specify it explicitly above. | ||
# This issue seems to be sorted in docker-compose 1.8.0 however that requires | ||
# Docker 1.10 and CI isn't at that version yet. | ||
volumes: | ||
- /var/run/:/host/var/run/ | ||
|
||
# Use these options if coverage desired for peers | ||
#image: hyperledger/fabric-peer-coverage | ||
#command: ./peer.test --test.coverprofile=coverage.cov node start | ||
membersrvc: | ||
image: hyperledger/fabric-membersrvc | ||
command: membersrvc |
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
3 changes: 3 additions & 0 deletions
3
bddtests/bdd-docker/docker-compose-4-consensus-vp3-byzantine.yml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
vp3: | ||
environment: | ||
- CORE_PBFT_GENERAL_BYZANTINE=true |
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,18 +1,4 @@ | ||
vp: | ||
image: hyperledger/fabric-peer | ||
environment: | ||
- CORE_PEER_ADDRESSAUTODETECT=true | ||
- CORE_VM_ENDPOINT=http://172.17.0.1:2375 | ||
# TODO: This is currently required due to BUG in variant logic based upon log level. | ||
- CORE_LOGGING_LEVEL=DEBUG | ||
# Script will wait until membersrvc is up (if it exists) before starting | ||
# $$GOPATH (double dollar) required to prevent docker-compose doing its own | ||
# substitution before the value gets to the container | ||
command: sh -c "exec $$GOPATH/src/github.com/hyperledger/fabric/bddtests/scripts/start-peer.sh" | ||
|
||
# Use these options if coverage desired for peers | ||
#image: hyperledger/fabric-peer-coverage | ||
#command: ./peer.test --test.coverprofile=coverage.cov node start | ||
membersrvc: | ||
image: hyperledger/fabric-membersrvc | ||
command: membersrvc | ||
- | | ||
This file is a simple dummy to satisfy the CI scripts which make modifications | ||
to this file. This file now lives in bddtests/bdd-docker. When the CI scripts | ||
are modified to remove that logic, this file can be removed. |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Empty file.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters