-
Notifications
You must be signed in to change notification settings - Fork 37
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
Allow for 92 endpoint to be used in later versions of U4V #133
Comments
@rawstorage as far as I see it's closed as completed. |
Roman, import PyU4V conn = PyU4V.U4VConn( print(version('PyU4V')) C:\Users\martip5\PycharmProjects\PyU4V_Playground\venv\Scripts\python.exe C:\Users\martip5\AppData\Roaming\JetBrains\PyCharm2023.2\scratches\scratch_4.py Process finished with exit code 0 |
Sorry, my statement was not correct. You're right it's possible to connect to Unisphere 10.1 from PyU4V 9.2.1.7. If 92 endpoint is created for Unisphere 10.1, do you know how I should run provisioning.get_srp('SRP_1') and performance.get_array_stats(metrics='ALL', start_time, end_time) functions there? |
Roman, With Unisphere 10.1 the following versions of the API are provided and supported by Unisphere { This means I can use PyU4V version 10.1/10.0 or 9.2 against this instance of Unisphere. PyU4V 10.1 is not tested and therefore blocked with an error e.g Unisphere version V9.2.1.6 does not meet the minimum requirement of v10.1.x Please upgrade your version of Unisphere to use this SDK. Exiting... You can spin off your own branch of code and create a package that will support both however that is outside the scope and we wouldn't support that as it's not tested. There are advantages to upgrading to 10.1 version especially for performance stats as you can take advantage of the enhanced api calls which will make it easier and quicker to get metrics. Also the new volumes and storage groups bulk calls get you a load of new information. I understand if you are using Embedded Unisphere this means you will need an external client to get this functionality. The alternative is to use virtual environments with the version of PyU4V for each setup and activate the correct venv with PyU4V based on version of Unisphere. |
Many thanks Paul for comprehensive details. Happy to close this discussion. |
No Problem Roman, if you need anything else just reach out. if it's not a bug though you can Open a discussion on GitHub and we are more than happy to have technical conversations.. Glad to help |
No description provided.
The text was updated successfully, but these errors were encountered: