sodafoundation / dock Goto Github PK

Issue/Feature Description: Currently Volumes created in the NetApp SAN Driver are not having user friendly names, there is no user-friendly mechanism to identify the volumes in the NetApp Backend

Why this issue to fixed / feature is needed(give scenarios or use cases): To provide better User Experience

How to reproduce, in case of a bug:
Create Volume For NetApp ONTAP SAN driver

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Make the GET API work for Replication Feature and add the documentation for it.

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Any AZ required for replication should be created by user OR informed to user. It should not be assumed that the user knows about the requirements & Documentation / Help should be improved.

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

What happened:
After separation of Hotpot project into SODA API/DOCK/CONTROLLER we need to update CI accordingly so that project can be run independently

What you expected to happen:
CI for SODA Dock should run properly and independently

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:
In order to use the Host Based Replication from API, the user has to get information for the body from UI / CLI.
All the information should be available consistently from UI only.
More over, ID / UUIDs should not be shown on UI for any of the entities [Storage, Profile etc.]

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Any Sync Operations should have time outs associated with them, otherwise the user is kept waiting.

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description: Volume Snapshot is failed with the following reason:

E0924 15:17:14.712424   51158 ontap_san.go:412] delete volume snapshot (7b4837b9-bdb1-4f6d-be1a-deaa2e865bea) failed: error deleting snapshot: API status: failed, Reason: Snapshot copy "opensds_snapshot_7b4837b9bdb14f6dbe1adeaa2e865bea" of volume "opensds_4238af04bb8e4cd9ab3bce6a4cdc2f5e" on Vserver "svm_soda" has not expired or is locked. Use the "snapshot show -fields owners, expiry-time" command to view the expiry and lock status of the Snapshot copy., Code: 13024
E0924 15:17:14.712876   51158 dock.go:235] error occurred in dock module when delete snapshot:error deleting snapshot: API status: failed, Reason: Snapshot copy "opensds_snapshot_7b4837b9bdb14f6dbe1adeaa2e865bea" of volume "opensds_4238af04bb8e4cd9ab3bce6a4cdc2f5e" on Vserver "svm_soda" has not expired or is locked. Use the "snapshot show -fields owners, expiry-time" command to view the expiry and lock status of the Snapshot copy., Code: 13024

Why this issue to fixed / feature is needed(give scenarios or use cases): This issue needs to fix for Volume Snapshot deletion or provide valid reasons for the operations result

How to reproduce, in case of a bug:

1. Create a Volume for NetApp ONTAP SAN driver.
2. Create a Snapshot for the above volume
3. Create a Volume using above Volume Snapshot.
4. Delete the Volume Snapshot created on 2 Step

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
In the dashboard, all the information should be consistently displayed using Names of the entities not the UUID .

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Replication Vol with same name one same Host should not be created.

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Test the HBR with SODA using cURL or Postman
Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

What happened:
Add new storage backend support for EMC VMAX array
What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:
A host can connect volume after delete attachment using "osdsctl volume attachment delete" command.

What you expected to happen:
A host cannot connect to volume after delete attachment.

How to reproduce it (as minimally and precisely as possible):

1. create host using "osdsctl host create" command
2. create NetApp volume using "osdsctl volume create" command
3. create attachment for the host to the volume using "osdsctl volume attachment" command
4. connect and disconnect to the volume from the host using iscsiadm command
5. delete the attahcment that is created in procedure 3
6. try to connect the volume from the host

Anything else we need to know?:
I think this issue cause trouble in situation that user can use command (e.g. iscsiadm) to connect to volume manually.

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
SODA doesn't have the capability about ONTAP SVM user auth and SVM Interface.
To access ONTAP, SODA need to use ONTAP Cluster admin ID and Cluster management Interface.

Why this issue to fixed / feature is needed(give scenarios or use cases):
Service providers normaly provides multi-tenant storage service by SVM.
If SODA use only Cluster admin/mgmt, another tenant customer could access another tenant's storage resource through SODA.

How to reproduce, in case of a bug:
This is a feature request.

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add delete fileshare for Netapp NAS fileshare driver
Why this issue to fixed / feature is needed(give scenarios or use cases):
Support NetApp NAS feature APIs
Linked issue #35
How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Hosts should be discovered and the Replication feature should be driven from the Host
Context Menu / UI .

At present , the Replication Feature is driven from the Volumes., however as its a Host Based Replication, it would be more apt for the functionality to be driven from the Host itself rather than the volumes.

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Profile modification allows only modifying the Name, it should permit the user to modify any of the attributes that were provided during creation.

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

What happened:
Add support for NetApp E-Series storage
What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:
Explore the Data Replication and Failover feature in Kubernetes for Storages, specifically for CSI

Why this issue to fixed / feature is needed(give scenarios or use cases):
This report is needed to analyze the industry standards/mechanism for dealing with DR and Failover for Volumes in CO systems

