github.com/tw-bc-group/fabric-ca-gm@v0.0.0-20201218004200-3b690512bd5a/README.md (about) 1 # Fabric CA Developer's Guide 2 3 This is the Developer's Guide for Fabric CA, which is a Certificate Authority for Hyperledger Fabric. 4 5 See [User's Guide for Fabric CA](https://hyperledger-fabric-ca.readthedocs.io) for information on how to use Fabric CA. 6 7 ## Prerequisites 8 9 * Go 1.14.7 installation or later 10 * **GOPATH** environment variable is set correctly 11 * docker version 19.03.13 or later 12 * docker-compose version 1.27.4 or later 13 * A Linux Foundation ID (see [create a Linux Foundation ID](https://identity.linuxfoundation.org/)) 14 15 ## Build artifacts 16 ``` 17 $ make native 18 $ make docker 19 ``` 20 21 ## Contribution guidelines 22 23 You are welcome to contribute to Fabric CA! 24 25 The following are guidelines to follow when contributing: 26 27 1. See the general information about [contributing to fabric](http://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html). 28 29 2. To set up your development environment for doing common development tasks, see [bash_profile](https://github.com/hyperledger/fabric-ca/blob/master/scripts/bash_profile). This contains variables and functions which can be copied directly into your `.bash_profile` file. Even if you do not use bash, you should still find the functions instructive. For example: 30 a. **clone** - pulls the latest fabric-ca code from gerrit and places it based on your GOPATH setting 31 b. **cdr** - cd to the fabric-ca repository root, which is equivalent to "cd $GOPATH/src/github.com/hyperledger/fabric-ca" 32 c. **gencov** - generates a test coverage report 33 34 3. To run the unit tests manually: 35 36 ``` 37 # cdr 38 # make unit-tests 39 ``` 40 41 The test coverage for each package must be 75% or greater. If this fails due to insufficient test coverage, then you can run `gencov` to get a coverage report to see what code is not being tested. Once you have added additional test cases, you can run `go test -cover` in the appropriate package to see the current coverage level. 42 43 WARNING: Running the unit-tests may fail due to too many open file descriptors. 44 Depending on where the failure occurs, the error message may not be obvious and may only say something similar to "unable to open database file". 45 Depending on the settings on your host, you may need to increase the maximum number of open file descriptors. 46 For example, the OSX default per-process maximum number of open file descriptors is 256. 47 You may issue the following command to display your current setting: 48 49 ``` 50 # ulimit -n 51 256 52 ``` 53 54 And the following command will increase this setting to 65536: 55 56 ``` 57 # ulimit -n 65536 58 ``` 59 60 Please note that this change is only temporary. To make it permanent, you will need to consult the documentation for your host operating system. 61 62 ## Package overview 63 64 1. **cmd/fabric-ca-server** contains the main for the fabric-ca-server command. 65 2. **cmd/fabric-ca-client** contains the main for the fabric-ca-client command. 66 3. **lib** contains most of the code. 67 a) **server.go** contains the main Server object, which is configured by **serverconfig.go**. 68 b) **client.go** contains the main Client object, which is configured by **clientconfig.go**. 69 4. **util/csp.go** contains the Crypto Service Provider implementation. 70 5. **lib/dbutil** contains database utility functions. 71 6. **lib/ldap** contains LDAP client code. 72 7. **lib/spi** contains Service Provider Interface code for the user registry. 73 8. **lib/tls** contains TLS related code for server and client. 74 9. **util** contains various utility functions. 75 76 ## Additional info 77 78 ## Profiling 79 Fabric CA server can be profiled two ways, namely, using benchmarks and by retrieving profiling data from the server (at /debug/pprof/ endpoint) while running load. 80 81 ### Benchmarks 82 You can profile the benchmarks by running `make bench-cpu` or `make bench-mem` commands. You can profile benchmarks in one package or all the packages using these make targets. For example, to profile benchmarks in the *lib* package, run: `make bench-cpu pkg=github.com/hyperledger/fabric-ca/lib`. This will create **bench-cpu.prof**, **lib.test** and **bench** files in the *lib* folder. The **bench** file will contain benchmark stats: bytes/operation, allocations/operation and nanoseconds/operation. **lib.test** file is the executable and **bench-cpu.prof** contains cpu profile information. To analyze the profile, run: `go tool pprof lib.test bench-cpu.prof`. Similarly, you can run `make bench-mem pkg=github.com/hyperledger/fabric-ca/lib` to perform memory profiling of the benchmarks in the *lib* package. The **bench-mem.prof** file contains memory profile information. 83 84 If you run `make bench-cpu` or `make bench-mem` without *pkg* variable, benchmarks in each package are run with cpu or memory profiling. So, executable, benchmark output, and profile info files are created in each package folder. You need to analyze these profiles separately. 85 86 ### Whole server 87 To enable profiling on the server, set the FABRIC_CA_SERVER_PROFILE_PORT environment 88 variable to a valid, available port number and start the server. The server will start listening for profile requests at the */debug/pprof/* HTTP endpoint and the specified port. Then run `go tool pprof` with server's profiling URL (http://<server host>:<profiling port>/debug/pprof/<profile|heap|block>) as an argument, it will download and examine a live profile. 89 90 You can start the server in the FVT image by running following docker command from the fabric-ca root directory: 91 92 `docker run -p 8888:8888 -p 8054:8054 -v $PWD:/opt/gopath/src/github.com/hyperledger/fabric-ca -e FABRIC_CA_SERVER_PROFILE_PORT=8054 --name loadTest -td hyperledger/fabric-ca-fvt test/fabric-ca-load-tester/launchServer.sh 1` 93 94 Then start the load by running `/test/fabric-ca-load-tester/runLoad.sh -B` 95 96 In other window, you can start profiling by running (assuming load test takes about a minute to complete): 97 98 `curl http://localhost:8054/debug/pprof/profile?seconds=60 > load-cpu.prof` 99 100 then analyze the profile: 101 102 `go tool pprof bin/fabric-ca-server load-cpu.prof` 103 104 OR simply run: 105 106 `go tool pprof -seconds=60 -output=load-cpu.prof http://localhost:8054/debug/pprof/profile` 107 108 You can use commands like *top*, *top -cum*, *list* and *web* to look at the top consumers, list the code to see the hotspots and to view the graph in a browser. You can run `go tool pprof -h` to view all the options supported by the pprof tool 109 110 You can also use [**go-torch**](https://github.com/uber/go-torch) tool to analyze the profile: 111 112 `go-torch bin/fabric-ca-server load-cpu.prof` 113 114 ### Profiling Fabric CA client 115 To enable profiling on the client, set the FABRIC_CA_CLIENT_PROFILE_MODE environment variable to either "heap" or "cpu" to enable heap, cpu profiling respectively. A file containing profiling data is created in the present working directory of the client. Heap profiling data is written to **mem.pprof** and cpu profiling data is written to **cpu.pprof**. You can run `go tool pprof <client executable> <profiling file>` to analyze the profiling data. 116 117 ### Profiling links 118 https://blog.golang.org/profiling-go-programs 119 https://medium.com/@hackintoshrao/daily-code-optimization-using-benchmarks-and-profiling-in-golang-gophercon-india-2016-talk-874c8b4dc3c5 120 https://www.youtube.com/watch?v=2h_NFBFrciI 121 https://software.intel.com/en-us/blogs/2014/05/10/debugging-performance-issues-in-go-programs 122 http://www.soroushjp.com/2015/01/27/beautifully-simple-benchmarking-with-go/ 123 https://vinceyuan.github.io/profiling-memory-usage-of-a-go-app/ 124 https://www.youtube.com/watch?v=N3PWzBeLX2M&feature=youtu.be 125 https://www.youtube.com/watch?v=oorX84tBMqo&feature=youtu.be 126 127 ### FVT 128 129 See [FVT tests](scripts/fvt/README.md) for information on functional verification test cases. 130 131 132 ### Updating the cfssl vendored package 133 Following are the steps to update cfssl package using version 1.0.8 of govendor tool. 134 135 * Remove cfssl from vendor folder 136 * cd $GOPATH/src/github.com/hyperledger/fabric-ca/vendor 137 * govendor remove github.com/cloudflare/cfssl/... 138 * rm -rf github.com/cloudflare/cfssl/ 139 140 * Clone cfssl repo 141 * cd $GOPATH/src/github.com/ 142 * mkdir cloudflare 143 * cd cloudflare 144 * git clone https://github.com/cloudflare/cfssl.git 145 146 * Add cfssl from $GOPATH to the vendor folder 147 * cd $GOPATH/src/github.com/hyperledger/fabric-ca/vendor 148 * govendor add github.com/cloudflare/cfssl/^ 149 * You can optionally specify revision or tag to add a particular revision of code to the vendor folder 150 * govendor add github.com/cloudflare/cfssl/^@abc12032 151 152 * Remove sqlx package from cfssl vendor folder. This is because certsql.NewAccessor (called by fabric-ca) requires sqlx.db object to be passed from the same package. If we were to have sqlx package both in fabric-ca and cfssl vendor folder, go compiler will throw an error 153 * rm -rf github.com/cloudflare/cfssl/vendor/github.com/jmoiron/sqlx 154 155 * Remove the packages that are added to the fabric-ca vendor folder that are not needed by fabric-ca 156 157 158 ## Continuous Integration 159 160 Please have a look at [Continuous Integration Process](docs/source/ca-ci.md) 161 162 ## License <a name="license"></a> 163 164 Hyperledger Project source code files are made available under the Apache License, Version 2.0 (Apache-2.0), located in the [LICENSE](LICENSE) file. Hyperledger Project documentation files are made available under the Creative Commons Attribution 4.0 International License (CC-BY-4.0), available at http://creativecommons.org/licenses/by/4.0/.