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

Removed mesos as cloud provider from Kubernetes. #47232

Merged
merged 2 commits into from
Jul 12, 2017

Conversation

gyliu513
Copy link
Contributor

@gyliu513 gyliu513 commented Jun 9, 2017

What this PR does / why we need it:

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #47205

Special notes for your reviewer:

Release note:

Move Mesos Cloud Provider out of Kubernetes Repo

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jun 9, 2017
@k8s-github-robot k8s-github-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. release-note-none Denotes a PR that doesn't merit a release note. labels Jun 9, 2017
@dims
Copy link
Member

dims commented Jun 9, 2017

@gyliu513 Moving this code to an external cloud provider?

@luxas
Copy link
Member

luxas commented Jun 9, 2017

Yay, moving these things out-of-monorepo is a great step for the project!
Thanks @gyliu513 for making that possible!

I'd edit this to add a release note though 😄

@gyliu513
Copy link
Contributor Author

gyliu513 commented Jun 9, 2017

@dims Yes, there are some discussion at at xref #34924 , but I'd like we first move this out of the repo of kubernetes as first step.

@gyliu513
Copy link
Contributor Author

gyliu513 commented Jun 9, 2017

/release-note

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesn't merit a release note. labels Jun 9, 2017
@gyliu513
Copy link
Contributor Author

gyliu513 commented Jun 9, 2017

@luxas done, thanks ;)

@luxas
Copy link
Member

luxas commented Jun 9, 2017

@thockin woot, let's get this LGTM'd :)

@luxas
Copy link
Member

luxas commented Jun 9, 2017

For context to others reading this thread, this is following proposal https://github.com/kubernetes/community/blob/master/contributors/design-proposals/cloud-provider-refactoring.md to make Kubernetes core leaner, one step at a time

@k82cn
Copy link
Member

k82cn commented Jun 9, 2017

sorry for the confusion by (#34924), kube-mesos still need this provider to get all hosts from Mesos until external cloud-provider is done.

@k8s-github-robot k8s-github-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 22, 2017
@luxas
Copy link
Member

luxas commented Jun 24, 2017

@k82cn Is there any tracking issue for moving mesos out?

@k82cn
Copy link
Member

k82cn commented Jun 25, 2017

@luxas , #34924 is used to trace moving mesos out; let me update sub-tasks and dependencies.

@gyliu513
Copy link
Contributor Author

gyliu513 commented Jul 5, 2017

I think the kube-mesos project is dead and I belive no one is working on it, I think that it is time to retire it from Kubernetes. @luxas

@luxas
Copy link
Member

luxas commented Jul 5, 2017

I think the kube-mesos project is dead and I belive no one is working on it, I think that it is time to retire it from Kubernetes.

SGTM, the incubation project kube-mesos-framework hasn't been updated in ~9 months so...

@k82cn
Copy link
Member

k82cn commented Jul 5, 2017

SGTM, the incubation project kube-mesos-framework hasn't been updated in ~9 months so...

I think China Unicom or Didi maybe using that, and I'm not sure whether Mesosphere will include k8s in its DC/OS . Let me check whether anyone of them would like to invest resource for this project.

@luxas
Copy link
Member

luxas commented Jul 5, 2017

@k82cn Anyway, that's not blocking this PR, or is it?

@k82cn
Copy link
Member

k82cn commented Jul 5, 2017

@luxas , let me check the status of "pluggable cloud providers" in 1.7; if it's ready, I think we can continue to merge this PR.

@k82cn
Copy link
Member

k82cn commented Jul 6, 2017

@luxas , as we slack yesterday, ccm is enough for kube-mesos; so I think we can merge this PR :).

@k82cn
Copy link
Member

k82cn commented Jul 6, 2017

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 6, 2017
@k8s-github-robot k8s-github-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 6, 2017
@gyliu513
Copy link
Contributor Author

@k82cn did not quite catch what do you mean, can you explain more?

So I need first run godep-restore.sh then godep-save.sh?

But when I run godep-restore.sh, it failed.

root@pc005:~/go/src/k8s.io/kubernetes# ./hack/godep-restore.sh
Starting to download all kubernetes godeps. This takes a while
godep: error downloading dep (vbom.ml/util/sortorder): unrecognized import path "vbom.ml/util/sortorder"
godep: Error downloading some deps. Aborting restore and check.
!!! Error in ./hack/godep-restore.sh:28
  Error in ./hack/godep-restore.sh:28. 'GOPATH=${GOPATH}:${KUBE_ROOT}/staging godep restore "$@"' exited with status 1
Call stack:
  1: ./hack/godep-restore.sh:28 main(...)
Exiting with status 1

@k82cn
Copy link
Member

k82cn commented Jul 10, 2017

Because of GFW ?

@sttts
Copy link
Contributor

sttts commented Jul 10, 2017

The deleted files are all bazel BUILD files. Do a hack/update-bazel.sh after godep-save.sh.

@gyliu513
Copy link
Contributor Author

Thanks @sttts and @k82cn

I think what @sttts proposed does make sense as my VM was located in US and there is no GFW. After I finished both ./hack/godep-save.sh and hack/update-godep-licenses.sh, then when I run hack/update-bazel.sh, it failed again as following, complaining cannot find vendor/github.com/docker/docker/project/CONTRIBUTORS.md as this file was already deleted when I run ./hack/godep-save.sh.

root@pc005:~/go/src/k8s.io/kubernetes# ./hack/update-bazel.sh
F0710 03:14:50.252162   22870 gazel.go:54] err walking vendor: stat vendor/github.com/docker/docker/project/CONTRIBUTORS.md: no such file or directory
goroutine 1 [running]:
gopkg.in/mikedanese/gazel.v17/vendor/github.com/golang/glog.stacks(0xc42052ea00, 0xc4202893b0, 0x97, 0xeb)
	/root/go/src/gopkg.in/mikedanese/gazel.v17/vendor/github.com/golang/glog/glog.go:766 +0xa7
gopkg.in/mikedanese/gazel.v17/vendor/github.com/golang/glog.(*loggingT).output(0x6c05a0, 0xc400000003, 0xc4202e3600, 0x6a2614, 0x8, 0x36, 0x0)
	/root/go/src/gopkg.in/mikedanese/gazel.v17/vendor/github.com/golang/glog/glog.go:717 +0x348
gopkg.in/mikedanese/gazel.v17/vendor/github.com/golang/glog.(*loggingT).printf(0x6c05a0, 0xc400000003, 0x5dd1ff, 0x16, 0xc4200f1f38, 0x1, 0x1)
	/root/go/src/gopkg.in/mikedanese/gazel.v17/vendor/github.com/golang/glog/glog.go:655 +0x14f
gopkg.in/mikedanese/gazel.v17/vendor/github.com/golang/glog.Fatalf(0x5dd1ff, 0x16, 0xc4200f1f38, 0x1, 0x1)
	/root/go/src/gopkg.in/mikedanese/gazel.v17/vendor/github.com/golang/glog/glog.go:1145 +0x67
main.main()
	/root/go/src/gopkg.in/mikedanese/gazel.v17/gazel/gazel.go:54 +0x2cd
!!! Error in ./hack/update-bazel.sh:40
  Error in ./hack/update-bazel.sh:40. '"${gazel}" -root="$(kube::realpath ${KUBE_ROOT})"' exited with status 255
Call stack:
  1: ./hack/update-bazel.sh:40 main(...)
Exiting with status 1

The steps I did was as following:

Step 1: Remove Godeps/ and vendor/, then run ./hack/godep-save.sh

root@pc005:~/go/src/k8s.io/kubernetes# ./hack/godep-save.sh
Don't forget to run hack/update-godep-licenses.sh if you added or removed a dependency!

Step 2: Run hack/update-godep-licenses.sh

root@pc005:~/go/src/k8s.io/kubernetes# hack/update-godep-licenses.sh

Step 3: Run hack/update-bazel.sh failed as above.

@sttts any comments for this? Thanks!

@sttts
Copy link
Contributor

sttts commented Jul 10, 2017

Known issue. Solution: delete vendor/github.com/docker/docker/project/

@sttts
Copy link
Contributor

sttts commented Jul 10, 2017

@gyliu513 can you test #48685?

@k8s-github-robot k8s-github-robot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 10, 2017
@gyliu513
Copy link
Contributor Author

/retest

@luxas
Copy link
Member

luxas commented Jul 10, 2017

@gyliu513 I think that worked 🎉
The test failures are unrelated AFAICS

@sttts
Copy link
Contributor

sttts commented Jul 10, 2017

Yes, tests are broken #48683 and federation times out or looses connection.

@mikedanese
Copy link
Member

Love the diff :)

@sttts
Copy link
Contributor

sttts commented Jul 10, 2017

Love the -68k lines of code.

@k82cn
Copy link
Member

k82cn commented Jul 10, 2017

+1 :).

@gyliu513
Copy link
Contributor Author

/retest

1 similar comment
@luxas
Copy link
Member

luxas commented Jul 11, 2017

/retest

k8s-github-robot pushed a commit that referenced this pull request Jul 11, 2017
Automatic merge from submit-queue

godep-save.sh: add workaround and more instructions

Fixes #48593, hit again in #47232 (comment).
@gyliu513
Copy link
Contributor Author

/retest

@gyliu513
Copy link
Contributor Author

ping @luxas and @mikedanese for lgtm and approve

@luxas
Copy link
Member

luxas commented Jul 12, 2017

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 12, 2017
@k8s-github-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: gyliu513, k82cn, luxas, mikedanese
We suggest the following additional approver: jregan

Assign the PR to them by writing /assign @jregan in a comment when ready.

Associated issue: 47205

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@luxas luxas added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 12, 2017
@luxas
Copy link
Member

luxas commented Jul 12, 2017

As everyone here is happy with this, I approved as well

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit a3430ad into kubernetes:master Jul 12, 2017
@gyliu513 gyliu513 deleted the remove-mesos-cp branch July 12, 2017 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove mesos cloud provider from Kubernetes