You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are in the process of transitioning our load_data workflow towards an integration of AWS Batch in order to speed up file computation and archival by means of parallelization. This Epic will begin this transition process.
Next Steps
The first step will be to flesh out the Batch infrastructure, which will be broken up as follows:
Develop a batch.tf terraform file to be able to declare Batch compute resources
Open questions: what type of compute instances do we want to use?
Work through the container based complexities of porting scpca_portal to the intended instances
Uploading containers to ecr, using fargate or ec2 with ecs, etc
Make sure that batch.tf is referenced inside of our start up scripts when we spin up our architecture in local/staging/prod environments
Analyze other infrastructure dependencies which will relate to Batch
A later epic will handle the actual implementation of Batch inside of the load_data command.
The text was updated successfully, but these errors were encountered:
Context
We are in the process of transitioning our
load_data
workflow towards an integration of AWS Batch in order to speed up file computation and archival by means of parallelization. This Epic will begin this transition process.Next Steps
The first step will be to flesh out the Batch infrastructure, which will be broken up as follows:
batch.tf
terraform file to be able to declare Batch compute resourcesscpca_portal
to the intended instancesbatch.tf
is referenced inside of our start up scripts when we spin up our architecture in local/staging/prod environmentsA later epic will handle the actual implementation of Batch inside of the
load_data
command.The text was updated successfully, but these errors were encountered: