Skip to content

node_id should be required for plugins that implement ControllerPublishVolume #121

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

Closed
saad-ali opened this issue Oct 18, 2017 · 4 comments
Closed
Milestone

Comments

@saad-ali
Copy link
Member

node_id in the GetNodeIDResponse is currently defined as optional:

  message Result {
    // The ID of the node which SHALL be used by CO in
    // `ControllerPublishVolume`. This is an OPTIONAL field. If unset,
    // the CO SHALL leave the `node_id` field unset in
    // `ControllerPublishVolume`.
    NodeID node_id = 1;
  }

If it is not returned, the CO is expected to not pass it on subsequent ControllerPublishVolume calls:

  // The ID of the node. This field is OPTIONAL. The CO SHALL set (or
  // clear) this field to match the `NodeID` returned by `GetNodeID`.
  // `GetNodeID` is allowed to omit `NodeID` from a successful `Result`;
  // in such cases the CO SHALL NOT specify this field.
  NodeID node_id = 3;

I don't think that controller node ID should be optional. If a plugin has PUBLISH_UNPUBLISH_VOLUME controller capability, then it should implement GetNodeId() and return a non-empty node ID. If a plugin doesn't require a call to connect storage to a node then it should not implement a PUBLISH_UNPUBLISH_VOLUME controller capability.

@saad-ali saad-ali added this to the v0.1 milestone Oct 18, 2017
@julian-hj
Copy link
Contributor

Makes sense to me.

@jieyu
Copy link
Member

jieyu commented Oct 26, 2017

SGTM. @saad-ali do you want to send a PR for this?

@akutz
Copy link
Contributor

akutz commented Oct 26, 2017

Hi @jieyu,

I'd propose we hold off on this as #117 changes NodeID to a simple string. I could make the doc change there?

@jieyu
Copy link
Member

jieyu commented Nov 9, 2017

xref #141

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

No branches or pull requests

4 participants