You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NASA VEDA has two sets of users accessing the JupyterHub. Permanent trusted users and temporary users participating in trainings/workshops. It would be really helpful to enable resource tagging to track usage by these groups and have a general idea on costs associated with operating a hub.
Proposal
This would likely look something like adding a tag that allowed resource tracking by allowed organizations . Additionally it may be good to have another tag for overall 2i2c resources required for operating the hub.
@freitagb we can probably add tags for 2i2c managed resources. However, splitting this out by 'per-org' or whatever is going to be difficult, as JupyterHub spawns kubernetes resources, based on users, and cost allocation tags are AWS resources separate from kubernetes resources. Also, multiple users may end up on the same node, and nodes are the primary unit of cost allocation on AWS. However, prometheus may be used to figure out usage if needed, after the fact.
If you'd like, we can work on adding a 'managed-by': '2i2c' or similar tag to everything though.
@yuvipanda thanks for the clarification. Let's start with the managed-by tag you recommend and we can think on ways to get more detailed information in the future.
Next Actions
Add 'managed-by': '2i2c' tag to resources
@yuvipanda is this something you are able to take on, or provide pointers for someone else to do? Assigning to you for now, but feel free to re-assign.
The text was updated successfully, but these errors were encountered:
Copying over from 2i2c-org/infrastructure#2737
From @freitagb in above issue:
Context
NASA VEDA has two sets of users accessing the JupyterHub. Permanent trusted users and temporary users participating in trainings/workshops. It would be really helpful to enable resource tagging to track usage by these groups and have a general idea on costs associated with operating a hub.
Proposal
This would likely look something like adding a tag that allowed resource tracking by allowed organizations . Additionally it may be good to have another tag for overall 2i2c resources required for operating the hub.
Updates and actions
No response
Reply from @yuvipanda :
@freitagb we can probably add tags for 2i2c managed resources. However, splitting this out by 'per-org' or whatever is going to be difficult, as JupyterHub spawns kubernetes resources, based on users, and cost allocation tags are AWS resources separate from kubernetes resources. Also, multiple users may end up on the same node, and nodes are the primary unit of cost allocation on AWS. However, prometheus may be used to figure out usage if needed, after the fact.
If you'd like, we can work on adding a 'managed-by': '2i2c' or similar tag to everything though.
From @freitagb :
@yuvipanda thanks for the clarification. Let's start with the managed-by tag you recommend and we can think on ways to get more detailed information in the future.
Next Actions
'managed-by': '2i2c'
tag to resources@yuvipanda is this something you are able to take on, or provide pointers for someone else to do? Assigning to you for now, but feel free to re-assign.
The text was updated successfully, but these errors were encountered: