Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

If this message is too spammy, please complain to ixdy.

Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

If this message is too spammy, please complain to ixdy.

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.

@ohtake is also a author of those commits

Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

If this message is too spammy, please complain to ixdy.

ok to test

@ohtake needs to sign the CLA.

cc/ @ashw7n

@davidopp I have just singned the CLA. Could you re-verify the CLA?

Adding label:do-not-merge because PR changes docs prohibited to auto merge
See http://kubernetes.github.io/docs/editdocs/ for information about editting docs

I don't think the CLA bot ever works for PRs with multiple authors.

We're still trying to get 1.2 out the door and have a couple other new cloudproviders to review, so this will need to wait for a little while.

It would also be useful to have some people using K8s on Openstack to review. I suggest posting to kubernetes-dev to plead for reviewers.

I've created post on kubernetes-der regarding to openstack-provider:
https://groups.google.com/forum/#!topic/kubernetes-dev/t1-0zG3Lmeg

I hope someone will be interested.

This PR and documentation kubernetes/website#74 ready for review
PTAL

@quinton-hoole Looks like the bot didn't like you :)

@elsonrodriguez That only because commits were added after I gave the LGTM. So bot is being good :-) New commits also LGTM. Re-adding label.

@elsonrodriguez Oh, I see what you mean, the bot reassigned it. That was due to a bug in github a week or so ago. I've manually re-assigned back to myself.

@zreigz @elsonrodriguez it is not mandatory, but nice to have:

1. requirements.txt file with the desired python-'project'client versions (to install it easily with pip install -r requirements.txt command/update the docs with this as well;
2. Replace "OpenStack" with "OpenStack-Heat" on https://github.com/FujitsuEnablingSoftwareTechnologyGmbH/kubernetes/blob/openstack-provider/cluster/get-kube.sh#L41 as we are expecting other different OpenStack-related providers.
3. Replace "minion" with "node", i.e. - https://github.com/FujitsuEnablingSoftwareTechnologyGmbH/kubernetes.github.io/blob/openstack-provider-doc/docs/getting-started-guides/openstack-heat.md#sshing-to-your-nodes

Everything else LGTM. @quinton-hoole, please, take a look, possibly you have some other/extra suggestions.

Thanks for suggestions. Regarding to:

1. It sounds as a good enhancement for the future. For sure we will do it.
2. Done
3. minion is used as user for instances. It is not only matter of documentation.
   https://github.com/FujitsuEnablingSoftwareTechnologyGmbH/kubernetes/blob/openstack-provider/cluster/openstack-heat/kubernetes-heat/fragments/kube-user.yaml#L4

GCE e2e build/test passed for commit 892c2ab.

• Build Log
• Test Artifacts
• Internal Jenkins Results

@quinton-hoole Another commit snuck in, could you take another look?

@zreigz
3) please, change that. Don't let people be confused.

@zreigz @idvoretskyi That is a minor cosmetic issue. Almost every other kube-up provider still makes a reference to minions in their usage/code, along with the salt manifests.

I do think the names could be normalized, but that is squarely in the territory of a future PR.

@elsonrodriguez @zreigz agree.
LGTM

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

GCE e2e build/test passed for commit 892c2ab.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Automatic merge from submit-queue

@zreigz
@quinton-hoole

Would you provide an update on the status + ETA for the documentation for this feature as well as add any PRs as they are created?

Not Started / In Progress / In Review / Done

Expected Merge Time:

Thanks
@pwittrock

@pwittrock
@zreigz
@quinton-hoole

Documentation is here: http://kubernetes.io/docs/getting-started-guides/openstack-heat/

And I have a pending PR to fix issues here: kubernetes/website#534

Any review/testing would be appreciated.

@elsonrodriguez Is this already available or will it be available in v1.3? The docs you linked are live, so it may be confusing to users if the feature is not available in the current release.

@pwittrock 1.3 only, I can put a warning regarding the curl | bash pattern, and say that only 1.3 releases will work for the tar pattern.