search

openflighthpc / flight-cloud

Cloud orchestration tool
Eclipse Public License 2.0
3 stars 2 forks source link

Merge the `Models::Cluster` and `Models::Domain` objects #288

Closed WilliamMcCumstie closed 5 years ago

WilliamMcCumstie commented 5 years ago

The original Models::Cluster stored configurations used to generate deployment stack names sent to the providers. The Models::Domain however represented the deployment that corresponds to the cluster level.

Their is no need to make a distinction between the two models anymore, and they should be merged into one.

WilliamMcCumstie commented 5 years ago

This issue is temporarily on hold. The concept of the current_cluster is not well suited to Cloudware. This is because the "current_cluster" must exist before it can be used, but it may or may not have a template.

Instead, a new Models::Profile with a "current_profile" should be created. That way the Models::Cluster does not exist until it has a template (even if its empty). This will make the Models::Cluster behave more like a Models::Node.

WilliamMcCumstie commented 5 years ago

The Cluster and Domain are no longer going to be merged. Instead the Cluster represents the core configuration ('provider', 'region', etc...) where the Domain is a deployment. The Cluster is reasonable synopsis with the Profile concept mentioned above.