Seagate/cortx

Update the cortx-s3samplecode to work with the newer OVA versions

r-wambui opened this issue · 5 comments

Problem

The documentation on the CORTX s3 sample code; used for testing S3 API IO using various programming languages is outdated and does not work with the new OVA. Most of them are still structured to use the OVA with 3 network interfaces.

Example:

  • During the hackathon, participants who followed the Node JS guide to make S3 IO ended up having a InvalidLocationConstraint: The specified location constraint is not valid
  • There were also issues with the endpoint URL as users could not add the port to access kubernetes cluster externally to the endpoint url

Expected behavior

The endpoint URL for example should include the Kubernetes port

How to reproduce

Set up OVA PI6 or PI7, then follow the documentation to test using either Python, Node JS etc

Deployment information

VMware Workstation pro 16 pro

Additional information

No response

For the convenience of the Seagate development team, this issue has been mirrored in a private Seagate Jira Server: https://jts.seagate.com/browse/CORTX-33918. Note that community members will not be able to access that Jira server but that is not a problem since all activity in that Jira mirror will be copied into this GitHub issue.

stale commented

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @mukul-seagate11 for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

ova issues which are reported by community https://github.com/Seagate/cortx/issues?q=is%3Aopen+is%3Aissue+label%3Aova will be further raised to QA and tracked in next sprint.

stale commented

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @mukul-seagate11 for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

#1657 is validated as per latest OVA image and no issue is observed