Etcd: Move etcd to github.com/etcd-io/etcd*

[gyuho]

We are moving etcd and other sub-projects to its own GitHub organization.

The new org will be https://github.com/etcd-io.

Many popular Go projects have done this, for better project management:

• https://github.com/google/protobuf/issues/4796
• https://github.com/kubernetes/kubernetes/issues/12211, https://github.com/kubernetes/kubernetes/issues/29014
• https://github.com/vitessio/vitess/pull/3702, https://github.com/vitessio/vitess/pull/3725

Some of our motivations are:

• Better team management.
• Better CI resource utilization; currently, etcd relies on free-tier public CI service, and sharing all resources with other github.com/coreos projects slows down development process.
• More visibilities to sub-projects and adopt more community projects under etcd organization.

Move github.com/coreos/etcd and github.com/coreos/bbolt:

• [x] Decide which namespace we will be using (1 ~ 2 weeks)
• [x] Announce to etcd and Kubernetes communities (Mon, August 6, 2018)
• [x] Update all internal github.com/coreos/etcd import paths in all branches (5PM PST, Mon, August 27, 2018)
• [x] Disable CI integration with current org (5PM PST, Mon, August 27, 2018)
• [x] Transfer ownership (5PM PST, Mon, August 27, 2018)
• [x] Set up new CIs (5PM PST, Mon, August 27, 2018)
  
  
  
  • Add environmental variable ETCD_ELECTION_TIMEOUT_TICKS=600
  
  
• [x] Make sure old URL redirects to new URL (5PM PST, Mon, August 27, 2018)
• [x] Set up vanity import paths to go.etcd.io/$proj

Sub-projects that do not have downstream projects can be transferred right away:

• [x] https://github.com/coreos/cetcd (9PM PST, Tue, August 7, 2018)
• [x] https://github.com/coreos/zetcd (9PM PST, Tue, August 7, 2018)
• [x] https://github.com/coreos/gofail (9PM PST, Tue, August 7, 2018)
• [x] https://github.com/coreos/dbtester (Mon, August 6, 2018)
• [x] https://github.com/coreos/etcdlabs (Mon, August 6, 2018)
• [x] https://github.com/coreos/etcd-play (Mon, August 6, 2018)
• [x] https://github.com/coreos/protodoc (Mon, August 6, 2018)
• [x] https://github.com/coreos/jetcd (9PM PST, Tue, August 7, 2018)

Projects that won't be moved:

• https://github.com/coreos/etcd-operator
• https://github.com/coreos/discovery.etcd.io

Note: GitHub will redirect all requests to new URL.

/cc @xiang90 @jpbetz @lburgazzoli @philips @jberkus

[xiang90]

probably we should try to get etcd org? Can someone try to contact the current owner?

[gyuho]

@xiang90 We have been already doing that for the past several months :)
Will keep you updated here.

[tamalsaha]

What does etcd mean?

[gyuho]

@tamalsaha http://etcd.readthedocs.io/en/latest/faq.html#how-to-pronounce-etcd

[lburgazzoli]

+1 for jetcd

[jpbetz]

Fingers crossed that we can get the etcd org. If not, some alternatives that come to mind: etcd-project, cncf-etcd, etcd-development (as already suggested), etcd-org

[hexfusion]

perhaps a few others to consider etcd-io etcd-dev

[philips]

I think etcd-io is reasonable given the ownership of etcd.io.

Brandon

On Tue, Jul 31, 2018 at 1:42 PM Sam Batschelet [e-mail]
wrote:

perhaps a few others to consider etcd-io etcd-dev

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coreos/etcd/issues/9965#issuecomment-409360703, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACDCDhGuhP7SZYsFBJe6vanCbwfPaxCks5uMME8gaJpZM4Vkztd
.

[hexfusion]

FTR I have secured etcd-io and can move to any user if we decide to go with that.

[jberkus]

Is there already a list of org owners for once we move? That is, folks who should have org admin rights?

[hexfusion]

Probably the maintainers should be owners?

https://github.com/coreos/etcd/blob/master/MAINTAINERS

On Jul 31, 2018, at 6:36 PM, Josh Berkus [e-mail] wrote:

Is there already a list of org owners for once we move? That is, folks who should have org admin rights?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[gyuho]

etcd-io sounds good to me, if we don't get etcd by this week.

@xiang90 @jpbetz Any thoughts?

[jpbetz]

@gyuho I'm happy with etcd-io. It's nice and short and maps clearly a domain CoreOS already owns. Kubernetes has gotten a lot of usage out of k8s.io and kubernetes.io domains. It's okay for the etcd.io domain to be donated to CNCF along with etcd, I assume?

