search

openstack-k8s-operators / dev-docs

Documentation
9 stars 25 forks source link

[spec]Grouping nodes #42

Closed gibizer closed 1 year ago

gibizer commented 1 year ago

Depends-on: #41

dprince commented 1 year ago

@gibizer This came across my path today and I was a bit confused why it exists. We have at least 3 or 4 google docs discussing architectural options for Dataplane services. Is this meant to be a consolidation of the Google docs perhaps and you only want comments here now?

gibizer commented 1 year ago

@gibizer This came across my path today and I was a bit confused why it exists. We have at least 3 or 4 google docs discussing architectural options for Dataplane services. Is this meant to be a consolidation of the Google docs perhaps and you only want comments here now?

I'm trying to follow the pattern started in https://github.com/openstack-k8s-operators/docs/pull/31. Where after the initial discussion started to settle in the google docs the actual proposal is cleaned up and moved to this repo. This is intentionally in Draft state as I just finished writing this up as a cleanup of the google doc where the question / comments seems to be settled.

I'm traveling this week. So this and #41 will remain in Draft state at least until next week. If you have comments feel free to provide it here or in the google docs (whichever is more convenient for you) in the meantime. I will sync things up next week and we can also chat about the way forward.

gibizer commented 1 year ago

/hold we need to land #41 first

gibizer commented 1 year ago

This is not applicable any more based on the decision that sevice-operators are should not run or trigger any ansible execution, and instead DataPlaneService CRs will do that. Such CRs forces to use DataPlaneRole for any kind of compute grouping. We might want to revisit the resulting Role explosion later.