consider separation of providers

mmm / infrastructure-gym

Train Reinforcement-Learning agents to understand and control cloud infrastructure

Apache License 2.0

3 stars 1 forks source link

consider separation of providers #30

Closed mmm closed 5 years ago

mmm commented 5 years ago

might make sense to separate out repos for a k8s-gym from a cloud-gym or do-gym/gcp-gym rather than dealing with multiple levels within the same project.

Pros:

Let the APIs evolve separately (k8s version might be better as an actual operator?)
Simpler to explain to folks

Cons:

Fewer degrees of freedom. Can't tweak both workload and the topology of the underlying container scheduler from within the same model

mmm commented 5 years ago

actually makes sense to have a gym_terraform with envs that're provider-specific. e.g., SimpleK8sWebApp.

That uses terraform_graph tools to build it up, but those're generic across provider... just the choice of layers used in each env are provider-specific.