Upload data annotation from CVAT to Azure Blob storage without using the manifest file

[himanshudw]

My actions before raising this issue

Read CVAT documentation to export dataset over the cloud service.
#4933 This does not solve the issue as even after creating manifest file we are not able to upload data to cloud

We expect that on the button click under the CVAT actions tab we are able to upload the annotation in a particular format to Azure blob storage.

Expected Behaviour

The annotation file should be stored in Azure blob storage

Current Behaviour

NA

Possible Solution

NA

Steps to Reproduce (for bugs)

We know that the util.py file under cvat/cvat/apps/dataset_manager needs to be updated to write the file over Azure blob storage but we are unable to get the location from where we can access the annotation file or a particular wat to use the API

Context

We are trying to use the annotation from CVAT to train our model but unable to fetch the dataset and their annotation

Your Environment

Docker version docker version :20.10.17
Operating System and version :Linux
CVAT Version :dev

[zhiltsov-max]

@Marishka17 , please look at this issue.

[Marishka17]

@himanshudw, Hi, Could you please explain why you cannot attach your Azure container with a dummy manifest file (if you are not going to use data from cloud storage to create tasks) and then use it for export annotations to Azure container?

[himanshudw]

We tried using the dummy manifest file but the UI does not show us option for uploading in Azure as per the demo shown here #4842.

Actually we want the data to be uploaded from our local computer and while we click on a train button(added in the action's menu) we would like to upload the annotation in TFrecord format for the task on Azure blob storage.

[himanshudw]

@Marishka17
We have been able to get the new UI wherein we got the option for local storage and the target storage.

We have an azure cloud storage mounted on the CVAT.

We did as per the demo(https://user-images.githubusercontent.com/49038720/188583538-43722c39-85b0-495e-8ef2-c7376b51e4f9.mp4) but after exporting the dataset in any of the format we get error as attached

[Marishka17]

@himanshudw, thanks for reporting the bug. I'll investigate.