In this task we need to explore the below listed items :

• DR and Failover feature in K8s for Volumes
• DR in IBM CSI driver
• DR in NetApp Trident CSI driver
• DR in PortWork
• DR in other competitive Solutions

Issue/Feature Description:
Test, Verify and Fix the Block Snapshot into S3

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind feature

What happened:
Need to automate the test cases for optimisation.

What you expected to happen:
Automated test cases instead of Manual

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:
Error in the Replication functionality should be meaningful and give suggestions to user to resolve it.

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Endusers can take a snapshot of Volume/FileShare on SODA dashboard.
However, they cannot recover volume/fileshare from these snapshots.

Why this issue to fixed / feature is needed(give scenarios or use cases):
Snapshot is an important feature.

How to reproduce, in case of a bug:
This is a feature request.

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

What happened:
Update test cases for all the drivers and also update the automation status
What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:
Duplicate Hosts with the same attributes should not be created from UI / API.

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add snapshot create/delete/List APIs for NetApp Fileshare

Why this issue to fixed / feature is needed(give scenarios or use cases):
To support snapshot feature for NetApp

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Is this a BUG REPORT or FEATURE REQUEST?:
BUG

Uncomment only one, leave it on its own line:

/kind bug

What happened:
The modules SODA dock and SODA controller has been separated out from the hotpot project. After that segregation also, there are some inter-dependencies in gRPC client server communication and protobuf files, which leads to the build and CI issues. Plus the projects are not totally independent.

What you expected to happen:
Both the projects/modules should run successfully after separation without any dependency on the other. The proto file should not be dependent on what version of gRPC we use in the project. Basically the communication between dock and controller should be successful and independent.

How to reproduce it (as minimally and precisely as possible):
Just try to make a build with different gRPC versions , there will be a failure in protobuf file.

Anything else we need to know?:
Need to come up with a generic solution to remove this dependency

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:
Deletion of Fileshare whose name was updated, goes in error state and deleted

Why this issue to fixed / feature is needed(give scenarios or use cases):
Bug as update only updates the Name in SODA DB and not in actual storage backend/

How to reproduce, in case of a bug:
Create FS
Update name of FS
Try deleting FS with the ID
FS doesn't get deleted and goes in errorDeleting state

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

What happened:
Even though driver config "provisioningPolicy" is set to "thin", I cannot create volumes over capacity of aggregate.

What you expected to happen:
The driver can overcommit when provisioning volumes.

How to reproduce it (as minimally and precisely as possible):

• Set "provisioningPolicy" in "/etc/opensds/driver/netapp_ontap_san.yaml" to "thin"
• Try to create volume over capacity of aggregate.

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version: v0.10.0(Daito Release)
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:
Make the POST API work and add documentation / help for it.

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

What happened:
We want to use NetApp for not only block storage, but also file storage.
Is there a plan for implement fileshare driver?

What you expected to happen:
We can use NetApp as file storage through SODA.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
When a command executes with exec.Command, it should be called with timeout. On one my setup "modprobe nvme-rdma" was hung and it didn't came out for long. There was no module for nvme-rdma on the host.

What you expected to happen:
Timeout of the command executed by the client
golang/go#9580

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

What happened: Build is failed due to different protoc Versions

What you expected to happen: Build should be successful

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Hotpot(release/branch) version:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

Issue/Feature Description:

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
As part of supporting Netapp Fileshare driver, user should be able to create fileshare on the NAS storage

Why this issue to fixed / feature is needed(give scenarios or use cases):
Add support for Netapp NAS.
Linked issue #35

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Rename docker images to sodafoundation/dock

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
SODA Dock framework should support:

• Support NetApp SAN and NAS co-existence and can use same pool
• Support multiple Block and File drivers
• Support multiple pool for the same driver
• Support muti-tenancy

Why this issue to fixed / feature is needed(give scenarios or use cases):

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
Add unit tests and achieve coverage >70%

Why this issue to fixed / feature is needed(give scenarios or use cases):
To imporove code quality and covergae

How to reproduce, in case of a bug:

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

Issue/Feature Description:
I created a volume from the dashboard using a profile which has snapshot policy enabled. When I created a snapshot of this volume the dock crashed. The error log is given below.

Why this issue to fixed / feature is needed(give scenarios or use cases):
All subsequent actions / api calls that involve the dock after this step will throw error. This renders the system unusable.
I was able to use the system after restarting the dock manually.

How to reproduce, in case of a bug:

1. Login to dashboard.
2. Create a profile with snapshot policy enabled.
3. Create a volume with this profile.
4. Create a snapshot of this volume, specify a different profile from the drop down list.
5. Check the volume details. Snapshot will be in error.
6. Try to create another volume or fileshare. or try to delete the snapshot created in 5.
7. All will show error.
   Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)