-
Notifications
You must be signed in to change notification settings - Fork 49
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
Separate NVMe initiator host management from target management #148
Labels
Comments
Additional notes @matteotenca wrote:
My reply:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@matteotenca writes in #145:
In my very humble opinion, the exporting/unexporting process should be handled apart from the process of choosing allowed hosts for an export. I don't know if it is mandatory to specify the allowed hosts upon exporting, though.
I say this because the unexport function is quite tricky just because it has to manage the allowed host list too: when more than one host is present, the function behaviour switches to a bare handling of the access list, since it cannot unexport until the allowed hosts list is empty.
My opinion is the -e and -x should just trigger exporting and unexporting, and that other two switches should be added to choose allowed hosts for an exported target, like this fictional example:
The text was updated successfully, but these errors were encountered: