Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add support for the openebs plugin #99

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from

Conversation

blaisedias
Copy link
Collaborator

@blaisedias blaisedias commented Nov 12, 2024

the openebs plugin supercedes the mayastor
plugin.
However it is not a dropin replacement.
It is functional for all openebs IO engines,
and stem commands needs to further qualify
which IO engine the command is for.

At present invocations of the plugin in the
code base only exist for mayastor.

Refactor by adding functions

  • GetMayastorPluginCmd returns and exec cmds with the
    correct argument list
  • GetMayastorPluginCmdString - needed for invocation of
    support shell scripts using the plugin
    For the argument list is determined by name.
    The assumption is that if the plugin name is
    not kubectl-mayastor then it is the new plugin.

Refactor to replace most uses of GetPluginPath,
the exceptions being

  • upgrade
  • plugin version check commands

Also add support to create a config map for mayastor
diskpools.

Compatibilty with kubectl-mayastor is maintained

@blaisedias blaisedias force-pushed the support-new-plugins branch 2 times, most recently from b37dfe0 to e225ec8 Compare November 13, 2024 14:02
the openebs plugin supercedes the mayastor
plugin.
However it is not a dropin replacement.
It is functional for all openebs IO engines,
and stem commands needs to further qualify
which IO engine the command is for.

At present invocations of the plugin in the
code base only exist for mayastor.

Refactor by adding functions
 -  GetMayastorPluginCmd returns and exec cmds with the
    correct argument list
 - GetMayastorPluginCmdString - needed for invocation of
   support shell scripts using the plugin
For the argument list is determined by name.
The assumption is that if the plugin name is
not kubectl-mayastor then it is the new plugin.

Refactor to replace most uses of GetPluginPath,
the exceptions being
  - upgrade
  - plugin version check commands

Also add support to create a config map for mayastor
diskpools.

Compatibilty with kubectl-mayastor is maintained

Signed-off-by: Blaise Dias <[email protected]>
Add support for specifying the full path
to the kubectl plugin.
Use that in preference over plugin dir
+ configured kubectl plugin name.

This gives invoking scripts more flexibility.

Signed-off-by: Blaise Dias <[email protected]>
Replace use of GetMayastorPluginCmdString
with GetMayastorPluginCmd().String()

Signed-off-by: Blaise Dias <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants