Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go get does build a binary... but the binary isn't particularly useful #986

Closed
onsi opened this issue Sep 4, 2014 · 11 comments
Closed

go get does build a binary... but the binary isn't particularly useful #986

onsi opened this issue Sep 4, 2014 · 11 comments

Comments

@onsi
Copy link

onsi commented Sep 4, 2014

As of e393509

go get -u github.com/coreos/etcd
etcd --help
Usage of etcd:
  -id="0xBEEF": Id of this server
  -l=":8080": HTTP service address (e.g., ':8080')
  -peers=todo: your peers
  -timeout=10s: Request Timeout

This is blocking all our pipelines that test against HEAD of etcd....
...and seems pretty bad.

@brendandburns
Copy link

+1, we're seeing this as well. It seems that running a minimal, single-node etcd is not as simple as

./etcd

anymore.

@philips
Copy link
Contributor

philips commented Sep 4, 2014

Yea, we must restore the ./etcd works use case.

@onsi
Copy link
Author

onsi commented Sep 4, 2014

I'm a bit confused. Right now there's literally no way to clone HEAD of coreos/etcd and build an etcd binary that can be run (whether a single-node or otherwise).

Is there, in fact, a way to build etcd that isn't go get that produces a working binary with all the flags that we need to pass it?

@xiang90
Copy link
Contributor

xiang90 commented Sep 5, 2014

@onsi The binary will not be useful as you described for a while. Please refer the email we sent in etcd-dev.
We plan to do a rc release around 9/20.
Sorry for the inconvenience!

@WhackoJacko
Copy link

@xiangli-cmu so, what is the solution? Etcd listens neither 4001 nor 7001 port.

@andrewmichaelsmith
Copy link

Worth updating the README.md? Was following the tutorial in that and quite baffled that etcd was coming up on port 8080 but not 4001/7001.

andrewmichaelsmith added a commit to andrewmichaelsmith/etcd that referenced this issue Sep 8, 2014
@jonboulle
Copy link
Contributor

I've made some tweaks to the README to reflect that users should use the tagged releases for now. We also have a couple of imminent changes to clarify the port situation:
#993 #948 #1010

@onsi
Copy link
Author

onsi commented Sep 11, 2014

Is 0.5 going to change the etcd binary's public interface? Are all the flags going to change? Just trying to understand how much work it's going to be to change our code to support 0.5.

@yichengq
Copy link
Contributor

@onsi Some flags may be changed because it makes user confused easily, but it should be easy to move from 0.4 to 0.5.
The flags in current master are just workarounds. And it will be refined.
We will record all changes in CHANGELOG, and give some method on how to adapt it.

@onsi
Copy link
Author

onsi commented Sep 11, 2014

great thanks!

On Thu, Sep 11, 2014 at 11:55 AM, Yicheng Qin [email protected]
wrote:

@onsi https://github.com/onsi Some flags may be changed because it
makes user confused easily, but it should be easy to move from 0.4 to 0.5.
The flags in current master are just workarounds. And it will be refined.
We will record all changes in CHANGELOG, and give some method on how to
adapt it.


Reply to this email directly or view it on GitHub
#986 (comment).

@barakmich
Copy link
Contributor

Works on HEAD today -- much more help, perhaps on the side of too verbose/complicated.

And running ./etcd for a single node works too.

(13:04|3)[barak@titania ~]
$ etcd --help
  -addr=:0: DEPRECATED: Use -advertise-client-urls instead.
  -advertise-client-urls=http://localhost:2379,http://localhost:4001: List of this member's client URLs to advertise to the rest of the cluster
  -advertise-peer-urls=http://localhost:2380,http://localhost:7001: List of this member's peer URLs to advertise to the rest of the cluster
  -bind-addr=:0: DEPRECATED: Use -listen-client-urls instead.
  -ca-file=: Path to the client server TLS CA file.
  -cert-file=: Path to the client server TLS cert file.
  -cors=: Comma-separated white list of origins for CORS (cross-origin resource sharing).
  -data-dir=: Path to the data directory
  -discovery=: Discovery service used to bootstrap the cluster
  -initial-cluster=: Initial cluster configuration for bootstrapping
  -initial-cluster-state=: Initial cluster configuration for bootstrapping
  -key-file=: Path to the client server TLS key file.
  -listen-client-urls=http://localhost:2379,http://localhost:4001: List of URLs to listen on for client traffic
  -listen-peer-urls=http://localhost:2380,http://localhost:7001: List of URLs to listen on for peer traffic
  -name=default: Unique human-readable name for this node
  -peer-addr=:0: DEPRECATED: Use -advertise-peer-urls instead.
  -peer-bind-addr=:0: DEPRECATED: Use -listen-peer-urls instead.
  -peer-ca-file=: Path to the peer server TLS CA file.
  -peer-cert-file=: Path to the peer server TLS cert file.
  -peer-key-file=: Path to the peer server TLS key file.
  -peers=: DEPRECATED: Use -initial-cluster instead
  -peers-file=: DEPRECATED: Use -initial-cluster instead
  -proxy=: Valid values include off, readonly, on
  -snapshot-count=10000: Number of committed transactions to trigger a snapshot
  -version=false: Print the version and exit
(13:04|4)[barak@titania ~]
$ etcd
2014/10/20 13:04:09 etcd: no data-dir provided, using default data-dir ./default_etcd_data
2014/10/20 13:04:09 etcdserver: start node 701739929774025524
2014/10/20 13:04:09 Listening for peers on http://localhost:2380
2014/10/20 13:04:09 Listening for peers on http://localhost:7001
2014/10/20 13:04:09 Listening for client requests on http://localhost:2379
2014/10/20 13:04:09 Listening for client requests on http://localhost:4001
2014/10/20 13:04:11 raft: leader changed from 0x0 to 0x9bd14bf86e36b34
2014/10/20 13:04:11 etcdserver: published {Name:default ClientURLs:[http://localhost:2379 http://localhost:4001]} to the cluster

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

9 participants