-
Notifications
You must be signed in to change notification settings - Fork 7
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
Containerized release and use of LANL and Microsoft. #112
Labels
enhancement
New feature or request
Comments
Dave, on your mark. Get set. Go.
Do you need anything from me?
|
Yes, are the software dependencies up-to-date on the README.md? |
Yes, they are up-to-date, but there is no need for Arivata. Okay?
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our current plan in order to take advantage of all resources given to us is to auto-build #34 three containers (I think, need confirmation):
This means that for a given set of resources the web server will submit a job, which will spin up a container of the job container type, both will interact with Solr.
Solr meanwhile will have to be configured to be cross datacenter. #101
We will build two distant readers to start West and East, later we could add an India cluster. reader-ws will be deployed to Jetstream in East and Microsoft in West, reader-j will run on Slurm, Jetstream in East and LANL in West, Solr will run on Jetstream in East and Microsoft in West.
This means that for me, what I should do is use the future West implementation as the test bed for containerization. Maybe starting with a simple https://azure.microsoft.com/en-us/resources/templates/slurm/ Slurm implementation in the West.
The text was updated successfully, but these errors were encountered: