Open AndreyMarchuk opened 5 years ago
Created following POC:
mu batch deploy
Here is the code for items 2 and 3: https://github.com/stelligent/mu/compare/develop...AndreyMarchuk:feature/batch-job?expand=1
Now the question is: would it be better handled as Service.Provider = batch
?
I think having aService.Provider = batch
would be the most ideal as it avoids a lot of duplication. how plausible would it be to implement?
POC for Service.Provider = batch
Environment.Provider = batch
https://github.com/stelligent/mu/compare/develop...AndreyMarchuk:batch-as-service-provider?expand=1
looking good! curious, what is this for?
ProviderOverride string `yaml:"provider,omitempty"`
Currently mu tries to fetch the Env Stack to get the Provider from the environment. ProviderOverride allows to specify Provider on Service level so that Env Stack does not have to exist. Batch job definition registration does not depend on environment.
service:
name: my-batch-job
# deployed as AWS Batch job
provider: batch
It also forces service to be treated as batch even if user mistakenly deploys the service onto non-batch environment (i.e. ecs, ec2 etc)
Example of Batch compute environment, Batch queue and Batch job definitions: