...
- Prabhjot Singh Sethi shared an initial blueprint https://github.com/Prabhjot-Sethi/tf-operator/blob/master/specs/initial.md
- Prasad Miriyala need to have more elaborative requirements captured
- Prabhjot Singh Sethi upgrade process needs to be defined aligning with Operator-Lifecycle-manager
- Michael Henkel olm does not work well with Contrail requirements, add more complexities
- Prabhjot Singh Sethi ATS has already made tf-operator olm compliant
- Sanju Abraham olm compliance is not complex
- Michael Henkel operator should be capable of handling a patch release where it allows only a specific rollout instead of complete migration for all components
- there are dependencies between components that are ought to work together always and mostly handled together as a single project definitions
- Sachchidanand Vaidya we may endup requiring to define versions per project and manage mapping of which version works with which other versions of Tungsten Fabric
- Prabhjot Singh Sethi patching release should not apply to individual components, however can be considered for projects itself.
- Prabhjot Singh Sethi we need to setup a collaboration medium to have a fast track development on operator
- Sanju Abraham created a slack channel for tf-operator
operator-sdk for config (cloud-native)
...