Skip to content
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

Managed-access pilot site for HCA #5740

Open
bvizzier-ucsc opened this issue Nov 30, 2023 · 22 comments
Open

Managed-access pilot site for HCA #5740

bvizzier-ucsc opened this issue Nov 30, 2023 · 22 comments
Assignees
Labels
epic [type] Issue consists of multiple smaller issues orange [process] Done by the Azul team

Comments

@bvizzier-ucsc
Copy link

This ticket is to create and stand up the HCA Manage Access pilot.

This pilot will have a small number (3 planned) managed access datasets and a couple of open access datasets to be able to demonstrate the difference between the two dataset types.

This will require work by both Data Browser and Azul teams.

@bvizzier-ucsc bvizzier-ucsc added the epic [type] Issue consists of multiple smaller issues label Nov 30, 2023
@github-actions github-actions bot added the orange [process] Done by the Azul team label Nov 30, 2023
@dsotirho-ucsc dsotirho-ucsc changed the title Stand up HCA Data Explorer Managed Access Pilot site. Stand up HCA Data Explorer Managed Access Pilot site Nov 30, 2023
@dsotirho-ucsc
Copy link
Contributor

Assignee to fill epic with child issues.

@hannes-ucsc
Copy link
Member

@bvizzier-ucsc, since the Azul team will be taking over the management of the HCA pilot site, and would be doing so in the HCA prod account, should we also take over management of the current HCA production site of the explorer? This would enable us satisfy the compliance constraint of CC not having access to deployment zones that contain MA data. If, for the pilot, we don't need to satisfy that constraint, we could have CC set up the pilot site and we take over both sites at a later time.

@hannes-ucsc
Copy link
Member

Note to self: Terra needs to allow-list OAuth client ID for the platform-hca-prod GCP project.

@hannes-ucsc hannes-ucsc removed their assignment Dec 5, 2023
@bvizzier-ucsc
Copy link
Author

bvizzier-ucsc commented Dec 5, 2023

Assignee will discuss with the parties having shared access to the platform-hca-prod GCP project. Once the managed access site is up and operational, ownership of the project will be turned over to the Azul team due to security requirements. At that time, the Azul team will be responsible for updating both the open access and managed access content.

Assignee will update this once agreement is obtained and set this issue back to "triage."

@bvizzier-ucsc
Copy link
Author

bvizzier-ucsc commented Dec 5, 2023

I talked with Dave (CC). He offered to setup the managed access site and help configure it. When that is done and the Pilot site is ready to go live, then the permissions will be set to remove CC and making the Azul team responsible for the management of the site per current processes and procedures.

@achave11-ucsc
Copy link
Member

Assignee to followup with CC to check if there's any followup tickets that need to be created or if DataBiosphere/data-browser#3802 is that ticket.

@bvizzier-ucsc
Copy link
Author

@NoopDog To confirm... The expectation is that CC will setup the environments as described in #5740 (comment)

@dsotirho-ucsc
Copy link
Contributor

Assignee to create child issues for any necessary Azul work.

@NoopDog
Copy link
Contributor

NoopDog commented Dec 7, 2023

Got it, thx. We will create the environment.

@hannes-ucsc hannes-ucsc changed the title Stand up HCA Data Explorer Managed Access Pilot site Stand up managed-access pilot site for HCA Dec 12, 2023
@hannes-ucsc
Copy link
Member

Done with creating children.

@hannes-ucsc hannes-ucsc removed their assignment Dec 13, 2023
@hannes-ucsc hannes-ucsc changed the title Stand up managed-access pilot site for HCA Managed-access pilot site for HCA Mar 28, 2024
@hannes-ucsc
Copy link
Member

The pilot site exists. I'm not sure #6131 needs to be part of this. If we can remove it, this epic can be closed. Triaging to discuss.

@achave11-ucsc
Copy link
Member

@hannes-ucsc: "Assignee to check with HCA leadership whether we can scrap the pilot site and when. Assignee to also decide if #6131 also needs to be part of this epic. If not we can scrap the pilot site and implement #6131 with high priority but not as part of this epic, in which case we can close the epic after scrapping the pilot site."

@bvizzier-ucsc
Copy link
Author

John Randell doesn't know of anyone who is using the ma-pilot site. He has asked me to check with Ida, Travis, and Jonathan. Please see this Slack message.

No responses at the time of this update.

@bvizzier-ucsc
Copy link
Author

We can take the HCA MA-Pilot site down. It is currently not in use.

@bvizzier-ucsc
Copy link
Author

Change in plans. They want to keep the site up until they can create some training materials.

I'll track this.

@hannes-ucsc
Copy link
Member

This is blocking us from moving forward with #6348, or at least the main child of that epic, #6344.

@hannes-ucsc
Copy link
Member

I would like to set a deadline of 1 week from today. That should be sufficient time to take the screenshots for the training material.

@bvizzier-ucsc
Copy link
Author

We are done with the managed access pilot site and are in the process of updating the production site.

@bvizzier-ucsc bvizzier-ucsc removed their assignment Aug 29, 2024
@NoopDog
Copy link
Contributor

NoopDog commented Aug 29, 2024 via email

@dsotirho-ucsc
Copy link
Contributor

@bvizzier-ucsc: "Next steps are to take down the pilot site."

@bvizzier-ucsc
Copy link
Author

@NoopDog, Please destroy the HCA MA Pilot site at your convenience.

@NoopDog
Copy link
Contributor

NoopDog commented Aug 30, 2024

Will do. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic [type] Issue consists of multiple smaller issues orange [process] Done by the Azul team
Projects
None yet
Development

No branches or pull requests

5 participants