Replies: 3 comments 6 replies
-
|
Please list components that you consider as not required for a minimal install |
Beta Was this translation helpful? Give feedback.
-
|
@lappanna @ronenkat @roee88 Reviewing the main fybrik repository I would suggest that the following components be moved out of the main fybrik repository (and thus would not automatically be installed with fybrik):
@roee88 @ronenkat Removing these would mean that we would have to change the quick start, samples, and CI tests to pull from multiple repositories under the fybrik organization. Would it make sense to have the following repositories under the fybrik organization?
If so, the current fybrik repository becomes the fybrik control plane. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I think that this list goes beyond the original request but I might be wrong. The movement operator is always installed, even if not running the CRDs and code are there. It would be good to try separating it. Storage provisioning related CRDs and code might eventually be generalized as modules instead of being dependent on datashim. I suspect that this is too much work for now and would leave it as is for now. I don't see a problem with samples and connectors being in the repo to fulfill the original request. Cleanup there is required but it's not necessarily related to this discussion. |
Beta Was this translation helpful? Give feedback.
-
|
@lappanna The comments by @shlomitk1 raise a good point. Are we trying to minimize what is installed, and/or to minimize what code resides in the fybrik control plane repository? I was assuming both, but perhaps I was wrong. One of the advantages of separating the control plane code from the other optional components is that it decreases the footprint when doing security scans, etc. @roee88 Your thoughts? |
Beta Was this translation helpful? Give feedback.
-
|
@simanadler moving code out of the Fybrik repo also mean more difficulty in keeping things consistent, impact CI effectiveness, etc. |
Beta Was this translation helpful? Give feedback.
-
|
@ronenkat Regarding connectors I think we need to be consistent. I think we can take two possible approaches:
Different connectors can be deployed when desired. Need to include docs and tools for doing this.
I suggest we go with #1. Is everyone in agreement? @lappanna @roee88 @ronenkat @shlomitk1 @lappanna You are OK with Ronen's suggestion to leave datashim and samples in the fybrik repository? |
Beta Was this translation helpful? Give feedback.
-
|
@simanadler agree with your suggestion to go with option 1. I think that after #845 we will reach this option. |
Beta Was this translation helpful? Give feedback.
-
|
@simanadler Agree with option 1. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It will be good if fybrik can be installed minimally by default without all components that are not required. Or there can be an option to install minimal fybrik.
Beta Was this translation helpful? Give feedback.
All reactions