Mirroristas/etcd
2
0
Fork 0
mirror of https://github.com/etcd-io/etcd.git synced 2024-09-27 06:25:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #8108 from radhikapc/building-qa

Browse Source 
etcd/Documentation/dl_build.md: removed an extra step for testing etcd
This commit is contained in:
Anthony Romano 2017-06-15 16:48:50 -07:00 committed by GitHub
commit 03ab4d9cc5
1 changed files with 13 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
Documentation/dl_build.md
View File

@ -2,7 +2,7 @@
## System requirements ## System requirements
The etcd performance benchmarks run etcd on 8 vCPU, 16GB RAM, 50GB SSD GCE instances, but any relatively modern machine with low latency storage and a few gigabytes of memory should suffice for most use cases. Applications with large v2 data stores will require more memory than a large v3 data store since data is kept in anonymous memory instead of memory mapped from a file. than For running etcd on a cloud provider, we suggest at least a medium instance on AWS or a standard-1 instance on GCE. The etcd performance benchmarks run etcd on 8 vCPU, 16GB RAM, 50GB SSD GCE instances, but any relatively modern machine with low latency storage and a few gigabytes of memory should suffice for most use cases. Applications with large v2 data stores will require more memory than a large v3 data store since data is kept in anonymous memory instead of memory mapped from a file. For running etcd on a cloud provider, see the [Example hardware configuration][example-hardware-configurations] documentation.
## Download the pre-built binary ## Download the pre-built binary
@ -18,7 +18,6 @@ To build `etcd` from the `master` branch without a `GOPATH` using the official `
$ git clone https://github.com/coreos/etcd.git $ git clone https://github.com/coreos/etcd.git
$ cd etcd $ cd etcd
$ ./build $ ./build
$ ./bin/etcd
``` ```
To build a vendored `etcd` from the `master` branch via `go get`: To build a vendored `etcd` from the `master` branch via `go get`:
@ -28,7 +27,6 @@ To build a vendored `etcd` from the `master` branch via `go get`:
$ echo $GOPATH $ echo $GOPATH
/Users/example/go /Users/example/go
$ go get github.com/coreos/etcd/cmd/etcd $ go get github.com/coreos/etcd/cmd/etcd
$ $GOPATH/bin/etcd
``` ```
To build `etcd` from the `master` branch without vendoring (may not build due to upstream conflicts): To build `etcd` from the `master` branch without vendoring (may not build due to upstream conflicts):
@ -38,20 +36,28 @@ To build `etcd` from the `master` branch without vendoring (may not build due to
$ echo $GOPATH $ echo $GOPATH
/Users/example/go /Users/example/go
$ go get github.com/coreos/etcd $ go get github.com/coreos/etcd
$ $GOPATH/bin/etcd
``` ```
## Test the installation ## Test the installation
Check the etcd binary is built correctly by starting etcd and setting a key. Check the etcd binary is built correctly by starting etcd and setting a key.
Start etcd: ### Starting etcd
If etcd is built without using GOPATH, run the following:
``` ```
$ ./bin/etcd $ ./bin/etcd
``` ```
If etcd is built using GOPATH, run the following:
Set a key: ```
$ $GOPATH/bin/etcd
```
### Setting a key
Run the following:
``` ```
$ ETCDCTL_API=3 ./bin/etcdctl put foo bar $ ETCDCTL_API=3 ./bin/etcdctl put foo bar
@ -64,4 +70,4 @@ If OK is printed, then etcd is working!
[go]: https://golang.org/doc/install [go]: https://golang.org/doc/install
[build-script]: ../build [build-script]: ../build
[cmd-directory]: ../cmd [cmd-directory]: ../cmd
[example-hardware-configurations]: op-guide/hardware.md#example-hardware-configurations