-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comments
Assignee to fill epic with child issues. |
@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 |
Note to self: Terra needs to allow-list OAuth client ID for the platform-hca-prod GCP project. |
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." |
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. |
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. |
@NoopDog To confirm... The expectation is that CC will setup the environments as described in #5740 (comment) |
Assignee to create child issues for any necessary Azul work. |
Got it, thx. We will create the environment. |
Done with creating children. |
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. |
@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." |
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. |
We can take the HCA MA-Pilot site down. It is currently not in use. |
Change in plans. They want to keep the site up until they can create some training materials. I'll track this. |
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. |
We are done with the managed access pilot site and are in the process of updating the production site. |
Nice!
…On Thu, Aug 29, 2024 at 11:41 AM Ben Vizzier ***@***.***> wrote:
We are done with the managed access pilot site and are in the process of
updating the production site.
—
Reply to this email directly, view it on GitHub
<#5740 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYW6ENXWGZ6ZYKF66CXH4TZT5TMRAVCNFSM6AAAAABJRETTFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJYGYYDENRWGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Dave Rogers
Partner, Clever Canary
M: 646 286 5371
http://clevercanary.com
@clevercanary
@_DaveRogers
https://www.linkedin.com/pub/dave-rogers/0/90/92
|
@bvizzier-ucsc: "Next steps are to take down the pilot site." |
@NoopDog, Please destroy the HCA MA Pilot site at your convenience. |
Will do. Thanks. |
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.
The text was updated successfully, but these errors were encountered: