search

NASA-Openscapes / 2i2cAccessPolicies

Policies for NASA Openscapes 2i2c Access
0 stars 0 forks source link

AWS Usage report #13

Closed ateucher closed 2 months ago

ateucher commented 4 months ago

Hi @jules32, I think this is in a good place for an initial review. You probably won't be able to run it as-is, as there are some credentials you need to set up (and I haven't written up the instructions for that yet).

I also haven't set up the automation with GitHub actions, but have run it several times by setting the year_month parameter and that is working well.

I haven't written too much contextual explanataion for the figures yet, but wanted to get your opinion at this point, then I can flesh it out.

I've attached three samples in the comment below - if you can have a look at those and let me know what you think is missing, I can tweak!

ateucher commented 4 months ago

I've attached three versions of the report here - for April, May, and June:

aws-usage-report_2024-04.pdf aws-usage-report_2024-05.pdf aws-usage-report_2024-06.pdf

jules32 commented 4 months ago

Thanks @ateucher , this is great progress! I made a few starter comments but please continue with the contextual explanation; this is definitely on the right track!

On the next round of reviews I can think more about how to help draw out the current month details (since page 1 is currently constant on each month report).

ateucher commented 4 months ago

Thanks @jules32, great suggestions! Re the first page being constant - I think it is different for each report? My intention with the first three figures was to have the reporting month compared to the previous 5 months, and then for the rest of it dive more deeply into the current month being reported on.

jules32 commented 4 months ago

Sounds good Andy - I was thinking about the Introduction Page being largely constant at this point. We can think about that more as you write the contextual text and maybe we end up shifting some intro text?

jules32 commented 3 months ago

Thanks @ateucher ! This looks good and I'll have a deeper look with feedback while you're away.

One question: in the "Total size of user home directories by access team and Hub namespace" figure, what does the Yellow N/A mean? (and thinking we should number figures, I'll include that in my review).

ateucher commented 3 months ago

Thanks for looking again @jules32! The N/A means that there is no team associated with the workshop Hub space, since we use the shared password approach for that Hub.

jules32 commented 3 months ago

Hi Andy! I just reviewed, making some small suggestions and also this bigger question about how to include this idea of human annotation.

I also just shared during our 2i2cAccessPolicy Hackday, and Yuvi, Eli, and Luis are excited. People asked whether this be more real-time (daily? or weekly, could we email users? and what info would change? still a PDF?) People are definitely interested in how this could be useful for other Hubs too. Jim asked how this could be used to communicate to funders as well as users, which is a good question. Communication as the #1 goal here.

Anyways, a lot of interest. I think getting the automation setup for these PDFs monthly first is still best, and then we can fine-tune and add features from there.

Awesome work!

ateucher commented 2 months ago

Related: https://github.com/2i2c-org/infrastructure/issues/4453