[philips]

Yes. Etcd.io will be donated along with the other things like mailing
groups, etc

On Wed, Aug 1, 2018, 11:38 AM Joe Betz [e-mail] wrote:

@gyuho https://github.com/gyuho I'm happy with etcd-io. It's nice and
short and maps clearly a domain CoreOS already owns. Kubernetes has gotten
a lot of usage out of k8s.io and kubernetes.io. It's okay for the etcd.io
domain to be donated to CNCF along with etcd, I assume?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coreos/etcd/issues/9965#issuecomment-409678436, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACDCEzJGz4Vgme69pbGuoYOW8CI8mOnks5uMfWJgaJpZM4Vkztd
.

[gyuho]

Sounds good. Let’s go for etcd-io.

[hexfusion]

Gyuho is now the owner of https://github.com/etcd-io

[jberkus]

Yah, just so you know, no further word on the /etcd/ namespace. If we get it someday, that would be great, but don't expect it any time soon.

[gyuho]

Ok, will announce next week.

[lburgazzoli]

@gyuho I'm preparing the sonatype oss stuffs for the migration of jetcd so, do we already own etcd.io ?

[gyuho]

@lburgazzoli Yes, CoreOS owns etcd.io. /cc @philips

[gyuho]

@lburgazzoli I am ready to transfer all sub projects by tonight or tomorrow. Do you have access to jetcd settings to transfer ownership?

[lburgazzoli]

@gyuho I don't have access to jetcd settings

[gyuho]

@lburgazzoli I can transfer. How about today, 9PM (PST), August 7, 2018?

[lburgazzoli]

fine with me

[gyuho]

@lburgazzoli Ok, I will transfer that tonight. Thanks!

[gyuho]

I don't have rights to move repositories any more. Contacted CoreOS team to move rest of the sub projects.

[philips]

transferred the remaining subprojects.

[gyuho]

@philips Thanks!

[jberkus]

How was this announced to Kubernetes project? I didn't see the announcement, so wondering where it was sent.

[gyuho]

@jberkus Here https://groups.google.com/forum/#!topic/kubernetes-dev/omNEDP9vTmQ.

[jberkus]

Suggestions for additional notices:

1. Put a warning in the README of the current repo
2. Share on #etcd and #coreos on IRC
3. CoreOS blog and twitter (I can handle this)
4. Are there other major projects we should be notifying?

I'm happy to help get the notices out. Just let me know if that's OK.

[gyuho]

@jberkus Sounds good. If you can help with 2 and 3, it would be great. We have a list of projects that should be aware of this. Will inform them (even though they are already vendoring etcd).

[philips]

I think github.com/coreos/discovery.etcd.io needs to be moved over to the new organization and if etcd is accepted to CNCF the CNCF needs to help run and operate the service.

cc @joelegasse

[philips]

I will take care of the etcd GH org moves next monday.

[philips]

We are going to skip the blog post (mentioned in https://github.com/coreos/etcd/issues/9965#issuecomment-411513749) and instead just do emails to coreos-dev and etcd-dev Google Groups.

This was my call, I don't think this URL change effects so many people that we need to notify all CoreOS blog readers. Particularly since GitHub will maintain a redirect to the old URLs.

[gyuho]

Disabled Semaphore CI integration. Will enable once migrated today.

[gyuho]

@philips Ping?

[philips]

transferred to etcd-io

[philips]

Confirmed the redirect worked. Can you do CI work @gyuho

[gyuho]

Will do. Thanks @philips !

[gyuho]

@philips Can we also move https://github.com/coreos/bbolt?

[philips]

done

On Mon, Aug 27, 2018 at 6:34 PM Gyuho Lee [e-mail] wrote:

@philips https://github.com/philips Can we also move
https://github.com/coreos/bbolt?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/etcd-io/etcd/issues/9965#issuecomment-416421626, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACDCKm7fN0orvXLTM1NNQdjp0VoQtcEks5uVJ4RgaJpZM4Vkztd
.

[gyuho]

@philips Thanks!

[philips]

While we are doing this should we do Go vanity URL for everything? go get etcd.io/etcd for example.

On Mon, Aug 27, 2018, 6:41 PM Gyuho Lee [e-mail] wrote:

@philips https://github.com/philips Thanks!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/etcd-io/etcd/issues/9965#issuecomment-416422802, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACDCF3G6_0cG2JLI4XPFxaEh0XtEyrDks5uVJ_MgaJpZM4Vkztd
.

[gyuho]

@philips Good idea (as k8s.io does). I think we can take a few days to migrate import paths. Can you help set up DNS for etcd.io?

[philips]

Probably easier if we do go.etcd.io or something instead and deploy
https://github.com/GoogleCloudPlatform/govanityurls/blob/master/README.md.

Yes I could do the DNS work.

On Mon, Aug 27, 2018, 7:31 PM Gyuho Lee [e-mail] wrote:

@philips https://github.com/philips Good idea (as k8s.io does). I think
we can take a few days to migrate import paths. Can you help set up DNS for
etcd.io?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/etcd-io/etcd/issues/9965#issuecomment-416430508, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACDCOfNoE9zeYC4FQXspqJxdFulbR-Fks5uVKtvgaJpZM4Vkztd
.

[gyuho]

Sounds good. We will wait until etcd.io DNS is ready.

[philips]

We need to configure and deploy the app engine app first. Then do the DNS.

I can deploy the app but I don't think I have access to the etcd Google
cloud account. Could you add [email protected]?

On Mon, Aug 27, 2018, 7:36 PM Gyuho Lee [e-mail] wrote:

Sounds good. We will wait until etcd.io DNS is ready.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/etcd-io/etcd/issues/9965#issuecomment-416431370, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACDCB_jRhtA7Tz4doO1Emcuook0JL08ks5uVKy2gaJpZM4Vkztd
.

[gyuho]

@philips Yeah, I only see your coreos.com email. Just sent an invite to that email address (https://console.cloud.google.com/compute/instances?project=etcd-development). Thanks!

[philips]

I have everything deployed for go.etcd.io but https://go.etcd.io isn't working; only http://go.etcd.io... hrm

FWIW, configuration is here: https://github.com/etcd-io/govanityurls

[philips]

@gyuho spoke too soon. Everything is working! Feel free to use go.etcd.io for package names. See https://go.etcd.io for how I set things up.

[gyuho]

@philips Will do today. Thanks!

[philips]

@gyuho OK, LMK if you need help or a code review.

[gyuho]

@philips Sure, will cc you. I've updated bbolt first. Now updating etcd ones.

[philips]

👍

On Tue, Aug 28, 2018, 4:50 PM Gyuho Lee [e-mail] wrote:

@philips https://github.com/philips Sure, will cc you. I've updated
bbolt first. Now updating etcd ones.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/etcd-io/etcd/issues/9965#issuecomment-416776938, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACDCNZAeIp13fWqhgaa7Z5jHaO4z1ECks5uVddWgaJpZM4Vkztd
.

[gyuho]

All done. Thanks all!

[vimalk78]

i just tried to go get etcd, and getting below errors. This is in my office environment, behind a firewall.

 ~/gowork/src$ go get -v github.com/etcd-io/etcd
Fetching https://go.etcd.io/etcd/etcdmain?go-get=1
https fetch failed: Get https://go.etcd.io/etcd/etcdmain?go-get=1: x509: certificate signed by unknown authority
package go.etcd.io/etcd/etcdmain: unrecognized import path "go.etcd.io/etcd/etcdmain" (https fetch: Get https://go.etcd.io/etcd/etcdmain?go-get=1: x509: certificate signed by unknown authority)

 ~/gowork/src$ go get -v go.etcd.io/etcd
Fetching https://go.etcd.io/etcd?go-get=1
https fetch failed: Get https://go.etcd.io/etcd?go-get=1: x509: certificate signed by unknown authority
package go.etcd.io/etcd: unrecognized import path "go.etcd.io/etcd" (https fetch: Get https://go.etcd.io/etcd?go-get=1: x509: certificate signed by unknown authority)

But, go get -v github.com/coreos/etcd is fine here. just thought of reporting the difference i observed.

[philips]

Vimal- does that URL work in your browser? What OS are you using? The site
is using the very common Let's Encrypt CA.

Common Name (CN)
Let's Encrypt Authority X3
Organization (O)
Let's Encrypt
Organizational Unit (OU)
<Not Part Of Certificate>

[vimalk78]

I am on Ubuntu 14.04 LTS
the URL doesnt works with curl.
curl: (35) error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

after adding following certs, still i get the same error with curl and go get
https://letsencrypt.org/certs/isrgrootx1.pem.txt
https://letsencrypt.org/certs/lets-encrypt-x3-cross-signed.pem.txt

querying /etc/ssl/certs/ca-certificates.crt gives :
subject= /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
subject= /C=US/O=Internet Security Research Group/CN=ISRG Root X1

i have an alternate environment outside the firewall, so this is not blocking