-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add HUIT cost allocation tags #4
Conversation
launch_cluster/launch.py
Outdated
@@ -71,6 +71,9 @@ def launch_manager(config): | |||
{"Key": "Owner", "Value": config.server_owner}, | |||
{"Key": "Creator", "Value": config.server_owner}, | |||
{"Key": "Jupyter Cluster", "Value": config.cluster_name}, | |||
{"Key": "platform", "Value": "linux"}, | |||
{"Key": "environment", "Value": "production"}, |
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.
Same comment with respect to the spawner.py
(optional param with a default).
@joshuagetega Looks good! My only comment is that we've hard-coded the environment tag to "production" which would preclude us from allocating costs to any "development" or "sandbox" clusters based on the tag. This also applies to the changes you made to the volume/snapshot tagging in our gitlab repo. I don't see this as a blocker, just something that we might want to address for maximum flexibility down the line. |
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.
See prior comments.
Tag manager and workers with 'platform', 'product', and 'environment' tags. These are required by HUIT, as specified in https://confluence.huit.harvard.edu/display/CLA/Cloud+Resource+Tagging#CloudResourceTagging-4.5%22platform%22Tag, for cost allocation.
I have parameterized the tags and provided defaults. Merging ... |
Tag manager and workers with 'platform', 'product', and 'environment' tags. These are required by HUIT, as specified here, for cost allocation. This change has been tested - see the tags of the manager and worker instance in the 'test-tagging' cluster. (The tagging of volumes and snapshots is
not implemented here but in a separate PR in our gitlab jupyterhub repo). Let me know if you have any thoughts. Otherwise a thumbs up review is good enough here :).