Skip to content

[skip ci] Add Cloud deployment documentation#1611

Closed
mrocklin wants to merge 3 commits intodask:masterfrom
mrocklin:docs-cloud
Closed

[skip ci] Add Cloud deployment documentation#1611
mrocklin wants to merge 3 commits intodask:masterfrom
mrocklin:docs-cloud

Conversation

@mrocklin
Copy link
Copy Markdown
Member

@mrocklin mrocklin commented Dec 4, 2017

This depends on a number of PRs currently in-flight

Comment thread docs/source/setup.rst
~~~~~~~~~~~~~

First you will need to set up an account with one of Google, Amazon, or
Microsoft Azure, and launch a cluster running Kubernetes. This is
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although it isn't "Cloud", I found minikube helpful for testing things out locally before trying on Google. Both helm install stable/dask-distributed and helm install stable/spark worked for me locally.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool. I wasn't aware of minikube. Should we mention here in these docs or is this just an FYI?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure... I think a parenthetical "or minikube for local testing" may be worthwhile to ease the burden of entry for people looking to test things out. It seems to be the officially blessed version of "local kubernetes", so I don't see much downside.

Comment thread docs/source/setup.rst
Conda packages are installed before pip packages. These values are appended
directly to the ``conda install`` and ``pip install`` commands and so you can
also include flags, such as specifying conda channels.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's another "Kubernetes" section on line 305 below, not sure if it should be removed or merged with this.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this and the dask-kubernetes section probably require some conversation to see what we want to do going forward

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that the decision here probably depends on how smooth we can make the Helm solution. Right now I don't think it's sufficiently smooth, but perhaps we can get it there?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The section I'm talking about is below the Google Cloud section, and looks like it lists some previous (and possibly outdated?) work.

@mrocklin
Copy link
Copy Markdown
Member Author

mrocklin commented Dec 4, 2017

Current work on dask helm chart: helm/charts#2914

Comment thread docs/source/setup.rst
might want to conda-install XArray and Arrow::

helm upgrade iced-mule stable/dask \
--set worker.pipPackages="gcsfs dask-ml" \
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gcsfs is now on conda-forge too (here and above)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My intent was to show off both. Personally I use pip for gcsfs just for speed. Conda can take a while.

@martindurant
Copy link
Copy Markdown
Member

cc @danielfrg

@mrocklin mrocklin closed this Feb 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants