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
Getting started guide for Mesos on Google Cloud Platform #5442
Getting started guide for Mesos on Google Cloud Platform #5442
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project, in which case you'll need to sign a Contributor License Agreement (CLA) at https://cla.developers.google.com/. If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check the information on your CLA or see this help article on setting the email on your git commits. Once you've done that, please reply here to let us know. If you signed the CLA as a corporation, please let us know the company's name. |
I'm covered by the corporate CLA signed by Mesosphere. |
Over the coming weeks we'd like to move some of the components of Kubernetes-Mesos upstream, simplifying this guide as that work progresses. |
Does upstream mean mesos repo or kubernetes repo, or some bits to each? |
@erictune I meant to the Kubernetes repo. @jdef and @vladimirvivien have done a bunch of work recently to migrate from depending on a shared library via cgo to a pure Go Mesos interface, which should make the pieces much more amenable to inclusion here. |
@ConnorDoyle huge +1 @rrati - inbound. |
Just got news we have to re-sign the CLA. Will report back when it's fixed. |
Who would be a good reviewer for this? |
I'll take it. |
This is good news. I'd like to review it as well. |
|
||
This tutorial will walk you through setting up Kubernetes on a Mesos cluster on [Google Cloud Plaform][4]. | ||
It provides a step by step walk through of adding Kubernetes to a Mesos cluster and running the classic GuestBook demo application. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you call out in the text what version of Kubernetes is being installed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do
On Mon, Mar 16, 2015 at 3:39 PM, Eric Tune notifications@github.com wrote:
In docs/getting-started-guides/mesos.md
#5442 (comment)
:@@ -0,0 +1,287 @@
+## Getting started with Kubernetes on Mesos
+
+
+
+Mesos allows dynamic sharing of cluster resources between Kubernetes and other first-class Mesos frameworks such as [Hadoop][1], [Spark][2], and [Chronos][3].
+Mesos ensures applications running on your cluster are isolated and that resources are allocated fairly.
+
+Running Kubernetes on Mesos allows you to easily move Kubernetes workloads from one cloud provider to another to your own physical datacenter.
+
+This tutorial will walk you through setting up Kubernetes on a Mesos cluster on [Google Cloud Plaform][4].
+It provides a step by step walk through of adding Kubernetes to a Mesos cluster and running the classic GuestBook demo application.
+Can you call out in the text what version of Kubernetes is being installed.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/5442/files#r26519939
.
James DeFelice
585.241.9488 (voice)
650.649.6071 (fax)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. This is the only issue blocking merge, I think.
Oh, and could you squash. |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
4d8f1b0
to
00b34af
Compare
CLAs look good, thanks! |
@erictune: squashed. |
00b34af
to
a62c4e6
Compare
``` | ||
It's also a good idea to ensure your etcd instance is reachable by testing it | ||
```bash | ||
curl -L http://$(hostname -i):4001/v2/keys/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any reason why $(hostname -i)
is used here instead of $servicehost
? I think it should be consistent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
4036c91
to
d916c9f
Compare
I haven't forgotten this. Just a little backed up with other work. Will try to loop back tomorrow. |
-A KUBE-PORTALS-HOST -d 10.10.10.149/32 -p tcp -m comment --comment frontend -m tcp --dport 9998 -j DNAT --to-destination 10.22.183.23:36336 | ||
-A KUBE-PORTALS-HOST -d 10.22.183.23/32 -p tcp -m comment --comment frontend -m tcp --dport 9998 -j DNAT --to-destination 10.22.183.23:36336 | ||
|
||
$ # open up access to the internal port for the frontend service portal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
extraneous $
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
<!-- TODO: Update, clean up. --> | ||
|
||
Mesos allows dynamic sharing of cluster resources between Kubernetes and other first-class Mesos frameworks such as [Hadoop][1], [Spark][2], and [Chronos][3]. | ||
Mesos ensures applications running on your cluster are isolated and that resources are allocated fairly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe clarify to "Mesos ensures applications from different frameworks running on your cluster..."
I think it's fine to leave as-is, but since Kubernetes also provides isolation and resource allocation, it might be good to clarify what kind of isolation/resource allocation you're talking about.
I made some minor comments. I don't think any of them are super-critical, so if you'd like us to just merge what you already have, let us know. |
521f977
to
38b0fe9
Compare
Made the changes. This is ready to be merged now. Thanks! |
38b0fe9
to
6872a73
Compare
CLAs look good, thanks! |
Sorry to nitpick, but I think it's still not clear how to get to the Mesos web UI (you mention it twice; see my earlier line comments). I think the instructions you want are something like "point your web browser to the value that is in ${mesos_master}" perhaps mentioning also that this only works if you set up the VPN properly. If you actually do explain how to get to the Mesos web UI and I missed it, please let me know (and my apologies). |
We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm. |
No worries, appreciate the attention to detail. I added an explanation for how to get to the GUI. |
LGTM Thanks! |
Getting started guide for Mesos on Google Cloud Platform
Thanks!
|
Adds instructions for building and running Kubernetes on a Mesos cluster via the Kubernetes-Mesos integration project.