-
Notifications
You must be signed in to change notification settings - Fork 88
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
Add hail backend - intitial status check #3480
Conversation
app = init_web_app() | ||
web.run_app( | ||
app, | ||
host='0.0.0.0', # nosec |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like a backend service web app without authentication support. It should not be accessible from external.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct. The hail backend service will only be accessible via an internal, unauthenticated kubernetes service, so that only seqr can access it. Actually setting up the deployment is out of scope of this PR, but you can see the kubernetes yaml that I used to get this working in a test environment here: https://github.com/broadinstitute/seqr/blob/62084009dd60a35eef1c85608ad0c8a3e2a90cf8/deploy/kubectl_helpers/utils/hail-search.yaml
This adds the directory and basic scaffolding for adding the hail search app to seqr. Currently, all this adds is a status endpoint and unit tests. The hail search app uses aiohttp, as this library comes built in on the hail docker image we are using, and is therefore the most lightweight and best supported approach.
Future work will be needed to actually release docker images for the hail search backend, but I wanted to wait until there was a bit more functionality integrated in before adding that