integrate remote scheduler

bolliger32 commented 5 years ago

[x] tests added / passed (checking but really haven't added any b/c don't know how we could add tests that require connection to a remote pod on kubernetes)
[x] docs reflect changes
[x] passes flake8 rhg_compute_tools tests docs
[x] entry in HISTORY.rst

Add remote scheduler deployment (part of dask_kubernetes 0.10)
Remove extraneous GCSFUSE_TOKENS env var no longer used in new worker images
Set library thread limits based on how many cpus are available for a single dask thread
Change formatting of the extra env_items passed to get_cluster to be a list rather than a list of dict-like name/value pairs

bolliger32 commented 5 years ago

not sure if/how we want to test a connection to a remote pod on kubernetes... I suppose we could set up tests that are meant to be run on gcs not on travis? This should be good to go other than tests.

delgadom commented 5 years ago

this sounds great. yeah so far I've only figured out how to do this with notebooks on a test deployment. have you given this a spin @bolliger32 ?

bolliger32 commented 5 years ago

yup! I have done it on the test2 deployment. We need updated versions of dask-kubernetes for this to work, so it won't work on the current compute.rhg deployment

bolliger32 commented 4 years ago

this should be to go to merge into master now, since it is actually the branch that is installed into the "staging" image

RhodiumGroup / rhg_compute_tools

integrate remote scheduler #55