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

Create AnVIL deployments of Azul #4122

Closed
hannes-ucsc opened this issue Apr 20, 2022 · 2 comments
Closed

Create AnVIL deployments of Azul #4122

hannes-ucsc opened this issue Apr 20, 2022 · 2 comments
Assignees
Labels
demo [process] To be demonstrated at the end of the sprint demoed [process] Successfully demonstrated to team enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts orange [process] Done by the Azul team

Comments

@hannes-ucsc
Copy link
Member

hannes-ucsc commented Apr 20, 2022

We will need separate AWS accounts and Google Cloud projects so that we can track the cost separately from HCA.

@github-actions github-actions bot added the orange [process] Done by the Azul team label Apr 20, 2022
@theathorn theathorn added enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts labels Apr 21, 2022
@hannes-ucsc hannes-ucsc changed the title Create AnVIL deployments of Azul and Data Browser Create AnVIL deployments of Azul Aug 4, 2022
@hannes-ucsc
Copy link
Member Author

hannes-ucsc commented Aug 4, 2022

For demo, show anvildev and anvilbox. Explain the operational aspects of each.

@hannes-ucsc hannes-ucsc added the demo [process] To be demonstrated at the end of the sprint label Aug 4, 2022
@hannes-ucsc
Copy link
Member Author

Data Browser work tracked in DataBiosphere/data-browser#2756

achave11-ucsc added a commit that referenced this issue Sep 1, 2022
@hannes-ucsc hannes-ucsc reopened this Sep 14, 2022
achave11-ucsc pushed a commit that referenced this issue Sep 20, 2022
Only .shared & .gitlab were deployed. The .gitlab component was subsequently
destroyed again. The main purpose was to have a GitLab instance to test the
changes for #4188 on.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
demo [process] To be demonstrated at the end of the sprint demoed [process] Successfully demonstrated to team enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts orange [process] Done by the Azul team
Projects
None yet
Development

No branches or pull requests

3 participants