-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add static provisioning example to PowerFlex #321
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reviewed this. There are a couple of minor edits.
d142d1f
to
038b0ad
Compare
When I was attempting to static-provision from PowerFlex recently, I had trouble getting the volume's ID. To get it, I used scli on the PowerFlex array to query the volume by its name. Using the UI is a much more convenient way to obtain the ID and is certainly more in line with the PowerStore method of getting the volume. However, the instructions are unclear to me:
I'm looking at the PowerFlex UI right now and I don't see any clear way to filter based on the volume. I think clearer directions on how to do this filtering would be helpful. |
Good point Christian. Could you provide the scli cmd you used, we can add that. PowerFlex UI is not as intuitive or powerful as PowerStore UI. |
Credit goes to Don Khan for finding these cmds out: scli --mdm_ip (IPs, comma separated) --login --username (user) --password (pass) I do recommend expanding on the UI version's directions as well, though, for ease of use. |
I looked around in the UI and I was not able to find a way to get the Id. |
@ChristianAtDell @bharathsreekanth The only way I was able to get the volume ID through the UI is by clicking the volume in the topology section which filters for only that volume. Afterwards, in the URL, the volume UUID is present. I will update the documentation to include both the |
Thanks Fernando. It is not really easy for one to know that is the ID of the volume. I suppose we could add a footnote below the documentation to tell how to get the ID. I am not a fan of it, but I dont see any easy way. Thoughts? |
I'm not a fan of the URL approach. That may be useful as a hint or note but not as main line documentation. We should just document the scli option as a PowerFlex user should already be familiar with scli. Put the UI hint in a note. |
6702d64
038b0ad
to
6702d64
Compare
I did confirm with Powerflex engg team that there is no easy from UI to get this. Let us rely on the scli for now. |
Can we open an enhancement request so that the ID is available in the UI. |
I asked them that. waiting to hear back |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reviewed this. There is one minor edit.
2e01501
6702d64
to
2e01501
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. No edits required.
9562a36
2e01501
to
9562a36
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reviewed this. No edits are reqired.
Description
It was identified that documentation for creating static provisioning on PowerFlex was missing. Similar to other drivers that support this feature, a section for the documentation was added for consistency.
GitHub Issues
List the GitHub issues impacted by this PR:
Checklist: