w261: Create cloud resources for users #713
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When a user pod starts, we ensure the following GCP resources: 1. A GCS bucket 2. A Service Account with admin rights on the bucket 3. A Service Account Key for the Service Account We then populate two environment variables in the spawned pod 1. SPARK_GCS_BUCKET - name of GCS bucket for this user 2. SPARK_GCS_KEY - JSON Private key for service account This is all done through a custom Spawner that inherits from KubeSpawner. This should operate at the level of a 'Spark+GCS on GCP', so nothing too UCB specific. In addition, there's a custom role created in the ucb-datahub-2018 project - projects/ucb-datahub-2018/roles/w261_hub_resource_creator that has the appropriate permissions needed by the *hub* to create the resources it needs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a user pod starts, we ensure the following GCP
resources:
We then populate two environment variables in the
spawned pod
This is all done through a custom Spawner that inherits
from KubeSpawner. This should operate at the level of
a 'Spark+GCS on GCP', so nothing too UCB specific.
In addition, there's a custom role created in the
ucb-datahub-2018 project - projects/ucb-datahub-2018/roles/w261_hub_resource_creator
that has the appropriate permissions needed by the hub
to create the resources it needs.