af5286c63b
Godeps should allow me to do godep restore godep save -r ./... But that doesn't work. Try it. This requires update to the following packages: github.com/prometheus/client_golang/ github.com/prometheus/procfs github.com/matttproud/golang_protobuf_extensions/ There were 2 major problems. 1. godeps have code.google.com/p/goprotobuf but that repo doesn't exist 2. prometheus/client_golang/_vendor moved to other packages and godep (with -r) can't handle it. At the end of this we should be able to use godeps again without tons of black magic. uggh. what a pain in the ass. The black magic to actually get godeps back in shape was: ```bash # remove code.google.com/p/goprotobuf (doesn't exist) # remove all _vendor lines from prometheus (we still have other # prometheus lines so restore still works) vi Godeps/Godeps.json # remove all the crazy vendoring crud because godep doesn't handle it # correctly find . -name \*.go | xargs sed -i 's|github.com/coreos/etcd/Godeps/_workspace/src/||' # ok now, restore as best we can (everything except it wines about # goprotobuf godep restore # now update the packages which were using the old (dead) goprotobuf go get -u github.com/prometheus/client_golang/ go get -u github.com/matttproud/golang_protobuf_extensions/ # update prometheus procfs because prometheus/client_golang/ has a # dependancy on this update go get -u github.com/prometheus/procfs # get rid of Godeps directory entirely git rm -rf Godeps # ok, now, rewrite the Godeps directory and redo the path rewrites godep save -r ./... # now put Godeps back into git git add Godeps/ # commit the new code git commit -aA # And now, you can use godeps! godep restore godep save -r ./... git diff # nothing!! ```
etcd
etcd is a distributed, consistent key value store for shared configuration and service discovery with a focus on being:
- Simple: curl'able user facing API (HTTP+JSON)
- Secure: optional SSL client cert authentication
- Fast: benchmarked 1000s of writes/s per instance
- Reliable: properly distributed using Raft
etcd is written in Go and uses the Raft consensus algorithm to manage a highly-available replicated log.
See etcdctl for a simple command line client. Or feel free to just use curl, as in the examples below.
If you're considering etcd for production use, please see: production-ready.md
Getting Started
Getting etcd
The latest release and setup instructions are available at GitHub.
You can build a latest etcd from master branch. All development occurs on the master branch which includes new features and bug fixes.
Bug fixes should target the master branch and ported to the appropriate release branch as described in the branch management guide.
Running etcd
First start a single-member cluster of etcd:
./bin/etcd
This will bring up etcd listening on port 2379 for client communication and on port 2380 for server-to-server communication.
Next, let's set a single key, and then retrieve it:
curl -L http://127.0.0.1:2379/v2/keys/mykey -XPUT -d value="this is awesome"
curl -L http://127.0.0.1:2379/v2/keys/mykey
You have successfully started an etcd and written a key to the store.
Running local etcd cluster
First install goreman, which manages Procfile-based applications.
Our Procfile script will set up a local example cluster. You can start it with:
goreman start
This will bring up 3 etcd members infra1, infra2 and infra3 and etcd proxy proxy, which runs locally and composes a cluster.
You can write a key to the cluster and retrieve the value back from any member or proxy.
Next Steps
Now it's time to dig into the full etcd API and other guides.
- Explore the full API.
- Set up a multi-machine cluster.
- Learn the config format, env variables and flags.
- Find language bindings and tools.
- Use TLS to secure an etcd cluster.
- Tune etcd.
- Upgrade from 0.4.6 to 2.0.0.
Contact
- Mailing list: etcd-dev
- IRC: #coreos on freenode.org
- Planning/Roadmap: milestones
- Bugs: issues
Contributing
See CONTRIBUTING for details on submitting patches and the contribution workflow.
Project Details
Versioning
Service Versioning
etcd uses semantic versioning New minor versions may add additional features to the API.
You can get the version of etcd by issuing a request to /version:
curl -L http://127.0.0.1:2379/version
API Versioning
The v2 API responses should not change after the 2.0.0 release but new features will be added over time.
32-bit systems
etcd has known issues on 32-bit systems due to a bug in the Go runtime. See #358 for more information.
License
etcd is under the Apache 2.0 license. See the LICENSE file for details.