Skip to content
This repository has been archived by the owner on Oct 25, 2023. It is now read-only.

HPE MSA 2060 API inconsistencies #12

Open
vankosa opened this issue Sep 17, 2021 · 0 comments
Open

HPE MSA 2060 API inconsistencies #12

vankosa opened this issue Sep 17, 2021 · 0 comments

Comments

@vankosa
Copy link

vankosa commented Sep 17, 2021

Good day!

I am using HPE MSA 2060 disk storage, which is declared supported in the project https://github.com/enix/san-iscsi-csi
The https://github.com/enix/san-iscsi-csi project uses the https://github.com/enix/dothill-api-go library where I found several HPE MSA 2060 API inconsistencies.

I took the HPE MSA 2060 API documentation here - https://www.intesiscon.com/ficheros/manuales-tecnicos/255-HPE-a00105313en-us-HPE-MSA-1060-2060-2062-CLI-Reference-Guide.pdf

Inconsistencies I found:

  1. https://github.com/enix/dothill-api-go/blob/master/endpoints.go#L52 - 63 documentation page. Use initiators instead of id
  2. https://github.com/enix/dothill-api-go/blob/master/endpoints.go#L57 - 116 documentation page. The initiator is used instead of host.
  3. https://github.com/enix/dothill-api-go/blob/master/endpoints.go#L71 - 450 documentation page. The initiator is used instead of host.
  4. https://github.com/enix/dothill-api-go/blob/master/endpoints.go#L95 - 336 documentation page. The initiators is used instead of host-maps.

Perhaps there are still some discrepancies, but at the moment I have found only these.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant